tscs0005 A PDF

TS-3GB-C.S0005-Av6.
Upper Layer (Layer 3)

Signaling Standard for cdma2000
Spread Spectrum Systems,
Release A -Version6.0
May 28, 2002
THE TELECOMMUNICATION TECHNOLOGY COMMITTEE

TS-3GB-C.S0005-Av6.0
Upper Layer (Layer 3) Signaling Standard
for cdma2000 Spread Spectrum Systems, Release A -Version6.0
<Remarks>
1. Application level of English description
Application level : E2
English description is included in the text and figures of main body, annexes and appendices.
2. Relationship with international recommendations and standards

This standard is standardized based on the Technical Specification C.S0005-A(Version 6.0) approved by 3GPP2.
3. Departures from international recommendations

Changes to original standard
Standards referred to in theoriginal standard, which are replaced by TTC standards.
Standards referred to in the original standard should be replaced by derived TTC standards.
4. IPR
There is no specific description about IPR in this standard.
5. Technical Committee
Technical Committee 6
i
C.S0005-A v6.0
Date: February 2002
Upper Layer (Layer 3) Signaling Standard for

cdma2000 Spread Spectrum Systems – Release
A Addendum 2
COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational
Partners may copyright and issue documents or standards publications in individual Organizational
Partner's name based on this document. Requests for reproduction of this document should be
directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual
Organizational Partner's documents should be directed to that Organizational Partner. See
www.3gpp2.org for more information.
3GPP2 C.S0005-A v6.0
CONTENTS
1 FOREWORD .................................................................................................................... xl
2 NOTES .......................................................................................................................... xlii
3 REFERENCES ...............................................................................................................xliv
4 1. GENERAL ................................................................................................................ 1-1
5 1.1 Terms and Numeric Information ............................................................................ 1-1
6 1.1.1 Terms ............................................................................................................. 1-1
7 1.1.2 Numeric Information ..................................................................................... 1-24
8 1.1.2.1 Reserved.................................................................................................. 1-24
9 1.1.2.2 CDMA Numeric Information ..................................................................... 1-24
10 1.2 Signaling Architecture......................................................................................... 1-45
11 1.3 Signaling and Functionality................................................................................. 1-45
12 1.3.1 General Architecture ..................................................................................... 1-45
13 1.3.2 Interface to Layer 2........................................................................................ 1-45
14 1.3.2.1 Message Control and Status Block (MCSB) ............................................... 1-45
15 1.3.2.2 Interface Primitives .................................................................................. 1-46
16 1.3.3 Reserved ....................................................................................................... 1-48
17 1.3.4 Functional Description ................................................................................. 1-48
18 1.3.5 PDU Transmission and Reception ................................................................. 1-48
19 2. REQUIREMENTS FOR MOBILE STATION CDMA OPERATION ................................... 2-1
20 2.1 Reserved ............................................................................................................... 2-1
21 2.2 Reserved ............................................................................................................... 2-1
22 2.3 Security and Identification .................................................................................... 2-1
23 2.3.1 Mobile Station Identification Number ............................................................... 2-1
24 2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S.......................................................... 2-3
25 2.3.1.2 Encoding of IMSI_M_11_12 and IMSI_T_11_12 ........................................... 2-6
26 2.3.1.3 Encoding of the MCC_M and MCC_T .......................................................... 2-6
27 2.3.1.4 Mobile Directory Number ........................................................................... 2-6
28 2.3.2 Electronic Serial Number ................................................................................. 2-6
29 2.3.3 Station Class Mark .......................................................................................... 2-6
30 2.3.4 Registration Memory........................................................................................ 2-7
31 2.3.5 Access Overload Class ..................................................................................... 2-8
i
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.3.6 Public Long Code Mask ................................................................................... 2-9
2 2.3.7 Reserved ......................................................................................................... 2-9
3 2.3.8 Home System and Network Identification......................................................... 2-9
4 2.3.9 Local Control Option ....................................................................................... 2-9
5 2.3.10 Preferred Operation Selection ........................................................................ 2-9
6 2.3.10.1 Preferred System ..................................................................................... 2-9
7 2.3.10.2 Preferred CDMA or Analog ..................................................................... 2-10
8 2.3.11 Discontinuous Reception ............................................................................. 2-10
9 2.3.12 Authentication, Encryption of Signaling Information/User Data and Voice

10 Privacy ....................................................................................................... 2-10
11 2.3.12.1 Authentication ...................................................................................... 2-10
12 2.3.12.1.1 Shared Secret Data (SSD)................................................................. 2-10
13 2.3.12.1.2 Random Challenge Memory (RAND) .................................................. 2-11

14 2.3.12.1.3 Call History Parameter (COUNTs-p)................................................... 2-11
15 2.3.12.1.4 Unique Challenge-Response Procedure ............................................. 2-11
16 2.3.12.1.5 Updating the Shared Secret Data (SSD) ............................................ 2-12
17 2.3.12.2 Signaling Message Encryption ............................................................... 2-15
18 2.3.12.2.1 Encrypted Messages on the f-dsch.................................................... 2-16
19 2.3.12.2.2 Encrypted Messages on the r-dsch ................................................... 2-19
20 2.3.12.3 Voice Privacy ......................................................................................... 2-21
21 2.3.12.4 Extended Encryption for Signaling Message and User Information .......... 2-22
22 2.3.12.4.1 Extended Encryption for Signaling Messages .................................... 2-22
23 2.3.12.4.1.1 Extended Encryption for Signaling on f/r-csch............................ 2-23
24 2.3.12.4.1.2 Extended Encryption for Signaling on f/r-dsch ........................... 2-24
25 2.3.12.4.1.3 Signaling Encryption/Decryption Procedures.............................. 2-24
26 2.3.12.4.1.4 Computation of the 8-bit Layer 3 PDU CRC Field ........................ 2-27
27 2.3.12.4.1.5 Duplicate Detection of Encrypted Messages ................................ 2-28
28 2.3.12.4.2 Extended Encryption for User Information........................................ 2-29
29 2.3.12.4.2.1 User Information Encryption/Decryption Procedures .................. 2-30
30 2.3.12.4.3 Interface to the Encryption Algorithms .......................................... 2-30
31 2.3.12.4.4 Encryption Negotiation..................................................................... 2-35
32 2.3.12.4.5 Computation of ENC_SEQ_H_SIG..................................................... 2-37
ii
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.3.13 Lock and Maintenance Required Orders ....................................................... 2-37
2 2.3.14 Mobile Station Revision Identification........................................................... 2-38
3 2.3.15 Temporary Mobile Station Identity................................................................ 2-38
4 2.3.15.1 Overview................................................................................................ 2-38
5 2.3.15.2 TMSI Assignment Memory...................................................................... 2-39
6 2.4 Accumulated Statistics........................................................................................ 2-40
7 2.4.1 Monitored Quantities and Statistics ............................................................... 2-40
8 2.4.2 Accumulated Paging, Broadcast, and Forward Common Control Channel

9 Statistics .................................................................................................... 2-40
10 2.5 Reserved ............................................................................................................. 2-40
11 2.6 Layer 3 Processing .............................................................................................. 2-41
12 2.6.1 Mobile Station Initialization State .................................................................. 2-43
13 2.6.1.1 System Determination Substate ............................................................... 2-45
14 2.6.1.1.1 Custom System Selection Process ....................................................... 2-51
15 2.6.1.1.2 System Selection Using Current Redirection Criteria ........................... 2-51
16 2.6.1.1.3 System Selection Using System Reselection Criteria ............................ 2-52
17 2.6.1.1.4 Acquiring the Selected System ............................................................ 2-53
18 2.6.1.2 Pilot Channel Acquisition Substate........................................................... 2-53
19 2.6.1.3 Sync Channel Acquisition Substate .......................................................... 2-53
20 2.6.1.4 Timing Change Substate .......................................................................... 2-57
21 2.6.2 Mobile Station Idle State ................................................................................ 2-59
22 2.6.2.1 Idle Procedures ........................................................................................ 2-61
23 2.6.2.1.1 Forward Channel Monitoring Procedures ............................................ 2-61
24 2.6.2.1.1.1 General Overview ......................................................................... 2-61
25 2.6.2.1.1.1.1 General Overview for Individually Addressed Messages ............ 2-62
26 2.6.2.1.1.1.1.1 Overview of Stopping Monitoring via the General Page

27 Message .......................................................................... 2-63
28 2.6.2.1.1.1.1.2 Overview of Stopping Monitoring via the Universal Page

29 Message .......................................................................... 2-65
30 2.6.2.1.1.1.2 Overview of Broadcast Messages on Paging Channel ................ 2-65
31 2.6.2.1.1.1.2.1 Method 1: Multi-Slot Broadcast Message Transmission ...... 2-65
32 2.6.2.1.1.1.2.2 Method 2: Periodic Broadcast Paging ................................. 2-66
iii
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.6.2.1.1.1.3 Overview of Broadcast Messages on Broadcast Control

2 Channel ............................................................................... 2-67
3 2.6.2.1.1.1.3.1 Method 1: Multi-Slot Enhanced Broadcast Paging.............. 2-67
4 2.6.2.1.1.1.3.2 Method 2: Periodic Enhanced Broadcast Paging ................. 2-68
5 2.6.2.1.1.2 Non-Slotted Mode Requirements................................................... 2-68
6 2.6.2.1.1.3 Slotted Mode Requirements .......................................................... 2-68
7 2.6.2.1.1.3.1 Monitoring Assigned Slots....................................................... 2-69
8 2.6.2.1.1.3.2 Determination of the Slot Cycle Index ..................................... 2-71
9 2.6.2.1.1.3.3 Slot Cycles for Broadcast Message Transmission ..................... 2-72
10 2.6.2.1.1.3.3.1 Slot Cycles for Broadcast Message Transmission on the

11 Paging Channel............................................................... 2-72
12 2.6.2.1.1.3.3.2 Slot Cycles for Broadcast Message Transmission on the

13 Forward Common Control Channel.................................. 2-72
14 2.6.2.1.1.3.4 Monitoring Paging Channel Broadcasts ................................... 2-73
15 2.6.2.1.1.3.5 Support of Broadcast Delivery Options on the Paging Channel

16 ............................................................................................ 2-74
17 2.6.2.1.1.3.6 Monitoring the Forward Common Control Channel for the

18 Enhanced Broadcast Page .................................................... 2-74
19 2.6.2.1.1.3.7 Support of Broadcast Delivery Options on the Forward

20 Common Control Channel/Broadcast Control Channel.......... 2-75
21 2.6.2.1.1.4 Common Channel Supervision ..................................................... 2-75
22 2.6.2.1.2 Quick Paging Channel Monitoring Procedures .................................... 2-75
23 2.6.2.1.2.1 Overview...................................................................................... 2-75
24 2.6.2.1.2.2 Requirements .............................................................................. 2-78
25 2.6.2.1.3 Registration ....................................................................................... 2-80
26 2.6.2.1.4 Idle Handoff....................................................................................... 2-80
27 2.6.2.1.4.1 Pilot Search ................................................................................. 2-80
28 2.6.2.1.4.2 Idle Handoff Procedures ............................................................... 2-82
29 2.6.2.1.5 Primary Broadcast Control Channel Monitoring.................................. 2-92
30 2.6.2.1.5.1 General Overview ......................................................................... 2-92
31 2.6.2.1.5.2 Requirements .............................................................................. 2-92
32 2.6.2.1.6 System Reselection Procedures .......................................................... 2-92
33 2.6.2.1.7 Slotted Timer Expiration .................................................................... 2-93
iv
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.6.2.2 Response to Overhead Information Operation ........................................... 2-93
2 2.6.2.2.1 System Parameters Message ............................................................... 2-97
3 2.6.2.2.1.1 Stored Parameters ........................................................................ 2-97
4 2.6.2.2.1.2 Paging Channel Assignment Change ........................................... 2-101
5 2.6.2.2.1.3 RESCAN Parameter .................................................................... 2-101
6 2.6.2.2.1.4 Roaming Status.......................................................................... 2-101
7 2.6.2.2.1.5 Registration................................................................................ 2-101
8 2.6.2.2.1.6 Slot Cycle Index.......................................................................... 2-101
9 2.6.2.2.1.7 PACA Disable for SID Change ..................................................... 2-102
10 2.6.2.2.1.8 Retry Delay Disable for Packet Zone ID or SID/NID Change......... 2-102
11 2.6.2.2.1.9 Encryption key reset for SID/NID Change ................................... 2-102
12 2.6.2.2.2 Access Parameters Message.............................................................. 2-102
13 2.6.2.2.3 Neighbor List Message ...................................................................... 2-104
14 2.6.2.2.4 CDMA Channel List Message ............................................................ 2-105
15 2.6.2.2.5 Extended System Parameters Message.............................................. 2-106
16 2.6.2.2.6 Global Service Redirection Message .................................................. 2-111
17 2.6.2.2.7 Extended Neighbor List Message....................................................... 2-112
18 2.6.2.2.8 General Neighbor List Message ......................................................... 2-113
19 2.6.2.2.9 User Zone Identification Message...................................................... 2-117
20 2.6.2.2.10 Private Neighbor List Message......................................................... 2-118
21 2.6.2.2.11 Extended Global Service Redirection Message ................................. 2-119
22 2.6.2.2.12 Extended CDMA Channel List Message Overview ............................ 2-120
23 2.6.2.2.12.1 Extended CDMA Channel List Message on Paging Channel ........ 2-120
24 2.6.2.2.12.2 Extended CDMA Channel List Message on Primary Broadcast

25 Control Channel....................................................................... 2-121
26 2.6.2.2.13 ANSI-41 System Parameters Message.............................................. 2-123
27 2.6.2.2.13.1 Stored Parameters .................................................................... 2-123
28 2.6.2.2.13.2 Roaming Status........................................................................ 2-126
29 2.6.2.2.13.3 Registration.............................................................................. 2-126
30 2.6.2.2.13.4 PACA Disable for SID Change ................................................... 2-126
31 2.6.2.2.14 MC-RR Parameters Message ........................................................... 2-126
32 2.6.2.2.14.1 Stored Parameters .................................................................... 2-127
v
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.6.2.2.14.2 Slot Cycle Index ........................................................................2-132
2 2.6.2.2.14.3 Forward Common Control Channel Assignment Change.............2-132
3 2.6.2.2.15 Enhanced Access Parameters Message ............................................2-132
4 2.6.2.2.16 ANSI-41 RAND Message ..................................................................2-138
5 2.6.2.2.17 Universal Neighbor List Message .....................................................2-138
6 2.6.2.3 Mobile Station Page Match Operation......................................................2-142
7 2.6.2.4 Mobile Station Order and Message Processing Operation .........................2-144
8 2.6.2.5 Mobile Station Origination Operation ......................................................2-154
9 2.6.2.6 Mobile Station Message Transmission Operation .....................................2-154
10 2.6.2.7 Mobile Station Power-Down Operation ....................................................2-155
11 2.6.2.8 Mobile Station PACA Cancel Operation ...................................................2-155
12 2.6.3 System Access State.....................................................................................2-155
13 2.6.3.1 Access Procedures ..................................................................................2-156
14 2.6.3.1.1 Access Attempts ...............................................................................2-156
15 2.6.3.1.2 Reserved...........................................................................................2-157
16 2.6.3.1.3 Handoffs...........................................................................................2-157
17 2.6.3.1.3.1 Pilot Search ................................................................................2-158
18 2.6.3.1.3.2 Access Handoff ...........................................................................2-158
19 2.6.3.1.3.3 Access Probe Handoff ..................................................................2-160
20 2.6.3.1.4 System Access State Exit Procedures.................................................2-161
21 2.6.3.1.5 Reserved...........................................................................................2-162
22 2.6.3.1.6 Full-TMSI Timer ...............................................................................2-162
23 2.6.3.1.7 Monitoring Pilots ..............................................................................2-162
24 2.6.3.1.7.1 Generation of the Initial Access Handoff List................................2-162
25 2.6.3.1.7.2 Update of the Access Handoff List................................................2-163
26 2.6.3.1.7.3 Generation of the Other Reported List .........................................2-163
27 2.6.3.1.7.4 Update of OTHER_REPORTED_LIST ............................................2-163
28 2.6.3.1.8 Paging Channel and Forward Common Control Channel/ Primary

29 Broadcast Control Channel Monitoring ...........................................2-164
30 2.6.3.2 Update Overhead Information Substate ..................................................2-165
31 2.6.3.3 Page Response Substate .........................................................................2-169
32 2.6.3.4 Mobile Station Order/Message Response Substate ..................................2-201
vi
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.6.3.5 Mobile Station Origination Attempt Substate .......................................... 2-206
2 2.6.3.6 Registration Access Substate ................................................................. 2-243
3 2.6.3.7 Mobile Station Message Transmission Substate ...................................... 2-249
4 2.6.3.8 PACA Cancel Substate ........................................................................... 2-256
5 2.6.4 Mobile Station Control on the Traffic Channel State ..................................... 2-261
6 2.6.4.1 Special Functions and Actions ............................................................... 2-263
7 2.6.4.1.1 Forward Traffic Channel Power Control............................................. 2-263
8 2.6.4.1.1.1 Forward Traffic Channel Power Control Initialization ................... 2-266
9 2.6.4.1.1.2 Processing the Power Control Parameters Message ...................... 2-266
10 2.6.4.1.1.3 Processing the Power Control Message ........................................ 2-267
11 2.6.4.1.2 Service Configuration and Negotiation .............................................. 2-269
12 2.6.4.1.2.1 Use of Variables ......................................................................... 2-274
13 2.6.4.1.2.1.1 Maintaining the Service Request Sequence Number ............... 2-274
14 2.6.4.1.2.1.2 Maintaining the Service Negotiation Indicator Variable........... 2-274
15 2.6.4.1.2.1.3 Maintaining the Service Option Request Number ................... 2-274
16 2.6.4.1.2.2 Service Subfunctions.................................................................. 2-274
17 2.6.4.1.2.2.1 Normal Service Subfunction .................................................. 2-277
18 2.6.4.1.2.2.2 Waiting for Service Request Message Subfunction.................. 2-279
19 2.6.4.1.2.2.3 Waiting for Service Response Message Subfunction ............... 2-281
20 2.6.4.1.2.2.4 Waiting for Service Connect Message Subfunction ................. 2-284
21 2.6.4.1.2.2.5 Waiting for Service Action Time Subfunction ......................... 2-286
22 2.6.4.1.2.2.6 SO Negotiation Subfunction .................................................. 2-290
23 2.6.4.1.3 Ordering of Messages ....................................................................... 2-293
24 2.6.4.1.4 Processing the In-Traffic System Parameters Message ....................... 2-293
25 2.6.4.1.5 Message Action Times ...................................................................... 2-294
26 2.6.4.1.6 Long Code Transition Request Processing ......................................... 2-295
27 2.6.4.1.7 Power Up Function (PUF).................................................................. 2-296
28 2.6.4.1.7.1 Processing the Power Up Function Message................................. 2-297
29 2.6.4.1.7.2 Power Up Function Procedures ................................................... 2-298
30 2.6.4.1.7.2.1 PUF Probe On Serving Frequency .......................................... 2-298
31 2.6.4.1.7.2.2 PUF Probe On PUF Target Frequency..................................... 2-299
vii
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.6.4.1.7.3 Processing the Power Up Function Completion Message ...............2-300
2 2.6.4.1.8 Forward Traffic Channel Supervision.................................................2-301
3 2.6.4.1.9 Processing the Extended Release Message and the Extended Release
4 Mini Message .................................................................................2-301
5 2.6.4.1.10 Processing the Resource Allocation Message and Resource

6 Allocation Mini Message..................................................................2-302
7 2.6.4.1.11 Reserved.........................................................................................2-303
8 2.6.4.1.12 Processing the Service Configuration Record....................................2-303
9 2.6.4.1.13 Processing the Non-Negotiable Service Configuration Record ............2-305
10 2.6.4.1.14 Processing the Security Mode Command Message ............................2-314
11 2.6.4.2 Traffic Channel Initialization Substate ....................................................2-315
12 2.6.4.3 Traffic Channel Substate ........................................................................2-326
13 2.6.4.4 Release Substate ....................................................................................2-341
14 2.6.5 Registration .................................................................................................2-349
15 2.6.5.1 Forms of Registration .............................................................................2-349
16 2.6.5.1.1 Power-Up Registration ......................................................................2-350
17 2.6.5.1.2 Power-Down Registration ..................................................................2-351
18 2.6.5.1.3 Timer-Based Registration ..................................................................2-351
19 2.6.5.1.4 Distance-Based Registration .............................................................2-352
20 2.6.5.1.5 Zone-Based Registration ...................................................................2-352
21 2.6.5.1.6 Parameter-Change Registration.........................................................2-354
22 2.6.5.1.7 Ordered Registration.........................................................................2-355
23 2.6.5.1.8 Implicit Registration .........................................................................2-355
24 2.6.5.1.9 Traffic Channel Registration..............................................................2-355
25 2.6.5.1.10 User Zone Registration....................................................................2-356
26 2.6.5.1.11 Encryption Re-sync Required Registration .......................................2-356
27 2.6.5.2 Systems and Networks ...........................................................................2-356
28 2.6.5.3 Roaming ................................................................................................2-357
29 2.6.5.4 Registration Timers and Indicators .........................................................2-359
30 2.6.5.5 Registration Procedures..........................................................................2-359
31 2.6.5.5.1 Actions in the Mobile Station Initialization State................................2-359
viii
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.6.5.5.1.1 Power-Up or Change to a Different Operating Mode, Band Class,

2 Serving System, or Frequency Block ......................................... 2-359
3 2.6.5.5.1.2 Timer Maintenance..................................................................... 2-360
4 2.6.5.5.1.3 Entering the Mobile Station Idle State ......................................... 2-360
5 2.6.5.5.2 Actions in the Mobile Station Idle State............................................. 2-360
6 2.6.5.5.2.1 Idle Registration Procedures ....................................................... 2-360
7 2.6.5.5.2.2 Processing the Registration Fields of the System Parameters

8 Message and ANSI-41 System Parameters Message ................... 2-362
9 2.6.5.5.2.3 Ordered Registration .................................................................. 2-362
10 2.6.5.5.2.4 Power Off ................................................................................... 2-362
11 2.6.5.5.2.5 Full-TMSI Timer Expiration ........................................................ 2-363
12 2.6.5.5.3 Actions in the System Access State................................................... 2-363
13 2.6.5.5.3.1 Successful Access, Registration, or Implicit Registration.............. 2-363
14 2.6.5.5.3.2 Unsuccessful Access................................................................... 2-365
15 2.6.5.5.3.3 Power Off ................................................................................... 2-366
16 2.6.5.5.4 Actions in the Mobile Station Control on the Traffic Channel State .... 2-366
17 2.6.5.5.4.1 Traffic Channel Initialization....................................................... 2-366
18 2.6.5.5.4.2 Timer Maintenance..................................................................... 2-366
19 2.6.5.5.4.3 Processing the Mobile Station Registered Message ....................... 2-367
20 2.6.5.5.4.4 Power Off ................................................................................... 2-368
21 2.6.6 Handoff Procedures ..................................................................................... 2-368
22 2.6.6.1 Overview ............................................................................................... 2-368
23 2.6.6.1.1 Types of Handoff .............................................................................. 2-368
24 2.6.6.1.2 Pilot Sets ......................................................................................... 2-369
25 2.6.6.2 Requirements ........................................................................................ 2-370
26 2.6.6.2.1 Pilot Search ..................................................................................... 2-370
27 2.6.6.2.2 Pilot Strength Measurements............................................................ 2-373
28 2.6.6.2.3 Handoff Drop Timer.......................................................................... 2-374
29 2.6.6.2.4 Pilot PN Phase.................................................................................. 2-375
30 2.6.6.2.5 Handoff Messages ............................................................................ 2-375
31 2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages ............ 2-375
32 2.6.6.2.5.1.1 Processing of the Forward Supplemental Burst Assignment ... 2-449
ix
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.6.6.2.5.1.2 Processing of the Reverse Supplemental Burst Assignment.....2-452
2 2.6.6.2.5.2 Processing of Reverse Traffic Channel Handoff Messages..............2-457
3 2.6.6.2.6 Set Maintenance ...............................................................................2-460
4 2.6.6.2.6.1 Maintenance of the Active Set......................................................2-460
5 2.6.6.2.6.2 Maintenance of the Candidate Set ...............................................2-461
6 2.6.6.2.6.3 Maintenance of the Neighbor Set .................................................2-461
7 2.6.6.2.7 Soft Handoff .....................................................................................2-463
8 2.6.6.2.7.1 Forward Traffic Channel Processing.............................................2-463
9 2.6.6.2.7.2 Reverse Traffic Channel Power Control During Soft Handoff .........2-463
10 2.6.6.2.7.3 Starting Periodic Search following Soft Handoff............................2-464
11 2.6.6.2.8 CDMA-to-CDMA Hard Handoff ..........................................................2-464
12 2.6.6.2.8.1 Hard Handoff without Return on Failure......................................2-464
13 2.6.6.2.8.2 Hard Handoff with Return on Failure...........................................2-465
14 2.6.6.2.8.2.1 Restoring the Configuration ...................................................2-470
15 2.6.6.2.8.3 Search of Pilots on the CDMA Candidate Frequency.....................2-473
16 2.6.6.2.8.3.1 CDMA Candidate Frequency Single Search.............................2-473
17 2.6.6.2.8.3.2 Candidate Frequency Periodic Search ....................................2-474
18 2.6.6.2.8.3.3 Candidate Frequency Pilot Measurements ..............................2-478
19 2.6.6.2.8.3.4 Aborting CDMA Candidate Frequency Periodic Search ............2-481
20 2.6.6.2.9 CDMA-to-Analog Handoff ..................................................................2-481
21 2.6.6.2.10 Search of Analog Frequencies..........................................................2-481
22 2.6.6.2.10.1 Analog Frequencies Single Search .............................................2-482
23 2.6.6.2.10.2 Analog Frequencies Periodic Search...........................................2-483
24 2.6.6.2.10.3 Analog Frequency Measurements ..............................................2-486
25 2.6.6.2.10.4 Aborting Analog Frequencies Periodic Search .............................2-488
26 2.6.6.2.11 Processing of Reverse Supplemental Code Channels and Reverse

27 Supplemental Channels..................................................................2-488
28 2.6.6.2.12 Periodic Serving Frequency Pilot Report Procedure...........................2-489
29 2.6.6.3 Examples ...............................................................................................2-490
30 2.6.7 Hash Functions and Randomization .............................................................2-496
31 2.6.7.1 Hash Function .......................................................................................2-496
32 2.6.7.2 Pseudorandom Number Generator ..........................................................2-497
x
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.6.8 CODE_CHAN_LISTs Maintenance................................................................. 2-498
2 2.6.9 CDMA Tiered Services.................................................................................. 2-500
3 2.6.9.1 Overview ............................................................................................... 2-500
4 2.6.9.1.1 Definition......................................................................................... 2-500
5 2.6.9.1.2 Types of User Zones ......................................................................... 2-500
6 2.6.9.2 Requirements ........................................................................................ 2-501
7 2.6.9.2.1 User Zone Operation in the Mobile Station Idle State:........................ 2-501
8 2.6.9.2.2 User Zone Operation in the Mobile Station Control on the Traffic
9 Channel State................................................................................ 2-502
10 2.6.10 Call Control Processing .............................................................................. 2-502
11 2.6.10.1 Alerting ............................................................................................... 2-505
12 2.6.10.1.1 Waiting for Order Substate ............................................................. 2-505
13 2.6.10.1.2 Waiting for Mobile Station Answer Substate .................................... 2-507
14 2.6.10.2 Conversation Substate ......................................................................... 2-510
15 2.6.10.3 Call Release Substate........................................................................... 2-517
16 2.7 PDU Formats for Mobile Stations....................................................................... 2-519
17 2.7.1.1 Reserved................................................................................................ 2-520
18 2.7.1.2 Reserved................................................................................................ 2-520
19 2.7.1.3 PDU Formats on r-csch.......................................................................... 2-520
20 2.7.1.3.1 Reserved .......................................................................................... 2-520
21 2.7.1.3.2 PDU Contents .................................................................................. 2-520
22 2.7.1.3.2.1 Registration Message .................................................................. 2-521
23 2.7.1.3.2.2 Order Message ........................................................................... 2-529
24 2.7.1.3.2.3 Data Burst Message ................................................................... 2-530
25 2.7.1.3.2.4 Origination Message ................................................................... 2-532
26 2.7.1.3.2.5 Page Response Message .............................................................. 2-553
27 2.7.1.3.2.6 Authentication Challenge Response Message............................... 2-565
28 2.7.1.3.2.7 Status Response Message ........................................................... 2-566
29 2.7.1.3.2.8 TMSI Assignment Completion Message........................................ 2-567
30 2.7.1.3.2.9 PACA Cancel Message................................................................. 2-568
31 2.7.1.3.2.10 Extended Status Response Message .......................................... 2-569
32 2.7.1.3.2.11 Device Information Message...................................................... 2-571
xi
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.7.1.3.2.12 Security Mode Request Message ................................................2-572
2 2.7.2 r-dsch.........................................................................................................2-574
3 2.7.2.1 Reserved ................................................................................................2-574
4 2.7.2.2 Reserved ................................................................................................2-574
5 2.7.2.3 PDU Formats for Messages on r-dsch......................................................2-574
6 2.7.2.3.1 Reserved...........................................................................................2-577
7 2.7.2.3.2 Message Body Contents ....................................................................2-577
8 2.7.2.3.2.1 Order Message ............................................................................2-578
9 2.7.2.3.2.2 Authentication Challenge Response Message ...............................2-579
10 2.7.2.3.2.3 Flash With Information Message..................................................2-580
11 2.7.2.3.2.4 Data Burst Message ....................................................................2-581
12 2.7.2.3.2.5 Pilot Strength Measurement Message ..........................................2-583
13 2.7.2.3.2.6 Power Measurement Report Message ...........................................2-585
14 2.7.2.3.2.7 Send Burst DTMF Message .........................................................2-589
15 2.7.2.3.2.8 Status Message...........................................................................2-591
16 2.7.2.3.2.9 Origination Continuation Message...............................................2-592
17 2.7.2.3.2.10 Handoff Completion Message.....................................................2-594
18 2.7.2.3.2.11 Parameters Response Message ..................................................2-595
19 2.7.2.3.2.12 Service Request Message ...........................................................2-596
20 2.7.2.3.2.13 Service Response Message.........................................................2-598
21 2.7.2.3.2.14 Service Connect Completion Message ........................................2-600
22 2.7.2.3.2.15 Service Option Control Message.................................................2-601
23 2.7.2.3.2.16 Status Response Message..........................................................2-602
24 2.7.2.3.2.17 TMSI Assignment Completion Message ......................................2-603
25 2.7.2.3.2.18 Supplemental Channel Request Message ...................................2-604
26 2.7.2.3.2.19 Candidate Frequency Search Response Message ........................2-611
27 2.7.2.3.2.20 Candidate Frequency Search Report Message ............................2-614
28 2.7.2.3.2.21 Periodic Pilot Strength Measurement Message............................2-619
29 2.7.2.3.2.22 Outer Loop Report Message .......................................................2-623
30 2.7.2.3.2.23 Resource Request Message ........................................................2-625
31 2.7.2.3.2.24 Resource Request Mini Message ................................................2-626
32 2.7.2.3.2.25 Extended Release Response Message .........................................2-627
xii
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.7.2.3.2.26 Extended Release Response Mini Message ................................. 2-628
2 2.7.2.3.2.27 Pilot Strength Measurement Mini Message ................................ 2-629
3 2.7.2.3.2.28 Supplemental Channel Request Mini Message ........................... 2-630
4 2.7.2.3.2.29 Resource Release Request Message ........................................... 2-631
5 2.7.2.3.2.30 Resource Release Request Mini Message ................................... 2-632
6 2.7.2.3.2.31 User Zone Update Request Message .......................................... 2-633
7 2.7.2.3.2.32 Enhanced Origination Message ................................................. 2-634
8 2.7.2.3.2.33 Extended Flash With Information Message ................................ 2-642
9 2.7.2.3.2.34 Extended Pilot Strength Measurement Message......................... 2-644
10 2.7.2.3.2.35 Extended Handoff Completion Message ..................................... 2-649
11 2.7.2.3.2.36 Security Mode Request Message................................................ 2-651
12 2.7.2.3.2.37 Call Cancel Message ................................................................. 2-654
13 2.7.2.3.2.38 Device Information Message...................................................... 2-655
14 2.7.2.3.2.39 Base Station Status Request Message ....................................... 2-656
15 2.7.3 Orders......................................................................................................... 2-659
16 2.7.3.1 Base Station Challenge Order ................................................................ 2-664
17 2.7.3.2 Service Option Request Order ................................................................ 2-665
18 2.7.3.3 Service Option Response Order .............................................................. 2-666
19 2.7.3.4 Mobile Station Reject Order.................................................................... 2-667
20 2.7.4 Information Records .................................................................................... 2-671
21 2.7.4.1 Reserved................................................................................................ 2-674
22 2.7.4.2 Keypad Facility ...................................................................................... 2-675
23 2.7.4.3 Called Party Number.............................................................................. 2-676
24 2.7.4.4 Calling Party Number............................................................................. 2-677
25 2.7.4.5 Reserved................................................................................................ 2-679
26 2.7.4.6 Call Mode .............................................................................................. 2-680
27 2.7.4.7 Terminal Information ............................................................................. 2-681
28 2.7.4.8 Roaming Information ............................................................................. 2-683
29 2.7.4.9 Security Status...................................................................................... 2-685
30 2.7.4.10 Connected Number .............................................................................. 2-686
31 2.7.4.11 IMSI .................................................................................................... 2-687
xiii
3GPP2 C.S0005-A v6.0
CONTENTS
1 2.7.4.12 ESN .....................................................................................................2-688
2 2.7.4.13 Band Class Information ........................................................................2-689
3 2.7.4.14 Power Class Information .......................................................................2-691
4 2.7.4.15 Operating Mode Information .................................................................2-692
5 2.7.4.16 Service Option Information ...................................................................2-694
6 2.7.4.17 Multiplex Option Information................................................................2-695
7 2.7.4.18 Service Configuration ...........................................................................2-700
8 2.7.4.19 Called Party Subaddress.......................................................................2-701
9 2.7.4.20 Calling Party Subaddress......................................................................2-703
10 2.7.4.21 Connected Subaddress .........................................................................2-704
11 2.7.4.22 Power Control Information ....................................................................2-705
12 2.7.4.23 IMSI_M ................................................................................................2-706
13 2.7.4.24 IMSI_T .................................................................................................2-707
14 2.7.4.25 Capability Information..........................................................................2-708
15 2.7.4.26 Extended Record Type - International ...................................................2-715
16 2.7.4.27 Channel Configuration Capability Information ......................................2-716
17 2.7.4.27.1 FCH Type-specific Fields .................................................................2-719
18 2.7.4.27.2 DCCH Type-Specific Fields ..............................................................2-722
19 2.7.4.27.3 FOR_SCH Type-Specific Fields.........................................................2-724
20 2.7.4.27.4 REV_SCH Type-Specific Fields.........................................................2-728
21 2.7.4.28 Extended Multiplex Option Information.................................................2-730
22 2.7.4.29 Geo-Location Capability........................................................................2-738
23 2.7.4.30 Band Subclass Information...................................................................2-739
24 2.7.4.31 Global Emergency Call..........................................................................2-741
25 2.7.4.32 Hook Status .........................................................................................2-743
26 2.7.4.33 QoS Parameters ...................................................................................2-744
27 2.7.4.34 Encryption Capability ...........................................................................2-745
28 3. REQUIREMENTS FOR BASE STATION CDMA OPERATION ....................................... 3-1
29 3.1 Reserved .............................................................................................................. 3-1
30 3.2 Reserved .............................................................................................................. 3-1
31 3.3 Security and Identification .................................................................................... 3-1
32 3.3.1 Authentication ................................................................................................ 3-1
xiv
3GPP2 C.S0005-A v6.0
CONTENTS
1 3.3.2 Encryption ...................................................................................................... 3-1
2 3.3.3 Voice Privacy ................................................................................................... 3-1
3 3.4 Supervision........................................................................................................... 3-1
4 3.4.1 Access Channel or Enhanced Access Channel .................................................. 3-1
5 3.4.2 Reverse Traffic Channel ................................................................................... 3-1
6 3.5 Reserved ............................................................................................................... 3-2
7 3.6 Layer 3 Processing ................................................................................................ 3-2
8 3.6.1 Pilot and Sync Channel Processing................................................................... 3-2
9 3.6.1.1 Preferred Set of CDMA Channels ................................................................ 3-2
10 3.6.1.2 Pilot Channel Operation............................................................................. 3-3
11 3.6.1.3 Sync Channel Operation ............................................................................ 3-3
12 3.6.2 Common Channel Processing........................................................................... 3-3
13 3.6.2.1 Paging Channel and Forward Common Control Channel Procedures ........... 3-3
14 3.6.2.1.1 CDMA Channel Determination.............................................................. 3-4
15 3.6.2.1.2 Common Channel Determination.......................................................... 3-5
16 3.6.2.1.3 Paging Slot Determination .................................................................... 3-5
17 3.6.2.1.4 Message Transmission and Acknowledgment Procedures....................... 3-5
18 3.6.2.2 Overhead Information ................................................................................ 3-6
19 3.6.2.3 Mobile Station Directed Messages............................................................... 3-9
20 3.6.2.3.1 Processing when the General Page Message is Used ............................ 3-10
21 3.6.2.3.2 Processing when the Universal Page Message is Used.......................... 3-12
22 3.6.2.4 Broadcast Messages................................................................................. 3-13
23 3.6.2.4.1 Broadcast Messages Sent on the Paging Channel ................................ 3-13
24 3.6.2.4.1.1 Broadcast Procedures for Slotted Mode ......................................... 3-13
25 3.6.2.4.1.1.1 General Overview.................................................................... 3-13
26 3.6.2.4.1.1.2 Requirements for Sending Broadcast Messages........................ 3-14
27 3.6.2.4.1.1.2.1 Broadcast Delivery Options................................................ 3-14
28 3.6.2.4.1.1.2.1.1 Method 1: Multi-Slot Broadcast Message

29 Transmission............................................................. 3-14
30 3.6.2.4.1.1.2.1.2 Method 2: Periodic Broadcast Paging............................ 3-14
31 3.6.2.4.1.1.2.2 Duplicate Broadcast Message Transmission ....................... 3-15
32 3.6.2.4.1.1.2.3 Periodic Broadcast Paging.................................................. 3-15
xv
3GPP2 C.S0005-A v6.0
CONTENTS
1 3.6.2.4.1.1.2.4 Broadcast Message Slot Determination .............................. 3-15
2 3.6.2.4.2 Broadcast Messages Sent on the Broadcast Control Channel .............. 3-16
3 3.6.2.4.2.1 Broadcast Procedures for Slotted Mode ......................................... 3-16
4 3.6.2.4.2.1.1 General Overview ................................................................... 3-16
5 3.6.2.4.2.1.2 Requirements for Sending Broadcast Messages ....................... 3-17
6 3.6.2.4.2.1.2.1 Broadcast Delivery Options ............................................... 3-17
7 3.6.2.4.2.1.2.1.1 Method 1: Multi-Slot Enhanced Broadcast Paging ........ 3-17
8 3.6.2.4.2.1.2.1.2 Method 2: Periodic Enhanced Broadcast Paging ........... 3-17
9 3.6.2.4.2.1.2.2 Duplicate Broadcast Message Transmission....................... 3-18
10 3.6.2.4.2.1.2.3 Periodic Enhanced Broadcast Paging ................................. 3-18
11 3.6.2.4.2.1.2.4 Broadcast Message Slot Determination .............................. 3-18
12 3.6.2.5 Quick Paging Channel Processing ............................................................ 3-18
13 3.6.2.5.1 Quick Paging Channel Determination................................................. 3-19
14 3.6.2.5.2 Quick Paging Channel Slot Determination ......................................... 3-20
15 3.6.2.5.3 Paging Indicator Position Determination ............................................ 3-20
16 3.6.2.5.4 Configuration Change Indicator Position Determination..................... 3-20
17 3.6.2.5.5 Broadcast Indicator Position Determination........................................ 3-20
18 3.6.2.5.6 Reserved Indicator Positions ............................................................. 3-21
19 3.6.3 Access Channel and Enhanced Access Channel Processing ............................ 3-21
20 3.6.3.1 Reserved ................................................................................................. 3-22
21 3.6.3.2 Reserved ................................................................................................. 3-22
22 3.6.3.3 Response to Page Response Message........................................................ 3-22
23 3.6.3.4 Response to Orders ................................................................................. 3-22
24 3.6.3.5 Response to Origination Message ............................................................. 3-22
25 3.6.3.6 Response to Registration Message............................................................ 3-23
26 3.6.3.7 Response to Data Burst Message ............................................................. 3-24
27 3.6.3.8 Reserved ................................................................................................. 3-24
28 3.6.3.9 Reserved ................................................................................................. 3-24
29 3.6.3.10 Service Redirection ................................................................................ 3-24
30 3.6.4 Traffic Channel Processing ............................................................................ 3-24
31 3.6.4.1 Special Functions and Actions ................................................................. 3-24
32 3.6.4.1.1 Forward Traffic Channel Power Control .............................................. 3-24
xvi
3GPP2 C.S0005-A v6.0
CONTENTS
1 3.6.4.1.2 Service Configuration and Negotiation ................................................ 3-25
2 3.6.4.1.2.1 Use of Variables ........................................................................... 3-30
3 3.6.4.1.2.1.1 Maintaining the Service Request Sequence Number ................. 3-30
4 3.6.4.1.2.1.2 Maintaining the Service Connect Sequence Number................. 3-31
5 3.6.4.1.2.1.3 Assigning Service Option Connection References ..................... 3-31
6 3.6.4.1.2.1.4 Maintaining the Service Negotiation Indicator Variable............. 3-31
7 3.6.4.1.2.1.5 Maintaining the Service Option Request Number ..................... 3-31
8 3.6.4.1.2.2 Service Subfunctions.................................................................... 3-31
9 3.6.4.1.2.2.1 Normal Service Subfunction .................................................... 3-34
10 3.6.4.1.2.2.2 Waiting for Service Request Message Subfunction.................... 3-35
11 3.6.4.1.2.2.3 Waiting for Service Response Message Subfunction ................. 3-37
12 3.6.4.1.2.2.4 Waiting for Service Action Time Subfunction ........................... 3-39
13 3.6.4.1.2.2.5 Waiting for Service Connect Completion Message Subfunction . 3-40
14 3.6.4.1.2.2.6 SO Negotiation Subfunction .................................................... 3-41
15 3.6.4.1.3 Ordering of Messages ......................................................................... 3-43
16 3.6.4.1.4 Message Action Times ........................................................................ 3-43
17 3.6.4.1.5 Long Code Transition Request Processing ........................................... 3-44
18 3.6.4.1.6 Processing Resource Request Messages............................................... 3-44
19 3.6.4.1.7 Response to Enhanced Origination Message........................................ 3-45
20 3.6.4.1.8 Processing Resource Release Request Message and Resource Release

21 Request Mini Message ...................................................................... 3-46
22 3.6.4.1.9 Processing Base Station Status Request Message ................................ 3-46
23 3.6.4.2 Traffic Channel Initialization Substate...................................................... 3-47
24 3.6.4.3 Traffic Channel Substate ......................................................................... 3-48
25 3.6.4.4 Release Substate ..................................................................................... 3-58
26 3.6.5 Registration................................................................................................... 3-62
27 3.6.5.1 Registration on the Common Channels..................................................... 3-63
28 3.6.5.2 Registration on the Traffic Channels ........................................................ 3-63
29 3.6.6 Handoff Procedures ....................................................................................... 3-63
30 3.6.6.1 Overview ................................................................................................. 3-63
31 3.6.6.1.1 Types of Handoff ................................................................................ 3-63
32 3.6.6.1.2 Active Set........................................................................................... 3-64
xvii
3GPP2 C.S0005-A v6.0
CONTENTS
1 3.6.6.2 Requirements.......................................................................................... 3-64
2 3.6.6.2.1 Overhead Information ........................................................................ 3-64
3 3.6.6.2.1.1 System Parameters ...................................................................... 3-65
4 3.6.6.2.1.2 Neighbor List ............................................................................... 3-65
5 3.6.6.2.1.3 Candidate Frequency Neighbor List .............................................. 3-65
6 3.6.6.2.1.4 Candidate Frequency Search List ................................................. 3-65
7 3.6.6.2.2 Call Processing During Handoff .......................................................... 3-66
8 3.6.6.2.2.1 Processing the Pilot Strength Measurement Message..................... 3-66
9 3.6.6.2.2.2 Processing the Extended Handoff Direction Message ..................... 3-66
10 3.6.6.2.2.3 Processing the Candidate Frequency Search Request Message ...... 3-68
11 3.6.6.2.2.4 Processing the Candidate Frequency Search Response Message .... 3-68
12 3.6.6.2.2.5 Processing the Candidate Frequency Search Control Message ....... 3-68
13 3.6.6.2.2.6 Processing the Candidate Frequency Search Report Message ........ 3-69
14 3.6.6.2.2.7 Transmitting During Handoff ....................................................... 3-69
15 3.6.6.2.2.8 Ordering Pilot Measurements From the Mobile Station.................. 3-69
16 3.6.6.2.2.9 Processing the Supplemental Channel Assignment Message.......... 3-70
17 3.6.6.2.2.10 Processing the General Handoff Direction Message...................... 3-73
18 3.6.6.2.2.11 Processing the Universal Handoff Direction Message ................... 3-77
19 3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment

20 Message .................................................................................... 3-80
21 3.6.6.2.2.13 Processing of Forward Supplemental Channel Assignment Mini

22 Message .................................................................................... 3-82
23 3.6.6.2.2.14 Processing of Reverse Supplemental Channel Assignment Mini

24 Message .................................................................................... 3-83
25 3.6.6.2.2.15 Processing of the Mobile Assisted Burst Operation Parameters

26 Message .................................................................................... 3-84
27 3.6.6.2.3 Active Set Maintenance ...................................................................... 3-85
28 3.6.6.2.4 Soft Handoff ...................................................................................... 3-86
29 3.6.6.2.4.1 Receiving During Soft Handoff...................................................... 3-86
30 3.6.6.2.4.2 Transmitting During Soft Handoff ................................................ 3-86
31 3.6.7 CDMA Tiered Services ................................................................................... 3-86
32 3.6.7.1 Overview ................................................................................................. 3-86
33 3.6.7.1.1 Definition .......................................................................................... 3-86
xviii
3GPP2 C.S0005-A v6.0
CONTENTS
1 3.6.7.1.2 Types of User Zones ........................................................................... 3-87
2 3.6.7.2 Requirements .......................................................................................... 3-87
3 3.6.7.2.1 User Zone Identification Message........................................................ 3-87
4 3.6.7.2.2 Private Neighbor List Message .......................................................... 3-87
5 3.6.7.2.3 User Zone Update Message and User Zone Reject Message on f-dsch ... 3-88
6 3.6.7.2.4 User Zone Reject Message on f-csch.................................................... 3-88
7 3.6.8 Call Control Processing.................................................................................. 3-88
8 3.6.8.1 Alerting ................................................................................................... 3-89
9 3.6.8.1.1 Waiting for Order Substate ................................................................. 3-89
10 3.6.8.1.2 Waiting for Answer Substate............................................................... 3-90
11 3.6.8.2 Conversation Substate ............................................................................. 3-91
12 3.6.8.3 Call Release Substate............................................................................... 3-92
13 3.7 PDU Formats for Messages .................................................................................. 3-95
14 3.7.1 Reserved ....................................................................................................... 3-95
15 3.7.2 f-csch............................................................................................................ 3-95
16 3.7.2.1 Reserved.................................................................................................. 3-95
17 3.7.2.2 Reserved.................................................................................................. 3-95
18 3.7.2.3 PDU Formats for Messages on the f-csch .................................................. 3-96
19 3.7.2.3.1 Reserved .......................................................................................... 3-100
20 3.7.2.3.2 Message Body Contents.................................................................... 3-100
21 3.7.2.3.2.1 System Parameters Message ....................................................... 3-101
22 3.7.2.3.2.2 Access Parameters Message ........................................................ 3-110
23 3.7.2.3.2.3 Neighbor List Message ................................................................ 3-119
24 3.7.2.3.2.4 CDMA Channel List Message ...................................................... 3-122
25 3.7.2.3.2.5 Reserved .................................................................................... 3-123
26 3.7.2.3.2.6 Reserved .................................................................................... 3-124
27 3.7.2.3.2.7 Order Message ........................................................................... 3-125
28 3.7.2.3.2.8 Channel Assignment Message..................................................... 3-126
30 3.7.2.3.2.10 Authentication Challenge Message ............................................ 3-141
31 3.7.2.3.2.11 SSD Update Message ................................................................ 3-142
xix
3GPP2 C.S0005-A v6.0
CONTENTS
1 3.7.2.3.2.12 Feature Notification Message .....................................................3-143
2 3.7.2.3.2.13 Extended System Parameters Message.......................................3-144
3 3.7.2.3.2.14 Extended Neighbor List Message................................................3-159
4 3.7.2.3.2.15 Status Request Message ............................................................3-164
5 3.7.2.3.2.16 Service Redirection Message ......................................................3-169
6 3.7.2.3.2.17 General Page Message ...............................................................3-174
7 3.7.2.3.2.18 Global Service Redirection Message ...........................................3-177
8 3.7.2.3.2.19 TMSI Assignment Message ........................................................3-182
9 3.7.2.3.2.20 PACA Message ..........................................................................3-183
10 3.7.2.3.2.21 Extended Channel Assignment Message ....................................3-185
11 3.7.2.3.2.22 General Neighbor List Message ..................................................3-223
12 3.7.2.3.2.23 User Zone Identification Message...............................................3-240
13 3.7.2.3.2.24 Private Neighbor List Message ...................................................3-241
14 3.7.2.3.2.25 Reserved ...................................................................................3-252
15 3.7.2.3.2.26 Sync Channel Message..............................................................3-253
16 3.7.2.3.2.27 Extended Global Service Redirection Message ............................3-263
17 3.7.2.3.2.28 Extended CDMA Channel List Message......................................3-268
18 3.7.2.3.2.29 User Zone Reject Message .........................................................3-271
19 3.7.2.3.2.30 ANSI-41 System Parameters Message ........................................3-273
20 3.7.2.3.2.31 MC-RR Parameters Message ......................................................3-281
21 3.7.2.3.2.32 ANSI-41 RAND Message ............................................................3-301
22 3.7.2.3.2.33 Enhanced Access Parameters Message ......................................3-302
23 3.7.2.3.2.34 Universal Neighbor List Message ...............................................3-322
24 3.7.2.3.2.35 Security Mode Command Message .............................................3-342
25 3.7.2.3.2.36 Universal Page Message.............................................................3-343
26 3.7.3 f-dsch ..........................................................................................................3-346
27 3.7.3.1 Reserved ................................................................................................3-346
28 3.7.3.2 Reserved ................................................................................................3-346
29 3.7.3.3 PDU Formats on the f-dsch ....................................................................3-347
30 3.7.3.3.1 Reserved...........................................................................................3-348
31 3.7.3.3.2 Message Body Contents ....................................................................3-348
32 3.7.3.3.2.1 Order Message ............................................................................3-349
xx
3GPP2 C.S0005-A v6.0
CONTENTS
1 3.7.3.3.2.2 Authentication Challenge Message .............................................. 3-351
2 3.7.3.3.2.3 Alert With Information Message .................................................. 3-352
4 3.7.3.3.2.5 Reserved .................................................................................... 3-355
5 3.7.3.3.2.6 Analog Handoff Direction Message .............................................. 3-356
6 3.7.3.3.2.7 In-Traffic System Parameters Message ........................................ 3-359
7 3.7.3.3.2.8 Neighbor List Update Message .................................................... 3-364
8 3.7.3.3.2.9 Send Burst DTMF Message ......................................................... 3-365
9 3.7.3.3.2.10 Power Control Parameters Message ........................................... 3-367
10 3.7.3.3.2.11 Retrieve Parameters Message .................................................... 3-369
11 3.7.3.3.2.12 Set Parameters Message ........................................................... 3-370
12 3.7.3.3.2.13 SSD Update Message ................................................................ 3-371
13 3.7.3.3.2.14 Flash With Information Message ............................................... 3-372
14 3.7.3.3.2.15 Mobile Station Registered Message ............................................ 3-373
15 3.7.3.3.2.16 Status Request Message ........................................................... 3-375
16 3.7.3.3.2.17 Extended Handoff Direction Message ........................................ 3-377
17 3.7.3.3.2.18 Service Request Message .......................................................... 3-384
18 3.7.3.3.2.19 Service Response Message ........................................................ 3-386
19 3.7.3.3.2.20 Service Connect Message .......................................................... 3-388
20 3.7.3.3.2.21 Service Option Control Message ................................................ 3-394
21 3.7.3.3.2.22 TMSI Assignment Message........................................................ 3-395
22 3.7.3.3.2.23 Service Redirection Message ..................................................... 3-396
23 3.7.3.3.2.24 Supplemental Channel Assignment Message ............................. 3-399
24 3.7.3.3.2.25 Power Control Message ............................................................. 3-408
25 3.7.3.3.2.26 Extended Neighbor List Update Message ................................... 3-448
26 3.7.3.3.2.27 Candidate Frequency Search Request Message.......................... 3-459
27 3.7.3.3.2.28 Candidate Frequency Search Control Message........................... 3-475
28 3.7.3.3.2.29 Power Up Function Message ..................................................... 3-476
29 3.7.3.3.2.30 Power Up Function Completion Message ................................... 3-478
30 3.7.3.3.2.31 General Handoff Direction Message........................................... 3-480
31 3.7.3.3.2.32 Resource Allocation Message..................................................... 3-502
xxi
3GPP2 C.S0005-A v6.0
CONTENTS
1 3.7.3.3.2.33 Resource Allocation Mini Message .............................................3-503
2 3.7.3.3.2.34 Extended Release Message ........................................................3-504
3 3.7.3.3.2.35 Extended Release Mini Message.................................................3-506
4 3.7.3.3.2.36 Universal Handoff Direction Message .........................................3-507
5 3.7.3.3.2.37 Extended Supplemental Channel Assignment Message...............3-559
6 3.7.3.3.2.38 Forward Supplemental Channel Assignment Mini Message ........3-577
7 3.7.3.3.2.39 Reverse Supplemental Channel Assignment Mini Message .........3-579
8 3.7.3.3.2.40 Mobile Assisted Burst Operation Parameters Message ................3-582
9 3.7.3.3.2.41 User Zone Reject Message .........................................................3-585
10 3.7.3.3.2.42 User Zone Update Message........................................................3-586
11 3.7.3.3.2.43 Call Assignment Message ..........................................................3-587
12 3.7.3.3.2.44 Extended Alert With Information Message..................................3-590
13 3.7.3.3.2.45 Extended Flash With Information Message.................................3-592
14 3.7.3.3.2.46 Security Mode Command Message .............................................3-594
15 3.7.3.3.2.47 Base Station Status Response Message......................................3-596
16 3.7.4 Orders .........................................................................................................3-600
17 3.7.4.1 Base Station Challenge Confirmation Order ............................................3-606
18 3.7.4.2 Service Option Request Order .................................................................3-607
19 3.7.4.3 Service Option Response Order...............................................................3-608
20 3.7.4.4 Status Request Order .............................................................................3-609
21 3.7.4.5 Registration Accepted Order ...................................................................3-610
22 3.7.4.6 Periodic Pilot Measurement Request Order ..............................................3-614
23 3.7.4.7 Retry Order ............................................................................................3-616
24 3.7.5 Information Records.....................................................................................3-618
25 3.7.5.1 Display ..................................................................................................3-622
26 3.7.5.2 Called Party Number ..............................................................................3-623
27 3.7.5.3 Calling Party Number .............................................................................3-624
28 3.7.5.4 Connected Number.................................................................................3-626
29 3.7.5.5 Signal ....................................................................................................3-628
30 3.7.5.6 Message Waiting ....................................................................................3-633
31 3.7.5.7 Service Configuration .............................................................................3-634
32 3.7.5.7.1 Channel Configuration for the Supplemental Channel .......................3-658
xxii
3GPP2 C.S0005-A v6.0
CONTENTS
1 3.7.5.8 Called Party Subaddress ........................................................................ 3-660
2 3.7.5.9 Calling Party Subaddress ....................................................................... 3-661
3 3.7.5.10 Connected Subaddress......................................................................... 3-662
4 3.7.5.11 Redirecting Number ............................................................................. 3-663
5 3.7.5.12 Redirecting Subaddress ....................................................................... 3-666
6 3.7.5.13 Meter Pulses ........................................................................................ 3-667
7 3.7.5.14 Parametric Alerting .............................................................................. 3-668
8 3.7.5.15 Line Control......................................................................................... 3-670
9 3.7.5.16 Extended Display................................................................................. 3-671
10 3.7.5.17 Extended Record Type - International................................................... 3-674
11 3.7.5.18 Reserved.............................................................................................. 3-675
12 3.7.5.19 Reserved.............................................................................................. 3-676
13 3.7.5.20 Non-Negotiable Service Configuration ................................................... 3-677
14 3.7.5.21 Multiple Character Extended Display.................................................... 3-707
15 3.7.5.22 Call Waiting Indicator .......................................................................... 3-709
16 3.7.6 Information Elements .................................................................................. 3-710
17 3.7.6.1 Pilot Record Type Specific Fields............................................................. 3-710
18 ANNEX A RESERVED ....................................................................................................A-1
19 ANNEX B CDMA CALL FLOW EXAMPLES.......................................................................B-1
20 ANNEX C RESERVED ....................................................................................................C-1
21 ANNEX D CDMA CONSTANTS....................................................................................... D-1
22 ANNEX E CDMA RETRIEVABLE AND SETTABLE PARAMETERS .....................................E-1
23 ANNEX F MOBILE STATION DATABASE......................................................................... F-1
24 F.1 Introduction.......................................................................................................... F-1
25 F.2 Mobile Station Indicators ...................................................................................... F-2
26 F.2.1 Permanent Mobile Station Indicators................................................................ F-2
27 F.2.2 Semi-permanent Mobile Station Indicators ....................................................... F-3
28 F.3 NAM Indicators ..................................................................................................... F-4
29 ANNEX G CDMA EXTENDED ENCRYPTION CALL FLOW EXAMPLES ............................. G-1
xxiii
3GPP2 C.S0005-A v6.0
FIGURES
1 Figure 1.3.1-1. cdma2000 Signaling – General Architecture......................................... 1-45
2 Figure 2.3.1-1. IMSI Structure...................................................................................... 2-1
3 Figure 2.3.1-2. IMSI_S Binary Mapping......................................................................... 2-2
4 Figure 2.3.12.1.1-1. Partitioning of SSD...................................................................... 2-11
5 Figure 2.3.12.1.5-1. SSD Update Message Flow........................................................... 2-13
6 Figure 2.3.12.1.5-2. Computation of Shared Secret Data (SSD).................................... 2-14
7 Figure 2.3.12.1.5-3. Computation of AUTHBS ............................................................. 2-14
8 Figure 2.3.12.4.1.4-1. 8-Bit Layer 3 SDU CRC Field Calculation .................................. 2-27
9 Figure 2.3.12.4.1.5-1 An 8-bit encryption sequence number space divided into 3

10 segments ................................................................................... 2-29
11 Figure 2.3.12.4.5-1. Message Bits ............................................................................... 2-37
12 Figure 2.3.15-1. TMSI Zone Example .......................................................................... 2-39
13 Figure 2.6-1. Mobile Station Layer 3 Processing States ................................................ 2-42
14 Figure 2.6.1-1. Mobile Station Initialization State ........................................................ 2-44
15 Figure 2.6.1.4-1. Mobile Station Internal Timing ......................................................... 2-58
16 Figure 2.6.2.1.1.1-1. Mobile Station Idle Slotted Mode Structure Example ................... 2-63
17 Figure 2.6.2.1.1.1.2.1-1. Multi-Slot Broadcast Message Transmission Example............ 2-66
18 Figure 2.6.2.1.1.1.2.2-1. Periodic Broadcast Paging Example....................................... 2-67
19 Figure 2.6.2.1.1.1.3.1-1. Multi-Slot Enhanced Broadcast Paging Example ................... 2-68
20 Figure 2.6.2.1.2.1-1. Quick Paging Channel Timeline .................................................. 2-77
21 Figure 2.6.3-1. System Access State ..........................................................................2-156
22 Figure 2.6.4-1. Mobile Station Control on the Traffic Channel State............................2-262
23 Figure 2.6.4.1.2.2-1. Mobile Station Service Subfunctions ..........................................2-276
24 Figure 2.6.4.1.7-1. Structure of PUF Attempt .............................................................2-297
25 Figure 2.6.4.3-1. Mobile Station Modes ......................................................................2-327
26 Figure 2.6.5.2-1. Systems and Networks Example ......................................................2-357
27 Figure 2.6.6.2.5.1.1-1. New Supplemental Channel Assignment Received while a

28 Previous Supplemental Channel Assignment is in Progress ........2-450
29 Figure 2.6.6.2.5.1.1-2. New Supplemental Channel Assignment Received before a

30 Previous Supplemental Channel Assignment starts....................2-450
31 Figure 2.6.6.3-1. Handoff Threshold Example if P_REV_IN_USEs is Less Than or Equal
32 to Three, or SOFT_SLOPEs is Equal to ‘000000’ .........................2-492
xxiv
3GPP2 C.S0005-A v6.0
FIGURES
1 Figure 2.6.6.3-2. Handoff Threshold Example if P_REV_IN_USEs is Greater Than Three,

2 and SOFT_SLOPEs is Not Equal to ‘000000’ .............................. 2-493
3 Figure 2.6.6.3-3. Pilot Strength Measurements Triggered by a Candidate Pilot if

4 P_REV_IN_USEs = 3 or SOFT_SLOPEs = ‘000000’ ...................... 2-494

6 P_REV_IN_USEs > 3 and SOFT_SLOPEs is Not Equal to‘000000’ 2-495
7 Figure 2.6.10-1. Call Control...................................................................................... 2-504
8 Figure B-1A. Simple Call Flow, Mobile Station Origination Example Using Service
9 Option Negotiation with Service Option 1 ......................................B-2
10 Figure B-1B. Simple Call Flow, Mobile Station Origination Example Using Service
11 Negotiation with Service Option 1 .................................................B-3
12 Figure B-2A. Simple Call Flow, Mobile Station Termination Example Using Service
13 Option Negotiation with Service Option 1 ......................................B-4
14 Figure B-2B. Simple Call Flow, Mobile Station Termination Example Using Service
15 Negotiation with Service Option 1 .................................................B-5
16 Figure B-3. Simple Call Flow, Mobile Station Initiated Call Disconnect Example .............B-6
17 Figure B-4. Simple Call Flow, Base Station Initiated Call Disconnect Example................B-6
18 Figure B-5. Simple Call Flow, Three-Party Calling Example............................................B-7
19 Figure B-6. Simple Call Flow, Call-Waiting Example ......................................................B-8
20 Figure B-7. Call Processing During Soft Handoff ............................................................B-9
21 Figure B-8. Call Processing During Sequential Soft Handoff (Part 1 of 2) ......................B-10
22 Figure B-8. Call Processing During Sequential Soft Handoff (Part 2 of 2) ......................B-11
23 Figure B-9. PACA Call Processing (Part 1 of 2) .............................................................B-12
24 Figure B-9. PACA Call Processing (Part 2 of 2) .............................................................B-13
25 Figure B-10. Call Flow for Same Frequency Hard Handoff Failure Recovery ..................B-14
26 Figure B-11. Call Flow for Inter-Frequency Hard Handoff Failure Recovery without
27 Search .......................................................................................B-15
28 Figure B-12. Call Flow for Inter-Frequency Handoff (Single Search Using Candidate
29 Frequency Search Control Message) (Part 1 of 2) .........................B-16
32 Figure B-13. Call Flow for Inter-Frequency Handoff (Periodic Search Using Candidate
xxv
3GPP2 C.S0005-A v6.0
FIGURES
2 Frequency Search Control Message) (Part 3 of 3) ......................... B-20
3 Figure B-14. Call Flow for Inter-Frequency Handoff (Single Search Using General
4 Handoff Direction Message) (Part 1 of 3)...................................... B-21
9 Figure B-15. Call Flow for Inter-Frequency Handoff (Periodic Search Using General
17 Figure B-16. Call Flow for Periodic Search on F2 from F1, Failed Handoff Attempt to F3,
18 Continued Periodic Search of F2 from F1 (Part 1 of 3) ................. B-28
23 Figure B-17. Call Flow for Periodic Search on F2 from F1, Successful Handoff to F3,
24 Continued Periodic Search on F2 from F3 (Part 1 of 2) ................ B-31
25 Figure B-17. Call Flow for Periodic Search on F2 from F1, Successful Handoff to F3,
26 Continued Periodic Search on F2 from F3 (Part 2 of 2) ................ B-32
27 Figure B-18. Simple Call Flow Mobile Station Origination Example with Transmission
28 on Forward Supplemental Code Channels (Part 1 of 2) ................ B-33
30 on Forward Supplemental Code Channels (Part 2 of 2) ................ B-34
32 on Reverse Supplemental Code Channels (Part 1 of 2) ................. B-35
34 on Reverse Supplemental Code Channels (Part 2 of 2) ................. B-36
35 Figure B-20. Simple Call Flow, Mobile Station Termination Example with Transmission
36 on Forward Supplemental Code Channel(s) (Part 1 of 3) .............. B-37
xxvi
3GPP2 C.S0005-A v6.0
FIGURES
1 on Forward Supplemental Code Channel(s) (Part 2 of 3)...............B-38
3 on Forward Supplemental Code Channel(s) (Part 3 of 3)...............B-39
5 on Reverse Supplemental Code Channel(s) (Part 1 of 3) ...............B-40
10 Figure B-22. Active/Control Hold to Idle State Transition; Release all services (BS
11 Initiated) ....................................................................................B-43
12 Figure B-23. Active/Control Hold to Idle State Transition; Release all services (MS
13 Initiated) ....................................................................................B-44
14 Figure B-24. Active to Control Hold State Transition (BS Initiated) ................................B-45
15 Figure B-25. Active to Control Hold State Transition (MS Initiated)................................B-46
16 Figure B-26. Control Hold to Active Transition (BS Initiated) .........................................B-47
17 Figure B-27. Control Hold to Active Transition (MS Initiated) ........................................B-48
18 Figure B-28. Connecting an Additional Service (MS Initiated) .......................................B-49
19 Figure B-29. Connecting an Additional Service (BS Initiated).........................................B-50
20 Figure B-30. Releasing a Service that is not the last one connected (MS Initiated)..........B-51
21 Figure B-31. Releasing a Service that is not the last one connected (BS Initiated) .........B-52
22 Figure G-1. Power-Up Registration, Origination, and Call Release (BS waits for the new
23 CMEKEY before sending CAM/ECAM).......................................... G-2
24 Figure G-2. Quick channel assignment (BS does not wait for the new key before sending
25 CAM/ECAM) ............................................................................... G-3
26 Figure G-3. MS Initiates call origination during the Registration Access Substate ........... G-4
27 Figure G-4. Implicit registration (MS crosses a SID/NID boundary during MS Idle State.
28 MS originates before registering) .................................................. G-5
29 Figure G-5. BS lost the stored key (A rare out-of-sync case) ........................................... G-6
30 Figure G-6. MS fails to decrypt messages (MS recovers by re-synchronizing the crypt-
31 sync) ........................................................................................... G-7
32 Figure G-7. MS fails to decrypt messages (MS recovers by re-registering after failing to
33 re-synchronize the crypto-sync) ................................................... G-8
34 Figure G-8. BS fails to decrypt messages (BS recovers by re-synchronizing the crypt-
35 sync) ........................................................................................... G-9
xxvii
3GPP2 C.S0005-A v6.0
FIGURES
1 Figure G-9. BS fails to decrypt messages (BS recovers by forcing the MS to re-register
2 after failing to re-synchronize the crypto-sync)............................ G-10
xxviii
3GPP2 C.S0005-A v6.0
TABLES
1 Table 2.3.1.1-1. Decimal to Binary Conversion Table ..................................................... 2-4
2 Table 2.3.1.1-2. BCD Mapping ...................................................................................... 2-5
3 Table 2.3.3-1. Station Class Mark ................................................................................. 2-7

4 Table 2.3.5-1. ACCOLCp Mapping for ACCOLC 0 through ACCOLC 9 ............................. 2-8
5 Table 2.3.5-2. ACCOLCp Mapping for ACCOLC 10 through ACCOLC 15 ......................... 2-9
6 Table 2.3.12.1-1. Auth_Signature Input Parameters..................................................... 2-10
7 Table 2.4.1-1. Monitored Quantities and Statistics........................................................ 2-40
8 Table 2.4.2-1. Accumulated PCH/BCCH/F-CCCH Channel Statistics ........................... 2-40
9 Table 2.6.4.2-1. Default Logical to Physical Mapping Table ......................................... 2-320
10 Table 2.6.6.2.1-1. Searcher Window Sizes ................................................................. 2-371
11 Table 2.6.6.2.1-2. Search Window Offset ................................................................... 2-371
12 Table 2.6.6.2.3-1. Handoff Drop Timer Expiration Values........................................... 2-375
13 Table 2.6.6.2.5.1-1. Search Parameter Settings ......................................................... 2-385
14 Table 2.6.6.2.8.3.2-1. Search Period Values............................................................... 2-476
15 Table 2.6.7.1-1. Hash Function Modifier.................................................................... 2-497
16 Table 2.7.1.3-1. Messages on r-csch .......................................................................... 2-520
17 Table 2.7.1.3.2.1-1. Registration Type (REG_TYPE) Codes .......................................... 2-522
18 Table 2.7.1.3.2.1-2. RETURN_CAUSE Codes.............................................................. 2-523
19 Table 2.7.1.3.2.1-3. WLL Device Types ...................................................................... 2-525
20 Table 2.7.1.3.2.1-4. Hook Status Values.................................................................... 2-526
21 Table 2.7.1.3.2.1-5. Encoding of the SIG_ENCRYPT_SUP Field ................................... 2-527
22 Table 2.7.1.3.2.4-1. REQUEST_MODE Codes............................................................. 2-535
23 Table 2.7.1.3.2.4-2. Number Types............................................................................ 2-536
24 Table 2.7.1.3.2.4-3. Numbering Plan Identification .................................................... 2-537
25 Table 2.7.1.3.2.4-4. Representation of DTMF Digits ................................................... 2-538
26 Table 2.7.1.3.2.4-5. Encryption Algorithms Supported ............................................... 2-539
27 Table 2.7.1.3.2.4-6. Channel Indicator ...................................................................... 2-540
28 Table 2.7.1.3.2.4-7. Geo-location Types ..................................................................... 2-543
29 Table 2.7.1.3.2.4-8. ORIG_COUNT field for ORIG_REASON = ‘0’ ................................. 2-544
30 Table 2.7.1.3.2.4-9. Encoding of the UI_ENCRYPT_SUP Field ..................................... 2-549
31 Table 2.7.1.3.2.4-10. Encoding of the SO_BITMAP_IND Field ..................................... 2-551
xxix
3GPP2 C.S0005-A v6.0
TABLES
1 Table 2.7.1.3.2.5-1. Channel indicator .......................................................................2-558
2 Table 2.7.2.3-1. Messages on r-dsch ..........................................................................2-575
3 Table 2.7.2.3.2.7-1. Recommended DTMF Pulse Width ...............................................2-589
4 Table 2.7.2.3.2.7-2. Recommended Minimum Inter-digit Interval ................................2-590
5 Table 2.7.2.3.2.12-1. REQ_PURPOSE Codes...............................................................2-596
6 Table 2.7.2.3.2.13-1. RESP_PURPOSE Codes .............................................................2-598
7 Table 2.7.2.3.2.32-1. Channel Indicator .....................................................................2-636
8 Table 2.7.2.3.2.34-1. Pilot Record Types.....................................................................2-645
9 Table 2.7.2.3.2.39-1. Base Station Status Request Information Record Types..............2-657
10 Table 2.7.3-1. Order and Order Qualification Codes Used on the r-dsch and the r-csch
11 (Part 1 of 4)...............................................................................2-660
13 (Part 2 of 4)...............................................................................2-661
15 (Part 3 of 4)...............................................................................2-662
17 (Part 4 of 4)...............................................................................2-663
18 Table 2.7.3.4-1. REJECTED_PDU_TYPE codes ...........................................................2-670
19 Table 2.7.4-1. Information Record Types (Part 1 of 2) .................................................2-672
21 Table 2.7.4.4-1. Presentation Indicators.....................................................................2-677
22 Table 2.7.4.4-2. Screening Indicators .........................................................................2-678

23 Table 2.7.4.15-1. OP_MODE for P_REV_IN_USEs Less Than or Equal to Three............2-692
24 Table 2.7.4.15-2. OP_MODE for P_REV_IN_USEs Greater Than Three.........................2-693
25 Table 2.7.4.17-1. Forward Fundamental Traffic Channel Number of Bits per Frame for
26 Forward Multiplex Option 1.......................................................2-697
27 Table 2.7.4.17-2. Forward Fundamental Traffic Channel Number of Bits per Frame for
28 Forward Multiplex Option equal to 2..........................................2-697
29 Table 2.7.4.17-3. Reverse Fundamental Traffic Channel Number of Bits per Frame for
30 Reverse Multiplex Option equal to 1...........................................2-698
31 Table 2.7.4.17-4. Reverse Fundamental Traffic Channel Number of Bits per Frame for
32 Reverse Multiplex Option equal to 2...........................................2-698
33 Table 2.7.4.19-1. Subaddress Types...........................................................................2-701
34 Table 2.7.4.19-2. Odd/Even Indicator ........................................................................2-702
xxx
3GPP2 C.S0005-A v6.0
TABLES
1 Table 2.7.4.25-1. Set of supported Reverse Pilot Gating Rates .................................... 2-711
2 Table 2.7.4.27.1-1. Forward Channel Radio Configurations Supported ....................... 2-720
3 Table 2.7.4.27.1-2. Reverse Channel Radio Configurations Supported ........................ 2-721
4 Table 2.7.4.27.2-1. DCCH Frame Size Supported ....................................................... 2-722
5 Table 2.7.4.27.3-1. Block Size .................................................................................... 2-725
6 Table 2.7.4.27.3-2. SCH Data Rate............................................................................. 2-727
7 Table 2.7.4.28-1. Forward Fundamental Channel Number of Bits per Frame for
8 MO_FOR_FCH equal to 1 .......................................................... 2-732
10 MO_FOR_FCH equal to 2 .......................................................... 2-733
12 MO_FOR_FCH equal to 0x704................................................... 2-733
13 Table 2.7.4.28-4. Reverse Fundamental Channel Number of Bits per Frame for
14 MO_REV_FCH equal to 1 .......................................................... 2-734
16 MO_REV_FCH equal to 2 .......................................................... 2-735
18 MO_REV_FCH equal to 0x704................................................... 2-735
19 Table 2.7.4.34-1. Geo-location Codes......................................................................... 2-738
20 Table 3.7.2.3-1. f-csch Messages (Part 1 of 2) .............................................................. 3-97
21 Table 3.7.2.3-1. f-csch Messages (Part 2 of 2) .............................................................. 3-99
22 Table 3.7.2.3.2.1-1. Value of Zone Timer ................................................................... 3-103
23 Table 3.7.2.3.2.2-1. ACCT access overload class bitmap subfields. .............................. 3-117
24 Table 3.7.2.3.2.3-1. Neighbor Configuration Field ...................................................... 3-120
25 Table 3.7.2.3.2.8-1. Assignment Mode ....................................................................... 3-129
26 Table 3.7.2.3.2.8-2. Message Encryption Modes......................................................... 3-130
27 Table 3.7.2.3.2.8-3. Default Configuration ................................................................. 3-135
28 Table 3.7.2.3.2.13-1. Preferred MSID Types ............................................................... 3-147
29 Table 3.7.2.3.2.13-2. QPCH Indicator Data Rate ......................................................... 3-153
30 Table 3.7.2.3.2.13-3 Quick Paging Channel Transmit Power Level ............................... 3-154
31 Table 3.7.2.3.2.13-4. AUTO_MSG_INTERVAL Values.................................................. 3-156
32 Table 3.7.2.3.2.14-1. Neighbor Configuration Field .................................................... 3-160
33 Table 3.7.2.3.2.14-2. Search Priority Field ................................................................. 3-162
xxxi
3GPP2 C.S0005-A v6.0
TABLES
1 Table 3.7.2.3.2.15-1. Qualification Information Type ..................................................3-164
2 Table 3.7.2.3.2.15-2. Status Information Record Types...............................................3-165
3 Table 3.7.2.3.2.15-3. Operating Mode for MOB_P_REV Less Than or Equal to Three....3-167
4 Table 3.7.2.3.2.15-4. Operating Mode for MOB_P_REV Greater Than Three.................3-167
5 Table 3.7.2.3.2.16-1. Redirection Types......................................................................3-169
6 Table 3.7.2.3.2.16-2. Redirection Record Types ..........................................................3-170
7 Table 3.7.2.3.2.16-3. SYS_ORDERING .......................................................................3-172
8 Table 3.7.2.3.2.20-1. Purpose of PACA Message .........................................................3-183
9 Table 3.7.2.3.2.20-2. Value of PACA State Timer ........................................................3-184
10 Table 3.7.2.3.2.21-1. Assignment Mode......................................................................3-193
11 Table 3.7.2.3.2.21-2. Default Configuration................................................................3-195
12 Table 3.7.2.3.2.21-7. Mapping between Multiplex Options and Radio Configurations...3-196
13 Table 3.7.2.3.2.21-3. Radio Configurations ................................................................3-198
15 Table 3.7.2.3.2.21-5. 1X Reverse Link Frequency Offset .............................................3-209
16 Table 3.7.2.3.2.21-6. Pilot Record Types.....................................................................3-210
17 Table 3.7.2.3.2.22-1. Search Mode Field ....................................................................3-225
18 Table 3.7.2.3.2.22-2. Neighbor Configuration Field.....................................................3-227
19 Table 3.7.2.3.2.22-3. Search Priority Field .................................................................3-229
20 Table 3.7.2.3.2.22-4. Cellular System A/B .................................................................3-231
21 Table 3.7.2.3.2.22-5. Neighbor Pilot Record Types ......................................................3-232
22 Table 3.7.2.3.2.22-6. Walsh Code Length ...................................................................3-233
23 Table 3.7.2.3.2.22-7. Auxiliary Transmit Diversity Pilot Transmit Power Level .............3-235
24 Table 3.7.2.3.2.24-1. Radio Interface Type .................................................................3-242
25 Table 3.7.2.3.2.26-1. Paging Channel Data Rate.........................................................3-255
26 Table 3.7.2.3.2.26-2. Broadcast Control Channel Data Rate .......................................3-257
27 Table 3.7.2.3.2.26-3. TD Mode ...................................................................................3-259
28 Table 3.7.2.3.2.26-4. TD Transmit Power Level...........................................................3-259
29 Table 3.7.2.3.2.26-5. The Position of the Primary SR3 Pilot..........................................3-261
30 Table 3.7.2.3.2.26-6. Pilot Transmission Power ..........................................................3-261
31 Table 3.7.2.3.2.29-1. Rejection Action Indicators........................................................3-271
32 Table 3.7.2.3.2.30-1. Value of Zone Timer ..................................................................3-275
xxxii
3GPP2 C.S0005-A v6.0
TABLES
1 Table 3.7.2.3.2.30-2. Preferred MSID Types ............................................................... 3-277
2 Table 3.7.2.3.2.31-1. Forward Common Control Channel Rate Words......................... 3-293
3 Table 3.7.2.3.2.31-2. Broadcast Control Channel Data Rate....................................... 3-295
4 Table 3.7.2.3.2.31-3. Quick Paging Channel Transmit Power Level ............................. 3-296
5 Table 3.7.2.3.2.33-1. Enhanced Access Modes........................................................... 3-309
6 Table 3.7.2.3.2.33-2. Applicable Modes...................................................................... 3-311
7 Table 3.7.2.3.2.33-3. EACH and RCCCH Data Rate and Frame Size ........................... 3-314
8 Table 3.7.2.3.2.33-4. CPCCH Power Control Rate....................................................... 3-319
9 Table 3.7.2.3.2.34-1. Radio Interface Type ................................................................. 3-323
10 Table 3.7.2.3.2.34-2. Search Mode Field .................................................................... 3-326
11 Table 3.7.2.3.2.34-3. Neighbor Configuration Field .................................................... 3-328
12 Table 3.7.2.3.2.34-4. Neighbor Pilot Record Types...................................................... 3-331
13 Table 3.7.2.3.2.34-4. Search Priority Field ................................................................. 3-338
14 Table 3.7.2.3.2.34-5. Cellular System A/B................................................................. 3-341
15 Table 3.7.3.3-1. f-dsch Messages (Part 1 of 2) ............................................................ 3-347
16 Table 3.7.3.3-1. f-dsch Messages (Part 2 of 2) ............................................................ 3-348
17 Table 3.7.3.3.2.6-1. Analog Channel Type.................................................................. 3-357
18 Table 3.7.3.3.2.17-1. Traffic Channel Preamble Length ............................................... 3-382
19 Table 3.7.3.3.2.18-1. REQ_PURPOSE Codes .............................................................. 3-384
20 Table 3.7.3.3.2.19-1. RESP_PURPOSE Codes............................................................. 3-386
21 Table 3.7.3.3.2.20-1. USE_OLD_SERV_CONFIG values ............................................... 3-390
22 Table 3.7.3.3.2.25-1. Closed Loop Power Control Step Size......................................... 3-409
23 Table 3.7.3.3.2.25-2. Target Frame Error Rate........................................................... 3-411
24 Table 3.7.3.3.2.25-3. RPC_ADJ_REC_TYPE and RPC_ADJ_REC_LEN fields ................ 3-414
25 Table 3.7.2.3.2.25-4. Type Specific Fields for RECORD_TYPE = ‘0000’ ........................ 3-415
28 Table 3.7.3.3.2.26-1. NGHBR_SRCH_MODE Field...................................................... 3-449
29 Table 3.7.3.3.2.26-2. SEARCH_PRIORITY Field.......................................................... 3-451
30 Table 3.7.3.3.2.27-1. SEARCH_TYPE Codes............................................................... 3-460
31 Table 3.7.3.3.2.27-2. SEARCH_MODE Types ............................................................. 3-460
xxxiii
3GPP2 C.S0005-A v6.0
TABLES
1 Table 3.7.3.3.2.27-3. CF_NGHBR_SRCH_MODE Field ................................................3-465
3 Table 3.7.3.3.2.34-2. Actual Reverse Pilot Gating rate ................................................3-505
4 Table 3.7.3.3.2.36-1. Channel Indicator ......................................................................3-529
5 Table 3.7.3.3.2.37-1. REV_WALSH_ID Field ...............................................................3-565
6 Table 3.7.3.3.2.37-2. R-SCH Number of Information Bits per Frame ...........................3-565
7 Table 3.7.3.3.2.37-3. FOR_SCH_DURATION and REV_SCH_DURATION Fields ............3-566
8 Table 3.7.3.3.2.37-4. F-SCH Number of Information Bits per Frame ...........................3-569
9 Table 3.7.3.3.3.47-1. Base Station Status Response Information Record Types ...........3-597
10 Table 3.7.4-1. Order and Order Qualification Codes Used on the f-csch and the f-dsch
11 (Part 1 of 4)...............................................................................3-601
13 (Part 2 of 4)...............................................................................3-602
15 (Part 3 of 4)...............................................................................3-603
17 (Part 4 of 4)...............................................................................3-605
18 Table 3.7.4.4-1. Status Request ORDQ Values ...........................................................3-609
19 Table 3.7.4.5-1. (Part 1 of 2) Signaling Message Encryption Modes .............................3-611
20 Table 3.7.4.5-1 (Part 2 of 2). Signaling Message Encryption Modes .............................3-612
21 Table 3.7.4.5-2. ENC_KEY_SIZE Values .....................................................................3-613
22 Table 3.7.4.7-1 Retry Delay Type ................................................................................3-616
23 Table 3.7.4.7-2 Retry Delay for RETRY_TYPE ‘001’ ......................................................3-617
27 Table 3.7.5.5-1. Signal Type ......................................................................................3-628
28 Table 3.7.5.5-2. Alert Pitch ........................................................................................3-629
29 Table 3.7.5.5-3. Tone Signals (SIGNAL_TYPE = ‘00’)....................................................3-630
30 Table 3.7.5.5-4. ISDN Alerting (SIGNAL_TYPE = ‘01’) ..................................................3-631
31 Table 3.7.5.5-5. IS-54B Alerting (SIGNAL_TYPE = ‘10’)................................................3-632
32 Table 3.7.5.7-1. FOR_TRAFFIC Codes ........................................................................3-642
33 Table 3.7.5.7-2. REV_TRAFFIC Codes ........................................................................3-643
xxxiv
3GPP2 C.S0005-A v6.0
TABLES
1 Table 3.7.5.7-3. User information Encryption Modes.................................................. 3-644
2 Table 3.7.5.7-4. DCCH Frame Size ............................................................................. 3-652
3 Table 3.7.5.7-5. SCH Identifier .................................................................................. 3-654
4 Table 3.7.5.11-1. Redirection Reason ........................................................................ 3-665
5 Table 3.7.5.16-1. Display Type .................................................................................. 3-671
6 Table 3.7.5.16-2. Mandatory Control Tags and Display Text Tags ............................... 3-672
7 Table 3.7.5.20-1. Reverse Pilot Gating rate ................................................................ 3-685
8 Table 3.7.5.20-2. Logical to Physical Mapping indicator ............................................. 3-687
9 Table 3.7.5.20-3. Logical Resource Identifier.............................................................. 3-687
10 Table 3.7.5.20-4. Physical Resource Identifier............................................................ 3-688
11 Table 3.7.5.20-4. CRC_LEN_IDX ............................................................................... 3-691
12 Table 3.7.5.20-5. NUM_LTUS .................................................................................... 3-700
13 Table 3.7.6.1-1. TD Transmit Power Level................................................................... 3-710
14 Table 3.7.6.1-2. TD Mode .......................................................................................... 3-711
15 Table 3.7.6.1-3. Walsh Code Length .......................................................................... 3-712
16 Table 3.7.6.1-4. Auxiliary Transmit Diversity Pilot Transmit Power Level .................... 3-713
17 Table 3.7.6.1-5. The Position of the Primary SR3 Pilot................................................. 3-714
18 Table 3.7.6.1-6. Pilot Transmission Power ................................................................. 3-714
19 Table D-1. Time Limits (Part 1 of 5) .............................................................................. D-1
24 Table D-2. Other Constants ......................................................................................... D-7
25 Table E-1. Retrievable and Settable Parameters (Part 1 of 19).........................................E-2
xxxv
3GPP2 C.S0005-A v6.0
TABLES
1 Table E-1. Retrievable and Settable Parameters (Part 8 of 19) ........................................ E-9
2 Table E-1. Retrievable and Settable Parameters (Part 9 of 19) ...................................... E-10
3 Table E-1. Retrievable and Settable Parameters (Part 10 of 19) .................................... E-11
13 Table F.2.1-1. Permanent Mobile Station Indicators ...................................................... F-2
14 Table F.2.2-1. CDMA Semi-permanent Mobile Station Indicators ................................... F-3
15 Table F.3-1. NAM Indicators (Part 1 of 2)....................................................................... F-4
16 Table F.3-1. NAM Indicators (Part 2 of 2)....................................................................... F-5
17
xxxvi
3GPP2 C.S0005-A v6.0
TABLES
1 No text.
xxxvii
3GPP2 C.S0005 v6.0
1 ADDENDUM INTRODUCTION
2 This addendum is provided to correct errors and omissions in the published version of
3 3GPP2 C.S0005-A. This addendum replaces 3GPP2 C.S0005-A.
4 Revisions are indicated by change bars located in the left or right hand margins, and also
5 by specific markings applied to the text.
6 New text is underlined, as shown below.
7 Deleted text is crossed out, as shown below.
8 This is how deleted text is identified.
9 A modified figure is marked similarly to modified text. A new figure is underlined; a deleted
10 figure is crossed out through the middle of the figure.
11 The table of contents does not identify revisions to any section heading, table, or figure.
xxxviii
3GPP2 C.S0005 v6.0
2 No text
xxxix
3GPP2 C.S0005 v6.0
1 FOREWORD
2 1. General. This section defines the terms and numeric indications used in this
3 document. This section also describes the time reference used in the CDMA system and the
4 tolerances used throughout the documentgeneral signaling architecture.
5 2. Requirements for Mobile Station CDMA Operation. This section describes the
6 requirements for CDMA-analog dual-mode mobile stations operating in the CDMA mode. A
7 mobile station complying with these requirements will be able to operate with CDMA base
8 stations complying with this document.
9 3. Requirements for Base Station CDMA Operation. This section describes the
10 requirements for CDMA base stations. A base station complying with these requirements
11 will be able to operate in the CDMA mode with mobile stations complying with this
12 document.
13 Annex A. Reserved.
14 Annex B. CDMA Call Flow Examples. This informative annex provides examples of simple
15 call flows in the CDMA system.
16 Annex C. Reserved.
17 Annex D. CDMA Constants. This normative annex contains tables that give specific
18 values for the constant identifiers found in Section 2 and Section 3.
19 Annex E. CDMA Retrievable and Settable Parameters. This normative annex describes
20 the mobile station parameters that the base station can set and retrieve.
21 Annex F. Mobile Station Database. This informative annex describes a database model
22 that can be used for dual-mode mobile stations complying with this document.
23 Annex G. Encryption Call Flows. This informative annex provides examples of extended
24 encryption call flows in the CDMA system.
xl
3GPP2 C.S0005-A v6.0
1 No text.
xli
3GPP2 C.S0005-A v6.0
1 NOTES
2 1. Compatibility, as used in connection with cdma2000, is understood to mean: any

3 cdma2000 mobile station is able to place and receive calls in cdma2000 and IS-95
4 systems. Conversely, any cdma2000 system is able to place and receive calls for
5 CDMAcdma2000 and IS-95 mobile stations.
6 2. The term “dual-mode mobile station” indicates a mobile station capable of both
7 analog (FM) and spread spectrum (CDMA) operation.
8 3. This compatibility specification is based upon spectrum allocations that have been
9 defined by various governmental administrations.
10 4. Each mobile station is assigned a single unique 32-bit binary serial number (ESN)
11 that cannot be changed by the subscriber without rendering the mobile station
12 inoperative (see 2.3.2).
13 5. “Base station” refers to the functions performed in the fixed network. These
14 functions typically distributed among cells, sectors, and mobile switching centers.
15 6. This standard uses the following verbal forms: “Shall” and “shall not” identify
16 requirements strictly to be followed in order to conform with the standard and from
17 which no deviation is permitted. “Should” and “should not” indicate that one of
18 several possibilities is recommended as particularly suitable, without mentioning or
19 excluding others; that a certain course of action is preferred but not necessarily
20 required; or that (in the negative form) a certain possibility or course of action is
21 discouraged but not prohibited. “May” and “need not” indicate a course of action
22 permissible within the limits of the standard. “Can” and “cannot” are used for
23 statements of possibility and capability, whether material, physical, or causal.
24 7. Footnotes appear at various points in this specification to elaborate and further

25 clarify items discussed in the body of the specification.
26 8. Unless indicated otherwise, this document presents numbers in decimal form.

27 Binary numbers are distinguished in the text by the use of single quotation marks.
28 9. The following operators define mathematical operations:
29 × indicates multiplication.
30 x indicates the largest integer less than or equal to x: 1.1 = 1, 1.0 = 1.
31 x indicates the smallest integer greater or equal to x: 1.1 = 2, 2.0 = 2.
32 |x| indicates the absolute value of x: |-17| = 17, |17| = 17.
33 ⊕ indicates exclusive OR (modulo-2 addition).
34 min (x, y) indicates the minimum of x and y.
35 max (x, y) indicates the maximum of x and y.
xlii
3GPP2 C.S0005-A v6.0
1 x mod y indicates the remainder after dividing x by y: x mod y = x - (y × x/y).
2 10. While communication between Layer 3 and Layer 2 is specified, there is no

3 requirement to implement layering.
xliii
3GPP2 C.S0005-A v6.0
1 REFERENCES
2 The following standards contain provisions which, through reference in this text, constitute
3 provisions of this Standard. At the time of publication, the editions indicated were valid.
4 All standards are subject to revision, and parties to agreements based on this Standard are
5 encouraged to investigate the possibility of applying the most recent editions of the
6 standards indicated below.
xliv
3GPP2 C.S0005-A v6.0
1. Reserved.
2. C.S0002-A v6.0, Physical Layer Standard for cdma2000 Spread Spectrum
Systems, February 2002.
3. C.S0003-A v6.0, Medium Access Control (MAC) Standard for cdma2000 Spread
Spectrum Systems, February 2002.
4. C.S0004-A v6.0, Signaling Link Access Control (LAC) Standard for cdma2000
Spread Spectrum Systems, February 2002.
5. Reserved.
6. C.S0006-A v6.0, Analog Signaling Standard for cdma2000 Spread Spectrum
Systems, February 2002.
7. ANSI T1.607-1990, Integrated Services Digital Network (ISDN)–Layer 3 Signaling
Specification for Circuit Switched Bearer Service for Digital Subscriber Signaling
System Number 1 (DSS1), July 1990.
8. ANSI TI.610-1994, Generic Procedures for the Control of ISDN Supplementary
Services, August, 1994.
9. ANSI X3.4-1986, Coded Character Set - 7-bit American National Standard Code
for Information Interchange, 1992.
10. C.S0010-A0, Recommended Minimum Performance Standards for Base Stations
Supporting Dual-Mode Spread Spectrum Mobile Stations, April 2001.
11. C.S0011-A0, Recommended Minimum Performance Standards for Dual-Mode
Spread Spectrum Mobile Stations, April 2001.
12. TIA/EIA-553-A, Core Analog Standard 800 MHz Mobile Station - Land Station
Compatibility Specification with Authentication, November 1999.
13. TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem Operations,
December 1997.
14. C.S0015-0, Short Message Services for Spread Spectrum Cellular Systems,
November 1999.
15. Common Cryptographic Algorithms, Revision C, 1997. An EAR-controlled
document subject to restricted distribution. Contact the Telecommunications
Industry Association, Arlington, VA.
xlv
3GPP2 C.S0005-A v6.0
16. ITU-T Recommendation E.163, Numbering Plan for the International Telephone
Service, 1988. Note: merged with E.164.
17. ITU-T Recommendation E.164 (I.331), Numbering Plan for the ISDN Era, 1991.
18. ITU-T Recommendation E.212, Identification Plan for Land Mobile Stations,
1988.
19. ITU-T Recommendation F.69, The International Telex Service–Service and
Operational Provisions of Telex Destination Codes and Telex Network
Identifications Codes, 1994.
20. ITU-T Recommendation X.121, International Numbering Plan for Public Data
Networks, 1992.
21. EIA/TIA/IS-54-B, Cellular System Dual-Mode Mobile Station - Base Station
Compatibility Standard, April 1992.
22. TIA/EIA/IS-91, Mobile Station-Base Station Compatibility Standard for 800
MHz Analog Cellular, October 1994.
23. Interface Specification for Common Cryptographic Algorithms, Rev C, 1997.
Contact the Telecommunications Industry Association, Arlington, VA.
24. TIA/EIA-95-B, Mobile Station-Base Station Compatibility Standard for Dual-
Mode Spread Spectrum Cellular System, November 1998.
25. TIA/EIA/IS-136, 800 MHz TDMA Cellular-Radio Interface-Mobile Station-Base
Station Compatibility, December 1994.
26. C.S0016-0, Over-the-Air Service Provisioning of Mobile Stations in Spread
Spectrum Systems, November 1999.
27. TIA/EIA/IS-735, Enhancements to TIA/EIA-41-D & TIA/EIA-664 for Advanced
Features in Wideband Spread Spectrum Systems, January 1998.
28. TSB16, Assignment of Access Overload Classes in the Cellular
Telecommunications Services, March 1985.
29. TSB50, User Interface for Authentication Key Entry, March 1993.
30. C.R1001-0TIA/EIA/TSB58-B, Administration of Parameter Value Assignments
for TIA/EIA Wideband Spread Spectrum Standards, December 1999.
31. C.S0008-0, Multi-Carrier Specification for Spread Spectrum System on GSM MAP
(MC-MAP) – Lower Layers Air Interface, June 2000.
32. C.S0007-0, Direct Spread Specification for Spread Spectrum System on ANSI-41
(DS-41) – Upper Layers Air Interface, June 2000.
33. Enhanced Cryptographic Algorithms, TR45.AHAG 2001.
34. ANSI T1.625, Integrated Services Digital Network (ISDN) – Calling Line
Identification Presentation and Restriction Supplementary Services.
35. CCITT X.213, Information Technology – Open Systems Interconnection –
Network Service Definition, November 1995.
xlvi
3GPP2 C.S0005-A v6.0
36. CCITT X.25, Interface between Data Terminal Equipment (DTE) and Data
Circuit-Terminating Equipment (DCE) for terminals operating in the packet
mode and connected to public data networks by dedicated circuit, October
1996.
xlvii
3GPP2 C.S0005-A v6.0
1 1. GENERAL
2 This section defines the terms and numeric indications used in this document. This section
3 also describes the time reference used in the CDMA system and the tolerances used
4 throughout the documentthe general signaling architecture.
5 1.1 Terms and Numeric Information
6 1.1.1 Terms
7 Abbreviated Alert. An abbreviated alert is used to remind the mobile station user that
8 previously selected alternative routing features are still active.
9 AC. See Authentication Center.
10 Access Attempt. The entire process of sending one message and receiving (or failing to
11 receive) an acknowledgment for that message, consisting of one or more access sub-
12 attempts. See also Access Probe, Access Probe Sequence, and Access Sub-attempt.
13 Access Channel. A Reverse CDMA Channel used by mobile stations for communicating to
14 the base station. The Access Channel is used for short signaling message exchanges such
15 as call originations, responses to pages, and registrations. The Access Channel is a slotted
16 random access channel.
17 Access Channel Message. The information part of an access probe consisting of the
18 message body, length field, and CRC.
19 Access Channel Message Capsule. An Access Channel message plus the padding.
20 Access Channel Preamble. The preamble of an access probe consisting of a sequence of

21 all-zero frames that are sent at the 4800 bps rate.
22 Access Channel Request Message. An Access Channel message that is autonomously

23 generated by the mobile station. See also Access Channel Response Message.
24 Access Channel Response Message. A message on the Access Channel generated to reply
25 to a message received from the base station.
26 Access Channel Slot. The assigned time interval for an access probe. An Access Channel
27 slot consists of an integer number of frames. The transmission of an access probe is
28 performed within the boundaries of an Access Channel slot.
29 Access Entry Handoff. The act of transferring reception of the Paging Channel from one
30 base station to another, when the mobile station is transitioning from the Mobile Station Idle
31 State to the System Access State.
32 Access Handoff. The act of transferring reception of the Paging Channel from one base
33 station to another, when the mobile station is in the System Access State after an Access
34 Attempt.
35 Access Overload Class. See Overload Class.
36 Access Probe. One Access Channel transmission consisting of a preamble and a message.
37 The transmission is an integer number of frames in length and transmits one Access
1-1
3GPP2 C.S0005-A v6.0
1 Channel message. See also Access Probe Sequence, Access Sub-attempt, and Access
2 Attempt.
3 Access Probe Handoff. A handoff that occurs while the mobile station is performing an
4 Access Attempt in the System Access State.
5 Access Probe Sequence. A sequence of one or more access probes on the Access Channel.
6 Other than the reported pilot information, the same Access Channel message content is
7 transmitted in every access probe of an access sub-attempt. See also Access Probe, Access
8 Sub-attempt, and Access Attempt.
9 Access Sub-attempt. A sequence of one or more access probe sequences on the Access
10 Channel transmitted to one pilot, containing the same message content other than the
11 reported pilot information. See also Access Probe, Access Probe Sequence, and Access
12 Attempt.
13 Acknowledgment. A Layer 2 response by the mobile station or the base station confirming
14 that a signaling message was received correctly.
15 Action Time. The time at which the action implied by a message should take effect.
16 Active Set. The set of pilots associated with the CDMA Channels containing Forward
17 Traffic Channels assigned to a particular mobile station.
18 Active User Zone. A user zone in which the mobile station makes its presence known via
19 an explicit registration in order to activate tiered service features. See also CDMA Tiered
20 Services, User Zone, and Passive User Zone.
21 Aging. A mechanism through which the mobile station maintains in its Neighbor Set the
22 pilots that have been recently sent to it from the base station and the pilots whose handoff
23 drop timers have recently expired.
24 A-key. A secret, 64-bit pattern stored in the mobile station and HLR/AC. It is used to
25 generate/update the mobile station’s Shared Secret Data.
26 Assured Mode. Mode of delivery that guarantees that a PDU will be delivered to the peer.
27 A PDU sent in assured mode is retransmitted by the LAC sublayer, up to a maximum
28 number of retransmissions, until the LAC entity at the sender receives an acknowledgement
29 for the PDU. See also Confirmation of Delivery.
30 Authentication. A procedure used by a base station to validate a mobile station’s identity.
31 Authentication Center (AC). An entity that manages the authentication information

32 related to the mobile station.
33 Authentication Response (AUTHR). An 18-bit output of the authentication algorithm. It

34 is used, for example, to validate mobile station registrations, originations and terminations.
35 Autonomous Registration. A method of registration in which the mobile station registers

36 without an explicit command from the base station.
37 Auxiliary Pilot Channel. A non-data-bearing, direct-sequence spread spectrum signal

38 optionally transmitted by a CDMA base station.
1-2
3GPP2 C.S0005-A v6.0
1 Auxiliary Transmit Diversity Pilot Channel. A pilot channel, counterpart to an Auxiliary

2 Pilot Channel, that is transmitted by a CDMA base station from the non-primary antenna
3 when orthogonal transmit diversity is employed.
4 Bad Frames. Frames classified as insufficient frame quality or as 9600 bps primary traffic
5 only, with bit errors. See also Good Frames.
6 Band Class. A set of CDMA frequency assignments and a numbering scheme for these
7 channels. See also CDMA Frequency Assignment.
8 Base Station. A fixed station used for communicating with mobile stations. Depending
9 upon the context, the term base station may refer to a cell, a sector within a cell, an MSC,
10 or other part of the cellular wireless system. See also MSC.
11 Base Station Authentication Response (AUTHBS). An 18-bit pattern generated by the

12 authentication algorithm. AUTHBS is used to confirm the validity of base station orders to
13 update the Shared Secret Data.
14 Base Station Random Variable (RANDBS). A 32-bit random number generated by the
15 mobile station for authenticating base station orders to update the Shared Secret Data.
16 Blank-and-Burst. The preemption of an entire Traffic Channel frame’s primary traffic by

17 signaling traffic or secondary traffic. Blank-and-burst is performed on a frame-by-frame
18 basis.
19 BLOB. Block of Bits.
20 bps. Bits per second.
21 Broadcast Control Channel. A code channel in a Forward CDMA Channel used for
22 transmission of control information or broadcast messages from a base station to a mobile
23 station.
24 Broadcast Control Channel Number (BCN). A number that identifies the Broadcast
25 Control Channel. BCN number 1 corresponds to the Primary Broadcast Control Channel.
26 BCN numbers 2 through 8 correspond to other Broadcast Control Channels (if any).
27 Broadcast User Zone. A user zone that is identified to the mobile station by means of
28 broadcast messages. It corresponds to the RF coverage area of a particular set of cells and
29 sectors. See also CDMA Tiered Services and Mobile-Specific User Zone.
30 Call Disconnect. The process that releases the resources handling a particular call. The
31 disconnect process begins either when the mobile station user indicates the end of the call
32 by generating an on-hook condition or other call-release mechanism, or when the base
33 station initiates a release.
34 Call History Parameter (COUNT). A modulo-64 event counter maintained by the mobile
35 station and Authentication Center that is used for clone detection.
36 Candidate Frequency. The frequency, either analog or CDMA, for which the base station
37 specifies a search set, using a Candidate Frequency Search Request Message.
1-3
3GPP2 C.S0005-A v6.0
1 Candidate Set. The set of pilots that have been received with sufficient strength by the
2 mobile station to be successfully demodulated, but have not been placed in the Active Set
3 by the base station. See also Active Set, Neighbor Set, and Remaining Set.
4 CDMA. See Code Division Multiple Access.
5 CDMA Candidate Frequency. The Candidate Frequency specified for a search of CDMA
6 pilots.
7 CDMA Channel. The set of channels transmitted between the base station and the mobile
8 stations within a given CDMA Frequency Assignment. See also Forward CDMA Channel
9 and Reverse CDMA Channel.
10 CDMA Channel Number. An 11-bit number that identifies a CDMA Frequency Assignment.
11 CDMA Frequency Assignment. A 1.23 or 3.69 MHz segment of spectrum. The center of a
12 CDMA frequency assignment is given by a CDMA Channel Number.
13 CDMA Preferred Set. The set of CDMA channel numbers in a CDMA system corresponding
14 to Frequency Assignments that a mobile station will normally search to acquire a CDMA
15 Pilot Channel. For CDMA cellular systems, the primary and secondary channels comprise
16 the CDMA Preferred Set.
17 CDMA Tiered Services. System features and services that are based on location,
18 potentially including private networks. User zones establish the availability of services. See
19 also User Zone, Broadcast User Zone, Mobile-Specific User Zone, Active User Zone, and
20 Passive User Zone.
21 Center SR3 Frequency. The Spreading Rate 3 frequency that has the center frequency
22 assignment.
23 Chip. See PN Chip.
24 Code Channel. A subchannel of a Forward CDMA Channel or Reverse CDMA Channel.

25 Each subchannel uses an orthogonal Walsh function or quasi-orthogonal function.
26 Code Division Multiple Access (CDMA). A technique for spread-spectrum multiple-access

27 digital communications that creates channels through the use of unique code sequences.
28 Code Symbol. The output of an error-correcting encoder. Information bits are input to the
29 encoder and code symbols are output from the encoder. See Convolutional Code.
30 Configuration Change Indicator. A one-bit datum, sent on the Quick Paging Channel.
31 Appearance of the Configuration Change Indicator in the Quick Paging Channel serves to
32 alert a slotted mode mobile station, operating in the idle state, that, after performing an idle
33 handoff, it should monitor the Paging Channel, the Forward Common Control Channel, or
34 the Primary Broadcast Control Channel in order to determine if it should update its stored
35 parameters.
36 Confirmation of Delivery. A notification sent by the LAC sublayer to Layer 3 at the

37 sender, when the LAC entity at the sender receives the acknowledgment for a specific PDU
38 sent in assured mode.
1-4
3GPP2 C.S0005-A v6.0
1 Convolutional Code. A type of error-correcting code. A code symbol can be considered as

2 modulo 2 the convolution of the input data sequence with the impulse response of a
3 generator function.
4 CRC. See Cyclic Redundancy Code.
5 Cyclic Redundancy Code (CRC). A class of linear error detecting codes that generate
6 parity check bits by finding the remainder of a polynomial division. See also Frame Quality
7 Indicator.
8 dBc. The ratio (in dB) of the sideband power of a signal, measured in a given bandwidth at
9 a given frequency offset from the center frequency of the same signal, to the total inband
10 power of the signal.
11 dBm. A measure of power expressed in terms of its ratio (in dB) to one milliwatt.
12 dBm/Hz. A measure of power spectral density. The ratio, dBm/Hz, is the power in one
13 Hertz of bandwidth, where power is expressed in units of dBm.
14 dBW. A measure of power expressed in terms of its ratio (in dB) to one Watt.
15 Dedicated Control Channel. A portion of a Traffic Channel (Forward or Reverse) that

16 carries a combination of user data, signaling, and power control information.
17 Deinterleaving. The process of unpermuting the symbols that were permuted by the
18 interleaver. Deinterleaving is performed on received symbols prior to decoding.
19 Discontinuous Transmission (DTX). A mode of operation in which a base station or a

20 mobile station switches its transmitter on and off on a particular code channel
21 autonomously. For the case of DTX operation on the Forward Dedicated Control Channel,
22 the Forward Power Control Subchannel is still transmitted.
23 Distance-Based Registration. An autonomous registration method in which the mobile

24 station registers whenever it enters a cell whose distance from the cell in which the mobile
25 station last registered exceeds a given threshold.
26 DTMF. See Dual-Tone Multifrequency.
27 Dual-Tone Multifrequency (DTMF). Signaling by the simultaneous transmission of two

28 tones, one from a group of low frequencies and another from a group of high frequencies.
29 Each group of frequencies consists of four frequencies.
30 Eb. A measure of the energy in a signal, at some point in a communication system, per
31 information bit conveyed by that signal, or an average value of such energies. Its relevance
32 to system performance is most often expressed by its ratio to additive noise and
33 interference, such as in Eb/N0 or Eb/I0. Such ratios are dimensionless, and are usually
34 expressed in dB units.
35 Ec/Io. A notation used to represent a dimensionless ratio of the average power of some
36 code-distinguished CDMA signal channel, typically a pilot, to the total power comprised of
37 signal plus interference, within the signal bandwidth. It is usually expressed in dB units.
38 Effective Radiated Power (ERP). The product of the power supplied to the antenna and
39 its gain relative to a half-wave dipole in a given direction.
1-5
3GPP2 C.S0005-A v6.0
1 EIRP. See Equivalent Isotropic Radiated Power.
2 Electronic Serial Number (ESN). A 32-bit number assigned by the mobile station
3 manufacturer, uniquely identifying the mobile station equipment.
4 Encoder Tail Bits. A fixed sequence of bits added to the end of a block of data to reset the
5 convolutional encoder to a known state.
6 Enhanced Access Channel. A reverse channel used by mobile station for communicating
7 to the base station. The Enhanced Access Channel operates in the Basic Access Mode, and
8 Reservation Access Mode. It is used for transmission of short messages, such as signaling,
9 MAC messages, response to pages, and call originations. It can also be used to transmit
10 moderate-sized data packets.
11 Enhanced Access Channel Preamble. A non-data bearing portion of the Enhanced Access
12 probe sent by the mobile station to assist the base station in initial acquisition and channel
13 estimation.
14 Enhanced Access Channel Slot. The assigned time interval for an enhanced access probe.
15 An Enhanced Access Channel slot consists of an integer number of Enhanced Access
16 Channel frames. The transmission of an enhanced access probe is performed within the
17 boundaries of an Enhanced Access Channel slot.
18 Enhanced Access Data. The data transmitted while in the Basic Access Mode on the
19 Enhanced Access Channel or while in the Reservation Access Mode on a Reverse Common
20 Control Channel.
21 Enhanced Access Header. A frame containing access origination information transmitted

22 immediately after the Enhanced Access Channel Preamble while in the Reservation Access
23 Mode.
24 Enhanced Access Probe. One Enhanced Access Channel transmission consisting of an

25 Enhanced Access Channel preamble, optionally an Enhaned Enhanced Access header, and
26 optionally EnhanedEnhanced Access data. See also Enhanced Access Probe Sequence.
27 Enhanced Access Probe Sequence. A sequence of one or more Enhanced Access probes
28 on the Enhanced Access Channel. See also Enhanced Access Probe.
29 Equivalent Isotropically Radiated Power (EIRP). The product of the power supplied to
30 the antenna and the antenna gain in a direction relative to an isotropic antenna.
31 Erasure Indicator Bit. See [2].
32 ERP. See Effective Radiated Power.
33 ESN. See Electronic Serial Number.

34 f-csch. Forward common signaling logical channel.
35 f-dsch. Forward dedicated signaling logical channel.
36 Fade Timer. A timer kept by the mobile station as a measure of Forward Traffic Channel
37 continuity. If the fade timer expires, the mobile station drops the call.
38 Flash. An indication sent on the Reverse CDMA Channel indicating that the user directed
39 the mobile station to invoke special processing.
1-6
3GPP2 C.S0005-A v6.0
1 Foreign NID Roamer. A mobile station operating in the same system (SID) but in a
2 different network (NID) from the one in which service was subscribed. See also Foreign SID
3 Roamer and Roamer.
4 Foreign SID Roamer. A mobile station operating in a system (SID) other than the one from
5 which service was subscribed. See also Foreign NID Roamer and Roamer.
6 Forward CDMA Channel. A CDMA Channel from a base station to mobile stations. The
7 Forward CDMA Channel contains one or more code channels that are transmitted on a
8 CDMA Frequency Assignment using a particular pilot PN offset. The code channels are
9 associated with the Pilot Channel, Sync Channel, Paging Channels, Broadcast Control
10 Channel, Forward Common Control Channels, and Traffic Channels. The Forward CDMA
11 Channel always carries a Pilot Channel and may also carry up to one Sync Channel, up to
12 seven Paging Channels, one up to eight Broadcast Control Channels, up to seven Forward
13 Common Control Channels and up to the maximum number of channels allowed for the
14 assigned Radio Configuration minus one Traffic Channels, as long as the total number of
15 channels, including the Pilot Channel, is no greater than the maximum number of channels
16 allowed for the assigned Radio Configuration (see [2] section 3.1.3.1.13).
17 Forward Common Control Channel. A control channel used for the transmission of digital
18 control information from a base station to one or more mobile stations.
19 Forward Dedicated Control Channel. A Dedicated Control Channel that is transmitted on

20 the Forward CDMA Channel.
21 Forward Fundamental Channel. A Fundamental Channel that is transmitted on the

22 Forward CDMA Channel.
23 Forward Pilot Channel. A non-data-bearing direct-sequence spread spectrum signal

24 transmitted continuously by each CDMA base station. The Forward Pilot Channel allows a
25 mobile station to acquire the timing of the Forward CDMA Channel, provides a phase
26 reference for coherent demodulation, and provides a means for signal strength comparisons
27 between base stations for determining when to handoff. Different base stations are
28 identified by different pilot PN sequence time phases. See also Pilot PN Sequence, Pilot PN
29 Sequence Offset.
30 Forward Supplemental Channel. A Supplemental Channel that is transmitted on the

31 Forward CDMA Channel.
32 Forward Supplemental Code Channel. A Supplemental Code Channel that is transmitted

33 on the Forward CDMA Channel.
34 Forward Traffic Channel. One or more code channels used to transport user and
35 signaling traffic from the base station to the mobile station. See Forward Fundamental
36 Code Channel, Forward Dedicated Control Channel, Forward Fundamental Channel,
37 Forward Supplemental, and Forward Supplemental Code Channel.
38 Forward Transmit Diversity Pilot Channel. A pilot channel transmitted by a CDMA base
39 station from the non-primary antenna when orthogonal transmit diversity is employed.
40 Frame. A basic timing interval in the system. For the Access Channel, Paging Channel,
41 Broadcast Control Channel, Forward Supplemental Code Channel, and Reverse
1-7
3GPP2 C.S0005-A v6.0
1 Supplemental Code Channel, a frame is 20 ms long. For the Forward Supplemental

2 Channel and Reverse Supplemental channel, a frame is 20, 40, or 80 ms long. For the
3 Sync Channel, a frame is 26.666... ms long. For the Forward Fundamental Channel,
4 Forward Dedicated Control Channel, Reverse Fundamental Channel, and Reverse Dedicated
5 Control Channel, a frame is 5 or 20 ms long. For the Enhance Access Channel, the
6 Forward Common Control Channel, and the Reverse Common Control Channel, a frame is
7 5, 10 or 20 ms long.
8 Frame Category. A classification of a received Traffic Channel frame based upon

9 transmission data rate, the frame contents (primary traffic, secondary traffic, or signaling
10 traffic), and whether there are detected errors in the frame.
11 Frame Offset. A time skewing of Traffic Channel frames from System Time in integer
12 multiples of 1.25 ms. The maximum frame offset is 18.75 ms.
13 Frame Quality Indicator. See [2].
14 Full TMSI. The combination of TMSI_ZONE and TMSI_CODE. The full TMSI is a globally
15 unique address for the mobile station.
16 Fundamental Channel. A portion of a Traffic Channel that can carry a combination of

17 primary data, secondary data, signaling, and power control information.
18 Gating Rate Set. This specifies the set of supported reverse pilot gating rates. The base
19 station and the mobile station may support one or more gating rates.
20 GHz. Gigahertz (109 Hertz).
21 Global Positioning System (GPS). A US government satellite system that provides location
22 and time information to users. See Navstar GPS Space Segment / Navigation User
23 Interfaces ICD-GPS-200 for specifications.
24 Good Frames. Frames not classified as bad frames. See also Bad Frames.
25 GPS. See Global Positioning System.
26 Handoff. The act of transferring communication with a mobile station from one base
27 station to another.
28 Hard Handoff. A handoff characterized by a temporary disconnection of the Traffic

29 Channel. Hard handoffs occur when the mobile station is transferred between disjoint
30 Active Sets, when the CDMA Frequency Assignment changes, when the frame offset
31 changes, or when the mobile station is directed from a CDMA Traffic Channel to an analog
32 voice channel. See also Soft Handoff.
33 Hash Function. A function used by the mobile station to select one out of N available
34 resources. The hash function distributes the available resources uniformly among a
35 random sample of mobile stations.
36 Highest SR3 Frequency. The SR3 frequency that has the highest frequency assignment.
37 HLR. See Home Location Register.
38 Home Location Register (HLR). The location register to which a MIN/IMSI is assigned for
39 record purposes such as subscriber information.
1-8
3GPP2 C.S0005-A v6.0
1 Home System. The wirelesscellular or PCS system in which the mobile station subscribes
2 for service.
3 Hopping Pilot Beacon. A pilot beacon that changes CDMA Frequency periodically to
4 simulate multiple base stations operating on different frequencies. The transmission of the
5 hopping pilot beacon is discontinuous on any CDMA Channel.
6 Idle Handoff. The act of transferring reception of the Paging Channel, Broadcast Control
7 Channel or the Forward Common Control Channel from one base station to another, when
8 the mobile station is in the Mobile Station Idle State.
9 Implicit Registration. A registration achieved by a successful transmission of an

10 origination or page response on the r-csch.
11 IMSI. See International Mobile Station Identity.
12 IMSI_M. MIN-based IMSI using the lower 10 digits to store the MIN.
13 IMSI_O. Operational value of IMSI used by the mobile station for operation with the base
14 station.
15 IMSI_T. True IMSI not associated with MIN. This could be 15 digits or fewer.
16 Interleaving. The process of permuting a sequence of symbols.
17 International Mobile Station Identity (IMSI). A method of identifying stations in the land
18 mobile service as specified in [18].
19 kHz. Kilohertz (103 Hertz).
20 ksps. Kilo-symbols per second (103 symbols per second).
21 LAC. See Link Access Control.
22 Layering. A method of organization for communication protocols in which the transmitted

23 or received information is transferred in pipeline fashion, within each station, in well-
24 defined encapsulated data units between otherwise decoupled processing entities (“layers”).
25 A layer is defined in terms of its communication protocol to a peer layer in another entity
26 and the services it offers to the next higher layer in its own entity.
27 Layer 1. Layer 1 provides for the transmission and reception of radio signals between the
28 base station and the mobile station. Also see Physical Layer.
29 Layer 2. Layer 2 provides for the correct transmission and reception of signaling messages,
30 including partial duplicate detection. Layer 2 makes use of the services provided by Layer
31 1. See also Layering and Layer 3.
32 Layer 3. Layer 3 provides the control messaging for the wirelesscellular or PCS telephone
33 system. Layer 3 originates and terminates signaling messages according to the semantics
34 and timing of the communication protocol between the base station and the mobile station.
35 Layer 3 makes use of the services provided by Layer 2. See also Layering and Layer 2.
36 Link Access Control. See LAC. The LAC Sublayer is the upper sublayer of Layer 2. It
37 implements a data link protocol that provides for the correct transport and delivery of
38 signaling messages generated by Layer 3. The LAC Sublayer makes use of the services
1-9
3GPP2 C.S0005-A v6.0
1 provided by the Lower Layers (Layer 1 and the MAC Sublayer).
2 Local Control. An optional mobile station feature used to perform manufacturer-specific

3 functions.
4 Logical Channel. A communication path between the mobile station and the base station,
5 described in terms of the intended use of, and access to, the transferred data, and direction
6 of transfer. A logical channel can be “mapped” to and from one or more physical channels.
7 Logical-to-physical Mapping. The technique for forming associations between logical and
8 physical channels.
9 Long Code. A PN sequence with period 242 - 1 that is used for scrambling on the Forward
10 CDMA Channel and spreading on the Reverse CDMA Channel. The long code uniquely
11 identifies a mobile station on both the Reverse Traffic Channel and the Forward Traffic
12 Channel. The long code provides limited privacy. The long code also separates multiple
13 Access Channels and Enhanced Access Channels on the same CDMA Channel. See also
14 Public Long Code and Private Long Code.
15 Long Code Mask. A 42-bit binary number that creates the unique identity of the long code.
16 See also Public Long Code, Private Long Code, Public Long Code Mask, and Private Long
17 Code Mask.
18 Lowest SR3 Frequency. The SR3 frequency that has the lowest frequency assignment.
19 LSB. Least significant bit.
20 LTU. Logical Transmission Unit. One of more Type 3 MuxPDUs with a 16-bit CRC.
21 MAC. See Medium Access Control.
22 Maximal Length Sequence (m-Sequence). A binary sequence of period 2n - 1, n being a

23 positive integer, with no internal periodicities. A maximal length sequence can be
24 generated by a tapped n-bit shift register with linear feedback.
25 MCC. See Mobile Country Code.
26 Mcps. Megachips per second (106 chips per second).
27 MCSB. See Message Control and Status Block.
28 Mean Input Power. The total received calorimetric power measured in a specified
29 bandwidth at the antenna connector, including all internal and external signal and noise
30 sources.
31 Mean Output Power. The total transmitted calorimetric power measured in a specified
32 bandwidth at the antenna connector when the transmitter is active.
33 Medium Access Control. See MAC. The MAC Sublayer is the lower sublayer of Layer 2. It
34 implements the medium access protocol and is responsible for transport of LAC protocol
35 data units using the services provided by Layer 1.
36 Message. A data structure that conveys control information or application information. A

37 message consists of a length field (MSG_LENGTH), a message body (the part conveying the
38 information), and a CRC.
1-10
3GPP2 C.S0005-A v6.0
1 Message Body. The part of the message contained between the length field (MSG_LENGTH)
2 and the CRC field.
3 Message Capsule. A sequence of bits comprising a single message and padding. The
4 padding always follows the message and may be of zero length.
5 Message Control and Status Block. In this document, a parameter block representing the
6 PCI being transferred between Layer 3 and Layer 2.
7 Message CRC. The CRC check associated with a message. See also Cyclic Redundancy
8 Code.
9 Message Field. A basic named element in a message. A message field may consist of zero
10 or more bits.
11 Message Record. An entry in a message consisting of one or more fields that repeats in the
12 message.
13 MHz. Megahertz (106 Hertz).
14 MIN. See Mobile Identification Number.
15 MNC. See Mobile Network Code.
16 Mobile Country Code (MCC). A part of the E.212 IMSI identifying the home country. See
17 [18].
18 Mobile Directory Number. A dialable directory number that is not necessarily the same as
19 the mobile station’s air interface identification, i.e., MIN, IMSI_M or IMSI_T.
20 Mobile Identification Number (MIN). The 34-bit number that is a digital representation of
21 the 10-digit number assigned to a mobile station.
22 Mobile Network Code (MNC). A part of the E.212 IMSI identifying the home network
23 within the home country. See [18].
24 Mobile Protocol Capability Indicator (MPCI). A 2-bit field used to indicate the mobile
25 station’s capabilities.
26 Mobile-Specific User Zone. A user zone that is identified by the mobile station. The
27 mobile station may consider parameters such as the identity of the serving system, cell, and
28 sector, and the geographic location of that station in making the determination. See also
29 CDMA Tiered Services, User Zone, Broadcast User Zone, Active User Zone, and Passive User
30 Zone.
31 Mobile Station. A station in the Public WirelessCellular Radio Telecommunications Service

32 intended to be used while in motion or during halts at unspecified points. Mobile stations
33 include portable units (e.g., hand-held personal units) and units installed in vehicles.
34 Mobile Station Class. A classification of mobile stations based on characteristics such as

35 slotted operation and transmission power. See Table 2.3.3-1 of [12] and Table 2.3.3-1 of
36 this document.
37 Mobile Station Identification Number (MSIN). A part of the E.212 IMSI identifying the
38 mobile station within its home network. See [18].
1-11
3GPP2 C.S0005-A v6.0
1 Mobile Station Originated Call. A call originating from a mobile station.
2 Mobile Station Terminated Call. A call received by a mobile station (not to be confused
3 with a disconnect or call release).
4 ms. Millisecond (10-3 second).
5 MSB. Most significant bit.
6 MSC. See Mobile Switching Center.
7 MSIN. See Mobile Station Identification Number.
8 Multiplex Option. The ability of the multiplex sublayer and lower layers to be tailored to
9 provide special capabilities. A multiplex option defines such characteristics as the frame
10 format, the maximum number of Supplemental Code Channels supported, and the rate
11 decision rules. See also Multiplex Sublayer.
12 Multiplex Sublayer. One of the conceptual layers of the system that multiplexes and
13 demultiplexes primary traffic, secondary traffic, and signaling traffic.
14 NAM. See Number Assignment Module.
15 National Mobile Station Identity (NMSI). A part of the E.212 IMSI identifying the mobile
16 station within its home country. The NMSI consists of the MNC and the MSIN. See [18].
17 NDSS. See Network Directed System Selection.
18 Neighbor Set. The set of pilots associated with the CDMA Channels that are probable
19 candidates for handoff. Normally, the Neighbor Set consists of the pilots associated with
20 CDMA Channels that cover geographical areas near the mobile station. See also Active Set,
21 Candidate Set, Remaining Set, and Private Neighbor Set.
22 Network. A network is a subset of a wirelesscellular or PCS system, such as an area-wide

23 cellular network, a private group of base stations, or a group of base stations set up to
24 handle a special requirement. A network can be as small or as large as needed, as long as
25 it is fully contained within a system. See also System.
26 Network Directed System Selection (NDSS). A feature that allows the mobile station to
27 automatically register with a preferred system while roaming, or to be automatically
28 directed by a service provider, typically the home service provider, to a suggested system,
29 regardless of the frequency band class, cellular band, or PCS frequency block.
30 Network Identification (NID). A number that uniquely identifies a network within a

31 wirelesscellular or PCS system. See also System Identification.
32 NID. See Network Identification.
33 NMSI. See National Mobile Station Identity.
34 Non-Autonomous Registration. A registration method in which the base station initiates

35 registration. See also Autonomous Registration.
36 Non-Slotted Mode. An operation mode of the mobile station in which the mobile station
37 continuously monitors the Paging Channel, or the Forward Common Control Channel/
38 Broadcast Control Channel.
1-12
3GPP2 C.S0005-A v6.0
1 ns. Nanosecond (10-9 second).
2 NULL. Any value that is not in the specified range of a field.
3 Null Traffic Channel Data. One or more frames of a specified data sequence sent at the
4 lowest agreed-upon rate of the negotiated radio configuration. Null Traffic Channel data
5 may be sent when there is no primary, secondary, or signaling traffic available. Null Traffic
6 Channel data serves to maintain the connectivity between the mobile station and the base
7 station.
8 Number Assignment Module (NAM). A set of MIN/IMSI-related parameters stored in the

9 mobile station.
10 Numeric Information. Numeric information consists of parameters that appear as

11 numeric fields in messages exchanged by the base station and the mobile station and
12 information used to describe the operation of the mobile station.
13 Optional Field. A field defined within a message structure that is optionally transmitted to
14 the message recipient.
15 Order. A type of message that contains control codes for either the mobile station or the
16 base station.
17 Ordered Registration. A registration method in which the base station orders the mobile
18 station to send registration related parameters.
19 Orthogonal Transmit Diversity (OTD). An optional method of transmission of the

20 Forward CDMA Channel that uses two antennas, each transmitting a fraction of the code
21 symbols. It can be used to enhance performance in the presence of multipath fading radio
22 propagation.
23 OTD. See Orthogonal Transmit Diversity
24 Overhead Message. A message sent by the base station on the Paging Channel or the
25 Primary Broadcast Control Channel to communicate base-station-specific and system-wide
26 information to mobile stations.
27 Overload Class (OLC). The means used to control system access by mobile stations,
28 typically in emergency or other overloaded conditions. Mobile stations are assigned one (or
29 more) of sixteen overload classes. Access to the CDMA system can then be controlled on a
30 per class basis by persistence values transmitted by the base station.
31 PACA. Priority Access and Channel Assignment. See PACA Call.
32 PACA Call. A priority mobile station originated call for which no traffic channel or voice
33 channel was immediately available, and which has been queued for a priority access
34 channel assignment.
35 Packet. The unit of information exchanged between the service option applications of the
36 base station and the mobile station.
37 Padding. A sequence of bits used to fill from the end of a message to the end of a message
38 capsule, typically to the end of the frame or half frame. All bits in the padding are ‘0’.
39 Paging. The act of seeking a mobile station when a call has been placed to that mobile
1-13
3GPP2 C.S0005-A v6.0
1 station.
2 Paging Channel. A code channel in a Forward CDMA Channel used for transmission of
3 control information and pages from a base station to a mobile station.
4 Paging Channel Slot. An 80 ms interval on the Paging Channel. Mobile stations operating
5 in the slotted mode are assigned specific slots in which they monitor messages from the
6 base station.
7 Paging Indicator. A one-bit datum, sent on the Quick Paging Channel. Quick paging
8 indicators are associated with mobile stations, in pairs, via a hashing algorithm.
9 Appearance of both of its indicators in its assigned Quick Paging Channel slot serves to
10 alert a slotted mode mobile station, operating in the idle state, that it should monitor the
11 Paging Channel or the Forward Common Control Channel starting in the next slot. See
12 also Quick Paging Channel.
13 Parameter-Change Registration. A registration method in which the mobile station

14 registers when certain of its stored parameters change.
15 Parity Check Bits. Bits added to a sequence of information bits to provide error detection,
16 correction, or both.
17 Passive User Zone. A user zone in which the implicit registration that takes place at call
18 setup is sufficient to trigger a change in tiered service features. See also CDMA Tiered
19 Services, User Zone, and Active User Zone.
20 PCI. See Protocol Control Information.
21 PCS. See Personal Communications Services.
22 PCSC. See Personal Communications Switching Center.
23 PCS System. See Personal Communications Services System.
24 PDU. See Protocol Data Unit.
25 Personal Communications Services System. A configuration of equipment that provides

26 PCS radiotelephone services.
27 Personal Communications Services (PCS). A family of mobile and portable radio

28 communications services for individuals and businesses that may be integrated with a
29 variety of competing networks. Broadcasting is prohibited and fixed operations are to be
30 ancillary to mobile operations.
31 Personal Communications Switching Center (PCSC). See Mobile Switching Center

32 (MSC).
33 Physical Channel. A communication path between stations, described in terms of the RF

34 characteristics such as coding, power control policies, etc.
35 Physical Layer. The part of the communication protocol between the mobile station and
36 the base station that is responsible for the transmission and reception of data. The
37 physical layer in the transmitting station is presented a frame by the multiplex sublayer
38 and transforms it into an over-the-air waveform. The physical layer in the receiving station
1-14
3GPP2 C.S0005-A v6.0
1 transforms the waveform back into a frame and presents it to the multiplex sublayer above
2 it.
3 Pilot Beacon. A transmit-only base station that broadcasts a Pilot Channel, a Sync
4 Channel, optionally a Paging Channel or a Primary Broadcast Control Channel, but no
5 Forward Common Control Channels and Forward Traffic Channels. The mobile station
6 measures the pilot beacon to assist in CDMA hard handoffs and inter-frequency idle-mode
7 handoffs.
8 Pilot Channel. A non-data-bearing signal transmitted by a CDMA station. See Forward

9 Pilot Channel, Transmit Diversity Pilot Channel, Auxiliary Pilot Channel, Auxiliary Transmit
10 Diversity Pilot Channel, and Reverse Pilot Channel.
11 Pilot PN Chip. One bit, or bit pair, of a pilot PN sequence, or the time interval
12 corresponding thereto.
13 Pilot PN Sequence. A pair of modified maximal length PN sequences used to spread the
14 quadrature components of a CDMA Channel.
15 Pilot PN Sequence Offset. The time offset of a Forward Pilot Channel from CDMA System
16 time, as transmitted by the base station, expressed modulo the pilot period.
17 Pilot PN Sequence Offset Index. The pilot PN sequence offset in units of 64 PN chips of a
18 Forward Pilot Channel, relative to the zero offset pilot PN sequence.
19 Pilot Strength. The ratio of pilot power to total power in the signal bandwidth of a CDMA
20 Forward or Reverse Channel. See also Ec/Io.
21 PN. Pseudonoise.
22 PN Chip. One bit in a PN sequence, or the time duration of such a bit. It corresponds to
23 the smallest modulation interval in a CDMA system.
24 PN Sequence. Pseudonoise sequence. A deterministic, periodic binary sequence having

25 limited statistical similarity to a Bernoulli (coin-tossing).
26 Power Control Bit. A bit sent on the Forward Power Control Subchannel or Reverse Power
27 Control Subchannel to signal the mobile station or base station to increase or decrease its
28 transmit power.
29 Power Control Group. A 1.25 ms interval on the Forward Traffic Channel and the Reverse
30 Traffic Channel. See also Power Control Bit.
31 Power-Down Registration. An autonomous registration method in which the mobile

32 station registers on power-down.
33 Power Up Function. A method by which the mobile station increases its output power to
34 support location services.
35 Power-Up Registration. An autonomous registration method in which the mobile station

36 registers on power-up.
37 PPM. Parts per million.
38 Preamble. See Access Channel Preamble and Traffic Channel Preamble.
1-15
3GPP2 C.S0005-A v6.0
1 Primary CDMA Channel. A pre-assigned channel in a CDMA Cellular System used by the
2 mobile station for initial acquisition. See also Secondary CDMA Channel.
3 Primary Paging Channel (CDMA). The default code channel (code channel 1) assigned for
4 paging on a CDMA Channel.
5 Primary Pilot. One of the three pilots on the Spreading Rate 3 Forward Channels. The
6 primary pilot may be on any one of the SR3 frequencies and may have a higher
7 transmission power comparing to the pilots on the other two SR3 frequencies.
8 Primary Traffic. The main traffic stream carried between the mobile station and the base
9 station on the Traffic Channel. See also Secondary Traffic and Signaling Traffic.
10 Primitive. An atomic, well-defined method of transferring data and control information

11 between two adjacent layers and sublayers. Conventionally represented as a function
12 invocation with the data and/or control information as parameters.
13 Private Long Code. The long code characterized by the private long code mask. See also
14 Long Code.
15 Private Long Code Mask. The long code mask used to form the private long code. See also
16 Public Long Code Mask and Long Code.
17 Private Neighbor Set. The set of pilots associated with the private system base stations
18 that are probable candidates for idle handoff. See also Active Set, Neighbor Set, Remaining
19 Set, and CDMA Tiered Services.
20 Protocol Control Information (PCI). Data passed between adjacent layers in the protocol
21 stack, together with the SDU, to assist a layer to properly encapsulate/decapsulate the
22 SDU. Examples of PCI in this document are the MCSB and the PCSB.
23 Protocol Data Unit. Encapsulated data communicated between peer layers on the mobile
24 station and base station. Unless specified otherwise, in this document PDU refers to the
25 Layer 3 protocol data unit transferred at the interface between lLayer 3 and lLayer 2.
26 Protocol Stack. Conceptual model of the layered architecture for communication protocols
27 (see Layering) in which layers within a station are represented in the order of their numeric
28 designation and requiring that transferred data be processed sequentially by each layer, in
29 the order of their representation. Graphically, the “stack” is drawn vertically, with the layer
30 having the lowest numeric designation at the base.
31 Public Long Code. The long code characterized by the public long code mask.
32 Public Long Code Mask. The long code mask used to form the public long code. The mask
33 contains a permutation of the bits of the ESN, and also includes the channel number when
34 used for a Supplemental Code Channel. See also Private Long Code Mask and Long Code.
35 PUF. See Power Up Function.
36 PUF Attempt. A sequence of PUF probes sent by the mobile station in response to a Power
37 Up Function Message.
38 PUF Probe. One or more consecutive frames on the Reverse Traffic Channel within which
39 the mobile station transmits the PUF pulse.
1-16
3GPP2 C.S0005-A v6.0
1 PUF Pulse. Portion of PUF probe that may be transmitted at elevated output power.
2 PUF Target Frequency. The CDMA frequency assignment to which the base station directs
3 a mobile station for transmitting the PUF probe.
4 Punctured Code. An error-correcting code generated from another error-correcting code by

5 deleting (i.e., puncturing) code symbols from the coder output.
6 QoS. See Quality of Service.
7 Quality of Service. Set of parameters and procedures associated with a service and/or
8 user, indicating some of the capabilities and constraints related to the delivery of the
9 service to the user.
10 Quick Paging. A feature that permits mobile stations to further conserve battery power
11 beyond the savings achieved by slotted mode operation. See also Paging Indicator and
12 Configuration Change Indicator.
13 Quick Paging Channel. An uncoded, on-off-keyed (OOK) spread spectrum signal sent by
14 base stations to inform slotted mode mobile stations, operating in the idle state, whether to
15 monitor the Paging Channel or the Forward Common Control Channel. See also Quick
16 Paging, Paging Indicator, and Configuration Change Indicator.
17 Quick Paging Channel Slot. An 80 ms interval on the Quick Paging Channel. See also
18 Paging Indicator and Configuration Change Indicator.
19 Quick Repeats. Additional transmissions of identical copies of a message within a short

20 interval to increase the probability that the message is received correctly.
21 r-csch. Reverse common signaling logical channel.
22 r-dsch. Reverse dedicated signaling logical channel.
23 Radio Configuration. A set of Forward Traffic Channel and Reverse Traffic Channel
24 transmission formats that are characterized by physical layer parameters such as
25 transmission rates, modulation characteristics and spreading rate. See Table 3.1.3.1-1 and
26 Table 2.1.3.1-1 of [2].
27 Radio Configuration Class. A group of Radio Configurations. All Radio Configurations, for
28 the Forward Traffic Channel and the Reverse Traffic Channel, are divided into three classes
29 by the types of pre-spreading symbols (BPSK and QPSK) and spreading rates. RC Class 1
30 consists of RC 1 and RC 2 for the Forward Traffic Channel and the Reverse Traffic Channel.
31 RC Class 2 consists of RC 3 and RC 4 of the Reverse Traffic Channel, and RC 3, RC 4 and
32 RC 5 of the Forward Traffic Channel. RC Class 3 consists of RC 5 and RC 6 of the Reverse
33 Traffic Channel, and RC 6, RC 7, RC 8, and RC 9 of the Forward Traffic Channel.
34 RC. See Radio Configuration.
35 Registration. The process by which a mobile station identifies its location and parameters
36 to a base station.
37 Registration Zone. A collection of one or more base stations treated as a unit when
38 determining whether a mobile station should perform zone-based registration. See also
39 User Zone, with which it should not be confused.
1-17
3GPP2 C.S0005-A v6.0
1 Release. A process that the mobile station and base station use to inform each other of call
2 disconnect.
3 Remaining Set. The set of all allowable pilot offsets as determined by PILOT_INC,
4 excluding the pilot offsets of the pilots in the Active Set, Candidate Set, and Neighbor Set.
5 See also Active Set, Candidate Set, and Neighbor Set.
6 Replay Attack. An attempt by a third party to record an over-the-air message and send it
7 later in time so as to mislead the receiver.
8 Request. A lLayer 3 message generated by either the mobile station or the base station to
9 retrieve information, ask for service, or command an action.
10 Response. A lLayer 3 message generated as a result of another message, typically a

11 request.
12 Reverse CDMA Channel. The CDMA Channel from the mobile station to the base station.
13 From the base station’s perspective, the Reverse CDMA Channel is the sum of all mobile
14 station transmissions on a CDMA Frequency Assignment.
15 Reverse Dedicated Control Channel. A Dedicated Control Channel that is transmitted on

16 the Reverse CDMA Channel.
17 Reverse Fundamental Channel. A Fundamental Channel that is transmitted on the

18 Reverse CDMA Channel.
19 Reverse Pilot Channel. A non-data-bearing direct-sequence spread spectrum signal

20 transmitted by each CDMA mobile station whenever the Enhanced Access Channel, Reverse
21 Common Control Channel, or Reverse Traffic Channel is enabled. The Reverse Pilot
22 Channel allows a base station to acquire the timing of the Reverse CDMA Channel and
23 provides a phase reference for coherent demodulation. The Reverse Pilot Channel may be
24 transmitted either continuously or in gated mode.
25 Reverse Supplemental Channel. A Supplemental Channel that is transmitted on the

26 Reverse CDMA Channel.
27 Reverse Supplemental Code Channel. A Supplemental Code Channel that is transmitted

28 on the Reverse CDMA Channel.
29 Reverse Traffic Channel. A Traffic Channel on which data and signaling are transmitted
30 from a mobile station to a base station. The Reverse Traffic Channel is composed of zero or
31 one Reverse Fundamental Channel, zero to seven Reverse Supplemental Code Channels,
32 zero to two Reverse Supplemental Channels, and zero or one Reverse Dedicated Control
33 Channel.
34 Roamer. A mobile station operating in a wirelesscellular system (or network) other than
35 the one from which service was subscribed. See also Foreign NID Roamer and Foreign SID
36 Roamer.
37 SAP. See Service Access Point.
38 SCI. See Synchronized Capsule Indicator Bit.
39 SDU. See Service Data Unit.
1-18
3GPP2 C.S0005-A v6.0
1 Search Window. The range of PN sequence offsets that a mobile station searches for a
2 pilot.
3 Search Window Offset. PN sequence offset used by the mobile station to position the
4 search window when searching for a pilot.
5 Secondary CDMA Channel. A pre-assigned channel in a CDMA Cellular System used by

6 the mobile station for initial acquisition. See also Primary CDMA Channel.
7 Secondary Traffic. An additional traffic stream that can be carried between the mobile
8 station and the base station on the Traffic Channel. See also Primary Traffic and Signaling
9 Traffic.
10 Service Access Point. Conceptual point at the interface between two adjacent layers
11 where services are provided to the upper layer and data and protocol information is
12 exchanged between layers.
13 Service Configuration. The common attributes used by the mobile station and the base
14 station to build and interpret Traffic Channel frames. Service configuration corresponds to
15 the parameters contained in the Service Configuration information record and the Non-
16 negotiable Service Configuration information record. Examples of such parameters include
17 Forward and Reverse Traffic Channel multiplex options, Forward and Reverse Traffic
18 Channel transmission rates, service option connections, and reverse pilot gating rate.
19 Service Data Unit. Data transferred between adjacent layers in the protocol stack. Unless
20 specified otherwise in this document SDU refers to the Layer 3 service data unit being
21 transferred to/from Layer 2.
22 Service Negotiation. The procedures used by the mobile station and base station to
23 establish a service configuration. See also Service Option Negotiation.
24 Service Option. A service capability of the system. Service options may be applications
25 such as voice, data, or facsimile. See [30].
26 Service Option Connection. A particular instance or session in which the service defined
27 by a service option is used. Associated with a service option connection are a reference,
28 which is used for uniquely identifying the service option connection, a service option, which
29 specifies the particular type of service in use, a Forward Traffic Channel traffic type, which
30 specifies what type of Forward Traffic Channel traffic is used to support the service option
31 connection, and a Reverse Traffic Channel traffic type, which specifies what type of Reverse
32 Traffic Channel traffic is used by the service option connection.
33 Service Option Connection Reference. A designator used by the base station and mobile
34 station to uniquely identify a particular service option connection.
35 Service Option Negotiation. The procedures used by the mobile station and base station
36 to establish a service configuration. Service option negotiation is similar to service
37 negotiation, but allows less flexibility for specifying the attributes of the service
38 configuration. See also Service Negotiation.
39 Service Redirection. The process by which the base station alters the system selection
40 made by a mobile station. It can be used temporarily during maintenance and testing to
41 divert subscribers to an alternate system.
1-19
3GPP2 C.S0005-A v6.0
1 Serving Frequency. The CDMA frequency on which a mobile station is currently

2 communicating with one or more base stations.
3 Shared Secret Data (SSD). A 128-bit pattern stored in the mobile station (in semi-
4 permanent memory) and known by the base station. SSD is a concatenation of two 64-bit
5 subsets: SSD_A, which is used to support the authentication procedures, and SSD_B,
6 which serves as one of the inputs to the process generating the encryption mask and
7 private long code.
8 Short Message Services (SMS). A suite of services such as SMS Text Delivery, Digital
9 Paging (i.e., Call Back Number - CBN), and Voice Mail Notification (VMN).
10 SID. See System Identification.
11 Signaling Traffic. Control messages that are carried between the mobile station and the
12 base station on the Traffic Channel. See also Primary Traffic and Secondary Traffic.
13 Silent Re-origination. An autonomous attempt to re-originate a call after the mobile

14 station Layer 3 receives an access attempt failure indication from Layer 2 following a user-
15 initiated origination or a re-origination. Silent re-origination does not apply to any user-
16 programmable capabilities or services, e.g. user-programmable automatic redial.
17 Slotted Mode. An operation mode of the mobile station in which the mobile station
18 monitors only selected slots on the Paging Channel or the Forward Common Control
19 Channel when in the Mobile Station Idle State.
20 Soft Handoff. A handoff occurring while the mobile station is in the Mobile Station Control
21 on the Traffic Channel State. This handoff is characterized by commencing communications
22 with a new base station on the same CDMA Frequency Assignment before terminating
23 communications with an old base station. See also Hard Handoff.
24 SOM. Start-of-Message bit.
25 Space Time Spreading (STS). A forward link transmission method which transmits all
26 forward link channel symbols on multiple antennas and spreads the symbols with
27 complementary Walsh or quasi-orthogonal functions.
28 Spreading Rate. The PN chip rate of the system, defined as a multiple of 1.2288 Mcps.
29 Spreading Rate 1. A 1.2288 Mcps chip rate-based system using a direct-spread single
30 carrier.
31 Spreading Rate 3. A 3.6864 Mcps chip rate-based system using three 1.2288 Mcps carriers
32 on the Forward CDMA Channel. The Reverse CDMA Channel uses a 3.6864 Mcps direct-
33 spread carrier.
34 sps. Symbols per second.
35 SR. See Spreading Rate.
36 SR1. See Spreading Rate 1.
37 SR3. See Spreading Rate 3.
38 SR3 Frequencies. CDMA frequencies for the three 1.2288 Mcps carriers on the Forward
1-20
3GPP2 C.S0005-A v6.0
1 CDMA Channel. SR3 frequencies include the lowest SR3 frequency, the center SR3
2 frequency, and the highest SR3 frequency.
3 SR3 Primary Pilot. See Primary Pilot.
4 SSD. See Shared Secret Data.
5 Station Class Mark (SCM). An identification of certain characteristics of a mobile station.

6 Classes are defined in Table 2.3.3-1 of [12] and Table 6.3.3-1 of this document.
7 Status Information. The following status information is used to describe mobile station
8 operation when using the analog system:
9 • Serving-System Status. Indicates whether a mobile station is tuned to channels

10 associated with System A or System B.
11 • First Registration ID Status. A status variable used by the mobile station in

12 association with its processing of received Registration ID messages.
13 • First Location Area ID Status. A status variable used by the mobile station in
14 association with its processing of received Location Area ID messages.
15 • Location Registration ID Status. A status variable used by the mobile station in

16 association with its processing of power-up registrations and location-based
17 registrations.
18 • First Idle ID Status. A status variable used by the mobile station in association with
19 its processing of the Idle Task.
20 • Local Control Status. Indicates whether a mobile station must respond to local
21 control messages.
22 • Roam Status. Indicates whether a mobile station is in its home system.
23 • Termination Status. Indicates whether a mobile station must terminate the call
24 when it is on an analog voice channel.
25 • Update Protocol Capability Status. Indicates whether the mobile station should
26 report its protocol capability to the serving system.
27 Supplemental Channel. An optional portion of a Traffic Channel (Forward or Reverse

28 Radio Configurations 3 and above) that operates in conjunction with a Fundamental
29 Channel in that Traffic Channel, and (optionally) with other Supplemental Channels to
30 provide higher data rate services.
31 Supplemental Code Channel. An optional portion of a Traffic Channel (Forward or

32 Reverse Radio Configurations 1 and 2) that operates in conjunction with a Fundamental
33 Code Channel in that Traffic Channel, and (optionally) with other Supplemental Code
34 Channels to provide higher data rate services. On this channel a combination of primary
35 data, secondary data, or both (but never signaling information) are transmitted.
36 Symbol. See Code Symbol and Modulation Symbol.
37 Sync Channel. Code channel 32 in the Forward CDMA Channel which transports the
38 synchronization message to the mobile station.
1-21
3GPP2 C.S0005-A v6.0
1 Sync Channel Superframe. An 80 ms interval consisting of three Sync Channel frames

2 (each 26.666... ms in length).
3 System. A system is a cellular telephone service or personal wireless communications

4 service that covers a geographic area such as a city, metropolitan region, county, or group
5 of counties. See also Network.
6 System Identification (SID). A number uniquely identifying a cellular or PCS wireless

7 system.
8 System Time. The time reference used by the system. System Time is synchronous to
9 UTC time (except for leap seconds) and uses the same time origin as GPS time. All base
10 stations use the same System Time (within a small error). Mobile stations use the same
11 System Time, offset by the propagation delay from the base station to the mobile station.
12 See also Universal Coordinated Time.
13 Target Frequency. The CDMA frequency assignment to which the base station directs a
14 mobile station in a handoff using an Extended Handoff Direction Message, a General
15 Handoff Direction Message, or a Universal Handoff Direction Message.
16 TD. See Transmit Diversity.
17 Temporary Mobile Station Identity (TMSI). A temporary mobile station identification

18 assigned by the base station.
19 Timer-Based Registration. A registration method in which the mobile station registers

20 whenever a counter reaches a predetermined value. The counter is incremented an average
21 of once per 80 ms period.
22 Time Reference. A reference established by the mobile station that is synchronous with
23 the earliest arriving multipath component used for demodulation.
24 TMSI. See Temporary Mobile Station Identity.
25 TMSI Zone. The administrative zone that allows the TMSI to be reused. The TMSI_CODE
26 has to be unique within a TMSI zone but may be reused in a different TMSI zone. The TMSI
27 zone is identified by the field TMSI_ZONE.
28 Traffic Channel. A communication path between a mobile station and a base station used
29 for user and signaling traffic. The term Traffic Channel implies a Forward Traffic Channel
30 and Reverse Traffic Channel pair. See also Forward Traffic Channel and Reverse Traffic
31 Channel.
32 Traffic Channel Preamble. For RC1 and RC2, a sequence of all-zero frames that is sent by
33 the mobile station on the Reverse Traffic Channel as an aid to Traffic Channel acquisition.
34 For RC3 to RC6 inclusive, the traffic preamble is the ungated transmission of the Reverse
35 Pilot.
36 Transmit Diversity. See Orthogonal Transmit Diversity and Space Time Spreading.
37 Unassured Mode. Mode of delivery that does not guarantee that a PDU will be delivered to
38 the peer. The LAC entity at the receiver does not acknowledge a PDU sent in unassured
39 mode.
1-22
3GPP2 C.S0005-A v6.0
1 Unique Challenge-Response Procedure. An exchange of information between a mobile

2 station and a base station for the purpose of confirming the mobile station’s identity. The
3 procedure is initiated by the base station and is characterized by the use of a challenge-
4 specific random number (i.e., RANDU) instead of the random variable broadcast globally
5 (RAND).
6 Unique Random Variable (RANDU). A 24-bit random number generated by the base
7 station in support of the Unique Challenge-Response procedure.
8 Universal Coordinated Time (UTC). An internationally agreed-upon time scale maintained

9 by the Bureau International de l’Heure (BIH) used as the time reference by nearly all
10 commonly available time and frequency distribution systems i.e., WWV, WWVH, LORAN-C,
11 Transit, Omega, and GPS.
12 User Zone. An area within which CDMA Tiered Services may be provided. It may
13 correspond to an RF coverage area, or it may be established independent of RF topology.
14 User Zones are classified as broadcast versus mobile-specific, and as active versus passive.
15 See Broadcast User Zone, Mobile-Specific User Zone, Active User Zone, and Passive User
16 Zone. See also Registration Zone, with which it should not be confused.
17 User Zone Registration. An autonomous registration method in which the mobile station
18 registers when it selects an active user zone while in the Idle State. See also Zone-Based
19 Registration, with which it should not be confused.
20 Upper Layers. General reference to Layer 3 and the layers above it.
21 User Zone Exit parameter. A parameter used by the mobile station to determine if it
22 should exit a User Zone.
23 UTC. Universal Temps Coordiné. See Universal Coordinated Time.
24 Voice Privacy. The process by which user voice transmitted over a CDMA Traffic Channel
25 is afforded a modest degree of protection against eavesdropping over the air.
26 Walsh Chip. See [2].
27 Walsh Function. One of 2N time orthogonal binary functions (note that the functions are
28 orthogonal after mapping ‘0’ to 1 and ‘1’ to -1).
29 Wireless Local Loop. Wireless alternative access mechanism to provide standard

30 telecommunication services using standard wireline terminal via a radio link between the
31 network and customer premises equipment.
32 WLL. See Wireless Local Loop.
33 Zone-Based Registration. An autonomous registration method in which the mobile station

34 registers whenever it enters a zone that is not in the mobile station’s zone list. See also
35 User Zone Registration, with which it should not be confused.
36 Zone Timer. A timer used by the mobile station to remove outdated entries from its list of
37 zones in which it has previously registered.
38 µs. Microsecond (10-6 second).
1-23
3GPP2 C.S0005-A v6.0
1 1.1.2 Numeric Information
2 Numeric information is used to describe the operation of the mobile station. The following
3 subscripts are used to clarify the use of the numeric information:
4 • “s” indicates a value stored in a mobile station’s temporary memory.
5 • “sv” indicates a stored value that varies as a mobile station processes various tasks.
6 • “sl” indicates the stored limits on values that vary.
7 • “r” indicates a value received by a mobile station over a forward analog control
8 channel or a CDMA Forward Channel.
9 • “p” indicates a value set in a mobile station’s permanent security and identification
10 memory.
11 • “s-p” indicates a value stored in a mobile station’s semi-permanent security and

12 identification memory.
13 1.1.2.1 Reserved
14 1.1.2.2 CDMA Numeric Information
15 The following are internal values that are stored by the mobile station in temporary memory
16 that are not sent over the air. See Annex F for values stored by the mobile station in
17 permanent and semi-permanent memory.
18 1XRL_FREQ_OFFSETs – Frequency offset of the 1X reverse link.
19 A41_SYS_PAR_MSG_SEQs – ANSI-41 System Parameters Message sequence number.
20 ACC_CHANs – Number of Access Channels supported by the current Paging Channel.
21 ACC_ENT_HO_ORDERs – Access entry handoff permitted from the Mobile Station Order and
22 Message Processing Operation of the Mobile Station Idle State.
23 ACCESS_ENTRY_HOs – Idle handoff permitted when entering the System Access State.
24 ACCESS_HOs – Handoff permitted after performing an access attempt while the mobile
25 station is in the System Access State.
26 ACCESS_HO_ALLOWEDs – Handoff permitted to the corresponding neighbor base station
27 while in the System Access State.
28 ACCESS_HO_LIST – List of pilots to which access handoff or access probe handoff is

29 permitted.
30 ACC_HO_LIST_UPDs – Access handoff list update permitted indicator.
31 ACCESS_HO_MSG_RSPs – Access handoff permitted in the System Access State between

32 the time that the mobile station receives a message and responds to that message.
33 ACCESS_PROBE_HOs – Access probe handoff permitted during an access attempt in the
34 Mobile Station Origination Attempt Substate or the Page Response Substate.
1-24
3GPP2 C.S0005-A v6.0
1 ACC_MSG_SEQs – Last received Access Parameters Message or Enhanced Access

2 Parameters Message sequence number.
3 ACC_PROBE_HO_OTHER_MSGs – Access probe handoff permitted for Access Channel
4 messages other than the Origination Message and the Page Response Message.
5 ACCT_INCL_EMGs – Access Control based on Call Type (ACCT) applies to emergency calls
6 indicator.
7 ACCT_SO_GRP_LIST – List of service option groups that have Access Control based on Call
8 Type (ACCT) enabled.
9 ACCT_SO_LIST – List of individual service options that have Access Control based on Call
10 Type (ACCT) enabled.
11 ACH_ACC_TMOs – Access Channel acknowledgment timeout, in units of 80 ms.
12 ACK_WAITINGs[i] – Acknowledgment status indicator for message sequence number i. Set

13 to YES if an acknowledgment is pending for the message; otherwise, set to NO.
14 ADD_INTERCEPTs – The intercept in the inequality criterion for adding a pilot to the Active
15 Set.
16 AGEs – Neighbor list age. For each pilot in the Neighbor Set, the mobile station increments
17 this counter each time a Neighbor List Update Message or an Extended Neighbor List Update
18 Message is received. When AGEs exceeds NGBHR_MAX_AGE, the pilot is deleted from the
19 Neighbor Set.
20 ALIGN_TIMING_USEDs – Indicates whether the mobile station aligns the times of visits
21 away from the Serving Frequency, as requested by the base station, in the periodic search
22 procedures.
23 ANALOG_CHANs – Analog channel number for CDMA-to-analog handoff.
24 ANALOG_NGHBR_LIST – List containing information about neighboring analog systems.

25 AN_CHAN_TYPEs – Analog voice channel type.
26 ASSIGNED_QPAGECHs – Assigned Quick Paging Channel number.
27 AUTHs – Current authentication mode.
28 AUTO_MSG_INTERVAL – Autonomous message interval.
29 AUTO_MSG_SUPPORTED – Autonomous message supported indicator.

30 BAD_FRAMESs – Forward Fundamental Channel bad frames count. The number of
31 received bad forward Fundamental Channel frames.
32 BASE_CLASSs – Base station class of the current base station.
33 BASE_IDs – Base station identification of the current base station.
34 BASE_LATs – Latitude of the current base station, in units of 0.25 seconds.
35 BASE_LONGs – Longitude of the current base station, in units of 0.25 seconds.
1-25
3GPP2 C.S0005-A v6.0
1 BEGIN_PREAMBLEs – A stored variable in the mobile station that contains the size of the
2 preamble that shall be transmitted on a Reverse Supplemental Code Channel at the
3 beginning of a Reverse Supplemental Code Channel transmission.
4 BKOFFs – Access Channel probe sequence backoff range.
5 BRATs – Data rate of the Broadcast Control Channel.
6 BYPASS_ALERT_ANSWERs – Mobile station termination bypass indicator. This is set to ‘1’

7 if the mobile station is to bypass the Waiting for Order Substate and the Waiting for Mobile
8 Station Answer Substate, and proceed directly to the Conversation Substate when Layer 3
9 receives a forward dedicated channel-acquired indication from Layer 2.
10 CDMABANDs. CDMA band class. The CDMA band class currently used by the mobile
11 station.
12 CDMACHs – CDMA Channel number. The CDMA Channel number currently used by the
13 mobile station.
14 CF_CDMABANDs – Candidate Frequency CDMA band class. The CDMA band class
15 specified in the Candidate Frequency Search Request Message.
16 CF_CDMACHs – Candidate Frequency CDMA Channel number. The CDMA Channel
17 number specified in the Candidate Frequency Search Request Message.
18 CF_PILOT_INCs – PILOT_INC to be used by the mobile station after an inter-frequency hard
19 handoff to the CDMA Candidate Frequency is successfully completed.
20 CF_SEARCH_PRIORITY_INCLs – Candidate Frequency neighbor pilots’ search priority
21 included indicator.
22 CF_SRCH_OFFSET_INCLs – Candidate Frequency neighbor pilot search window offset
24 CF_SRCH_WIN_NGHBR_INCLs – Candidate Frequency neighbor pilots’ search window
26 CF_SRCH_WIN_Ns – Search window size for the Candidate Frequency Search Set.
27 CF_SRCH_WIN_Rs – Search window size to be used for the Remaining Set after an inter-
28 frequency hard handoff to the CDMA Candidate Frequency is successfully completed.
29 CF_T_ADDs – Pilot detection threshold to be used on the CDMA Candidate Frequency. The
30 stored value is a positive value in units of 0.5 dB.
31 CH_INDs – A two-bit physical channel indicator, based on the currently established

32 physical channels. The least significant bit denotes the Fundamental Channel, and the
33 most significant bit denotes the Dedicated Control Channel.
34 CHAN_LST_MSG_SEQs – CDMA Channel List Message sequence number.
35 CODE_CHAN_LIST – Code Channel List. A descriptive structure used to manage the

36 Forward Fundamental Channel, and Forward Supplemental Code Channels, if any,
37 associated with the mobile station’s Active Set.
38 COMPLETE_PUF_FRAMEs – Number of power control groups required to make the PUF
1-26
3GPP2 C.S0005-A v6.0
1 probe an integer number of frames.

2 COMPLETE_SEARCHs – Flag to indicate if the mobile station is to complete the search of
3 the Candidate Frequency Search Set after it has determined that the inter-frequency
4 handoff attempt to the CDMA Candidate Frequency is unsuccessful.
5 CONFIG_MSG_SEQs – Current message sequence number for the System Parameters
6 Message, Neighbor List Message, Extended Neighbor List Message, General Neighbor List
7 Message, CDMA Channel List Message, Extended System Parameters Message, Global Service
8 Redirection Message, Private Neighbor List Message, User Zone Identification Message,
9 Extended CDMA Channel List Message, Extended Global Service Redirection Message, MC-RR
10 Parameters Message, ANSI-41 System Parameters Message.
11 COUNTER_ENABLEDs – Timer-based registration indicator. Set to YES if timer-based
12 registration is enabled; otherwise, set to NO.
13 C_SIG_ENCRYPT_MODEs – Common Channel signaling message encryption mode.
14 CS_SUPPORTEDs – Base station Concurrent Services supported indicator. This 1-bit field
15 is set to ‘1’ if the base station supports concurrent connection of at least two services that
16 use either Primary or Secondary traffic type concurrent services.
17 CURR_ACC_MSG_SEQ – Current Access Parameters Message or Enhanced Access
18 Parameters Message sequence number.
19 CURRENT_ACTIVE_PILOTs – Identifies the current pilot in the Active Set during an access
20 attempt.
21 CURRENT_PUF_PROBEs – Number of the next PUF probe to be transmitted within the PUF
22 attempt.
23 DAYLTs – Daylight Savings Time indicator.
24 DCCH_BAD_FRAMESs – Forward Dedicated Control Channel bad frames count. The

25 number of received bad forward Dedicated Control Channel frames.
26 DCCH_TOT_FRAMESs – Total forward Dedicated Control Channel frames received. The
27 total number of received forward Dedicated Control Channel frames, counted for Forward
28 Traffic Channel power control.
29 DECORR – Hashing function input used to decorrelate hashing function applications for
30 the same mobile station.
31 DEFAULT_CONFIGs – Mobile station current default configuration.
32 DELETE_FOR_TMSIs – A storage variable in the mobile station that indicates whether the
33 mobile station should delete its current TMSI if the TMSI was assigned in a different TMSI
34 zone.
35 DIFF_RX_PWR_THRESHs – Threshold for the difference between the received power on the
36 Serving Frequency and the received power on the CDMA Candidate Frequency for the
37 mobile station to search for pilots on the CDMA Candidate Frequency.
38 DISTANCE – Distance from registered base station to current base station, used for
39 distance-based registration.
1-27
3GPP2 C.S0005-A v6.0
1 DROP_INTERCEPTs – The intercept in the inequality criterion for dropping a pilot from the
2 Active Set.
3 DSCCs – Digital supervisory color code.
4 D_SIG_ENCRYPT_MODEs – Dedicated Channel signaling message encryption mode.
5 DTXs – Discontinuous transmission mode for analog channel assignment and CDMA-to-
6 analog handoff.
7 EACH_ACC_TMOs – Enhanced Access Channel acknowledgment timeout, in units of 20
8 ms.
9 EACH_SLOTs – See [2].
10 EACH_SLOT_OFFSET1s – See [2].
11 EACH_SLOT_OFFSET2s – See [2].
12 EC_IO_THRESHs – Pilot Ec/Io threshold used for system reselection.
13 EC_THRESHs – Pilot power threshold used for system reselection.
14 ENC_KEY_SIZEs – The key size used for signaling and user information encryption on
15 common channel and dedicated channel.
16 ENC_KEYs – The encryption key for signaling and user information encryption on common
17 channel and dedicated channel.
18 ENC_SEQ – An 8-bit temporary variable for encryption/decryption.

19 ENCRYPT_MODEs – Current message encryption mode.
20 EXCL_P_REV_MS – Exclude from redirection by MOB_P_REV indicator.

21 EXT_NGHBR_LST_MSG_SEQs – Extended Neighbor List Message sequence number.
22 EXT_CHAN_LISTs – Extended CDMA Channel List Message sent indicator.
23 EXT_CHAN_LST_MSG_SEQs – Extended CDMA Channel List Message sequence number.
24 EXT_DECRYPT_SEQ[i] – The 32-bit crypto-sync counter used to decrypt signaling

25 messages, where i = 0 is for unassured messages and i = 1 is for assured messages.
26 EXT_ENCRYPT_SEQ[i] – The 32-bit crypto-sync counter used to encrypt signaling

27 messages, where i = 0 is for unassured messages and i = 1 is for assured messages.
28 EXT_ENC_SEQ – A 32-bit temporary variable for encryption/decryption.

29 EXT_GLOBAL_REDIRECTs – Extended Global Service Redirection Message sent indicator.
30 EXT_GLOB_SERV_REDIR_MSG_SEQs – Extended Global Service Redirection Message

31 sequence number.
32 EXT_SYS_PARAMETERs – Extended System Parameters Message sent indicator.
33 EXT_SYS_PAR_MSG_SEQs – Extended System Parameters Message sequence number.
34 FCCCHs – Current Forward Common Control Channel number.
1-28
3GPP2 C.S0005-A v6.0
1 FIRST_ACTIVE_PILOTs – While the mobile station is in the System Access State, identifies
2 the pilot to which the first access probe was transmitted, upon entering the System Access
3 State.
4 FOR_DURATIONs – A stored variable in the mobile station that contains the duration (in
5 units of 80 ms) of a forward Supplemental Code Channel transmission that begins at time
6 FOR_START_TIMEs.
7 FOR_FCH_RCs – Forward Fundamental Channel Radio Configuration.
8 FOR_FRAME_40_MAX_RATEs – The maximum data rate for the mobile station's

9 transmission at 40 ms frame length on the Forward Supplemental Channel.
10 FOR_FRAME_80_MAX_RATEs – The maximum data rate for the mobile station's
11 transmission at 80 ms frame length on the Forward Supplemental Channel.
12 FOR_LINKED_HDM_SEQs – Storage variable containing the most recent forward sequence
13 number of the General Handoff Direction Message to which a Supplemental Channel
14 Assignment Message forward assignment was linked.
15 FOR_NID_REGs – Foreign NID roamer autonomous registration enable.
16 FOR_RCs – Forward Channel Radio Configuration.
17 FOR_SCH_CC_INDEXs – Supplemental code channel index used on the Supplemental

18 Channel.
19 FOR_SCH_DURATIONs – A stored variable in the mobile station which contains the
20 duration of a forward Supplemental Channel transmission which begins at time
21 FOR_SCH_START_TIMEs.
22 FOR_SCH_FRAME_LENGTHs – The Forward Supplemental Channel frame length.
23 FOR_SCH_RATEs – The rate of the Forward Supplemental Channel.
24 FOR_SCH_START_TIMEs – A stored variable in the mobile station which contains the

25 System Time, in units of time specified by START_TIME_UNITs, (modulo 32) at which the
26 mobile station shall start (or resume) processing Forward Supplemental Channels.
27 FOR_SID_REGs – Foreign SID roamer autonomous registration enable.
28 FOR_START_TIMEs – A stored variable in the mobile station that contains the System
29 Time, in units of 80 ms, (modulo 64) at which the mobile station shall start (or resume)
30 processing Forward Supplemental Code Channels.
31 FPC_DCCH_CURR_SETPTs – Current power control subchannel outer loop setpoint for the
32 Forward Dedicated Control Channel.
33 FPC_DCCH_FERs – Target frame error rate for the Forward Dedicated Control Channel.
34 FPC_DCCH_MAX_SETPTs – Maximum value of the power control subchannel outer loop

35 setpoint for the Forward Dedicated Control Channel.
36 FPC_DCCH_MIN_SETPTs – Minimum value of the power control subchannel outer loop
37 setpoint for the Forward Dedicated Control Channel.
1-29
3GPP2 C.S0005-A v6.0
1 FPC_DELTA_SCH_SETPTs – The difference between the Fundamental Channel current

2 power control subchannel outer loop setpoint and the Supplemental Channel current power
3 control subchannel outer loop setpoint.
4 FPC_DELTA_SETPTs – The difference between the Fundamental Channel current power
5 control subchannel outer loop setpoint and the Dedicated Control Channel current power
6 control subchannel outer loop setpoint.
7 FPC_FCH_CURR_SETPTs – Current power control subchannel outer loop setpoint for the
8 Forward Fundamental Channel.
9 FPC_FCH_FERs – Target frame error rate for the Forward Fundamental Channel.
10 FPC_FCH_MAX_SETPTs – Maximum value of the power control subchannel outer loop

11 setpoint for the Forward Fundamental Channel.
12 FPC_FCH_MIN_SETPTs – Minimum value of the power control subchannel outer loop
13 setpoint for the Forward Fundamental Channel.
14 FPC_MODEs – Forward power control operating mode.
15 FPC_MODE_NO_SCHs – Forward power control operating mode except during the forward
16 Supplemental Channel assignment interval.
17 FPC_MODE_SCHs – Forward power control operating mode during the forward
18 Supplemental Channel assignment interval.
19 FPC_PRI_CHANs – Primary power control subchannel measured channel.
20 FPC_SEC_CHANs – Index of Forward Supplemental Channel to be measured by the

21 secondary power control subchannel.
22 FPC_SCH_CURR_SETPTs[i] – Current power control subchannel outer loop setpoint for
23 Forward Supplemental Channel i.
24 FPC_SCH_FERs[i] – Target frame error rate for Forward Supplemental Channel i.
25 FPC_SCH_MAX_SETPTs[i] – Maximum value of the power control subchannel outer loop

26 setpoint for Forward Supplemental Channel i.
27 FPC_SCH_MIN_SETPTs[i] – Minimum value of the power control subchannel outer loop
28 setpoint for Forward Supplemental Channel i.
29 FPC_SETPT_THRESHs – Power control subchannel outer loop setpoint report threshold for
30 the Dedicated Control Channel.
31 FPC_SETPT_THRESH_SCHs – Power control subchannel outer loop setpoint report
32 threshold for the Supplemental Channel.
33 FRAME_OFFSETs – Current Traffic Channel frame offset, in units of 1.25 ms.
34 GEN_NGHBR_LST_MSG_SEQs – General Neighbor List Message sequence number.
35 GLOBAL_REDIRECTs – Global Service Redirection Message sent indicator.
36 GLOB_SERV_REDIR_MSG_SEQs – Global Service Redirection Message sequence number.
37 GRANTED_MODEs – Mobile station current granted mode.
1-30
3GPP2 C.S0005-A v6.0
1 HASH_KEY – Hashing function input that determines the return value. Derived from
2 IMSI_O.
3 HDM_SEQs – Last received Extended Handoff Direction Message, General Handoff Direction
4 Message, or Universal Handoff Direction Message sequence number.
5 HOME_REGs – Home (non-roaming) autonomous registration enable.
6 IGNORE_ESCAMs – Identifies whether a mobile station will process the reverse

7 supplemental channel assignment portion of the subsequent Supplemental Channel
8 Assignment Message or Reverse Supplemental Channel Assignment Mini Message.
9 IGNORE_SCAMs – Identifies whether a mobile station will process the reverse supplemental
10 code channel assignment portion of the subsequent Supplemental Channel Assignment
11 Message.
12 IMSI_11_12s – The 11th and 12th digits of the IMSI used for address matching.
13 IMSI_O_ADDR_NUMs- The number of digits in the NMSI of the Operational IMSI (IMSI_O)
14 minus four.
15 IMSI_O_Ss – The last 10-digits of Operational IMSI (IMSI_O).
16 IMSI_O_11_12s – The 11th and 12th digits of the Operational IMSI (IMSI_O).
17 INIT_PWRs – Initial power offset for Access Channel probes.
18 LC_STATEs – Long code state obtained from the Sync Channel Message.
19 LOGICAL_TO_PHYSICAL_MAPPING_TABLE[]s – This table contains the logical to physical

20 mapping for signaling and user traffic.
21 LP_SECs – Leap seconds count (offset of CDMA system time from UTC).
22 LTM_OFFs – Local time offset from UTC, in units of 15 minutes.
23 MAX_CAP_SZs – Maximum number of Access Channel or Enhanced Access Channel frames

24 in an Access Channel message capsule, less 3.
25 MAX_NUM_ALT_SOs – The maximum number of alternative service option numbers that
26 the mobile station is allowed to include in the Origination Message or in the Page Response
27 Message.
28 MAX_NUM_PROBE_HOs – The maximum number of times that a mobile station is
29 permitted to perform an access probe handoff.
30 MAX_PWR_PUFs – Maximum number of PUF probes to be transmitted at maximum mobile
31 station output power during a PUF attempt.
32 MAX_REQ_SEQs – Maximum number of access probe sequences for an Access Channel or
33 Enhanced Access Channel request.
34 MAX_RSP_SEQs – Maximum number of access probe sequences for an Access Channel or
35 Enhanced Access Channel response.
36 MAX_SLOT_CYCLE_INDEXs – Maximum value of the slot cycle index allowed by the
37 current base station.
1-31
3GPP2 C.S0005-A v6.0
1 MCCs – The Mobile Country Code used for address matching.
2 MCC_Os – The Mobile Country Code of IMSI_O.
3 MC_RR_PAR_MSG_SEQs – MC-RR System Parameters Message sequence number.
4 MEMs – Analog message encryption mode for CDMA-to-analog handoff.

5 MIN_PILOT_EC_IO_THRESHs – Threshold for total Ec/Io of pilots in the Serving Frequency
6 Active Set used in the Periodic Serving Frequency Pilot Report Procedure.
7 MIN_PILOT_PWR_THRESHs – Threshold for total Ec of pilots in the Serving Frequency
8 Active Set used in the Periodic Serving Frequency Pilot Report Procedure.
9 MIN_P_REVs – Minimum mobile station protocol revision level required for access to the
10 CDMA system.
11 MIN_TOTAL_PILOT_EC_IOs – Total pilot strength threshold for the mobile station to
12 attempt to demodulate the Forward Traffic Channel on the CDMA Candidate Frequency.
13 MOB_QOSs – Indicator of whether the mobile station is allowed to request QoS settings in
14 the Origination Message, Origination Continuation Message, or Enhanced Origination
15 Message.
16 MOB_TERMs – Mobile station termination indicator. Set to ‘1’ if the mobile station will
17 accept mobile station terminated calls in its current roaming status.
18 MSG_PSISTs – Persistence modifier for Access Channel message and Enhanced Access data
19 transmissions.
20 MS_LATs – The latitude of the mobile station as estimated by the base station.
21 MS_LOC_TSTAMPs – The time corresponding to the estimate of mobile station’s latitude

22 and longitude.
23 MS_LONGs – The longitude of the mobile station as estimated by the base station.
24 MS_INIT_POS_LOC_SUP_INDs – Mobile station initiated position location determination

25 supported indicator.
26 MULT_NIDSs – Multiple NID storage indicator. Set to ‘1’ if the mobile station may store
27 more than one entry in SID_NID_LISTs for each SID.
28 MULT_SIDSs – Multiple SID storage indicator. Set to ‘1’ if the mobile station may store
29 entries in SID_NID_LISTs having different SIDs.
30 NAR_AN_CAPs – Narrow analog voice channel capability.
31 NDSS_ORIGs – NDSS Origination Indicator. Indicator used when the mobile station is
32 NDSS-redirected while originating a call.
33 NGHBR_BANDs – Neighbor band class.
34 NGHBR_CONFIGs – Neighbor base station channel allocation configuration.
35 NGHBR_FREQs – Neighbor CDMA channel number.
36 NGHBR_LST_MSG_SEQs – Neighbor List Message sequence number.
1-32
3GPP2 C.S0005-A v6.0
1 NGHBR_MAX_AGEs – Neighbor set maximum age for retention in the set.
2 NGHBR_PNs – Neighbor base station Pilot Channel PN sequence offset in units of 64 PN

3 chips.
4 NGHBR_REC – Record containing information about a neighbor base station (see also
5 NGHBR_REC_LIST).
6 NGHBR_REC_LIST – Neighbor base station record list. A descriptive structure used to

7 manage the base station’s information records about neighbor base stations (see also
8 NGHBR_REC).
9 NGHBR_SET_ACCESS_INFOs – Neighbor Set access handoff or access probe handoff
10 information included indicator.
11 NGHBR_SET_ENTRY_INFOs – Neighbor Set access entry handoff information included
12 indicator.
13 NGHBR_SET_SIZEs – Size of the Neighbor Set.
14 NGHBR_TIMING_INCLs – Indicates that hopping pilot beacon timing information is

15 included.
16 NGHBR_TX_DURATIONs – Hopping pilot beacon transmit time duration.
17 NGHBR_TX_OFFSETs – Hopping pilot beacon transmit time offset.
18 NGHBR_TX_PERIODs – Hopping pilot beacon transmit time period.
19 NIDs – Network identification. A network is a subset of the base stations within a

20 wirelesscellular or PCS system.
21 NOM_PWRs – Nominal transmit power offset. A correction factor to be used by mobile
22 stations in the open loop power estimate.
23 NUM_ANALOG_NGHBRs – Number of neighboring analog systems.
24 NUM_FCCCHs – Number of Forward Common Control Channels supported on the current

25 CDMA channel.
26 NUM_PREAMBLEs – Number of Traffic Channel preamble.
27 NUM_QPCHs – Number of Quick Paging Channels supported on the current CDMA channel.
28 NUM_REV_CODESs – A storage variable in the mobile station that contains the number of
29 Reverse Supplemental Code Channels that will be utilized in the next Reverse Supplemental
30 Code Channel transmission beginning at time REV_START_TIMEs. A value of 0 indicates
31 no Reverse Supplemental Code Channel transmission will be permitted (i.e., there is no
32 pending Reverse Supplemental Code Channel transmission).
33 NUM_STEPs – Number of access probes or enhanced access probes in a single access probe
34 sequence or enhanced access probe sequence.
35 OTHER_REPORTED_LIST – List of other pilots that have pilot strengths exceeding T_ADD
36 and that are not included in ACCESS_HO_LIST.
1-33
3GPP2 C.S0005-A v6.0
1 PACAs – PACA call indicator. Set to enabled to indicate that the mobile station is waiting
2 for a priority access channel assignment; otherwise, set to disabled. In Sections 2 and 3,
3 PACAs = 0 is equivalent to setting PACAs to disabled and PACAs = 1 is equivalent to setting
4 PACAs to enabled.
5 PACA_CANCEL – PACA call cancel indicator. Set to ‘1’ when the mobile station is directed
6 by the user to cancel the PACA call; otherwise, set to ‘0’.
7 PACA_SIDs – PACA system identifier. Equal to the SID of the system on which the mobile
8 station originated a PACA call.
9 PACA_TIMEOUTs – PACA state timer duration. Specifies how long the mobile station
10 should wait for a PACA Message from the base station.
11 PACKET_ZONE_IDs – Packet data services zone identifier of the base station.
12 PAGECHs – Current CDMA Paging Channel number.
13 PAGED – Indicator for a page match detected while the mobile station is in the System
14 Access State.
15 PAGE_CHANs – Number of Paging Channels supported on the current CDMA channel.
16 PAM_SZs – Number of frames in the Access Channel or Enhanced Access Channel

17 preamble, less 1.
18 PARAMETER_REGs – Parameter-change registration enable.
19 PERIODIC_SEARCHs – Flag to indicate if the mobile station is to perform a periodic search

20 on the Candidate Frequency.
21 PGSLOT – Value obtained from the hashing function, used to determine the mobile
22 station’s assigned Paging Channel slots.
23 PILOT_ARRIVAL – Time of occurrence, as measured at the mobile station antenna

24 connector, of the earliest arriving usable multipath component of the pilot. The arrival time
25 is measured relative to the mobile station’s time reference.
26 PILOT_INFO_REQ_SUPPORTEDs – Pilot information request supported indicator.
27 PILOT_GATING_RATEs – Reverse pilot gating rate on the Reverse Pilot Channel.
28 PILOT_GATING_USE_RATE – Reverse pilot gating rate enable indicator. It indicates

29 whether or not the Reverse Pilot Channel is gated.
30 PILOT_INCs – Pilot PN sequence offset index increment. The interval between pilots, in
31 units of 64 PN chips, for base stations in a system.
32 PILOT_PNs – Pilot Channel PN sequence offset, in units of 64 PN chips, for a base station.
33 PILOT_PN_PHASE – Calculated Pilot Channel PN phase, in chips, including the PN

34 sequence offset and the arrival time relative to the mobile station’s time reference.
35 PILOT_REPORTs – Pilot reporting indicator.
36 POTENTIAL_CDMACHs – The CDMA Channel number that could potentially be used by the
37 mobile station.
1-34
3GPP2 C.S0005-A v6.0
1 POWER_DOWN_REGs – Power down registration enable indicator.
2 POWER_UP_REGs – Power up registration enable indicator.
3 PPSMM_PERIODs – The period used in the Periodic Serving Frequency Pilot Report
4 Procedure.
5 PRATs – Data rate of the Paging Channels.
6 P_REVs – Protocol revision level supported by a base station.
7 P_REV_IN_USEs – Protocol revision level currently in use by a mobile station.
8 PREF_MSID_TYPEs – Preferred mobile station identifier field type.
9 PREVIOUS_ACTIVE_PILOTs – Identifies the pilot, if any, which was in the Active Set
10 immediately prior to the current pilot in the Active Set, during the current access attempt.
11 PRI_NGHBR_LISTs – Private Neighbor List Message sent indicator.
12 PRI_NGHBR_PN – Private Neighbor base station Pilot Channel PN sequence offset in units
13 of 64 PN chips.
14 PRI_NGHBR_REC – Record containing information about a private neighbor base station

15 (see also PRI_NGHBR_REC_LIST).
16 PRI_NGHBR_REC_LIST – Private neighbor base station record list. A descriptive structure

17 used to manage the base station’s information records about private neighbor base stations
18 (see also PRI_NGHBR_REC).
19 PRI_NGHBR_LST_MSG_SEQs – Private Neighbor List Message sequence number.
20 PROBE_BKOFFs – Access Channel probe backoff range, in slots.
21 PROBE_PN_RANs – Range for hashing function selection of the delay prior to transmission
22 of Access Channel probes. Value is log2(range + 1).
23 PSISTs – Persistence value for the mobile station’s overload class.
24 PUF_FREQ_INCLs – Flag to indicate whether the mobile station is to transmit a PUF probe
25 on the serving frequency or on a target frequency.
26 PUF_INIT_PWRs – Power increase (in dB) of the first PUF pulse in a PUF attempt.
27 PUF_INTERVALs – Number of frames between the start of each PUF probe.
28 PUF_PULSE_SIZEs – Duration of a PUF pulse in power control groups.
29 PUF_PWR_STEPs – Amount (in dB) by which the mobile station is to increment the power
30 of a PUF pulse above nominal power from one PUF pulse to the next.
31 PUF_SETUP_SIZEs – Number of power control groups within a PUF probe before the
32 transmission of the PUF pulse.
33 PUF_SF_CDMABANDs – Serving Frequency CDMA band class.
34 PUF_SF_CDMACHs – Serving Frequency CDMA Channel number.
35 PUF_TF_CDMABANDs – Target Frequency CDMA band class.
1-35
3GPP2 C.S0005-A v6.0
1 PUF_TF_CDMACHs – Target Frequency CDMA Channel number.
2 PUF_TX_PWRs – Mobile station’s output power for the PUF pulse.
3 PWR_CNTL_STEPs – Power control step size assigned by the base station that the mobile
4 station is to use for closed loop power control.
5 PWR_PERIOD_ENABLEs – Forward power control periodic reporting enabled indicator.
6 PWR_REP_DELAYs – Power report delay. The period that the mobile station waits following
7 an autonomous Power Measurement Report before restarting frame counting for power
8 control purposes.
9 PWR_REP_FRAMESs – Power control reporting frame count. The number of frames over
10 which the mobile station is to count frame errors. Value is 2 × log2(frames / 5).
11 PWR_REP_THRESHs – Power control reporting threshold. The number of bad frames to be

12 received in a measurement period before the mobile station is to generate a Power
13 Measurement Report Message.
14 PWR_STEPs – Power increment for successive access probes, in units of 1.0 dB.
15 PWR_THRESH_ENABLEs – Forward power control threshold reporting enabled indicator.
16 QOF_IDs – Quasi-orthogonal function index on the Supplemental Channel.
17 QPAGECHs – Current Quick Paging Channel number.
18 QPCH_CCI_SUPPORTEDs – Flag to indicate if configuration change indicators are

19 supported on the Quick Paging Channel.
20 QPCH_POWER_LEVEL_PAGEs – Relative power level of the transmitted Quick Paging
21 Channel Paging Indicator modulation symbols, relative to the Forward Pilot Channel.
22 QPCH_POWER_LEVEL_CONFIGs – Relative power level of the transmitted Quick Paging
23 Channel Configuration Change Indicator modulation symbols, relative to the Forward Pilot
24 Channel.
25 QPCH_RATEs – Indicator rate of the current Quick Paging Channel(s).
26 QPCH_SUPPORTEDs – Flag to indicate if the Quick Paging Channel is supported by the

27 base station.
28 RA – Random access channel number. The Access Channel number generated (pseudo-
29 randomly) by the mobile station.
30 RANDs – Authentication random challenge value.
31 RANDC – The eight most-significant bits of the random challenge value used by the mobile
32 station.
33 RANDOM_TIME – Random time. A portion of SYS_TIME used to seed the random number
34 generator.
35 RC_CAP_REQUESTEDs – Radio Configuration Capability indicator. When set to “1” the
36 mobile station shall include the Radio Configuration capabilities that it supports in the
37 Origination Message and Page Response Message.
1-36
3GPP2 C.S0005-A v6.0
1 RCCCH_SLOTs – See [2].
2 RCCCH_SLOT_OFFSET1s – See [2].

3 RCCCH_SLOT_OFFSET2s – See [2].
4 REDIRECTIONs – Service redirection indicator. Set to enabled to indicate that service

5 redirection is currently in effect; otherwise, set to disabled.
6 REDIRECT_RECs – Holds the service redirection criteria specified in the redirection record
7 of the most recently received Global Service Redirection Message or Service Redirection
8 Message.
9 REG_COUNTs – The timer-based registration counter.
10 REG_COUNT_MAXs – Timer-based registration count limit. The timer-based registration

11 counter expiration value computed from REG_PRDr.
12 REG_DISTs – Registration distance. Distance from last registration that causes a distance-
13 based registration to occur.
14 REG_ENABLEDs – Autonomous registrations enabled indicator.
15 REG_ENCRYPT_RESYNC – Encryption re-sync required registration indicator.

16 REGISTEREDs – Mobile station registered indicator.
17 REG_PRDs – Registration period. The time interval between timer-based registrations.

18 Value is 4 × log2(time / 0.08 s).
19 REG_PSISTs – Persistence modifier for registration accesses (except ordered registrations).
20 REG_ZONEs – Registration zone number of the base station.
21 REJECT_UZIDs – User Zone identifier of the User Zone rejected by the base station.
22 RESELECT_INCLUDEDs – System reselection information included indicator. When this is

23 set to ‘1’, the system reselection procedure is enabled.
24 RESUME_PREAMBLEs – A storage variable in the mobile station that contains the size of
25 the preamble that shall be transmitted on a Reverse Supplemental Code Channel at the
26 beginning of transmission on a Reverse Supplemental Code Channel when resuming
27 transmission following an interruption when discontinuous transmission is occurring.
28 RETRY_DELAYs[i] – A storage variable in the mobile station that contains the system time
29 before which the mobile station may not transmit a specific message. The type of message
30 that cannot be transmitted is specified by RETRY_TYPE, represented here by i. A
31 RETRY_DELAYs[i] value of 0 indicates no retry delay is in effect, and a value of ‘11111111’
32 indicates an infinite retry delay.
33 RETRY_DELAY_UNITs – The units for the value of RETRY_DELAYs. Possible values are
34 1000ms and 60000ms.
35 RETRY_DELAY_VALUEs – The unitless value of the retry delay.
36 RETRY_TYPEs – The retry delay type. It specifies the type of message to which the retry
37 delay value applies. If set to a value of 0, it indicates that all retry delay values should be
1-37
3GPP2 C.S0005-A v6.0
1 cleared.
2 RETURN_CAUSEs – Reason for the mobile station registering or accessing the system.
3 RETURN_IF_FAILs – Return if fail indicator. Set to ‘1’ to indicate that mobile station is to
4 return to the system from which it was redirected if it fails to acquire service on a system
5 using specified redirection criteria. Otherwise, set to ‘0’.
6 RETURN_IF_HANDOFF_FAILs – Return if handoff fail indicator. Indicates if the mobile
7 station is to resume using the Active Set on the Serving Frequency following an
8 unsuccessful hard handoff attempt.
9 REV_DTX_DURATIONs – Maximum duration of time in units of 20 ms that the mobile
10 station is allowed to stop transmitting on a Reverse Supplemental Code Channel or Reverse
11 Supplemental Channel within the reverse assignment duration.
12 REV_DURATIONs – A stored variable in the mobile station that contains the duration (in
13 units of 80 ms) of the Reverse Supplemental Code Channel transmission that will begin at
14 time REV_START_TIMEs.
15 REV_FCH_GATING_MODEs – The reverse Fundamental Traffic Channel gating mode in

16 Radio Configurations 3, 4, 5, and 6 where 50% of the PCGs in the 1500 bps and 1800 bps
17 frames are gated off (see 2.1.3.7.8 of C.P0002-A). Set to ‘1’ if the mobile station is operating
18 in the reverse fundamental channel gating mode.
19 REV_FCH_RCs – Reverse Fundamental Channel Radio Configuration.
20 REV_FRAME_40_MAX_RATEs – The maximum data rate for the mobile station's

21 transmission at 40 ms frame length on the Reverse Supplemental Channel.
22 REV_FRAME_80_MAX_RATEs – The maximum data rate for the mobile station's
23 transmission at 80 ms frame length on the Reverse Supplemental Channel.
24 REV_LINKED_HDM_SEQs – Storage variable containing the most recent reverse sequence
25 number of the General Handoff Direction Message to which a Supplemental Channel
26 Assignment Message reverse assignment was linked.
27 REV_PWR_CNTL_DELAYs – The reverse link power control delay for the reverse
28 fundamental channel gating mode in Radio Configurations 3, 4, 5, and 6 and the gated
29 preamble transmission on the Enhanced Access Channel or the Reverse Common Control
30 Channel. The delay is the time between the end of the reverse link PCG and the beginning
31 of the forward link PCG minus one, when the round trip delay is zero.
32 REV_RCs – Reverse Channel Radio Configuration.
33 REV_SCH_DTX_DURATIONs – Maximum duration of time in units of 20 ms that the mobile

34 station is allowed to stop transmitting on a Reverse Supplemental Channel within the
35 reverse assignment duration.
36 REV_SCH_DURATIONs – A stored variable in the mobile station which contains the
37 duration of the Reverse Supplemental Channel transmission which will begin at time
38 REV_SCH_START_TIMEs.
39 REV_SCH_FRAME_LENGTHs – The Reverse Supplemental Channel frame length.
1-38
3GPP2 C.S0005-A v6.0
1 REV_SCH_RATEs – The rate of the Reverse Supplemental Channel.
2 REV_SCH_START_TIMEs – A stored variable in the mobile station which contains the

3 System Time, in units of time specified by START_TIME_UNITs, (modulo 32) at which the
4 mobile station shall start (or resume) processing Reverse Supplemental Channels.
5 REV_START_TIMEs – A stored variable in the mobile station that contains the next 80 ms
6 frame boundary (modulo 64) on which the mobile station is assigned to start Reverse
7 Supplemental Code Channel transmission.
8 REV_WALSH_IDs – Reverse Supplemental Channel Walsh cover Identifier.
9 RN_HASH_KEYs – Name of an internal variable having the same value as the mobile
10 station's ESN. This variable is used by procedures defined in [3].
11 ROAM_INDIs – Enhanced roaming indicator used for mobile station roaming condition
12 display.
13 RS – Inter-probe sequence backoff. The delay in slots generated (pseudorandomly) by the

14 mobile station following an unsuccessful access probe sequence or prior to the first access
15 probe in a response attempt.
16 RT – Inter-probe backoff. The delay in slots generated (pseudorandomly) by the mobile

17 station following an unacknowledged access probe.
18 SCCs – SAT color code for analog channel assignment and CDMA-to-analog handoff.
19 SCAM_FOR_DURATION_MODEs – Indicator for a specific or an indefinite Forward

20 Supplemental Code Channel assignment duration.
21 SCAM_FOR_ORDERs – The stop or start command set by a Supplemental Channel
22 Assignment Message that is linked to a General Handoff Direction Message.
23 SCAM_REV_DURATION_MODEs – Indicator for a specific or an indefinite Reverse
24 Supplemental Code Channel assignment duration.
25 SCH_BAD_FRAMESs – Forward Supplemental Channel bad frames count. The number of
26 received bad forward Supplemental Channel frames.
27 SCH_TOT_FRAMESs – Total forward Supplemental Channel frames received. The total
28 number of received forward Supplemental Channel frames, counted for Forward Traffic
29 Channel power control.
30 SYNC_IDs – Service Configuration Synchronization Identifier. This is a 16-bit CRCvariable
31 length computed over the entire identifier corresponding to the Service Configuration
32 information record and Non-negotiable Service Configuration information record that may
33 be stored by the mobile station.and The SYNC_ID value is used for by the base station to
34 determineining whether these two information records should may be includomitted in from
35 the Service Connect Message sent by the base station to the mobile station. The mobile
36 station generates this parameter based on the Service Configuration information record and
37 Non-negotiable Service Configuration information record stored at the mobile station (if
38 stored), and sends it to the base station in the Origination Message or the Page Response
39 Message. The base station computes this parameter based on these two information records
40 targeted to be sent to the mobile station. If the computed value matches the one sent by
1-39
3GPP2 C.S0005-A v6.0
1 the mobile station, then Based on the value of SYNC_ID sent by the mobile station, base
2 station doesmay not send these two information records over the air and expects the mobile
3 station to start using the stored ones.
4 SCRM_SEQ_NUMs – Storage variable containing the most recently transmitted
5 Supplemental Channel Request Message sequence number.
6 SEARCH_MODEs – Search mode to be used in a periodic search on the Candidate
7 Frequency.
8 SEARCH_OFFSETs – Time offset of the start of the first search from the action time of the
9 Candidate Frequency Search Request Message or the Candidate Frequency Search Control
10 Message that starts a search.
11 SEARCH_PERIODs – Period for search on the Candidate Frequency.
12 SEARCH_PRIORITYs – Neighbor Pilot Channel search priority.
13 SEARCH_PRIORITY_INCLs – Search priorities included indicator.
14 SEARCH_TIME_RESOLUTIONs – Unit of delay used in the Candidate Frequency Search

15 Report Message to report the total and maximum times away from the Serving Frequency.
16 SENDING_RANDs – ANSI-41 RAND Message sent indicator.
17 SERV_NEGs – Service negotiation indicator. Indicates whether the mobile station is to use
18 service negotiation or service option negotiation.
19 SERV_REQ_NUMs – Service request sequence number. Sequence number to use when
20 requesting a new service configuration.
21 SERVSYSs – Selected serving system indicator for Band Class 0. Set to SYS_A if the mobile
22 station operates in system A; otherwise, set to SYS_B.
23 SETTING_SEARCH_WIN – SRCH_WIN_NGHBR Setting flag. Set to ‘1’ if the mobile station

24 shall set the SRCH_WIN_NGHBR field of each NGHBR_REC to SEARCH_WIN_Ns for all
25 NGHBR_SET_SIZEs entries upon receiving the System Parameters Message.
26 SF_ADD_INTERCEPTs – Intercept of the handoff add criterion for the Serving Frequency,
27 stored during hard handoff.
28 SF_CDMABANDs – Serving Frequency CDMA band class, stored during hard handoff.
29 SF_CDMACHs – Serving Frequency CDMA Channel number, stored during hard handoff.
30 SF_CODE_CHAN_LISTs – Serving Frequency Code Channel List, stored during hard

31 handoff.
32 SF_DROP_INTERCEPTs – Intercept of the handoff drop criterion for the Serving Frequency,
34 SF_ENCRYPT_MODEs – Message encryption indicator for the Serving Frequency, stored
35 during hard handoff.
36 SF_FRAME_OFFSETs – Traffic Channel frame offset used on the Serving Frequency, stored
1-40
3GPP2 C.S0005-A v6.0
1 SF_NOM_PWRs – Nominal transmit power offset used on the Serving Frequency, stored
3 SF_NOM_PWR_EXTs – Extended nominal transmit power offset indicator for the Serving
4 Frequency, stored during hard handoff.
5 SF_P_REVs – Protocol revision level supported by the base station on the Serving
6 Frequency.
7 SF_P_REV_IN_USEs – Protocol revision level currently used by the mobile station on the
8 Serving Frequency.
9 SF_PRIVATE_LCMs – Private long code mask indicator for the Serving Frequency, stored
11 SF_SERV_NEGs – Service negotiation indicator for the Serving Frequency, stored during
12 hard handoff.
13 SF_SERVICE_CONFIGs – Service configuration (service configuration record and non-
14 negotiable service configuration record) for the Serving Frequency.
15 SF_SOFT_SLOPEs – Slope of the handoff add/drop criterion for the Serving Frequency,
17 SF_SRCH_WIN_As – Search window size for the Active Set and Candidate Set used on the
18 Serving Frequency, stored during hard handoff.
19 SF_SRCH_WIN_Ns – Search window size for the Neighbor Set used on the Serving
21 SF_SRCH_WIN_Rs – Search window size for the Remaining Set used on the Serving
23 SF_T_ADDs – Pilot detection threshold used on the Serving Frequency, stored during hard
24 handoff.
25 SF_T_COMPs – Active Set versus Candidate Set comparison threshold used on the Serving
27 SF_T_DROPs – Pilot drop threshold used on the Serving Frequency, stored during hard
28 handoff.
29 SF_T_TDROPs – Pilot drop timer value used on the Serving Frequency, stored during hard
30 handoff.
31 SF_TOTAL_EC_THRESHs – Threshold for total Ec of pilots in the Serving Frequency Active
32 Set used in the Candidate Frequency periodic search procedures.
33 SF_TOTAL_EC_IO_THRESHs – Threshold for total Ec/Io of pilots in the Serving Frequency
34 Active Set used in the Candidate Frequency periodic search procedures.
35 SIDs – System identifier.
36 SID_NID_LISTs – Registration SID, NID list. The SID, NID pairs in which the mobile station
37 has registered.
1-41
3GPP2 C.S0005-A v6.0
1 SLOT_CYCLE_INDEXs – Slot cycle index. Equal to the smaller of SLOT_CYCLE_INDEXp

2 and the received maximum slot cycle index.
3 SLOT_NUM – Paging Channel or Forward Common Control Channel slot number.

4 SOFT_SLOPEs – The slope in the inequality criterion for adding a pilot to the Active Set, or
5 dropping a pilot from the Active Set.
6 SO_REQs – Service option request number. The number of the service option requested by
7 the mobile station during service option negotiation.
8 SR1_BRAT_NON_TDs – Spreading Rate 1 Broadcast data rate with no transmit diversity.
9 SR1_BRAT_TDs – Spreading Rate 1 Broadcast data rate with transmit diversity.
10 SR1_CRAT_NON_TDs – Spreading Rate 1 coding rate with no transmit diversity.
11 SR1_CRAT_TDs – Spreading Rate 1 coding rate with transmit diversity.
12 SR1_TD_MODEs – Spreading Rate 1 transmit diversity mode in support of OTD or STS.
13 SR1_TD_LEVELs – Spreading Rate 1 transmit diversity power level.
14 SR3_BRATs – Data rate of the Broadcast Control Channel on SR3 frequencies.
15 SR3_PRIMARY_PILOTs – Frequency offset of the primary SR3 pilot.
16 SR3_PILOT_POWER1s – The power level of the primary pilot with respect to the pilot on the
17 lower frequency of the two remaining SR3 frequencies.
18 SR3_PILOT_POWER2s – The power level of the primary pilot with respect to the pilot on the
19 higher frequency of the two remaining SR3 frequencies.
20 SRCH_OFFSET_INCLs – Neighbor pilot search window offset included indicator.
21 SRCH_OFFSET_NGHBRs – Neighbor pilot search window offset.
22 SRCH_WIN_As – Search window size for the Active Set and Candidate Set.
23 SRCH_WIN_NGHBRs – Neighbor Pilot Channel search window size.
24 SRCH_WIN_NGHBR_INCLs – Neighbor Pilot Channel search window size included indicator.
25 SRCH_WIN_Ns – Search window size for the Neighbor Set.
26 SRCH_WIN_Rs – Search window size for the Remaining Set.
27 START_TIME_UNITs – A stored variable in the mobile station which contains the time unit
28 used for determining FOR_SCH_START_TIME and REV_SCH_START_TIME on Supplemental
29 Channels.
30 SYS_PAR_MSG_SEQs – System Parameters Message sequence number.
31 SYS_TIMEs – Current value of CDMA system time as received in the Sync Channel
32 Message.
33 TA – Acknowledgment response timeout.

34 T_ADDs – Pilot detection threshold. The stored value is a positive value in units of 0.5 dB.
1-42
3GPP2 C.S0005-A v6.0
1 T_COMPs – Active Set versus Candidate Set comparison threshold. The stored value is a
2 positive value in units of 0.5 dB.
3 T_DROPs – Pilot drop threshold. The stored value is a positive value in units of 0.5 dB.
4 TAGs – Transaction identifier. This is a 4-bit parameter maintained by the mobile station
5 which is used to uniquely identify a new call origination (via an Enhanced Origination
6 Message) by the mobile station. When the mobile station is to send an Enhanced Origination
7 Message, the mobile station increments the stored value of TAG and includes it in the
8 message.
9 TAG_OUTSTANDING_LIST – List of outstanding TAG values. This corresponds to those

10 values of TAG sent in the Enhanced Origination Message which have neither been accepted
11 by the base station (by assigning the requested call) nor rejected by the base station.
12 TEMP_SUBs – User Zone temporary subscription flag.
13 TF_CDMABANDs – Target Frequency CDMA band class. The CDMA band class specified in
14 the Extended Handoff Direction Message or the General Handoff Direction Message.
15 TF_CDMACHs – Target Frequency CDMA Channel number. The CDMA Channel number
16 specified in the Extended Handoff Direction Message or the General Handoff Direction
17 Message.
18 TF_RESET_FPCs – Flag to initialize the Forward Traffic Channel power control counters on
19 the Target Frequency.
20 TF_RESET_L2s – Flag to reset acknowledgment procedures on the Target Frequency.
21 TF_T_ADDs – Pilot detection threshold to be used on the Target Frequency. The stored
22 value is a positive value in units of 0.5 dB.
23 TF_WAIT_TIMEs – Maximum time that the mobile station may wait to receive a period of
24 (N11m × 20) ms with sufficient signal quality (e.g. good frames) on the CDMA Target
25 Frequency.
26 TMSI_ZONEs – TMSI zone number of the base station.
27 TMSI_ZONE_LENs – The number of octets in TMSI zone.
28 T_MULCHANs – A storage variable in the mobile station that contains tThe threshold offset
29 that the mobile station is to use when reporting neighbor pilot strength measurements in a
30 Supplemental Channel Request MessageReverse Supplemental Code Channel neighbor pilot
31 strength measurement offset. The stored value is a positive value in units of 0.5 dB.
32 TOTAL_PUF_PROBESs – Maximum number of PUF probes transmitted in a PUF attempt.
33 TOTAL_ZONESs – Number of registration zones to be retained in ZONE_LISTs.
34 TOT_FRAMESs – Total forward Fundamental Channel frames received. The total number
35 of received forward Fundamental Channel frames, counted for Forward Traffic Channel
36 power control.
37 T_TDROPs – Pilot drop timer value.
1-43
3GPP2 C.S0005-A v6.0
1 USE_FOR_HDM_SEQs – Storage variable containing a flag indicating a pending

2 Supplemental Channel Assignment Message forward assignment that is linked to a General
3 Handoff Direction Message.
4 USE_REV_HDM_SEQs – Storage variable containing a flag indicating a pending
5 Supplemental Channel Assignment Message reverse assignment that is linked to a General
7 USE_T_ADD_ABORTs – A storage variable in the mobile station that contains the Reverse
8 Supplement Code Channel assignment T_ADD abort indicator.
9 USE_TMSIs – Base station’s preference of the use of TMSI.
10 USER_ZONE_IDs – User Zone Identification Message sent indicator.
11 USER_ZONE_ID_MSG_SEQs – User Zone Identification Message sequence number.
12 UZ_EXIT_IN_USEs – The User Zone Exit parameter that the mobile station received from
13 the User Zone Identification Message broadcast by the last base station of the old user zone.
14 UZ_EXIT_RCVDs – The User Zone Exit parameter that the mobile station just received from
15 the User Zone Identification Message broadcast by the currently serving base station.
16 UZIDs – User Zone identifier.
17 UZ_REC – Record containing information about a User Zone broadcast by the base station
18 (see also UZ_REC_LIST).
19 UZ_REC_LIST – Broadcast User Zone record list. A descriptive structure used to manage
20 the base station’s information records about broadcast User Zones (see also UZ_REC).
21 UZ_REVs – User Zone update revision number.
22 VMACs – Analog voice mobile station attenuation code for analog channel assignment or
23 CDMA-to-analog handoff.
24 ZONE_LISTs – Registration zone list. List of zones in which the mobile station has
25 registered.
26 ZONE_TIMERs – Zone timer length.
1-44
3GPP2 C.S0005-A v6.0
1 1.2 Signaling Architecture
2 Layer 3 signaling for cdma2000 is modeled as follows:
3 • Protocol Layer. Layer 3 generates Layer 3 PDUs and passes these PDUs to Lower
4 Layers, where proper encapsulation into Lower Layer PDUs is performed. On the
5 receiving end, Lower Layer PDUs are decapsulated and the resulting SDUs are sent
6 from Lower Layers to Layer 3 for processing.
7 • Service Access Points. SAPs and corresponding communication primitives are

8 defined between the Layer 3 and Lower Layers over the data plane. No SAPs are
9 defined for communications through the control plane.
10 1.3 Signaling and Functionality
11 1.3.1 General Architecture
12 The general architecture is presented in Figure 1.3.1-1.
Layer 3
Signaling
Signaling
Data
Supervision
and
configuration SAP
management
LAC
Signaling
SAP
13
14 Figure 1.3.1-1. cdma2000 Signaling – General Architecture
15 1.3.2 Interface to Layer 2
16 The interface between Layer 3 and Layer 2 is a Service Access Point (SAP). At the SAP,
17 Layer 3 and Layer 2 exchange Service Data Units (SDU) and interface control information in
18 the form of Message Control and Status Blocks (MCSB) using a set of primitives.
19 1.3.2.1 Message Control and Status Block (MCSB)
20 The MCSB is a parameter block for the defined primitives, containing relevant information
21 about an individual Layer 3 message (PDU), as well as instructions on how the message
1-45
3GPP2 C.S0005-A v6.0
1 may be handled or how it is to be (for transmission), or was (for reception), processed by

2 Layer 2. The MCSB is a conceptual construct and is not subject to detailed specification in
3 this document; however, it is envisioned the MCSB will contain information such as:
4 • The MSG_TAG. If the message is generated in response to a previously received

5 message, the MSG_TYPE of the previously received message is also stored.
6 • The length of the PDU.

7 • Page record length parameters, i.e., values of the SDU_INCLUDED field for a Mobile
8 Station-addressed record in a General Page Message, the
9 EXT_MS_SDU_LENGTH_INCL and EXT_MS_SDU_LENGTH fields for a Mobile
10 Station-addressed record in a Universal Page Message, and the
11 EXT_BCAST_SDU_LENGTH_IND and EXT_BCAST_SDU_LENGTH fields for an
12 Enhanced Broadcast record sent in a General Page Message or a Universal Page
13 Message.
14 • A unique instance identifier associated with the message, which enables

15 identification of a message for notifications of delivery/non-delivery or recovery
16 procedures.
17 • Whether the message should be acknowledged at Layer 2 (i.e., delivered in assured

18 mode or unassured mode).
19 • Whether notification of delivery is required.
20 • The identity of the addressee for the message.
21 • Whether the PDU delivered to Layer 3 is a duplicate (in cases where Layer 2 does
22 not discard duplicates).
23 • Data needed by the authentication procedures (e.g., the CHARi fields of the
24 Origination Message).
25 • Relevant PDU classification (e.g., registrations, originations), where processing at

26 Layer 2 is sensitive to the kind of PDU being transferred.
27 • The encryption status of the logical channel.
28 • CDMA System Time corresponding to the frame in which the first or last bit of a
29 message was received.
30 • Transmission instructions for Layer 2, such as an instruction to send a message

31 with a certain priority (before, after, or by interrupting the transmission of other
32 messages), an instruction regarding supervision, and so on.
33 • Abnormal conditions indications from Layer 2.
34 1.3.2.2 Interface Primitives
35 The following primitives are defined for communication between the Layer 3 and Layer 2:
36
37 Name: L2-Data.Request
1-46
3GPP2 C.S0005-A v6.0
1 Type: Request
2 Direction: Layer 3 to Layer 2
3 Parameters: PDU, MCSB
4 Action: The PDU is handed to Layer 2 for delivery across the radio interface.
6 Name: L2-Data.Confirm
7 Type: Confirm
9 Parameters: MCSB
10 Action: Reception of the specified (in the MCSB) transmitted PDU was acknowledged
11 at Layer 2 by the addressee.
12
13 Name: L2-Data.Indication
14 Type: Indication
16 Parameters: PDU, MCSB
17 Action: The received PDU is handed to Layer 3.
18
19 Name: L2-Condition.Notification
20 Type: Indication
22 Parameters: MCSB
23 Action: Layer 3 is notified of a relevant event (e.g. abnormal condition) detected at

24 Layer 2. Details are indicated via the MCSB.
25
26 Name: L2-Supervision.Request
27 Type: Request
29 Parameters: MCSB
30 Action: Layer 2 executes a control command as directed by Layer 3. This could be,
31 for example, an order to abandon retransmission of a message or an order
32 for local reset for the message sequence number, acknowledgment sequence
33 number and duplicate detection.
1-47
3GPP2 C.S0005-A v6.0
1 1.3.3 Reserved
3 1.3.4 Functional Description
4 In the Data Plane, Layer 3 originates and terminates signaling data units according to the
5 semantic and timing of the communication protocol between the base station and the
6 mobile station. From a semantic point of view the signaling data units are referred to as
7 “messages” (or “orders”). From a protocol point of view, the signaling data units are PDUs.
8 In general, the language of this specification does not explicitly distinguish between the
9 terms “PDU” and “Message”. It is considered that the context provides enough information
10 to allow the reader to make the appropriate distinctions.
11 1.3.5 PDU Transmission and Reception
12 Layer 3 employs the services offered at the interface with Layer 2 to transfer PDUs to and
13 from the lLayer 3 entity.
14 When requesting the transmission of a PDU, Layer 3 will typically specify whether the
15 transfer will be performed in assured mode or in unassured mode (for example, by setting
16 the proper parameters in the MCSB argument of the L2-Data.Request primitive). For
17 transmission in assured mode, lLayer 3 may specify if confirmation of delivery of the PDU is
18 required.
19 Layer 2 guarantees that an assured mode PDU received from the transmitting Layer 3
20 entity is delivered to the receiving Layer 3 entity. Each assured mode PDU is delivered to
21 the receiving Layer 3 entity only once and without errors. Additionally, if the transmitting
22 Layer 3 entity requests confirmation of delivery of an assured mode PDU, Layer 2 will send
23 an indication to the transmitting Layer 3 entity (for example by using the L2-Data.Confirm
24 primitive) when Layer 2 receives an acknowledgment for that PDU. If Layer 2 is not able to
25 deliver an assured mode PDU, it sends an indication of the failure to Layer 3 which can
26 then take corrective action.
27 Layer 2 does not guarantee that an unassured mode PDU received from the transmitting
28 Layer 3 entity is delivered to the receiving Layer 3 entity. Thus, Layer 2 acknowledgments
29 may not be required for unassured mode PDUs. To increase the probability of delivery of
30 unassured mode PDUs, Layer 3 may request Layer 2 to send those PDUs multiple times in
31 quick repeat sequence and rely on the duplicate detection capabilities of the receiver to
32 achieve uniqueness of delivery.
33 Layer 3 can also request Layer 2 to perform a reset of the Layer 2 ARQ procedures (for
34 example, by using the L2-Supervision.Request primitive).
1-48
3GPP2 C.S0005-A v6.0
1 2. REQUIREMENTS FOR MOBILE STATION CDMA OPERATION
2 This section defines requirements that are specific to CDMA mobile station equipment and
3 operation. A CDMA mobile station may support operation in one or more band classes.
4 2.1 Reserved
5 2.2 Reserved
6 2.3 Security and Identification
7 2.3.1 Mobile Station Identification Number
8 Mobile stations operating in the CDMA mode are identified by the International Mobile
9 Station Identity (IMSI).1 Mobile Stations shall have two different identifiers, IMSI_T and
10 IMSI_M. The IMSI consists of up to 15 numerical characters (0-9). The first three digits of
11 the IMSI are the Mobile Country Code (MCC), and the remaining digits are the National
12 Mobile Station Identity (NMSI). The NMSI consists of the Mobile Network Code (MNC) and
13 the Mobile Station Identification Number (MSIN). The IMSI structure is shown in Figure
14 2.3.1-1.
15
MCC MNC MSIN
3 digits NMSI
IMSI (≤15 digits)
MCC Mobile Country Code

MNC Mobile Network Code
MSIN Mobile Station Identifier Number
NMSI National Mobile Station Identity
IMSI International Mobil Station Identity
16
17
18 Figure 2.3.1-1. IMSI Structure
19
20 An IMSI that is 15 digits in length is called a class 0 IMSI (the NMSI is 12 digits in length);
21 an IMSI that is less than 15 digits in length is called a class 1 IMSI (the NMSI is less than
22 12 digits in length).
1 See [18]CCITT Blue Book, Volume II-Fascicle II.2, Recommendation E.212, November 1988.
2-1
3GPP2 C.S0005-A v6.0
1 IMSI_M is an IMSI that contains a MIN in the lower ten digits of the NMSI. An IMSI_M can
2 be a class 0 or a class 1 IMSI. If the IMSI_M is not programmed, the mobile station shall
3 set the four least-significant digits of the IMSI_M to the value of the ESNp, converted
4 directly from binary to decimal, modulo 10000, and the mobile station shall set the other
5 digits to 0.
6 IMSI_T is an IMSI that is not associated with the MIN assigned to the mobile station. An
7 IMSI_T can be a class 0 or class 1 IMSI. If the IMSI_T is not programmed, the mobile
8 station shall set the four least-significant digits of the IMSI_T to the value of the ESNp,
9 converted directly from binary to decimal, modulo 10000, and the mobile station shall set
10 the other digits to 0.
11 When operating in the CDMA mode the mobile station shall set its operational IMSI value,
12 IMSI_O, to either the IMSI_M or the IMSI_T depending on the capabilities of the base
13 station (See 2.6.2.2.5).
14 An IMSI_S is a 10-digit (34-bit) number derived from the IMSI. When an IMSI has ten or
15 more digits, IMSI_S is equal to the last ten digits. When an IMSI has fewer than ten digits,
16 the least significant digits of IMSI_S are equal to the IMSI and zeros are added to the most
17 significant side to obtain a total of ten digits. A 10-digit IMSI_S consists of 3- and 7-digit
18 parts, called IMSI_S2 and IMSI_S1, respectively, as illustrated in Figure 2.3.1-2. IMSI_S is
19 mapped into a 34-bit number (see 2.3.1.1). The IMSI_S derived from IMSI_M is designated
20 IMSI_M_S. The IMSI_S derived from IMSI_T is designated IMSI_T_S. The IMSI_S derived
21 from IMSI_O is designated IMSI_O_S.
22 The mobile station shall have memory to store the 34-bit IMSI_M_Sp and the 34-bit
23 IMSI_T_Sp. IMSI_M_Sp is represented by the 10-bit IMSI_M_S2p and the 24 bit
24 IMSI_M_S1p. IMSI_T_Sp is represented by the 10-bit IMSI_T_S2p and the 24 bit
25 IMSI_T_S1p.
26
IMSI_S2 IMSI_S1
First 3 Second 3 Thousands Last 3

IMSI_S Digits Digits Digits Digit Digits
XXX XXX X XXX
Bits 10 10 4 10
27
28
29 Figure 2.3.1-2. IMSI_S Binary Mapping
30
31 When an IMSI has 12 or more digits, IMSI_11_12 is equal to the 11th and 12th digits of the
32 IMSI. When an IMSI has fewer than 12 digits, digits with a value equal to zero are added to
2-2
3GPP2 C.S0005-A v6.0
1 the most significant side to obtain a total of 12 digits and the IMSI_11_12 is equal to the
2 11th and 12th digits of the resulting number.
3 IMSI_11_12 is encoded as described in 2.3.1.2. The mobile station shall have memory to
4 store the 7-bit IMSI_M_11_12p and the 7-bit IMSI_T_11_12p.
5 The 3-digit MCC is encoded as described in 2.3.1.3. The mobile station shall have memory
6 to store the 10-bit MCC_Mp and the 10-bit MCC_Tp.
7 If the mobile station has a class 1 IMSI_T, or IMSI_M, it shall have memory to store
8 IMSI_T_ADDR_NUMp and IMSI_M_ADDR_NUMp. IMSI_T_ADDR_NUMp is equal to the
9 number of digits in the NMSI2 minus four. IMSI_M_ADDR_NUMp is equal to the number of
10 digits in the NMSI of the IMSI_M minus four.
11 2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S
12 The IMSI_M_S and IMSI_T_S binary mapping is defined as follows:
13 1. The first three digits of the IMSI_M_S and the first three digits of the IMSI_T_S are
14 mapped into ten bits (corresponding to IMSI_M_S2p and IMSI_T_S2p, respectively)
15 by the following coding algorithm:
16 a. Represent these three digits as D1 D2 D3 with the digit equal to zero being given
17 the value of ten.
18 b. Compute 100 × D1 + 10 × D2 + D3 - 111.
19 c. Convert the result in step b to binary by the standard decimal-to-binary

20 conversion as shown in Table 2.3.1.1-1.
21
2 It is assumed that the number of digits in NMSI is greater than three.
2-3
3GPP2 C.S0005-A v6.0
1 Table 2.3.1.1-1. Decimal to Binary Conversion Table
Decimal Number Binary Number
0 0000000000
1 0000000001
2 0000000010
3 0000000011
4 0000000100
• •
• •
• •
998 1111100110
999 1111100111
3 2. The second three digits of IMSI_M_S and the second three digits of IMSI_T_S are
4 mapped into the ten most significant bits of IMSI_M_S1p and IMSI_T_S1p,
5 respectively, by the coding algorithm indicated in 1.
6 3. The last four digits of IMSI_M_S and the last four digits of IMSI_T_S are mapped into
7 the 14 least significant bits of IMSI_M_S1p and IMSI_T_S1p, respectively, as follows:
8 a. The thousands digit is mapped into four bits by a Binary-Coded-Decimal (BCD)

9 conversion, as shown in Table 2.3.1.1-2.
10 b. The last three digits are mapped into ten bits by the coding algorithm indicated
11 in 1.
12
2-4
3GPP2 C.S0005-A v6.0
1 Table 2.3.1.1-2. BCD Mapping
Decimal Digit Binary Number
1 0001
2 0010
3 0011
4 0100
5 0101
6 0110
7 0111
8 1000
9 1001
0 1010
3 The following example illustrates the IMSI_T_S2p and IMSI_T_S1p calculation procedure.
4 Let the IMSI_T be the 9-digit number 123456789. Since the IMSI_T has fewer than ten
5 digits, the nine least significant digits of the IMSI_T_S are equal to the IMSI_T digits and the
6 most significant IMSI_T_S digit is set to zero. So the 10-digit IMSI_T_S is 012 345 6 789.
7 IMSI_T_S2p and IMSI_T_S1p are calculated as follows:
8 • IMSI_T_S2p. The ten-bit IMSI_T_S2p is derived from the first three digits of the
9 IMSI_T_S (i.e., 012):
10 a. D1 = 10; D2 = 1; D3 = 2.
11 b. 100 × D1 + 10 × D2 + D3 - 111 = 100 × 10 + 10 × 1 + 2 - 111 = 901.
12 c. 901 in binary is ‘11 1000 0101’.

13 Therefore, IMSI_T_S2p is ‘11 1000 0101’.
14 • IMSI_T_S1p. The ten most significant bits of IMSI_T_S1p are derived from the
15 second three digits of the IMSI_T_S (i.e., 345):
16 a. D1= 3; D2 = 4; D 3 = 5.
17 b. 100 × D1 + 10 × D2 + D3 - 111 = 100 × 3 + 10 × 4 + 5 - 111 = 234.
18 c. 234 in binary is ‘0011 1010 10’.

19 The next four most significant bits of IMSI_T_S1p are derived from the thousands digit of
20 the IMSI_T_S (i.e., 6) by BCD conversion: 6 in BCD is ‘0110’.
21 The ten least significant bits of IMSI_T_S1p are derived from the last three digits of the
22 IMSI_T_S (i.e., 789):
23 a. D1 = 7; D2 = 8; D3 = 9.
24 b. 100 × D1 + 10 × D2 + D3 - 111 = 100 × 7 + 10 × 8 + 9 - 111 = 678.
2-5
3GPP2 C.S0005-A v6.0
1 c. 678 in binary is ‘10 1010 0110’.

2 Therefore, IMSI_T_S1p is ‘0011 1010 1001 1010 1010 0110’.
3 2.3.1.2 Encoding of IMSI_M_11_12 and IMSI_T_11_12
4 The IMSI_M_11_12 and IMSI_T_11_12 binary mapping is defined as follows:

5 1. Represent the 11th digit as D11 and the 12th digit as D12 with the digit equal to
6 zero being given the value of ten.
7 2. Compute 10 × D12 + D11 - 11.
8 3. Convert the result in step 2 to binary by a standard decimal-to-binary conversion as

9 described in Table 2.3.1.1-1 and limit the resulting number to the 7 least significant
10 bits.
11 2.3.1.3 Encoding of the MCC_M and MCC_T
12 The MCC_M and MCC_T binary mapping is defined as follows:

13 1. Represent the 3-digit Mobile Country Code as D1 D2 D3 with the digit equal to zero
14 being given the value of ten.
15 2. Compute 100 × D1 + 10 × D2 + D3 - 111.
16 3. Convert the result in step (2) to binary by a standard decimal-to-binary conversion

17 as described in Table 2.3.1.1-1.
18 2.3.1.4 Mobile Directory Number
19 A Mobile Directory Number (MDN) is a dialable number associated with the mobile station
20 through a service subscription. A Mobile Directory Number is not necessarily the same as
21 the mobile station identification on the air interface, i.e., MIN, IMSI_M or IMSI_T. An MDN
22 consists of up to 15 digits. The mobile station should have memory to store at least one
23 Mobile Directory Number (see Table F.3-1).
24 2.3.2 Electronic Serial Number
25 The ESN is a 32-bit binary number that uniquely identifies the mobile station to any
26 wireless system. The ESN value is available to procedures in the mobile station as the
27 value of the variable ESNp. The value of the variable RN_HASH_KEYs is the same as the
28 value of the variable ESNp, and need not be stored separately.
29 2.3.3 Station Class Mark

30 Class-of-station information referred to as the station class mark (SCMp) must be stored in
31 a mobile station. The digital representation of this class mark is specified in Table 2.3.3-1.
32
2-6
3GPP2 C.S0005-A v6.0
1 Table 2.3.3-1. Station Class Mark
Function Bit(s) Setting
Extended SCM Indicator 7 Band Classes 1,4 1XXXXXXX

Other bands
0XXXXXXX
Dual Mode 6 CDMA Only X0XXXXXX
Dual Mode X1XXXXXX
Slotted Class 5 Non-Slotted XX0XXXXX
Slotted XX1XXXXX
IS-54 Power Class 4 Always 0 XXX0XXXX
25 MHz Bandwidth 3 Always 1 XXXX1XXX
Transmission 2 Continuous XXXXX0XX
Discontinuous XXXXX1XX
Power Class for Band 1-0 Class I XXXXXX00
Class 0 Analog Operation Class II XXXXXX01
Class III XXXXXX10
Reserved XXXXXX11
3 If the mobile station supports analog mode operation in Band Class 0, the mobile station
4 shall set the Power Class function bits to reflect its analog power class at Band Class 0,
5 regardless of the band class in which it is operating; otherwise, the mobile station shall set
6 these bits to ‘00’.
7 2.3.4 Registration Memory
8 The mobile station shall have memory to store one element in the zone-based registration
9 list ZONE_LISTs-p (see 2.6.5.1.5 and 2.6.5.5). This stored element shall include both
10 REG_ZONE and the corresponding (SID, NID) pair. The data retention time under power-off
11 conditions shall be at least 48 hours. If, after 48 hours, the data integrity cannot be
12 guaranteed, then the entry in ZONE_LISTs-p shall be deleted upon power-on.
13 The mobile station shall have memory to store one element in the system/network
14 registration list SID_NID_LISTs-p (see 2.6.5.1.5 and 2.6.5.5). The data retention time under
15 power-off conditions shall be at least 48 hours. If, after 48 hours, the data integrity cannot
16 be guaranteed, then the entry in SID_NID_LISTs-p shall be deleted upon power-on.
17 The mobile station shall have memory to store the distance-based registration variables
18 BASE_LAT_REGs-p, BASE_LONG_REGs-p, and REG_DIST_REGs-p (see 2.6.5.1.4 and
19 2.6.5.5). The data retention time under power-off conditions shall be at least 48 hours. If,
20 after 48 hours, the data integrity cannot be guaranteed, then REG_DIST_REGs-p shall be
21 set to zero upon power-on.
2-7
3GPP2 C.S0005-A v6.0
1 2.3.5 Access Overload Class

2 The 4-bit access overload class indicator (ACCOLCp) is used to identify which overload class
3 controls access attempts by the mobile station and is used to identify redirected overload
4 classes in global service redirection.
5 The mobile station shall store 4-bit access overload class (ACCOLCp). Mobile stations that
6 are not for test or emergency use should be assigned to overload classes ACCOLC 0 through
7 ACCOLC 9. For mobile stations that are classified as overload classes ACCOLC 0 through
8 ACCOLC 9, the mobile station’s 4-bit access overload class indicator (ACCOLCp) shall be
9 automatically derived from the last digit of the associated decimal representation of the
10 IMSI_M by a decimal to binary conversion as specified in Table 2.3.5-1. When a mobile
11 station’s IMSI_M is updated, the mobile station shall re-calculate the ACCOLCp as indicated
12 above. Mobile stations designated for test use should be assigned to ACCOLC 10; mobile
13 stations designated for emergency use should be assigned to ACCOLC 11. ACCOLC 12
14 through ACCOLC 15 are reserved.3 Programming the 4-bit ACCOLCp for overload classes
15 ACCOLC 10 through ACCOLC 15 as specified in Table 2.3.5-2 shall require a special facility
16 only available to equipment manufacturers and system operators.
17 The content of ACCOLCp shall not be visible through the mobile station’s display.
18
19 Table 2.3.5-1. ACCOLCp Mapping for ACCOLC 0 through ACCOLC 9
Last Digit of the Decimal

Representation of the ACCOLCp
IMSI
(binary)
0 0000
1 0001
2 0010
3 0011
4 0100
5 0101
6 0110
7 0111
8 1000
9 1001
20
3 For more information, refer to [28].
2-8
3GPP2 C.S0005-A v6.0
1 Table 2.3.5-2. ACCOLCp Mapping for ACCOLC 10 through ACCOLC 15
Overload Class ACCOLCp

(binary)
10 1010
11 1011
12 1100
13 1101
14 1110
15 1111
3 2.3.6 Public Long Code Mask
4 The Public Long Code Mask consists of 42 bits (see [2]). The 37 least significant bits
5 (PLCM_37) are set as follows:
6 Bits M36 through M32 shall be set to ‘11000’; bits M31 through M0 shall be set to a
7 permutation of the mobile station’s ESN as follows:
8 ESN = (E31, E30, E29, E28, E27, E26, E25, . . . E2, E1, E0)
9 Permuted ESN = (E0, E31, E22, E13, E4, E26, E17, E8, E30, E21, E12, E3, E25, E16,
10 E7, E29, E20, E11, E2, E24, E15, E6, E28, E19, E10, E1, E23, E14,
11 E5, E27, E18, E9).
12 2.3.7 Reserved
13 2.3.8 Home System and Network Identification

14 In addition to the HOME_SIDp parameter that the mobile station stores for 800 MHz analog
15 operation, the mobile station shall provide memory to store at least one home (SIDp, NIDp)
16 pair. The mobile station shall also provide memory to store the 1-bit parameters
17 MOB_TERM_HOMEp, MOB_TERM_FOR_SIDp, and MOB_TERM_FOR_NIDp (see 2.6.5.3).
18 2.3.9 Local Control Option
19 If the mobile station supports the local control option, a means shall be provided within the
20 mobile station to enable or disable the local control option.
21 2.3.10 Preferred Operation Selection
22 2.3.10.1 Preferred System
23 If the mobile station supports operation in Band Class 0 or Band Class 3 (see [2]), a means
24 shall be provided within the mobile station to identify the preferred system. In addition, the
25 mobile station may provide a means for allowing operation only with System A or only with
26 System B.
2-9
3GPP2 C.S0005-A v6.0
1 2.3.10.2 Preferred CDMA or Analog
2 If the mobile station supports operation in Band Class 0 (see [2]), a means may be provided
3 within the mobile station to identify the preferred operation type as either CDMA mode or
4 analog mode. In addition, the mobile station may provide a means for allowing operation
5 only in the preferred mode.
6 2.3.11 Discontinuous Reception
7 The mobile station shall provide memory to store the preferred slot cycle index,
8 SLOT_CYCLE_INDEXp (see 2.6.2.1.1.3.2).
9 2.3.12 Authentication, Encryption of Signaling Information/User Data and Voice Privacy
10 2.3.12.1 Authentication
11 Authentication is the process by which information is exchanged between a mobile station

12 and base station for the purpose of confirming the identity of the mobile station. A
13 successful outcome of the authentication process occurs only when it can be demonstrated
14 that the mobile station and base station possess identical sets of shared secret data.
15 The authentication algorithms are described in [15]. The interface (input and output
16 parameters) for the algorithms is described in [23], Table 2.3.12.1-1 summarizes the
17 setting of the input parameters of the Auth_Signature procedure for each of its uses in this
18 standard.
19 For authentication purposes, the mobile station shall use IMSI_M if it is programmed;
20 otherwise, the mobile station shall use IMSI_T. The base station uses the IMSI selected
21 according to the same criteria.
22
23 Table 2.3.12.1-1. Auth_Signature Input Parameters
AUTH_ SSD_ SAVE_

Procedure RAND_CHALLENGE ESN
DATA AUTH REGISTERS
Unique RANDU and 8 LSBs ESNp IMSI_S1 SSD_A FALSE

Challenge of IMSI_S2
(2.3.12.1.4)
Base Station RANDBS ESNp IMSI_S1 SSD_A FALSE
Challenge _ NEW
(2.3.12.1.5)
24
25 2.3.12.1.1 Shared Secret Data (SSD)
26 SSD is a 128-bit quantity that is stored in semi-permanent memory in the mobile station
27 and is readily available to the base station. As depicted in Figure 2.3.12.1.1-1, SSD is
28 partitioned into two distinct subsets. Each subset is used to support a different process.
29
2-10
3GPP2 C.S0005-A v6.0
Contents SSD_A SSD_B
Length (bits) 64 64
1 Figure 2.3.12.1.1-1. Partitioning of SSD
3 SSD_A is used to support the authentication procedures and SSD_B is used to support
4 voice privacy (see 2.3.12.3) and message encryption (see 2.3.12.2). SSD is generated
5 according to the procedure specified in 2.3.12.1.5. The SSD shall not be accessible to the
6 user.
7 2.3.12.1.2 Random Challenge Memory (RAND)
8 RAND is a 32-bit value held in the mobile station. When operating in CDMA mode, it is
9 equal to the RAND value received in the last Access Parameters Message (see 3.7.2.3.2.2) or
10 the ANSI-41 RAND Message (see 3.7.2.3.2.31) of the CDMA f-csch.
11 RANDs is used in conjunction with SSD_A and other parameters, as appropriate, to
12 authenticate mobile station originations, terminations and registrations.
13 2.3.12.1.3 Call History Parameter (COUNTs-p)
14 COUNTs-p is a modulo-64 count held in the mobile station. COUNTs-p is updated by the
15 mobile station when a Parameter Update Order is received on the f-dsch (see 3.7.4).
16 2.3.12.1.4 Unique Challenge-Response Procedure
17 The Unique Challenge-Response Procedure is initiated by the base station and can be
18 carried out either on the f-csch and r-csch, or on the f-dsch and r-dsch. The procedure is
19 as follows:
20 The base station generates the 24-bit quantity RANDU and sends it to the mobile station in
21 the Authentication Challenge Message on either the f-csch or f-dsch. Upon receipt of the
22 Authentication Challenge Message, the mobile station shall set the input parameters of the
23 Auth_Signature procedure (see [23] section 2.3) as illustrated in Figure 2.3.12.1.5-3. The
24 24 most significant bits of the RAND_CHALLENGE input parameter shall be filled with
25 RANDU, and the 8 least significant bits of RAND_CHALLENGE shall be filled with the 8
26 least significant bits of IMSI_S2.
27 The mobile station shall set the SAVE_REGISTERS input parameter to FALSE.
28 The mobile station shall then execute the Auth_Signature procedure. The 18-bit output
29 AUTH_SIGNATURE shall be used to fill the AUTHU field of the Authentication Challenge
30 Response Message, which shall be sent to the base station.
31 The base station computes the value of AUTHU in the same manner as the mobile station,
32 but using its internally stored value of SSD_A. The base station compares its computed
33 value of AUTHU to the value received from the mobile station. If the comparison fails, the
34 base station may deny further access attempts by the mobile station, drop the call in
35 progress, or initiate the process of updating SSD (see 2.3.12.1.5).
2-11
3GPP2 C.S0005-A v6.0
1 2.3.12.1.5 Updating the Shared Secret Data (SSD)
2 SSD is updated using the SSD_Generation procedure (see [23], section 2.2.1), initialized
3 with mobile station specific information, random data, and the mobile station’s A-key. The
4 A-key is 64 bits long. It is assigned to the mobile station and is stored in the mobile
5 station’s permanent security and identification memory. The A-key is known only to the
6 mobile station and to its associated Home Location Register/Authentication Center
7 (HLR/AC) (see [13]). Non-manual methods, such as described in [26], are preferred for
8 entry of the A-key into the mobile station. A manual method of entry that may be used
9 when automated methods are not available is described in [29].
10 The SSD update procedure is performed as follows (see Figure 2.3.12.1.5-1):
11 The base station sends an SSD Update Message on either the f-csch or the f-dsch. The
12 RANDSSD field of the SSD Update Message contains the same value used for the HLR/AC
13 computation of SSD.
14 Upon receipt of the SSD Update Message the mobile station shall set the input parameters
15 of the SSD_Generation procedure (see [23], section 2.2.1) as illustrated in Figure 2.3.12.1.5-
16 2. The mobile station shall then execute the SSD_Generation procedure. The mobile
17 station shall set SSD_A_NEW and SSD_B_NEW to the outputs of the SSD_Generation
18 procedure.
19 The mobile station shall then select a 32-bit random number, RANDBS, and shall send it to
20 the base station in a Base Station Challenge Order on the r-csch or r-dsch.
21 Both the mobile station and the base station shall then set the input parameters of the
22 Auth_Signature procedure (see [23], section 2.3) as illustrated in Figure 2.3.12.1.5-3 and
23 shall execute the Auth_Signature procedure.
24 The mobile station and base station shall set the SAVE_REGISTERS input parameter to
25 FALSE.
26 The mobile station and base station shall execute the Auth_Signature procedure. AUTHBS
27 is set to the 18-bit result AUTH_SIGNATURE. The base station sends its computed value of
28 AUTHBS to the mobile station in a Base Station Challenge Confirmation Order on the f-csch
29 or the f-dsch.
30 Upon receipt of the Base Station Challenge Confirmation Order the mobile station shall
31 compare the received value of AUTHBS to its internally computed value. (If the mobile
32 station receives a Base Station Challenge Confirmation Order when an SSD update is not in
33 progress, the mobile station shall respond with an SSD Update Rejection Order.)
34 If the comparison is successful, the mobile station shall execute the SSD_Update procedure
35 (see [23], section 2.2.2) to set SSD_A and SSD_B to SSD_A_NEW and SSD_B_NEW,
36 respectively. The mobile station shall then send an SSD Update Confirmation Order to the
37 base station, indicating successful completion of the SSD update.
38 If the comparison is not successful, the mobile station shall discard SSD_A_NEW and
39 SSD_B_NEW. The mobile station shall then send an SSD Update Rejection Order to the base
40 station, indicating unsuccessful completion of the SSD update.
2-12
3GPP2 C.S0005-A v6.0
1 Upon receipt of the SSD Update Confirmation Order, the base station sets SSD_A and SSD_B
2 to the values received from the HLR/AC (see [13]).
3 If the mobile station fails to receive the Base Station Challenge Confirmation Order within
4 T64m seconds of when the acknowledgment to the Base Station Challenge Order was
5 received, the mobile station shall discard SSD_A_NEW and SSD_B_NEW. The mobile
6 station shall then terminate the SSD update process.
MOBILE STATION BASE STATION
SSD Update Message

(RANDSSD)
RANDSSD A-key RANDSSD A-key
SSD_Generation SSD_Generation
Procedure Procedure
SSD_B_NEW SSD_B_NEW
SSD_A_NEW
SSD_A_NEW Base Station Challenge Order
RANDBS
(RANDBS)
Auth_Signature Auth_Signature
Procedure Procedure
AUTHBS
AUTHBS
=
AUTHBS? (AUTHBS)
SSD Update Confirmation Order (success)

SSD Update Rejection Order (failure)
8
9 Figure 2.3.12.1.5-1. SSD Update Message Flow
2-13
3GPP2 C.S0005-A v6.0
RANDSSD ESN
RANDSSD ESN A-key
56 32 64
SSD_Generation
Procedure
SSD_A_NEW SSD_B_NEW
64 64
1
2 Figure 2.3.12.1.5-2. Computation of Shared Secret Data (SSD)
RAND_CHALLENGE ESN AUTH_DATA SSD_AUTH
RANDBS ESN IMSI_S1 SSD_A_NEW

32 32 24 64
Auth_Signature
Procedure
AUTH_SIGNATURE
AUTHBS
18
6
7
8 Figure 2.3.12.1.5-3. Computation of AUTHBS
2-14
3GPP2 C.S0005-A v6.0
1 2.3.12.2 Signaling Message Encryption
2 In an effort to enhance the authentication process and to protect sensitive subscriber

3 information (such as PINs), a method is provided to encrypt certain fields of selected f-dsch
4 or r-dsch signaling messages.
5 The following is a description of the messages on f-dsch (See see 2.3.12.2.1) and r-dsch (see
6 2.3.12.2.2) that are enciphered using the Cellular Message Encryption Algorithm (see
7 section 2.5.1, [15]) or the Enhanced Cellular Message Encryption Algorithm (see section
8 2.5.2, [15]), and when ENCRYPT_MODEs is set to ‘01’ or ‘10’. The availability of encryption
9 algorithm information is under government control.
10 For each message, the enciphered fields are identified. The messages are grouped by
11 channel designation.
12 Messages shall not be encrypted if authentication is not performed (AUTHs is set to ‘00’).
13 See [23] for details of the initialization and use of the encryption procedure.
14 Signaling message encryption is controlled for each call individually. If PREV_IN_USE is

15 less than or equal to six, the mobile station identifies its encryption capability in the
16 ENCRYPTION_SUPPORTED field in the Origination Message and the Page Response Message
17 as shown in Table 2.7.1.3.2.4-5. If PREV_IN_USE is greater than or equal to seven, the
18 mobile station identifies its encryption capability in the SIG_ENCRYPT_SUP field in
19 Registration Message, Origination Message, Page Response Message, Security Mode Request
20 Message, and the encryption capability information record in Status Response Message and
21 Extended Status Response Message, as shown in Table 2.7.1.3.2.1-5. The initial encryption
22 mode for the call is established by setting the ENCRYPT_MODE field to ‘00’, ‘01’, or ‘10’ in
23 the Channel Assignment Message or in the Extended Channel Assignment Message. If
24 ENCRYPT_MODE is set to ‘00’, message encryption is off. To turn encryption on after
25 channel assignment, the base station sends one of the following f-dsch messages to the
26 mobile station:
27 • Extended Handoff Direction Message with the ENCRYPT_MODE field set to ‘01’ or
28 ‘10’
29 • General Handoff Direction Message with the ENCRYPT_MODE field set to ‘01’ or ‘10’
30 • Universal Handoff Direction Message with the ENCRYPT_MODE field set to ‘01’ or
31 ‘10’
32 • Analog Handoff Direction Message with the MEM field set to ‘1’
33 • Message Encryption Mode Order with the ENCRYPT_MODE field set to ‘01’ or ‘10’
34 To turn signaling message encryption off, the base station sends one of the following f-dsch
35 messages to the mobile station:
36 • Extended Handoff Direction Message with the ENCRYPT_MODE field set to ‘00’
37 • General Handoff Direction Message with the ENCRYPT_MODE field set to ‘00’
38 • Universal Handoff Direction Message with the ENCRYPT_MODE field set to ‘00’
2-15
3GPP2 C.S0005-A v6.0
1 • Analog Handoff Direction Message with the MEM field set to ‘0’
2 • Message Encryption Mode Order with the ENCRYPT_MODE field set to ‘00’
3 Encryption shall apply only to the part of the Layer 3 message specified below.
4 When encryption is off, all fields of all Layer 3 messages sent by the mobile station and base
5 station are unencrypted.
6 When additional octets are inserted, the overall Lower Layers message length is updated to
7 reflect the addition. Specific Layer 3 record length fields (e.g., RECORD_LEN,
8 NUM_FIELDS, or NUM_DIGITS) shall not be affected by the insertion of additional bits.
9 If the Enhanced Cellular Message Encryption Algorithm is used, the following requirements
10 apply:
11 • The mobile station and base station shall each maintain an 8-bit encryption
12 sequence counter. The encryption sequence counter shall be incremented modulo
13 256 for each new encryption. The counter value, hereafter called ES_COUNT, shall
14 be used to form the SYNC parameter of the Enhanced Cellular Message Encryption
15 Algorithm as described below.
16 • As part of each encryption, an additional octet of value ES_COUNT shall be inserted

17 immediately following the encrypted part of the message. This additional octet shall
18 not be encrypted. The additional octet shall be removed from the message after
19 decryption.
20 2.3.12.2.1 Encrypted Messages on the f-dsch

21 When encryption is on (ENCRYPT_MODEs equal to binary ‘01’ or ‘10’), the encryptable fields
22 of the following messages sent on f-dsch, as listed below, shall be encrypted. All other
23 messages sent on f-dsch shall be unencrypted.
24 1. Alert With Information Message (see 3.7.3.3.2.3) and Extended Alert With Information
25 Message (see 3.7.3.3.2.42) are encrypted.
26 The type-specific fields of all information records (see 3.7.5) shall be encrypted. For each
27 information record, the type-specific fields shall be treated by the encryption procedure
28 as a new single message. If the type-specific fields of an information record consist of a
29 single octet (RECORD_LEN field equal to 1), an additional octet of value ‘00000000’ shall
30 be inserted following the information record and shall be encrypted as if part of the
31 record. (If the RECORD_LEN field is 0, the information record contains no type-specific
32 fields, and the record contains no encrypted data.)
33 No other fields in the Alert With Information Message and Extended Alert With
34 Information Message are encrypted.
35 If the Enhanced Cellular Message Encryption Algorithm is used (ENCRYPT_MODEs
36 equal to binary ‘10’), the following requirements apply for each information record:
37 • The DATA_TYPE parameter shall be set to ‘0’.
38 • The SYNC parameter shall be set as follows:
2-16
3GPP2 C.S0005-A v6.0
1 – SYNC[0] = ES_COUNT
2 – SYNC[1] = RECORD_TYPE
3 2. Flash With Information Message (see 3.7.3.3.2.14) and Extended Flash With
4 Information Message (see 3.7.3.3.2.43) are encrypted.
12 No other fields in the Flash With Information Message and Extended Flash With

20 3. Send Burst DTMF Message (see 3.7.3.3.2.9) is encrypted.
21 The DIGITi fields of the Send Burst DTMF Message shall be encrypted. These fields are
22 treated by the encryption procedure as a new single message, with the 4-bit digit codes
23 packed into consecutive octets. If the NUM_DIGITS field contains an odd number, four
24 bits of value ‘0000’ shall follow the last digit and shall be included in the encrypted
25 message. If NUM_DIGITS is less than 3, an additional eight bits of value ‘00000000’
26 shall follow the DIGITi fields and shall be included in the encrypted part of the message.
28 equal to binary ‘10’), the following requirements apply:
32 – SYNC[1] = MSG_TYPE = ‘00001001’

33 4. Continuous DTMF Tone Order (see 3.7.3.3.2.1) is encrypted.
34 The 16 bits comprised of ADD_RECORD_LEN, the order-specific fields and the first five
35 (5) bits of the RESERVED field shall be encrypted. These fields shall be treated by the
36 encryption procedure as a new single message.
2-17
3GPP2 C.S0005-A v6.0
5 – SYNC[1] = MSG_TYPE = ‘00000001’
6 5. Data Burst Message (see 3.7.3.3.2.4) is encrypted.
7 If BURST_TYPE is equal to ‘111110’ or ‘111111’, all CHARi fields after the first two shall
8 be encrypted; otherwise, all CHARi fields shall be encrypted.
9 If the CHARi field consists of a single octet (NUM_FIELDS field equal to 1), an
10 additional octet of value ‘00000000’ shall be inserted following the information record
11 and shall be encrypted as if part of the record. (If the NUM_FIELDS field is 0, the
12 information record contains no type-specific fields, and the record contains no
13 encrypted data).
14 If the Cellular Message Encryption Algorithm is used (ENCRYPT_MODEs equal to binary
15 ‘01’), the following requirements apply:
16 • If BURST_TYPE is equal to ‘000011’ (SMS) or ‘000100’ (OTASP), the message

17 shall be encrypted.
18 • For all other values of BURST_TYPE, the message shall be encrypted only if
19 encryption is required by the service option standard governing use of the Data
20 Burst Message; otherwise, the message shall not be encrypted.
23 • If BURST_TYPE is equal to ‘000100’ (OTASP), the DATA_TYPE parameter shall be

24 set to ‘0’. Otherwise, the DATA_TYPE parameter shall be set to ‘1’.
27 – SYNC[1] = MSG_TYPE = ‘00000100’
28 6. Power Up Function Completion Message (see 3.7.3.3.2.30) is encrypted.
29 If the LOC_IND field is set to ‘1’, the fields RESERVED (3 bits), MS_LAT (22 bits),
30 MS_LONG (23 bits), and MS_LOC_TSTAMP (24 bits) are encrypted. These fields shall be
31 treated by the encryption procedure as a new single message.
32 Otherwise, if the LOC_IND field is set to ‘0’, no fields in this message are encrypted.

2-18
3GPP2 C.S0005-A v6.0
2 – SYNC[1] = MSG_TYPE = ‘00011110’
3 2.3.12.2.2 Encrypted Messages on the r-dsch

4 When encryption is on (ENCRYPT_MODEs equal to binary ‘01’ or ‘10’) the encryptable fields
5 of the following r-dsch lLayer 3 messages, as listed below, shall be encrypted. All other r-
6 dsch messages shall be unencrypted.
7 1. Origination Continuation Message (see 2.7.2.3.2.9) and Enhanced Origination Message

8 are encrypted.
9 The CHARi fields of the Origination Continuation Message and Enhanced Origination
10 Message shall be encrypted. These fields shall be treated by the encryption procedure
11 as a new single message, with the character codes packed into consecutive octets. If
12 DIGIT_MODE is ‘0’ and the NUM_FIELDS field contains an odd number, four bits of
13 value ‘0000’ shall follow the last digit and shall be included in the encrypted part of the
14 message. In addition, if ENCRYPT_MODEs is equal to ‘01’, the following requirement
15 applies
16 • If DIGIT_MODE is ‘0’ and NUM_FIELDS is less than 3, or if DIGIT_MODE is ‘1’

17 and NUM_FIELDS is less than 2, an additional eight bits of value ‘00000000’
18 shall follow the CHARi fields and shall be included in the encrypted part of the
19 message.
25 – SYNC[1] = MSG_TYPE = ‘00001001’ for Origination Continuation Message
26 – SYNC[1] = MSG_TYPE = ‘00011010’ for Enhanced Origination Message
27 The type-specific fields of all information records (see 2.7.4) in the Origination
28 Continuation Message and Enhanced Origination Message shall be encrypted. For each
2-19
3GPP2 C.S0005-A v6.0
3 2. Flash With Information Message (see 2.7.2.3.2.3) and Extended Flash With Information
4 Message (see 2.7.2.3.2.32) are encrypted.
12 No other fields in the Flash With Information Message and Extended Flash With
20 3. Send Burst DTMF Message (see 2.7.2.3.2.7) is encrypted.
21 The DIGITi fields of the Send Burst DTMF Message shall be encrypted. These fields shall
22 be treated by the encryption procedure as a new single message, with the 4-bit digit
23 codes packed into consecutive octets. If the NUM_DIGITS field contains an odd
24 number, four bits of value ‘0000’ shall follow the last digit and shall be included in the
25 encrypted message. If NUM_DIGITS is less than 3, an additional eight bits of value
26 ‘00000000’ shall follow the DIGITi fields and shall be included in the encrypted part of
27 the message.
33 – SYNC[1] = MSG_TYPE = ‘00000111’
34 4. Continuous DTMF Tone Order (see 2.7.2.3.2.1) is encrypted.
35 The 16 bits comprised of ADD_RECORD_LEN, the order-specific fields and the first five
36 (5) bits of the RESERVED field shall be encrypted. These fields shall be treated by the
37 encryption procedure as a new single message.
2-20
3GPP2 C.S0005-A v6.0
5 – SYNC[1] = MSG_TYPE = ‘00000001’
6 5. Data Burst Message (see 2.7.2.3.2.4) is encrypted.
7 If BURST_TYPE is equal to ‘111110’ or ‘111111’, all CHARi fields after the first two shall
8 be encrypted; otherwise, all CHARi fields shall be encrypted.
9 If the CHARi field consists of a single octet (NUM_FIELDS field equal to 1), an
10 additional octet of value ‘00000000’ shall be inserted following the information record
11 and shall be encrypted as if part of the record. (If the NUM_FIELDS field is 0, the
12 information record contains no type-specific fields, and the record contains no
13 encrypted data).
14 If the Cellular Message Encryption Algorithm is used (ENCRYPT_MODEs equal to binary
15 ‘01’), the following requirements apply:
16 • If BURST_TYPE is equal to ‘000011’ (SMS) or ‘000100’ (OTASP), the message

17 shall be encrypted.
18 • For all other values of BURST_TYPE, the message shall be encrypted only if
19 encryption is required by the service option standard governing use of the Data
20 Burst Message; otherwise, the message shall not be encrypted.
23 • If BURST_TYPE is equal to ‘000100’ (OTASP), the DATA_TYPE parameter shall be

24 set to ‘0’. Otherwise, the DATA_TYPE parameter shall be set to ‘1’.
27 – SYNC[1] = MSG_TYPE = ‘00000100’
28 2.3.12.3 Voice Privacy
29 Also see [2].
30 Voice privacy is provided in the CDMA system by means of the private long code mask used
31 for PN spreading.
32 Voice privacy is provided on the Traffic Channels only. All calls are initiated using the
33 public long code mask for PN spreading. The mobile station user may request voice privacy
34 during call setup using the Origination Message or Page Response Message, and during
35 Traffic Channel operation using the Long Code Transition Request Order.
36 The transition to private long code mask shall not be performed if authentication is not
37 performed (AUTHs is set to ‘00’ or mobile station unable to perform authentication).
2-21
3GPP2 C.S0005-A v6.0
1 To initiate a transition to the private or public long code mask, either the base station or
2 the mobile station sends a Long Code Transition Request Order on the f-dsch or r-dsch. The
3 mobile station actions in response to receipt of this order are specified in 2.6.4, and the
4 base station actions in response to receipt of this order are specified in 3.6.4.
5 The base station can also cause a transition to the private or public long code mask by
6 sending the Extended Handoff Direction Message, the General Handoff Direction Message, or
7 the Universal Handoff Direction Message with the PRIVATE_LCM bit set appropriately.
8 2.3.12.4 Extended Encryption for Signaling Message and User Information
9 In an effort to enhance the authentication process and to protect sensitive subscriber

10 information (such as PINs), a method is provided to encrypt selected f-dsch, r-dsch, f-csch,
11 or r-csch Layer 3 signaling PDUs.
12 The availability of encryption algorithm information is under government control.
13 Extended encryption is an encryption framework used for encrypting/decrypting both

14 signaling messages and user information on f/r-dsch or f/r-csch. Signaling message and
15 user information encryption algorithms can be negotiated independently. Signaling message
16 and user information encryption can be turned on or off independently.
17 Signaling mMessages or user information shall not be encrypted if authentication is not

18 performed (i.e., when AUTHs is set to ‘00’. See 2.3.12.1). See [23] for details of the
19 initialization and use of the encryption procedure.
20 2.3.12.4.1 Extended Encryption for Signaling Messages
21 Signaling mMessages with zero length shall be sent un-encrypted, in which case Layer 3
22 shall indicate to LAC layer that the messages are sent un-encrypted, and the following
23 encryption/decryption procedures shall not be performed on the messages.
24 All mini messages shall be sent un-encrypted., in which case the following
25 encryption/decryption procedures shall not be performed on the messages.
26 When sending a Registration Accepted Order, Security Mode Command Message, or Base
27 Station Reject Order, the base station should use assured mode.
28 The initial encryption mode for the call is established by setting one of the following in the
29 Channel Assignment Message, Extended Channel Assignment Message, Registration Accepted
30 Order, or Security Mode Command Message.
31 • ENCRYPT_MODE field is set to ‘00’; or
32 • ENCRYPT_MODE field is set to ‘11’ and the SIG_ENCRYPT_MODE field is set to ‘000’
33 or ‘001’.
34 If the ENCRYPT_MODE field is set to ‘00’, or if the ENCRYPT_MODE field is set to ‘11’ and
35 the SIG_ENCRYPT_MODE field is set to ‘000’, message encryption is off. To turn encryption
36 on after channel assignment, the base station sends one of the following f-dsch messages to
37 the mobile station:
2-22
3GPP2 C.S0005-A v6.0
1 • General Handoff Direction Message with the ENCRYPT_MODE field set to ‘11’ and
2 the SIG_ENCRYPT_MODE field set to ‘001’.
3 • Universal Handoff Direction Message with the ENCRYPT_MODE field set to ‘11’ and
4 the SIG_ENCRYPT_MODE field set to ‘001’.
5 • Security Mode Command Message with the ENCRYPT_MODE field set to ‘11’ and the
6 SIG_ENCRYPT_MODE field set to ‘001’.
7 To turn signaling message encryption off, the base station sends one of the following f-dsch
8 messages to the mobile station:
9 • General Handoff Direction Message with the ENCRYPT_MODE field set to ‘00’, or the
10 ENCRYPT_MODE field set to ‘11’ and the SIG_ENCRYPT_MODE field set to ‘000’.
11 • Universal Handoff Direction Message with the ENCRYPT_MODE field set to ‘00’, or
12 the ENCRYPT_MODE field set to ‘11’ and the SIG_ENCRYPT_MODE field set to ‘000’.
13 • Security Mode Command Message with the ENCRYPT_MODE field set to ‘00’, or the
14 ENCRYPT_MODE field set to ‘11’ and the SIG_ENCRYPT_MODE field set to ‘000’.
15 2.3.12.4.1.1 Extended Encryption for Signaling on f/r-csch
16 To turn f/r-csch signaling encryption on or off, the base station sends a Registration
17 Accepted Order or Security Mode Command Message on f-csch, with the
18 C_SIG_ENCRYPT_MODE field set to one of the values specified in Table 3.7.4.5-1. The value
19 of C_SIG_ENCRYPT_MODEr is then stored in C_SIG_ENCRYPT_MODEs.
20 If C_SIG_ENCRYPT_MODEs is not equal to ‘000’ and ENC_KEYs is not equal to NULL, all
21 f/r-csch signaling messages shall be encrypted based on the value of
22 C_SIG_ENCRYPT_MODEs using the procedures specified in 2.3.12.4.1.3; except for the
23 exceptions listed below in the rest of this section.
24 If the mobile station sends an encrypted Registration Message, Origination Message, or Page
25 Response Message, and receives a layer 2 acknowledgement from the base station, but does
26 not receive any Layer 3 message from the base station that the mobile station could decrypt
27 successfully thereafter, then the mobile station should resend the same message un-
28 encrypted.
29 On the f-csch, General Page Message, Universal Page Message, Registration Request Order,
30 Authentication Challenge Message, and Registration Accepted Order shall be sent un-
31 encrypted. Channel Assignment Message, Extended Channel Assignment Message, and
32 Security Mode Command Message may be sent un-encrypted. All overhead messages and all
33 signaling messages with a broadcast address type shall be sent un-encrypted.
34 On the r-csch, Registration Message, Page Response Message, Authentication Challenge

35 Response Message, and Security Mode Request Message shall be sent un-encrypted. When
36 sending an Origination Message, if all of the following conditions are true, the mobile station
37 shall not include the dialed digits in the Origination Message, and the mobile station shall
38 include the dialed digits in the Origination Continuation Message:
39 • The base station supports extended encryption;
2-23
3GPP2 C.S0005-A v6.0
1 • C_SIG_ENCRYPT_MODEs is equal to ‘000’ or ENC_KEYs is equal to NULL;
2 • C_SIG_ENCRYPT_REQ is set to ‘1’ or D_SIG_ENCRYPT_REQ is set to ‘1’ in the

3 Origination Message;
4 • The mobile station does not recognize that this is an emergency call.
5 2.3.12.4.1.2 Extended Encryption for Signaling on f/r-dsch
6 The initial mode of extended encryption for f/r-dsch signaling messages is established by
7 sending a Channel Assignment Message or Extended Channel Assignment Message with the
8 ENCRYPT_MODE field set to ‘11’4 and the D_SIG_ENCRYPT_MODE field set to one of the
9 values specified in Table 3.7.4.5-1. The value of D_SIG_ENCRYPT_MODEr is then stored in
10 D_SIG_ENCRYPT_MODEs.
11 To turn f/r-dsch signaling encryption on or off after channel assignment, the base station
12 sends a General Handoff Direction Message or Universal Handoff Direction Message with the
13 ENCRYPT_MODE field and the D_SIG_ENCRYPT_MODE field set accordingly. Alternatively,
14 the base station may send a Security Mode Command Message on f-dsch with the
15 D_SIG_ENCRYPT_MODE field set accordingly.
16 If D_SIG_ENCRYPT_MODEs is not equal to ‘000’ and ENC_KEYs is not equal to NULL, all
17 f/r-dsch signaling messages shall be encrypted based on the value of
18 D_SIG_ENCRYPT_MODEs using the procedures specified in 2.3.12.4.1.3, except for the
19 exceptions listed below in the rest of this section.
20 On the f-dsch, the Security Mode Command Message may be sent un-encrypted. The Base
21 Station Reject Order shall be sent un-encrypted.
22 On the r-dsch, the Security Mode Request Message shall be sent un-encrypted.
23 2.3.12.4.1.3 Signaling Encryption/Decryption Procedures
24 In order to perform signaling encryption/decryption on f/r-csch or f/r-dsch, both the

25 mobile station and the base station shall each maintain the following 32-bit counters:
26 • EXT_ENCRYPT_SEQ[i] (the 32-bit crypto-sync for encryption. i = 0 and 1)
27 • EXT_DECRYPT_SEQ[i] (the 32-bit crypto-sync for decryption. i = 0 and 1)
28 The above counters in the base station and the mobile station shall only be initialized by a
29 Registration Accepted Order, Channel Assignment Message, Extended Channel Assignment
30 Message, or Security Mode Command Message in response to a Registration Message,
31 Origination Message, Page Response Message, or Security Mode Request Message that
32 carries an ENC_SEQ_H field with a valid ENC_SEQ_H_SIG field.5 The response to a
4 If ENCRYPT_MODE is set to a value other than ‘11’, see section 2.3.12.2.1.
5 The mobile station should select a different value of ENC_SEQ_H every time ENC_SEQ_H is
included in a message. This is to prevent the re-use of the same 24 most significant bits of the 32-bit
crypto-sync.
2-24
3GPP2 C.S0005-A v6.0
1 Registration Message is a Registration Accepted Order. The response to an Origination

2 Message or Page Response Message is a Channel Assignment Message or Extended Channel
3 Assignment Message. The response to a Security Mode Request Message is a Security Mode
4 Command Message.
5 Upon initialization of the crypto-sync counters, the following initialization shall be

6 performed at the mobile station:
7 • The 24 most significant bits of EXT_ENCRYPT_SEQ[i] and EXT_DECRYPT_SEQ[i]
8 shall be set to the value of the ENC_SEQ_H field included in the message for i = 0
9 and 1.
10 • The 8 least significant bits of EXT_ENCRYPT_SEQ[i] and EXT_DECRYPT_SEQ[i] shall
11 be set to 0 for i = 0 and 1.
12 The sender shall perform the following procedures for each Layer 3 PDU (including all Layer
13 3 PDU retransmitted by Layer 3) that is to be encrypted:
14 If ENCRYPT_MODEs is equal to ‘11’ and SIG_ENCRYPT_MODEs is equal to ‘001’, the mobile
15 station or the base station shall perform the following procedures for transmission of
16 messages that are to be encrypted, in the order listed:
17 1. The sender of the message shall aAppend between 0 and 7 inclusive padding bits
18 (set to any random combination of ‘0’s and ‘1’s) to the Layer 3 PDU such that the
19 length of the padded Layer 3 PDU in bits is an integer multiple of eight (the padding
20 bits become part of the L3 PDU).
21 2. The sender of the message shall cCompute an 8-bit Layer 3 PDU CRC as specified in
22 2.3.12.4.1.4 over the un-encrypted Layer 3 PDU (including the padding bits, if any).
23 3. The sender of the message shall aAppend the 8-bit CRC to the end of the Layer 3
24 PDU.
25 4. The sender of the message shall set EXT_ENC_SEQs to (EXT_ENC_SEQs + 1) mod
26 232, and set ENC_SEQs to the 8 least significant bits of the crypto-sync,
27 EXT_ENC_SEQs.If the PDU is to be transmitted on f/r-csch, let
28 SDU_ENCRYPT_MODE equal C_SIG_ENCRYPT_MODEs. If the PDU is to be
29 transmitted on f/r-dsch, let SDU_ENCRYPT_MODE equal D_SIG_ENCRYPT_MODEs.
30 If the Layer 3 PDU uses unassured mode, let i = 0; otherwise, let i = 1.
31 5. The sender of the message shall encrypt the concatenated Layer 3 PDU and the 8-bit
32 Layer 3 CRC using the encryption procedures specified in 2.3.12.4.1.2.Let
33 EXT_ENC_SEQ equal EXT_ENCRYPT_SEQ[i]. Encrypt the concatenated Layer 3 PDU
34 and the 8-bit CRC by using EXT_ENC_SEQ and the encryption algorithm specified
35 by SDU_ENCRYPT_MODE, in accordance with 2.3.12.4.3.
36 6. Let ENC_SEQ be the 8 least significant bits of EXT_ENCRYPT_SEQ[i].The sender of

37 the message shall passThe sender shall pass the encrypted concatenated Layer 3
38 PDU and the 8-bit Layer 3 CRC, along with ENC_SEQs and the signaling encryption
39 mode indicated by SIGSDU_ENCRYPT_MODEs, to the LAC layer.
40 7. Set EXT_ENCRYPT_SEQ[i] to (EXT_ENCRYPT_SEQ[i] + 1) mod 232.
2-25
3GPP2 C.S0005-A v6.0
1 If ENCRYPT_MODEs is not equal to ‘11’, or ENCRYPT_MODEs is equal to ‘11’ and

2 SIG_ENCRYPT_MODEs is equal to ‘000’, the mobile station and base station shall not
3 perform the above encryption procedures for Layer 3 PDU as specified in this section.
4 The mobile station or the base station shall perform the following procedures upon
5 reception of encrypted messages (i.e., if SDU_ENCRYPT_MODE indicated by LAC Layer is
6 equal to ‘001’), in the order listedThe receiver shall perform the following procedures upon
7 reception of an encrypted signaling message with an ENC_SEQ field passed by the LAC
8 Layer (e.g., if SDU_ENCRYPT_MODE indicated by LAC Layer is not equal to ‘000’ ):
9 1. The receiver of the message shall update EXT_ENC_SEQs as specified in
10 2.3.12.4.1.1 by using the 8-bit ENC_SEQ passed from the LAC Layer.If the Layer 3
11 PDU uses unassured mode, let i = 0 and N = 8; otherwise, let i = 1 and N = 4. Let V
12 be the 8 least significant bits of EXT_ENC_SEQ_D[i]. Perform the duplicate detection
13 procedures in accordance with 2.3.12.4.1.5 using N and V, before proceeding
14 further.
15 2. The receiver of the message shall set ENC_SEQs to ENC_SEQ, which is received
16 from the LAC Layer.Construct EXT_ENC_SEQ as follows:
17 If (ENC_SEQ - V) mod 256 < 128:
18 EXT_ENC_SEQ[i] = (EXT_DECRYPT_SEQ[i] + (ENC_SEQ - V) mod 256) mod 232
19 Else:
20 EXT_ENC_SEQ[i] = (EXT_DECRYPT_SEQ[i] - (V - ENC_SEQ) mod 256) mod 232
21 3. The receiver of the message shall rRemove the LAC Layer padding, at the end of the
22 Layer 3 PDU, if any, such that the Layer 3 PDU is octet aligned.
23 4. The receiver of the message shall dDecrypt the concatenated Layer 3 PDU and the 8-
24 bit Layer 3 CRC using EXT_ENC_SEQ and the encryption algorithm specified by
25 SDU_ENCRYPT_MODE, in accordance with 2.3.12.4.3.the decryption procedures
26 specified in 2.3.12.4.1.2.
27 5. The receiver of the message shall cCompute an 8-bit CRC as specified in

28 2.3.12.4.1.4 over the un-encrypted Layer 3 PDU (excluding the received 8-bit CRC).
29 6. The receiver of the message shall cCompare the value of the computed CRC with the
30 decrypted 8-bit CRC. If the two CRCs are equal, the receiver shall declare that the
31 decryption has been performed is defined to be successfully; otherwise the
32 decryption is defined to be not unsuccessful.
33 7. If the decryption was unsuccessful, the message shall be discarded; otherwise, if

34 ((ENC_SEQ - V) mod 256) < 128, the receiver shall set EXT_DECRYPT_SEQ[i] to
35 EXT_ENC_SEQ.
36 8. If the base station can not decrypt an Origination Message, the base station should
37 send a Base Station Reject Order (ORDQ = ‘00000000’). If the base station can not
38 decrypt any other message, the base station should send a Base Station Reject Order
39 (ORDQ = ‘00000001’).
2-26
3GPP2 C.S0005-A v6.0
1 2.3.12.4.1.4 Computation of the 8-bit Layer 3 PDU CRC Field
2 The generator polynomials for the 8-bit Layer 3 PDU CRC field shall be as follows:
3 g(x) = x8 + x7 + x4 + x3 + x + 1
4 The Layer 3 PDU CRC field shall be computed according to the following procedure using
5 the logic shown in Figures 2.3.12.4.5-1:
6 • Initially, all shift register elements shall be set to logical one and the switches shall
7 be set in the up position.
8 • The register shall be clocked a number of times equal to the number bits in the
9 Layer 3 PDU with those bits as input.
10 • The switches shall be set in the down position so that the output is a modulo-2
11 addition with a ‘0’ and the successive shift register inputs are ‘0’.
12 • The register shall be clocked an additional 8 number of times.
13 • These additional bits shall be the Layer 3 PDU CRC field indicator bits.
14 • The bits shall be transmitted in the order calculated.
15
In p u t
0 1 2 3 4 5 6 7
x x x x x x x x
Ou t p u t
Den ot es on e-b it s t or a ge elem en t Up for a ll t h e b it s of t h e L3 S DU a n d
Den ot es m od u lo-2 a d d it ion Down for t h e la s t 8 clock

cycles
16
17 Figure 2.3.12.4.1.4-1. 8-Bit Layer 3 SDU CRC Field Calculation
18
19 2.3.12.4.1 Extended-Encryption of Signaling Messages
20 All broadcast messages (messages that are not addressed to a particular mobile station)
21 shall not be encrypted.
22 When ENCRYPT_MODEs is equal to ‘11’ and SIG_ENCRYPT_MODEs is equal to ‘001’ and
23 when there is a valid encryption key, all Layer 3 PDU of the signaling messages with the
24 following exceptions shall be encrypted as specified in 2.3.12.4.
25 • General Page Message
26 • Universal Page Message
27 If the mobile station sends an encrypted Registration Message, Origination Message, or a
2-27
3GPP2 C.S0005-A v6.0
1 Page Response Message, and receives a layer 2 acknowledgement from the base station, but
2 does not receive any Layer 3 message from the base station that the mobile station could
3 decrypt successfully thereafter, then the mobile station should resend the same message
4 un-encrypted.
5 2.3.12.4.1.1 Extension of ENC_SEQ to EXT_ENC_SEQ for decryption

6 EXT_ENC_SEQs is the Extended Encryption Sequence Number that is used as one of the
7 inputs to the encryption algorithm as shown in Figure 2.3.12.4.2-1. The following formula
8 shall be used to update the 32-bit EXT_ENC_SEQs in the receiver from the 8-bit ENC_SEQ
9 passed by the LAC Layer:
10 If (ENC_SEQ - ENC_SEQs) mod 256 < 128:
11 EXT_ENC_SEQs = (EXT_ENC_SEQs + (ENC_SEQ - ENC_SEQs) mod 256) mod 232
12 Else:
13 EXT_ENC_SEQs = (EXT_ENC_SEQs - ( ENC_SEQs - ENC_SEQ) mod 256) mod 232.
14 2.3.12.4.1.5 Duplicate Detection of Encrypted Messages
15 This section describes the duplicate detection of encrypted signaling messages (see the
16 decryption procedures at the receiver described in 2.3.12.4.1.3).
17 Given the value of the latest sequence number received, V, and the window size, N (see the
18 decryption procedures at the receiver described in 2.3.12.4.1.3), the 8-bit encryption
19 sequence number space at the receiver can be divided into the following three segments as
20 shown in Figure 2.3.12.4.1.5-1:
21 • Segment #1 - sequence numbers from ((V - N + 1) mod 256) to V inclusive (the anti-
22 replay window)
23 • Segment #2 - sequence numbers from ((V + 1) mod 256) to ((V + 127) mod 256)
24 inclusive (future sequence numbers)
25 • Segment #3 - sequence numbers from ((V + 128) mod 256) to ((V - N) mod 256)
26 inclusive (past sequence numbers)
2-28
3GPP2 C.S0005-A v6.0
N[i
] (s
eg m
ent
#1)
V
t #3
men
Seg
8-bit Circle
)
t #2
en
gm
Se
7(
12
1
2 Figure 2.3.12.4.1.5-1 An 8-bit encryption sequence number space divided into 3

3 segments
5 If the received sequence number, ENC_SEQ, belongs to segment #1, the receiver shall check
6 whether ENC_SEQ has already been received.6 If ENC_SEQ has been received already, the
7 receiver shall discard the message and shall not perform the remaining steps of the
8 decryption procedures described in 2.3.12.4.1.3; otherwise, the receiver shall continue the
9 decryption procedures described in 2.3.12.4.1.3.
10 If the received sequence number, ENC_SEQ, belongs to segment #2, the receiver shall
11 continue the decryption procedures described in 2.3.12.4.1.3.
12 If the received sequence number, ENC_SEQ, belongs to segment #3, the receiver shall
13 discard the message and shall not perform the remaining steps of the decryption
14 procedures described in 2.3.12.4.1.3.
15 2.3.12.4.2 Extended Encryption for User Information
16 Extended encryption can be turned on or off independently for each individual service on
17 f/r-dtch.
6 The actual means of checking is left to implementation. One simple implementation is for the
receiver to maintain an N-bit bitmap, w, to represent the sequence numbers in segment #1. The order
of w is most significant bit first (i.e., w[N-1], w[N-2],..., w[1], w[0]). Let w[0] represents V, w[1]
represents ((V - 1) mod 256), etc. w[i] = ‘1’ means sequence number i has already been received. When
a message with sequence number i has been decrypted successfully, w[i] is set to ‘1’. Whenever V
moves from V1 to V2, left-shift w ((V2 - V1) mod 256) times. Each time w is left-shifted, stuff a ‘0’ at
the eight end of w. After all the shifting, set w(0) to ‘1’.
2-29
3GPP2 C.S0005-A v6.0
1 The initial encryption mode of user information of a service is established by sending a

2 Security Mode Command Message on f-csch or by setting the UI_ENCRYPT_MODE field in
3 the Service Configuration information record, with the UI_ENCRYPT_MODE field set to one
4 of the values specified in 3.7.5.7-3. The value of the UI_ENCRYPT_MODE field is then
5 stored in SO_CON_RECs[j].UI_ENCRYPT_MODE, where SO_CON_RECs[j] is the service
6 option connection record (see 2.6.4.1.12) corresponding to the service.
7 To turn user information encryption for a service on or off after channel assignment, the
8 base station sends a Security Mode Command Message on f-dsch with the
9 UI_ENCRYPT_MODE field set accordingly. Explicit action time should be used when
10 sending the Security Mode Command Message.
11 User information shall be encrypted based on the value of

12 SO_CON_RECs[j].UI_ENCRYPT_MODE, where SO_CON_RECs[j] is the service option
13 connection record (see 2.6.4.1.12) corresponding to the service.
14 2.3.12.4.2.1 User Information Encryption/Decryption Procedures
15 [Reserved]
16 If extended encryption for user information is turned on for a service, the sender shall
17 encrypt each data block (see [3]) from that service, in accordance with 2.3.12.4.3, before
18 passing the data blocks to MAC Layer. On the receiver side, the receiver shall decrypt each
19 data block for that service from MAC Layer, in accordance with 2.3.12.4.3, before passing
20 them to that service.
21 2.3.12.4.31.2 Encryption/Decryption Procedures Interface to the Encryption Algorithms
22 Figure 2.3.12.4.3-1 shows the structure for encrypting/decrypting both signaling messages
23 and user information. Various encryption algorithms can be used with this structure. The
24 encryption algorithm takes all or part of the following parameters as inputs, as illustrated
25 in Figure 2.3.12.4.3-1. The actual inputs to the algorithm are specified in the rest of this
26 section.
27 The encryption algorithm used takes all or part of the following parameters as input (as
28 illustrated in Figure 2.3.12.4.1.2-1). The actual inputs to the algorithm are specified in this
29 section.
30
2-30
3GPP2 C.S0005-A v6.0
This part is
only performed
at the
receiver2)
ENC_SEQ
8 3 Encryption
1 Key
compute sr_id
EXT_ENC_SEQs Direction
Encryption Hook
EXT_ENC_SEQs3),4)
32
un-encrypted data1) encrypted data for receiver 1)

General Encryption Algorithm
encrypted data from sender 2) un-encrypted data2)

Notes:
1) For encryption only
2) For decryption only
3) RLP generates the cryptosync value when RLP is used for a service option
4) The following value shall be used instead of EXT_ENC_SEQ for voice service: sys_time/20 mod 232,
where sys_time is the system time, in units of ms, corresponding to the start of the frame that carries the voice
information bits.
1
2
3 Figure 2.3.12.4.1.2-1. Encryption Input Parameters
2-31
3GPP2 C.S0005-A v6.0
Encryption
Key
EXT_ENC_SEQ sr_id Direction ACK_Mode
Variable
32 3 1 1
Encryption Hook
encrypted data
un-encrypted data(1) for receiver (1)
encrypted data from un-encrypted

sender (2) data(2)
Notes:
(1) For encryption only
(2) For decryption only
Encryption
Key
EXT_ENC_SEQ(3) sr_id Direction ACK_Mode
Variable
32 3 1 1
Encryption Hook
encrypted data
un-encrypted data(1) for receiver(1)
encrypted data from un-encrypted

sender(2) data(2)
Notes:
(1) For encryption only
(2) For decryption only
(3) The following value shall be used instead of EXT_ENC_SEQ for voice service: sys_time/20 mod 232,
where sys_time is the system time, in units of ms, corresponding to the start of the frame that carries the voice
information bits.
3 Figure 2.3.12.4.3-1. Encryption Input Parameters
2-32
3GPP2 C.S0005-A v6.0
2 The inputs to the encryption algorithm are described as follows:

3 • EXT_ENC_SEQs - A 32-bit Extended Encryption Sequence Number stored in the
4 sender or receiver (in the receiver, it is updated and derived from the 8-bit ENC_SEQ
5 as described in 2.3.12.4.1.1)for encryption/decryption.
6 • sr_id - Service Reference Identifier (see [3]), which identifies the associated service
7 option instance. The value of ‘000’ is reserved for signaling.
8 • Direction - The direction of the message data being transmittedencrypted/decrypted.

9 This shall be set to ‘0’ if the message data is transmitted on or received on a forward
10 link. Otherwise, it shall be set to ‘1’.
11 • Encryption Key – Session Key for Encryption. This shall be a result of successful
12 Session Key Agreement between the base station and the mobile station. The
13 Encryption Key shall be stored by the mobile station in a semi-permanent memory,
14 (ENC_KEYs[i], where i ranges from ‘0000’ to ‘1111’).
15 • Channel_id – Channel identifier, which identifies the physical channel that carries
16 the data to be encrypted or decrypted. This is applicable only to user information
17 encryption on f/r-dtch. Channel_id shall be set to, ‘000’ for Fundamental Channel,
18 ‘001’ for Dedicated Control Channel, ‘010’ for Supplemental Code Channel, ‘011’ for
19 Supplemental Channel 0, and ‘101’ for Supplemental Channel 1.
20 • ACK_Mode – The delivery mode (unassured or assured) of the signaling message.

21 This shall be set to ‘0’ if the message is delivered using unassured mode; otherwise,
22 this shall be set to ‘1’.
23 If the Enhanced Cellular Message Encryption Algorithm is used (ENCRYPT_MODEs is equal
24 to ‘11’ and SIG_ENCRYPT_MODEs is equal to ‘001’), the following requirements apply for
25 encrypting/decrypting signaling messages, the input parameters of the Enhanced Cellular
26 Message Encryption Algorithm (see [23]) shall be set as follows:

29 – SYNC[0] = ENC_SEQs when encryptingEXT_ENC_SEQ [7:0]7.
30 – SYNC[0] = ENC_SEQ passed by the LAC Layer associated with the Layer 3 PDU
31 when decrypting.
32 – SYNC[1] = (ACK_Mode |Direction | EXT_ENC_SEQs [1413:8] ), where “|” denotes
33 concatenation and EXT_ENC_SEQs [1413:8] is bits 8 through 1413 of
34 EXT_ENC_SEQs (with the LSB being bit 0).
35 If the Rijndael Encryption Algorithm is used for encrypting/decrypting signaling messages,
7 Z [y:x] denotes bit x to bit y of the binary value Z with bit 0 the least significant bit of Z.
2-33
3GPP2 C.S0005-A v6.0
1 the input parameters of ESP_AES (see [33]) shall be set as follows:
2 • The key parameter shall be set to ENC_KEYS.
3 • The FRESH parameter shall be set to (ACK_Mode | sr_id [2:0] | Direction |

4 EXT_ENC_SEQ [31:0] | ‘000’).
5 • The FRESHSIZE parameter shall be set to 5.
6 • The BUF parameter shall be set to the pointer of the most significant bit of the
7 buffer8 that contains the data to be encrypted or decrypted.
8 • The BIT_OFFSET parameter shall be set to the offset between the bit position of the
9 most significant bit of the data to be encrypted/decrypted and the bit position of the
10 most significant bit of the buffer (e.g., if the bit position of the most significant bit of
11 the data to be encrypted/decrypted and the bit position of the most significant bit of
12 the buffer are equal, BIT_OFFSET = 0).
13 • The BIT_COUNT parameter shall be set to the number of bits of the data to be
14 encrypted/decrypted.
15 If the Rijndael Encryption Algorithm is used for encrypting/decrypting user information,

16 the input parameters of ESP_AES (see [33]) shall be set as follows:
17 • The key parameter shall be set to ENC_KEYS.
18 • The FRESH parameter shall be set to (sr_id [2:0] | Direction | (sys_time/20 mod
32
19 2 ) [31:0]| Channel_id [2:0] | ‘0’), where sys_time is the system time, in units of ms,
20 corresponding to the start of the physical layer frame that carries the data block(s).
21 • The FRESHSIZE parameter shall be set to 5.
22 • The BUF parameter shall be set to the pointer of the most significant bit of the
23 buffer9 that contains the data to be encrypted or decrypted.
24 • The BIT_OFFSET parameter shall be set to the offset between the bit position of the
25 most significant bit of the data to be encrypted/decrypted and the bit position of the
26 most significant bit of the buffer (e.g., if the bit position of the most significant bit of
27 the data to be encrypted/decrypted and the bit position of the most significant bit of
28 the buffer are equal, BIT_OFFSET = 0).
29 • The BIT_COUNT parameter shall be set to the number of bits of the data to be
30 encrypted/decrypted.
8 “Buffer” refers to the physical memory that stores the data to be encrypted or decrypted. The octets
in the buffer are assumed to be most-significant first, and the first bit of the buffer is the most
significant bit of the first octet.
9 “Buffer” refers to the implementation-dependent physical memory that stores the data to be
encrypted or decrypted. The octets in the buffer are assumed to be most-significant first, and the first
bit of the buffer is the most significant bit of the first octet.
2-34
3GPP2 C.S0005-A v6.0
1 2.3.12.4.2 Extended-Encryption for Voice
2 Extended-Encryption for voice service option is performed by means of the encryption

3 procedures as specified in 2.3.12.4.1.2. If UI_ENCRYPT_MODEs[i] is equal to ‘000’, where i
4 is the connection reference associated with the voice service option, the voice data shall not
5 be encrypted. Instead of EXT_ENC_SEQs, the following value shall be used as an input to
6 the encryption procedure specified in 2.3.12.4.1.2.
32
7 sys_time/20 mod 2 ,
8 where sys_time is the system time, in units of ms, corresponding to the start of the frame
9 that carries the information bits.
10 2.3.12.4.34 Encryption Negotiation
11 The mobile station shall indicate to the base station the encryption algorithms supported by
12 using SIG_ENCRYPT_SUP and UI_ENCRYPT_SUP in one of the following messages:
13 • Registration Message
14 • Origination Message
15 • Page Response Message
16 • Security Mode Request Message
17 • Status Response Message (in Encryption Capability information record)
18 • Extended Status Response Message (in Encryption Capability information record)
19 The mobile station can also indicate to the base station the encryption algorithms
20 supported by using SIG_ENCRYPT_SUP and UI_ENCRYPT_SUP in Encryption Capability
21 information record in the Status Response Message or Extended Status Response Message.
22 The base station may turn on or turn off the encryption of the voice, data services, or
23 signaling encryption with a Security Mode Command Message sent on f-dsch or f-csch.
24 Similarly, the mobile station may propose to turn on or turn off the user information
25 encryption or signaling encryption with a Security Mode Request Message sent on r-dsch or
26 r-csch.
27 2.3.12.4.4 Computation of the 8-bit Layer 3 PDU CRC Field
28 The generator polynomials for the 8-bit Layer 3 PDU CRC field shall be as follows:
29 g(x) = x8 + x7 + x4 + x3 + x + 1
30 The Layer 3 PDU CRC field shall be computed according to the following procedure using
31 the logic shown in Figures 2.3.12.4.4-1:
32 • Initially, all shift register elements shall be set to logical one and the switches shall
33 be set in the up position.
34 • The register shall be clocked a number of times equal to the number bits in the
35 Layer 3 PDU with those bits as input.
2-35
3GPP2 C.S0005-A v6.0
1 • The switches shall be set in the down position so that the output is a modulo-2
3 • The register shall be clocked an additional 8 number of times.
4 • These additional bits shall be the Layer 3 PDU CRC field indicator bits.
5 • The bits shall be transmitted in the order calculated.
2-36
3GPP2 C.S0005-A v6.0
In p u t
0 1 2 3 4 5 6 7
x x x x x x x x
Ou t p u t
Den ot es on e-b it s t or a ge elem en t Up for a ll t h e b it s of t h e L3 S DU a n d
Den ot es m od u lo-2 a d d it ion Down for t h e la s t 8 clock

cycles
2
3 Figure 2.3.12.4.4-1. 8-Bit Layer 3 SDU CRC Field Calculation
4 2.3.12.4.5 Computation of ENC_SEQ_H_SIG
5 The ENC_SEQ_H_SIG field (included in the Registration Message, Origination Message, Page
6 Response Message, and Security Mode Request Message) is a signature of the 24 most
7 significant 24 bits of the cryptosync (ENC_SEQ_H). The mobile station shall compute this
8 8-bit field as follows:
9 1. The mobile station shall construct the message bits as shown in Figure 2.3.12.4.5-1.
10 For messages that are sent on the r-csch, X is set to RANDs. For messages that are sent
11 on the r-dsch, X is set to (sys_time/20000) mod 232, where sys_time is the system
12 time in ms at which the message is assembled.
13
MSB LSB
SSD_A XRANDs ENC_SEQ_H
(64 bits) (32 bits) (24 bits)
14 Figure 2.3.12.4.5-1. Message Bits
15
16 2. The mobile station shall pad the message bits constructed in the previous step, as
17 specified in FIPS PUB 180-1 (Federal Information Processing Standards Publication 180-
18 1), and compute the 160-bit message digest as specified in FIPS PUB 180-1.
19 3. The mobile station shall store the 8 rightmost (least significant) bits of the message
20 digest in ENC_SEQ_H_SIG.
21 2.3.13 Lock and Maintenance Required Orders

22 The mobile station shall have memory to store the lock reason code (LCKRSN_Ps-p) received
23 in the Lock Until Power-Cycled Order. The data retention time under power-off conditions
24 shall be at least 48 hours.
2-37
3GPP2 C.S0005-A v6.0
1 The mobile station shall have memory to store the maintenance reason code (MAINTRSNs-p)
2 received in the Maintenance Required Order. The data retention time under power-off
3 conditions shall be at least 48 hours.
4 There are no requirements on the use of the lock and maintenance reason codes, and
5 interpretation and use are implementation dependent.
6 2.3.14 Mobile Station Revision Identification
7 The mobile station shall provide memory to store the following parameters sent in the
8 Status Message, the Status Response Message, or the Extended Status Response Message
9 (Terminal Information information record):
10 • Mobile manufacturer code (MOB_MFG_CODEp)
11 • Manufacturer’s model number (MOB_MODELp)
12 • Firmware revision number (MOB_FIRM_REVp)
13 In addition, the mobile station shall provide memory to store the following parameter for
14 each supported band class:
15 • Protocol revision number (MOB_P_REVp)
16 2.3.15 Temporary Mobile Station Identity
17 2.3.15.1 Overview
18 The Temporary Mobile Station Identity (TMSI) is a temporary locally assigned number used
19 for addressing the mobile station. The mobile station obtains a TMSI when assigned by the
20 base station. The TMSI as a number does not have any association with the mobile
21 station’s IMSI, ESN, or directory number all of which are permanent identifications.
22 A TMSI zone is an arbitrary set of base stations for the administrative assignment of TMSIs.
23 A TMSI_CODE is uniquely assigned to a mobile station inside a TMSI zone. A TMSI zone is
24 identified by the TMSI_ZONE field. The same TMSI_CODE may be reused to identify a
25 different mobile station in a different TMSI zone. The pair (TMSI_ZONE, TMSI_CODE) is a
26 globally unique identity for the mobile station. This pair is called the full TMSI. The
27 TMSI_CODE can be two, three, or four octets in length. The TMSI_ZONE can range from 1
28 to 8 octets in length. Figure 2.3.15-1 shows an example of a TMSI_ZONE where the
29 TMSI_ZONE is a subset of the NID (see 2.6.5.2).
2-38
3GPP2 C.S0005-A v6.0
SID = j
TMSI_ZONE = q
TMSI_ZONE = p
SID = k
TMSI_ZONE = r
NID = u
SID = i
SID = 1
2 Figure 2.3.15-1. TMSI Zone Example
4 The base station sends a TMSI Assignment Message to assign a TMSI. In response, the
5 mobile station sends a TMSI Assignment Completion Message. The base station instructs
6 the mobile station to delete the TMSI by sending a TMSI Assignment Message with all the
7 bits in the TMSI_CODE field set equal to ‘1’.
8 The TMSI expiration time is used to automatically delete the assigned TMSI. The mobile
9 station obtains the expiration time when the TMSI is assigned in the TMSI Assignment
10 Message. The mobile station compares the expiration time to the current System Time
11 when it powers up and periodically during operation.
12 Whenever the mobile station sends its full TMSI, the mobile station sets a timer, called the
13 full-TMSI timer. If the full-TMSI timer expires, the mobile station deletes the TMSI by
14 setting all bits in the TMSI_CODE field to ‘1’.
15 2.3.15.2 TMSI Assignment Memory
16 The mobile station shall provide memory to store the following parameters:
17 • 4-bit assigning TMSI zone length (ASSIGNING_TMSI_ZONE_LENs-p)
18 • 8-octet assigning TMSI zone (ASSIGNING_TMSI_ZONEs-p)
19 • 4-octet TMSI code (TMSI_CODEs-p)
20 • 3-octet TMSI expiration time (TMSI_EXP_TIMEs-p)
21
2-39
3GPP2 C.S0005-A v6.0
1 2.4 Accumulated Statistics
2 2.4.1 Monitored Quantities and Statistics
3 The mobile station shall store the value described in Table 2.4.1-1.
4 Table 2.4.1-1. Monitored Quantities and Statistics
Length
Quantity Identifier Description
(bits)
OTHER_SYS_TIME 36 The SYS_TIME field from the most recently

received Sync Channel Message
5 2.4.2 Accumulated Paging, Broadcast, and Forward Common Control Channel Statistics
6 The mobile station shall maintain the counters shown in Table 2.4.2-1. The counters shall
7 have the length as specified in Table 2.4.2-1. The mobile station shall initialize each
8 counter described herein to zero upon power-on; the mobile station shall not re-initialize
9 any counter described herein at any other time except upon command from the base
10 station. Each counter shall be maintained modulo 2Length, where Length is specified in
11 Table 2.4.2-1.
12 The mobile station shall increment the counter PAG_6 each time that it declares a loss of
13 the Paging Channel (see 2.6.2.1.1.4). The mobile station shall increment the counter
14 PAG_7 for each idle handoff it performs. The mobile station shall increment the counter
15 FCCCH_4 each time that it declares a loss of the Forward Common Control Channel (see
16 2.6.2.1.1.4). The mobile station shall increment the counter BCCH_5 each time that it
17 declares a loss of the Broadcast Control Channel (see 2.6.2.1.1.4).
18 Table 2.4.2-1. Accumulated PCH/BCCH/F-CCCH Channel Statistics
Counter Length
Description
Identifier (bits)
PAG_6 16 Number of times that the mobile station

declared a loss of the Paging Channel
PAG_7 16 Number of mobile station idle handoffs
FCCCH_4 16 Number of times that the mobile station
declared a loss of the Forward Common
Control Channel
BCCH_5 16 Number of times that the mobile station
declared a loss of the Broadcast Control
Channel
19 2.5 Reserved
20
21
22
23
2-40
3GPP2 C.S0005-A v6.0
1 2.6 Layer 3 Processing
2 This section describes mobile station lLayer 3 processing. It contains frequent references to
3 the messages that flow between the mobile station and base station. While reading this
4 section, it may be helpful to refer to the PDU formats (see 2.7 and 3.7), and to the message
5 flow examples (see Annex B).
6 The mobile station shall ignore fields at the end of messages that do not exist in the
7 protocol revision supported by the mobile station.
8 The values for the time and numerical constants used in this section (e.g., T20m, N4m) are
9 specified in Annex D.
10 As illustrated in Figure 2.6-1, mobile station lLayer 3 processing consists of the following
11 states:
12 • Mobile Station Initialization State - In this state, the mobile station selects and
13 acquires a system.
14 • Mobile Station Idle State - In this state, the mobile station monitors messages on the
15 f-csch.
16 • System Access State - In this state, the mobile station sends messages to the base
17 station on the r-csch and receives messages from the base station on the f-csch.
18 • Mobile Station Control on the Traffic Channel State - In this state, the mobile station
19 communicates with the base station using the f/r-dsch and f/r-dtch.
20 After power is applied to the mobile station, it shall enter the System Determination Substate
21 of the Mobile Station Initialization State with a power-up indication (see 2.6.1.1).
2-41
3GPP2 C.S0005-A v6.0
Power-Up
Initialization Begin analog

Task mode
(TIA/EIA/IS-2000-6) operation
End Analog
mode
Mobile
operation
Station
Initialization
State
(2.6.1)
Mobile Station Idle
Handoff Operation
with
NGHBR_CONFIG Mobile station
equal to has fully
'011' or unable to acquired
receive PCH or system timing
BCCH/F-CCCH
message
Mobile
Station
Idle State
(2.6.2)
Receives an
acknowledgment
Receives a PCH or
to an Access
F-CCCH message
Channel or
requiring an
Enhanced Access
acknowledgment or
Channel
response; originates
transmission
a
other than an
call or performs
Origination
registration.
Message or a
Page Response
System
Message
Access
State
(2.6.3)
Ends use of
Directed to a Traffic the Traffic
Channel Channel
Mobile Station
Control on the
Traffic Channel
State
Note: Not all state (2.6.4)
transitions are
shown.
1
2 Figure 2.6-1. Mobile Station Layer 3 Processing States
2-42
3GPP2 C.S0005-A v6.0
1 2.6.1 Mobile Station Initialization State
2 In this state, the mobile station first selects a system to use. If the selected system is a
3 CDMA system, the mobile station proceeds to acquire and then synchronize to the CDMA
4 system. If the selected system is an analog system, the mobile station begins analog mode
5 operation (see 2.6.1 of [6]).
6 As illustrated in Figure 2.6.1-1, the Mobile Station Initialization State consists of the
7 following substates:
8 • System Determination Substate - In this substate, the mobile station selects which
9 system to use.
10 • Pilot Channel Acquisition Substate - In this substate, the mobile station acquires the
11 Pilot Channel of a CDMA system.
12 • Sync Channel Acquisition Substate - In this substate, the mobile station obtains
13 system configuration and timing information for a CDMA system.
14 • Timing Change Substate - In this substate, the mobile station synchronizes its
15 timing to that of a CDMA system.
16 While in the Mobile Station Initialization State, the mobile station shall update all active
17 registration timers as specified in 2.6.5.5.1.2.
2-43
3GPP2 C.S0005-A v6.0
Power-up or
Any Other State
System
Determination
Substate
(2.6.1.1)
CDMA system
selected
Pilot Channel
Acquistion
Substate
(2.6.1.2)
Acquires Pilot Channel
Sync Channel
Acquisition
Substate
(2.6.1.3)
Receives Sync
Channel Message
Timing Change Note: Not all state

Substate transitions are
(2.6.1.4) shown.
Mobile Station
1 Idle State
2 Figure 2.6.1-1. Mobile Station Initialization State
2-44
3GPP2 C.S0005-A v6.0
1 2.6.1.1 System Determination Substate
2 In this substate, the mobile station selects the system to use.

3 Upon entering the System Determination Substate, the mobile station shall initialize
4 registration parameters as specified in 2.6.5.5.1.1.
5 If the mobile station enters the System Determination Substate with a power-up indication,
6 the mobile station shall set RANDs to 0 (see 2.3.12.1.2), PACAs to disabled, PACA_CANCEL
7 to ‘0’, the PACA state timer to disabled, NDSS_ORIGs to disabled, MAX_REDIRECT_DELAYs
8 to 31, REDIRECTIONs to disabled, all entries of SDB_SO_OMITs to ‘0’, and T_SLOTTEDs to
9 T74m, KEYs to NULL, and C_SIG_ENCRYPT_MODEs to ‘000’. If the mobile station supports
10 analog mode operation in Band Class 0, the mobile station shall set the First-Idle ID status
11 to enabled (see [6]). The mobile station shall select a system in accordance with the custom
12 system selection process (see 2.6.1.1.1) and shall attempt to acquire the selected system
13 (see 2.6.1.1.4).
14 If the mobile station enters the System Determination Substate with any indication other
15 than a power-up indication, and if PACAs is equal to enabled, the mobile station shall also
16 set PACAs to disabled, PACA_CANCEL to ‘0’, the PACA state timer to disabled, and should
17 indicate to the user that the PACA call has been canceled.
18 If the mobile station enters the System Determination Substate with an acquisition failure
19 indication, the mobile station shall perform the following:
20 • If REDIRECTIONs is equal to enabled, the mobile station shall attempt to select
21 another system in accordance with the current redirection criteria (see 2.6.1.1.2). If
22 the mobile station is able to select another system, the mobile station shall attempt
23 to acquire the selected system (see 2.6.1.1.4). Otherwise, if the mobile station has
24 exhausted all possible selections using the current redirection criteria, the mobile
25 station shall perform the following:
26 – The mobile station shall set REDIRECTIONs to disabled.
27 – The mobile station shall set RETURN_CAUSEs to ‘0001’.
28 – If RETURN_IF_FAILs is equal to ‘1’, the mobile station shall attempt to select the
29 system from which it was redirected and shall attempt to acquire the selected
30 system (see 2.6.1.1.4). The precise process for determining how to select the
31 system from which the mobile station was redirected is left to the mobile station
32 manufacturer.
33 – If RETURN_IF_FAILs is equal to ‘0’, the mobile station shall select a system other
34 than the system from which it was redirected in accordance with the custom
35 system selection process (see 2.6.1.1.1) and shall attempt to acquire the selected
36 system (see 2.6.1.1.4). The precise process that the mobile station uses to avoid
37 selecting the system from which it was redirected is left to the mobile station
38 manufacturer.
2-45
3GPP2 C.S0005-A v6.0
1 • If REDIRECTIONs is equal to disabled, the mobile station shall select a system in

2 accordance with the custom system selection process (see 2.6.1.1.1) and shall
3 attempt to acquire the selected system (see 2.6.1.1.4).
4 If the mobile station enters the System Determination Substate with a new system
5 indication, the mobile station shall set REDIRECTIONs to disabled. If NDSS_ORIGs is
6 enabled, the mobile station shall set NDSS_ORIGs to disabled and should indicate to the
7 user that the call origination has been canceled. The mobile station shall select a system in
8 accordance with the custom system selection process (see 2.6.1.1.1) and shall attempt to
9 acquire the selected system (see 2.6.1.1.4).
10 If the mobile station enters the System Determination Substate with a CDMA available
13 user that the call origination is canceled. The mobile station should set CDMACHs to the
14 CDMA Channel (CDMA_FREQ) specified in the CDMA Capability Global Action Message and
15 should attempt to acquire a CDMA system on the specified CDMA channel (see 2.6.1.1.4).
16 If the mobile station does not attempt to acquire a CDMA system on the specified CDMA
17 Channel, the mobile station shall select a system in accordance with the custom system
18 selection process (see 2.6.1.1.1) and shall attempt to acquire the selected system (see
19 2.6.1.1.4).
20 If the mobile station enters the System Determination Substate with an additional CDMA
21 available indication, the mobile station shall set REDIRECTIONs to disabled. If
22 NDSS_ORIGs is enabled, the mobile station shall set NDSS_ORIGs to disabled and should
23 indicate to the user that the call origination is canceled. The mobile station should set
24 CDMACHs to the CDMA Channel (CDMA_FREQ) specified in the CDMA Info Order and
25 should attempt to acquire a CDMA system on the specified CDMA channel (see 2.6.1.1.4).
26 If the mobile station does not attempt to acquire a CDMA system on the specified CDMA
27 Channel, the mobile station shall select a system in accordance with the custom system
28 selection process (see 2.6.1.1.1) and shall attempt to acquire the selected system (see
29 2.6.1.1.4).
30 If the mobile station enters the System Determination Substate with a reselection indication,
31 the mobile station shall set REDIRECTIONs to disabled. If NDSS_ORIGs is enabled, the
32 mobile station shall set NDSS_ORIGs to disabled and should indicate to the user that the
33 call origination is canceled. The mobile station shall select a system in accordance with the
34 custom system selection process (see 2.6.1.1.1) and shall attempt to acquire the selected
35 system (see 2.6.1.1.4).
36 If the mobile station enters the System Determination Substate with an encryption failure
37 indication, the mobile station shall set REDIRECTIONs to disabled, ENC_KEYs to NULL,
38 D_SIG_ENCRYPT_MODEs to ‘000’ and C_SIG_ENCRYPT_MODEs to ‘000’. If NDSS_ORIGs is
40 user that the call origination is canceled. The mobile station shall select a system in
2-46
3GPP2 C.S0005-A v6.0
1 If the mobile station enters the System Determination Substate with a system reselection
4 user that the call origination is canceled. The mobile station should attempt to select a
5 system available for system reselection as specified in 2.6.1.1.3, and should attempt to
6 acquire the selected system (see 2.6.1.1.4). The precise process for determining how to
7 select such a system is left to the mobile station manufacturer. If the mobile station does
8 not attempt to select such a system, the mobile station shall select a system in accordance
9 with the custom system selection process (see 2.6.1.1.1) and shall attempt to acquire the
10 selected system (see 2.6.1.1.4).
11 If the mobile station enters the System Determination Substate with a rescan indication, the
12 mobile station shall set REDIRECTIONs to disabled. If NDSS_ORIGs is enabled, the mobile
13 station shall set NDSS_ORIGs to disabled and should indicate to the user that the call
14 origination is canceled. The mobile station shall select a system in accordance with the
16 system (see 2.6.1.1.4).
17 If the mobile station enters the System Determination Substate with a protocol mismatch
31 manufacturer.
35 system (see 2.6.1.1.4). The precise process for determining how to avoid the
37 manufacturer.
41 If the mobile station enters the System Determination Substate with a system lost indication,
2-47
3GPP2 C.S0005-A v6.0
2 call origination is canceled. The mobile station should attempt to select the same system
3 that was lost, and should attempt to acquire the selected system (see 2.6.1.1.4). The
4 precise process for determining how to select the same system is left to the mobile station
5 manufacturer. If the mobile station does not attempt to select the same system, the mobile
6 station shall select a system in accordance with the custom system selection process (see
7 2.6.1.1.1) and shall attempt to acquire the selected system (see 2.6.1.1.4).
8 If the mobile station enters the System Determination Substate with a lock indication, the
13 system (see 2.6.1.1.4).
14 If the mobile station enters the System Determination Substate with an unlock indication,
19 system (see 2.6.1.1.4).
20 If the mobile station enters the System Determination Substate with an access denied
23 user that the call origination is canceled. The mobile station shall select a system in
26 If the mobile station enters the System Determination Substate with an ACCT blocked
28 enabled, the mobile station shall set NDSS_ORIGs to disabled. The mobile station shall
29 select a system in accordance with the custom system selection process (see 2.6.1.1.1) and
30 shall attempt to acquire the selected system (see 2.6.1.1.4).
31 If the mobile station enters the System Determination Substate with an NDSS off indication,
36 system (see 2.6.1.1.4).
37 If the mobile station enters the System Determination Substate with a release indication and
38 REDIRECTIONs is equal to enabled, the mobile station shall attempt to select the same
39 system on which the release occurred and shall attempt to acquire the selected system (see
40 2.6.1.1.4). The precise process for determining how to select the same system is left to the
41 mobile station manufacturer. If REDIRECTIONs is equal to disabled, the mobile station
42 shall select a system in accordance with the custom system selection process (see 2.6.1.1.1)
2-48
3GPP2 C.S0005-A v6.0
1 and shall attempt to acquire the selected system (see 2.6.1.1.4). If NDSS_ORIGs is enabled,
2 the mobile station shall set NDSS_ORIGs to disabled.
3 If the mobile station enters the System Determination Substate with an error indication, the
8 system (see 2.6.1.1.4).
9 If the mobile station enters the System Determination Substate with a redirection indication,
10 the mobile station shall set REDIRECTIONs to enabled. The mobile station shall delete all
11 entries from the ZONE_LISTs and SID_NID_LISTs. The mobile station shall select a system
12 in accordance with the current redirection criteria (see 2.6.1.1.2) and shall attempt to
14 If the mobile station enters the System Determination Substate with a registration rejected
16 • The mobile station shall delete the newly generated encryption key (if any).
17 • If REDIRECTIONs is equal to enabled, the mobile station shall perform the following:
24 manufacturer.
30 manufacturer.
34 If the mobile station enters the System Determination Substate with a wrong system
2-49
3GPP2 C.S0005-A v6.0
7 manufacturer.
13 manufacturer.
17 If the mobile station enters the System Determination Substate with a wrong network
31 manufacturer.
37 manufacturer.
2-50
3GPP2 C.S0005-A v6.0
1 2.6.1.1.1 Custom System Selection Process
2 The precise process for custom system selection is left to the mobile station manufacturer.
3 The mobile station shall perform the custom system selection process as follows:
4 • The mobile station shall determine which system to use.

5 • If the mobile station is to use a CDMA system, it shall set CDMABANDs to the band
6 class (see [30]) for the selected system.
7 • If the mobile station is to use a CDMA system with CDMABANDs = ‘00000’ or
8 CDMABANDs = ‘00011’, it shall perform the following:
9 – If the mobile station is to use System A, it shall set SERVSYSs to SYS_A. If the
10 mobile station is to use System B, it shall set SERVSYSs to SYS_B.
11 – The mobile station shall set CDMACHs either to the Primary or Secondary CDMA
12 Channel number (see 2.1.1.1.1 of [2]) for the selected serving system
13 (SERVSYSs). If the mobile station fails to acquire a CDMA system on the first
14 CDMA Channel it tries, the mobile station should attempt to acquire on the
15 alternate CDMA Channel (Primary or Secondary) before attempting other
16 alternatives.
17 • If the mobile station is to use a CDMA system with CDMABANDs other than ‘00000’
18 or ‘00011’,= ‘00001’, CDMABANDs = ‘00010’, CDMABANDs = ‘00100’, CDMABANDs
19 = ‘00101’, CDMABANDs = ‘00110’, CDMABANDs = ‘00111’, CDMABANDs = ‘01000’,
20 or CDMABANDs = ‘01001’ it shall set CDMACHs to the CDMA Channel number (see
21 2.1.1.1.1 of [2]) for the selected system.
22 If the mobile station is to use System A of the 800 MHz analog system, it shall set
23 SERVSYSs to SYS_A. If the mobile station is to use System B of the 800 MHz analog
24 system, it shall set SERVSYSs to SYS_B.
25 2.6.1.1.2 System Selection Using Current Redirection Criteria
26 To perform system selection using current redirection criteria, the mobile station shall use
27 information received either in a Service Redirection Message, a Global Service Redirection
28 Message, or an Extended Global Service Redirection Message and stored in the variable
29 REDIRECT_RECs.
30 If the RECORD_TYPE field of REDIRECT_RECs is equal to ‘00000001’ and the mobile

31 station supports Band Class 0, the mobile station shall perform system selection as follows:
32 • If the SYS_ORDERING field is equal to ‘000’, the mobile station shall make
33 sequential system selections as follows:
34 – The mobile station shall set SERVSYSs either to SYS_A or SYS_B. The precise
35 process for determining how many system selections to make and for
36 determining whether to use SYS_A or SYS_B is left to the mobile station
37 manufacturer.
38 • If the SYS_ORDERING field is equal to ‘001’, the mobile station shall select no more
39 than one system selection as follows:
2-51
3GPP2 C.S0005-A v6.0
1 – The mobile station shall set SERVSYSs to SYS_A.
2 • If the SYS_ORDERING field is equal to ‘010’, the mobile station shall select no more
3 than one system selection as follows:
4 – The mobile station shall set SERVSYSs to SYS_B.
5 • If the SYS_ORDERING field is equal to ‘011’, the mobile station shall make at most
6 two sequential system selections as follows:
7 – For the first system selection, the mobile station shall set SERVSYSs to SYS_A.
8 – For the second system selection, the mobile station shall set SERVSYSs to
9 SYS_B.
10 • If the SYS_ORDERING field is equal to ‘100’, the mobile station shall make at most 2
12 – For the first system selection, the mobile station shall set SERVSYSs to SYS_B.
14 SYS_A.
15 • If the SYS_ORDERING field is equal to ‘101’, the mobile station shall make at most 2
17 – For the first system selection, the mobile station shall set SERVSYSs either to
18 SYS_A or SYS_B. The precise process for determining whether to use SYS_A or
19 SYS_B first is left to the mobile station manufacturer.
21 SYS_B if SYS_A was used for the first selection, or to SYS_A if SYS_B was used
22 for the first selection.
23 If the RECORD_TYPE field of REDIRECT_RECs is equal to ‘00000010’, the mobile station
24 shall perform system selection as follows:
25 • If the mobile station supports CDMA mode operation in the band class identified by
26 the BAND_CLASS field, the mobile station shall make at most n sequential system
27 selections, where n is equal to the value of the NUM_CHANS field, as follows:
28 – For the ith system selection, where i ranges from 1 to n, if the mobile station
29 supports operation on the CDMA channel associated with the value of the ith
30 occurrence of the CDMA_CHAN field, the mobile station shall set CDMACHs to
31 the value of the ith occurrence of the CDMA_CHAN field and shall set
32 CDMABANDs to the value specified in the BAND_CLASS field. If the mobile
33 station does not support operation on the CDMA Channel associated with the
34 value of the ith occurrence of the CDMA_CHAN field, the mobile station shall not
35 make the ith system selection.
36 2.6.1.1.3 System Selection Using System Reselection Criteria
37 The precise process for selecting a system using system reselection criteria is left to the
38 mobile station manufacturer. The mobile station should use information received in the
2-52
3GPP2 C.S0005-A v6.0
1 Neighbor List Message, Extended Neighbor List Message, General Neighbor List Message, or
2 the Universal Neighbor List Message to perform the system reselection process as follows:
3 • If there are pilots in the Neighbor List on a different Frequency Assignment than
4 that of the mobile station, the mobile station may select the CDMA system
5 consisting of these neighbor pilots. If the mobile station is to use a CDMA system, it
6 shall set CDMABANDs to the band class (see [30]) for the selected system and shall
7 set CDMACHs to the CDMA Channel number (see 2.1.1.1 of [2]) for the selected
8 system.
9 • If NUM_ANALOG_NGHBRs is not equal to ‘000’, the mobile station may select an
10 analog system as specified by ANALOG_NGHBR_LIST. If the mobile station is to use
11 System A of the 800 MHz analog system, it shall set SERVSYSs to SYS_A. If the
12 mobile station is to use System B of the 800 MHz analog system, it shall set
13 SERVSYSs to SYS_B.
14 2.6.1.1.4 Acquiring the Selected System
15 The mobile station shall attempt to acquire the selected system as follows:
16 • If the selected system is an analog system, the mobile station shall enter the
17 Initialization Task (see 2.6.1 of [6]).
18 • If the selected system is a CDMA system, the mobile station shall enter the Pilot
19 Channel Acquisition Substate.
20 2.6.1.2 Pilot Channel Acquisition Substate
21 In this substate, the mobile station acquires the Pilot Channel of the selected CDMA
22 system.
23 Upon entering the Pilot Channel Acquisition Substate, the mobile station shall tune to the
24 CDMA Channel number equal to CDMACHs, shall set its code channel for the Pilot Channel
25 (see 3.1.3.1.10 of [2]) and shall search for the Pilot Channel for no longer than T20m
26 seconds (see Annex D). If the mobile station acquires the Pilot Channel, the mobile station
27 shall enter the Sync Channel Acquisition Substate.
28 If the mobile station determines that it is unlikely to acquire the Pilot Channel within T20m
29 seconds, the mobile station may enter the System Determination Substate with an
30 acquisition failure indication (see 2.6.1.1). The time, to either acquire the Pilot Channel or
31 determine that Pilot Channel acquisition is unlikely, shall not exceed T20m seconds (see
32 Annex D), after which the mobile station shall enter the System Determination Substate with
33 an acquisition failure indication (see 2.6.1.1).
34 2.6.1.3 Sync Channel Acquisition Substate
35 In this substate, the mobile station receives and processes the Sync Channel Message to
36 obtain system configuration and timing information.
37 Upon entering the Sync Channel Acquisition Substate, the mobile station shall set its code
38 channel for the Sync Channel (see [2]).
2-53
3GPP2 C.S0005-A v6.0
1 If the mobile station does not receive a valid Sync Channel Message within T21m seconds,
2 the mobile station shall enter the System Determination Substate with an acquisition failure
3 indication.
4 If the mobile station receives a valid Sync Channel Message within T21m seconds, but the
5 protocol revision level supported by the mobile station (MOB_P_REVp of the current band
6 class) is less than the minimum protocol revision level supported by the base station
7 (MIN_P_REVr), the mobile station shall enter the System Determination Substate with a
8 protocol mismatch indication (see 2.6.1.1).
9 If the mobile station receives a valid Sync Channel Message within T21m seconds, but the
10 values of the PRATr, the SR1_BRAT_NON_TDr, the SR1_BRAT_TDr, or the SR3_BRATr fields
11 are designated as reserved by the protocol revision level supported by the mobile station
12 (MOB_P_REVp of the current band class), the mobile station shall enter the System
13 Determination Substate with a protocol mismatch indication (see 2.6.1.1).
14 If the mobile station receives a valid Sync Channel Message within T21m seconds and the
15 protocol revision level supported by the mobile station (MOB_P_REVp of the current band
16 class) is greater than or equal to the minimum protocol revision level supported by the base
17 station (MIN_P_REVr), the mobile station shall store the following information from the
18 message:
19 • Protocol revision level (P_REVs = P_REVr)
20 • Minimum protocol revision level (MIN_P_REVs = MIN_P_REVr)
21 • System identification (SIDs = SIDr)
22 • Network identification (NIDs = NIDr)
23 • Pilot PN sequence offset index (PILOT_PNs = PILOT_PNr)
24 • Long code state (LC_STATEs = LC_STATEr)
25 • System Time (SYS_TIMEs = SYS_TIMEr)
26 • Paging Channel data rate (PRATs = PRATr)
27 • Protocol revision level currently in use (P_REV_IN_USEs = the lesser value of P_REVs
28 and MOB_P_REVp of the current band class)
29 SR1 Non-TD BCCH support indicator (SR1_BCCH_SUPPORTEDsNON_TD_INCLs =

30 SR1_BCCH_SUPPORTEDrNON_TD_INCLr)
31 SR1 TD BCCH support indicator (SR1_TD_INCLs = SR1_ TD_INCLr)
32 If SR1_BCCH_NON_TD_INCLSUPPORTEDr is equal to ‘1’:
33 − SR1_BRAT_NON_TDs = SR1_BRAT_NON_TDr;
34 – SR1_CRAT_NON_TDs = SR1_CRAT_NON_TDr;
35 − BCCH_CODE_CHAN_NON_TDs= SR1_BCCH_CODE_CHAN_NON_TDr.
2-54
3GPP2 C.S0005-A v6.0
1 If SR1_TD_INCLr is included and is equal to ‘1’ the mobile station supports the
2 Transmit Diversity indicated by SR1_TD_MODEr, SR1_TD_INCLr is included and is
3 equal to ‘1’:
4 − SR1_BRAT_TDs = SR1_BRAT_TDr;
5 – SR1_CRAT_TDs = SR1_CRAT_TDr;
6 − BCCH_CODE_CHAN_TDs = SR1_BCCH_ CODE_CHAN _TDr.
7 If the mobile station supports the Transmit Diversity, SR1_BCCH_NON_TD_INCLr is

8 equal to ‘1’, and SR1_TD_INCLr is equal to ‘0’:
9 − SR1_BRAT_TDs = SR1_BRAT_NON_TDr;
10 − SR1_CRAT_TDs = SR1_CRAT_NON_TDr;
11 − BCCH_CODE_CHAN_TDs = SR1_BCCH_CODE_CHAN_NON_TDr.
12 SR3 support indicator (SR3_INCLs = SR3_INCLr)
13 The mobile station shall ignore any fields at the end of the Sync Channel Message that are
14 not defined according to the protocol revision level (MOB_P_REVp of the current band class)
15 being used by the mobile station.
16 The mobile station may store the following information from the message:
17 • Number of leap seconds that have occurred since the start of System Time
18 (LP_SECs = LP_SECr)
19 • Offset of local time from System Time (LTM_OFFs = LTM_OFFr)
20 • Daylight savings time indicator (DAYLTs = DAYLTr)
21 If REDIRECTIONs and NDSS_ORIGs are equal to disabled, the mobile station may enter the
22 System Determination Substate with a reselection indication (see 2.6.1.1).
23 If REDIRECTIONs is equal to enabled, the EXPECTED_SID field of REDIRECT_RECs is not
24 equal to 0, and SIDr is not equal to EXPECTED_SID, the mobile station shall enter the
25 System Determination Substate with a wrong system indication (see 2.6.1.1). If
26 REDIRECTIONs is equal to enabled, the EXPECTED_NID field of REDIRECT_RECs is not
27 equal to 65535, and NIDr is not equal to EXPECTED_NID, the mobile station shall enter the
28 System Determination Substate with a wrong network indication.
29 If P_REV_IN_USEs is less than 6, the mobile station shall set POTENTIAL_CDMACHs to
30 CDMA_FREQr.
31 If P_REV_IN_USEs is equal to six, and the mobile station shall perform the following:
32 • If the mobile station supports the Quick Paging Channel or any radio configuration
33 in the Radio Configuration Class 2 or 3 (see 1.1.1), the mobile station shall set
34 POTENTIAL_CDMACHs equal to EXT_CDMA_FREQr; otherwise, the mobile station
35 shall set POTENTIAL_CDMACHs equal to CDMA_FREQr.
36 If P_REV_IN_USEs is greater than six, the mobile station shall perform the following:
37 If the mobile station supports Spreading Rate 3 on the common channels and
2-55
3GPP2 C.S0005-A v6.0
1 SR3_INCLs is equal to ‘1’, the mobile station shall set:
2 − BRATs = SR3_BRATr;
3 – BCCH_CODE_RATEs = 1/3;
4 − BCCHs = SR3_BCCH_ CODE_CHANr;
5 − SR3_PRIMARY_PILOTs = SR3_PRIMARY_PILOTr;
6 − SR3_PILOT_POWER1s = SR3_PILOT_POWER1r;
7 − SR3_PILOT_POWER2s = SR3_PILOT_POWER2r;
8 − If SR3_CENTER_FREQ_INCLr is equal to ‘1’, POTENTIAL_CDMACHs =

9 SR3_CENTER_FREQr; otherwise, POTENTIAL_CDMACHs = EXT_CDMA_FREQr.
10 If the mobile station does not support Spreading Rate 3 on the common channel or
11 if SR3_INCLs is equal to ‘0’, the mobile station shall perform the following:
12 −If SR1_BCCH_SUPPORTEDs is equal to ‘1’, the mobile station shall perform the
13 following:
14 − If SR1_TD_INCLr is equal to ‘1’ and the mobile station supports the Transmit
15 Diversity mode specified by SR1_TD_MODEr, the mobile station shall set:
16 +If SR1_TD_INCLr is equal to ‘1’ and the mobile station supports the Transmit
17 Diversity mode specified by SR1_TD_MODEr, the mobile station shall set:
18 + SR1_TD_MODEs = SR1_TD_MODEr
19 + SR1_TD_POWER_LEVELs = SR1_TD_POWER_LEVELr
20 + BRATs = SR1_BRAT_TDr
21 + BCCH_CODE_RATEs = SR1_CRAT_TDr,
22 + BCCHs = SR1_BCCH_ CODE_CHAN _TDr,
23 + POTENTIAL_CDMACHs = SR1_CDMA_FREQ_TDr
24 − Otherwise, if SR1_BCCH_NON_TD_INCLr is equal to ‘1’, the mobile station shall

25 set:
26 +If SR1_TD_INCLr is equal to ‘0’, or if SR1_TD_INCLr is equal to ‘1’ and the
27 mobile station does not support the Transmit Diversity mode specified by
28 SR1_TD_MODEr, the mobile station shall set:
29 + BRATs = SR1_BRAT_NON_TDr
30 + BCCH_CODE_RATEs = SR1_CRAT_NON_TDr,
31 + BCCHs = SR1_BCCH_ CODE_CHAN _NON_TDr,
32 + If SR1_NON_TD_FREQ_INCLr is equal to ‘1’, POTENTIAL_CDMACHs =

33 SR1_CDMA_FREQ_NON_TDr; otherwise, POTENTIAL_CDMACHs =
34 EXT_CDMA_FREQr
35 − If OtherwiseSR1_BCCH_SUPPORTEDs is equal to ‘0’, the mobile station shall
2-56
3GPP2 C.S0005-A v6.0
1 perform the following:
2 + If the mobile station supports the Quick Paging Channel or any radio
3 configuration in the Radio Configuration Class 2 or 3 (see 1.1.1), the mobile
4 station shall set POTENTIAL_CDMACHs = EXT_CDMA_FREQr; otherwise, the
5 mobile station shall set POTENTIAL_CDMACHs = CDMA_FREQr.
6 If POTENTIAL_CDMACHs is different from CDMACHs, the mobile station shall set

7 CDMACHs = POTENTIAL_CDMACHs and then tune to the CDMA Channel (CDMACHs).
8 The mobile station shall enter the Timing Change Substate.
9 2.6.1.4 Timing Change Substate
10 Figure 2.6.1.4-1 illustrates the mobile station timing changes that occur in this substate.
11 The mobile station synchronizes its long code timing and system timing to those of the
12 CDMA system, using the PILOT_PNs, LC_STATEs, and SYS_TIMEs values obtained from the
13 received Sync Channel Message. SYS_TIMEs is equal to the System Time (see 1.3 of [2])
14 corresponding to 320 ms past the end of the last 80 ms superframe (see Figure 3.1.3.2.1-1
15 of [2]) of the received Sync Channel Message minus the pilot PN sequence offset.
16 LC_STATEs is equal to the system long code state (see 2.1.3.1.12 of [2]) corresponding to
17 SYS_TIMEs.
18 In the Timing Change Substate, the mobile station shall synchronize its long code timing to
19 the CDMA system long code timing derived from LC_STATEs, and synchronize its system
20 timing to the CDMA system timing derived from SYS_TIMEs.
21 The mobile station shall perform the following:

22 • If SR1_BCCH_NON_TD_INCLs SR1_BCCH_SUPPORTEDs is equal to ‘1’, or if
23 SR1_TD_INCLs is equal to ‘1’ and the mobile supports the transmit diversity mode
24 specified by SR1_TD_MODEs, or if the mobile station supports Spreading Rate 3 on
25 the common channel and SR3_INCLs is equal to ‘1’, the mobile station shall:
26 – Set the stored message sequence numbers CONFIG_MSG_SEQs,

27 A41_SYS_PAR_MSG_SEQs, ACC_MSG_SEQs, MC_RR_PAR_MSG_SEQs,
28 UNI_NGHBR_LST_MSG_SEQs, EXT_GLOB_SERV_REDIR_MSG_SEQs,
29 EXT_CHAN_LST_MSG_SEQs, USER_ZONE_ID_MSG_SEQs and
30 PRI_NGHBR_LST_MSG_SEQs variables to NULL (see 2.6.2.2);
31 – Set the index number of the Primary Broadcast Control Channel (BCN) to 1;
32 – Set IMSI_11_12s and MCCs to NULL;
33 – Perform registration initialization as specified in 2.6.5.5.1.3; and

34 – If the bits of TMSI_CODEs-p are not all equal to ‘1’ and if SYS_TIMEs exceeds
35 TMSI_EXP_TIMEs-p × 212, the mobile station shall set all the bits of
36 TMSI_CODEs-p to ‘1’.
37 • Otherwise, the mobile station shall:

38 – Set PAGECHs to the Primary Paging Channel (see 3.1.3.4 of [2]);
2-57
3GPP2 C.S0005-A v6.0
1 – Set PAGE_CHANs to ‘1’;
2 – Set the stored message sequence numbers CONFIG_MSG_SEQs,

3 SYS_PAR_MSG_SEQs, ACC_MSG_SEQs, NGHBR_LST_MSG_SEQs,
4 GEN_NGHBR_LST_MSG_SEQs, EXT_NGHBR_LST_MSG_SEQs,
5 CHAN_LST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs,
6 GLOB_SERV_REDIR_MSG_SEQs, EXT_GLOB_SERV_REDIR_MSG_SEQs,
7 EXT_CHAN_LST_MSG_SEQs, USER_ZONE_ID_MSG_SEQs and
8 PRI_NGHBR_LST_MSG_SEQs variables to NULL (see 2.6.2.2);
9 – Set IMSI_11_12s and MCCs to NULL;
10 – Perform registration initialization as specified in 2.6.5.5.1.3; and

11 – If the bits of TMSI_CODEs-p are not all equal to ‘1’ and if SYS_TIMEs exceeds
12 TMSI_EXP_TIMEs-p × 212, the mobile station shall set all the bits of
14 The mobile station shall enter the Mobile Station Idle State.
26.667 ms
Time specified in
Sync Channel
Message
System Time
showing zero
shift pilot
rollover
Pilot PN
Sequence
Offset
Sync Channel
Sync Channel
Message Sync Channel
Superframe
80ms
320 ms
15
16
17 Figure 2.6.1.4-1. Mobile Station Internal Timing
2-58
3GPP2 C.S0005-A v6.0
2-59
3GPP2 C.S0005-A v6.0
1 2.6.2 Mobile Station Idle State
2 In this state, the mobile station monitors the Paging Channel or the Quick Paging Channel
3 or Forward Common Control Channel/Primary Broadcast Control Channel. The mobile
4 station can receive messages, receive an incoming call (mobile station terminated call),
5 initiate a call (mobile station originated call), cancel a PACA call, initiate a registration, or
6 initiate a message transmission.
7 The mobile station may monitor the Quick Paging Channel to determine if it should receive
8 messages from the Paging Channel or Forward Common Control Channel.
9 Upon entering the Mobile Station Idle State from the Mobile Station Initialization State, the
10 mobile station shall perform the following:
11 • If SR1_BCCH_NON_TD_INCLs SR1_BCCH_SUPPORTEDs is equal to ‘1’, or if
12 SR1_TD_INCLs is equal to ‘1’ and the mobile station supports the transmit diversity
13 mode specified by SR1_TD_MODEs, or if the mobile station supports Spreading Rate
14 3 on the common channel and SR3_INCLs is equal to ‘1’, the mobile station shall
16 – Set its Primary Broadcast Control Channel code channel to BCCHs,
17 – Set the Primary Broadcast Control Channel data rate as determined by BRATs,
18 – Set the Primary Broadcast Control Channel code rate as determined by

19 BCCH_CODE_RATEs,
20 – Set SLOTTEDs to YES if T_SLOTTEDs is equal to ‘00000000’ or if the mobile

21 station does not support the slotted timer; otherwise enable the TMS_Slotted
22 timer with the duration specified by T_SLOTTEDs and set SLOTTEDs to NO, and
23 – Perform common channel supervision as specified in 2.6.2.1.1.4.
24 • Otherwise, the mobile station shall perform the following:

25 – Set its code channel to PAGECHs,
26 – Set the Paging Channel data rate as determined by PRATs,
27 – Set SLOTTEDs to YES if T_SLOTTEDs is equal to ‘00000000’ or if the mobile

28 station does not support the slotted timer; otherwise enable the TMS_Slotted
29 timer with the duration specified by T_SLOTTEDs and set SLOTTEDs to NO, and
30 – Perform Paging Channel supervision as specified in 2.6.2.1.1.4.

31 If REDIRECTIONs, PACAs, and NDSS_ORIGs are equal to disabled, the mobile station may
32 exit the Mobile Station Idle State at any time and enter the System Determination Substate of
33 the Mobile Station Initialization State with a reselection indication (see 2.6.1.1).
34 While in the Mobile Station Idle State, the mobile station shall perform the following
35 procedures:
36 • The mobile station shall perform Paging Channel or Forward Common Control
37 Channel monitoring procedures as specified in 2.6.2.1.1.
2-60
3GPP2 C.S0005-A v6.0
1 • The mobile station shall perform message acknowledgment procedures as specified

2 in 2.1.1.2 and 2.1.2.1 of [4].
3 • The mobile station shall perform registration procedures as specified in 2.6.2.1.3.
4 • The mobile station shall perform idle handoff procedures as specified in 2.6.2.1.4.
5 • The mobile station shall perform system reselection procedures as specified in

6 2.6.2.1.6.
7 • The mobile station shall perform the Response to Overhead Information Operation as
8 specified in 2.6.2.2 whenever the mobile station receives a system overhead message
9 (ANSI-41 System Parameters Message, Enhanced Access Parameters Message,
10 Extended CDMA Channel List Message, MC-RR Parameters Message, Universal
11 Neighbor List Message, ANSI-41 RAND Message, System Parameters Message, CDMA
12 Channel List Message, Extended System Parameters Message, Neighbor List Message,
13 Extended Neighbor List Message, General Neighbor List Message, Global Service
14 Redirection Message, Extended Global Service Redirection Message, User Zone
15 Identification Message, Private Neighbor List Message, or Access Parameters
16 Message).
17 • The mobile station shall perform the Mobile Station Page Match Operation as
18 specified in 2.6.2.3 whenever it receives a mobile station-directed page.
19 • The mobile station shall perform the Mobile Station Order and Message Processing
20 Operation as specified in 2.6.2.4 whenever a message or order directed to the mobile
21 station is received other than a mobile station-directed page.
22 • The mobile station shall set NDSS_ORIGs to disabled if directed by the user to
23 cancel the call origination.
24 • The mobile station shall perform the Mobile Station Origination Operation as specified
25 in 2.6.2.5 if directed by the user to initiate a call, or if NDSS_ORIGs is equal to
26 enabled.
27 • The mobile station shall not send any subsequent Origination Message containing
28 the same packet data service option until the system time stored in
29 RETRY_DELAYs[001]. At the system time stored in RETRY_DELAYs[001], the mobile
30 station shall reset RETRY_DELAYs[001] to 0.
31 • The mobile station shall perform the Mobile Station PACA Cancel Operation as
32 specified in 2.6.2.8, if PACAs is equal to enabled and any one of the following
33 conditions is met:
34 – PACA_CANCEL is equal to ‘1’; or
35 – The mobile station is directed by the user to cancel the PACA call.
36 • If the PACA state timer expires, the mobile station shall perform the following:
37 – The mobile station should enter the Update Overhead Information Substate of the
38 System Access State (see 2.6.3) with an origination indication within T33m
39 seconds to re-originate the PACA call.
2-61
3GPP2 C.S0005-A v6.0
1 – Otherwise, the mobile station shall perform the Mobile Station PACA Cancel
2 Operation as specified in 2.6.2.8.
3 • If the mobile station supports Data Burst Message transmission, it shall perform the
4 Mobile Station Message Transmission Operation as specified in 2.6.2.6 if directed by
5 the user to transmit a message.
6 • If the mobile station supports the Device Information Message on the r-csch,
7 AUTO_MSG_SUPPORTEDs is equal to ‘1’, and the mobile station has detected a
8 change in hook status since the last time when the mobile station sent hook status
9 information, the mobile station shall perform the following:
10 – If the autonomous message timer has expired or is disabled, the mobile station
11 shall perform the Mobile Station Message Transmission Operation as specified in
12 2.6.2.6.
13 – If the autonomous message timer has not expired, the mobile station shall set
14 the autonomous message timer equal to AUTO_MSG_INTERVALs and shall
15 restart the timer.
16 • The mobile station shall perform the Mobile Station Power-Down Operation as
17 specified in 2.6.2.7 if directed by the user to power down.
18 • If the bits of TMSI_CODEs-p are not all equal to ‘1’ and if System Time (in 80 ms
19 units) exceeds TMSI_EXP_TIMEs-p × 212, the mobile station shall set all the bits of
20 TMSI_CODEs-p to ‘1’ within T66m seconds.
21 • If the full-TMSI timer expires or has expired, the mobile station shall set all the bits
22 of TMSI_CODEs-p to ‘1’. The mobile station shall update the registration variables
23 as described in 2.6.5.5.2.5.
24 2.6.2.1 Idle Procedures
25 2.6.2.1.1 Forward Channel Monitoring Procedures
26 2.6.2.1.1.1 General Overview
27 The Paging Channel is divided into 80 ms slots called Paging Channel slots. Paging and
28 control messages for a mobile station operating in the non-slotted mode can be received in
29 any of the Paging Channel slots; therefore, the non-slotted mode of operation requires the
30 mobile station to monitor all slots.
31 The Forward Common Control Channel is divided into 80 ms slots called Forward Common
32 Control Channel slots. Paging and mobile directed messages for a mobile station operating
33 in the non-slotted mode can be received in any of the Forward Common Control Channel
34 slots. The overhead messages can be received on the Primary Broadcast Control Channel.
35 Therefore, the non-slotted mode of operation requires the mobile station to continuously
36 monitor the Forward Common Control Channel/Primary Broadcast Control Channel.
2-62
3GPP2 C.S0005-A v6.0
1 2.6.2.1.1.1.1 General Overview for Individually Addressed Messages
2 The Paging Channel or the Forward Common Control Channel protocol provides for
3 scheduling the transmission of messages for a specific mobile station in certain assigned
4 slots. Support of this feature is optional and may be enabled by each mobile station. A
5 mobile station that monitors the Paging Channel or the Forward Common Control Channel
6 only during certain assigned slots is referred to as operating in the slotted mode. During
7 the slots in which the Paging Channel or the Forward Common Control Channel is not
8 being monitored, the mobile station can stop or reduce its processing for power
9 conservation. A mobile station may not operate in the slotted mode in any state except the
10 Mobile Station Idle State.
11 A mobile station operating in the slotted mode generally monitors the Paging Channel or the
12 Forward Common Control Channel for one or two slots per slot cycle. The mobile station
13 can specify its preferred slot cycle using the SLOT_CYCLE_INDEX field in the Registration
14 Message, Origination Message, or Page Response Message. The mobile station can also
15 specify its preferred slot cycle using the SLOT_CYCLE_INDEX field of the Terminal
16 Information record of the Status Response Message or the Extended Status Response
17 Message. In addition, the mobile station can also specify its preferred slot cycle using the
18 SLOT_CYCLE_INDEX field of the Terminal Information record of the Status Response
19 Message or the Status Message when in the Mobile Station Control on the Traffic Channel
20 State. The length of the slot cycle, T, in units of 1.28 seconds,1 is given by
21 T = 2i,
22 where i is the selected slot cycle index (see 2.6.2.1.1.3).
23 A mobile station operating in the slotted mode may optionally monitor additional slots to
24 receive broadcast messages and/or broadcast pages (see 2.6.2.1.1.3.3 and 2.6.2.1.1.3.4).
25 There are 16 × T slots in a slot cycle.
26 SLOT_NUM is the Paging Channel or the Forward Common Control Channel slot number,
27 modulo the maximum length slot cycle (2048 slots). That is, the value of SLOT_NUM is
28 SLOT_NUM = t/4 mod 2048,
29 where t is the System Time in frames. For each mobile station, the starting times of its slot
30 cycles are offset from the slot in which SLOT_NUM equals zero by a fixed, randomly selected
31 number of slots as specified in 2.6.2.1.1.3.
32 Figure 2.6.2.1.1.1-1 shows an example for a slot cycle length of 1.28 seconds, in which the
33 computed value of PGSLOT (see 2.6.2.1.1.3) is equal to 6, so that one of the mobile station’s
34 slot cycles begins when SLOT_NUM equals 6. The mobile station begins monitoring the
35 Paging Channel or the Forward Common Control Channel at the start of the slot in which
36 SLOT_NUM equals 6. The next slot in which the mobile station must begin monitoring the
1 The minimum length slot cycle consists of 16 slots of 80 ms each, hence 1.28 seconds.
2-63
3GPP2 C.S0005-A v6.0
1 Paging Channel or the Forward Common Control Channel is 16 slots later, i.e., the slot in
2 which SLOT_NUM is 22.
System Time
1.28 seconds
2047 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
PCH/F-CCCH Slots
Mobile Station PCH/F-CCCH Slot Mobile Station

in Non-Active in Non-Active
State A 6 State
80 ms
A - Reacquisition of CDMA System

3 6 - Mobile Station's Assigned PCH/F-CCCH Slot
4 Figure 2.6.2.1.1.1-1. Mobile Station Idle Slotted Mode Structure Example
6 2.6.2.1.1.1.1.1 Overview of Stopping Monitoring via the General Page Message
7 Layer 3 determines when a mobile station operating in the slotted mode may stop
8 monitoring the Paging Channel or the Forward Common Control Channel based upon
9 indications received from Layer 2 (see 2.1.2.2.2.4.1 of [4]). When the General Page Message
10 is used, Layer 2 determines whether there is an address mismatch or a broadcast address
11 mismatch, based upon the address information received in the General Page Message.
12 Based upon the address mismatch and broadcast address mismatch indications received
13 from Layer 2, Layer 3 can determine when no further messages or records addressed to an
14 individual mobile station will be present in the slot.
15 A General Page Message contains four fields: CLASS_0_DONE, CLASS_1_DONE,
16 TMSI_DONE, and ORDERED_TMSIS, which indicate when a mobile station operating in the
17 slotted mode may stop monitoring the Paging Channel or the Forward Common Control
18 Channel.
19 When CLASS_0_DONE is set to ‘1’ during a mobile station’s assigned slot and the mobile
20 station is operating in the slotted mode, no further messages or records addressed by a
21 class 0 IMSI will be directed to the mobile station during the current slot. When
22 CLASS_1_DONE is set to ‘1’ during a mobile station’s assigned slot and the mobile station is
23 operating in the slotted mode, no further messages or records addressed by a class 1 IMSI
24 will be directed to the mobile station during the current slot. Similarly, when TMSI_DONE
25 is set to ‘1’ during a mobile station’s assigned slot and the mobile station is operating in the
2-64
3GPP2 C.S0005-A v6.0
1 slotted mode, no further messages or records addressed by a TMSI will be directed to the
2 mobile station during the current slot.
3 The field ORDERED_TMSIS, when set to ‘1’ during a mobile station’s assigned slot,
4 indicates that the base station has ordered TMSI page records directed to mobile stations
5 operating in the slotted mode so that the resulting TMSI_CODE values are in ascending
6 order in the General Page Messages in the slot.
7 A mobile station which is operating in the slotted mode, has a class 0 IMSI assigned, and
8 does not have a TMSI assigned (all the bits of TMSI_CODEs-p are equal to ‘1’), may stop
9 monitoring the Paging Channel or the Forward Common Control Channel after processing a
10 General Page Message containing CLASS_0_DONE equal to ‘1’. Similarly, a mobile station
11 which is operating in the slotted mode, has a class 1 IMSI assigned, and does not have a
12 TMSI assigned (all the bits of TMSI_CODEs-p are equal to ‘1’), may stop monitoring the
13 Paging Channel or the Forward Common Control Channel after processing a General Page
14 Message containing CLASS_1_DONE equal to ‘1’.
15 A mobile station which is operating in the slotted mode, has a class 0 IMSI assigned, and
16 has a TMSI assigned (the bits of TMSI_CODEs-p are not all equal to ‘1’), may stop
17 monitoring the Paging Channel or the Forward Common Control Channel after processing a
18 General Page Message containing both CLASS_0_DONE equal to ‘1’ and TMSI_DONE equal
19 to ‘1’. Similarly, a mobile station which is operating in the slotted mode, has a class 1 IMSI
20 assigned, and has a TMSI assigned (the bits of TMSI_CODEs-p are not all equal to ‘1’), may
21 stop monitoring the Paging Channel or the Forward Common Control Channel after
22 processing a General Page Message containing both CLASS_1_DONE equal to ‘1’ and
23 TMSI_DONE equal to ‘1’.
24 If ORDERED_TMSIS is equal to ‘1’ and CLASS_0_DONE is equal to ‘1’, a mobile station

25 which has a class 0 IMSI assigned, is operating in the slotted mode, and has a TMSI
26 assigned (the bits of TMSI_CODEs-p are not all equal to ‘1’), may stop monitoring the Paging
27 Channel or the Forward Common Control Channel after processing a page record with a
28 TMSI_CODE value of higher numerical value than TMSI_CODEs-p.
29 If ORDERED_TMSIS is equal to ‘1’ and CLASS_1_DONE is equal to ‘1’, a mobile station

30 which has a class 1 IMSI assigned, is operating in the slotted mode, and has a TMSI
31 assigned (the bits of TMSI_CODEs-p are not all equal to ‘1’), may stop monitoring the Paging
32 Channel or the Forward Common Control Channel after processing a page record with a
33 TMSI_CODE value of higher numerical value than TMSI_CODEs-p.
34 The mobile station continues to monitor the Paging Channel or the Forward Common
35 Control Channel for one additional slot unless, within its assigned slot, the mobile station
36 receives a General Page Message containing the appropriate indicator permitting it to stop
37 monitoring the Paging Channel or the Forward Common Control Channel (CLASS_0_DONE,
38 CLASS_1_DONE, TMSI_DONE, or ORDERED_TMSIS equal to ‘1’, whichever is appropriate).
39 This allows the base station to carry over a message begun in the assigned slot into the
40 following slot, if necessary.
2-65
3GPP2 C.S0005-A v6.0
1 2.6.2.1.1.1.1.2 Overview of Stopping Monitoring via the Universal Page Message

2 Layer 3 determines when a mobile station operating in the slotted mode may stop
3 monitoring the Forward Common Control Channel based upon indications from Layer 2
4 (see 2.1.2.2.2.4.2 of [4]). When the Universal Page Message is used on the Forward
5 Common Control Channel, Layer 2 determines whether there is an address mismatch or a
6 broadcast address mismatch, based upon the address information received in the Universal
7 Page Message. Based upon the address mismatch and broadcast address mismatch
8 indications received from Layer 2, Layer 3 can determine when no further messages or
9 records addressed to an individual mobile station will be present in the slot.
10 The Universal Page Message contains the READ_NEXT_SLOT field, which, when equal to ‘1’
11 and received in an assigned slot, indicates to a mobile station that it is to monitor the
12 Forward Common Control Channel in time to receive the first bit of the slot following the
13 assigned slot. This allows the base station to use both an assigned slot and the following
14 slot for pages if all of the pages for an assigned slot cannot be fit into the assigned slot. The
15 Universal Page Message also contains the READ_NEXT_SLOT_BCAST field, which, when
16 equal to ‘1’ and received in an assigned slot or broadcast slot, indicates to a mobile station
17 configured to receive broadcast messages that it is to monitor the Forward Common Control
18 Channel in time to receive the first bit of the subsequent slot. This allows the base station
19 to use the subsequent slot for enhanced broadcast pages if all of the enhanced broadcast
20 pages for an assigned slot or broadcast slot cannot be fit into the slot.
21 2.6.2.1.1.1.2 Overview of Broadcast Messages on Paging Channel
22 The Paging Channel protocol provides two methods for the transmission of broadcast
23 messages. Each method enables mobile stations operating in the slotted mode or in the
24 non-slotted mode to receive broadcast messages. A broadcast message on the Paging
25 Channel is a Data Burst Message that has a broadcast address type. A mobile station
26 operating in the slotted mode has assigned slots that it monitors to receive Paging Channel
27 messages (see 2.6.2.1.1.1). A broadcast page is a record within a General Page Message
28 that has a broadcast address type. A base station may transmit a broadcast page in an
29 assigned slot to inform mobile stations monitoring that slot that a broadcast message will
30 be transmitted in a predetermined subsequent slot. A slot that a mobile station monitors in
31 order to receive either a broadcast page or a broadcast message is referred to as a broadcast
32 slot.
33 2.6.2.1.1.1.2.1 Method 1: Multi-Slot Broadcast Message Transmission
34 According to this method, a broadcast message is sent in a sufficient number of assigned

35 slots such that it may be received by all mobile stations that are operating in the slotted
36 mode.
37 Figure 2.6.2.1.1.1.2.1-1 shows an example for the case when the maximum slot cycle index
38 is equal to 0. In this example, the broadcast message fits in a single slot. The Data Burst
39 Message is transmitted in 16 consecutive slots.
40
2-66
3GPP2 C.S0005-A v6.0
1.28 seconds (16

slots)
... ...
Paging Channel Slots Data Burst Message is sent in 16
1
consecutive slots
2 Figure 2.6.2.1.1.1.2.1-1. Multi-Slot Broadcast Message Transmission Example
4 2.6.2.1.1.1.2.2 Method 2: Periodic Broadcast Paging
5 According to this method, mobile stations configured to receive broadcast messages monitor
6 a specific broadcast slot (the first slot of a broadcast paging cycle; see 2.6.2.1.1.3.3). There
7 are two methods of sending broadcast messages used with Periodic Broadcast Paging.
8 If all of the broadcast messages to be transmitted fit within the first slot of a broadcast
9 paging cycle, they may all be transmitted in this broadcast slot. If there is a single
10 broadcast message to be transmitted, it may be transmitted beginning in this broadcast
11 slot.
12 Alternately, one or more broadcast pages may be transmitted in the first slot of a broadcast
13 paging cycle. Each broadcast page is associated with a subsequent broadcast slot. For
14 each broadcast page, an associated broadcast message may be transmitted in the
15 associated subsequent broadcast slot. The broadcast slot for the associated broadcast
16 message is determined according to the position of the broadcast page within the General
17 Page Message transmitted in the first slot of the broadcast paging cycle.
18 Figure 2.6.2.1.1.1.2.2-1 shows an example of Periodic Broadcast Paging when the broadcast
19 index is set to 1. A General Page Message containing three broadcast pages is transmitted
20 in the first slot of the broadcast paging cycle. For each of the three broadcast pages, a Data
21 Burst Message is transmitted in a subsequent slot.
22
2-67
3GPP2 C.S0005-A v6.0
Paging
Channel
Slots
3 3 3 3 1 1 1 1 3 3 3 3
0 1 2 3 4 5 6 7 8 9 0 1
1 2 3 4 0 1 2 3 1 2 3 4
Broadcast Broadcast Broadcast Broadcast Broadcast Broadcast

Page #1 Page #2 Page #3 Msg #1 Msg #2 Msg #3
1
2 Figure 2.6.2.1.1.1.2.2-1. Periodic Broadcast Paging Example
3 2.6.2.1.1.1.3 Overview of Broadcast Messages on Broadcast Control Channel
4 The Broadcast Control Channel/Forward Common Control Channel protocol provides two
5 methods for the transmission of broadcast messages. Each method enables mobile stations
6 operating in the slotted mode or in the non-slotted mode to receive broadcast messages on
7 the Broadcast Control Channel. A broadcast message on the Broadcast Control Channel is
8 a Data Burst Message that has a broadcast address type. A mobile station operating in the
9 slotted mode has assigned Forward Common Control Channel slots that it monitors to
10 receive Forward Common Control Channel messages (see 2.6.2.1.1.1). A mobile station
11 operating in the slotted mode and configured to receive broadcast messages may also have
12 special assigned Forward Common Control Channel slots, called broadcast slots, that it
13 monitors to receive enhanced broadcast pages. An enhanced broadcast page is a record
14 within a General Page Message or a Universal Page Message that has a broadcast address
15 type and that includes broadcast message scheduling information. A base station may
16 transmit an enhanced broadcast page in an assigned Forward Common Control Channel
17 slot, or in a broadcast slot, to inform mobile stations that a broadcast message will be
18 transmitted in a specified Broadcast Control Channel slot. The enhanced broadcast page
19 identifies the Broadcast Control Channel and the slot the mobile station is to monitor to
20 receive the broadcast message.
21 2.6.2.1.1.1.3.1 Method 1: Multi-Slot Enhanced Broadcast Paging
22 According to this method, an enhanced broadcast page is sent in a sufficient number of

23 assigned slots on the Forward Common Control Channel such that it may be received by all
24 mobile stations that are operating in the slotted mode.
25 Figure 2.6.2.1.1.1.3.1-1 shows an example for the case when the maximum slot cycle index
26 is equal to 0. The enhanced broadcast page is transmitted in 16 consecutive slots.
27
2-68
3GPP2 C.S0005-A v6.0
1.28 seconds (16

slots)
... ...
Forward Common
Control Channel Enhanced broadcast page is sent in
1
16 consecutive slots
2 Figure 2.6.2.1.1.1.3.1-1. Multi-Slot Enhanced Broadcast Paging Example
4 2.6.2.1.1.1.3.2 Method 2: Periodic Enhanced Broadcast Paging
5 According to this method, mobile stations configured to receive broadcast messages monitor
6 a specific broadcast slot (the first slot of a broadcast paging cycle).
7 One or more enhanced broadcast pages may be transmitted in the first slot of a broadcast
8 paging cycle and/or in the subsequent slot. Each enhanced broadcast page is associated
9 with a subsequent broadcast slot. The broadcast slot for the associated broadcast message
10 is determined according to a time offset specified in the enhanced broadcast page. In
11 addition, a broadcast slot for a repeat of the broadcast message can be specified via a time
12 offset from the slot of the first broadcast message.
13 2.6.2.1.1.2 Non-Slotted Mode Requirements
14 A mobile station operating in the non-slotted mode shall monitor the Paging Channel or the
15 Forward Common Control Channel/Primary Broadcast Control Channel at all times. If the
16 mobile station declares a loss of the Paging Channel or the Forward Common Control
17 Channel/Primary Broadcast Control Channel (see 2.6.2.1.1.4), the mobile station shall
18 enter the System Determination Substate of the Mobile Station Initialization State with a
19 system lost indication (see 2.6.1.1).
20 When a mobile station monitors the Paging Channel or the Forward Common Control
21 Channel in any state other than the Mobile Station Idle State, it shall operate in the non-
22 slotted mode.
23 A mobile station monitoring the Paging Channel shall operate in the non-slotted mode when
24 PACAs is equal to enabled.
25 A mobile station monitoring the Paging Channel shall operate in the non-slotted mode when
26 SLOTTEDs is equal to NO.
27 2.6.2.1.1.3 Slotted Mode Requirements
28 A mobile station monitoring the Paging Channel shall not operate in the slotted mode if any
2-69
3GPP2 C.S0005-A v6.0
1 of the of the following conditions are true:

2 • SLOTTEDs is equal to NO,
3 • Bit 5 of the station class mark is set to ‘0’ (see 2.3.3),

4 • PACAs is equal to enabled, or
5 • The mobile station’s configuration parameters are not current (see 2.6.2.2).
6 A mobile station monitoring the Forward Common Control Channel shall not operate in the
7 slotted mode if either of the following conditions is true:
8 • Bit 5 of the station class mark is set to ‘0’ (see 2.3.3), or
9 • The mobile station’s configuration parameters are not current (see 2.6.2.2).
10 A mobile station monitoring the Forward Common Control Channel with bit 5 of the station
11 class mark set to ‘1’ shall monitor all Forward Common Control Channel slots (see
12 2.6.2.1.1.3.1) if either of the following conditions is true:
13 • SLOTTEDs is equal to NO, or
14 • PACAs is equal to enabled.
15 During operation in the slotted mode, the mobile station shall ensure that its stored
16 configuration parameter values are current (see 2.6.2.2).
17 If the mobile station declares a loss of the Paging Channel or the Forward Common Control
18 Channel/Primary Broadcast Control Channel (see 2.6.2.1.1.4), the mobile station shall
21 2.6.2.1.1.3.1 Monitoring Assigned Slots
22 If the mobile station does not support Quick Paging Channel operation or if
23 QPCH_SUPPORTEDs = ‘0’, the mobile station shall monitor the Paging Channel or the
24 Forward Common Control Channel in each of its assigned slots.
25 If the mobile station supports Quick Paging Channel operation and if QPCH_SUPPORTEDs
26 = ‘1‘, for each of its assigned slots, the mobile station shall perform the following:
27 • The mobile station should check its assigned paging indicators in the complete
28 Quick Paging Channel slot immediately preceding its assigned Paging Channel or
29 Forward Common Control Channel slot, as specified in 2.6.2.1.2.1; the mobile
30 station shall monitor the assigned Paging Channel or Forward Common Control
31 Channel slot if the paging indicators meet the conditions specified in 2.6.2.1.2.2.
32 • If the mobile station does not check its assigned paging indicators, the mobile
33 station shall monitor its assigned Paging Channel or Forward Common Control
34 Channel slot.
35 If the mobile station supports Quick Paging Channel operation, the mobile station is
36 configured to receive broadcast messages, BCAST_INDEXs is not equal to ‘000’, and
37 QPCH_BI_SUPPORTEDs equals ‘1’, then for each of its assigned broadcast slots on the
38 Forward Common Control Channel, the mobile station shall perform the following:
2-70
3GPP2 C.S0005-A v6.0
1 • The mobile station should check the broadcast indicators in the complete Quick
2 Paging Channel broadcast slot immediately preceding its assigned broadcast slot, as
3 specified in 2.6.2.1.1.3.3.
4 • The mobile station should receive its assigned broadcast slot on the Forward
5 Common Control Channel if the broadcast indicators meet the conditions specified
6 in 2.6.2.1.2.1.
7 The mobile station shall monitor each slot following an assigned slot in which the mobile
8 station received a Universal Page Message with READ_NEXT_SLOT equal to ‘1’, and shall
9 begin monitoring the Forward Common Control Channel in time to receive the first bit of
10 the slot. If the mobile station is configured to receive broadcast messages, it shall monitor
11 each slot following an assigned slot in which the mobile station received a Universal Page
12 Message with READ_NEXT_SLOT_BCAST equal to ‘1’, and shall begin monitoring the
13 Forward Common Control Channel in time to receive the first bit of the slot.
14 If SLOTTEDs is equal to NO or PACAs is equal to enabled, the mobile station may stop
15 monitoring a Forward Common Control Channel slot when Layer 3 receives an address
16 mismatch indication from Layer 2. When the mobile station stops monitoring a Forward
17 Common Control Channel slot when SLOTTEDs is equal to NO or PACAs is equal to
18 enabled, the mobile station shall begin monitoring the subsequent Forward Common
19 Control Channel slot in time to receive the first bit of the slot.
20 If the mobile station monitors a Paging Channel or Forward Common Control Channel slot,
21 it shall begin monitoring the Paging Channel or the Forward Common Control Channel in
22 time to receive the first bit of the slot. If the mobile station is not configured to receive
23 broadcast addresses, the mobile station shall continue to monitor the Paging Channel or
24 the Forward Common Control Channel until one of the following conditions is satisfied:
25 • Layer 3 receives an address mismatch indication from Layer 2 (see 2.1.2.2.2.4 of

26 [4]); or
27 • The mobile station monitors the assigned slot and the slot following the assigned
28 slot, and the mobile station receives at least one valid message (see 2.1.2.4.2 of [4]).
29 If the mobile station is configured to receive broadcast addresses and the mobile station is
30 monitoring a Paging Channel, the mobile station shall continue to monitor the Paging
31 Channel until one of the preceding conditions is satisfied and should monitor the Paging
32 Channel until Layer 3 receives a broadcast address mismatch indication from Layer 2 (see
33 2.1.2.2.2.4 of [4]).
34 If the mobile station is configured to receive broadcast addresses and the mobile station is
35 monitoring a Forward Common Control Channel Channel, the mobile station shall continue
36 to monitor the the Forward Common Control Channel until one of the preceding conditions
37 is satisfied and should monitor the Forward Common Control Channel until Layer 3
38 receives a broadcast address mismatch indication from Layer 2 (see 2.1.2.2.2.4 of [4]).
39 The mobile station shall monitor each slot following a broadcast slot in which the mobile
40 station received a Universal Page Message with READ_NEXT_SLOT_BCAST equal to ‘1’, and
41 shall begin monitoring the Forward Common Control Channel in time to receive the first bit
42 of the slot.
2-71
3GPP2 C.S0005-A v6.0
1 For each broadcast slot monitored to receive broadcast pages or broadcast messages that is
2 not one of its assigned slots, the mobile station should begin monitoring the Paging
3 Channel or the Forward Common Control Channel in the first bit of the broadcast slot. The
4 mobile station should continue to monitor the Paging Channel or the Forward Common
5 Control Channel until one of the following conditions is satisfied:
6 • Layer 3 receives a broadcast address mismatch indication from Layer 2; or
7 • The mobile station monitors the Paging Channel or the Forward Common Control
8 Channel to receive all messages beginning in the broadcast slot and in the slot
9 following the broadcast slot, and the mobile station receives at least one valid
10 message (see 2.2.2.3.2 of [4]).
11 To determine its assigned slots, the mobile station shall use the hash function specified in
12 2.6.7.1 to select a number, PGSLOT, in the range 0 to 2047 (spanning the maximum slot
13 cycle length, which is 163.84 seconds). The mobile station’s assigned slots shall be those
14 slots in which
15 (t/4 − PGSLOT) mod (16 × T) = 0,
16 where t is the System Time in frames and T is the slot cycle length in units of 1.28 seconds
17 given by
18 T = 2i,
19 where i is the slot cycle index.
20 For each slot on the Broadcast Control Channel monitored to receive broadcast messages,
21 the mobile station should begin monitoring the Broadcast Control Channel in the first bit of
22 the slot. The mobile station should continue to monitor the Broadcast Control Channel
23 until one of the following conditions is satisfied:
24 • The mobile station has monitored all frames of a Broadcast Control Channel slot
25 and the frame quality for all of the frames of the slot was insufficient; or
26 • The mobile station monitors the Broadcast Control Channel slot specified by the
27 enhanced broadcast page and the slot did not contain an SCI bit set to ‘1’ (see [4]).
28 • The mobile station has received a broadcast Data Burst Message having the same
29 BURST_TYPE and broadcast address as the enhanced broadcast page which
30 announced the Data Burst Message.
31 2.6.2.1.1.3.2 Determination of the Slot Cycle Index

32 If the SID and NID of the current base station (SIDs and NIDs, as stored from the System
33 Parameters Message or ANSI-41 System Parameters Message) do not match any entry of
34 SID_NID_LISTs, the mobile station shall use a slot cycle index no greater than the smaller
35 of MAX_SLOT_CYCLE_INDEXs and 1; otherwise, the mobile station shall use a slot cycle
36 index no greater than SLOT_CYCLE_INDEXs (see 2.6.2.2.1.6).
37 If the mobile station is directed by the user to modify the preferred slot cycle index
38 (SLOT_CYCLE_INDEXp), the mobile station shall perform parameter-change registration
39 (see 2.6.5.1.6).
2-72
3GPP2 C.S0005-A v6.0
1 2.6.2.1.1.3.3 Slot Cycles for Broadcast Message Transmission
2 2.6.2.1.1.3.3.1 Slot Cycles for Broadcast Message Transmission on the Paging Channel
3 Distribution of broadcast messages relies on specially defined Paging Channel slot cycles.
4 The definitions are as follows:
5 Maximum paging cycle: On the Paging Channel, a maximum paging cycle is a Paging
6 Channel slot cycle (see 2.6.2.1.1.3.1) having a duration of M slots such that:
7 M = 2i × 16, 0 ≤ i ≤ 7
8 where i = MAX_SLOT_CYCLE_INDEXs as received in the System Parameters Message.
9 The first slot of each maximum paging cycle is any Paging Channel slot in which
10 t/4 mod M = 0,
11 where t represents system time in frames.
12 Broadcast paging cycle: On the Paging Channel, a broadcast paging cycle is a Paging
13 Channel slot cycle (see 2.6.2.1.1.3.1) having a duration of B + 3 slots where:
14 B = 2i × 16, 1 ≤ i ≤ 7
15 where i = BCAST_INDEXs as received in the Extended System Parameters Message, or set

16 by default when the Extended System Parameters Message is not sent.
17 The first slot of each broadcast paging cycle is any Paging Channel slot in which
18 t/4 mod (B + 3) = 0,
20 2.6.2.1.1.3.3.2 Slot Cycles for Broadcast Message Transmission on the Forward Common
21 Control Channel
22 Distribution of broadcast messages relies on specially defined Forward Common Control

23 Channel slot cycles. The definitions are as follows:
24 Maximum paging cycle: On the Forward Common Control Channel, a maximum paging
25 cycle is a Forward Common Channel slot cycle (see 2.6.2.1.1.3.1) having a duration of M
26 slots such that:
27 M = 2i × 16, 0 ≤ i ≤ 7
28 where i = MAX_SLOT_CYCLE_INDEXs as received in the MC-RR Parameters Message.
29 The first slot of each maximum paging cycle is any Forward Common Control Channel slot
30 in which
31 t/4 mod M = 0,
2-73
3GPP2 C.S0005-A v6.0
2 Broadcast paging cycle: On the Forward Common Control Channel, a broadcast paging
3 cycle is a Forward Common Control Channel slot cycle (see 2.6.2.1.1.3.1) having a duration
4 of B + 7 slots where:
5 B = 21+i × 16, 1 ≤ i ≤ 7
6 where i = BCAST_INDEXs as received in the MC-RR Parameters Message.
7 The first slot of each broadcast paging cycle is any Forward Common Control Channel slot
8 in which
9 t/4 mod (B + 7) = 0,
11 2.6.2.1.1.3.4 Monitoring Paging Channel Broadcasts
12 The following requirements apply to mobile stations monitoring the Paging Channel and
13 supporting the reception of broadcast messages.
14 If BCAST_INDEXs is equal to ‘000’, the mobile station shall monitor only its assigned Paging
15 Channel slots (see 2.6.2.1.1.3.1).
16 If BCAST_INDEXs is not equal to ‘000’, and the mobile station is configured to receive
17 messages addressed to broadcast addresses, the mobile station should also monitor the
18 Paging Channel beginning with the first slot of each broadcast paging cycle (see
19 2.6.2.1.1.3.3).
20 If the mobile station receives a broadcast page containing a burst type and broadcast
21 address that the mobile station has been configured to receive (see 2.6.2.3), the mobile
22 station should monitor the slot in which the corresponding broadcast Paging Channel
23 message will be sent, determined as follows:
24 • The mobile station shall consider a broadcast page to have been received in the
25 paging slot in which the General Page Message containing the broadcast page
26 began.
27 • If BCAST_INDEXs is not equal to ‘000’, the paging slot containing the broadcast
28 page is defined as the reference slot.
29 • Let n represent the ordinal number of the broadcast page relative to other broadcast
30 pages that are contained in the same General Page Message (n = 1, 2, 3,…). The
31 mobile station should monitor the Paging Channel slot that occurs n × 3 paging
32 slots after the reference slot.
33 After receiving a broadcast message or a broadcast page and a corresponding broadcast

34 Paging Channel message when BCAST_INDEXs is not equal to ‘000’, the mobile station
35 should discard all further broadcast pages and all further broadcast Paging Channel
36 messages containing the same BURST_TYPE and BC_ADDR fields that are received within 4
37 × (B + 3) paging slots of the first paging slot in the broadcast paging cycle in which the
2-74
3GPP2 C.S0005-A v6.0
1 broadcast page or broadcast message was first received. (B + 3 is the duration of the
2 broadcast paging cycle as defined in 2.6.2.1.1.3.3).
3 2.6.2.1.1.3.5 Support of Broadcast Delivery Options on the Paging Channel
4 A mobile station configured to receive broadcast messages shall support reception of

5 broadcast messages transmitted using Multi-Slot Broadcast Message Transmission (see
6 3.6.2.4.1.2.1.1).

8 broadcast messages transmitted using Periodic Broadcast Paging (see 3.6.2.4.1.2.1.2).
9 2.6.2.1.1.3.6 Monitoring the Forward Common Control Channel for the Enhanced
10 Broadcast Page
11 The following requirements apply to mobile stations monitoring the Forward Common
12 Control Channel and supporting the reception of broadcast messages.
13 If BCAST_INDEXs is equal to ‘000’, the mobile station shall monitor only its assigned Quick
14 Paging Channel slots or its assigned Forward Common Control Channel slots (see 2.6.2.1.2)
15 for enhanced broadcast pages.
16 If BCAST_INDEXs is not equal to ‘000’, and the mobile station is configured to receive
17 messages addressed to broadcast addresses, the mobile station should also monitor the
18 Quick Paging Channel broadcast slots or the Forward Common Control Channel broadcast
19 slots (see 2.6.2.1.2) beginning with the first slot of each broadcast paging cycle.
20 If the mobile station receives an enhanced broadcast page containing a burst type and
21 broadcast address that the mobile station has been configured to receive, the mobile station
22 should monitor at least one Broadcast Control Channel slot in which the corresponding
23 broadcast message will be sent, determined as follows:
24 • The mobile station shall monitor the Broadcast Control Channel slot which begins
25 40 ms × (1 + TIME_OFFSET) later than the beginning of the slot in which the
26 message containing the enhanced broadcast page began or the Broadcast Control
27 Channel slot which begins 40 ms × (1 + REPEAT_TIME_OFFSET) later than the
28 Broadcast Control Channel slot in which the first transmission began.
29 After receiving an enhanced broadcast page and a corresponding broadcast message when
30 BCAST_INDEXs is not equal to ‘000’, the mobile station should discard all further enhanced
31 broadcast pages containing the same BURST_TYPE and having the same broadcast address
32 that are received within 4 × (B + 7) slots of the first slot in the broadcast paging cycle in
33 which the enhanced broadcast page was received. (B + 7 is the duration of the broadcast
34 paging cycle as defined in 2.6.2.1.1.3.3.1). The mobile station should ignore broadcast
35 messages for which a corresponding enhanced broadcast page was not received.
36 If the mobile station received an enhanced broadcast page and a corresponding broadcast
37 message, and the broadcast message announced by a pending enhanced broadcast page
38 containing the same BURST_TYPE and having the same broadcast address has not yet been
39 received, the mobile station shall ignore the pending enhanced broadcast page.
2-75
3GPP2 C.S0005-A v6.0
1 2.6.2.1.1.3.7 Support of Broadcast Delivery Options on the Forward Common Control

2 Channel/Broadcast Control Channel

4 broadcast messages transmitted using Multi-Slot Enhanced Broadcast Paging (see
5 2.6.2.1.1.1.3.1).

7 broadcast messages transmitted using Periodic Enhanced Broadcast Paging (see
8 2.6.2.1.1.1.3.2).
9 2.6.2.1.1.4 Common Channel Supervision
10 The mobile station shall monitor the Paging Channel, the Forward Common Control
11 Channel, or the Primary Broadcast Control Channel as specified in 2.6.2.1.1. The mobile
12 station shall set a timer for T30m seconds whenever it begins to monitor the Paging
13 Channel, the Forward Common Control Channel, or the Primary Broadcast Control
14 Channel. The mobile station shall reset the timer for T30m seconds whenever it gets an
15 indication that a valid message was received on the Paging Channel, the Forward Common
16 Control Channel, or the Primary Broadcast Control Channel, whether addressed to the
17 mobile station or not (see 2.1.2.3.2 of [4]). The mobile station shall disable the timer when
18 it is not monitoring the Paging Channel, the Forward Common Control Channel, or the
19 Primary Broadcast Control Channel. If the timer expires, the mobile station shall declare a
20 loss of the Paging Channel, the Forward Common Control Channel, or the Primary
22 2.6.2.1.2 Quick Paging Channel Monitoring Procedures
23 2.6.2.1.2.1 Overview
24 The Quick Paging Channel is divided into 80 ms slots called Quick Paging Channel slots.
25 The Quick Paging Channel protocol provides for scheduling the transmission of paging
26 indicators for a mobile station in Quick Paging Channel slots assigned to the mobile station.
27 Support of this feature is optional.
28 The Quick Paging Channel protocol provides for scheduling the transmission of
29 configuration change indicators for mobile stations in Quick Paging Channel slots. Support
30 of this feature is optional.
31 The Quick Paging Channel protocol provides for scheduling the transmission of broadcast
32 indicators for mobile stations in Quick Paging Channel broadcast slots. Support of this
33 feature is optional.
34 If the mobile station is operating in the slotted mode and it supports the Quick Paging
35 Channel, and QPCH_SUPPORTEDs is equal to ‘1’, the mobile station monitors paging
36 indicators on the Quick Paging Channel as follows:
37 The mobile station’s assigned Quick Paging Channel slots are offset from its assigned
38 Paging Channel slots or its assigned Forward Common Control Channel slots by 100 ms, as
39 shown in Figure 2.6.2.1.2.1-1. Two paging indicators are assigned to a mobile station in its
2-76
3GPP2 C.S0005-A v6.0
1 assigned Quick Paging Channel slot. In the following, t* is the start time of the mobile
2 station’s assigned Paging Channel or Forward Common Control Channel slot. According to
3 the hash function specified in 2.6.7.1, paging indicators are assigned as follows:
4 • The first paging indicator for the mobile station is assigned between (t*-100) ms and
5 (t*-80) ms (marked as 1 in Figure 2.6.2.1.2.1-1) and the second paging indicator is
6 assigned between (t*-60) ms and (t*-40) ms (marked as 3 in the figure); or
7 • The first paging indicator for the mobile station is assigned between (t*-80) ms and
8 (t*-60) ms (marked as 2 in the figure) and the second paging indicator is assigned
9 between (t*-40) ms and (t*-20) ms (marked as 4 in the figure).
10 If the mobile station is operating in the slotted mode and it supports the Quick Paging
11 Channel, the mobile station can, when performing an idle handoff to a base station whose
12 Paging Channel or Forward Common Control Channel/Primary Broadcast Control Channel
13 has recently been monitored, monitor one or more configuration change indicators.
14 Configuration change indicators are scheduled every 40 ms on the first Quick Paging
15 Channel.
16 If the mobile station is operating in the slotted mode, is configured to receive the broadcast
17 messages, supports the Quick Paging Channel, BCAST_INDEXs is not equal to ‘000’,
18 QPCH_SUPPORTEDs is equal to ‘1’, and QPCH_BI_SUPPORTEDs is equal to ‘1’, the mobile
19 station monitors broadcast indicators on the Quick Paging Channel as follows:
20 • The mobile station’s assigned Quick Paging Channel broadcast slots are offset from
21 its assigned Forward Common Control Channel broadcast slots by 100 ms, as
22 shown in Figure 2.6.2.1.2.1-1.
23 • The mobile station monitors one or more broadcast indicators in an assigned Quick
24 Paging Channel broadcast slot.
25
2-77
3GPP2 C.S0005-A v6.0
1.28 s
PCH/F-CCCH
2047 0 1 2 ... 15 16
t*
PCH/F-CCCH Slot
(80 ms)
Quick Paging Channel Slot Quick Paging Channel Slot

(80 ms) (80 ms)
Quick Paging
Channel
1 2 3 4 1 2 3 4
t
20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms 20 ms
QPCH Rate
2400 bps
(Indicator
Rate 4800
bps)
paging indicators paging indicators
2 configuration change
2 broadcast indicators for 2 configuration change 2 broadcast indicators for
indicators for the first
the first QPCH; indicators for the first the first QPCH;
QPCH;
2 reserved indicators for QPCH; 2 reserved indicators for
2 reserved indicators for
QPCHs other than the first 2 reserved indicators for QPCHs other than the first
QPCHs other than the first
QPCH Rate
4800 bps
(Indicator
Rate 9600
bps)
paging indicators paging indicators
4 configuration change
4 broadcast indicators for 4 configuration change 4 broadcast indicators for
indicators for the first
the first QPCH; indicators for the first the first QPCH;
QPCH;
4 reserved indicators for QPCH; 4 reserved indicators for
4 reserved indicators for
QPCHs other than the first 4 reserved indicators for QPCHs other than the first
1
3 Figure 2.6.2.1.2.1-1. Quick Paging Channel Timeline
2-78
3GPP2 C.S0005-A v6.0
1 2.6.2.1.2.2 Requirements
2 A mobile station operating in the slotted mode should monitor the paging indicators in the
3 mobile station’s assigned Quick Paging Channel slot if all of the following conditions hold:
4 • The mobile station supports the Quick Paging Channel;

5 • QPCH_SUPPORTEDs = ‘1’; and
6 • The mobile station is not monitoring the Paging Channel or the Forward Common
7 Control Channel.
8 The mobile station’s assigned Quick Paging Channel slots shall be those slots in which
9 ((t+5)/4 − PGSLOT) mod (16 × T) = 0.
10 where t is the System Time in frames, PGSLOT is selected in the range 0 to 2047 by using
11 the hash function specified in 2.6.7.1, and T is the slot cycle length in units of 1.28 seconds
12 such that
13 T = 2i,
14 and i is the slot cycle index.
15 To determine the position of the mobile station’s two assigned paging indicators respective
16 to the beginning of the mobile station’s assigned Quick Paging Channel slot, the mobile
17 station shall use the hash function specified in 2.6.7.1. The R1 and R2 outputs of the
18 hashing algorithm correspond to an indicator bit position relative to the beginning of the
19 Quick Paging Channel slot. The hashing algorithm is so devised that two paging indicators
20 (R1 and R2) for a mobile station will be in the first and third quarter slot or the second and
21 fourth quarter slot.
22 If the mobile station checks assigned paging indicators, the mobile station shall perform the
23 following:
24 • If the mobile station detects that one of the paging indicators is set to “OFF”, the
25 mobile station need not detect another paging indicator.
26 • If the mobile station does not detect that at least one of the paging indicators is set
27 to “OFF”, the mobile station shall monitor its assigned Paging Channel or Forward
28 Common Control Channel slot immediately following its assigned Quick Paging
29 Channel slot.2
30 When performing an idle handoff to a base station whose Paging Channel or Forward
31 Common Control Channel was previously monitored, a mobile station operating in the
32 slotted mode should monitor one or more configuration change indicators on the first Quick
2 A case for which the mobile station may not be able to detect that at least one of the paging
indicators is set to “OFF” is for a mobile station that misses a part of or its entire Quick Paging
Channel slot during overhead information update. In this case, the mobile station monitors its
assigned Paging Channel slot.
2-79
3GPP2 C.S0005-A v6.0
1 Paging Channel for the new base station if all of the following conditions hold:
3 • The mobile station has knowledge that the new base station supports the Quick
4 Paging Channel;
5 • The mobile station has knowledge that the new base station supports configuration
6 change indicators,
7 • The mobile station is not monitoring the Paging Channel or the Forward Common
8 Control Channel; and
9 • No more than T31m seconds have elapsed since the mobile station last received a
10 valid message on the new Paging Channel or the new Forward Common Control
11 Channel.
12 Before monitoring a configuration change indicator, the mobile station shall perform the
13 following:
14 • The mobile station shall set ASSIGNED_QPAGECHs equal to QPAGECHs, and
15 • The mobile station shall set QPAGECHs equal to 1.
16 Before monitoring a paging indicator subsequent to monitoring a configuration change

17 indicator, the mobile station shall set QPAGECHs equal to ASSIGNED_QPAGECHs.
18 If the Quick Paging Channel data rate is 2400 bps (indicator rate is 4800 bps), the bit
19 positions of the mobile station’s first pair of configuration change indicators shall be the
20 last two bits in the first 40 ms half of a Quick Paging Channel slot. The bit positions of the
21 mobile station’s second pair of configuration change indicators shall be the last two bits in
22 a Quick Paging Channel slot.
24 positions of the mobile station’s first four configuration change indicators shall be the last
25 four bits in the first 40 ms half of a Quick Paging Channel slot. The bit positions of the
26 mobile station’s second four configuration change indicators shall be the last four bits in a
27 Quick Paging Channel slot.
28 If the mobile station monitors a configuration change indicator and determines that it is set
29 to “OFF”, the mobile station can enter or remain in the slotted mode after an idle handoff
30 (see 2.6.2.1.4.2).
31 If a mobile station is operating in the slotted mode and is configured to receive broadcast
32 messages, it should monitor the broadcast indicators in the mobile station’s assigned Quick
33 Paging Channel broadcast slot if all of the following conditions hold:

35 • BCAST_INDEXs is not equal to ‘000’
36 • QPCH_BI_SUPPORTEDs = ‘1’; and
37 • The mobile station is not monitoring the Forward Common Control Channel or the
38 Primary Broadcast Control Channel.
2-80
3GPP2 C.S0005-A v6.0
1 The mobile station’s assigned Quick Paging Channel broadcast slots shall be those slots in
2 which
3 (t+5)/4 mod (B + 7) = 0.
4 where t is the System Time in frames, and B is the broadcast paging cycle such that B =
5 21+i × 16, 1 ≤ i ≤ 7 and i = BCAST_INDEXs as received in the MC-RR Parameters Message.
6 The mobile station should monitor one or more broadcast indicators on the Quick Paging
7 Channel. If the Quick Paging Channel data rate is 2400 bps (indicator rate is 4800 bps),
8 the bit positions of the mobile station’s first pair of broadcast indicators shall be the two
9 bits prior to the last two bits in the first 40 ms half of a Quick Paging Channel slot. The bit
10 positions of the mobile station’s second pair of broadcast indicators shall be the two bits
11 prior to the last two bits in a Quick Paging Channel slot.
12 If the Quick Paging Channel data rate 4800 bps (indicator rate is 9600 bps), the bit
13 positions of the mobile station’s first four broadcast indicators shall be the four bits prior to
14 the last four bits in the first 40 ms half of a Quick Paging Channel slot. The bit positions of
15 the mobile station’s second four broadcast indicators shall be the four bits prior to the last
16 four bits in a Quick Paging Channel slot.
17 If the mobile station monitors broadcast indicators and determines that they are not set to
18 “OFF”, the mobile station should perform the following:
19 • The mobile station should receive its assigned broadcast slot on the Forward
20 Common Control Channel immediately following its assigned Quick Paging Channel
21 broadcast slot.
22 2.6.2.1.3 Registration
23 While in the Mobile Station Idle State, the mobile station shall perform the registration
24 procedures specified in 2.6.5.5.2.1.
25 2.6.2.1.4 Idle Handoff
26 2.6.2.1.4.1 Pilot Search
27 An idle handoff occurs when a mobile station has moved from the coverage area of one base
28 station into the coverage area of another base station during the Mobile Station Idle State. If
29 the mobile station detects a Pilot Channel signal from another base station that is
30 sufficiently stronger than that of the current base station, the mobile station determines
31 that an idle handoff should occur. When multiple idle handoff candidates are available, the
32 mobile station should select, if any, a candidate which supports Primary Broadcast Control
33 Channel.
34 Pilot Channels are identified by their offsets relative to the zero offset pilot PN sequence (see
35 3.1.3.2.1). Pilot offsets are grouped into sets describing their status with regard to pilot
36 searching.
37 The following sets of pilot offsets are defined for a mobile station in the Mobile Station Idle
38 State. Each pilot offset is a member of only one set.
2-81
3GPP2 C.S0005-A v6.0
1 • Active Set: The pilot offset of the Forward CDMA Channel whose Paging Channel or
2 Forward Common Control Channel is being monitored.
3 • Neighbor Set: The offsets of the Pilot Channels that are likely candidates for idle
4 handoff. The members of the Neighbor Set are specified in the Neighbor List
5 Message, Extended Neighbor List Message, and the General Neighbor List Message on
6 the Paging Channel, and the Universal Neighbor List Message on the Primary
8 • Remaining Set: The set of all possible pilot offsets in the current system (integer
9 multiples of PILOT_INCs) on the current CDMA Frequency Assignment, excluding
10 the pilots in the Neighbor Set and the Active Set.
11 • Private Neighbor Set: The offsets of the Pilot Channels for the private systems that
12 are likely candidates for idle handoff. The members of the Private Neighbor Set are
13 specified in the Private Neighbor List Message.
14 The mobile station shall support a Neighbor Set size of at least N8m pilots (see Annex D).
15 In the Mobile Station Idle State, the mobile station shall continuously search for the
16 strongest Pilot Channel signal on the corresponding CDMA Frequency Assignment
17 whenever it monitors the Paging Channel or the Forward Common Control Channel.
18 The mobile station may search other frequencies and band classes. For example, if a pilot
19 in the Neighbor Set or in the Private Neighbor Set is on a different Frequency Assignment
20 than that of the mobile station, this frequency should be included in the search criteria.
21 Search performance criteria are defined in [11].
22 This search should be governed by the following:
23 • Active Set: The search window size for the pilot in the Active Set shall be the
24 number of PN chips specified in Table 2.6.6.2.1-1 corresponding to SRCH_WIN_As.
25 The mobile station should center the search window for the pilot of the Active Set
26 around the earliest arriving usable multipath component of the pilot. If the mobile
27 station receives a value greater than or equal to 13 for SRCH_WIN_Ar, it may store
28 and use the value 13 in SRCH_WIN_As.
29 • Neighbor Set: The search window size for each pilot in the Neighbor Set shall be the
30 number of PN chips specified in Table 2.6.6.2.1-1 corresponding to
31 SRCH_WIN_NGHBRs field of the NGHBR_REC for the pilot. The mobile station
32 should center the search window for each pilot in the Neighbor Set around the
33 pilot’s PN sequence offset plus the corresponding SRCH_OFFSET_NGHBRs (see
34 Table 2.6.6.2.1-2) using timing defined by the mobile station’s time reference (see
35 2.1.5 of [2]). The mobile station should use the SEARCH_PRIORITY field of the
36 NGHBR_REC for the corresponding pilot to schedule its neighbor search. If
37 ADD_PILOT_REC_INCL field of the NGHBR_REC for the corresponding pilot is equal
38 to ‘1’, the mobile station shall use the information included in the
39 NGHBR_PILOT_REC field for searching the neighbor.
2-82
3GPP2 C.S0005-A v6.0
1 If the mobile station supports hopping pilot beacons and the TIMING_INCL field of
2 the NGHBR_REC for the corresponding pilot is equal to ‘1’, then the mobile station
3 shall use the information included in the NGHBR_TX_OFFSET,
4 NGHBR_TX_DURATION, and NGHBR_TX_PERIOD fields of the NGHBR_REC for the
5 corresponding pilot to schedule the time for searching the neighbor.
6 • Remaining Set: The search window size for each pilot in the Remaining Set shall be
7 the number of PN chips specified in Table 2.6.6.2.1-1 corresponding to
8 SRCH_WIN_Rs. The mobile station should center the search window for each pilot
9 in the Remaining Set around the pilot’s PN sequence offset using timing defined by
10 the mobile station’s time reference (see 2.1.5 of [2]). The mobile station should only
11 search for Remaining Set pilots whose pilot PN sequence offset indices are equal to
12 integer multiples of PILOT_INCs.
13 • Private Neighbor Set: The search window size for each pilot in the Private Neighbor
14 Set shall be the number of PN chips specified in Table 2.6.6.2.1-1 corresponding to
15 SRCH_WIN_PRI_NGHBRs field of the PRI_NGHBR_REC for the pilot. The mobile
16 station should center the search window for each pilot in the Private Neighbor Set
17 around the pilot’s PN sequence offset using timing defined by the mobile station’s
18 time reference (see 2.1.5 of [2]).
19 If the mobile station determines that one of the Neighbor Set, Private Neighbor Set or
20 Remaining Set Pilot Channel signals is sufficiently stronger (see [11]) than the Pilot Channel
21 of the Active Set, the mobile station should perform an idle handoff as specified in
22 2.6.2.1.4.2.
23 A mobile station operating in slotted mode, which is successfully demodulating the Paging
24 Channel or the Forward Common Control Channel, should not perform an idle handoff
25 while it is required to monitor its assigned slot (see 2.6.2.1.1.3.1).
26 2.6.2.1.4.2 Idle Handoff Procedures
27 While performing an idle handoff, the mobile station should not begin operating in non-
28 slotted mode after the idle handoff if all of the following conditions hold:
30 • The mobile station has knowledge that the new base station supports configuration
31 change indicators;
32 • The mobile station determines that the Quick Paging Channel configuration change
33 indicator for the new Quick Paging Channel is set to “OFF” (see 2.6.2.1.2.1); and
34 • No more than T31m seconds have elapsed since the mobile station last received a
35 valid message on the new Paging Channel or Forward Common Control
36 Channel/Primary Broadcast Control Channel.
37 Otherwise, the mobile station shall operate in non-slotted mode until the mobile station has
38 received at least one valid configuration message or mobile station-addressed page on the
39 new Paging Channel or Forward Common Control Channel/Primary Broadcast Control
40 Channel. Following the reception of this message the mobile station may resume slotted
41 mode operation in accordance with 2.6.2.1.1.3. After performing an idle handoff, the
2-83
3GPP2 C.S0005-A v6.0
1 mobile station shall discard all unprocessed messages received on the old Paging Channel
2 or Forward Common Control Channel/Primary Broadcast Control Channel.
3 If the new base station is listed in NGHBR_REC_LIST for the old base station (see 2.6.2.2.3,
4 2.6.2.2.7, and 2.6.2.1.4.1), the mobile station shall use the corresponding 3-bit
5 NGHBR_CONFIG field to determine the actions required to transition to the new base
6 station. If the new base station is not listed in NGHBR_REC_LIST for the old base station,
7 the mobile station shall perform the handoff operation using the same procedure as for a
8 pilot in NGHBR_REC_LIST with the NGHBR_CONFIG field set to ‘011’.
9 If the mobile station is currently monitoring the Paging Channel and selected a neighbor
10 base station for idle handoff which supports Primary Broadcast Control Channel, the
12 – The mobile station shall enter the System Determination Substate of the Mobile Station
13 Initialization State with a new system indication, upon performing idle handoff to this
14 neighbor base station.
15 – The mobile station shall not perform any of the remaining procedures in this section.
16 If the NGHBR_CONFIG field is ‘000’, the mobile station shall perform the following:
17 • The mobile station shall set ACC_MSG_SEQs and CURR_ACC_MSG_SEQ to NULL
18 (see 2.6.2.2) and shall set PILOT_PNs to the pilot offset index of the base station
19 transmitting the new Paging Channel or Forward Common Control
20 Channel/Primary Broadcast Control Channel.
21 • If the mobile station has not stored configuration parameters for the new Paging
22 Channel or Forward Common Control Channel and Primary Broadcast Control
23 Channel, or if the stored information is not current, the mobile station shall perform
24 the following:
25 - If the mobile station has monitored the Paging Channel before the idle handoff,
26 the mobile station shall set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs,
27 NGHBR_LST_MSG_SEQs, EXT_NGHBR_LST_MSG_SEQs,
28 GEN_NGHBR_LST_MSG_SEQs, CHAN_LST_MSG_SEQs,
29 EXT_SYS_PAR_MSG_SEQs, GLOB_SERV_REDIR_MSG_SEQs,
30 EXT_GLOB_SERV_REDIR_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
31 USER_ZONE_ID_MSG_SEQs, and PRI_NGHBR_LST_MSG_SEQs to NULL.
32 - If the mobile station has monitored the Forward Common Control

33 Channel/Primary Broadcast Control Channel before the idle handoff, the mobile
34 station shall set CONFIG_MSG_SEQs, A41_SYS_PAR_MSG_SEQs,
35 UNI_NGHBR_LST_MSG_SEQs, MC_RR_PAR_MSG_SEQs,
2-84
3GPP2 C.S0005-A v6.0
1 • If the stored information for the new Paging Channel or the Forward Common
2 Control Channel and Primary Broadcast Control Channel is current, the mobile
3 station shall set CONFIG_MSG_SEQs to the stored information for the new Paging
4 Channel or Forward Common Control Channel and Primary Broadcast Control
5 Channel, and the mobile station shall set NGHBR_REC_LIST to the stored
6 information for the new Paging Channel or the new Forward Common Control
7 Channel and Primary Broadcast Control Channel.
8 • If the associated NGHBR_BANDs or NGHBR_FREQs of the new base station in

9 NGHBR_REC_LIST of the old base station is not equal to CDMABANDs and
10 CDMACHs respectively, the mobile station shall set CDMABANDs to NGHBR_BANDs,
11 CDMACHs to NGHBR_FREQs, and tune to the new CDMA Channel. The mobile
12 station shall begin monitoring the Paging Channel or the Forward Common Control
13 Channel/Primary Broadcast Control Channel of the new base station, using the
14 same rate, code rate, and code channel, as applicable.
15 • If PACAs is equal to enabled, the mobile station shall enter the Update Overhead
16 Information Substate of the System Access State (see 2.6.3) with an origination
17 indication within T33m seconds to re-originate the PACA call using the new base
18 station.
21 and shall set PILOT_PNs to the pilot offset index of the base station transmitting the
22 new Paging Channel.
23 • If the stored information for Primary Paging Channel or any of the Paging Channels
24 on the associated NGHBR_FREQs of the new base station in NGHBR_REC_LIST of
25 the old base station is current, the mobile station shall perform the following:
26 - The mobile station shall use the hash algorithm specified in 2.6.7.1 to select a
27 new Paging Channel number in the range 1 to PAGE_CHANs, where
28 PAGE_CHANs is the value stored for the Paging Channel whose stored
29 information is current. The mobile station shall store the new Paging Channel
30 number as PAGECHs. The mobile station shall perform the following:
31 + If the mobile station has not stored configuration parameters for the new
32 Paging Channel, or if the stored parameters are not current (see 2.6.2.2), the
33 mobile station shall set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs,
36 EXT_SYS_PAR_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
37 PRI_NGHBR_LST_MSG_SEQs, and EXT_GLOB_SERV_REDIR_MSG_SEQs,
38 EXT_CHAN_LST_MSG_SEQs, and GLOB_SERV_REDIR_MSG_SEQs to NULL.
2-85
3GPP2 C.S0005-A v6.0
1 + If the stored information for the new Paging Channel is current, the mobile
2 station shall set CONFIG_MSG_SEQs to the stored information for the new
3 Paging Channel and set NGHBR_REC_LIST to the stored information for the
4 new Paging Channel.

7 station shall set Paging Channel data rate, PRATs = ‘00’.
8 - If the associated NGHBR_BANDs or NGHBR_FREQs of the new base station in

10 CDMACHs respectively, the mobile station shall set CDMABANDs to
11 NGHBR_BANDs, CDMACHs to NGHBR_FREQs, and tune to the new CDMA
12 Channel. The mobile station shall begin monitoring the new Paging Channel of
13 the new base station.
14 • If none of the Paging Channel stored information on the associated NGHBR_FREQs

15 of the new base station in NGHBR_REC_LIST of the old base station are current, the
17 - The mobile station shall set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs,


25 station shall set Paging Channel data rate, PRATs = ‘00’.
26 - The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the Primary
27 Paging Channel. If the associated NGHBR_BANDs or NGHBR_FREQs of the new
28 base station in NGHBR_REC_LIST of the old base station is not equal to
29 CDMABANDs and CDMACHs respectively, the mobile station shall set
30 CDMABANDs to NGHBR_BANDs, CDMACHs to NGHBR_FREQs, and tune to the
31 new CDMA Channel. The mobile station shall begin monitoring the Primary
32 Paging Channel of the new base station.
36 station.
2-86
3GPP2 C.S0005-A v6.0

2 and shall set PILOT_PNs to the pilot offset index of the base station transmitting the
3 new Paging Channel or Forward Common Control Channel/Primary Broadcast
4 Control Channel.
5 • If the mobile station has monitored the Paging Channel before the idle handoff, the
7 - If the stored information for Primary Paging Channel or any of the Paging
8 Channels on the target frequency or any of the frequencies of the new base
9 station is current, the mobile station shall perform the following:
10 + The mobile station shall use the hash algorithm specified in 2.6.7.1 and the
11 stored value of the number of CDMA channels to determine the new CDMA
12 Channel and shall set FREQ_NEW to this new CDMA Channel. The mobile
14 ο If the stored information for any of the Paging Channels on the CDMA
15 channel specified by FREQ_NEW is current, the mobile station shall
17 ◊ The mobile station shall use the hash algorithm specified in 2.6.7.1 to
18 select a new Paging Channel number in the range 1 to PAGE_CHANs,
19 where PAGE_CHANs is the value stored for the Paging Channel whose
20 stored information is current. The mobile station shall store the new
21 Paging Channel number as PAGECHs. The mobile station shall
23 – If the mobile station has not stored configuration parameters for

24 the new Paging Channel, or if the stored parameters are not
25 current (see 2.6.2.2), the mobile station shall set CONFIG-
26 _MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,
27 EXT_NGHBR_LST_MSG_SEQs, GEN_NGHBR_LST_MSG_SEQs,
29 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LST_MSG_SEQs, and
30 EXT_GLOB_SERV_REDIR_MSG_SEQs,
31 EXT_CHAN_LST_MSG_SEQs, and
32 GLOB_SERV_REDIR_MSG_SEQs to NULL.
33 – If the stored information for the new Paging Channel is current,

34 the mobile station shall set CONFIG_MSG_SEQs to the stored
35 information for the new Paging Channel and set
36 NGHBR_REC_LIST to the stored information for the new Paging
37 Channel.
2-87
3GPP2 C.S0005-A v6.0
1 ◊ If the band class corresponding to FREQ_NEW is not equal to

2 CDMABANDs of the old base station or FREQ_NEW is not equal to
3 CDMACHs of the old base station, the mobile station shall set
4 CDMABANDs to band class corresponding to FREQ_NEW and shall
5 set CDMACHs to FREQ_NEW, and tune to the new CDMA Channel.
6 The mobile station shall begin monitoring the new Paging Channel of
7 the new base station.
8 ο If none of the Paging Channel stored information on the CDMA channel

9 specified by FREQ_NEW are current, the mobile station shall perform the
10 following:
11 ◊ The mobile station shall set CONFIG_MSG_SEQs, SYS_PAR-
12 _MSG_SEQs, NGHBR_LST_MSG_SEQs,
15 GLOB_SERV_REDIR_MSG_SEQs,
17 USER_ZONE_ID_MSG_SEQs, and PRI_NGHBR_LST_MSG_SEQs to
18 NULL.
19 ◊ The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the
20 Primary Paging Channel. If the band class corresponding to
21 FREQ_NEW is not equal to CDMABANDs of the old base station or
22 FREQ_NEW is not equal to CDMACHs of the old base station, the
23 mobile station shall set CDMABANDs to band class corresponding to
24 FREQ_NEW and shall set CDMACHs to FREQ_NEW, and tune to the
25 new CDMA Channel. The mobile station shall begin monitoring the
26 Primary Paging Channel of the new base station.
27 - If none of the Paging Channel stored information on any of the frequencies of the
28 new base station are current, the mobile station shall perform the following:
29 + The mobile station shall set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs,

35 + The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the Primary
36 Paging Channel. If the associated NGHBR_BANDs or NGHBR_FREQs of the
37 new base station in NGHBR_REC_LIST of the old base station is not equal to
38 CDMABANDs and CDMACHs of the old base station respectively, the mobile
39 station shall set CDMABANDs to NGHBR_BANDs, and CDMACHs to
40 NGHBR_FREQs; otherwise, the mobile station shall set CDMACHs as follows:
2-88
3GPP2 C.S0005-A v6.0
1 ο If the Extended CDMA Channel List Message is being sent on the old base
2 station, set CDMACHs to the first CDMA Channel given in the Extended
3 CDMA Channel List Message for the old base station.
4 ο Otherwise, set CDMACHs to the first CDMA Channel given in the CDMA
5 Channel List Message for the old base station.
6 Then the mobile station shall tune to the new CDMA channel and begin
7 monitoring the Primary Paging Channel of the new base station.
8 • If the mobile station has monitored the Forward Common Control Channel/Primary
9 Broadcast Control Channel before the idle handoff, the mobile station shall perform
10 the following:
11 − If the stored information for any of the Forward Common Control Channels and
12 Primary Broadcast Control Channel on any of the frequencies of the new base
13 station is current, the mobile station shall perform the following:
14 + The mobile station shall use the hash algorithm specified in 2.6.7.1 and the
15 stored value of the number of CDMA channels to determine the new CDMA
16 Channel and shall set FREQ_NEW to this new CDMA Channel. The mobile
17 station shall perform the following
18 ο If the stored information for any of the Forward Common Control

19 Channels and Primary Broadcast Control Channel on the CDMA channel
20 specified by FREQ_NEW is current, the mobile station shall perform the
21 following: If the Extended CDMA Channel List Message is being sent on
22 the old base station, set CDMACHs to the first CDMA Channel given in
23 the Extended CDMA Channel List Message for the old base station.
24 ◊ The mobile station shall use the hash algorithm specified in 2.6.7.1 to
25 select a new Forward Common Control Channel number in the range
26 1 to NUM_FCCCHs, where NUM_FCCCHs is the stored value. The
27 mobile station shall store the new Forward Common Control Channel
28 number as FCCCH_IDs.
29 ◊ If the stored information for this new Forward Common Control

30 Channel and Primary Broadcast Control Channel is current, the
32 – The mobile station shall set CONFIG_MSG_SEQs to the stored
33 information for this new Forward Common Control Channel and
34 Primary Broadcast Control Channel and the mobile station shall
35 set NGHBR_REC_LIST to the stored information for this new
36 Forward Common Control Channel and Primary Broadcast
37 Control Channel.
2-89
3GPP2 C.S0005-A v6.0
1 – If the band class corresponding to FREQ_NEW is not equal to

4 CDMABANDs to band class corresponding to FREQ_NEW and
5 shall set CDMACHs to FREQ_NEW, and tune to the new CDMA
6 Channel. The mobile station shall begin monitoring the new
7 Forward Common Control Channel/Primary Broadcast Control
8 Channel of the new base station.
9 ◊ If the stored information for this new Forward Common Control

10 Channel and Primary Broadcast Control Channel is not current, the
12 – The mobile station shall set CONFIG_MSG_SEQs,
13 A41_SYS_PAR_MSG_SEQs, UNI_NGHBR_LST_MSG_SEQs,
14 MC_RR_PAR_MSG_SEQs, EXT_GLOB_SERV_REDIR_MSG_SEQs,
15 EXT_CHAN_LST_MSG_SEQs, USER_ZONE_ID_MSG_SEQs, and
16 PRI_NGHBR_LST_MSG_SEQs to NULL.
17 – If the band class corresponding to FREQ_NEW is not equal to

20 CDMABANDs to band class corresponding to FREQ_NEW and
21 shall set CDMACHs to FREQ_NEW, and tune to the new CDMA
22 Channel. The mobile station shall begin monitoring the Primary
23 Broadcast Control Channel of the new base station.
24 ο If none of the Forward Common Control Channel and Primary Broadcast

25 Control Channel stored information on the CDMA channel specified by
26 FREQ_NEW are current, the mobile station shall perform the following:
27 ◊ The mobile station shall set CONFIG_MSG_SEQs,

28 A41_SYS_PAR_MSG_SEQs, UNI_NGHBR_LST_MSG_SEQs,
29 MC_RR_PAR_MSG_SEQs, EXT_GLOB_SERV_REDIR_MSG_SEQs,
31 PRI_NGHBR_LST_MSG_SEQs to NULL.
32 ◊ If the associated NGHBR_BANDs of the new base station in

33 NGHBR_REC_LIST of the old base station is not equal to
34 CDMABANDs or the associated NGHBR_FREQs of the new base
35 station in NGHBR_REC_LIST of the old base station is not equal to
37 CDMABANDs to NGHBR_BANDs, CDMACHs to NGHBR_FREQs, and
38 tune to the new CDMA Channel. Otherwise, the mobile station shall
39 set CDMACHs to the first CDMA Channel given in the Extended
40 CDMA Channel List Message for the old base station and tune to the
41 new CDMA channel.
2-90
3GPP2 C.S0005-A v6.0
1 ◊ Then the mobile station shall begin monitoring the Primary Broadcast
2 Control Channel of the new base station, using the same rate, code
3 rate, and code channel.
4 – If none of the Forward Common Control Channel and Primary Broadcast Control
5 Channel stored information on any of the frequencies of the new base station are
6 current, the mobile station shall perform the following:
7 + The mobile station shall set CONFIG_MSG_SEQs, A41_SYS_PAR_MSG_SEQs,
11
12 + If the associated NGHBR_BANDs or NGHBR_FREQs of the new base station

13 in NGHBR_REC_LIST of the old base station is not equal to CDMABANDs
14 and CDMACHs of the old base station respectively, the mobile station shall
15 set CDMABANDs to NGHBR_BANDs, CDMACHs to NGHBR_FREQs, and tune
16 to the new CDMA Channel. Otherwise, the mobile station shall set
17 CDMACHs to the first CDMA Channel given in the Extended CDMA Channel
18 List Message for the old base station and tune to the new CDMA channel.
19 + Then the mobile station shall begin monitoring the Primary Broadcast
20 Control Channel of the new base station, using the same rate, code rate, and
21 code channel.
25 station.
27 • Enter the System Determination Substate of the Mobile Station Initialization State with
28 a new system indication (see 2.6.1.1).

31 (see 2.6.2.2) and shall set PILOT_PNs to the pilot offset index of the base station
32 transmitting the new Forward Common Control Channel/Primary Broadcast Control
33 Channel.
34 • If the stored information for any of the Forward Common Control Channels and
35 Primary Broadcast Control Channel on the associated NGHBR_FREQs of the new
36 base station in NGHBR_REC_LIST of the old base station is current, the mobile
2-91
3GPP2 C.S0005-A v6.0
1 – The mobile station shall use the hash algorithm specified in 2.6.7.1 to select a
2 new Forward Common Control Channel number in the range 1 to
3 NUM_FCCCHs, where NUM_FCCCHs is the stored value. The mobile station shall
4 store the new Forward Common Control Channel number as FCCCH_IDs.
5 – If the mobile station has not stored configuration parameters for this new
6 Forward Common Control Channel and Primary Broadcast Control Channel, or
7 if the stored information is not current, the mobile station shall perform the
8 following:
9 + The mobile station shall set CONFIG_MSG_SEQs, A41_SYS_PAR_MSG_SEQs,


15 and CDMACHs respectively, the mobile station shall set CDMABANDs to
17 Channel.
18 + Then the mobile station shall begin monitoring the Primary Broadcast
19 Control Channel of the new base station, using the same rate, code rate, and
20 code channel.
21 – If the stored information for this new Forward Common Control Channel and
22 Primary Broadcast Control Channel is current, the mobile station shall perform
23 the following:
24 + The mobile station shall set CONFIG_MSG_SEQs to the stored information

25 for this new Forward Common Control Channel and Primary Broadcast
26 Control Channel and the mobile station shall set NGHBR_REC_LIST to the
27 stored information for this new Forward Common Control Channel and

31 and CDMACHs respectively, the mobile station shall set CDMABANDs to
33 Channel. The mobile station shall begin monitoring the new Forward
34 Common Control Channel/Primary Broadcast Control Channel of the new
35 base station.
36 • If none of the Forward Common Control Channel and Primary Broadcast Control
37 Channel stored information on the associated NGHBR_FREQs of the new base
38 station in NGHBR_REC_LIST of the old base station are current, the mobile station
39 shall perform the following:
2-92
3GPP2 C.S0005-A v6.0
1 – The mobile station shall set CONFIG_MSG_SEQs, A41_SYS_PAR_MSG_SEQs,

5 – If the associated NGHBR_BANDs or NGHBR_FREQs of the new base station in

7 CDMACHs respectively, the mobile station shall set CDMABANDs to
9 Channel.
10 – The mobile station shall begin monitoring the Primary Broadcast Control
11 Channel of the new base station, using the same rate, code rate, and code
12 channel.
16 station.
17 2.6.2.1.5 Primary Broadcast Control Channel Monitoring
18 2.6.2.1.5.1 General Overview
19 The Broadcast Control Channel is divided into 40, 80, or 160 ms slots called the Broadcast
20 Control Channel slots (see 3.1.3.5 in [2]). The Primary Broadcast Control Channel will be
21 used for control messages. Support for the Primary Broadcast Control Channel is
22 mandatory for mobile stations. The Primary Broadcast Control Channel will operate with
23 the Forward Common Control Channels and the Quick Paging Channels, or only with the
24 Forward Common Control Channels.
25 After a mobile station acquires and synchronizes with a new base station that supports a
26 Primary Broadcast Control Channel, the mobile station monitors the Primary Broadcast
27 Control Channel to receive overhead information. Once the mobile station has received the
28 updated overhead information from the Primary Broadcast Control Channel, the mobile
29 station may begin to monitor a Forward Common Control Channel or a Quick Paging
30 Channel, if it is supported.
31 2.6.2.1.5.2 Requirements
32 If the base station supports the Primary Broadcast Control Channel, the mobile station
33 shall monitor the Primary Broadcast Control Channel for overhead messages. If the mobile
34 station determines that the CONFIG_MSG_SEQ has changed, the mobile station shall
35 monitor the Primary Broadcast Control Channel to receive updated overhead messages.
36 2.6.2.1.6 System Reselection Procedures
37 If the mobile station supports more than one operating mode or the Remaining
2-93
3GPP2 C.S0005-A v6.0
1 Set/Neighbor Set contains pilots on frequencies different from the current frequency, the
2 mobile station shall enter the System Determination Substate of the Mobile Station
3 Initialization State with a system reselection indication (see 2.6.1.1) if all of the following are
4 true:
5 • RESELECT_INCLUDEDs is equal to ‘1’;
6 • The following inequality is satisfied:

7 –20 × log10 (Ec/Io) > EC_IO_THRESHs
8 where Ec/Io is the measured Ec/Io of the active pilot; and
9 • The following inequality is satisfied:

10 pilot_power < EC_THRESHs -115
11 where pilot_power (dBm/1.23 MHz) = 10 × log10 (PS) (dB) + mean input power
12 (dBm/1.23 MHz) and PS is the strength of the active pilot, as specified in 2.6.6.2.2.
13 2.6.2.1.7 Slotted Timer Expiration

14 Upon expiration of the slotted TMS Slotted timer, the mobile station shall disable the timer
15 and set SLOTTEDs to YES.
16 2.6.2.2 Response to Overhead Information Operation
17 The overhead messages on the Primary Broadcast Control Channel are:
18 • ANSI-41 System Parameters Message
19 • MC-RR Parameters Message
20 • Enhanced Access Parameters Message
21 • Universal Neighbor List Message
22 • User Zone Identification Message
23 • Private Neighbor List Message
24 • Extended Global Service Redirection Message
25 • Extended CDMA Channel List Message
26 • ANSI-41 RAND Message
27 The overhead messages on the Paging Channel are:

28 • System Parameters Message
29 • Access Parameters Message
30 • Neighbor List Message
31 • CDMA Channel List Message
32 • Extended System Parameters Message
33 • Global Service Redirection Message
2-94
3GPP2 C.S0005-A v6.0
1 • Extended Neighbor List Message
2 • General Neighbor List Message
7 The Response to Overhead Information Operation is performed whenever the mobile station
8 receives an overhead message. The mobile station updates internally stored information
9 from the received message’s data fields.
10 Configuration parameters and access parameters are received in the configuration

11 messages and the Access Parameters Message or the Enhanced Access Parameters Message.
12 The configuration messages on the Primary Broadcast Control Channel are:
13 • ANSI-41 System Parameters Message
20 The configuration messages on the Paging Channel are:

23 • CDMA Channel List Message
24 • Extended System Parameters Message
25 • Global Service Redirection Message
32 Associated with the set of configuration messages sent on each Paging Channel or Primary
33 Broadcast Control Channel is a configuration message sequence number
34 (CONFIG_MSG_SEQ). When the contents of one or more of the configuration messages
2-95
3GPP2 C.S0005-A v6.0
1 change, the configuration message sequence number is incremented. For each of the
2 configuration messages received, the mobile station stores the configuration message
3 sequence number contained in the configuration message (A41_SYS_PAR_MSG_SEQs,
4 MC_RR_PAR_MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LIST_MSG_SEQs,
6 UNI_NGHBR_LST_MSG_SEQs, CHAN_LIST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs,
7 GLOB_SERV_REDIR_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
8 EXT_CHAN_LST_MSG_SEQs, EXT_GLOB_SERV_REDIR_MSG_SEQs, or
9 PRI_NGHBR_LST_MSG_SEQs). The mobile station also stores the most recently received
10 configuration message sequence number (CONFIG_MSG_SEQs) contained in any message
11 (see 2.6.2.2.1, 2.6.2.2.3, 2.6.2.2.4, 2.6.2.2.5, 2.6.2.2.6, 2.6.2.2.7, 2.6.2.2.8, 2.6.2.2.9,
12 2.6.2.2.10, 2.6.2.2.11, 2.6.2.2.12, 2.6.2.2.13, 2.6.2.2.14, 2.6.2.2.17, and 2.6.2.3). The
13 mobile station examines the stored values of the configuration message sequence numbers
14 to determine whether the configuration parameters stored by the mobile station are
15 current.
16 The field EXT_SYS_PARAMETER in the System Parameters Message, when set equal to ‘0’,
17 indicates that the base station is not sending the Extended System Parameters Message.
18 When the mobile station receives the System Parameters Message with the
19 EXT_SYS_PARAMETER field set equal to ‘0’, the mobile station shall set
20 EXT_SYS_PAR_MSG_SEQs to CONFIG_MSG_SEQs to indicate that the Extended System
21 Parameters Message is current.
22 The field EXT_CHAN_LST in the System Parameters Message, when set equal to ‘0’,
23 indicates that the base station is not sending the Extended CDMA Channel List Message.
24 When the mobile station receives the System Parameters Message with the EXT_CHAN_LST
25 field set equal to ‘0’, the mobile station shall set EXT_CHAN_LST_MSG_SEQs to
26 CONFIG_MSG_SEQs to indicate that the Extended CDMA Channel List Message is current.
27 The field GEN_NGHBR_LST in the System Parameters Message, when set equal to ‘0’,
28 indicates that the base station is not sending the General Neighbor List Message. When the
29 mobile station receives the System Parameters Message with the GEN_NGHBR_LST field set
30 equal to ‘0’, the mobile station shall set the GEN_NGHBR_LST_MSG_SEQs to
31 CONFIG_MSG_SEQs to indicate that the General Neighbor List Message is current.
32 The field EXT_NGHBR_LST in the System Parameters Message, when set equal to ‘0’,
33 indicates that the base station is not sending the Extended Neighbor List Message. When
34 the mobile station receives the System Parameters Message with the EXT_NGHBR_LST field
35 set equal to ‘0’, the mobile station shall set EXT_NGHBR_LIST_MSG_SEQs to
36 CONFIG_MSG_SEQs to indicate that the Extended Neighbor List Message is current.
37 The field GLOBAL_REDIRECT in the System Parameters Message, when set equal to ‘0’,
38 indicates that the base station is not sending the Global Service Redirection Message. When
39 the mobile station receives the System Parameters Message with the GLOBAL_REDIRECT
40 field set equal to ‘0’, the mobile station shall set GLOB_SERV_REDIR_MSG_SEQs to
41 CONFIG_MSG_SEQs to indicate that the Global Service Redirection Message is current.
42 The field EXT_GLOBAL_REDIRECT in the System Parameters Message or MC-RR Parameters

43 Message, when set equal to ‘0’, indicates that the base station is not sending the Extended
2-96
3GPP2 C.S0005-A v6.0
1 Global Service Redirection Message. When the mobile station receives the System
2 Parameters Message or MC-RR Parameters Message with the EXT_GLOBAL_REDIRECT field
3 set equal to ‘0’, the mobile station shall set EXT_GLOB_SERV_REDIR_MSG_SEQs to
4 CONFIG_MSG_SEQs to indicate that the Extended Global Service Redirection Message is
5 current.
6 The field USER_ZONE_ID in the System Parameters Message or MC-RR Parameters
7 Message, when set equal to ‘0’, indicates that the base station is not sending the User Zone
8 Identification Message. When the mobile station receives the System Parameters Message or
9 MC-RR Parameters Message with the USER_ZONE_ID field set equal to ‘0’, the mobile
10 station shall set USER_ZONE_ID_MSG_SEQs to CONFIG_MSG_SEQs to indicate that the
11 User Zone Identification Message is current.
12 The field PRI_NGHBR_LIST in the System Parameters Message or MC-RR Parameters

13 Message, when set equal to ‘0’, indicates that the base station is not sending the Private
14 Neighbor List Message. When the mobile station receives the System Parameters Message or
15 MC-RR Parameters Message with the PRI_NGHBR_LIST field set equal to ‘0’, the mobile
16 station shall set PRI_NGHBR_LIST_MSG_SEQs to CONFIG_MSG_SEQs to indicate that the
17 Private Neighbor List Message is current.
18 The configuration message sequence number is also included in the General Page Message
19 and the Universal Page Message. This allows the mobile station to determine whether the
20 stored configuration parameters are current without waiting for a configuration message.
21 Access Parameters Messages or Enhanced Access Parameters Messages are independently

22 sequence-numbered by the ACC_MSG_SEQ field. The mobile station stores the most
23 recently received Access Parameters Message or Enhanced Access Parameters Messages
24 sequence number (ACC_MSG_SEQs).
25 Paging Channels, Broadcast Control Channels, and Forward Common Control Channels
26 shall be considered different if they are transmitted by different base stations, if they are
27 transmitted on different code channels, or if they are transmitted on different CDMA
28 Channels. Configuration and access parameters from one Paging Channel or Primary
29 Broadcast Control Channel shall not be used while monitoring a different Paging Channel
30 or Primary Broadcast Control Channel/Forward Common Control Channel except for
31 registration and authentication parameters while the mobile station is performing an access
32 probe handoff or access handoff. The mobile station shall ignore any overhead message
33 whose PILOT_PNr field is not equal to the pilot offset index (PILOT_PNs) of the base station
34 whose Paging Channel or Primary Broadcast Control Channel is being monitored.
35 The mobile station may store the configuration parameters from Paging Channels or
36 Primary Broadcast Control Channel it has recently monitored. When a mobile station
37 starts monitoring a Paging Channel or a Primary Broadcast Control Channel/Forward
38 Common Control Channel that it has recently monitored, the mobile station can determine
39 whether the stored parameters are current by examining the CONFIG_MSG_SEQs in a
40 configuration message or a page message.
41 The mobile station shall use a special value, NULL, to be stored in place of sequence
42 numbers for messages that have not been received or are marked as not current. The
43 special value NULL shall be unequal to any valid message sequence number.
2-97
3GPP2 C.S0005-A v6.0
1 The mobile station shall consider the stored configuration parameters to be current only if
2 all of the following conditions are true:
3 • If the mobile station is monitoring the Paging Channel, all stored configuration
4 message sequence numbers (SYS_PAR_MSG_SEQs, NGHBR_LIST_MSG_SEQs,
5 EXT_NGHBR_LIST_MSG_SEQs, CHAN_LIST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs,
6 GEN_NGHBR_LIST_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
7 PRI_NGHBR_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
8 EXT_GLOB_SERV_REDIR_MSG_SEQs and GLOB_SERV_REDIR_MSG_SEQs) are
9 equal to CONFIG_MSG_SEQs; and
10 • If the mobile station is monitoring the Forward Common Control Channel/ Primary
11 Broadcast Control Channel, all stored configuration message sequence numbers
12 (A41_SYS_PAR_MSG_SEQs, MC_RR_PAR_MSG_SEQs,
13 UNI_NGHBR_LST_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
14 PRI_NGHBR_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs, and
15 EXT_GLOB_SERV_REDIR_MSG_SEQs) are equal to CONFIG_MSG_SEQs; and
16 • CONFIG_MSG_SEQs is not equal to NULL; and
17 • No more than T31m seconds (see Annex D) have elapsed since the mobile station last
18 received a valid message on the Paging Channel or the Primary Broadcast Control
19 Channel/Forward Common Control Channel for which the parameters were stored.
20 If the configuration parameters are not current, the mobile station shall process the stored
21 parameters upon receipt of the configuration messages as described in 2.6.2.2.1, 2.6.2.2.3,
22 2.6.2.2.4, 2.6.2.2.5, 2.6.2.2.6, 2.6.2.2.7, 2.6.2.2.8, 2.6.2.2.9, 2.6.2.2.10, 2.6.2.2.11,
23 2.6.2.2.12, 2.6.2.2.13, 2.6.2.2.14, and 2.6.2.2.17.
24 2.6.2.2.1 System Parameters Message
25 Whenever a System Parameters Message is received on the Paging Channel, the

26 configuration message sequence number, CONFIG_MSG_SEQr, shall be compared to that
27 stored in SYS_PAR_MSG_SEQs. If the comparison results in a match, the mobile station
28 may ignore the message. If the comparison results in a mismatch, then the mobile station
29 shall process the remaining fields in the message as described in 2.6.2.2.1.1, 2.6.2.2.1.2,
30 2.6.2.2.1.3, 2.6.2.2.1.4, 2.6.2.2.1.5, and 2.6.2.2.1.6, 2.6.2.2.1.7, 2.6.2.2.1.8, and
31 2.6.2.2.1.9.
32 If PAGE_CHAN, REG_PRD, BASE_LAT, BASE_LONG, or PWR_REP_THRESH are not within

33 the valid ranges specified in 3.7.2.3.2.1, then the mobile station shall ignore the System
34 Parameters Message that contains them.
35 If BAND_CLASS is equal to ‘00001’ and if either EXT_SYS_PARAMETERSr is not equal to ‘1’
36 or EXT_NGHBR_LSTr is not equal to ‘1’, or both, the mobile station shall ignore the System
37 Parameters Message containing these fields.
38 2.6.2.2.1.1 Stored Parameters
39 The mobile station shall store the following parameters:
2-98
3GPP2 C.S0005-A v6.0
1 • Configuration message sequence number

2 (CONFIG_MSG_SEQs = CONFIG_MSG_SEQr,
3 SYS_PAR_MSG_SEQs = CONFIG_MSG_SEQr)
4 • Base station identification (BASE_IDs = BASE_IDr)
5 • Base station class (BASE_CLASSs = BASE_CLASSr)
6 • Maximum slot cycle index

7 (MAX_SLOT_CYCLE_INDEXs = MAX_SLOT_CYCLE_INDEXr)
8 • Home registration indicator (HOME_REGs = HOME_REGr)
9 • SID roamer registration indicator (FOR_SID_REGs = FOR_SID_REGr)
10 • NID roamer registration indicator (FOR_NID_REGs = FOR_NID_REGr)
11 • Power-up registration indicator (POWER_UP_REGs = POWER_UP_REGr)
12 • Power-down registration indicator (POWER_DOWN_REGs = POWER_DOWN_REGr)
13 • Parameter-change registration indicator (PARAMETER_REGs = PARAMETER_REGr)
14 • Search window size for the Active Set and Candidate Set
15 (SRCH_WIN_As = SRCH_WIN_Ar)
16 • Search window size for the Neighbor Set (SRCH_WIN_Ns = SRCH_WIN_Nr)
17 • Search window size for the Remaining Set (SRCH_WIN_Rs = SRCH_WIN_Rr)
18 • Maximum age for retention of Neighbor Set members

19 (NGHBR_MAX_AGEs = NGHBR_MAX_AGEr)
20 • Power control reporting threshold (PWR_REP_THRESHs = PWR_REP_THRESHr)
21 • Power control reporting frame count (PWR_REP_FRAMESs = PWR_REP_FRAMESr)
22 • Threshold report mode indicator

23 (PWR_THRESH_ENABLEs = PWR_THRESH_ENABLEr)
24 • Periodic report mode indicator (PWR_PERIOD_ENABLEs = PWR_PERIOD_ENABLEr).
25 • Power report delay (PWR_REP_DELAYs = PWR_REP_DELAYr)
26 • Pilot detection threshold (T_ADDs = T_ADDr)
27 • Pilot drop threshold (T_DROPs = T_DROPr)
28 • Active Set versus Candidate Set comparison threshold (T_COMPs = T_COMPr)
29 • Drop timer value (T_TDROPs = T_TDROPr)
30 • Extended System Parameters Message sent

31 (EXT_SYS_PARAMETERs = EXT_SYS_PARAMETERr)
32 • Global Service Redirection Message sent

33 (GLOBAL_REDIRECTs = GLOBAL_REDIRECTr)
34 • Extended Global Service Redirection Message sent

35 (EXT_GLOBAL_REDIRECTs = EXT_GLOBAL_REDIRECTr)
2-99
3GPP2 C.S0005-A v6.0
1 • Extended Neighbor List Message sent

2 (EXT_NGHBR_LSTs = EXT_NGHBR_LSTr)
3 • General Neighbor List Message sent

4 (GEN_NGHBR_LSTs = GEN_NGHBR_LSTr)
5 • User Zone Identification Message sent

6 (USER_ZONE_IDs = USER_ZONE_IDr)
7 • Private Neighbor List Message sent

8 (PRI_NGHBR_LSTs = PRI_NGHBR_LSTr)
9 • Extended CDMA Channel List Message sent

10 (EXT_CHAN_LISTs = EXT_CHAN_LISTr)
11 The mobile station shall also store the following parameters if the mobile station is not in
12 the Origination Attempt Substate or Page Response Substate:
15 • Registration zone (REG_ZONEs = REG_ZONEr)
16 • Number of registration zones to be retained (TOTAL_ZONESs = TOTAL_ZONESr)
17 • Zone timer length (ZONE_TIMERs = ZONE_TIMERr)
18 • Multiple SID storage indicator (MULT_SIDSs = MULT_SIDSr)
19 • Multiple NID storage indicator (MULT_NIDSs = MULT_NIDSr)
20 • Registration period (REG_PRDs = REG_PRDr)
21 • Base station latitude (BASE_LATs = BASE_LATr)
22 • Base station longitude (BASE_LONGs = BASE_LONGr)
23 • Registration distance (REG_DISTs = REG_DISTr)
24 If EXT_SYS_PARAMETERs is equal to ‘0’, then the mobile station shall perform the
25 following:
26 • Set EXT_SYS_PAR_MSG_SEQs to CONFIG_MSG_SEQs,
27 • Set BCAST_INDEXs to MAX_SLOT_CYCLE_INDEXs,
28 • Set IMSI_O to IMSI_M by setting IMSI_O_Ss to IMSI_M_Sp (i.e., setting IMSI_O_S1s

29 to IMSI_M_S1p and IMSI_O_S2s to IMSI_M_S2p), MCC_Os to MCC_Mp,
30 IMSI_O_11_12s to IMSI_M_11_12p, and IMSI_O_ADDR_NUMs to
31 IMSI_M_ADDR_NUMp,
32 • Set RESELECT_INCLUDEDs to ‘0’,
33 • For Band Class 0, if the mobile station determines it is operating in Korea, set
34 P_REVs to ‘00000010’; otherwise, set P_REVs to ‘00000011’. For For Band Class 2
35 and Band Class 3, set P_REVs to ‘00000011’. For Band Class 1 and Band Class 4,
36 set P_REVs to ‘00000001’, and
2-100
3GPP2 C.S0005-A v6.0
1 • Set P_REV_IN_USEs to the lesser value of P_REVs and MOB_P_REVp of the current
2 band class.
3 If EXT_CHAN_LISTs is equal to ‘0’, then the mobile station shall set
4 EXT_CHAN_LST_MSG_SEQs to CONFIG_MSG_SEQs.
5 If GLOBAL_REDIRECTs is equal to ‘0’, then the mobile station shall set GLOB_SERV-
6 _REDIR_MSG_SEQs to CONFIG_MSG_SEQs.
7 If EXT_GLOBAL_REDIRECTs is equal to ‘0’, then the mobile station shall set

8 EXT_GLOB_SERV_REDIR_MSG_SEQs to CONFIG_MSG_SEQs.
9 If EXT_NGHBR_LSTs is equal to ‘0’, then the mobile station shall set

10 EXT_NGHBR_LST_MSG_SEQs to CONFIG_MSG_SEQs.
11 If GEN_NGHBR_LSTs is equal to ‘0’, then the mobile station shall perform the following:
12 • Set GEN_NGHBR_LST_MSG_SEQs to CONFIG_MSG_SEQs.
13 • Set the SRCH_WIN_NGHBR field of NGHBR_REC to SRCH_WIN_Ns for all entries.
14 • Set the SRCH_OFFSET_NGHBR field of NGHBR_REC to ‘000’ for all entries.
15 • Set the TIMING_INCL field of NGHBR_REC to ‘0’ for all entries.

16 • Set NUM_ANALOG_NGHBRs to ‘000’ and ANALOG_NGHBR_LIST to NULL.
17 • If EXT_NGHBR_LSTs is equal to ‘0’:
18 – Set the SEARCH_PRIORITY field of the NGHBR_REC to ‘10’ (high) for all entries.
19 – Set the NGHBR_BAND field of the NGHBR_REC to CDMABANDs for all entries.
20 – Set the NGHBR_FREQ field of the NGHBR_REC to CDMACHs for all entries.
21 If GEN_NGHBR_LSTs is equal to ‘1’, GEN_NGHBR_LST_MSG_SEQs is equal to

22 CONFIG_MSG_SEQs, and SETTING_SEARCH_WIN is equal to ‘1’, the mobile station shall
24 • Set the SRCH_WIN_NGHBR field of each NGHBR_REC to SEARCH_WIN_Ns for all
25 NGHBR_SET_SIZEs entries.
26 • Set SETTING_SEARCH_WIN to ‘0’.

27 If USER_ZONE_IDs is equal to ‘0’, then the mobile station shall perform the following:
28 • Set USER_ZONE_ID_MSG_SEQs to CONFIG_MSG_SEQs.
29 • Set the UZID field of the UZ_REC to ‘0000000000000000’ for all entries.
30 • Set the UZ_REV field of the UZ_REC to ‘0000’ for all entries.
31 • Set the TEMP_SUB field of the UZ_REC to ‘0’ for all entries.
32 If USER_ZONE_IDs is equal to ‘1’ and the mobile station does not support Tiered Services,
33 then the mobile station shall set USER_ZONE_ID_MSG_SEQs to CONFIG_MSG_SEQs.
34 If PRI_NGHBR_LISTs is equal to ‘0’, then the mobile station shall set

35 PRI_NGHBR_LIST_MSG_SEQs to CONFIG_MSG_SEQs.
2-101
3GPP2 C.S0005-A v6.0
1 If PRI_NGHBR_LISTs is equal to ‘1’ and the mobile station does not support Tiered Services,
2 then the mobile station shall set PRI_NGHBR_LIST_MSG_SEQs to CONFIG_MSG_SEQs.
3 The mobile station shall ignore any fields at the end of the System Parameters Message that
4 are not defined according to the protocol revision level (MOB_P_REVp of the current band
5 class) being used by the mobile station.
6 2.6.2.2.1.2 Paging Channel Assignment Change

7 If the number of Paging Channels specified in the System Parameters Message
8 (PAGE_CHANr) is different from PAGE_CHANs, the mobile station shall use the hash
9 algorithm specified in 2.6.7.1 to select a new Paging Channel number in the range 1 to
10 PAGE_CHANr. The mobile station shall store the new Paging Channel number as
11 PAGECHs. The mobile station shall then set PAGE_CHANs to PAGE_CHANr. The mobile
12 station shall set ACC_MSG_SEQs to NULL. If the mobile station has not stored
13 configuration parameters for the new Paging Channel, or if the stored parameters are not
14 current (see 2.6.2.2), the mobile station shall set CONFIG_MSG_SEQs, SYS_PAR_MSG-
15 _SEQs, NGHBR_LST_MSG_SEQs, EXT_NGHBR_LST_MSG_SEQs,
16 GEN_NGHBR_LST_MSG_SEQs, CHAN_LST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs,
17 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LST_MSG_SEQs, and
18 EXT_GLOB_SERV_REDIR_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs, and
19 GLOB_SERV_REDIR_MSG_SEQs to NULL. The mobile station shall then begin monitoring
20 the new Paging Channel as specified in 2.6.2.1.1.
21 2.6.2.2.1.3 RESCAN Parameter

22 If the RESCANr field in the System Parameters Message equals ‘1’, the mobile station shall
24 rescan indication (see 2.6.1.1).
25 2.6.2.2.1.4 Roaming Status
26 The mobile station shall determine the roaming status for the mobile station (see 2.6.5.3).
27 The mobile station should indicate to the user whether the mobile station is roaming.
28 2.6.2.2.1.5 Registration
29 The mobile station shall update stored variables and perform other registration procedures
30 as specified in 2.6.5.5.2.2.
31 2.6.2.2.1.6 Slot Cycle Index

32 The mobile station shall set SLOT_CYCLE_INDEXs to the smaller of: the preferred slot cycle
33 index SLOT_CYCLE_INDEXp and the maximum slot cycle index
34 MAX_SLOT_CYCLE_INDEXs. If the mobile station is operating in the slotted mode, it shall
35 set its slot cycle length as described in 2.6.2.1.1.3.
2-102
3GPP2 C.S0005-A v6.0
1 2.6.2.2.1.7 PACA Disable for SID Change

2 If PACAs is equal to enabled, and SIDs is not equal to PACA_SIDs, the mobile station shall
3 set PACAs to disabled and PACA_CANCEL to ‘0’, shall disable the PACA state timer, and
4 should indicate to the user that the PACA call has been canceled.
5 2.6.2.2.1.8 Retry Delay Disable for Packet Zone ID or SID/NID Change

6 The mobile station shall set RETRY_DELAYs[RETRY_TYPE] to 0 when the mobile station
7 determines that the Packet Zone Identification or the System Identification/Network
8 Identification (SID/NID pair) has been changed, where RETRY_TYPE is equal to ‘001’, ‘010’,
9 or ‘011’.
10 2.6.2.2.1.9 Encryption key reset for SID/NID Change

11 The mobile station shall reset ENC_KEYs to NULL when the mobile station determines that
12 the System Identification/Network Identification (SID/NID pair) has been changed.
13 2.6.2.2.2 Access Parameters Message

14 Whenever an Access Parameters Message is received on the Paging Channel, the sequence
15 number, ACC_MSG_SEQr, shall be compared to ACC_MSG_SEQs. If the comparison
16 results in a match, the mobile station may ignore the message. If the comparison results in
17 a mismatch, then the mobile station shall process the remaining fields in the message as
18 follows.
19 If PROBE_PN_RAN, MAX_REQ_SEQ, or MAX_RSP_SEQ are not within the valid ranges

20 specified in 3.7.2.3.2.2, then the mobile station shall ignore the Access Parameters Message
21 that contains them.

23 • Access Parameters Message sequence number (ACC_MSG_SEQs = ACC_MSG_SEQr)
24 • Number of Access Channels (ACC_CHANs = ACC_CHANr)
25 • Nominal transmit power offset (NOM_PWRs = NOM_PWRr)
26 • Initial power offset for access (INIT_PWRs = INIT_PWRr)
27 • Power increment (PWR_STEPs = PWR_STEPr)
28 • Number of access probes (NUM_STEPs = NUM_STEPr)
29 • Maximum Access Channel message capsule size (MAX_CAP_SZs = MAX_CAP_SZr)
30 • Access Channel preamble length (PAM_SZs = PAM_SZr)
31 • Persistence modifier for Access Channel attempts for registrations which are not
32 responses to the Registration Request Order (REG_PSISTs = REG_PSISTr)
33 • Persistence modifier for Access Channel attempts for message transmissions

34 (MSG_PSISTs = MSG_PSISTr)
2-103
3GPP2 C.S0005-A v6.0
1 • If PSIST_EMG_INCLr is equal to ‘0’, the mobile station shall set the persistence
2 modifier for emergency calls from mobile stations in access overload classes 0 to 9
3 (PSIST_EMGs) to ‘000’; otherwise, the mobile station shall set PSIST_EMGs equal
4 to PSIST_EMGr.
5 • Time randomization for Access Channel probes

6 (PROBE_PN_RANs = PROBE_PN_RANr)
7 • Acknowledgment timeout (ACH_ACC_TMOs = ACC_TMOr)
8 • Access Channel probe backoff range (PROBE_BKOFFs = PROBE_BKOFFr)
9 • Access Channel probe sequence backoff range (BKOFFs = BKOFFr)
10 • Maximum number of probe sequences for an Access Channel request

11 (MAX_REQ_SEQs = MAX_REQ_SEQr)
12 • Maximum number of probe sequences for an Access Channel response

13 (MAX_RSP_SEQs = MAX_RSP_SEQr)
14 • If CDMABANDs is equal to ‘0’, the mobile station shall set extended nominal
15 transmit power NOM_PWR_EXTs to ‘0’; otherwise, the mobile station shall store
16 extended nominal transmit power (NOM_PWR_EXTs = NOM_PWR_EXTr).
17 • IC threshold (IC_THRESHs = -7)
20 • Authentication mode (if AUTHr is equal to ‘00’ or ‘01’, then AUTHs = AUTHr;
21 otherwise AUTHs = ‘01’)
22 • Random challenge value (RANDs = RANDr)
23 The mobile station shall ignore any fields at the end of the Access Parameters Message
24 which are not defined according to the protocol revision level (MOB_P_REVp of the current
25 band class) being used by the mobile station.
26 The mobile station shall store the persistence parameter number according to the following
27 rule: If the mobile station’s access overload class is in the range 0-9, set PSISTs equal to
28 PSIST(0-9)r; otherwise set PSISTs equal to PSIST(n)r, where n is equal to the mobile station
29 access overload class.
30 The mobile station shall store the Access Control based on Call Type (ACCT) information as
31 follows:
32 • Set ACCT_SO_LIST to NULL.
33 • Set ACCT_SO_GRP_LIST to NULL.

34 • If ACCT_INCLr is equal to ‘1’ and ACCOLCp is in the range 0 to 9, then the mobile
36 – Set ACCT_INCL_EMGs to ACCT_INCL_EMGr.
37 – If ACCT_SO_INCLr is equal to ‘1’, then for each ACCT_SOr included in this

38 message:
2-104
3GPP2 C.S0005-A v6.0
1 + If ACCT_AOC_BITMAP_INCLr is equal to ‘0’, or if ACCT_AOC_BITMAP_INCLr

2 is equal to ‘1’ and the bit in the associated ACCT_AOC_BITMAP1r
3 corresponding to the mobile station’s ACCOLCp (see Table 3.7.2.3.2.2-1) is
4 equal to ‘1’, then add ACCT_SOr to ACCT_SO_LIST.
5 – If ACCT_SO_GRP_INCLr is equal to ‘1’, then for each ACCT_SO_GRPr included in

6 this message:
7 + If ACCT_AOC_BITMAP_INCLr is equal to ‘0’, or if ACCT_AOC_BITMAP_INCLr
8 is equal to ‘1’ and the bit in the associated ACCT_AOC_BITMAP2r
9 corresponding to the mobile station’s ACCOLCp (see Table 3.7.2.3.2.2-1) is
10 equal to ‘1’, then add ACCT_SO_GRPr to ACCT_SO_GRP_LIST.
11 The mobile station shall set CURR_ACC_MSG_SEQ equal to ACC_MSG_SEQs.
12 2.6.2.2.3 Neighbor List Message

13 Whenever a valid Neighbor List Message is received on the current Paging Channel
14 (PAGECHs), the configuration message sequence number, CONFIG_MSG_SEQr, shall be
15 compared to that stored in NGHBR_LST_MSG_SEQs. If the comparison results in a match,
16 the mobile station shall ignore the message. If the comparison results in a mismatch, then
17 the mobile station shall process the remaining fields in the message as follows.
18 If the PILOT_INC field is not within the valid range specified in 3.7.2.3.2.3, then the mobile
19 station shall ignore the Neighbor List Message that contains it.

23 NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr)
24 • Pilot PN sequence offset increment (PILOT_INCs = PILOT_INCr)
25 The mobile station shall set NGHBR_SET_SIZEs to the number of neighboring base stations
26 contained in the Neighbor List Message.
27 For each of the neighboring base stations contained in the Neighbor List Message, the
28 mobile station shall do the following:
29 • If the ith occurrence of NGHBR_CONFIGr is equal to ‘000’, ‘001’, or ‘010’, set the
30 NGHBR_CONFIG field of NGHBR_REC[i] to the ith occurrence of NGHBR_CONFIGr;
31 otherwise, set the NGHBR_CONFIG field of NGHBR_REC [i] to ‘011’.
32 • Set the NGHBR_PN field of NGHBR_REC [i] to the ith occurrence of NGHBR_PNr.
33 If GEN_NGHBR_LST_MSG_SEQs is not equal to CONFIG_MSG_SEQs, the mobile station

35 • Set the SEARCH_PRIORITY field of the NGHBR_REC to ‘10’ (high) for all
37 • Set the NGHBR_BAND field of NGHBR_REC to CDMABANDs for all

2-105
3GPP2 C.S0005-A v6.0
1 • Set the NGHBR_FREQ field of NGHBR_REC to CDMACHs for all NGHBR_SET_SIZEs

2 entries.
3 • Set the SRCH_WIN_NGHBR field of NGHBR_REC to SRCH_WIN_Ns for all

6 • Set NUM_ANALOG_NGHBRs to ‘000’ and set ANALOG_NGHBR_LIST to NULL.
7 The mobile station shall set the ACCESS_ENTRY_HO field of the NGHBR_REC to ‘0’ for all
8 NGHBR_SET_SIZEs entries if any of the following conditions are met:
9 • EXT_SYS_PARAMETERs is equal to ‘0’,
10 • NGHBR_SET_ENTRY_INFOs is equal to ‘0’, or
11 • EXT_SYS_PAR_MSG_SEQs is not equal to CONFIG_MSG_SEQs.
12 The mobile station shall set the ACCESS_HO_ALLOWED field of the NGHBR_REC to ‘0’ for
13 all NGHBR_SET_SIZEs entries if any of the following conditions are met:
15 • NGHBR_SET_ACCESS_INFOs is equal to ‘0’, or
17 The mobile station shall update the idle handoff Neighbor Set (see 2.6.2.1.4) so that it
18 consists only of pilot offsets listed in the Neighbor List Message. If the Neighbor List
19 Message contains more pilot offsets than the mobile station can store, the mobile station
20 shall store the pilot offsets beginning at the start of the Neighbor List Message, up to the
21 limits of the mobile station’s Neighbor Set storage capacity.
22 2.6.2.2.4 CDMA Channel List Message
23 Whenever a CDMA Channel List Message is received on the Paging Channel, the
25 stored in CHAN_LST_MSG_SEQs. If the comparison results in a match, the mobile station
26 may ignore the message. If the comparison results in a mismatch, then the mobile station
27 shall process the remaining fields in the message as follows.

31 CHAN_LST_MSG_SEQs = CONFIG_MSG_SEQr)
32 The mobile station shall perform the following:

33 • If both SYS_PAR_MSG_SEQs and EXT_SYS_PAR_MSG_SEQs are is current,
34 – If EXT_CHAN_LISTs is equal to ‘1’, the mobile station shall ignore this message.
35 – If EXT_CHAN_LISTs is equal to ‘0’, the mobile station shall process this message
36 as described below.
2-106
3GPP2 C.S0005-A v6.0
1 • Otherwise, the mobile station shall process this message after SYS_PAR_MSG_SEQs
2 and EXT_SYS_PAR_MSG_SEQs become current.
3 The mobile station shall use the hash algorithm specified in 2.6.7.1 and the number of
4 channels listed in the CDMA Channel List Message to determine the CDMA Channel
5 (Frequency Assignment) for its Paging Channel. If the CDMA Frequency Assignment has
6 changed (the computed CDMA Channel is different from CDMACHs), the mobile station
7 shall perform the following actions:
8 • Set CDMACHs to the new CDMA Channel.
9 • Set PAGE_CHANs to ‘1’.
10 • Set PAGECHs to the Primary Paging Channel.
11 • If the stored configuration parameters is not current (see 2.6.2.2) for the
12 corresponding base station and frequency assignment, set CONFIG_MSG_SEQs,
13 SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs, CHAN_LST_MSG_SEQs,
15 EXT_SYS_PAR_MSG_SEQs, GLOB_SERV_REDIR_MSG_SEQs, USER_ZONE_ID-
16 _MSG_SEQs, PRI_NGHBR_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
17 EXT_GLOB_SERV_REDIR_MSG_SEQs, and ACC_MSG_SEQs to NULL.
18 • Tune to the new CDMA Channel.
19 2.6.2.2.5 Extended System Parameters Message

20 Whenever an Extended System Parameters Message is received on the Paging Channel, the
22 stored in EXT_SYS_PAR_MSG_SEQs. If the comparison results in a match, the mobile
23 station may ignore the message. If the comparison results in a mismatch, then the mobile
24 station shall process the remaining fields in the message as follows.
25 If the protocol revision level supported by the mobile station (MOB_P_REVp) is less than the
26 minimum protocol revision level supported by the base station (MIN_P_REVr), the mobile
27 station shall enter the System Determination Substate of the Mobile Station Initialization State
28 with a protocol mismatch indication (see 2.6.1.1). Otherwise, the mobile station shall store
29 the following parameters:

32 EXT_SYS_PAR_MSG_SEQs= CONFIG_MSG_SEQr)
33 • Preferred Access Channel MSID type (PREF_MSID_TYPEs = PREF_MSID_TYPEr)
34 • Broadcast slot cycle index (BCAST_INDEXs = BCAST_INDEXr)
35 • The mobile station shall set its operational IMSI, IMSI_O, as follows:
36 – If IMSI_T_SUPPORTEDr is equal to ‘0’, the mobile station shall set IMSI_O to
37 IMSI_Mp.
38 – If IMSI_T_SUPPORTEDr is equal to ‘1’ and the mobile station’s IMSI_Tp has been
39 programmed, the mobile station shall set IMSI_O to IMSI_Tp.
2-107
3GPP2 C.S0005-A v6.0
1 – If IMSI_T_SUPPORTEDr is equal to ‘1’ and the mobile station’s IMSI_Tp has not
2 been programmed, the mobile station shall set IMSI_O to IMSI_Mp.
3 – If IMSI_O has been changed, the mobile station shall set SYS_PAR_MSG_SEQs
4 and CHAN_LST_MSG_SEQs and EXT_CHAN_LST_MSG_SEQs to NULL and set
5 PAGE_CHANs to ‘1’.
6 • If MCCr = ‘1111111111’ and IMSI_11_12r = ‘1111111’, the mobile station shall set
7 the IMSI_O to IMSI_Mp and store:
8 – Mobile Country Code (MCCs = MCC_Mp) and
9 – IMSI 11th and 12th digits (IMSI_11_12s = IMSI_M_11_12p);
10 otherwise, the mobile station shall store:

11 – Mobile Country Code (MCCs = MCCr) and
12 – IMSI 11th and 12th digits (IMSI_11_12s = IMSI_11_12r).
13 • If IMSI_O is set to the IMSI_M, the mobile station shall set:

14 – IMSI_O_Ss to IMSI_M_Sp (i.e., IMSI_O_S1s to IMSI_M_S1p and IMSI_O_S2s to
15 IMSI_M_S2p)
16 – IMSI_O_11_12s to IMSI_M_11_12p
17 – MCC_Os to MCC_Mp
18 – IMSI_O_ADDR_NUMs to IMSI_M_ADDR_NUMp
19 • If IMSI_O is set to the IMSI_T, the mobile station shall set:

20 – IMSI_O_Ss to IMSI_T_Sp (i.e., IMSI_O_S1s to IMSI_T_S1p and IMSI_O_S2s to
21 IMSI_T_S2p).
22 – IMSI_O_11_12s to IMSI_T_11_12p
23 – MCC_Os to MCC_Tp
24 – IMSI_O_ADDR_NUMs to IMSI_T_ADDR_NUMp
25 • If IMSI_O has been changed, the mobile station shall set SYS_PAR_MSG_SEQs,
26 CHAN_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs to NULL, and set PAGE_CHANs
27 to ‘1’, and set PAGECHs to the Primary Paging Channel.
28 • Protocol revision level (P_REVs = P_REVr) if included in the message; otherwise, set
29 P_REVs as follows:
30 – For Band Class 0, if the mobile station determines it is operating in Korea, set
31 P_REVs to ‘00000010’; otherwise, set P_REVs to ‘00000011’.
32 – For Band Class 2 and Band Class 3, set P_REVs to ‘00000011’.
33 – For Band Class 1 and Band Class 4, set P_REVs to ‘00000001’.
2-108
3GPP2 C.S0005-A v6.0
1 • Minimum protocol revision level (MIN_P_REVs = MIN_P_REVr) if included in the

2 message; otherwise, MIN_P_REVs = ‘00000010’ for Band Class 0, MIN_P_REVs =
3 ‘00000001’ for Band Class 1 and Band Class 4, and MIN_P_REVs = ‘00000011’ for
4 Band Class 3.
5 • Protocol revision level currently in use (P_REV_IN_USEs = the lesser value of P_REVs
6 and MOB_P_REVp of the current band class)
7 • Slope of the handoff add/drop criterion (SOFT_SLOPEs = SOFT_SLOPEr) if included

8 in the message; otherwise, SOFT_SLOPEs = ‘000000’.
9 • Intercept of the handoff add criterion (ADD_INTERCEPTs = ADD_INTERCEPTr)
10 • Intercept of the handoff drop criterion (DROP_INTERCEPTs = DROP_INTERCEPTr)
11 • Delete foreign TMSI (DELETE_FOR_TMSIs = DELETE_FOR_TMSIr)
12 • Use TMSI (USE_TMSIs = USE_TMSIr)
13 • TMSI zone length (TMSI_ZONE_LENs = TMSI_ZONE_LENr)
14 • TMSI zone number (TMSI_ZONEs = TMSI_ZONEr)
15 • Maximum number of alternative service options (MAX_NUM_ALT_SOs =

16 MAX_NUM_ALT_SOr) if included in the message; otherwise, MAX_NUM_ALT_SOs =
17 ‘000’.
18 • System reselection indicator (RESELECT_INCLUDEDs = RESELECT_INCLUDEDr) if
19 included in the message; otherwise, RESELECT_INCLUDEDs = ‘0’.
20 • Pilot reporting indicator (PILOT_REPORTs = PILOT_REPORTr)
21 • Neighbor Set access entry handoff information indicator

22 (NGHBR_SET_ENTRY_INFOs = NGHBR_SET_ENTRY_INFOr) if included in the
23 message; otherwise, NGHBR_SET_ENTRY_INFOs = ‘0’.
24 • Neighbor Set access handoff information indicator (NGHBR_SET_ACCESS_INFOs =

25 NGHBR_SET_ACCESS_INFOr) if included in the message; otherwise,
26 NGHBR_SET_ACCESS_INFOs = ‘0’.
27 • Short Data Burst supported indicator (SDB_SUPPORTEDs = SDB_SUPPORTEDr)
28 • Nominal reverse traffic channel output power offset relative to Reverse Pilot Channel
29 power (RLGAIN_TRAFFIC_PILOTs = RLGAIN_TRAFFIC_PILOTr)
30 • Broadcast GPS Assist Indicator (BROADCAST_GPS_ASSTs =

31 BROADCAST_GPS_ASSTr)
32 • Reverse Power Control Delay (REV_PWR_CNTL_DELAYs = REV_PWR_CNTL_DELAYr)

33 if included
34 • Permission for the mobile station to request QoS settings in the Origination Message,
35 Origination Continuation Message, or Enhanced Origination Message (MOB_QOSs =
36 MOB_QOSr)
37 • If ENC_SUPPORTEDr is equal to ‘1’, the mobile station shall store:
2-109
3GPP2 C.S0005-A v6.0
1 – Signaling encryption supported indicator (SIG_ENCRYPT_SUPs =

2 SIG_ENCRYPT_SUPr)
3 – User information encryption supported indicator (UI_ENCRYPT_SUPs =

4 UI_ENCRYPT_SUPr)
5 – Store encryption key indicator (STORE_KEYs = STORE_KEYr)
6 • Sync ID supported indicator (USE_SYNC_IDs = USE_SYNC_IDr)
7 • Concurrent services supported indicator (CS_SUPPORTEDs = CS_SUPPORTEDr)
8 • Primary Broadcast Control Channel supported indicator (BCCH_SUPPORTEDs =

9 BCCH_SUPPORTEDr).
10 • Pilot information request supported indicator (PILOT_INFO_REQ_SUPPORTEDs =

11 PILOT_INFO_REQ_SUPPORTEDr).
12 If BCCH_SUPPORTEDs equals ‘1’, the mobile station shall enter the System Determination
13 Substate of the Mobile Station Initialization State with a new system indication.
14 If P_REV_IN_USEs has been changed, the mobile station shall set ACC_MSG_SEQs,
15 CURR_ACC_MSG_SEQ, SYS_PAR_MSG_SEQs, EXT_NGHBR_LST_MSG_SEQs,
16 GEN_NGHBR_LST_MSG_SEQs, and GLOB_SERV_REDIR_MSG_SEQs to NULL.
17 If NGHBR_SET_ENTRY_INFO is equal to ‘1’, the mobile station shall store the access entry
18 handoff in order and message processing operation indicator (ACC_ENT_HO_ORDERs =
19 ACC_ENT_HO_ORDERr).
20 If the mobile station supports packet data service options and the PACKET_ZONE_ID field is
21 included in the message, the mobile station shall store the packet data services zone
22 identifier (PACKET_ZONE_IDs = PACKET_ZONE_IDr); otherwise, the mobile station shall set
23 PACKET_ZONE_IDs to ‘00000000’.
24 If RESELECT_INCLUDEDs is equal to ‘1’, the mobile station shall store:
25 • Pilot power threshold (EC_THRESHs = EC_THRESHr)
26 • Pilot Ec/Io threshold (EC_IO_THRESHs = EC_IO_THRESHr)
27 If NGHBR_SET_ACCESS_INFOs is equal to ‘1’, the mobile station shall store:
28 • Access handoff permitted indicator (ACCESS_HOs = ACCESS_HOr)
29 • Access probe handoff permitted indicator (ACCESS_PROBE_HOs =

30 ACCESS_PROBE_HOr)
31 • If ACCESS_PROBE_HOs is equal to ‘1’, access handoff list update permitted

32 indicator (ACC_HO_LIST_UPDs = ACC_HO_LIST_UPDr)
33 • Maximum number of times that the mobile station is permitted to perform an access
34 probe handoff (MAX_NUM_PROBE_HOs = MAX_NUM_PROBE_HOr)
35 • Access handoff permitted for message response indicator (ACCESS_HO_MSG_RSPs =

36 ACCESS_HO_MSG_RSPr)
2-110
3GPP2 C.S0005-A v6.0
1 • Access probe handoff permitted for other messages indicator

2 (ACC_PROBE_HO_OTHER_MSGs = ACC_PROBE_HO_OTHER_MSGr)
3 If NGHBR_SET_ENTRY_INFOs or NGHBR_SET_ACCESS_INFOs is equal to ‘1’, the mobile

4 station shall store the size of the Neighbor Set (NGHBR_SET_SIZEs = NGHBR_SET_SIZEr).
5 If NGHBR_SET_ENTRY_INFOs is equal to ‘0’, then for all NGHBR_SET_SIZEs occurrences of

6 ACCESS_ENTRY_HO, the mobile station shall set the ACCESS_ENTRY_HO field of
7 NGHBR_REC[i] to ‘0’.
8 If NGHBR_SET_ENTRY_INFOs is equal to ‘1’, then for all NGHBR_SET_SIZEs occurrences of
10 NGHBR_REC[i] to the ith occurrence of ACCESS_ENTRY_HOr.
11 If NGHBR_SET_ACCESS_INFOs is equal to ‘0’, then for all NGHBR_SET_SIZEs occurrences

12 of ACCESS_HO_ALLOWED, the mobile station shall set the ACCESS_HO_ALLOWED field of
14 If NGHBR_SET_ACCESS_INFOs is equal to ‘1’, then for all NGHBR_SET_SIZEs occurrences
16 NGHBR_REC[i] to the ith occurrence of ACCESS_HO_ALLOWEDr.
17 The mobile station shall set all bits of TMSI_CODEs-p to ‘1’ if all of the following conditions
18 are met:
19 • The bits of TMSI_CODEs-p are not all equal to ‘1’,
20 • DELETE_FOR_TMSIs is equal to ‘1’, and
21 • ASSIGNING_TMSI_ZONE_LENs-p is not equal to TMSI_ZONE_LENs, or the least

22 significant ASSIGNING_TMSI_ZONE_LENs-p octets of ASSIGNING_TMSI_ZONEs-p
23 are not equal to TMSI_ZONEs.
24 If the mobile station supports the Quick Paging Channel operation:

25 • The mobile station shall set QPCH_SUPPORTEDs to QPCH_SUPPORTEDr.
26 • If QPCH_SUPPORTEDr = ‘1’:
27 – The mobile station shall set QPCH_RATEs to QPCH_RATEr.
28 – If the number of Quick Paging Channels specified in the received message

29 (NUM_QPCHr) is different from NUM_QPCHs, the mobile station shall use the
30 hash algorithm specified in 2.6.7.1 to select a new Quick Paging Channel
31 number in the range 1 to NUM_QPCHr. The mobile station shall store the new
32 Quick Paging Channel number as QPAGECHs and as ASSIGNED_QPAGECHs.
33 The mobile station shall then set NUM_QPCHs to NUM_QPCHr.
34 – The mobile station shall set QPCH_POWER_LEVEL_PAGEs to

35 QPCH_POWER_LEVEL_PAGEr.
36 – The mobile station shall set QPCH_CCI_SUPPORTEDs to

37 QPCH_CCI_SUPPORTEDr.
2-111
3GPP2 C.S0005-A v6.0
1 – If QPCH_CCI_SUPPORTEDr = ‘1’, the mobile station shall set

2 QPCH_POWER_LEVEL_CONFIGs to QPCH_POWER_LEVEL_CONFIGr.
3 If the mobile station supports the Device Information Message on the r-csch, the mobile
4 station shall store:
5 • Autonomous message supported indicator
6 (AUTO_MSG_SUPPORTEDs= AUTO_MSG_SUPPORTEDr)
7 If AUTO_MSG_SUPPORTEDr is equal to ‘1’ and the mobile station supports the Device
8 Information Message on the r-csch, the mobile station shall store:
9 • Autonomous message interval
10 (AUTO_MSG_INTERVALs = AUTO_MSG_INTERVALr)
11 The mobile station shall store mobile station initiated position location determination
12 supported indicator (MS_INIT_POS_LOC_SUP_INDs = MS_INIT_POS_LOC_SUP_INDr).
13 2.6.2.2.6 Global Service Redirection Message

14 Whenever a Global Service Redirection Message is received on the Paging Channel, the
16 stored in GLOB_SERV_REDIR_MSG_SEQs. If the comparison results in a match or if
17 SYS_PAR_MSG_SEQs is not current, the mobile station may ignore the message; otherwise,
18 the mobile station shall store the following parameters:

21 GLOB_SERV_REDIR_MSG_SEQs= CONFIG_MSG_SEQr)
22 • If the P_REV_IN_USEs is equal to or greater than 6, the The mobile station shall
23 ignore this message, if any of the following conditions is true:
24 – EXT_GLOBAL_REDIRECTs = ‘1’
25 – EXCL_P_REV_MSr = ‘1’
26 If the subfield corresponding to the access overload class, ACCOLCp, of the mobile station
27 is set equal to ‘1’ in the REDIRECT_ACCOLCr field of the received message, the mobile
28 station shall store the following parameters and then shall enter the System Determination
29 Substate of the Mobile Station Initialization State with a redirection indication (see 2.6.1.1):
30 • Return if fail indicator (RETURN_IF_FAILs = RETURN_IF_FAILr)
31 • If DELETE_TMSIr is equal to ‘1’, the mobile station shall set all the bits of
32 TMSI_CODEs-p to ‘1’
33 • Redirection record (REDIRECT_RECs = redirection record from received message)
34 • If RECORD_TYPEr = ‘00000001’, the mobile station shall:
35 − Set CDMA_MODEs to ‘1’
36 − Set DIGITAL_REGs-p to ‘00000000’
37 − Max delay upon redirection (MAX_REDIRECT_DELAYs =

38 MAX_REDIRECT_DELAYr)
2-112
3GPP2 C.S0005-A v6.0
1 2.6.2.2.7 Extended Neighbor List Message
2 Whenever a valid Extended Neighbor List Message is received on the current Paging Channel
3 (PAGECHs), the configuration message sequence number, CONFIG_MSG_SEQr, shall be
4 compared to that stored in EXT_NGHBR_LST_MSG_SEQs. If the comparison results in a
5 match, the mobile station may ignore the message. If the comparison results in a
6 mismatch, then the mobile station shall process the remaining fields in the message as
7 follows.
9 station shall ignore the Extended Neighbor List Message that contains it.

13 EXT_NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr,
14 NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr)
15 • Pilot PN sequence offset increment (PILOT_INCs = PILOT_INCr)
17 contained in the Extended Neighbor List Message.
18 For each of the neighboring base stations contained in the Extended Neighbor List Message,
19 if FREQ_INCLr equals ‘0’, or if FREQ_INCLr equals ‘1’ and NGHBR_BANDr is supported, the
21 • If the ith occurrence of NGHBR_CONFIGr is equal to ‘000’, ‘001’, or ‘010’, set the
22 NGHBR_CONFIG field of NGHBR_REC[i] to the ith occurrence of NGHBR_CONFIGr;
23 otherwise, set the NGHBR_CONFIG field of NGHBR_REC [i] to ‘011’.
24 • Set the NGHBR_PN field of NGHBR_REC[i] to the ith occurrence of NGHBR_PNr.
25 • Set the SEARCH_PRIORITY field of NGHBR_REC[i] to the ith occurrence of

26 SEARCH_PRIORITYr.
28 if FREQ_INCLr equals ‘1’ and NGHBR_BANDr is supported, the mobile station shall also do
29 the following:
30 • Set the NGHBR_BAND field of NGHBR_REC[i] to the ith occurrence of

31 NGHBR_BANDr.
32 • Set the NGHBR_FREQ field of NGHBR_REC[i] to the ith occurrence of

33 NGHBR_FREQr.
35 if FREQ_INCLr equals ‘0’, the mobile station shall also do the following:
36 • Set the NGHBR_BAND field of NGHBR_REC[i] to CDMABANDs.
37 • Set the NGHBR_FREQ field of NGHBR_REC[i] to CDMACHs.
2-113
3GPP2 C.S0005-A v6.0
1 If GEN_NGHBR_LST_MSG_SEQs is not equal to CONFIG_MSG_SEQs, the mobile station

2 shall do the following:
3 • Set the SRCH_WIN_NGHBR field of NGHBR_REC to SRCH_WIN_Ns for all

6 • Set NUM_ANALOG_NGHBRs to ‘000’ and set ANALOG_NGHBR_LIST to NULL.
18 consists only of pilot offsets listed in the Extended Neighbor List Message. If the Extended
19 Neighbor List Message contains more pilot offsets than the mobile station can store, the
20 mobile station shall store the pilot offsets beginning at the start of the Extended Neighbor
21 List Message, up to the limits of the mobile station’s Neighbor Set storage capacity.
22 2.6.2.2.8 General Neighbor List Message
23 Whenever a valid General Neighbor List Message is received on the current Paging Channel
24 (PAGECHs), the configuration message sequence number, CONFIG_MSG_SEQr shall be
25 compared to that stored in GEN_NGHBR_LST_MSG_SEQs. If the comparison results in a
26 mismatch, then the mobile station shall process the remaining fields in the message as
27 follows.
29 station shall ignore the General Neighbor List Message that contains it.

33 GEN_NGHBR_LST_MSG_SEQs= CONFIG_MSG_SEQr).
34 • Pilot PN sequence offset increment (PILOT_INCs = PILOT_INCr).
35 If NGHBR_CONFIG_PN_INCLr is equal to ‘1’ and FREQ_FIELDS_INCLr is equal to ‘1’, the

36 mobile station shall store the following parameters:
2-114
3GPP2 C.S0005-A v6.0

2 (EXT_NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr,
3 NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr).
5 contained in the General Neighbor List Message.
6 For each of the neighboring base stations contained in the General Neighbor List Message, if
7 FREQ_INCLr equal ‘0’, or if FREQ_INCLr equal ‘1’ and NGHBR_BANDr is supported, the
9 • If NGHBR_CONFIG_PN_INCLr is equal to ‘1’, set the NGHBR_CONFIG and
10 NGHBR_PN fields as follows:
11 – If the ith occurrence of NGHBR_CONFIGr is equal to ‘000’, ‘001’, or ‘010’, set the
12 NGHBR_CONFIG field of NGHBR_REC[i] to the ith occurrence of
13 NGHBR_CONFIGr; otherwise, set the NGHBR_CONFIG field of NGHBR_REC[i] to
14 ‘011’.
15 – Set the NGHBR_PN field of NGHBR_REC[i] to the ith occurrence of NGHBR_PNr.
16 • If NGHBR_SRCH_MODEr = ‘00’ or ‘10’ and EXT_NGHBR_LST_MSG_SEQs is not

17 equal to CONFIG_MSG_SEQr, set SEARCH_PRIORITY field of each NGHBR_REC to
18 ‘10’ (high) for all NGHBR_SET_SIZEs entries.
19 • If NGHBR_SRCH_MODEr = ‘01’ or ‘11’, set the SEARCH_PRIORITY field of

20 NGHBR_REC[i] to the ith occurrence of SEARCH_PRIORITYr.
21 • If NGHBR_SRCH_MODEr = ‘00’ or ‘01’, set the SRCH_WIN_NGHBR field of each

22 NGHBR_REC to SEARCH_WINs for all NGHBR_SET_SIZEs entries if
23 SYS_PAR_MSG_SEQs is equal to CONFIG_MSG_SEQs; otherwise, set
24 SETTING_SEARCH_WIN to ‘1’.
25 • If NGHBR_SRCH_MODEr = ‘00’ or ‘01’, set the SRCH_OFFSET_NGHBR field of each
26 NGHBR_REC to ‘000’.
27 • If NGHBR_SRCH_MODEr = ‘10’ or ‘11’:
28 – set the SRCH_WIN_NGHBR field of NGHBR_REC[i] to the ith occurrence of

29 SRCH_WIN_NGHBRr
30 – if SRCH_OFFSET_INCLr equals to ‘1’, set the SRCH_OFFSET_NGHBR field of

31 NGHBR_REC[i] to the ith occurrence of SRCH_OFFSET_NGHBRr, and

33 each NGHBR_REC to ‘000’.
34 • If USE_TIMINGr is equal to ‘1’, set the TIMING_INCL field of NGHBR_REC[i] to the
35 ith occurrence of TIMING_INCLr; otherwise, set the TIMING_INCL field of
36 NGHBR_REC to ‘0’ for all entries.
2-115
3GPP2 C.S0005-A v6.0
1 • If BCCH_IND_INCLr is equal to ‘1’, set the BCCH_SUPPORT field of NGHBR_REC[i]

2 to the ith occurrence of BCCH_SUPPORTr; otherwise, set the BCCH_IND_INCL field
3 of NGHBR_REC to ‘0’ for all entries.
5 FREQ_FIELDS_INCLr equals ‘1’, FREQ_INCLr equals ‘1’, and NGHBR_BANDr is supported,
6 the mobile station shall also perform the following:

8 NGHBR_BANDr.

10 NGHBR_FREQr.
12 USE_TIMINGr is equal to ‘1’ and TIMING_INCLr equals ‘1’, the mobile station shall also
14 • Set the NGHBR_TX_OFFSET field of NGHBR_REC[i] to the ith occurrence of

15 NGHBR_TX_OFFSETr.
16 • If GLOBAL_TIMING_INCLr is equal to ‘1’, then the mobile station shall:
17 – Set the NGHBR_TX_DURATION field of NGHBR_REC to

18 GLOBAL_TX_DURATIONr for all entries.
19 – Set the NGHBR_TX_PERIOD field of NGHBR_REC to GLOBAL_TX_PERIODr for

20 all entries.
22 – Set the NGHBR_TX_DURATION field of NGHBR_REC[i] to the ith occurrence of

23 NGHBR_TX_DURATIONr.
24 – Set the NGHBR_TX_PERIOD field of NGHBR_REC[i] to the ith occurrence of

25 NGHBR_TX_PERIODr.
27 FREQ_FIELDS_INCLr equals ‘1’ and FREQ_INCLr equals ‘0’, or if FREQ_FIELDS_INCLr
28 equals ‘0’ and EXT_NGHBR_LST_MSG_SEQs is not equal to CONFIG_MSG_SEQr, the
29 mobile station shall also do the following:
34 • EXT_SYS_PARAMETERs is equal to ‘0’
2-116
3GPP2 C.S0005-A v6.0
3 • EXT_SYS_PARAMETERs is equal to ‘0’
7 consists only of pilot offsets listed in the General Neighbor List Message. If the General
9 mobile station shall store the pilot offsets beginning at the start of the General Neighbor List
10 Message, up to the limits of the mobile station’s Neighbor Set storage capacity.
11 The mobile station shall set NUM_ANALOG_NGHBRs to NUM_ANALOG_NGHBRr, the
12 number of neighboring analog systems contained in the General Neighbor List Message. For
13 each of the neighboring analog systems contained in the General Neighbor List Message, the
15 • Set the BAND_CLASS field of ANALOG_NGHBR_LIST[i] to the ith occurrence of

16 BAND_CLASSr.
17 • Set the SYS_A_B field of ANALOG_NGHBR_LIST[i] to the ith occurrence of SYS_A_Br.
18 For each of the neighboring base stations contained in the General Neighbor List Message,
19 the mobile station shall set the ADD_PILOT_REC_INCL field of NGHBR_REC[i] to the ith
20 occurrence of ADD_PILOT_REC_INCLr. If ADD_PILOT_REC_INCLr equals ‘1’, for each pilot
21 included in the message, the mobile station shall also perform the following:
22 • Set the NGHBR_PILOT_REC_TYPE field of NGHBR_PILOT_REC to

23 NGHBR_PILOT_REC_TYPEr.
24 • If NGHBR_PILOT_REC_TYPEr is equal to ‘000’. The mobile station shall:
25 – Set the TD_POWER_LEVEL field of NGHBR_PILOT_REC to TD_POWER_LEVELr.
26 – Set the TD_MODE field of NGHBR_PILOT_REC to TD_MODEr.
27 • If NGHBR_PILOT_REC_TYPEr is equal to ‘001’, the mobile station shall:
28 – Set the AUX_PILOT_QOF field of NGHBR_PILOT_REC to QOFr.
29 – Set the AUX_PILOT_WALSH_CODE field of NGHBR_PILOT_REC to

30 AUX_PILOT_WALSHr with the Walsh Code length specified by WALSH_LENGTHr.

35 – Set the AUX_TD_POWER_LEVEL field of NGHBR_PILOT_REC to

36 AUX_TD_POWER_LEVELr.
2-117
3GPP2 C.S0005-A v6.0
2 – Set the SR3_PRIMARY_PILOT field of NGHBR_PILOT_REC to

3 SR3_PRIMARY_PILOTr.
4 – Set the SR3_PILOT_POWER1 field of NGHBR_PILOT_REC to

5 SR3_PILOT_POWER1r.

9 – Set the SR3_PRIMARY_PILOT field of NGHBR_PILOT_REC to




18 – If ADD_INFO_INCL1r is equal to ‘1’, set the AUX_PILOT_QOF1 field of

19 NGHBR_PILOT_REC to QOF1r and set the AUX_PILOT_WALSH_CODE1 field of
20 NGHBR_PILOT_REC to AUX_PILOT_WALSH1r with the Walsh Code length
21 specified by WALSH_LENGTH1r.
22 – Otherwise, set the AUX_PILOT_QOF1 field of NGHBR_PILOT_REC to QOFr and

23 set the AUX_PILOT_WALSH_CODE1 field of NGHBR_PILOT_REC to
25 – If ADD_INFO_INCL2r is equal to ‘1’, set the AUX_PILOT_QOF2 field of

26 NGHBR_PILOT_REC to QOF2r and set the AUX_PILOT_WALSH_CODE2 field of
27 NGHBR_PILOT_REC to AUX_PILOT_WALSH2r with the Walsh Code length
28 specified by WALSH_LENGTH2r.
29 – Otherwise, set the AUX_PILOT_QOF2 field of NGHBR_PILOT_REC to QOFr and

30 set the AUX_PILOT_WALSH_CODE2 field of NGHBR_PILOT_REC to
32 2.6.2.2.9 User Zone Identification Message

33 Whenever a User Zone Identification Message is received on the Paging Channel or Primary
34 Broadcast Control Channel, and if the mobile station supports Tiered Services, the mobile
35 station shall compare the configuration message sequence number, CONFIG_MSG_SEQr, to
36 that stored in USER_ZONE_ID_MSG_SEQs. If the comparison results in a match, the
37 mobile station may ignore the message. If the comparison results in a mismatch, then the
38 mobile station shall process the remaining fields in the message as follows.
2-118
3GPP2 C.S0005-A v6.0

4 USER_ZONE_ID_MSG_SEQs = CONFIG_MSG_SEQr)
5 • UZ_EXIT_RCVDs = UZ_EXITr
6 The mobile station shall set NUM_UZIDs to the number of User Zones contained in the User
7 Zone Identification Message.
8 For each User Zone contained in the User Zone Identification Message, the mobile station
9 shall do the following:
th
10 • Set the UZID field of UZ_REC(i) to the i occurrence of UZIDr.
th
11 • Set the UZ_REV field of the UZ_REC(i) to the i occurrence of UZ_REVr.
th
12 • Set the TEMP_SUB field of the UZ_REC(i) to the i occurrence of TEMP_SUBr.
13 2.6.2.2.10 Private Neighbor List Message

14 Whenever a Private Neighbor List Message is received on the Paging Channel or Primary
15 Broadcast Control Channel, and if the mobile station supports Tiered Services, the mobile
16 station shall compare the configuration message sequence number, CONFIG_MSG_SEQr, to
17 that stored in PRI_NGHBR_LST_MSG_SEQs. If the comparison results in a match, the
18 mobile station may ignore the message. If the comparison results in a mismatch, then the
19 mobile station shall process the remaining fields in the message as follows.

23 PRI_NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr)
24 • Common configuration included indicator (COMMON_INCLs = COMMON_INCLr)
25 The mobile station shall set NUM_PRI_NGHBRs to the number of Private Neighbor base
26 stations contained in the Private Neighbor List Message.
27 For each Private Neighbor base station contained in the Private Neighbor List Message the
29 • Set the SRCH_WIN_PRI_NGHBR field of PRI_NGHBR_REC(i) to SRCH_WIN_PNr.
th
30 • Set the SID field of PRI_NGHBR_REC(i) to the i occurrence SIDr.
th
31 • Set the NID field of PRI_NGHBR_REC(i) to the i occurrence NIDr.
th
32 • Set the PRI_NGHBR_PN field of PRI_NGHBR_REC(i) to the i occurrence
33 PRI_NGHBR_PNr.
34 • If COMMON_INCLr is equal to ‘1’, then the mobile station shall:
35 – Set the BAND_CLASS field of PRI_NGHBR_REC(i) to COMMON_BAND_CLASSr.
36 – Set the NGHBR_FREQ field of PRI_NGHBR_REC(i) to COMMON_NGHBR_FREQr.
2-119
3GPP2 C.S0005-A v6.0
1 • If COMMON_INCLr is equal to ‘0’, then the mobile station shall:

th
2 – Set the BAND_CLASS field of PRI_NGHBR_REC(i) to the i occurrence of
3 BAND_CLASSr.
th
4 – Set the NGHBR_FREQ field of PRI_NGHBR_REC(i) to the i occurrence of
5 NGHBR_FREQr.
th
6 • If i occurrence of UZID_INCLr is equal to ‘0’, then the mobile station shall set the
7 PS_NUM_UZID field of PRI_NGHBR_REC(i) to ‘0000’.
th
8 • If i occurrence of UZID_INCLr is equal to ‘1’, then the mobile station shall set the
th
9 PS_NUM_UZID field of PRI_NGHBR_REC(i) to the NUM_UZIDr associated with the i
10 occurrence of UZID_INCLr.
th
11 • For each User Zone supported by the i private system, the mobile station shall do
12 the following:
th
13 – Set the PS_UZID(j) field of PRI_NGHBR_REC(i) to the j occurrence of UZIDr.
th
14 – Set the PS_UZ_REV(j) field of PRI_NGHBR_REC(i) to the j occurrence of
15 UZ_REVr.
th
16 – Set the PS_TEMP_SUB(j) field of PRI_NGHBR_REC(i) to the j occurrence of
17 TEMP_SUBr.
18 2.6.2.2.11 Extended Global Service Redirection Message

19 Whenever an Extended Global Service Redirection Message is received on the Paging
20 Channel or Primary Broadcast Control Channel, the configuration message sequence
21 number, CONFIG_MSG_SEQr, shall be compared to that stored in
22 EXT_GLOB_SERV_REDIR_MSG_SEQs. If the comparison results in a match, the mobile
23 station may ignore the message. If the comparison results in a mismatch, the mobile
24 station shall store the following parameters:

27 GLOB_SERV_REDIR_MSG_SEQs= CONFIG_MSG_SEQr,
28 EXT_GLOB_SERV_REDIR_MSG_SEQs= CONFIG_MSG_SEQr)
29 The mobile station shall ignore the rest of the message if any of the following conditions is
30 satisfied:
31 • The subfield corresponding to the access overload class, ACCOLCp, of the mobile
32 station is set equal to ‘0’ in the REDIRECT_ACCOLCr field of the received message,
33 • MOB_P_REVp is not in the redirection mobile protocol revision range (i.e.,

34 REDIRECT_P_REV_INCLr = ‘1’ and EXCL_P_REV_INDr = ‘0’, and MOB_P_REVp <
35 REDIRECT_P_MINr or MOB_P_REVp >REDIRECT_P_MAXr), or
36 • MOB_P_REVp is in the excluded mobile protocol revision range (i.e.,

37 REDIRECT_P_REV_INCLr = ‘1’ and EXCL_P_REV_INDr = ‘1’ and (REDIRECT_P_MINr
38 ≤ MOB_P_REVp ≤ REDIRECT_P_MAXr)).
2-120
3GPP2 C.S0005-A v6.0
1 Otherwise, the mobile station shall store the following parameters and then shall enter the
2 System Determination Substate of the Mobile Station Initialization State with a redirection
3 indication (see 2.6.1.1):
6 • Return if fail indicator (RETURN_IF_FAILs = RETURN_IF_FAILr).
7 • Redirection record (REDIRECT_RECs = redirection record from received message)
8 • If RECORD_TYPEr = ‘00000001’, the mobile station shall:
9 − Set CDMA_MODEs to ‘1’
10 − Set DIGITAL_REGs-p to ‘00000000’
11 − Max delay upon redirection (MAX_REDIRECT_DELAYs =

12 MAX_REDIRECT_DELAYr)
13 2.6.2.2.12 Extended CDMA Channel List Message Overview
14 The mobile station may receive the Extended CDMA Channel List Message from the Paging
15 Channel or from the Primary Broadcast Control Channel. The mobile station shall follow
16 requirements defined in 2.6.2.2.12.1 or 2.6.2.2.12.2 to process the Extended CDMA Channel
17 List Message.
18 2.6.2.2.12.1 Extended CDMA Channel List Message on Paging Channel
19 Whenever an Extended CDMA Channel List Message is received on the Paging Channel, the
20 mobile station shall compare the configuration message sequence number,
21 CONFIG_MSG_SEQr, to that stored in EXT_CHAN_LST_MSG_SEQs. If the comparison
24 follows:

28 EXT_CHAN_LST_MSG_SEQs = CONFIG_MSG_SEQr,
29 CHAN_LST_MSG_SEQs = CONFIG_MSG_SEQr).
30 The mobile station shall determine the CDMA Channel (Frequency Assignment) for its
31 Paging Channel as follows:
32 • If RC_QPCH_SEL_INCLr is equal to ‘1’ and the mobile station is capable of RC
33 greater than 2 or capable of supporting Quick Paging Channel, the mobile station
34 shall eliminate those channels with RC_QPCH_HASH_INDr equal to ‘0’ from the
35 CDMA channel list and use the hash algorithm specified in 2.6.7.1 and the number
36 of channels whose RC_QPCH_HASH_INDr is equal to ‘1’ in the Extended CDMA
37 Channel List Message to determine the CDMA Channel (Frequency Assignment) for
38 its Paging Channel.
2-121
3GPP2 C.S0005-A v6.0
1 • If RC_QPCH_SEL_INCLr is equal to ‘1’ and the mobile station is not capable of RC

2 greater than 2 and not capable of supporting Quick Paging Channel, the mobile
3 station shall use the hash algorithm specified in 2.6.7.1 and the number of
4 channels in the Extended CDMA Channel List Message to determine the CDMA
5 Channel (Frequency Assignment) for its Paging Channel.
6 • If RC_QPCH_SEL_INCLr is equal to ‘0’, the mobile station shall use the hash
7 algorithm specified in 2.6.7.1 and the number of channels in the Extended CDMA
8 Channel List Message to determine the CDMA Channel (Frequency Assignment) for
9 its Paging Channel.
10 If the CDMA Frequency Assignment has changed (the computed CDMA Channel is different
11 from CDMACHs), the mobile station shall perform the following actions:
12 • If the stored configuration parameters is not current (see 2.6.2.2) for the
13 corresponding base station and frequency assignment, the mobile station shall
14 perform the following actions:
15 – Set CDMACHs to the new CDMA Channel.
16 – Set PAGE_CHANs to ‘1’.
17 – Set PAGECHs to the Primary Paging Channel.
18 – Set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,

19 CHAN_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
22 EXT_GLOB_SERV_REDIR_MSG_SEQs, USER_ZONE_IDMSG_SEQs,
23 PRI_NGHBR_LST_MSG_SEQs, and ACC_MSG_SEQs to NULL.
24 • Tune to the new CDMA Channel.
25 • Otherwise, the mobile station shall perform the following actions:

26 – Set CDMACHs to the new CDMA Channel.
27 – The mobile station shall use the hash algorithm specified in 2.6.7.1 to select a
28 new Paging Channel number in the range 1 to PAGE_CHANs, where
29 PAGE_CHANs is the value stored for the Paging Channel whose stored
30 information is current. The mobile station shall store the new Paging Channel
31 number as PAGECHs.
32 – Tune to the new CDMA Channel and shall begin monitoring the new Paging
33 Channel.
34 2.6.2.2.12.2 Extended CDMA Channel List Message on Primary Broadcast Control Channel
35 Whenever the Extended CDMA Channel List Message is received on the Primary Broadcast
36 Control Channel, the mobile station shall compare the configuration message sequence
37 number, CONFIG_MSG_SEQr, to that stored in CONFIG_MSG_SEQs. If the comparison
39 a mismatch, the mobile station shall process the remaining fields in the message as follows:
2-122
3GPP2 C.S0005-A v6.0

4 EXT_CHAN_LST_MSG_SEQs = CONFIG_MSG_SEQr).
5 To determine the CDMA Channel (Frequency Assignment) for its Primary Broadcast Control
6 Channel, the mobile station shall first select a subset of CDMA channels from the Extended
7 CDMA Channel List Message that will be used for channel hashing. The attributes for
8 channel selection are support for RC greater than 2, Quick Paging Channel and transmit
9 diversity. The mobile station shall first select the entire CDMA channel list for channel
10 hashing. The mobile station shall then select the first subset as follows:
11 • If TD_SEL_INCLr is equal to ‘1’, the mobile station shall perform the following:
12 − If the mobile station is capable of supporting the transmit diversity mode

13 specified by TD_MODEr, the mobile station shall select those CDMA channels
14 that have TD_HASH_INDr set to ‘1’ from the CDMA channel list for the first
15 subset.
16 − If the mobile station is not capable of supporting the transmit diversity mode
17 specified by TD_MODEr, the mobile station shall select those CDMA channels
18 that have TD_HASH_INDr set to ‘0’ from the CDMA channel list for the first
19 subset. If this selected subset is empty, the mobile station shall not perform the
20 remaining procedures in this section.
21 • If TD_SEL_INCLr is equal to ‘0’, the mobile station shall select the entire list for the
22 first subset.
23 From this first subset, the mobile station shall select the final subset as follows:
24 • If RC_QPCH_SEL_INCLr is equal to ‘1’ and the mobile station is capable of RC

25 greater than 2 or capable of supporting QPCH, the mobile station shall select those
26 CDMA channels with RC_QPCH_HASH_INDr set to ‘1’ for the final subset for CDMA
27 channel hashing. If this list is empty, the mobile station shall use the first subset as
28 the final subset for CDMA channel hashing.
29 • Otherwise, the mobile station shall use the first subset as the final subset for CDMA
30 channel hashing.
31 After the final subset has been selected, the mobile station shall use the hash algorithm
32 specified in 2.6.7.1 with the number of channels in the final subset of the CDMA channel
33 list to determine the CDMA Channel (Frequency Assignment) for its Primary Broadcast
34 Control Channel.
35 If the CDMA Frequency Assignment has changed (the computed CDMA Channel is different
36 from CDMACHs), the mobile station shall perform the following:
37 • Set CDMACHs to the new CDMA Channel.
2-123
3GPP2 C.S0005-A v6.0
1 • Set CONFIG_MSG_SEQs, A41_SYS_PAR_MSG_SEQs, MC_RR_PAR_MSG_SEQs,

2 UNI_NGHBR_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
3 USER_ZONE_ID_MSG_SEQs, and PRI_NGHBR_LST_MSG_SEQs and
4 ACC_MSG_SEQs to NULL
5 • If the mobile station is operating in the Spreading Rate 1:
6 − If the assigned CDMA channel supports transmit diversity, the mobile station
7 shall set the following fields corresponding to the assigned CDMA channel:
8 + SR1_TD_POWER_LEVELs = TD_POWER_LEVELr.
9 + SR1_TD_MODEs = TD_MODEr.
10 + BRATs = SR1_BRAT_TDs.
11 + BCCH_CODE_RATEs = SR1_CRAT_TDs.
12 + BCCHs = BCCH_ CODE_CHAN_TDs.
13 − Otherwise, the mobile station shall set the following fields corresponding to the
14 assigned CDMA channel:
15 + BRATs = SR1_BRAT_NON_TDs,
16 + BCCH_CODE_RATEs = SR1_CRAT_NON_TDs,
17 + BCCHs = BCCH_CODE_CHAN_NON_TDs,
18 • Tune to the new CDMA Channel
19 2.6.2.2.13 ANSI-41 System Parameters Message

20 Whenever an ANSI-41 System Parameters Message is received, the configuration message
21 sequence number, CONFIG_MSG_SEQr, shall be compared to that stored in
22 A41_SYS_PAR_MSG_SEQs. If the comparison results in a match, the mobile station may
23 ignore the message. If the comparison results in a mismatch, then the mobile station shall
24 process the remaining fields in the message as described in 2.6.2.2.13.1, 2.6.2.2.13.2,
25 2.6.2.2.13.3, and 2.6.2.2.13.4.
26 If REG_PRD is not within the valid range specified in 3.7.2.3.2.31, then the mobile station
27 shall ignore the ANSI-41 System Parameters Message that contains it.

32 A41_SYS_PAR_MSG_SEQs = CONFIG_MSG_SEQr)
33 • Home registration indicator (HOME_REGs = HOME_REGr)
34 • SID roamer registration indicator (FOR_SID_REGs = FOR_SID_REGr)
35 • NID roamer registration indicator (FOR_NID_REGs = FOR_NID_REGr)
2-124
3GPP2 C.S0005-A v6.0
1 • Power-up registration indicator (POWER_UP_REGs = POWER_UP_REGr)
2 • Power-down registration indicator (POWER_DOWN_REGs = POWER_DOWN_REGr)
3 • Parameter-change registration indicator (PARAMETER_REGs = PARAMETER_REGr)
4 • Preferred Enhanced Access Channel MSID type

5 (PREF_MSID_TYPEs = PREF_MSID_TYPEr)
6 • The mobile station shall set its operational IMSI, IMSI_O, as follows:
7 – If IMSI_T_SUPPORTEDr is equal to ‘0’, the mobile station shall set IMSI_O to
8 IMSI_Mp.
9 – If IMSI_T_SUPPORTEDr is equal to ‘1’ and the mobile station’s IMSI_Tp has been
10 programmed, the mobile station shall set IMSI_O to IMSI_Tp.
11 – If IMSI_T_SUPPORTEDr is equal to ‘1’ and the mobile station’s IMSI_Tp has not
12 been programmed, the mobile station shall set IMSI_O to IMSI_Mp.
13 – If IMSI_O has been changed, the mobile station shall set

14 A41_SYSMC_RR_PAR_MSG_SEQs and EXT_CHAN_LST_MSG_SEQs to NULL and
15 set NUM_FCCCHs to ‘1’ and FCCCH_IDs to ‘1’.
16 • If OTHER_INFO_INCLr is set to ‘1’, the mobile station shall store:
17 – Base station identification (BASE_IDs = BASE_IDr)
18 – If MCCr = ‘1111111111’ and IMSI_11_12r = ‘1111111’, the mobile station shall

19 set the IMSI_O to IMSI_Mp and store:
20 + Mobile Country Code (MCCs = MCC_Mp) and
21 + IMSI 11th and 12th digits (IMSI_11_12s = IMSI_M_11_12p);
22 – Otherwise, the mobile station shall store:

23 + Mobile Country Code (MCCs = MCCr) and
24 + IMSI 11th and 12th digits (IMSI_11_12s = IMSI_11_12r).
25 – Broadcast GPS assist indicator (BROADCAST_GPS_ASSTs =


28 SIG_ENCRYPT_SUPr)
29 –Store encryption key indicator (STORE_KEYs = STORE_KEYr)
30 – Concurrent services supported indicator (CS_SUPPORTEDs = CS_SUPPORTEDr)
31 • If IMSI_O is set to the IMSI_M, the mobile station shall set:

32 – IMSI_O_Ss to IMSI_M_Sp (i.e., IMSI_O_S1s to IMSI_M_S1p and IMSI_O_S2s to
33 IMSI_M_S2p)
34 – IMSI_O_11_12s to IMSI_M_11_12p
35 – MCC_Os to MCC_Mp
2-125
3GPP2 C.S0005-A v6.0
1 – IMSI_O_ADDR_NUMs to IMSI_M_ADDR_NUMp
2 • If IMSI_O is set to the IMSI_T, the mobile station shall set:

3 – IMSI_O_Ss to IMSI_T_Sp (i.e., IMSI_O_S1s to IMSI_T_S1p and IMSI_O_S2s to
4 IMSI_T_S2p).
5 – IMSI_O_11_12s to IMSI_T_11_12p
6 – MCC_Os to MCC_Tp
7 – IMSI_O_ADDR_NUMs to IMSI_T_ADDR_NUMp
8 • Delete foreign TMSI (DELETE_FOR_TMSIs = DELETE_FOR_TMSIr)
9 • Use TMSI (USE_TMSIs = USE_TMSIr)
10 • TMSI zone length (TMSI_ZONE_LENs = TMSI_ZONE_LENr)
11 • TMSI zone number (TMSI_ZONEs = TMSI_ZONEr)
12 • Maximum number of alternative service options (MAX_NUM_ALT_SOs =

13 MAX_NUM_ALT_SOr) if included in the message; otherwise, MAX_NUM_ALT_SOs =
14 ‘000’.
15 • The mobile station shall set all bits of TMSI_CODEs-p to ‘1’ if all of the following
16 conditions are met:
17 – The bits of TMSI_CODEs-p are not all equal to ‘1’,
18 – DELETE_FOR_TMSIs is equal to ‘1’, and
19 – ASSIGNING_TMSI_ZONE_LENs-p is not equal to TMSI_ZONE_LENs, or the least

20 significant ASSIGNING_TMSI_ZONE_LENs-p octets of ASSIGNING_TMSI_ZONEs-
21 p are not equal to TMSI_ZONEs.
22 If the mobile station supports packet data service, the mobile station shall store the packet
23 data services zone identifier (PACKET_ZONE_IDs = PACKET_ZONE_IDr); otherwise, the
24 mobile station shall set PACKET_ZONE_IDs to ‘00000000’.
25 If the mobile station supports the Device Information Message on the r-csch, the mobile
26 station shall store:
27 • Autonomous message supported indicator
28 (AUTO_MSG_SUPPORTEDs= AUTO_MSG_SUPPORTEDr)
29 If AUTO_MSG_SUPPORTEDr is equal to ‘1’ and the mobile station supports the Device
30 Information Message on the r-csch, the mobile station shall store:
31 • Autonomous message interval
32 (AUTO_MSG_INTERVALs = AUTO_MSG_INTERVALr)
33 The mobile station shall store concurrent service supported indicator (CS_SUPPORTEDs=
34 CS_SUPPORTEDr).
35 The mobile station shall store mobile station initiated position location determination
36 supported indicator (MS_INIT_POS_LOC_SUP_INDs = MS_INIT_POS_LOC_SUP_INDr).
2-126
3GPP2 C.S0005-A v6.0

9 • Registration period (REG_PRDs = REG_PRDr)
10 • If DIST_REG_INCL is equal to ‘1’, the mobile station shall store:

11 – Registration distance (REG_DISTs = REG_DISTr)
12 • If DIST_REG_INCL is equal to ‘0’, then the mobile station shall set REG_DIST equal
13 to ‘00000000000’.
14 The mobile station shall ignore any fields at the end of the ANSI-41 System Parameters
15 Message that are not defined according to the protocol revision level (MOB_P_REVp of the
16 current band class) being used by the mobile station.
17 2.6.2.2.13.2 Roaming Status
18 The mobile station shall determine the roaming status for the mobile station (see 2.6.5.3).
19 The mobile station should indicate to the user whether the mobile station is roaming.
20 2.6.2.2.13.3 Registration
21 The mobile station shall update stored variables and perform other registration procedures
23 2.6.2.2.13.4 PACA Disable for SID Change

24 If PACAs is equal to enabled, and SIDs is not equal to PACA_SIDs, the mobile station shall
25 set PACAs to disabled and PACA_CANCEL to ‘0’, shall disable the PACA state timer, and
26 should indicate to the user that the PACA call has been canceled
27 2.6.2.2.14 MC-RR Parameters Message
28 Whenever an MC-RR Parameters Message is received, the configuration message sequence

29 number, CONFIG_MSG_SEQr, shall be compared to that stored in MC_RR_PAR_MSG_SEQs.
30 If the comparison results in a match, the mobile station may ignore the message. If the
31 comparison results in a mismatch, then the mobile station shall process the remaining
32 fields in the message as described in 2.6.2.2.14.1, 2.6.2.2.14.2, and 2.6.2.2.14.3.
33 If the protocol revision level supported by the mobile station (MOB_P_REVp) is less than the
34 minimum protocol revision level supported by the base station (MIN_P_REVr), the mobile
35 station shall enter the System Determination Substate of the Mobile Station Initialization State
2-127
3GPP2 C.S0005-A v6.0
1 with a protocol mismatch indication (see 2.6.1.1).
2 If BASE_LAT, BASE_LONG, or PWR_REP_THRESH is are not within the valid ranges

3 specified in 3.7.2.3.2.31, then the mobile station shall ignore the MC-RR Parameters
4 Message that contains them.
5 If the mobile station supports Spreading Rate 3 on the common channel and SR3_INCLs is
6 equal to ‘1’, the mobile station shall set:
7 • BRATs = SR3_BRATr,
8 • BCCHs = SR3_BCCH_CODE_CHANr;
9 • BCCH_CODE_RATEs = 1/3;
10 • SR3_PRIMARY_PILOTs = SR3_PRIMARY_PILOTr;
11 • SR3_PILOT_POWER1s = SR3_PILOT_POWER1r;
12 • SR3_PILOT_POWER2s = SR3_PILOT_POWER2r;
13 • If SR3_CENTER_FREQ_INCLr is equal to ‘1’, POTENTIAL_CDMACHs =

14 SR3_CENTER_FREQr.
15 If POTENTIAL_CDMACHs is different from CDMACHs, the mobile station shall set

16 CDMACHs = POTENTIAL_CDMACHs and then tune to the CDMA Channel (CDMACHs).

21 MC_RR_PAR_MSG_SEQs= CONFIG_MSG_SEQr)
22 • Base station identification (BASE_IDs = BASE_IDr)
23 • Protocol revision level (P_REVs = P_REVr)
24 • Protocol revision level currently in use (P_REV_IN_USEs = the lesser value of

25 P_REVs and MOB_P_REVp of the current band class)
26 • Minimum protocol revision level (MIN_P_REVs = MIN_P_REVr).
2-128
3GPP2 C.S0005-A v6.0

3 • Slope of the handoff add/drop criterion (SOFT_SLOPEs = SOFT_SLOPEr) if included

4 in the message; otherwise, SOFT_SLOPEs = ‘000000’.

9 SIG_ENCRYPT_SUPr)

11 UI_ENCRYPT_SUPr)
12 – Store encryption key indicator (STORE_KEYs = STORE_KEYr)
13 If P_REV_IN_USEs has been changed, the mobile station shall set ACC_MSG_SEQs,
14 CURR_ACC_MSG_SEQ, A41_SYS_PAR_MSG_SEQs, UNI_NGHBR_LST_MSG_SEQs, and
15 EXT_GLOB_SERV_REDIR_MSG_SEQs to NULL.
16 If CCH_INFO_INCLr is equal to ‘1’, the mobile station shall store:
17 • If MCCr = ‘1111111111’ and IMSI_11_12r = ‘1111111’, the mobile station shall set
18 the IMSI_O to IMSI_Mp and store:
19 – Mobile Country Code (MCCs = MCC_Mp) and
20 – IMSI 11th and 12th digits (IMSI_11_12s = IMSI_M_11_12p);
21 • Otherwise, the mobile station shall store:

22 – Mobile Country Code (MCCs = MCCr) and
23 – IMSI 11th and 12th digits (IMSI_11_12s = IMSI_11_12r).
24 • If IMSI_O has been changed, the mobile station shall set

25 EXT_CHAN_LST_MSG_SEQs to NULL, and set NUM_FCCCHs to ‘1’ and FCCCH_IDs
26 to ‘1’.
27 • Extended Global Service Redirection Message sent
28 (EXT_GLOBAL_REDIRECTs = EXT_GLOBAL_REDIRECTr) if included; otherwise,
29 EXT_GLOBAL_REDIRECTs = ‘0’
30 • User Zone Identification Message sent

31 (USER_ZONE_IDs = USER_ZONE_IDr) if included; otherwise, USER_ZONE_IDs = ‘0’
32 • Private Neighbor List Message sent

33 (PRI_NGHBR_LSTs = PRI_NGHBR_LSTr) if included; otherwise,
34 PRI_NGHBR_LSTs = ‘0’
35 • ANSI-41 RAND Message sent

36 (SENDING_RANDs = SENDING_RANDr) if included; otherwise,
37 SENDING_RANDs = ‘0’
2-129
3GPP2 C.S0005-A v6.0
1 • Maximum slot cycle index

2 (MAX_SLOT_CYCLE_INDEXs = MAX_SLOT_CYCLE_INDEXr)

7 • Periodic report mode indicator (PWR_PERIOD_ENABLEs = PWR_PERIOD_ENABLEr).
9 • System reselection indicator (RESELECT_INCLUDEDs = RESELECT_INCLUDEDr).
12 • Pilot reporting indicator (PILOT_REPORTs = PILOT_REPORTr)
13 • Short Data Burst supported indicator (SDB_SUPPORTEDs = SDB_SUPPORTEDr)
14 • Broadcast GPS Assist Indicator (BROADCAST_GPS_ASSTs =

16 • Nominal reverse traffic channel output power offset relative to Reverse Pilot Channel
17 power (RLGAIN_TRAFFIC_PILOTs = RLGAIN_TRAFFIC_PILOTr)
18 • If NUM_FCCCHr is not equal to ‘0’:
19 – Number of the Forward Common Control Channels (NUM_FCCCHs =

20 NUM_FCCCHr)
21 – Data rate for the Forward Common Control Channels (FCCCH_RATEs =

22 FCCCH_RATEr)
23 – Code rate for the Forward Common Control Channels (FCCCH_CODE_RATEs =

24 FCCCH_CODE_RATEr)
25 – For i = 0 to NUM_FCCCHr - 1, store the channel code index for each Forward
26 Common Control Channel (FCCCH_CODE_CHANs[i] = FCCCH_CODE_CHANr)
27 • Number of Forward Common Control Channels (NUM_FCCCHs = NUM_FCCCHr)
28 • Data rate for the Forward Common Control Channels (FCCCH_RATEs =

29 FCCCH_RATEr)
30 • Code rate for the Forward Common Control Channels (FCCCH_CODE_RATEs =

31 FCCCH_CODE_RATEr)
32 • If NUM_FCCCHr is not equal to ‘0’, then for i = 0 to NUM_FCCCHr - 1, store the

33 channel code index for each Forward Common Control Channel
34 (FCCCH_CODE_CHANs[i] = FCCCH_CODE_CHANr)
35 • Broadcast index (BCAST_INDEXs = BCAST_INDEXr)
2-130
3GPP2 C.S0005-A v6.0
1 • If NUM_BCCH_BCASTr is greater than ‘000’, i occurrences of the following fields,

2 where i ranges from 1 to NUM_BCCH_BCASTr:
3 – Set the index number of the Broadcast Control Channel Number (BCN) to i+1
4 – BCCH walsh code index (BCCH_CODE_CHAN[BCNi]s = BCCH_CODE_CHAN[i]r)
5 – BCCH data rate (BRAT[BCNi]s = BRAT[i]r)
6 – BCCH code rate (BCCH_CODE_RATE[BCNi]s = BCCH_CODE_RATE[i]r)
7 –Set the index number of the Broadcast Control Channel (BCN)[i] to i+1
8 • Sync ID supported indicator (USE_SYNC_IDs = USE_SYNC_IDr)
9 • Pilot information request supported indicator (PILOT_INFO_REQ_SUPPORTEDs =

10 PILOT_INFO_REQ_SUPPORTEDr).
11 • Access entry handoff in order and message processing operation indicator

12 (ACC_ENT_HO_ORDERs = ACC_ENT_HO_ORDERr).
13 • reverse power control delay

If REV_PWR_CNTL_DELAY_INCL is equal to ‘1’,
14 (REV_PWR_CNTL_DELAYs = REV_PWR_CNTL_DELAYr)
15 • Permission indicator for the mobile station to request QoS settings in the Origination
16 Message, Origination Continuation Message, or Enhanced Origination Message
17 (MOB_QOSs = MOB_QOSr)
18 • If RESELECT_INCLUDEDs is equal to ‘1’, the mobile station shall store:
19 – Pilot power threshold (EC_THRESHs = EC_THRESHr)
20 – Pilot Ec/Io threshold (EC_IO_THRESHs = EC_IO_THRESHr)
21 • Access handoff permitted indicator (ACCESS_HOs = ACCESS_HOr)
22 • Access probe handoff permitted indicator (ACCESS_PROBE_HOs =

23 ACCESS_PROBE_HOr)
24 • If ACCESS_PROBE_HOs is equal to ‘1’, access handoff list update permitted

25 indicator (ACC_HO_LIST_UPDs = ACC_HO_LIST_UPDr)
26 • Maximum number of times that the mobile station is permitted to perform an access
27 probe handoff (MAX_NUM_PROBE_HOs = MAX_NUM_PROBE_HOr)
28 • Access handoff permitted for message response indicator (ACCESS_HO_MSG_RSPs =

29 ACCESS_HO_MSG_RSPr)
30 • Access probe handoff permitted for other messages indicator

31 (ACC_PROBE_HO_OTHER_MSGs = ACC_PROBE_HO_OTHER_MSGr)
32 • If USER_ZONE_IDs is equal to ‘0’, then the mobile station shall perform the
33 following:
34 – Set USER_ZONE_ID_MSG_SEQs to CONFIG_MSG_SEQs.
35 – Set the UZID field of the UZ_REC to ‘0000000000000000’ for all entries.
36 – Set the UZ_REV field of the UZ_REC to ‘0000’ for all entries.
2-131
3GPP2 C.S0005-A v6.0
1 – Set the TEMP_SUB field of the UZ_REC to ‘0’ for all entries.
2 • If USER_ZONE_IDs is equal to ‘1’ and the mobile station does not support Tiered
3 Services, then the mobile station shall set USER_ZONE_ID_MSG_SEQs to
4 CONFIG_MSG_SEQs.
5 • If PRI_NGHBR_LISTs is equal to ‘0’, then the mobile station shall set

6 PRI_NGHBR_LIST_MSG_SEQs to CONFIG_MSG_SEQs.
7 • If PRI_NGHBR_LISTs is equal to ‘1’ and the mobile station does not support Tiered
8 Services, then the mobile station shall set PRI_NGHBR_LIST_MSG_SEQs to
9 CONFIG_MSG_SEQs.
10 • If EXT_GLOBAL_REDIRECTs is equal to ‘0’, then the mobile station shall set

11 EXT_GLOB_SERV_REDIR_MSG_SEQs to CONFIG_MSG_SEQs.
12 • If SENDING_RANDs is equal to ‘1’ and the mobile station is not in the Origination
13 Attempt Substate or Page Response Substate, then the mobile station shall perform
14 the following:set AUTHs to ‘01’. Otherwise, the mobile station shall set AUTHs to
15 ‘00’.
16 – If SENDING_RANDs is equal to ‘1’, the mobile station shall set AUTHs to ‘01’;
17 otherwise, the mobile station shall set AUTHs to ‘00’.
18 • If the mobile station is not in the Origination Attempt Substate or Page Response
19 Substate, then the mobile station shall store the following:
20 – Base station latitude (BASE_LATs = BASE_LATr)
21 – Base station longitude (BASE_LONGs = BASE_LONGr)
22 If CCH_INFO_INCLr is equal to ‘1’ and the mobile station supports the Quick Paging
23 Channel operation:
24 • The mobile station shall set QPCH_SUPPORTEDs to QPCH_SUPPORTEDr.
25 • If QPCH_SUPPORTEDr = ‘1’:
26 – The mobile station shall set QPCH_RATEs to QPCH_RATEr.
27 – If the mobile station is monitoring the Primary Broadcast Control Channel in

28 Spreading Rate 1 and the number of Quick Paging Channels specified in the
29 received message (NUM_QPCHr) is different from NUM_QPCHs, the mobile
30 station shall use the hash algorithm specified in 2.6.7.1 to select a new Quick
31 Paging Channel number in the range 1 to NUM_QPCHr. The mobile station shall
32 store the new Quick Paging Channel number as QPAGECHs and as
33 ASSIGNED_QPAGECHs. The mobile station shall then set NUM_QPCHs to
34 NUM_QPCHr.
35 – If the mobile station is monitoring the Primary Broadcast Control Channel in

36 Spreading Rate 3 and the number of Quick Paging Channels specified in the
37 received message (NUM_QPCHr) is different from NUM_QPCHs, the mobile
2-132
3GPP2 C.S0005-A v6.0
1 + The mobile station shall use the hash algorithm specified in 2.6.7.1 to select
2 a new Quick Paging Channel number in the range 1 to NUM_QPCHr.
3 + The mobile station shall store the new Quick Paging Channel number as
4 QPAGECHs and as ASSIGNED_QPAGECHs.
5 + For i = 0 to NUM_QPCHs - 1, store the channel code index for each Quick
6 Paging Channel (QPCH_CODE_CHANs[i] = QPCH_CODE_CHANr.
7 • The mobile station shall set QPCH_POWER_LEVEL_PAGEs to

8 QPCH_POWER_LEVEL_PAGEr.
9 • The mobile station shall set QPCH_CCI_SUPPORTEDs to QPCH_CCI_SUPPORTEDr.
10 • If QPCH_CCI_SUPPORTEDr = ‘1’, the mobile station shall set

11 QPCH_POWER_LEVEL_CONFIGs to QPCH_POWER_LEVEL_CONFIGr.
12 • The mobile station shall set QPCH_BI_SUPPORTEDs to QPCH_BI_SUPPORTEDr.
13 • If QPCH_BI_SUPPORTEDr = ‘1’, the mobile station shall set

14 QPCH_POWER_LEVEL_BCASTs to QPCH_POWER_LEVEL_BCASTr.
15 The mobile station shall ignore any fields at the end of the MC-RR Parameters Message that
18 2.6.2.2.14.2 Slot Cycle Index

19 The mobile station shall set SLOT_CYCLE_INDEXs to the smaller of: the preferred slot cycle
20 index SLOT_CYCLE_INDEXp and the maximum slot cycle index
21 MAX_SLOT_CYCLE_INDEXs. If the mobile station is operating in the slotted mode, it shall
22 set its slot cycle length as described in 2.6.2.1.1.3.
23 2.6.2.2.14.3 Forward Common Control Channel Assignment Change
24 If the number of Forward Common Control Channels specified in the MC-RR Parameters
25 Message (NUM_FCCCHr) is not equal to ‘0’ and is different from NUM_FCCCHs, the mobile
26 station shall use the hash algorithm specified in 2.6.7.1 to select a new Forward Common
27 Control Channel number in the range 1 to NUM_FCCCHr and shall store this value as
28 FCCCH_IDs,. If NUM_FCCCHr is not equal to ‘0’ , Tthe mobile station shall store the FCCCH
29 rate (FCCCH_RATEs = FCCCH_RATEr), the FCCCH code rate (FCCCH_CODE_RATEs =
30 FCCCH_CODE_RATEr ), and store FCCCH_CODE_CHANr of the corresponding Forward
31 Common Control Channel as FCCCH_CODE_RATEs and FCCCH_CODE_CHANs. The
32 mobile station shall then set NUM_FCCCHs to NUM_FCCCHr.
33 The mobile station shall set ACC_MSG_SEQs to NULL.
34 2.6.2.2.15 Enhanced Access Parameters Message
35 Whenever an Enhanced Access Parameters Message is received on the f-csch, the sequence
36 number, ACC_MSG_SEQr, shall be compared to ACC_MSG_SEQs. If the comparison
2-133
3GPP2 C.S0005-A v6.0
1 follows:
2 If PROBE_PN_RAN, MAX_REQ_SEQ, or MAX_RSP_SEQ are not within the valid ranges

3 specified in 3.7.2.3.2.2, then the mobile station shall ignore the Enhanced Access
4 Parameters Message that contains them.
6 • Enhanced Access Parameters Message sequence number

7 (ACC_MSG_SEQs = ACC_MSG_SEQr)
8 • Persistence related parameters:
9 – If PSIST_PARMS_INCL is equal to ‘1’, store the following:
10 + Persistence parameter number according to the following rule: If the mobile

11 station’s access overload class is in the range 0-9 inclusive, set PSISTs equal
12 to PSIST(0-9)_EACHr; otherwise set PSISTs equal to PSIST(n)_EACHr, where
13 n is equal to the mobile station access overload class.
14 + Persistence modifier for Enhanced Access Channel attempts for registrations

15 which are not responses to the Registration Request Order
16 (REG_PSISTs = REG_PSIST_EACHr).
17 + Persistence modifier for Enhanced Access Channel attempts for message

18 transmissions (MSG_PSISTs = MSG_PSIST_EACHr).
19 + Persistence modifier for emergency calls by the mobile stations in access

20 overload classes 0 to 9(PSIST_EMGs = PSIST_EMGr).
21 – If PSIST_PARMS_INCLr is equal to ‘0’, store the following:
22 + Set PSISTs to ‘0’.
23 + Persistence modifier for emergency calls by a mobile station in access

24 overload classes 0 to 9 (PSIST_EMGs = ‘0’).
25 + Persistence modifier for Enhanced Access Channel attempts for message

26 transmissions (MSG_PSISTs = ‘0’).
27 + Persistence modifier for Enhanced Access Channel attempts for registrations

28 which are not responses to the Registration Request Order (REG_PSISTs = ‘0’).
29 • The mobile station shall store the Access Control based on Call Type (ACCT)
30 information as follows:
31 – Set ACCT_SO_LIST to NULL.
32 – Set ACCT_SO_GRP_LIST to NULL.

33 – If ACCT_INCLr is equal to ‘1’ and ACCOLCp is in the range 0 to 9, then the
35 + Set ACCT_INCL_EMGs to ACCT_INCL_EMGr.
36 + If ACCT_SO_INCLr is equal to ‘1’, then for each ACCT_SOr included in this

37 message:
2-134
3GPP2 C.S0005-A v6.0
1 ο If ACCT_AOC_BITMAP_INCLr is equal to ‘0’, or if

2 ACCT_AOC_BITMAP_INCLr is equal to ‘1’ and the bit in the associated
3 ACCT_AOC_BITMAP1r corresponding to the mobile station’s ACCOLCp
4 (see Table 3.7.2.3.2.2-1) is equal to ‘1’, then add ACCT_SOr to
5 ACCT_SO_LIST.
6 + If ACCT_SO_GRP_INCLr is equal to ‘1’, then for each ACCT_SO_GRPr
7 included in this message:
8 ο If ACCT_AOC_BITMAP_INCLr is equal to ‘0’, or if
9 ACCT_AOC_BITMAP_INCLr is equal to ‘1’ and the bit in the associated
10 ACCT_AOC_BITMAP2r corresponding to the mobile station’s ACCOLCp
11 (see Table 3.7.2.3.2.2-1) is equal to ‘1’, then add ACCT_SO_GRPr to
12 ACCT_SO_GRP_LIST.
13
14 • Link Access Control related parameters:

15 – Acknowledgment timeout (EACH_ACC_TMOs = ACC_TMOr)
16 –Time randomization for Enhanced Access Channel probes

17 (PROBE_PN_RANs = PROBE_PN_RANr)
18 – Maximum number of probe sequences for an Enhanced Access Channel request

19 (MAX_REQ_SEQs = MAX_REQ_SEQr)
20 – Maximum number of probe sequences for an Enhanced Access Channel

21 response (MAX_RSP_SEQs = MAX_RSP_SEQr)
22 • Mode Selection Table:

23 NUM_MODE_SELECTION_ENTRIESs = (NUM_MODE_SELECTION_ENTRIESr + 1)
24 For i = 1 to NUM_MODE_SELECTION_ENTRIESsNUM_MODE_SELECTION_ENTRIES
25 + 1:
26 – MODE_SELECTIONs[i].ACCESS_MODE = ACCESS_MODE field of the ith
27 occurrence of the record
28 – MODE_SELECTIONs[i].MIN_DURATION = ACCESS_MODE_MIN_DURATION field
29 of the ith occurrence of the record
30 – MODE_SELECTIONs[i].MAX_DURATION = ACCESS_MODE_MAX_DURATION
31 field of the ith occurrence of the record
32 • Reverse gain adjustment of the Enhanced Access Channel or Reverse Common

33 Control Channel relative to the Reverse Pilot Channel (RLGAIN_COMMON_PILOTs =
34 RLGAIN_COMMON_PILOTr)
35 • The threshold level at which the interference correction begins to be applied

36 (IC_THRESHs = - IC_THRESHr)
37 • The maximum interference correction that can be applied (IC_MAXs = IC_MAXr)
38 • Mode-specific parameters for the Enhanced Access Channel:
2-135
3GPP2 C.S0005-A v6.0
1 For i = 1 to NUM_MODE_PARM_REC + 1:
2 For j = 0 to 7:
3 If the (j+1)th subfield of APPLICABLE_MODES is equal to ‘1’, store the

4 following parameters:
5 – Nominal transmit power offset on the Enhanced Access Channel

6 (MODE_PARMSs[j].EACH_NOM_PWR = EACH_NOM_PWR field of the ith
7 occurrence of the record)
8 – Initial power offset for access on the Enhanced Access Channel

9 (MODE_PARMSs[j].EACH_INIT_PWR = EACH_INIT_PWR field of the ith
11 – Power increment on the Enhanced Access Channel

12 (MODE_PARMSs[j].EACH_PWR_STEP = EACH_PWR_STEP field of the ith
13 occurrence of the record )
14 – Number of access probes on the Enhanced Access Channel

15 (MODE_PARMSs[j].EACH_NUM_STEP = EACH_NUM_STEP field of the ith
17 – Preamble enabled indicator on the Enhanced Access Channel

18 (MODE_PARMSs[j].EACH_PREAMBLE_ENABLED = EACH_PREAMBLE_E
19 NABLED field of the ith occurrence of the record)
20 – Number of preamble fractions sent on the Enhanced Access Channel if

21 MODE_PARMSs[j].EACH_PREAMBLE_ENABLED is equal to ‘1’
22 (MODE_PARMSs[j].EACH_PREAMBLE_NUM_FRAC =
23 EACH_PREAMBLE_NUM_FRAC field of the ith occurrence of the record)
24 – Fractional preamble duration on the Enhanced Access Channel if

26 (MODE_PARMSs[j].EACH_PREAMBLE_FRAC_DURATION = EACH_PREAM
27 BLE_FRAC_DURATION field of the ith occurrence of the record)
28 – Preamble gated-off duration on the Enhanced Access Channel if

30 (MODE_PARMSs[j].EACH_PREAMBLE_OFF_DURATION = EACH_PREAMB
31 LE_OFF_DURATION field of the ith occurrence of the record)
32 – Additional preamble duration on the Enhanced Access Channel if

34 (MODE_PARMSs[j].EACH_PREAMBLE_ADD_DURATION =
35 EACH_PREAMBLE_ADD_DURATION field of the ith occurrence of the
36 record)
37 –Access threshold on the Enhanced Access Channel

38 (MODE_PARMSs[j].EACH_ACCESS_THRESH = EACH_ACCESS_THRESH
39 field of the ith occurrence of the record)
40 – Enhanced Access Channel probe backoff range
2-136
3GPP2 C.S0005-A v6.0
1 (MODE_PARMSs[j].EACH_PROBE_BKOFF = EACH_PROBE_BKOFF field

2 of the ith occurrence of the record)
3 – Enhanced Access Channel probe sequence backoff range

4 (MODE_PARMSs[j].EACH_BKOFF = EACH_BKOFF field of the ith
6 – Enhanced Access Channel slot (MODE_PARMSs[j].EACH_SLOT = 1 +
7 EACH_SLOT field of the ith occurrence of the record)
8 – Enhanced Access Channel first slot offset

9 (MODE_PARMSs[j].EACH_SLOT_OFFSET1 = EACH_ SLOT_OFFSET1 field
11 – Enhanced Access Channel second slot offset

12 (MODE_PARMSs[j].EACH_SLOT_OFFSET2 = EACH_SLOT_OFFSET2 field
14 • Additional parameters for the Basic Access Mode:

15 If BA_PARMS_LENr is equal to ‘000’, set the Basic Access Mode supported indicator,
16 BA_SUPPORTEDs, to ‘0’; otherwise store the following parameters:
17 – Basic Access Mode supported indicator (BA_SUPPORTEDs = ‘1’)
18 – Number of Enhanced Access Channels (NUM_EACH_BAs = (NUM_EACH_BAr +

19 1))
20 – Rate words supported on the Enhanced Access Channels

21 (EACH_BA_RATES_SUPPORTEDs = EACH_BA_RATES_SUPPORTEDr)
22 • Additional parameters for the Reservation Access Mode:

23 If RA_PARMS_LENr is equal to ‘00000’, set the Reservation Access Mode supported
24 indicator, RA_SUPPORTEDs, to ‘0’; otherwise store the following parameters, if
25 included in the message:
26 – Reservation Access Mode supported indicator (RA_SUPPORTEDs = ‘1’)
27 – Number of Enhanced Access Channels (NUM_EACH_RAs = (NUM_EACH_RAr +

28 1))
29 – Number of Common Assignment Channels (NUM_CACHs = (NUM_CACHr + 1))
30 – Code rate of Common Assignment Channels (CACH_CODE_RATEs =

31 CACH_CODE_RATEr)
32 – For i = 0 to NUM_CACHs - 1, store the channel code index for each Common
33 Assignment Channel (CACH_CODE_CHANs[i] = CACH_CODE_CHANr.
34 – Number of Reverse Common Control Channels (NUM_RCCCHs = (NUM_RCCCHr

35 + 1))
36 – Rate words supported on the Reverse Common Control Channels

37 (RCCCH_RATES_SUPPORTEDs = RCCCH_RATES_SUPPORTEDr)
2-137
3GPP2 C.S0005-A v6.0
1 – Preamble enabled indicator on the Reverse Common Control Channels

2 (RCCCH_PREAMBLE_ENABLEDs = RCCCH_PREAMBLE_ENABLEDr)
3 – Number of preamble fractions sent on the Reverse Common Control Channel if

4 RCCCH_PREAMBLE_ENABLEDr is equal to ‘1’
5 (RCCCH_PREAMBLE_NUM_FRACs = RCCCH_PREAMBLE_NUM_FRACr)
6 – Fractional preamble duration on the Reverse Common Control Channel if

8 (RCCCH_PREAMBLE_FRAC_DURATIONs =
9 RCCCH_PREAMBLE_FRAC_DURATIONr)
10 – Preamble gated-off duration on the Reverse Common Control Channel if

12 (RCCCH_PREAMBLE_OFF_DURATIONs = RCCCH_PREAMBLE_OFF_DURATIONr)
13 – Additional preamble duration on the Reverse Common Control Channel if

15 (RCCCH_PREAMBLE_ADD_DURATIONs =
16 RCCCH_PREAMBLE_ADD_DURATIONr)
17 – Slot duration on the Reverse Common Control Channel (RCCCH_SLOTs = 1 +

18 RCCCH_SLOTr)
19 – First slot offset of the Reverse Common Control Channel

20 (RCCCH_SLOT_OFFSET1s = RCCCH_SLOT_OFFSET1r)
21 – Second slot offset of the Reverse Common Control Channel

22 (RCCCH_SLOT_OFFSET2s = RCCCH_SLOT_OFFSET2r)
23 – Nominal transmit power offset on the Reverse Common Control Channel

24 (RCCCH_NOM_PWRs = RCCCH_NOM_PWRr)
25 – Initial power offset for access on the Reverse Common Control Channel
26 (RCCCH_INIT_PWRs = RCCCH_INIT_PWRr)
27 – Power Control delay for the Reservation Access Mode

28 (RA_PC_DELAYs = RA_PC_DELAYr)
29 – Maximum delay to receive the Early Acknowledgment Channel Assignment

30 Message on the Common Assignment Channel
31 (EACAM_CACH_DELAYs = EACAM_CACH_DELAYr)
32 – Indicator for handoff supported on the Reverse Common Control Channels

33 (RCCCH_HO_SUPPORTEDs = RCCCH_HO_SUPPORTEDr)
34 – Threshold for handoff on the Reverse Common Control Channels if

35 RCCCH_HO_SUPPORTEDr is equal to ‘1’
36 (RCCCH_HO_THRESHs = RCCCH_HO_THRESHr)
37 – Maximum delay to receive the Early Acknowledgment Channel Assignment

38 Message and the Power Control Channel Assignment Message if
39 RCCCH_HO_SUPPORTEDr is equal to ‘1’
40 (EACAM_PCCAM_DELAYs = EACAM_PCCAM_DELAYr)
2-138
3GPP2 C.S0005-A v6.0
1 – Number of Common Power Control Channels (NUM_CPCCHs = (NUM_CPCCHr +

2 1))
3 – Power control rate for the Common Power Control Channels

4 (CPCCH_RATEs = CPCCH_RATEr)
5 – For i = 0 to NUM_CPCCHs - 1, store the channel code index for each Common
6 Power Control Channel (CPCCH_CODE_CHANs[i] = CPCCH_CODE_CHANr.
7 – Number of Power Control Subchannels for the Reservation Access Mode

8 (NUM_PCSCH_RAs = (NUM_PCSCH_RAr + 1))
9 2.6.2.2.16 ANSI-41 RAND Message

10 Whenever an ANSI-41 RAND Message is received, the mobile station shall process the fields
11 in the message as follows.
12 The mobile station shall store the following parameter if the mobile station is not in the
13 Origination Attempt Substate or Page Response Substate:
14 • Random challenge value (RANDs = RANDr)
15 • Pilot PN sequence offset increment (PILOT_PNs = PILOT_PNr)
16 The mobile station shall ignore any fields at the end of the ANSI-41 RAND Message which
19 2.6.2.2.17 Universal Neighbor List Message

20 Whenever a valid Universal Neighbor List Message is received on the Primary Broadcast
21 Control Channel, the configuration message sequence number, CONFIG_MSG_SEQr shall
22 be compared to that stored in UNIV_NGHBR_LST_MSG_SEQs. If the comparison results in
24 described below.

28 UNIV_NGHBR_LST_MSG_SEQs= CONFIG_MSG_SEQr).
29 If RADIO_INTERFACE_TYPEr is equal to ‘0000’ but the PILOT_INC field is not within the
30 valid range specified in 3.7.2.3.2.33, then the mobile station shall ignore the entire record
31 that contains it.
32 If RADIO_INTERFACE_TYPEr is equal to ‘0000’ and the PILOT_INC field is within the valid
33 range specified in 3.7.2.3.2.33, the mobile station shall perform the following:
34 The mobile station shall store the Pilot PN sequence offset increment (PILOT_INCs =
35 PILOT_INCr).
36 The mobile station shall set NGHBR_SET_SIZEs to NUM_NGHBRr.
2-139
3GPP2 C.S0005-A v6.0
1 For each of the neighboring base stations contained in the Universal Neighbor List Message,
2 if FREQ_INCLr is equal to ‘0’, or if FREQ_INCLr is equal to ‘1’ and NGHBR_BANDr is
3 supported, the mobile station shall do the following:
4 • If the ith occurrence of NGHBR_CONFIGr is equal to ‘000’, ‘001’, ‘010’, or ‘100’, set
5 the NGHBR_CONFIG field of NGHBR_REC[i] to the ith occurrence of
6 NGHBR_CONFIGr; otherwise, set the NGHBR_CONFIG field of NGHBR_REC[i] to
7 ‘011’.
8 • Set the NGHBR_PN field of NGHBR_REC[i] to the ith occurrence of NGHBR_PNr.
9 • If NGHBR_CONFIGr is equal to ‘011’, set the BCCH_SUPPORT field of NGHBR_

10 REC[i] to BCCH_SUPPORTr of the corresponding record.
11 • Set the ADD_PILOT_REC_INCL field of NGHBR_REC[i] to the ith occurrence of

12 ADD_PILOT_REC_INCLr. If ADD_PILOT_REC_INCLr equals ‘1’, for each pilot
13 included in the message, the mobile station shall also perform the following:
14 – Set the NGHBR_PILOT_REC_TYPE field of NGHBR_PILOT_REC to

16 – If NGHBR_PILOT_REC_TYPEr is equal to ‘000’. The mobile station shall:
17 + Set the TD_POWER_LEVEL field of NGHBR_PILOT_REC to

18 TD_POWER_LEVELr.
19 + Set the TD_MODE field of NGHBR_PILOT_REC to TD_MODEr.
20 – If NGHBR_PILOT_REC_TYPEr is equal to ‘001’, the mobile station shall:
21 + Set the AUX_PILOT_QOF field of NGHBR_PILOT_REC to QOFr.
22 + Set the AUX_PILOT_WALSH_CODE field of NGHBR_PILOT_REC to

23 AUX_PILOT_WALSHr with the Walsh Code length specified by
24 WALSH_LENGTHr.

28 AUX_WALSHr with the Walsh Code length specified by WALSH_LENGTHr.
29 + Set the AUX_TD_POWER_LEVEL field of NGHBR_PILOT_REC to

33 + Set the SR3_PRIMARY_PILOT field of NGHBR_PILOT_REC to

35 + Set the SR3_PILOT_POWER1 field of NGHBR_PILOT_REC to

2-140
3GPP2 C.S0005-A v6.0





13 WALSH_LENGTHr.
14 + If ADD_INFO_INCL1r is equal to ‘1’, set the AUX_PILOT_QOF1 field of

15 NGHBR_PILOT_REC to QOF1r and set the AUX_PILOT_WALSH_CODE1 field
16 of NGHBR_PILOT_REC to AUX_PILOT_WALSH1r with the Walsh Code length
17 specified by WALSH_LENGTH1r; otherwise, set the AUX_PILOT_QOF1 field of
18 NGHBR_PILOT_REC to QOFr and set the AUX_PILOT_WALSH_CODE1 field of
19 NGHBR_PILOT_REC to AUX_PILOT_WALSHr with the Walsh Code length
20 specified by WALSH_LENGTHr.

22 NGHBR_PILOT_REC to QOF2r and set the AUX_PILOT_WALSH_CODE2 field
23 of NGHBR_PILOT_REC to AUX_PILOT_WALSH2r with the Walsh Code length
24 specified by WALSH_LENGTH2r; otherwise, set the AUX_PILOT_QOF2 field of
25 NGHBR_PILOT_REC to QOFr and set the AUX_PILOT_WALSH_CODE2 field of
26 NGHBR_PILOT_REC to AUX_PILOT_WALSHr with the Walsh Code length
27 specified by WALSH_LENGTHr.
28 • If NGHBR_SRCH_MODEr = ‘00’ or ‘10’, set the SEARCH_PRIORITY field of each

29 NGHBR_REC to ‘10’ (high) for all NGHBR_SET_SIZEs entries.
30 • If NGHBR_SRCH_MODEr = ‘01’ or ‘11’, set the SEARCH_PRIORITY field of

31 NGHBR_REC[i] to the ith occurrence of SEARCH_PRIORITYr.
32 • If NGHBR_SRCH_MODEr = ‘00’ or ‘01’, set the SRCH_WIN_NGHBR field of each

33 NGHBR_REC to SRCH_WIN_Nr for all NGHBR_SET_SIZEs entries.
34 • If NGHBR_SRCH_MODEr = ‘00’ or ‘01’, set the SRCH_OFFSET_NGHBR field of each

35 NGHBR_REC to ‘000’.
36 • If NGHBR_SRCH_MODEr = ‘10’ or ‘11’:
37 – set the SRCH_WIN_NGHBR field of NGHBR_REC[i] to the ith occurrence of

38 SRCH_WIN_NGHBRr
2-141
3GPP2 C.S0005-A v6.0

2 NGHBR_REC[i] to the ith occurrence of SRCH_OFFSET_NGHBRr, and

4 each NGHBR_REC to ‘000’.
5 • If USE_TIMINGr is equal to ‘1’, set the TIMING_INCL field of NGHBR_REC[i] to the
6 ith occurrence of TIMING_INCLr; otherwise, set the TIMING_INCL field of
7 NGHBR_REC to ‘0’ for all entries.
9 if FREQ_FIELDS_INCLr equals ‘1’, FREQ_INCLr equals ‘1’, and NGHBR_BANDr is
10 supported, the mobile station shall also perform the following:

12 NGHBR_BANDr.

14 NGHBR_FREQr.
16 if USE_TIMINGr is equal to ‘1’ and TIMING_INCLr equals ‘1’, the mobile station shall also
18 • Set the NGHBR_TX_OFFSET field of NGHBR_REC[i] to the ith occurrence of

19 NGHBR_TX_OFFSETr.
21 – Set the NGHBR_TX_DURATION field of NGHBR_REC to

22 GLOBAL_TX_DURATIONr for all entries.
23 – Set the NGHBR_TX_PERIOD field of NGHBR_REC to GLOBAL_TX_PERIODr for

24 all entries.
26 – Set the NGHBR_TX_DURATION field of NGHBR_REC[i] to the ith occurrence of

27 NGHBR_TX_DURATIONr.
28 – Set the NGHBR_TX_PERIOD field of NGHBR_REC[i] to the ith occurrence of

29 NGHBR_TX_PERIODr.
31 if FREQ_FIELDS_INCLr equals ‘1’ and FREQ_INCLr equals ‘0’ the mobile station shall also
32 do the following:
35 If NGHBR_SET_ENTRY_INFOr is equal to ‘0’, then for all NGHBR_SET_SIZEs occurrences of

2-142
3GPP2 C.S0005-A v6.0
1 If NGHBR_SET_ENTRY_INFOr is equal to ‘1’, then for all NGHBR_SET_SIZEs occurrences of

3 NGHBR_REC[i] to the ith occurrence of ACCESS_ENTRY_HOr.
4 If NGHBR_SET_ACCESS_INFOr is equal to ‘0’, then for all NGHBR_SET_SIZEs occurrences

7 If NGHBR_SET_ACCESS_INFOr is equal to ‘1’, then for all NGHBR_SET_SIZEs occurrences
9 NGHBR_REC[i] to the ith occurrence of ACCESS_HO_ALLOWEDr.
11 consists only of pilot offsets listed in the Universal Neighbor List Message. If the Universal
13 mobile station shall store the pilot offsets beginning at the start of the Universal Neighbor
14 List Message, up to the limits of the mobile station’s Neighbor Set storage capacity.
15 If RADIO_INTERFACE_TYPEr is equal to ‘0001’, the mobile station shall process the fields
16 contained in the record as follows:
17 The mobile station shall set NUM_ANALOG_NGHBRs to NUM_ANALOG_NGHBRr, the
18 number of neighboring analog systems contained in the Universal Neighbor List Message.
19 For each of the neighboring analog systems contained in the Universal Neighbor List
20 Message, the mobile station shall perform the following:
21 • Set the BAND_CLASS field of ANALOG_NGHBR_LIST[i] to the ith occurrence of

22 BAND_CLASSr.
23 • Set the SYS_A_B field of ANALOG_NGHBR_LIST[i] to the ith occurrence of SYS_A_Br.
24 2.6.2.3 Mobile Station Page Match Operation
25 The Mobile Station Page Match Operation is performed whenever the mobile station receives
26 a mobile-station-addressed page or a broadcast page. If the mobile station receives a
27 mobile-station-addressed page that contains the IMSI or TMSI assigned to the mobile
28 station (see [4]) on the Paging Channel, the mobile station transmits a Page Response
29 Message on the Access Channel. If the mobile station receives a mobile-station-addressed
30 page that contains the IMSI or TMSI assigned to the mobile station (see [4]) on the Forward
31 Common Control Channel, the mobile station transmits a Page Response Message on the r-
32 csch. If the mobile station is configured to receive broadcast messages and it receives a
33 General Page Message that contains a burst type and broadcast address that the mobile
34 station has been configured to receive (see [4]) on the Paging Channel, the mobile station
35 performs the broadcast page procedures as described in 2.6.2.1.1.3.4. If the mobile station
36 is configured to receive broadcast messages and it receives a General Page Message or a
37 Universal Page Message that contains a burst type and broadcast address that the mobile
38 station has been configured to receive (see [4]) on the Forward Common Control Channel,
39 the mobile station performs the enhanced broadcast page procedures as described in
40 2.6.2.1.1.3.6.
2-143
3GPP2 C.S0005-A v6.0
1 When the mobile station receives a page message, it shall compare the configuration
2 message sequence number, CONFIG_MSG_SEQr, to CONFIG_MSG_SEQs. If the
3 comparison results in a mismatch, then the mobile station shall set CONFIG_MSG_SEQs to
4 CONFIG_MSG_SEQr. The mobile station shall also compare the Access Parameters
5 Message or the Enhanced Access Parameters Message sequence number, ACC_MSG_SEQr,
6 with that stored in ACC_MSG_SEQs. If the comparison results in a mismatch, then the
7 mobile station shall set ACC_MSG_SEQs to NULL (see 2.6.2.2). The mobile station shall set
8 CURR_ACC_MSG_SEQ to ACC_MSG_SEQs.
9 The mobile station shall process each record for which it declares a page match (see [4]).
10 If the mobile station receives a broadcast page that contains a burst type and broadcast
11 address that the mobile station has been configured to receive on the Paging Channel, the
12 mobile station should perform the broadcast page procedures described in 2.6.2.1.1.3.4. If
13 the mobile station receives a broadcast page that contains a burst type and broadcast
14 address that the mobile station has been configured to receive on the Forward Common
15 Control Channel, the mobile station should perform the enhanced broadcast page
16 procedures as described in 2.6.2.1.1.3.6.
17 If a page match is declared, the mobile station shall perform the following:
18 • The mobile station shall set SYNC_IDs to NULL if the mobile station is currently in a
19 different SID, NID, or CDMA Channel than where the SYNC_IDs was stored.
20 • the The mobile station shall enter the Update Overhead Information Substate of the
21 System Access State (see 2.6.3.2) with a page response indication within T33m
22 seconds after the page message is received.
23 If a page match is declared and the mobile station determines that it should be monitoring
24 a neighboring base station, the mobile station may perform an access entry handoff to the
25 neighboring base station, if all of the following conditions hold:
26 • The neighboring base station is listed in NGHBR_REC.
27 • The ACCESS_ENTRY_HO field of the NGHBR_REC corresponding to the neighboring

28 base station is equal to ‘1’.
29 • If the mobile station performs an access entry handoff on the Access Channel, none
30 of CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,
32 CHAN_LST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
33 USER_ZONE_ID_MSG_SEQs, and PRI_NGHBR_LST_MSG_SEQs are equal to NULL.
34 • If the mobile station performs an access entry handoff on the Enhanced Access
35 Channel, none of CONFIG_MSG_SEQs, A41_SYS_PAR_MSG_SEQs,
36 MC_RR_PAR_MSG_SEQs, UNI_NGHBR_LST_MSG_SEQs,
38 PRI_NGHBR_LST_MSG_SEQs are equal to NULL.
39 Otherwise, the mobile station shall not perform an access entry handoff to the neighboring
40 base station.
2-144
3GPP2 C.S0005-A v6.0
1 The mobile station need not perform an access entry handoff to a base station operating on
2 another frequency.
3 If the mobile station performs an access entry handoff, it shall follow the procedures
4 specified in 2.6.2.1.4.2 and shall perform the access entry handoff before entering the
5 Update Overhead Information Substate of the System Access State (see 2.6.3.2).
6 If PACA is enabled, and if the mobile station performs an access entry handoff, the mobile
7 station shall respond to the mobile-station-addressed page first and shall then re-originate
8 the PACA call on the new base station.
9 2.6.2.4 Mobile Station Order and Message Processing Operation
10 During the Mobile Station Order and Message Processing Operation, the mobile station
11 processes all messages except overhead messages (see 2.6.2.2) and page messages (see
12 2.6.2.3).
13 The mobile station shall set CURR_ACC_MSG_SEQ to NULL.
14 The mobile station shall perform address matching as described in 2.1.2.2 of [4].
15 If Layer 3 receives a message that requires acknowledgement, the mobile station shall enter
16 the Update Overhead Information Substate of the System Access State with an
17 order/message response indication within T33m seconds, unless otherwise specified for a
18 particular message.
19 If Layer 3 receives a message that does not require acknowledgement, the mobile station
20 shall transmit a response only if it is required by the message or order. If a response is
21 required, the mobile station shall enter the Update Overhead Information Substate of the
22 System Access State with an order/message response indication within T33m seconds,
23 unless otherwise specified for a particular message.
24 If the mobile station is to enter the Update Overhead Information Substate of the System
25 Access State with an order/message response indication and the mobile station determines
26 that it should be monitoring a neighboring base station, the mobile station may perform an
27 access entry handoff to the neighboring base station, if all of the following conditions hold:
28 • The neighboring base station is listed in NGHBR_REC.
29 • The ACCESS_ENTRY_HO field of the NGHBR_REC corresponding to the neighboring

30 base station is equal to ‘1’.
31 • ACC_ENT_HO_ORDERs is equal to ‘1’.
32 • If the mobile station performs an access entry handoff on the Access Channel, none
33 of CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,
35 CHAN_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
36 PRI_NGHBR_LST_MSG_SEQs, and EXT_SYS_PAR_MSG_SEQs are equal to NULL.
2-145
3GPP2 C.S0005-A v6.0
1 • If the mobile station performs an access entry handoff on the Enhanced Access
2 Channel, none of CONFIG_MSG_SEQs, A41_SYS_PAR_MSG_SEQs,
3 MC_RR_PAR_MSG_SEQs, UNI_NGHBR_LST_MSG_SEQs,
5 PRI_NGHBR_LST_MSG_SEQs are equal to NULL.
6 Otherwise, the mobile station shall not perform an access entry handoff to the neighboring
7 base station.
8 The mobile station need not perform an access entry handoff to a base station operating on
9 another frequency.
10 If the mobile station performs an access entry handoff, it shall follow the procedures
11 specified in 2.6.2.1.4.2 and shall perform the access entry handoff before entering the
12 Update Overhead Information Substate of the System Access State (see 2.6.3.2). If PACA is
13 enabled and the mobile station performs an access entry handoff, the mobile station shall
14 respond to the order/message first and then re-originate the PACA call in the new base
15 station.
16 The following directed messages and orders can be received. If any field value of the
17 message or order is outside its permissible range, the mobile station shall send a Mobile
18 Station Reject Order with ORDQ equal to ‘00000100’ (message field not in valid range).
19 1. Abbreviated Alert Order: The mobile station may alert the user.
20 2. Audit Order
21 3. Authentication Challenge Message: The mobile station shall process the message
22 and shall respond with an Authentication Challenge Response Message as specified
23 in 2.3.12.1.4, regardless of the value of AUTHs. The mobile station shall enter the
24 Update Overhead Information Substate of the System Access State with an
25 order/message response indication within T32m seconds.
26 4. Base Station Challenge Confirmation Order: The mobile station shall process the
27 message and shall respond with an SSD Update Confirmation Order or SSD Update
28 Rejection Order as specified in 2.3.12.1.5. The mobile station shall enter the Update
29 Overhead Information Substate of the System Access State with an order/message
30 response indication within T32m seconds.
31 5. Base Station Reject Order:

32 • If ORDQr = ‘00000001’, the mobile station shall send a Security Mode Request
33 Message with the ENC_SIG_H field included in it. If the mobile receives two Base
34 Station Reject Orders without successfully decrypting any encrypted messages
35 from the base station between the orders, the mobile station shall set
36 REG_ENCRYPT_RESYNC to YES and enter the System Determination Substate
37 with an encryption failure indication.
38 5.6. Channel Assignment Message: The mobile station shall process the message as
39 follows:
40 • If ASSIGN_MODEr equals ‘001’, the mobile station shall perform the following
41 actions:
2-146
3GPP2 C.S0005-A v6.0
1 - If the message requires acknowledgement, the mobile station shall wait until
2 Layer 3 receives an indication from Layer 2 that the acknowledgement to the
3 message has been sent and acknowledged.
4 - If a CDMA channel (CDMA_FREQ) is specified in the assignment, the mobile

5 station shall set CDMACHs = CDMA_FREQr, tune to the new Frequency
6 Assignment, and measure the strength of each pilot listed in the assignment
7 using the Neighbor Set search procedures specified in 2.6.6.2.1 and
8 2.6.6.2.2.
9 - The mobile station shall set CONFIG_MSG_SEQs and ACC_MSG_SEQs to
10 NULL (see 2.6.2.2) and shall set PILOT_PNs to the pilot PN sequence offset of
11 the strongest pilot in the list (PILOT_PNr).
12 - If the mobile station has not stored configuration parameters for the Primary
13 Paging Channel of the new base station, or if the stored information is not
14 current (see 2.6.2.2), the mobile station shall set SYS_PAR_MSG_SEQs,
17 EXT_CHAN_LST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs,
18 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LST_MSG_SEQs,
19 GLOB_SERV_REDIR_MSG_SEQs, and EXT_GLOB_SERV_REDIR_MSG_SEQs
20 to NULL. The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to
21 the Primary Paging Channel. If the mobile station was monitoring Forward
22 Common Control Channel, the mobile station shall set the PRATs to ‘00’. The
23 mobile station shall then begin monitoring the Primary Paging Channel of
24 the selected base station.
25 • If ASSIGN_MODEr equals ‘101’ and FREQ_INCLr equals ‘0’, the mobile station
30 - The mobile station shall measure the strength of each pilot listed in the
31 assignment using the Neighbor Set search procedures specified in 2.6.6.2.1
32 and 2.6.6.2.2, set PILOT_PNs to the pilot PN sequence offset of the strongest
33 pilot in the list (PILOT_PNr), and set CONFIG_MSG_SEQs and
34 ACC_MSG_SEQs to NULL (see 2.6.2.2).
2-147
3GPP2 C.S0005-A v6.0
10 the Primary Paging Channel. The mobile station shall then begin monitoring
11 the Primary Paging Channel of the selected base station.
12 • If ASSIGN_MODEr equals ‘101’, FREQ_INCLr equals ‘1’, and the band class is
13 not supported by the mobile station, the mobile station shall enter the Update
14 Overhead Information Substate of the System Access State with an
15 order/message response indication within T33m seconds and send a Mobile
16 Station Reject Order with ORDQ field set to ‘00000110’ (capability not supported
17 by the mobile station).
19 supported by the mobile station, the mobile station shall perform the following
20 actions:
21 - If the message requires acknowledgment, the mobile station shall wait until
22 Layer 3 receives an indication from Layer 2 that the acknowledgment to the
24 - The mobile station shall set CDMACHs = CDMA_FREQr and CDMABANDs =
25 BAND_CLASSr. Then the mobile station shall tune to the new Frequency
26 Assignment, measure the strength of each pilot listed in the assignment
28 2.6.6.2.2, set PILOT_PNs to the pilot PN sequence offset of the strongest pilot
29 in the list (PILOT_PNr), and set CONFIG_MSG_SEQs and ACC_MSG_SEQs to
30 NULL (see 2.6.2.2).
2-148
3GPP2 C.S0005-A v6.0
1 • If ASSIGN_MODEr is not equal to ‘001’ or ‘101’, the mobile station shall enter
2 the Update Overhead Information Substate of the System Access State with an
4 Station Reject Order with ORDQ field set to ‘00000010’ (message not accepted in
5 this state).
6 6.7. Data Burst Message
7 7.8. Extended Channel Assignment Message: The mobile station shall process the
8 message as follows:
9 • If ASSIGN_MODEr equals ‘001’, FREQ_INCLr equals ‘0’, the mobile station shall
14 - The mobile station shall measure the strength of each pilot listed in the
15 assignment using the Neighbor Set search procedures specified in 2.6.6.2.1
16 and 2.6.6.2.2 set PILOT_PNs to the pilot PN sequence offset of the strongest
17 pilot in the list (PILOT_PNr), and set CONFIG_MSG_SEQs and
18 ACC_MSG_SEQs to NULL (see 2.6.2.2).
28 the Primary Paging Channel. If the mobile station was monitoring Forward
29 Common Control Channel, the mobile station shall set the PRATs to ‘00’. The
30 mobile station shall then begin monitoring the Primary Paging Channel of
33 not supported by the mobile station, the mobile station shall enter the Update
36 Station Reject Order with ORDQ field set to ‘00000110’ (capability not supported
37 by the mobile station).
39 supported by the mobile station, the mobile station shall perform the following
40 actions:
2-149
3GPP2 C.S0005-A v6.0
4 - The mobile station shall set CDMACHs = CDMA_FREQr and CDMABANDs =
5 BAND_CLASSr. The mobile station shall set CONFIG_MSG_SEQs and
6 ACC_MSG_SEQs to NULL (see 2.6.2.2). Then the mobile station shall tune to
7 the new Frequency Assignment, measure the strength of each pilot listed in
8 the assignment using the Neighbor Set search procedures specified in
9 2.6.6.2.1 and 2.6.6.2.2, and set PILOT_PNs to the pilot PN sequence offset of
22 • If ASSIGN_MODEr is not equal to ‘001’, the mobile station shall enter the Update
25 Station Reject Order with ORDQ field set to ‘00000010’ (message not accepted in
26 this state).
27 8.9. Feature Notification Message
28 9.10 Local Control Order
29 10.11 Lock Until Power-Cycled Order: The mobile station shall record the reason for the
30 Lock Until Power-Cycled Order in the mobile station’s semi-permanent memory
31 (LCKRSN_Ps-p equals the least significant four bits of ORDQr). After a mobile station
32 receives this order, it shall not enter the System Access State (see 2.6.3) until it has
33 received an Unlock Order or until after power-cycling the mobile station (i.e., after the
34 next mobile station power-up). This requirement shall take precedence over any other
35 mobile station requirement specifying entry to the System Access State. The mobile
36 station should notify the user of the locked condition. The mobile station shall exit the
37 Mobile Station Idle State and enter the System Determination Substate of the Mobile
38 Station Initialization State with a lock indication (see 2.6.1.1). This allows the mobile
39 station to operate in an alternate operating mode while locked.
40 11.12 Maintenance Required Order: The mobile station shall record the reason for the
41 Maintenance Required Order in the mobile station’s semi-permanent memory
42 (MAINTRSNs-p equals the least significant four bits of ORDQr). If the mobile station
43 has previously received a Lock Until Power-Cycled Order, it shall remain in the locked
2-150
3GPP2 C.S0005-A v6.0
1 condition; otherwise the mobile station shall remain in the unlocked condition. The
2 mobile station should notify the user of the maintenance required condition.
3 12.13 PACA Message: If P_REV_IN_USEs is less than or equal to four, and if the
4 mobile station does not support PACA capability, the mobile station shall send a Mobile
5 Station Reject Order with the ORDQ field set to ‘00000110’ (message requires a
6 capability that is not supported by the mobile station); otherwise, the mobile station
7 shall process the message as follows:
8 • If PACAs is equal to disabled, the mobile station shall enter the Update Overhead
9 Information Substate of the System Access State with an order/message response
10 indication within T33m seconds and shall send a Mobile Station Reject Order with
11 the ORDQ field set to ‘00000010’ (message not accepted in this state).
12 • If PACAs is equal to enabled, the mobile station shall perform the following:
13 – If the purpose of the message is to respond to an Origination Message

14 (PURPOSEr is equal to ‘0000’), the mobile station shall enter the Update
17 Station Reject Order with the ORDQ field set to ‘00000010’ (message not
18 accepted in this state).
19 – If the purpose of the message is to provide the queue position of the PACA
20 call (PURPOSEr is equal to ‘0001’), the mobile station shall set the PACA
21 state timer to the duration shown in Table 3.7.2.3.2.20-2, corresponding to
22 the value of PACA_TIMEOUTs, should indicate to the user that the PACA call
23 is still queued, and should indicate the current queue position (Q_POSr) of
24 the call.
25 – If the purpose of the message is to instruct the mobile station to re-originate

26 the PACA call (PURPOSEr is equal to ‘0010’), the mobile station shall set the
27 PACA state timer to the duration shown in Table 3.7.2.3.2.20-2
28 corresponding to the value of PACA_TIMEOUTs, and the mobile station shall
29 enter the Update Overhead Information Substate of the System Access State
30 (see 2.6.3) with a PACA response indication within T33m seconds to re-
31 originate the PACA call.
32 – If the purpose of the message is to cancel the PACA call (PURPOSEr is equal
33 to ‘0011’), the mobile station shall set PACAs to disabled and PACA_CANCEL
34 to ‘0’, shall disable the PACA state timer, and should indicate to the user
35 that the PACA call has been canceled.
36 13.14 Registration Accepted Order:

37 • If ORDQr = ‘00000101’, the mobile station shall set ROAM_INDIs = ROAM_INDIr
38 and should display the roaming condition.
39 • If ORDQr = ‘00000111’, the mobile station shall perform the following
40 - The mobile station shall set ROAM_INDIs =to ROAM_INDIr and should
41 display the roaming condition.
2-151
3GPP2 C.S0005-A v6.0
1 - The mobile station shall set C_SIG_ENCRYPT_MODEs =to

2 C_SIG_ENCRYPT_MODEr.
3 - If USE_NEW_KEYr is not included, or is included and is set to ‘1’, the mobile

4 station shall use the session key generated at the most recent registration for
5 encryption of signaling and user information. The mobile station shall store
6 the session key in KEYs[KEY_SEQ_NEWs-p]. The mobile station shall store
7 KEY_SIZEr in KEY_SIZEs. The mobile station shall increment the variable
8 KEY_SEQ_NEWs-p by one (modulo 16).If ENC_KEY_SIZEr is included, the
9 mobile station shall set ENC_KEY_SIZEs to ENC_KEY_SIZEr.
10 -If USE_NEW_KEYr is included and is set to ‘0’, then the mobile station shall use
11 KEYs[KEY_SEQr] as the session key.
12 - If C_SIG_ENCRYPT_MODEr is not equal to ‘000’, the mobile station shall set

13 ENC_KEYs to the most recently generated CMEAKEY in the mobile station
14 associated with the AUTHR of the Registration Message, and
15 EXT_ENCRYPT_SEQ[0] and EXT_ENCRYPT_SEQ[1] to 256 × ENC_SEQ_H
16 (the ENC_SEQ_H field in the Registration Message).
17 14.15 Registration Rejected Order: This order indicates that normal service is not
18 available on this system. The mobile station shall disable the full-TMSI timer. If the
19 received order specifies to delete the TMSI (ORDQ = ‘00000100’), the mobile station
20 shall set all the bits of the TMSI_CODEs-p to ‘1’. The mobile station shall enter the
21 System Determination Substate of the Mobile Station Initialization State with a
22 registration rejected indication (see 2.6.1.1).
23 15.16 Registration Request Order: The mobile station shall process the message and
24 perform registration procedures as specified in 2.6.5.5.2.3.
25 16.17 Security Mode Command Message: The mobile station shall process the message
26 as follows:
27 • The mobile station shall set C_SIG_ENCRYPT_MODEs to
29 • If USE_NEW_KEYr is not included, or is included and is set to ‘1’, the mobile

31 encryption of signaling and user information. The mobile station shall store the
32 session key in KEYs[KEY_SEQ_NEWs-p]. The mobile station shall store
33 KEY_SIZEr in KEY_SIZEs. The mobile station shall then increment the variable
34 KEY_SEQ_NEWs-p by one (modulo 16).If ENC_KEY_SIZEr is included, the mobile
35 station shall set ENC_KEY_SIZEs to ENC_KEY_SIZEr .
36 • If USE_NEW_KEYr is included and is set to ‘0’, then the mobile station shall use
38 17. 18 Service Redirection Message: The mobile station shall process the message
39 as follows:
2-152
3GPP2 C.S0005-A v6.0
1 • If the mobile station is directed to an unsupported operation mode or band class,

2 the mobile station shall respond with a Mobile Station Reject Order with ORDQ
3 equal to ‘00000110’ (message requires a capability that is not supported by the
4 mobile station).
6 TMSI_CODEs-p to ‘1’. The mobile station shall disable the full-TMSI timer.
7 • The mobile station shall set RETURN_IF_FAILs = RETURN_IF_FAILr.
8 • If RECORD_TYPEr is equal to ‘00000000’, the mobile station shall enter the

9 System Determination Substate of the Mobile Station Initialization State with an
10 NDSS off indication (see 2.6.1.1); otherwise, the mobile station shall store the
11 redirection record received in the message as REDIRECT_RECs and shall enter
12 the System Determination Substate of the Mobile Station Initialization State with a
13 redirection indication (see 2.6.1.1).
14 18.19 Retry Order: The mobile station shall process the message as follows:
15 • If RETRY_TYPEr is equal to ‘000’, the mobile station shall set
16 RETRY_DELAYs[RETRY_TYPE] to 0, where RETRY_TYPE is equal to ‘001’, ‘010’,
17 or ‘011’.
18 • If RETRY_TYPEr is equal to ‘001’, the mobile station shall perform the following:
19 − If RETRY_DELAYr is equal to ‘00000000’, then the mobile station shall set

20 RETRY_DELAYs[RETRY_TYPEr] to 0.
21 − If RETRY_DELAYr is not equal to ‘00000000’, the mobile station shall set

22 RETRY_DELAYs[RETRY_TYPEr] as follows:
23 + If the most significant bit of the RETRY_DELAYr is ‘0’, set

24 RETRY_DELAY_UNITs to 1000ms. If the most significant bit of the
25 RETRY_DELAYr is ‘1’, set RETRY_DELAY_UNITs to 60000ms.
26 + The mobile station shall set RETRY_DELAY_VALUEs to the seven least

27 significant bits of RETRY_DELAYr.
28 + The mobile station shall store the next system time 80 ms boundary +
29 RETRY_DELAY_VALUEs × RETRY_DELAY_UNITs ms as
30 RETRY_DELAYs[RETRY_TYPEr].
31 19.20 Slotted Mode Order: After receiving this order, the mobile station shall set
32 SLOTTEDs to YES. The mobile station shall disable the TMS_Slotted timer.
33 20.21 SSD Update Message: The mobile station shall process the message and shall
34 respond with a Base Station Challenge Order as specified in 2.3.12.1.5. The mobile
35 station shall enter the Update Overhead Information Substate of the System Access
36 State with an order/message response indication within T32m seconds.
37 21.22 Status Request Message: The mobile station shall process the message. If
38 P_REV_IN_USEs is less than or equal to three, the mobile station shall respond with a
39 Status Response Message. If P_REV_IN_USEs is greater than three, the mobile station
40 shall respond with an Extended Status Response Message. The mobile station shall
2-153
3GPP2 C.S0005-A v6.0
1 enter the Update Overhead Information Substate of the System Access State with an
2 order/message response indication within T33m seconds. If the message does not
3 specify any qualification information (QUAL_INFO_TYPEr is equal to ‘00000000’), the
4 mobile station shall include the requested information records in the response. If the
5 message specifies a band class (QUAL_INFO_TYPEr is equal to ‘00000001’), the mobile
6 station shall only include the requested information records for the specified band class
7 (BAND_CLASSr) in the response. If the message specifies a band class and an
8 operating mode (QUAL_INFO_TYPEr is equal to ‘00000010’), the mobile station shall
9 only include the requested information records for the specified band class
10 (BAND_CLASSr) and operating mode (OP_MODEr) in the response. If the message
11 specifies a band class or a band class and an operating mode which is not supported
12 by the mobile station, the mobile station shall send a Mobile Station Reject Order with
13 ORDQ set to ‘00000110’ (message requires a capability that is not supported by the
14 mobile station). If the response to this message exceeds the allowable length, the
15 mobile station shall send a Mobile Station Reject Order with ORDQ set to ‘00001000’
16 (response message would exceed the allowable length). If the message specifies an
17 information record which is not supported by the mobile station for the specified band
18 class and operating mode, the mobile station shall send a Mobile Station Reject Order
19 with ORDQ set to ‘00001001’ (information record is not supported for the specified
20 band class and operating mode).
21 22.23 TMSI Assignment Message: The mobile station shall store the TMSI zone and
22 code as follows:
23 • The mobile station shall store the length of the TMSI zone field by setting
24 ASSIGNING_TMSI_ZONE_LENs-p to TMSI_ZONE_LENr,
25 • The mobile station shall store the assigning TMSI zone number by setting the
26 ASSIGNING_TMSI_ZONE_LENs-p least significant octets of
27 ASSIGNING_TMSI_ZONEs-p to TMSI_ZONEr, and
28 • The mobile station shall store the TMSI code by setting TMSI_CODEs-p to
29 TMSI_CODEr.
30 The mobile station shall set the TMSI expiration time by setting TMSI_EXP_TIMEs-p
31 to TMSI_EXP_TIMEr. The mobile station shall disable the full-TMSI timer. The
32 mobile station shall then respond with a TMSI Assignment Completion Message
33 within T56m seconds.
34 23.24 Unlock Order: After receiving this order, the mobile station is no longer locked.
35 The mobile station should notify the user that the locked condition has been removed.
36 The mobile station shall enter the System Determination Substate of the Mobile Station
37 Initialization State with an unlock indication (see 2.6.1.1).
38 24.25 User Zone Reject Message
39 9.Base Station Reject Order:
2-154
3GPP2 C.S0005-A v6.0
6 with an encryption failure indication.
7 The mobile station shall ignore all other messages and orders.
8 2.6.2.5 Mobile Station Origination Operation
9 The Mobile Station Origination Operation is performed when the mobile station is directed by
10 the user to initiate a call, or if the Mobile Station Idle State is entered with NDSS_ORIGs
11 enabled.
12 If the mobile station is directed by the user to initiate a call, the mobile station shall
14 • If PACAs is equal to enabled, the mobile station shall set PACAs to disabled and
15 PACA_CANCEL to ‘0’, shall disable the PACA state timer, and should indicate to the
16 user that the PACA call has been canceled.
17 • The mobile station shall set CURR_ACC_MSG_SEQ to NULL.

18 • The mobile station shall set SYNC_IDs to NULL if the mobile station is currently in a
19 different SID, NID, or CDMA Channel than where the SYNC_IDs was stored.
20 The mobile station shall enter the Update Overhead Information Substate of the System
21 Access State (see 2.6.3) with an origination indication within T33m seconds.
22 2.6.2.6 Mobile Station Message Transmission Operation
23 Support of this operation is optional. If the mobile station supports the Mobile Station
24 Message Transmission Operation, the operation is performed when the user directs the
25 mobile station to transmit a Data Burst Message, or when the mobile station detects a
26 change in hook status since the last time when the mobile station sent hook status
27 information and the mobile station supports the Device Information Message on the r-csch.
28 If the mobile station supports this operation, the mobile station shall set
29 CURR_ACC_MSG_SEQ to NULL.
30 If the mobile station supports this operation and the operation is performed when the user
31 directs the mobile station to transmit a Data Burst Message, the mobile station shall enter
32 the Update Overhead Information Substate of the System Access State (see 2.6.3.2) with a
33 message transmission indication within T33m seconds.
34 If the mobile station supports this operation and the operation is performed when the
35 mobile station detects a change in hook status since the last time when the mobile station
36 sent hook status information, the mobile station shall enter the Update Overhead
37 Information Substate of the System Access State (see 2.6.3.2) with a hook status indication
2-155
3GPP2 C.S0005-A v6.0
1 2.6.2.7 Mobile Station Power-Down Operation
2 The Mobile Station Power-Down Operation is performed when the user directs the mobile
3 station to power down.
4 The mobile station shall update stored parameters and perform other registration
5 procedures as specified in 2.6.5.5.2.4.
6 If no power-down registration is performed (see 2.6.5.5.2.4), the mobile station may power
7 down.
8 2.6.2.8 Mobile Station PACA Cancel Operation
9 The Mobile Station PACA Cancel Operation is performed when the user directs the mobile
10 station to cancel a PACA call.
11 If PACAs is equal to enabled, the mobile station shall perform the following:
12 • The mobile station shall set PACAs to disabled.
13 • The mobile station shall set PACA_CANCEL to ‘0’, if PACA_CANCEL is equal to ‘1’.
14 • The mobile station shall disable the PACA state timer.
15 • The mobile station should indicate to the user that the PACA call has been canceled.
16 • The mobile station shall set CURR_ACC_MSG_SEQ to NULL.
17 • The mobile station shall enter the Update Overhead Information Substate of the
18 System Access State (see 2.6.3) with a PACA cancel indication within T33m seconds.
19 2.6.3 System Access State

20 In this state, the mobile station sends messages to the base station on the r-csch and
21 receives messages from the base station on the f-csch.
22 As illustrated in Figure 2.6.3-1, the System Access State consists of the following substates:
23 • Update Overhead Information Substate - In this substate, if the base station supports
24 the Primary Broadcast Control Channel for Spreading Rate 1 or if both the base
25 station and mobile station supports the Primary Broadcast Control Channel for
26 Spreading Rate 3 and if the protocol revision level in use is greater than six, the
27 mobile station will monitor the Primary Broadcast Control Channel until it has
28 received a current set of overhead messages; otherwise, the mobile station will
29 monitor the Paging Channel until it has a current set of overhead messages.
30 • Mobile Station Origination Attempt Substate - In this substate, the mobile station
31 sends an Origination Message to the base station.
32 • Page Response Substate - In this substate, the mobile station sends a Page
33 Response Message to the base station.
34 • Mobile Station Order/Message Response Substate - In this substate, the mobile

35 station sends a response to a message received from the base station.
2-156
3GPP2 C.S0005-A v6.0
1 • Registration Access Substate - In this substate, the mobile station sends a

2 Registration Message to the base station.
3 • Mobile Station Message Transmission Substate - In this substate, the mobile station
4 sends a Data Burst Message or a Device Information Message to the base station.
5 • PACA Cancel Substate - In this substate, the mobile station sends a PACA Cancel
6 Message to the base station.
(Enter from Mobile Station Idle State)
GPM= Received a UPM = Received a

Note:Transitions arising General Page Universal Page
from error conditions and Update Overhead
Information Message Message
lock orders are not shown.
Substate
(2.6.3.2)
GPM/UPM
Received message or
order requiring an User initiated a Page Response
acknowledgement or call, or PACA Substate
Registration User
response call re-originated (2.6.3.3)
access generated
Data Burst
Message /UPM
GPM
User
PM
Registration Access
/UPM
/U
Mobile Station initiated
PM
Substate a call
Order/Message
G
(2.6.3.6)
GPM
Response
Substate User Mobile Station
Mobile Station
(2.6.3.4) cancelled a Origination Attempt
Message
PACA call Substate
Transmission
(2.6.3.5)
Substate
(2.6.3.7)
(EnterMobile Station
PACA
Control on the Traffic
Cancel Substate
Channel State or go to
(Enter Mobile (2.6.3.8)
analog)
Station Idle
State) (Enter Mobile Station
Idle State, Mobile
Station Control on the
Traffic Channel State
or go to analog)
10
11 Figure 2.6.3-1. System Access State
12 2.6.3.1 Access Procedures
13 2.6.3.1.1 Access Attempts
14 If the mobile station monitors the Paging Channel, the mobile station transmits on the
15 Access Channel using a random access procedure. Many parameters of the random access
16 procedure are supplied by the base station in the Access Parameters Message. The random
17 access procedure is described in [4] and [3].
18 If the mobile station monitors the Forward Common Control Channel/ Primary Broadcast
19 Control Channel, the mobile station transmits on the Enhanced Access Channel using a
20 random access procedure. Many parameters of the random access procedure are supplied
21 by the base station in the Enhanced Access Parameters Message.
2-157
3GPP2 C.S0005-A v6.0
1 If Layer 3 receives an indication from Layer 2 that the system access is denied, the mobile
2 station shall update its registration variables using SIDs, NIDs, REG_ZONEs, and
3 ZONE_TIMERs that were stored from the first base station to which the mobile station sent
4 an Access Probe, as specified in 2.6.5.5.3.2, and enter the System Determination Substate of
5 the Mobile Station Initialization State with an access denied indication (see 2.6.1.1).
6 If Layer 3 receives an indication from Layer 2 that the system is lost, the mobile station
7 shall update its registration variables using SIDs, NIDs, REG_ZONEs, and ZONE_TIMERs
8 that were stored from the first base station to which the mobile station transmitted an
9 Access Probe, as specified in 2.6.5.5.3.2 and enter the System Determination Substate of the
10 Mobile Station Initialization State with a system lost indication (see 2.6.1.1)
11 2.6.3.1.2 Reserved
12 2.6.3.1.3 Handoffs
13 While in the System Access State, the mobile station shall continue its pilot search
14 (see 2.6.3.1.3.1), and may perform access handoffs (see 2.6.3.1.3.2) and/or access probe
15 handoffs (see 2.6.3.1.3.3).
16 If the mobile station performs access handoffs and/or access probe handoffs, the mobile
17 station shall maintain the following variables:
18 • CURRENT_ACTIVE_PILOTs
19 • PREVIOUS_ACTIVE_PILOTs
20 • FIRST_ACTIVE_PILOTs
21 Upon entering the System Access State the mobile station shall set
22 CURRENT_ACTIVE_PILOTs, PREVIOUS_ACTIVE_PILOTs and FIRST_ACTIVE_PILOTs to
23 NULL. Prior to starting an access attempt, the mobile station shall set
24 CURRENT_ACTIVE_PILOTs and PREVIOUS_ACTIVE_PILOTs to NULL. When the mobile
25 station selects a base station for transmission of an access probe, the mobile station shall
26 proceed as follows:
27 • If CURRENT_ACTIVE_PILOTs is not the same as the pilot of the selected base
28 station, the mobile station shall set PREVIOUS_ACTIVE_PILOTs to the value of
29 CURRENT_ACTIVE_PILOTs.
30 • The mobile station shall set CURRENT_ACTIVE_PILOTs to the identity of the pilot
31 corresponding to the selected base station.
32 • If FIRST_ACTIVE_PILOTs is NULL, the mobile station shall set
33 FIRST_ACTIVE_PILOTs to the value of CURRENT_ACTIVE_PILOTs.
34 Before the mobile station transmits an access probe to a new base station on the Access
35 Channel, the mobile station shall update parameters based on the System Parameters
36 Message, the Access Parameters Message and the Extended System Parameters Message on
37 the associated new Paging Channel and process parameters from the messages (see
38 2.6.2.2.1, 2.6.2.2.2, and 2.6.2.2.5).
2-158
3GPP2 C.S0005-A v6.0
1 Before the mobile station transmits an access probe to a new base station on the Enhanced
2 Access Channel, the mobile station shall update parameters based on the ANSI-41 System
3 Parameters Message, the Enhanced Access Parameters Message, and the MC-RR System
4 Parameters Message on the associated new Primary Broadcast Control Channel and process
5 parameters from the messages (see 2.6.2.2.13, 2.6.2.2.14, and 2.6.2.2.15).
6 If the mobile station monitors the Paging Channel, the mobile station shall update
7 parameters based on the Neighbor List Message, the Extended Neighbor List Message, or the
8 General Neighbor List Message on the associated new Paging Channel and process
9 parameters from the message (see 2.6.2.2.3, 2.6.2.2.7, and 2.6.2.2.8).
10 If the mobile station monitors the Forward Common Control Channel/ Primary Broadcast
11 Control Channel, the mobile station shall update parameters based on the Universal
12 Neighbor List Message on the associated new Primary Broadcast Control Channel and
13 process parameters from the message (see 2.6.2.2.17).
14 If the mobile station receives the User Zone Identification Message or the Private Neighbor
15 List Message, the mobile station shall update parameters based on these messages on the
16 associated new Paging Channel or Primary Broadcast Control Channel and process
17 parameters from the messages (see 2.6.2.2.9 and 2.6.2.2.10). If the mobile station receives
18 a Global Service Redirection Message (see 2.6.2.2.6) which directs the mobile station away
19 from the new base station, the mobile station shall not access the new base station. If the
20 mobile station receives an Extended Global Service Redirection Message (see 2.6.2.2.11)
21 which directs the mobile station away from the new base station, the mobile station shall
22 not access the new base station. The mobile station shall process these messages only once
23 after each access handoff.
24 2.6.3.1.3.1 Pilot Search
25 The following sets of pilot offsets are defined for a mobile station in the System Access State.
26 Each pilot offset is a member of only one set.
27 • Active Set: The pilot offset of the Forward CDMA Channel whose Paging Channel or
28 Forward Common Control Channel/ Primary Broadcast Control Channel is being
29 monitored.
30 • Neighbor Set: The pilots that are not currently in the Active Set and are likely
31 candidates for access handoff or access probe handoff. The members of the
32 Neighbor Set are specified in the Neighbor List Message, the Extended Neighbor List
33 Message, and the General Neighbor List Message on the Paging Channel. The
34 members of the Neighbor Set are specified in the Universal Neighbor List Message on
35 the Primary Broadcast Control Channel.
36 • Remaining Set: The set of all possible pilot offsets in the current system (integer
37 multiples of PILOT_INCs) on the current CDMA Frequency Assignment, excluding
38 the pilots in the Neighbor Set and the Active Set.
39 2.6.3.1.3.2 Access Handoff
40 The mobile station is permitted to perform an access handoff to use the Paging Channel
41 with the best pilot strength and an associated Access Channel. The mobile station is
2-159
3GPP2 C.S0005-A v6.0
1 permitted to perform an access handoff to use the Forward Common Control Channel with
2 the best pilot strength and an associated Enhanced Access Channel. The mobile station is
3 permitted to perform an access handoff when waiting for a response from the base station
4 or before sending a response to the base station. An access handoff is permitted after an
5 access attempt while the mobile station is in the Page Response Substate or the Mobile
6 Station Origination Attempt Substate.
7 When the mobile station declares a loss of the Paging Channel or the Forward Common
8 Control Channel while waiting for a response from the base station in the Page Response
9 Substate or in the Mobile Station Origination Attempt Substate, the mobile station shall
10 perform an access handoff, if all of the following conditions hold:
11 • The pilot corresponding to the new base station is in the list ACCESS_HO_LIST,
12 • ACCESS_HOs is equal to ‘1’, and
13 • The mobile station is not already in the process of performing an access attempt.
14 When the mobile station declares a loss of the Paging Channel or the Forward Common
15 Control Channel, after receiving a message but before responding to that message while in
16 the Page Response Substate or in the Mobile Station Origination Attempt Substate, the mobile
17 station shall perform an access handoff if the following conditions hold:
19 • ACCESS_HOs is equal to ‘1’,
20 • ACCESS_HO_MSG_RSPs is equal to ‘1’, and
22 When the mobile station declares an insufficiency of the Paging Channel3 or the Forward
23 Common Control Channel, while waiting for a response from the base station in the Page
24 Response Substate or in the Mobile Station Origination Attempt Substate, the mobile station
25 may perform an access handoff if all of the following conditions hold:
27 • ACCESS_HOs is equal to ‘1’, and
29 When the mobile station declares an insufficiency of the Paging Channel4 or the Forward
30 Common Control Channel, after receiving a message but before responding to that message
31 while in the Page Response Substate or in the Mobile Station Origination Attempt Substate,
32 the mobile station may perform an access handoff if all of the following conditions hold:
3 Insufficiency of the Paging Channel and the Forward Common Control Channel is implementor-
defined.
defined.
2-160
3GPP2 C.S0005-A v6.0
2 • ACCESS_HOs is equal to ‘1’,
3 • ACCESS_HO_MSG_RSPs is equal to ‘1’, and
5 If ACCESS_PROBE_HOs is equal to ‘0’ and ACCESS_HOs is equal to ‘1’, and the mobile
6 station declares a loss of the Paging Channel or the Forward Common Control Channel
7 during an access attempt, after sending at least one complete access probe, the mobile
8 station may monitor other Paging Channels or the Forward Common Control Channels
9 which are in ACCESS_HO_LIST for T42m seconds after the loss of the Paging Channel or
10 the Forward Common Control Channel on which the access attempt was made5.
11 2.6.3.1.3.3 Access Probe Handoff
12 The mobile station is permitted to perform an access probe handoff when the mobile station
13 is in the Page Response Substate or the Mobile Station Origination Attempt Substate.
14 The mobile station may perform an access probe handoff during an access attempt to a
15 pilot in ACCESS_HO_LIST when the message being sent is the Origination Message or the
16 Page Response Message, if all of the following conditions hold:
17 • ACCESS_PROBE_HOs is equal to ‘1’,
18 • The mobile station is in the Page Response Substate or the Mobile Station Origination
19 Attempt Substate, and
20 • The mobile station has performed fewer than (MAX_NUM_PROBE_HOs +1) access
21 probe handoffs during the current access attempt.
22 The mobile station may also perform an access probe handoff during an access attempt to a
23 pilot in ACCESS_HO_LIST when the message being sent is a message other than the
24 Origination Message or the Page Response Message, if all of the preceding conditions hold
25 and ACC_PROBE_HO_OTHER_MSGs is equal to ‘1’.
27 pilot not in ACCESS_HO_LIST when the message being sent is the Origination Message or
28 the Page Response Message, if all of the following conditions hold:
29 • ACC_HO_LIST_UPDs is equal to ‘1’,
30 • ACCESS_PROBE_HOs is equal to ‘1’,
31 • The new pilot is stronger than any pilot in ACCESS_HO_LIST,
32 • The new pilot has the corresponding ACCESS_HO_ALLOWED field in the

33 NGHBR_REC equal to ‘1’,
5 The mobile station would be waiting for a response to the message transmitted in the access probe.
2-161
3GPP2 C.S0005-A v6.0
1 • Inclusion of the new pilot in ACCESS_HO_LIST does not cause the Access Channel
2 or Enhanced Access Channel message to exceed the maximum capsule size,
3 • Inclusion of the new pilot in ACCESS_HO_LIST does not cause the number of
4 members to exceed N13m,
5 • The mobile station is in the Page Response Substate or the Mobile Station Origination
6 Attempt Substate, and
7 • The mobile station has performed fewer than (MAX_NUM_PROBE_HOs +1) access
8 probe handoffs during the current access attempt.
10 pilot not in ACCESS_HO_LIST when the message being sent is a message other than the
11 Origination Message or the Page Response Message, if all of the preceding conditions hold
12 and ACC_PROBE_HO_OTHER_MSGs is equal to ‘1’.
13 If the above conditions are met, the mobile station may perform an access probe handoff
14 when the mobile station declares a loss of the Paging Channel or Forward Common Control
15 Channel (see 2.6.2.1.1.4 2.6.3.1.8); the mobile station may also perform an access probe
16 handoff after getting an indication that the TA timer expired (see 2.1.1.2.2 of [4]) and the
17 mobile station declares an insufficiency of the Paging Channel6 or the Forward Common
18 Control Channel.
19 If the mobile station performs an access probe handoff, the mobile station shall suspend
20 the access attempt on the old pilot and shall restart the access attempt on the new pilot (i.e.
21 starting with the first probe of the first probe sequence of the access sub-attempt), as
22 specified in 2.1.1.2.2 of [4]. The mobile station shall record the identity of the pilots to
23 which access probes have been transmitted within the current access attempt.
24 The mobile station shall not reset its access probe handoff count until the access attempt
25 ends.
26 Layer 3 shall send an L2-Supervision.Request primitive to Layer 2 to cancel the access

27 attempt if the length of the message to be sent exceeds MAX_CAP_SIZE of the new base
28 station. The mobile station may monitor other Paging Channels or Forward Common
29 Control Channels which are in ACCESS_HO_LIST for T42m seconds after aborting the
30 access attempt7.
31 2.6.3.1.4 System Access State Exit Procedures

32 Upon exiting the System Access State, the mobile station shall direct Layer 2 to cancel (see
33 2.1.1.2.2 of [4]) any access attempt in progress and discard the associated message. The
34 mobile station shall then disable the System Access State timer.
defined.
7 The mobile station would be waiting for a response to the message transmitted in the access probe.
2-162
3GPP2 C.S0005-A v6.0
1 2.6.3.1.5 Reserved
2 2.6.3.1.6 Full-TMSI Timer
3 Whenever the mobile station sends its full TMSI, the mobile station enables a timer, called
4 the full-TMSI timer. If the full-TMSI timer expires, the mobile station deletes the TMSI by
5 setting all of the bits in the TMSI_CODEs-p field to ‘1’.
6 The mobile station shall maintain the full-TMSI timer. The mobile station shall provide a
7 means for enabling or disabling the full-TMSI timer.
8 If the mobile station sends a message with an address including the

9 ASSIGNING_TMSI_ZONEs-p and the full-TMSI timer is disabled, the mobile station shall
10 enable the full-TMSI timer with a duration equal to T69m + 2.56 × 2i seconds where i is
11 equal to SLOT_CYCLE_INDEXs.
12 2.6.3.1.7 Monitoring Pilots
13 The mobile station assists the base station in the Traffic Channel assignment process by
14 monitoring and reporting (see 2.1.1.4.1.2 of [4]) the pilot strength of the pilot in the mobile
15 station’s Paging Channel or Forward Common Control Channel Active Set (see 2.6.3.1.3.1).
16 The mobile station can also monitor and report (see 2.1.1.4.1.2 of [4]) other pilots on the
17 same frequency; in such cases, the mobile station shall create ACCESS_HO_LIST and
18 OTHER_REPORTED_LIST and shall monitor the pilots on those lists, if any.
19 For each monitored pilot, the mobile station shall record the pilot PN phase and the pilot
20 strength PS, using the most recent measurements from the searcher element (see 2.2.2.1 of
21 [2]), as they become available. The mobile station shall identify each pilot through its pilot
22 PN phase (the phase of the pilot PN sequence, in units of one chip, relative to the zero offset
23 pilot PN sequence of the pilot (see 2.6.6.2.4)). The mobile station shall determine the pilot
24 strength, PS, as specified in 2.6.6.2.2.
25 2.6.3.1.7.1 Generation of the Initial Access Handoff List
26 ACCESS_HO_LIST is created immediately before transmitting the first access probe after
27 entering the System Access State. When it is created, ACCESS_HO_LIST is defined as a set
28 of at most N13m pilots, having the greatest pilot strength in comparison with other
29 qualifying pilots and for which all of the following apply:
30 • The strength of each member exceeds T_ADD.
31 • Each member, other than the Active Set pilot, has the corresponding
32 ACCESS_HO_ALLOWED field in the NGHBR_REC equal to ‘1’.
33 • The Active Set pilot that the mobile station monitors when the mobile station enters
34 the System Access State is a member.
35 • All members can be contained in the Access Channel or Enhanced Access Channel
36 message without exceeding the maximum capsule size.
2-163
3GPP2 C.S0005-A v6.0
1 2.6.3.1.7.2 Update of the Access Handoff List
2 When the mobile station performs an access probe handoff to a pilot which was not
3 previously included in ACCESS_HO_LIST (see 2.6.3.1.3.3), it adds the pilot to
4 ACCESS_HO_LIST.
5 If ACC_HO_LIST_UPDs is equal to ‘1’, the mobile station can update ACCESS_HO_LIST, as
6 follows:
7 • The mobile station can add one or more new pilots other than the Active Set pilot to
8 ACCESS_HO_LIST before transmitting an access probe.
9 • The mobile station can also drop from ACCESS_HO_LIST pilots to which access
10 probes have not been transmitted since entering the System Access State and whose
11 strength have fallen below T_ADD.
12 When it is updated before transmitting a subsequent access probe, ACCESS_HO_LIST is

13 defined as a set of at most N13m pilots, having the greatest pilot strength in comparison
14 with other qualifying pilots and for which all of the following apply:
15 • The strength of each member to which access probes have not been transmitted
16 exceeds T_ADD.
17 • Each member other than the pilot to which the first access probe in the System
18 Access State was transmitted has the corresponding ACCESS_HO_ALLOWED field
19 in the NGHBR_REC equal to ‘1’.
20 • The Active Set pilot to which the next access probe is to be transmitted is a member.
21 • All pilots to which access probes have been transmitted since entering the System
22 Access State are members.
25 2.6.3.1.7.3 Generation of the Other Reported List
26 OTHER_REPORTED_LIST (specified by NUM_ADD_PILOTS and NUM_AUX_PILOTS, see

27 2.1.1.4.1.5.1 of [4]) is defined as a set of no more than N13m minus the number of pilots in
28 ACCESS_HO_LIST pilots, having the greatest pilot strength in comparison with other
29 qualifying pilots and for which all of the following apply:
30 • The strength of each me4mber exceeds T_ADD.
31 • No member is included in ACCESS_HO_LIST.
34 2.6.3.1.7.4 Update of OTHER_REPORTED_LIST
35 Before transmitting each access probe, the mobile station shall generate
36 OTHER_REPORTED_LIST according to section 2.6.3.1.7.3, using the most recent pilot
37 strength information available from its searcher element (see 2.2.2.1 of [2]). If the mobile
2-164
3GPP2 C.S0005-A v6.0
1 station updates ACCESS_HO_LIST before transmitting an access probe, it shall update

2 OTHER_REPORTED_LIST after updating ACCESS_HO_LIST.
3 2.6.3.1.8 Paging Channel and Forward Common Control Channel/ Primary Broadcast
4 Control Channel Monitoring
5 When in the System Access State, the mobile station shall monitor the Paging Channel or
6 the Forward Common Control Channel/ Primary Broadcast Control Channel at all times.
7 The mobile station shall set a timer for T72m seconds, when it begins to monitor the Paging
8 Channel or the Forward Common Control Channel/ Primary Broadcast Control Channel
9 and whenever it gets an indication that a valid message was received on the Paging Channel
10 or the Forward Common Control Channel/ Primary Broadcast Control Channel, whether
11 addressed to the mobile station or not (see 2.1.2.3.2 of [4]).
12 If the T72m timer expires:
13 • The mobile station shall first finish transmitting the access probe in progress, if any.
14 • The mobile station shall declare a loss of the Paging Channel or the Forward
15 Common Control Channel/ Primary Broadcast Control Channel if:
16 – ACCESS_HOs is equal to ‘1’ and ACCESS_HO_LIST contains more than one
17 pilot,
18 – ACC_HO_LIST_UPDs is equal to ‘1’, and Access Probe Handoff is supported by
19 the mobile station, or
20 – ACC_HO_LIST_UPDs is equal to ‘0’ and the following conditions are met:
21 + ACCESS_HO_LIST contains more than one pilot, and
22 + Access Probe Handoff is supported by the mobile station and is enabled by

23 the base station.
24 • If by declaring a loss of the Paging Channel or the Forward Common Control

25 Channel, the eligibility requirements for performing access handoff are met (see
26 2.6.3.1.3.2), then Tthe mobile station shall declare a loss of the Paging Channel or
27 the Forward Common Control Channel, and perform an access handoff if the
28 requirements in 2.6.3.1.3.2 are met. If by declaring a loss of the Paging Channel or
29 the Forward Common Control Channel, the eligibility requirements for performing
30 access probe handoff are met (see 2.6.3.1.3.3), then Tthe mobile station may
31 declare a loss of the Paging Channel or the Forward Common Control Channel, and
32 perform an access probe handoff if the requirements in 2.6.3.1.3.3 are met. If the
33 mobile station performs an access handoff or an access probe handoff, the mobile
34 station restarts the Paging Channel or the Forward Common Control Channel/
35 Primary Broadcast Control Channel monitoring procedure for the new base station.
2-165
3GPP2 C.S0005-A v6.0
1 • If an access attempt was in progress when the timer expired and that access
2 attempt had already been suspended and resumed previously (see below), the mobile
3 station shall declare a loss of the Paging Channel8 or the Forward Common Control
4 Channel and shall disable its transmitter.
5 • If an access attempt was in progress when the timer expired and that access
6 attempt had not been suspended and resumed before and the mobile station does
7 not perform access probe handoff, the mobile station shall declare a temporary
8 consider the loss of the Paging Channel or the Forward Common Control Channel as
9 temporary, shall direct Layer 2 to suspend the access attempt (see 2.1.1.2.2 of [4]),
10 and shall perform the following:
11 – The mobile station shall set the timer to (T40m-T72m) seconds.
12 – If the mobile station receives an indication that a valid message on the Paging
13 Channel or the Forward Common Control Channel, whether addressed to the
14 mobile station or not, was received (see 2.1.2.3.2 of [4]) prior to the expiration of
15 the (T40m-T72m) timer, the mobile station shall re-enable the transmitter, shall
16 direct Layer 2 to resume operation from the beginning of the interrupted access
17 probe sequence of the access sub-attempt (see 2.1.1.2.2 of [4]), and shall
18 transmit the first probe of the new access probe sequence immediately after re-
19 enabling the transmitter.
20 – – If the (T40m-T72m) timer expires, the mobile station shall direct Layer 2 to
21 cancel any access attempt (see 2.1.1.2.2 of [4]) and shall declare a loss of the
22 Paging Channel or the Forward Common Control Channel/ Primary Broadcast
23 Control Channel.
24 • If an access attempt was not in progress when the timer expired and the mobile
25 station does not perform access handoff, the mobile station shall perform the
26 following:
27 – The mobile station shall set the timer to (T40m-T72m) seconds.
28 – If the (T40m-T72m) timer expires, the mobile station shall declare a loss of the
29 Paging Channel or the Forward Common Control Channel/ Primary Broadcast
30 Control Channel.
31 2.6.3.2 Update Overhead Information Substate
32 In this substate, if the base station supports the Primary Broadcast Control Channel for
33 Spreading Rate 1, or if both the mobile station and base station support Spreading Rate 3
34 on the common channels, then the mobile station shall monitor the Primary Broadcast
35 Control Channel until it has received the current configuration messages; otherwise, the
36 mobile station shall monitor the Paging Channel until it has received the current
8 Requirements for processing the loss of Paging Channel are given separately for each substate of
the System Access State, in the sections describing the substates.
2-166
3GPP2 C.S0005-A v6.0
1 configuration messages. The mobile station compares sequence numbers to determine

2 whether all of the configuration messages are up-to-date. To make sure it has the latest
3 access parameters, the mobile station receives at least one message containing the
4 ACC_MSG_SEQ field (except in case of a page response, since the initiating page contains
5 ACC_MSG_SEQ), and waits, if necessary, for an Access Parameters Message or an Enhanced
6 Access Parameters Message. In addition, if the mobile station is monitoring the Primary
7 Broadcast Control Channel and SENDING_RANDs is equal to ‘1’, then it shall also wait for
8 an ANSI-41 RAND Message.
9 Upon entering the Update Overhead Information Substate, the mobile station shall set the
10 System Access State timer to a value of T41m seconds. The mobile station shall set PAGED
11 to NO.
12 If the System Access State timer expires while in this substate, the mobile station shall
15 If the mobile station declares a loss of the Paging Channel or the Primary Broadcast Control
16 Channel (see 2.6.2.1.1.4 2.6.3.1.8), the mobile station shall perform the following:
20 • The mobile station shall declare an access attempt failure and update its
21 registration variables as specified in 2.6.5.5.3.2.
22 • The mobile station shall enter the Mobile Station Idle State.
23 If PACAs is equal to enabled, the mobile station shall set PACA_CANCEL to ‘1’ when the
24 user directs the mobile station to cancel a PACA call.
25 If the mobile station receives any of the following messages, it shall process the message as
26 follows:
27 1. System Parameters Message: The mobile station shall process the parameters from
28 the message (see 2.6.2.2.1).
29 2. Access Parameters Message: The mobile station shall process the parameters from
31 3. Neighbor List Message: The mobile station shall process the parameters from the
32 message (see 2.6.2.2.3).
33 4. CDMA Channel List Message: The mobile station shall process the parameters from
35 5. Extended System Parameters Message: The mobile station shall process the
36 parameters from the message (see 2.6.2.2.5).
37 6. Global Service Redirection Message: The mobile station shall process the
2-167
3GPP2 C.S0005-A v6.0
1 7. Extended Neighbor List Message: The mobile station shall process the parameters
2 from the message (see 2.6.2.2.7).
3 8. General Neighbor List Message: The mobile station shall process the parameters
5 9. Lock Until Power-Cycled Order: The mobile station shall record the reason for the
6 Lock Until Power-Cycled Order in the mobile station’s semi-permanent memory
7 (LCKRSN_Ps-p equals the least-significant four bits of ORDQr). The mobile station
8 should notify the user of the locked condition. The mobile station shall then enter
10 lock indication (see 2.6.1.1), and shall not enter the System Access State again until
11 after the next mobile station power-up or until it has received an Unlock Order.
12 This requirement shall take precedence over any other mobile station requirement
13 specifying entry to the System Access State.
14 10. General Page Message or Universal Page Message: If CURR_ACC_MSG_SEQ is equal

15 to NULL, the mobile station shall set CURR_ACC_MSG_SEQ to ACC_MSG_SEQr.
16 The mobile station shall compare CONFIG_MSG_SEQs to CONFIG_MSG_SEQr. If
17 the comparison results in a mismatch, the mobile station shall set
18 CONFIG_MSG_SEQs to CONFIG_MSG_SEQr. The mobile station may ignore the
19 rest of the message. If this substate was not entered with an origination or page
20 response indication, the mobile station may also determine whether there is a page
21 match. If the mobile station attempts to determine whether there is a page match,
22 it shall use the procedure as defined in 2.6.2.3. If a match is declared, the mobile
23 station shall set PAGED to YES.
24 11. User Zone Identification Message: The mobile station shall process the parameters
26 12. Private Neighbor List Message: The mobile station shall process the parameters from
28 13. Extended Global Service Redirection Message: The mobile station shall process the
30 14. Extended CDMA Channel List Message: The mobile station shall process the
32 15. ANSI-41 System Parameters Message: The mobile station shall process the
34 16. MC-RR Parameters Message: The mobile station shall process the parameters from
36 17. Enhanced Access Parameters Message: The mobile station shall process the
38 18. ANSI-41 RAND Message: The mobile station shall process the parameters from the
39 message (see 2.6.2.2.16).
40 19. Universal Neighbor List Message: The mobile station shall process the parameters
2-168
3GPP2 C.S0005-A v6.0
1 If the mobile station receives a message which is not included in the above list, the mobile
2 station shall ignore the message.
3 When all of the following conditions are met:
4 • the stored configuration parameters are current (see 2.6.2.2)

5 • CURR_ACC_MSG_SEQs and ACC_MSG_SEQs are equal and are not NULL, and
6 • if the mobile station is monitoring the Primary Broadcast Control Channel and
7 SENDING_RANDs is equal to ‘1’, the ANSI-41 RAND Message has been received,
8 then the mobile station shall disable the System Access State timer and shall do one of
9 the following:
10 • If PAGED is equal to YES, the mobile station shall determine whether the message
11 resulting in the page match was received on the current Paging Channel or Forward
12 Common Control Channel. If the message was received on the current Paging
13 Channel or Forward Common Control Channel, the mobile station shall enter the
14 Page Response Substate; otherwise, the mobile station shall enter the Mobile Station
15 Idle State.
16 • If this substate was entered with a page response indication and the mobile station
17 has not performed an access entry handoff, the mobile station shall determine
18 whether the message resulting in the page match was received on the current
19 Paging Channel or Forward Common Control Channel. If the message was received
20 on the current Paging Channel or Forward Common Control Channel, the mobile
21 station shall enter the Page Response Substate; otherwise, the mobile station shall
22 enter the Mobile Station Idle State.
23 • If this substate was entered with a page response indication and the mobile station
24 has performed an access entry handoff, the mobile station shall enter the Page
25 Response Substate.
26 • If this substate was entered with a page response retransmission indication, the
27 mobile station shall enter the Page Response Substate.
28 • If this substate was entered with an origination indication, the mobile station shall
29 enter the Mobile Station Origination Attempt Substate with an origination indication.
30 • If this substate was entered with a PACA response indication, the mobile station
31 shall enter the Mobile Station Origination Attempt Substate with a PACA response
32 indication.
33 • If this substate was entered with an order/message response indication and the
34 mobile station has not performed an access entry handoff, the mobile station shall
35 determine whether the message resulting in the response was received on the
36 current Paging Channel or Forward Common Control Channel. If the message was
37 received on the current Paging Channel or Forward Common Control Channel, the
38 mobile station shall enter the Mobile Station Order/Message Response Substate;
39 otherwise, the mobile station shall discard the response and enter the Mobile Station
40 Idle State.
2-169
3GPP2 C.S0005-A v6.0
1 • If this substate was entered with an order/message response indication and the
2 mobile station has performed an access entry handoff, the mobile station shall enter
3 the Mobile Station Order/Message Response Substate.
4 • If this substate was entered with a registration indication, the mobile station shall
5 enter the Registration Access Substate.
6 • If this substate was entered with a message transmission indication, the mobile
7 station shall enter the Mobile Station Message Transmission Substate with a message
8 transmission indication.
9 • If this substate was entered with a hook status indication, the mobile station shall
10 enter the Mobile Station Message Transmission Substate with a hook status
11 indication.
12 • If this substate was entered with a PACA cancel indication, the mobile station shall
13 enter the PACA Cancel Substate.
14 2.6.3.3 Page Response Substate
15 In this substate, the mobile station sends a Page Response Message in response to a
16 mobile-station-addressed page from a base station. If a base station responds to the Page
17 Response Message with an authentication request, the mobile station responds in this
18 substate.
19 If a message received from the base station requires a Layer 2 acknowledgment and does
20 not require a Layer 3 response, Layer 3 shall indicate to Layer 2 that no response is
21 outstanding (see 2.1.1.2.2.1 of [4]).
22 If a message received from the base station requires a Layer 2 acknowledgment and also a
23 Layer 3 response, Layer 3 shall indicate to Layer 2 that a response is outstanding (see
24 2.1.1.2.2.1 of [4]).
25 When transmitting a response to a message received from the base station, Layer 3 shall
26 indicate to Layer 2 that the type of the message is a response (see 2.1.1.2.2.1 of [4]).
27 When transmitting an autonomous message (i.e., a message that is not sent as a response
28 to a message received from the base station), Layer 3 shall indicate to Layer 2 that the type
29 of the message is a request other than a registration request or a message transmission
30 request (see 2.1.1.2.2.1 of [4]).
31 If the mobile station has a stored service configuration (that is, parameters conveyed by
32 both the Service Configuration information record and the Non-negotiable Service
33 Configuration information record), SYNC_IDs is not equal to NULL, and USE_SYNC_IDs is
34 equal to ‘1’, the mobile station may include the SYNC_ID field in the Page Response
35 Message and, if included, shall set it to the 16-bit CRC computed over the entire stored
36 service configuration as specified in 2.6.11 SYNC_IDs corresponding to the stored service
37 configuration.
38 Upon entering the Page Response Substate, the mobile station shall set RLGAIN_ADJs to
39 ‘0000’ and send a Page Response Message.
2-170
3GPP2 C.S0005-A v6.0
1 While in this substate, the mobile station shall monitor the Paging Channel or the Forward
2 Common Control Channel. The mobile station may perform an access probe handoff or
3 access handoff as described in 2.6.3.1.3.2 and 2.6.3.1.3.3. If the mobile station declares a
4 loss of the Paging Channel or the Forward Common Control Channel (see 2.6.2.1.1.4
5 2.6.3.1.8) during an access attempt, the mobile station may perform an access probe
6 handoff; otherwise, it shall declare an access attempt failure and shall perform the following
7 actions:
8 • The mobile station shall update its registration variables as specified in 2.6.5.5.3.2,
9 • If the mobile station is monitoring the Paging Channel, the mobile station shall set
10 SYS_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL,
11 • If the mobile station is monitoring the Forward Common Control Channel, the
12 mobile station shall set MC_RR_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL.
16 • The mobile station shall disable its transmitter, and
18 If the mobile station receives confirmation of delivery of any message sent by the mobile
19 station in this substate, the mobile station shall perform an access handoff if all of the
20 following conditions hold:
21 • The mobile station declares a loss of the Paging Channel or the Forward Common
22 Control Channel, and
23 • The mobile station is permitted to perform an access handoff (see 2.6.3.1.3.2), and
24 there are pilots other than the active pilot in the access handoff list (see 2.6.3.1.3.2).
26 Channel and does not perform an access handoff, the mobile station shall perform the
27 following:
29 SYS_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL.
33 PACA_CANCEL to 0, shall disable the PACA state timer, and should indicate to the
34 user that the PACA call has been canceled,
35 • The mobile station shall disable its transmitter, and
2-171
3GPP2 C.S0005-A v6.0
1 If the mobile station receives confirmation of delivery of the Page Response Message sent in
2 this substate, the mobile station shall update its registration variables with respect to the
3 base station to which the first access probe was transmitted after entering the System
4 Access State, as specified in 2.6.5.5.3.1.
11 SYS_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL, and shall enter the Mobile
12 Station Idle State.
14 mobile station shall set MC_RR_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL and
16 The mobile station shall set and disable the System Access State timer as follows:
17 • The mobile station shall disable the timer whenever it begins an access attempt.
18 • The mobile station shall set the timer to T42m seconds whenever it ends an access
19 attempt.
20 • The mobile station shall disable the timer whenever it exits the System Access State.
21 If the mobile station receives a Channel Assignment Message or the Extended Channel
22 Assignment Message, Layer 3 shall send a dedicated channel assignment indication to Layer
23 2 (see 2.1.2.1.2 of [4]). If the mobile station has not received confirmation of delivery of the
24 Page Response Message, before receiving the Channel Assignment Message or the Extended
25 Channel Assignment Message, the mobile station shall update its registration variables with
26 respect to the base station to which the first access probe was transmitted after entering
27 the System Access State, as specified in 2.6.5.5.3.1.
28 If the mobile station is to exit the System Access State as a result of processing Layer 3
29 fields of a message requiring an acknowledgment, the mobile station shall exit the System
30 Access State after Layer 3 receives an indication from Layer 2 that the acknowledgment to
31 the message has been sent and acknowledged.
32 If Layer 3 receives a message other than a Channel Assignment Message or an Extended

33 Channel Assignment Message with an indication from Layer 2 that an access attempt for a
34 message being transmitted was not terminated as a result of processing the Layer 2 fields of
35 the received message, the mobile station shall ignore the received message.
37 message or order is outside its permissible range, the mobile station may send a Mobile
39 1. Authentication Challenge Message: The mobile station shall respond to the message
40 as specified in 2.3.12.1.4, regardless of the value of AUTHs.
2-172
3GPP2 C.S0005-A v6.0
1 2. Base Station Challenge Confirmation Order: The mobile station shall respond to the
2 message as specified in 2.3.12.1.5.
9 with an encryption failure indication
11 follows:
13 actions:
14 − The mobile station shall set CH_INDs to ‘01’.
15 − The mobile station shall store the frame offset (FRAME_OFFSETs =

16 FRAME_OFFSETr), the message encryption mode indicator
17 (ENCRYPT_MODEs = ENCRYPT_MODEr), and, if FREQ_INCLr equals ‘1’, the
18 Frequency Assignment (CDMACHs = CDMA_FREQr).
19 − The mobile station shall perform the following procedures in the order listed
20 below:
21 + If D_SIG_ENCRYPT_MODEr is included, the mobile station shall perform
22 the following:
23 ο If D_SIG_ENCRYPT_MODEr is equal to ‘000’, the mobile station shall
24 set D_SIG_ENCRYPT_MODEs to C_SIG_ENCRYPT_MODEs; otherwise,
25 the mobile station shall set D_SIG_ENCRYPT_MODEs to
26 D_SIG_ENCRYPT_MODEr, ENC_KEYs to the most recently generated
27 CMEAKEY in the mobile station associated with the AUTHR of the
28 Page Response Message, and EXT_ENCRYPT_SEQ[0] and
29 EXT_ENCRYPT_SEQ[1] to 256 × ENC_SEQ_H (the ENC_SEQ_H field
30 in the Page Response Message).
31 + If USE_NEW_KEYr is not included, or is included and is set to ‘1’, the
32 mobile station shall use the session key generated at the most recent
33 registration for encryption of signaling and user information. The mobile
34 station shall store the session key in KEYs[KEY_SEQ_NEWs-p]. The
35 mobile station shall store KEY_SIZEr to KEY_SIZEs. The mobile station
36 shall then increment the variable KEY_SEQ_NEWs-p by one (modulo 16).
37 If ENC_KEY_SIZEr is included, the mobile station shall set
38 ENC_KEY_SIZEs to ENC_KEY_SIZEr.
39 − If USE_NEW_KEYr is included and is set to ‘0’ then the mobile station shall
40 use KEYs [KEY_SEQr] as the session key.
2-173
3GPP2 C.S0005-A v6.0
1 + If C_SIG_ENCRYPT_MODE is included, the mobile station shall set

2 C_SIG_ENCRYPT_MODEs to C_SIG_ENCRYPT_MODEr.
3 − The mobile station shall set SERV_NEGs to disabled.
4 − If PACAs is equal to enabled, the mobile station shall set PACAs to disabled
5 and PACA_CANCEL to ‘0’, shall disable the PACA state timer, and should
7 − The mobile station shall initialize CODE_CHAN_LIST as described in 2.6.8.
8 − The mobile station shall enter the Traffic Channel Initialization Substate of
9 the Mobile Station Control on the Traffic Channel State.
11 actions:
12 − If FREQ_INCLr equals ‘1’, the mobile station shall perform the following:
13 + If the message requires acknowledgement, the mobile station shall wait

14 until Layer 3 receives an indication from Layer 2 that the
15 acknowledgement to the message has been sent and acknowledged.
16 + The mobile station shall set CDMACHs to CDMA_FREQr, tune to the new
17 Frequency Assignment, and measure the strength of each pilot listed in
18 the assignment using the Neighbor Set search procedures specified in
19 2.6.6.2.1 and 2.6.6.2.2.
20 − The mobile station shall set CONFIG_MSG_SEQs and ACC_MSG_SEQs to
23 − If the mobile station has not stored configuration parameters for the Primary
28 PRI_NGHBR_LST_MSG_SEQs, CHAN_LST_MSG_SEQs,
31 to NULL.
32 − The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the Primary
33 Paging Channel. If the mobile station was monitoring Forward Common
34 Control Channel, the mobile station shall set the PRATs to ‘00’. The mobile
35 station shall then begin monitoring the Primary Paging Channel of the
36 selected base station.
37 − If RESPONDr is equal to ‘1’, the mobile station shall enter the Update
38 Overhead Information Substate with a page response retransmission
39 indication within T34m seconds after receiving the Channel Assignment
40 Message.
2-174
3GPP2 C.S0005-A v6.0
1 − If RESPONDr is equal to ‘0’, the mobile station shall enter the Mobile Station
2 Idle State within T34m seconds after receiving the Channel Assignment
3 Message.
5 actions:
6 − If the mobile station does not support analog operation in the requested
7 band class, the mobile station shall send a Mobile Station Reject Order with
8 ORDQ field set to ‘00000110’ (capability not supported by the mobile station)
9 and shall remain in the Page Response Substate.
10 − If the mobile station supports analog operation in the requested band class,
11 the mobile station shall perform the following actions:
12 + If USE_ANALOG_SYSr equals ‘1’, the mobile station shall set SERVSYSs
13 to SYS_A if ANALOG_SYSr is equal to ‘0’, or shall set SERVSYSs to SYS_B
14 if ANALOG_SYSr is equal to ‘1’.
15 + If PACAs is equal to enabled, the mobile station shall set PACAs to

16 disabled and PACA_CANCEL to ‘0’, shall disable the PACA state timer,
17 and should indicate to the user that the PACA call has been canceled.
18 + If RESPONDr equals ‘0’, the mobile station shall enter the analog
19 Initialization Task with a wait-for-page indication (see 2.6.1). If
20 RESPONDr equals ‘1’, the mobile station shall enter the analog
21 Initialization Task with a page response indication (see 2.6.1).
23 actions:
27 and remain in the Page Response Substate.
28 − If the mobile station supports analog operation in the requested band class:
29 + If PACAs is equal to enabled, the mobile station shall set PACAs to
32 + If the analog channel type is ‘00’, the mobile station shall store the
33 system identification (SIDs = SIDr), voice mobile station attenuation code
34 (VMACs = VMACr), voice channel number (ANALOG_CHANs =
35 ANALOG_CHANr), SAT color code (SCCs = SCCr), and message encryption
36 mode indicator (MEMs = MEMr), shall set DTXs to ‘00’ and shall enter the
37 Confirm Initial Voice Channel Task (see 2.6.4.2) with a page response
38 indication.
39 + If the analog channel type is not ‘00’:
2-175
3GPP2 C.S0005-A v6.0
1 ο If the mobile station supports narrow analog mode, the mobile station
2 shall store the system identification (SIDs = SIDr), voice mobile
3 station attenuation code (VMACs = VMACr), voice channel number
4 (ANALOG_CHANs = ANALOG_CHANr), message encryption mode
5 indicator (MEMs = MEMr), analog channel type (AN_CHAN_TYPEs =
6 AN_CHAN_TYPEr) and the digital SAT code (DSCCs = DSCC_MSBr × 4
7 + SCCr), shall set DTXs to ‘00’, and shall enter the Confirm Initial
8 Narrow Analog Voice Channel Task (see 2.6.5.2A of [22]) with a page
9 response indication.
10 ο If the mobile station does not support narrow analog mode, the
11 mobile station shall send a Mobile Station Reject Order with the ORDQ
12 field set to ‘00000110’ (capability not supported by the mobile station)
13 and the mobile station shall remain in the Page Response Substate of
14 the System Access State.
16 actions:
21 − If GRANTED_MODEr equals ‘00’, and the multiplex option and radio
22 configuration combination specified in the DEFAULT_CONFIG field is not
23 supported by the mobile station, the mobile station shall send a Mobile
24 Station Reject Order with ORDQ field set to ‘00000110’ (capability not
25 supported by the mobile station) and remain in the Page Response Substate.
26 − If FREQ_INCLr equals ‘0’, the mobile station shall perform the following
27 actions:
28 + The mobile station shall store the frame offset (FRAME_OFFSETs =
30 (ENCRYPT_MODEs = ENCRYPT_MODEr), the granted mode
31 (GRANTED_MODEs = GRANTED_MODEr), and default configuration
32 (DEFAULT_CONFIGs = DEFAULT_CONFIGr).
33 + The mobile station shall perform the following procedures in the order
34 listed below:
35 ο If D_SIG_ENCRYPT_MODEr is included, the mobile station shall
37 ◊ If D_SIG_ENCRYPT_MODEr is equal to ‘000’, the mobile station
38 shall set D_SIG_ENCRYPT_MODEs to C_SIG_ENCRYPT_MODEs;
39 otherwise, the mobile station shall set D_SIG_ENCRYPT_MODEs
40 to D_SIG_ENCRYPT_MODEr, ENC_KEYs to the most recently
41 generated CMEAKEY in the mobile station associated with AUTHR
2-176
3GPP2 C.S0005-A v6.0
1 of the Page Response Message, and EXT_ENCRYPT_SEQ[0] and

2 EXT_ENCRYPT_SEQ[1] to 256 × ENC_SEQ_H (the ENC_SEQ_H
3 field in the Page Response Message).
4 ο If USE_NEW_KEYr is not included, or is included and is set to ‘1’, the
6 registration for encryption of signaling and user information. The
7 mobile station shall store the session key in KEYs[KEY_SEQ_NEWs-
8 p]. The mobile station shall store KEY_SIZEr to KEY_SIZEs. The
9 mobile station shall then increment the variable KEY_SEQ_NEWs-p
10 by one (modulo 16). If ENC_KEY_SIZEr is included, the mobile station
11 shall set ENC_KEY_SIZEs to ENC_KEY_SIZEr.
12 + If USE_NEW_KEYr is included and is set to ‘0’ then the mobile station

13 shall use KEYs [KEY_SEQr] as the session key.
14 ο If C_SIG_ENCRYPT_MODE is included, the mobile station shall set

16 + The mobile station shall set SERV_NEGs to enabled.
17 + The mobile station shall initialize CODE_CHAN_LIST as described in

18 2.6.8 and shall then enter the Traffic Channel Initialization Substate of
21 actions:
22 + If the band class is not supported by the mobile station, the mobile
23 station shall send a Mobile Station Reject Order with ORDQ field set to
24 ‘00000110’ (capability not supported by the mobile station) and shall
25 remain in the Page Response Substate.
26 + If the band class is supported by the mobile station, the mobile station
28 ο The mobile station shall store the frame offset (FRAME_OFFSETs =
30 (ENCRYPT_MODEs = ENCRYPT_MODEr), the bypass indicator
31 (BYPASS_ALERT_ANSWERs = BYPASS_ALERT_ANSWERr), the
32 granted mode (GRANTED_MODEs = GRANTED_MODEr), the default
33 configuration (DEFAULT_CONFIGs = DEFAULT_CONFIGr), the band
34 class (CDMABANDs = BAND_CLASSr), and the Frequency Assignment
35 (CDMACHs = CDMA_FREQr).
36 ο The mobile station shall perform the following procedures in the order
37 listed below:
38 ◊ If D_SIG_ENCRYPT_MODEr is included, the mobile station shall
2-177
3GPP2 C.S0005-A v6.0
1 − If D_SIG_ENCRYPT_MODEr is equal to ‘000’, the mobile

2 station shall set D_SIG_ENCRYPT_MODEs to
3 C_SIG_ENCRYPT_MODEs; otherwise, the mobile station shall
4 set D_SIG_ENCRYPT_MODEs to D_SIG_ENCRYPT_MODEr,
5 ENC_KEYs to the most recently generated CMEAKEY in the
6 mobile station associated with AUTHR of the Page Response
7 Message, and EXT_ENCRYPT_SEQ[0] and
8 EXT_ENCRYPT_SEQ[1] to 256 × ENC_SEQ_H (the
9 ENC_SEQ_H field in the Page Response Message).
10 ◊ If USE_NEW_KEYr is not included, or is included and is set to ‘1’,
11 the mobile station shall use the session key generated at the most
12 recent registration for encryption of signaling and user
13 information. The mobile station shall store the session key in
14 KEYs[KEY_SEQ_NEWs-p]. The mobile station shall store
15 KEY_SIZEr to KEY_SIZEs. The mobile station shall then
16 increment the variable KEY_SEQ_NEWs-p by one (modulo 16).If
17 ENC_KEY_SIZEr is included, the mobile station shall set
19 ◊ If USE_NEW_KEYr is included and is set to ‘0’ then the mobile

20 station shall use KEYs [KEY_SEQr] as the session key.

23 ο The mobile station shall initialize CODE_CHAN_LIST as described in

24 2.6.8, and shall set SERV_NEGs to enabled.
25 ο The mobile station shall then tune to the new Frequency Assignment
26 and shall enter the Traffic Channel Initialization Substate of the Mobile
27 Station Control on the Traffic Channel State.
29 actions:
31 actions:

35 + The mobile station shall set CONFIG_MSG_SEQs and ACC_MSG_SEQs to
36 NULL (see 2.6.2.2) and shall set PILOT_PNs to the pilot PN sequence
37 offset of the strongest pilot in the list (PILOT_PNr).
2-178
3GPP2 C.S0005-A v6.0
1 + If the mobile station has not stored configuration parameters for the
2 Primary Paging Channel of the new base station, or if the stored
3 information is not current (see 2.6.2.2), the mobile station shall set
4 SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,
5 EXT_NGHBR_LST_MSG_SEQs, GEN_NGHBR_LIST_MSG_SEQs,
6 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LST_MSG_SEQs
8 EXT_SYS_PAR_MSG_SEQs, GLOB_SERV_REDIR_MSG_SEQs, and
10 + The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the
11 Primary Paging Channel. The mobile station shall then begin monitoring
13 + If RESPONDr is equal to ‘1’, the mobile station shall perform the
14 following:
15 ο Ιf the Channel Assignment Message does not require an

16 acknowledgment, the mobile station shall enter the Update Overhead
17 Information Substate with a page response retransmission indication
18 within T34m seconds after receiving the Channel Assignment
19 Message.
20 ο Ιf the Channel Assignment Message requires an acknowledgment, the

21 mobile station shall enter the Update Overhead Information Substate
22 with a page response retransmission indication within T34m seconds
23 after Layer 3 receives an indication from Layer 2 that the
24 acknowledgement to the Channel Assignment Message has been sent
25 and acknowledged.
27 following:
29 acknowledgment, the mobile station shall enter the Mobile Station Idle
30 State within T34m seconds after receiving the Channel Assignment
31 Message.

33 mobile station shall enter the Mobile Station Idle State within T34m
34 seconds after Layer 3 receives an indication from Layer 2 that the
38 actions:
41 ‘00000110’ (capability not supported by the mobile station) and shall
42 remain in the Page Response Substate.
2-179
3GPP2 C.S0005-A v6.0
3 ο If the message requires acknowledgement, the mobile station shall

4 wait until Layer 3 receives an indication from Layer 2 that the
6 ο The mobile station shall set CDMACHs to CDMA_FREQr and
7 CDMABANDs to BAND_CLASSr. Then the mobile station shall tune
8 to the new Frequency Assignment, measure the strength of each pilot
9 listed in the assignment using the Neighbor Set search procedures
10 specified in 2.6.6.2.1 and 2.6.6.2.2, set PILOT_PNs to the pilot PN
11 sequence offset of the strongest pilot in the list (PILOT_PNr), and set
12 CONFIG_MSG_SEQs and ACC_MSG_SEQs to NULL (see 2.6.2.2).
13 ο If the mobile station has not stored configuration parameters for the
17 EXT_NGHBR_LST_MSG_SEQs, GEN_NGHBR_LIST_MSG_SEQs,
22 ο The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the
23 Primary Paging Channel. The mobile station shall then begin
24 monitoring the Primary Paging Channel of the selected base station.
25 ο If RESPONDr is equal to ‘1’, the mobile station shall perform the
26 following:
27 ◊ If the Channel Assignment Message does not require an

28 acknowledgment, the mobile station shall enter the Update
29 Overhead Information Substate with a page response
30 retransmission indication within T34m seconds after receiving the
31 Channel Assignment Message.
32 ◊ Ιf the Channel Assignment Message requires an acknowledgment,

33 the mobile station shall enter the Update Overhead Information
34 Substate with a page response retransmission indication within
35 T34m seconds after Layer 3 receives an indication from Layer 2
36 that the acknowledgement to the Channel Assignment Message
37 has been sent and acknowledged.
38 ο If RESPONDr is equal to ‘0’, the mobile station perform the following:
39 ◊ Ιf the Channel Assignment Message does not require an

40 acknowledgment, the mobile station shall enter the Mobile Station
41 Idle State within T34m seconds after receiving the Channel
42 Assignment Message .
2-180
3GPP2 C.S0005-A v6.0

2 the mobile station shall enter the Mobile Station Idle State within
10 actions:
16 configuration specified in the DEFAULT_CONFIG field are not supported by
17 the mobile station, the mobile station shall send a Mobile Station Reject Order
18 with ORDQ field set to ‘00000110’ (capability not supported by the mobile
19 station) and shall remain in the Page Response Substate.
20 − If GRANTED_MODEr is equal to ‘00’ and DEFAULT_CONFIGr is not equal to
21 ‘100’, the mobile station shall send a Mobile Station Reject Order with ORDQ
22 field set to ‘00001110’ (RC does not match with DEFAULT_CONFIGr) and
23 shall remain in the Page Response Substate if any of the following conditions
24 is true:
25 + FOR_FCH_RCr is not equal to the RC associated with
26 DEFAULT_CONFIGr (see Table 3.7.2.3.2.21-2).
27 + REV_FCH_RCr is not equal to the RC associated with DEFAULT_CONFIGr

28 (see Table 3.7.2.3.2.21-2).
29 − If the mobile station does not support either of the Fundamental Channel
30 Radio Configurations (FOR_FCH_RC or REV_FCH_RC), the mobile shall send
31 a Mobile Station Reject Order with the ORDQ field set to ‘00000110’
32 (capability not supported by the mobile station) and remain in the Page
33 Response Substate.
34 − If P_REV_IN_USEs is equal to or greater than 6, the mobile station shall store
35 the Forward Fundamental Channel Radio Configuration (FOR_FCH_RCs =
36 FOR_FCH_RCr) and the Reverse Fundamental Channel Radio Configuration
37 (REV_FCH_RCs = REV_FCH_RCr).
39 actions:
2-181
3GPP2 C.S0005-A v6.0

2 FRAME_OFFSETr); the message encryption mode indicator
3 (ENCRYPT_MODEs = ENCRYPT_MODEr); the bypass indicator
4 (BYPASS_ALERT_ANSWERs = BYPASS_ALERT_ANSWERr); the granted
5 mode (GRANTED_MODEs = GRANTED_MODEr); the default configuration
6 (DEFAULT_CONFIGs = DEFAULT_CONFIGr); and the occurrences of
7 PILOT_PN and PWR_COMB for each included member of the Active Set.
9 listed below:



34 + The mobile station shall set FPC_FCH_INIT_SETPTs to

35 FPC_FCH_INIT_SETPTr, FPC_FCH_CURR_SETPTs to
36 FPC_FCH_INIT_SETPTs, FPC_FCH_FERs to FPC_FCH_FERr,
37 FPC_FCH_MIN_SETPTs to FPC_FCH_MIN_SETPTr,
38 FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr, and FPC_PRI_CHANs
39 to ‘0’ if the mobile station supports any Radio Configuration greater than
40 2.
41 + The mobile station shall set FPC_SUBCHAN_GAINs to
42 FPC_SUBCHAN_GAINr.
2-182
3GPP2 C.S0005-A v6.0
1 + The mobile station shall set RLGAIN_ADJs to RLGAIN_ADJr.
2 + The mobile station shall set REV_FCH_GATING_MODEs to

3 REV_FCH_GATING_MODEr.
4 + The mobile station shall set REV_PWR_CNTL_DELAYs to

5 REV_PWR_CNTL_DELAYr if REV_PWR_CNTL_DELAY_INCLr is equal to
6 ‘1’.
7 + The mobile station shall then enter the Traffic Channel Initialization
8 Substate of the Mobile Station Control on the Traffic Channel State.
9 − If FREQ_INCLr equals ‘1’, and the band class is not supported by the mobile
10 station, the mobile station shall send a Mobile Station Reject Order with
13 − If FREQ_INCLr equals ‘1’, and the band class is supported by the mobile
14 station, the mobile station shall perform the following actions:
17 (ENCRYPT_MODEs = ENCRYPT_MODEr); the bypass indicator
18 (BYPASS_ALERT_ANSWERs = BYPASS_ALERT_ANSWERr); the granted
19 mode (GRANTED_MODEs = GRANTED_MODEr); the default configuration
20 (DEFAULT_CONFIGs = DEFAULT_CONFIGr); the band class
21 (CDMABANDs = BAND_CLASSr); the Frequency Assignment
22 (CDMACHs = CDMA_FREQr); and the occurrences of PILOT_PN and
23 PWR_COMB_IND for each included member of the Active Set.
25 listed below:
2-183
3GPP2 C.S0005-A v6.0

7 by one (modulo 16).If ENC_KEY_SIZEr is included, the mobile station



19 2.


27 ‘1’.

30 + The mobile station shall then tune to the new Frequency Assignment and
31 shall enter the Traffic Channel Initialization Substate of the Mobile Station
32 Control on the Traffic Channel State.
34 actions:
36 actions:

2-184
3GPP2 C.S0005-A v6.0

3 offset of the strongest pilot in the list (PILOT_PNr). If the mobile station
4 has not stored configuration parameters for the Primary Paging Channel
5 of the new base station, or if the stored information is not current (see
6 2.6.2.2), the mobile station shall set SYS_PAR_MSG_SEQs,
9 PRI_NGHBR_LST_MSG_SEQs CHAN_LST_MSG_SEQs,
11 GLOB_SERV_REDIR_MSG_SEQs, and
14 Primary Paging Channel. If the mobile station was monitoring the
15 Forward Common Control Channel, the mobile station shall set the
16 PRATs to ‘00’. The mobile station shall then begin monitoring the Primary
17 Paging Channel of the selected base station.
19 following:
20 ο Ιf the Extended Channel Assignment Message does not require an
23 within T34m seconds after receiving the Extended Channel
24 Assignment Message.
25 ο Ιf the Extended Channel Assignment Message requires an

28 within T34m seconds after Layer 3 receives an indication from Layer 2
29 that the acknowledgement to the Extended Channel Assignment
30 Message has been sent and acknowledged.
32 following:
35 State within T34m seconds after receiving the Extended Channel

39 State within T34m seconds after Layer 3 receives an indication from
40 Layer 2 that the acknowledgement to the Extended Channel
41 Assignment Message has been sent and acknowledged.
2-185
3GPP2 C.S0005-A v6.0
1 − If FREQ_INCLr equals ‘1’, and the band class is not supported by the mobile
2 station, the mobile station shall send a Mobile Station Reject Order with
5 − If FREQ_INCLr equals ‘1’, and the band class is supported by the mobile
6 station, the mobile station shall perform the following actions:

10 + The mobile station shall set CDMACHs to CDMA_FREQr and
11 CDMABANDs to BAND_CLASSr. Then the mobile station shall tune to
12 the new Frequency Assignment, measure the strength of each pilot listed
13 in the assignment using the Neighbor Set search procedures specified in
14 2.6.6.2.1 and 2.6.6.2.2, set PILOT_PNs to the pilot PN sequence offset of
15 the strongest pilot in the list (PILOT_PNr), and set CONFIG_MSG_SEQs
16 and ACC_MSG_SEQs to NULL (see 2.6.2.2).
22 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LST_MSG_SEQs
30 following:

2-186
3GPP2 C.S0005-A v6.0

2 following:
5 State within T34m seconds after receiving the Extended Channel

9 State within T34m seconds after Layer 3 receives an indication from
10 Layer 2 that the acknowledgement to the Extended Channel
11 Assignment Message has been sent and acknowledged.
13 actions:
14 − If the mobile station does not support analog operation in the requested band
15 class, the mobile station shall send a Mobile Station Reject Order with ORDQ field
16 set to ‘00000110’ (capability not supported by the mobile station) and remain in
17 the Page Response Substate.
18 − If the mobile station supports analog operation in the requested band class, the
19 mobile station shall perform the following actions:
20 + If PACAs is equal to enabled, the mobile station shall set PACAs to disabled
23 + If RESPONDr equals ‘0’, and USE_ANALOG_SYSr equals ‘1’, the mobile
24 station shall set SERVSYSs to SYS_A if ANALOG_SYSr is equal to ‘0’, or set
25 SERVSYSs to SYS_B if ANALOG_SYSr is equal to ‘1’. The mobile station shall
26 then enter the analog Initialization Task with a wait-for-page indication (see
27 2.6.1 of [6]).
28 + If RESPONDr equals ‘1’, and USE_ANALOG_SYSr equals ‘1’, the mobile
29 station shall set SERVSYSs to SYS_A if ANALOG_SYSr is equal to ‘0’, or set
30 SERVSYSs to SYS_B if ANALOG_SYSr is equal to ‘1’. The mobile station shall
31 then enter the analog Initialization Task with a page response indication (see
32 2.6.1 of [6]).
33 + If RESPONDr equals ‘0’, and USE_ANALOG_SYSr equals ‘0’ the mobile
34 station shall enter the analog Initialization Task with a wait for page
35 indication (see 2.6.1 of [6]).
36 + If RESPONDr equals ‘1’, and USE_ANALOG_SYSr equals ‘0’ the mobile
37 station shall enter the analog Initialization Task with a page response
38 indication (see 2.6.1 of [6]).
40 actions:
2-187
3GPP2 C.S0005-A v6.0
1 − If the mobile station does not support analog operation in the requested band
2 class, the mobile station shall send a Mobile Station Reject Order with ORDQ field
3 set to ‘00000110’ (capability not supported by the mobile station) and remain in
4 the Page Response Substate.
5 − If the mobile station supports analog operation in the requested band class, and
6 the analog channel type is ‘00’, the mobile station shall store the system
7 identification (SIDs = SIDr), voice mobile station attenuation code (VMACs =
8 VMACr), voice channel number (ANALOG_CHANs = ANALOG_CHANr), SAT color
9 code (SCCs = SCCr), and message encryption mode indicator (MEMs = MEMr),
10 shall set DTXs to ‘00’, and shall enter the Confirm Initial Voice Channel Task
11 (see 2.6.4.2) with a page response indication. If PACAs is equal to enabled, the
12 mobile station shall set PACAs to disabled and PACA_CANCEL to ‘0’, shall
13 disable the PACA state timer, and should indicate to the user that the PACA call
14 has been canceled.
15 − If the mobile station supports analog operation in the requested band class, the
16 analog channel type is not ‘00’:
17 + If the mobile supports narrow analog mode, the mobile station shall store the
18 system identification (SIDs = SIDr), voice mobile station attenuation code
19 (VMACs = VMACr), voice channel number (ANALOG_CHANs =
20 ANALOG_CHANr), message encryption mode indicator (MEMs = MEMr),
21 analog channel type (AN_CHAN_TYPEs = AN_CHAN_TYPEr) and the digital
22 SAT code (DSCCs = DSCC_MSBr × 4 + SCCr), shall set DTXs to ‘00’, and shall
23 enter the Confirm Initial Narrow Analog Voice Channel Task (see 2.6.5.2A of
24 [22]) with a page response indication. If PACAs is equal to enabled, the
25 mobile station shall set PACAs to disabled and PACA_CANCEL to ‘0’, shall
26 disable the PACA state timer, and should indicate to the user that the PACA
27 call has been canceled.
28 + If the mobile station does not support narrow analog mode, the mobile
29 station shall send a Mobile Station Reject Order with the ORDQ field set to
30 ‘00000110’ (capability not supported by the mobile station) and the mobile
31 station shall remain in the Page Response Substate of the System Access
32 State.
34 actions:
35 − If PACAs is equal to enabled, the mobile station shall set PACAs to disabled and
36 PACA_CANCEL to ‘0’, shall disable the PACA state timer, and should indicate to
37 the user that the PACA call has been canceled.
38 − If GRANTED_MODEr equals ‘00’ and the multiplex option and radio
39 configuration specified in the DEFAULT_CONFIGr field are not supported by the
40 mobile station, the mobile station shall send a Mobile Station Reject Order with
42 and shall remain in the Page Response Substate.
2-188
3GPP2 C.S0005-A v6.0
1 − If GRANTED_MODEr equals ‘00’ and DEFAULT_CONFIGr is not equal to ‘100’,

2 the mobile station shall send a Mobile Station Reject Order with ORDQ field set to
3 ‘00001110’ (RC does not match with DEFAULT_CONFIG) and shall remain in the
4 Page Response Substate if one of the following conditions is true:
5 + FOR_RCr is not equal to the RC associated with DEFAULT_CONFIGr as
6 specified in Table 3.7.2.3.2.21-2.
7 + REV_RCr is not equal to the RC associated with DEFAULT_CONFIGr as

9 − If the mobile station does not support either of the Radio Configurations
10 (FOR_RC or REV_RC), the mobile station shall send a Mobile Station Reject Order
11 with the ORDQ field set to ‘00000110’ (capability not supported by the mobile
12 station) and remain in the Page Response Substate.
13 − If CH_INDr = ‘01’ and the mobile station does not support Fundamental
14 Channel, the mobile station shall send a Mobile Station Reject Order with the
17 − If CH_INDr = ‘10’ and the mobile station does not support the Dedicated Control
21 − If CH_INDr = ‘11’ and the mobile station does not support the Dedicated Control
22 Channel and Fundamental Channel concurrently, the mobile station shall send
23 a Mobile Station Reject Order with the ORDQ field set to ‘00000110’ (capability
24 not supported by the mobile station) and remain in the Page Response Substate.
25 − If FREQ_INCLr equals ‘1’ and if the band class (BAND_CLASSr) is not supported
26 by the mobile station, the mobile station shall send a Mobile Station Reject Order
28 station) and remain in the Page Response Substate.
29 − If the mobile station does not send a Mobile Station Reject Order as specified
30 above, it shall continue to perform the actions specified below.
31 − If FREQ_INCLr equals ‘1’, the mobile station shall set
32 + CDMABANDs = BAND_CLASSr
33 + CDMACHs = CDMA_FREQr
34 − The mobile station shall store the bypass indicator (BYPASS_ALERT_ANSWERs =
35 BYPASS_ALERT_ANSWERr).
36 − The mobile station shall store granted mode (GRANTED_MODEs =

37 GRANTED_MODEr )
38 − The mobile station shall store the default configuration (DEFAULT_CONFIGs =

39 DEFAULT_CONFIGr).
2-189
3GPP2 C.S0005-A v6.0
1 − The mobile station shall store the Forward Traffic Channel Radio Configuration
2 (FOR_RCs = FOR_RCr) and the Reverse Traffic Channel Radio Configuration
3 (REV_RCs = REV_RCr).

5 FRAME_OFFSETr).
6 − The mobile station shall store the message encryption mode indicator
7 (ENCRYPT_MODEs = ENCRYPT_MODEr).
9 below:
10 + If D_SIG_ENCRYPT_MODEr is included, the mobile station shall perform the
11 following:
12 ο If D_SIG_ENCRYPT_MODEr is equal to ‘000’, the mobile station shall set
13 D_SIG_ENCRYPT_MODEs to C_SIG_ENCRYPT_MODEs; otherwise, the
14 mobile station shall set D_SIG_ENCRYPT_MODEs to
16 CMEAKEY in the mobile station associated with AUTHR of the Page
17 Response Message, and EXT_ENCRYPT_SEQ[0] and
18 EXT_ENCRYPT_SEQ[1] to 256 × ENC_SEQ_H (the ENC_SEQ_H field in
19 the Page Response Message).
20 + If USE_NEW_KEYr is not included, or is included and is set to ‘1’, the mobile
24 KEY_SIZEr to KEY_SIZEs. The mobile station shall then increment the
25 variable KEY_SEQ_NEWs-p by one (modulo 16). If ENC_KEY_SIZEr is
26 included, the mobile station shall set ENC_KEY_SIZEs to ENC_KEY_SIZEr.
27 − If USE_NEW_KEYr is included and is set to ‘0’ then the mobile station shall
28 use KEYs [KEY_SEQr] as the session key.

31 − The mobile station shall store the Forward power control subchannel relative
32 gain [FPC_SUBCHAN_GAINs = FPC_SUBCHAN_GAINr).
33 − The mobile station shall set RLGAIN_ADJs to RLGAIN_ADJr.
34 − The mobile station shall set REV_FCH_GATING_MODEs to

36 − The mobile station shall set REV_PWR_CNTL_DELAYs to

37 REV_PWR_CNTL_DELAYr if REV_PWR_CNTL_DELAY_INCLr is equal to ‘1’.
38 − If 3XFL_1XRL_INCLr is equal to ‘1’, the mobile station shall set

39 1XRL_FREQ_OFFSETs to 1XRL_FREQ_OFFSETr.
2-190
3GPP2 C.S0005-A v6.0
1 − The mobile station shall store the channel indicator (CH_INDs = CH_INDr) and
3 + If CH_INDr equals ‘01’, the mobile station shall set FPC_FCH_INIT_SETPTs to
4 FPC_FCH_INIT_SETPTr, FPC_FCH_CURR_SETPTs to FPC_FCH_INIT_SETPTs,
5 FPC_FCH_FERs to FPC_FCH_FERr, FPC_FCH_MIN_SETPTs to
6 FPC_FCH_MIN_SETPTr, FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr,
7 and FPC_PRI_CHANs to ‘0’ if the mobile station supports any Radio
8 Configuration greater than 2. Then for each included member of the Active
9 Set, the mobile station shall store the following:
10 ο Set the PILOT_PN field to PILOT_PNr.
11 ο Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC_INCLr. If

12 ADD_PILOT_REC_INCLr equals ‘1’, the mobile station shall store the
13 following:
14 ◊ Set the PILOT_REC_TYPE field of PILOT_REC to PILOT_REC_TYPEr.
15 ◊ If PILOT_REC_TYPEr equals ‘000’, the mobile station shall set the

16 TD_POWER_LEVEL field of PILOT_REC to TD_POWER_LEVELr and
17 set the TD_MODE field of PILOT_REC to TD_MODEr.
18 ◊ If PILOT_REC_TYPEr is equal to ‘001’, the mobile station shall.
19 – Set the AUX_PILOT_QOF field of PILOT_REC to QOFr.
20 – Set the AUX_PILOT_WALSH_CODE field of PILOT_REC to

22 WALSH_LENGTHr.
23 ◊ If NGHBR_PILOT_REC_TYPEr is equal to ‘010’, the mobile station

24 shall:
25 – Set the AUX_PILOT_TD_QOF field of PILOT_REC to QOFr.

27 AUX_WALSHr with the Walsh Code length specified by
28 WALSH_LENGTHr.
29 – Set the AUX_TD_POWER_LEVEL field of PILOT_REC to

32 ◊ If PILOT_REC_TYPEr is equal to ‘011’, the mobile station shall:
33 – Set the SR3_PRIMARY_PILOT field of PILOT_REC to

35 – Set the SR3_PILOT_POWER1 field of PILOT_REC to


2-191
3GPP2 C.S0005-A v6.0




11 WALSH_LENGTHr.
12 – If ADD_INFO_INCL1r is equal to ‘1’, set the AUX_PILOT_QOF1

13 field of PILOT_REC to QOF1r and set the
14 AUX_PILOT_WALSH_CODE1 field of PILOT_REC to
15 AUX_PILOT_WALSH1r with the Walsh Code length specified by
16 WALSH_LENGTH1r.
17 – Otherwise, set the AUX_PILOT_QOF1 field of PILOT_REC to QOFr

18 and set the AUX_PILOT_WALSH_CODE1 field of PILOT_REC to
20 WALSH_LENGTHr.

25 WALSH_LENGTH2r.

29 WALSH_LENGTHr.
30 ο Set the PWR_COMB_IND field to PWR_COMB_INDr.
31 ο Set the CODE_CHAN_FCH field to CODE_CHAN_FCHr.
32 ο Set the QOF_MASK_ID_FCH field to QOF_MASK_ID_FCHr.
33 + If CH_INDr equals ‘01’ and 3X_FCH_INFO_INCLr equals to ‘1’, for each

34 included member of the Active Set, the mobile station store the following:
35 ο If 3X_FCH_LOW_INCLr equals ‘1’, set the QOF_MASK_ID_FCH_LOW field

36 to QOF_MASK_ID_FCH_LOWr and the CODE_CHAN_FCH_LOW field to
37 CODE_CHAN_FCH_LOWr. Otherwise, set the QOF_MASK_ID_FCH_LOW
38 field to QOF_MASK_ID_FCHr and the CODE_CHAN_FCH_LOW to
39 CODE_CHAN_FCHr.
2-192
3GPP2 C.S0005-A v6.0
1 ο If 3X_FCH_HIGH_INCLr equals ‘1’, set the QOF_MASK_ID_FCH_HIGH

2 field to QOF_MASK_ID_FCH_HIGHr and the CODE_CHAN_FCH_HIGH
3 field to CODE_CHAN_FCH_HIGHr. Otherwise, set the
4 QOF_MASK_ID_FCH_HIGH field to QOF_MASK_ID_FCHr and the
5 CODE_CHAN_FCH_HIGH to CODE_CHAN_FCHr.
6 + If CH_INDr equals ‘10’, the mobile station shall set FPC_DCCH_INIT_SETPTs

7 to FPC_DCCH_INIT_SETPTr, FPC_DCCH_CURR_SETPTs to
8 FPC_DCCH_INIT_SETPTs, FPC_DCCH_FERs to FPC_DCCH_FERr,
9 FPC_DCCH_MIN_SETPTs to FPC_DCCH_MIN_SETPTr,
10 FPC_DCCH_MAX_SETPTs to FPC_DCCH_MAX_SETPTr, and FPC_PRI_CHANs
11 to ‘1’ if the mobile station supports any Radio Configuration greater than 2.
12 Then for each included member of the Active Set, the mobile station shall
13 store the following:
14 ο Set the PILOT_PN to PILOT_PNr.

16 ADD_PILOT_REC_INCL is equal to ‘1’, the mobile station shall store the
17 following:

22 ◊ If PILOT_REC_TYPEr is equal to ‘001’, the mobile station shall.

26 WALSH_LENGTHr.

31 WALSH_LENGTHr.

34 – Set the TD_MODE field of PILOT_REC to TD_MODEr.


2-193
3GPP2 C.S0005-A v6.0





13 WALSH_LENGTHr.

18 WALSH_LENGTH1r.

22 WALSH_LENGTHr.

27 WALSH_LENGTH2r.

31 WALSH_LENGTHr.
35 ο Set the DCCH_INCL field to DCCH_INCLr. If DCCH_INCLr equals ‘1’, the

36 mobile station shall store the following:
37 ◊ Set the CODE_CHAN_DCCH field to CODE_CHAN_DCCHr.
38 ◊ Set the QOF_MASK_ID_DCCH field to QOF_MASK_ID_DCCHr.
2-194
3GPP2 C.S0005-A v6.0
1 + If CH_INDr equals ‘10’ and 3X_DCCH_INFO_INCLr equals to ‘1’, for each

3 ο If 3X_DCCH_LOW_INCLr equals ‘1’, set the QOF_MASK_ID_DCCH_LOW

4 field to QOF_MASK_ID_DCCH_LOWr and the CODE_CHAN_DCCH_LOW
5 field to CODE_CHAN_DCCH_LOWr. Otherwise, set the
6 QOF_MASK_ID_DCCH_LOW field to QOF_MASK_ID_FCHr and the
7 CODE_CHAN_DCCH_LOW to CODE_CHAN_FCHr.
8 ο If 3X_DCCH_HIGH_INCLr equals ‘1’, set the QOF_MASK_ID_DCCH_HIGH

9 field to QOF_MASK_ID_DCCH_HIGHr and the CODE_CHAN_DCCH_HIGH
10 field to CODE_CHAN_DCCH_HIGHr. Otherwise, set the
11 QOF_MASK_ID_DCCH_HIGH field to QOF_MASK_ID_FCHr and the
12 CODE_CHAN_DCCH_HIGH to CODE_CHAN_FCHr.
13 + If CH_INDr equals ‘11’, the mobile station shall set FPC_FCCH_INIT_SETPTs

14 to FPC_FCH_INIT_SETPTr, FPC_FCH_CURR_SETPTs to
16 FPC_FCH_MIN_SETPTs to FPC_FCH_MIN_SETPTr, FPC_FCH_MAX_SETPTs to
17 FPC_FCH_MAX_SETPTr, FPC_DCCH_INIT_SETPTs to
18 FPC_DCCH_INIT_SETPTr, FPC_DCCH_CURR_SETPTs to
19 FPC_DCCH_INIT_SETPTs, FPC_DCCH_FERs to FPC_DCCH_FERr,
20 FPC_DCCH_MIN_SETPTs to FPC_DCCH_MIN_SETPTr,
21 FPC_DCCH_MAX_SETPTs to FPC_DCCH_MAX_SETPTr and FPC_PRI_CHANs
22 to FPC_PRI_CHANr. Then for each included member of the Active Set, the
25 ο Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC. If

26 ADD_PILOT_REC_INCL is equal to ‘1’, the mobile station shall store the
27 following:


36 WALSH_LENGTHr.
2-195
3GPP2 C.S0005-A v6.0

3 WALSH_LENGTHr.








24 WALSH_LENGTHr.

29 WALSH_LENGTH1r.

33 WALSH_LENGTHr.

38 WALSH_LENGTH2r.
2-196
3GPP2 C.S0005-A v6.0

4 WALSH_LENGTHr.
8 ο Set the CODE_CHAN_DCCH field to CODE_CHAN_DCCHr.
9 ο Set the QOF_MASK_ID_DCCH field to QOF_MASK_ID_DCCH.

12 ο If 3X_FCH_LOW_INCLr equals ‘1’, set the QOF_MASK_ID_FCH_LOW field

13 to QOF_MASK_ID_FCH_LOWr and the CODE_CHAN_FCH_LOW field to
14 CODE_CHAN_FCH_LOWr. Otherwise, set the QOF_MASK_ID_FCH_LOW
15 field to QOF_MASK_ID_FCHr and the CODE_CHAN_FCH_LOW to
16 CODE_CHAN_FCHr.


24 ο If 3X_DCCH_LOW_INCLr equals ‘1’, set the QOF_MASK_ID_DCCH_LOW

25 field to QOF_MASK_ID_DCCH_LOWr and the CODE_CHAN_DCCH_LOW
26 field to CODE_CHAN_DCCH_LOWr. Otherwise, set the
29 ο If 3X_DCCH_HIGH_INCLr equals ‘1’, set the QOF_MASK_ID_DCCH_HIGH

30 field to QOF_MASK_ID_DCCH_HIGHr and the CODE_CHAN_DCCH_HIGH
34 − The mobile station shall initialize CODE_CHAN_LIST as described in 2.6.8, and

35 shall set SERV_NEGs to enabled.
36 − If FREQ_INCLr equals ‘1’, the mobile station shall then tune to the new
37 frequency assignment.
38 − The mobile station shall then enter the Traffic Channel Initialization Substate of
2-197
3GPP2 C.S0005-A v6.0
2 7.7. Local Control Order
3 8.8. Lock Until Power-Cycled Order: The mobile station shall disable its transmitter
4 and record the reason for the Lock Until Power-Cycled Order in the mobile station’s
5 semi-permanent memory (LCKRSN_Ps-p equals the least significant four bits of
6 ORDQr). The mobile station should notify the user of the locked condition. The
8 Initialization State with a lock indication (see 2.6.1.1), and shall not enter the System
9 Access State again until after the next mobile station power-up or until it has
10 received an Unlock Order. This requirement shall take precedence over any other
11 mobile station requirement specifying entry to the System Access State.
12 9.10. Maintenance Required Order: The mobile station shall record the reason for the
14 (MAINTRSNs-p equals the least significant four bits of ORDQr). The mobile station
15 shall remain in the unlocked condition. The mobile station should notify the user of
16 the maintenance required condition.
17 10.11. Registration Accepted Order:

18 • If ORDQr = ‘00000101’, the mobile station shall set ROAM_INDIs =to
19 ROAM_INDIr and should display the roaming condition.
20 • If ORDQr = ‘00000111’, the mobile station shall perform the following:

30 KEY_SEQ_NEWs-p by one (modulo 16). If ENC_KEY_SIZEr is included, the
32 - If USE_NEW_KEYr is included and is set to ‘0’, then the mobile station shall
33 use KEYs[KEY_SEQr] as the session key.

35 ENC_KEYs to the most recently generated CMEAKEY in the mobile station,
38 (the ENC_SEQ_H field in the Registration Message)
39 11.12. Registration Rejected Order: This order indicates that normal service is not
2-198
3GPP2 C.S0005-A v6.0
4 12.13. Release Order: If NDSS_ORIGs is equal to enabled, the mobile station shall set
5 NDSS_ORIGs to disabled, and should indicate to the user that the call origination
6 has been canceled. The mobile station shall enter the Mobile Station Idle State or the
7 System Determination Substate of the Mobile Station Initialization State with a release
8 indication (see 2.6.1.1). If the mobile station enters the Mobile Station Idle State,
9 and if PACAs is equal to enabled, the mobile station shall set PACAs to disabled and
12 13.14. Retry Order: The mobile station shall process the message as follows:
15 or ‘011’.




29 14.15. Security Mode Command Message: The mobile station shall process the message
30 as follows:
31 • The mobile station shall set C_SIG_ENCRYPT_MODEs
32 =C_SIG_ENCRYPT_MODEr.

2-199
3GPP2 C.S0005-A v6.0
3 15.16. Service Redirection Message: The mobile station shall process the message as
4 follows:

8 mobile station).

18 16.17. SSD Update Message: The mobile station shall respond to the message as
19 specified in 2.3.12.1.5.
20 17.18. Status Request Message: The mobile station shall disable the System Access
21 State timer and respond to the message. If P_REV_IN_USEs is less than or equal to
22 three, the mobile station shall respond with a Status Response Message. If
23 P_REV_IN_USEs is greater than three, the mobile station shall respond with an
24 Extended Status Response Message. If the message does not specify any
25 qualification information (QUAL_INFO_TYPEr is equal to ‘00000000’), the mobile
26 station shall include the requested information records in the response. If the
27 message specifies a band class (QUAL_INFO_TYPEr is equal to ‘00000001’), the
28 mobile station shall only include the requested information records for the specified
29 band class (BAND_CLASSr) in the response. If the message specifies a band class
30 and an operating mode (QUAL_INFO_TYPEr is equal to ‘00000010’), the mobile
31 station shall only include the requested information records for the specified band
32 class (BAND_CLASSr) and operating mode (OP_MODEr) in the response. If the
33 message specifies a band class or a band class and an operating mode which is not
34 supported by the mobile station, the mobile station shall send a Mobile Station Reject
35 Order with ORDQ set to ‘00000110’ (message requires a capability that is not
36 supported by the mobile station). If the response to this message exceeds the
37 allowable length, the mobile station shall send a Mobile Station Reject Order with
38 ORDQ set to ‘00001000’ (response message would exceed the allowable length). If
39 the message specifies an information record which is not supported by the mobile
40 station for the specified band class and operating mode, the mobile station shall
41 send a Mobile Station Reject Order with ORDQ set to ‘00001001’ (information record
42 is not supported for the specified band class and operating mode).
2-200
3GPP2 C.S0005-A v6.0
1 18.19. TMSI Assignment Message: The mobile station shall store the TMSI zone and
2 code as follows:
4 ASSIGNING_TMSI_ZONE_LENs-p to TMSI_ZONE_LENr;
9 TMSI_CODEr.
14 19.20. User Zone Reject Message
15 20.Base Station Reject Order:

16 • If ORDQr = ‘00000001’, the mobile station shall send a Security Mode
17 Request Message with the ENC_SIG_H field included in it. If the mobile
18 receives two Base Station Reject Orders without successfully decrypting any
19 encrypted messages from the base station between the orders, the mobile
20 station shall set REG_ENCRYPT_RESYNC to YES and enter the System
21 Determination Substate with an encryption failure indication
22 21. Any other message: If the mobile station receives any other message specified in
23 Table 3.7.2.3-1, it shall ignore all Layer 3 fields. The mobile station shall ignore all
24 other messages.
25 If the mobile station performs an access probe handoff or access handoff and
26 receives any of the following messages, it shall process the message as specified in
27 2.6.3.1.3:
28 • If the mobile station is currently monitoring the Paging Channel:

29 1. System Parameters Message
30 2. Access Parameters Message
31 3. Neighbor List Message
32 4. Extended System Parameters Message
33 5. Extended Neighbor List Message
34 6. General Neighbor List Message
35 7. Global Service Redirection Message
36 8. Extended Global Service Redirection Message
37 • If the mobile station is currently monitoring the Primary Broadcast Control Channel:
2-201
3GPP2 C.S0005-A v6.0
1 1. ANSI-41 System Parameters Message
2 2. Enhanced Access Parameters Message
3 3. Universal Neighbor List Message
4 4. MC-RR Parameters Message
6 2.6.3.4 Mobile Station Order/Message Response Substate
7 In this substate, the mobile station sends a message that is a response to a message
8 received from the base station. If the base station responds to the mobile station’s message
9 with an authentication request, the mobile station responds in this substate.
15 2.1.1.2.2.1 of [4]).
21 request (see 2.1.1.2.2.1 of [4]).
22 Upon entering the Mobile Station Order/Message Response Substate, the mobile station
23 shall send the response message.
24 If this substate was entered with a service release message response with success
25 indication, the mobile station shall send a Service Release Response Message to the base
26 station. The mobile station shall set the SUCCESS_IND field to ‘1’.
27 If this substate was entered with a service release message response with failure indication,
28 the mobile station shall send a Service Release Response Message to the base station. The
29 mobile station shall set the SUCCESS_IND field to ‘0’.
31 Common Control Channel. If the mobile station declares a loss of the Paging Channel or
32 the Forward Common Control Channel (see 2.6.2.1.1.4 2.6.3.1.8), the mobile station shall
2-202
3GPP2 C.S0005-A v6.0
1 • The mobile station shall disable its transmitter.
4 station in this substate, it shall send a response in this substate if required, and shall then
12 If Layer 3 receives a message with an indication from Layer 2 that an access attempt for a

27 REG_ENCRYPT_RESYNC to YES and the mobile station shall go to the System
28 Determination Substate with an encryption failure indication.
2-203
3GPP2 C.S0005-A v6.0

9 • If ORDQr = ‘00000111’, the mobile station shall perform the following:


34 10.11. Retry Order: The mobile station shall process the message as follows:
37 or ‘011’.

2-204
3GPP2 C.S0005-A v6.0



12 as follows:
15 • If If USE_NEW_KEYr is not included, or is included and is set to ‘1’, the mobile

20 KEY_SEQ_NEWs-p by one (modulo 16)If ENC_KEY_SIZEr is included, the mobile
21 station shall set ENC_KEY_SIZEs to ENC_KEY_SIZEr.
22 • If If USE_NEW_KEYr is included and is set to ‘0’, then the mobile station shall
25 follows:

29 mobile station).

2-205
3GPP2 C.S0005-A v6.0
14 message specifies a band class or a band class and an operating mode which is not
25 code as follows:
32 TMSI_CODEr.
38 17.18. Any other message: If the mobile station receives any other message specified
39 in Table 3.7.2.3-1, it shall ignore all Layer 3 fields. The mobile station shall ignore
40 all other messages.
2-206
3GPP2 C.S0005-A v6.0
7 2.6.3.5 Mobile Station Origination Attempt Substate
8 In this substate, the mobile station sends an Origination Message. If the base station
9 responds to the Origination Message with an authentication request, the mobile station
10 responds in this substate.
16 2.1.1.2.2.1 of [4]).
22 request (see 2.1.1.2.2.1 of [4]).
23 Upon entering the Mobile Station Origination Attempt Substate, the mobile station shall set
24 RLGAIN_ADJs to ‘0000’ and perform the following:
25 • The mobile station shall exit the Mobile Station Origination Attempt Substate, shall
26 enter either the Mobile Station Idle State or the System Determination Substate with
27 an ACCT blocked indication, and should indicate to the user that the call has
28 terminated if all of the following conditions are true:
29 – P_REV_IN_USEs is greater than six,
30 – ACCT_INCL_EMGs is equal to ‘1’ or the mobile station determines that the call is
31 not an emergency call,
32 – ACCT is enabled for the requested service option number, due to either of the
33 following two conditions:
34 + the requested service option number is equal to an ACCT_SO entry in

35 ACCT_SO_LIST, or
36 + the service option group number of the requested service option is equal to
37 an ACCT_SO_GRP entry in ACCT_SO_GRP_LIST.
38 • If the substate was entered with an origination indication, the mobile station shall
39 send the Origination Message as an r-csch request.
2-207
3GPP2 C.S0005-A v6.0
1 • If the substate was entered with a PACA response indication, the mobile station
2 shall send the Origination Message as an r-csch response using the access
3 procedures specified in 2.6.3.1.1.2. The mobile station shall include the dialed
4 digits (if any) from the previous origination attempt in the Origination Message.
5 • If the origination is a result of NDSS_ORIGs being equal to enabled, the mobile
6 station shall include in the Origination Message the dialed digits ([if any]) recorded
7 from the previous origination attempt.
8 • If the mobile station has a stored service configuration (that is, parameters conveyed
9 by both the Service Configuration information record and the Non-negotiable Service
10 Configuration information record), SYNC_IDs is not equal to NULL, and
11 USE_SYNC_IDs is equal to ‘1’, the mobile station may include the SYNC_ID field in
12 the Origination Message and, if included, shall set it to the 16-bit CRC computed
13 over the entire stored service configuration as specified in 2.6.11SYNC_IDs
14 corresponding to the stored service configuration.
15 • The mobile station shall include in the Origination Message as many of the dialed
16 digits as possible without exceeding the message capsule size. When calculating the
17 number of dialed digits to be included in the Origination Message, the mobile station
18 shall assume the following if P_REV_IN_USEs is greater than three:
19 − The number of additional reported pilots (NUM_ADD_PILOTS) is equal to five (see

20 2.6.3.1.7 and 2.7.1.3.1.3) so that up to five additional pilots may be reported in
21 any access probe, and
22 – The number of alternative service option numbers (NUM_ALT_SO) is less than or

23 equal to the maximum alternative service option numbers (MAX_NUM_ALT_SOs).
24 • If PACAs is equal to enabled, the mobile station shall set the PACA_REORIG field of
25 the Origination Message to ‘1’; otherwise, the mobile station shall set the field to ‘0’.
27 Common Control Channel. The mobile station may perform an access probe handoff or an
28 access handoff as described in 2.6.3.1.3.2 and 2.6.3.1.3.3. If the mobile station declares a
29 loss of the Paging Channel or the Forward Common Control Channel (see 2.6.2.1.1.4
30 2.6.3.1.8) during an access attempt, the mobile station may perform an access probe
31 handoff; otherwise, it shall declare an access attempt failure and shall perform the
32 following:
40 • If NDSS_ORIGs is equal to enabled, the mobile station shall set NDSS_ORIGs to
41 disabled, and should indicate to the user that the call origination is canceled.
2-208
3GPP2 C.S0005-A v6.0
1 • The mobile station shall update its registration variables as specified in 2.6.5.5.3.2.
2 • The mobile station shall disable its transmitter and enter the Mobile Station Idle
3 State.
5 station in this substate, the mobile station shall perform an access handoff if all of the
6 following conditions hold:
7 • The mobile station declares a loss of the Paging Channel or the Forward Common
8 Control Channel,
9 • The mobile station is permitted to perform an access handoff (see 2.6.3.1.3.2) and
10 there are pilots other than the active pilot in the access handoff list (see 2.6.3.1.3.2).
12 Channel and does not perform an access handoff, the mobile station shall perform the
13 following:
22 disabled and should indicate to the user that the call origination is canceled.
24 State.
25 If the mobile station receives confirmation of delivery of the Origination Message, the mobile
26 station shall update its registration variables with respect to the base station to which the
27 first access probe was transmitted after entering the System Access State as specified in
28 2.6.5.5.3.1.
29 The mobile station shall set and disable the System Access State timer as follows:
30 • The mobile station shall disable the timer whenever it begins an access attempt.
31 • The mobile station shall set the timer to T42m seconds whenever it ends an access
32 attempt.
33 • The mobile station shall disable the timer whenever it exits the System Access State.
2-209
3GPP2 C.S0005-A v6.0

2 disabled, and should indicate to the user that the call origination is canceled.
4 SYS_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL and enter the Mobile Station Idle
5 State.
7 mobile station shall set MC_RR_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL and
9 If the mobile station is directed by the user to disconnect the call, the mobile station shall
11 • Layer 3 shall send an L2-Supervision.Request primitive to Layer 2 to abort any

12 access attempt in progress.
13 • The mobile station shall send the Release Order (normal release) in assured mode
14 requiring confirmation of delivery.
15 • After receiving confirmation of delivery of the Release Order, the mobile station shall
16 enter the System Determination Substate of the Mobile Station Initialization State with
17 a release indication (see 2.6.1.1).
18 If the mobile station is directed by the user to power off, the mobile station shall perform
19 the following actions:

22 • The mobile station shall send the Release Order (with power-down indication) in
23 assured mode requiring confirmation of delivery.
24 • After receiving confirmation of delivery of the Release Order, the mobile station shall
25 perform power-down registration procedures (see 2.6.5.1.2).
26 • The mobile station may power off.
27 If the mobile station receives a Channel Assignment Message or the Extended Channel
28 Assignment Message, Layer 3 shall send a dedicated channel assignment indication to Layer
29 2 (see 2.1.2.1.2 of [4]). If the mobile station has not received confirmation of delivery of the
30 Origination Message before receiving the Channel Assignment Message or the Extended
31 Channel Assignment Message, the mobile station shall update its registration variables with
32 respect to the base station to which the first access probe was transmitted after entering
33 the System Access State, as specified in 2.6.5.5.3.1.
38 If Layer 3 receives a message other than a Channel Assignment Message or an Extended

39 Channel Assignment Message with an indication from Layer 2 that an access attempt for a
2-210
3GPP2 C.S0005-A v6.0
10 • If ORDQr = ‘00000000’, the mobile station shall set ENC_KEYs to NULL and set
11 C_SIG_ENCRYPT_MODE to ‘000’. The mobile station shall re-originate by
12 sending a new Origination Message.
20 follows:
22 actions:

26 (ENCRYPT_MODEs = ENCRYPT_MODEr), and, if FREQ_INCLr equals ‘1’, the
27 Frequency Assignment (CDMACHs = CDMA_FREQr).
29 below:
31 the following:
36 CMEAKEY in the mobile station associated with the AUTHR of the
37 Origination Message, and EXT_ENCRYPT_SEQ[0] and
39 in the Origination Message).
2-211
3GPP2 C.S0005-A v6.0

9 − If USE_NEW_KEYr is included and is set to ‘0’ then the mobile station


15 indicate to the user that the PACA call is proceeding.
16 − The mobile station shall initialize the CODE_CHAN_LIST as described in

17 2.6.8, shall set SERV_NEGs to disabled, and shall enter the Traffic Channel
18 Initialization Substate of the Mobile Station Control on the Traffic Channel
19 State.
21 actions:
22 − If the message requires acknowledgement, the mobile station shall wait until
25 − If a CDMA channel (CDMA_FREQ) is specified in the assignment, the mobile

26 station shall set CDMACHs = CDMA_FREQr, tune to the new Frequency
27 Assignment, and measure the strength of each pilot listed in the assignment
29 2.6.6.2.2.
30 − The mobile station shall set CONFIG_MSG_SEQs and ACC_MSG_SEQs to
32 the strongest pilot in the list.
39 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LIST_MSG_SEQs,
41 to NULL.
2-212
3GPP2 C.S0005-A v6.0
2 Forward Common Control Channel of the new base station, or if the stored
6 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LIST_MSG_SEQs,
7 GLOB_SERV_REDIR_MSG_SEQs, A41_SYS_PAR_MSG_SEQs
8 MC_RR_PAR_MSG_SEQs UNIV_NGHBR_LIST_MSG_SEQs and
10 − The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the Primary
11 Paging Channel. If the mobile station was monitoring Forward Common
12 Control Channel, the mobile station shall set the PRATs to ‘00’. The mobile
13 station shall then begin monitoring the Primary Paging Channel of the
15 − The mobile station shall set FCCCH_CHANs to ‘1’ and FCCCH_IDs to the
16 Primary Forward Common Control Channel. The mobile station shall then
17 begin monitoring the Primary Forward Common Control Channel of the
19 − If RESPONDr is equal to ‘1’, the mobile station shall enter the Update
20 Overhead Information Substate with an origination indication.
22 actions:
23 – If the mobile station does not support analog operation in the requested
25 the ORDQ field set to ‘00000110’ (capability not supported by the mobile
26 station) and the mobile station shall remain in the Mobile Station Origination
27 Attempt Substate.
28 − If the mobile station supports analog operation in the requested band class
29 and RESPONDr equals ‘1’, the mobile station shall perform the following
30 actions:
31 + If USE_ANALOG_SYSr equals ‘0’, the mobile station shall perform the
32 following actions:
33 ο If PACAs is equal to enabled, the mobile station shall set PACAs to
36 ο The mobile station shall enter the analog Initialization Task with an
37 origination indication (see 2.6.1).
38 + If USE_ANALOG_SYSr equals ‘1’, the mobile station shall perform the
2-213
3GPP2 C.S0005-A v6.0
1 ο The mobile station shall set SERVSYSs to SYS_A if ANALOG_SYSr is

2 equal to ‘0’, or shall set SERVSYSs to SYS_B if ANALOG_SYSr is equal
3 to ‘1’.
7 ο The mobile station shall then enter the analog Initialization Task with
8 an origination indication (see 2.6.1).
10 actions:
16 − If the mobile station supports analog operation in the requested band class:
17 + If the analog channel type is ‘00’, the mobile station shall perform the
19 ο The mobile station shall store the system identification (SIDs = SIDr),
20 the voice mobile station attenuation code (VMACs = VMACr), the voice
21 channel number (ANALOG_CHANs = ANALOG_CHANr), the SAT color
22 code (SCCs = SCCr), and the message encryption mode indicator
23 (MEMs = MEMr).
24 ο The mobile station shall set DTXs to ‘00’.

27 and should indicate to the user that the PACA call is proceeding.
28 ο The mobile station shall enter the Confirm Initial Voice Channel Task
29 (see 2.6.4.2) with an origination indication.
30 + If the analog channel type is not ‘00’, the mobile station shall perform the
32 ο If the mobile supports narrow analog mode, the mobile station shall
34 ◊ The mobile station shall store the system identification (SIDs =
35 SIDr), the voice mobile station attenuation code (VMACs =
36 VMACr), the voice channel number (ANALOG_CHANs =
37 ANALOG_CHANr), the message encryption mode indicator (MEMs
38 = MEMr), the analog channel type (AN_CHAN_TYPEs =
39 AN_CHAN_TYPEr) and the digital SAT code (DSCCs = DSCC_MSBr
40 × 4 + SCCr).
2-214
3GPP2 C.S0005-A v6.0
1 ◊ The mobile station shall set DTXs to ‘00’.
2 ◊ If PACAs is equal to enabled, the mobile station shall set PACAs to

3 disabled, shall disable the PACA state timer, and should indicate
4 to the user that the PACA call is proceeding.
5 ◊ The mobile station shall enter the Confirm Initial Narrow Analog
6 Voice Channel Task (see 2.6.5.2A of [22]) with an origination
7 indication.
11 and the mobile station shall remain in the Mobile Station Origination
12 Attempt Substate of the System Access State.
14 actions:
16 − If GRANTED_MODEr equals ‘00’, and the multiplex option or radio

17 configuration specified in the DEFAULT_CONFIG field is not supported by
20 station) and remain in Mobile Station Origination Attempt Substate.
22 actions:
26 (GRANTED_MODEs = GRANTED_MODEr), and the default configuration
27 (DEFAULT_CONFIGs = DEFAULT_CONFIGr).
29 listed below:
36 generated CMEAKEY in the mobile station, associated with the
37 AUTHR of the Origination Message, and EXT_ENCRYPT_SEQ[0]
38 and EXT_ENCRYPT_SEQ[1] to 256 × ENC_SEQ_H (the
39 ENC_SEQ_H field in the Origination Message).
2-215
3GPP2 C.S0005-A v6.0



14 + If PACAs is equal to enabled, the mobile station shall set PACAs equal to

18 2.6.8.
22 actions:
25 ‘00000110’ (capability not supported by the mobile station) and remain in
26 the Mobile Station Origination Attempt Substate.
32 (GRANTED_MODEs = GRANTED_MODEr), the default configuration
33 (DEFAULT_CONFIGs = DEFAULT_CONFIGr), the band class
34 (CDMABANDs = BAND_CLASSr), and the Frequency Assignment
35 (CDMACHs = CDMA_FREQr).
37 listed below:
2-216
3GPP2 C.S0005-A v6.0

5 mobile station, associated with the AUTHR of the Origination
15 increment the variable KEY_SEQ_NEWs-p by one (modulo 16). If
18 ο If USE_NEW_KEYr is included and is set to ‘0’ then the mobile

20 ◊ If C_SIG_ENCRYPT_MODE is included, the mobile station shall

21 set C_SIG_ENCRYPT_MODEs to C_SIG_ENCRYPT_MODEr.
22 ο The mobile station shall set SERV_NEGs to enabled.

26 ο The mobile station shall initialize the CODE_CHAN_LIST as described

27 in 2.6.8.
29 and enter the Traffic Channel Initialization Substate of the Mobile
32 actions:
34 actions:

2-217
3GPP2 C.S0005-A v6.0
8 PRI_NGHBR_LST_MSG_SEQs, GLOB_SERV_REDIR_MSG_SEQs, and
16 GLOB_SERV_REDIR_MSG_SEQs, A41_SYS_PAR_MSG_SEQs,
17 MC_RR_PAR_MSG_SEQs, UNIV_NGBHR_LST_MSG_SEQs, and
22 + The mobile station shall set FCCCH_CHANs to ‘1’ and FCCCH_IDs to the
23 Primary Forward Common Control Channel. The mobile station shall
24 then begin monitoring the Primary Forward Common Control Channel of
27 following:
31 within T34m seconds after receiving the Channel Assignment
32 Message.

34 mobile station shall enter the Update Overhead Information Substate
35 with a page response retransmission indication within T34m seconds
36 after Layer 3 receives an indication from Layer 2 that the
40 following:
2-218
3GPP2 C.S0005-A v6.0

3 State within T34m seconds after receiving the Channel Assignment
4 Message.

6 mobile station shall enter the Mobile Station Idle State within T34m
7 seconds after Layer 3 receives an indication from Layer 2 that the
9 and acknowledged.
11 actions:

41 following:
2-219
3GPP2 C.S0005-A v6.0


7 the mobile station shall enter the Update Overhead Information
8 Substate with a page response retransmission indication within
13 following:
15 acknowledgment, the mobile station shall enter the Mobile Station
16 Idle State within T34m seconds after receiving the Channel

19 the mobile station shall enter the Mobile Station Idle State within
27 actions:
29 − If P_REV_IN_USEs is equal to or greater than six, the mobile station shall

30 store the Forward Fundamental Channel Radio Configuration
31 (FOR_FCH_RCs = FOR_FCH_RCr) and the Reverse Fundamental Channel
32 Radio Configuration (REV_FCH_RCs = REV_FCH_RCr)
34 actions:
38 (GRANTED_MODEs = GRANTED_MODEr), the default configuration
39 (DEFAULT_CONFIGs = DEFAULT_CONFIGr), and the occurrences of
40 PILOT_PN and PWR_COMB for each included member of the Active Set.
2-220
3GPP2 C.S0005-A v6.0
2 listed below:
9 generated CMEAKEY in the mobile station, associated with the
10 AUTHR of the Origination Message, and EXT_ENCRYPT_SEQ[0]
11 and EXT_ENCRYPT_SEQ[1] to 256 × ENC_SEQ_H (the
19 by one (modulo 16).If ENC_KEY_SIZEr is included, the mobile station


26 + If PACAs is equal to enabled, the mobile station shall set PACAs equal to

30 2.6.8.
37 2.

2-221
3GPP2 C.S0005-A v6.0

3 ‘1’.
8 actions:
17 (ENCRYPT_MODEs = ENCRYPT_MODEr); the granted mode
18 (GRANTED_MODEs = GRANTED_MODEr); the default configuration
19 (DEFAULT_CONFIGs = DEFAULT_CONFIGr); the band class
20 (CDMABANDs = BAND_CLASSr); the Frequency Assignment
21 (CDMACHs = CDMA_FREQr); and the occurrences of PILOT_PN and
22 PWR_COMB_IND for each included member of the Active Set.
24 listed below:
32 mobile station, associated with the AUTHR of the Origination
2-222
3GPP2 C.S0005-A v6.0

7 increment the variable KEY_SEQ_NEWs-p by one (modulo 16).If
10 ο If USE_NEW_KEYr is included and is set to ‘0’ then the mobile

12 ◊ If C_SIG_ENCRYPT_MODE is included, the mobile station shall

13 set C_SIG_ENCRYPT_MODEs to C_SIG_ENCRYPT_MODEr.
14 ο The mobile station shall set SERV_NEGs to enabled.
15 ο The mobile station shall initialize CODE_CHAN_LIST as described in

16 2.6.8.
17 ο The mobile station shall set FPC_FCH_INIT_SETPTs to
21 FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr, and
22 FPC_PRI_CHANs to ‘0’ if the mobile station supports any Radio
23 Configuration greater than 2.
24 ο The mobile station shall set FPC_SUBCHAN_GAINs to
26 ο The mobile station shall set RLGAIN_ADJs to RLGAIN_ADJr.
27 ο The mobile station shall set REV_FCH_GATING_MODEs to

29 ο The mobile station shall set REV_PWR_CNTL_DELAYs to

30 REV_PWR_CNTL_DELAYr if REV_PWR_CNTL_DELAY_INCLr is equal
31 to ‘1’.
33 and enter the Traffic Channel Initialization Substate of the Mobile
36 configuration specified in the DEFAULT_CONFIG field is not supported by
39 station) and remain in the Mobile Station Origination Attempt Substate.
2-223
3GPP2 C.S0005-A v6.0
1 − If GRANTED_MODEr equals ‘00’ and DEFAULT_CONFIGr is not equal to

2 '100', the mobile station shall send a Mobile Station Reject Order with the
3 ORDQ field set to ‘00001110’ (RC does not match with DEFAULT_CONFIGr)
4 and shall remain in the Mobile Station Origination Attempt Substate if any of
5 the following conditions is true:
6 + FOR_FCH_RCr is not equal to the Radio Configuration associated with
8 + REV_FCH_RCr is not equal to the Radio Configuration associated with

10 − If the mobile station does not support either of the Fundamental Channel
11 Radio Configurations (FOR_FCH_RC or REV_FCH_RC), the mobile shall send
12 a Mobile Station Reject Order with the ORDQ field set to ‘00000110’
13 (capability not supported by the mobile station) and remain in the Mobile
14 Station Origination Attempt Substate.
16 actions:
18 actions:

35 Primary Paging Channel. If the mobile station was monitoring Forward
36 Common Control Channel, the mobile station shall set the PRATs to ‘00’.
37 The mobile station shall then begin monitoring the Primary Paging
38 Channel of the selected base station.
40 following:
2-224
3GPP2 C.S0005-A v6.0


13 actions:

2-225
3GPP2 C.S0005-A v6.0

2 following:
3 ◊ Ιf the Extended Channel Assignment Message does not require an
7 Extended Channel Assignment Message.
8 ◊ Ιf the Extended Channel Assignment Message requires an

11 retransmission indication within T34m seconds after Layer 3
12 receives an indication from Layer 2 that the acknowledgement to
13 the Extended Channel Assignment Message has been sent and
14 acknowledged.
16 actions:
20 and remain in the Mobile Station Origination Attempt Substate.
23 + If RESPONDr equals ‘1’ and USE_ANALOG_SYSr equals ‘0’, the mobile
24 station shall enter the analog Initialization Task with an origination
25 indication (see 2.6.1).
26 + If RESPONDr equals ‘1’ and USE_ANALOG_SYSr equals ‘1’, the mobile
27 station shall perform the following actions:
28 ο The mobile station shall set SERVSYSs to SYS_A if ANALOG_SYSr is
29 equal to ‘0’, or set SERVSYSs to SYS_B if ANALOG_SYSr is equal to
30 ‘1’.
31 ο The mobile station shall then enter the analog Initialization Task with
32 an origination indication (see 2.6.1).
34 actions:
2-226
3GPP2 C.S0005-A v6.0
1 + If the analog channel type is ‘00’, the mobile station shall perform the
3 ο The mobile station shall store the system identification (SIDs = SIDr),
4 voice mobile station attenuation code (VMACs = VMACr), voice
5 channel number (ANALOG_CHANs = ANALOG_CHANr), SAT color
6 code (SCCs = SCCr), and message encryption mode indicator (MEMs =
7 MEMr).
8 ο The mobile station shall set DTXs to ‘00’.

12 ο The mobile station shall enter the Confirm Initial Voice Channel Task
13 (see 2.6.4.2) with an origination indication.
14 + If the analog channel type is not ‘00’, the mobile station shall perform the
16 ο If the mobile supports narrow analog mode, the mobile station shall
18 ◊ The mobile station shall store the system identification (SIDs =
19 SIDr), voice mobile station attenuation code (VMACs = VMACr),
20 voice channel number (ANALOG_CHANs = ANALOG_CHANr),
21 message encryption mode indicator (MEMs = MEMr), analog
22 channel type (AN_CHAN_TYPEs = AN_CHAN_TYPEr) and the
23 digital SAT code (DSCCs = DSCC_MSBr × 4 + SCCr).
24 ◊ The mobile station shall set DTXs to ‘00’.
25 ◊ If PACAs is equal to enabled, the mobile station shall set PACAs to

26 disabled and PACA_CANCEL to ‘0’, shall disable the PACA state
27 timer, and should indicate to the user that the PACA call is
28 proceeding.
29 ◊ The mobile station shall enter the Confirm Initial Narrow Analog
30 Voice Channel Task (see 2.6.5.2A of [22]) with an origination
31 indication.
35 and the mobile station shall remain in the Mobile Station Origination
36 Attempt Substate of the System Access State.
37 If ASSIGN_MODEr equals ‘100’, the mobile station shall perform the following
38 actions:
2-227
3GPP2 C.S0005-A v6.0
4 − If GRANTED_MODEr equals ‘00’ and the multiplex option and radio
5 configuration specified in the DEFAULT_CONFIGr field are not supported by
8 station) and shall remain in the Mobile Station Origination Attempt Substate.
9 − If GRANTED_MODEr equals ‘00’ and DEFAULT_CONFIGr is not equal to
10 ‘100’, the mobile station shall send a Mobile Station Reject Order with ORDQ
11 field set to ‘00001110’ (RC does not match with DEFAULT_CONFIG) and
12 shall remain in the Mobile Station Origination Attempt Substate if one of the
13 following conditions is true:
14 + FOR_RCr is not equal to the Radio Configuration associated with
15 DEFAULT_CONFIGr as specified in Table 3.7.2.3.2.21-2.
16 + REV_RCr is not equal to the Radio Configuration associated with

17 DEFAULT_CONFIGr as specified in Table 3.7.2.3.2.21-2.
18 − If the mobile station does not support either of the Radio Configurations
19 (FOR_RC or REV_RC), the mobile station shall send a Mobile Station Reject
20 Order with the ORDQ field set to ‘00000110’ (capability not supported by the
21 mobile station) and remain in the Mobile Station Origination Attempt Substate.
22 − If CH_INDr = ‘01’ and the mobile station does not support the Fundamental
24 ORDQ field set to ‘00000110’ (capability not supported by the mobile
25 station) and remain in the Mobile Station Origination Attempt Substate.
26 − If CH_INDr = ‘10’ and the mobile station does not support the Dedicated
27 Control Channel, the mobile station shall send a Mobile Station Reject Order
28 with the ORDQ field set to ‘00000110’ (capability not supported by the
29 mobile station) and remain in the Mobile Station Origination Attempt Substate.
30 − If CH_INDr = ‘11’ and the mobile station does not support the Dedicated
31 Control Channel and Fundamental Channel concurrently, the mobile station
32 shall send a Mobile Station Reject Order with the ORDQ field set to
35 − If FREQ_INCLr equals ‘1’ and if the band class (BAND_CLASSr) is not
36 supported by the mobile station, the mobile station shall send a Mobile
37 Station Reject Order with ORDQ field set to ‘00000110’ (capability not
38 supported by the mobile station) and remain in the Mobile Station Origination
40 − If the mobile station does not send a Mobile Station Reject Order as specified
41 above, it shall continue to perform the actions specified below.
2-228
3GPP2 C.S0005-A v6.0
1 − If FREQ_INCLr equals ‘1’, the mobile station shall set
2 + CDMABANDs = BAND_CLASSr
3 + CDMACHs = CDMA_FREQr
4 − The mobile station shall store the bypass indicator

5 (BYPASS_ALERT_ANSWERs = BYPASS_ALERT_ANSWERr).
6 − The mobile station shall store granted mode (GRANTED_MODEs =

7 GRANTED_MODEr )
8 − The mobile station shall store the default configuration (DEFAULT_CONFIGs

9 = DEFAULT_CONFIGr).
10 − The mobile station shall store the Forward Traffic Channel Radio
11 Configuration (FOR_RCs = FOR_RCr) and the Reverse Traffic Channel Radio
12 Configuration (REV_RCs = REV_RCr).

14 FRAME_OFFSETr).
15 − The mobile station shall store the message encryption mode indicator
16 (ENCRYPT_MODEs = ENCRYPT_MODEr).
18 below:
20 the following:
25 CMEAKEY in the mobile station, associated with the AUTHR of the
26 Origination Message, and EXT_ENCRYPT_SEQ[0] and
28 in the Origination Message).
37 − If USE_NEW_KEYr is included and is set to ‘0’ then the mobile station


2-229
3GPP2 C.S0005-A v6.0
1 − The mobile station shall store the Forward power control subchannel relative
2 gain (FPC_SUBCHAN_GAINs = FPC_SUBCHAN_GAINr).
3 − The mobile station shall set RLGAIN_ADJs to RLGAIN_ADJr.
4 − The mobile station shall set REV_FCH_GATING_MODEs to

6 − The mobile station shall set REV_PWR_CNTL_DELAYs to

7 REV_PWR_CNTL_DELAYr if REV_PWR_CNTL_DELAY_INCLr is equal to ‘1’.

10 − The mobile station shall store the channel indicator (CH_INDs = CH_INDr)
11 and the mobile station shall perform the following actions:
12 + If CH_INDr equals ‘01’, the mobile station shall set
13 FPC_FCH_INIT_SETPTs to FPC_FCH_INIT_SETPTr,
14 FPC_FCH_CURR_SETPTs to FPC_FCH_INIT_SETPTs, FPC_FCH_FERs to
15 FPC_FCH_FERr, FPC_FCH_MIN_SETPTs to FPC_FCH_MIN_SETPTr,
18 2. Then for each included member of the Active Set, the mobile station
19 shall store the following:
20 ο Set the PILOT_PN field to PILOT_PNr.

23 following:
24 ◊ Set the PILOT_REC_TYPE field of PILOT_REC to

25 PILOT_REC_TYPEr.

27 TD_POWER_LEVEL field of PILOT_REC to TD_POWER_LEVELr
28 and set the TD_MODE field of PILOT_REC to TD_MODEr.
29 ◊ If PILOT_REC_TYPEr is equal to ‘001’, the mobile station shall

33 WALSH_LENGTHr.

38 WALSH_LENGTHr.
2-230
3GPP2 C.S0005-A v6.0








21 WALSH_LENGTHr.

25 AUX_PILOT_WALSH1r with the Walsh Code length specified
26 by WALSH_LENGTH1r; otherwise, set the AUX_PILOT_QOF1
27 field of PILOT_REC to QOFr and set the
30 WALSH_LENGTHr.

39 WALSH_LENGTHr.
2-231
3GPP2 C.S0005-A v6.0

5 ο If 3X_FCH_LOW_INCLr equals ‘1’, set the QOF_MASK_ID_FCH_LOW

6 field to QOF_MASK_ID_FCH_LOWr and the CODE_CHAN_FCH_LOW
7 field to CODE_CHAN_FCH_LOWr. Otherwise, set the
8 QOF_MASK_ID_FCH_LOW field to QOF_MASK_ID_FCHr and the
9 CODE_CHAN_FCH_LOW to CODE_CHAN_FCHr.


16 FPC_DCCH_INIT_SETPTs to FPC_DCCH_INIT_SETPTr,
17 FPC_DCCH_CURR_SETPTs to FPC_DCCH_INIT_SETPTs,
18 FPC_DCCH_FERs to FPC_DCCH_FERr, FPC_DCCH_MIN_SETPTs to
19 FPC_DCCH_MIN_SETPTr, FPC_DCCH_MAX_SETPTs to
20 FPC_DCCH_MAX_SETPTr, and FPC_PRI_CHANs to ‘1’ if the mobile station
21 supports any Radio Configuration greater than 2. Then for each included
22 member of the Active Set, the mobile station shall store the following:
24 ο Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC_INCL. If

25 ADD_PILOT_REC_INCL is equal to ‘1’, the mobile station shall store
26 the following:

28 PILOT_REC_TYPEr.


36 WALSH_LENGTHr.
2-232
3GPP2 C.S0005-A v6.0

3 WALSH_LENGTHr.








24 WALSH_LENGTHr.

33 WALSH_LENGTHr.
2-233
3GPP2 C.S0005-A v6.0

9 WALSH_LENGTHr.
13 ο Set the DCCH_INCL field to DCCH_INCLr. If DCCH_INCLr equals ‘1’,

14 the mobile station shall store the following:
15 ◊ Set the CODE_CHAN_DCCH field to CODE_CHAN_DCCHr.
16 ◊ Set the QOF_MASK_ID_DCCH field to QOF_MASK_ID_DCCHr.

18 included member of the Active Set, the mobile station shall store the
19 following:
20 ο If 3X_DCCH_LOW_INCLr equals ‘1’, set the

21 QOF_MASK_ID_DCCH_LOW field to QOF_MASK_ID_DCCH_LOWr and
22 the CODE_CHAN_DCCH_LOW field to CODE_CHAN_DCCH_LOWr.
23 Otherwise, set the QOF_MASK_ID_DCCH_LOW field to
24 QOF_MASK_ID_FCHr and the CODE_CHAN_DCCH_LOW to
25 CODE_CHAN_FCHr.
26 ο If 3X_DCCH_HIGH_INCLr equals ‘1’, set the

27 QOF_MASK_ID_DCCH_HIGH field to QOF_MASK_ID_DCCH_HIGHr
28 and the CODE_CHAN_DCCH_HIGH field to
29 CODE_CHAN_DCCH_HIGHr. Otherwise, set the
2-234
3GPP2 C.S0005-A v6.0

2 FPC_FCCH_INIT_SETPTs to FPC_FCH_INIT_SETPTr,
3 FPC_FCH_CURR_SETPTs to FPC_FCH_INIT_SETPTs, FPC_FCH_FERs to
4 FPC_FCH_FERr, FPC_FCH_MIN_SETPTs to FPC_FCH_MIN_SETPTr,
5 FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr,
6 FPC_DCCH_INIT_SETPTs to FPC_DCCH_INIT_SETPTr,
7 FPC_DCCH_CURR_SETPTs to FPC_DCCH_INIT_SETPTs,
8 FPC_DCCH_FERs to FPC_DCCH_FERr, FPC_DCCH_MIN_SETPTs to
9 FPC_DCCH_MIN_SETPTr, FPC_DCCH_MAX_SETPTs to
10 FPC_DCCH_MAX_SETPTr and FPC_PRI_CHANs to FPC_PRI_CHANr.
11 Then for each included member of the Active Set, the mobile station shall
14 ο Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC. If

15 ADD_PILOT_REC_INCL is equal to ‘1’, the mobile station shall store
16 the following:

18 PILOT_REC_TYPEr.


26 WALSH_LENGTHr.

31 WALSH_LENGTHr.



2-235
3GPP2 C.S0005-A v6.0





13 WALSH_LENGTHr.

22 WALSH_LENGTHr.

31 WALSH_LENGTHr
32 ο Set the PWR_COMB_IND field to PWR_COMB_INDr
35 ο Set the CODE_CHAN_DCCH field to CODE_CHAN_DCCHr.
36 ο Set the QOF_MASK_ID_DCCH field to QOF_MASK_ID_DCCHr.

2-236
3GPP2 C.S0005-A v6.0
1 ο If 3X_FCH_LOW_INCLr equals ‘1’, set the QOF_MASK_ID_FCH_LOW

2 field to QOF_MASK_ID_FCH_LOWr and the CODE_CHAN_FCH_LOW
3 field to CODE_CHAN_FCH_LOWr. Otherwise, set the
4 QOF_MASK_ID_FCH_LOW field to QOF_MASK_ID_FCHr and the
5 CODE_CHAN_FCH_LOW to CODE_CHAN_FCHr.



14 QOF_MASK_ID_DCCH_LOW field to QOF_MASK_ID_DCCH_LOWr and
15 the CODE_CHAN_DCCH_LOW field to CODE_CHAN_DCCH_LOWr.
16 Otherwise, set the QOF_MASK_ID_DCCH_LOW field to
17 QOF_MASK_ID_FCHr and the CODE_CHAN_DCCH_LOW to
18 CODE_CHAN_FCHr.

20 QOF_MASK_ID_DCCH_HIGH field to QOF_MASK_ID_DCCH_HIGHr
21 and the CODE_CHAN_DCCH_HIGH field to
22 CODE_CHAN_DCCH_HIGHr. Otherwise, set the
25 − The mobile station shall initialize CODE_CHAN_LIST as described in 2.6.8,

26 and shall set SERV_NEGs to enabled.
27 − If FREQ_INCLr equals ‘1’, the mobile station shall then tune to the new
28 frequency assignment.
29 − The mobile station shall then enter the Traffic Channel Initialization Substate
30 of the Mobile Station Control on the Traffic Channel State.
31 6.7. Feature Notification Message: If RELEASEr is equal to ‘1’, the mobile station
32 shall enter the Mobile Station Idle State or the System Determination Substate of the
33 Mobile Station Initialization State with a release indication (see 2.6.1.1).
34 7.8. Intercept Order: The mobile station shall enter the Mobile Station Idle State.
2-237
3GPP2 C.S0005-A v6.0
9 11.12. PACA Message: If P_REV_IN_USEs is less than or equal to four and the mobile
10 station does not support PACA capability, the mobile station shall send a Mobile
14 • If PACAs is equal to disabled, the mobile station shall perform the following
15 actions:
16 − If the purpose of the message is to respond to an Origination Message

17 (PURPOSEr is equal to ‘0000’), the mobile station shall perform the following
18 actions:
19 + The mobile station shall set PACAs to enabled and shall set PACA_SIDs to
20 SIDs.
21 + The mobile station shall set the PACA state timer to the duration shown
22 in Table 3.7.2.3.2.20-2 corresponding to the value of PACA_TIMEOUTs.
23 + The mobile station should indicate to the user that the call has been
24 queued as a PACA call, and should indicate the current queue position
25 (Q_POSr) of the call.
26 + The mobile station shall enter the Mobile Station Idle State.
27 − If the purpose of the message is to cancel the PACA call (PURPOSEr is equal
28 to ‘0011’), the mobile station shall perform the following actions:
29 + The mobile station shall set PACAs to disabled and PACA_CANCEL to ‘0’,
30 shall disable the PACA state timer, and should indicate to the user that
31 the PACA call has been canceled.
33 − If the purpose of the message is anything else (PURPOSEr is not equal to
34 ‘0000’ or ‘0011’), the mobile station shall ignore the message. The mobile
35 station shall remain in the Mobile Station Origination Attempt Substate.
36 • If PACAs is equal to enabled, the mobile station shall perform the following
37 actions:
38 − If the purpose of the message is to respond to an Origination Message
39 (PURPOSEr is equal to ‘0000’), the mobile station shall perform the following
40 actions:
2-238
3GPP2 C.S0005-A v6.0
1 + The mobile station should indicate to the user that the PACA call is still
2 queued, and should indicate to the user the current queue position
3 (Q_POSr) of the call.
7 − If the purpose of the message is to provide the queue position of the PACA
8 call (PURPOSEr is equal to ‘0001’), the mobile station shall perform the
10 + The mobile station should indicate to the user that the PACA call is still
11 queued, and should indicate the current queue position (Q_POSr) of the
12 call.
16 − If the purpose of the message is to instruct the mobile station to re-originate

17 the PACA call (PURPOSEr is equal to ‘0010’), the mobile station shall remain
18 in the Mobile Station Origination Attempt Substate.
19 − If the purpose of the message is to cancel the PACA call (PURPOSEr is equal
20 to ‘0011’), the mobile station shall perform the following actions:
21 + The mobile station shall set PACAs to disabled, shall disable the PACA
22 state timer, and should indicate to the user that the PACA call has been
23 canceled.

26 • If ORDQr = ‘00000101’, the mobile station shall set ROAM_INDIs = to
29 - The mobile station shall set ROAM_INDIs = ROAM_INDIr and should display
30 the roaming condition.
31 - The mobile station shall set C_SIG_ENCRYPT_MODEs = to

2-239
3GPP2 C.S0005-A v6.0

4 ENC_KEYs to the most recently generated CMEAKEY in the mobile
5 station,associated with the AUTHR of the Registration Message, and
14 14.15. Release Order: If NDSS_ORIGs is equal to enabled, the mobile station shall set
18 indication (see 2.6.1.1). If the mobile station enters the Mobile Station Idle State, and
19 if PACAs is equal to enabled, the mobile station shall set PACAs to disabled and
22 15.16. Reorder Order: If NDSS_ORIGs is equal to enabled, the mobile station shall set
24 has been canceled. If PACAs is equal to enabled, the mobile station shall set PACAs
25 to disabled and PACA_CANCEL to ‘0’, shall disable the PACA state timer, and should
26 indicate to the user that the PACA call has been canceled. The mobile station shall
28 16.17. Retry Order: This order indicates that the origination is rejected and specifies the
29 time before which the mobile station shall not send an Origination Message
30 containing the same packet data Service Option. The mobile station shall process
31 the order as follows:
34 or ‘011’.
35 • If RETRY_TYPEr is equal to ‘001’, then the mobile station shall perform the
36 following:
39 − If RETRY_DELAYr is not equal to ‘00000000’ the mobile station shall set

40 RETRY_DELAYs as follows:
2-240
3GPP2 C.S0005-A v6.0


9 + If NDSS_ORIGs is equal to enabled, the mobile station shall set

10 NDSS_ORIGs to disabled, and should indicate to the user that the call
11 origination has been canceled. If PACAs is equal to enabled, the mobile
12 station shall set PACAs to disabled and PACA_CANCEL to ‘0’, shall
13 disable the PACA state timer, and should indicate to the user that the
14 PACA call has been canceled.
17 as follows:

25 KEY_SEQ_NEWs-p by one (modulo 16).If ENC_KEY_SIZEr is included, the mobile
26 station shall set ENC_KEY_SIZEs to ENC_KEY_SIZEr.
30 follows:

34 mobile station).
35 • If DELETE TMSIr is equal to ‘1’, the mobile station shall set all the bits of
37 • The mobile station shall disable the full-TMSI timer.

2-241
3GPP2 C.S0005-A v6.0
1 • If RECORD_TYPEr is ‘00000000’, the mobile station shall set RETURN_IF_FAILs

2 = RETURN_IF_FAILr, and enter the System Determination Substate of the Mobile
3 Station Initialization State with an NDSS off indication (see 2.6.1.1); otherwise:
4 – if REDIRECT_TYPEr is ‘0’, the mobile station shall store the redirection
5 record received in the message as REDIRECT_RECs and shall enter the
6 System Determination Substate of the Mobile Station Initialization State with
7 a redirection indication (see 2.6.1.1).
8 − if REDIRECT_TYPEr is ‘1’, the mobile station shall store the redirection
9 record received in the message as REDIRECT_RECs and shall enable
10 NDSS_ORIGs, and shall record the dialed digits ([if any]). The mobile station
11 shall enter the System Determination Substate of the Mobile Station
12 Initialization State with a redirection indication (see 2.6.1.1).
28 message specifies a band class or a band class and an operating mode which are not
39 code as follows:
2-242
3GPP2 C.S0005-A v6.0
5 TMSI_CODEr.
11 23.24. Any other message: If the mobile station receives any other message specified in
13 other messages.
15 • If ORDQr = ‘00000000’, the mobile station shall set KEYs to NULL and set
16 C_SIG_ENCRYPT_MODE to ‘000’. The mobile station shall re-originate by
17 sending a new Origination Message.
24 If the mobile station performs an access probe handoff or access handoff and receives any
25 of the following messages, it shall process the message as specified in 2.6.3.1.3:
26 • If the mobile station is currently monitoring the Paging Channel:
29 3. Neighbor List Message
31 5. Extended Neighbor List Message
35 • If the mobile station is currently monitoring the Primary Broadcast Control Channel:
2-243
3GPP2 C.S0005-A v6.0
4 2.6.3.6 Registration Access Substate
5 In this substate, the mobile station sends a Registration Message. If the base station
6 responds with an authentication request, the mobile station responds in this substate.
7 Upon entering the Registration Access Substate, the mobile station shall send the
8 Registration Message.
14 2.1.1.2.2.1 of [4]).
18 to a message received from the base station) other than the Registration Message, Layer 3
19 shall indicate to Layer 2 that the type of the message is a request other than a registration
20 request or a message transmission request (see 2.1.1.2.2.1 of [4]).
21 When transmitting an autonomous Registration Message (i.e., it is not sent as a response to
22 a Registration Request Order received from the base station), Layer 3 shall indicate to Layer
23 2 that the type of the message is a request that is a registration (see 2.1.1.2.2.1 of [4]).
34 State.
36 station in this substate, it shall then enter the Mobile Station Idle State unless:
2-244
3GPP2 C.S0005-A v6.0
1 • If the registration access was initiated due to a user direction to power down, the
2 mobile station shall update registration variables as specified in 2.6.5.5.3.3 and may
3 power down.
4 • If the mobile station has included the ENC_SEQ_H field in the Registration Message,
5 then the mobile station should set this field to one plus the previous value of this
6 field (if any).
7 • If the mobile station has included the ENC_SEQ_H field in the Registration
8 Message, then the mobile station shall set EXT_ENC_SEQs to 265 × ENC_SEQ_H.
9 • If the a message received from the base station requires a response, the mobile
10 station shall send a response to the message in this substate.
11 If the mobile station receives confirmation of delivery of the Registration Message, the
12 mobile station shall update its registration variables as specified in 2.6.5.5.3.1.
13 If the mobile station is directed by the user to originate a call, the mobile station may
14 process the origination request as follows:

20 • The mobile station shall enter the Mobile Station Origination Attempt Substate with
21 an origination indication.
24 If the mobile station receives a mobile-station-addressed page, the mobile station may
25 determine if there is a page match (see 2.6.2.3). If a match is declared, the mobile station

29 • The mobile station shall enter the Page Response Substate.
2-245
3GPP2 C.S0005-A v6.0
1 1. Authentication Challenge Message: If the registration access was initiated due to a

2 user direction to power down, the mobile station shall ignore the message;
3 otherwise, the mobile station shall respond to the message as specified in
4 2.3.12.1.4, regardless of the value of AUTHs.
5 2. Base Station Challenge Confirmation Order: If the registration access was initiated
6 due to a user direction to power down, the mobile station shall ignore the message;
7 otherwise, the mobile station shall respond to the message as specified in
8 2.3.12.1.5.
16 34. Data Burst Message
17 45. Feature Notification Message
18 56. Local Control Order
19 67. Lock Until Power-Cycled Order: The mobile station shall disable its transmitter and
20 record the reason for the Lock Until Power-Cycled Order in the mobile station’s semi-
21 permanent memory (LCKRSN_Ps-p equals the least significant four bits of ORDQr).
22 The mobile station should notify the user of the locked condition. The mobile
23 station shall enter the System Determination Substate of the Mobile Station
28 78. Maintenance Required Order: The mobile station shall record the reason for the
33 89. PACA Message: If P_REV_IN_USEs is less than or equal to four and the mobile
38 If PACAs is equal to disabled, the mobile station shall send a Mobile Station Reject
39 Order with the ORDQ field set to ‘00000010’ (message not accepted in this state).
2-246
3GPP2 C.S0005-A v6.0
1 • If the purpose of the message is to respond to an Origination Message

2 (PURPOSEr is equal to ‘0000’), the mobile station shall send a Mobile Station
3 Reject Order with the ORDQ field set to ‘00000010’ (message not accepted in this
4 state).
5 • If the purpose of the message is to provide the queue position of the PACA call
6 (PURPOSEr is equal to ‘0001’), the mobile station shall set the PACA state timer
7 to the duration shown in Table 3.7.2.3.2.20-2 corresponding to the value of
8 PACA_TIMEOUTs, should indicate to the user that the PACA call is still queued,
9 and should indicate to the user the current queue position (Q_POSr) of the call.
10 • If the purpose of the message is to instruct the mobile station to re-originate the
11 PACA call (PURPOSEr is equal to ‘0010’), Layer 3 shall send an L2-
12 Supervision.Request primitive to Layer 2 to abort any access attempt in
13 progress, shall set the PACA state timer to the duration shown in Table
14 3.7.2.3.2.20-2 corresponding to the value of PACA_TIMEOUTs, and shall enter
15 the Mobile Station Origination Attempt Substate with a PACA response indication.
16 • If the purpose of the message is to cancel the PACA call (PURPOSEr is equal to
17 ‘0011’), the mobile station shall set PACAs to disabled and PACA_CANCEL to ‘0’,
18 shall disable the PACA state timer, and should indicate to the user that the
20 910. Registration Accepted Order:
28 -If USE_NEW_KEYr is not included, or is included and is set to ‘1’, the mobile

2-247
3GPP2 C.S0005-A v6.0
1 • The mobile station shall then enter the Mobile Station Idle State.
2 1011. Registration Rejected Order: This order indicates that normal service is not available
3 on this system. The mobile station shall disable the full-TMSI timer. If the received
4 order specifies to delete the TMSI (ORDQ = ‘00000100’), the mobile station shall set
5 all the bits of the TMSI_CODEs-p to ‘1’. The mobile station shall enter the System
6 Determination Substate of the Mobile Station Initialization State with a registration
7 rejected indication (see 2.6.1.1).
8 1112. Release Order: If NDSS_ORIGs is equal to enabled, the mobile station shall set
12 indication (see 2.6.1.1). If the mobile station enters the Mobile Station Idle State, and
13 if PACAs is equal to enabled, the mobile station shall set PACAs to disabled and
16 1213. Retry Order: The mobile station shall process the message as follows:
19 or ‘011’.




33 1314. Security Mode Command Message: The mobile station shall process the message as
34 follows:
2-248
3GPP2 C.S0005-A v6.0
1 • If USE_NEW_KEYr is not included, or is included and is set to ‘1’, the

5 mobile station shall store KEY_SIZEr in KEY_SIZEs. The mobile station
9 • If USE_NEW_KEYr is included and is set to ‘0’, then the mobile station

10 shall use KEYs[KEY_SEQr] as the session key.
11
12 1415. Service Redirection Message: The mobile station shall process the message as
13 follows:

17 mobile station).

27 1516. SSD Update Message: If the registration access was initiated due to a user direction
28 to power down, the mobile station shall ignore the message. Otherwise, the mobile
29 station shall respond to the message as specified in 2.3.12.1.5.
30 1617. Status Request Message: The mobile station shall disable the System Access State
31 timer and respond to the message. If P_REV_IN_USEs is less than or equal to three,
32 the mobile station shall respond with a Status Response Message. If
42 class (BAND_CLASSr) and operating mode (OP_MODEr) in the response.
2-249
3GPP2 C.S0005-A v6.0
1 If the message specifies a band class or a band class and an operating mode which
2 are not supported by the mobile station, the mobile station shall send a Mobile
3 Station Reject Order with ORDQ set to ‘00000110’ (message requires a capability that
4 is not supported by the mobile station). If the response to this message exceeds the
11 1718. TMSI Assignment Message: The mobile station shall store the TMSI zone and code
12 as follows:
19 TMSI_CODEr.
24 1819. User Zone Reject Message
27 other messages.
35 2.6.3.7 Mobile Station Message Transmission Substate
36 In this substate, the mobile station sends a Data Burst Message or a Device Information
37 Message. If the base station responds with an authentication request, the mobile station
38 responds in this substate.
39 Support of this substate is optional.
2-250
3GPP2 C.S0005-A v6.0
6 2.1.1.2.2.1 of [4]).
10 to a message received from the base station) other than the Data Burst Message, Layer 3
11 shall indicate to Layer 2 that the message is a request other than a registration request or a
12 message transmission request (see 2.1.1.2.2.1 of [4]).
13 When transmitting an autonomous Data Burst Message, Layer 3 shall indicate to Layer 2
14 that the type of the message is a request that is a message transmission (see 2.1.1.2.2.1 of
15 [4]).
16 Upon entering the Mobile Station Message Transmission Substate, the mobile station shall
17 transmit the message as follows:
18 • The mobile station shall exit the Mobile Station Message Transmission Substate, shall
19 enter either the Mobile Station Idle State or the System Determination Substate with
20 an ACCT blocked indication, and should indicate to the user that the message
21 transmission has terminated if all of the following conditions are true:
22 – P_REV_IN_USEs is greater than six,
23 – ACCT is enabled for the service option number associated with the data burst
24 message, due to either of the following two conditions:
25 + The service option number associated with the data burst message is equal
26 to an ACCT_SO entry in ACCT_SO_LIST, or
27 + The service option group number of the service option associated with the
28 data burst message is equal to an ACCT_SO_GRP entry in
29 ACCT_SO_GRP_LIST.
30 • If the mobile station entered this substate with a message transmission indication,
31 the mobile station shall transmit the Data Burst Message to the base station.
32 • If the mobile station entered this substate with a hook status indication, the mobile
33 station shall set the autonomous message timer equal to AUTO_MSG_INTERVALs
34 and shall start the timer. The mobile station shall transmit the Device Information
35 Message to the base station, with the RECORD_TYPE field of the message set to
36 00100000 and the Hook Indicator field set to the current hook status.
2-251
3GPP2 C.S0005-A v6.0
7 State.
8 If the mobile station receives confirmation of any message sent by the mobile station in this
9 substate, it shall send a response in this substate if required and shall then enter the
10 Mobile Station Idle State.
14 determine whether there is a page match (see 2.6.2.3). If a match is declared, the mobile

18 • The mobile station shall enter the Page Response Substate.
19 • If the mobile station entered this substate with a message transmission indication,
20 the mobile station may store the Data Burst Message for later transmission.
2-252
3GPP2 C.S0005-A v6.0
23 78. PACA Message: If P_REV_IN_USEs is less than or equal to four and the mobile
28 If PACAs is equal to disabled, the mobile station shall send a Mobile Station Reject
29 Order with the ORDQ field set to ‘00000010’ (message not accepted in this state).
31 • If the purpose of the message is to respond to an Origination Message

32 (PURPOSEr is equal to ‘0000’), the mobile station shall send a Mobile Station
33 Reject Order with the ORDQ field set to ‘00000010’ (message not accepted in this
34 state).
35 • If the purpose of the message is to provide the queue position of the PACA call
36 (PURPOSEr is equal to ‘0001’), the mobile station shall set the PACA state timer
37 to the duration shown in Table 3.7.2.3.2.20-2 corresponding to the value of
38 PACA_TIMEOUTs, should indicate to the user that the PACA call is still queued,
39 and should indicate to the user the current queue position (Q_POSr) of the call.
2-253
3GPP2 C.S0005-A v6.0
1 • If the purpose of the message is to instruct the mobile station to re-originate the
2 PACA call (PURPOSEr is equal to ‘0010’), Layer 3 shall send an L2-
3 Supervision.Request primitive to Layer 2 to abort any access attempt in
4 progress, shall set the PACA state timer to the duration shown in Table
5 3.7.2.3.2.20-2 corresponding to the value of PACA_TIMEOUTs, and shall enter
6 the Mobile Station Origination Attempt Substate with a PACA response indication.
7 • If the purpose of the message is to cancel the PACA call (PURPOSEr is equal to
8 ‘0011’), the mobile station shall set PACAs to disabled and PACA_CANCEL to ‘0’,
9 shall disable the PACA state timer, and should indicate to the user that the



2-254
3GPP2 C.S0005-A v6.0

3 or ‘011’.




18 follows:

31 follows:

35 mobile station).
2-255
3GPP2 C.S0005-A v6.0

7 1314. SSD Update Message: The mobile station shall respond to the message as specified
8 in 2.3.12.1.5.
21 class (BAND_CLASSr) and operating mode (OP_MODEr) in the response.
23 is not supported by the mobile station, the mobile station shall send a Mobile Station
24 Reject Order with ORDQ set to ‘00000110’ (message requires a capability that is not
33 as follows:
40 TMSI_CODEr.
41 The mobile station shall set the TMSI expiration time by setting
42 TMSI_EXP_TIMEs-p to TMSI_EXP_TIMEr. The mobile station shall disable the
2-256
3GPP2 C.S0005-A v6.0
1 full-TMSI timer. The mobile station shall then respond with a TMSI Assignment
2 Completion Message within T56m seconds.
5 other messages.
13 2.6.3.8 PACA Cancel Substate
14 In this substate, the mobile station sends a PACA Cancel Message. If the base station
15 responds with an authentication request, the mobile station responds in this substate.
16 Upon entering the PACA Cancel Substate, the mobile station shall transmit the PACA Cancel
17 Message.
23 2.1.1.2.2.1 of [4]).
29 request (see 2.1.1.2.2.1 of [4]).
32 the Forward Common Control Channel (see 2.6.2.1.1.4 2.6.3.1.8), it shall declare an access
33 attempt failure and update its registration variables as specified in 2.6.5.5.3.2, disable its
34 transmitter and enter the Mobile Station Idle State. If the mobile station receives
35 confirmation of any message sent by the mobile station in this substate, it shall send a
36 response in this substate if required and shall then enter the Mobile Station Idle State.
38 determine if there is a page match (see 2.6.2.3). If a match is declared, Layer 3 shall send
39 an L2-Supervision.Request primitive to Layer 2 to abort any access attempt in progress and
40 shall enter the Page Response Substate.
2-257
3GPP2 C.S0005-A v6.0
38 78. PACA Message: The mobile station shall send a Mobile Station Reject Order with the
39 ORDQ field set to ‘00000010’ (message not accepted in this state).
2-258
3GPP2 C.S0005-A v6.0



31 or ‘011’.



2-259
3GPP2 C.S0005-A v6.0

7 follows:

20 follows:

24 mobile station).

34 1314. SSD Update Message: The mobile station shall respond to the message as specified
35 in 2.3.12.1.5.
2-260
3GPP2 C.S0005-A v6.0
7 class (BAND_CLASSr) and operating mode (OP_MODEr) in the Status Response
8 Message.
10 is not supported by the mobile station, the mobile station shall send a Mobile Station
11 Reject Order with ORDQ set to ‘00000110’ (message requires a capability that is not
20 as follows:
27 TMSI_CODEr.
34 other messages.

2-261
3GPP2 C.S0005-A v6.0
1 2.6.4 Mobile Station Control on the Traffic Channel State
2 In this state, the mobile station communicates with the base station using the Forward and
3 Reverse Traffic Channels.
4 As illustrated in Figure 2.6.4-1, the Mobile Station Control on the Traffic Channel State
5 consists of the following substates:
6 • Traffic Channel Initialization Substate - In this substate, the mobile station verifies
7 that it can receive the Forward Traffic Channel and begins transmitting on the
8 Reverse Traffic Channel.
9 • Traffic Channel Substate - In this substate, the mobile station exchanges Traffic
10 Channel frames with the base station in accordance with the current service
11 configuration. The mobile station may perform the gating operation of Reverse Pilot
12 Channel. While in this substate, one or more Call Control instances can be
13 activated (see 2.6.10).
14 • Release Substate - In this substate, the mobile station disconnects the calls and the
16
2-262
3GPP2 C.S0005-A v6.0
(Enter from System Access State)
Traffic
Channel
Initialization
Substate
(2.6.4.2)
Layer 3 receives a forward dedicated channel acquired indication from Layer 2
Traffic Channel Substate

(2.6.4.3)
Last call is to be released (initiated by

Mobile Station user or Release Order/
Extended Release Message received from
base station Receives 'enter traffic
channel substate'
indication
Release
Substate
(2.6.4.4)
System Determination Substate

of the Mobile Station
Initialization State
2 Figure 2.6.4-1. Mobile Station Control on the Traffic Channel State
2-263
3GPP2 C.S0005-A v6.0
1 2.6.4.1 Special Functions and Actions
2 The mobile station performs special functions and actions in one or more of the substates of
4 2.6.4.1.1 Forward Traffic Channel Power Control

5 The mobile station uses FPC_MODE_NO_SCHs as FPC_MODEs except during the forward
6 Supplemental Channel assignment interval. During the forward Supplemental Channel
7 assignment interval, the mobile station uses FPC_MODE_SCHs as FPC_MODEs.
8 To support Forward Traffic Channel power control, the mobile station reports frame error
9 rate statistics to the base station. If the base station enables periodic reporting, the mobile
10 station reports frame error rate statistics at specified intervals. If the base station enables
11 threshold reporting, the mobile station reports frame error rate statistics when the frame
12 error rate reaches a specified threshold.9
13 The mobile station shall maintain the following frame counters:

14 • A counter (TOT_FRAMESs) for the total number of frames received on the Forward
15 Fundamental Channel.
16 • A counter (BAD_FRAMESs) for the number of bad frames detected on the Forward
18 • A counter (DCCH_TOT_FRAMESs) for the total number of frames received on the
19 Forward Dedicated Control Channel, when the Dedicated Control Channel is
20 assigned.
21 • A counter (DCCH_BAD_FRAMESs] for the total number of bad frames received on
22 the Forward Dedicated Control Channel, when the Dedicated Control Channel is
23 assigned.
24 The mobile station shall maintain the following counters for each Supplemental Channel
25 assigned, if FOR_SCH_FER_REPs is equal to ‘1’:
26 • A counter (SCH_TOT_FRAMESs) for the number of frames received on the assigned

27 Supplemental Channel.
28 • A counter (SCH_BAD_FRAMESs) for the number of bad frames received on the
29 assigned Supplemental Channel.
30 The mobile station shall increment the counter by 1 at every 20 ms interval if a 20ms frame
31 or at least one 5ms frame is received from the Forward Fundamental Channel or Dedicated
32 Control Channel:
9 Periodic reporting and threshold reporting may be independently enabled or disabled by the base
station.
2-264
3GPP2 C.S0005-A v6.0
1 • If the received frame is from the Fundamental Channel, the mobile station shall
3 – Increment TOT_FRAMESs by 1.
4 – If the received 20ms frame is bad or one of the 5ms frames is bad, the mobile
5 station shall increment BAD_FRAMESs by 1.
6 • If the received frame is from the Forward Dedicated Control Channel, the mobile
8 – Increment DCCH_TOT_FRAMESs by 1.
9 – If the received 20ms frame is bad or one of the 5ms frames is bad, the mobile
10 station shall increment DCCH_BAD_FRAMESs by 1.
11 • If either
12 – PWR_THRESH_ENABLEs is equal to ‘1’ and if one of the following conditions is
13 true:
14 + The Fundamental Channel carries the Power Control Subchannel

15 [FPC_PRI_CHANs = ‘0’], and BAD_FRAMESs is equal to PWR_REP_THRESHs
16 or
17 + The Dedicated Control Channel carries the Power Control Subchannel

18 [FPC_PRI_CHANs = ‘1’], and DCCH_BAD_FRAMESs is equal to
19 PWR_REP_THRESHs.
20 or
21 – PWR_PERIOD_ENABLEs is equal to ‘1’ and if one of the following conditions is
22 true:
23 + The Fundamental Channel carries the Power Control Subchannel

24 [FPC_PRI_CHANs = ‘0’], and TOT_FRAMESs is equal to
25 (2(PWR_REP_FRAMESs/2) × 5), or
26 + The Dedicated Control Channel carries the Power Control Subchannel

27 [FPC_PRI_CHANs = ‘1’], and DCCH_TOT_FRAMESs is equal to
28 (2(PWR_REP_FRAMESs/2) × 5),
29 then the mobile station shall send a Power Measurement Report Message to the base
30 station. The mobile station should send the Power Measurement Report Message in
31 unassured mode. After sending a Power Measurement Report Message, the mobile
32 station shall set TOT_FRAMESs, BAD_FRAMESs to zero, and if the Dedicated
33 Control Channel is assigned, shall set DCCH_TOT_FRAMESs and
34 DCCH_BAD_FRAMESs to zero. The mobile station shall not increment the counters
35 for a period of PWR_REP_DELAYs × 4 frames following the first transmission of the
36 message.
37 • If FPC_PRI_CHANs is equal to ‘0’ and TOT_FRAMESs is equal to
38 (2(PWR_REP_FRAMESs/2) × 5), the mobile station shall perform the following:
39 – Set TOT_FRAMESs and BAD_FRAMESs to zero.
2-265
3GPP2 C.S0005-A v6.0
1 – Set DCCH_TOT_FRAMESs and DCCH_BAD_FRAMESs to zero, if the Dedicated

2 Control Channel is assigned.
3 • If FPC_PRI_CHANs is equal to ‘1’ and DCCH_TOT_FRAMESs is equal to
4 (2(PWR_REP_FRAMESs/2) × 5), the mobile station shall set
5 TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs, and DCCH_BAD_FRAMESs
6 to zero.
7 For each received frame from an assigned Supplemental Channel, the mobile station shall
8 perform the following, if FOR_SCH_FER_REPs is equal to ‘1’:
9 • Increment SCH_TOT_FRAMESs by 1.
10 • If the received frame is bad, increment SCH_BAD_FRAMESs by 1.
11 At the end of a burst on each assigned Supplemental Channel, if FOR_SCH_FER_REPs is

12 equal to ‘1’, the mobile station shall report the total number of frames received on this
13 Supplemental Channel (SCH_TOT_FRAMESs) and the bad frames detected
14 (SCH_BAD_FRAMESs) with the fields SCH_PWR_MEAS_FRAMES and
15 SCH_ERRORS_DETECTED in the Power Measurement Report Message respectively. After
16 sending the Power Measurement Report Message for the Supplemental Channel, the mobile
17 station shall set SCH_TOTAL_FRAMESs and SCH_BAD_FRAMESs of the reported SCH to
18 zero.
19 If both Forward Fundamental Channel and the Forward Dedicated Control Channel are
20 assigned to the mobile station, the mobile station shall perform the following:
21 • The mobile station shall set FPC_DELTA_SETPTs to (FPC_FCH_CURR_SETPTs –

22 FPC_DCCH_CURR_SETPTs).
23 • For each received frame, if |FPC_FCH_CURR_SETPTs – FPC_DCCH_CURR_SETPTs

24 – FPC_DELTA_SETPTs| is equal to or greater than its assigned threshold
25 FPC_SETPT_THRESHs, the mobile station shall send the Outer Loop Report Message
26 requiring acknowledgment to the base station, and the mobile station shall then set
27 FPC_DELTA_SETPTs to (FPC_FCH_CURR_SETPTs – FPC_DCCH_CURR_SETPTs).
28 For each of the supplemental channels assigned to the mobile station and FPC_MODEs is
29 set to ‘000’, the mobile station shall perform the following:
30 • The mobile station shall set FPC_DELTA_SCH_SETPTs to

31 (FPC_FCH_CURR_SETPTs – FPC_SCH_CURR_SETPTs) if FPC_PRI_CHANs is equal to
32 ‘0’.
34 (FPC_DCCH_CURR_SETPTs – FPC_SCH_CURR_SETPTs) if FPC_PRI_CHANs is equal
35 to ‘1’.
2-266
3GPP2 C.S0005-A v6.0
1 • For each received frame, if FPC_PRI_CHANs is equal to ‘0’ and

2 |FPC_FCH_CURR_SETPTs – FPC_SCH_CURR_SETPTs –
3 FPC_DELTA_SCH_SETPTs| is equal to or greater than its assigned threshold
4 FPC_SETPT_THRESH_SCHs, the mobile station shall send the Outer Loop Report
5 Message in assured mode, and the mobile station shall then set
6 FPC_DELTA_SCH_SETPTs to (FPC_FCH_CURR_SETPTs – FPC_SCH_CURR_SETPTs).
7 • For each received frame, if FPC_PRI_CHANs is equal to ‘1’ and

8 |FPC_DCCH_CURR_SETPTs – FPC_SCH_CURR_SETPTs –
9 FPC_DELTA_SCH_SETPTs| is equal to or greater than its assigned threshold
10 FPC_SETPT_THRESH_SCHs, the mobile station shall send the Outer Loop Report
11 Message in assured mode, and the mobile station shall then set
12 FPC_DELTA_SCH_SETPTs to (FPC_DCCH_CURR_SETPTs –
13 FPC_SCH_CURR_SETPTs).
14 If the Supplemental channels are assigned to the mobile station and FPC_MODEs is set to
15 ‘001’, ‘010’, ‘101’, or ‘110’, for each additional Forward Supplemental Channel other than
16 the Forward Supplemental Channel specified by FPC_SEC_CHANs, the mobile station shall

19 (FPC_SCH_CURR_SETPTs[FPC_SEC_CHANs] – FPC_SCH_CURR_SETPTs) for the
21 • For each received frame, if |FPC_SCH_CURR_SETPTs[FPC_SEC_CHANs] –
22 FPC_SCH_CURR_SETPTs – FPC_DELTA_SCH_SETPTs| is equal to or greater than
23 its assigned threshold FPC_SETPT_THRESH_SCHs, the mobile station shall send the
24 Outer Loop Report Message in assured mode, and the mobile station shall then set
25 FPC_DELTA_SCH_SETPTs to (FPC_SCH_CURR_SETPTs[FPC_SEC_CHANs] –
26 FPC_SCH_CURR_SETPTs).
27 2.6.4.1.1.1 Forward Traffic Channel Power Control Initialization
28 To initialize Forward Traffic Channel power control, the mobile station shall set
29 TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs, and DCCH_BAD_FRAMESs to zero.
30 The mobile station shall initialize the frame counters SCH_TOT_FRAMESs and
31 SCH_BAD_FRAMESs for each assigned Supplemental Channel to zero. The mobile station
32 shall initialize FOR_SCH_FER_REPs to zero.
33 2.6.4.1.1.2 Processing the Power Control Parameters Message

34 The mobile station shall store the following parameters from the Power Control Parameters
35 Message:

2-267
3GPP2 C.S0005-A v6.0
1 • Periodic report mode indicator

2 (PWR_PERIOD_ENABLEs = PWR_PERIOD_ENABLEr)
4 The mobile station shall set TOT_FRAMESs and BAD_FRAMESs to zero if FCH is assigned.
5 The mobile station shall set DCCH_TOT_FRAMESs and DCCH_BAD_FRAMESs to zero if
6 DCCH is assigned.
7 2.6.4.1.1.3 Processing the Power Control Message

8 The mobile station shall send a Mobile Station Reject Order with the ORDQ field set to
9 ‘00000110’ (message requires a capability that is not supported by the mobile station) if any
10 of the following conditions are detected:
11 • If the mobile station does not support any Radio Configuration greater than 2 and
12 FPC_MODEr is not supported by the mobile station.
13 • If the mobile station does not support Supplemental Channel and FPC_MODEr is set
14 to the ‘001’, ‘010’, ‘101’, or ‘110’.
15 • If PWR_CNTL_STEPr corresponds to a power control step size (see 2.1.2.3.2 of [2]) is
16 not supported by the mobile station.
18 ‘00000111’ (message cannot be handled by the current mobile station configuration) if any
20 • FPC_PRI_CHANr is set to ‘1’ and only the Fundamental Channel is assigned.
21 • FPC_PRI_CHANr is set to ‘0’ and only the Dedicated Control Channel is assigned.
22 If none of the above conditions are true, the mobile station shall process the message as
23 follows at the action time (see 2.6.4.1.5) specified in the message:
24 • The mobile station shall store the power control step size (PWR_CNTL_STEPs =
25 PWR_CNTL_STEPr).
26 • If FPC_INCLr is equal to ‘1’, the mobile station shall perform the following:
27 – The mobile station shall set FPC_MODE_NO_SCHs = FPC_MODEr.
28 – The mobile station shall set FPC_MODEs = FPC_MODE_NO_SCHs if there is no

29 forward Supplemental Channel burst in progress (see 2.6.6.2.5.1.1).
30 – The mobile station shall set FPC_PRI_CHANs to FPC_PRI_CHANr
31 – If FPC_OLPC_FCH_INCL is equal to ‘1’, the mobile station shall:

32 + Set FPC_FCH_FERs to FPC_FCH_FERr.
33 + If FPC_FCH_MIN_SETPTr is not equal to ‘11111111’, set

34 FPC_FCH_MIN_SETPTs to FPC_FCH_MIN_SETPTr; otherwise, set
35 FPC_FCH_MIN_SETPTs to FPC_FCH_CURR_SETPTs.
2-268
3GPP2 C.S0005-A v6.0
1 + If FPC_FCH_MAX_SETPTr is not equal to ‘11111111’, set

2 FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr; otherwise, set
3 FPC_FCH_MAX_SETPTs to FPC_FCH_CURR_SETPTs.
4 – If FPC_OLPC_DCCH_INCL is equal to ‘1’, the mobile station shall:

5 + Set FPC_ DCCH_FERs to FPC_DCCH_FERr.
6 + If FPC_DCCH_MIN_SETPTr is not equal to ‘11111111’, set

7 FPC_DCCH_MIN_SETPTs to FPC_DCCH_MIN_SETPTr; otherwise, set
8 FPC_DCCH_MIN_SETPTs to FPC_DCCH_CURR_SETPTs.
9 + If FPC_DCCH_MAX_SETPTr is not equal to ‘11111111’, set

10 FPC_DCCH_MAX_SETPTs to FPC_DCCH_MAX_SETPTr; otherwise, set
11 FPC_DCCH_MAX_SETPTs to FPC_DCCH_CURR_SETPTs.
12 – If FPC_INCL is equal to '1' and FPC_MODE is equal to '001', '010', ‘101’, or ‘110’,
13 the mobile station shall:
14 + Set FPC_SEC_CHANs to FPC_SEC_CHANr.
15 – If NUM_SUPr is not equal to ‘00’, for each Supplemental Channel included in the
16 message, the mobile station shall:
17 + Set SCH_IDs to SCH_IDr.
18 + Set FPC_SCH_FERs[SCH_IDs] to FPC_SCH_FERr.
19 + If FPC_SCH_MIN_ SETPTr is not equal to ‘11111111’, set

20 FPC_SCH_MIN_SETPTs[SCH_IDs] to FPC_SCH_MIN_SETPTr; otherwise, set
21 FPC_SCH_MIN_SETPTs[SCH_IDs] to FPC_SCH_CURR_SETPTs.
22 + If FPC_SCH_MAX_SETPTr is not equal to ‘11111111’, set

23 FPC_SCH_MAX_SETPTs[SCH_IDs] to FPC_SCH_MAX_SETPTr; otherwise, set
24 FPC_SCH_MAX_SETPTs[SCH_IDs] to FPC_SCH_CURR_SETPTs.
25 – If FPC_THRESH_INCL is equal to ‘1’, the mobile station shall set

26 FPC_SETPT_THRESHs to FPC_SETPT_THRESHr.
27 – If FPC_THRESH_SCH_INCL is equal to ‘1’, the mobile station shall set

28 FPC_SETPT_THRESH_SCHs to FPC_SETPT_THRESH_SCHr
29 • If RPC_INCLr is equal to ‘1’ and the mobile station supports any Radio Configuration
30 greater than 2, the mobile station shall perform the following:
31 – If RPC_ADJ_REC_TYPE is equal to ‘0000’, the mobile station shall update the

32 Reverse Channel Adjustment Gain Table (see 2.1.2.3.3.2 of [2]) containing an
33 offset relative to the Reverse Pilot Channel power for each reverse link code
34 channel received in this message.
35 – If RPC_ADJ_REC_TYPE is equal to ‘0001’ or ‘0010’, the mobile station shall

36 update the Reverse Link Attribute Adjustment Gain Table (see 2.1.2.3.3.2 of [2])
37 containing an offset relative to the Reverse Pilot Channel power for each
38 transmission rate, frame length, coding type received in this message.
2-269
3GPP2 C.S0005-A v6.0
1 2.6.4.1.2 Service Configuration and Negotiation
2 During Traffic Channel operation, the mobile station and base station communicate
3 through the exchange of Forward and Reverse Traffic Channel frames. The mobile station
4 and base station use a common set of attributes for building and interpreting Traffic
5 Channel frames. This set of attributes, referred to as a service configuration, consists of
6 both negotiable and non-negotiable parameters.
7 The set of negotiable service configuration parameters consists of the following:

8 1.Forward and Reverse Multiplex Options: These control the way in which the
9 information bits of the Forward and Reverse Traffic Channel frames, respectively,
10 are divided into various types of traffic, such as signaling traffic, primary traffic and
11 secondary traffic. A multiplex option together with a radio configuration specifies
12 the frame structures and transmission rates (see [3]). The multiplex options which
13 support Supplemental Code Channel transmission and Supplemental Channel
14 transmission on the Forward and Reverse Traffic Channels are included in [3].
15 Multiplex Options 3 through 16 also indicate the capability for supporting
16 Supplemental Code Channel transmission on the Forward and Reverse Traffic
17 Channels. Invocation of Supplemental Code Channel operation on the Forward or
18 Reverse Traffic Channels occurs by the Supplemental Channel Request Message, the
19 Supplemental Channel Assignment Message, and the General Handoff Direction
20 Message. Invocation of Supplemental Channel operation on the Forward or Reverse
21 Traffic Channels occurs by the Supplemental Channel Request Mini Message, the
22 Extended Supplemental Channel Assignment Message, the Forward Supplemental
23 Channel Assignment Mini Message, Universal Handoff Direction Message, and the
24 Reverse Supplemental Channel Assignment Mini Message. The multiplex option
25 used for the Forward Traffic Channel can be the same as that used for the Reverse
26 Traffic Channel, or it can be different.
27 2.Forward and Reverse Traffic Channel Configurations: These include the Radio
28 Configurations and other necessary attributes for the Forward and Reverse Traffic
29 Channels. The Traffic Channel Configuration used can be different for the Forward
30 and Reverse Traffic Channels or it can be the same.
31 3.Forward and Reverse Traffic Channel Transmission Rates: These are the transmission
32 rates actually used for the Forward and Reverse Traffic Channels respectively. The
33 transmission rates for the Forward Traffic Channel can include all of the
34 transmission rates supported by the radio configuration associated with the
35 Forward Traffic Channel multiplex option, or a subset of the supported rates.
36 Similarly, the transmission rates used for the Reverse Traffic Channel can include
37 all rates supported by the radio configuration associated with the Reverse Traffic
38 Channel multiplex option, or a subset of the supported rates. The transmission
39 rates used for the Forward Traffic Channel can be the same as those used for the
40 Reverse Traffic Channel, or they can be different.
41 4. Service Option Connections: These are the services in use on the Traffic Channel.
42 There can be multiple service option connections. It is also possible that there is no
43 service option connection, in which case the mobile station uses the Reverse Traffic
2-270
3GPP2 C.S0005-A v6.0
1 Channel as follows:
2 • Sends null traffic on the Reverse Fundamental Channel, if the Fundamental

3 Channel is present.
4 • Sends signaling traffic on the Reverse Traffic Channel where r-dsch is mapped
5 to.
6 Associated with each service option connection are a service option, a Forward
7 Traffic Channel traffic type, a Reverse Traffic Channel traffic type, and a service
8 option connection reference. The associated service option formally defines the way
9 in which traffic bits are processed by the mobile station and base station. The
10 associated Forward and Reverse Traffic Channel traffic types specify the types of
11 traffic used to support the service option. A service option can require the use of a
12 particular type of traffic, such as primary or secondary, or it can accept more than
13 one traffic type. A service option can be one-way, in which case it can be supported
14 on the Forward Traffic Channel only or the Reverse Traffic Channel only.
15 Alternatively, a service option can be two-way, in which case it can be supported on
16 the Forward and Reverse Traffic Channels simultaneously. Connected service
17 options can also invoke operation on Supplemental Code Channels in either one or
18 both of the Forward and Reverse Traffic Channels by negotiating a multiplex option
19 that supports operation on Supplemental Code Channels (see [3] for Multiplex
20 options applicable to Supplemental Code Channels), and by using the appropriate
21 Supplemental Code Channel related messages (i.e., the Supplemental Channel
22 Request Message, the Supplemental Channel Assignment Message, and the General
23 Handoff Direction Message). After Supplemental Code Channels have been assigned
24 by the base station, the connected service option can transmit primary and/or
25 secondary traffic on Supplemental Code Channels. Connected service options can
26 also invoke operation on Supplemental Channels in either one or both of the
27 Forward and Reverse Traffic Channels by negotiating a multiplex option that
28 supports operation on Supplemental Channels (see [3] for Multiplex Options
29 applicable to Supplemental Channel) and by using the appropriate Supplemental
30 Channel related messages (i.e., the Supplemental Channel Request Mini Message, the
32 Channel Assignment Mini Message, the Reverse Supplemental Channel Assignment
33 Mini Message, and the Universal Handoff Direction Message). After Supplemental
34 Channels have been assigned by the base station, the connected service option can
35 transmit primary and/or secondary traffic on Supplemental Channels. The
36 associated service option connection reference provides a means for uniquely
37 identifying the service option connection. The reference serves to resolve ambiguity
38 when there are multiple service option connections in use.
39 The non-negotiable service configuration parameters are sent from the base station to the
40 mobile stations only, and consists of the following:
41 1. Reverse Pilot Gating Rate: This controls the way in which the reverse pilot is gated
42 on the Reverse Pilot Channel. The base station specifies the reverse pilot gating rate
43 to be used in the Service Connect Message, the General Handoff Direction Message,
44 and the Universal Handoff Direction Message.
2-271
3GPP2 C.S0005-A v6.0
1 2. Forward and Reverse Power Control Parameters: These consist of forward power
2 control operation mode, outer loop power control parameters (e.g. target frame error
3 rate, minimum Eb/Nt setpoint, and maximum Eb/Nt setpoint) for the Forward
4 Fundamental Channel and Forward Dedicated Control Channel, and Power Control
5 Subchannel indicator which indicates where the mobile station is to perform the
6 primary inner loop estimation and the base station is to multiplex the Power Control
7 Subchannel.
8 3. Logical to Physical Mapping: This is a table of logical to physical mapping entries,
9 consisting of service reference identifier, logical resource, physical resource, forward
10 flag, reverse flag, and priority.
11 The mobile station can request a default service configuration associated with a service
12 option at call origination, and can request new service configurations during Traffic
13 Channel operation. A requested service configuration can differ greatly from its predecessor
14 or can be very similar. For example, the mobile station can request a service configuration
15 in which all of the service option connections are different from those of the existing
16 configuration; or the mobile station can request a service configuration in which the
17 existing service option connections are maintained with only minor changes, such as a
18 different set of transmission rates or a different mapping of service option connections to
19 Forward and Reverse Traffic Channel traffic types.
20 If the mobile station requests a service configuration that is acceptable to the base station,
21 they both begin using the new service configuration. If the mobile station requests a
22 service configuration that is not acceptable to the base station, the base station can reject
23 the requested service configuration or propose an alternative service configuration. If the
24 base station proposes an alternative service configuration, the mobile station can accept or
25 reject the base station’s proposed service configuration, or propose yet another service
26 configuration. This process, called service negotiation, ends when the mobile station and
27 the base station find a mutually acceptable service configuration, or when either the mobile
28 station or the base station rejects a service configuration proposed by the other.
29 It is also possible for the base station to request a default service configuration associated
30 with a service option when paging the mobile station and to request new service
31 configurations during Traffic Channel operation. The service negotiation proceeds as
32 described above, but with the roles of the mobile station and base station reversed.
33 For CDMA mode operation in Band Class 0, the mobile station and base station can also
34 use an alternative method for negotiating a service configuration known as service option
35 negotiation. Service option negotiation is similar to service negotiation, but offers less
36 flexibility for specifying the attributes of the service configuration. During service option
37 negotiation, the base station or the mobile station specifies only which service option is to
38 be used. There is no facility for explicitly specifying the multiplex options, traffic types or
39 transmission rates to be used on the Forward and Reverse Traffic Channels in conjunction
40 with the service option. Instead, implicit service configuration attributes are assumed. In
41 particular, the Forward and Reverse multiplex options and transmission rates are assumed
42 to be the default multiplex options and transmission rates associated with the requested
43 service option, and the traffic type for both the Forward and Reverse Traffic Channels is
2-272
3GPP2 C.S0005-A v6.0
1 assumed to be primary traffic; furthermore, a service configuration established using

2 service option negotiation is restricted to having only a single service option connection.
3 At mobile station origination and termination, the type of negotiation to use, either service
4 negotiation or service option negotiation, is indicated in the Channel Assignment Message.
5 Service negotiation is always used after the mobile station receives an Extended Channel
6 Assignment Message. If a CDMA-to-CDMA hard handoff occurs during the call, the type of
7 negotiation to use following the handoff is indicated in the Extended Handoff Direction
8 Message, the General Handoff Direction Message, or the Universal Handoff Direction
9 Message.
10 For CDMA mode operation in band classes other than Band Class 0, only service
11 negotiation is to be used.
12 The following messages are used to support service negotiation:

13 1. Service Request Message: The mobile station can use this message to propose a
14 service configuration, or to accept or reject a service configuration proposed in a
15 Service Response Message. The base station can use this message to propose a
16 service configuration, or to reject a service configuration proposed in a Service
17 Response Message.
18 2. Service Response Message: The mobile station can use this message to accept or
19 reject a service configuration proposed in a Service Request Message, or to propose
20 an alternative service configuration. The base station can use this message to reject
21 a service configuration proposed in a Service Request Message, or to propose an
22 alternative service configuration.
23 3. Service Connect Message: The base station can use this message to accept a service
24 configuration proposed in a Service Request Message or Service Response Message,
25 and to instruct the mobile station to begin using the service configuration.
26 4. Service Connect Completion Message: The mobile station can use this message to
27 acknowledge the transition to a new service configuration.
28 5. Service Option Control Message: The mobile station and base station can use this
29 message to invoke service-option-specific functions.
30 6. Extended Channel Assignment Message: The base station can use this message to
31 accept or reject the initial service configuration proposed by the mobile station in an
32 Origination Message or a Page Response Message.
33 The following messages are used to support service option negotiation:
34 1. Service Option Request Order: The mobile station and base station can use this
35 message either to request a service option or to suggest an alternative service
36 option.
37 2. Service Option Response Order: The mobile station and base station can use this
38 message to accept or to reject a service option request.
39 3. Service Option Control Order: The mobile station and base station can use this
40 message to invoke service option specific functions.
2-273
3GPP2 C.S0005-A v6.0
1 The following messages are used to support both service negotiation and service option
2 negotiation:
3 1.Origination Message: The mobile station can use this message to propose an initial
4 service configuration.
5 2.Channel Assignment Message: The base station can use this message to accept or to
6 reject the initial service configuration proposed by the mobile station in an
7 Origination Message or a Page Response Message and to indicate which type of
8 negotiation, either service negotiation or service option negotiation, is to be used
9 during the call.
10 3.Extended Handoff Direction Message: The base station can use this message to
11 indicate which type of negotiation, either service negotiation or service option
12 negotiation, is to be used following a CDMA-to-CDMA hard handoff.
13 4.General Handoff Direction Message: The base station can use this message to indicate
14 which type of negotiation, either service negotiation or service option negotiation, is
15 to be used following a CDMA-to-CDMA hard handoff. The base station can use this
16 message to accept a service configuration proposed in a Service Request Message or
17 Service Response Message. The base station can also use this message to instruct
18 the mobile station to begin using the service configuration.
19 5.General Page Message or Universal Page Message: The base station can use a mobile-
20 station-addressed page in a General Page Message or in a Universal Page Message
21 to propose an initial service configuration.
22 6.Page Response Message: The mobile station can use this message to accept or to
23 reject the initial service configuration proposed by the base station in a mobile-
24 station-addressed page, or to propose an alternative initial service configuration.
25 7.Status Request Message: The base station can use this message to request service
26 capability information from the mobile station.
27 8.Status Response Message: The mobile station can use this message to return the
28 service capability information requested by the base station in a Status Request
29 Message.
30 9.Extended Status Response Message: The mobile station can use this message to
31 return the service capability information requested by the base station in a Status
32 Request Message.
33 10. Universal Handoff Direction Message: The base station can use this message to
35 negotiation, is to be used following a CDMA-to-CDMA hard handoff. The base
36 station can use this message to accept a service configuration proposed in a Service
37 Request Message or Service Response Message. The base station can also use this
38 message to instruct the mobile station to begin using the service configuration.
2-274
3GPP2 C.S0005-A v6.0
1 2.6.4.1.2.1 Use of Variables
2 2.6.4.1.2.1.1 Maintaining the Service Request Sequence Number
3 The mobile station shall maintain a service request sequence number variable,
4 SERV_REQ_NUMs for use with service negotiation. Upon entering the Mobile Station
5 Control on the Traffic Channel State, the mobile station shall set SERV_REQ_NUMs to 0.
6 Each time the mobile station sends a new Service Request Message, it shall set the
7 SERV_REQ_SEQ field of the message to the current value of SERV_REQ_NUMs, and shall
8 then set SERV_REQ_NUMs equal to (SERV_REQ_NUMs + 1) modulo 8.
9 2.6.4.1.2.1.2 Maintaining the Service Negotiation Indicator Variable

10 The mobile station shall maintain a service negotiation indicator variable, SERV_NEGs, to
11 indicate which type of negotiation to use, either service negotiation or service option
12 negotiation. The mobile station shall set SERV_NEGs to enabled whenever service
13 negotiation is to be used, and shall set SERV_NEGs to disabled whenever service option
14 negotiation is to be used. The precise rules for setting SERV_NEGs are specified in 2.6.4.2
15 and 2.6.6.2.5.1.
16 For CDMA operation in band classes other than Band Class 0, the mobile station shall set
17 SERV_NEGs to enabled.
18 2.6.4.1.2.1.3 Maintaining the Service Option Request Number

19 The mobile station shall maintain a service option request number variable, SO_REQs, for
20 use with service option negotiation. The mobile station shall set SO_REQs to a special
21 value, NULL, if the mobile station does not have an outstanding service option request. If
22 the mobile station has an outstanding service option request, the mobile station shall set
23 SO_REQs to the number of the service option associated with the outstanding request.
24 2.6.4.1.2.2 Service Subfunctions
25 As illustrated in Figure 2.6.4.1.2.2-1, the mobile station supports service configuration and
26 negotiation by performing the following set of service subfunctions:
27 • Normal Service Subfunction - While this subfunction is active, the mobile station
28 processes service configuration requests from the user and from the base station.
29 • Waiting for Service Request Message Subfunction - While this subfunction is active,
30 the mobile station waits to receive a Service Request Message.
31 • Waiting for Service Response Message Subfunction - While this subfunction is active,
32 the mobile station waits to receive a Service Response Message.
33 • Waiting for Service Connect Message Subfunction - While this subfunction is active,
34 the mobile station waits to receive a Service Connect Message, a General Handoff
35 Direction Message, or a Universal Handoff Direction Message containing a service
36 configuration record.
2-275
3GPP2 C.S0005-A v6.0
1 • Waiting for Service Action Time Subfunction - While this subfunction is active, the
2 mobile station waits for the action time associated with a new service configuration
3 and then sends a Service Connect Completion Message, a Handoff Completion
4 Message, or an Extended Handoff Completion Message.
5 • SO Negotiation Subfunction - While this subfunction is active, the mobile station

6 supports service option negotiation with the base station. This subfunction is only
7 used while operating in Band Class 0.
8 The SO Negotiation Subfunction supports service option negotiation. All of the other service
9 subfunctions support service negotiation.
10 At any given time during Traffic Channel operation, only one of the service subfunctions is
11 active. For example, when the mobile station first enters the Traffic Channel Initialization
12 Substate of the Mobile Station Control on the Traffic Channel State, the Normal Service
13 Subfunction, the Waiting for Service Connect Message Subfunction or the SO Negotiation
14 Subfunction is active. Each of the other service subfunctions may become active in
15 response to various events which occur during the Traffic Channel substates. Typically, the
16 mobile station processes events pertaining to service configuration and negotiation in
17 accordance with the requirements for the active service subfunction, however, some Traffic
18 Channel substates do not allow for the processing of certain events pertaining to service
19 configuration and negotiation, or specify requirements for processing such events which
20 supersede the requirements of the active service subfunction.
21
2-276
3GPP2 C.S0005-A v6.0
For service
negotiation
Receives Service For service option SO Entered from any

Request Message negotiation Negotiation subfunction when
proposing; sends Subfunction SERV_NEGs is disabled.
Service Response
Message rejecting.
SERV_NEGs
is enabled.
Normal
Service
Receives Service
Subfunction
Request Message Receives Service
proposing; sends Request Message User requests new
Service Response proposing; sends service configuration;
Message proposing Service Response sends Service Request Receives Service
Message proposing. Message proposing. Response Message
proposing; sends
Service Request
Message proposing.
Receives Service
Receives Service Response Message
Request Message rejecting.
Waiting for rejecting. - or - Waiting for
Service - or - Receives Service Service
Request Receives Service Response Message Response
Message Request Message proposing; sends Message
Subfunction proposing; sends Service Request Subfunction
Service Response Message rejecting.
Message rejecting.
Receives Service
Request Message
Action time passes; proposing; sends
Receives uses new service Service Response
SCM configuration; sends Message accepting
GHDM Service Connect
or UHDM Completion Message, Handoff
Completion Message, or Extended
Handoff Completion Message.
Receives
SCM, GHDM, or UHDM Receives
Waiting for SCM, GHDM, or UHDM
Service
Action Time
Subfunction
Receives Service
Request Message
proposing; sends Receives Service
Receives SCM, GHDM, or UHDM Response Message
Service Response
Message accepting. proposing; sends
Service Request
Waiting for Message accepting.
Service
Connect
Message
Subfunction
Notes:
SCM stands for Service Connect Message.
GHDM stands for General Handoff Direction Message.
UHDM stands for Universal Handoff Direction Message.
Processing for special cases, such as timeouts and errors, is not shown in this diagram.
3 Figure 2.6.4.1.2.2-1. Mobile Station Service Subfunctions
2-277
3GPP2 C.S0005-A v6.0
1 2.6.4.1.2.2.1 Normal Service Subfunction
2 While this subfunction is active, the mobile station processes service configuration requests
3 from the user and from the base station.
4 While the Normal Service Subfunction is active, the mobile station shall perform the
5 following:
6 • The mobile station shall process Forward and Reverse Traffic Channel frames in
7 accordance with the current service configuration. The mobile station shall discard
8 any Forward Traffic Channel frame which has a format that is not supported by the
9 mobile station. The mobile station may discard any type of Forward Traffic Channel
10 traffic that is not signaling traffic and is not part of the current service
11 configuration.
12 • To initiate service negotiation for a new service configuration, the mobile station
13 shall send a Service Request Message to propose the new service configuration. The
14 mobile station shall activate the Waiting for Service Response Message Subfunction.
15 • For any service option connection that is part of the current service configuration,
16 the mobile station may send a Service Option Control Message to invoke a service
17 option specific function in accordance with the requirements for the associated
18 service option.
19 • If SERV_NEGs changes from enabled to disabled (see 2.6.6.2.5.1), the mobile station
20 shall activate the SO Negotiation Subfunction.
21 • If the mobile station receives one of the following service negotiation messages, the
22 mobile station shall process the message according to the specified requirements:
23 1. Service Connect Message: The mobile station shall perform the following:
24 • If USE_OLD_SERV_CONFIGr equals ‘00’, the mobile station shall perform the
25 following: If the mobile station accepts the service configuration specified in
26 the message, the mobile station shall activate the Waiting for Service Action
27 Time Subfunction; otherwise, the mobile station shall send a Mobile Station
28 Reject Order (ORDQ = ‘00000111’) within T56m seconds.

30 following: If the mobile station accepts the service configuration currently
31 stored at the mobile station, the mobile station shall activate the Waiting for
32 Service Action Time Subfunction; otherwise, the mobile station shall send a
33 Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds.

35 following: If the mobile station accepts the service configuration resulting
36 from updating the stored service configuration with the service configuration
37 received in this message, the mobile station shall activate the Waiting for
2-278
3GPP2 C.S0005-A v6.0
1 2. Service Option Control Message: If the service option connection specified by the
2 message is part of the current service configuration, and the service option
3 specified by the message is the same as the service option associated with the
4 service option connection, the mobile station shall interpret the action time of
5 the message as specified in 2.6.4.1.5, and shall process the message in
6 accordance with the requirements for the service option; otherwise, the mobile
7 station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within
8 T56m seconds.
9 3. Service Request Message: The mobile station shall process the message as
10 follows:
11 – If the purpose of the message is to reject a proposed service configuration,

12 the mobile station shall send a Mobile Station Reject Order (ORDQ =
13 ‘00000010’) within T56m seconds.
14 – If the purpose of the message is to propose a service configuration, the

15 mobile station shall process the message as follows:
16 + If the mobile station accepts the proposed service configuration, the

17 mobile station shall send a Service Response Message to accept the
18 proposed service configuration within T59m seconds. The mobile station
19 shall activate the Waiting for Service Connect Message Subfunction.
20 + If the mobile station does not accept the proposed service configuration
21 and does not have an alternative service configuration to propose, the
22 mobile station shall send a Service Response Message to reject the
23 proposed service configuration within T59m seconds.
25 and has an alternative service configuration to propose, the mobile
26 station shall send a Service Response Message to propose the alternative
27 service configuration within T59m seconds. The mobile station shall
28 activate the Waiting for Service Request Message Subfunction.
29 4.3. Service Response Message: The mobile station shall send a Mobile Station
30 Reject Order (ORDQ = ‘00000010’) within T56m seconds.
31 5.4. General Handoff Direction Message: If the SCR_INCLUDED field is included

32 in this message and is set to ‘1’:
33 If the mobile station has not rejected this message, the mobile station shall
34 activate the Waiting for Service Action Time Subfunction.
35 6. Universal Handoff Direction Message: If the SCR_INCLUDED field is included in

36 this message and is set to ‘1’:
39 • If the mobile station receives one of the following service option negotiation
40 messages, the mobile station shall send a Mobile Station Reject Order (ORDQ =
41 ‘00000010’) within T56m seconds:
2-279
3GPP2 C.S0005-A v6.0
1 1. Service Option Request Order
2 2. Service Option Response Order
3 3. Service Option Control Order
4 2.6.4.1.2.2.2 Waiting for Service Request Message Subfunction
5 While this subfunction is active, the mobile station waits to receive a Service Request
6 Message.
7 Upon activation of the Waiting for Service Request Message Subfunction, the mobile station
8 shall set the subfunction timer for T68m seconds.
9 While the Waiting for Service Request Message Subfunction is active, the mobile station shall
11 • If the subfunction timer expires, the mobile station shall activate the Normal Service
12 Subfunction.
18 configuration.
19 • The mobile station shall not initiate service negotiation for a new service
20 configuration.
24 service option.
30 • If USE_OLD_SERV_CONFIGr equals ‘00’, the mobile station shall perform
31 the following: If the mobile station accepts the service configuration
32 specified in the message, the mobile station shall activate the Waiting for
33 Service Action Time Subfunction; otherwise, the mobile station shall send
34 a Mobile Station Reject Order (ORDQ = ‘00000111’) within T56m seconds
35 and shall activate the Normal Service Subfunction.
38 currently stored at the mobile station, the mobile station shall activate
39 the Waiting for Service Action Time Subfunction; otherwise, the mobile
2-280
3GPP2 C.S0005-A v6.0
1 station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’)


5 resulting from updating the stored service configuration with the service
6 configuration received in this message, the mobile station shall activate
7 the Waiting for Service Action Time Subfunction; otherwise, the mobile
8 station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’)
17 T56m seconds.
19 follows:

21 the mobile station shall activate the Normal Service Subfunction.


32 shall activate the Normal Service Subfunction.
37 reset the subfunction timer for T68m seconds.
38 4. Service Response Message: The mobile station shall send a Mobile Station Reject
39 Order (ORDQ = ‘00000010’) within T56m seconds.
40 5. General Handoff Direction Message: If the SCR_INCLUDED field is included in

2-281
3GPP2 C.S0005-A v6.0
2 activate the Waiting for Service Action Time Subfunction; otherwise, the mobile
3 station shall activate the Normal Service Subfunction.

15 2.6.4.1.2.2.3 Waiting for Service Response Message Subfunction
16 While this subfunction is active, the mobile station waits to receive a Service Response
17 Message.
18 Upon activation of the Waiting for Service Response Message Subfunction, the mobile station
20 While the Waiting for Service Response Message Subfunction is active, the mobile station
23 Subfunction.
29 configuration.
31 configuration.
35 service option.
2-282
3GPP2 C.S0005-A v6.0
8 Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate
9 the Normal Service Subfunction.

28 T56m seconds.
30 follows:


35 mobile station shall discontinue processing the service configuration
36 requested by the user and shall process the message as follows:

2-283
3GPP2 C.S0005-A v6.0
11 4. Service Response Message: The mobile station shall process the message as
12 follows:
13 – If the service request sequence number (SERV_REQ_SEQr) from the message
14 does not match the sequence number of the Service Request Message for
15 which the mobile station is expecting a response, the mobile station shall not
16 process the other lLayer 3 fields of the message.
17 – If the purpose of the message is to reject the service configuration proposed

18 in the corresponding Service Request Message, the mobile station shall
19 activate the Normal Service Subfunction. The mobile station may indicate to
20 the user that the requested service configuration has been rejected.


24 mobile station shall send a Service Request Message to accept the
29 mobile station shall send a Service Request Message to reject the
34 station shall send a Service Request Message to propose the alternative
36 reset the subfunction timer for T68m seconds.

2-284
3GPP2 C.S0005-A v6.0

12 2.6.4.1.2.2.4 Waiting for Service Connect Message Subfunction
13 While this subfunction is active, the mobile station waits to receive a Service Connect
14 Message, a General Handoff Direction Message, or a Universal Handoff Direction Message
15 containing a service configuration record.
16 Upon activation of the Waiting for Service Connect Message Subfunction, the mobile station
18 While the Waiting for Service Connect Message Subfunction is active, the mobile station shall
21 Subfunction.
27 configuration.
29 configuration.
33 service option.
2-285
3GPP2 C.S0005-A v6.0

5 Reject Order (ORDQ = ‘00000111’) within T56m seconds and shall activate
6 the Normal Service Subfunction.

25 T56m seconds.
27 follows:



36 shall reset the subfunction timer for T65m seconds.
2-286
3GPP2 C.S0005-A v6.0


24 2.6.4.1.2.2.5 Waiting for Service Action Time Subfunction
25 While this subfunction is active, the mobile station waits for the action time associated with
26 a new service configuration. If the action time was specified by a Service Connect Message,
27 the mobile station shall send the Service Connect Completion Message at the action time.
28 While the Wait for Service Action Time Subfunction is active, the mobile station shall perform
29 the following:
30 • Prior to the action time associated with the Service Connect Message, General
31 Handoff Direction Message (containing a service configuration record), or Universal
32 Handoff Direction Message (containing a service configuration record), the mobile
33 station shall process Forward and Reverse Traffic Channel frames in accordance
34 with the current service configuration. The mobile station shall discard any
35 Forward Traffic Channel frame which has a format that is not supported by the
38 configuration.
2-287
3GPP2 C.S0005-A v6.0
1 • At the action time associated with the Service Connect Message, General Handoff
2 Direction Message (containing a service configuration record) or Universal Handoff
3 Direction Message (containing a service configuration record), the mobile station
4 shall perform the following10:
5 – If this is a Service Connect Message with USE_OLD_SERV_CONFIGr equals ‘01’,
6 the mobile station shall perform the following:
7 + The Call Control instance identified by NULL shall also be identified by the
8 connection reference assigned to the first service option connection in the
9 stored Service Configuration information record.
10 + For each service option connection (with corresponding connection reference

11 CON_REFi) in the stored service configuration record, if any, except for the
12 first one, lLayer 3 shall instantiate a Call Control instance (as specified in
13 2.6.10) with a ‘restore indication’. The mobile station shall identify each of
14 these Call Control instances by the corresponding CON_REFi.
15 + The mobile station shall begin to use the service configuration which was
16 stored by the mobile station when it left the Mobile Station Control on the
17 Traffic Channel State as the current service configuration and shall begin to
18 process Forward and Reverse Traffic Channel frames accordingly. The mobile
19 station shall send a Service Connect Completion Message within T56m
20 seconds after the action time. The mobile station shall exit this subfunction
21 and activate the Normal Service Subfunction.
22 + The mobile station shall store the synchronization identifier corresponding to

23 the stored service configuration as SYNC_IDs.
24 – If this is a Service Connect Message with USE_OLD_SERV_CONFIGr equals ‘10’,

26 + The mobile station shall update the stored service configuration with the
27 received service configuration as follows:
28 ο The mobile station shall process the received Service Configuration

29 Record as specified in 2.6.4.1.12.
10 Note that these procedures that take place at the action time may not occur for this
message if a GHDM/UHDM with SCR_INCLUDED equal to ‘1’ is received before the action
time of this message. In this case, these procedures take place for the new message. One
exception is that the call assignments from this message take effect at the action time of
this message regardless of the call assignments from the new message.
2-288
3GPP2 C.S0005-A v6.0
1 ο The mobile station shall process the received Non-negotiable Service

2 Configuration Record as specified in 2.6.4.1.13.
3 + The mobile station shall begin to use the updated service configuration as
4 the current service configuration and shall begin to process Forward and
5 Reverse Traffic Channel frames accordingly. The mobile station shall send a
6 Service Connect Completion Message within T56m seconds after the action
7 time. The mobile station shall exit this subfunction and activate the Normal
8 Service Subfunction
9 + The mobile station shall store (if included) the synchronization identifier
10 received from the base station corresponding to this updated service
11 configuration (SYNC_IDs = SYNC_IDr).
12 – Otherwise, the mobile station shall perform the following:
13 + Prior to this message, if a Service Connect Message, General Handoff

14 Direction Message (with service configuration), or Universal Handoff Direction
15 Message (with service configuration) was not successfully received or
16 accepted by the mobile station since entering the Traffic Channel Substate,
18 ο The mobile station shall delete the stored service configuration (if any).
19 ο Τhe mobile station shall set the service configuration parameters (i.e.
20 those signaled via the Service Configuration information record and the
21 Non-Negotiable Service Configuration information record) to their default
22 values as specified in 2.6.4.2.
23 + The mobile station shall process the received Service Configuration Record as
24 specified in 2.6.4.1.12, shall process the received Non-negotiable Service
25 Configuration Record as specified in 2.6.4.1.13 (if included), and shall begin
26 to use the service configuration specified by the Service Connect Message,
27 General Handoff Direction Message or Universal Handoff Direction Message
28 containing a service configuration record as the current service configuration
29 and shall begin to process Forward and Reverse Traffic Channel frames
30 accordingly. If the action time was specified by a Service Connect Message,
31 the mobile station shall send a Service Connect Completion Message within
32 T56m seconds after the action time. The mobile station shall exit this
33 subfunction and activate the Normal Service Subfunction.
34 + The mobile station shall store (if included) the synchronization identifier
35 received from the base station corresponding to this service configuration
36 (SYNC_IDs = SYNC_IDr).
2-289
3GPP2 C.S0005-A v6.0
1 + If P_REV_IN_USEs is greater than six, the Non-Negotiable Service

2 Configuration information record is not included in this message, and the
3 value of SR_ID corresponding to the logical resource of ‘0000’ in the
4 LOGICAL_TO_PHYSICAL_MAPPING_TABLE is NULL, the mobile station shall
5 set this SR_ID field to the value specified in the Service Configuration
6 information record.
7 + If CC_INFO_INCLr equals ‘1’, then for each of the NUM_CALLS_ASSIGNr
8 occurrences of the call control parameters included in the message, the
10 ο If RESPONSE_INDr equals ‘1’, and TAGr matches any of the TAG values
11 contained in the list TAG_OUTSTANDING_LIST, the lLayer 3 shall
12 instantiate a Call Control instance (as specified in 2.6.10). The mobile
13 station shall identify this Call Control instance by CON_REFr. The mobile
14 station shall disable the enhanced origination timer associated with this
15 call origination and remove the TAG value specified by TAGr from the list
16 TAG_OUTSTANDING_LIST.
17 ο If RESPONSE_INDr equals ‘0’, the mobile station shall store the bypass
18 indicator (BYPASS_ALERT_ANSWERs = BYPASS_ALERT_ANSWERr) and
19 the lLayer 3 shall instantiate a Call Control instance (as specified in
20 2.6.10). The mobile station shall identify this Call Control instance by
21 CON_REFr.
23 configuration.
24 • For any service option connection that is part of the current or pending service
25 configuration, the mobile station may send a Service Option Control Message to
26 invoke a service option specific function in accordance with the requirements for the
27 associated service option.
32 1. Service Connect Message: The mobile station shall send a Mobile Station Reject
35 message is part of the current or pending service configuration, and the service
36 option specified by the message is the same as the service option associated with
37 the service option connection, the mobile station shall interpret the action time
38 of the message as specified in 2.6.4.1.5, and shall process the message in
41 T56m seconds.
2-290
3GPP2 C.S0005-A v6.0
1 3. Service Request Message: The mobile station shall send a Mobile Station Reject

8 remain in this subfunction until the action time specified in the message, and
10 ο The mobile station shall not perform the above procedures for the previous
11 message. But the call assignments from the previous message (if any) shall
12 take effect at the action time of the previous message.
13 ο The mobile station shall perform the above procedures for this message (that
14 is, begin to use the service configuration specified by the General Handoff
15 Direction Message) at the action time of this message.

19 remain in this subfunction until the action time specified in the message, and
21 ο The mobile station shall not perform the above procedures for the previous
22 message. But the call assignments from the previous message (if any) shall
23 take effect at the action time of the previous message.
24 ο The mobile station shall perform the above procedures for this message (that
25 begin to use the service configuration and call assignments (if any) specified
26 by the Universal Handoff Direction Message at the action time of this
27 message.
34 2.6.4.1.2.2.6 SO Negotiation Subfunction

35 The SO Negotiation Subfunction is only supported for mobile stations operating in Band
36 Class 0.
37 Service option negotiation is not supported for P_REV_IN_USEs greater than six.
2-291
3GPP2 C.S0005-A v6.0
1 Upon activation of the SO Negotiation Subfunction, the mobile station shall delete from the
2 current service configuration any service option connection which does not use primary
3 traffic on both the Forward and Reverse Traffic Channels and the lLayer 3 shall terminate
4 the corresponding Call Control instances. The Call Control instance corresponding to the
5 service option connection which uses primary traffic, if any, shall be identified by NULL.
6 While the SO Negotiation Subfunction is active, the mobile station shall perform the
7 following:
8 • If the current service configuration includes a service option connection, the mobile
9 station shall process the received primary traffic bits in accordance with the
10 requirements for the service option associated with the service option connection;
11 otherwise, the mobile station shall discard the received primary traffic bits.
13 station shall transmit primary traffic bits in accordance with the requirements for
14 the service option associated with the service option connection; otherwise, the
15 mobile station shall transmit null traffic on the Reverse Fundamental Channel, if
16 the Fundamental Channel is present or transmit power control bits on the Reverse
17 Pilot Channel, if only the Dedicated Control Channel is present.
19 station may send a Service Option Control Order to invoke a service option specific
20 function in accordance with the requirements for the service option associated with
21 the service option connection.
22 • To initiate service option negotiation, the mobile station shall set SO_REQs to the
23 number of the requested service option and shall send a Service Option Request
24 Order containing the requested service option number.
25 • If SERV_NEGs changes from disabled to enabled (see 2.6.6.2.5.1), the mobile station
26 shall set SO_REQs to NULL and shall activate the Normal Service Subfunction.
27 • If the mobile station receives a Service Option Request Order, it shall process the
28 order as follows:
2-292
3GPP2 C.S0005-A v6.0
1 – If the mobile station accepts the requested service option, the mobile station
2 shall set SO_REQs to NULL and shall send a Service Option Response Order
3 accepting the requested service option within T58m seconds. The mobile station
4 shall interpret the message action time of the Service Option Request Order in
5 accordance with the requirements for the requested service option and the
6 mobile station shall begin using the service configuration implied by the
7 requested service option in accordance with those requirements. The implied
8 service configuration shall include the default Forward and Reverse multiplex
9 options and radio configurations associated with the requested service option,
10 and shall include one service option connection for which the service option
11 connection reference is 1, the service option is the requested service option, and
12 the Forward and Reverse Traffic Channel types are both primary traffic. If a Call
13 Control instance currently exists, the Layer 3 shall use this Call Control
14 instance for a new service option connection; otherwise, The the lLayer 3 shall
15 instantiate a Call Control instance (as specified in 2.6.10) and; this Call Control
16 instance shall be identified by both a connection reference with a value of 1 and
17 a default identifier with a value of NULL.
18 – If the mobile station does not accept the requested service option and has an
19 alternative service option to request, the mobile station shall set SO_REQs to the
20 alternative service option number and shall send a Service Option Request Order
21 requesting the alternative service option within T58m seconds.
22 – If the mobile station does not accept the requested service option and does not
23 have an alternative service option to request, the mobile station shall set
24 SO_REQs to NULL and shall send a Service Option Response Order to reject the
25 request within T58m seconds. The mobile station shall continue to use the
26 current service configuration.
27 • If the mobile station receives a Service Option Response Order, it shall process the
29 – If the service option number specified in the order is equal to SO_REQs, the
30 mobile station shall set SO_REQs to NULL. The mobile station shall interpret
31 the message action time of the Service Option Response Order in accordance with
32 the requirements for the specified service option, and the mobile station shall
33 begin using the service configuration implied by the specified service option in
34 accordance with those requirements. The implied service configuration shall
35 include the default Forward and Reverse multiplex options and radio
36 configurations associated with the specified service option, and shall include one
37 service option connection for which the service option connection reference is 1,
38 the service option is the specified service option, and the Forward and Reverse
39 Traffic Channel types are both primary traffic. If a Call Control instance
40 currently exists, the Layer 3 shall use this Call Control instance for a new
41 service option connection; otherwise, The the lLayer 3 shall instantiate a Call
42 Control instance (as specified in 2.6.10) and; this Call Control instance shall be
43 identified by both a connection reference with a value of 1 and a default
44 identifier with a value of NULL.
2-293
3GPP2 C.S0005-A v6.0
1 – If the order indicates a service option rejection, the mobile station shall set
2 SO_REQs to NULL. The mobile station shall continue to use the current service
3 configuration.
4 – If the order does not indicate a service option rejection and the service option
5 specified in the order is not equal to SO_REQs, the mobile station shall set
6 SO_REQs to NULL and shall send a Mobile Station Reject Order (ORDQ =
7 ‘00000100’) within T58m seconds. The mobile station shall continue to use the
9 • If the mobile station receives a Service Option Control Order, it shall process the
11 – If the current service configuration includes a service option connection, the

12 mobile station shall interpret the message action time of the Service Option
13 Control Order in accordance with the requirements for the service option
14 associated with the service option connection and the mobile station shall
15 process the Service Option Control Order in accordance with those requirements;
16 – otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ =
19 mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within
20 T56m seconds:
21 1. Service Connect Message
22 2. Service Option Control Message
23 3. Service Request Message
24 4. Service Response Message
25 2.6.4.1.3 Ordering of Messages
26 The Layer 2 protocol does not guarantee delivery of messages in any order. If the mobile
27 station requires that the base station receive a set of messages in a certain order, the
28 mobile station shall send each message in assured mode requiring confirmation of delivery
29 and shall wait for the confirmation of delivery of each message before transmitting the next
30 message in the set.
31 2.6.4.1.4 Processing the In-Traffic System Parameters Message

32 The mobile station shall store the following parameters from the In-Traffic System
33 Parameters Message:
36 • Search window size for the Active Set and the Candidate Set
38 • Search window size for the Neighbor Set (SRCH_WIN_Ns = SRCH_WIN_Nr)
2-294
3GPP2 C.S0005-A v6.0

8 • Protocol revision level (P_REVs = P_REVr), and protocol revision level currently in
9 use (P_REV_IN_USEs = min (P_REVs, MOB_P_REVp of the current band class) )
10 • Slope of the handoff add/drop criterion (SOFT_SLOPEs = SOFT_SLOPEr)
13 • If included, Reverse Supplemental Code Channel or Reverse Supplemental Channel

14 neighbor pilot strength measurement transmission threshold offset threshold
15 (T_MULCHANs = T_MULCHANr)
16 • If included, Reverse Supplemental Code Channel beginning of transmission

17 preamble length (BEGIN_PREAMBLEs = BEGIN_PREAMBLEr)
18 • If included, Reverse Supplemental Code Channel discontinuous transmission

19 resumption preamble length (RESUME_PREAMBLEs = RESUME_PREAMBLEr)
20 • If included, Slotted Timer (T_SLOTTEDs = T_SLOTTEDr)
21 • If the mobile station supports packet data service options, the mobile station shall
22 store the packet data services zone identifier (PACKET_ZONE_IDs =
23 PACKET_ZONE_IDr).

26 SIG_ENCRYPT_SUPr)

28 UI_ENCRYPT_SUPr)
29 • Concurrent services supported indicator (CS_SUPPORTEDs = CS_SUPPORTEDr).
30 The mobile station shall determine its roaming status (see 2.6.5.3). The mobile station
31 should indicate to the user whether the mobile station is roaming.
32 2.6.4.1.5 Message Action Times
33 A Forward Traffic Channel message without a USE_TIME field or with a USE_TIME field set
34 to ‘0’ has an implicit action time. A message that has its USE_TIME field set to ‘1’ has an
35 explicit action time that is specified in the ACTION_TIME field of the message.
36 A message with an explicit action time is called a pending message.
2-295
3GPP2 C.S0005-A v6.0
1 Unless otherwise specified, a message having an implicit action time shall take effect no
2 later than the first 80 ms boundary (relative to System Time) occurring at least 80 ms after
3 the end of the frame containing the last bit of the message. A message with an explicit
4 action time, except for a Power Up Function Message, shall take effect when System Time (in
5 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME field. A Power Up
6 Function Message shall take effect ACTION_TIME_FRAME frames after the time when
7 System Time (in 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME
8 field. The difference in time between ACTION_TIME and the end of the frame containing the
9 last bit of the message shall be at least 80 ms.
10 The mobile station shall support two pending messages at any given time, not including
11 pending Service Option Control Orders or Service Option Control Messages. The number of
12 pending Service Option Control Orders or Service Option Control Messages that the mobile
13 station is required to support is specific to the service option (see the relevant service option
14 description). In addition, the mobile station shall support one pending Power Up Function
15 Message.
16 2.6.4.1.6 Long Code Transition Request Processing
17 The mobile station performs these procedures upon receiving a Long Code Transition
18 Request Order.
19 If the Long Code Transition Request Order requests a transition to the private long code, and
20 the mobile station is able to generate the private long code (see 2.3.12.3), and the mobile
21 station accepts the request, the mobile station shall send a Long Code Transition Response
22 Order (ORDQ = ‘00000011’) within T56m seconds. The mobile station shall use the private
23 long code on both the Forward Traffic Channel and the Reverse Traffic Channel. The
24 mobile station shall begin using the private long code at the explicit action time (see
25 2.6.4.1.5) specified in the message. At the action time of the message, the mobile station
26 should indicate to the user that the voice privacy mode is active. If the Long Code
27 Transition Request Order requests a private long code transition, and the mobile station is
28 not able to generate the private long code or the mobile station does not accept the request,
29 the mobile station shall send a Long Code Transition Response Order (ORDQ = ‘00000010’)
31 If the Long Code Transition Request Order requests a transition to the public long code and
32 the mobile station accepts the request, the mobile station shall send a Long Code Transition
33 Response Order (ORDQ = ‘00000010’) within T56m seconds. The mobile station shall use
34 the public long code on both the Forward Traffic Channel and the Reverse Traffic Channel.
35 The mobile station shall begin using the public long code at the explicit action time (see
36 2.6.4.1.5) specified in the message. At the action time of the message, the mobile station
37 should indicate to the user that the voice privacy mode is inactive. If the Long Code
38 Transition Request Order requests a public long code transition, and the mobile station does
39 not accept the request, the mobile station shall send a Long Code Transition Response Order
40 (ORDQ = ‘00000011’) within T56m seconds.
2-296
3GPP2 C.S0005-A v6.0
1 2.6.4.1.7 Power Up Function (PUF)
2 Figure 2.6.4.1.7-1 illustrates the general structure of a PUF attempt. A PUF pulse is the
3 interval during which the mobile station transmits at the specified power level while
4 executing the Power Up Function.
5 A PUF probe is one or more consecutive Traffic Channel frames. A PUF probe consists of
6 three parts: PUF setup, PUF pulse, and PUF recovery. PUF_SETUP_SIZE is the duration of
7 the PUF setup part, in power control groups. PUF_PULSE_SIZE is the duration of the PUF
8 pulse, in power control groups. The PUF recovery period occupies the remainder of the last
9 frame of the PUF probe.
10 A PUF attempt is a sequence of PUF probes sent by the mobile station in response to a
11 Power Up Function Message. A PUF attempt begins at an offset frame boundary within 80
12 ms of the ACTION_TIME specified in the Power Up Function Message. A PUF attempt can be
13 terminated in one of four ways:
14 • The mobile station receives a Power Up Function Completion Message.
15 • The mobile station has transmitted the maximum number of PUF probes specified in
16 the Power Up Function Message.
17 • The mobile station has transmitted the maximum number of probes allowed at its
18 maximum output power.
19 • The mobile station receives a new Power Up Function Message.
20
2-297
3GPP2 C.S0005-A v6.0
PUF attempt
PUF_INIT_PWRs + (PUF_PWR_STEPs x
CURRENT_PUF_PROBEs) PUF probe
PUF_INIT_PWRs
0 1 M Nominal Output
Nominal output power can

PUF_ vary between PUF probes
INTERVALs
PUF pulse
PUF_SETUP_ COMPLETE_PUF_
SIZEs FRAMEs
PUF_PULSE_SIZEs
PUF setup PUF recovery

PUF probe 0
Offset Frame Offset Frame

Boundary Boundary
1
2 Figure 2.6.4.1.7-1. Structure of PUF Attempt
4 2.6.4.1.7.1 Processing the Power Up Function Message
6 ‘00000110’ (message requires a capability that is not supported by the mobile station) if any
8 • PUF_FREQ_INCLr is set to ‘1’ and PUF_BAND_CLASSr is not supported by the
9 mobile station.
10 • PUF_FREQ_INCLr is set to ‘1’ and the mobile station is unable to re-tune to the PUF
11 Target Frequency during (PUF_SETUP_SIZEr + 1) power control groups.
12 • MOB_P_REVp is not equal to five and the mobile station does not support the Power
13 Up Function.
15 ‘00001100’ (invalid Frequency Assignment), if the Frequency Assignment specified in the
16 message is the same as the Serving Frequency (PUF_FREQ_INCLr is equal to ‘1’,
17 PUF_BAND_CLASSr is equal to CDMABANDs and PUF_CDMA_FREQr is equal to
18 CDMACHs).
2-298
3GPP2 C.S0005-A v6.0
1 If the mobile station is processing a PUF probe, the mobile station shall wait for the PUF
2 probe to complete. It shall then terminate the current PUF attempt. The mobile station
3 shall store the following parameters:
4 • Maximum number of PUF probes transmitted at full power level (MAX_PWR_PUFs =
5 MAX_PWR_PUFr + 1)
6 • Total number of PUF probes (TOTAL_PUF_PROBESs = TOTAL_PUF_PROBESr + 1)
7 • PUF interval (PUF_INTERVALs = PUF_INTERVALr)
8 • Number of PUF setup power control groups (PUF_SETUP_SIZEs =

9 PUF_SETUP_SIZEr + 1)
10 • Number of PUF pulse power control groups (PUF_PULSE_SIZEs = PUF_PULSE_SIZEr

11 +1)
12 • Power increase of initial PUF pulse (PUF_INIT_PWRs = PUF_INIT_PWRr)
13 • Power increase for each successive PUF pulse (PUF_PWR_STEPs =

14 PUF_PWR_STEPr)
15 • Frequency included indicator (PUF_FREQ_INCLs = PUF_FREQ_INCLr)
16 If PUF_FREQ_INCLs equals ‘1’, the mobile station shall store the following:
17 • PUF probe Target Frequency CDMA Channel number (PUF_TF_CDMACHs =

18 PUF_CDMA_FREQr)
19 • PUF probe Target Frequency CDMA band class (PUF_TF_CDMABANDs =

20 PUF_BAND_CLASSr)
21 The mobile station shall set CURRENT_PUF_PROBEs equal to 0.
22 The mobile station shall then begin the PUF attempt at the time specified in 2.6.4.1.7.2.
23 2.6.4.1.7.2 Power Up Function Procedures
24 The mobile station shall process the initial PUF probe beginning at the start of the frame
25 which starts ACTION_TIME_FRAMEr × 20 ms + FRAME_OFFSETs × 1.25 ms after the
26 System Time specified by ACTION_TIMEr. The mobile station shall process additional PUF
27 probes beginning at intervals of PUF_INTERVALs frames from the beginning of the initial
28 PUF probe.
29 The mobile station shall transmit the PUF probes as described in 2.6.4.1.7.2.1 and
30 2.6.4.1.7.2.2.
31 2.6.4.1.7.2.1 PUF Probe On Serving Frequency
32 The mobile station shall process each PUF probe as follows:
33 • The mobile station shall use closed loop power control procedures as specified in
34 2.1.2.3.2 of [2].
35 • The mobile station shall use the gated output procedures specified in 2.1.2.2.2.4
36 and 2.1.3.1.10.3 of [2].
2-299
3GPP2 C.S0005-A v6.0
1 • The mobile station shall control its mean output power as specified in 2.1.2.3.1 of
2 [2].
3 • The mobile station shall monitor its output power during the PUF pulse, and should
4 monitor its output power at least once during each power control group of the PUF
5 pulse. If the mobile station detects that the transmit power level specified in of [2] is
6 equal to or greater than the maximum power output of the mobile station at any
7 time during a PUF pulse, the mobile station shall decrement MAX_PWR_PUFs by one
8 for that PUF pulse.
9 • The mobile station shall transmit the traffic channel preamble for the duration of
10 the PUF probe on the Reverse Fundamental Code Channel.
11 After the processing of each PUF probe, the mobile station shall increment
12 CURRENT_PUF_PROBEs by 1. If MAX_PWR_PUFs is equal to 0, the mobile station shall
13 terminate the PUF attempt. If CURRENT_PUF_PROBEs equal to TOTAL_PUF_PROBEs, the
14 mobile station shall terminate the PUF attempt.
15 2.6.4.1.7.2.2 PUF Probe On PUF Target Frequency
16 The mobile station shall process each PUF probe as follows:
17 • The mobile station shall use closed loop power control procedures as specified in
18 2.1.2.3.2 of [2].
19 • The mobile station shall use the gated output procedures specified in 2.1.3.1.10.3 of
20 [2].
21 • The mobile station shall control its mean output power as specified in 2.1.2.3.1 of
22 [2].
23 • The mobile station shall store the following Serving Frequency parameters from its
24 current configuration:
25 – CDMA Band Class (PUF_SF_CDMABANDs = CDMABANDs)
26 – Frequency assignment (PUF_SF_CDMACHs = CDMACHs)
27 • The mobile station shall monitor its output power during the PUF pulse, and should
28 monitor its output power at least once during each power control group of PUF
29 pulse. If the mobile station detects that the transmit power level specified in
30 2.1.2.3.1 of [2] is equal to or greater than the maximum power output of the mobile
31 station at any time during a PUF pulse, the mobile station shall decrement the
32 MAX_PWR_PUFs by one for that PUF pulse.
33 • At the beginning of the PUF probe, the mobile station shall disable its transmitter,
34 stop processing the Forward Supplemental Code Channel (if any), or the Forward
35 Supplemental Channel (if any), disable all corrections to the mobile station time
36 reference (see 2.1.5 of [2]), tune to the CDMA channel specified by
37 PUF_TF_CDMACHs, and PUF_TF_CDMABANDs and re-enable its transmitter.
38 • The mobile station shall transmit the traffic channel preamble on the Reverse
39 Fundamental Code Channel during the PUF pulse at PUF_TX_PWRs.
2-300
3GPP2 C.S0005-A v6.0
1 • The mobile station should disable its transmitter immediately after the end of the
2 PUF pulse, and shall disable its transmitter before the end of the first power control
3 group after the PUF pulse. It shall then tune to its assigned CDMA channel as given
4 by CDMACHs and CDMABANDs.
5 • If the interval between the time that the mobile station tunes to the PUF Target
6 Frequency and the time that it re-tunes to the Serving Frequency is equal to or
7 greater than (N2m × 0.02) seconds, the mobile station shall wait to receive a period
8 of (N3m × 20) ms with sufficient signal quality (e.g. good frames) on the physical
9 channel corresponding to FPC_PRI_CHANs.
10 • The mobile station shall then re-enable its transmitter and re-enable any
11 adjustments to the mobile station time reference.
12 • If the Forward Supplemental Code Channel assignment has not expired while the
13 mobile station has tuned to the PUF Target Frequency, then the mobile station shall
14 resume processing the Forward Supplemental Code Channels after re-tuning to the
16 • If the Forward Supplemental Channel assignment has not expired while the mobile
17 station has tuned to the PUF Target Frequency, then the mobile station shall
18 resume processing the Forward Supplemental Channels after re-tuning to the
20 • If the Reverse Supplemental Code Channel assignment has not expired while the
21 mobile station has tuned to the PUF Target Frequency, then the mobile station may
22 resume transmitting the Reverse Supplemental Code Channels after re-tuning to the
24 • If the Reverse Supplemental Channel assignment has not expired while the mobile
25 station has tuned to the PUF Target Frequency, then the mobile station may resume
26 transmitting the Reverse Supplemental Code Channels after re-tuning to the Serving
27 Frequency.
28 After the processing of each PUF probe, the mobile station shall increment
29 CURRENT_PUF_PROBEs by one. If MAX_PWR_PUFs is equal to 0, the mobile station shall
30 terminate the PUF attempt. If CURRENT_PUF_PROBEs is equal to TOTAL_PUF_PROBEs,
31 the mobile station shall terminate the PUF attempt.
32 2.6.4.1.7.3 Processing the Power Up Function Completion Message
33 The mobile station shall terminate any PUF attempt no later than the completion of the
34 current probe in progress and shall discard any pending Power Up Function Message. If
35 LOC_INDr is equal to ‘1’, the mobile station may store the following parameters:
36 • Mobile Station Latitude (MS_LATs = MS_LATr)
37 • Mobile Station Longitude (MS_LONGs = MS_LONGr)
38 • Time stamp (MS_LOC_TSTAMPs = MS_LOC_TSTAMPr)
2-301
3GPP2 C.S0005-A v6.0
1 2.6.4.1.8 Forward Traffic Channel Supervision
2 When in the Mobile Station Control on the Traffic Channel State, the mobile station shall
3 continuously monitor the Forward Channel, except:
4 • During a PUF probe in which it transmits on a PUF target frequency (see 2.6.4.1.7),
5 • During a search of pilots on a CDMA Candidate Frequency (see 2.6.6.2.8.3),
6 • During a search of analog frequencies (see 2.6.6.2.10).

7 The mobile station shall monitor the physical channel corresponding to FPC_PRI_CHANs.
8 If the mobile station receives a period of (N2m × 20) ms with insufficient signal quality (e.g.
9 bad frames) on the physical channel corresponding to FPC_PRI_CHANs, it shall disable its
10 transmitter. Thereafter, if the mobile station receives a period of (N3m × 20) ms with
11 sufficient signal quality (e.g. good frames) on the physical channel corresponding to
12 FPC_PRI_CHANs, then the mobile station should re-enable its transmitter.
13 The mobile station shall establish a Forward Traffic Channel fade timer. The timer shall be
14 enabled when the mobile station first enables its transmitter when in the Traffic Channel
15 Initialization Substate of the Mobile Station Control on the Traffic Channel State. The fade
16 timer shall be reset for T5m seconds whenever the mobile station receives a period of (N3m
17 × 20) ms with sufficient signal quality (e.g. good frames) on the physical channel
18 corresponding to FPC_PRI_CHANs. The mobile station shall disable the fade timer when it
19 tunes to a PUF target frequency, and shall re-enable the fade timer at the end of the PUF
20 probe. If the timer expires, the mobile station shall disable its transmitter and declare a
21 loss of the Forward Traffic Channel.
22 The mobile station also enables, disables, and resets the fade timer when it performs a hard
23 handoff or a periodic search, as described in 2.6.6.2.8 and 2.6.6.2.10.
24 2.6.4.1.9 Processing the Extended Release Message and the Extended Release Mini Message
25 • Upon receiving the Extended Release Message or the Extended Release Mini
26 Message, the mobile station shall process the message as follows:
27 – If the mobile station determines that the configuration specified by CH_INDr is
28 not valid, the mobile station shall send a Mobile Station Reject Order with the
29 ORDQ field set to ‘00000111’ (message can not be handled by the current mobile
30 station configuration) and the mobile station shall not perform the remaining
31 procedures in this section.
32 – If the physical channels indicated by the two least significant bits of CH_INDr
33 includes all the physical channels (FCH, DCCH, or both) currently being
34 processed by the mobile station, the lLayer 3 shall send a “release indication” to
35 all Call Control instances and shall perform the following:
36 + Enter the Release Substate with a base station extended release indication if
37 the message is the Extended Release Message.
38 + Enter the Release Substate with a base station extended release mini
39 message indication if the message is the Extended Release Mini Message.
2-302
3GPP2 C.S0005-A v6.0
1 – Otherwise , the mobile station shall perform the following:
2 + If the received message is the Extended Release Message, the mobile station
3 shall send an Extended Release Response Message to the base station. If the
4 received message is the Extended Release Mini Message, the mobile station
5 shall send an Extended Release Response Mini Message to the base station.
6 + The mobile station shall update CH_INDs as follows: If the least significant
7 bit of CH_INDr equals ‘1’, the mobile station shall set CH_INDs = ‘10’.;
8 otherwise (iIf the second most least significant bit of CH_INDr equals ‘01’ ),
9 the mobile station shall set CH_INDs = ‘01’.
10 + If CH_INDr is equal to ‘001’ or ‘101’, the mobile station shall set

11 FPC_PRI_CHANs to ‘1’ at the action time of the message.
12 + If CH_INDr is equal to ‘010’, the mobile station shall set FPC_PRI_CHANs to

13 ‘0’ at the action time of the message.
14 + If the least significant bit of CH_INDr equals ‘1’, then the mobile station shall
15 stop transmitting on R-FCH and stop processing F-FCH at the action time
16 specified by the message.
17 + If the second most significant bit of CH_INDr equals ‘1’, then the mobile
18 station shall stop transmitting on R-DCCH and stop processing F-DCCH at
19 the action time specified by the message.
20 + If GATING_RATE_INCLr equals ‘1’, the mobile station shall set
21 PILOT_GATING_RATEs = PILOT_GATING_RATEr at the action time of the
22 message.
23 + If the most significant bit of CH_INDr equals ‘1’, the mobile station shall set
24 PILOT_GATING_USE_RATE to ‘1’. The mobile station shall start the reverse
25 pilot gating at PILOT_GATING_RATEs at the action time of the message.
26 Furthermore, if the least significant bit of CH_INDr equals ‘1’ (that is, the
27 Fundamental Channel is being released), the mobile station shall store the
28 configuration used for the Fundamental Channel. The mobile station shall
29 cancel the forward and reverse supplemental channel assignment, if any.
30 2.6.4.1.10 Processing the Resource Allocation Message and Resource Allocation Mini
31 Message
32 The mobile station shall process the Resource Allocation Message and the Resource
33 Allocation Mini Message as follows:
34 • The mobile station shall set FPC_PRI_CHANs = FPC_PRI_CHANr at the action time of
35 the message.
2-303
3GPP2 C.S0005-A v6.0
1 • If the Fundamental Channel was previously established prior to transitioning to the

2 Control Hold Mode, the mobile station shall start processing F-FCH and start
3 transmitting on R-FCH at the action time of the message. The mobile station shall
4 establish the Fundamental Channel with the same configuration as previously used,
5 and shall set CH_INDs to ‘11’.
6 • The mobile station shall set PILOT_GATING_USE_RATE to ‘0’ and shall start the
7 continuous reverse pilot at the action time of the message.
8 2.6.4.1.11 Reserved
9 2.6.4.1.12 Processing the Service Configuration Record
10 The mobile station shall update the Service Configuration information record currently in
11 use as follows:
12 • The mobile station shall store the forward Fundamental Channel and Dedicated
13 Control Channel multiplex option [FOR_MUX_OPTIONs = FOR_MUX_OPTIONr].
14 • The mobile station shall store the reverse Fundamental Channel and Dedicated
15 Control Channel multiplex option [REV_MUX_OPTIONs = REV_MUX_OPTIONr].
16 • The mobile station shall store the set of number of bits per frame of the forward
17 Fundamental Channel and Dedicated Control Channel traffic channel
18 [FOR_NUM_BITSs = FOR_NUM_BITSr].
19 • The mobile station shall store the set of number of bits per frame of the reverse
20 Fundamental Channel and Dedicated Control Channel traffic channel
21 [REV_NUM_BITSs = REV_NUM_BITSr].
22 • If a service option connection has been omitted from the service option connection
23 records, the lLayer 3 shall terminate the call control instance (currently existing or
24 pending instantiation) identified by the connection reference corresponding to the
25 omitted service option connection.
26 • If this is the first Service Configuration Record received from the base station in a
27 Service Connect Message, General Handoff Direction Message, or Universal Handoff
28 Direction Message and accepted by the mobile station since entering the Traffic
29 Channel substate, the mobile station shall also identify the Call Control instance
30 currently identified by NULL by the connection reference assigned to the first service
31 option connection, CON_REFr.; otherwise, the mobile station shall identify the Call
32 Control instance corresponding to the first service option connection listed in this
33 Service Configuration information record by the NULL identifier.
34 • The mobile station shall delete all instances of current service option connection
35 records. For each of the NUM_CON_RECr occurrences of the service option
36 connection record (SO_CON_REC[i]), the mobile station shall perform the following:
37 – The mobile station shall store the service option connection reference
38 (SO_CON_RECs[i].CON_REF = CON_REFr).
2-304
3GPP2 C.S0005-A v6.0
1 – The mobile station shall store the service option

2 (SO_CON_RECs[i].SERVICE_OPTION = SERVICE_OPTIONr).
3 – The mobile station shall store the forward traffic channel traffic type
4 (SO_CON_RECs[i].FOR_TRAFFIC = FOR_TRAFFICr).
5 – The mobile station shall store the reverse traffic channel traffic type
6 (SO_CON_RECs[i].REV_TRAFFIC = REV_TRAFFICr).
7 – The mobile station shall store the encryption mode indicator for user information
8 privacy (SO_CON_RECs[i].UI_ENCRYPT_MODE = UI_ENCRYPT_MODEr).
9 – The mobile station shall store the service reference identifier

10 (SO_CON_RECs[i].SR_ID = SR_IDr).
11 – If RLP_INFO_INCLr equals ‘1’, the mobile station shall store the Radio Link
12 Protocol block of bits (SO_CON_RECs[i].RLP_BLOB = RLP_BLOBr).
13 – If QOS_PARMS_INCLr equals ‘1’, the mobile station shall store the QoS
14 parameters block (SO_CON_RECs[i].QOS_PARMS = QOS_PARMSr).
15 • If FCH_CC_INCLr equals ‘1’, the mobile station shall do the following:
16 – The mobile station shall store the indicator for 5ms frames on Fundamental
17 Channel as follows: if FCH_FRAME_SIZEr equals ‘1’, the mobile station shall set
18 FCH_5MS_FRAMESs = ‘1’; otherwise, it is set to ‘0’.
19 - The mobile station shall store the Forward Fundamental Channel Radio
20 Configuration (FOR_FCH_RCs = FOR_FCH_RCr).
21 - The mobile station shall store the Reverse Fundamental Channel Radio
22 Configuration (REV_FCH_RCs = REV_FCH_RCr).
23 • If DCCH_CC_INCLr equals ‘1’, the mobile station shall do the following:
24 - The mobile station shall store the indicator for 5ms frames on Dedicated Control
25 Channel as follows: If DCCH_FRAME_SIZEr equals ‘10’ or ‘11’, the mobile station
26 shall set DCCH_5MS_FRAMESs = ‘1’; otherwise, it is set to ‘0’.
27 - The mobile station shall store the Forward Dedicated Control Channel Radio
28 Configuration (FOR_DCCH_RCs = FOR_DCCH_RCr).
29 - The mobile station shall store the Reverse Dedicated Control Channel Radio
30 Configuration (REV_DCCH_RCs = REV_DCCH_RCr).
31 • If FOR_SCH_CC_INCLr equals ‘1’, the mobile station shall store the NUM_FOR_SCHr
32 occurrences of the Forward Supplemental Channel channel configuration records as
33 follows:
34 - The mobile station shall store the Forward Supplemental Channel Identification
35 (FOR_SCH_ID[FOR_SCH_IDr]s = FOR_SCH_IDr).
2-305
3GPP2 C.S0005-A v6.0
1 - The mobile station shall store the Forward Supplemental Channel Multiplex
2 Option (FOR_SCH_MUX[FOR_SCH_IDr]s = FOR_SCH_MUXr).
3 - The mobile station shall store the Forward Supplemental Channel Radio
4 Configuration (FOR_SCH_RC[FOR_SCH_IDr]s = SCH_RCr).
5 - The mobile station shall store the Forward Supplemental Channel Coding Type
6 (FOR_SCH_CODING[FOR_SCH_IDr]s = CODINGr).
7 - If FRAME_40_USEDr and FRAME_80_USEDr are both equal to '0', the mobile

8 station shall set FOR_SCH_FRAME_LENGTHs[FOR_SCH_IDr] to '00' (i.e., 20 ms
9 frame length).
10 - If FRAME_40_USEDr is equal to '1', the mobile station shall set
11 FOR_SCH_FRAME_LENGTHs[FOR_SCH_IDr] to '01' (i.e., 40 ms frame length).

13 FOR_SCH_FRAME_LENGTHs[FOR_SCH_IDr] to '10' (i.e., 80 ms frame length).
14 - F_MAX_RATE_IDXs[FOR_SCH_IDr] = MAX_RATEr.
15 • If REV_SCH_CC_INCLr equals ‘1’, the mobile station shall store the NUM_REV_SCHr
16 occurrences of the Reverse Supplemental Channel channel configuration records as
17 follows:
18 - The mobile station shall store the Reverse Supplemental Channel Identification
19 (REV_SCH_ID[REV_SCH_IDr]s = REV_SCH_IDr).
20 - The mobile station shall store the Reverse Supplemental Channel Multiplex
21 Option (REV_SCH_MUX[REV_SCH_IDr]s = REV_SCH_MUXr).
22 - The mobile station shall store the Reverse Supplemental Channel Radio
23 Configuration (REV_SCH_RC[REV_SCH_IDr]s = SCH_RCr).
24 - The mobile station shall store the Reverse Supplemental Channel Coding Type
25 (REV_SCH_CODING[REV_SCH_IDr]s = CODINGr).
26 - If FRAME_40_USEDr and FRAME_80_USEDr are both equal to '0', the mobile

27 station shall set REV_SCH_FRAME_LENGTHs[REV_SCH_IDr] to '00' (i.e., 20 ms
28 frame length).
30 REV_SCH_FRAME_LENGTHs[REV_SCH_IDr] to '01' (i.e., 40 ms frame length).

32 REV_SCH_FRAME_LENGTHs[REV_SCH_IDr] to '10' (i.e., 80 ms frame length).
33 - R_MAX_RATE_IDXs[REV_SCH_IDr] = MAX_RATEr.
34 2.6.4.1.13 Processing the Non-Negotiable Service Configuration Record
35 The mobile station shall update the Non-Negotiable Service Configuration information
36 record currently in use as follows:
37 • If FPC_INCLr equals ‘1’, the mobile station shall do the following:
2-306
3GPP2 C.S0005-A v6.0
1 - The mobile station shall store the Power Control Subchannel indicator
2 (FPC_PRI_CHANs = FPC_PRI_CHANr).
3 - The mobile station shall store the forward power control operation mode
4 (FPC_MODE_NO_SCHs = FPC_MODEr).
5 - The mobile station shall set FPC_MODEs = FPC_MODE_NO_SCHs if there is no

6 forward Supplemental Channel assignment in progress (see 2.6.6.2.5.1.1).
7 - If FPC_OLPC_FCH_INCLr equals ‘1’, the mobile station shall do the following:
8 + The mobile station shall store the Fundamental Channel target Frame Error
9 Rate (FPC_FCH_FERs = FPC_FCH_FERr).
10 + The mobile station shall store the minimum Fundamental Channel Outer
11 Loop Eb/Nt setpoint (FPC_FCH_MIN_SETPTs = FPC_FCH_MIN_SETPTr).
12 + The mobile station shall store the maximum Fundamental Channel Outer
13 Loop Eb/Nt setpoint (FPC_FCH_MAX_SETPTs = FPC_FCH_MAX_SETPTr).
14 - If FPC_OLPC_DCCH_INCLr equals ‘1’, the mobile station shall do the following:
15 + The mobile station shall store the Dedicated Control Channel target Frame
16 Error Rate (FPC_DCCH_FERs = FPC_DCCH_FERr).
17 + The mobile station shall store the minimum Dedicated Control Channel
18 Outer Loop Eb/Nt setpoint (FPC_DCCH_MIN_SETPTs =
19 FPC_DCCH_MIN_SETPTr).
20 + The mobile station shall store the maximum Dedicated Control Channel
21 Outer Loop Eb/Nt setpoint (FPC_DCCH_MAX_SETPTs =
22 FPC_DCCH_MAX_SETPTr).
23 • If GATING_RATE_INCLr equals ‘1’, the mobile station shall store the Reverse Pilot
24 Channel gating rate (PILOT_GATING_RATEs = PILOT_GATING_RATEr).
25 • If FOR_SCH_INCLr equals ‘1’, the mobile station shall store the NUM_FOR_SCHr
26 occurrences of the Forward Supplemental Channel information as follows:
27 - The mobile station shall store the Forward Supplemental Channel Multiframe
28 Offset (FOR_SCH_FRAME_OFFSET[FOR_SCH_IDr]s =
29 FOR_SCH_FRAME_OFFSETr).
30 • If REV_SCH_CC_INCLr equals ‘1’, the mobile station shall store the NUM_REV_SCHr
31 occurrences of the Reverse Supplemental Channel information as follows:
32 - The mobile station shall store the Reverse Supplemental Channel Multiframe
33 Offset (REV_SCH_FRAME_OFFSET[REV_SCH_IDr]s =
34 REV_SCH_FRAME_OFFSETr).
35 • The mobile station shall determine the Logical-to-Physical Mapping to be used as

36 follows:
2-307
3GPP2 C.S0005-A v6.0
1 - If LPM_INDr equals ‘00’ and P_REV_IN_USEs is greater than six, the mobile
2 station shall reset the Logical-to-Physical Mapping to their default values as
3 specified in Table 2.6.4.2-1 but with the following modification for requirement 1
4 stated in Table 2.6.4.2-1:
5 + The mobile station shall set the SR_ID field to the value specified in the
6 Service Configuration information record.
7 - If LPM_INDr equals ‘00’ and P_REV_IN_USEs is equal to or less than six, the
8 mobile station shall reset the Logical-to-Physical Mapping to their default values
9 as follows:
10 + Default number of Logical-to-Physical Mapping entries

11 (NUM_LPM_ENTRIESs = ‘0100’).
12 + Default Table(0) Logical-to-Physical Mapping service reference identifier

13 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].SR_IDs = ‘000’).
14 + Default Table(0) Logical-to-Physical Mapping logical resource identifier

15 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].LOGICAL_RESOURCEs =
16 ‘0001’].
17 + Default Table(0) Logical-to-Physical Mapping physical resource identifier:

18 ο If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall set
19 LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].PHYSICAL_RESOURCE
20 s to ‘0000’.
21 ο If CH_INDs is equal to ‘10’, the mobile station shall set

23 s to ‘0001’.
24 + Default Table(0) Logical-to-Physical Mapping forward mapping indicator

25 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].FORWARD_FLAGs = ‘1’).
26 + Default Table(0) Logical-to-Physical Mapping reverse mapping indicator

27 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].REVERSE_FLAGs = ‘1’).
28 + Default Table(0) Logical-to-Physical Mapping priority

29 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].PRIORITYs = ‘0000’).


34 ‘0000’).
35 + Default Table(1) Logical-to-Physical Mapping physical resource identifier:

36 ο If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall set
38 s to ‘0000’.
2-308
3GPP2 C.S0005-A v6.0
1 ο If CH_INDs is equal to ‘10’, the mobile station shall set

3 s to ‘0001’.





14 ‘0000’].
15 + Default Table(2) Logical-to-Physical Mapping physical resource identifier

16 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[2].PHYSICAL_RESOURCEs to
17 ‘0010’).





28 ‘0000’].
29 + Default Table(3) Logical-to-Physical Mapping physical resource identifier

31 ‘0011’).



2-309
3GPP2 C.S0005-A v6.0
1 - If LPM_INDr equals ‘01’, the mobile station shall use the Logical-to-Physical
2 Mapping included in this Non-Negotiable Service Configuration Record. The
3 mobile station shall do the following: The mobile station shall delete the Logical-
4 to-Physical Mapping currently in use. The mobile station shall store the number
5 of Logical-to-Physical Mapping entries (NUM_LPM_ENTRIESs =
th
6 NUM_LPM_ENTRIESr). For each i record of the NUM_LPM_ENTRIESr Logical-
7 to-Physical Mapping records included in the received Non-Negotiable Service
8 Configuration Record:
9 + The mobile station shall store the Logical-to-Physical Mapping service

10 reference identifier (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[i].SR_IDs =
11 SR_IDr).
12 + The mobile station shall store the Logical-to-Physical Mapping logical

13 resource identifier
14 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[i].LOGICAL_RESOURCEs =
15 LOGICAL_RESOURCEr).
16 + The mobile station shall store the Logical-to-Physical Mapping Physical

17 Channel
18 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[i].PHYSICAL_RESOURCEs =
19 PHYSICAL_RESOURCEr).
20 + The mobile station shall store the Logical-to-Physical Mapping forward

21 mapping indicator
22 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[i].FORWARD_FLAGs =
23 FORWARD_FLAGr).
24 + The mobile station shall store the Logical-to-Physical Mapping reverse

25 mapping indicator
26 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[i].REVERSE_FLAGs =
27 REVERSE_FLAGr).
28 + The mobile station shall store the Logical-to-Physical Mapping priority

29 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[i].PRIORITYs = PRIORITYr).
30 - If LPM_INDr equals ‘10’, the mobile station shall use the Logical-to-Physical
31 Mapping currently in use.
32 • For each of the NUM_RECr occurrences of the service-specific records included in
33 the Non-negotiable Service Configuration Record, the mobile station shall perform
34 the following:
35 – The mobile station shall store the Short Data Burst service option number
36 omitted indicator (SDB_SO_OMITs [SR_IDr]= SDB_SO_OMITr ).
37 • The mobile station shall store the following:

38 - USE_FLEX_NUM_BITSs = USE_FLEX_NUM_BITSr
39 - USE_VAR_RATEs = USE_VAR_RATEr
2-310
3GPP2 C.S0005-A v6.0
1 - If USE_VAR_RATEr is equal to ‘1’, then the mobile station shall store the
2 following:
3 + R_INC_RATE_ALLOWEDs = R_INC_RATE_ALLOWEDr
4 + F_INC_RATE_ALLOWEDs = F_INC_RATE_ALLOWEDr
5 • If NUM_BITS_TABLES_INCLr is included and is equal to ‘1’, the mobile station shall

6 store NUM_BITS_TABLES_COUNT+1 instances of the Flexible Rate Table
7 (NUM_RECS triplets of (NUM_BITS_IDX, NUM_BITS, CRC_LEN_IDX) corresponding
8 to each NUM_BITS_TABLE_ID) as follows:
9 - For each of the NUM_RECS occurrences of the three field record consisting of
10 NUM_BITS_IDX, NUM_BITS, and CRC_LEN_IDX the mobile station shall store
11 the following
12 + NUM_BITSs[NUM_BITS_TABLE_IDr][NUM_BITS_IDXr] = NUM_BITSr;
13 + CRC_LEN_IDXs[NUM_BITS_TABLE_IDr][NUM_BITS_IDXr] = CRC_LEN_IDXr;
14 *Otherwise, the mobile station shall use the previously stored values for the
15 NUM_BITSs and CRC_LEN_IDXs.
16 • If USE_OLD_FLEX_MAPPINGr is included and equal to ‘0’, the mobile station shall

18 - FFCH_NBIT_TABLE_IDs = FFCH_NBIT_TABLE_IDr.
19 - RFCH_NBIT_TABLE_IDs = RFCH_NBIT_TABLE_IDr.
20 - FSCH_NBIT_TABLE_IDs[1] = FSCH0_NBIT_TABLE_IDr.
21 - FSCH_NBIT_TABLE_IDs[2] = FSCH1_NBIT_TABLE_IDr.
22 - RSCH_NBIT_TABLE_IDs[1] = RSCH0_NBIT_TABLE_IDr.
23 - RSCH_NBIT_TABLE_IDs[2] = RSCH1_NBIT_TABLE_IDr.
24 - FDCCH_NBIT_TABLE_IDs = FDCCH_NBIT_TABLE_IDr.
25 - If FDCCH_NBIT_TABLE_IDs is not equal to ‘0000’, then the mobile station shall

26 store FDCCH_NBITS_IDXs = FDCCH_NBITS_IDXr.
27 - RDCCH_NBIT_TABLE_IDs = RDCCH_NBIT_TABLE_IDr.
28 - If RDCCH_NBIT_TABLE_IDs is not equal to ‘0000’, then the mobile station shall

29 store RDCCH_NBITS_IDXs = RDCCH_NBITS_IDXr.
30 • Otherwise, the mobile station shall use the previously stored values for the above six
31 variables.
32 • If USE_FLEX_NUM_BITSr is equal to ‘0’, the mobile station shall store the following:
33 - FFCH_NBIT_TABLE_IDs = ‘0000’.
34 - RFCH_NBIT_TABLE_IDs = ‘0000’.
35 - FSCH_NBIT_TABLE_IDs[1] = ‘0000’.
2-311
3GPP2 C.S0005-A v6.0
1 - FSCH_NBIT_TABLE_IDs[2] = ‘0000’.
2 - RSCH_NBIT_TABLE_IDs[1] = ‘0000’.
3 - RSCH_NBIT_TABLE_IDs[2] = ‘0000’.
4 - FDCCH_NBIT_TABLE_IDs = ‘0000’.
5 - FDCCH_NBITS_IDXs = ‘0000’.
6 - RDCCH_NBIT_TABLE_IDs = ‘0000’.
7 - FDCCH_NBITS_IDXs = ‘0000’.
8 • If VAR_TABLES_INCLr is included and is equal to ‘1’, the mobile station shall store
9 VAR_RATE_TABLES_COUNT+1 instances of the Variable Rate Mask Table
10 (NUM_RECS pairs of (NUM_BITS_IDX, MASK) corresponding to each
11 VAR_RATE_TABLE_ID) as follows:
12 - For each of the NUM_RECS + 1 occurrences of the two-field record consisting of

13 NUM_BITS_IDX and MASK the mobile station shall store the following:
14 + MASKs[VAR_RATE_TABLE_IDr][NUM_BITS_IDXr] = MASKr;
15 - If FSCH_VAR_TABLE_IDs[1] is not equal to ‘000’, then the mobile station shall

17 + For row=1, …, 15
18 ο For i=1, …, row,

th
19 ◊ If the i bit position in MASKs[FSCH_VAR_TABLE_IDs[1]][row] is equal
20 to '1', then the mobile station shall set
21 VAR_FSCH_RATE_OFFSETs[1][row][i] to i,
22 ◊ otherwise, the mobile shall set VAR_FSCH_RATE_OFFSETs[1][row][i]

23 to '0'.
24 - If FSCH_VAR_TABLE_IDs[2] is not equal to ‘000’, then the mobile station shall
26 + For row=1, …, 15
27 ο For i=1, …, row,

th
28 ◊ If the i bit position in MASKs[FSCH_VAR_TABLE_IDs[2]][row] is equal
29 to '1', then the mobile station shall set
30 VAR_FSCH_RATE_OFFSETs[2][row][i] to i,
31 ◊ otherwise, the mobile shall set VAR_FSCH_RATE_OFFSETs[2][row][i]

32 to '0'.
33 - If RSCH_VAR_TABLE_IDs[1] is not equal to ‘000’, then the mobile station shall
35 + For row=1, …, 15
2-312
3GPP2 C.S0005-A v6.0
1 ο For i=1, …, row,

th
2 ◊ If the i bit position in MASKs[RSCH_VAR_TABLE_IDs[1]][row] is
3 equal to '1', then the mobile station shall set
4 VAR_RSCH_RATE_OFFSETs[1][row][i] to i,
5 ◊ otherwise, the mobile shall set VAR_RSCH_RATE_OFFSETs[1][row][i]

6 to '0'.
7 - If RSCH_VAR_TABLE_IDs[2] is not equal to ‘000’, then the mobile station shall
9 + For row=1, …, 15
10 ο For i=1, …, row,

th
11 ◊ If the i bit position in MASKs[RSCH_VAR_TABLE_IDs[2]][row] is
12 equal to '1', then the mobile station shall set
13 VAR_RSCH_RATE_OFFSETs[2][row][i] to i,
14 ◊ otherwise, the mobile shall set VAR_RSCH_RATE_OFFSETs[2][row][i]

15 to '0'.
16 Else (if USE_OLD_VAR_TABLEr is included and equal to ‘1’), use the previously
17 stored values for VAR_RSCH_RATE_OFFSETs and VAR_FSCH_RATE_OFFSETs.
18 • If USE_OLD_VAR_MAPPINGr is included and equal to ‘0’, the mobile station shall

20 - FSCH_VAR_TABLE_IDs[1] = FSCH0_VAR_TABLE_IDr.
21 - FSCH_VAR_TABLE_IDs[2] = FSCH1_VAR_TABLE_IDr.
22 - RSCH_VAR_TABLE_IDs[1] = RSCH0_VAR_TABLE_IDr.
23 - RSCH_VAR_TABLE_IDs[2] = RSCH1_VAR_TABLE_IDr.
24 • Otherwise, use the previously stored values for the above four variables.
25 • If USE_VAR_RATEr is equal to ‘0’, the mobile station shall store the following:
26 - FSCH_VAR_TABLE_IDs[1] = ‘000’.
27 - FSCH_VAR_TABLE_IDs[2] = ‘000’.
28 - RSCH_VAR_TABLE_IDs[1] = ‘000’.
29 - RSCH_VAR_TABLE_IDs[2] = ‘000’.
30 • If LTU_TABLES_ INCLr is included and is equal to ‘1’, then the mobile station shall
31 store NUM_LTU_TABLES + 1 instances of the LTU Table which determines the
32 number of LTUs per frame for convolutionally encoded supplemental channels for
33 each number of bits per frame. Each LTU Table is identified by its LTU_TABLE_ID.
34 - For each of the NUM_ROWS +1 rows of the LTU Size Table, the mobile station
2-313
3GPP2 C.S0005-A v6.0
1 + LTU_TABs[LTU_TABLE_IDr][NBITS_IDXr] = LTU_LENNUM_LTUSr
2 *Else (if USE_OLD_LTU_TABLE is included and equal to ‘1’), the mobile station shall
3 use the previously stored values for the LTU_TABs.
4 • If USE_OLD_LTU_MAPPINGr is included and is equal to ‘0’, then the mobile station

6 - FSCH_LTU_TAB_IDs[1] = FSCH0_LTU_TAB_IDr
7 - FSCH_LTU_TAB_IDs[2] = FSCH1_LTU_TAB_IDr
8 - RSCH_LTU_TAB_IDs[1] = RSCH0_LTU_TAB_IDr
9 - RSCH_LTU_TAB_IDs[2] = RSCH1_LTU_TAB_IDr
10 • Else (if USE_OLD_LTU_MAPPINGr is included and is equal to ‘1’), the mobile station
11 shall use the previously stored values for the above four variables.
12 • If LTU_INFO_INCLr is equal to ‘0’, then the mobile station shall store the following:
13 - FSCH_LTU_TAB_IDs[1] = ‘000’
14 - FSCH_LTU_TAB_IDs[2] = ‘000’
15 - RSCH_LTU_TAB_IDs[1] = ‘000’
16 - RSCH_LTU_TAB_IDs[2] = ‘000’
17 • If PARTITION_TABLES_INCLr is included and is equal to ‘1’, then the mobile station

18 shall store NUM_PARTITION_TABLES + 1 instances of the Partition Table which
19 determines the number of bits allocated to each service per FCH or DCCH frame as
20 follows. Each Partition Table is identified by its PARTITION_TABLE_ID.
21 - For each of the NUM_ROWS+1 rows of the Partition Table, the mobile station
23 + PART_TABs[PARTITION_TABLE_IDr][CATEGORYr].MUX_HEADER_LEN =
24 MUX_HEADER_LENr
25 + PART_TABs[PARTITION_TABLE_IDr][CATEGORYr].MUX_HEADER =
26 MUX_HEADERr
27 + PART_TABs[PARTITION_TABLE_IDr][CATEGORYr]. NUM_PARTITIONS =
28 NUM_PARTITIONSr
29 + For i=1, …, NUM_PARTITIONS+1; the mobile station shall store the following:
30 ο PART_TABs[PARTITION_TABLE_IDr][CATEGORYr]. PARTITION_SR_ID[i] =
31 SR_IDr
32 ο PART_TABs[PARTITION_TABLE_IDr][CATEGORYr]. PARTITION_NBITS[i] =
33 SRV_NUM_BITSr
34 • Else (if PARTITION_TABLES_INCLr is included and is equal to ‘0’), the mobile station
35 shall use the previously stored values for the PART_TABs.
2-314
3GPP2 C.S0005-A v6.0
1 • If USE_OLD_PART_MAPPINGr is included and is equal to ‘0’, then the mobile station

3 - FFCH_PART_TAB_IDs = FFCH_PART_TAB_IDr
4 - RFCH_PART_TAB_IDs = RFCH_PART_TAB_IDr
5 - FDCCH_PART_TAB_IDs = FDCCH_PART_TAB_IDr
6 - RDCCH_PART_TAB_IDs = RDCCH_PART_TAB_IDr
7 *Else (if USE_OLD_PART_MAPPINGr is included and equal to ‘1’), the mobile station
8 shall use the previously stored values for the above four variables.
9 • If USE_FLEX_NUM_BITSs is equal to ‘0’, then the mobile station shall store the
10 following:
11 - FFCH_PART_TAB_IDs = ‘000’
12 - RFCH_PART_TAB_IDs = ‘000’
13 - FDCCH_PART_TAB_IDs = ‘000’
14 - RDCCH_PART_TAB_IDs = ‘000’
15 2.6.4.1.14 Processing the Security Mode Command Message
16 The mobile station shall process the received Security Mode Command Message as follows:
17 • The mobile station shall set D_SIG_ENCRYPT_MODEs to D_SIG_ENCRYPT_MODEr.
18 *For each of the NUM_RECSr instances of the two-field record consisting of

19 CON_REF and UI_ENCRYPT_MODE, the mobile station shall set
20 UI_ENCRYPT_MODEs[CON_REFr] to UI_ENCRYPT_MODEr.
21 • If D_SIG_ENCRYPT_MODEr is not equal to ‘000’, the mobile station shall perform

22 the following:
23 − Set ENCRYPT_MODEs to ‘11’
24 − Set ENC_KEYs to the most recently generated CMEAKEY in the mobile station
25 associated with the AUTHR of the Origination Message or Page Response
26 Message
27 − Set EXT_ENCRYPT_SEQ[0] and EXT_ENCRYPT_SEQ[1] to 256 × ENC_SEQ_H if

28 either of the following conditions is true:
29 + The ENC_SEQ_H field is included in the last Origination Message or Page

30 Response Message and EXT_ENCRYPT_SEQ[0] and EXT_ENCRYPT_SEQ[1]
31 have not been initialized by the last Channel Assignment Message, Extended
32 Channel Assignment Message, or an earlier f-dsch Security Mode Command
33 Message (see 2.3.12.4.1.3).
34 + This message is a response to a Security Mode Request Message (see

35 2.3.12.4.1.3) that includes an ENC_SEQ_H field.
2-315
3GPP2 C.S0005-A v6.0
1 • For each of the service option connections specified by the CON_REF field included
2 in this message, the mobile station shall set the user information encryption mode
3 in the corresponding service option connection record (SO_CON_RECs[i]) to
4 UI_ENCRYPT_MODEr) (i.e., set SO_CON_RECs[i].UI_ENCRYPT_MODE to
5 UI_ENCRYPT_MODEr where SO_CON_RECs[i].CON_REF = CON_REFr).
6 • For each of the service option connections specified by the CON_REF field included
7 in this message, at the action time of the message the mobile station shall start
8 encrypting user information (e.g., voice and data) using the encryption algorithm
9 specified by SO_CON_RECs[i].UI_ENCRYPT_MODE where
10 SO_CON_RECs[i].CON_REF = CON_REFr .(see Table 3.7.4.5-1).
11 • If USE_NEW_KEYr is not included, or is included and is set to ‘1’, the mobile station
12 shall use the session key generated at the most recent registration for encryption of
13 signaling and user information. The mobile station shall store the session key in
14 KEYs[KEY_SEQ_NEWs-p]. The mobile station shall store KEY_SIZEr in KEY_SIZEs.
15 The mobile station shall then increment the variable KEY_SEQ_NEWs-p by one
16 (modulo 16). If ENC_KEY_SIZEr is included, the mobile station shall set
18 If USE_NEW_KEYr is included and is set to ‘0’, then the mobile station shall use
20 • If C_SIG_ENCRYPT_MODE is included, the mobile station shall set

22 2.6.4.2 Traffic Channel Initialization Substate
23 In this substate, the mobile station verifies that it can receive the Forward Traffic Channel
24 and begins transmitting on the Reverse Traffic Channel.
25 Upon entering the Traffic Channel Initialization Substate, the mobile station shall perform
26 the following:
27 • The mobile station shall perform registration initialization as specified in 2.6.5.5.4.1.
28 • Layer 3 shall send an L2-Supervision.Request primitive to Layer 2 to reset the

29 acknowledgment procedures as specified in 2.2.1.1 and 2.2.2.1 of [4].
30 • The mobile station shall initialize Forward Traffic Channel power control as specified
31 in 2.6.4.1.1.1.
32 • The mobile station shall initialize the list TAG_OUTSTANDING_LIST to be empty.

33 • If P_REV_IN_USEs is less than seven, the mobile station shall set CS_SUPPORTEDs
34 to ‘0’.
35 • The mobile station shall set the following variables to their initial default values
36 given below:
2-316
3GPP2 C.S0005-A v6.0
1 – If the mobile station has included the SYNC_ID field in the Origination Message
2 or Page Response Message, the mobile station shall not reset any of the service
3 configuration parameters (i.e. those signaled via the Service Configuration
4 information record and the Non-Negotiable Service Configuration information
5 record) to their default values.
6 – Default power control step size

7 (PWR_CNTL_STEPs = ‘000’)
8 – Default Reverse Supplemental Channel power offset adjustment relative to

9 Reverse Pilot Channel power
10 + RLGAIN_SCH_PILOTs [0]= ‘000000’
11 + RLGAIN_SCH_PILOTs [1]= ‘000000’
12 – Default Reverse Discontinuous Transmission Duration on Reverse Supplemental

13 Code Channel (REV_DTX_DURATIONs = ‘0000’)
14 – Default Reverse Discontinuous Transmission Duration on Reverse Supplemental

15 Channel (REV_SCH_DTX_DURATIONs = ‘0000’)
16 – Default channel on which the mobile station is to perform the primary inner loop
17 estimation and the base station is to multiplex the Power Control Subchannel:
18 + If CH_INDs is equal to ‘01’, the mobile station shall set FPC_PRI_CHANs to
19 ‘0’.
20 + If CH_INDs is equal to ‘10’, the mobile station shall set FPC_PRI_CHANs to
21 ‘1’.
22 – Default forward power control operation mode used except during the forward
23 Supplemental Channel interval
24 (FPC_MODE_NO_SCHs = ‘000’)
25 – Default forward power control operation mode used during the forward
26 Supplemental Channel interval
27 (FPC_MODE_SCHs = ‘000’)
28 – Default forward power control operation mode

29 (FPC_MODEs = ‘000’)
30 – Slotted timer (T_SLOTTEDs =T74m)
31 – Default Reverse Pilot Channel gating (PILOT_GATING_USE_RATE=‘0’)
32 – Default begin preamble for Reverse Supplemental Code Channels

33 (BEGIN_PREAMBLEs = ‘000’)
34 – Default resume preamble for Reverse Supplemental Code Channels

35 (RESUME_PREAMBLEs = ‘000’)
36 – Default start time for Reverse Supplemental Code Channel assignment

37 (REV_START_TIMEs = NULL)
38 – Default retry delays:
2-317
3GPP2 C.S0005-A v6.0
1 + RETRY_DELAYs[010] = 0
2 + RETRY_DELAYs[011] = 0
3 – Default neighbor pilot strength measurement threshold reporting offset

4 (T_MULCHANs = ‘000’)
5 – Default start time for forward Supplemental Code Channel Assignment

6 (FOR_START_TIMEs = NULL)
7 – Default number of Reverse Supplemental Code Channels

8 (NUM_REV_CODESs = ‘000’)
9 – Default reverse use T_ADD abort indicator

10 (USE_T_ADD_ABORTs = ‘0’)
11 – Default Supplemental Channel Request Message sequence number

12 (SCRM_SEQ_NUMs = NULL)
13 – Default indicator to ignore reverse Supplemental Code Channel assignment

14 Supplemental Channel Assignment Message
15 (IGNORE_SCAMs = ‘0’)
16 – Default indicator to ignore reverse Supplemental Channel assignment Extended

17 Supplemental Channel Assignment Message
18 (IGNORE_ESCAMs = ‘0’)
19 – Default maximum wait time on the CDMA Candidate Frequency

20 (CF_WAIT_TIMEs = ‘1111’)
21 – Default search period for the candidate search

22 (SEARCH_PERIODs = ‘1111’)
23 – Default search window size for the Candidate Frequency Search Set
24 (CF_SRCH_WIN_Ns = SRCH_WIN_Ns)
25 – Default search window size for the Remaining Set on the CDMA Candidate
26 Frequency (CF_SRCH_WIN_Rs = SRCH_WIN_Rs)
27 – Default pilot PN sequence offset increment for the CDMA Candidate Frequency
28 (CF_PILOT_INCs = PILOT_INCs)
29 – Default Candidate Frequency search priorities included indicator

30 (CF_SEARCH_PRIORITY_INCLs =‘0’)
31 – Default Candidate Frequency search window size included indicator

32 (CF_SRCH_WIN_NGHBR_INCLs = ‘0’)
33 – Default Candidate Frequency search window offset included indicator

34 (CF_SRCH_OFFSET_INCLs = ‘0’)
35 – Default periodic search indicator

36 (PERIODIC_SEARCHs = ‘0’)
37 – Default return-if-handoff-fail indicator

38 (RETURN_IF_HANDOFF_FAILs = ‘0’)
2-318
3GPP2 C.S0005-A v6.0
1 – Default total pilot Ec/Io threshold

2 (MIN_TOTAL_PILOT_EC_IOs = ‘00000’)
3 – Default total pilot Ec threshold

4 (SF_TOTAL_EC_THRESHs = ‘11111’)
5 – Default total pilot Ec/Io threshold

6 (SF_TOTAL_EC_IO_THRESHs = ‘11111’)
7 – Default received power difference threshold

8 (DIFF_RX_PWR_THRESHs = ‘00000’)
9 – Default maximum wait time on the CDMA Target Frequency

10 (TF_WAIT_TIMEs = ‘1111’)
11 – Default Candidate Frequency Search Set

12 (Candidate Frequency Search Set is empty)
13 – Default Analog Frequency Search Set

14 (Analog Frequency Search Set is empty)
15 – Default Candidate Frequency CDMA band

16 (CF_CDMABANDs = NULL)
17 – Default Candidate Frequency CDMA channel

18 (CF_CDMACHs = NULL)
19 – Default indicator for 5ms frames on Fundamental Channel

20 (FCH_5MS_FRAMESs = ‘0’)
21 – Default indicator for 5ms frames on Dedicated Control Channel

22 (DCCH_5MS_FRAMESs = ‘0’)
23 – Default start time unit for Supplemental Channel

24 (START_TIME_UNITs = ‘000’)
25 – Default Forward Supplemental Channel FER report indicator

26 (FOR_SCH_FER_REPs = ‘0’)
27 – Default Forward Supplemental Channel Configuration parameters:
28 + Set the Forward Supplemental Channel frame length

29 FOR_SCH_FRAME_LENGTHs[0] to NULL.
30 + Set the Forward Supplemental Channel Multiplex Option FOR_SCH_MUXs[0]

31 to NULL.
32 + Set the Forward Supplemental Channel Radio Configuration

33 FOR_SCH_RCs[0] to NULL.
34 + Set the Forward Supplemental Channel Coding Type FOR_SCH_CODINGs[0]

35 to NULL.
36 + Set QOF_IDs[0][SCCL_INDEXs][i] to NULL, for all integer values of i from 0 to
37 15.
2-319
3GPP2 C.S0005-A v6.0
1 + Set FOR_SCH_CC_INDEXs [0][SCCL_INDEXs][i] to NULL, for all integer

2 values of i from 0 to 15.
3 + Set the Forward Supplemental Channel frame length

4 FOR_SCH_FRAME_LENGTHs[1] to NULL.
5 + Set the Forward Supplemental Channel Multiplex Option FOR_SCH_MUXs[1]

6 to NULL.
7 + Set the Forward Supplemental Channel Radio Configuration

8 FOR_SCH_RCs[1] to NULL.
9 + Set the Forward Supplemental Channel Coding Type FOR_SCH_CODINGs[1]

10 to NULL.
11 + Set QOF_IDs[1][SCCL_INDEXs][i] to NULL, for all integer values of i from 0 to
12 15.
13 + Set FOR_SCH_CC_INDEXs [1][SCCL_INDEXs][i] to NULL, for all integer
14 values of i from 0 to 15.
15 – Call Origination Transaction Identifier

16 (TAGs = ‘0000’).
17 – Default Reverse Supplemental Channel Configuration parameters:

18 + REV_WALSH_IDs[0][0000] = 1
19 + REV_WALSH_IDs[0][0001] = 1
20 + REV_WALSH_IDs[0][0010] = 1
21 + REV_WALSH_IDs[0][0011] = 1
22 + REV_WALSH_IDs[0][0100] = 0
23 + REV_WALSH_IDs[0][0101] = 0
24 + REV_WALSH_IDs[0][0110] = 0
25 + REV_WALSH_IDs[1][0000] = 1
26 + REV_WALSH_IDs[1][0001] = 1
27 + REV_WALSH_IDs[1][0010] = 1
28 + REV_WALSH_IDs[1][0011] = 0
29 + REV_WALSH_IDs[1][0100] = 0
30 + REV_WALSH_IDs[1][0101] = 0
31 + REV_WALSH_IDs[1][0110] = 0
32 + Set the Reverse Supplemental Channel frame length

33 REV_SCH_FRAME_LENGTHs[0] to NULL.
34 + Set the Reverse Supplemental Channel Multiplex Option REV_SCH_MUXs[0]

35 to NULL.
2-320
3GPP2 C.S0005-A v6.0
1 + Set the Reverse Supplemental Channel Radio Configuration

2 REV_SCH_RCs[0] to NULL.
3 + Set the Reverse Supplemental Channel Coding Type REV_SCH_CODINGs[0]

4 to NULL.
5 + Set the Reverse Supplemental Channel frame length

6 REV_SCH_FRAME_LENGTHs[1] to NULL.
7 + Set the Reverse Supplemental Channel Multiplex Option REV_SCH_MUXs[1]

8 to NULL.
9 + Set the Reverse Supplemental Channel Radio Configuration

10 REV_SCH_RCs[1] to NULL.
11 + Set the Reverse Supplemental Channel Coding Type REV_SCH_CODINGs[1]

12 to NULL.
13
14 • If P_REV_IN_USEs is greater than six, the mobile station shall initialize the logical to
15 physical mapping table (LOGICAL_TO_PHYSICAL_MAPPING_TABLE) according to
16 the requirements in Table 2.6.4.2-1:
17
18 Table 2.6.4.2-1. Default Logical to Physical Mapping Table
SR_ID LOGICAL_ PHYSICAL_ FORWARD_ REVERSE_ PRIORITY
RESOURCE RESOURCE FLAG FLAG
000 0001 (shall be set 1 1 0000

according to
requirement 2)
(shall be set 0000 (shall be set 1 1 0000

according to according to
requirement 1) requirement 3)
19 Where requirement 1 is as follows:
20 + The SR_ID field shall be set to NULL.
21 Requirement 2 is as follows:
22 + If CH_INDs is equal to ‘01’, the PHYSICAL_RESOURCE field shall be set to

23 ‘0000’.
24 + If CH_INDs is equal to ‘10’, the PHYSICAL_RESOURCE field shall be set to
25 ‘0001’.
2-321
3GPP2 C.S0005-A v6.0
1 + If CH_INDs is equal to ‘11’, there shall be two entries in the default LPM table
2 where the PHYSICAL_RESOURCE field shall be set to ‘0000’ and ‘0001’
3 respectively.
4 Requirement 3 is as follows:
5 + If CH_INDs is equal to ‘01’:
6 ο If the Radio Configuration in use is less than three, the

7 PHYSICAL_RESOURCE field shall be set to ‘0000’; otherwise, there shall
8 be three entries in the default LPM table where the
9 PHYSICAL_RESOURCE field shall be set to ‘0000’, ‘0010’, and ‘0011’
10 respectively.
12 ο There shall be three entries in the default LPM table where the
13 PHYSICAL_RESOURCE field shall be set to ‘0001’, ‘0010’, and ‘0011’
14 respectively.
16 ο There shall be four entries in the default LPM table where the
17 PHYSICAL_RESOURCE field shall be set to ‘0000’, ‘0001’, ‘0010’, and
18 ‘0011’ respectively.
19 • If P_REV_IN_USEs is equal to or less than six, the mobile station shall initialize the
20 logical to physical mapping table (LOGICAL_TO_PHYSICAL_MAPPING_TABLE) as
21 follows:
22 – Default number of Logical-to-Physical Mapping entries

23 (NUM_LPM_ENTRIESs = ‘0100’)
24 – Default Table(0) Logical-to-Physical Mapping service reference identifier

25 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].SR_IDs = ‘000’)
26 – Default Table(0) Logical-to-Physical Mapping logical resource identifier

27 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].LOGICAL_RESOURCEs = ‘0001’)
28 – Default Table(0) Logical-to-Physical Mapping physical resource identifier:

29 + If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall set
30 LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].PHYSICAL_RESOURCEs to
31 ‘0000’.
32 + If CH_INDs is equal to ‘10’, the mobile station shall set
34 ‘0001’.
35 – Default Table(0) Logical-to-Physical Mapping forward mapping indicator

36 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].FORWARD_FLAGs = ‘1’)
37 – Default Table(0) Logical-to-Physical Mapping reverse mapping indicator

38 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].REVERSE_FLAGs = ‘1’)
2-322
3GPP2 C.S0005-A v6.0
1 – Default Table(0) Logical-to-Physical Mapping priority

2 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].PRIORITYs = ‘0000’)


7 – Default Table(1) Logical-to-Physical Mapping physical resource identifier:

8 + If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall set
10 ‘0000’.
11 + If CH_INDs is equal to ‘10’, the mobile station shall set
13 ‘0001’.





24 – Default Table(2) Logical-to-Physical Mapping physical resource identifier

26 ‘0010’).





2-323
3GPP2 C.S0005-A v6.0
1 – Default Table(3) Logical-to-Physical Mapping physical resource identifier

3 ‘0011’).



10 • The mobile station shall disable the TMS_Slotted timer, and set SLOTTEDs to YES.
11 • If the ASSIGN_MODEr field from the Channel Assignment Message equals ‘000’, the
12 mobile station shall set SERV_NEGs to disabled.
13 • If the ASSIGN_MODEr field from the Channel Assignment Message equals ‘100’, the
14 mobile station shall set SERV_NEGs to enabled.
15 • The mobile station shall determine the service configuration as follows:

16 – If SERV_NEGs equals disabled, the initial service configuration shall include
17 Multiplex Option 1 and Radio Configuration 1 for both the Forward and Reverse
18 Traffic Channels, and shall include no service option connections.
19 – If SERV_NEGs equals enabled, and if GRANTED_MODEs equals ‘00’, the initial
20 service configuration shall include the multiplex option and radio configuration
21 for the Forward and Reverse Traffic Channels as specified by
22 DEFAULT_CONFIGs, and shall include no service option connections.
23 – If SERV_NEGs equals enabled and GRANTED_MODEs equals ‘01’ or ‘10’;, the

24 initial service configuration shall include the default Forward and Reverse Traffic
25 Channel multiplex options and transmission rates corresponding to the service
26 option requested by the mobile station in the Origination Message, in the case of
27 a mobile station originated call, or the Page Response Message, in the case of a
28 mobile station terminated that are derived from the radio configurations
29 corresponding to the Table 3.7.2.3.2.21-7call, and shall include no service option
30 connections.
31 + If the mobile station enters the Traffic Channel Initialization Substate because
32 of receiving the Channel Assignment Message, the initial service
33 configuration shall include the default Forward and Reverse Traffic Channel
34 multiplex options and transmission rates corresponding to the service option
35 requested by the mobile station in the Origination Message, in the case of a
36 mobile station originated call, or the Page Response Message, in the case of a
37 mobile station terminated, and shall include no service option connections.
2-324
3GPP2 C.S0005-A v6.0
1 + If the mobile station enters the Traffic Channel Initialization Substate because
2 of receiving the Extended Channel Assignment Message, the initial service
4 multiplex options that are derived from the radio configurations
5 corresponding to the Table 3.7.2.3.2.21-7, and shall include no service
6 option connections.
7 – If SERV_NEGs equals disabled, the mobile station shall perform the following:
8 + If the call is mobile station originated and the Origination Message requests a
9 special service option, the mobile station shall set SO_REQs to the special
10 service option number.
11 + If the call is mobile station originated and the Origination Message does not
12 request a special service option, the mobile station shall set SO_REQs to 1
13 (the default service option number).
14 + If the call is mobile station terminated, the mobile station shall set SO_REQs
15 to the service option number requested in the Page Response Message.
16 While in the Traffic Channel Initialization Substate, the mobile station shall perform the
17 following:
18 • The mobile station shall monitor Forward Traffic Channels associated with one or
19 more pilots in the Active Set.
20 • The mobile station shall perform pilot strength measurements as specified in

21 2.6.6.2.2, but shall not send Pilot Strength Measurement Messages or Extended Pilot
22 Strength Measurement Messages.
23 • The mobile station shall perform registration timer maintenance as specified in

24 2.6.5.5.4.2.
25 • If the bits of TMSI_CODEs-p are not all equal to ‘1’ and if System Time (in 80 ms
31 If the mobile station does not support the assigned CDMA Channel (see 2.1.1 and 3.1.1 of
32 [2]) or all of the assigned Forward Traffic code channels (see 2.1.3.1.9 of [2]), the mobile
33 station shall enter the System Determination Substate of the Mobile Station Initialization
34 State with an error indication (see 2.6.1.1).
35 If the mobile station supports the assigned CDMA Channel and the assigned Forward
36 Traffic code channels, the mobile station shall perform the following:
37 • The mobile station shall tune to the assigned CDMA Channel.
38 • The mobile station shall set its code channel for the assigned Forward Traffic code
39 channel.
2-325
3GPP2 C.S0005-A v6.0
1 • The mobile station shall set its Forward and Reverse Traffic Channel frame offsets to
2 the assigned frame offset as determined by FRAME_OFFSETs.
3 • The mobile station shall set its Forward and Reverse Traffic Channel long code
4 masks to the public long code mask (see 2.1.3.1.12 of [2]).
5 If the mobile station does not receive a period of (N5m × 20) ms with sufficient signal
6 quality (e.g. good frames) on the physical channel corresponding to FPC_PRI_CHANs within
7 T50m seconds after entering this substate, the mobile station shall enter the System
8 Determination Substate of the Mobile Station Initialization State with a system lost indication
9 (see 2.6.1.1).
10 If the mobile station receives a period of (N5m × 20) ms with sufficient signal quality (e.g.
11 good frames) on the physical channel corresponding to FPC_PRI_CHANs within T50m
12 seconds after entering this substate, the mobile station shall perform the following
13 additional functions while it remains in the Traffic Channel Initialization Substate:
14 • The mobile station shall perform Forward Traffic Channel supervision as specified in
15 2.6.4.1.8. If a loss of the Forward Traffic Channel is declared, the mobile station
16 shall enter the System Determination Substate of the Mobile Station Initialization State
17 with a system lost indication (see 2.6.1.1).
18 • The mobile station shall adjust its transmit power as specified in 2.1.2.3 of [2].
19 • The mobile station shall transmit the Traffic Channel preamble as specified in
20 2.1.3.6.2.3 and 2.1.3.7.2.3 of [2], and Layer 3 shall send an acquiring dedicated
21 channel indication to Layer 2 (see 2.2.2.1.2 of [4]).
22 • The mobile station shall process Forward Traffic Channel signaling traffic and shall
23 discard other types of Forward Traffic Channel traffic.
24 • If Layer 3 receives a L2-Condition.Notification primitive from Layer 2 indicating an

25 acknowledgment failure, the mobile station shall disable its transmitter and enter
28 The mobile station should provide diversity combining of the Forward Traffic Channels
29 associated with pilots in the Active Set if the mobile station receives multiple pilots in the
30 Extended Channel Assignment Message.
31 If Layer 3 does not receive a forward dedicated channel acquired indication from Layer 2 (see
32 2.2.2.1.2 of [4]) within T51m seconds after the first occurrence of receiving a period of (N5m
33 × 20) ms with sufficient signal quality (e.g. good frames) on the physical channel
34 corresponding to FPC_PRI_CHANs, the mobile station shall disable its transmitter and enter
35 the System Determination Substate of the Mobile Station Initialization State with a system lost
36 indication (see 2.6.1.1).
37 If Layer 3 receives a forward dedicated channel acquired indication from Layer 2 within
38 T51m seconds after the first occurrence of receiving a period of (N5m × 20) ms with
39 sufficient signal quality (e.g. good frames) on the physical channel corresponding to
40 FPC_PRI_CHANs, the mobile station shall perform the following:
2-326
3GPP2 C.S0005-A v6.0
1 • If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall begin transmitting on the
2 Reverse Fundamental Channel.
3 • If CH_INDs is equal to ‘10’ or ‘11’, the mobile station shall begin transmitting on the
4 Reverse Dedicated Control Channel when the mobile station has user data or
5 signaling traffic to send on the Reverse Dedicated Control Channel.
6 • If SERV_NEGs equals disabled, the mobile station shall activate the SO Negotiation
7 Subfunction.
8 • If SERV_NEGs equals enabled and the GRANTED_MODEs is ‘00’ or ‘01’, the mobile
10 • If SERV_NEGs equals enabled and the GRANTED_MODEs is ‘10’, the mobile station
12 • The lLayer 3 shall instantiate a Call Control instance (as specified in 2.6.10). The
13 lLayer 3 shall assign a default identifier of NULL to this Call Control instance.
14 • The lLayer 3 shall enter the Traffic Channel Substate.
15 2.6.4.3 Traffic Channel Substate
16 In this substate, the mobile station may exchange Traffic Channel frames with the base
17 station in accordance with the current service configuration. The mobile station may
18 perform the gating operation of Reverse Pilot Channel.
19 The mobile station can be in the Active Mode or Control Hold Mode while in this substate.
20 The following are the attributes when the mobile station is in the Active Mode of Traffic
21 Channel Substate:
22 • PILOT_GATING_USE_RATE is set to ‘0’ (i.e., the reverse pilot (r-pich) is not gated).
23 • Flow of data traffic is permitted by the Multiplex Sublayer.
24 The following are the attributes when the mobile station is in the Control Hold Mode of
25 Traffic Channel Substate:
26 • PILOT_GATING_USE_RATE is set to ‘1’.

27 • The reverse pilot (r-pich) may be gated (if PILOT_GATING_RATEs is not equal to ‘00’).
28 • Flow of data traffic is blocked by the Multiplex Sublayer.

29 Figure 2.6.4.3-1 shows the valid transitions between the modes of a Traffic Channel
30 Substate and the over-the-air Upper Layer Signaling Messages that trigger transitions
31 between these modes.
2-327
3GPP2 C.S0005-A v6.0
Extended Release Message,

Extended Release Mini Message, or
Universal Handoff Direction Message.
Active
Control Hold Mode
Mode
Resource Allocation (Mini) Message,

Extended Supplemental Channel Assignment Message,
Forward/Reverse Supplemental Channel Assignment Mini Message, or
Universal Handoff Direction Message.
Note:The mode transition occurs

when the fields are set appropriately
2 Figure 2.6.4.3-1. Mobile Station Modes
4 Upon entering the Traffic Channel Substate, the mobile station shall perform the following:
5 • If SERV_NEGs equals enabled, the call is mobile station originated, and
6 GRANTED_MODEs is equal to ‘00’ or ‘01’, the mobile station should initiate service
7 negotiation to request a service configuration in accordance with the requirements
8 for the active service subfunction (see 2.6.4.1.2.2).
9 While in the Traffic Channel Substate, the mobile station shall perform the following:
11 2.6.4.1.8. If a loss of the Forward Traffic Channel is declared, the lLayer 3 shall
12 terminate all Call Control instances, and shall enter the System Determination
13 Substate of the Mobile Station Initialization State with a system lost indication (see
14 2.6.1.1).
15 • The mobile station may send a Pilot Strength Measurement Mini Message to report
16 pilot strength order change information, periodic pilot strength information, or
17 threshold based pilot strength information, as specified in the Mobile Assisted Burst
18 Operation Parameters Message (see 2.6.6.2.5.2).
20 • The mobile station shall perform Forward Traffic Channel power control as specified
21 in 2.6.4.1.1.
2-328
3GPP2 C.S0005-A v6.0
1 • The mobile station shall perform handoff processing as specified in 2.6.6.
3 accordance with requirements for the active service subfunction (see 2.6.4.1.2.2).

5 2.6.5.5.4.2.
6 • If the mobile station is directed to send a Data Burst Message, the mobile station
7 shall send a Data Burst Message. If PILOT_GATING_USE_RATE is set to ‘1’, the
8 mobile station may request to transition to the Active Mode
9 (PILOT_GATING_USE_RATE set to ‘0’) prior to sending the Data Burst Message.
10 • If the mobile station has user data to send and PILOT_GATING_USE_RATE is equal
11 to ‘1’, then the mobile station may send a Resource Request Message, Resource
12 Request Mini Message, Supplemental Channel Request Message, or Supplemental
13 Channel Request Mini Message to request for continuous reverse pilot transmission
14 and user traffic transmission. The mobile station shall not send a Resource Request
15 Message or a Resource Request Mini Message if RETRY_DELAYs[010] is not equal to
16 0; the mobile station shall not send a Supplemental Channel Request Message or a
17 Supplemental Channel Request Mini Message if RETRY_DELAYs[011] is not equal to
18 0.
19 • If the mobile station is directed by the user to request a new service configuration,
20 the mobile station shall initiate service negotiation or service option negotiation in
21 accordance with the requirements for the active service subfunction (see
22 2.6.4.1.2.2).
23 • The mobile station may send a Service Option Control Message or Service Option
24 Control Order to invoke a service option specific function in accordance with the
25 requirements for the active service subfunction (see 2.6.4.1.2.2).
26 • If the mobile station is directed by the user to request a private long code transition
27 and has the long code mask (see 2.3.12.3), the mobile station shall send a Long
28 Code Transition Request Order (ORDQ = ‘00000001’) in assured mode.
29 • If the mobile station is directed by the user to request a public long code transition,
30 the mobile station shall send a Long Code Transition Request Order (ORDQ =
31 ‘00000000’) in assured mode.
32 • If the mobile station is directed by the user to operate in analog mode, allowing
33 operation in either wide or narrow analog mode, the mobile station shall send the
34 Request Analog Service Order in assured mode.
35 • If the mobile station is directed by the user to operate in wide analog mode, the
36 mobile station shall send the Request Wide Analog Service Order in assured mode.
37 • If the mobile station is directed by the user to operate in narrow analog mode, the
38 mobile station shall send the Request Narrow Analog Service Order in assured mode.
39 • If the mobile station is directed by the user to originate a call, the mobile station
2-329
3GPP2 C.S0005-A v6.0
1 - If this is an emergency call origination, the mobile station shall perform the
2 following:
3 + If it can be indicated to the base station within an existing Call Control

4 instance, the mobile station shall send an indication to this Call Control
5 instance that the user has originated an emergency call.
6 + Otherwise, the mobile station shall perform the following:

7 ο The mobile station shall increment the stored value of TAGs to the next
8 unused integer value.
9 ο The mobile station shall add TAGs to the list TAG_OUTSTANDING_LIST.
10 ο The mobile station shall send an Enhanced Origination Message to the

11 base station, with the TAG field of the message set to TAGs.
12 ο Upon sending the Enhanced Origination Message and prior to receiving a

13 lLayer 3 response from the base station, if the mobile station is directed
14 by the user to cancel this call, the mobile station shall perform the
15 following:
16 ◊ The mobile station shall send a Call Cancel Message to the base
17 station, with the TAG field of the message set to the TAG value in the
18 Enhanced Origination Message sent to originate this call.
19 ◊ The mobile station shall remove the TAG field corresponding to this
20 call from the list TAG_OUTSTANDING_LIST.
21 - Otherwise, the mobile station shall perform the following:
22 + If this is a packet data call origination, the mobile station shall first
23 determine the following conditions:
24 ο If RETRY_DELAYs[001] is set to infinity, the mobile station shall not send
25 the Enhanced Origination Message to the base station.
26 ο If RETRY_DELAYs[001] is not 0 or infinity, the mobile station shall not
27 send the Enhanced Origination Message until after the system time stored
28 in RETRY_DELAYs[001].
29 + If the above conditions do not prohibit the mobile station from sending an
30 Enhanced Origination Message at this time, the mobile station shall perform
31 the following:
32 ο The mobile station shall increment the stored value of TAGs to the next
33 unused integer value.
34 ο The mobile station shall add TAGs to the list TAG_OUTSTANDING_LIST.
35 ο The mobile station shall set an enhanced origination timer to a value of

36 T42m seconds.
2-330
3GPP2 C.S0005-A v6.0
1 ο The mobile station shall send an Enhanced Origination Message to the

2 base station, with the TAG field of the message set to TAGs.
3 + Upon sending the Enhanced Origination Message and prior to receiving a

4 lLayer 3 response from the base station, if the mobile station is directed by
5 the user to cancel this call, the mobile station shall perform the following:
6 ο The mobile station shall send a Call Cancel Message to the base station,
7 with the TAG field of the message set to the TAG value in the Enhanced
8 Origination Message sent to originate this call.
9 ο The mobile station shall disable the enhanced origination timer and shall
10 remove the TAG field corresponding to this call from the list
12 + If the enhanced origination timer expires, mobile station shall remove the
13 TAG field corresponding to this call from TAG_OUTSTANDING_LIST.
14 • If the lLayer 3 receives a “call release request” from a Call Control instance, lLayer 3
16 - If there are no other active or pending calls, the lLayer 3 shall enter the Release
17 Substate with a mobile station release indication (see 2.6.4.4).
18 − Otherwise, the mobile station shall send a Service Request Message, Resource
19 Release Request Message, or a Resource Release Request Mini Message to the
20 base station requesting to release this service option connection. If the mobile
21 station sends a Resource Release Request Message or a Resource Release
22 Request Mini Message, it shall set the PURGE_SERVICE field to ‘0’.
23 • If the lLayer 3 receives a “call inactive indication” from a Call Control instance,
24 lLayer 3 shall perform the following:
25 − If there are no other active or pending calls, the lLayer 3 shall enter the Release
26 Substate with a service inactive indication (see 2.6.4.4).
27 − Otherwise, the mobile station shall send a Service Request Message, Resource
28 Release Request Message, or a Resource Release Request Mini Message. If the
29 mobile station sends a Resource Release Request Message or a Resource Release
30 Request Mini Message, it shall set the PURGE_SERVICE field to ‘1’.
31 • If the mobile station is directed by the user to power down, the layerLayer 3 shall
32 send a “release indication” to all Call Control instances, and shall enter the Release
33 Substate with a power-down indication (see 2.6.4.4).
34 • If Layer 3 receives a L2-Condition. Notification primitive from Layer 2 indicating an

35 acknowledgment failure, the layer 3 shall terminate all Call Control instances, and
36 the mobile station shall disable its transmitter and shall enter the System
37 Determination Substate of the Mobile Station Initialization State with a system lost
2-331
3GPP2 C.S0005-A v6.0
1 • The mobile station shall perform the following:
2 − The mobile station may send the Resource Request Message or Resource Request
3 Mini Message in accordance with requirements for the currently connected
4 service option whenever RETRY_DELAYs[RETRY_TYPE] is equal to 0, where,
5 RETRY_TYPE is equal to ‘010’.
6 − The mobile station shall not send the Resource Request Message or Resource
7 Request Mini Message whenever RETRY_DELAYs[RETRY_TYPE] is set to infinity,
8 where, RETRY_TYPE is equal to ‘010’.
9 − If RETRY_DELAYs[RETRY_TYPE] is not 0 or infinity, the mobile station shall not
10 send the Resource Request Message or Resource Request Mini Message until after
11 the system time stored in RETRY_DELAYs[RETRY_TYPE], where, RETRY_TYPE is
12 equal to ‘010’.
13 − The mobile station may send the Supplemental Channel Request Message or
14 Supplemental Channel Request Mini Message whenever
15 RETRY_DELAYs[RETRY_TYPE] is set to ‘0’, where, RETRY_TYPE is equal to ‘011’.
16 − The mobile station shall not send the Supplemental Channel Request Message or
17 Supplemental Channel Request Mini Message whenever
18 RETRY_DELAYs[RETRY_TYPE] is set to infinity, where, RETRY_TYPE is equal to
19 ‘011’.
20 − If RETRY_DELAYs[RETRY_TYPE] is not 0 or infinity, the mobile station shall not
21 send the Supplemental Channel Request Message or Supplemental Channel
22 Request Mini Message until after the system time stored in
23 RETRY_DELAYs[RETRY_TYPE], where, RETRY_TYPE is equal to ‘011’.
24 − At the system time stored in RETRY_DELAYs[RETRY_TYPE], the mobile station

25 shall reset RETRY_DELAYs[RETRY_TYPE] to ‘0’, where RETRY_TYPE is equal to
26 ‘001’, ‘010’ or ‘011’.
27 • The mobile station may send a Resource Release Request Message or a Resource
28 Release Request Mini Message to request for reverse pilot gating operation to be
29 performed or to request a service option connection to be disconnected.
30 • The mobile station may enter the Release Substate with a service inactive indication
31 (see 2.6.4.4) if the service corresponding to the packet data service option instance
32 is inactive at the mobile station.
33 • If layer 3Layer 3 receives a “substate timer expired indication” from a Call Control
34 instance, the layer 3Layer 3 shall perform the following:
35 - If there are no other active or pending calls, the layer 3Layer 3 shall terminate
36 this Call Control instance; and the mobile station shall disable its transmitter
37 and enter the System Determination Substate of the Mobile Station Initialization
38 State with a system lost indication (see 2.6.1.1).
39 - Otherwise, the mobile station shall send a Service Request Message, Resource
40 Release Request Message, or a Resource Release Request Mini Message.
2-332
3GPP2 C.S0005-A v6.0
1 • If there are no active or pending calls, the layer 3Layer 3 shall enter the Release
2 Substate with a mobile station release indication.
3 • If layer 3Layer 3 receives a ‘message rejected indication’ from a Call Control

4 instance, mobile station shall send a Mobile Station Reject Order (ORDQ set to the
5 applicable reason code as determined from Table 2.7.3-1) within T56m seconds as
6 follows:
7 - If P_REV_IN_USEs is equal to or greater than seven, the mobile station shall
8 include the CON_REF_INCL field with this message and shall perform the
9 following: if the corresponding Call Control instance is identified by NULL, the
10 mobile station shall either set the CON_REF_INCL field of the message to ‘0’ or
11 set the CON_REF_INCL field to ‘1’ and set the CON_REF field to the connection
12 reference of the service option connection corresponding to this Call Control
13 instance; otherwise, the mobile station shall set the CON_REF_INCL field of the
14 message to ‘1’ and the CON_REF field of the message to the connection reference
15 of the service option connection corresponding to this Call Control instance.
16 • If Layer 3 is requested by the upper layers to query base station identification

17 number, SID, and NID related information for one or more pilots, and
18 PILOT_INFO_REQ_SUPPORTEDs equals ‘1’, mobile station shall send a Base Station
19 Status Request Message with a “Pilot Information” record type to the base station.
20 • If the mobile station receives a message which is included in the following list and
21 every message field value is within its permissible range, the mobile station shall
22 process the message as described below and in accordance with the message’s
23 action time (see 2.6.4.1.5).
24 1. Alert With Information Message: If P_REV_IN_USEs is less than seven, the layer
25 3Layer 3 shall deliver this message to the Call Control instance; otherwise, the
26 layer 3Layer 3 shall deliver this message to the Call Control instance identified
27 by NULL.
28 2. Analog Handoff Direction Message: If the analog mode directed by the base
29 station is supported by the mobile station, the mobile station shall process the
30 message as specified in 2.6.6.2.9, and shall perform the following at the action
31 time of the message:
33 perform the following: if CON_REF_INCLr equals ‘0’, the layer 3Layer 3 shall
34 terminate all Call Control instances (if there are any) except the one
35 identified by NULL; otherwise, the layer 3Layer 3 shall terminate all Call
36 Control instances (if there are any) except the one identified by CON_REFr.
37 - The mobile station shall perform the following (see [6] for handoff to a wide
38 analog channel and [22] for handoff to an 800 MHz narrow analog channel):
39 + If this Call Control instance is in the Waiting for Order Substate, the
40 mobile station shall enter the Waiting for Order Task.
2-333
3GPP2 C.S0005-A v6.0
1 + If this Call Control instance is in the Waiting for Mobile Station Answer
2 Substate, the mobile station shall enter the Waiting for Answer Task.
3 + If this Call Control instance is in the Conversation Substate, the mobile

4 station shall enter the Conversation Task.
5 - If the mobile station is directed to an unsupported operation mode or band

6 class, the mobile station shall respond with a Mobile Station Reject Order with
7 ORDQ equal to ‘00000110’ (message requires a capability that is not
8 supported by the mobile station).
9 3. Audit Order
10 4. Authentication Challenge Message: The layer 3Layer 3 shall send a “reset waiting
11 for order substate timer indication” to all Call Control instances. The mobile
12 station shall process the message and shall respond as specified in 2.3.12.1.4
13 within T32m seconds, regardless of the value of AUTHs.
14 5. Base Station Challenge Confirmation Order: The layer 3Layer 3 shall send a
15 “reset waiting for order substate timer indication” to all Call Control instances.
16 The mobile station shall process the message and shall respond with an SSD
17 Update Confirmation Order or SSD Update Rejection Order as specified in
18 2.3.12.1.5 within T32m seconds.
19 6. Base Station Status Response Message: The Layer 3 shall deliver the information
20 contained in this message to the Upper Layer entity that requested for this
21 information.
22 6.7. Call Assignment Message: The mobile station shall process this message as
23 follows:
24 – If RESPONSE_INDr equals ‘1’ and TAGr matches any of the TAG values
25 contained in the list TAG_OUTSTANDING_LIST, the mobile station shall
27 + If ACCEPT_INDr equals ‘0’, the mobile station shall disable the enhanced
28 origination timer and shall remove the TAG value specified by TAGr from
29 the list TAG_OUTSTANDING_LIST.
30 + If ACCEPT_INDr equals ‘1’, the mobile station shall perform the

31 following:
32 ο If there already exists or currently pending instantiation a Call

33 Control instance identified by CON_REFr, the mobile station shall
34 send a Mobile Station Reject Order with ORDQ field set to ‘00010010’
35 (a call control instance is already present with the specified
36 identifier), with the CON_REF field of the order set to CON_REFr.
2-334
3GPP2 C.S0005-A v6.0
1 ο Otherwise, layer 3Layer 3 shall instantiate a Call Control instance (as

2 specified in 2.6.10) at the action time of the message. The mobile
3 station shall identify this Call Control instance by CON_REFr. If a
4 service option connection corresponding to this call has not been
5 established, the mobile station should wait for the base station to
6 initiate service negotiation to establish the service option connection.
7 ο The mobile station shall disable the enhanced origination timer and
8 shall remove the TAG value specified by TAGr from the list
10 – If RESPONSE_INDr equals ‘1’ and TAGr does not match any of the TAG
11 values contained in the list TAG_OUTSTANDING_LIST, the mobile station
12 shall send a Mobile Station Reject Order with ORDQ field set to ‘00010011’
13 (TAG received does not match TAG stored), with the TAG field of the order set
14 to TAGr, and the CON_REF field of the order set to CON_REFr.
15 – If RESPONSE_INDr equals ‘0’, the mobile station shall perform the following:
16 + If there already exists or currently pending instantiation a Call Control

17 instance identified by CON_REFr, the mobile station shall send a Mobile
18 Station Reject Order with ORDQ field set to ‘00010010’ (a call control
19 instance is already present with the specified identifier), with the
20 CON_REF field of the order set to CON_REFr.
21 + Otherwise, if the mobile station does not accept this call assignment, the
22 mobile station shall send a Mobile Station Reject Order with ORDQ field
23 set to ‘00010000’ (call assignment not accepted), with the CON_REF field
24 of the order set to CON_REFr.
25 + Otherwise, at the action time of the message, the mobile station shall
26 store the bypass indicator (BYPASS_ALERT_ANSWERs =
27 BYPASS_ALERT_ANSWERr) and the layer 3Layer 3 shall instantiate a
28 Call Control instance (as specified in 2.6.10). The mobile station shall
29 identify this Call Control instance by CON_REFr. If a service option
30 connection corresponding to this call has not been established, the
31 mobile station should wait for the base station to initiate service
32 negotiation to establish the service option connection.
33 7.8. Candidate Frequency Search Control Message: The mobile station shall process
34 the message as specified in 2.6.6.2.5.1.
35 8.9. Candidate Frequency Search Request Message: The mobile station shall process
37 9.10. Continuous DTMF Tone Order: Support of this order by the mobile station is
38 optional. If P_REV_IN_USEs is less than seven, the layer 3Layer 3 shall deliver
39 this message to the Call Control instance; otherwise, the layer 3Layer 3 shall
2-335
3GPP2 C.S0005-A v6.0
2 deliver this message to the Call Control instance identified by NULL; otherwise,
3 the layer 3Layer 3 shall deliver this message to the Call Control instance
4 identified by CON_REFr.
6 11.12. Extended Alert With Information Message: The mobile station shall perform
7 the following: If CON_REF_INCLr equals ‘0’, the layer 3Layer 3 shall deliver this
8 message to the Call Control instance identified by NULL; otherwise, the layer
9 3Layer 3 shall deliver this message to the Call Control instance identified by
10 CON_REFr.
11 12.13. Extended Flash With Information Message: The mobile station shall perform
12 the following: If CON_REF_INCLr equals ‘0’, the layer 3Layer 3 shall deliver this
15 CON_REFr.
16 13.14. Extended Handoff Direction Message: The layer 3Layer 3 shall send a “reset
17 waiting for order substate timer indication” to all Call Control instances. The
18 mobile station shall process the message as specified in 2.6.6.2.5.1.
19 14.15. Extended Neighbor List Update Message: The mobile station shall process the
20 message as specified in 2.6.6.2.5.1.
21 15.16. Extended Release Message: The mobile station shall process the message as
23 16.17. Extended Release Mini Message: The mobile station shall process the
25 17.18. Forward Supplemental Channel Assignment Mini Message: The mobile station
26 shall process the message as specified in 2.6.6.2.5.1.
27 18.19. Flash With Information Message: If P_REV_IN_USEs is less than seven, the
28 layer 3Layer 3 shall deliver this message to the Call Control instance; otherwise,
30 identified by NULL.
31 19.20. Extended Supplemental Channel Assignment Message: The mobile station

33 20.21. General Handoff Direction Message: The layer 3Layer 3 shall send a “reset
36 21.22. In-Traffic System Parameters Message: The mobile station shall process the
39 23.24. Lock Until Power-Cycled Order: The mobile station shall disable its
40 transmitter and record the reason for the Lock Until Power-Cycled Order in the
2-336
3GPP2 C.S0005-A v6.0
1 mobile station’s semi-permanent memory (LCKRSN_Ps-p equals the least-

2 significant four bits of ORDQr). The mobile station should notify the user of the
3 locked condition. The layer 3Layer 3 shall terminate all Call Control instances,
4 and shall enter the System Determination Substate of the Mobile Station
5 Initialization State with a lock indication (see 2.6.1.1), and shall not enter the
6 System Access State again until after the next mobile station power-up or until
7 it has received an Unlock Order. This requirement shall take precedence over
8 any other mobile station requirement specifying entry to the System Access
9 State.
10 24.25. Long Code Transition Request Order: The mobile station shall process the
12 25.26. Maintenance Order: If P_REV_IN_USEs is less than seven, the layer 3Layer 3
13 shall deliver this message to the Call Control instance; otherwise, the layer
14 3Layer 3 shall perform the following: if CON_REF_INCLr equals ‘0’, the layer
16 NULL; otherwise, the layer 3Layer 3 shall deliver this message to the Call
17 Control instance identified by CON_REFr.
18 26.27. Maintenance Required Order: The mobile station shall record the reason for
19 the Maintenance Required Order in the mobile station’s semi-permanent memory
20 (MAINTRSNs-p equals the least-significant four bits of ORDQr). The mobile
21 station shall remain in the unlocked condition. The mobile station should
22 notify the user of the maintenance required condition.
23 27.28. Message Encryption Mode Order: The mobile station shall process the
24 message as specified in 2.3.12.2.
25 28.29. Mobile Station Registered Message: The mobile station shall process the
27 29.30. Mobile Assisted Burst Operation Parameters Message: The mobile station
29 30.31. Neighbor List Update Message: The mobile station shall process the message
31 31.32. Outer Loop Report Request Order: The mobile station shall send the Outer
32 Loop Report Message in assured mode to the base station.
33 32.33. Parameter Update Order: The layer 3Layer 3 shall send a “reset waiting for
34 order substate timer indication” to all Call Control instances. The mobile
35 station shall increment COUNTs-p (see 2.3.12.1.3). The mobile station shall
36 send a Parameter Update Confirmation Order within T56m seconds. The mobile
37 station shall set the ORDQ field of the Parameter Update Confirmation Order to
38 the same value as the ORDQ field of the Parameter Update Order.
39 33.34. Periodic Pilot Measurement Request Order: The mobile station shall process
40 the order as specified in 2.6.6.2.5.1.
41 34.35. Pilot Measurement Request Order: The mobile station shall process the order
2-337
3GPP2 C.S0005-A v6.0
2 35.36. Power Control Message: The mobile station shall process the message as
3 specified in 2.6.4.1.1.3.
4 36.37. Power Control Parameters Message: The mobile station shall process the
6 37.38. Power Up Function Message: The mobile station shall process the message as
8 38.39. Power Up Function Completion Message: The mobile station shall process the
10 39.40. Release Order: The layer 3Layer 3 shall send a “release indication” to all Call
11 Control instances, and shall enter the Release Substate with a base station
12 release indication (see 2.6.4.4).
13 40.41. Resource Allocation Message: The mobile station shall process the message
14 as specified in 2.6.4.1.10.
15 41.42. Resource Allocation Mini Message: The mobile station shall process the
17 42.43. Retrieve Parameters Message: The mobile station shall send, within T56m
18 seconds, a Parameters Response Message.
19 43.44. Retry Order: The mobile station shall process the order as follows:
21 RETRY_DELAYs[RETRY_TYPE] to ‘0’, where RETRY_TYPE is equal to ‘001’,
22 ‘010’, or ‘011’.
24 following:
25 − If RETRY_DELAYr is equal to ‘00000000’, then the mobile station shall
26 set RETRY_DELAYs [RETRY_TYPEr] to 0.

29 + If the most significant bit of the RETRY_DELAYr is 0, set

32 + The mobile station shall set RETRY_DELAY_VALUEs to the seven

33 least significant bits of RETRY_DELAYr.
37 • If RETRY_TYPEr is equal to ‘010’ or ‘011’, the mobile station shall perform

38 the following:
2-338
3GPP2 C.S0005-A v6.0
1 – If RETRY_DELAYr[RETRY_TYPEr] is ‘00000000’, then the mobile station

2 shall set RETRY_DELAYs [RETRY_TYPEr] to ‘0’.
3 – If RETRY_DELAYr[RETRY_TYPEr] is ‘11111111’, then the mobile station

4 shall set RETRY_DELAYs[RETRY_TYPEr] to infinity.
5 – If RETRY_DELAYr[RETRY_TYPEr] is not equal to ‘00000000’ or

6 ‘11111111’, the mobile station shall store the next system time 80 ms
7 boundary + RETRY_DELAYr[RETRY_TYPEr] × 320 ms as
9 44.45. Reverse Supplemental Channel Assignment Mini Message: The mobile station
11 45.46. Security Mode Command Message: The mobile station shall process the
13 46.47. Send Burst DTMF Message: Support of this order by the mobile station is
14 optional. If P_REV_IN_USEs is less than seven, the layer 3Layer 3 shall deliver
15 this message to the Call Control instance; otherwise, the layer 3Layer 3 shall
19 identified by CON_REFr.
20 47.48. Service Connect Message: The mobile station shall process the message in
22 2.6.4.1.2.2).if the message is not rejected due to the following conditions:
23 - If the CC_INFO_INCL field is included in this message and is set to ‘1’, the
24 mobile station shall perform the following for each of the
25 NUM_CALLS_ASSIGN call assignments included in this message:
26 + If there already exists or currently pending instantiation a Call Control

28 Station Reject Order with ORDQ field set to ‘00010010’ (a call control
29 instance is already present with the specified identifier), with the
30 CON_REF field of the order set to CON_REFr.
31 + If RESPONSE_INDr equals ‘1’ and TAGr does not match any of the TAG
33 shall send a Mobile Station Reject Order with ORDQ field set to
34 ‘00010011’ (TAG received does not match TAG stored), with the TAG field
35 of the order set to TAGr, and the CON_REF field of the order set to
36 CON_REFr.
37 + If the mobile station does not accept this call assignment, the mobile
39 ‘00010000’ (call assignment not accepted), with the CON_REF field of the
40 order set to CON_REFr.
2-339
3GPP2 C.S0005-A v6.0
1 48.49. Service Option Control Message: The mobile station shall process the
2 message in accordance with the requirements for the active service subfunction
3 (see 2.6.4.1.2.2).
4 49.50. Service Option Control Order: The mobile station shall process the message
5 in accordance with the requirements for the active service subfunction (see
6 2.6.4.1.2.2).
7 50.51. Service Option Request Order: The mobile station shall process the message
9 2.6.4.1.2.2).
10 51.52. Service Option Response Order: The mobile station shall process the message
12 2.6.4.1.2.2).
13 52.53. Service Redirection Message: The mobile station shall process the message
14 as follows:
15 If RECORD_TYPEr is equal to ‘00000000’, the mobile station shall do the
16 following:
17 – The mobile station shall set RETURN_IF_FAILs = RETURN_IF_FAILr.
18 – If DELETE_TMSIr is equal to ‘1’, the mobile station shall set all the bits of
20 – The mobile station shall disable the full-TMSI timer.
21 – The layer 3Layer 3 shall send a “release indication” to all Call Control
22 instances, and shall enter the Release Substate with an NDSS off
24 If RECORD_TYPEr is not equal to ‘00000000’, REDIRECT_TYPEr is ‘1’, and the
25 mobile station supports the band class and operating mode specified in the
26 message, the mobile station shall do the following:
27 – The mobile station shall store the redirection record received in the
28 message as REDIRECT_RECs.
29 – The mobile station shall enable NDSS_ORIGs and shall record the dialed
30 digits (if any) corresponding to the last MS originated call.
35 – The layer 3Layer 3 shall send a “release indication” to all Call Control
36 instances, and shall enter the Release Substate with a redirection indication (see
37 2.6.4.4).Otherwise, the mobile station shall discard the message and send a
38 Mobile Station Reject Order (ORDQ set to the applicable reason code as
39 determined from Table 2.7.3-1) within T56m seconds.
2-340
3GPP2 C.S0005-A v6.0
1 53.54. Service Request Message: The mobile station shall process the message in
3 2.6.4.1.2.2).
4 54.55. Service Response Message: The mobile station shall process the message in
6 2.6.4.1.2.2).
7 55.56. Set Parameters Message: If the mobile station can set all of the parameters
8 specified by the PARAMETER_ID fields in the message, the mobile station shall
9 set them; otherwise, the mobile station shall send, within T56m seconds, a
10 Mobile Station Reject Order.
11 56.57. SSD Update Message: The layer 3Layer 3 shall send a “reset waiting for order
12 substate timer indication” to all Call Control instances. The mobile station shall
13 process the message and respond with a Base Station Challenge Order as
14 specified in 2.3.12.1.5 within T32m seconds.
15 57.58. Status Request Message: The mobile station shall send, within T56m
16 seconds, a Status Response Message. If the message does not specify any
18 station shall include the requested information records in the Status Response
19 Message. If the message specifies a band class (QUAL_INFO_TYPEr is equal to
20 ‘00000001’), the mobile station shall only include the requested information
21 records for the specified band class (BAND_CLASSr) in the Status Response
22 Message. If the message specifies a band class and an operating mode
23 (QUAL_INFO_TYPEr is equal to ‘00000010’), the mobile station shall only
24 include the requested information records for the specified band class
25 (BAND_CLASSr) and operating mode (OP_MODEr) in the Status Response
26 Message.
27 If the message specifies a band class or a band class and an operating mode
28 which is not supported by the mobile station, the mobile station shall send a
29 Mobile Station Reject Order with ORDQ set to ‘00000110’ (message requires a
30 capability that is not supported by the mobile station).
31 If the response to this message exceeds the allowable length, the mobile station
32 shall send a Mobile Station Reject Order with ORDQ set to ‘00001000’ (response
33 message would exceed the allowable length).
34 If the message specifies an information record which is not supported by the

35 mobile station for the specified band class and operating mode, the mobile
36 station shall send a Mobile Station Reject Order with ORDQ set to ‘00001001’
37 (information record is not supported for the specified band class and operating
38 mode).
39 58.59. Status Request Order: If CDMABANDs is equal to ‘00000’, the mobile station
40 shall send a Status Message within T56m seconds. The mobile station shall
41 respond with information corresponding to the current band class and
42 operating mode.
2-341
3GPP2 C.S0005-A v6.0
1 59.60. Supplemental Channel Assignment Message: The mobile station shall process
4 code as follows:
7 • The mobile station shall store the assigning TMSI zone number by setting
8 the ASSIGNING_TMSI_ZONE_LENs-p least significant octets of
11 TMSI_CODEr.
13 TMSI_EXP_TIMEs-p to TMSI_EXP_TIMEr. The mobile station shall disable
14 the full-TMSI timer. The mobile station shall then respond with a TMSI
15 Assignment Completion Message within T56m seconds.
16 61.62. Universal Handoff Direction Message: The layer 3Layer 3 shall send a “reset
19 62.63. User Zone Reject Message: The mobile station shall process this message as
21 63.64. User Zone Update Message: The mobile station shall process this message as
23 • If the mobile station receives a message that is not included in the above list, cannot
24 be processed, or requires a capability which is not supported, the mobile station
25 shall discard the message and send a Mobile Station Reject Order (ORDQ set to the
26 applicable reason code as determined from Table 2.7.3-1) within T56m seconds. If
27 the mobile station receives a Call Control message (see 2.6.10) which is directed to a
28 Call Control instance that does not exists, the mobile station shall send a Mobile
29 Station Reject Order with ORDQ field set to ‘00010001’ (no call control instance
30 present with the specified identifier) to the base station within T56m seconds.
31 • If the bits of TMSI_CODEs-p are not all equal to ‘1’, and if System Time (in 80 ms
37 2.6.4.4 Release Substate
38 In this substate, the mobile station confirms the disconnect of all calls and physical
39 channels.
2-342
3GPP2 C.S0005-A v6.0
1 Upon entering the Release Substate, the mobile station shall perform the following:
2 • The mobile station shall set the substate timer for T55m seconds.
3 • If the mobile station enters the Release Substate with a power-down indication, the
4 mobile station shall send a Release Order (ORDQ = ‘00000001’), and shall perform
5 power-down registration procedures (see 2.6.5.5.4.4). The layer 3Layer 3 shall
6 terminate all Call Control instances.
7 • If the mobile station enters the Release Substate with a mobile station release
8 indication, the mobile station shall send a Release Order (ORDQ = ‘00000000’), and
9 set RETURN_CAUSEs to ‘0000’. The mobile station may store the current service
10 configuration (that is, parameters conveyed by both the Service Configuration
11 information record and the Non-negotiable Service Configuration information
12 record); if the mobile station stores the current service configuration, then the
13 mobile station shall store the SYNC_IDs corresponding to the current service
14 configuration.
15 • If the mobile station enters the Release Substate with a service inactive indication,
16 the mobile station shall send a Release Order (ORDQ = ‘00000010’), and set
17 RETURN_CAUSEs to ‘0000’.
18 • If the mobile station enters the Release Substate with a base station release
19 indication, the mobile station shall send a Release Order (ORDQ = ‘00000000’). The
20 layer 3Layer 3 shall terminate all Call Control instances. The mobile station may
21 store the current service configuration (that is, parameters conveyed by both the
22 Service Configuration information record and the Non-negotiable Service
23 Configuration information record); if the mobile station stores the current service
24 configuration, then the mobile station shall store the SYNC_IDs corresponding to the
25 current service configuration. The mobile station shall disable its transmitter, set
26 RETURN_CAUSEs to ‘0000’, and shall enter the System Determination Substate of
27 the Mobile Station Initialization State with a release indication (see 2.6.1.1).
28 • If the mobile station entered the Release Substate with a base station extended
29 release indication, the mobile station shall perform the following:
30 − The mobile station may store the current service configuration (that is,
31 parameters conveyed by both the Service Configuration information record and
32 the Non-negotiable Service Configuration information record); if the mobile
33 station stores the current service configuration, then the mobile station shall
34 store the SYNC_IDs corresponding to the current service configuration.
35 – The mobile station shall send an Extended Release Response Message to the
36 base station.
37 – The layer 3Layer 3 shall terminate all Call Control instances.
38 – The mobile station shall disable its transmitter, set RETURN_CAUSEs to ‘0000’,
40 Initialization State with a release indication (see 2.6.1.1).
2-343
3GPP2 C.S0005-A v6.0
1 • If the mobile station entered the Release Substate with a base station extended
2 release with mini message indication, then the mobile station shall perform the
3 following:
4 The mobile station may store the current service configuration (that is,
5 parameters conveyed by both the Service Configuration information record and
6 the Non-negotiable Service Configuration information record); if the mobile
7 station stores the current service configuration, then the mobile station shall
8 store the SYNC_IDs.
9 – The mobile station shall send an Extended Release Response Mini Message to the
10 base station.
11 – The layer 3Layer 3 shall terminate all Call Control instances.
12 – The mobile station shall disable its transmitter, set RETURN_CAUSEs to ‘0000’,
14 Initialization State with a release indication (see 2.6.1.1).
15 • If the mobile station enters the Release Substate with a redirection indication, the
16 mobile station shall send a Release Order (ORDQ = ‘00000000’) and shall enter the
18 redirection indication (see 2.6.1.1). The layer 3Layer 3 shall terminate all Call
19 Control instances.
20 • If the mobile station enters the Release Substate with an NDSS off indication, the
21 mobile station shall send a Release Order (ORDQ = ‘00000000’), and shall enter the
22 System Determination Substate of the Mobile Station Initialization State with an NDSS
23 off indication (see 2.6.1.1). The layer 3Layer 3 shall terminate all Call Control
24 instances.
25 While in the Release Substate, the mobile station shall perform the following:
26 • If the substate timer expires, the layer 3Layer 3 shall terminate all Call Control
27 instances, and the mobile station shall disable its transmitter and shall enter the
31 2.6.4.1.8. If a loss of the Forward Traffic Channel is declared, the layer 3Layer 3
32 shall terminate all Call Control instances, and shall enter the System Determination
33 Substate of the Mobile Station Initialization State with a release indication (see
34 2.6.1.1).
36 • The mobile station shall perform Forward Traffic Channel power control as specified
37 in 2.6.4.1.1.
38 • The mobile station shall perform handoff processing as specified in 2.6.6.
2-344
3GPP2 C.S0005-A v6.0
1 • If the Fundamental Channel is present, the mobile station shall transmit null traffic,
2 except when transmitting signaling traffic, on the Reverse Fundamental Channel.
3 • The mobile station shall process Forward Traffic Channel signaling traffic and shall
4 discard other types of Forward Traffic Channel traffic.

6 2.6.5.5.4.2.
7 • If Layer 3 receives a L2-Condition.Notification primitive from Layer 2 indicating an

8 acknowledgment failure, the layer 3Layer 3 shall terminate all Call Control
9 instances, and the mobile station shall disable its transmitter and enter the System
10 Determination Substate of the Mobile Station Initialization State with a release
12 • If the layer 3Layer 3 receives an “enter traffic channel substate indication” from a
13 Call Control instance, the layer 3Layer 3 shall enter the Traffic Channel substate.
14 • If layer 3Layer 3 receives a ‘message rejected indication’ from a Call Control

15 instance, mobile station shall send a Mobile Station Reject Order (ORDQ set to the
16 applicable reason code as determined from Table 2.7.3-1) within T56m seconds as
17 follows:
19 include the CON_REF_INCL field with this message and shall perform the
20 following: if the corresponding Call Control instance is identified by NULL, the
23 reference of the service option connection corresponding to this Call Control
24 instance; otherwise, the mobile station shall set the CON_REF_INCL field of the
25 message to ‘1’ and the CON_REF field of the message to the connection reference
26 of the service option connection corresponding to this Call Control instance.
27 • If the mobile station receives a message which is included in the following list, and if
28 every message field value is within its permissible range, the mobile station shall
29 process the message as described below and in accordance with the message’s
30 action time (see 2.6.4.1.5):
31 1. Alert With Information Message: If P_REV_IN_USEs is less than seven, the layer
32 3Layer 3 shall deliver this message to the Call Control instance; otherwise, the
34 by NULL.
35 2. Candidate Frequency Search Control Message: The mobile station shall process
37 3. Candidate Frequency Search Request Message: The mobile station shall process
40 5. Extended Alert With Information Message: The mobile station shall perform the
2-345
3GPP2 C.S0005-A v6.0
1 following: If CON_REF_INCLr equals ‘0’, the layer 3Layer 3 shall deliver this
4 CON_REFr.
5 6. Extended Handoff Direction Message: The mobile station shall process the
7 7. Extended Neighbor List Update Message: The mobile station shall process the
9 8. Extended Supplemental Channel Assignment Message: The mobile station shall
10 process the message as specified in 2.6.6.2.5.1.
11 9. General Handoff Direction Message: The mobile station shall process the
13 10. In-Traffic System Parameters Message: The mobile station shall process the
16 12. Mobile Assisted Burst Operation Parameters Message: The mobile station shall
18 13. Lock Until Power-Cycled Order: The mobile station shall disable its transmitter
19 and record the reason for the Lock Until Power-Cycled Order in the mobile
20 station’s semi-permanent memory (LCKRSN_Ps-p equals the least-significant
21 four bits of ORDQr). The mobile station should notify the user of the locked
22 condition. The layer 3Layer 3 shall terminate all Call Control instances. The
23 layer 3Layer 3 shall enter the System Determination Substate of the Mobile
24 Station Initialization State with a lock indication (see 2.6.1.1), and shall not enter
25 the System Access State again until after the next mobile station power-up or
26 until it has received an Unlock Order. This requirement shall take precedence
27 over any other mobile station requirement specifying entry to the System Access
28 State.
31 (MAINTRSNs-p equals the least-significant four bits of ORDQr). The mobile
32 station shall remain in the unlocked condition. The mobile station should
33 notify the user of the maintenance required condition.
34 15. Mobile Station Registered Message: The mobile station shall process the
36 16.Mobile Assisted Burst Operation Parameters Message: The mobile station shall
38 17.16. Neighbor List Update Message: The mobile station shall process the message
40 18.17. Outer Loop Report Request Order: The mobile station shall send the Outer
2-346
3GPP2 C.S0005-A v6.0
1 Loop Report Message in assured mode to the base station.
2 19.18. Power Control Message: The mobile station shall process the message as
4 20.19. Power Control Parameters Message: The mobile station shall process the
6 21.20. Power Up Function Message: The mobile station shall process the message as
8 22.21. Power Up Function Completion Message: The mobile station shall process the
10 23.22. Release Order: The mobile station shall disable its transmitter. The layer
11 3Layer 3 shall terminate all Call Control instances. If the mobile station enters
12 the Release Substate with a power-down indication, the mobile station may
13 power down; otherwise, the mobile station shall enter the System Determination
14 Substate of the Mobile Station Initialization State with a release indication (see
15 2.6.1.1).
16 24.23. Retrieve Parameters Message: The mobile station shall send, within T56m
17 seconds, a Parameters Response Message.
18 25.24. Retry Order: The mobile station shall process the order as follows:
20 RETRY_DELAYs[RETRY_TYPE] to ‘0’, where RETRY_TYPE is equal to ‘001’,
21 ‘010’, or ‘011’.
23 following:
24 − If RETRY_DELAYr is equal to ‘00000000’, then the mobile station shall
25 set RETRY_DELAYs [RETRY_TYPEr] to 0.

28 + If the most significant bit of the RETRY_DELAYr is 0, set

31 + The mobile station shall set RETRY_DELAY_VALUEs to the seven

32 least significant bits of RETRY_DELAYr.
36 26.25. Service Option Control Message: The mobile station shall process the
38 (see 2.6.4.1.2.2).
39 27.26. Service Option Control Order: The mobile station shall process the message
2-347
3GPP2 C.S0005-A v6.0
2 2.6.4.1.2.2).
3 28.27. Service Redirection Message: The mobile station shall disable its transmitter.
4 If the mobile station enters the Release Substate with a power-down indication,
5 the mobile station may power down (if powering down, the layer 3Layer 3 shall
6 terminate all Call Control instances); otherwise, the mobile station shall process
7 the message as follows:
8 • If RECORD_TYPEr is ‘00000000’, the mobile station shall do the following:
13 – The layer 3Layer 3 shall terminate all Call Control instances, and shall
14 enter the System Determination Substate of the Mobile Station Initialization
15 State with an NDSS off indication (see 2.6.1.1).
16 • If RECORD_TYPE is not equal to ‘00000000’, REDIRECT_TYPEr is ‘1’, and
17 the mobile station supports the band class and operating mode specified in
18 the message, the mobile station shall do the following:
19 – The mobile station shall store the redirection record received in the
20 message as REDIRECT_RECs.
25 – The layer 3Layer 3 shall terminate all Call Control instances, and shall
26 enter the System Determination Substate of the Mobile Station Initialization
27 State with a redirection indication (see 2.6.1.1).
28 • Otherwise, the mobile station shall discard the message and send a Mobile
29 Station Reject Order (ORDQ set to the applicable reason code as determined
30 from Table 2.7.3-1) within T56m seconds.
31 29.28. Status Request Message: The mobile station shall send, within T56m
32 seconds, a Status Response Message. If the message does not specify any
34 station shall include the requested information records in the Status Response
35 Message. If the message specifies a band class (QUAL_INFO_TYPEr is equal to
36 ‘00000001’), the mobile station shall only include the requested information
37 records for the specified band class (BAND_CLASSr) in the Status Response
38 Message. If the message specifies a band class and an operating mode
39 (QUAL_INFO_TYPEr is equal to ‘00000010’), the mobile station shall only
40 include the requested information records for the specified band class
2-348
3GPP2 C.S0005-A v6.0
1 (BAND_CLASSr) and operating mode (OP_MODEr) in the Status Response

2 Message. If the message specifies a band class or a band class and an
3 operating mode which are not supported by the mobile station, the mobile
4 station shall send a Mobile Station Reject Order with ORDQ set to ‘00000110’
5 (message requires a capability that is not supported by the mobile station). If
6 the response to this message exceeds the allowable length, the mobile station
7 shall send a Mobile Station Reject Order with ORDQ set to ‘00001000’ (response
8 message would exceed the allowable length). If the message specifies an
9 information record which is not supported by the mobile station for the
10 specified band class and operating mode, the mobile station shall send a Mobile
11 Station Reject Order with ORDQ set to ‘00001001’ (information record is not
12 supported for the specified band class and operating mode).
13 30.29. Status Request Order: If CDMABANDs is equal to ‘00000’, the mobile station
14 shall send, a Status Message within T56m seconds. The mobile station shall
15 respond with information corresponding to the current band class and
16 operating mode.
17 31.30. Supplemental Channel Assignment Message: The mobile station shall process
20 code as follows:
27 TMSI_CODEr.
29 TMSI_EXP_TIMEs-p to TMSI_EXP_TIMEr. The mobile station shall disable the
30 full-TMSI timer. The mobile station shall then respond with a TMSI Assignment
31 Completion Message within T56m seconds.
32 33.32. Universal Handoff Direction Message: The mobile station shall process the
34 34.33. User Zone Reject Message: The mobile station shall process this message as
36 35.34. User Zone Update Message: The mobile station shall process this message as
2-349
3GPP2 C.S0005-A v6.0
1 • If the mobile station receives a message that is not included in the above list or
2 cannot be processed, the mobile station shall discard the message and send a Mobile
3 Station Reject Order (ORDQ set to the applicable reason code as determined from
4 Table 2.7.3-1) within T56m seconds. If the mobile station receives a Call Control
5 message (see 2.6.10) which is directed to a Call Control instance that does not
6 exists, the mobile station shall send a Mobile Station Reject Order with ORDQ field
7 set to ‘00010001’ (no call control instance present with the specified identifier) to the
8 base station within T56m seconds.
9 • If the bits of TMSI_CODEs-p are not all equal to ‘1’, and if System Time (in 80 ms
15 2.6.5 Registration
16 2.6.5.1 Forms of Registration
17 Registration is the process by which the mobile station notifies the base station of its
18 location, status, identification, slot cycle, and other characteristics. The mobile station
19 informs the base station of its location and status so that the base station can efficiently
20 page the mobile station when establishing a mobile station terminated call. For operation
21 in the slotted mode, the mobile station supplies the SLOT_CYCLE_INDEX parameter so that
22 the base station can determine which slots the mobile station is monitoring. The mobile
23 station supplies the station class mark and the protocol revision number so that the base
24 station knows the capabilities of the mobile station.
25 The CDMA system supports ten eleven different forms of registration:
26 1. Power-up registration. The mobile station registers when it powers on, switches
27 from using a different frequency block, switches from using a different band class,
28 switches from using an alternative operating mode, or switches from using the
29 analog system.
30 2. Power-down registration. The mobile station registers when it powers off if

31 previously registered in the current serving system.
32 3. Timer-based registration. The mobile station registers when a timer expires.
33 4. Distance-based registration. The mobile station registers when the distance

34 between the current base station and the base station in which it last registered
35 exceeds a threshold.
36 5. Zone-based registration. The mobile station registers when it enters a new zone.
37 6. Parameter-change registration. The mobile station registers when certain of its

38 stored parameters change or when it enters a new system.
39 7. Ordered registration. The mobile station registers when the base station requests it.
2-350
3GPP2 C.S0005-A v6.0
1 8. Implicit registration. When a mobile station successfully sends an Origination

2 Message or Page Response Message, the base station can infer the mobile station’s
3 location. This is considered an implicit registration.
4 9. Traffic Channel registration. Whenever the base station has registration information
5 for a mobile station that has been assigned to a Traffic Channel, the base station
6 can notify the mobile station that it is registered.
7 10. User Zone Registration. The mobile station registers when it selects an active User
8 Zone (see 2.6.9.1.2).
9 11. Encryption re-sync required registration. The mobile station registers when
10 extended encryption is turned on and the mobile station determines that it can not
11 decrypt any messages from the base station (see 2.3.12.4.1.3).
12 The first five forms of registration, User Zone Registration, and Encryption re-sync required
13 registration, as a group, are called autonomous registration and are enabled by roaming
14 status (see 2.6.5.3). Parameter-change registration is independent of roaming status.
15 Ordered registration is initiated by the base station through an Order Message. Implicit
16 registration does not involve the exchange of any registration messages between the base
17 station and the mobile station. The base station can obtain registration information by
18 sending the Status Request Message to the mobile station on either the f-csch or the f-dsch.
19 The base station can obtain limited registration information by sending the Status Request
20 Order to the mobile station on the f-dsch. The mobile station can be notified that it is
21 registered through the Mobile Station Registered Message.
22 Any of the various forms of autonomous registration and parameter-change registration can
23 be enabled or disabled. The forms of registration that are enabled and the corresponding
24 registration parameters are communicated in the System Parameters Message on the Paging
25 Channel, or the ANSI-41 System Parameters Message on the Primary Broadcast Control
26 Channel.
27 In addition, the mobile station may enable or disable autonomous registration for each type
28 of roaming described in 2.6.5.3.
29 2.6.5.1.1 Power-Up Registration
30 Power-up registration is performed when the mobile station is turned on. To prevent
31 multiple registrations when power is quickly turned on and off, the mobile station delays
32 T57m seconds before registering, after entering the Mobile Station Idle State.
33 The mobile station shall maintain a power-up/initialization timer. While the power-
34 up/initialization timer is active, the mobile station shall not make registration access
35 attempts.
36 Power-up registration is also performed when the mobile station changes to a different
37 operating mode, band class, serving system, or frequency block (see 2.6.5.5.1.1)
2-351
3GPP2 C.S0005-A v6.0
1 2.6.5.1.2 Power-Down Registration
2 Power-down registration is performed when the user directs the mobile station to power off.
3 If power-down registration is performed, the mobile station does not power off until after
4 completing the registration attempt.
5 The mobile station does not perform power-down registration if it has not previously
6 registered in the system that corresponds to the current SIDs and NIDs (see 2.6.5.5.2.4).
7 2.6.5.1.3 Timer-Based Registration
8 Timer-based registration causes the mobile station to register at regular intervals. Its use
9 also allows the system to automatically deregister mobile stations that did not perform a
10 successful power-down registration. Timer-based registration uses a Paging Channel or a
11 Forward Common Control Channel slot counter (equivalent to a timer with time increments
12 of 80 ms). Timer-based registration is performed when the counter reaches a maximum
13 value (REG_COUNT_MAXs) that is controlled by the base station via the REG_PRD field of
14 the System Parameters Message or ANSI-41 System Parameters Message. The base station
15 disables timer-based registration by setting REG_PRD to zero.
16 The mobile station shall maintain a timer-based registration counter (REG_COUNTs). The
17 mobile station shall compute and store the timer expiration count (REG_COUNT_MAXs) as
18 REG_COUNT_MAXs = 2REG_PRD/4 .
19 The mobile station shall maintain an indicator of timer-based registration timer enable
20 status (COUNTER_ENABLEDs).
21 The counter is reset when the mobile station powers on and when the mobile station
22 switches from different band classes, different serving systems, different frequency blocks,
23 and alternate operating modes. The counter is also reset after each successful registration.
24 Whenever the mobile station changes COUNTER_ENABLEDs from NO to YES, it shall set
25 REG_COUNTs to a pseudorandom value between 0 and REG_COUNT_MAXs - 1, using the
26 pseudorandom number generator specified in 2.6.7.2.
27 If the mobile station is operating in the non-slotted mode, it shall increment the timer-
28 based registration counter once per 80 ms whenever COUNTER_ENABLEDs equals YES. If
29 the mobile station is operating in slotted mode, it may increment the timer-based
30 registration counter when it begins to monitor the Paging Channel (see 2.6.2.1.1.3) or the
31 Forward Common Control Channel. A mobile station operating in the slotted mode shall
32 increment the counter by the same amount that the counter would have been incremented
33 if the mobile station had been operating in the non-slotted mode.11
11 For example, if the mobile station uses a 2.56 second slot cycle, then it may increment the counter
by 32 every time it becomes active.
2-352
3GPP2 C.S0005-A v6.0
1 2.6.5.1.4 Distance-Based Registration

2 Distance-based registration causes a mobile station to register when the distance between
3 the current base station and the base station in which it last registered exceeds a
4 threshold. The mobile station determines that it has moved a certain distance by
5 computing a distance measure based on the difference in latitude and longitude between
6 the current base station and the base station where the mobile station last registered. If
7 this distance measure exceeds the threshold value, the mobile station registers.
8 The mobile station stores the base station latitude (BASE_LAT_REGs-p), the base station
9 longitude (BASE_LONG_REGs-p) and the registration distance (REG_DIST_REGs-p), of the
10 base station to which the first access probe (for a Registration Message, Origination
11 Message, or Page Response Message sent on the r-csch) was transmitted after entering the
12 System Access State. The mobile station shall compute the current base station’s distance
13 from the last registration point (DISTANCE) as:
( ∆lat ) 2 + ( ∆long ) 2
14 DISTANCE =  ,
16
15 where
16 ∆lat = BASE_LATs - BASE_LAT_REGs-p
17 and
18 ∆long = (BASE_LONGs - BASE_LONG_REGs-p) × cos (π/180 × BASE_LAT_REGs-p/14400).
19 The mobile station shall compute DISTANCE with an error of no more than ±5% of its true
20 value when |BASE_LAT_REGs-p/14400| is less than 60 and with an error of no more than
21 ±7% of its true value when |BASE_LAT_REGs-p/14400| is between 60 and 70.12
22 2.6.5.1.5 Zone-Based Registration

23 Registration zones are groups of base stations within a given system and network. A base
24 station’s zone assignment is identified by the REG_ZONE field of the System Parameters
25 Message or ANSI-41 System Parameters Message.
26 Zone-based registration causes a mobile station to register whenever it moves into
27 determines it is in a new zone (see 2.6.5.5.2.1), not on its internally stored list of visited
28 registration zones. A zone is added to the list whenever a registration (including implicit
29 registration) occurs, and is deleted upon expiration of a timer. After a system access,
30 timers are enabled for every zone except one that was successfully registered by the access.
31 A mobile station can be registered in more than one zone. Zones are uniquely identified by
32 a zone number (REG_ZONE) plus the SID and NID of the zone.
12 BASE_LAT and BASE_LONG are given in units of 1/4 seconds. BASE_LAT/14400 and
BASE_LONG/14400 are in units of degrees.
2-353
3GPP2 C.S0005-A v6.0
1 The mobile station shall store a list of the zones in which the mobile station has registered
2 (ZONE_LISTs). Each entry in ZONE_LISTs shall include the zone number (REG_ZONE) and
3 the (SID, NID) pair for the zone. The mobile station shall be capable of storing at least N9m
4 entries in ZONE_LISTs. A base station shall be considered to be in ZONE_LISTs only if the
5 base station’s REG_ZONE, SID and NID are found in an entry in ZONE_LISTs. The mobile
6 station provides storage for one entry of ZONE_LISTs in semi-permanent memory,
7 ZONE_LISTs-p (see 2.3.4).
8 The mobile station shall maintain a zone list entry timer for each entry in ZONE_LISTs.
9 When an entry in ZONE_LISTs is removed from the list, the corresponding zone list entry
10 timer shall be disabled. The timer duration shall be as determined from the stored value of
11 ZONE_TIMERs using Table 3.7.2.3.2.1-1. The mobile station shall provide a means to
12 examine each timer’s value while the timer is active, so that the age of list entries can be
13 compared.
14 If the mobile station supports Band Class 1, Band Class 2, Band Class 4, Band Class 5, or
15 Band Class 7, or Band Class 10, the mobile station shall maintain an identifier of the
16 frequency block for each entry in ZONE_LISTs (see 2.1.1.1 of [2]). When the mobile station
17 adds a zone to ZONE_LISTs, the mobile station shall include the identifier for the frequency
18 block.13
19 If the mobile station supports multiple band classes, the mobile station shall maintain an
20 identifier of the band class for each entry in ZONE_LISTs (see 2.1.1.1 of [2]). When the
21 mobile station adds a zone to ZONE_LISTs, the mobile station shall include the identifier for
22 the band class.
23 The base station controls the maximum number of zones in which a mobile station may be
24 considered registered, by means of the TOTAL_ZONES field of the System Parameters
25 Message or ANSI-41 System Parameters Message. When an entry is added to the zone list,
26 or if TOTAL_ZONES is decreased, the mobile station removes entries from the zone list if
27 there are more entries than allowed by the setting of TOTAL_ZONES.
28 Whenever ZONE_LISTs contains more than TOTAL_ZONESs entries, the mobile station shall
29 delete the excess entries according to the following rules:
30 • If TOTAL_ZONESs is equal to zero, the mobile station shall delete all entries.
31 • If TOTAL_ZONESs is not equal to zero, the mobile station shall delete those entries
32 having active zone list entry timers, starting with the oldest entry, as determined by
33 the timer values, and continuing in order of decreasing age until no more than
34 TOTAL_ZONESs entries remain.
35 The mobile station shall store a list of the systems/networks in which the mobile station
36 has registered (SID_NID_LISTs). Each entry in SID_NID_LISTs shall include the (SID, NID)
37 pair for the system/network. The mobile station shall be capable of storing N10m entries in
13 The mobile station need not maintain a separate identifier for Band Class 0, as the least
significant bit of the SID identifies the serving system.
2-354
3GPP2 C.S0005-A v6.0
1 SID_NID_LISTs. A base station shall be considered to be in the SID_NID_LISTs only if the

2 base station’s SID and NID are found in an entry in SID_NID_LISTs. The mobile station
3 shall provide storage for one entry of SID_NID_LISTs in semi-permanent memory
4 (SID_NID_LISTs-p).
5 If the mobile station supports Band Class 1, Band Class 2, Band Class 4, Band Class 5, or
6 Band Class 7, or Band Class 10, the mobile station shall maintain an identifier of the
7 frequency block for each entry in SID_NID_LISTs (see 2.1.1.1 of [2]). When the mobile
8 station adds an entry to SID_NID_LISTs, the mobile station shall include the identifier for
9 the frequency block.
10 If the mobile station supports multiple band classes, the mobile station shall maintain an
11 identifier of the band class for each entry in SID_NID_LISTs (see 2.1.1.1 of [2]). When the
12 mobile station adds an entry to SID_NID_LISTs, the mobile station shall include the
13 identifier for the band class.
14 The mobile station shall maintain a SID/NID list entry timer for each entry in
15 SID_NID_LISTs. When an entry in SID_NID_LISTs is removed from the list, the
16 corresponding SID/NID list entry timer shall be disabled. The timer duration shall be as
17 determined from the stored value of ZONE_TIMERs using Table 3.7.2.3.2.1-1. The mobile
18 station shall provide a means to examine each timer’s value while the timer is active, so
19 that the age of list entries can be compared.
20 Whenever SID_NID_LISTs contains more than N10m entries, the mobile station shall delete
21 the excess entries according to the following rule:
22 • The mobile station shall delete those entries having active SID/NID list entry timers,
23 starting with the oldest entry, as determined by the timer values, and continuing in
24 order of decreasing age.
25 Whenever MULT_SIDSs is equal to ‘0’ and SID_NID_LIST contains entries with different
26 SIDs, the mobile station shall delete the excess entries according to the following rules:
27 • If the SID/NID entry timer for any entry is disabled, the mobile station shall delete
28 all entries not having the same SID as the entry whose timer is disabled;
29 • Otherwise, the mobile station shall delete all entries not having the same SID as the
30 newest entry in SID_NID_LIST, as determined by the timer values.
31 Whenever MULT_NIDSs is equal to ‘0’, and SID_NID_LIST contains more than one entry for
32 any SID, the mobile station shall delete the excess entries for each SID according to the
33 following rules:
34 • If the SID/NID entry timer for any entry is disabled, the mobile station shall delete
35 all entries for that SID except the entry whose timer is disabled;
36 • For all other SIDs, the mobile station shall delete all entries for each SID except the
37 newest entry, as determined by the timer values.
38 2.6.5.1.6 Parameter-Change Registration
39 Parameter-change registration is performed when a mobile station modifies any of the

40 following stored parameters:
2-355
3GPP2 C.S0005-A v6.0
1 • The preferred slot cycle index (SLOT_CYCLE_INDEXp)
2 • The station class mark (SCMp)
3 • The call termination enabled indicators (MOB_TERM_HOMEp,

4 MOB_TERM_FOR_SIDp, and MOB_TERM_FOR_NIDp)
5 Parameter-change registration is also performed when any of the following capabilities

6 supported by the mobile station changes:
7 • The band classes
8 • The power classes
9 • The radio configurations
10 • The operating modes
11 • Transmit diversity (OTD or STS)
12 • Quick Paging Channel
13 • Spreading Rate 3 common channels support
14 • Encryption capability
15 Parameter-change registration is performed whenever there is no entry in the mobile

16 station’s SID_NID_LISTs that matches the base station’s SID and NID.
17 Parameter-change registration is independent of the roaming status of the mobile station.14
18 Whenever a parameter changes, the mobile station shall delete all entries from
19 SID_NID_LISTs.
20 2.6.5.1.7 Ordered Registration

21 The base station can command the mobile station to register by sending a Registration
22 Request Order. Ordered registration is performed in the Mobile Station Order and Message
23 Processing Operation (2.6.2.4). Requirements are specified in 2.6.5.5.2.3.
24 2.6.5.1.8 Implicit Registration

25 Whenever an Origination Message or Page Response Message is sent, the base station can
26 infer the location of the mobile station. This is considered an implicit registration.
27 Requirements are specified in 2.6.5.5.3.
28 2.6.5.1.9 Traffic Channel Registration
29 While a mobile station is assigned a Traffic Channel, the mobile station is notified that it is
30 registered through the Mobile Station Registered Message. Requirements are specified in
31 2.6.5.5.4.3.
14 The indicator REG_ENABLED does not govern parameter-change registration.
2-356
3GPP2 C.S0005-A v6.0
1 2.6.5.1.10 User Zone Registration
2 User Zone registration is performed when the mobile station selects an active User Zone
3 (see 2.6.9.2.1).
4 2.6.5.1.11 Encryption Re-sync Required Registration
5 Encryption re-sync required registration is performed when the mobile station determines
6 that it can not decrypt any message from the base station (see 2.3.12.4.1.3). This type of
7 registration is needed for the mobile station to recover from any encryption out-of-sync
8 scenario.
9 2.6.5.2 Systems and Networks
10 A base station is a member of a cellular or PCS system and a network. A network is a

11 subset of a system.
12 Systems are labeled with an identification called the system identification or SID; networks
13 within a system are given a network identification or NID. A network is uniquely identified
14 by the pair (SID, NID). The SID number 0 is a reserved value. The NID number 0 is a
15 reserved value indicating all base stations that are not included in a specific network. The
16 NID number 65535 (216-1) is a reserved value the mobile station may use for roaming
17 status determination (see 2.6.5.3) to indicate that the mobile station considers the entire
18 SID (regardless of NID) as home (non-roaming).
19 Figure 2.6.5.2-1 shows an example of systems and networks. SID i contains three
20 networks labeled t, u, and v. A base station in system i that is not in one of these three
21 networks is in NID 0.
22
2-357
3GPP2 C.S0005-A v6.0
SID j SID k
NID t NID u
NID 0 NID v
SID i
SID 1
2 Figure 2.6.5.2-1. Systems and Networks Example
3 2.6.5.3 Roaming
4 The mobile station has a list of one or more home (non-roaming) (SID, NID) pairs. A mobile
5 station is roaming if the stored (SIDs, NIDs) pair (received in the System Parameters
6 Message on the Paging Channel, or the ANSI-41 System Parameters Message on the Primary
7 Broadcast Control Channel) does not match one of the mobile station’s non-roaming (SID,
8 NID) pairs. Two types of roaming are defined: A mobile station is a foreign NID roamer if
9 the mobile station is roaming and there is some (SID, NID) pair in the mobile station’s (SID,
10 NID) list for which SID is equal to SIDs. A mobile station is a foreign SID roamer if there is
11 no (SID, NID) pair in the mobile station’s (SID, NID) list for which SID is equal to SIDs15.
15 For example, suppose a mobile station has the following SID, NID list: (2, 3), (2, 0), (3, 1). If the
base station (SID, NID) pair is (2, 3), then the mobile station is not roaming because the (SID, NID)
(footnote continued on next page)
2-358
3GPP2 C.S0005-A v6.0
1 The mobile station may use the special NID value 65535 to indicate that the mobile station
2 considers all NIDs within a SID to be non-roaming (i.e., that the mobile station is not
3 roaming when operating with any base station in that system).
4 The mobile station shall store three 1-bit parameters in its permanent memory (see 2.3.8).
5 These parameters are MOB_TERM_HOMEp, MOB_TERM_FOR_SIDp, and MOB_TERM-
6 _FOR_NIDp. The mobile station shall set MOB_TERM_HOMEp to ‘1’ if the mobile station is
7 configured to receive mobile station terminated calls when using a home (SID, NID) pair;
8 otherwise, the mobile station shall set MOB_TERM_HOMEp to ‘0’. The mobile station shall
9 set MOB_TERM_FOR_SIDp to ‘1’ if the mobile station is configured to receive mobile station
10 terminated calls when it is a foreign SID roamer; otherwise MOB_TERM_FOR_SIDp shall be
11 set to ‘0’. The mobile station shall set MOB_TERM_FOR_NIDp to ‘1’ if the mobile station is
12 configured to receive mobile station terminated calls when it is a foreign NID roamer;
13 otherwise the mobile station shall set MOB_TERM_FOR_NIDp to ‘0’.
14 The mobile station determines the registration status using these parameters and the
15 HOME_REG, FOR_NID_REG, and FOR_SID_REG fields of the System Parameters Message
16 or ANSI-41 System Parameters Message.
17 The mobile station shall store a mobile station call termination enabled indicator,
18 MOB_TERMs. The mobile station shall set MOB_TERMs to YES if any of the following
19 conditions is met:
20 • The mobile station is not roaming, and MOB_TERM_HOMEp is equal to ‘1’; or
21 • The mobile station is a foreign NID roamer and MOB_TERM_FOR_NIDp is equal to

22 ‘1’; or
23 • The mobile station is a foreign SID roamer and MOB_TERM_FOR_SIDp is equal to
24 ‘1’; otherwise the mobile station shall set MOB_TERMs to NO.
25 The mobile station shall store a registration status indicator, REG_ENABLEDs. The mobile
26 station shall set the indicator REG_ENABLEDs to YES if any of the following conditions is
27 met for the mobile station:
28 • The mobile station is not roaming, and both HOME_REGs and MOB_TERM_HOMEp
29 are equal to ‘1’; or
30 • The mobile station is a foreign NID roamer and both FOR_NID_REGs and
31 MOB_TERM_FOR_NIDp are equal to ‘1’; or
32 • The mobile station is a foreign SID roamer and both FOR_SID_REGs and
33 MOB_TERM_FOR_SIDp are equal to ‘1’; otherwise the mobile station shall set
34 REG_ENABLEDs to NO.
pair is in the list. If the base station (SID, NID) pair is (2, 7), then the mobile station is a foreign NID
roamer, because the SID 2 is in the list, but the (SID, NID) pair (2, 7) is not in the list. If the base
station (SID, NID) pair is (4, 0), then the mobile station is a foreign SID roamer, because SID 4 is not
in the list.
2-359
3GPP2 C.S0005-A v6.0
1 The mobile station performs autonomous registrations if REG_ENABLEDs is YES.
2 2.6.5.4 Registration Timers and Indicators
3 The mobile station shall provide the following registration timers:
4 • Power-up/initialization timer (see 2.6.5.1.1).
5 • Timer-based registration timer (see 2.6.5.1.3).
6 • Zone list entry timers (see 2.6.5.1.5).
7 • SID/NID list entry timers (see 2.6.5.1.5).
8 The mobile station shall provide a means of enabling and disabling each timer. When a
9 timer is disabled, it shall not be considered expired. A timer that has been enabled is
10 referred to as active.
11 2.6.5.5 Registration Procedures
12 2.6.5.5.1 Actions in the Mobile Station Initialization State
13 2.6.5.5.1.1 Power-Up or Change to a Different Operating Mode, Band Class, Serving

14 System, or Frequency Block
15 Upon power-up, the mobile station shall perform the following actions:
16 • Delete all entries of ZONE_LISTs.
17 • If ZONE_LISTs-p contains an entry, copy the entry to ZONE_LISTs and disable the
18 corresponding entry timer.
19 • Delete all entries of SID_NID_LISTs.
20 • If SID_NID_LISTs-p contains an entry, copy the entry to SID_NID_LISTs and disable

21 the corresponding entry timer.
22 • Set the registered flag (REGISTEREDs) to NO.
23 • Set timer-based registration enable status (COUNTER_ENABLEDs) to NO.
24 • Set autonomous registration enable status (REG_ENABLEDs) to NO.
25 • Set RETURN_CAUSEs to ‘0000’.
26 • Set ENC_KEYs to NULL.
27 • Set D_SIG_ENCRYPT_MODEs and C_SIG_ENCRYPT_MODEs to ‘000’.
28 Upon switching from using CDMA in a different band class, from using CDMA in a different
29 serving system in a band class that supports multiple serving systems (e.g., Band Class 0),
30 from using CDMA in a different frequency block in a band class that supports frequency
31 block allocations (e.g. Band Class 1, Band Class 4), or from using the 800 MHz analog
32 system, the mobile station shall perform the following actions:
33 • Set timer-based registration enable status (COUNTER_ENABLEDs) to NO.
34 • Set autonomous registration enable status (REG_ENABLEDs) to NO.
2-360
3GPP2 C.S0005-A v6.0
1 • Set RETURN_CAUSEs to ‘0000’.
2 • Set the registered flag (REGISTEREDs) to NO.
3 • Set ENC_KEYs to NULL.
4 2.6.5.5.1.2 Timer Maintenance
5 While in the Mobile Station Initialization State, the mobile station shall update all active
6 registration timers (see 2.6.5.4). If any timer expires while in this state, the mobile station
7 shall preserve the expiration status so that further action can be taken in the Mobile Station
8 Idle State.
9 2.6.5.5.1.3 Entering the Mobile Station Idle State

10 Before entering the Mobile Station Idle State from the Mobile Station Initialization State, the
11 mobile station shall perform the following action:
12 • If REGISTEREDs is equal to NO, enable the power-up/initialization timer with an
13 expiration time of T57m seconds (see 2.6.5.1.1) only when the mobile station is
14 entering this state with a power-up indication.
15 2.6.5.5.2 Actions in the Mobile Station Idle State
16 Requirements in this section and its subsections apply only when the mobile station is in
17 the Mobile Station Idle State.
18 2.6.5.5.2.1 Idle Registration Procedures

19 These procedures are performed whenever the mobile station is in the Mobile Station Idle
20 State (see 2.6.2.1.3).
21 While in the Mobile Station Idle State, the mobile station shall update all active registration
22 timers (see 2.6.5.4).
23 If the power-up/initialization timer has expired or is disabled, the mobile station shall
24 perform the following actions in the order given. If any action necessitates a registration,
25 the mobile station shall enter the Update Overhead Information Substate of the System
26 Access State (see 2.6.3) with a registration indication.
27 1. The timer-based registration timer shall be enabled (COUNTER_ENABLEDs = YES)
28 and the timer count (REG_COUNTs) shall be set to a pseudorandom number as
29 specified in 2.6.5.1.3, if the following conditions are met:
30 a. COUNTER_ENABLEDs is equal to NO; and
31 b. The stored configuration parameters are current (see 2.6.2.2); and

32 c. REG_ENABLEDs is equal to YES; and
33 d. REG_PRDs is not equal to zero.
34 2. If any zone list entry timer (see 2.6.5.1.5) has expired, the mobile station shall delete
35 the corresponding entry from ZONE_LISTs.
2-361
3GPP2 C.S0005-A v6.0
1 3. If any SID/NID list entry timer (see 2.6.5.1.5) has expired, the mobile station shall
2 delete the corresponding entry from SID_NID_LISTs.
3 4. The mobile station shall perform power-up registration, as specified in 2.6.5.1.1, if

4 all the following conditions are met:
5 a. POWER_UP_REGs is equal to ‘1’; and

7 c. REGISTEREDs is equal to NO, and
8 d. REG_ENABLEDs is equal to YES.
9 5. The mobile station shall perform parameter-change registration (see 2.6.5.1.6) if all
10 the following conditions are met:
11 a. PARAMETER_REGs is equal to ‘1’; and

13 c. There is no entry of SID_NID_LISTs whose SID and NID fields match the stored
14 SIDs and NIDs.
15 6. The mobile station shall perform timer-based registration (see 2.6.5.1.3) if all the
16 following conditions are met:
17 a. COUNTER_ENABLEDs is equal to YES; and

20 d. REG_COUNTs is greater than or equal to REG_COUNT_MAXs.
21 7. The mobile station shall perform distance-based registration (see 2.6.5.1.4) if all the
23 a. REG_DISTs is not equal to zero; and

26 d. The current base station’s distance from the base station in which the mobile
27 station last registered (see 2.6.5.1.4) is greater than or equal to
28 REG_DIST_REGs-p.
29 8. The mobile station shall perform zone-based registration (see 2.6.5.1.5) if all the
31 a. TOTAL_ZONESs is not equal to zero; and

34 d. There is no entry of ZONE_LISTs whose SID, NID and REG_ZONE fields match
35 the stored SIDs, NIDs and REG_ZONEs.
2-362
3GPP2 C.S0005-A v6.0
1 9. The mobile station shall perform User Zone registration (see 2.6.2.5.1.10) if it selects
2 an active User Zone (see 2.6.9.1.2).
3 10. The mobile station shall perform encryption re-sync required registration (see
4 2.6.5.1.11) if all the following conditions are met:
5 a. REG_ENCRYPT_RESYNC is equal to YES; and
6 b. None of the above registrations have been performed since the last entering of
7 the Mobile Station Idle State.
8 2.6.5.5.2.2 Processing the Registration Fields of the System Parameters Message and ANSI-
9 41 System Parameters Message
10 When the mobile station processes the System Parameters Message or ANSI-41 System
11 Parameters Message, it shall perform the following actions:
12 1. If REG_PRDs is equal to zero, the mobile station shall set COUNTER_ENABLEDs to
13 NO.
14 2. If REG_PRDs is not equal to zero, the mobile station shall set REG_COUNT_MAXs as
16 3. The mobile station shall update its roaming status and set REG_ENABLEDs as
17 specified in 2.6.5.3.
18 4. If ZONE_LISTs contains more than TOTAL_ZONESs entries, the mobile station shall
19 delete the excess entries according to the rules specified in 2.6.5.1.5.
20 5. If MULT_SIDSs is equal to ‘0’ and SID_NID_LIST contains entries with different
21 SIDs, delete the excess entries according to the rules specified in 2.6.5.1.5.
22 6. If MULT_NIDSs is equal to ‘0’ and SID_NID_LIST contains more than one entry for
23 any SID, delete the excess entries according to the rules specified in 2.6.5.1.5.
24 2.6.5.5.2.3 Ordered Registration

25 Ordered registration is performed after receiving a Registration Request Order while in the
26 Mobile Station Order and Message Processing Operation (see 2.6.2.4).
27 The mobile station shall enter the Update Overhead Information Substate of the System
28 Access State with a registration indication within T33m seconds after the Registration
29 Request Order is received.
30 2.6.5.5.2.4 Power Off
31 These procedures are performed when the mobile station is directed by the user to power
32 off.
33 The mobile station shall perform the following actions:

34 • If an entry of ZONE_LISTs does not have an active timer, copy that entry to
35 ZONE_LISTs-p; otherwise, delete any entry in ZONE_LISTs-p.
2-363
3GPP2 C.S0005-A v6.0
1 • If an entry of SID_NID_LISTs does not have an active timer, copy that entry to
2 SID_NID_LISTs-p; otherwise, delete any entry in SID_NID_LISTs-p.
3 The mobile station shall perform power-down registration (see 2.6.5.1.2) by entering the
4 System Access State with a registration indication within T33m seconds after the user
5 directs the mobile station to power off, if all the following conditions are true:
6 • REG_ENABLEDs equals YES; and
7 • POWER_DOWN_REGs equals ‘1’; and
8 • There is an entry of SID_NID_LISTs for which the SID and NID fields are equal to
9 SIDs and NIDs; and
10 • The power-up/initialization timer (see 2.6.5.1.1) is disabled or has expired.
11 2.6.5.5.2.5 Full-TMSI Timer Expiration

12 When the mobile station sets all the bits of TMSI_CODEs-p to ‘1’ upon expiration of the full-
13 TMSI timer (see 2.6.2), the mobile station shall delete all entries from SID_NID_LISTs and
14 ZONE_LISTs.
15 2.6.5.5.3 Actions in the System Access State
17 the System Access State.
18 2.6.5.5.3.1 Successful Access, Registration, or Implicit Registration
19 These procedures shall be performed after the mobile station receives confirmation of
20 delivery of a Registration Message, Origination Message, or Page Response Message sent on
21 the r-csch (see 2.6.3.1.2).
22 • Disable the power-up/initialization timer (see 2.6.5.1.1).
23 • If the mobile station supports the 800 MHz analog mode, set the First-Idle ID status
24 to enabled (see 2.6.3.11[6]).
25 • Set DIGITAL_REGs-p to ‘00000001’.
26 • Set REG_COUNTs to zero.
27 • Set REGISTEREDs to YES.
28 • Delete all entries from ZONE_LISTs belonging to a different band class (see 2.1.1.1 of
29 [2]) than CDMABANDs.
30 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete all entries from

31 ZONE_LISTs that have a SID from a different serving system than SERVSYSs.
32 • If CDMABANDs = ‘00001’, CDMABANDs = ‘00010’, CDMABANDs = ‘00100’,

33 CDMABANDs = ‘00101’, or CDMABANDs = ‘00111’, or CDMABANDs = ‘01010’, delete
34 all entries from ZONE_LISTs belonging to a different frequency block (see 2.1.1.1 of
35 [2]) than the frequency block associated with SIDs.
2-364
3GPP2 C.S0005-A v6.0
1 • Add REG_ZONEs, SIDs, and NIDs to ZONE_LISTs if not already in the list. If
2 required, include the band class identifier and block identifier for the current band
3 and frequency block as specified in 2.6.5.1.5.
4 • Disable the zone list entry timer for the entry of ZONE_LISTs containing
5 REG_ZONEs, SIDs, and NIDs. For any other entry of ZONE_LISTs whose entry timer
6 is not active, enable the entry timer with the duration specified by ZONE_TIMERs
7 (see 2.6.5.1.5).
8 • If ZONE_LISTs contains more than TOTAL_ZONESs entries, delete the excess entries
9 according to the rules specified in 2.6.5.1.5.
10 • Delete all entries from SID_NID_LISTs belonging to a different band class (see
11 2.1.1.1 of [2]) than CDMABANDs
12 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete all entries from

13 SID_NID_LISTs that have a SID from a different serving system than SERVSYSs.

16 all entries from SID_NID_LISTs belonging to a different frequency block (see 2.1.1.1
17 of [2]) than the frequency block associated with SIDs.
18 • Add SIDs and NIDs to SID_NID_LISTs if not already in the list. If required, include
19 the band class identifier and block identifier for the current band and frequency
20 block as specified in 2.6.5.1.5.
21 • Disable the SID/NID list entry timer for the entry of SID_NID_LISTs containing SIDs,
22 and NIDs. For any other entry of SID_NID_LISTs whose entry timer is not active,
23 enable the entry timer with the duration specified in 2.6.5.1.5.
24 • If SID_NID_LISTs contains more than N10m entries, delete the excess entries
26 • If MULT_SIDSs is equal to ‘0’ and SID_NID_LIST contains entries with different
28 • If MULT_NIDSs is equal to ‘0’ and SID_NID_LIST contains more than one entry for
30 • Set the stored location of last registration (BASE_LAT_REGs-p and BASE_LONG-
31 _REGs-p) to the current base station’s location (BASE_LATs and BASE_LONGs). Set
32 the stored registration distance (REG_DIST_REGs-p) to the current base station’s
33 registration distance (REG_DISTs).
34 • Set REG_ENCRYPT_RESYNC to NO.
35 These procedures shall be performed after the mobile station receives confirmation of
36 delivery of any other message:
38 to enabled (see 2.6.3.11[6]).
2-365
3GPP2 C.S0005-A v6.0
3 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete from ZONE_LISTs all

4 entries from ZONE_LISTs that have a SID from a different serving system than
5 SERVSYSs.

10 • For any entry of ZONE_LISTs not matching REG_ZONEs, SIDs, and NIDs and not
11 having an active entry timer, enable the entry timer with the duration specified by
12 ZONE_TIMERs (see 2.6.5.1.5).
14 2.1.1.1 of [2]) than CDMABANDs.
15 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete from SID_NID_LISTs all

16 entries from SID_NID_LISTs that have a SID from a different serving system than
17 SERVSYSs.

22 • For any entry of SID_NID_LISTs not matching SIDs and NIDs and not having an
23 active entry timer, enable the entry timer with the duration specified by
25 2.6.5.5.3.2 Unsuccessful Access
26 These procedures are performed when the mobile station declares an access attempt failure
27 when in the System Access State (see 2.6.3).
30 to enabled (see 2.6.3.11[6]).
34 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete from ZONE_LISTs all

35 entries from ZONE_LISTs that have a SID from a different serving system than
36 SERVSYSs.
2-366
3GPP2 C.S0005-A v6.0

5 • For any entry of ZONE_LISTs not matching REG_ZONEs, SIDs, and NIDs and not
6 having an active entry timer, enable the entry timer with the duration specified by
9 2.1.1.1 of [2]) than CDMABANDs.
10 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete from SID_NID_LISTs all

11 entries from SID_NID_LISTs that have a SID from a different serving system than
12 SERVSYSs.

17 • For any entry of SID_NID_LISTs not matching SIDs and NIDs and not having an
18 active entry timer, enable the entry timer with the duration specified by
20 2.6.5.5.3.3 Power Off
22 off.

25 ZONE_LISTs-p; otherwise, delete any entry in ZONE_LISTs-p.
27 SID_NID_LISTs-p; otherwise, delete any entry in SID_NID_LISTs-p.
28 2.6.5.5.4 Actions in the Mobile Station Control on the Traffic Channel State
31 2.6.5.5.4.1 Traffic Channel Initialization
32 Upon entering the Traffic Channel Initialization Substate of the Mobile Station Control on the
33 Traffic Channel State, the mobile station shall set COUNTER_ENABLEDs to NO.
34 2.6.5.5.4.2 Timer Maintenance
35 While in the Mobile Station Control on the Traffic Channel State, the mobile station shall
36 update all active registration timers.
2-367
3GPP2 C.S0005-A v6.0
1 If a zone list entry timer expires, the mobile station shall delete the corresponding entry
2 from ZONE_LISTs. If a SID/NID list entry timer expires, the mobile station shall delete the
3 corresponding entry from SID_NID_LISTs.
4 2.6.5.5.4.3 Processing the Mobile Station Registered Message

5 The mobile station receives the Mobile Station Registered Message on the Forward Traffic
6 Channel when the mobile station is considered registered for the base station whose
7 location and other parameters are included in the message.

18 • Registration distance (REG_DISTs = REG_DISTr)
21 to enabled (see [6]).
23 • Add REG_ZONEs, SIDs, and NIDs to ZONE_LISTs if not already in the list. If
24 required, include the band class identifier and block identifier for the current band
25 and frequency block as specified in 2.6.5.1.5.
28 • Disable the zone list entry timer for the entry of ZONE_LISTs containing
29 REG_ZONEs, SIDs, and NIDs. For any other entry of ZONE_LISTs whose entry timer
30 is not active, enable the entry timer with the duration specified by ZONE_TIMERs
31 (see 2.6.5.1.5).
32 • If ZONE_LISTs contains more than TOTAL_ZONESs entries, delete the excess entries
34 • Delete all entries from SID_NID_LISTs belonging to a different band class (see [2])
35 than CDMABANDs.
2-368
3GPP2 C.S0005-A v6.0
1 • Add SIDs and NIDs to SID_NID_LISTs if not already in the list. If required, include
2 the band class identifier and block identifier for the current band and frequency
3 block as specified in 2.6.5.1.5.
4 • Disable the SID/NID list entry timer for the entry of SID_NID_LISTs containing SIDs,
5 and NIDs. For any other entry of SID_NID_LISTs whose entry timer is not active,
6 enable the entry timer with the duration specified in 2.6.5.1.5.
7 • If SID_NID_LISTs contains more than N10m entries, delete the excess entries
9 • If MULT_SIDSs is equal to ‘0’ and SID_NID_LIST contains entries with different
11 • If MULT_NIDSs is equal to ‘0’ and SID_NID_LIST contains more than one entry for
13 • Set the stored location of last registration (BASE_LAT_REGs-p and BASE_LONG-
14 _REGs-p) to the base station’s location (BASE_LATs and BASE_LONGs). Set the
15 stored registration distance (REG_DIST_REGs-p) to the base station’s registration
16 distance (REG_DISTs).
17 • Update its roaming status and set MOB_TERMs as specified in 2.6.5.3. The mobile
18 station should indicate to the user whether the mobile station is roaming.
19 2.6.5.5.4.4 Power Off
21 off.

24 ZONE_LISTs-p; otherwise, delete the entry in ZONE_LISTs-p if ZONE_LISTs-p
25 contains an entry.
27 SID_NID_LISTs-p; otherwise, delete the entry in SID_NID_LISTs-p if SID_NID_LISTs-p
28 contains an entry.
29 2.6.6 Handoff Procedures
30 This section presents an overview and mobile station requirements for handoffs occurring
31 while the mobile station is in the Mobile Station Control on the Traffic Channel State (see
32 2.6.4). Mobile station requirements for handoffs occurring while the mobile station is in the
33 Mobile Station Idle State are specified in 2.6.2.1.4.
34 2.6.6.1 Overview
35 2.6.6.1.1 Types of Handoff

36 The mobile station supports the following three handoff procedures while in the Mobile
37 Station Control on the Traffic Channel State:
2-369
3GPP2 C.S0005-A v6.0
1 • Soft Handoff: A handoff in which the mobile station commences communications

2 with a new base station without interrupting communications with the old base
3 station. Soft handoff can only be used between CDMA Channels having identical
4 Frequency Assignments. Soft handoff provides diversity of Forward Traffic Channels
5 and Reverse Traffic Channel paths on the boundaries between base stations.
6 • CDMA-to-CDMA Hard Handoff: A handoff in which the mobile station is transitioned

7 between disjoint sets of base stations, different band classes, different Frequency
8 Assignments, or different frame offsets.
9 • CDMA-to-Analog Handoff: A handoff in which the mobile station is directed from a
10 CDMA traffic channel to an analog voice channel.
11 The mobile station shall support soft handoffs on the same Frequency Assignment (see
12 2.6.6.2.7). The mobile station shall support CDMA-to-CDMA hard handoffs between band
13 classes on which it supports CDMA operation (see 2.6.6.2.8). The mobile station shall
14 support CDMA-to-Analog handoffs from band classes on which it supports CDMA operation
15 to band classes on which it supports analog operation (see 2.6.6.2.9).
16 2.6.6.1.2 Pilot Sets
17 Within section 2.6.6 the term pilot refers to a Pilot Channel identified by a pilot sequence
18 offset (see 3.1.3.2.1 of [2]), a Walsh function or a quasi-orthogonal function (see 3.1.3.2.2 of
19 [2]), and a Frequency Assignment (see 2.1.1.1 of [2]). A pilot is associated with the Forward
20 Traffic Channels in the same Forward CDMA Channel. All pilots in a pilot set have the
21 same CDMA Frequency Assignment.
22 The mobile station searches for pilots on the current CDMA Frequency Assignment to detect
23 the presence of CDMA Channels and to measure their strengths. When the mobile station
24 detects a pilot of sufficient strength that is not associated with any of the Forward Traffic
25 Channels assigned to it, it sends a Pilot Strength Measurement Message or an Extended Pilot
26 Strength Measurement Message to the base station. The base station can then assign a
27 Forward Traffic Channel associated with that pilot to the mobile station and direct the
28 mobile station to perform a handoff.
29 The pilot search parameters and the rules for Pilot Strength Measurement Message or
30 Extended Pilot Strength Measurement Message transmission are expressed in terms of the
31 following sets of pilots:
32 • Active Set: The pilots associated with the Forward Traffic Channels assigned to the
33 mobile station.
34 • Candidate Set: The pilots that are not currently in the Active Set but have been
35 received by the mobile station with sufficient strength to indicate that the associated
36 Forward Traffic Channels could be successfully demodulated.
37 • Neighbor Set: The pilots that are not currently in the Active Set or the Candidate Set
38 and are likely candidates for handoff.
2-370
3GPP2 C.S0005-A v6.0
1 • Remaining Set: The set of all possible pilots in the current system on the current
2 CDMA Frequency Assignment, excluding the pilots in the Neighbor Set, the
3 Candidate Set, and the Active Set. This set of possible pilots consists of pilots
4 whose pilot PN sequence offset indices are integer multiples of PILOT_INCs.
5 The base station may direct the mobile station to search for pilots on a different CDMA
6 frequency to detect the presence of CDMA Channels and to measure their strengths. The
7 mobile station reports the results of the search to the base station using the Candidate
8 Frequency Search Report Message. Depending upon the pilot strength measurements
9 reported in the Candidate Frequency Search Report Message, the base station can direct the
10 mobile station to perform an inter-frequency hard handoff.
11 The pilot search parameters are expressed in terms of the following sets of pilots on the
12 CDMA Candidate Frequency:
13 • Candidate Frequency Neighbor Set: A list of pilots on the CDMA Candidate
14 Frequency.
15 • Candidate Frequency Search Set: A subset of the Candidate Frequency Neighbor Set
16 that the base station may direct the mobile station to search.
17 2.6.6.2 Requirements
18 2.6.6.2.1 Pilot Search
19 For the pilot sets defined in 2.6.6.1.2, the base station sets the search window (range of PN
20 offsets) in which the mobile station is to search for usable multipath components (i.e.,
21 multipath components that the mobile station can use for demodulation of the associated
22 Forward Traffic Channel) of the pilots in the set.
23 Search performance criteria are defined in [11].
24 This search shall be governed by the following:

25 • Active Set and Candidate Set: The search procedures for pilots in the Active Set and
26 Candidate Set shall be identical. The search window size16 for each pilot in the
27 Active Set and Candidate Set shall be the number of PN chips specified in Table
28 2.6.6.2.1-1 corresponding to SRCH_WIN_As. The mobile station should center the
29 search window for each pilot of the Active Set and Candidate Set around the earliest
30 arriving usable multipath component of the pilot. If the mobile station receives a
31 value greater than or equal to 13 for SRCH_WIN_Ar, it may store and use the value
32 13 in SRCH_WIN_As.
16 The table defines the entire search range. For example, SRCH_WIN_A = 6 corresponds to a 28 PN
s
chip search window or ±14 PN chips around the search window center.
2-371
3GPP2 C.S0005-A v6.0
1 Table 2.6.6.2.1-1. Searcher Window Sizes
SRCH_WIN_A SRCH_WIN_A
window_size window_size
SRCH_WIN_N SRCH_WIN_N
(PN chips) (PN chips)
SRCH_WIN_NGHBR SRCH_WIN_NGHBR
SRCH_WIN_R SRCH_WIN_R
CF_SRCH_WIN_N CF_SRCH_WIN_N
0 4 8 60
1 6 9 80
2 8 10 100
3 10 11 130
4 14 12 160
5 20 13 226
6 28 14 320
7 40 15 452
3 Table 2.6.6.2.1-2. Search Window Offset
SRCH_OFFSET_NGHBR Offset ( PN chips)

CF_SRCH_OFFSET_NGHBR
0 0
1 window_size/2
2 window_size
3 3 × window_size /2
4 - window_size /2
5 - window_size
6 -3 × window_size /2
7 Reserved
4
2-372
3GPP2 C.S0005-A v6.0
1 • Neighbor Set: If SRCH_WIN_NGHBR_INCLs is equal to ‘1’, the search window size for
2 each pilot in the Neighbor Set shall be the number of PN chips specified in Table
3 2.6.6.2.1-1, corresponding to SRCH_WIN_NGHBRs associated with the pilot being
4 searched. If SRCH_WIN_NGHBR_INCLs is equal to ‘0’, the search window size for
5 each pilot in the Neighbor Set shall be the number of PN chips specified in Table
6 2.6.6.2.1-1 corresponding to SRCH_WIN_Ns. If SRCH_OFFSET_INCLs is equal to ‘1’,
7 the search window offset for each pilot in the Neighbor Set shall be the number of
8 PN chips specified in Table 2.6.6.2.1-2, corresponding to SRCH_OFFSET_NGHBRs
9 associated with the pilot being searched. If SRCH_OFFSET_INCLs is equal to ‘0’, the
10 search window offset for each pilot in the Neighbor Set shall be zero PN chip. The
11 mobile station should center the search window for each pilot in the Neighbor Set
12 around the pilot’s PN sequence offset plus the corresponding search window offset,
13 using timing defined by the mobile station’s time reference (see [2]). If
14 SEARCH_PRIORITY_INCLs is equal to ‘1’, the mobile station should use
15 SEARCH_PRIORITYs for the corresponding pilot to schedule its neighbor search. If
16 the mobile station supports hopping pilot beacons and the TIMING_INCL field of the
17 NGHBR_REC for the corresponding pilot is equal to ‘1’, then the mobile station shall
18 use the information included in the NGHBR_TX_OFFSET, NGHBR_TX_DURATION,
19 and NGHBR_TX_PERIOD fields of the NGHBR_REC for the corresponding pilot to
20 schedule the time for searching the neighbor. If ADD_PILOT_REC_INCL field of the
21 NGHBR_REC for the corresponding pilot is equal to ‘1’, the mobile station shall use
22 the information included in the NGHBR_PILOT_REC field for searching the neighbor.
23 • Remaining Set: The search window size for each pilot in the Remaining Set shall be
24 the number of PN chips specified in Table 2.6.6.2.1-1 corresponding to
25 SRCH_WIN_Rs. The mobile station should center the search window for each pilot
26 in the Remaining Set around the pilot’s PN sequence offset, using timing defined by
27 the mobile station’s time reference (see [2]). The mobile station should only search
28 for Remaining Set pilots whose pilot PN sequence offset indices are equal to integer
29 multiples of PILOT_INCs.
2-373
3GPP2 C.S0005-A v6.0
1 • Candidate Frequency Search Set: If CF_SRCH_WIN_NGHBRN_INCLs is equal to ‘1’,

2 the search window size for each pilot in the Candidate Frequency Search sSet shall
3 be the number of PN chips specified in Table 2.6.6.2.1-1, corresponding to
4 SRCH_WIN_NGHBRs associated with the pilot being searched. If
5 CF_SRCH_WIN_NGHBR_INCLs is equal to ‘0’, the search window size for each pilot
6 in the Candidate Frequency Search Set shall be the number of PN chips specified in
7 Table 2.6.6.2.1-1 corresponding to CF_SRCH_WIN_Ns. If CF_SRCH_OFFSET_INCLs
8 is equal to ‘1’, the search window offset for each pilot in the Candidate Frequency
9 Search Set shall be the number of PN chips specified in Table 2.6.6.2.1-2,
10 corresponding to SRCH_OFFSET_NGHBRs associated with the pilot being searched.
11 If CF_SRCH_OFFSET_INCLs is equal to ‘0’, the search window offset for each pilot in
12 the Candidate Frequency Search Set shall be zero PN chips. The mobile station
13 should center the search window for each pilot in the Candidate Frequency Search
14 Set around the pilot’s PN sequence offset plus the corresponding search window
15 offset using timing defined by the mobile station’s time reference (see [2]). If
16 CF_SEARCH_PRIORITY_INCLs is equal to ‘1’, the mobile station should use
17 SEARCH_PRIORITYs associated with each pilot to schedule a search of its Candidate
18 Frequency Search Set.
19 2.6.6.2.2 Pilot Strength Measurements
20 The mobile station assists the base station in the handoff process and in the Reverse
21 Supplemental Code Channel operation and in the Reverse Supplemental Channel operation
22 by measuring and reporting the strengths of received pilots.
23 For an SR1 pilot, the mobile station should use the searcher element (see [2]) to compute
24 the strength of a pilot (PS) by adding the ratios of received pilot energy per chip, Ec, to total
25 received spectral density (noise and signals), Io, of at most k usable multipath components,
26 where k is the number of demodulating elements (see [2]) supported by the mobile station.
27 For an SR3 pilot, the pilot strength is given by
  Ec   E c  
     
1   Ec   I o 1  I o  2 
×   + +  where:
3   I o
28
 Pr imary ∆1 ∆2 
 
 
 Ec 
29 -   is the pilot Ec/Io measured on the Primary carrier (computed as specified
 Io  Pr imary
30 above for SR1 pilots),
 Ec 
31 -   is the pilot Ec/Io measured on the pilot on the lower frequency of the two
 Io 1
32 remaining SR3 frequencies (computed as specified above for SR1 pilots), and ∆ 1 is
2-374
3GPP2 C.S0005-A v6.0
1 the pilot power level on the lower frequency of the two remaining SR3 frequencies
2 relative to that of the primary SR3 pilot, i.e. ∆ 1 = 10 ( − SR3_PILOT_POWER1 / 10) .
 Ec 
3 -   is the pilot Ec/Io measured on the pilot on the higher frequency of the two
 Io 2
4 remaining SR3 frequencies (computed as specified above for SR1 pilots), and ∆ 2 is
5 the pilot power level on the higher frequency of the two remaining SR3 frequencies
6 relative to that of the primary SR3 pilot, i.e. ∆ 2 = 10 ( −SR3_PILOT_POWER2 / 10) .
7 2.6.6.2.3 Handoff Drop Timer
8 The mobile station shall maintain a handoff drop timer for each pilot in the Active Set and
9 Candidate Set.
10 If P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to ‘000000’, the
12 • For the Candidate Set, the mobile station shall start the timer whenever the
13 strength of the corresponding pilot becomes less than T_DROPs. The mobile station
14 shall reset and disable the timer if the strength of the corresponding pilot exceeds
15 T_DROPs.
16 • For the Active Set, the mobile station shall start the timer whenever the strength of
17 the corresponding pilot becomes less than T_DROPs. The mobile station shall start
18 the timer even if the timer has previously expired. The mobile station shall reset
19 and disable the timer if the strength of the corresponding pilot exceeds T_DROPs.
20 If P_REV_IN_USEs is greater than three and SOFT_SLOPEs is not equal to ‘000000’, the
22 • For the Candidate Set, the mobile station shall start the timer whenever the
23 strength of the corresponding pilot becomes less than T_DROPs. The mobile station
24 shall reset and disable the timer if the strength of the corresponding pilot exceeds
25 T_DROPs.
26 • For the Active Set, the mobile station shall sort the NA pilots in the Active Set in
27 order of increasing strengths, i.e., PS1 < PS2 < PS3 < …< PSNA where the strength
28 PS is as defined in 2.6.6.2.2. The mobile station shall start the timer whenever the
29 strength PSi satisfies the following inequality:
SOFT_SLOPE s DROP_INTER CEPTs T_DROPs
30 10 × log 10 PS i < max( × 10 × log 10 ∑ PS j + ,- )
8 j> i 2 2
i = 1, 2, ..., PS N A -1
31
32 For the Active Set, the mobile station shall start the timer even if the timer has previously
33 expired. The mobile station shall reset and disable the timer whenever the above inequality
34 is not satisfied for the corresponding pilot.
2-375
3GPP2 C.S0005-A v6.0
1 If T_TDROPs equals zero, the mobile station shall consider the timer expired within 100 ms
2 of enabling it. Otherwise, the mobile station shall consider the timer expired within 10% of
3 the timer expiration value shown in Table 2.6.6.2.3-1 corresponding to T_TDROPs. If
4 T_TDROPs changes, the mobile station shall begin using the new value for all handoff drop
5 timers within 100 ms.
7 Table 2.6.6.2.3-1. Handoff Drop Timer Expiration Values
Timer Timer
T_TDROP Expiration T_TDROP Expiration
(seconds) (seconds)
0 0.1 8 27
1 1 9 39
2 2 10 55
3 4 11 79
4 6 12 112
5 9 13 159
6 13 14 225
7 19 15 319
9 The mobile station shall indicate the status of the handoff drop timer for all pilots in the
10 Active Set and Candidate Set when transmitting a Pilot Strength Measurement Message or
11 an Extended Pilot Strength Measurement Message.
12 2.6.6.2.4 Pilot PN Phase
13 The mobile station shall measure the arrival time, PILOT_ARRIVAL, for each pilot reported
14 to the base station. The pilot arrival time shall be the time of occurrence, as measured at
15 the mobile station antenna connector, of the earliest arriving usable multipath component
16 of the pilot (for SR3 pilots, it is based on the earliest arriving usable multipath component
17 from all three carriers). The arrival time shall be measured relative to the mobile station’s
18 time reference (see [2]) in units of PN chips. The mobile station shall compute the reported
19 pilot PN phase, PILOT_PN_PHASE, as
20 PILOT_PN_PHASE = (PILOT_ARRIVAL + (64 × PILOT_PN)) mod 215,
21 where PILOT_PN is the PN sequence offset index of the pilot (see [2]).
22 2.6.6.2.5 Handoff Messages
23 2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
24 If the mobile station receives any of the following messages, then the mobile station shall
25 process the message as described.
2-376
3GPP2 C.S0005-A v6.0
1 1. Pilot Measurement Request Order: The mobile station shall send, within T56m
2 seconds, a Pilot Strength Measurement Message if P_REV_IN_USE is less than seven
3 or a Extended Pilot Strength Measurement Message if P_REV_IN_USE is equal to or
4 greater than seven.
5 2. Analog Handoff Direction Message: The mobile station shall process the message as
7 3. Neighbor List Update Message: The mobile station shall process the message as
8 specified in 2.6.6.2.6.3 and set SEARCH_PRIORITY_INCLs,
9 SRCH_WIN_NGHBR_INCLs, and SRCH_OFFSET_INCLs to ‘0’, and set TIMING_INCL
10 for each of the neighboring base stations in the Neighbor List Update Message to ‘0’.
11 4. Extended Handoff Direction Message: The mobile station shall process the message as
12 follows:
13 The mobile station shall send a Mobile Station Reject Order with the ORDQ field set
14 to ‘00000110’ (capability not supported), if the mobile station does not support the
15 band class specified in the Extended Handoff Direction Message.
16 If the mobile station does not send a Mobile Station Reject Order in response to the
17 Extended Handoff Direction Message, the mobile station shall perform the following at
18 the action time of the message:
19 • The mobile station shall send a Handoff Completion Message or an Extended

20 Handoff Completion Message as specified in 2.6.6.2.5.2.
21 • Update the Active Set, Candidate Set, and Neighbor Set in accordance with the
22 Extended Handoff Direction Message processing (see 2.6.6.2.6.1, 2.6.6.2.6.2, and
23 2.6.6.2.6.3).
24 • The mobile station shall delete all pilots that are not listed in the Active Set of the
25 Fundamental Channel from the Active Set of the Supplemental Channel for the
26 Forward Supplemental Channel Assignment (if any). If these deleted pilots include
27 all pilots in the Active Set of the Supplemental Channel, the mobile station shall
28 cancel the Forward Supplemental Channel Assignment.
29 • Discontinue use of all Forward Traffic Channels associated with pilots not listed in
30 the Extended Handoff Direction Message.
31 • The mobile station shall update the Code Channel List, CODE_CHAN_LISTs, as
32 specified in 2.6.8.
33 • If the mobile station is currently processing Forward Supplemental Code Channels,

34 then it shall continue processing the Forward Supplemental Code Channels using
35 the updated Code Channel List, CODE_CHAN_LISTs.
36 • The mobile station shall set IGNORE_SCAMs and IGNORE_ESCAMs to ‘0’.
37 • If HARD_INCLUDED is equal to ‘1’, perform the following actions:

38 – If FRAME_OFFSETr is not equal to FRAME_OFFSETs, change the frame
39 offset on all of the code channels of the Forward Traffic Channel and of the
2-377
3GPP2 C.S0005-A v6.0
1 – If RESET_L2r is equal to ‘1’, Layer 3 shall send a L2-Supervision.Request

2 primitive to Layer 2 to reset the acknowledgment procedures as specified in
3 2.2.1.1 and 2.2.2.1 of [4]. The acknowledgment procedures shall be reset
4 immediately after the action time of the Extended Handoff Direction Message.
5 – If RESET_FPCr is equal to ‘1’, initialize the Forward Traffic Channel power
6 control counters as specified in 2.6.4.1.1.1.
7 – If SERV_NEG_TYPEr is equal to ‘1’, set SERV_NEGs to enabled; otherwise set
8 SERV_NEGs to disabled.
9 – Use the long code mask specified by the PRIVATE_LCMr (see 2.3.12.3) and
10 indicate to the user the voice privacy mode status.
11 – Process the ENCRYPT_MODE field as specified in 2.3.12.2.
12 • Store the following parameters from the current configuration:

13 – Serving Frequency Assignment (SF_CDMACHs = CDMACHs)
14 – Serving Frequency band class (SF_BAND_CLASSs = BAND_CLASSs)
15 – Serving Frequency frame offset (SF_FRAME_OFFSETs= FRAME_OFFSETs)
16 • If HARD_INCLUDED is not equal to ‘1’, set NUM_PREAMBLEs = ‘000’.
17 • Store the following parameters from the Extended Handoff Direction Message:
18 – Extended Handoff Direction Message sequence number (HDM_SEQs =
19 HDM_SEQr)
20 – If SEARCH_INCLUDED is equal to ‘1’, then store the following:

21 + Search window size for the Active Set and Candidate Set
22 (SRCH_WIN_As = SRCH_WIN_Ar )
23 + Pilot detection threshold (T_ADDs = T_ADDr)
24 + Pilot drop threshold (T_DROPs = T_DROPr)
25 + Active Set versus Candidate Set comparison threshold

26 (T_COMPs = T_COMPr)
27 + Drop timer value (T_TDROPs = T_TDROPr)
28 – If HARD_INCLUDED is equal to ‘1’, then store the following:

29 + Frame offset (FRAME_OFFSETs = FRAME_OFFSETr)
30 + Nominal power setting of the target cell (NOM_PWRs = NOM_PWRr)
31 + Hard handoff traffic channel preamble count required before transmitting

32 Handoff Completion Message or Extended Handoff Completion Message
33 (NUM_PREAMBLEs = NUM_PREAMBLEr )
34 + CDMA band class (CDMABANDs = BAND_CLASSr)
35 + Frequency assignment (CDMACHs = CDMA_FREQr)
2-378
3GPP2 C.S0005-A v6.0
1 + Nominal power setting of the target cell (If CDMABANDs = ‘00000’ or

2 CDMABANDs = ‘00011’, then NOM_PWR_EXTs = ‘0’; otherwise,
3 NOM_PWR_EXTs = NOM_PWR_EXTr)
4 – One occurrence of PILOT_PN and PWR_COMB_IND for each included

5 member of the Active Set.
6 – If ADD_LENGTH is not equal to ‘000’, then store the following:

7 + Protocol revision level (P_REVs = P_REVr)
8 + Protocol revision level currently in use (P_REV_IN_USEs = the minimum

9 value of P_REVs and MOB_P_REVp of the current band class)
10 – Disable return on failure (RETURN_IF_HANDOFF_FAILs = ‘0’)
11 • Perform a soft or hard handoff depending on the following conditions:
12 – If any of the following conditions is true, the mobile station shall perform a
13 hard handoff:
14 + HARD_INCLUDED is set to ‘1’ and either BAND_CLASSr is not equal to
15 SF_CDMABANDs, CDMA_FREQr is not equal to SF_CDMACHs, or
16 FRAME_OFFSETr is not equal to SF_FRAME_OFFSETs, or
17 + The set of pilots specified by the message is disjoint from the Active Set
18 prior to the action time of the message.
19 – If the mobile station performs a hard handoff, it shall do the following:
20 + If a Periodic Serving Frequency Pilot Report Procedure is in progress, abort

21 the procedure (see 2.6.6.2.12).
22 + If a Candidate Frequency periodic search is in progress, abort the periodic

23 search (see 2.6.6.2.8.3.4 and 2.6.6.2.10.4) and set PERIODIC_SEARCHs to
24 ‘0’.
25 + The mobile station shall cancel the Forward Supplemental Channel

26 assignment or the Reverse Supplemental Channel assignment (if any).
27 + Perform the actions specified in 2.6.6.2.8.1. If the message specifies more

28 than one pilot, the mobile station shall also perform the actions specified in
29 2.6.6.2.7.1 and 2.6.6.2.7.2.
30 – Otherwise, the mobile station shall perform a soft handoff as specified in

31 2.6.6.2.7.
32 5. Candidate Frequency Search Request Message: The mobile station shall process the
35 to ‘00000110’ (capability not supported), if the following condition is true:
36 • SEARCH_MODEr is not equal to ‘0000’, and the mobile station does not support
37 the capability specified by SEARCH_MODEr.
2-379
3GPP2 C.S0005-A v6.0
1 If none of the above conditions is true, the mobile station shall perform the actions
2 described in the remainder of this section to process the Candidate Frequency
3 Search Request Message.
4 If SEARCH_MODEr is equal to ‘0000’, the mobile station shall process the Candidate
5 Frequency Search Request Message as follows:
6 • The mobile station shall send a Mobile Station Reject Order with the ORDQ field
7 set to ‘00001100’ (invalid Frequency Assignment), if the Frequency Assignment
8 specified in the message is the same as the Serving Frequency (BAND_CLASSr is
9 equal to CDMABANDs and CDMA_FREQr is equal to CDMACHs).
11 set to ‘00001010’ (search set not specified), if SEARCH_TYPEr is equal to ‘01’ or
12 ‘11’, and one of the following conditions is true:
13 − PILOT_UPDATEr is equal to ‘0’ and the Candidate Frequency Search Set
14 before the action time of the Candidate Frequency Search Request Message is
15 empty, or
16 − PILOT_UPDATEr is equal to ‘1’ and the message specifies an empty search
17 set.
19 set to ‘00001101’ (search period too short), if SEARCH_TYPEr is equal to ‘11’ and
20 search_period is less than (max (fwd_time, rev_time ) + T71m) seconds, where
21 search_period, fwd_time and rev_time are defined below.
22 (In the following, if PILOT_UPDATEr is equal to ‘1’, rec_search_set is the set of
23 pilots specified in the Candidate Frequency Search Request Message with the
24 corresponding SEARCH_SET field set to ‘1’; otherwise, rec_search_set is the
25 Candidate Frequency Search Set before the action time of the Candidate
26 Frequency Search Request Message.)
27 search_period = time period corresponding to SEARCH_PERIODr shown in
28 Table 2.6.6.2.8.3.2-1
29 fwd_time = the mobile station’s estimate of the total length of time, in

30 seconds, for which the mobile station will need to suspend its
31 current Forward Traffic Channel processing in order to tune to
32 the Candidate Frequency, to search rec_search_set, and to re-
33 tune to the Serving Frequency; if the mobile station searches
34 rec_search_set in multiple visits, fwd_time is the total time for
35 all visits to the Candidate Frequency in a search period (see
36 2.6.6.2.8.3.2)
2-380
3GPP2 C.S0005-A v6.0
1 rev_time = the mobile station’s estimate of the total length of time, in

3 current Reverse Traffic Channel processing in order to tune to
4 the Candidate Frequency, to search rec_search_set, and to re-
5 tune to the Serving Frequency; if the mobile station searches
6 rec_search_set in multiple visits, rev_time is the total time for
7 all visits to the Candidate Frequency in a search period
8 • If the mobile station does not send a Mobile Station Reject Order in response to
9 the Candidate Frequency Search Request Message, it shall perform the following:
10 − The mobile station shall send a Candidate Frequency Search Response

11 Message in assured mode, within T56m seconds of receiving the Candidate
12 Frequency Search Request Message. The mobile station shall set the fields of
13 the Candidate Frequency Search Response Message as follows:
14 + The mobile station shall set TOTAL_OFF_TIME_FWD and

15 TOTAL_OFF_TIME_REV to its estimate of the total number of frames or
16 power control groups for which it will need to suspend its current
17 Forward Traffic Channel processing and Reverse Traffic Channel
18 processing, respectively, in order to tune to the Candidate Frequency, to
19 search rec_search_set, and to re-tune to the Serving Frequency (see
20 2.6.6.2.8.3.2). If the mobile station searches rec_search_set in multiple
21 visits to the Candidate Frequency, the mobile station shall report the
22 total number of frames or power control groups in all visits in a search
23 period for which it will need to suspend its current Forward Traffic
24 Channel and the Reverse Traffic Channel processing.
25 + The mobile station shall set MAX_OFF_TIME_FWD and

26 MAX_OFF_TIME_REV to its estimate of the maximum number of frames
27 or power control groups for which it will need to suspend its current
29 processing, respectively, during any single visit to tune to the Candidate
30 Frequency, to search a subset of rec_search_set, and to re-tune to the
31 Serving Frequency.17
17 If the mobile station searches the entire Candidate Frequency Search Set in a single visit to the
Candidate Frequency, TOTAL_OFF_TIME_FWD will be equal to MAX_OFF_TIME_FWD, and

TOTAL_OFF_TIME_REV will be equal to MAX_OFF_TIME_REV.
2-381
3GPP2 C.S0005-A v6.0
1 + The mobile station shall set PCG_OFF_TIMES to ‘1’ if

2 TOTAL_OFF_TIME_FWD, MAX_OFF_TIME_FWD, TOTAL_OFF_TIME_-
3 REVFWD and MAX_OFF_TIME_REVFWD are expressed in units of power
4 control groups. If these time estimates are expressed in units of frames,
5 the mobile station shall set PCG_OFF_TIMES to ‘0’. The mobile station
6 shall not use power control groups as the unit of delay duration if
7 P_REV_IN_USEs is less than six.
8 + If ALIGN_TIMINGr is equal to ‘1’, the mobile station shall set

9 ALIGN_TIMING_USED to ‘1’ to indicate if it will align its search as
10 requested by the base station; otherwise, the mobile station shall set
11 ALIGN_TIMING_USED to ‘0’. If ALIGN_TIMING_USED is set to ‘1’, the
12 mobile station shall set MAX_NUM_VISITS to the maximum number of
13 visits per search period minus one. and, iIf MAX_NUM_VISITS is not
14 equal to 0, the mobile station shall set INTER_VISIT_TIME, in units of
15 frames or power control groups, to its estimate of the time between
16 subsequent the beginning of consecutive visits to the Candidate
17 Frequency within the same search period.
18 − When the message takes effect, the mobile station shall perform the following
19 actions:
20 + If any periodic search is in progress, the mobile station shall abort it (see
21 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
22 + Store the following parameters from the Candidate Frequency Search

23 Request Message:
24 ο Candidate Frequency Search Request Message sequence number

25 (CFSRM_SEQs = CFSRM_SEQr)
26 ο Periodic search flag: If SEARCH_TYPEr is equal to ‘11’, the mobile

27 station shall set PERIODIC_SEARCHs to ‘1’; otherwise, the mobile
28 station shall set PERIODIC_SEARCHs to ‘0’.
29 ο Search period on the Candidate Frequency

30 (SEARCH_PERIODs = SEARCH_PERIODr)
31 ο Candidate Frequency search mode

32 (SEARCH_MODEs = SEARCH_MODEr)
33 ο Band class for the Candidate Frequency

34 (CF_CDMABANDs = BAND_CLASSr)
35 ο CDMA Channel number for the CDMA Candidate Frequency

36 (CF_CDMACHs = CDMA_FREQr)
37 ο Serving Frequency total pilot Ec threshold

38 (SF_TOTAL_EC_THRESHs = SF_TOTAL_EC_THRESHr)
39 ο Serving Frequency total pilot Ec/Io threshold

40 (SF_TOTAL_EC_IO_THRESHs = SF_TOTAL_EC_IO_THRESHr)
2-382
3GPP2 C.S0005-A v6.0
1 ο Received power difference threshold

2 (DIFF_RX_PWR_THRESHs = DIFF_RX_PWR_THRESHr)
3 ο Candidate Frequency Total pilot Ec/Io threshold

4 (MIN_TOTAL_PILOT_EC_IOs = MIN_TOTAL_PILOT_EC_IOr)
5 ο Pilot detection threshold on the CDMA Candidate Frequency

6 (CF_T_ADDs = CF_T_ADDr)
7 ο Maximum time on the CDMA Target Frequency that the mobile

8 station may wait to receive a period of (N11m × 20) ms with sufficient
9 signal quality (e.g. good frames) on the physical channel
10 corresponding to FPC_PRI_CHANs
11 (TF_WAIT_TIMEs = TF_WAIT_TIMEr)
12 ο Pilot PN sequence offset increment on the CDMA Candidate

13 Frequency (CF_PILOT_INCs = CF_PILOT_INCr)
14 ο Search window for pilots in the Neighbor Set on the CDMA Candidate
15 Frequency (CF_SRCH_WIN_Ns = CF_SRCH_WIN_Nr)
16 ο Search window for pilots in the Remaining Set on the CDMA

17 Candidate Frequency (CF_SRCH_WIN_Rs = CF_SRCH_WIN_Rr)
18 ο If PILOT_UPDATE is equal to ‘1’, the mobile station shall perform the

19 following:
20 ◊ Set CF_SEARCH_PRIORITY_INCLs and
21 CF_SRCH_WIN_NGHBR_INCLs to the values corresponding to
22 CF_NGHBR_SRCH_MODE shown in Table 2.6.6.2.5.1-1,
23 ◊ Set CF_SRCH_OFFSET_INCLs to CF_SRCH_OFFSET_INCLr.
24 ο If PILOT_UPDATE is equal to ‘1’, the mobile station shall replace the

25 Candidate Frequency Neighbor Set with all neighbor pilots specified
26 in the Candidate Frequency Search Request Message. Specifically, the
28 ◊ Set the NGHBR_PN field of the Candidate Frequency Neighbor Set

29 Pilot Record to NGHBR_PNr.
30 ◊ Set the ADD_PILOT_REC_INCL field of the Candidate Frequency

31 Neighbor Set Pilot Record to ADD_PILOT_REC_INCLr. If
32 ADD_PILOT_REC_INCLr is equal to ‘1’, the mobile station shall
34 – Set the NGHBR_PILOT_REC_TYPE field of the Candidate

35 Frequency Neighbor Set Pilot Record to
2-383
3GPP2 C.S0005-A v6.0
1 – If NGHBR_PILOT_REC_TYPEr equals ‘000’, the mobile station

2 shall set the TD_POWER_LEVEL and TD_MODE fields of the
3 Candidate Frequency Neighbor Set Pilot Record to
4 TD_POWER_LEVELr and set the TD_MODE field of
5 NGHBR_PILOT_REC to TD_MODEr, respectively.
6 – If NGHBR_PILOT_REC_TYPEr is equal to ‘001’, the mobile

7 station shall
8 + Set the AUX_PILOT_QOF field of the Candidate Frequency

9 Neighbor Set Pilot Record to QOFr.
10 + Set the AUX_PILOT_WALSH_CODE field of the Candidate

12 AUX_PILOT_WALSHr with the Walsh Code length specified
13 by WALSH_LENGTHr.

15 station shall:
16 + Set the AUX_PILOT_TD_QOF field of the Candidate

17 Frequency Neighbor Set Pilot Record to QOFr.
18 + Set the AUX_PILOT_WALSH_CODE field of the Candidate

19 Frequency Neighbor Set Pilot Record to AUX_WALSHr with
20 the Walsh Code length specified by WALSH_LENGTHr.
21 + Set the AUX_TD_POWER_LEVEL field of the Candidate

24 + Set the TD_MODE field of the Candidate Frequency

25 Neighbor Set Pilot Record to TD_MODEr.

27 station shall:
28 + Set the SR3_PRIMARY_PILOT field of Candidate Frequency

29 Neighbor Set Pilot Record to SR3_PRIMARY_PILOTr.
30 + Set the SR3_PILOT_POWER1 field of Candidate Frequency

31 Neighbor Set Pilot Record to SR3_PILOT_POWER1r.


35 station shall:
36 + Set the SR3_PRIMARY_PILOT field of Candidate Frequency

37 Neighbor Set Pilot Record to SR3_PRIMARY_PILOTr.

2-384
3GPP2 C.S0005-A v6.0

3 + Set the AUX_PILOT_QOF field of Candidate Frequency

4 Neighbor Set Pilot Record to QOFr.
5 + Set the AUX_PILOT_WALSH_CODE field of Candidate

8 by WALSH_LENGTHr.
9 + If ADD_INFO_INCL1r is equal to ‘1’, set the

10 AUX_PILOT_QOF1 field of Candidate Frequency Neighbor
11 Set Pilot Record to QOF1r and set the
12 AUX_PILOT_WALSH_CODE1 field of Candidate Frequency
13 Neighbor Set Pilot Record to AUX_PILOT_WALSH1r with
14 the Walsh Code length specified by WALSH_LENGTH1r;
15 otherwise, set the AUX_PILOT_QOF1 field of Candidate
16 Frequency Neighbor Set Pilot Record to QOFr and set the
18 Neighbor Set Pilot Record to AUX_PILOT_WALSHr with the
19 Walsh Code length specified by WALSH_LENGTHr.
20 + If ADD_INFO_INCL2r is equal to ‘1’, set the

21 AUX_PILOT_QOF2 field of Candidate Frequency Neighbor
22 Set Pilot Record to QOF2r and set the
24 Neighbor Set Pilot Record to AUX_PILOT_WALSH2r with
25 the Walsh Code length specified by WALSH_LENGTH2r;
26 otherwise, set the AUX_PILOT_QOF2 field of Candidate
27 Frequency Neighbor Set Pilot Record to QOFr and set the
29 Neighbor Set Pilot Record to AUX_PILOT_WALSHr with the
30 Walsh Code length specified by WALSH_LENGTHr.
31 ο If PILOT_UPDATE is equal to ‘1’ and CF_SEARCH_PRIORITY_INCLs is

32 equal to ‘1’, the mobile station shall store the search priority
33 (SEARCH_PRIORITYs = SEARCH_PRIORITYr) associated with each of
34 the neighboring base stations contained in the Candidate Frequency
35 Neighbor Set.
36 ο If PILOT_UPDATE is equal to ‘1’ and CF_SRCH_WIN_NGHBR_INCLs is
37 equal to ‘1’, the mobile station shall perform the following:
38 ◊ Store the neighbor pilot channel search window size

39 (SRCH_WIN_NGHBRs = SRCH_WIN_NGHBRr) associated with
40 each of the neighboring base stations contained in the Candidate
41 Frequency Neighbor Set,
2-385
3GPP2 C.S0005-A v6.0
1 ◊ If CF_SRCH_OFFSET_INCLr equals to ‘1’, store the neighbor pilot

2 channel search window offset (SRCH_OFFSET_NGHBRs =
3 SRCH_OFFSET_NGHBRr) associated with each of the neighboring
4 base stations contained in the Candidate Frequency Neighbor Set.
5 ο If PILOT_UPDATE is equal to ‘1’, the mobile station shall replace the

6 Candidate Frequency Search Set with all flagged pilots (those with the
7 corresponding SEARCH_SET field set to ‘1’) specified in the Candidate
8 Frequency Search Request Message.
9 ο Search offset time (If ALIGN_TIMINGr is equal to ‘1’,
10 SEARCH_OFFSETs = SEARCH_OFFSETr; otherwise,
11 SEARCH_OFFSETs = ‘000000’)
12 + If ALIGN_TIMINGr is equal to ‘1’ and the mobile station will align its
13 search as requested by the base station, the mobile station shall set
14 ALIGN_TIMING_USEDs to ‘1’ and SEARCH_OFFSETs to
15 SEARCH_OFFSETr; otherwise, the mobile station shall
16 set ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs to ‘000000’.
17 + If the mobile station sets the PCG_OFF_TIMES field of the Candidate

18 Frequency Search Response Message to ‘1’, it shall set
19 SEARCH_TIME_RESOLUTIONs to 0.00125; otherwise, it shall set
20 SEARCH_TIME_RESOLUTIONs to 0.02.
21 + If SEARCH_TYPEr is equal to ‘01’, the mobile station shall perform a
22 single search of the Candidate Frequency Search Set, as described in
23 2.6.6.2.8.3.1. If SEARCH_TYPEr is equal to ‘11’, the mobile station shall
24 perform the periodic search procedures, as described in 2.6.6.2.8.3.2.
25
26 Table 2.6.6.2.5.1-1. Search Parameter Settings
NGHBR_SRCH_ SEARCH_- SRCH_WIN_-

-MODE PRIORITY_INCL NGHBR_INCL
CF_NGHBR_- CF_SEARCH_- CF_SRCH_-
SRCH_MODE PRIORITY_INCL WIN_NGHBR_INCL
00 0 0
01 1 0
10 0 1
11 1 1
27
28 If SEARCH_MODEr is equal to ‘0001’, and if the mobile station supports analog

29 searching, the mobile station shall process the Candidate Frequency Search Request
30 Message as follows:
2-386
3GPP2 C.S0005-A v6.0
3 search_period is less than (max (fwd_time, rev_time ) + T71m) seconds where
4 search_period, fwd_time and rev_time are defined below.
5 (In the following, rec_search_set is the set of analog frequencies specified in the
6 Candidate Frequency Search Request Message.)
8 Table 2.6.6.2.8.3.2-1
12 each analog frequency in rec_search_set and measure its
13 strength, and to re-tune to the Serving Frequency; if the mobile
14 station searches rec_search_set in multiple visits, fwd_time is
15 the total time for all visits away from the Serving Frequency in a
16 search period (see 2.6.6.2.10.2)
20 each analog frequency in rec_search_set and measure its
21 strength, and to re-tune to the Serving Frequency; if the mobile
22 station searches rec_search_set in multiple visits, rev_time is the
23 total time for all visits away from the Serving Frequency in a
24 search period
25 • If the mobile station does not send a Mobile Station Reject Order in response to
26 the Candidate Frequency Search Request Message, it shall perform the following:
27 − The mobile station shall send a Candidate Frequency Search Response

28 Message in assured mode, within T56m seconds of receiving the Candidate
29 Frequency Search Request Message. The mobile station shall set the fields of
30 the Candidate Frequency Search Response Message as follows:
31 + The mobile station shall set TOTAL_OFF_TIME_FWD and

32 TOTAL_OFF_TIME_REV to its estimate of the total number of frames or
33 power control groups for which it will need to suspend its current
35 processing, respectively, in order to tune to each analog frequency in
36 rec_search_set, to measure its strength, and to re-tune to the Serving
37 Frequency (see 2.6.6.2.8.3.2). If the mobile station searches
38 rec_search_set in multiple visits away from the Serving Frequency, the
39 mobile station shall report the total number of frames or power control
40 groups in all visits in a search period for which it will need to suspend its
41 current Forward Traffic Channel and the Reverse Traffic Channel
42 processing.
2-387
3GPP2 C.S0005-A v6.0
1 + The mobile station shall set MAX_OFF_TIME_FWD and

2 MAX_OFF_TIME_REV to its estimate of the maximum number of frames
3 or power control groups for which it will need to suspend its current
5 processing, respectively, during any single visit away from the Serving
6 Frequency, to search a subset of rec_search_set, and to re-tune to the
8 + The mobile station shall set PCG_OFF_TIMES to ‘1’ if

9 TOTAL_OFF_TIME_FWD, MAX_OFF_TIME_FWD, TOTAL_OFF_TIME_-
10 REVFWD and MAX_OFF_TIME_REVFWD are expressed in units of power
11 control groups. If these time estimates are expressed in units of frames,
12 the mobile station shall set PCG_OFF_TIMES to ‘0’. The mobile station
13 shall not use power control groups as the unit of delay duration if
14 P_REV_IN_USEs is less than six.
15 + If ALIGN_TIMINGr is equal to ‘1’, the mobile station shall set

16 ALIGN_TIMING_USED to ‘1’ to indicate if it will align its search as
17 requested by the base station; otherwise, the mobile station shall set
18 ALIGN_TIMING_USED to ‘0’. If ALIGN_TIMING_USED is set to ‘1’, the
19 mobile station shall set MAX_NUM_VISITS to the maximum number of
20 visits per search period minus one. and, iIf MAX_NUM_VISITS is not
21 equal to 0, the mobile station shall set INTER_VISIT_TIME, in units of
22 frames or power control groups, to its estimate of the time between
23 subsequent the beginning of consecutive visits away from the Serving
24 Frequency within the same search period.
25 − When the message takes effect, the mobile station shall perform the following
26 actions:
27 + If any periodic search is in progress, the mobile station shall abort it (see
28 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
29 + Store the following parameters from the Candidate Frequency Search
30 Request Message:
31 ο Candidate Frequency Search Request Message sequence number

32 (CFSRM_SEQs = CFSRM_SEQr)
33 ο Periodic search flag: If SEARCH_TYPEr is equal to ‘11’, the mobile

34 station shall set PERIODIC_SEARCHs to ‘1’; otherwise, the mobile
35 station shall set PERIODIC_SEARCHs to ‘0’.
36 ο Search period for the analog frequencies search

37 (SEARCH_PERIODs = SEARCH_PERIODr)
38 ο Candidate Frequency search mode

39 (SEARCH_MODEs = SEARCH_MODEr)
40 ο Band class for the analog frequencies

41 (CF_CDMABANDs = BAND_CLASSr)
2-388
3GPP2 C.S0005-A v6.0
1 ο Serving Frequency total pilot Ec threshold

2 (SF_TOTAL_EC_THRESHs = SF_TOTAL_EC_THRESHr)
3 ο Serving Frequency total pilot Ec/Io threshold

4 (SF_TOTAL_EC_IO_THRESHs = SF_TOTAL_EC_IO_THRESHr)
5 ο Candidate Frequency Analog Search Set: The mobile station shall

6 replace the Candidate Frequency Analog Search Set with the analog
7 frequencies included in the Candidate Frequency Search Request
8 Message.
9 οSearch offset time (If ALIGN_TIMINGr is equal to ‘1’, SEARCH_OFFSETs
10 = SEARCH_OFFSETr; otherwise, SEARCH_OFFSETs = ‘000000’)
11 + If ALIGN_TIMINGr is equal to ‘1’ and the mobile station will align its
12 search as requested by the base station, the mobile station shall set
13 ALIGN_TIMING_USEDs to ‘1’ and SEARCH_OFFSETs to
14 SEARCH_OFFSETr; otherwise, the mobile station shall set

15 ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs to ‘000000’.
16 + If the mobile station sets the PCG_OFF_TIMES field of the Candidate

17 Frequency Search Response Message to ‘1’, it shall set
18 SEARCH_TIME_RESOLUTIONs to 0.00125; otherwise, it shall set
19 SEARCH_TIME_RESOLUTIONs to 0.02.
20 + If SEARCH_TYPEr is equal to ‘01’, the mobile station shall perform a

21 single search of the Candidate Frequency Analog Search Set as described
22 in 2.6.6.2.10.1. If SEARCH_TYPEr is equal to ‘11’, the mobile station
23 shall perform the periodic search procedures described in 2.6.6.2.10.2.
24 6. Candidate Frequency Search Control Message: The mobile station shall process the
26 If SEARCH_MODEs is equal to ‘0000’:
28 set to ‘00001010’ (search set not specified), if SEARCH_TYPEr is not equal to ‘00’
29 and the Candidate Frequency Search Set is empty.
31 set to ‘00001011’ (invalid search request), if SEARCH_TYPEr is not equal to ‘00’
32 and the Candidate Frequency is the same as the Serving Frequency
33 (CF_CDMABANDs is equal to CDMABANDs and CF_CDMACHs is equal to
34 CDMACHs).

39 Table 2.6.6.2.8.3.2-1,
2-389
3GPP2 C.S0005-A v6.0

4 the Candidate Frequency, to search the Candidate Frequency
5 Search Set and to re-tune to the Serving Frequency; if the
6 mobile station searches the Candidate Frequency Search Set in
7 multiple visits, fwd_time is the total time for all visits to the
8 Candidate Frequency in a search period (see 2.6.6.2.8.3.2),
9 and
13 the Candidate Frequency, to search the Candidate Frequency
14 Search Set and to re-tune to the Serving Frequency; if the
15 mobile station searches the Candidate Frequency Search Set in
16 multiple visits, rev_time is the total time for all visits to the
17 Candidate Frequency in a search period.
18 • If the mobile station does not reject the Candidate Frequency Search Control
19 Message, it shall perform the following actions when the message takes effect:
20 − If any periodic search is in progress, the mobile station shall abort it (see
21 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
22 − If ALIGN_TIMINGr is equal to ‘1’ and the mobile station will align its search
23 as requested by the base station, the mobile station shall set
24 ALIGN_TIMING_USEDs to ‘1’; otherwise, the mobile station shall set
26 − If SEARCH_TYPEr is equal to ‘00’, the mobile station shall set

27 PERIODIC_SEARCHs to ‘0’.
28 − If SEARCH_TYPEr is equal to ‘01’:
29 + The mobile station shall set PERIODIC_SEARCHs to ‘0’.
30 + The mobile station shall perform a single search of the Candidate

31 Frequency Search Set, as described in 2.6.6.2.8.3.1.
34 + The mobile station shall perform the periodic search procedures for the
35 Candidate Frequency Search Set, as described in 2.6.6.2.8.3.2.
36 If SEARCH_MODEs is equal to ‘0001’:
38 set to ‘00001010’ (search set not specified), if SEARCH_TYPEr is not equal to ‘00’
39 and the Candidate Frequency Analog Search Set is empty.
2-390
3GPP2 C.S0005-A v6.0

5 Table 2.6.6.2.8.3.2-1,
9 each analog frequency in the Candidate Frequency Analog
10 Search Set and measure its strength, and to re-tune to the
11 Serving Frequency; if the mobile station searches the Candidate
12 Frequency Analog Search Set in multiple visits, fwd_time is the
14 search period (see 2.6.6.2.10.2),
15 and

19 each analog frequency in the Candidate Frequency Analog
20 Search Set and measure its strength, and to re-tune to the
21 Serving Frequency; if the mobile station searches the Candidate
22 Frequency Analog Search Set in multiple visits, fwd_time is the
24 search period (see 2.6.6.2.10.2).
25 • If the mobile station does not reject the Candidate Frequency Search Control
26 Message, it shall perform the following actions when the message takes effect:
27 − If any periodic search is in progress, the mobile station shall abort it (see
28 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
29 − If ALIGN_TIMINGr is equal to ‘1’ and the mobile station will align its search
30 as requested by the base station, the mobile station shall set
31 ALIGN_TIMING_USEDs to ‘1’; otherwise, the mobile station shall set
33 − If SEARCH_TYPEr is equal to ‘00’, the mobile station shall set

37 + The mobile station shall perform a single search of the Candidate

38 Frequency Analog Search Set, as described in 2.6.6.2.10.1.
2-391
3GPP2 C.S0005-A v6.0
1 + The mobile station shall perform the periodic search procedures for the
2 Candidate Frequency Analog Search Set, as described in 2.6.6.2.10.2.
3 7. Extended Neighbor List Update Message: The mobile station shall update its
4 neighbor set as specified in 2.6.6.2.6.3 and perform the following:
5 • If NGHBR_SRCH_MODEr is equal to ‘01’ or ‘11’, the mobile station shall store
6 the search priority (SEARCH_PRIORITYs = SEARCH_PRIORITYr) associated with
7 each of the neighboring base stations contained in the Extended Neighbor List
8 Update Message which are in the mobile’s neighbor set.
9 • If NGHBR_SRCH_MODEr is equal to ‘01’ or ‘00’, the mobile station shall set the
10 SRCH_OFFSET_INCLs field ‘0’.
11 • If NGHBR_SRCH_MODEr is equal to ‘10’ or ‘11’, the mobile station shall perform

12 the following:
13 − Store the neighbor pilot channel search window size

14 (SRCH_WIN_NGHBRs = SRCH_WIN_NGHBRr) associated with each of the
15 neighboring base stations contained in the Extended Neighbor List Updated
16 Message which are in the mobile’s neighbor set,
17 − If SRCH_OFFSET_INCLr equals to ‘1’, set the SRCH_OFFSET_NGHBR field of
18 NGHBR_REC[i] to the ith occurrence of SRCH_OFFSET_NGHBRr,
19 − Set SRCH_OFFSET_INCLs to SRCH_OFFSET_INCLr.
20 • The mobile station shall update the default search window size for its Neighbor
21 Set (SRCH_WIN_Ns = SRCH_WIN_Nr).
22 • The mobile station shall set SEARCH_PRIORITY_INCLs and

23 SRCH_WIN_NGHBR_INCLs to the value specified in Table 2.6.6.2.5.1-1
24 corresponding to NGHBR_SRCH_MODEr.
25 • If USE_TIMING is equal to ‘1’, the mobile station shall store the timing included
26 flag (TIMING_INCL) associated with each of the neighboring base stations
27 contained in the Extended Neighbor List Update Message which are in the mobile
28 station neighbor set; otherwise the mobile station shall set the timing included
29 flag (TIMING_INCL) associated with each of the neighboring base stations to ‘0’.
30 • If USE_TIMING is equal to ‘1’ and TIMING_INCLr is equal to ‘1’, the mobile
31 station shall store the neighbor transmit time offset (NGHBR_TX_OFFSET =
32 NGHBR_TX_OFFSETr) associated with each of the neighboring base stations
33 contained in the Extended Neighbor List Update Message which are in the mobile
34 station neighbor set.
35 • If USE_TIMING is equal to ‘1’ and the TIMING_INCL is equal to ‘1’, then the
2-392
3GPP2 C.S0005-A v6.0
1 − If the GLOBAL_TIMING_INCL field is equal to ‘1’, then the mobile station

2 shall store the neighbor transmit time duration (NGHBR_TX_DURATION =
3 GLOBAL_TX_DURATIONr) and the neighbor transmit time duration
4 (NGHBR_TX_PERIOD = GLOBAL_TX_PERIODr) contained in the Extended
5 Neighbor List Update Message.
6 − If the GLOBAL_TIMING_INCL field is equal to ‘0’, then the mobile station

7 shall store the neighbor transmit time duration (NGHBR_TX_DURATION =
8 NGHBR_TX_DURATIONr) and the neighbor transmit time duration
9 (NGHBR_TX_PERIOD = NGHBR_TX_PERIODr) associated with each of the
10 neighboring base stations contained in the Extended Neighbor List Update
11 Message which are in the mobile station neighbor set.
12 • For each of the neighboring base stations contained in the General Neighbor List
13 Message, the mobile station shall set ADD_PILOT_REC_INCL field of
14 NGHBR_REC[i] to the ith occurrence of ADD_PILOT_REC_INCLr. If
15 ADD_PILOT_REC_INCLr equals ‘1’, for each pilot, the mobile station shall also
17 − Set the NGHBR_PILOT_REC_TYPE field of NGHBR_PILOT_REC to

19 − If NGHBR_PILOT_REC_TYPEr is equal to ‘000’. The mobile station shall set

20 the TD_POWER_LEVEL field of NGHBR_PILOT_REC to TD_POWER_LEVELr
21 and set the TD_MODE field of NGHBR_PILOT_REC to TD_MODEr.
22 − If NGHBR_PILOT_REC_TYPEr is equal to ‘001’, the mobile station shall:
23 + Set the AUX_PILOT_QOF field of NGHBR_PILOT_REC to QOFr

26 WALSH_LENGTHr
27 − If NGHBR_PILOT_REC_TYPEr is equal to ‘010’, the mobile station shall:
28 + Set the AUX_PILOT_TD_QOF field of NGHBR_PILOT_REC to QOFr.

31 WALSH_LENGTHr.
32 + Set the AUX_TD_POWER_LEVEL field of NGHBR_PILOT_REC to




2-393
3GPP2 C.S0005-A v6.0





13 WALSH_LENGTHr.

15 NGHBR_PILOT_REC to QOF1r and set the AUX_PILOT_WALSH_CODE1
16 field of NGHBR_PILOT_REC to AUX_PILOT_WALSH1r with the Walsh
17 Code length specified by WALSH_LENGTH1r; otherwise, set the
18 AUX_PILOT_QOF1 field of NGHBR_PILOT_REC to QOFr and set the
19 AUX_PILOT_WALSH_CODE1 field of NGHBR_PILOT_REC to
21 WALSH_LENGTHr.

23 NGHBR_PILOT_REC to QOF2r and set the AUX_PILOT_WALSH_CODE2
24 field of NGHBR_PILOT_REC to AUX_PILOT_WALSH2r with the Walsh
25 Code length specified by WALSH_LENGTH2r; otherwise, set the
26 AUX_PILOT_QOF2 field of NGHBR_PILOT_REC to QOFr and set the
27 AUX_PILOT_WALSH_CODE2 field of NGHBR_PILOT_REC to
29 WALSH_LENGTHr.
30 8. Supplemental Channel Assignment Message: The mobile station shall process this
33 to the specified value if any of the following conditions is true, and shall not perform
34 any other action described in this section for processing the Supplemental Channel
35 Assignment Message:
37 set to ‘00000110’ (capability not supported), if the number of forward or reverse
38 Supplemental Code Channels specified in the Supplemental Channel Assignment
39 Message is greater than the maximum number of Supplemental Code Channels
40 supported by the mobile station.
2-394
3GPP2 C.S0005-A v6.0
2 set to ‘00000011’ (message structure not acceptable), if both
3 USE_REV_HDM_SEQ and EXPL_REV_START_TIME or both
4 USE_FOR_HDM_SEQ and EXPL_FOR_START_TIME specified in the
5 Supplemental Channel Assignment Message are set to ‘1’.
7 set to ‘00000100’ (message field not in valid range), if PILOT_PN specified in the
8 Supplemental Channel Assignment Message is not in the Active Set and this
9 message is not linked with a General Handoff Direction Message.
10 If none of the above conditions is true, the mobile station shall perform the
11 following.
12 • The mobile station shall store the following parameters from the Supplemental
13 Channel Assignment Message:
14 − Use General Handoff Direction Message forward sequence number indicator

15 (USE_FOR_HDM_SEQs = USE_FOR_HDM_SEQr)
16 − If USE_FOR_HDM_SEQr is equal to ‘1’, then the mobile station shall store

17 the following:
18 + The sequence number of the General Handoff Direction Message to which
19 this messaged is linked for the Forward Supplemental Code Channel
20 assignment (FOR_LINKED_HDM_SEQs = FOR_LINKED_HDM_SEQr)
21 + The forward Supplemental Code Channel assignment order

22 (SCAM_FOR_ORDERs = least significant bit of FOR_SUP_CONFIGr)
23 + The forward duration assignment indicator

24 (SCAM_FOR_DURATION_MODEs = USE_FOR_DURATIONr).
25 − Use General Handoff Direction Message reverse sequence number indicator

26 (USE_REV_HDM_SEQs = USE_REV_HDM_SEQr)
27 − If USE_REV_HDM_SEQr is equal to ‘1’, then the mobile station shall store

28 the following:
29 + The sequence number of the General Handoff Direction Message to which
30 this messaged is linked for the Reverse Supplemental Code Channel
31 assignment (REV_LINKED_HDM_SEQs = REV_LINKED_HDM_SEQr)
32 + The reverse duration assignment indicator

33 (SCAM_REV_DURATION_MODEs = USE_REV_DURATIONr).
34 • If USE_RETRY_DELAYr is ‘0’, then the mobile station shall store 0 as

35 RETRY_DELAYs. The mobile station may send subsequent Supplemental
36 Channel Request Messages whenever RETRY_DELAYs is set to 0.
37 • If USE_RETRY_DELAYr is set to ‘1’, the mobile station shall interpret the

38 Supplemental Channel Assignment Message as an indication that the base
39 station has specified a Supplemental Channel Request Message retry delay in
40 RETRY_DELAYr as follows:
2-395
3GPP2 C.S0005-A v6.0
1 − The mobile station shall store the next system time 80 ms boundary +
2 RETRY_DELAYr × 320 ms as RETRY_DELAYs. The mobile station shall not
3 send any subsequent Supplemental Channel Request Message until after the
4 system time stored in RETRY_DELAYs. At the system time stored in
5 RETRY_DELAYs, the mobile station shall reset RETRY_DELAYs to 0.
6 − If RETRY_DELAYr is ‘00000000’, then the mobile station shall store 0 as

7 RETRY_DELAYs. The mobile station may send subsequent Supplemental
8 Channel Request Messages whenever RETRY_DELAYs is set to 0.
9 − If RETRY_DELAYr is ‘11111111’, then the mobile station shall store infinity

10 as RETRY_DELAYs, and the mobile station shall not send any further
11 Supplemental Channel Request Messages until the mobile station receives a
12 new Supplemental Channel Assignment Message with no retry delay or a non-
13 infinite retry delay specified, or until the mobile station receives a General
14 Handoff Direction Message with a CLEAR_RETRY_DELAY indication set.
15 • If REV_INCLUDEDr is equal to ‘1’, then the mobile station shall process Reverse
16 Supplemental Code Channel assignment information for the Supplemental
17 Channel Assignment Message. This information shall be processed as follows:
18 − The mobile station shall store USE_T_ADD_ABORTr, the Reverse
19 Supplemental Code Channel assignment T_ADD abort indicator, as
20 USE_T_ADD_ABORTs.
21 – The mobile station shall store REV_DTX_DURATIONr, Reverse Supplemental

22 Channel Discontinuous Transmission Duration, as REV_DTX_DURATIONs.
23 − If REV_PARMS_INCLUDEDr is equal to ‘1’, the mobile station shall store the

24 following:
25 + T_MULCHANs = T_MULCHANr
26 + BEGIN_PREAMBLEs = BEGIN_PREAMBLEr
27 + RESUME_PREAMBLEs = RESUME_PREAMBLEr
28 − If IGNORE_SCAMs is equal to ‘1’ and SCRM_SEQ_NUMr is not present or is

29 present and is not equal to SCRM_SEQ_NUMs, then the mobile station shall
30 not process the remaining Reverse Supplemental Code Channel assignment
31 information in this message.
32 − If IGNORE_SCAMs is equal to ‘1’ and SCRM_SEQ_NUMr is present and is
33 equal to SCRM_SEQ_NUMs, then the mobile station shall set
34 IGNORE_SCAMs to ‘0’.
35 − The mobile station shall set REV_START_TIMEs as follows:
36 + If EXPL_REV_START_TIMEr is equal to ‘1’, the mobile station shall set

37 the REV_START_TIMEs to REV_START_TIMEr.
38 + If USE_REV_HDM_SEQr is equal to ‘1’ and REV_LINKED_HDM_SEQr is

39 not equal to HDM_SEQs, the mobile station shall set the
40 REV_START_TIMEs to NULL.
2-396
3GPP2 C.S0005-A v6.0
1 + If USE_REV_HDM_SEQr is equal to ‘1’ and REV_LINKED_HDM_SEQr is

2 equal to HDM_SEQs, then the mobile station shall set the
3 REV_START_TIMEs to the action time of the General Handoff Direction
4 Message that is linked to the Supplemental Channel Assignment Message.
5 + If EXPL_REV_START_TIMEr is equal to ‘0’ and USE_REV_HDM_SEQr is
6 equal to ‘0’, the mobile station shall set the REV_START_TIMEs to the
7 next 80 ms boundary following the action time of the Supplemental
9 – The mobile station shall set NUM_REV_CODESs to NUM_REV_CODESr. If
10 REV_START_TIMEs is not equal to NULL, the mobile station shall perform the
12 + If NUM_REV_CODESr is equal to ‘000’, the mobile station shall stop
13 transmitting the Reverse Supplemental Code Channels at the start time
14 specified by REV_START_TIMEs.
15 + If NUM_REV_CODESr is not equal to ‘000’, the mobile station shall set

16 PILOT_GATING_USE_RATE to ‘0’ at the action time of the message and
17 the mobile station may start transmitting on NUM_REV_CODESs Reverse
18 Supplemental Code Channels at the start time specified by
19 REV_START_TIMEs for a duration of time specified by the following rules:
20 ο If USE_REV_DURATIONr is equal to ‘1’, the mobile station shall set

21 REV_DURATIONs to REV_DURATIONr. The mobile station may
22 continue transmitting on the Reverse Supplemental Code Channels
23 for a period of (REV_DURATIONs × 80) ms, or until it receives the
24 action time of a subsequent General Handoff Direction Message or a
25 Supplemental Channel Assignment Message that specifies a different
26 Reverse Supplemental assignment duration or start time.
27 ο If USE_REV_DURATIONr is equal to ‘0’, the mobile station may
28 continue to transmit indefinitely on the Reverse Supplemental Code
29 Channels, or until it receives the action time of a subsequent General
30 Handoff Direction Message or a Supplemental Channel Assignment
31 Message that specifies a different Reverse Supplemental assignment
32 duration or start time.
33 • If FOR_INCLUDED is equal to ‘1’, then the mobile station shall process Forward
34 Supplemental Code Channel assignment information as follows:
35 − The mobile station shall assign a value to FOR_START_TIMEs according to
36 the following rules:
37 + If EXPL_FOR_START_TIME is equal to ‘1’, the mobile station shall set the

38 FOR_START_TIMEs to FOR_START_TIMEr.
39 + If USE_FOR_HDM_SEQr is equal to ‘1’ and FOR_LINKED_HDM_SEQr is

40 not equal to HDM_SEQs, the mobile station shall set the
41 FOR_START_TIMEs to NULL.
2-397
3GPP2 C.S0005-A v6.0
1 + If USE_FOR_HDM_SEQr is equal to ‘1’ and FOR_LINKED_HDM_SEQr is

2 equal to HDM_SEQs, then the mobile station shall set the
3 FOR_START_TIMEs to the action time of the General Handoff Direction
4 Message that is linked to the Supplemental Channel Assignment Message.
5 + If EXPL_FOR_START_TIMEr is equal to ‘0’ and USE_FOR_HDM_SEQr
6 equals ‘0’, the mobile station shall set the FOR_START_TIMEs to the
7 action time of the Supplemental Channel Assignment Message.
8 − If FOR_SUP_CONFIGr is equal to ‘00’ and FOR_START_TIMEs is not equal to
9 NULL, the mobile station should stop processing the Forward Supplemental
10 Code Channels at the time specified by FOR_START_TIMEs.
11 − If FOR_SUP_CONFIGr is equal to ‘01’ and FOR_START_TIMEs is not equal to

12 NULL, the mobile station shall set PILOT_GATING_USE_RATE to ‘0’ at the
13 action time of the message and start processing the Forward Supplemental
14 Code Channels in the CODE_CHAN_LISTs at FOR_START_TIMEs for a period
15 of time specified by the following rules:
16 + If USE_FOR_DURATION is equal to ‘1’, the mobile station shall set

17 FOR_DURATIONs to FOR_DURATIONr. The mobile station shall continue
18 processing the Forward Supplemental Code Channels for a period of
19 (FOR_DURATIONs × 80) ms, or until it receives the action time of a
20 subsequent Supplemental Channel Assignment Message or a General
21 Handoff Direction Message that specifies a different Forward
22 Supplemental assignment duration or start time.
23 + If USE_FOR_DURATIONr is equal to ‘0’, the mobile station shall continue
24 processing the Forward Supplemental Code Channels until it receives the
25 action time of a subsequent Supplemental Channel Assignment Message
26 or a General Handoff Direction Message that specifies a different Forward
27 Supplemental assignment duration or start time.
28 − If FOR_SUP_CONFIGr is equal to ‘10’, the mobile station shall perform the
29 following:
30 + The mobile station shall update the CODE_CHAN_LISTs as specified in
31 2.6.8.
32 + If FOR_START_TIMEs is not equal to NULL the mobile station should stop
33 processing Forward Supplemental Code Channels at the time specified by
34 FOR_START_TIMEs.
35 − If FOR_SUP_CONFIGr is equal to ‘11’, the mobile station shall perform the

36 following:
37 + The mobile station shall update the CODE_CHAN_LISTs as specified in
38 2.6.8.
2-398
3GPP2 C.S0005-A v6.0
1 + If FOR_START_TIMEs is not equal to NULL, then the mobile station shall

2 set PILOT_GATING_USE_RATE to ‘0’ at the action time of the message
3 and start processing the Forward Supplemental Code Channels in the
4 CODE_CHAN_LISTs at the time specified by FOR_START_TIMEs for a
5 period of time specified by the following rules:
6 ο If USE_FOR_DURATIONr is equal to ‘1’, the mobile station shall set
7 FOR_DURATIONs to FOR_DURATIONr. The mobile station shall
8 continue processing the Forward Supplemental Code Channels for
9 (FOR_DURATIONs × 80) ms, until it receives a subsequent
10 Supplemental Channel Assignment Message or a General Handoff
11 Direction Message that specifies a different Forward Supplemental
12 assignment duration or start time.
13 ο If USE_FOR_DURATIONr is equal to ‘0’, the mobile station shall
14 continue processing the Forward Supplemental Code Channels until
15 it receives a subsequent Supplemental Channel Assignment Message
16 or a General Handoff Direction Message that specifies a different
17 Forward Supplemental assignment duration or start time.
18 9. General Handoff Direction Message: The mobile station shall process the message as
19 follows:
20 In addition to the requirements in this section, if the SCR_INCLUDED field is

21 included in this message and is set to ‘1’ the mobile station shall also process this
22 message in accordance with the requirements for the active service subfunction (see
23 2.6.4.1.2.2).
26 any other action described in this section for processing the General Handoff
27 Direction Message:
29 set to ‘00000110’ (capability not supported), if the mobile station does not
30 support the band class specified in the General Handoff Direction Message.
32 set to ‘00000110’ (capability not supported), if the number of forward or reverse
33 Supplemental Code Channels specified in the General Handoff Direction Message
34 is greater than the maximum number of Supplemental Code Channels
36 • If the SCR_INCLUDED field is included in this message and is set to ‘1’, the
38 - The mobile station shall send a Mobile Station Reject Order with the ORDQ
39 field set to ‘00000111’ (message cannot be handled by the current mobile
40 station configuration), if the mobile station does not support the service
41 configuration specified in the General Handoff Direction Message.
2-399
3GPP2 C.S0005-A v6.0
1 - The mobile station shall send a Mobile Station Reject Order (ORDQ =
2 ‘00000111’) within T56m seconds, if the mobile station supports the service
3 configuration specified but does not accept the service configuration specified
4 in the General Handoff Direction Message.
6 set to ‘00000111’ (message cannot be handled by the current mobile station
7 configuration), if the NNSCR_INCLUDED field is included and set to ‘1’ and the
8 SCR_INCLUDED field is either not included or included but set to ‘0’, and the
9 mobile station does not support the configuration specified in the non-negotiable
10 service configuration information record in the General Handoff Direction
11 Message.
13 set to ‘00001010’ (search set not specified), if the PERIODIC_SEARCH field is
14 included in the General Handoff Direction Message and is set to ‘1’, and the
15 Candidate Frequency Search Set is empty.
17 set to ‘00001101’ (search period too short), if the PERIODIC_SEARCH field is
18 included in the General Handoff Direction Message and is set to ‘1’, and
19 search_period is less than (max (fwd_time, rev_time) + T71m seconds), where
20 search_period = time period corresponding to SEARCH_PERIODs shown in

21 Table 2.6.6.2.8.3.2-1,
22 fwd_time = the mobile station’s estimate of the total length of time, in seconds,
23 for which the mobile station will need to suspend its current
24 Forward Traffic Channel processing in order to tune to the CDMA
25 Candidate Frequency, to search the Candidate Frequency Search
26 Set, and to re-tune to the Serving Frequency; if the mobile station
27 searches the Candidate Frequency Search Set in multiple visits,
28 fwd_time is the total time for all visits to the CDMA Candidate
29 Frequency in a search period (see 2.6.6.2.8.3.2),
30 and
31 rev_time = the mobile station’s estimate of the total length of time, in seconds,
32 for which the mobile station will need to suspend its current Reverse
33 Traffic Channel processing in order to tune to the CDMA Candidate
34 Frequency, to search the Candidate Frequency Search Set, and to
35 re-tune to the Serving Frequency; if the mobile station searches the
36 Candidate Frequency Search Set in multiple visits, rev_time is the
37 total time for all visits to the CDMA Candidate Frequency in a search
38 period.
40 described in the remainder of this section to process the General Handoff Direction
41 Message at the action time of the message.
2-400
3GPP2 C.S0005-A v6.0
1 If EXTRA_PARMS is equal to ‘1’, the mobile station shall store the return on failure
2 indicator from the General Handoff Direction Message (RETURN_IF_HANDOFF_FAILs
3 = RETURN_IF_HANDOFF_FAILr); otherwise the mobile station shall set
4 RETURN_IF_HANDOFF_FAILs to ‘0’.
5 The mobile station shall set RETURN_IF_HANDOFF_FAILs to ‘0’ (disable return on

6 failure) if any of the following conditions is true:
7 • If P_REV_IN_USEs is less than or equal to four and the mobile station does not
8 support hard handoff with return on failure, or
9 • At least one of the pilots specified by the message is also included in the Active
10 Set prior to the action time of the message, and one of the following conditions is
11 true:
12 − EXTRA_PARMS is equal to ‘0’, or
13 − EXTRA_PARMS is equal to ‘1’, the message specifies the same Frequency

14 Assignment as the Serving Frequency (BAND_CLASSr is equal to
15 CDMABANDs and CDMA_FREQr is equal to CDMACHs), and
16 FRAME_OFFSETr is equal to FRAME_OFFSETs.
17 The mobile station shall store the following parameters from its current
18 configuration:
19 • CDMA band class (SF_CDMABANDs = CDMABANDs)
20 • Frequency assignment (SF_CDMACHs = CDMACHs)
21 • Frame Offset (SF_FRAME_OFFSETs = FRAME_OFFSETs)
22 If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, the mobile station shall also store the
23 following parameters from its current configuration:
24 • Protocol revision level

25 (SF_P_REVs = P_REVs)
26 • Protocol revision level in use on the Serving Frequency

27 (SF_P_REV_IN_USEs = P_REV_IN_USEs)
29 (SF_SRCH_WIN_As = SRCH_WIN_As)
30 • Search window size for the Neighbor Set

31 (SF_SRCH_WIN_Ns = SRCH_WIN_Ns)
32 • Search window size for the Remainder Set

33 (SF_SRCH_WIN_Rs = SRCH_WIN_Rs)
34 • Pilot detection threshold

35 (SF_T_ADDs = T_ADDs)
36 • Pilot drop threshold

37 (SF_T_DROPs = T_DROPs)
2-401
3GPP2 C.S0005-A v6.0
1 • Active Set versus Candidate Set comparison threshold

2 (SF_T_COMPs = T_COMPs)
3 • Drop timer value

4 (SF_T_TDROPs = T_TDROPs)
5 • Soft slope for the dynamic add and drop thresholds

6 (SF_SOFT_SLOPEs = SOFT_SLOPEs)
7 • Intercept for the dynamic add threshold

8 (SF_ADD_INTERCEPTs = ADD_INTERCEPTs)
9 • Intercept for the dynamic drop threshold

10 (SF_DROP_INTERCEPTs = DROP_INTERCEPTs)
11 • Private long code mask indicator: If the mobile station is using the private long
12 code mask on the Serving Frequency, it shall set SF_PRIVATE_LCMs to ‘1’;
13 otherwise, it shall set SF_PRIVATE_LCMs to ‘0’.
14 • Service negotiation type

15 (SF_SERV_NEGs = SERV_NEGs)
16 • Service configuration:
17 Store the current service configuration (service configuration record and non-
18 negotiable service configuration record) in SF_SERVICE_CONFIGs
19 • Call Information:
20 Store the list of current calls (Call Control instances, etc.) in SF_CALLSs
21 • Message encryption mode: If message encryption is on, the mobile station shall
22 set SF_ENCRYPT_MODEs to ‘1’; otherwise, the mobile station shall set
23 SF_ENCRYPT_MODEs to ‘0’.
24 • Extended nominal power setting of the current cell

25 (SF_NOM_PWR_EXTs = NOM_PWR_EXTs)
26 • Nominal power setting of the current cell

27 (SF_NOM_PWRs = NOM_PWRs)
28 • Power control step

29 (SF_PWR_CNTL_STEPs = PWR_CNTL_STEPs)
30 • Serving Frequency Active Set (SF Active Set = For each pilot in the current
31 Active Set: (PILOT_PN, PWR_COMB_IND) )
32 • Serving Frequency Code Channel List

33 (SF_CODE_CHAN_LISTs = CODE_CHAN_LISTs)
34 When the message takes effect, the mobile station shall perform the following
35 actions:

2-402
3GPP2 C.S0005-A v6.0
2 General Handoff Direction Message processing (see 2.6.6.2.6.1, 2.6.6.2.6.2, and
3 2.6.6.2.6.3).
4 • The mobile station shall delete all pilots that are not listed in the Active Set of
5 the Fundamental Channel from the Active Set of the Supplemental Channel for
6 the Forward Supplemental Channel Assignment (if any). If these deleted pilots
7 include all pilots in the Active Set of the Supplemental Channel, the mobile
8 station shall cancel the Forward Supplemental Channel Assignment.
9 • Discontinue use of all Forward Traffic Channels associated with pilots not listed
10 in the General Handoff Direction Message.
11 • If EXTRA_PARMS is equal to ‘1’, perform the following actions:

12 − If FRAME_OFFSETr is not equal to FRAME_OFFSETs, change the frame
15 − If RESET_L2r is equal to ‘1’, and RETURN_IF_HANDOFF_FAILs is equal to ‘0’,
16 Layer 3 shall send a L2-Supervision.Request primitive to Layer 2 to reset the
17 acknowledgment procedures, as specified in 2.2.1.1 and 2.2.2.1 of [4]. The
18 mobile station shall reset the acknowledgment procedures immediately after
19 the action time of the General Handoff Direction Message.
20 − If RESET_FPCr is equal to ‘1’ and RETURN_IF_HANDOFF_FAILs is equal to
21 ‘0’, initialize the Forward Traffic Channel power control counters, as specified
22 in 2.6.4.1.1.1.
23 − If SERV_NEG_TYPEr is equal to ‘1’, set SERV_NEGs to enabled; otherwise set
24 SERV_NEGs to disabled.
25 − Use the long code mask specified by the PRIVATE_LCMr (see 2.3.12.3) and
27 − Process the ENCRYPT_MODE field, as specified in 2.3.12.2.

28 − If D_SIG_ENCRYPT_MODEr is included and is not set to ‘000’, the mobile
29 station shall set D_SIG_ENCRYPT_MODEs to D_SIG_ENCRYPT_MODEr and
30 set ENC_KEYs to the most recently generated CMEAKEY in the mobile
31 station.
32 − If D_SIG_ENCRYPT_MODEr is included, the mobile station shall perform the
33 following:
34 + If D_SIG_ENCRYPT_MODEr is equal to ‘000’, the mobile station shall set
35 D_SIG_ENCRYPT_MODEs to C_SIG_ENCRYPT_MODEs; otherwise, the
36 mobile station shall set D_SIG_ENCRYPT_MODEs to
37 D_SIG_ENCRYPT_MODEr and set KEYs to the most recently generated
38 CMEAKEY in the mobile station.
39 – If D_SIG_ENCRYPT_MODEr is included, the mobile station shall set
40 D_SIG_ENCRYPT_MODEs to D_SIG_ENCRYPT_MODEr.
2-403
3GPP2 C.S0005-A v6.0
1 − If ENC_KEY_SIZEr is included, the mobile station shall set ENC_KEY_SIZEs

2 to ENC_KEY_SIZEr.
3 • If EXTRA_PARMS is equal to ‘0’, set the following variables to the values

4 indicated:
5 − Hard handoff traffic channel preamble count required before transmitting a

6 Handoff Completion Message or an Extended Handoff Completion Message
7 (NUM_PREAMBLEs = ‘000’)
8 – Complete search flag (COMPLETE_SEARCHs = ‘1’)
9 − CDMA band class for the Target Frequency

10 (TF_CDMABANDs = SF_CDMABANDs)
11 − Frequency assignment for the Target Frequency

12 (TF_CDMACHs = SF_CDMACHs)
13 • Store the following parameters from the General Handoff Direction Message:
14 − General Handoff Direction Message sequence number

15 (HDM_SEQs = HDM_SEQr)
16 − Forward power control subchannel relative gain (FPC_SUBCHAN_GAINs =

17 FPC_SUBCHAN_GAINr).
18 − If the mobile station uses FPC_SUBCHAN_GAINs, the mobile station shall

20 + If PC_ACTION_TIMEr is received, the mobile station shall apply its usage
21 of the FPC_SUBCHAN_GAINs at the time specified by PC_ACTION_TIMEr.
22 + If PC_ACTION_TIME is not received and the explicit action time is

23 received, the mobile station shall apply its usage of the
24 FPC_SUBCHAN_GAINs at the action time.
25 + If neither PC_ACTION_TIMEr nor explicit action time is received, the

26 mobile station shall apply its usage of the FPC_SUBCHAN_GAINs at the
27 first 80ms boundary occurring at least 80ms after the end of the frame
28 containing the last bit of the General Handoff Direction Message sent to
29 the mobile station.
30 − Reverse Eighth Gating Mode (REV_FCH_GATING_MODEs =
31 REV_FCH_GATING_MODEr).
32 − Reverse Power Control Delay if REV_PWR_CNTL_DELAY_INCLr is equal to ‘1’

33 (REV_PWR_CNTL_DELAYs = REV_PWR_CNTL_DELAYr).
34 − If SEARCH_INCLUDED is equal to ‘1’, store the following:
37 + Pilot detection threshold

38 (T_ADDs = T_ADDr)
2-404
3GPP2 C.S0005-A v6.0
1 + Pilot drop threshold

2 (T_DROPs = T_DROPr)

5 + Drop timer value

6 (T_TDROPs = T_TDROPr)
7 + Soft slope for the dynamic add and drop thresholds

8 (SOFT_SLOPEs = SOFT_SLOPEr)
9 + Intercept for the dynamic add threshold

10 (ADD_INTERCEPTs = ADD_INTERCEPTr)
11 + Intercept for the dynamic drop threshold

12 (DROP_INTERCEPTs = DROP_INTERCEPTr)
13 − If EXTRA_PARMS is equal to ‘1’, store the following:

14 + Protocol revision level (P_REVs = P_REVr), and protocol revision level
15 currently in use (P_REV_IN_USEs = min (P_REVs, MOB_P_REVp of the
16 current band class) )
17 + If the mobile station supports packet data service options, the packet
18 data services zone identifier (PACKET_ZONE_IDs = PACKET_ZONE_IDr)
20 + Acknowledgment procedures reset indicator

21 (If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, set TF_RESET_L2s to
22 RESET_L2r)
23 + Indicator to initialize the Forward Traffic Channel power control counters

24 (If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, set TF_RESET_FPCs to
25 RESET_FPCr)
27 + Extended nominal power setting of the target cell (If CDMABANDs =

28 ‘00000’ or CDMABANDs = ‘00011’, then NOM_PWR_EXTs = ‘0’; otherwise,
29 NOM_PWR_EXTs = NOM_PWR_EXTr)
30 + Hard handoff traffic channel preamble count required before transmitting

31 a Handoff Completion Message or an Extended Handoff Completion
32 Message (NUM_PREAMBLEs = NUM_PREAMBLEr )
33 + CDMA band class for the Target Frequency

34 (TF_CDMABANDs = BAND_CLASSr and CDMABANDs = BAND_CLASSr)
35 + Frequency assignment for the Target Frequency

36 (TF_CDMACHs = CDMA_FREQr and CDMACHs = CDMA_FREQr)
37 + Complete search flag (COMPLETE_SEARCHs = COMPLETE_SEARCHr)
38 + Periodic search flag (PERIODIC_SEARCHs = PERIODIC_SEARCHr)
2-405
3GPP2 C.S0005-A v6.0
1 + Nominal code channel output power offset relative to the Reverse Pilot
2 Channel power (RLGAIN_TRAFFIC_PILOTs = RLGAIN_TRAFFIC_PILOTr)
3 – If EXTRA_PARMS is equal to ‘1’ and DEFAULT_RLAG is equal to ‘1’, the

4 mobile station shall set each entry of the Reverse Link Attribute Adjustment
5 Gain Table and Reverse Channel Adjustment Gain Table (see 2.1.2.3.3 of [2])
6 to 0.
7 − If REV_PARMS_INCLUDED is included and is equal to '1', the mobile station

9 + Reverse Supplemental Code Channel Request Message neighbor
10 Neighbor pilot strength measurement threshold offset channel pilot
11 strength offset (T_MULCHANs = T_MULCHANr)
12 + Reverse Supplemental Code Channel beginning of transmission preamble

13 length (BEGIN_PREAMBLEs = BEGIN_PREAMBLEr)
14 + Reverse Supplemental Code Channel resumption of transmission

15 preamble length (RESUME_PREAMBLEs = RESUME_PREAMBLEr)
16 − For each pilot included in the message, the mobile station shall store the
17 following:
18 + PILOT_PN, the pilot PN sequence offset index
19 + PWR_COMB_IND, the power control symbol combining indicator

20 − If USE_PWR_CNTL_STEP is equal to ‘1’ and PWR_CNTL_STEPr corresponds
21 to a power control step size supported by the mobile station (see 2.1.2.3.2 of
22 [2]), then the mobile station shall set PWR_CNTL_STEPs to
23 PWR_CNTL_STEPr.
24 • Set the pilot detection threshold for the Target Frequency and the Candidate
25 Frequency:
26 − Set TF_T_ADDs to T_ADDs.
27 − If the Target Frequency is the same as the Candidate Frequency

28 (TF_CDMABANDs is equal to CF_CDMABANDs and TF_CDMACHs is equal to
29 CF_CDMACHs), set CF_T_ADDs to T_ADDs.
30 • If FOR_INCLUDED is included and is equal to ‘0’, the mobile station shall

32 − The mobile station shall update the Code Channel List, CODE_CHAN_LISTs,
33 as specified in 2.6.8.
34 − If USE_FOR_HDM_SEQs is equal to ‘1’ and FOR_LINKED_HDM_SEQs is
35 equal to HDM_SEQr (this indicates that there is pending Forward
36 Supplemental Code Channel assignment information, received in a
37 Supplemental Channel Assignment Message, linked to this General Handoff
38 Direction Message), then the mobile station shall perform the following
39 actions:
2-406
3GPP2 C.S0005-A v6.0
1 + The mobile station shall set USE_FOR_HDM_SEQs to ‘0’.
2 + If SCAM_FOR_ORDERs is equal to ‘0’, the mobile station shall stop

3 processing all Forward Supplemental Code Channels at the action time of
4 the General Handoff Direction Message.
5 + If SCAM_FOR_ORDERs is equal to ‘1’, the mobile station shall start
6 processing the Forward Supplemental Code Channels specified in
7 CODE_CHAN_LISTs at the action time of the General Handoff Direction
8 Message, for a period of time determined by the following rules:
9 ο If SCAM_FOR_DURATION_MODEs is equal to ‘1’, the mobile station
10 shall continue processing the Forward Supplemental Code Channels
11 for a period of (FOR_DURATIONs × 80) ms, until it receives a
12 subsequent General Handoff Direction Message or a Supplemental
13 Channel Assignment Message that specifies a different Forward
14 Supplemental Code Channel assignment.
15 ο If SCAM_FOR_DURATION_MODEs is equal to ‘0’, the mobile station
16 shall continue processing the Forward Supplemental Code Channels
17 until it receives a subsequent Supplemental Channel Assignment
18 Message or a General Handoff Direction Message that specifies a
19 different Forward Supplemental Code Channel assignment.
20 − If USE_FOR_HDM_SEQs is equal to ‘0’ or FOR_LINKED_HDM_SEQs is not
21 equal to HDM_SEQr, and if the mobile station is currently processing
22 Forward Supplemental Code Channels, it shall continue processing the
23 Forward Supplemental Code Channels using the updated Code Channel List,
24 CODE_CHAN_LISTs.
25 • If NNSCR_INCLUDED field is included and set to ‘1’ and SCR_INCLUDED field is

26 either not included or included but set to ‘0’, the mobile station shall process the
27 received Non-negotiable Service Configuration Record as specified in 2.6.4.1.13
28 at the action time of this message and the mobile station shall store (if included)
29 the synchronization identifier received from the base station corresponding to
30 this service configuration (SYNC_IDs = SYNC_IDr).
31 • If FOR_INCLUDED is included and is equal to ‘1’, then the mobile station shall
32 process the Forward Supplemental Code Channel assignment information as
33 follows:
34 − The mobile station shall set USE_FOR_HDM_SEQs to ‘0’.
35 − If FOR_START_TIMEs specifies a time which is after the action time of the

36 General Handoff Direction Message, the mobile station shall cancel any
37 pending Forward Supplemental Code Channel assignment and shall set
38 FOR_START_TIMEs to NULL.
39 − The mobile station shall update the Code Channel List, CODE_CHAN_LISTs,
40 in accordance with the value of FOR_SUP_CONFIG, as specified in 2.6.8.
2-407
3GPP2 C.S0005-A v6.0
1 − If FOR_SUP_CONFIG is equal to ‘00’ or ‘10’, the mobile station should stop

2 processing Forward Supplemental Code Channels, if any, when the message
3 takes effect.
4 − If FOR_SUP_CONFIG is equal to ‘01’ or ‘11’, the mobile station shall set

5 PILOT_GATING_USE_RATE to ‘0’ at the action time of the message and start
6 processing the Forward Supplemental Code Channels in the updated Code
7 Channel List, CODE_CHAN_LISTs, at the action time of the message, for a
8 period of time determined by the following rules:
9 + If USE_FOR_DURATION is equal to ‘1’, the mobile station shall set

10 FOR_DURATIONs to FOR_DURATIONr. The mobile station shall continue
11 processing the Forward Supplemental Code Channels for a period of
12 (FOR_DURATIONs × 80) ms, until it receives a subsequent Supplemental
13 Channel Assignment Message or a General Handoff Direction Message
14 that specifies a different Forward Supplemental Code Channel
15 assignment.
16 + If USE_FOR_DURATION is equal to ‘0’, the mobile station shall continue
17 processing the Forward Supplemental Code Channels until it receives a
18 subsequent Supplemental Channel Assignment Message or a General
19 Handoff Direction Message that specifies a different Forward
21 • If REV_INCLUDED is included and is equal to ‘0’, the mobile station shall

23 − If USE_REV_HDM_SEQs is equal to ‘1’ and REV_LINKED_HDM_SEQs is
24 equal to HDM_SEQr (this indicates that there is pending Reverse
25 Supplemental Code Channel assignment information, received in a
26 Supplemental Channel Assignment Message, linked to this General Handoff
27 Direction Message), the mobile station shall perform the following actions:
28 + If NUM_REV_CODESs is equal to ‘000’, the mobile station shall stop
29 transmitting on all Reverse Supplemental Code Channels at the action
30 time of the message.
31 + If NUM_REV_CODESs is not equal to ‘000’, the mobile station may start

32 transmitting on NUM_REV_CODESs Reverse Supplemental Code
33 Channels at the action time of the message, for a duration of time
34 determined by the following rules:
35 ο If SCAM_REV_DURATION_MODEs is equal to ‘1’, the mobile station
36 may continue transmitting on the Reverse Supplemental Code
37 Channels for a period of (REV_DURATIONs × 80) ms, until it receives
38 a subsequent General Handoff Direction Message or a Supplemental
39 Channel Assignment Message that specifies a different Reverse
2-408
3GPP2 C.S0005-A v6.0
1 ο If SCAM_REV_DURATION_MODEs is equal to ‘0’, the mobile station

2 may continue transmitting on the Reverse Supplemental Code
3 Channels until it receives a subsequent General Handoff Direction
4 Message or a Supplemental Channel Assignment Message that
5 specifies a different Reverse Supplemental Code Channel assignment.
6 + The mobile station shall set USE_REV_HDM_SEQs to ‘0’.
7 − If USE_REV_HDM_SEQs is equal to ‘0’ or REV_LINKED_HDM_SEQs is not
8 equal to HDM_SEQr, and if the previous Reverse Supplemental Code
9 Channel assignment is still valid, the mobile station may continue to
10 transmit on the Reverse Supplemental Code Channels according to the
11 previously specified Reverse Supplemental Code Channel assignment.
12 • If REV_INCLUDED is included and is equal to ‘1’, then the mobile station shall
13 process the Reverse Supplemental Code Channel assignment information as
14 follows:
15 − The mobile station shall set REV_DTX_DURATIONs to
16 REV_DTX_DURATIONr.
17 − The mobile station shall set USE_REV_HDM_SEQs to ‘0’.
18 − If REV_START_TIMEs specifies a time which is after the action time of the

19 General Handoff Direction Message, the mobile station shall cancel any
20 pending Reverse Supplemental Code Channel assignment and shall set
21 REV_START_TIMEs to NULL.
22 − If CLEAR_RETRY_DELAY is equal to ‘1’, the mobile station shall cancel any

23 previously indicated retry delay and shall set RETRY_DELAYs to 0;
24 otherwise, the mobile station shall continue to honor any previously active
25 retry delay stored in RETRY_DELAYs.
26 − The mobile station shall set NUM_REV_CODESs to NUM_REV_CODESr, and

28 + If NUM_REV_CODESs is equal to ‘000’, the mobile station shall stop
29 transmitting on all Reverse Supplemental Code Channels at the action
30 time of the message.
31 + If NUM_REV_CODESs is not equal to ‘000’, the mobile station shall set

32 PILOT_GATING_USE_RATE to ‘0’ at the action time of the message and
33 may start transmitting on NUM_REV_CODESs Reverse Supplemental
34 Code Channels at the action time of the message, for a duration of time
35 determined by the following rules:
2-409
3GPP2 C.S0005-A v6.0
1 ο If USE_REV_DURATIONr is equal to ‘1’, the mobile station shall set

2 REV_DURATIONs to REV_DURATIONr. The mobile station may
3 continue transmitting on the Reverse Supplemental Code Channels
4 for a period of (REV_DURATIONs × 80) ms, until it receives a
5 subsequent General Handoff Direction Message or a Supplemental
6 Channel Assignment Message that specifies a different Reverse
8 ο If USE_REV_DURATION is equal to ‘0’, the mobile station may

9 continue to transmit on the Reverse Supplemental Code Channels
10 until it receives a subsequent General Handoff Direction Message or a
11 Supplemental Channel Assignment Message that specifies a different
12 Reverse Supplemental Code Channel assignment.
13 − The mobile station shall store USE_T_ADD_ABORTr, the Reverse
14 Supplemental Code Channel assignment T_ADD abort indicator, as
15 USE_T_ADD_ABORTs.
16 • The mobile station shall set IGNORE_SCAMs and IGNORE_ESCAMs to ‘0’.
17 • If PERIODIC_SEARCHs is equal to ‘0’ and a periodic search is in progress, the

18 mobile station shall abort the periodic search (see 2.6.6.2.8.3.4 and
19 2.6.6.2.10.4).
21 − If any of the following conditions is true, the mobile station shall perform a
22 hard handoff:
23 + EXTRA_PARMS is set to ‘1’ and either BAND_CLASSr is not equal to
26 + The set of pilots specified by the message is disjoint from the Active
27 Set prior to the action time of the message.
28 − If the mobile station performs a hard handoff, it shall do the following:
29 + If a Periodic Serving Frequency Pilot Report Procedure is in progress, the

30 mobile station shall abort the procedure (see 2.6.6.2.12).
31 + If a Candidate Frequency periodic search is in progress, the mobile station

32 shall abort the periodic search (see 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
33 + The mobile station shall cancel the Forward Supplemental Channel

34 assignment or the Reverse Supplemental Channel assignment (if any).
35 + If RETURN_IF_HANDOFF_FAILs is equal to ‘0’, the mobile station shall
36 perform actions specified in 2.6.6.2.8.1. If the message specifies more than
37 one pilot, the mobile station shall also perform actions specified in
38 2.6.6.2.7.1 and 2.6.6.2.7.2.
2-410
3GPP2 C.S0005-A v6.0

2 perform actions specified in 2.6.6.2.8.2. If the message specifies more than
3 one pilot, the mobile station shall also perform actions specified in
4 2.6.6.2.7.1 and 2.6.6.2.7.2.
5 − Otherwise, the mobile station shall perform a soft handoff as specified in

6 2.6.6.2.7.
7 10. Periodic Pilot Measurement Request Order: The mobile station shall perform the
8 following:
9 • If the PPSMM timer is enabled, disable it.

10 • If ORDQ is equal to ‘11111111’, the mobile station shall send a Periodic Pilot
11 Strength Measurement Message to the base station within T56m seconds.
12 • If ORDQ is not equal to ‘11111111’, the mobile station shall perform the
13 following:
14 − Set the MIN_PILOT_PWR_THRESHs to MIN_PILOT_PWR_THRESHr received
15 from the Periodic Pilot Strength Measurement Request Order.
16 − Set the MIN_PILOT_EC_IO_THRESHs to MIN_PILOT_EC_IO_THRESHr
17 received from the Periodic Pilot Strength Measurement Request Order.
18 − Set PPSMM_PERIODs equal to the larger value of ORDQ and the total length
19 of time, in units of 80 ms, required by the mobile station to update the pilot
20 strength measurement of each pilot in the Active Set and the Candidate Set.
21 − Perform the Periodic Serving Frequency Pilot Report Procedure as specified in

22 2.6.6.2.12.
23 • If the mobile station sends the Periodic Pilot Strength Measurement Message and
24 if INCL_SETPTr is equal to ‘1’, the mobile station shall include outer loop Eb/Nt
25 setpoint information corresponding to the physical channel specified by
26 FPC_PRI_CHANs, and Supplemental Channel outer loop Eb/Nt setpoint
27 information if one or more Supplemental Channels are assigned, in the Periodic
28 Pilot Strength Measurement Message.
29 11. Universal Handoff Direction Message: The mobile station shall process the message
30 as follows:
31 In addition to the requirements in this section, if the SCR_INCLUDED field is

32 included in this message and is set to ‘1’ the mobile station shall also process this
33 message in accordance with the requirements for the active service subfunction (see
34 2.6.4.1.2.2).
37 any other action described in this section for processing the Universal Handoff
38 Direction Message:
2-411
3GPP2 C.S0005-A v6.0
1 set to ‘00000110’ (capability not supported), if the mobile station does not
2 support the band class specified in the Universal Handoff Direction Message.
3 • If the SCR_INCLUDED field is included in this message and is set to ‘1’, the
5 - The mobile station shall send a Mobile Station Reject Order with the ORDQ
6 field set to ‘00000111’ (message cannot be handled by the current mobile
7 station configuration), if the mobile station does not support the service
8 configuration specified in the Universal Handoff Direction Message.
9 - The mobile station shall send a Mobile Station Reject Order (ORDQ =
10 ‘00000111’) within T56m seconds, if the mobile station supports the service
11 configuration specified but does not accept the service configuration specified
12 in the Universal Handoff Direction Message.
14 set to ‘00000111’ (message cannot be handled by the current mobile station
15 configuration), if the NNSCR_INCLUDED field is included and set to ‘1’ and the
16 SCR_INCLUDED field is either not included or included but set to ‘0’, and the
17 mobile station does not support the configuration specified in the non-negotiable
18 service configuration information record in the Universal Handoff Direction
19 Message.
20 • If the CC_INFO_INCL field is included in this message and is set to ‘1’, the
21 mobile station shall perform the following for each of the NUM_CALLS_ASSIGN
22 call assignments included in this message:
23 − If there already exists or currently pending instantiation a Call Control

25 Station Reject Order with ORDQ field set to ‘00010010’ (a call control instance
26 is already present with the specified identifier), with the CON_REF field of the
27 order set to CON_REFr.
28 − If RESPONSE_INDr equals ‘1’ and TAGr does not match any of the TAG
31 (TAG received does not match TAG stored), with the TAG field of the order set
32 to TAGr, and the CON_REF field of the order set to CON_REFr.
33 − If the mobile station does not accept this call assignment, the mobile station
35 (call assignment not accepted), with the CON_REF field of the order set to
36 CON_REFr.
38 set to ‘00001010’ (search set not specified), if the PERIODIC_SEARCH field is
2-412
3GPP2 C.S0005-A v6.0
1 included in the Universal Handoff Direction Message and is set to ‘1’ and the
2 Candidate Frequency Search Set is empty.
4 set to ‘00000011’ (message structure not acceptable), if the message specifies the
5 Forward/Reverse Supplemental Channel assignment and the most significant
6 bit of CH_INDr is set to ‘0’.
8 set to ‘00000111’ (message can not be handled by the current mobile station
9 configuration), if the message includes a reverse Supplemental Channel
10 assignment, and any of the mobile station’s reverse supplemental channel
11 configuration parameter for the corresponding Supplemental Channel
12 (REV_SCH_MUXs, REV_SCH_RCs, REV_SCH_CODINGs, or
13 REV_SCH_FRAME_LENGTHs) is NULL.
16 configuration), if the message includes a forward Supplemental Channel
17 assignment and any of the mobile station’s forward supplemental channel
18 configuration parameters for the corresponding Supplemental Channel is not
19 included in the message and its stored value (FOR_SCH_MUXs, FOR_SCH_RCs,
20 FOR_SCH_CODINGs, FOR_SCH_FRAME_LENGTHs, QOF_IDs for the
21 corresponding SCCL_INDEXr, or FOR_SCH_CC_INDEXs for the corresponding
22 SCCL_INDEXr) is NULL.
23 • The mobile station shall send a Mobile Station Reject Order with the ORDQ field set
24 to ‘00001101’ (search period too short), if the PERIODIC_SEARCH field is included
25 in the Universal Handoff Direction Message and is set to ‘1’, and search_period is less
26 than (max (fwd_time, rev_time) + T71m seconds), where
27 search_period = time period corresponding to SEARCH_PERIODs shown in

28 Table 2.6.6.2.8.3.2-1,
29 fwd_time = the mobile station’s estimate of the total length of time, in seconds,
30 for which the mobile station will need to suspend its current Forward Traffic
31 Channel processing in order to tune to the CDMA Candidate Frequency, to search
32 the Candidate Frequency Search Set, and to re-tune to the Serving Frequency; if the
33 mobile station searches the Candidate Frequency Search Set in multiple visits,
34 fwd_time is the total time for all visits to the CDMA Candidate Frequency in a search
35 period (see 2.6.6.2.8.3.2),
36 and
2-413
3GPP2 C.S0005-A v6.0
1 rev_time = the mobile station’s estimate of the total length of time, in seconds, for
2 which the mobile station will need to suspend its current Reverse Traffic Channel
3 processing in order to tune to the CDMA Candidate Frequency, to search the
4 Candidate Frequency Search Set, and to re-tune to the Serving Frequency; if the
5 mobile station searches the Candidate Frequency Search Set in multiple visits,
6 rev_time is the total time for all visits to the CDMA Candidate Frequency in a search
7 period.
9 described in the remainder of this section to process the Universal Handoff Direction
10 Message at the action time of the message.
11 If EXTRA_PARMS is equal to '1', the mobile station shall store the return on failure
12 indicator from the Universal Handoff Direction Message
13 (RETURN_IF_HANDOFF_FAILs = RETURN_IF_HANDOFF_FAILr); otherwise the
14 mobile station shall set RETURN_IF_HANDOFF_FAILs to ‘0’.
15 The mobile station shall set RETURN_IF_HANDOFF_FAILs to ‘0’ (disable return on

16 failure) if any of the following conditions is true:
17 • If P_REV_IN_USEs is less than or equal to four and the mobile station does not
18 support hard handoff with return on failure, or
19 • At least one of the pilots specified by the message is also included in the Active
20 Set prior to the action time of the message, and one of the following conditions is
21 true:
22 − EXTRA_PARMS is equal to ‘0’, or
23 − EXTRA_PARMS is equal to ‘1’, the message specifies the same Frequency

24 Assignment as the Serving Frequency (BAND_CLASSr is equal to
25 CDMABANDs and CDMA_FREQr is equal to CDMACHs), and
26 FRAME_OFFSETr is equal to FRAME_OFFSETs.
27 The mobile station shall store the following parameters from its current
28 configuration:
29 • CDMA band class (SF_CDMABANDs = CDMABANDs)
30 • Frequency assignment (SF_CDMACHs = CDMACHs)
31 • Frame Offset (SF_FRAME_OFFSETs = FRAME_OFFSETs)
32 If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, the mobile station shall also store the
33 following parameters from its current configuration:
34 • Protocol revision level (SF_P_REVs = P_REVs)
35 • Protocol revision level in use on the Serving Frequency (SF_P_REV_IN_USEs =
36 P_REV_IN_USEs)
37 • Search window size for the Active Set and Candidate Set (SF_SRCH_WIN_As =
38 SRCH_WIN_As)
2-414
3GPP2 C.S0005-A v6.0
1 • Search window size for the Neighbor Set

2 (SF_SRCH_WIN_Ns = SRCH_WIN_Ns),
3 • Search window size for the Remainder Set

4 (SF_SRCH_WIN_Rs = SRCH_WIN_Rs)
5 • Pilot detection threshold (SF_T_ADDs = T_ADDs)
6 • Pilot drop threshold (SF_T_DROPs = T_DROPs)
7 • Active Set versus Candidate Set comparison threshold

8 (SF_T_COMPs = T_COMPs)
9 • Drop timer value (SF_T_TDROPs = T_TDROPs)
10 • Soft slope for the dynamic add and drop thresholds

11 (SF_SOFT_SLOPEs = SOFT_SLOPEs)
12 • Intercept for the dynamic add threshold

13 (SF_ADD_INTERCEPTs = ADD_INTERCEPTs)
14 • Intercept for the dynamic drop threshold

15 (SF_DROP_INTERCEPTs = DROP_INTERCEPTs)
16 • Private long code mask indicator: If the mobile station is using the private long
17 code mask on the Serving Frequency, it shall set SF_PRIVATE_LCMs to ‘1’;
18 otherwise, it shall set SF_PRIVATE_LCMs to ‘0’.
19 • Service negotiation type (SF_SERV_NEGs = SERV_NEGs)
20 • Service configuration: Store the current service configuration (service

21 configuration record and non-negotiable service configuration record) in
22 SF_SERVICE_CONFIGs
23 • Call Information:
24 Store the list of current calls (Call Control instances, etc.) in SF_CALLSs
25 • Message encryption mode: If message encryption is on, the mobile station shall
26 set SF_ENCRYPT_MODEs to ‘1’; otherwise, the mobile station shall set
27 SF_ENCRYPT_MODEs to ‘0’.
28 • If NNSCR_INCLUDED field is included and set to ‘1’ and SCR_INCLUDED field is

29 either not included or included but set to ‘0’, the mobile station shall process the
30 received Non-negotiable Service Configuration Record as specified in 2.6.4.1.13
31 at the action time of this message and the mobile station shall store (if included)
32 the synchronization identifier received from the base station corresponding to
33 this service configuration (SYNC_IDs = SYNC_IDr).
34 – Extended nominal power setting of the current cell

35 (SF_NOM_PWR_EXTs = NOM_PWR_EXTs)
36 – Nominal power setting of the current cell (SF_NOM_PWRs = NOM_PWRs)
37 – Power control step (SF_PWR_CNTL_STEPs = PWR_CNTL_STEPs)
2-415
3GPP2 C.S0005-A v6.0
1 – Serving Frequency Active Set (SF Active Set = (For each pilot in the current
2 Active Set: (PILOT_PN, PWR_COMB_IND) ) )
3 – Serving Frequency Code Channel List

4 (SF_CODE_CHAN_LISTs = CODE_CHAN_LISTs)
5 When the message takes effect, the mobile station shall perform the following
6 actions:
10 Universal Handoff Direction Message processing (see 2.6.6.2.6.1, 2.6.6.2.6.2, and
11 2.6.6.2.6.3).
12 • Discontinue use of all Forward Traffic Channels associated with pilots not in the
13 updated Active Set.
14 • If PARMS_INCL is equal to ‘1’, perform the following actions:

15 – Set protocol revision level (P_REVs = P_REVr), and protocol revision level
16 currently in use (P_REV_IN_USEs = min (P_REVs, MOB_P_REVp of the
17 current band class)).
18 – If SERV_NEG_TYPEr is equal to ‘1’, set SERV_NEGs to enabled; otherwise set
19 SERV_NEGs to disabled. • If EXTRA_PARMS is equal to ‘1’, perform the
21 • If EXTRA_PARMS is equal to ‘1’, perform the following actions:

22 – If FRAME_OFFSETr is not equal to FRAME_OFFSETs, change the frame
25 – If RESET_L2r is equal to ‘1’, and RETURN_IF_HANDOFF_FAILs is equal to ‘0’,
26 Layer 3 shall send a L2-Supervision.Request primitive to Layer 2 to reset the
27 acknowledgment procedures, as specified in 2.2.1.1 and 2.2.2.1 of [4]. The
28 mobile station shall reset the acknowledgment procedures immediately after
29 the action time of the Universal Handoff Direction Message.
30 – If RESET_FPCr is equal to ‘1’ and RETURN_IF_HANDOFF_FAILs is equal to
31 ‘0’, initialize the Forward Traffic Channel power control counters, as specified
32 in 2.6.4.1.1.1.
33 – Use the long code mask specified by the PRIVATE_LCMr (see 2.3.12.3) and
35 – Process the ENCRYPT_MODE field, as specified in 2.3.12.2.

36 – If D_SIG_ENCRYPT_MODEr is included, the mobile station shall set
37 D_SIG_ENCRYPT_MODEs to D_SIG_ENCRYPT_MODEr.
38 − If D_SIG_ENCRYPT_MODEr is included, the mobile station shall perform the

39 following:
2-416
3GPP2 C.S0005-A v6.0
1 + If D_SIG_ENCRYPT_MODEr is equal to ‘000’, the mobile station shall

4 D_SIG_ENCRYPT_MODEr and set KEYs to the most recently
5 generated CMEAKEY in the mobile station.
6 – If USE_NEW_KEYr is not included, or is include and is set to ‘1’, the mobile
10 KEY_SIZEr in KEY_SIZEs. The mobile station shall then increment the
11 variable KEY_SEQ_NEWs-p by one (modulo 16).If ENC_KEY_SIZEr is
12 included, the mobile station shall set ENC_KEY_SIZEs to ENC_KEY_SIZEr.
13 – If USE_NEW_KEYr is included and is set to ‘0’, the mobile station shall use
14 KEYs[KEY_SEQr] as the session key with the key-size specified by
15 KEY_SIZEr.
16 • If EXTRA_PARMS is equal to ‘0’, set the following variables to the values

17 indicated:
18 – Hard handoff traffic channel preamble count required before transmitting

19 a Handoff Completion Message or an Extended Handoff Completion
20 Message (NUM_PREAMBLEs = ‘000’)
21 – Complete search flag (COMPLETE_SEARCHs = ‘1’)
22 – CDMA band class for the Target Frequency

23 (TF_CDMABANDs = SF_CDMABANDs)
24 – Frequency assignment for the Target Frequency

25 (TF_CDMACHs = SF_CDMACHs)
26 • Store the following parameters from the Universal Handoff Direction Message:
27 – Universal Handoff Direction Message sequence number

28 (HDM_SEQs = HDM_SEQr)
29 – Forward power control subchannel relative gain (FPC_SUBCHAN_GAINs =

30 FPC_SUBCHAN_GAINr).
31 − If the mobile station uses FPC_SUBCHAN_GAINs, the mobile station shall

33 + If PC_ACTION_TIMEr is received, the mobile station shall apply its
34 usage of the FPC_SUBCHAN_GAINs at the time specified by
35 PC_ACTION_TIMEr.
36 + If PC_ACTION_TIME is not received and the explicit action time is

37 received, the mobile station shall apply its usage of the
38 FPC_SUBCHAN_GAINs at the action time.
2-417
3GPP2 C.S0005-A v6.0
1 + If neither PC_ACTION_TIMEr nor explicit action time is received, the

2 mobile station shall apply its usage of the FPC_SUBCHAN_GAINs at
3 the first 80ms boundary occurring at least 80ms after the end of the
4 frame containing the last bit of the Universal Handoff Direction
5 Message sent to the mobile station.
6 − Reverse Eighth Gating Mode (REV_FCH_GATING_MODEs =
7 REV_FCH_GATING_MODEr).
8 − Reverse Power Control Delay if REV_PWR_CNTL_DELAY_INCLr is equal to

9 ‘1’ (REV_PWR_CNTL_DELAYs = REV_PWR_CNTL_DELAYr).
10 – If SEARCH_INCLUDED is equal to ‘1’, store the following:
13 + Pilot detection threshold (T_ADDs = T_ADDr)
14 + Pilot drop threshold (T_DROPs = T_DROPr)

17 + Drop timer value (T_TDROPs = T_TDROPr)
18 + Soft slope for the dynamic add and drop thresholds

19 (SOFT_SLOPEs = SOFT_SLOPEr)
20 + Intercept for the dynamic add threshold

21 (ADD_INTERCEPTs = ADD_INTERCEPTr)
22 + Intercept for the dynamic drop threshold

23 (DROP_INTERCEPTs = DROP_INTERCEPTr)
24 – If EXTRA_PARMS is equal to ‘1’, store the following:
25 + If the mobile station supports packet data service options, the packet
26 data services zone identifier (PACKET_ZONE_IDs =
27 PACKET_ZONE_IDr)
29 + Acknowledgment procedures reset indicator

30 (If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, set TF_RESET_L2s to
31 RESET_L2r)
32 + Indicator to initialize the Forward Traffic Channel power control

33 counters (If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, set
34 TF_RESET_FPCs to RESET_FPCr)
36 + Extended nominal power setting of the target cell (If CDMABANDs =

37 ‘00000’ or CDMABANDs = ‘00011’, then NOM_PWR_EXTs = ‘0’;
38 otherwise, NOM_PWR_EXTs = NOM_PWR_EXTr)
2-418
3GPP2 C.S0005-A v6.0
1 + Hard handoff traffic channel preamble count required before

2 transmitting a Handoff Completion Message or an Extended Handoff
3 Completion Message (NUM_PREAMBLEs = NUM_PREAMBLEr)
4 + CDMA band class for the Target Frequency

5 (TF_CDMABANDs = BAND_CLASSr and CDMABANDs =
6 BAND_CLASSr)
7 + Frequency assignment for the Target Frequency

8 (TF_CDMACHs = CDMA_FREQr and CDMACHs = CDMA_FREQr)
9 + Complete search flag (COMPLETE_SEARCHs =
10 COMPLETE_SEARCHr)
11 + Periodic search flag (PERIODIC_SEARCHs = PERIODIC_SEARCHr)
12 + Nominal code channel output power offset relative to the Reverse Pilot
13 Channel power (RLGAIN_TRAFFIC_PILOTs =
14 RLGAIN_TRAFFIC_PILOTr)
15 – If EXTRA_PARMS is equal to ‘1’ and DEFAULT_RLAG is equal to ‘1’, the

16 mobile station shall set each entry of the Reverse Link Attribute
17 Adjustment Gain Table and Reverse Channel Adjustment Gain Table (see
18 2.1.2.3.3 of [2]) to 0.
19 – If USE_PWR_CNTL_STEP is equal to ‘1’ and PWR_CNTL_STEPr
20 corresponds to a power control step size supported by the mobile station
21 (see of [2]), then the mobile station shall set PWR_CNTL_STEPs to
22 PWR_CNTL_STEPr.
23 – If CLEAR_RETRY_DELAYr is equal to ‘1’, the mobile station shall cancel

24 any previously indicated retry delay and shall set
25 RETRY_DELAYs[RETRY_TYPE] to 0, where RETRY_TYPE is equal to ‘001’,
26 ‘010’ or ‘011’; otherwise, the mobile station shall continue to honor any
27 previously active retry delay stored in RETRY_DELAYs.

30 – If SCH_INCLr is equal to ‘1’ and NUM_FOR_ASSIGNr is not equal to ‘00’,

31 the mobile station shall store the following information for each
32 occurrence of the record and process the Forward Supplemental Burst as
33 specified in 2.6.6.2.5.1.1:
34 + FOR_SCH_START_TIME_INCLs[FOR_SCH_IDr] =
35 FOR_SCH_START_TIME_INCLr
36 + If FOR_SCH_START_TIME_INCLs[FOR_SCH_IDr] is equal to’1’, set

37 FOR_SCH_START_TIMEs[FOR_SCH_IDr] = FOR_SCH_START_TIMEr
38 + FOR_SCH_DURATIONs[FOR_SCH_IDr] = FOR_SCH_DURATIONr
39 + SCCL_INDEXs[FOR_SCH_IDr] = SCCL_INDEXr
2-419
3GPP2 C.S0005-A v6.0
1 – If SCH_INCLr is equal to ‘1’ and NUM_REV_ASSIGNr is not equal to ‘00’,

2 the mobile station shall store the following information for each
3 occurrence of the record and process the Reverse Supplemental Burst as
4 specified in 2.6.6.2.5.1.2:
5 + REV_SCH_START_TIME_INCLs[REV_SCH_IDr] =
6 REV_SCH_START_TIME_INCLr
7 + If REV_SCH_START_TIME_INCLs[REV_SCH_IDr] is equal to’1’, set

8 REV_SCH_START_TIMEs[REV_SCH_IDr] = REV_SCH_START_TIMEr
9 + REV_SCH_DURATIONs[REV_SCH_IDr] = REV_SCH_DURATIONr
10 + REV_SCH_NUM_BITS_IDXs[REV_SCH_IDr] =
11 REV_SCH_NUM_BITS_IDXr
12 – If CH_INDr is equal to ‘101’, the mobile station shall perform the
13 following:
14 + The mobile station shall set CH_INDs = ‘01’.
15 + If SCH_INCLr is equal to ‘1’ and NUM_FOR_SCH is not equal to

16 ‘00000’, for all the NUM_FOR_SCH occurrences, the mobile station
18 ο The mobile station shall determine,

19 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr], the number
20 of information bits per Forward Supplemental Channel frame
21 identified by FOR_SCH_ID and corresponding to the index
22 SCCL_INDEX according to the following rules:
23 ◊ If FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is equal to ‘000’,
24 then:
25 – If USE_FLEX_NUM_BITSs is equal to '0' or if
26 USE_FLEX_NUM_BITSs is equal to '1' and
27 FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr] is equal to ‘0000’,
28 then the mobile station shall set the number of
29 information bits per frame,
30 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr] and
31 number of CRC bits per frame,
32 FSCH_CRC_LEN_SETs[FOR_SCH_IDr][SCCL_INDEXr],
33 according to Table 3.7.3.3.2.37-2 using
34 FOR_SCH_NUM_BITS_IDXr as the index to the table.
2-420
3GPP2 C.S0005-A v6.0
1 – If USE_FLEX_NUM_BITSs is equal to '1' and

2 FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr] is not equal to
3 ‘0000’, then the mobile station shall set the number of
4 CRC bits per frame,
6 using Table 3.7.5.20-1 and
7 CRC_LEN_IDXs[FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr]][F
8 OR_SCH_NUM_BITS_IDXr] as the index to the table.
9 The mobile station shall also set the number of
10 information bits per frame corresponding to
11 SCCL_INDEXr,
12 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr], to
13 NUM_BITSs[FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr]][FOR_
14 SCH_NUM_BITS_IDXr].
15 ◊ If FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is not equal to ‘000’,

16 then:
17 – The mobile station shall set

18 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr], the set of indices
19 to the number of information bits per frame as follows:
20 + If FOR_SCH_NUM_BITS_IDXr is equal to ‘0000’, then
21 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr] = {
22 FOR_SCH_NUM_BITS_IDXr },
23 + otherwise the mobile station shall set (initialize)

24 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr] =
25 {FOR_SCH_NUM_BITS_IDXr} and for i=1, …,
26 FOR_SCH_NUM_BITS_IDXr the mobile station shall
27 add FOR_SCH_NUM_BITS_IDXr -
28 VAR_FSCH_RATE_OFFSETs[FOR_SCH_IDr][FOR_SCH_
29 NUM_BITS_IDXr][i] to the set specified by
30 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr]
31

35 then the mobile station shall set
36 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr], the
37 set of number of information bits per frame as follows.
th
38 The i member of the set
39 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr] is
th
40 obtained using Table 3.7.3.3.2.37-2 and the i member of
41 the set N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr] as the
42 index to the table.
2-421
3GPP2 C.S0005-A v6.0

3 ‘0000’, then
4 + the mobile station shall set

5 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr],
6 the set of number of information bits per frame as
7 follows.
th
10 equal to
11 NUM_BITSs[FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr]]
12 [N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr][i]], where
13 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr][i] denotes the
th
14 i member of the set
15 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr] and,

18 the set of number CRC bits per frame as follows.
th
20 FSCH_CRC_LEN_SETs[FOR_SCH_IDr][SCCL_INDEXr]
22 CRC_LEN_IDXs[FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr
23 ]][N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr][i]] as the
24 index to the table, where
th
27 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr].
28 + If SCH_INCLr is equal to ‘1’ and NUM_REV_SCH is not equal to

29 ‘00000’, for all the NUM_REV_SCH occurrences, the mobile station
31 ο Set REV_SCH_NUM_BITS_IDXs[REV_SCH_IDr] to
32 REV_SCH_NUM_BITS_IDXr.
33 ο Set REV_WALSH_IDs [REV_SCH_IDr][REV_SCH_NUM_BITS_IDXs]

34 to REV_WALSH_IDr.
35 + For each member of the Active Set included in the message, the
37 ο Set PILOT_PN to PILOT_PNr.
38 ο If SRCH_OFFSET_INCLr equals to ‘1’, set the SRCH_OFFSET field

39 of PILOT_REC to SRCH_OFFSETr; otherwise, set the
40 SRCH_OFFSET field of PILOT_REC to ‘000’.
41 ο Set ADD_PILOT_REC_INCL to ADD_PILOT_REC_INCLr.
2-422
3GPP2 C.S0005-A v6.0
1 ο If ADD_PILOT_REC_INCLr equals ‘1’, the mobile station shall also


4 PILOT_REC_TYPEr.

6 set the TD_POWER_LEVEL field of PILOT_REC to
8 NGHBR_PILOT_REC to TD_MODEr.


18 WALSH_LENGTHr.







2-423
3GPP2 C.S0005-A v6.0

3 by WALSH_LENGTHr.
4 – If ADD_INFO_INCL1r is equal to ‘1’, set the

5 AUX_PILOT_QOF1 field of PILOT_REC to QOF1r and set
6 the AUX_PILOT_WALSH_CODE1 field of PILOT_REC to
7 AUX_PILOT_WALSH1r with the Walsh Code length
8 specified by WALSH_LENGTH1r; otherwise, set the
9 AUX_PILOT_QOF1 field of PILOT_REC to QOFr and set the

22 ο Store PWR_COMB_IND, CODE_CHAN_FCH and

23 QOF_MASK_ID_FCH.
24 ο If SCH_INCLr is equal to ‘1’ and NUM_SCH is equal to ‘00000’, the
25 mobile station shall delete the corresponding pilot from the all
26 entries of the corresponding Supplemental Channel.
27 ο If SCH_INCLr is equal to ‘1’ and NUM_SCH is not equal to ‘00000’,
28 for each Supplemental Channel included in this record, the
29 mobile station shall:
30 ◊ If PILOT_INCL is equal to ‘0’, the mobile station shall delete

31 the corresponding pilot from the Active Set of Supplemental
32 Channel for the corresponding SCCL_INDEXr.
33 ◊ If PILOT_INCL is equal to ‘1’, for each Supplemental Channel

34 included in this record, the mobile station shall set PILOT_PNs
35 [FOR_SCH_IDr][SCCL_INDEXr][i] to PILOT_PNr,
36 QOF_IDs[FOR_SCH_IDr][SCCL_INDEXr][i] to
37 QOF_MASK_ID_SCHr, and
38 FOR_SCH_CC_INDEXs[FOR_SCH_IDr][SCCL_INDEXr][i] to
39 CODE_CHAN_SCHr.
2-424
3GPP2 C.S0005-A v6.0
1 ◊ The mobile station shall delete all pilots that are not included
2 in the list specified by the NUM_PILOTS field from the Active
3 Set of Supplemental Channel for the corresponding
4 SCCL_INDEXr.
5 + If 3X_FCH_INFO_INCLr equals to ‘1’, for each included member of the

6 Active Set, the mobile station store the following:
7 ο If 3X_FCH_LOW_INCLr equals ‘1’, set the

8 QOF_MASK_ID_FCH_LOW field to QOF_MASK_ID_FCH_LOWr and
9 the CODE_CHAN_FCH_LOW field to CODE_CHAN_FCH_LOWr.
10 Otherwise, set the QOF_MASK_ID_FCH_LOW field to
11 QOF_MASK_ID_FCHr and the CODE_CHAN_FCH_LOW to
12 CODE_CHAN_FCHr.
13 ο If 3X_FCH_HIGH_INCLr equals ‘1’, set the

14 QOF_MASK_ID_FCH_HIGH field to QOF_MASK_ID_FCH_HIGHr
15 and the CODE_CHAN_FCH_HIGH field to
16 CODE_CHAN_FCH_HIGHr. Otherwise, set the
19 ο If 3X_SCH_INFO_INCLr equals to ‘1’, for each Supplemental

20 Channel included, the mobile station store the following:
21 ◊ If 3X_SCH_LOW_INCLr equals ‘1’, set the QOF_ID_SCH_LOWs
22 [FOR_SCH_IDr][SCCL_INDEXr][i] to
23 QOF_MASK_ID_SCH_LOWr and the
24 FOR_SCH_CC_INDEX_LOW[FOR_SCH_IDr][SCCL_INDEXr][i]
25 field to CODE_CHAN_SCH_LOWr. Otherwise, set
26 QOF_ID_SCH_LOWs[FOR_SCH_IDr][SCCL_INDEXr][i] to
28 FOR_SCH_CC_INDEX_LOWs[FOR_SCH_IDr][SCCL_INDEXr][i]
29 to CODE_CHAN_SCHr.
30 ◊ If 3X_SCH_HIGH_INCLr equals ‘1’, set the

31 QOF_ID_SCH_HIGHs [FOR_SCH_IDr][SCCL_INDEXr][i] to
32 QOF_MASK_ID_SCH_HIGHr and the
33 FOR_SCH_CC_INDEX_HIGH[FOR_SCH_IDr][SCCL_INDEXr][i]
34 field to CODE_CHAN_SCH_HIGHr. Otherwise, set
35 QOF_ID_SCH_HIGHs[FOR_SCH_IDr][SCCL_INDEXr][i] to
37 FOR_SCH_CC_INDEX_HIGHs[FOR_SCH_IDr][SCCL_INDEXr][i]
39 + The mobile station shall delete all pilots that are not listed in the
40 NUM_PILOTS field from the Active Set of Fundamental Channel.
2-425
3GPP2 C.S0005-A v6.0
2 Active Set of the Fundamental Channel from the Active Set of the
3 Supplemental Channel for the Forward Supplemental Channel
4 Assignment (if any). If these deleted pilots include all pilots in the
5 Active Set of the Supplemental Channel, the mobile station shall
7 – If CH_INDr is equal to ‘010’ or ‘110’, the mobile station shall perform the
8 following:


19 then:
2-426
3GPP2 C.S0005-A v6.0

11 SCCL_INDEXr,
15 ◊ If FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is not equal to ‘000’,

16 then:



th
th
2-427
3GPP2 C.S0005-A v6.0

3 ‘0000’, then

7 follows.
th
10 equal to
th

th
th

33 ο Set REV_WALSH_IDs [REV_SCH_IDr][REV_SCH_NUM_BITS_IDXs]

35 + For each member of the Active Set included in the message, the
36 mobile station shall perform the followings:

2-428
3GPP2 C.S0005-A v6.0


4 PILOT_REC_TYPEr.

8 PILOT_REC to TD_MODEr.


18 WALSH_LENGTHr.







2-429
3GPP2 C.S0005-A v6.0

3 by WALSH_LENGTHr.


22 ο Store PWR_COMB_IND, CODE_CHAN_DCCH and

23 QOF_MASK_ID_DCCH.
25 mobile station shall delete the corresponding pilot from all entries
26 of the corresponding Supplemental Channel.


34 [FOR_SCH_IDr][SCCL_INDEXs][i] to PILOT_PNr,
35 QOF_IDs[FOR_SCH_IDr][SCCL_INDEXs][i] to
36 QOF_MASK_ID_SCHr, and FOR_SCH_CC_INDEXs
37 [FOR_SCH_IDs][SCCL_INDEXs][i] to CODE_CHAN_SCHr.
41 SCCL_INDEXr.
2-430
3GPP2 C.S0005-A v6.0
1 + If 3X_DCCH_INFO_INCLr equals to ‘1’, for each included member of

2 the Active Set, the mobile station store the following:

4 QOF_MASK_ID_DCCH_LOW field to QOF_MASK_ID_DCCH_LOWr
5 and the CODE_CHAN_DCCH_LOW field to
6 CODE_CHAN_DCCH_LOWr. Otherwise, set the

10 QOF_MASK_ID_DCCH_HIGH field to
11 QOF_MASK_ID_DCCH_HIGHr and the CODE_CHAN_DCCH_HIGH
13 QOF_MASK_ID_DCCH_HIGH field to QOF_MASK_ID_FCHr and
14 the CODE_CHAN_DCCH_HIGH to CODE_CHAN_FCHr.

17 ◊ If 3X_SCH_LOW_INCLr equals ‘1’, set
18 QOF_ID_SCH_LOW[FOR_SCH_IDr][SCCL_INDEXr][i] to
19 QOF_MASK_ID_SCH_LOWr and
26 ◊ If 3X_SCH_HIGH_INCLr equals ‘1’, set

27 QOF_ID_SCH_HIGH[FOR_SCH_IDr][SCCL_INDEXr][i] to
36 NUM_PILOTS field from the Active Set of Dedicated Control Channel.
38 Active Set of the Dedicated Control Channel from the Active Set of the
39 Supplemental Channel for the Forward Supplemental Channel
40 Assignment (if any). If these deleted pilots include all pilots in the
41 Active Set of the Supplemental Channel, the mobile station shall
2-431
3GPP2 C.S0005-A v6.0
1 – If CH_INDr is equal to ‘111’, the mobile station shall perform the

2 following:


13 then:

34 SCCL_INDEXr,
38 ◊ If If FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is not equal to

39 ‘000’, then:

2-432
3GPP2 C.S0005-A v6.0



th
th
25 ‘0000’, then

29 follows.
th
32 equal to
th
2-433
3GPP2 C.S0005-A v6.0

th
th

18 ο Set REV_WALSH_IDs[REV_SCH_IDr][REV_SCH_NUM_BITS_IDXs]
20 + For each member in the Active Set included in the message, the
21 mobile station shall perform the followings:



30 PILOT_REC_TYPEr.

34 PILOT_REC to TD_MODEr.

2-434
3GPP2 C.S0005-A v6.0

4 WALSH_LENGTHr.









2-435
3GPP2 C.S0005-A v6.0

9 by WALSH_LENGTHr.
10 ο Store PWR_COMB_IND, CODE_CHAN_FCH, QOF_MASK_ID_FCH,

11 CODE_CHAN_DCCH and QOF_MASK_ID_DCCH.
13 mobile station shall delete the corresponding pilot from all entries
14 of the corresponding Supplemental Channel.


22 [FOR_SCH_IDr][SCCL_INDEXr][i] to PILOT_PNr,
23 QOF_IDs[FOR_SCH_IDr][SCCL_INDEXr][i] to
24 QOF_MASK_ID_SCHr, and FOR_SCH_CC_INDEXs
25 [FOR_SCH_IDr][SCCL_INDEXr][i] to CODE_CHAN_SCHr.
29 SCCL_INDEXr.
30 + If 3X_FCH_INFO_INCLr equals to ‘1’, for each included member of the

31 Active Set, the mobile station store the following:
32 ο If 3X_FCH_LOW_INCLr equals ‘1’, set the

33 QOF_MASK_ID_FCH_LOW field to QOF_MASK_ID_FCH_LOWr and
34 the CODE_CHAN_FCH_LOW field to CODE_CHAN_FCH_LOWr.
35 Otherwise, set the QOF_MASK_ID_FCH_LOW field to
36 QOF_MASK_ID_FCHr and the CODE_CHAN_FCH_LOW to
37 CODE_CHAN_FCHr.
2-436
3GPP2 C.S0005-A v6.0
1 ο If 3X_FCH_HIGH_INCLr equals ‘1’, set the

2 QOF_MASK_ID_FCH_HIGH field to QOF_MASK_ID_FCH_HIGHr
3 and the CODE_CHAN_FCH_HIGH field to
4 CODE_CHAN_FCH_HIGHr. Otherwise, set the
7 + If 3X_DCCH_INFO_INCLr equals to ‘1’, for each included member of

8 the Active Set, the mobile station store the following:

10 QOF_MASK_ID_DCCH_LOW field to QOF_MASK_ID_DCCH_LOWr
11 and the CODE_CHAN_DCCH_LOW field to
12 CODE_CHAN_DCCH_LOWr. Otherwise, set the

16 QOF_MASK_ID_DCCH_HIGH field to
17 QOF_MASK_ID_DCCH_HIGHr and the CODE_CHAN_DCCH_HIGH
19 QOF_MASK_ID_DCCH_HIGH field to QOF_MASK_ID_FCHr and
20 the CODE_CHAN_DCCH_HIGH to CODE_CHAN_FCHr.
21 + If 3X_FCH_INFO_INCLr or 3X_DCCH_INFO_INCLr equals to ‘1’, for

22 each included member of the Active Set, the mobile station store the
23 following:

26 ◊ If 3X_SCH_LOW_INCLr equals ‘1’, set
28 QOF_MASK_ID_SCH_LOWr and the
35 ◊ If 3X_SCH_HIGH_INCLr equals ‘1’, set

2-437
3GPP2 C.S0005-A v6.0
2 NUM_PILOTS field from the Active Set of Fundamental Channel and
3 Dedicated Control Channel.
5 Active Set of the Fundamental Channel and Dedicated Control
6 Channel from the Active Set of the Supplemental Channel for the
7 Forward Supplemental Channel Assignment (if any). If these deleted
8 pilots include all pilots in the Active Set of the Supplemental
9 Channel, the mobile station shall cancel the Forward Supplemental
10 Channel Assignment.
11 • If the most significant bit of CH_INDr is set to ‘1’ and

12 PILOT_GATING_USE_RATE is equal to ‘1’, the mobile station shall set
13 PILOT_GATING_USE_RATE to ‘0’ and shall start the continuous reverse pilot
14 at the specified action time. If the most significant bit of CH_INDr is set to ‘0’
15 and PILOT_GATING_USE_RATE is equal to ‘0’, the mobile station shall
17 – The mobile station shall set PILOT_GATING_USE_RATE to ‘1’ and shall

18 start the reverse pilot gating at the specified action time.
19 – If the Fundamental Channel is also being released, the mobile station

20 shall store the configuration used for the Fundamental Channel.
21 – The mobile station shall cancel the forward and reverse supplemental
22 channel assignment, if any.
23 • The mobile station shall set IGNORE_ESCAMs and IGNORE_SCAMs to ‘0’.
24 • Set the pilot detection threshold for the Target Frequency and the Candidate
25 Frequency:
26 – Set TF_T_ADDs to T_ADDs.
27 – If the Target Frequency is the same as the Candidate Frequency

28 (TF_CDMABANDs is equal to CF_CDMABANDs and TF_CDMACHs is
29 equal to CF_CDMACHs), set CF_T_ADDs to T_ADDs.
30 • If PERIODIC_SEARCHs is equal to ‘0’ and a periodic search is in progress,

31 the mobile station shall abort the periodic search (see 2.6.6.2.8.3.4 and
32 2.6.6.2.10.4).
34 – If any of the following conditions is true, the mobile station shall perform a
35 hard handoff:
36 + EXTRA_PARMS is set to ‘1’ and either BAND_CLASSr is not equal to
39 + The set of pilots specified by the message is disjoint from the Active Set
40 prior to the action time of the message.
2-438
3GPP2 C.S0005-A v6.0
1 – If the mobile station performs a hard handoff, it shall do the following:
2 + If a Periodic Serving Frequency Pilot Report Procedure is in progress, the

3 mobile station shall abort the procedure (see 2.6.6.2.12).
4 + If a Candidate Frequency periodic search is in progress, the mobile

5 station shall abort the periodic search (see 2.6.6.2.8.3.4 and
6 2.6.6.2.10.4).
7 + If a Forward Supplemental Channel assignment or a Reverse

8 Supplemental Channel assignment is in progress, the mobile station
9 shall abort it.
10 + The mobile station shall cancel any outstanding Forward

11 Supplemental Channel assignment or Reverse Supplemental Channel
12 assignment that is not specified by this message.
13 + The mobile station shall cancel the current Forward Supplemental

14 Channel assignment or the Reverse Supplemental Channel assignment,
15 if it is in progress. If the message does not specify another Forward
17 assignment, the mobile station shall cancel the outstanding Forward
19 assignment, if any.
21 perform actions specified in 2.6.6.2.8.1. If the message specifies more
22 than one pilot, the mobile station shall also perform actions specified in
23 2.6.6.2.7.1 and 2.6.6.2.7.2.
25 perform actions specified in 2.6.6.2.8.2. If the message specifies more
26 than one pilot, the mobile station shall also perform actions specified in
27 2.6.6.2.7.1 and 2.6.6.2.7.2.
28 – Otherwise, the mobile station shall perform a soft handoff as specified in

29 2.6.6.2.7.
30 12. Mobile Assisted Burst Operation Parameters Message: The mobile station shall
31 process this message as follows:
32 • The mobile station shall set ORDER_FLAGs to ORDER_FLAGr.
33 • If ORDER_FLAGr is equal to ‘1’, the mobile station shall perform the

34 following:
35 – The mobile station shall set PS_MIN_DELTAs to PS_MIN_DELTAr + 1.
36 – The mobile station shall set ORDER_INTERVALs to ORDER_INTERVALr.
37 • If ORDER_FLAGr is equal to ‘0’, the mobile station shall perform the

38 following:
39 – The mobile station shall set PS_MIN_DELTAs to 0.
2-439
3GPP2 C.S0005-A v6.0
1 – The mobile station shall set ORDER_INTERVALs to 0.
2 • The mobile station shall set PERIODIC_FLAGs to PERIODIC_FLAGr.
3 • If PERIODIC_FLAGr is equal to ‘1’, the mobile station shall perform the

4 following:
5 – The mobile station shall set NUM_PILOTSs to NUM_PILOTSr.
6 – The mobile station shall set PERIODIC_INTERVALs to

7 PERIODIC_INTERVALr.
8 • If PERIODIC_FLAGr is equal to ‘0’, the mobile station shall perform the

9 following:
10 – The mobile station shall set NUM_PILOTSs to 0.
11 – The mobile station shall set PERIODIC_INTERVALs to 0.
12 • The mobile station shall set THRESHOLD_FLAGs to THRESHOLD_FLAGr.
13 • If THRESHOLD_FLAGr is equal to ‘1’, the mobile station shall perform the

14 following:
15 – The mobile station shall set PS_FLOOR_LOWs to PS_FLOOR_LOWr.
16 – The mobile station shall set PS_FLOOR_HIGHs to PS_FLOOR_HIGHr.
17 – The mobile station shall set PS_CEILING_LOWs to PS_CEILING_LOWr.
18 – The mobile station shall set PS_CEILING_HIGHs to PS_CEILING_HIGHr.
19 • If THRESHOLD_FLAGr is equal to ‘0’, the mobile station shall perform the

20 following:
21 – The mobile station shall set PS_FLOOR_LOWs to ‘0’.
22 – The mobile station shall set PS_FLOOR_HIGHs to ‘0’.
23 – The mobile station shall set PS_CEILING_LOWs to ‘0’.
24 – The mobile station shall set PS_CEILING_HIGHs to ‘0’.
25 13. Extended Supplemental Channel Assignment Message: The mobile station shall
27 The mobile station shall send a Mobile Station Reject Order with the ORDQ field
28 set to the specified value if any of the following conditions is true, and shall not
29 perform any other action described in this section for processing the Extended
30 Supplemental Channel Assignment Message:
31 • The mobile station shall send a Mobile Station Reject Order with the ORDQ
32 field set to ‘00000110’ (capability not supported), if the number of forward or
33 reverse Supplemental Channels specified in the Extended Supplemental
34 Channel Assignment Message is greater than the maximum number of
35 Supplemental Channels supported by the mobile station.
2-440
3GPP2 C.S0005-A v6.0
2 field set to ‘00000100’ (message field not in valid range), if PILOT_PN
3 specified in the Extended Supplemental Channel Assignment Message is not
4 in the Active Set.
6 field set to ‘00000111’ (message can not be handled by the current mobile
7 station configuration), if the message includes a reverse Supplemental
8 Channel assignment, and any of the mobile station’s reverse supplemental
9 channel configuration parameter for the corresponding Supplemental
10 Channel is not included in the message and its stored value
11 (REV_SCH_MUXs, REV_SCH_RCs, REV_SCH_CODINGs,
12 REV_SCH_FRAME_LENGTHs, QOF_IDs for the corresponding SCCL_INDEXr,
13 or FOR_SCH_CC_INDEXs for the corresponding SCCL_INDEXr) is NULL.
15 field set to ‘00000111’ (message can not be handled by the current mobile
16 station configuration), if the message includes a forward Supplemental
17 Channel assignment and any of the mobile station’s forward supplemental
18 channel configuration parameter for the corresponding Supplemental
19 Channel (FOR_SCH_MUXs, FOR_SCH_RCs, FOR_SCH_CODINGs, or
20 FOR_SCH_FRAME_LENGTHs) is NULL.
21 If none of the above conditions is true, the mobile station shall perform the
22 following:
23 • The mobile station shall store REV_SCH_DTX_DURATIONr, Reverse
24 Supplemental Channel Discontinuous Transmission Duration, as
25 REV_SCH_DTX_DURATIONs.
26 • The mobile station shall store the unit for START_TIME_UNITs =

27 START_TIME_UNITr.
28 • The mobile station shall store USE_T_ADD_ABORTr, Reverse Supplemental

29 Channel assignment T_ADD abort indicator, as USE_T_ADD_ABORTs.
30 • If IGNORE_ESCAMs is equal to ‘1’ and SCRM_SEQ_NUMr is not present or is

31 present and is not equal to SCRM_SEQ_NUMs, then the mobile station shall
32 not process the remaining Reverse Supplemental Channel assignment
33 information in this message.
34 • If IGNORE_ESCAMs is equal to ‘1’ and SCRM_SEQ_NUMr is present and is
35 equal to SCRM_SEQ_NUMs, then the mobile station shall set
36 IGNORE_ESCAMs to ‘0’.
37 • If ADD_INFO_INCLr is equal to ‘1’, the message includes a Supplemental

38 Channel assignment (that is, NUM_FOR_SCHr is not equal to ‘00’ and/or
39 NUM_REV_SCHr is not equal to ‘00’), and PILOT_GATING_USE_RATE is
40 equal to ‘1’, the mobile station shall process the following information of the
41 Extended Supplemental Channel Assignment Message as follows:
2-441
3GPP2 C.S0005-A v6.0
1 – The mobile station shall set FPC_PRI_CHANs = FPC_PRI_CHANr at the

2 action time of the message.
3 –The mobile station shall set PILOT_GATING_USE_RATE to ‘0’ and shall start
4 the continuous reverse pilot at the specified action time.
5 – If the Fundamental Channel was previously established prior to

6 transitioning to the Control Hold Mode, the mobile station shall start
7 processing F-FCH and start transmitting on R-FCH at the action time of
8 the message. The mobile station shall establish the Fundamental
9 Channel with the same configuration as previously used.
10 • If REV_CFG_INCLUDED is equal to ‘1’, for all the (NUM_REV_CFG_RECS + 1)

11 occurrences of the reverse configuration record, the mobile station shall
12 store the REV_WALSH_ID matrix as follows:
13 – REV_WALSH_IDs[REV_SCH_IDr][REV_SCH_NUM_BITS_IDXr] =
14 REV_WALSH_IDr
15 • If NUM_REV_SCHr is not equal to ‘00’, then the mobile station set

16 PILOT_GATING_USE_RATE to ‘0’ and shall store the following information for
17 each occurrence of the record and process the Reverse Supplemental Burst
18 as specified in 2.6.6.2.5.1.2:
19 – REV_SCH_START_TIME_INCLs[REV_SCH_IDr] =
20 REV_SCH_START_TIME_INCLr
21 – If REV_SCH_START_TIME_INCLs[REV_SCH_IDr] is set to ‘1’, set

22 REV_SCH_START_TIMEs[REV_SCH_IDr] = REV_SCH_START_TIMEr
23 – REV_SCH_DURATIONs[REV_SCH_IDr] = REV_SCH_DURATIONr
24 – REV_SCH_NUM_BITS_IDXs[REV_SCH_IDr] = REV_SCH_NUM_BITS_IDXr
25 • If NUM_FOR_SCHr is not equal to ‘00’, then the mobile station shall set
26 PILOT_GATING_USE_RATE to ‘0’ and store the following information for each
27 occurrence of the record and process the Forward Supplemental Burst as
28 specified in 2.6.6.2.5.1.1:
29 – FOR_SCH_START_TIME_INCLs[FOR_SCH_IDr] =
30 FOR_SCH_START_TIME_INCLr
31 – If FOR_SCH_START_TIME_INCLs[FOR_SCH_IDr] is set to ‘1’, set

32 FOR_SCH_START_TIMEs[FOR_SCH_IDr] = FOR_SCH_START_TIMEr
33 – FOR_SCH_DURATIONs[FOR_SCH_IDr] = FOR_SCH_DURATIONr
34 – FOR_SCH_FER_REPs[FOR_SCH_IDr] = FOR_SCH_FER_REPr
35 – SCCL_INDEXs[FOR_SCH_IDr] = SCCL_INDEXr
36 • If FOR_CFG_INCLUDED is equal to ‘1’, the mobile station shall perform

37 the following:– Set FOR_SCH_FER_REPs to FOR_SCH_FER_REPr.
2-442
3GPP2 C.S0005-A v6.0
1 • If FOR_CFG_INCLUDED is equal to ‘1’, the mobile station shall perform the

2 following:
3 – Set FOR_SCH_FER_REPs to FOR_SCH_FER_REPr.
4 – If FOR_SCH_FER_REPr is equal to ‘0’, set SCH_TOT_FRAMESs and

5 SCH_BAD_FRAMESs to 0.
6 – Store NUM_FOR_CFG_RECS occurrences of Forward Supplemental

7 Channel Configuration associated with the identification of Forward
9 • For each record of the Forward Supplemental Channel Code list the mobile
10 station shall store the Forward Supplemental Channel Code list associated
11 with the FOR_SCH_IDr as follows:
12 – NUM_SUP_SHOs[FOR_SCH_IDr][SCCL_INDEXr] = NUM_SUP_SHOr.
13 – The mobile station shall determine,

14 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr], the number of
15 information bits per Forward Supplemental Channel frame identified by
16 FOR_SCH_ID and corresponding to the index SCCL_INDEX according to
18 + If FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is equal to ‘000’, then:
19 ο If USE_FLEX_NUM_BITSs is equal to '0' or if

21 FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr] is equal to ‘0000’, then
22 the mobile station shall set the number of information bits per
23 frame, N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr] and
25 FSCH_CRC_LEN_SETs[FOR_SCH_IDr][SCCL_INDEXr], according
26 to Table 3.7.3.3.2.37-2 using FOR_SCH_NUM_BITS_IDXr as the
28 ο If USE_FLEX_NUM_BITSs is equal to '1' and
29 FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr] is not equal to ‘0000’,
30 then the mobile station shall set the number of CRC bits per
31 frame, FSCH_CRC_LEN_SETs[FOR_SCH_IDr][SCCL_INDEXr],
33 CRC_LEN_IDXs[FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr]][FOR_SC
34 H_NUM_BITS_IDXr] as the index to the table.
35 The mobile station shall also set the number of information bits
36 per frame corresponding to SCCL_INDEXr,
38 NUM_BITSs[FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr]][FOR_SCH_N
39 UM_BITS_IDXr].
40 + If FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is not equal to ‘000’, then:
2-443
3GPP2 C.S0005-A v6.0
1 ο The mobile station shall set

2 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr], the set of indices to the
3 number of information bits per frame as follows:
4 ◊ If FOR_SCH_NUM_BITS_IDXr is equal to ‘0000’, then
7 ◊ otherwise the mobile station shall set (initialize)

10 FOR_SCH_NUM_BITS_IDXr the mobile station shall add
11 FOR_SCH_NUM_BITS_IDXr -
12 VAR_FSCH_RATE_OFFSETs[FOR_SCH_IDr][FOR_SCH_NUM_B
13 ITS_IDXr][i] to the set specified by
15 ο If USE_FLEX_NUM_BITSs is equal to '0' or if

17 FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr] is equal to ‘0000’, then
18 the mobile station shall set
19 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr], the set of
20 number of information bits per frame as follows.
th
22 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr] is obtained
th
23 using Table 3.7.3.3.2.37-2 and the i member of the set
24 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr] as the index to the table.
25 ο If USE_FLEX_NUM_BITSs is equal to '1' and

26 FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr] is not equal to ‘0000’,
27 then
28 ◊ the mobile station shall set

29 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr], the set of
30 number of information bits per frame as follows.
th
32 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr] is equal to
th
35 N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr][i] denotes the i
36 member of the set N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr]
37 and,
2-444
3GPP2 C.S0005-A v6.0
1 ◊ the mobile station shall set

2 FSCH_CRC_LEN_SETs[FOR_SCH_IDr][SCCL_INDEXr], the set
3 of number CRC bits per frame as follows.
th
5 FSCH_CRC_LEN_SETs[FOR_SCH_IDr][SCCL_INDEXr] using
6 Table 3.7.5.20-1 and
7 CRC_LEN_IDXs[FSCH_NBIT_TABLE_IDs[FOR_SCH_IDr]][N_FS
8 CH_BITS_IDX_SETs[FOR_SCH_IDr][i]] as the index to the
9 table, where N_FSCH_BITS_IDX_SETs[FOR_SCH_IDr][i]
th
10 denotes the i member of the set
th
12 – For the i record of the Forward Supplemental Channel Active Set (for all
13 values of i between 1 and NUM_SUP_SHO+1) specified in this message,
14 the mobile station shall store the following three entries corresponding to
15 the SCCL_INDEXr as follows:
16 + PILOT_PNs[FOR_SCH_IDr][SCCL_INDEXr][i] = PILOT_PNr,
17 + Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC_INCLr. If

19 following:
20 ο Set the PILOT_REC_TYPE field of PILOT_REC to
21 PILOT_REC_TYPEr.
22 ο If PILOT_REC_TYPEr equals ‘000’, the mobile station shall set the
25 ο If PILOT_REC_TYPEr is equal to ‘001’, the mobile station shall.

29 WALSH_LENGTHr.
30 ο If NGHBR_PILOT_REC_TYPEr is equal to ‘010’, the mobile station

31 shall:

35 WALSH_LENGTHr.

39 ο If PILOT_REC_TYPEr is equal to ‘011’, the mobile station shall:
2-445
3GPP2 C.S0005-A v6.0



7 ο If PILOT_REC_TYPEr is equal to ‘100’, the mobile station shall:




17 WALSH_LENGTHr.

22 by WALSH_LENGTH1r.
23 – Otherwise, set the AUX_PILOT_QOF1 field of PILOT_REC to

24 QOFr and set the AUX_PILOT_WALSH_CODE1 field of
25 PILOT_REC to AUX_PILOT_WALSHr with the Walsh Code
26 length specified by WALSH_LENGTHr.

31 by WALSH_LENGTH2r.
32 – Otherwise, set the AUX_PILOT_QOF2 field of PILOT_REC to

33 QOFr and set the AUX_PILOT_WALSH_CODE2 field of
34 PILOT_REC to AUX_PILOT_WALSHr with the Walsh Code
35 length specified by WALSH_LENGTHr.
36 + QOF_MASK_ID_SCHs[FOR_SCH_IDr][SCCL_INDEXr][i] =
37 QOF_MASK_ID_SCHr,
38 + FOR_SCH_CC_INDEXs[FOR_SCH_IDr][SCCL_INDEXr][i]=
39 CODE_CHAN_SCHr.
2-446
3GPP2 C.S0005-A v6.0
1 • The mobile station may soft-combine the Forward Supplemental Channel

2 frames received on the Forward Supplemental Channels in the same Forward
3 Supplemental Channel Active Set.
4 • If the mobile station supports any Radio Configuration greater than 2, the
6 – If FPC_INCLr is equal to ‘1’, the mobile station shall:
7 + Set FPC_MODE_SCHs to FPC_MODE_SCHr.
8 – If FPC_INCL is equal to ‘1’ and FPC_MODE is equal to '001', '010', ‘101’,

9 or ‘110’, the mobile station shall:
10 + Set FPC_SEC_CHANs to FPC_SEC_CHANr.
11 – If NUM_SUPr is included and not equal to ‘00’, for each Supplemental
12 Channel included in the message, the mobile station shall:
13 + Set SCH_IDs to SCH_IDr.
14 + Set FPC_SCH_FERs to FPC_SCH_FERr.
15 + Set FPC_SCH_INIT_SETPTs as follows:
16 ο If FPC_SCH_INIT_SETPT_OPr is set to ‘0’, set

17 FPC_SCH_INIT_SETPTs to FPC_SCH_INIT_SETPTr.
18 ο If FPC_SCH_INIT_SETPT_OPr is set to ‘1’:
19 ◊ If FPC_PRI_CHANr is equal to ‘0’, set FPC_SCH_INIT_SETPTs

20 to (FPC_FCH_CURR_SETPTs + FPC_SCH_INIT_SETPTr).
21 ◊ Otherwise, set FPC_SCH_INIT_SETPTs to

22 (FPC_DCCH_CURR_SETPTs + FPC_SCH_INIT_SETPTr).
23 + Set FPC_SCH_MIN_SETPTs to FPC_SCH_MIN_SETPTr.
24 + Set FPC_SCH_MAX_SETPTs to FPC_SCH_MAX_SETPTr.
25 – If FPC_THRESH_SCH_INCL is included and equal to ‘1’, the mobile

26 station shall set FPC_SETPT_THRESH_SCHs to SETPT_THRESH_SCHr.
27 • If RPC_INCL is equal to ‘1’, the mobile station shall set RLGAIN_SCH_PILOTs

28 to RLGAIN_SCH_PILOTr.
29 • If NUM_3X_CFGr is not equal to ‘00’, the mobile station shall store the
30 Forward 3X Supplemental Channel Configuration associated with the
31 identification of Forward Supplemental Channel (NUM_3X_CFGs =
32 NUM_3X_CFGr).
33 • For each 3X SCH record included in this message, the mobile station shall
34 update the Forward Supplemental Channel Code list associated with the
35 FOR_SCH_IDr as follows:
2-447
3GPP2 C.S0005-A v6.0
th
1 – For the i record of the Forward Supplemental Channel Active Set (for all
2 values of i between 1 and NUM_SUP_SHO+1) specified in this message,
3 the mobile station shall store the following three entries corresponding to
4 the SCCL_INDEXr as follows:
5 + If 3X_SCH_LOW_INCLr equals ‘1’, set

6 QOF_MASK_ID_SCH_LOW[FOR_SCH_IDr][SCCL_INDEXr][i] to
7 QOF_MASK_ID_SCH_LOWr and
8 FOR_SCH_CC_INDEX_LOW[FOR_SCH_IDr][SCCL_INDEXr][i] to
9 CODE_CHAN_SCH_LOWr. Otherwise, set
10 QOF_MASK_ID_SCH_LOW[FOR_SCH_IDr][SCCL_INDEXr][i] to
11 QOF_MASK_ID_SCH[FOR_SCH_IDr][SCCL_INDEXr][i] and
12 FOR_SCH_CC_INDEX_LOW[FOR_SCH_IDr][SCCL_INDEXr][i] to
13 CODE_CHAN_SCH[FOR_SCH_IDr][SCCL_INDEXr][i].
14 + If 3X_SCH_HIGH_INCLr equals ‘1’, set

15 QOF_MASK_ID_SCH_HIGH[FOR_SCH_IDr][SCCL_INDEXr][i] to
16 QOF_MASK_ID_SCH_HIGHr and
17 FOR_SCH_CC_INDEX_HIGH[FOR_SCH_IDr][SCCL_INDEXr][i] to
18 CODE_CHAN_SCH_HIGHr. Otherwise, set
19 QOF_MASK_ID_SCH_HIGH[FOR_SCH_IDr][SCCL_INDEXr][i] to
20 QOF_MASK_ID_SCH[FOR_SCH_IDr][SCCL_INDEXr][i] and
21 FOR_SCH_CC_INDEX_HIGH[FOR_SCH_IDr][SCCL_INDEXr][i] to
22 CODE_CHAN_SCH[FOR_SCH_IDr][SCCL_INDEXr][i].
23 • If PILOT_GATING_USE_RATE is set to ‘1’ and if NUM_REV_SCHr or
24 NUM_FOR_SCHr is not equal to ‘00’, the mobile station shall perform the
25 following:

27 start the continuous reverse pilot at the specified action time.

33 14. Forward Supplemental Channel Assignment Mini Message: The mobile station
34 shall process this message as follows:
37 configuration), if any of the mobile station’s forward supplemental channel
38 configuration parameters for the corresponding Supplemental Channel
39 (FOR_SCH_MUXs, FOR_SCH_RCs, FOR_SCH_CODINGs,
40 FOR_SCH_FRAME_LENGTHs, QOF_IDs for the corresponding SCCL_INDEXr, or
41 FOR_SCH_CC_INDEXs for the corresponding SCCL_INDEXr) is NULL.
42 Otherwise, the mobile station shall store the following information and process
2-448
3GPP2 C.S0005-A v6.0
1 the Forward Supplemental Burst as specified in 2.6.6.2.5.1.1:

2 • Set FOR_SCH_START_TIME_INCLs[FOR_SCH_IDr] to ‘1’
3 • FOR_SCH_START_TIMEs[FOR_SCH_IDr] = FOR_SCH_START_TIMEr
4 • FOR_SCH_DURATIONs[FOR_SCH_IDr] = FOR_SCH_DURATIONr
5 • SCCL_INDEXs[FOR_SCH_IDr] = SCCL_INDEXr
6 • If PILOT_GATING_USE_RATE is set to ‘1’, the mobile station shall perform

7 the following:


15 15. Reverse Supplemental Channel Assignment Mini Message: The mobile station shall
19 configuration), if any of the mobile station’s reverse supplemental channel
20 configuration parameters for the corresponding Supplemental Channel
21 (REV_SCH_MUXs, REV_SCH_RCs, REV_SCH_CODINGs, or
22 REV_SCH_FRAME_LENGTHs) is NULL.
23 If IGNORE_ESCAMs is equal to ‘1’, the mobile station shall not process the
24 Reverse Supplemental Channel assignment information in this message.
25 Otherwise, the mobile station shall store the following information and process
26 the Reverse Supplemental Burst as specified in 2.6.6.2.5.1.2:
27 • Set REV_SCH_START_TIME_INCLs[REV_SCH_IDr] to ‘1’
28 • REV_SCH_START_TIMEs[REV_SCH_IDr] = REV_SCH_START_TIMEr
29 • REV_SCH_DURATIONs[REV_SCH_IDr] = REV_SCH_DURATIONr
30 • REV_SCH_NUM_BITS_IDXs[REV_SCH_IDr] = REV_SCH_NUM_BITS_IDXr
31 • If PILOT_GATING_USE_RATE is set to ‘1’, the mobile station shall perform

32 the following:

2-449
3GPP2 C.S0005-A v6.0

6 2.6.6.2.5.1.1 Processing of the Forward Supplemental Burst Assignment
7 A Forward Supplemental Assignment specifies the explicit start time identified by

8 FOR_SCH_START_TIME or the implicit start time (if FOR_SCH_START_TIME_INCL is set to
9 ‘0’), FOR_SCH_DURATION, and SCCL_INDEX of a forward burst assignment. The time
10 interval of duration is specified by FOR_SCH_DURATION (see Table 3.7.3.3.2.37-3) and
11 starts at the time specified by the explicit start time FOR_SCH_START_TIME or the implicit
12 start time (if FOR_SCH_START_TIME_INCL is set to ‘0’). This time interval for a Forward
13 Supplemental Assignment is called the Forward Supplemental Assignment Interval. A
14 value of FOR_SCH_DURATION equal to '1111' indicates infinite duration. The variable
15 SCCL_INDEXs[FOR_SCH_ID] specifies the rate, QOF index and the Active Set for the
16 Forward Supplemental Channel identified by FOR_SCH_ID for a given Forward
17 Supplemental Assignment. A value of FOR_SCH_DURATION equal to '0000' indicates that
18 the mobile station should stop processing the forward Supplemental Channels at the
19 explicit start time specified by FOR_SCH_START_TIME or the implicit start time (if
20 FOR_SCH_START_TIME_INCL is set to ‘0’). The implicit start time is the time occurring no
21 later than the first 80 ms boundary (relative to System Time) which occurs at least 80 ms
22 after the end of the frame containing the last bit of the Extended Supplemental Channel
24 For each Forward Supplemental Assignment the mobile station shall determine the start
25 time for processing forward supplemental channel as the time for which the following
26 equation holds:
27 (t/(START_TIME_UNITs+1) − FOR_SCH_START_TIMEr) mod 32 = 0,
28 where t is the System Time in units of 20 ms.
29 Figure 2.6.6.2.5.1.1-1 illustrates the scenario in which a second Forward Supplemental

30 Assignment is received while the mobile station is processing the forward supplemental
31 channel according to a previously received assignment. Two cases are displayed in Figure
32 2.6.6.2.5.1.1-1: Case a) where the first assignment extends beyond the start time of the
33 second assignment and Case b) where the first assignment ends before the second one
34 starts.
35
2-450
3GPP2 C.S0005-A v6.0
Assignment 1
Assignment 2
time
Result
t1 t2 t3 t4
time
a) "Assignment 1" extends beyond the start time for "Assignment 2"
Assignment 1
Assignment 2
time Result
t1 t2 t3 t4 t5
time
b) "Assignment 1" ends prior to the start time of "Assignment 2"

1
2 Figure 2.6.6.2.5.1.1-1. New Supplemental Channel Assignment Received while a

3 Previous Supplemental Channel Assignment is in Progress
4 Figure 2.6.6.2.5.1.1-2 shows an example scenario in which the mobile station receives a
5 second Forward Supplemental Assignment before it starts processing the supplemental
6 channel according to the first assignment. In this case, the second assignment simply
7 replaces the first assignment.
8
Assignment 1
Assignment 2
Result
t1 t2 t3 t4 time
9 time
10 Figure 2.6.6.2.5.1.1-2. New Supplemental Channel Assignment Received before a

11 Previous Supplemental Channel Assignment starts
12 The mobile station shall set FPC_MODEs to FPC_MODE_SCHs at the
13 FOR_SCH_START_TIMEs of the forward Supplemental Channel assignment. The mobile
14 station shall set FPC_MODEs to FPC_MODE_NO_SCHs at the end of the forward
15 Supplemental Channel assignment.
2-451
3GPP2 C.S0005-A v6.0
1 For each Forward Supplemental Channel assignment corresponding to each Forward

2 Supplemental Channel (identified by FOR_SCH_ID), the mobile station should perform the
3 following:
4 • If FOR_SCH_DURATIONs[FOR_SCH_ID] is not equal to ‘0000’, then
5 – If the mobile station is currently processing the Forward Supplemental Channel

6 identified by FOR_SCH_ID, then the mobile station should continue processing
7 the Forward Supplemental Channel identified by FOR_SCH_ID according to the
8 Forward Supplemental Assignment previously received for the Forward
9 Supplemental Channel identified by FOR_SCH_ID up to the time specified by the
10 FOR_SCH_START_TIMEs[FOR_SCH_ID] (i.e., the mobile station should stop
11 processing the forward supplemental channel identified by FOR_SCH_ID at
12 either the time specified by FOR_SCH_START_TIMEs[FOR_SCH_ID], the start
13 time of the new assignment, or at the time the previously received assignment
14 ends, whichever time is earlier).
15 At the time specified by FOR_SCH_START_TIMEs[FOR_SCH_ID], the mobile
16 station should start processing the Forward Supplemental Channel identified by
17 FOR_SCH_ID for a duration of time specified by
18 FOR_SCH_DURATION[FOR_SCH_ID]s with the QOF index, the Supplemental
19 Channel Active Set indexed by SCCL_INDEXs[FOR_SCH_ID], and number of
20 information bits per frame (or set of number of bits per frame if
21 FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is not equal to ‘000’) specified by
22 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr].
23 If the set of number of bits per frame,

24 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr], has more than one member
25 and F_INC_RATE_ALLOWEDs is equal to ‘0’, then the following rule applies for
26 the duration of this assignment:
27 + Once the mobile station determines the forward Supplemental Channel

28 number of bits per frame, the number of bits per frame in the subsequent
29 Forward Supplemental Channel frames may be any member of the set
30 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr] which is smaller or equal
31 to the number of bits in the current frame.
32 – Otherwise, if the mobile station is not currently processing the Forward

33 Supplemental Channel identified by FOR_SCH_ID, then at the time specified by
34 FOR_SCH_START_TIMEs[FOR_SCH_ID], the mobile station should start
35 processing the Forward Supplemental Channel identified by FOR_SCH_ID for a
36 duration of time specified by FOR_SCH_DURATIONs[FOR_SCH_ID] with the QOF
37 index, the Supplemental Channel Active Set indexed by
38 SCCL_INDEXs[FOR_SCH_ID], and number of bits per frame (or set of number of
39 information bits per frame if FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is not equal
40 to ‘000’) specified by N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr].
2-452
3GPP2 C.S0005-A v6.0
1 If the set of number of bits per frame,

3 F_INC_RATE_ALLOWEDs is equal to ‘0’, has more than one member, then the
4 following rule applies for the duration of this assignment:
5 + Once the mobile station determines the forward Supplemental Channel

6 number of bits per frame, the number of bits per frame in the subsequent
7 Forward Supplemental Channel frames may be any member of the set
8 N_FSCH_BITS_SETs[FOR_SCH_IDr][SCCL_INDEXr] which is smaller or equal
9 to the number of bits in the current frame.
10 • If FOR_SCH_DURATIONs[FOR_SCH_ID] is equal to ‘0000’, the mobile station should
12 – If the mobile station is currently processing the Forward Supplemental Channel

13 identified by FOR_SCH_ID, then the mobile station should continue processing
14 the Forward Supplemental Channel identified by FOR_SCH_ID according to the
15 Forward Supplemental Assignment previously received for the Forward
16 Supplemental Channel identified by FOR_SCH_ID up to the time specified by the
17 implicit start time (FOR_SCH_START_TIME INCLs is set to ‘0’) or the explicit
18 start time (FOR_SCH_START_TIME INCLs is set to ‘1’) (i.e., the mobile station
19 should stop processing the forward supplemental channel identified by
20 FOR_SCH_ID at the time specified by the implicit start time or the explicit start
21 time, or at the time the previously received assignment ends, whichever time is
22 earlier). The mobile station should cancel the pending Forward Supplemental
23 Channel assignment if any.
24 + – If FOR_SCH_START_TIME INCLs is equal to ‘1’, the mobile station should
25 stop processing the Forward Supplemental Channel identified by
26 FOR_SCH_ID at the time specified by
27 FOR_SCH_START_TIMEs[FOR_SCH_ID].
28 + – If FOR_SCH_START_TIME INCLs is equal to ‘0’, the mobile station should

29 stop processing the Forward Supplemental Channel identified by
30 FOR_SCH_ID no later than the first 80 ms boundary (relative to System
31 Time) occurring at least 80 ms after the end of the frame containing the last
32 bit of the message.
33 – Otherwise, if the mobile station is not currently processing the Forward

34 Supplemental Channel identified by FOR_SCH_ID, the mobile station should
35 cancel the pending Forward Supplemental Channel assignment if any.
36 • If the PILOT_GATING_USE_RATE to equal to ‘0’, the mobile station shall start the
37 continuous reverse pilot at the specified action time.
38 2.6.6.2.5.1.2 Processing of the Reverse Supplemental Burst Assignment
39 A Reverse Supplemental Assignment specifies the explicit start time identified by

40 REV_SCH_START_TIME or the implicit start time (if REV_SCH_START_TIME_INCL is set to
41 ‘0’), REV_SCH_DURATION, and REV_SCH_NUM_BITS_IDX of a reverse burst assignment.
2-453
3GPP2 C.S0005-A v6.0
1 The time interval of duration is specified by REV_SCH_DURATION (see Table 3.7.3.3.2.37-3)

2 and starts at the time specified by the explicit start time REV_SCH_START_TIME or the
3 implicit start time (if REV_SCH_START_TIME_INCL is set to ‘0’). This time interval for a
4 Reverse Supplemental Assignment is called the reverse supplemental assignment interval.
5 A value of REV_SCH_DURATION equal to '1111' indicates infinite duration. A value of
6 REV_SCH_DURATION equal to '0000' indicates that the mobile station should stop
7 transmitting the reverse Supplemental Channels at the explicit start time specified by
8 REV_SCH_START_TIME or the implicit start time (if REV_SCH_START_TIME_INCL is set to
9 ‘0’). The implicit start time is the time occurring no later than the first 80 ms boundary
10 (relative to System Time) which occurs at least 80 ms after the end of the frame containing
11 the last bit of the Extended Supplemental Channel Assignment Message.
12 For each Reverse Supplemental Assignment the mobile station shall determine the start
13 time for processing reverse supplemental channel as the time for which the following
14 equation holds:
15 (t/(START_TIME_UNITs+1) − REV_SCH_START_TIMEr) mod 32 = 0,
17 Figure 2.6.6.2.5.1.1-1 illustrates the scenario in which a second Reverse Supplemental

18 Assignment is received while the mobile station is transmitting on the reverse supplemental
19 channel according to a previously received assignment. Two cases are displayed in Figure
20 2.6.6.2.5.1.1-1: Case a) where the first assignment extends beyond the start time of the
21 second assignment and Case b) where the first assignment ends before the second one
22 starts.
23 Figure 2.6.6.2.5.1.1-2 shows an example scenario in which the mobile station receives a
24 second Reverse Supplemental Assignment before it starts transmitting on the supplemental
25 channel according to the first assignment. In this case, the second assignment simply
26 replaces the first assignment.
27 For each Reverse Supplemental Channel assignment corresponding to each Reverse

28 Supplemental Channel (identified by REV_SCH_ID), the mobile station shall perform the
29 following:
30 • The mobile station shall determine, N_RSCH_BITSs[REV_SCH_IDr], the number of
31 information bits per Reverse Supplemental Channel frame identified by
32 REV_SCH_ID according to the following rules:
33 – If RSCH_VAR_TABLE_IDs[REV_SCH_IDr] is equal to ‘000’, then:
34 + If USE_FLEX_NUM_BITSs is equal to '0' or if USE_FLEX_NUM_BITSs is equal

35 to '1' and RSCH_NBIT_TABLE_IDs[REV_SCH_IDr] is equal to ‘0000’, then the
36 mobile station shall set the number of information bits per frame,
37 N_RSCH_BITS_SETs[REV_SCH_IDr] and number of CRC bits per frame,
38 RSCH_CRC_LEN_SETs[REV_SCH_IDr], according to Table 3.7.3.3.2.37-21
39 using REV_SCH_NUM_BITS_IDXr as the index to the table.
2-454
3GPP2 C.S0005-A v6.0
1 + If USE_FLEX_NUM_BITSs is equal to '1' and

2 RSCH_NBIT_TABLE_IDs[REV_SCH_IDr] is not equal to ‘0000’, then the
3 mobile station shall set the number of CRC bits per frame,
4 RSCH_CRC_LEN_SETs[REV_SCH_IDr], according to Table 3.7.5.20-1 using
5 CRC_LEN_IDXs[RSCH_NBIT_TABLE_IDs[REV_SCH_IDr]][REV_SCH_NUM_BIT
6 S_IDXr] as the index to the table. The mobile station shall also set the
7 number of information bits per frame, N_SCH_BITS_SETs[REV_SCH_IDr], to
8 NUM_BITSs[RSCH_NBIT_TABLE_IDs[REV_SCH_IDr]]
9 [REV_SCH_NUM_BITS_IDXr].
10 – If RSCH_VAR_TABLE_IDs[REV_SCH_IDr] is not equal to ‘000’, then:
11 + The mobile station shall set N_RSCH_BITS_IDX_SETs[REV_SCH_IDr], the set

12 of indices to the number of information bits per frame as follows:
13 ο If REV_SCH_NUM_BITS_IDXr is equal to ‘0000’, then
14 N_RSCH_BITS_IDX_SETs[REV_SCH_IDr] = {REV_SCH_NUM_BITS_IDXr},
15 ο otherwise, the mobile station shall set (initialize)

16 N_RSCH_BITS_IDX_SETs[REV_SCH_IDr] = { REV_SCH_NUM_BITS_IDXr },
17 and for i=1, …, REV_SCH_NUM_BITS_IDXr the mobile station shall add
18 REV_SCH_NUM_BITS_IDXr -
19 VAR_RSCH_RATE_OFFSETs[REV_SCH_IDr][REV_SCH_NUM_BITS_IDXr][i
20 ] to the set specified by N_RSCH_BITS_IDX_SETs[FOR_SCH_IDr]
21 + If USE_FLEX_NUM_BITSs is equal to '0' or if USE_FLEX_NUM_BITSs is equal

22 to '1' and RSCH_NBIT_TABLE_IDs[REV_SCH_IDr] is equal to ‘0000’, then the
23 mobile station shall determine N_RSCH_BITS_SETs[REV_SCH_IDr], the set of
th
24 number of information bits per frame as follows. The i member of the set
25 N_RSCH_BITS_SETs[REV_SCH_IDr] is obtained using Table 3.7.3.3.2.37-1
th
26 and the i member of the set N_RSCH_BITS_IDX_SETs[REV_SCH_IDr] as the
28 + If USE_FLEX_NUM_BITSs is equal to '1' and
29 RSCH_NBIT_TABLE_IDs[FOR_SCH_IDr] is not equal to ‘0000’, then
30 ο the mobile station shall set N_RSCH_BITS_SETs[REV_SCH_IDr], the set

31 of number of information bits per frame as follows.
th
32 The i member of the set N_RSCH_BITS_SETs[REV_SCH_IDr] is equal to
33 NUM_BITSs[SCH_NBIT_TABLE_IDs[REV_SCH_IDr]]
34 [N_RSCH_BITS_IDX_SETs[REV_SCH_IDr][i]], where
th
35 N_RSCH_BITS_IDX_SETs[REV_SCH_IDr][i] denotes the i member of the
36 set N_RSCH_BITS_IDX_SETs[REV_SCH_IDr].
2-455
3GPP2 C.S0005-A v6.0
1 ο the mobile station shall set RSCH_CRC_LEN_SETs[REV_SCH_IDr], the

th
3 The i member of the set RSCH_CRC_LEN_IDX_SETs[REV_SCH_IDr] is
4 equal to
5 CRC_LEN_IDXs[RSCH_NBIT_TABLE_IDs[REV_SCH_IDr]][N_RSCH_BITS_I
6 DX_SETs[REV_SCH_IDr][i]], where
th
7 N_RSCH_BITS_IDX_SETs[REV_SCH_IDr][i] denotes the i member of the
8 set N_RSCH_BITS_IDX_SETs[REV_SCH_IDr].
9 • If REV_SCH_DURATIONs[REV_SCH_ID] is not equal to ‘0000’, then
10 – If the mobile station is currently transmitting on the Reverse Supplemental

11 Channel identified by REV_SCH_ID, then the mobile station may continue
12 transmitting on the Reverse Supplemental Channel identified by REV_SCH_ID
13 with the Walsh cover specified by
14 REV_WALSH_IDs[REV_SCH_ID][REV_SCH_NUM_BITS_IDX[REV_SCH_IDr]]
15 according to the current Reverse Supplemental Assignment for the Reverse
16 Supplemental Channel identified by REV_SCH_ID up to the time specified by the
17 REV_SCH_START_TIMEs[REV_SCH_IDr] (i.e., the mobile station shall stop
18 transmitting on the reverse supplemental channel identified by REV_SCH_ID at
19 either the time specified by REV_SCH_START_TIMEs[REV_SCH_ID], the start
20 time of the new assignment, or at the time the previously received assignment
21 ends, whichever time is earlier).
22 At the time specified by REV_SCH_START_TIMES[REV_SCH_IDr], the mobile
23 station may start transmitting on the Reverse Supplemental Channel identified
24 by REV_SCH_ID with the Walsh cover specified by
25 REV_WALSH_IDs[REV_SCH_ID][REV_SCH_NUM_BITS_IDXs[REV_SCH_IDr]] and
26 and number of bits per frame (or set of number of information bits per frame if
27 RSCH_VAR_TABLE_IDs[REV_SCH_IDr] is not equal to ‘000’) specified by
28 N_RSCH_BITS_SETs[REV_SCH_IDr].
29 If the set of number of bits per frame, N_RSCH_BITS_SETs[REV_SCH_IDr], has

30 more than one member and R_INC_RATE_ALLOWEDs is equal to ‘0’, then the
31 following rule applies for the duration of this assignment:
32 + Once the mobile station transmits n number of bits per Reverse
33 Supplemental Channel specifies by REV_SCH_ID, where n is a member of the
34 set N_RSCH_BITS_SETs[REV_SCH_IDr], the mobile station shall not transmit
35 at a rate higher than the one specifies by n information bits per frame for the
36 duration of the assignment.
2-456
3GPP2 C.S0005-A v6.0
1 – If the mobile station is not currently transmitting on the Reverse Supplemental

2 Channel identified by REV_SCH_IDr, then at the time specified by
3 REV_SCH_START_TIMEs[REV_SCH_IDr], the mobile station may start
6 REV_WALSH_IDs[REV_SCH_ID][REV_SCH_NUM_BITS_IDXs[REV_SCH_IDr]] and
7 number of bits per frame (or set of number of information bits per frame if
8 RSCH_VAR_TABLE_IDs[REV_SCH_IDr] is not equal to ‘000’) specified by
9 N_RSCH_BITS_SETs[REV_SCH_IDr]. If the set of number of bits per frame,
10 N_RSCH_BITS_SETs[REV_SCH_IDr], has more than one member and
11 R_INC_RATE_ALLOWEDs is equal to ‘0’, then the following rule applies for the
12 duration of this assignment:
13 + Once the mobile station transmits n number of bits per Reverse
14 Supplemental Channel specifies by REV_SCH_ID, where n is a member of the
15 set N_RSCH_BITS_SETs[REV_SCH_IDr], the mobile station shall not transmit
16 at a rate higher than the one specifies by n information bits per frame for the
17 duration of the assignment.
18 • If REV_SCH_DURATIONs[REV_SCH_IDr] is equal to ‘0000’, the mobile station shall
19 perform the followings:
20 – If the mobile station is currently transmitting on the Reverse Supplemental

21 Channel identified by REV_SCH_ID, then the mobile station may continue
24 REV_WALSH_IDs[REV_SCH_ID][REV_SCH_NUM_BITS_IDX[REV_SCH_IDr]]
25 according to the current Reverse Supplemental Assignment for the Reverse
26 Supplemental Channel identified by REV_SCH_ID up to the time specified by the
27 implicit start time (if REV_START_TIME_INCLs is equal to ‘1’) or the explicit start
28 time (if REV_START_TIME_INCLs is equal to ‘1’) (i.e., the mobile station shall
29 stop transmitting on the reverse supplemental channel identified by
30 REV_SCH_ID at the implicit start time or the explicit start time, or at the time
31 the previously received assignment ends, whichever time is earlier). The mobile
32 station shall cancel the pending Reverse Supplemental Channel assignment if
33 any.
34 + – If REV_START_TIME_INCLs is equal to ‘1’, the mobile station shall stop
35 transmitting on the Reverse Supplemental Channel identified by
36 REV_SCH_IDr at the time specified by
37 REV_SCH_START_TIMEs[REV_SCH_IDr].
38 + – If REV_START_TIME_INCLs is equal to ‘0’, the mobile station shall stop

39 transmitting on the Reverse Supplemental Channel identified by
40 REV_SCH_IDr no later than the first 80 ms boundary (relative to System
41 Time) occurring at least 80 ms after the end of the frame containing the last
42 bit of the message.
2-457
3GPP2 C.S0005-A v6.0
1 – Otherwise, if the mobile is not currently transmitting on the Reverse

2 Supplemental Channel identified by REV_SCH_ID, the mobile station shall
3 cancel the pending Forward Supplemental Channel assignment if any.
4 • If the PILOT_GATING_USE_RATE to equal to ‘0’, the mobile station shall start the
5 continuous reverse pilot at the specified action time.
6 2.6.6.2.5.2 Processing of Reverse Traffic Channel Handoff Messages
7 The mobile station sends the following messages on the Reverse Traffic Channel in support
8 of handoff when its transmitter is enabled, following the receipt of a forward dedicated
9 channel acquired indication from Layer 2 (see 2.2.2.1.2 of [4]):
10 1. Pilot Strength Measurement Message or Extended Pilot Strength Measurement

11 Message: The mobile station shall send an autonomous Pilot Strength Measurement
12 Message if P_REV_IN_USE is less than seven or Extended Pilot Strength
13 Measurement Message if P_REV_IN_USE is equal to or greater than seven in assured
14 mode. The mobile station shall send either Pilot Strength Measurement Message or
15 Extended Pilot Strength Measurement Message containing measurements consistent
16 with the event whenever any of the following events occur:
17 • P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to
18 ‘000000’ and the strength of a Neighbor Set or Remaining Set pilot is found to be
19 above T_ADDs.
20 • P_REV_IN_USEs is greater than three, SOFT_SLOPEs is not equal to ‘000000’,

21 and the strength PS, as specified in 2.6.6.2.2, of any Candidate Set pilot is found
22 to satisfy the following inequality:
∑ PS i +
SOFT_SLOPE s ADD_INTERCEPT s
23 10 × log 10 PS > × 10 × log 10
8 2
i∈A
24 where the summation is performed over all pilots currently in the Active Set and
25 a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement
26 Message carrying this information has not been sent since the last Extended
27 Handoff Direction Message , General Handoff Direction Message or Universal
28 Handoff Direction Message was received.
30 and the strength PS, as specified in 2.6.6.2.2, of any Neighbor Set or Remaining
31 Set pilot is found to satisfy the following inequality:
SOFT_SLOPE s ADD_INTERCEPTs T_ADD s
32 10 × log10 PS > max( × 10 × log10 ∑ PS i + ,− )
8 i∈A 2 2
33 where the summation is performed over all pilots currently in the Active Set.
2-458
3GPP2 C.S0005-A v6.0
1 • P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to

2 ‘000000’, the strength of a Candidate Set pilot exceeds the strength of an Active
3 Set pilot by T_COMPs × 0.5 dB, and a Pilot Strength Measurement Message
4 carrying this information has not been sent since the last Extended Handoff
5 Direction Message, General Handoff Direction Message or Universal Handoff
6 Direction Message was received.
8 and the strength of a Candidate Set pilot exceeds the strength of an Active Set
9 pilot by T_COMPs × 0.5 dB and satisfies the following inequality:
∑ PS i +
10 10 × log 10 PS > × 10 × log 10
8 2
i∈A
11 where the summation is performed over all pilots currently in the Active Set and
12 a Pilot Strength Measurement Message or an Extended Pilot Strength Measurement
13 Message carrying this information has not been sent since the last Extended
14 Handoff Direction Message ,General Handoff Direction Message or Universal
15 Handoff Direction Message was received.
16 • The handoff drop timer of an Active Set pilot has expired and a Pilot Strength
17 Measurement Message or an Extended Pilot Strength Measurement Message
18 carrying this information has not been sent since the last Extended Handoff
19 Direction Message, General Handoff Direction Message, or Universal handoff
20 Direction Message was received.
21 2. Handoff Completion Message or Extended Handoff Completion Message: The mobile

22 station shall send a Handoff Completion Message if P_REV_IN_USE is less than
23 seven or an Extended Handoff Completion Message if P_REV_IN_USE is equal to or
24 greater than seven in assured mode as follows:
25 • If the handoff message (Extended Handoff Direction Message, General Handoff
26 Direction Message or Universal Handoff Direction Message) specifies a soft
27 handoff, the mobile station shall send the Handoff Completion Message if
28 P_REV_IN_USE is less than seven or an Extended Handoff Completion Message if
29 P_REV_IN_USE is equal to or greater than seven within T56m seconds after the
30 action time of the received handoff message.
31 • If the handoff message (Extended Handoff Direction Message, General Handoff

32 Direction Message or Universal Handoff Direction Message) specifies a hard
33 handoff without return on failure (see 2.6.6.2.8.1), the mobile station shall send
34 the Handoff Completion Message if P_REV_IN_USE is less than seven or an
35 Extended Handoff Completion Message if P_REV_IN_USE is equal to or greater
36 than seven within T73m seconds after the action time of the received handoff
37 message.
2-459
3GPP2 C.S0005-A v6.0
1 • If the handoff message (General Handoff Direction Message or Universal Handoff

2 Direction Message) specifies a hard handoff with return on failure (see
3 2.6.6.2.8.2), the mobile station shall send the Handoff Completion Message if
4 P_REV_IN_USE is less than seven or an Extended Handoff Completion Message if
5 P_REV_IN_USE is equal to or greater than seven within T56m seconds after
6 mobile station declares the handoff to be successful (see 2.6.6.2.8.2).
7 3. Candidate Frequency Search Report Message: The mobile station shall send a
8 Candidate Frequency Search Report Message in assured mode, whenever any of the
9 following events occur:
10 • RETURN_IF_HANDOFF_FAILs is equal to ‘1’, and a handoff attempt is
11 unsuccessful (see 2.6.6.2.8.2). In this case, the mobile station shall send a
12 Candidate Frequency Search Report Message within T56m seconds after
13 completing a search of all pilots in the Candidate Frequency Search Set and
14 resuming the use of the Serving Frequency Active Set (see 2.6.6.2.8.2.1).
15 • RETURN_IF_HANDOFF_FAILs is equal to ‘1’, an inter-frequency handoff attempt
16 is unsuccessful (see 2.6.6.2.8.2), and PERIODIC_SEARCHs is equal to ‘1’. In
17 this case, the mobile station shall send a Candidate Frequency Search Report
18 Message in a search period if the conditions specified in 2.6.6.2.8.3.2 are met.
19 • The mobile station receives a Candidate Frequency Search Request Message or a

20 Candidate Frequency Search Control Message with SEARCH_TYPE set to ‘01’. If
21 none of the conditions requiring the mobile station to send a Mobile Station
22 Reject Order is true (see 2.6.6.2.5.1), the mobile station shall send a Candidate
23 Frequency Search Report Message, as described in 2.6.6.2.8.3.1 and
24 2.6.6.2.10.1.
25 • The mobile station receives a Candidate Frequency Search Request Message or
26 Candidate Frequency Search Control Message with SEARCH_TYPE set to ‘11’,
27 SEARCH_MODEs is equal to ‘0000’ and the Candidate Frequency Search Set is
28 not empty. If none of the conditions requiring the mobile station to send a
29 Mobile Station Reject Order is true (see 2.6.6.2.5.1), the mobile station shall send
30 a Candidate Frequency Search Report Message in a search period if the
31 conditions specified in 2.6.6.2.8.3.2 are met.
32 • The mobile station receives a Candidate Frequency Search Request Message or
33 Candidate Frequency Search Control Message with SEARCH_TYPE set to ‘11’,
34 SEARCH_MODEs is equal to ‘0001’ and the Candidate Frequency Analog Search
35 Set is not empty. If none of the conditions requiring the mobile station to send a
36 Mobile Station Reject Order is true (see 2.6.6.2.5.1), the mobile station shall send
37 a Candidate Frequency Search Report Message in a search period if the
38 conditions specified in 2.6.6.2.10.2 are met.
39 4. Periodic Pilot Strength Measurement Message: The mobile station shall send a
40 Periodic Pilot Strength Measurement Message in unassured mode, as specified in
41 2.6.6.2.5.1 and 2.6.6.2.12.
42 5. Pilot Strength Measurement Mini Message: If the mobile station supports the Mobile
2-460
3GPP2 C.S0005-A v6.0
1 Assisted Burst operation capability, the mobile station shall send this message while
2 processing any Supplemental Channel, according to the following:
3 • The mobile station shall transmit a Pilot Strength Measurement Mini Message for
4 a pilot p in the Active Set on the r-dsch logical channel whenever all of the
5 following conditions are true:
6 – ORDER_FLAGs is equal to ‘1’.
7 – The pilot p in the Active Set has a received signal strength that is greater
8 than the signal strength of another pilot in the Active Set by
9 PS_MIN_DELTAs, in units of 0.5 dB, at the current time and has been for
10 ORDER_INTERVALs most recent successive 20 ms frame intervals since this
11 pilot was last reported in a rank order based Pilot Strength Measurement Mini
12 Message.
13 – The rank order of pilot p has changed.
14 • If PERIODIC_FLAGs is equal to ‘1’, the mobile station shall transmit a Pilot

15 Strength Measurement Mini Message within PERIODIC_INTERVALs 20 ms frame
16 intervals on the r-dsch for each of the n pilots in the Active Set with the largest
17 signal strengths, where n = (min (NUM_PILOTS, the number of pilots in the
18 Active Set)), whenever the following condition is true:
19 – The mobile station has not transmitted another Pilot Strength

20 Measurement Mini Message for the corresponding pilot during the last
21 PERIODIC_INTERVALs 20 ms frame intervals.
22 • If THRESHOLD_FLAGs is equal to ‘1’, the mobile station shall transmit a Pilot

23 Strength Measurement Mini Message for pilot p on the r-dsch logical channel
24 whenever all of the following conditions are true:
25 – The mobile station has not transmitted a previous Pilot Strength Measurement
26 Mini Message for pilot p within the most recent THRESHOLD_INTERVALs 20
27 ms frames intervals.
28 – Pilot p is in the Active Set.

29 – The signal strength of pilot p is greater than PS_CEILING_HIGHs and the
30 signal strength of pilot p was less than or equal to PS_CEILING_LOWs at any
31 time since the mobile station last sent a Pilot Strength Measurement Mini
32 Message for pilot p; or the signal strength of pilot p is less than
33 PS_FLOOR_LOWs and the signal strength for pilot p was greater than or
34 equal to PS_FLOOR_HIGHs at any time since the last time that the mobile
35 station sent a Pilot Strength Measurement Mini Message for pilot p.
36 2.6.6.2.6 Set Maintenance
37 2.6.6.2.6.1 Maintenance of the Active Set

38 The mobile station shall support a maximum Active Set size of N6m pilots. The mobile
39 station shall track the pilot strengths of all pilots in the Active Set.
2-461
3GPP2 C.S0005-A v6.0
1 When the mobile station is first assigned Forward Traffic Channels, the mobile station shall
2 initialize the Active Set to contain the pilots associated with the assigned Forward Traffic
3 Channels. When the mobile station processes an Extended Handoff Direction Message, a
4 General Handoff Direction Message or Universal Handoff Direction Message, then at the
5 action time of the message the mobile station shall replace the pilots in the Active Set with
6 the pilots listed in the message.
7 2.6.6.2.6.2 Maintenance of the Candidate Set

8 The mobile station shall support a maximum Candidate Set size of N7m pilots.
9 When the mobile station is first assigned a Forward Traffic Channel, the mobile station
10 shall initialize the Candidate Set to contain no pilots. The mobile station shall adjust the
11 Candidate Set whenever any of the following events occur:
12 • If the mobile station detects that the strength of a Neighbor Set pilot or a Remaining
13 Set pilot exceeds T_ADDs, the mobile station shall add the pilot to the Candidate
14 Set.
15 • If the mobile station processes an Extended Handoff Direction Message, a General
16 Handoff Direction Message or a Universal Handoff Direction Message which does not
17 list a pilot in the current Active Set, and the handoff drop timer corresponding to
18 that pilot has not expired at the action time of the message, the mobile station shall
19 add the pilot to the Candidate Set at the action time of the message.
20 • If P_REV_IN_USEs is greater than three, and SOFT_SLOPEs is not equal to ‘000000’,
21 the mobile station shall perform the following: If the mobile station processes a
22 General Handoff Direction Message or a Universal Handoff Direction Message which
23 does not list a pilot in the current Active Set, the handoff drop timer corresponding
24 to that pilot has expired at the action time of the message, and that pilot is found to
25 be above T_DROPs, the mobile station shall add the pilot to the Candidate Set at the
28 Handoff Direction Message or Universal Handoff Direction Message, which lists a
29 pilot in the current Candidate Set, the mobile station shall delete the pilot from the
30 Candidate Set at the action time of the message.
31 • If the handoff drop timer corresponding to a Candidate Set pilot expires, the mobile
32 station shall delete the pilot from the Candidate Set.
33 • If the mobile station adds a pilot to the Candidate Set, and the resulting Candidate
34 Set size exceeds N7m, the mobile station shall delete from the Candidate Set the
35 pilot whose handoff drop timer is closest to expiration. If more than one such pilot
36 exists, the mobile station shall delete one such pilot that has the lowest strength. If
37 no pilot in the Candidate Set has an enabled handoff drop timer, the mobile station
38 shall delete from the Candidate Set the pilot that has the lowest strength.
39 2.6.6.2.6.3 Maintenance of the Neighbor Set

40 The mobile station shall support a Neighbor Set size of at least N8m pilots.
2-462
3GPP2 C.S0005-A v6.0
1 When the mobile station is first assigned a Forward Traffic Channel, the mobile station
2 shall initialize the Neighbor Set to contain all the pilots specified in the most recently
3 received Neighbor List Message, Extended Neighbor List Message or General Neighbor List
4 Message.
5 The mobile station shall maintain a counter, AGEs, for each pilot in the Neighbor Set. The
6 mobile station shall initialize this counter to zero when it moves the pilot from the Active
7 Set or the Candidate Set to the Neighbor Set. The mobile station shall initialize this
8 counter to NGHBR_MAX_AGEs when it moves the pilot from the Remaining Set to the
9 Neighbor Set. The mobile station shall increment AGEs for each pilot in the Neighbor Set
10 upon receipt of a Neighbor List Update Message or an Extended Neighbor List Update
11 Message. When the mobile station is first assigned to a Forward Traffic Channel, the
12 mobile station shall set AGEs for each pilot in the Neighbor Set to NGHBR_MAX_AGEs.
13 The mobile station shall adjust the Neighbor Set whenever any of the following events
14 occur:
15 • If the mobile station receives a Neighbor List Update Message or an Extended

16 Neighbor List Update Message, it shall perform the following:
17 – Increment AGEs for each pilot in the Neighbor Set.
18 – Delete from the Neighbor Set all pilots whose AGEs exceeds NGHBR_MAX_AGEs.
19 – Add to the Neighbor Set each pilot named in the message, if it is not already a
20 pilot of the Active Set, Candidate Set, or Neighbor Set. If the mobile station can
21 store in the Neighbor Set only k additional pilots, and more than k new pilots
22 were sent in the Neighbor List Update Message or the Extended Neighbor List
23 Update Message, the mobile station shall store the first k new pilots listed in the
24 message.
25 • If the handoff drop timer of a pilot in the Candidate Set expires, the mobile station
26 shall add the pilot to the Neighbor Set.
27 • If P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to
28 ‘000000’, the mobile station shall perform the following: If the mobile station
29 processes an Extended Handoff Direction Message, a General Handoff Direction
30 Message, or a Universal Handoff Direction Message in which a pilot in the Active Set
31 is not listed, and the handoff drop timer corresponding to the pilot has expired, the
32 mobile station shall add the pilot to the Neighbor Set.
33 • If P_REV_IN_USEs is greater than three, and SOFT_SLOPEs is not equal to ‘000000’,
34 the mobile station shall perform the following: If the mobile station processes an
35 Extended Handoff Direction Message, a General Handoff Direction Message, or a
36 Universal Handoff Direction Message which does not list a pilot in the current Active
37 Set, the handoff drop timer corresponding to that pilot has expired, and that pilot is
38 found to be below T_DROPs, the mobile station shall add the pilot to the Neighbor
39 Set.
2-463
3GPP2 C.S0005-A v6.0
1 • If the mobile station adds a pilot to the Candidate Set, and the resulting Candidate
2 Set size exceeds the size supported by the mobile station, the mobile station shall
3 add the deleted Candidate Set pilot to the Neighbor Set (see 2.6.6.2.6.2).
4 • If the mobile station detects that the strength of a Neighbor Set pilot exceeds
5 T_ADDs, the mobile station shall delete the pilot from the Neighbor Set.

7 Handoff Direction Message or a Universal Handoff Direction Message which lists a
8 pilot in the current Neighbor Set, the mobile station shall delete the pilot from the
9 Neighbor Set.
10 • If the mobile station adds a pilot to the Neighbor Set, and the resulting Neighbor Set
11 size exceeds the size supported by the mobile station, the mobile station shall delete
12 from the Neighbor Set the pilot whose AGEs is the largest. If more than one such
13 pilot exists, the mobile station shall delete one such pilot that has the lowest
14 strength.
15 2.6.6.2.7 Soft Handoff
16 2.6.6.2.7.1 Forward Traffic Channel Processing
17 All Forward Traffic Channels associated with pilots in the Active Set of the mobile station
18 carry identical modulation symbols with the exception of the power control subchannel (see
19 [2]).
20 When the Active Set contains more than one pilot, the mobile station should provide
21 diversity combining of the associated Forward Traffic Channels. The mobile station shall
22 provide for differential propagation delays from zero to at least 150 µs.
23 2.6.6.2.7.2 Reverse Traffic Channel Power Control During Soft Handoff
24 The Extended Handoff Direction Message, a General Handoff Direction Message or a

25 Universal Handoff Direction Message identifies sets of Forward Fundamental Code Channels
26 or Forward Dedicated Control Channels that carry identical closed loop power control
27 subchannels. A set consists of one or more Forward Fundamental Code Channels or
28 Forward Dedicated Control Channels with identical power control information.
29 In each power control group containing valid power control bits (see [2]), the mobile station
30 should provide diversity combining of the identical closed loop power control subchannels
31 and shall obtain at most one power control bit from each set of identical closed loop power
32 control subchannels. The mobile station should only combine reliable power control bits
33 (see 9.3.8 of [11]) as follows:
34 • If the reliable power control bits obtained from all sets are equal to ‘0’, the mobile
35 station shall increase its power as specified in [2].
36 • If the reliable power control bit obtained from any set is equal to ‘1’, the mobile
37 station shall decrease its power as specified in [2].
2-464
3GPP2 C.S0005-A v6.0
1 2.6.6.2.7.3 Starting Periodic Search following Soft Handoff

2 If the PERIODIC SEARCHs is equal to ‘1’, a periodic search is not already in progress, and
3 the Frequency Assignment after handoff is different from the Candidate Frequency
4 (CDMABANDs is not equal to CF_CDMABANDs or CDMACHs is not equal to CF_CDMACHs),
5 the mobile station shall do the following:
6 • The mobile station shall set ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs to
7 ‘000000’.
8 • The mobile station shall start a periodic search as described in 2.6.6.2.8.3.2.
9 2.6.6.2.8 CDMA-to-CDMA Hard Handoff
10 The base station directs the mobile station to perform a CDMA-to-CDMA hard handoff by
11 sending an Extended Handoff Direction Message, a General Handoff Direction Message or a
12 Universal Handoff Direction Message in which the mobile station is transitioned between
13 disjoint sets of base stations, different Frequency Assignments, or different frame offsets. If
14 RETURN_IF_HANDOFF_FAILs is equal to ‘0’, the mobile station performs the actions
15 described in 2.6.6.2.8.1. If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, the mobile station
16 performs the actions described in 2.6.6.2.8.2.
17 2.6.6.2.8.1 Hard Handoff without Return on Failure

18 At the action time specified in the Extended Handoff Direction Message, the General Handoff
19 Direction Message or Universal Handoff Direction Message the mobile station shall disable
20 its transmitter, reset the fade timer specified in 2.6.4.1.8, suspend incrementing
21 TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs, and DCCH_BAD_FRAMESs if
22 applicable as specified in 2.6.4.1.1, and tune to the assigned Forward Traffic Channel. The
23 mobile station shall perform acquisition of the pilots in the new Active Set.
24 If a periodic Serving Frequency pilot report procedure is in progress, the mobile station
25 shall abort it (see 2.6.6.2.12).
26 The mobile station shall begin monitoring the assigned Forward Traffic Channel within the
27 time specified below:
28 • If the Extended Handoff Direction Message, General Handoff Direction Message or
29 Universal Handoff Direction Message specifies a CDMA Frequency Assignment
30 different from the Serving Frequency and an Active Set containing pilots with pilot
31 PN sequence offsets identical to those of the pilots in the Serving Frequency Active
32 Set, the mobile station shall begin monitoring the assigned Forward Traffic Channel
33 within T60m seconds after the action time.

35 Universal Handoff Direction Message specifies a CDMA Frequency Assignment
36 different from the Serving Frequency and an Active Set containing a pilot with pilot
37 PN sequence offset not equal to that of any pilot in the Serving Frequency Active Set,
38 the mobile station shall begin monitoring the assigned Forward Traffic Channel
39 within T61m seconds after the action time.
2-465
3GPP2 C.S0005-A v6.0

2 Universal Handoff Direction Message specifies a CDMA-to-CDMA hard handoff
3 without changing the CDMA Frequency Assignment, the mobile station shall begin
4 monitoring the assigned Forward Traffic Channel within T62m seconds after the
5 action time.
6 If the Target Frequency is the same as the Candidate Frequency (TF_CDMABANDs is equal
7 to CF_CDMABANDs, and TF_CDMACHs is equal to CF_CDMACHs) and is different from the
8 Serving Frequency (TF_CDMABANDs is not equal to SF_CDMABANDs, or TF_CDMACHs is
9 not equal to SF_CDMACHs), the mobile station shall perform the following:
10 • If applicable, the mobile station shall replace its Neighbor Set with its Candidate
11 Frequency Neighbor Set, excluding the pilots in its Active Set. When the mobile
12 station adds a pilot from its Candidate Frequency Neighbor Set to its Active Set, it
13 shall maintain SEARCH_PRIORITYs, SRCH_WIN_NGHBRs, and
14 SRCH_OFFSET_NGHBRs associated with the pilot.
15 • The mobile station shall set PILOT_INCs to CF_PILOT_INCs, SRCH_WIN_Ns to

16 CF_SRCH_WIN_Ns, and SRCH_WIN_Rs to CF_SRCH_WIN_Rs.
17 • The mobile station shall set SEARCH_PRIORITY_INCLs to

18 CF_SEARCH_PRIORITY_INCLs, SRCH_OFFSET_INCLs to CF_SRCH_OFFSET_INCLs,
19 and SRCH_WIN_NGHBR_INCLs to CF_SRCH_WIN_NGHBR_INCLs.
20 After the action time, upon receiving a period of (N11m × 20) ms with sufficient signal
21 quality (e.g. good frames) on the physical channel corresponding to FPC_PRI_CHANs on the
22 assigned Forward Traffic Channel, the mobile station shall re-enable its transmitter. The
23 mobile station shall transmit the Traffic Channel Preamble, as described in 2.1.3.6.2.3 of
24 [2], followed by a Handoff Completion Message or Extended Handoff Completion Message.
25 After the action time, upon receiving a period of (N3m × 20) ms with sufficient signal quality
26 (e.g. good frames) on the physical channel corresponding to FPC_PRI_CHANs, the mobile
27 station shall resume incrementing TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs,
28 and DCCH_BAD_FRAMESs if applicable as specified in 2.6.4.1.1.
29 If the PERIODIC SEARCHs is equal to ‘1’, a periodic search is not already in progress, and
30 the Frequency Assignment after handoff is different from the Candidate Frequency
31 (CDMABANDs is not equal to CF_CDMABANDs or CDMACHs is not equal to CF_CDMACHs),
33 • The mobile station shall set ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs to
34 ‘000000’.
35 • The mobile station shall start a periodic search as described in 2.6.6.2.8.3.2.
36 2.6.6.2.8.2 Hard Handoff with Return on Failure

37 At the action time specified in the General Handoff Direction Message or Universal Handoff
38 Direction Message, the mobile station shall do the following:
2-466
3GPP2 C.S0005-A v6.0
1 • The mobile station shall stop processing the Forward Fundamental Code Channel,
2 the Forward Dedicated Control Channel, the Forward Supplemental Code Channels
3 (if any), and the Forward Supplemental Channels (if any).
4 • The mobile station shall stop transmitting on the Reverse Fundamental Code
5 Channel, on the Reverse Dedicated Control Channel, and on the Reverse
6 Supplemental Code Channels (if any), and on the Reverse Supplemental Channels (if
7 any).
8 • The mobile station shall disable the fade timer (see 2.6.4.1.8) and the handoff drop
9 timers corresponding to the Serving Frequency Active Set and Candidate Set (see
10 2.6.6.2.3), and shall suspend incrementing TOT_FRAMESs, BAD_FRAMESs,
11 DCCH_TOT_FRAMESs, and DCCH_BAD_FRAMESs if applicable (see 2.6.4.1.1).
12 • The mobile station shall lock the accumulation of valid level changes in the closed
13 loop mean output power and shall ignore received power control bits related to the
14 period that the transmitter is disabled (see 2.1.2.3.2 of [2]).
15 • If the Serving Frequency is different from the Target Frequency (SF_CDMACHs is not
16 equal to TF_CDMACHs or SF_CDMABANDs is not equal to TF_CDMABANDs), the
17 mobile station shall set CDMACHs to TF_CDMACHs and CDMABANDs to
18 TF_CDMABANDs, and shall tune to the Target Frequency.
19 The mobile station shall not change its time reference (see 2.1.5 of [2]) until the handoff is
20 successfully completed (as described later in this section) or the mobile station resumes
21 using the Serving Frequency Active Set (as described in 2.6.6.2.8.2.1).
22 The mobile station shall maintain a handoff timer. The mobile station shall set the
23 expiration time for the handoff timer to (0.08 × TF_WAIT_TIMEs) seconds and enable the
24 timer at the action time of the General Handoff Direction Message or Universal Handoff
25 Direction Message.

27 • If the Target Frequency is different from the Serving Frequency (TF_CDMABANDs is
28 not equal to SF_CDMABANDs, or TF_CDMACHs is not equal to SF_CDMACHs), the
29 mobile station shall measure the mean input power on the Target Frequency
30 (target_freq_pwr, in dBm/1.23 MHz) and may use target_freq_pwr along with the
31 measurement of the average input power on the Serving Frequency
32 (avg_serving_freq_pwr, in dBm/1.23 MHz) in the handoff procedure. The mobile
33 station may declare the handoff attempt to be unsuccessful if all of the following
34 conditions are true:
35 – DIFF_RX_PWR_THRESHs is not equal to ‘00000’,
36 – the mobile station has been measuring the received power on the Serving
37 Frequency for at least the last N12m frames, and
38 – (target_freq_pwr - avg_serving_freq_pwr) is less than (-30 + 2 ×

39 DIFF_RX_PWR_THRESHs) dB.
2-467
3GPP2 C.S0005-A v6.0
1 If the mobile station declares the handoff attempt to be unsuccessful, it shall restore
2 the configuration to what it was before the handoff attempt (see 2.6.6.2.5.1) and
3 send a Candidate Frequency Search Report Message as described in 2.6.6.2.8.2.1.
4 • The mobile station shall measure Ec/Io for each pilot in the Active Set using the
5 procedures specified in 2.6.6.2.2, if any of the following conditions is true:
6 – the Target Frequency is the same as the Serving Frequency (TF_CDMABANDs is
7 equal to SF_CDMABANDs, and TF_CDMACHs is equal to SF_CDMACHs),
8 – the mobile station does not use the power measurements in the handoff
9 procedure,
10 – DIFF_RX_PWR_THRESHs is equal to ‘00000’,
11 – the mobile station has not been measuring the received power on the Serving
12 Frequency for at least the last N12m frames, or
13 – (target_freq_pwr - avg_servng_freq_pwr) is not less than (-30 + 2 ×

14 DIFF_RX_PWR_THRESHs) dB.
15 If the mobile station measures Ec/Io for pilots in the Active Set, it shall compare the
16 sum of the measured Ec/Io for all pilots with the minimum total pilot Ec/Io
17 threshold (MIN_TOTAL_PILOT_EC_IOs).
18 – If MIN_TOTAL_PILOT_EC_IOs is not equal to ‘00000’, and (-20 × log10

19 (Ec/Io)total) is less greater than MIN_TOTAL_PILOT_EC_IOs, where (Ec/Io)total is
20 the sum of the measured Ec/Io for the pilots in the Active Set, the mobile station
21 shall declare the handoff attempt to be unsuccessful, and shall do the following:
22 + If COMPLETE_SEARCHs is equal to ‘1’, and the Target Frequency is the same
23 as the Candidate Frequency (TF_CDMABANDs is equal to CF_CDMABANDs,
24 and TF_CDMACHs is equal to CF_CDMACHs) and is different from the
25 Serving Frequency (TF_CDMABANDs is not equal to SF_CDMABANDs, or
26 TF_CDMACHs is not equal to SF_CDMACHs), the mobile station shall
27 measure the strength of each pilot in its Candidate Frequency Search Set
28 using the procedures specified in 2.6.6.2.2; otherwise, the mobile station
29 shall end the search.
30 + Otherwise, the mobile station shall end the search.
31 + The mobile station shall then restore its configuration to what it was before
32 the handoff attempt (see 2.6.6.2.5.1) and send a Candidate Frequency Search
33 Report Message as described in 2.6.6.2.8.2.1.
34 –The mobile station shall then restore its configuration to what it was before the
35 handoff attempt (see 2.6.6.2.5.1) and send a Candidate Frequency Search Report
36 Message as described in 2.6.6.2.8.2.1.
2-468
3GPP2 C.S0005-A v6.0
1 – If MIN_TOTAL_PILOT_EC_IOs is equal to ‘00000’, or ( - 20 × log10 (Ec/Io)total) is

2 not less than MIN_TOTAL_PILOT_EC_IOs, where (Ec/Io)total is the sum of the
3 measured Ec/Io for the pilots in the Active Set, the mobile station shall attempt
4 to demodulate the Forward Traffic Channel(s). If the Active Set contains more
5 than one pilot, the mobile station shall perform the actions specified in
6 2.6.6.2.7. If the Target Frequency is the same as the Candidate Frequency
7 (TF_CDMABANDs is equal to CF_CDMABANDs, and TF_CDMACHs is equal to
8 CF_CDMACHs), and is different for from the Serving Frequency
9 (TF_CDMABANDs is not equal to SF_CDMABANDs, or TF_CDMACHs is not equal
10 to SF_CDMACHs), the mobile station shall measure the strength of each pilot in
11 its Candidate Frequency Search Set using the procedures specified in 2.6.6.2.2,
12 and wait to receive a period of (N11m × 20) ms with sufficient signal quality (e.g.
13 good frames) on the physical channel corresponding to FPC_PRI_CHANs. The
14 mobile station shall wait for the first of the following events to occur:
15 + The handoff timer expires and the mobile station has not received a period of
16 (N11m × 20) ms with sufficient signal quality (e.g. good frames) on the
17 physical channel corresponding to FPC_PRI_CHANs. In this case, the mobile
18 station shall declare the handoff attempt to be unsuccessful, and do the
19 following:
20 ο If COMPLETE_SEARCHs is equal to ‘1’, and if the Target Frequency is the
21 same as the Candidate Frequency (TF_CDMABANDs is equal to
22 CF_CDMABANDs, and TF_CDMACHs is equal to CF_CDMACHs) and is
23 different from the Serving Frequency (TF_CDMABANDs is not equal to
24 SF_CDMABANDs, or TF_CDMACHs is not equal to SF_CDMACHs), and
25 the mobile station has not completed the search of all pilots in its
26 Candidate Frequency Search Set, then it shall complete the search, i.e.,
27 it shall obtain at least one measurement of the strength of each pilot in
28 its Candidate Frequency Search Set, using the search procedures
29 specified in 2.6.6.2.8.3.
30 ο Otherwise, the mobile station shall end the search.
31 The mobile station shall then restore its configuration to what it was before
32 the handoff attempt (see 2.6.6.2.5.1) and send a Candidate Frequency Search
33 Report Message as described in 2.6.6.2.8.2.1.
34 + The mobile station receives a period of (N11m × 20) ms with sufficient signal
35 quality (e.g. good frames) on the physical channel corresponding to
36 FPC_PRI_CHANs. In this case, the mobile station shall declare the handoff
37 attempt to be successful, and do the following:
38 ο The mobile station shall disable the handoff timer.

39 ο If TF_RESET_L2s is equal to ‘1’, Layer 3 shall send a L2-
40 Supervision.Request primitive to Layer 2 to reset the acknowledgment
41 procedures as specified in 2.2.1.1 and 2.2.2.1 of [4].
2-469
3GPP2 C.S0005-A v6.0
1 ο If TF_RESET_FPCs is equal to ‘1’, the mobile station shall initialize the

2 Forward Traffic Channel power control counters as specified in
3 2.6.4.1.1.1.
4 ο If the Target Frequency is the same as the Candidate Frequency

5 (TF_CDMABANDs is equal to CF_CDMABANDs, and TF_CDMACHs is
6 equal to CF_CDMACHs) and is different from the Serving Frequency
7 (TF_CDMABANDs is not equal to SF_CDMABANDs, or TF_CDMACHs is
8 not equal to SF_CDMACHs), the mobile station shall do the following:
9 ◊ If applicable, The the mobile station shall replace its Neighbor Set
10 with its Candidate Frequency Neighbor Set, excluding the pilots in its
11 Active Set. When the mobile station adds a pilot from its Candidate
12 Frequency Neighbor Set to its Active Set, it shall maintain
13 SEARCH_PRIORITYs, SRCH_WIN_NGHBRs, and
14 SRCH_OFFSET_NGHBRs associated with the pilot.
15 ◊ The mobile station shall set PILOT_INCs to CF_PILOT_INCs,

16 SRCH_WIN_Ns to CF_SRCH_WIN_Ns, and SRCH_WIN_Rs to
17 CF_SRCH_WIN_Rs.
18 ◊ The mobile station shall set SEARCH_PRIORITY_INCLs to

19 CF_SEARCH_PRIORITY_INCLs, SRCH_OFFSET_INCLs to
20 CF_SRCH_OFFSET_INCLs, and SRCH_WIN_NGHBR_INCLs to
21 CF_SRCH_WIN_NGHBR_INCLs.
22 ο The mobile station shall re-enable its transmitter and shall re-enable the
23 fade timer (see 2.6.4.1.8) and reset it for T5m seconds. Then, the mobile
24 station shall transmit the Traffic Channel Preamble, as described in
25 2.1.3.6.2.3 of [2], followed by a Handoff Completion Message if
26 P_REV_IN_USE is less than seven or an Extended Handoff Completion
27 Message if P_REV_IN_USE is equal to or greater than seven.
28 ο After starting the handoff timer, upon receiving the first period of (N3m ×
29 20) ms with sufficient signal quality (e.g. good frames) on the physical
30 channel corresponding to FPC_PRI_CHANs, the mobile station shall
31 resume incrementing TOT_FRAMESs, BAD_FRAMESs,
32 DCCH_TOT_FRAMESs, and DCCH_BAD_FRAMESs if applicable as
34 ο If the Target Frequency is same as the Candidate Frequency

35 (TF_CDMABANDs is equal to CF_CDMABANDs and TF_CDMACHs is
36 equal to CF_CDMACHs), then the mobile station shall set
38 ο If PERIODIC_SEARCHs is equal to ‘1’, the mobile station shall do the

39 following:
40 ◊ The mobile station shall set ALIGN_TIMING_USEDs to ‘0’ and
41 SEARCH_OFFSETs to ‘000000’.
2-470
3GPP2 C.S0005-A v6.0
1 ◊ The mobile station shall start a periodic search as described in

2 2.6.6.2.8.3.2.
3 ο The mobile station shall maintain its pilot sets using the procedures
4 described in 2.6.6.2.6.
5 2.6.6.2.8.2.1 Restoring the Configuration
6 If the mobile station declares a handoff attempt to be unsuccessful (see 2.6.6.2.8.2), it shall
8 • If the handoff timer is enabled, the mobile station shall disable it.
9 • The mobile station shall restore the following parameters:

10 – Message encryption mode: If SF_ENCRYPT_MODEs is equal to ‘0’, the mobile
11 station shall turn off message encryption; otherwise, it shall turn on message
12 encryption.
13 – Service configuration: The mobile station shall use the service configuration
14 stored in SF_SERVICE_CONFIGs to process Forward and Reverse Traffic
15 Channel frames.
16 – The mobile station shall restore the list of calls stored in SF_CALLSs.
17 – Protocol revision level (P_REVs = SF_P_REVs)
18 – Protocol revision level in use on the serving frequency (P_REV_IN_USEs =

19 SF_P_REV_IN_USEs)
20 – Service negotiation type (SERV_NEGs = SF_SERV_NEGs)
21 – Long code mask: If SF_PRIVATE_LCMs is equal to ‘1’, the mobile station shall
22 use the private long code mask; otherwise, it shall use the public long code
23 mask.
24 – Search window size for the Active Set and Candidate Set
25 (SRCH_WIN_As = SF_SRCH_WIN_As)
26 – Search window size for the Neighbor Set

27 (SRCH_WIN_Ns = SF_SRCH_WIN_Ns)
28 – Search window size for the Remaining Set

29 (SRCH_WIN_Rs = SF_SRCH_WIN_Rs)
30 – Pilot detection threshold (T_ADDs = SF_T_ADDs)
31 – Pilot drop threshold (T_DROPs = SF_T_DROPs)
32 – Soft slope for the dynamic add and drop threshold (SOFT_SLOPEs =
33 SF_SOFT_SLOPEs)
34 – Intercept for the dynamic add threshold (ADD_INTERCEPTs =

35 SF_ADD_INTERCEPTs)
36 – Intercept for the dynamic drop threshold (DROP_INTERCEPTs =

37 SF_DROP_INTERCEPTs)
2-471
3GPP2 C.S0005-A v6.0
1 – Active Set versus Candidate Set comparison threshold (T_COMPs =

2 SF_T_COMPs)
3 – Drop timer value (T_TDROPs = SF_T_TDROPs)
4 – Frame offset (FRAME_OFFSETs = SF_FRAME_OFFSETs)
5 – Nominal power setting (NOM_PWRs = SF_NOM_PWRs)
6 – Extended nominal power setting (NOM_PWR_EXTs = SF_NOM_PWR_EXTs)
7 – Power control step (PWR_CNTL_STEPs = SF_PWR_CNTL_STEPs)
8 – CDMA band class (CDMABANDs = SF_CDMABANDs)
9 – Frequency assignment (CDMACHs = SF_CDMACHs)
10 – Active Set (For each pilot in the Serving Frequency Active Set: (PILOT_REC,
11 PWR_COMB_IND) )
12 – Code channel list (CODE_CHAN_LISTs = SF_CODE_CHAN_LISTs)
13 • The mobile station shall tune to the Serving Frequency and resume using the
14 Serving Frequency Active Set as follows:
15 – If the mobile station was processing the Forward Fundamental Channel prior to
16 tuning to the Candidate Frequency, the mobile station shall resume processing
17 the Forward Fundamental Channel. If the mobile station was transmitting on
18 the Reverse Fundamental Channel prior to tuning to the Candidate Frequency,
19 the mobile station shall resume transmitting on the Reverse Fundamental
20 Channel.
21 – If the mobile station was processing the Forward Dedicated Control Channel
22 prior to tuning to the Candidate Frequency, the mobile station shall resume
23 processing the Forward Dedicated Control Channel. If the mobile station was
24 transmitting on the Reverse Dedicated Control Channel prior to tuning to the
25 Candidate Frequency, the mobile station shall resume transmitting on the
26 Reverse Dedicated Control Channel.
27 – The mobile station shall not resume transmitting on the Reverse Supplemental
28 Code Channels and Reverse Supplemental Channels (if any). The mobile station
29 shall not process on the Forward Supplemental Code Channels and Forward
30 Supplemental Channels (if any).
31 – When the mobile station resumes transmission on the Reverse Traffic Channel,
32 it shall use the following rules to re-enable its transmitter:
33 + If the interval between the time that the mobile station disables its
34 transmitter and the time that it resumes using the Serving Frequency Active
35 Set is equal to or greater than (N2m × 20) ms, then the mobile station shall
36 wait to receive a period of (N3m × 20) ms with sufficient signal quality (e.g.
37 good frames) on the physical channel corresponding to FPC_PRI_CHANs
38 before it re-enables its transmitter.
2-472
3GPP2 C.S0005-A v6.0
1 + Otherwise, the mobile station shall re-enable its transmitter no later than
2 N3m × 20 ms after the mobile station tunes to the Serving Frequency. The
3 mobile station should re-enable its transmitter earlier. After the mobile
4 station re-enables its transmitter, the mean output power shall be as
5 specified in 2.1.2.4.1 of [2] for a step change in input power. If the mobile
6 station re-enables its transmitter earlier than N3m × 20 ms after it tunes to
7 the Serving Frequency, the initial mean output power shall be as specified in
8 2.1.2.3.1 of [2], where the initial mean input power estimate is either:
9 ο within 6 dB of the actual mean input power, or
10 ο equal to the mean input power before the mobile station tuned to the
11 Target Frequency.
12 • The mobile station shall enable the fade timer and the handoff drop timers
13 corresponding to the pilots in its Active Set and Candidate Set. The mobile station
14 shall resume incrementing TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs,
15 and DCCH_BAD_FRAMESs if applicable as specified in 2.6.4.1.1.
16 • The mobile station shall send a Candidate Frequency Search Report Message within
17 T56m seconds of declaring the handoff attempt to be unsuccessful. The mobile
18 station shall report the contents of the Candidate Frequency Search Report Message
19 as follows:
20 – The mobile station shall report the two components of the Target Frequency in
21 the CDMA_FREQ and BAND_CLASS fields.
22 – The mobile station shall report the received power on the Target Frequency and
23 on the Serving Frequency in the CF_TOTAL_RX_PWR and SF_TOTAL_RX_PWR
24 fields, respectively.
25 – For each pilot in the Target Frequency Active Set that measures above
26 TF_T_ADDs, the mobile station shall report its phase and strength in the fields
27 PILOT_PN_PHASE and PILOT_STRENGTH, respectively.
28 – If the Target Frequency is the same as the Candidate Frequency

29 (TF_CDMABANDs is equal to CF_CDMABANDs, and TF_CDMACHs is equal to
30 CF_CDMACHs), and is different form from the Serving Frequency
31 (TF_CDMABANDs is not equal to SF_CDMABANDs or TF_CDMACHs is not equal
32 to SF_CDMACHs), the mobile station shall also report the strength of each pilot
33 in the Candidate Frequency Search Set that measures above CF_T_ADDs.
34 • If the Serving Frequency is the same as the Candidate Frequency (SF_CDMABANDs

35 is equal to CF_CDMABANDs and SF_CDMACHs is equal to CF_CDMACHs), then the
36 mobile station shall set PERIODIC_SEARCHs to ‘0’.
37 • If PERIODIC_SEARCHs is equal to ‘1’ and the Candidate Frequency Search Set is

38 not empty, the mobile station shall do the following:
39 – The mobile station shall set ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs
40 to ‘000000’.
2-473
3GPP2 C.S0005-A v6.0
1 – The mobile station shall carry out the periodic search procedures described in
2 2.6.6.2.8.3.2.
3 2.6.6.2.8.3 Search of Pilots on the CDMA Candidate Frequency

4 If SEARCH_MODEs is equal to ‘0000’, the mobile station shall do the following: If
5 PERIODIC_SEARCHs is equal to ‘0’, the mobile station shall search the Candidate
6 Frequency Search Set once, as described in 2.6.6.2.8.3.1; otherwise, the mobile station
7 shall search the Candidate Frequency Search Set periodically, as described in 2.6.6.2.8.3.2.
8 2.6.6.2.8.3.1 CDMA Candidate Frequency Single Search
9 The mobile station does a single search of the Candidate Frequency Search Set by
10 performing the following actions at the action time of the Candidate Frequency Search
11 Control Message or the Candidate Frequency Search Request Message that started the
12 search:
13 • If ALIGN_TIMING_USEDs is set to ‘0’, the mobile station shall measure the strength
14 of all pilots in the Candidate Frequency Search Set in one or more visits to the
15 Candidate Frequency, as described in 2.6.6.2.8.3.3.
17 of all pilots in the Candidate Frequency Search Set in one or more scheduled visits
18 (see below) to the Candidate Frequency, as described in 2.6.6.2.8.3.3.
19 The mobile station shall schedule visits to the Candidate Frequency only at
20 ((0.00125 × SEARCH_OFFSETs) + k × (SEARCH_TIME_RESOLUTIONs ×
21 inter_visit_time)) seconds after the action time of the Candidate Frequency Search
22 Request Message or the Candidate Frequency Search Control Message that started
23 the search, where
24 k = an integer between 0 and max_num_visits, inclusive, where

25 max_num_visits is the value of MAX_NUM_VISITS field of the
26 last Candidate Frequency Search Response Message sent by the
27 mobile station,
28 and
29 inter_visit_time = the value of the INTER_VISIT_TIME field of the last Candidate
30 Frequency Search Response Message sent by the mobile station.
31 • The mobile station shall complete the measurements and send a Candidate
32 Frequency Search Report Message within ((0.00125 × SEARCH_OFFSETs) +
33 freshness_interval) seconds after the action time of the Candidate Frequency Search
34 Control Message, or the Candidate Frequency Search Request Message, where
35 freshness_interval is determined as follows:
36 – If the value of the TOTAL_OFF_TIME_FWD field or of the TOTAL_OFF_TIME_REV

37 field of the last Candidate Frequency Search Response Message sent by the
38 mobile station to the base station is greater than or equal to (T70m - T71m)/
39 SEARCH_TIME_RESOLUTIONs, then
2-474
3GPP2 C.S0005-A v6.0
1 freshness_interval = (max (fwd_time, rev_time) + T71m) seconds,
2 where
3 fwd_time = SEARCH_TIME_RESOLUTIONs × (value of the
4 TOTAL_OFF_TIME_FWD field of the last Candidate Frequency
5 Search Response Message sent by the mobile station),
6 and
7 rev_time = SEARCH_TIME_RESOLUTIONs × (value of the
8 TOTAL_OFF_TIME_REV field of the last Candidate Frequency
9 Search Response Message sent by the mobile station).
10 – Otherwise,
11 freshness_interval = T70m seconds.
12 The mobile station shall set the fields of the Candidate Frequency Search Report
13 Message as follows:
14 – The mobile station shall report the two components of the Candidate Frequency
15 in the CDMA_FREQ and BAND_CLASS fields.
16 – The mobile station shall report the received power on the Candidate Frequency
17 and on the Serving Frequency in the CF_TOTAL_RX_PWR and
18 SF_TOTAL_RX_PWR fields, respectively.
19 – For each pilot in the Candidate Frequency Search Set that measures above
20 CF_T_ADDs, the mobile station shall report its phase and strength in the fields
22 2.6.6.2.8.3.2 Candidate Frequency Periodic Search
23 When the mobile station performs a periodic search, it periodically searches the Candidate
24 Frequency Search Set and reports the results to the base station in the Candidate
25 Frequency Search Report Message, as described in this section. The mobile station may
26 measure all pilots in the Candidate Frequency Search Set in one visit to the Candidate
27 Frequency, or it may visit the Candidate Frequency several times in a search period, each
28 time measuring all or some of the pilots in the Candidate Frequency Search Set, as
29 described in 2.6.6.2.8.3.3.
30 If SF_TOTAL_EC_THRESHs is not equal to ‘11111’, while tuned to the Serving Frequency
31 (specified by CDMACHs and CDMABANDs), the mobile station shall measure the total
32 received power spectral density, in mW/1.23 MHz, on the Serving Frequency at least once
33 every 20 ms frame. The mobile station shall maintain the average of the spectral density
34 (spec_density) over the last N12m frames.
35 (In the following, (Ec/Io)total is the total Ec/Io of the pilots in the Active Set, measured as
36 specified in 2.6.6.2.2, and total_ec is defined as (10 × log10 ((Ec/Io)total × spec_density)).)
37 The mobile station shall maintain a periodic search timer as follows:
2-475
3GPP2 C.S0005-A v6.0
1 • When the mobile station starts a periodic search, it shall set the periodic search
2 timer to the value in Table 2.6.6.2.8.3.2-1 corresponding to SEARCH_PERIODs and
3 shall enable the timer.
4 – If the periodic search is started by a Candidate Frequency Search Request
5 Message or a Candidate Frequency Search Control Message, then the mobile
6 station shall start the periodic search (0.00125 × SEARCH_OFFSETs) seconds
7 after the action time of the Candidate Frequency Search Request Message or the
8 Candidate Frequency Search Control Message that started the search.
9 – If the periodic search is started following successful or unsuccessful handoff

10 attempt, the mobile station shall start the periodic search:
11 + Upon sending the Handoff Completion Message or Extended Handoff

12 Completion Message, in the case that the handoff was successful.
13 + Upon sending the Candidate Frequency Search Report Message, in the case
14 that the handoff was unsuccessful.
15 • When the periodic search timer expires, the mobile station shall reset the periodic
16 search timer to the value in Table 2.6.6.2.8.3.2-1 corresponding to
17 SEARCH_PERIODs and shall re-enable the timer.
18 • If ALIGN_TIMING_USEDs is set to ‘0’, SF_TOTAL_EC_THRESHs is not equal to

19 ‘11111’ and SF_TOTAL_EC_IO_THRESHs is equal to ‘11111’, the mobile station shall
20 perform the following actions once per frame:
21 – Disable the periodic search timer if total_ec is not less than

22 (-120 + 2 × SF_TOTAL_EC_THRESHs).
23 – Reset the expiration time of the periodic search timer to the value in
24 Table 2.6.6.2.8.3.2-1 corresponding to SEARCH_PERIODs, and re-enable the
25 timer if the following conditions are true:
26 + the periodic search timer is disabled, and

27 + total_ec is less than (-120 + 2 × SF_TOTAL_EC_THRESHs).
28 • If ALIGN_TIMING_USEDs is set to ‘0’, SF_TOTAL_EC_THRESHs is equal to ‘11111’

29 and SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’, the mobile station shall
31 – Disable the periodic search timer if (-20 × log10 (Ec/Io)total) is not greater than
32 SF_TOTAL_EC_IO_THRESHs.

37 + (-20 × log10 (Ec/Io)total) is greater than SF_TOTAL_EC_IO_THRESHs.
2-476
3GPP2 C.S0005-A v6.0

2 ‘11111’ and SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’, the mobile station
3 shall perform the following actions once per frame:
4 – Disable the periodic search timer if the following conditions are true:
5 + total_ec is not less than (-120 + 2 × SF_TOTAL_EC_THRESHs), and
6 + (-20 × log10 (Ec/Io)total) is not greater than SF_TOTAL_EC_IO_THRESHs.

11 + total_ec is less than (-120 + 2 × SF_TOTAL_EC_THRESHs), or (-20 × log10
12 (Ec/Io)total) is greater than SF_TOTAL_EC_IO_THRESHs.
13 • The mobile station shall maintain the periodic search timer independent of the total
14 Ec and the total Ec/Io of the pilots in the Serving Frequency Active Set, if any of the
16 – ALIGN_TIMING_USEDs is set to ‘1, or
17 – SF_TOTAL_EC_THRESHs is equal to ‘11111’ and SF_TOTAL_EC_IO_THRESHs is

18 equal to ‘11111’.
19
20 Table 2.6.6.2.8.3.2-1. Search Period Values
Search Search
SEARCH_PERIODs Period SEARCH_PERIODs Period
(seconds) (seconds)
0 0.48 8 30
1 0.96 9 40
2 2 10 50
3 2.96 11 60
4 4 12 80
5 4.96 13 100
6 10 14 150
7 20 15 200
21
22 If the periodic search timer is enabled, the mobile station shall perform the following
23 actions before the timer expires:
2-477
3GPP2 C.S0005-A v6.0
2 of all pilots in the Candidate Frequency Search Set at least once in one or more
3 visits to the Candidate Frequency, as described in 2.6.6.2.8.3.3.
5 of all pilots in the Candidate Frequency Search Set in one or more scheduled visits
6 (see below) to the Candidate Frequency, as described in 2.6.6.2.8.3.3.
7 The mobile station shall schedule visits to the Candidate Frequency only at
15 mobile station,
16 and

19 – The mobile station shall abort a scheduled visit to the Candidate Frequency if at
20 the scheduled time, one or both of the following conditions hold:
21 + SF_TOTAL_EC_THRESHs is not equal to ‘11111’ and total_ec is not less than
22 (-120 + 2 × SF_TOTAL_EC_THRESHs), or
23 + SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’ and (-20 × log10

24 (Ec/Io)total) is not greater than SF_TOTAL_EC_IO_THRESHs.
25 – If the mobile station aborts a scheduled visit during a search period, it may
26 abort all remaining scheduled visits in that search period.
27 • The mobile station shall send a Candidate Frequency Search Report Message if
28 MIN_TOTAL_PILOT_EC_IOs is equal to ‘00000’ or if (- 20 × log10 (Ec/Io)total) is not
29 less than or equal to MIN_TOTAL_PILOT_EC_IOs, where (Ec/Io)total is the sum of
30 Ec/Io for all those pilots that measure above CF_T_ADDs in the current search
31 period.
32 The mobile station shall report the contents of the Candidate Frequency Search
33 Report Message as follows:
34 – The mobile station shall report the two components of the Candidate Frequency
35 in the CDMA_FREQ and BAND_CLASS fields.
36 – The mobile station shall report the received power on the Candidate Frequency
37 and on the Serving Frequency in the CF_TOTAL_RX_PWR and
38 SF_TOTAL_RX_PWR fields, respectively.
2-478
3GPP2 C.S0005-A v6.0
1 – For each pilot in the Candidate Frequency Search Set that measures above
2 CF_T_ADDs, the mobile station shall report its phase and strength in the fields
4 • The mobile station shall ensure that the strength measurement for all pilots in the
5 Candidate Frequency Search Set were obtained within freshness_interval before the
6 Candidate Frequency Search Report Message is sent, where freshness_interval is
7 determined as follows:

10 mobile station to the base station is greater than or equal to
11 (T70m - T71m)/SEARCH_TIME_RESOLUTIONs, then
13 where
17 and
21 – Otherwise,
23 2.6.6.2.8.3.3 Candidate Frequency Pilot Measurements
24 The mobile station measures the strength of all pilots in the Candidate Frequency Search
25 Set in one or more visits to the Candidate Frequency. The mobile station shall perform the
26 following actions each time it visits the Candidate Frequency to measure pilot strengths:
27 • If the mobile station is processing the Forward Fundamental Channel, the mobile
28 station shall stop processing the Forward Fundamental Code Channel. If the mobile
29 station is transmitting on the Reverse Fundamental Channel, the mobile station
30 shall stop transmitting on the Reverse Fundamental Channel.
31 • If the mobile station is processing the Forward Dedicated Control Channel, the
32 mobile station shall stop processing the Forward Dedicated Control Channel. If the
33 mobile station is transmitting on the Reverse Dedicated Control Channel, the mobile
34 station shall stop transmitting on the Reverse Dedicated Control Channel.
35 • The mobile station shall stop processing the Forward Supplemental Code Channels
36 and Forward Supplemental Channels (if any). The mobile station shall stop
37 transmitting on the Reverse Supplemental Code Channels and Reverse
2-479
3GPP2 C.S0005-A v6.0
2 timers corresponding to its current Active Set and Candidate Set (see 2.6.6.2.3), and
3 shall suspend incrementing TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs,
4 DCCH_BAD_FRAMESs, SCH_TOT_FRAMESs, and SCH_BAD_FRAMESs if applicable
5 (see 2.6.4.1.1).
8 period that the transmitter is disabled (see 2.1.2.3.1 of [2]).
9 • The mobile station shall store the following parameters from its current
10 configuration:
11 – CDMA band class (SF_CDMABANDs = CDMABANDs)
12 – Frequency Assignment (SF_CDMACHs = CDMACHs)
13 – Pilot detection threshold (SF_T_ADDs = T_ADDs)
14 • The mobile station shall set the following parameters:

15 – CDMABANDs = CF_CDMABANDs
16 – CDMACHs = CF_CDMACHs
17 – T_ADDs = CF_T_ADDs
18 The mobile station shall tune to the Candidate Frequency.
19 • The mobile station shall not change its time reference (see 2.1.5 of [2]) until it
20 resumes using the Serving Frequency Active Set, as described below.
21 • The mobile station shall measure the mean input power on the Candidate Frequency
22 (cand_freq_pwr, in dBm / 1.23 MHz), and may use cand_freq_pwr along with the
23 measurement of the mean input power on the Serving Frequency
24 (avg_serving_freq_pwr, in dBm / 1.23 MHz) in the search procedure as follows:
25 – If DIFF_RX_PWR_THRESHs is not equal to ‘00000’, and (cand_freq_pwr -
26 avg_serving_freq_pwr) is less than (-30 + 2 × DIFF_RX_PWR_THRESHs) dB, the
27 mobile station may terminate the search for pilots in the current visit to the
28 Candidate Frequency.
29 – If DIFF_RX_PWR_THRESHs is equal to ‘00000’, the mobile station does not use
30 the power measurements in the search procedure, or (cand_freq_pwr -
31 avg_serving_freq_pwr) is not less than (-30 + 2 × DIFF_RX_PWR_THRESHs) dB,
32 the mobile station shall measure Ec/Io for all or some of the pilots in its
33 Candidate Frequency Search Set, using the search procedures specified in
34 2.6.6.2.2.
35 • The mobile station shall restore the following parameters:

36 – Pilot detection threshold (T_ADDs = SF_T_ADDs)
37 – CDMA band class (CDMABANDs = SF_CDMABANDs)
38 – Frequency assignment (CDMACHs = SF_CDMACHs)
2-480
3GPP2 C.S0005-A v6.0
1 • The mobile station shall tune to the Serving Frequency and shall resume using the
8 Channel.
15 – If the Forward Supplemental Code Channels and Forward Supplemental

16 Channels assignment has not expired, the mobile station shall resume
17 processing the Forward Supplemental Code Channels and Forward
18 Supplemental Channels (if any). If the Reverse Supplemental Code Channel and
19 Reverse Supplemental Channels assignment has not expired, the mobile station
20 may resume transmitting on the Reverse Supplemental Code Channels and
21 Reverse Supplemental Channels (if any).
34 specified in 2.1.2.4.1 for a step change in input power. If the mobile station
35 re-enables its transmitter earlier than N3m × 20 ms after it tunes to the
36 Serving Frequency, the initial mean output power shall be as specified in
2-481
3GPP2 C.S0005-A v6.0
6 2.6.6.2.8.3.4 Aborting CDMA Candidate Frequency Periodic Search
7 When the mobile station aborts a periodic search, it shall do the following:
8 • The mobile station shall cancel any remaining visits to the Candidate Frequency in
9 the current search period, and shall not send a Candidate Frequency Search Report
10 Message for the current search period.
11 • The mobile station shall disable the periodic search timer.
12 2.6.6.2.9 CDMA-to-Analog Handoff
13 The base station directs the mobile station to perform a CDMA-to-Analog handoff by
14 sending an Analog Handoff Direction Message. If the mobile station has narrow analog
15 capability, the base station may direct the handoff to a narrow analog channel.
16 If the mobile station supports analog operation in the requested band class, the mobile
17 station shall set DTXs to ‘00’ and store the following parameters from the Analog Handoff
20 • Voice mobile station attenuation code (VMACs = VMACr)
21 • Analog voice channel number (ANALOG_CHANs = ANALOG_CHANr)
22 • SAT color code (SCCs = SCCr)
23 • Message encryption mode indicator (MEMs = MEMr)
24 • Analog voice channel type (AN_CHAN_TYPEs = AN_CHAN_TYPEr)
25 • Digital supervisory audio color code (DSCCs = DSCC_MSBr × 4 + SCCr)
26 If the mobile station does not support analog operation in the requested band class, the
27 mobile station shall discard the message and send a Mobile Station Reject Order with the
28 ORDQ field set to ‘00000110’ (capability not supported by the mobile station).
29 At the action time specified by the Analog Handoff Direction Message (see 2.6.4.1.5), the
30 mobile station shall disable its transmitter. The mobile station shall enable its transmitter
31 on the wide analog voice channel or optional narrow analog voice channel within T63m
32 seconds after the action time.
33 2.6.6.2.10 Search of Analog Frequencies

34 If SEARCH_MODEs is equal to ‘0001’, and the mobile station supports analog searching,
35 the mobile station shall do the following: If PERIODIC_SEARCHs is equal to ‘0’, the mobile
36 station shall search the Candidate Analog Frequency Search Set once, as described in
2-482
3GPP2 C.S0005-A v6.0
1 2.6.6.2.10.1; otherwise, the mobile station shall search the Candidate Frequency Analog
2 Search Set periodically, as described in 2.6.6.2.10.2.
3 2.6.6.2.10.1 Analog Frequencies Single Search
4 The mobile station does a single search of the Candidate Frequency Analog Search Set by
5 performing the following actions at the action time of the Candidate Frequency Search
6 Control Message or the Candidate Frequency Search Request Message that started the
7 search:
9 of all analog frequencies in the Candidate Frequency Analog Search Set in one or
10 more visits away from the Serving Frequency, as described in 2.6.6.2.10.3.
12 of analog frequencies in the Candidate Frequency Analog Search Set in one or more
13 scheduled visits (see below) away from the Serving Frequency, as described in
14 2.6.6.2.10.3.
15 The mobile station shall schedule visits away from the Serving Frequency only at
23 mobile station,
24 and
27 • The mobile station shall complete the measurements and send a Candidate
28 Frequency Search Report Message within ((0.00125 × SEARCH_OFFSETs) +
29 freshness_interval) seconds after the action time of the Candidate Frequency Search
30 Control Message or the Candidate Frequency Search Request Message, where
31 freshness_interval is determined as follows:

35 SEARCH_TIME_RESOLUTIONs, then
37 where
2-483
3GPP2 C.S0005-A v6.0
1 and
5 – Otherwise,
7 2.6.6.2.10.2 Analog Frequencies Periodic Search
8 When the mobile station performs a periodic search, it periodically searches the Candidate
9 Frequency Analog Search Set, and reports the results to the base station in the Candidate
10 Frequency Search Report Message, as described in this section. The mobile station may
11 measure all analog frequencies in the Candidate Frequency Analog Search Set in one visit
12 away from the Serving Frequency, or it may make multiple visits in a search period, each
13 time measuring all or some of the analog frequencies in the Candidate Frequency Analog
14 Search Set, as described in 2.6.6.2.10.3.
15 If SF_TOTAL_EC_THRESHs is not equal to ‘11111’, while tuned to the Serving Frequency
16 (specified by CDMACHs and CDMABANDs), the mobile station shall measure the total
17 received power spectral density, in mW/1.23 MHz, on the Serving Frequency at least once
18 every 20 ms frame. The mobile station shall maintain the average of the spectral density
19 (spec_density) over the last N12m frames.
20 (In the following, (Ec/Io)total is the total Ec/Io of the pilots in the Active Set, measured as
21 specified in 2.6.6.2.2, and total_ec is defined as (10 × log10 ((Ec/Io)total × spec_density)).)
22 The mobile station shall maintain a periodic search timer as follows:
23 • When the mobile station starts a periodic search, it shall set the periodic search
24 timer to the value in Table 2.6.6.2.8.3.2-1 corresponding to SEARCH_PERIODs and
25 shall enable the timer.
26 – If the periodic search is started by a Candidate Frequency Search Request
27 Message or a Candidate Frequency Search Control Message, then the mobile
28 station shall begin the periodic search (0.00125 × SEARCH_OFFSETs) seconds
29 after the action time of the Candidate Frequency Search Request Message or the
30 Candidate Frequency Search Control Message that started the search.
31 – If the periodic search is started following successful or unsuccessful handoff

32 attempt, the mobile station shall start the periodic search:
33 + Upon sending the Handoff Completion Message or Extended Handoff

34 Completion Message, in the case that the handoff was successful.
35 + Upon sending the Candidate Frequency Search Report Message, in the case
36 that the handoff was unsuccessful.
37 • When the periodic search timer expires, the mobile station shall reset the periodic
38 search timer to the value in Table 2.6.6.2.8.3.2-1 corresponding to
39 SEARCH_PERIODs and shall re-enable the timer.
2-484
3GPP2 C.S0005-A v6.0

2 ‘11111’ and SF_TOTAL_EC_IO_THRESHs is equal to ‘11111’, the mobile station shall
4 – Disable the periodic search timer if total_ec is not less than
5 (-120 + 2 × SF_TOTAL_EC_THRESHs).

10 + total_ec is less than (-120 + 2 × SF_TOTAL_EC_THRESHs).
11 • If ALIGN_TIMING_USEDs is set to ‘0’, SF_TOTAL_EC_THRESHs is equal to ‘11111’

12 and SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’, the mobile station shall
14 – Disable the periodic search timer if (-20 × log10 (Ec/Io)total) is not greater than
15 SF_TOTAL_EC_IO_THRESHs.

20 + (-20 × log10 (Ec/Io)total) is greater than SF_TOTAL_EC_IO_THRESHs.

22 ‘11111’ and SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’, the mobile station
23 shall perform the following actions once per frame:
24 – Disable the periodic search timer if the following conditions are true:
25 + total_ec is not less than (-120 + 2 × SF_TOTAL_EC_THRESHs), and
26 + (-20 × log10 (Ec/Io)total) is not greater than SF_TOTAL_EC_IO_THRESHs.

31 + total_ec is less than (-120 + 2 × SF_TOTAL_EC_THRESHs), or
32 (-20 × log10 (Ec/Io)total) is greater than SF_TOTAL_EC_IO_THRESHs.
33 • The mobile station shall maintain the periodic search timer independent of the total
34 Ec and the total Ec/Io of the pilots in the Serving Frequency Active Set, if any of the
36 – ALIGN_TIMING_USEDs is set to ‘1, or
2-485
3GPP2 C.S0005-A v6.0
1 – SF_TOTAL_EC_THRESHs is equal to ‘11111’ and SF_TOTAL_EC_IO_THRESHs is

2 equal to ‘11111’.
3 If the periodic search timer is enabled, the mobile station shall perform the following
4 actions before the timer expires:
6 of all analog frequencies in the Candidate Frequency Analog Search Set at least once
7 in one or more visits away from the Serving Frequency, as described in 2.6.6.2.10.3.
9 of analog frequencies in the Candidate Frequency Analog Search Set in one or more
10 scheduled visits (see below) away from the Serving Frequency, as described in
11 2.6.6.2.10.3.
12 The mobile station shall schedule visits away from the Serving Frequency only at

20 mobile station,
21 and

24 – The mobile station shall abort a scheduled visit away from the Serving
25 Frequency if at the scheduled time, one or both of the following conditions hold:
26 + SF_TOTAL_EC_THRESHs is not equal to ‘11111’ and total_ec is not less than
27 (-120 + 2 × SF_TOTAL_EC_THRESHs), or
28 + SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’ and (-20 × log10

29 (Ec/Io)total) is not greater than SF_TOTAL_EC_IO_THRESHs.
30 – If the mobile station aborts a scheduled visit during a search period, it may
31 abort all remaining scheduled visits in that search period.
32 • The mobile station shall set the fields of the Candidate Frequency Search Report
33 Message as follows: The mobile station shall report the received power on the
34 Serving Frequency in the TOTAL_RX_PWR_SF field. For each frequency in the
35 Candidate Frequency Analog Search Set, the mobile station shall report its
36 frequency and strength in the fields ANALOG_FREQ and SIGNAL_STRENGTH,
37 respectively.
2-486
3GPP2 C.S0005-A v6.0
1 • The mobile station shall ensure that the strength measurements for all analog
2 frequencies in the Candidate Frequency Analog Search Set were obtained within
3 freshness_interval before the Candidate Frequency Search Report Message is sent,
4 where freshness_interval is determined as follows:

8 SEARCH_TIME_RESOLUTIONs), then
10 where
14 and
18 – Otherwise,
20 2.6.6.2.10.3 Analog Frequency Measurements
21 The mobile station measures the strength of all analog frequencies in the Candidate
22 Frequency Analog Search Set in one or more visits away from the Serving Frequency. The
23 mobile station shall perform the following actions during each visit away from the Serving
24 Frequency to measure analog frequency signal strengths:
25 • If the mobile station is processing the Forward Fundamental Channel, the mobile
26 station shall stop processing the Forward Fundamental Channel. If the mobile
27 station is transmitting on the Reverse Fundamental Channel, the mobile station
28 shall stop transmitting on Reverse Fundamental Channel.
29 • If the mobile station is processing the Forward Dedicated Control Channel, the
30 mobile station shall stop processing Forward Dedicated Control Channel. If the
31 mobile station is transmitting on the Reverse Dedicated Control Channel, the mobile
32 station shall stop transmitting on Reverse Dedicated Control Channel.
33 • The mobile station shall stop processing the Forward Supplemental Code Channels
34 and Forward Supplemental Channels (if any). The mobile station shall stop
35 transmitting on the Reverse Supplemental Code Channels and Reverse
2-487
3GPP2 C.S0005-A v6.0
2 timers corresponding to its current Active Set and Candidate Set (see 2.6.6.2.3), and
3 shall suspend incrementing TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs,
5 (see 2.6.4.1.1).
8 period that the transmitter is disabled (see [2]).
9 • The mobile station shall tune to one of the analog frequencies in the Candidate
10 Frequency Analog Search Set, and shall measure the mean input power on the
11 analog frequency.
12 • The mobile station may tune to other frequencies in the Candidate Frequency
13 Analog Search Set and make power measurements during this visit away from the
15 • The mobile station shall not change its time reference (see 2.1.5 of [2]) until it
16 resumes using the Serving Frequency Active Set, as described below.
17 • The mobile station shall tune to the Serving Frequency and resume using the
24 Channel.
31 – If the Forward Supplemental Code Channels or Forward Supplemental Channels

32 assignment has not expired, the mobile station shall resume processing the
33 Forward Supplemental Code Channels or Forward Supplemental Channels
34 respectively (if any).
35 – If the Reverse Supplemental Code Channel or Reverse Supplemental Channels

36 assignment has not expired, the mobile station may resume transmitting on the
37 Reverse Supplemental Code Channels or Reverse Supplemental Channels
38 respectively (if any).
2-488
3GPP2 C.S0005-A v6.0
11 specified in 2.1.2.4.1 of [2] for a step change in input power. If the mobile
12 station re-enables its transmitter earlier than N3m × 20 ms after it tunes to
13 the Serving Frequency, the initial mean output power shall be as specified in
23 2.6.6.2.10.4 Aborting Analog Frequencies Periodic Search
24 When the mobile station aborts a periodic search, it shall do the following:
25 • The mobile station shall cancel any remaining visits away from the Serving
26 Frequency in the current search period and shall not send a Candidate Frequency
27 Search Report Message for the current search period.
28 • The mobile station shall disable the periodic search timer.
29 2.6.6.2.11 Processing of Reverse Supplemental Code Channels and Reverse Supplemental

30 Channels
31 If USE_T_ADD_ABORTs is set to ‘1’, and the strength of a Neighbor Set or Remaining Set
32 pilot is found to be above T_ADDs, then the mobile station shall terminate any active
33 transmission on Reverse Supplemental Code Channels or Reverse Supplemental Channels
34 at the end of the current 20 ms frame. The mobile station shall do the following:
35 • Any previously active Reverse Supplemental Code Channel or Reverse Supplemental

36 Channel assignment shall be considered implicitly terminated.
37 • If active transmission on Reverse Supplemental Code Channels is terminated, the

38 mobile station shall set NUM_REV_CODESs to ‘000’ and shall set IGNORE_SCAMs
39 to ‘1’.
2-489
3GPP2 C.S0005-A v6.0
1 • If active transmission on Reverse Supplemental Channels is terminated, the mobile

2 station shall set IGNORE_ESCAMs to ‘1’.
3 • The mobile station shall set SCRM_SEQ_NUMs to (SCRM_SEQ_NUMs + 1) mod 16.
4 • The mobile station shall transmit a Supplemental Channel Request Message with
5 USE_SCRM_SEQ_NUM set to ‘1’, SCRM_SEQ_NUM set to SCRM_SEQ_NUMs, and
6 SIZE_OF_REQ_BLOB set to ‘0000’.
7 2.6.6.2.12 Periodic Serving Frequency Pilot Report Procedure

8 While the mobile station is tuned to the Serving Frequency (specified by CDMACHs and
9 CDMABANDs), the mobile station shall measure the total received power spectral density, in
10 mW/1.23 MHz, on the Serving Frequency at least once every 20 ms frame. The mobile
11 station shall maintain the average value of the total received power spectral density,
12 spec_density, over the last N12m frames. The mobile station shall maintain the PPSMM
13 timer as follows:
14 • When the mobile station starts a Periodic Serving Frequency Pilot Report Procedure,
15 it shall set the PPSMM timer to PPSMM_PERIODs × 0.08 seconds and shall enable
16 the timer.
17 • When the PPSMM timer expires, the mobile station shall send a Periodic Pilot
18 Strength Measurement Message (2.6.6.2.5.2) to the base station, reset the PPSMM
19 timer to PPSMM_PERIODs × 0.08 seconds and shall re-enable the timer.
20 • When the mobile station receives an Extended Handoff Direction Message , a General
21 Handoff Direction Message or a Universal Handoff Direction Message directing the
22 mobile station to perform a hard handoff (see 2.6.6.2.5.1), it shall abort the Periodic
23 Serving Frequency Pilot Report Procedure and disable the PPSMM timer if it is
24 enabled.
25 • If MIN_PILOT_PWR_THRESHs is not equal to ‘11111’ and
26 MIN_PILOT_EC_IO_THRESHs is equal to ‘11111’, the mobile station shall perform
27 the following actions once per frame:
28 – Disable the PPSMM timer if the received total energy per PN chip, Ec, of the
29 pilots in the Active Set is not less than (-120 + 2 × MIN_PILOT_PWR_THRESHs),
30 where the value of Ec is computed as 10 × log10 (PS × spec_density) and PS is
31 the total Ec/Io of the pilots in the Active Set measured as specified in 2.6.6.2.2.
32 – Reset the expiration time of the PPSMM timer to PPSMM_PERIODs × 0.08

33 seconds and re-enable the timer if the following conditions are true:
34 ο the PPSMM timer is disabled, and

35 ο the received total energy per PN chip, Ec, of the pilots in the Active Set is less
36 than (-120 + 2 × MIN_PILOT_PWR_THRESHs).
37 • If MIN_PILOT_PWR_THRESHs is equal to ‘11111’ and MIN_PILOT_EC_IO_THRESHs

38 is not equal to ‘11111’, the mobile station shall perform the following actions once
39 per frame:
2-490
3GPP2 C.S0005-A v6.0
1 – Disable the PPSMM timer if the total pilot strength of the pilots in the Active Set,
2 PS, satisfies the condition that (-20 × log10(PS)) is not greater than
3 MIN_PILOT_EC_IO_THRESHs.

7 ο the total pilot strength of the pilots in the Active Set, PS, satisfies the
8 condition that (-20 × log10(PS)) is greater than MIN_PILOT_EC_IO_THRESHs.
9 • If MIN_PILOT_PWR_THRESHs is not equal to ‘11111’ and

10 MIN_PILOT_EC_IO_THRESHs is not equal to ‘11111’, the mobile station shall
12 – Disable the PPSMM timer if the following conditions are true:

13 ο the received total energy per PN chip, Ec, of the pilots in the Active Set is not
14 less than (-120 + 2 × MIN_PILOT_PWR_THRESHs), and
15 ο the total pilot strength of the pilots in the Active Set, PS, satisfies the
16 condition that (-20 × log10(PS)) is not greater than
17 MIN_PILOT_EC_IO_THRESHs.


21 ο the received total energy per PN chip, Ec, of the pilots in the Active Set is less
22 than (-120 + 2 × MIN_PILOT_PWR_THRESHs), or the total pilot strength of
23 the pilots in the Active Set, PS, satisfies the condition that (-20 × log10(PS)) is
24 greater than MIN_PILOT_EC_IO_THRESHs.
25 • If MIN_PILOT_PWR_THRESHs is equal to ‘11111’ and MIN_PILOT_EC_IO_THRESHs

26 is equal to ‘11111’, the mobile station shall maintain the PPSMM timer independent
27 of the received power and the total Ec/Io of the pilots.
28 2.6.6.3 Examples
29 The following examples illustrate typical message exchanges between the mobile station and
30 the base station during handoff. Refer to Annex B for examples of call processing during
31 handoff.
32 Figure 2.6.6.3-1 shows an example of the messages exchanged between the mobile station
33 and the base station during a typical handoff process if P_REV_IN_USEs is less than or
34 equal to three or SOFT_SLOPEs is equal to ‘000000’.
35 Figure 2.6.6.3-2 shows an example of the messages exchanged between the mobile station
36 and the base station during a typical handoff process if P_REV_IN_USEs is greater than
37 three and SOFT_SLOPEs is not equal to ‘000000’.
2-491
3GPP2 C.S0005-A v6.0
1 Figure 2.6.6.3-3 illustrates the messaging triggered by a pilot of the Candidate Set as its
2 strength gradually rises above the strength of each pilot of the Active Set if P_REV_IN_USEs
3 is less than or equal to three, or SOFT_SLOPEs is equal to ‘000000’. Note that the mobile
4 station reports that a Candidate Set pilot is stronger than an Active Set pilot only if the
5 difference between their respective strengths is at least T_COMP × 0.5 dB.
6 Figure 2.6.6.3-4 illustrates the messaging triggered by a pilot of the Candidate Set as its
7 strength gradually rises above the strength of each pilot of the Active Set if P_REV_IN_USEs
8 is greater than three and SOFT_SLOPEs is not equal to ‘000000’. Note that the mobile
9 station reports that a Candidate Set pilot is stronger than an Active Set pilot only if the
10 difference between their respective strengths is at least T_COMP × 0.5 dB and Pilot P0
11 strength exceeds [(SOFT_SLOPE/8) × 10 × log10(PS1 + PS2) + ADD_INTERCEPT/2].
2-492
3GPP2 C.S0005-A v6.0
Pilot
Strength
T_ADD
T_DROP
Time
(1) (2)(3) (4) (5) (6) (7)
Neighbor Candidate Active Neighbor
Set Set Set Set
1
3 (1) Pilot strength exceeds T_ADD. Mobile station sends a Pilot Strength Measurement
4 Message and transfers pilot to the Candidate Set.
5 (2) Base station sends an Extended Handoff Direction Message, a General Handoff
6 Direction Message or a Universal Handoff Direction Message.
7 (3) Mobile station transfers pilot to the Active Set and sends a Handoff Completion
8 Message.
9 (4) Pilot strength drops below T_DROP. Mobile station starts the handoff drop timer.
10 (5) Handoff drop timer expires. Mobile station sends a Pilot Strength Measurement
11 Message.
12 (6) Base station sends an Extended Handoff Direction Message, a General Handoff
13 Direction Message or a Universal Handoff Direction Message.
14 (7) Mobile station moves pilot from the Active Set to the Neighbor Set and sends a
15 Handoff Completion Message.
16 Figure 2.6.6.3-1. Handoff Threshold Example if P_REV_IN_USEs is Less Than or Equal

17 to Three, or SOFT_SLOPEs is Equal to ‘000000’
2-493
3GPP2 C.S0005-A v6.0
10log10 ∑ PSi
Pilot i∈A
Strength
P1 P2
T_ADD
P2
T_DROP
P1
Time
(1) (2) (3) (4) (5) (6) (7) (8)
Neighbor Candidate Active Candidate Neighbor

Set Set Set Set Set
2 (1) Pilot P2 strength exceeds T_ADD. Mobile station transfers the pilot to the Candidate Set.
3 (2) Pilot P2 strength exceeds [(SOFT_SLOPE/8) × 10 × log10(PS1) + ADD_INTERCEPT/2].
4 Mobile station sends a Pilot Strength Measurement Message.
5 (3) Mobile station receives an Extended Handoff Direction Message, a General Handoff
6 Direction Message or a Universal Handoff Direction Message, transfers the pilot P2 to the
7 Active Set, and sends a Handoff Completion Message.
8 (4) Pilot P1 strength drops below [(SOFT_SLOPE/8) × 10 × log10(PS2) +
9 DROP_INTERCEPT/2]. Mobile station starts the handoff drop timer.
10 (5) Handoff drop timer expires. Mobile station sends a Pilot Strength Measurement Message.
11 (6) Mobile station receives an Extended Handoff Direction Message, a General Handoff
12 Direction Message or a Universal Handoff Direction Message, transfers the pilot P1 to the
13 Candidate Set and sends a Handoff Completion Message.
14 (7) Pilot P1 strength drops below T_DROP. Mobile station starts the handoff drop timer.
15 (8) Handoff drop timer expires. Mobile station moves the pilot P1 from the Candidate Set to
16 the Neighbor Set.
17 Figure 2.6.6.3-2. Handoff Threshold Example if P_REV_IN_USEs is Greater Than

18 Three, and SOFT_SLOPEs is Not Equal to ‘000000’
2-494
3GPP2 C.S0005-A v6.0
Pilot
Strength Pilot P0
T_COMP× 0.5 dB
Pilot P2
T_COMP× 0.5 dB
Pilot P1
T_ADD
t0 t1 t2 Time
2 Candidate Set: Pilot P0
3 Active Set: Pilots P1, P2
4 t0 – Pilot Strength Measurement Message sent, P0 > T_ADD
5 t1 – Pilot Strength Measurement Message sent, P0 > P1 + T_COMP × 0.5 dB
6 t2 – Pilot Strength Measurement Message sent, P0 > P2 + T_COMP × 0.5 dB

8 P_REV_IN_USEs = 3 or SOFT_SLOPEs = ‘000000’
2-495
3GPP2 C.S0005-A v6.0
Pilot
Strength Pilot P0
10 log10(PS1 + PS2)
T_COMP× 0.5 dB
Pilot P2
T_COMP× 0.5 dB
Pilot P1
T_ADD
t0 t1 t 1’ t2 Time
2 Candidate Set: Pilot P0
3 Active Set: Pilots P1, P2
4 t0 – Pilot Strength Measurement Message not sent because

5 [10 × log10(PS0)] < [(SOFT_SLOPE/8) × 10 × log10(PS1 + PS2) + ADD_INTERCEPT/2]
6 t1 – Pilot Strength Measurement Message not sent because

7 P0 > [P1 + T_COMP × 0.5 dB] but
8 [10 × log10(PS0)] < [(SOFT_SLOPE/8) × 10 × log10(PS1 + PS2) + ADD_INTERCEPT/2]
9 t1’ – Pilot Strength Measurement Message sent because

10 [10 × log10(PS0)] > [(SOFT_SLOPE/8) × 10 × log10(PS1 + PS2) + ADD_INTERCEPT/2]
11 t2 – Pilot Strength Measurement Message sent because

12 P0 > [P2 + T_COMP × 0.5 dB] and
13 [10 × log10(PS0)] > [(SOFT_SLOPE/8) × 10 × log10(PS1 + PS2) + ADD_INTERCEPT/2]

15 P_REV_IN_USEs > 3 and SOFT_SLOPEs is Not Equal to‘000000’
2-496
3GPP2 C.S0005-A v6.0
1 2.6.7 Hash Functions and Randomization
2 2.6.7.1 Hash Function
3 Certain procedures require a uniform distribution of mobile stations among N resources.

4 The following function returns an integer, using as arguments the mobile station’s IMSI, the
5 number of resources N, and a modifier DECORR. The modifier serves to decorrelate the
6 values obtained for the various applications from the same mobile station.
7 HASH_KEY shall be equal to the 32 least significant bits of (IMSI_O_S1 + 224 × IMSI_O_S2).
8 Define:
9 • Word L to be bits 0-15 of HASH_KEY
10 • Word H to be bits 16-31 of HASH_KEY
11 where bit 0 is the least significant bit of HASH_KEY.
12 For determining CDMA Channel Number, Paging Channel Number, Forward Common
13 Control Channel Number, Quick Paging Channel Number, and Paging Slot Number, the
14 hash value is computed as follows:18
15 R = N × ((40503 × (L ⊕ H ⊕ DECORR)) mod 216 ) / 216.
16 For determining a mobile station’s assigned paging indicator bit positions, the hash value is
17 computed as follows:
18 R1 = N × ((40503 × (L ⊕ H ⊕ DECORR1)) mod 216)/216,
19 and
20 R2 = ( (1 - (2 ×R1)/(N+4) ) × (N+4)/2 + (2 ×R1)/(N+4) × ((N+4)/2 – 4)) × ((40503 × (L ⊕
21 H ⊕ DECORR2)) mod 216)/216 + N + 4 + (2 ×R1)/(N+4) × ((N+4)/2) for Quick
22 Paging Channel indicator rate of 4800 bps, or
23 R2 = ( (1 - (2 ×R1)/(N+8) ) × (N+8)/2 +
(2 ×R1)/(N+8) × ((N+8)/2 – 8) ) × ((40503 ×
24 16 16
(L ⊕ H ⊕ DECORR2)) mod 2 )/2 + N + 8 + (2 ×R1)/(N+8) × ((N+8)/2) for Quick
25 Paging Channel indicator rate of 9600 bps.
26 The mobile station shall choose the range N and the modifiers DECORR, DECORR1, and
27 DECORR2 according to the application as shown in Table 2.6.7.1-1. In the table,
28 HASH_KEY [0...11] denotes the 12 least significant bits of HASH_KEY.
29
18 This formula is adapted from Knuth, Donald N., The Art of Computer Programming, 2 volumes,
(Reading, MA, Addison-Wesley, 1998).
2-497
3GPP2 C.S0005-A v6.0
1 Table 2.6.7.1-1. Hash Function Modifier
Return
Application N DECORR
Value
CDMA Channel Number of channels in last 0 R+1

Number CDMA Channel List Message or
the number of qualified
channels in the last Extended
CDMA Channel List Message
Paging Channel PAGE_CHANs from System 2 × HASH_KEY [0…11] R+1
Number Parameters Message (up to 7)
Quick Paging NUM_QPCHs from Extended
2 × HASH_KEY [0…11] R+1
Channel Number System Parameters Message or
MC-RR Parameters Message (up
to 3)
Paging Slot 2048 6 × HASH_KEY[0…11] R
Number
Paging Indicator 376 (for 9600 bps), 188 (for 4800 DECORR1 = t /64 R1 and
Positions bps) mod 216, R2
DECORR2 = t /64 + 1
mod 216,
where t is the System

Time in frames, relative
to the beginning of the
assigned Quick Paging
Channel slot.
Forward Common NUM_FCCCHs from MC-RR
2 × HASH_KEY [0…11] R+1
Control Channel Parameters Message (up to 7)
Number
3 2.6.7.2 Pseudorandom Number Generator
4 Where pseudorandom numbers are needed, a linear congruential generator shall be used.
5 The mobile station shall implement the linear congruential generator defined by:
6 zn = a × zn - 1 mod m
7 where a = 75 = 16807 and m = 231 - 1 = 2147483647. zn is the output of the generator.19
19 This generator has full period, ranging over all integers from 1 to m-1; the values 0 and m are
never produced. Several suitable implementations can be found in Park, Stephen K. and Miller, Keith
2-498
3GPP2 C.S0005-A v6.0
1 During the Mobile Station Initialization State, the mobile station shall seed its generator with
2 z0 = (ESN ⊕ RANDOM_TIME) mod m
3 where RANDOM_TIME shall be the least-significant 32-bits of SYS_TIMEs stored from the
4 Sync Channel Message. If the initial value so produced is found to be zero, it shall be
5 replaced with one. The mobile station shall compute a new zn for each subsequent use.
6 The mobile station shall use the value un = zn / m for those applications that require a
7 binary fraction un, 0 < un < 1.
8 The mobile station shall use the value kn = N × zn / m for those applications that require
9 a small integer kn, 0 ≤ kn ≤ N - 1.
10 2.6.8 CODE_CHAN_LISTs Maintenance
11 The CODE_CHAN_LISTs is a descriptive structure used to manage the Forward

12 Fundamental Code Channel and Forward Supplemental Code Channels, if any, associated
13 with the mobile station’s Active Set. Associated with each member of the mobile station’s
14 Active Set, there is an ordered array of code channels. The first entry of the ordered array
15 specifies the Forward Fundamental Code Channel associated with the pilot and the
16 subsequent entries, if any, specify the Forward Supplemental Code Channels associated
17 with the pilot. The CODE_CHAN_LISTs is the collection of ordered arrays of code channels
18 for each member of the mobile station’s Active Set. The ith entry in every array (of code
19 channels associated with a member of the Active Set) corresponds to the ith code channel.
20 The mobile station shall maintain the CODE_CHAN_LISTs as follows:
21 • When the mobile station is first assigned a Forward Fundamental Code Channel, it
22 shall initialize the CODE_CHAN_LISTs to contain the Forward Fundamental Code
23 Channel for each member of the Active Set.
24 • When the mobile station processes the Extended Handoff Direction Message, the
25 mobile station shall update the CODE_CHAN_LISTs as follows:
26 − For each pilot listed in the Extended Handoff Direction Message which does not
27 have a corresponding code channel in the CODE_CHAN_LISTs, the mobile
28 station shall add the code channel, CODE_CHAN, of that pilot to the
29 CODE_CHAN_LISTs, as the Forward Fundamental Code Channel for the pilot.
30 − The mobile station shall delete all information in the CODE_CHAN_LISTs

31 associated with a pilot that is not included in the Extended Handoff Direction
32 Message.
W., “Random Number Generators: Good Ones are Hard to Find,” Communications of the ACM, vol. 31,
no. 10, October 1988, pp. 1192-1201.
2-499
3GPP2 C.S0005-A v6.0
1 • When the mobile station processes the General Handoff Direction Message, the
2 mobile station shall update the CODE_CHAN_LISTs to contain the Forward
3 Fundamental Code Channel associated with each pilot included in the General
4 Handoff Direction Message. The first code channel occurrence associated with each
5 pilot included in the General Handoff Direction Message corresponds to the Forward
6 Fundamental Code Channel. The mobile station shall do the following:
7 − If FOR_SUP_CONFIGr is included and FOR_SUP_CONFIGr is equal to ‘10’ or ‘11’,
9 + For each pilot listed in the General Handoff Direction Message, the mobile
10 station shall set the Forward Supplemental Code Channels (associated with
11 the pilot) in the CODE_CHAN_LISTs to the Forward Supplemental Code
12 Channels specified in the General Handoff Direction Message.
13 + The mobile station shall delete all information in the CODE_CHAN_LISTs
14 associated with a pilot that is not included in the General Handoff Direction
15 Message.
16 − If FOR_SUP_CONFIGr is equal to ‘00’ or ‘01’ or if FOR_SUP_CONFIGr is not
17 included in the General Handoff Direction Message, the mobile station shall not
18 update Supplemental Code Channels associated with the pilots included in the
19 General Handoff Direction Message. The mobile station shall perform the
21 + For each pilot listed in the General Handoff Direction Message which does not
22 have a corresponding code channel in the CODE_CHAN_LISTs, the mobile
23 station shall add the code channel, CODE_CHAN, of that pilot to the
24 CODE_CHAN_LISTs, as the Forward Fundamental Code Channel for the
25 pilot.
26 + The mobile station shall delete all information in the CODE_CHAN_LISTs
27 associated with a pilot that is not included in the General Handoff Direction
28 Message.
29 • When the mobile station processes the Supplemental Channel Assignment Message it
30 shall follow the following rules:
31 − If FOR_SUP_CONFIGr is equal to ‘10’ or ‘11’, the mobile station shall update the
32 Forward Supplemental Code Channels for each pilot in the Active Set.
33 − If the pilot is not listed in the Supplemental Channel Assignment Message, the
34 mobile station shall delete all occurrences of Forward Supplemental Code
35 Channels associated with the pilot from the Code Channel List.
36 − If a pilot is listed in the Supplemental Channel Assignment Message, then the
37 mobile station shall set the Forward Supplemental Code Channels (associated
38 with the pilot) in the CODE_CHAN_LISTs to the Forward Supplemental Code
39 Channels specified in the Supplemental Channel Assignment Message.
2-500
3GPP2 C.S0005-A v6.0
1 − If FOR_SUP_CONFIGr is equal to ‘00’ or ‘01’, the mobile station shall not update
2 Supplemental Code Channels associated with the pilots included in the
3 Supplemental Channel Assignment Message.
4 2.6.9 CDMA Tiered Services
5 This section presents an overview and mobile station requirements for the support of CDMA
6 Tiered services while the mobile station is in the Mobile Station Idle State and in the Mobile
8 2.6.9.1 Overview
9 2.6.9.1.1 Definition
10 The mobile station may support Tiered Services based upon User Zones. Tiered Services
11 provide the user custom services and special features based upon the mobile station
12 location. Tiered Services also provides private network support. Important to the operation
13 of CDMA Tiered Services is the concept of User Zones. It is via User Zones by which the
14 base station offers custom services based upon the mobile station location.
15 User Zones are associated with a set of features and services, plus a geographic area in
16 which the User Zone features/services are made available to the customers that have
17 subscribed to that User Zone. The boundary of the User Zone Geographic area may be
18 established based on the coverage area of a public or private base station or it may be
19 established independent of RF topology.
20 User Zones may be supported by the public system on the same frequency as the serving
21 base station, or they may be supported on a private system operating on a different
22 frequency.
23 2.6.9.1.2 Types of User Zones
24 User Zones may be of two basic types:

25 • Broadcast User Zones: Broadcast User Zones are identified to the mobile station using
26 the Paging Channel or the Primary Broadcast Control Channel. In this case, the base
27 station broadcasts on the Paging Channel or the Primary Broadcast Control Channel
28 messages identifying the User Zones that fall within the coverage area of the
29 particular cell/sector. Mobile stations, as part of their monitoring of the Paging
30 Channel or the Primary Broadcast Control Channel, will identify the presence of a
31 particular User Zone.
32 • Mobile Specific User Zones: Mobile Specific User Zones are not broadcast by the base
33 station. The mobile station may use other overhead message parameters and
34 compare them with internally stored User Zone parameters to identify the presence of
35 a particular User Zone. These parameters may include: SID, NID, BASE_ID,
36 BASE_LAT, and BASE_LONG.
37 Broadcast User Zones allow for permanent as well as temporary subscription. Temporary
38 subscription provides User Zone features and capabilities to users who are not subscribed
39 to the User Zone. In this case, a mobile station, upon entering a new coverage area, may
2-501
3GPP2 C.S0005-A v6.0
1 detect the presence of a User Zone that it presently does not subscribe to, but one that
2 supports temporary subscription. The mobile station then queries the network to obtain
3 the User Zone parameters. Once these parameters are received, the mobile station offers to
4 the user via the mobile station user interface, the option of subscribing to the particular
5 User Zone.
6 Some User Zones may require active registration (Active User Zones) upon the mobile
7 station’s entry to immediately trigger a change in a feature(s). For others, the implicit
8 registration at call setup is sufficient (Passive User Zones). Active User Zones are used
9 where inbound features change as a result of being in the User Zone. During the Mobile
10 Station Idle State, a mobile stations needs to register to update the User Zone ID whenever
11 the User Zone that the mobile station is entering and/or leaving is of the Active type.
12 A mobile station that supports User Zone services may store a list of User Zones, where
13 each User Zone is identified by a User Zone ID (UZID). Associated with each stored User
14 Zone, the mobile station may also store a number of determinant parameters used for
15 identifying User Zones.
17 If the mobile station supports User Zone services, it shall maintain and update UZIDs
18 according the following rule:
19 If the mobile station selects a User Zone supported by the base station, the mobile station
20 shall set UZIDs to the User Zone Identifier associated with the User Zone; otherwise, the
21 mobile station shall set UZIDs to ‘0000000000000000’. The precise process for determining
22 how to select a User Zone that is supported by the base station is left to the mobile station
23 manufacturer.
24 If the mobile station does not support User Zone services, the mobile station shall set
25 UZIDs to ‘0000000000000000’.
26 The mobile station may search pilots of private neighbor base stations on other frequencies
27 and band classes as identified in the Private Neighbor List Message. Search performance
28 criteria are defined [11].
29 2.6.9.2.1 User Zone Operation in the Mobile Station Idle State:
30 When a mobile station performs an idle handoff, it selects User Zones based on internally
31 stored parameters and information broadcast on the Paging Channel or on the Primary
32 Broadcast Control Channel as described in 2.6.9.1.
33 After the mobile station performs idle handoff, if the mobile station determines that a
34 change from one Broadcast User Zone to another Broadcast User Zone is required, the
35 mobile station shall not update UZIDs, UZ_EXIT_IN_USEs and shall not perform User Zone
36 registration until the pilot strength of the currently serving base station exceeds that of the
37 base station corresponding to the old User Zone by the value of UZ_EXIT_IN_USEs.
2-502
3GPP2 C.S0005-A v6.0
1 If the mobile station determines that it needs to change User Zone, and if the difference
2 between the pilot strengths exceeds UZ_EXIT_IN_USEs, then the mobile station shall do the
3 following:
4 • Perform User Zone registration.

5 • Update UZIDs.
6 • Set UZ_EXIT_IN_USEs to UZ_EXIT_RCVDs.
7 The mobile station may also implement other means to avoid the premature exiting of a
8 User Zone due to rapid changes in signal strength. The exact implementation of such
9 techniques is left to mobile station implementation.
10 If the mobile station is in the Mobile Station Idle State and it receives a User Zone Reject
11 Message the mobile station shall perform the following:
12 • Set REJECT_ACTION_INDIs to REJECT_ACTION_INDIr.
13 • If UZID_ASSIGN_INCLr = ‘0’, the mobile station shall set UZIDs to

14 ‘0000000000000000’, otherwise; the mobile station shall set UZIDs to
15 ASSIGN_UZIDr.
16 If the mobile station is in the Mobile Station Idle State and it selects an active User Zone,
17 then the mobile station shall perform User Zone registration (see 2.6.5.1.10) by entering the
18 System Access State with a registration indication.
19 The mobile station should provide the user with a User Zone indication corresponding to
20 the User Zone in service each time UZIDs is updated.
21 2.6.9.2.2 User Zone Operation in the Mobile Station Control on the Traffic Channel State
22 If the mobile station is in the Traffic Channel Substate of the Mobile Station Control on the
23 Traffic Channel State and if it determines that the User Zone has changed, it shall update
24 UZIDs and send a User Zone Update Request Message to the base station.
25 If the mobile station is in the Traffic Channel Substate or Release Substate of the Mobile
26 Station Control on the Traffic Channel State and it receives a User Zone Update Message,
27 then the mobile station shall update UZIDs and set it equal to UZIDr.
28 If the mobile station is in the Traffic Channel Substate or Release Substate of the Mobile
29 Station Control on the Traffic Channel State and it receives a User Zone Reject Message, then
31 • Set REJECT_ACTION_INDIs to REJECT_ACTION_ INDIr.
32 • If UZID_ASSIGN_INCLr = 0, the mobile station shall set UZIDs to ‘0’, otherwise; the
33 mobile station shall set UZIDs to ASSIGN_UZIDr.
34 The mobile station should provide the user with a User Zone indication corresponding to
35 the User Zone in service each time UZIDs is updated.
36 2.6.10 Call Control Processing
37 As illustrated in Figure 2.6.10-1, the Call Control consists of the following states:
2-503
3GPP2 C.S0005-A v6.0
1 • Waiting for Order Substate - In this substate, the Call Control instance waits for an
2 Alert With Information Message or an Extended Alert With Information Message.
3 • Waiting for Mobile Station Answer Substate - In this substate, the Call Control
4 instance waits for the user to answer the call.
5 • Conversation Substate - In this substate, the parties involved in this call

6 communicate.
7 • Call Release Substate - In this substate, the Call Control instance waits for the call
8 to be disconnected.
2-504
3GPP2 C.S0005-A v6.0
Mobile station terminated call
Waiting for
Order Substate
(2.6.10.1.1)
Mobile station originated call

Receives a(Extended) Maintenance Order, or or
an (Extended) Alert With Information Message
Receives Mobile station terminated

'call release' indication call, and bypass ordered
by the base station
Waiting for
Mobile Station
Answer Substate
(2.6.10.1.2)
Receives a(Extended)
Maintenance
Mobile station user Order or an (Extended)
answers call Alert With
Information Message*
Receives 'call release'
indication
Conversation
Substate
(2.6.10.2)
Receives(Extended) Alert
With
Information Message
Mobile station user initiates disconnect or 'call

release' indication received
*If SIGNAL_TYPE is
equal
Call Release to '01' or '10' or if
Substate the Signal Information
(2.6.10.3) Record is not included
Note: Not all state

transitions are shown.
3 Figure 2.6.10-1. Call Control
2-505
3GPP2 C.S0005-A v6.0
1 The following messages are processed by the Call Control:
2 - Alert With Information Message
3 - Extended Alert with Information Message:
4 - Flash With Information Message
5 - Extended Flash With Information Message
6 - Send Burst DTMF Message
7 - Origination Continuation Message
8 The following orders are processed by the Call Control:
9 - Continuous DTMF Tone Order
10 - Maintenance Order
11 - Connect Order
12 Upon instantiation, the Call Control instance shall perform the following:
13 • If this Call Control instance is instantiated with a ‘restore indication’, the Call
14 Control instance shall enter the Conversation Substate.
15 • If the call is mobile station terminated, and BYPASS_ALERT_ANSWERs is ‘1’, the

16 Call Control instance shall enter the Conversation Substate. If the call is mobile
17 station terminated and BYPASS_ALERT_ANSWERs is ‘0’, the Call Control instance
18 shall enter the Waiting for Order Substate.
19 • If the call is mobile station originated, the Call Control instance shall enter the
20 Conversation Substate.
21 2.6.10.1 Alerting
22 2.6.10.1.1 Waiting for Order Substate
23 In this substate, the Call Control instance waits for an Alert With Information Message or an
24 Extended Alert With Information Message.
25 Upon entering the Waiting for Order Substate, the Call Control instance shall set the
26 substate timer for T52m seconds.
27 While in the Waiting for Order Substate, the Call Control instance shall perform the
28 following:
2-506
3GPP2 C.S0005-A v6.0
1 • If the substate timer expires, the Call Control instance shall send a “substate timer
2 expired indication” to the layer 3Layer 3 and shall enter the Call Release Substate.
3 • If the Call Control instance receives a “reset waiting for order substate timer
4 indication” from the layer 3Layer 3, the Call Control instance shall reset the
5 substate timer for T52m seconds.
6 • If the Call Control instance receives a “release indication” from the layer 3Layer 3,
7 the Call Control instance shall enter the Call Release Substate.
8 • If the Call Control instance receives an indication that the user has originated an
9 emergency call (see 2.6.4.3), the mobile station shall send a Flash With Information
10 Message or an Extended Flash With Information Message in assured mode with a
11 Global Emergency Call Information Record (see 2.7.4.31), as follows:
12 - If this Call Control instance is identified by NULL, the mobile station shall send
13 either a Flash With Information Message or an Extended Flash With Information
14 Message (with either the CON_REF_INCL field of the message set to ‘0’ or the
15 CON_REF_INCL field set to ‘1’ and the CON_REF field set to the connection
16 reference of the service option connection corresponding to this call); otherwise,
17 the mobile station shall send an Extended Flash With Information Message, with
18 the CON_REF_INCL field of the message set to ‘1’ and the CON_REF field of the
19 message set to the connection reference of the service option connection
20 corresponding to this call.
21 • If the Call Control instance receives a message from the layer 3Layer 3 which is
22 included in the following list and every message field value is within its permissible
23 range, the Call Control instance shall process the message as described below and
24 in accordance with the message’s action time (see 2.6.4.1.5).
25 1. Alert With Information Message: If the message contains a Signal information

26 record, the mobile station should alert the user in accordance with the Signal
27 information record; otherwise, the mobile station should use standard alert as
28 defined in 3.7.5.5. The Call Control instance shall enter the Waiting for Mobile
29 Station Answer Substate (see 2.6.10.1.2).
30 2. Extended Alert with Information Message: If the message contains a Signal

31 information record, the mobile station should alert the user in accordance with
32 the Signal information record; otherwise, the mobile station should use
33 standard alert as defined in 3.7.5.5. The Call Control instance shall enter the
34 Waiting for Mobile Station Answer Substate (see 2.6.10.1.2).
35 3. Maintenance Order: The Call Control instance shall enter the Waiting for Mobile
36 Station Answer Substate.
2-507
3GPP2 C.S0005-A v6.0
1 • If the Call Control instance receives a message that is not included in the above list,
2 cannot be processed, or requires a capability which is not supported, the Call
3 Control instance shall discard the message and send a ‘message rejected indication’
4 to the layer 3Layer 3, with the reject reason indicated.
5 2.6.10.1.2 Waiting for Mobile Station Answer Substate
6 In this substate, the Call Control instance waits for the user to answer the mobile station
7 terminated call or to invoke special treatment.
8 Upon entering the Waiting for Mobile Station Answer Substate, the Call Control instance
9 shall set the substate timer for T53m seconds.
10 While in the Waiting for Mobile Station Answer Substate, the Call Control instance shall
12 • If the substate timer expires, the Call Control instance shall send a “substate timer
13 expired indication” to the layer 3Layer 3 and shall enter the Call Release Substate.
16 • If the Call Control instance is directed by the user to answer the call, the mobile
17 station shall send a Connect Order in assured mode:

19 perform the following: If this Call Control instance is identified by NULL, the
22 reference of the service option connection corresponding to this call; otherwise,
23 the mobile station shall set the CON_REF_INCL field of the message to ‘1’ and
24 the CON_REF field of the message to the connection reference of the service
25 option connection corresponding to this call.
26 The Call Control instance shall enter the Conversation Substate.
27 • If the Call Control instance is directed by the user to forward the incoming call, the
28 mobile station shall send a Flash With Information Message or an Extended Flash
29 With Information Message in assured mode with a Keypad Facility information record
30 (see 2.7.4.2) with the CHARi field set to a pre-programmed feature code which
31 indicates User Selective Call Forwarding with a pre-registered number, as follows:
32 - If P_REV_IN_USEs is less than seven, the mobile station shall send a Flash With
33 Information Message.
2-508
3GPP2 C.S0005-A v6.0

2 perform the following: if this Call Control instance is identified by NULL, the
3 mobile station shall send either a Flash With Information Message or an
4 Extended Flash With Information Message (with either the CON_REF_INCL field of
5 the message set to ‘0’ or the CON_REF_INCL field set to ‘1’ and the CON_REF
6 field set to the connection reference of the service option connection
7 corresponding to this call); otherwise, the mobile station shall send an Extended
8 Flash With Information Message, with the CON_REF_INCL field of the message
9 set to ‘1’ and the CON_REF field of the message set to the connection reference
10 of the service option connection corresponding to this call.
11 • If the Call Control instance is directed by user to forward the incoming call to a
12 number stored in the mobile station, the mobile station shall send a Flash With
13 Information Message or an Extended Flash With Information Message in assured
14 mode with a Keypad Facility information record (see 2.7.4.2) with the CHARi field set
15 to the following:
16 - a pre-programmed feature code which indicates User Selective Call

17 Forwarding to a number stored in the mobile station as the first digits in
18 the field and
19 - the forwarding to number immediately following the pre-programmed

20 feature code.
21 The mobile station shall send the message as follows:

34 • If the Call Control instance is directed by the user to forward the incoming call to
35 network-based voice mail, the mobile station shall send a Flash With Information
37 Keypad Facility information record (see 2.7.4.2) with the CHARi field set to a pre-
38 programmed feature code which indicates User Selective Call Forwarding to voice
39 mail, as follows:
2-509
3GPP2 C.S0005-A v6.0

13 • If the Call Control instance is directed by the user to activate answer holding, the
15 With Information Message in assured mode requiring confirmation of delivery with a
17 programmed feature code which indicates Answer Holding:

30 After receiving confirmation of delivery of the Flash With Information Message or the
31 Extended Flash With Information Message, the mobile station shall send a Connect
32 Order in assured mode:

2-510
3GPP2 C.S0005-A v6.0
1 The Call Control instance shall enter the Conversation Substate.
6 - If this Call Control instance is identified by NULL, the mobile station shall send
15 • If the Call Control instance receives a message from layer 3Layer 3 which is
19 1. Alert With Information Message: The Call Control instance shall reset the
20 substate timer for T53m seconds. If this message does not contain a Signal
21 information record, the mobile station should use standard alert as defined in
22 3.7.5.5.
23 2. Extended Alert With Information Message: The Call Control instance shall reset
24 the substate timer for T53m seconds. If this message does not contain a Signal
25 information record, the mobile station should use standard alert as defined in
26 3.7.5.5.
27 3. Maintenance Order: The mobile station shall reset the substate timer for T53m
28 seconds.
33 2.6.10.2 Conversation Substate
34 While in the Conversation Substate, the Call Control instance shall perform the following:
2-511
3GPP2 C.S0005-A v6.0
1 • The mobile station shall send an Origination Continuation Message in assured mode,
2 within T54m seconds after the Call Control instance entering the Conversation
3 Substate if any of the following conditions occur:
4 – The mobile station originated the call, and did not send all the dialed digits in
5 the Origination Message.
6 – There is more than one calling party number associated with the mobile station.
7 – A calling party subaddress is used in the call.
8 – A called party subaddress is used in the call.
9 If more than one calling party number is associated with the mobile station, the
10 mobile station shall include the calling party number being used in the calling party
11 number information record in the Origination Continuation Message. If only one
12 calling party number is associated with the mobile station, the mobile station shall
13 not include the calling party number information record in the Origination
14 Continuation Message. If a calling party subaddress is used, the mobile station shall
15 include the calling party subaddress information record in the Origination
16 Continuation Message: otherwise, the mobile station shall omit the calling party
17 subaddress information record. If a called party subaddress is used, the mobile
18 station shall include the called party subaddress information record in the
19 Origination Continuation Message: otherwise, the mobile station shall omit the calling
20 called party subaddress information record.
21 • If the Call Control instance is directed by the user to issue a flash, the mobile
22 station shall build a Flash With Information Message or an Extended Flash With
23 Information Message with the collected digits or characters contained in a Keypad
24 Facility information record, if needed, and shall send the message in assured mode,
25 as follows:

2-512
3GPP2 C.S0005-A v6.0
1 • If the Call Control instance is directed by the user to forward the incoming call, the
3 With Information Message in assured mode with a Keypad Facility information record
4 (see 2.7.4.2) with the CHARi field set to a pre-programmed feature code which
5 indicates User Selective Call Forwarding with a pre-registered number, as follows:

18 • If the Call Control instance is directed by the user to forward the incoming call to a
19 number stored in the mobile station, the mobile station shall send a Flash With
20 Information Message or an Extended Flash With Information Message in assured
21 mode with a Keypad Facility information record (see 2.7.4.2) with the CHARi field set
22 to the following:
23 - a pre-programmed feature code which indicates User Selective Call

24 Forwarding to a number stored in the mobile station as the first digits in
25 the field and
26 - the forwarding to number immediately following the pre-programmed

27 feature code.
28 The mobile station shall send the message as follows:
31 - If P_REV_IN_USEs is equal to or greater than seven and if this Call Control

32 instance is identified by NULL, the mobile station shall send either a Flash With
33 Information Message or an Extended Flash With Information Message (with either
34 the CON_REF_INCL field of the message set to ‘0’ or the CON_REF_INCL field set
35 to ‘1’ and the CON_REF field set to the connection reference of the service option
36 connection corresponding to this call). Otherwise, the mobile station shall send
37 an Extended Flash With Information Message, with the CON_REF_INCL field of
38 the message set to ‘1’ and the CON_REF field of the message set to the
39 connection reference of the service option connection corresponding to this call.
2-513
3GPP2 C.S0005-A v6.0
1 • If the Call Control instance is directed by the user to forward the incoming call to
2 network-based voice mail, the mobile station shall send a Flash With Information
5 programmed feature code which indicates User Selective Call Forwarding to voice
6 mail, as follows:
9 - If P_REV_IN_USEs is equal to or greater than seven and if this Call Control

10 instance is identified by NULL, the mobile station shall send either a Flash With
11 Information Message or an Extended Flash With Information Message (with either
12 the CON_REF_INCL field of the message set to ‘0’ or the CON_REF_INCL field set
13 to ‘1’ and the CON_REF field set to the connection reference of the service option
14 connection corresponding to this call). Otherwise, the mobile station shall send
15 an Extended Flash With Information Message, with the CON_REF_INCL field of
16 the message set to ‘1’ and the CON_REF field of the message set to the
17 connection reference of the service option connection corresponding to this call.
18 • If the Call Control instance is directed by the user to activate answer holding, the
20 With Information Message in assured mode requiring confirmation of delivery with a
22 programmed feature code which indicates Answer Holding, as follows:

2-514
3GPP2 C.S0005-A v6.0
1 • If answer holding is activated and the Call Control instance is directed by the user
2 to deactivate answer holding, the mobile station shall send a Flash With Information
5 programmed feature code which indicates Answer Holding, as follows:

18 • If the Call Control instance is directed by the user to send burst DTMF digits, the
19 mobile station shall build the Send Burst DTMF Message with the dialed digits and
20 shall send the message in assured mode requiring confirmation of delivery.

23 mobile station shall set the CON_REF_INCL field of the message to ‘0’; otherwise,
27 The mobile station sending multiple Send Burst DTMF Messages shall preserve
28 relative ordering of these messages (see 1.6 of [4]). The mobile station should
29 attempt to preserve the user timing as much as possible, using recommended values
30 of DTMF_ON_LENGTH (see Table 2.7.2.3.2.7-1) and DTMF_OFF_LENGTH (see Table
31 2.7.2.3.2.7-2).
32 • If the Call Control instance is directed by the user to send a continuous DTMF digit,
33 the mobile station shall build the Continuous DTMF Tone Order with the dialed digit
34 and shall send the order in assured mode requiring confirmation of delivery, as
35 follows:
2-515
3GPP2 C.S0005-A v6.0

9 When the Call Control instance is directed by the user to cease sending the
10 continuous DTMF digit, the mobile station shall send the Continuous DTMF Tone
11 Order (ORDQ = ‘11111111’) in assured mode requiring confirmation of delivery, as
12 follows:

21 The mobile station sending multiple Continuous DTMF Tone Orders shall preserve
22 relative ordering of these messages (see [2]). The mobile station shall send the
23 Continuous DTMF Tone Order with the ORDQ set to ‘11111111’ indicating the
24 completion of the current continuous DTMF digit before sending the Continuous
25 DTMF Tone Order for another digit or the Send Burst DTMF Message.
26 • If the Call Control instance is directed by the user to disconnect the call, the Call
27 Control instance shall send a ‘call release request’ to the layer 3Layer 3 and shall
28 enter the Call Release Substate.
29 • If the Call Control instance receives an indication that this packet data service
30 instance has been inactivated, the Call Control instance shall send a “call inactive
31 indication” to the layer 3Layer 3 and shall enter the Call Release Substate.
36
2-516
3GPP2 C.S0005-A v6.0
1 − If this Call Control instance is identified by NULL, the mobile station shall send
14 1. Alert With Information Message: If the message contains a Signal information

15 record with the SIGNAL_TYPE field set to ‘01’ or ‘10’, or if the message does not
16 contain a Signal information record, the Call Control instance shall enter the
17 Waiting For Mobile Station Answer Substate. The mobile station should alert the
18 user in accordance with the Signal information record. If this message does not
19 contain a Signal information record, the mobile station should use standard
20 alert as defined in 3.7.5.5.
21 2. Continuous DTMF Tone Order
22 3. Extended Alert With Information Message: If the message contains a Signal

23 information record with the SIGNAL_TYPE field set to ‘01’ or ‘10’, or if the
24 message does not contain a Signal information record, the Call Control instance
25 shall enter the Waiting For Mobile Station Answer Substate. The mobile station
26 should alert the user in accordance with the Signal information record. If this
27 message does not contain a Signal information record, the mobile station should
28 use standard alert as defined in 3.7.5.5.
29 4. Flash With Information Message
30 5. Extended Flash With Information Message
31 6. Maintenance Order: The Call Control instance shall enter the Waiting for Mobile
32 Station Answer Substate.
33 7. Send Burst DTMF Message:
2-517
3GPP2 C.S0005-A v6.0
1 2.6.10.3 Call Release Substate
2 In this substate, the Call Control instance waits for the call to be released.
3 While in the Call Release Substate, the Call Control instance shall perform the following:
8 1. Alert With Information Message: The Call Control instance shall send an “enter
9 traffic channel substate indication” to the layer 3Layer 3 and shall enter the
10 Waiting for Mobile Station Answer Substate. If this message does not contain a
11 Signal information record, the mobile station should use standard alert as
12 defined in 3.7.5.5.
13 2. Extended Alert With Information Message: The Call Control instance shall send a
14 “enter traffic channel substate indication” to layer 3Layer 3 and shall enter the
15 Waiting for Mobile Station Answer Substate. If this message does not contain a
16 Signal information record, the mobile station should use standard alert as
17 defined in 3.7.5.5.
22 2.6.11 SYNC_ID Computation
23 The SYNC_ID shall be calculated on all bits within the service configuration (that is, both
24 the Service Configuration information record and the Non-negotiable Service Configuration
25 information record).
26 The generator polynomials for computation of the SYNC_ID shall be as follows:
27 g(x) = x16 + x15 + x14 + x11 + x6 + x5 + x2 + x + 1
28 The SYNC_ID shall be computed according to the following procedure as shown in Figures
29 2.6.11-1:
30 •Initially, all shift register elements shall be set to logical one and the switches
31 shall be set in the up position.
32 •The register shall be clocked a number of times equal to the number bits in the
33 service configuration (that is, both the Service Configuration information
34 record and the Non-negotiable Service Configuration information record) with
35 those bits as input. The Service Configuration information record bits shall
36 be input first (starting with the first field of the record) followed by the Non-
37 negotiable Service Configuration information record bits (starting at the first
38 field of the record).
2-518
3GPP2 C.S0005-A v6.0
1 •The switches shall be set in the down position so that the output is a modulo-2
3 •The register shall be clocked an additional 16 times.
4 •These additional bits shall be the SYNC_ID.
5 •The first bit calculated shall be the most significant bit of SYNC_ID.
Input
0
x0 x1 x2 x5 x6 x11 x14 x15
Output
0
Denotes one-bit storage element Up for the Service
Configuration bits
Denotes modulo-2 addition Down for the last 16 bits
7
9 Figure 2.6.11-1. SYNC_ID Calculation
10
2-519
3GPP2 C.S0005-A v6.0
1 2.7 PDU Formats for Mobile Stations
2 This section describes the formats of the PDUs corresponding to the messages sent by the
3 mobile station.
4 In any multi-bit field in the following messages, the most significant bit (MSB) shall be
5 transmitted first.
6 Some bits in the PDUs are marked as RESERVED. These bits allow extension of the PDUs
7 for future features and capabilities. The mobile station sets all reserved bits to ‘0’.
2-519
3GPP2 C.S0005-A v6.0
1 2.7.1 r-csch
2 This section describes the messages and their PDU formats sent by the mobile station on
3 the r-csch.
4 2.7.1.1 Reserved
5 2.7.1.2 Reserved
6 2.7.1.3 PDU Formats on r-csch
7 The messages sent on the r-csch are summarized in Table 2.7.1.3-1.
9 Table 2.7.1.3-1. Messages on r-csch
Message Name MSG_TAG Section Number
Registration Message RGM 2.7.1.3.2.1

Order Message ORDM 2.7.1.3.2.2
Data Burst Message DBM 2.7.1.3.2.3
Origination Message ORM 2.7.1.3.2.4
Page Response Message PRM 2.7.1.3.2.5
Authentication Challenge Response Message AUCRM 2.7.1.3.2.6
Status Response Message STRPM 2.7.1.3.2.7
TMSI Assignment Completion Message TACM 2.7.1.3.2.8
PACA Cancel Message PACNM 2.7.1.3.2.9
Extended Status Response Message ESTRPM 2.7.1.3.2.10
Device Information Message DIM 2.7.1.3.2.11
Security Mode Request Message SMRM 2.7.1.3.2.12
10 2.7.1.3.1 Reserved
11 2.7.1.3.2 PDU Contents
12 The following sections specify the contents of the PDU for each message that may be sent
13 on the r-csch.
2-520
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.1 Registration Message
2 MSG_TAG: RGM
Field Length (bits)

REG_TYPE 4
SLOT_CYCLE_INDEX 3
MOB_P_REV 8
SCM 8
MOB_TERM 1
RETURN_CAUSE 4
QPCH_SUPPORTED 0 or 1
ENHANCED_RC 0 or 1
UZID_INCL 0 or 1
UZID 0 or 16
GEO_LOC_INCL 0 or 1
GEO_LOC_TYPE 0 or 3
OTD_SUPPORTED 0 or 1
STS_SUPPORTED 0 or 1
3X_CCH_SUPPORTED 0 or 1
WLL_INCL 0 or 1
WLL_DEVICE_TYPE 0 or 3
HOOK_STATUS 0 or 4
ENC_INFO_INCL 0 or 1
SIG_ENCRYPT_SUP 0 or 8
C_SIG_ENCRYPT_REQ 0 or 1
KEY_SEQ_NEW_INCL 0 or 1
KEY_SEQ_NEW 0 or 4
ENC_SEQ_H 0 or 24
ENC_SEQ_H_SIG 0 or 8
UI_ENCRYPT_SUP 0 or 8
5 REG_TYPE – Registration type.

6 This field indicates which type of event generated the
7 registration attempt.
8 The mobile station shall set this field to the REG_TYPE value
9 shown in Table 2.7.1.3.2.1-1 corresponding to the event that
10 caused this registration to occur (see 2.6.5.1).
2-521
3GPP2 C.S0005-A v6.0
2 Table 2.7.1.3.2.1-1. Registration Type (REG_TYPE) Codes
REG_TYPE
(binary) Type of Registration
0000 Timer-based (see 2.6.5.1.3)

0001 Power-up (see 2.6.5.1.1)
0010 Zone-based (see 2.6.5.1.5)
0011 Power-down (see 2.6.5.1.2)
0100 Parameter-change (see 2.6.5.1.6)
0101 Ordered (see 2.6.5.1.7)
0110 Distance-based (see 2.6.5.1.4)
0111 User Zone-based (see 2.6.5.1.10)
1000 Encryption Re-sync required (see 2.6.5.1.11)
All other REG_TYPE values are reserved.
4 SLOT_CYCLE_INDEX – Slot cycle index.

5 If the mobile station is configured for slotted mode operation,
6 the mobile station shall set this field to the preferred slot cycle
7 index, SLOT_CYCLE_INDEXp (see 2.6.2.1.1). Otherwise, the
8 mobile station shall set this field to ‘000’.
9 MOB_P_REV – Protocol revision of the mobile station.
10 The mobile station shall set this field to ‘00000111’.
11 SCM – Station class mark.
12 The mobile station shall set this field to its station class mark.
13 See 2.3.3.
14 MOB_TERM – Mobile terminated calls accepted indicator.
15 If the mobile station is configured to accept mobile terminated
16 calls while operating with the current roaming status (see
17 2.6.5.3), the mobile station shall set this bit to ‘1’. Otherwise,
18 the mobile station shall set this bit to ‘0’.
19 RETURN_CAUSE – Reason of the mobile station registration or access.
20 The mobile station shall set this field to the RETURN_CAUSE
21 value shown in Table 2.7.1.3.2.1-2 corresponding to the
22 service redirection failure condition (see 2.6.1.1).
23
2-522
3GPP2 C.S0005-A v6.0
1 Table 2.7.1.3.2.1-2. RETURN_CAUSE Codes
RETURN_CAUSE
Redirect Failure Condition
(binary)
0000 Normal access.

0001 Service redirection failed as a result of
system not found.
protocol mismatch.
registration rejection.
wrong SID.
wrong NID.
All other RETURN_CAUSE values are reserved.
3 QPCH_SUPPORTED – Quick Paging Channel supported indicator.

4 If P_REV_IN_USEs is less than six, the mobile station shall
5 omit this field; otherwise, the mobile station shall include this
6 field and set it as follows.
7 If the mobile station supports the Quick Paging Channel, the
8 mobile station shall set this field to ‘1’; otherwise, the mobile
9 station shall set this field to ‘0’.
10 ENHANCED_RC – Enhanced radio configuration supported indicator.
14 If the mobile station supports any radio configuration in the
15 Radio Configuration Class 2 (see 1.1.1), the mobile station
16 shall set this field to ‘1’; otherwise, the mobile station shall set
17 this field to ‘0’.
18 UZID_INCL – User Zone Identifier included indicator.
22 If the message is to contain the User Zone Identifier, the
25 UZID – User Zone Identifier.
2-523
3GPP2 C.S0005-A v6.0
1 If the UZID_INCL is included in the message and is set to ‘1’,

2 the mobile station shall include this field and set it to UZIDs;
3 otherwise, the mobile station shall omit this field.
4 GEO_LOC_INCL – Geo-location included indicator.
5 If P_REV_IN_USEs is less than seven, the mobile station shall
8 If the message is to contain the GEO_LOC_TYPE field, the
11 GEO_LOC_TYPE – Geo-Location Type.
12 If GEO_LOC_INCL is included in the message and is set to ‘1’,
13 the mobile station shall include this field and shall set it to
14 the value shown in Table 2.7.1.3.2.4-7; otherwise, the mobile
15 station shall omit this field.
16 OTD_SUPPORTED – Orthogonal Transmit Diversity supported.
20 The mobile station shall set this field to ‘1’ if Orthogonal
21 Transmit Diversity is supported; otherwise, the mobile station
22 shall set this field to ‘0’.
23 STS_SUPPORTED – Space Time Spreading Transmit Diversity supported.
27 The mobile station shall set this field to ‘1’, if Space Time
28 Spreading Transmit Diversity is supported; otherwise, the
30 3X_CCH_SUPPORTED – 3X Common Channels supported.
34 The mobile station shall set this field to ‘1’ if the mobile
35 station supports the Spreading Rate 3 common channels (3X
36 BCCH, 3X F-CCCH, and 3X R-EACH); otherwise, the mobile
38 WLL_INCL – WLL information included indicator.
42 If the mobile station is a Wireless Local Loop device, the
2-524
3GPP2 C.S0005-A v6.0
1 WLL_DEVICE_TYPE – WLL device type indicator.

2 If WLL_INCL is not included, or if WLL_INCL is included and is
3 set to ‘0’, the mobile station shall omit this field; otherwise,
4 the mobile station shall set this field as follows.
5 The mobile station shall set this field to the
6 WLL_DEVICE_TYPE value shown in Table 2.7.1.3.2.1-3
7 corresponding to the mobile station device type.
8 Table 2.7.1.3.2.1-3. WLL Device Types
WLL_DEVICE_TYPE Description
(binary)
000 Wireless Local Loop terminal with no

mobility
001 Wireless Local Loop terminal with
limited mobility
010 Wireless Local Loop terminal with full
mobility
011 - 111 Reserved
10 HOOK_STATUS – WLL terminal hook status.

13 the mobile station shall set this field to the value shown in
14 Table 2.7.1.3.2.1-4 corresponding to the hook state.
2-525
3GPP2 C.S0005-A v6.0
1 Table 2.7.1.3.2.1-4. Hook Status Values
HOOK_STATUS Description
(binary)
0000 Subscriber terminal is on-hook

0001 Subscriber terminal is off-hook
0010 Subscriber terminal is stuck off-hook
0011 – 1111 Reserved
3 ENC_INFO_INCL – Encryption fields included.

7 The mobile station shall set this field to ‘1’ if the encryption
8 related fields are included; otherwise the mobile station shall
9 set this field to ‘0’. The mobile station shall set this field to ‘1’
10 if it is unable to determine the base station support for
11 encryption. The mobile station shall set this field to ‘0’ if the
12 base station does not support encryption or the mobile station
13 does not support any of the encryption modes supported by
15
16 SIG_ENCRYPT_SUP – Signaling Eencryption supported indicator.

17 If ENC_INFO_INCL is included and is set to ‘1’, the mobile
18 station shall include this field; otherwise, the mobile station
19 shall omit this field. If this field is included, the mobile
20 station shall set this field to indicate which signaling
21 encryption algorithms are supported by the mobile station.
2-526
3GPP2 C.S0005-A v6.0
1 This field consists of the subfields shown in Table 2.7.1.3.2.1-

2 5.
3 Table 2.7.1.3.2.1-5. Encoding of the SIG_ENCRYPT_SUP Field
Length
Subfield (bits) Subfield Description
CMEA 1 Support of Cellular Message

Encryption Algorithm
ECMEA 1 Support of Enhanced Cellular Message
Encryption Algorithm
REA 1 Support of the Rijndael Encryption
Algorithm
RESERVED 56 Reserved bits
4 If this field is included, the mobile station shall set the

5 subfields as follows:
6 The mobile station shall set the CMEA subfield to ‘1’.
7 The mobile station shall set each other subfield to ‘1’ if the
8 corresponding signaling encryption algorithm is supported by
9 the mobile station; otherwise, the mobile station shall set the
10 subfield to ‘0’.
11 The mobile station shall set the RESERVED subfield to
12 ‘000000’.
13 C_SIG_ENCRYPT_REQ – Common Channel sSignaling mMessage encryption
14 request indicator.
18 station shall set this field to ‘1’ to request signaling encryption
19 to be turned on for signaling messages sent on f-dsch, r-dsch,
20 f-csch, and r-csch, and to ‘0’ to request signaling encryption
21 to be turned off for signaling messages sent on f-dsch, r-dsch,
22 f-csch, and r-csch.
23 KEY_SEQ_NEW_INCL – The new encryption key sequence number included indicator.
26 shall omit this field. If this field is included, the mobile station
27 shall set this field as follows:
28 If STORE_KEYs is equal to ‘1’ and KEY_SEQ_NEW is included in
29 this message, the mobile station shall set this field to ‘1’;
30 otherwise, the mobile station shall set this field to ‘0’.
31 KEY_SEQ_NEW – The key sequence number corresponding to the new encryption
32 key generated by the mobile station.
33
2-527
3GPP2 C.S0005-A v6.0
1 If KEY_SEQ_NEW_INCL is included and is set to ‘1’, the mobile

2 station shall include this field; otherwise, the mobile station shall
3 omit this field. If this field is included, the mobile station shall set
4 this field to KEY_SEQ_NEWs-p, the sequence number associated
5 with the new encryption key generated by the mobile station.
6 ENC_SEQ_H – The 24 MSB of the EXT_ENC_SEQ
7 If ENC_INFO_INCL is included and is set to ‘1’,

8 SIG_ENCRYPT_SUP is included and the ECMEA or REA
9 subfield in SIG_ENCRYPT_SUP is set to ‘1’and Enhanced
10 Cellular Message Encryption Algorithm is supported by the
11 mobile station, the mobile station shall include this field;
12 otherwise, the mobile station shall omit this field. If this field
13 is included, the mobile station shall set this field to the 24
14 most significant bits of the EXT_ENC_SEQ to be used as the
15 initial value of crypto sync for both forward and reverse link
16 encryptions.
17 ENC_SEQ_H_SIG – The signature of ENC_SEQ_H
18 If ENC_SEQ_H is included, the mobile station shall include
19 this field; otherwise, the mobile station shall omit this field. If
20 this field is included, the mobile station shall set this field to
21 the digital signature of the ENC_SEQ_H computed as
23 UI_ENCRYPT_SUP - User information eEncryption supported indicator.
27 station shall set this field to indicate the supported user
28 information encryption algorithms.
30 9.
31 The mobile station shall set each subfield to ‘1’ if the
32 corresponding user information encryption algorithm is
33 supported by the mobile station; otherwise, the mobile station
34 shall set the subfield to ‘0’.
36 ‘000000’.
2-528
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.2 Order Message
2 MSG_TAG: ORDM
Field Length (bits)
ORDER 6
ADD_RECORD_LEN 3
Order-specific fields (if used) 8 × ADD_RECORD_LEN
5 ORDER – Order code.

6 The mobile station shall set this field to the ORDER code
7 (see 2.7.3) for this type of Order Message.
8 ADD_RECORD_LEN – Additional record length.
9 The mobile station shall set this field to the number of octets
10 in the order-specific fields included in this message.
11 order-specific fields – Order-specific fields.
12 The mobile station shall include order-specific fields as
2-529
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.3 Data Burst Message
2 MSG_TAG: DBM
Field Length (bits)

MSG_NUMBER 8
BURST_TYPE 6
NUM_MSGS 8
NUM_FIELDS 8
NUM_FIELDS occurrences of the following field:
CHARi 8
4
5 MSG_NUMBER – Message number within the data burst stream.

6 The mobile station shall set this field to the number of this
7 message within the data burst stream.
8 BURST_TYPE – Data burst type.
9 The mobile station shall set the value of this field for the type
10 of this data burst as defined in [30]. If the mobile station sets
11 this field equal to ‘111110’, it shall set the first two CHARi
12 fields of this message equal to
13 EXTENDED_BURST_TYPE_INTERNATIONAL as described in
14 the definition of CHARi below. If the mobile station sets this
15 field equal to ‘111111’, it shall set the first two CHARi fields of
16 this message equal to the EXTENDED_BURST_TYPE as
17 described in the definition of CHARi below.
18 NUM_MSGS – Number of messages in the data burst stream.
19 The mobile station shall set this field to the number of
20 messages within this data burst stream.
21 NUM_FIELDS – Number of characters in this message.
22 The mobile station shall set this field to the number of CHARi
23 fields included in this message.
24 CHARi – Character.
25 The mobile station shall include NUM_FIELDS occurrences of
26 this field. The mobile station shall set these fields to the
27 corresponding octet of the data burst stream.
2-530
3GPP2 C.S0005-A v6.0
1 If the BURST_TYPE field of this message is equal to ‘111110’,

2 the first two CHARi octets shall represent a 16 bit
3 EXTENDED_BURST_TYPE_INTERNATIONAL field, which is
4 encoded as shown below. The first ten bits of this field
5 contain a binary mapping of the Mobile Country Code (MCC).
6 Encoding of the MCC shall be as specified in 2.3.1.3. The
7 remaining six bits of the
8 EXTENDED_BURST_TYPE_INTERNATIONAL field shall specify
9 the COUNTRY_BURST_TYPE. The mobile station shall set the
10 value of the COUNTRY_BURST_TYPE according to the type of
11 this data burst as defined in standards governed by the
12 country where this data burst type is to be used.
13
Field Length (bits)
Mobile Country Code 10

COUNTRY_BURST_TYPE 6
Remaining CHARi fields 8 × (NUM_FIELDS - 2)
14

16 the first two CHARi octets shall represent a single, 16 bit,
17 EXTENDED_BURST_TYPE field, as shown below. The mobile
18 station shall set the value of the EXTENDED_BURST_TYPE
19 according to the type of this data burst as defined in [30].
20
Field Length (bits)
EXTENDED_BURST_TYPE 16
(first two CHARi fields)
21
2-531
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.4 Origination Message
2 MSG_TAG: ORM
Field Length (bits)
MOB_TERM 1
SLOT_CYCLE_INDEX 3
MOB_P_REV 8
SCM 8
REQUEST_MODE 3
SPECIAL_SERVICE 1
SERVICE_OPTION 0 or 16
PM 1
DIGIT_MODE 1
NUMBER_TYPE 0 or 3
NUMBER_PLAN 0 or 4
MORE_FIELDS 1
NUM_FIELDS 8
CHARi 4 or 8
NAR_AN_CAP 1
PACA_REORIG 1
RETURN_CAUSE 4
MORE_RECORDS 1
ENCRYPTION_SUPPORTED 0 or 4
PACA_SUPPORTED 1
NUM_ALT_SO 3
NUM_ALT_SO occurrences of the following field:
ALT_SO 16
(continues on next page)
2-532
3GPP2 C.S0005-A v6.0
Field Length (bits)
DRS 0 or 1
UZID_INCL 0 or 1
UZID 0 or 16
CH_IND 0 or 2
SR_ID 0 or 3
ENHANCED_RC 0 or 1
FOR_RC_PREF 0 or 5
REV_RC_PREF 0 or 5
FCH_SUPPORTED 0 or 1
FCH Capability Type-specific fields 0 or variable
DCCH_SUPPORTED 0 or 1
DCCH Capability Type-specific 0 or variable
fields
GEO_LOC_INCL 0 or 1
GEO_LOC_TYPE 0 or 3
REV_FCH_GATING_REQ 0 or 1
ORIG_REASON 0 or 1
ORIG_COUNT 0 or 2
WLL_INCL 0 or 1
GLOBAL_EMERGENCY_CALL 0 or 1
MS_INIT_POS_LOC_IND 0 or 1
QOS_PARMS_INCL 0 or 1
QOS_PARMS_LEN 0 or 5
2-533
3GPP2 C.S0005-A v6.0
Field Length (bits)
QOS_PARMS 0 or variable
QOS_RESERVED 0-7
D_SIG_ENCRYPT_REQ 0 or 1
C_SIG_ENCRYPT_REQ
KEY_SEQ_NEW 0 or 4
ENC_SEQC_H 0 or 24
UI_ENCRYPT_REQ 0 or 1
SYNC_ID_INCL 0 or 1
SYNC_ID_LEN 0 or 4
SYNC_ID 0 or (8 x
16SYNC_ID_LEN)
PREV_SID_INCL 0 or 1
PREV_SID 0 or 15
PREV_NID_INCL 0 or 1
PREV_NID 0 or 16
PREV_PZID_INCL 0 or 1
PREV_PZID 0 or 8
If P_REV_IN_USEs is equal to or greater than 7, the mobile
station shall include the following fields:
SO_BITMAP_IND 0 or 2
SO_GROUP_NUM 0 or 5
SO_BITMAP 0 or 4 ×
SO_BITMAP_IND

5 2.6.5.3), the mobile station shall set this bit to ‘1’; otherwise,
2-534
3GPP2 C.S0005-A v6.0

4 index, SLOT_CYCLE_INDEXp (see 2.6.2.1.1); otherwise, the
9 The mobile station shall set this field to the station class mark
10 of the mobile station. See 2.3.3.
11 REQUEST_MODE – Requested mode code.
12 The mobile station shall set this field to the value shown in
13 Table 2.7.1.3.2.4-1 corresponding to its current configuration.
14
15 Table 2.7.1.3.2.4-1. REQUEST_MODE Codes
Value (binary) Requested Mode
000 Reserved
001 CDMA only
010 Wide analog only
011 Either wide analog or CDMA only
100 Narrow analog only
101 Either narrow analog or CDMA only
110 Either narrow analog or wide analog only
111 Narrow analog or wide analog or CDMA
16
17 SPECIAL_SERVICE – Special service option indicator.

18 To request a special service option, the mobile station shall set
19 this field to ‘1’. To request the default service option (Service
20 Option 1), the mobile station shall set this field to ‘0’.
21 SERVICE_OPTION – Requested service option for this origination.
22 If the SPECIAL_SERVICE field is set to ‘1’, the mobile station
23 shall set this field to the value specified in [30], corresponding
24 to the requested service option. If the SPECIAL_SERVICE
25 field is set to ‘0’, the mobile station shall omit this field.
26 PM – Privacy mode indicator.
27 To request voice privacy, the mobile station shall set this field
28 to ‘1’; otherwise, the mobile station shall set this field to ‘0’.
29 DIGIT_MODE – Digit mode indicator.
2-535
3GPP2 C.S0005-A v6.0
1 This field indicates whether the dialed digits are 4-bit DTMF
2 codes or 8-bit ASCII codes using a specified numbering plan.
3 To originate the call using the binary representation of DTMF
4 digits, the mobile station shall set this field to ‘0’. To originate
5 the call using ASCII characters, the mobile station shall set
7 NUMBER_TYPE – Type of number.
8 If the DIGIT_MODE field is set to ‘1’, the mobile station shall
9 set this field to the NUMBER_TYPE value shown in Table
10 2.7.1.3.2.4-2 corresponding to the type of the number as
11 defined in [7], Section 4.5.9. If the DIGIT_MODE field is set to
12 ‘0’, the mobile station shall omit this field.
13
14 Table 2.7.1.3.2.4-2. Number Types
NUMBER_TYPE
Description
(binary)
Unknown 000
International number 001
National number 010
Network-specific number 011
Subscriber number 100
Reserved 101
Abbreviated number 110
Reserved for extension 111
15
16 NUMBER_PLAN – Numbering plan.

18 set this field to the NUMBER_PLAN value shown in Table
19 2.7.1.3.2.4-3 corresponding to the requested numbering plan
20 as defined in [7], Section 4.5.9. If the DIGIT_MODE field is set
21 to ‘0’, the mobile station shall omit this field.
22
2-536
3GPP2 C.S0005-A v6.0
1 Table 2.7.1.3.2.4-3. Numbering Plan Identification
NUMBER_PLAN
Description
(binary)
Unknown 0000
ISDN/Telephony numbering plan 0001
([17] and [16])
Data numbering plan ([20]) 0011
Telex numbering plan ([19]) 0100
Private numbering plan 1001
Reserved for extension 1111
All other NUMBER_PLAN codes are reserved.
3 MORE_FIELDS – More dialed digits indicator.

4 This field indicates whether additional dialed digits will be
5 sent in a later Origination Continuation Message.
6 If all dialed digits will fit into this message, the mobile station
7 shall set this field to ‘0’. If not, the mobile station shall set
9 NUM_FIELDS – Number of dialed digits in this message.
10 The mobile station shall set this field to the number of dialed
11 digits included in this message.
12 CHARi – A dialed digit or character.
14 this field. If the DIGIT_MODE field is set to ‘0’, the mobile
15 station shall set each occurrence of this field to the code value
16 shown in Table 2.7.1.3.2.4-4 corresponding to the dialed digit.
18 set each occurrence of this field to the ASCII representation
19 corresponding to the dialed digit, as specified in [9], with the
20 most significant bit set to ‘0’.
21
2-537
3GPP2 C.S0005-A v6.0
1 Table 2.7.1.3.2.4-4. Representation of DTMF Digits
Digit Code (binary) Digit Code (binary)
1 0001 7 0111
2 0010 8 1000
3 0011 9 1001
4 0100 0 1010
5 0101 * 1011
6 0110 # 1100
All other codes are reserved.
3 NAR_AN_CAP – Narrow analog capability.

4 If the mobile station is capable of narrow analog operation, the
5 mobile station shall set this bit to ‘1’; otherwise, the mobile
6 station shall set this bit to ‘0’.
7 PACA_REORIG – PACA re-origination.
8 If this is a user directed origination, the mobile station shall
9 set this field to ‘0’. If this is a PACA re-origination, the mobile
11 RETURN_CAUSE – Reason for the mobile station registration or access.
12 The mobile station shall set this field to the RETURN_CAUSE
14 service redirection failure condition (see 2.6.1.1).
15 MORE_RECORDS – More records indicator.
16 This field indicates whether information records will be sent in
17 a later Origination Continuation Message. If information
18 records will be sent, the mobile station shall set this field to
19 ‘1’; otherwise, the mobile station shall set this field to ‘0’.
20 ENCRYPTION- – Encryption algorithms supported by the mobile station.
21 _SUPPORTED If P_REV_IN_USE is greater than or equal to 7 or
22 AUTH_MODE is equal to ‘00’, the mobile station shall omit the
23 ENCRYPTION_SUPPORTED field. If P_REV_IN_USE is less
24 than 7 and AUTH_MODE is not equal to ‘00’, the mobile
25 station shall set this field as specified in Table 2.7.1.3.2.4-5.
26
2-538
3GPP2 C.S0005-A v6.0
1 Table 2.7.1.3.2.4-5. Encryption Algorithms Supported
ENCRYPTION_SUPPORTED
Description
(binary)
Basic encryption supported 0000

Basic and Enhanced encryption 0001
supported
Reserved 0010 - 1111
3 PACA_SUPPORTED – CDMA PACA support indication.

4 This field identifies the mobile station’s support for PACA in
5 CDMA mode. The mobile station shall set this field to ‘1’.
6
7 NUM_ALT_SO – Number of alternative service options.

9 set this field to the number of alternative service options it
10 supports other than the one specified in the
11 SERVICE_OPTION field. The mobile station shall set this field
12 to a value less than or equal to MAX_NUM_ALT_SOs.
13 If P_REV_IN_USEs is equal to or greater than seven, the
14 mobile station shall set this field to the number of alternate
15 service options, which either have no service option group
16 number assigned or do not belong to the same service option
17 group whose bitmap is being included. The alternate service
18 option numbers are other than the one specified in the
21 ALT_SO – Alternative service option.

22 If P_REV_IN_USEs is less than 7, the mobile station shall
23 include NUM_ALT_SO occurrences of this field. The mobile
24 station shall set this field to the value specified in [30],
25 corresponding to the alternative service option supported by
28 mobile station shall include NUM_ALT_SO occurrences of this
29 field. The mobile station shall set this field to the service
30 option number defined in TSB58 [30] corresponding to the
31 alternate service options which either have no service option
32 group number assigned or do not belong to the same service
33 option group whose bitmap is included in this message.
34 DRS – Data Ready to Send.
2-539
3GPP2 C.S0005-A v6.0
1 If there is data to send, the mobile station shall set this field
11 If the UZID_INCL field is included in the message and is set to
12 ‘1’, the mobile station shall include this field and set it to
13 UZIDs; otherwise, the mobile station shall omit this field.
14 CH_IND – Channel indicator.

17 field and set it, as shown in Table 2.7.1.3.2.4-6, to request
18 physical resources.
19 Table 2.7.1.3.2.4-6. Channel Indicator
CH_IND Channel(s) Requested

(binary)
00 Reserved
01 Fundamental Channel
10 Dedicated Control Channel
11 Fundamental Channel and Dedicated
Control Channel
20
2-540
3GPP2 C.S0005-A v6.0
1 SR_ID – Service reference identifier.

4 field and set it as follows:
5 If the service instance provides a service reference identifier,
6 the mobile station shall set this field to the service reference
7 identifier specified by the service instance. If the service
8 instance does not provide a service reference identifier, the
9 mobile station shall set this field to the smallest unused
10 service reference identifier value between 1 and 6 (inclusive).
11 OTD_SUPPORTED – Orthogonal Transmit Diversity supported indicator.
15 If the mobile station supports orthogonal transmit diversity, it
19 If P_REV_IN_USE is less than six, the mobile station shall
29 If the mobile station supports any radio configuration in the
30 Radio Configuration Class 2 (see 1.1.1), the mobile station
33 FOR_RC_PREF – Forward Radio Configuration preference.
36 field and set this field as follows.
37 The mobile station shall set this field to its preferred Radio
38 Configuration for the Forward Traffic Channel.
39 REV_RC_PREF – Reverse FCH Radio Configuration Preference.
44 Configuration for the Reverse Traffic Channel.
2-541
3GPP2 C.S0005-A v6.0
1 FCH_SUPPORTED – Fundamental Channel supported indicator.

6 station supports Fundamental Channel; otherwise, the mobile
8 FCH Capability
9 Type-specific fields – Fundamental Channel capability information.
10 If the FCH_SUPPORTED field is included and is set to ‘1’, the
11 mobile station shall include this field and set it as defined in
12 2.7.4.27.1; otherwise, the mobile station shall omit this field.
13 DCCH_SUPPORTED – Dedicated Control Channel supported indicator.
15 omit this field; otherwise the mobile station shall include this
18 station supports Dedicated Control Channel; otherwise, the
20 DCCH Capability
21 Type specific fields – Dedicated Control Channel capability information.
22 If the DCCH_SUPPORTED field is included and is set to ‘1’,
23 the mobile station shall include this field and set it as defined
24 in 2.7.4.27.2; otherwise, the mobile station shall omit this
25 field.
26 GEO_LOC_INCL – Geo-location included indicator.
28 omit this field. If P_REV_IN_USEs is equal to six, the mobile
29 station shall set this field to ‘0’. Otherwise, the mobile station
30 shall include this field and set it as follows.
31 If the message is to contain the GEO_LOC_TYPE field, the
34 GEO_LOC_TYPE – Geo-Location Type.
35 If GEO_LOC_INCL is included in the message and is set to ‘1’,
37 the value shown in Table 2.7.1.3.2.4-7; otherwise, the mobile
2-542
3GPP2 C.S0005-A v6.0
1 Table 2.7.1.3.2.4-7. Geo-location Types
GEO_LOC_
Type of Geo-location
TYPE
(binary)
000 No mobile station assisted geo-location

capabilities
001 IS-801 capable (Advanced Forward Link
Triangulation only (AFLT))
Triangulation and Global Positioning Systems)
011 Global Positioning Systems only
All other GEO_LOC_TYPE values are reserved.
2 REV_FCH-
3 _GATING_REQ – Reverse Fundamental gating mode request indicator.
7 If the mobile station requests to turn on the reverse
8 Fundamental Traffic Channel gating mode in Radio
9 Configurations 3, 4, 5, and 6, the mobile station shall set this
10 field to ‘1’; otherwise, the mobile station shall set this field to
11 ‘0’.
12 ORIG_REASON - Re-Origination reason indicator.
13 If P_REV_IN_USEs is less than or equal to six, the mobile
14 station shall omit this field; otherwise, the mobile station shall
15 include this field and set it as follows.
17 station initiates a silent-retry, i.e. an autonomous access re-
18 attempt to re-originate this call without user interaction, after
19 the mobile station received an access attempt failure from the
20 ARQ Sublayer for a user initiated origination; otherwise, the
22 ORIG_COUNT - Re-Origination count.
23 If P_REV_IN_USEs is less than or equal to six, the mobile
25 include this field and set it as follows.
26 If the ORIG_REASON is set to ‘1’, the mobile station shall set
27 this field to the number of consecutive silent-retry, i.e. an
28 autonomous access re-attempt that were made to re-originate
29 the call, without user interaction, that were due to the mobile
30 receiving an access attempt failure from the ARQ Sublayer. If
31 the number of consecutive silent-retry is greater than three,
32 the mobile station shall set this field to ‘11’.
2-543
3GPP2 C.S0005-A v6.0
1 If the ORIG_REASON is set to ‘0’, the mobile station shall set

2 this field according to Table 2.7.1.3.2.4–8 depending on the
3 number of autonomous re-connection attempts for the desired
4 service (specified by SERVICE_OPTION) that have failed since
5 the last successful connection of that desired service1. The
6 count shall only include attempts since the last power-up.
7 Table 2.7.1.3.2.4-8. ORIG_COUNT field for ORIG_REASON = ‘0’
Number of autonomous re- ORIG_COUNT

origination attempts for the desired (binary)
service that have failed since the
last successful connection
0 ‘00’
1, 2, 3 or 4 ‘01’
5, 6, 7 or 8 ‘10’
9 or more ‘11’
9 STS_SUPPORTED – STS supported indicator.

14 station supports Space Time Spreading Transmit Diversity;
24 WLL_INCL – WLL information included indicator.
1 For example, if the mobile station requests SO in the Origination Message and SO is granted by
x y
the base station, the counter associated with SOx is reset.
2-544
3GPP2 C.S0005-A v6.0

11 GLOBAL-
12 _EMERGENCY_CALL – Global Emergency Call indicator.
15 field and shall set it as follows:
17 station recognizes that this is an emergency call; otherwise,
19 MS_INIT_POS_LOC_IND – Mobile Initiated Position Location Session indicator.
20 If the GLOBAL_EMERGENCY_CALL field is not included in
21 this message or is included but is set to ‘0’, the mobile station
22 shall omit this field; otherwise, the mobile station shall
23 include this field and shall set it as follows:
24 The mobile station shall set this field to ‘1’ if
25 MS_INIT_POS_LOC_SUP_INDs is equal to ‘1’ and if the mobile
26 station is to initiate a position location session associated with
27 this emergency call; otherwise, the mobile station shall set
29 QOS_PARMS_INCL - Presence indicator for the QoS parameters.
31 omit this field; otherwise the mobile station shall include this
33 The mobile station shall set this field to ‘1’, if QoS parameters
34 are included in the message; otherwise the mobile station
35 shall set this field to ‘0’. The mobile station shall not set this
36 field to ‘1’, if MOB_QOSs is set to ‘0’ or if the inclusion of the
37 QoS parameters would prevent the inclusion of all the dialed
38 digits in the message.
39 QOS_PARMS_LEN - Length of the block of QoS parameters.
2-545
3GPP2 C.S0005-A v6.0
1 If QOS_PARMS_INCL is included and is set to ‘1’, the mobile

4 shall set this field to the combined length in octets, of the
5 QOS_PARMS field and the immediately following
6 QOS_RESERVED field; otherwise, the mobile station shall
7 omit this field.
8 QOS_PARMS - QoS parameters block.
12 shall set it to the set of QoS parameter values as defined in
13 accordance with the requirements for the requested service
14 option and/or for the user, per subscription.
15 QOS_RESERVED - QoS reserved bits.
17 station shall include the minimum number of bits of ‘0’, such
18 that the combined length of the QOS_PARMS field and of this
19 field is an integer number of octets; otherwise, the mobile
33 SIG_ENCRYPT_SUP – Signaling eEncryption supported indicator.
36 shall omit this field. If this field is included, this field
37 indicates which signaling encryption algorithms are supported
38 by the mobile station.
2-546
3GPP2 C.S0005-A v6.0

2 5.
11 ‘000000’.
12 D_SIG_ENCRYPT_REQ – Dedicated channel sSignaling Message encryption request
13 indicator.
18 to be turned on for signaling messages sent on f-dsch ,and r-
19 dsch, f-csch, and r-csch, and to ‘0’ to request signaling
20 encryption to be turned off for signaling messages sent on f-
21 dsch and, r-dsch, f-csch, and r-csch.
22 KEY_SEQ_NEW_INCL– The new encryption key sequence number included indicator.
30 C_SIG_ENCRYPT_REQ – Common channel signaling encryption request indicator.
35 to be turned on for signaling messages sent on f-csch and r-
36 csch, and to ‘0’ to request signaling encryption to be turned
37 off for signaling messages sent on f-csch and r-csch.
38
39 KEY_SEQ_NEW - The key sequence number corresponding to the new encryption

43 omit this field. If this field is included, the mobile station shall
44 set this field to KEY_SEQ_NEWs-p, the sequence number
45 associated with the new encryption key generated by the mobile
46 station.
2-547
3GPP2 C.S0005-A v6.0
1 ENC_SEQ_H - The 24 MSB of the EXT_ENC_SEQ
2 If SIG_ENCRYPT_SUP is included and the ECMEA or REA

3 subfield in SIG_ENCRYPT_SUP is set to ‘1’, If ENC_INFO_INCL
4 is included and is set to ‘1’, and the Enhanced Cellular
5 Message Encryption Algorithm is supported by the mobile
6 station, the mobile station shall include this field; otherwise,
7 the mobile station shall omit this field. If this field is
8 included, the mobile station shall set this field to the 24 most
9 significant bits of the EXT_ENC_SEQ to be used as the initial
10 value of crypto sync for both forward and reverse link
11 encryptions.
12 ENC_SEQ_H_SIG - The signature of ENC_SEQ_H
16 the digital signature of the ENC_SEQ_H as described in
17 2.3.12.4.5.
18 UI_ENCRYPT_REQ – Request for user information encryption on the traffic channel
19 indicator.
23 station shall set this field to ‘1’ to request user information
24 encryption, and to ‘0’ to request no user information
25 encryption.
26 UI_ENCRYPT_SUP – User information eEncryption supported indicator.
2-548
3GPP2 C.S0005-A v6.0

2 9.
3 Table 2.7.1.3.2.4-9. Encoding of the UI_ENCRYPT_SUP Field
Length
ORYX 1 Support for ORYX

encryption algorithm
REA 1 Support for the Rijndael
encryption algorithm used
in extended encryption
RESERVED 76 Reserved bits

9 ‘0000000’.
10 SYNC_ID_INCL - SCR Service Configuration synchronization identifier included
11 indicator.
15 The mobile station shall set this field to ‘1’ if the SYNC_ID field
16 is included in this message; otherwise, the mobile station
18 SYNC_ID_LEN - Service Configuration synchronization identifier length

19 indicator.
20 If the SYNC_ID_INCL field is not included or is included and is

21 set to ‘0’, the mobile station shall omit this field; otherwise the
22 mobile station shall include this field and set it as follows:
23 The mobile station shall set this field to the length of the
24 SYNC_ID field included in this message.
25
26 SYNC_ID - SCR Service Configuration synchronization identifier.

30 If the SYNC_ID_INCL field is not included, or is included but is

2-549
3GPP2 C.S0005-A v6.0
1 the mobile station shall include this field and set it as follows:
2 The mobile station shall set this field to the Service

3 Configuration synchronization identifier corresponding to the
4 stored service configuration.
5 to the 16-bit CRC computed over the entire stored service
6 configuration (that is, both the Service Configuration
7 information record and the Non-negotiable Service
8 Configuration information record) as specified in 2.6.11.
9 PREV_SID_INCL - Previous System Identification (SID) included indicator.

10 If P_REV_IN_USE is less than seven, the mobile station shall
14 station determines that the SID has been changed after a
15 packet data dormant handoff and the PREV_SID field is
16 included in this message; otherwise, the mobile station shall
17 set this field to ‘0’.
18 PREV_SID - Previous System Identification.
19 If PREV_SID_INCL is not included, or is included but is set to
20 ‘0’, the mobile station shall omit this field; otherwise, the
22 If the mobile station determines SID has been changed after a
23 packet data dormant handoff, the mobile station shall set this
24 field to the previous SID.
25 PREV_NID_INCL - Previous Network Identification (NID) included indicator.
30 station determines that NID has been changed after a packet
31 data dormant handoff and the PREV_NID field is included in
32 this message; otherwise, the mobile station shall set this field
33 to ‘0’.
34 PREV_NID - Previous Network Identification.
35 If PREV_NID_INCL is not included, or is included but is set to
38 If the mobile station determines NID has been changed after a
40 field to the previous NID.
41 PREV_PZID_INCL - Previous Packet Zone ID (PZID) included indicator.
2-550
3GPP2 C.S0005-A v6.0
2 station determines that the Packet Zone ID has been changed
3 after a packet data dormant handoff and the PREV_PZID field
5 shall omit set this field to ‘0’.
6 PREV_PZID - Previous Packet Zone ID.
7 If PREV_PZID_INCL is not included, or is included but is set to
10 If the mobile station determines PZID has been changed after
11 a packet data dormant handoff, the mobile station shall set
12 this field to the previous PZID.
13 SO_BITMAP_IND - Service option bitmap indicator.
14 If P_REV_IN_USEs is less than 7, the mobile station shall omit
15 this field; otherwise, the mobile station shall set this field as
16 defined in Table 2.7.1.3.2.4-10.
17 Table 2.7.1.3.2.4-10. Encoding of the SO_BITMAP_IND Field
SO_BITMAP_IND Size of bitmap (in bits) included
00 0 bit (i.e., No bitmap included)

01 4 bits
10 8 bits
11 Reserved
18
19 SO_GROUP_NUM - Service option group number.

20 If SO_BITMAP_IND is included and not set to ‘00’, the mobile
21 station shall include this field and set this field to service
22 option group number defined in TSB58[30], of the bitmap to
23 be included in this message; otherwise, the mobile station
24 shall omit this field.
25 SO_BITMAP – Service option bitmap.
26 If the field SO_BITMAP_IND is included and is not set to ‘00’,
27 the mobile station shall include the bitmap of the service
28 option group (SO_GROUP_NUM); otherwise, the mobile station
30 When the service option bitmap is included, if there are more
31 than (4 × SO_BITMAP_IND) service options defined in TSB58
32 [30] for the service option group [SO_GROUP_NUM], the
33 mobile station shall include the bitmap containing the least
34 significant bits (4 × SO_BITMAP_IND) for the service option
35 group.
2-551
3GPP2 C.S0005-A v6.0
1 The mobile station shall set a bit in this bitmap to ‘1’, if the
2 mobile station is capable of supporting the service option for
3 which the bit represents; otherwise, the mobile station shall
4 set a bit in this bitmap to ‘0’.
2-552
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.5 Page Response Message
2 MSG_TAG: PRM
Field Length (bits)
MOB_TERM 1
SLOT_CYCLE_INDEX 3
MOB_P_REV 8
SCM 8
REQUEST_MODE 3
SERVICE_OPTION 16
PM 1
NAR_AN_CAP 1
ENCRYPTION_SUPPORTED 0 or 4
NUM_ALT_SO 3
ALT_SO 16
2-553
3GPP2 C.S0005-A v6.0
Field Length (bits)
UZID_INCL 0 or 1
UZID 0 or 16
CH_IND 0 or 2
ENHANCED_RC 0 or 1
FOR_RC_PREF 0 or 5
REV_RC_PREF 0 or 5
FCH_SUPPORTED 0 or 1
FCH Capability Type-specific fields 0 or variable
DCCH_SUPPORTED 0 or 1
DCCH Capability Type-specific 0 or variable
fields
REV_FCH_GATING_REQ 0 or 1
WLL_INCL 0 or 1
HOOK_STATUS 0 or 4
C_SIG_ENCRYPT_REQ
KEY_SEQ_NEW 0 or 4
ENC_SEQ_H 0 or 24
2-554
3GPP2 C.S0005-A v6.0
Field Length (bits)
SYNC_ID_INCL 0 or 1
SYNC_ID_LEN 0 or 4
SYNC_ID 0 or (8 x
SYNC_ID_LEN)16
If P_REV_IN_USEs is equal to or greater than 7, the mobile
station shall include the following fields:
SO_GROUP_NUM 0 or 5
SO_BITMAP 0 or 4 ×
SO_BITMAP_IND

6 2.6.5.3), the mobile station shall set this bit to ‘1’. Otherwise,
11 index, SLOT_CYCLE_INDEXp (see 2.6.2.1.1). Otherwise, the
16 The mobile station shall set this field to the station class mark
17 of the mobile station. See 2.3.3.
18 REQUEST_MODE – Requested mode code. The mobile station shall set this field
19 to the value shown in Table 2.7.1.3.2.4-1 corresponding to its
20 current configuration.
21 SERVICE_OPTION – Service option.
22 If the mobile station accepts the service option specified by the
23 mobile-station-addressed page, it shall set this field as follows:
24 • If the page record to which the mobile station is
25 responding contained a SERVICE OPTION field, the mobile
26 station shall set this field to the service option number
27 specified in the SERVICE OPTION field of the page record
28 to which the mobile station is responding.
29 • If the page record to which the mobile station is
30 responding did not contain a SERVICE OPTION field, the
2-555
3GPP2 C.S0005-A v6.0
1 mobile station shall set this field to the default option

2 number ‘0000000000000001’.
3 If the mobile station does not accept the service option
4 specified by the mobile-station-addressed page to which the
5 mobile station is responding and the mobile station has an
6 alternative service option to request, the mobile station shall
7 set this field to the service option code specified in [30]
8 corresponding to the alternative service option.
9 If the mobile station does not accept the service option
10 specified by the mobile-station-addressed page to which the
11 mobile station is responding and the mobile station does not
12 have an alternative service option to request, the mobile
13 station shall set this field to ‘0000000000000000’ to reject the
14 service option specified by the page record of the General Page
15 Message or Universal Page Message to which the mobile
16 station is responding.
17 PM – Privacy mode indicator.
18 To request voice privacy, the mobile station shall set this field
20 NAR_AN_CAP – Narrow analog capability.
21 If the mobile station is capable of narrow analog operation, the
22 mobile station shall set this bit to ‘1’; otherwise, the mobile
24 ENCRYPTION- – Encryption algorithms supported by the mobile station.
25 _SUPPORTED If P_REV_IN_USE is greater than or equal to 7 or
26 AUTH_MODE is equal to ‘00’, the mobile station shall omit
27 this field. If P_REV_IN_USE is less than 7 and AUTH_MODE
28 is not equal to ‘00’, then the mobile station shall set this field
29 as specified in table 2.7.1.3.2.4-5.
32 set this field to the number of alternative service options it
33 supports other than the one specified in the
37 mobile station shall set this field to the number of alternate
38 service options, which either have no service option group
39 number assigned or do not belong to the same service option
40 group whose bitmap is being included. The alternate service
41 option numbers are other than the one specified in the
2-556
3GPP2 C.S0005-A v6.0
1 The mobile station shall include NUM_ALT_SO occurrences of

2 this field. The mobile station shall set this field to the value
3 specified in [30], corresponding to the alternative service
4 option supported by the mobile station.
6 mobile station shall include NUM_ALT_SO occurrences of in
7 this field. The mobile station shall set this field to the service
8 option number defined in TSB58 [30] corresponding to the
9 alternate service options which either have no service option
10 group number assigned or do not belong to the same service
11 option group whose bitmap is included in this message.
20 If the UZID_INCL field is included in the message and is set to
21 ‘1’, the mobile station shall include this field and set it to
22 UZIDs; otherwise, the mobile station shall omit this field.
23 CH_IND – Channel Indicator.
26 field and set it, as shown in Table 2.7.1.3.2.5-1, to request
27 physical resources.
2-557
3GPP2 C.S0005-A v6.0
1 Table 2.7.1.3.2.5-1. Channel indicator

(binary)
00 Reserved
11 Fundamental Channel and Dedicated
Control Channel
3 OTD_SUPPORTED – Orthogonal transmit diversity supported indicator

7 If the mobile station supports orthogonal transmit diversity, it
11 If P_REV_IN_USE is less than six, the mobile station shall omit
12 this field; otherwise, the mobile station shall include this field and
13 set it as follows.
18 If P_REV_IN_USEs is less than six, the mobile station shall omit
19 this field; otherwise, the mobile station shall include this field and
20 set it as follows.
21 If the mobile station supports any radio configuration in the Radio
22 Configuration Class 2 (see 1.1.1), the mobile station shall set this
23 field to ‘1’; otherwise, the mobile station shall set this field to ‘0’.
24 FOR_RC_PREF – Forward Radio Configuration preference.
29 Configuration for the Forward Traffic Channel.
30 REV_RC_PREF – Reverse Radio Configuration preference.
2-558
3GPP2 C.S0005-A v6.0
2 Configuration for the Reverse Traffic Channel.
8 station supports Fundamental Channel; otherwise, the mobile
10 FCH Capability Type-
11 specific fields – Fundamental Channel capability information.
12 If the FCH_SUPPORTED field is included and is set to ‘1’, the
13 mobile station shall include this field and set it as described
14 in 2.7.4.27.1; otherwise, the mobile station shall omit this
15 field.
21 station supports Dedicated Control Channel; otherwise, the
23 DCCH Capability Type-
24 specific fields – Dedicated Control Channel capability information.
25 If DCCH_SUPPORTED is included and is set to ‘1’, the mobile
26 station shall include this field and set it as defined in
27 2.7.4.27.2; otherwise, the mobile station shall omit this field.
28 REV_FCH-
29 _GATING_REQ – Reverse eighth gating mode request indicator.
33 If the mobile station requests to turn on the reverse
34 Fundamental Traffic Channel gating mode in Radio
35 Configurations 3, 4, 5, and 6, the mobile station shall set this
37 ‘0’.
2-559
3GPP2 C.S0005-A v6.0

9 WLL_INCL - WLL information included indicator.
26 the mobile station shall set this field to the value shown in
27 Table 2.7.1.3.2.1-4 corresponding to the hook state.
44 station shall set this field to indicate which signaling
45 encryption algorithms are supported by the mobile station.
2-560
3GPP2 C.S0005-A v6.0

2 5.
11 ‘000000’.
13 indicator.
18 to be turned on for signaling messages sent on f-dsch and, r-
19 dsch, f-csch, and r-csch, and to ‘0’ to request signaling
20 encryption to be turned off for signaling messages sent on f-
21 dsch and, r-dsch, f-csch, and r-csch.
22 KEY_SEQ_NEW_INCL – The new encryption key sequence number included indicator.
26 shall set this field as follow:
30 C_SIG_ENCRYPT_REQ – Common channel signaling encryption request indicator.
35 to be turned on for signaling messages sent on f-csch and r-
36 csch, and to ‘0’ to request signaling encryption to be turned
37 off for signaling messages sent on f-csch and r-csch.
38
39 KEY_SEQ_NEW – The key sequence number corresponding to the new encryption

43 omit this field. If this field is included, the mobile station shall set
44 this field to KEY_SEQ_NEWs-p, the sequence number associated
45 with the new encryption key generated by the mobile station.
46 ENC_SEQ_H - The 24 MSB of the EXT_ENC_SEQ
2-561
3GPP2 C.S0005-A v6.0
1 If SIG_ENCRYPT_SUP is included and the ECMEA or REA

2 subfield in SIG_ENCRYPT_SUP is set to ‘1’, If ENC_INFO_INCL
3 is included and is equal to ‘1’, and the Enhanced Cellular
4 Message Encryption Algorithm is supported by the mobile
5 station, the mobile station shall include this field; otherwise,
6 the mobile station shall omit this field. If this field is
7 included, the mobile station shall set this field to the 24 most
8 significant bits of the EXT_ENC_SEQ to be used as the initial
9 value of crypto sync for both forward and reverse link
10 encryptions.
11 ENC_SEQ_H_SIG - The signature of ENC_SEQ_H
12 If the ENC_SEQ_H field is included in the message, the mobile
13 station shall set this field to the digital signature of the
14 ENC_SEQ_H as described in 2.3.12.4.5; otherwise, the mobile
17 indicator.
21 station shall set this field to ‘1’ to request user information
22 encryption, and to ‘0’ to request no user information
23 encryption. UI_ENCRYPT_SUP – User information
24 Encryption supported indicator.
2-562
3GPP2 C.S0005-A v6.0

2 9.

8 ‘0000000’.
9 SYNC_ID_INCL - SCR Service Configuration synchronization identifier included

10 indicator.
14 The mobile station shall set this field to ‘1’ if the SYNC_ID
15 field is included in this message; otherwise, the mobile
17 SYNC_ID_LEN - Service Configuration synchronization identifier length

18 indicator.

20 set to ‘0’, the mobile station shall omit this field; otherwise the
22 The mobile station shall set this field to the length of the
23 SYNC_ID field included in this message.
24
25 SYNC_ID - Service Configuration SCR synchronization identifier.
26 If the SYNC_ID_INCL field is not included, or is included and

27 is set to ‘0’, the mobile station shall omit this field; otherwise,
28 the mobile station shall include this field and set it as follows:
29 The mobile station shall set this field to the Service

30 Configuration synchronization identifier corresponding to the
31 stored service configuration.
32 to the 16-bit CRC computed over the entire stored service
33 configuration (that is, both the Service Configuration
34 information record and the Non-negotiable Service
35 Configuration information record) as specified in 2.6.11.
36 SO_BITMAP_IND - SO bitmap indicator.

37 If P_REV_IN_USEs is less than 7, the mobile station shall omit
38 this field; otherwise, the mobile station shall include this field
39 and set this field as defined in Table 2.7.1.3.2.4-10.
40 SO_GROUP_NUM - The service option group number.
2-563
3GPP2 C.S0005-A v6.0
1 If SO_BITMAP_IND is included and not set to ‘00’, the mobile

2 station shall include this field and set this field to service
3 option group number of the bitmap to be included in this
4 message; otherwise, the mobile station shall omit this field.
5 SO_BITMAP - Service option bitmap.
6 If the field SO_BITMAP_IND field is included and is not set to
7 ‘00’, the mobile station shall include the bitmap of the service
8 option group (SO_GROUP_NUM); otherwise, the mobile station
11 than (4 × SO_BITMAP_IND) service options defined for the
12 service option group, the mobile station shall include the
13 bitmap containing the least significant bits (4 ×
14 SO_BITMAP_IND) of the service option group.
15 The mobile station shall set a bit in this bitmap to ‘1’, if the
16 mobile station is capable of supporting the service option for
17 which the bit represents; otherwise, the mobile station shall
18 set a bit in this bitmap to ‘0’.
19
2-564
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.6 Authentication Challenge Response Message
2 MSG_TAG: AUCRM
Field Length (bits)
AUTHU 18
4 AUTHU – Authentication challenge response.

5 The mobile station shall set this field as specified in
6 2.3.12.1.4.
2-565
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.7 Status Response Message
2 MSG_TAG: STRPM
Field Length (bits)
QUAL_INFO_TYPE 8
QUAL_INFO_LEN 3
Type-specific fields 8 × QUAL_INFO_LEN
One or more occurrences of the following record:
RECORD_TYPE 8
RECORD_LEN 8
Type-specific fields 8 × RECORD_LEN
4 QUAL_INFO_TYPE – Qualification information type.

5 The mobile station shall set this field to the QUAL_INFO_TYPE
6 field in the corresponding Status Request Message.
7 QUAL_INFO_LEN – Qualification information length.
8 The mobile station shall set this field to the QUAL_INFO_LEN
10 Type-specific fields – Type-specific fields.
11 The mobile station shall set these fields to the qualification
12 information in the corresponding Status Request Message.
13 The mobile station shall include all the records requested in the corresponding Status
14 Request Message. The mobile station shall include one occurrence of the following fields for
15 each information record to be included:
16 RECORD_TYPE – Information record type.
17 The mobile station shall set this field to the record type value
18 shown in Table 3.7.2.3.2.15-2 corresponding to the type of
19 this information record.
20 RECORD_LEN – Information record length.
22 included in the type-specific fields of this information record.
24 The mobile station shall set these fields to the information as
25 specified in 2.7.4 for the specific type of records. The mobile
26 station shall only specify the information corresponding to the
27 included qualification information.
2-566
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.8 TMSI Assignment Completion Message
2 MSG_TAG: TACM
3 There are no Layer 3 fields associated with this message.
2-567
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.9 PACA Cancel Message
2 MSG_TAG: PACNM
2-568
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.10 Extended Status Response Message
2 MSG_TAG: ESTRPM
Field Length (bits)
QUAL_INFO_TYPE 8
QUAL_INFO_LEN 3
NUM_INFO_RECORDS 4
NUM_INFO_RECORDS occurrences of the following record:
RECORD_TYPE 8
RECORD_LEN 8
4

14 NUM_INFO_RECORDS – Number of information records included.
16 information records which are included. The mobile station
17 shall include all the records requested in the corresponding
18 Status Request Message.
19 The mobile station shall include one occurrence of the following fields for each information
20 record which is included:
2-569
3GPP2 C.S0005-A v6.0

2 The mobile station shall set these fields to the information as
3 specified in 2.7.4 for the specific type of records. The mobile
4 station shall only specify the information corresponding to the
5 included qualification information.
2-570
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.11 Device Information Message
2 MSG_TAG: DIM
Field Length (bits)
WLL_DEVICE_TYPE 3
NUM_INFO_RECORDS 5
RECORD_TYPE 8
RECORD_LEN 8

11 information records which are included.
15 The mobile station shall set this field to the record type code
16 shown in Table 2.7.4-1 corresponding to the type of this
20 in the type-specific fields of this record.
22 The mobile station shall set these fields as specified in 2.7.4
23 for this type of information record.
2-571
3GPP2 C.S0005-A v6.0
1 2.7.1.3.2.12 Security Mode Request Message
2 MSG_TAG: SMRM
Order-Specific Field Length (bits)
UI_ENC_INCL 1
SIG_ENC_INCL 1
C_SIG_ENCRYPT_REQ 0 or 1
ENC_SEQ_H_INCL 1
ENC_SEQ_H 0 or 24
5 UI_ENC_INCL – User information encryption fields included.

6 The mobile station shall set this field to ‘1’ if the user
7 information encryption related fields are included in this
8 message; otherwise, the mobile station shall set this field to
9 ‘0’.
11 If UI_ENC_INCL is equal to ‘1’, the mobile station shall include
14 indicate the supported user information encryption
15 algorithms.
17 9.
23 ‘0000000’.
24 SIG_ENC_INCL – Signaling encryption fields included.
25 The mobile station shall set this field to ‘1’ if the following two
26 fields related to signaling encryption fields are included in this
28 ‘0’.
2-572
3GPP2 C.S0005-A v6.0

2 If SIG_ENC_INCL is equal to ‘1’, the mobile station shall
3 include this field; otherwise, the mobile station shall omit this
4 field. If this field is included, the mobile shall set this field to
5 indicate the supported signaling encryption algorithms
8 5.
17 ‘000000’.
18 C_SIG_ENCRYPT_REQ – Common channel sSignaling Message encryption request
19 indicator.
22 field. If this field is included, the mobile station shall set this
23 field to ‘1’ to request signaling encryption to be turned on for
24 signaling messages sent on f-dsch, r-dsch, f-csch, and r-csch,
25 and to ‘0’ to request signaling encryption to be turned off for
26 signaling messages sent on f-dsch, r-dsch, f-csch, and r-csch.
27 ENC_SEQ_H_INCL – The 24 MSB of the EXT_ENC_SEQ included.
28 The mobile station shall set this field to ‘1’ if ENC_SEQ_H is
32 If ENC_SEQ_H_INCL is set to ‘1’, the mobile station shall
35 field to the 24 most significant bits of the EXT_ENC_SEQ to be
36 used as the initial value of crypto sync for both forward and
37 reverse link encryptions.
2-573
3GPP2 C.S0005-A v6.0
1 2.7.2 r-dsch
2 During Traffic Channel operation, the mobile station sends signaling messages to the base
3 station using the r-dsch.
4 2.7.2.1 Reserved
5 2.7.2.2 Reserved
6 2.7.2.3 PDU Formats for Messages on r-dsch
7 The messages sent on the r-dsch are summarized in Table 2.7.2.3-1.
2-574
3GPP2 C.S0005-A v6.0
1 Table 2.7.2.3-1. Messages on r-dsch
Message Name MSG_TAG Section

Number
Order Message ORDM 2.7.2.3.2.1

Authentication Challenge Response Message AUCRM 2.7.2.3.2.2
Flash With Information Message FWIM 2.7.2.3.2.3
Pilot Strength Measurement Message PSMM 2.7.2.3.2.5
Power Measurement Report Message PMRM 2.7.2.3.2.6
Send Burst DTMF Message BDTMFM 2.7.2.3.2.7
Status Message STM 2.7.2.3.2.8
Origination Continuation Message ORCM 2.7.2.3.2.9
Handoff Completion Message HOCM 2.7.2.3.2.10
Parameters Response Message PRSM 2.7.2.3.2.11
Service Request Message SRQM 2.7.2.3.2.12
Service Response Message SRPM 2.7.2.3.2.13
Service Connect Completion Message SCCM 2.7.2.3.2.14
Service Option Control Message SOCM 2.7.2.3.2.15
Status Response Message STRPM 2.7.2.3.2.16
TMSI Assignment Completion Message TACM 2.7.2.3.2.17
Supplemental Channel Request Message SCRM 2.7.2.3.2.18
Candidate Frequency Search Response Message CFSRSM 2.7.2.3.2.19
Candidate Frequency Search Report Message CFSRPM 2.7.2.3.2.20
Periodic Pilot Strength Measurement Message PPSMM 2.7.2.3.2.21
Outer Loop Report Message OLRM 2.7.2.3.2.22
Resource Request Message RRM 2.7.2.3.2.23
Resource Request Mini Message RRMM 2.7.2.3.2.24
Extended Release Response Message ERRM 2.7.2.3.2.25
Extended Release Response Mini Message ERRMM 2.7.2.3.2.26
Pilot Strength Measurement Mini Message PSMMM 2.7.2.3.2.27
Supplemental Channel Request Mini Message SCRMM 2.7.2.3.2.28
Resource Release Request Message RRRM 2.7.2.3.2.29
Resource Release Request Mini Message RRRMM 2.7.2.3.2.30
User Zone Update Request Message UZURM 2.7.2.3.2.31
2-575
3GPP2 C.S0005-A v6.0
Enhanced Origination Message EOM 2.7.2.3.2.32

Extended Flash With Information Message EFWIM 2.7.2.3.2.33
Extended Pilot Strength Measurement Message EPSMM 2.7.2.3.2.34
Extended Handoff Completion Message EHOCM 2.7.2.3.2.35
Security Mode Request Message SMRM 2.7.2.3.2.36
Call Cancel Message CLCM 2.7.2.3.2.37
Device Information Message DIM 2.7.12.3.2.38

Base Station Status Request Message BSSREQM 2.7.2.3.2.39
2-576
3GPP2 C.S0005-A v6.0
2 2.7.2.3.2 Message Body Contents
2-577
3GPP2 C.S0005-A v6.0
2 MSG_TAG: ORDM
Field Length (bits)
ORDER 6
ADD_RECORD_LEN 3
CON_REF_INCL 0 or 1
CON_REF 0 or 8
5 ORDER – Order code.

6 The mobile station shall set this field to the ORDER code.
7 See 2.7.3.
8 ADD_RECORD_LEN – Additional record length.
10 in the order-specific fields included in this message.
11 Order-specific fields – Order-specific fields.
12 The mobile station shall include order-specific fields as
14 CON_REF_INCL – Connection reference included indicator.
15 If the order carried by this message is not a Call Control order

16 (2.6.10), the mobile station shall omit this field; otherwise, the
18 The mobile station shall set this field to ‘1’ if the connection
19 reference field is included in this message; otherwise, it shall
21 CON_REF – Connection reference.
22 If the CON_REF_INCL field is not included, or is included but

23 is set to ‘0’, the mobile station shall omit this field; otherwise,
25 the value of the connection reference assigned to the service
26 option connection of the call, to which this message
27 corresponds.
2-578
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.2 Authentication Challenge Response Message
2 MSG_TAG: AUCRM
Field Length (bits)
AUTHU 18
5 AUTHU – Authentication challenge response.

7 2.3.12.1.4.
2-579
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.3 Flash With Information Message
2 MSG_TAG: FWIM
Field Length (bits)
Zero or more occurrences of the following record:

RECORD_TYPE 8
RECORD_LEN 8
5 The mobile station shall include one occurrence of the following record for each information
6 record to be included:
2-580
3GPP2 C.S0005-A v6.0
2 MSG_TAG: DBM
Field Length (bits)
MSG_NUMBER 8
BURST_TYPE 6
NUM_MSGS 8
NUM_FIELDS 8
CHARi 8
5 MSG_NUMBER – Message number within the data burst stream.

6 The mobile station shall set this field to the number of this
8 BURST_TYPE – Data burst type.
9 The mobile station shall set the value of this field for the type
10 of this data burst as defined in [30]. If the mobile station sets
14 the definition of CHARi below. If the mobile station sets this
16 this message equal to the EXTENDED BURST TYPE as
18 NUM_MSGS – Number of messages in the data burst stream.
20 messages within this data burst stream.
21 NUM_FIELDS – Number of characters in this message.
22 The mobile station shall set this field to the number of CHARi
23 fields included in this message.
26 this field. The mobile station shall set these fields to the
2-581
3GPP2 C.S0005-A v6.0

5 contain a binary mapping of the Mobile Country Code (MCC)
6 associated with the national standards organization
7 administering the use of the remaining octets of the message.
11 the COUNTRY_BURST_TYPE. The mobile station shall set the
15
Field Length (bits)

16
17 If the BURST TYPE field of this message is equal to ‘111111’,

19 EXTENDED BURST TYPE field, as shown below. The mobile
20 station shall set the value of the EXTENDED BURST TYPE
22
Field Length (bits)
2-582
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.5 Pilot Strength Measurement Message
2 MSG_TAG: PSMM
Field Length (bits)
REF_PN 9
PILOT_STRENGTH 6
KEEP 1
PILOT_PN_PHASE 15
PILOT_STRENGTH 6
KEEP 1
5 REF_PN – Time reference PN sequence offset.

6 The mobile station shall set this field to the PN sequence offset
7 of the pilot used by the mobile station to derive its time
8 reference, relative to the zero offset pilot PN sequence in units
9 of 64 PN chips.
10 PILOT_STRENGTH – Pilot strength.
11 The mobile station shall set this field to
12 -2 × 10 log10 PS,
13 where PS is the strength of the pilot used by the mobile

14 station to derive its time reference (see [2]), measured as
15 specified in 2.6.6.2.2. If this value (-2 × 10 log10 PS) is less
16 than 0, the mobile station shall set this field to ‘000000’. If
17 this value is greater than ‘111111’, the mobile station shall set
19 KEEP – Keep pilot indicator.
20 If the handoff drop timer (see 2.6.6.2.3) corresponding to the
21 pilot used by the mobile station to derive its time reference
22 (see 2.1.5 of [2]) has expired, the mobile station shall set this
24 ‘1’.
25
26 If P_REV_IN_USEs is less than or equal to three, the mobile station shall include one
27 occurrence of the three-field record given below for each pilot in the Active Set and for each
28 Candidate Set pilot reported (the number of Candidate Set pilots reported shall not exceed
29 5), other than the pilot identified by the REF_PN field. If P_REV_IN_USEs is greater than
30 three and SOFT_SLOPEs is equal to ‘000000’, the mobile station shall include one
31 occurrence of the three-field record given below for each pilot in the Active Set and for each
2-583
3GPP2 C.S0005-A v6.0
1 pilot in the Candidate Set, other than the pilot identified by the REF_PN field. If
2 P_REV_IN_USEs is greater than three and SOFT_SLOPEs is not equal to ‘000000’, the
3 mobile station shall include one occurrence of the three-field record given below for each
4 pilot in the Active Set, for each pilot in the Candidate Set whose strength exceeds T_ADD,
5 and shall also include one occurrence of the three-field record given below for each pilot in
6 the Candidate Set whose strength satisfies the following inequality:
∑ PS i +
7 10 × log 10 PS > × 10 × log 10
8 2
i∈A
8 where the summation is performed over all pilots currently in the Active Set. The mobile
9 station shall not include these fields for the pilot identified by the REF_PN field.
10 The mobile station shall order any occurrences of the three-field record given below which
11 correspond to pilots in the Active Set such that they occur before any occurrences of the
12 three-field record given below which correspond to pilots in the Candidate Set.
13 PILOT_PN_PHASE – Pilot measured phase.
14 The mobile station shall set this field to the phase of the pilot
15 PN sequence relative to the zero offset pilot PN sequence of
16 this pilot, in units of one PN chip, as specified in 2.6.6.2.4.
19 -2 × 10 log10 PS,
20 where PS is the strength of this pilot, measured as specified in

21 2.6.6.2.2. If this value (-2 × 10 log10 PS) is less than 0, the
22 mobile station shall set this field to ‘000000’. If this value is
23 greater than ‘111111’, the mobile station shall set this field to
24 ‘111111’.
26 If the handoff drop timer (see 2.6.6.2.3) corresponding to this
27 pilot has expired, the mobile station shall set this field to ‘0’;
2-584
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.6 Power Measurement Report Message
2 MSG_TAG: PMRM
Field Length (bits)
ERRORS_DETECTED 5
PWR_MEAS_FRAMES 10
LAST_HDM_SEQ 2
NUM_PILOTS 4
NUM_PILOTS occurrences of the following field:
PILOT_STRENGTH 6
DCCH_PWR_MEAS_INCL 1
DCCH_PWR_MEAS_FRAMES 0 or 10
DCCH_ERRORS_DETECTED 0 or 5
SCH_PWR_MEAS_INCL 1
SCH_ID 0 or 1
SCH_PWR_MEAS_FRAMES 0 or 16
SCH_ERRORS_DETECTED 0 or 10
5 ERRORS_DETECTED – Number of detected bad frames.

6 When the Forward Fundamental Channel is assigned, the
7 mobile station shall set this field to the number of bad frames
8 detected (BAD_FRAMESs, see 2.6.4.1.1] on the Forward
10 If P_REV_IN_USEs is greater than or equal to six and only the
11 Forward Dedicated Control Channel is assigned, the mobile
12 station shall set this field to the number of bad frames
13 detected on the Forward Dedicated Control Channel
14 (DCCH_BAD_FRAMESs, see 2.6.4.1.1].
15 If the number of bad frames received on this channel within

16 the measurement period is less than or equal to 31, the
17 mobile station shall set this field to that number. If that
18 number exceeds 31, the mobile station shall set this field to
19 ‘11111’.
2-585
3GPP2 C.S0005-A v6.0
1 PWR_MEAS_FRAMES – Number of power measurement frames.

2 When the Forward Fundamental Channel is assigned, the
3 mobile station shall set this field to the number of frames
4 received on the Forward Fundamental Channel within the
5 measurement period (TOT_FRAMESs, see 2.6.4.1.1).
6 If P_REV_IN_USE is greater than or equal to six and only the
7 Dedicated Control Channel is assigned, the mobile station
8 shall set this field to the number of frames received on the
9 Dedicated Control Channel (DCCH_TOT_FRAMESs, see
10 2.6.4.1.1).
11 LAST_HDM_SEQ – Extended Handoff Direction Message or a General Handoff
12 Direction Message, or Universal Handoff Direction Message
13 sequence number.
14 If an Extended Handoff Direction Message, a General Handoff
15 Direction Message, or Universal Handoff Direction Message has
16 been received during this call, the mobile station shall set this
17 field to the value of the HDM_SEQ field from the Extended
18 Handoff Direction Message, the General Handoff Direction
19 Message or the Universal Handoff Direction Message that
20 determined the current Active Set. If no Extended Handoff
21 Direction Message, General Handoff Direction Message, or
22 Universal Handoff Direction Message has been received during
23 this call, the mobile station shall set this field to ‘11’.
24 NUM_PILOTS – Number of pilots reported.
25 The mobile station shall set this field to the number of pilots
26 in the current Active Set.
28 The mobile station shall include one occurrence of this field
29 for each pilot in the Active Set. If the Active Set contains more
30 than one pilot, the mobile station shall include the pilot
31 strengths in the same order as in the Extended Channel
32 Assignment Message, Extended Handoff Direction Message,
33 General Handoff Direction Message or the Universal Handoff
34 Direction Message that determined the current Active Set.
35 The mobile station shall set each occurrence of this field to
36 -2 × 10 log10 PS,
37 where PS is the strength of the pilot, measured as specified in

41 ‘111111’.
42 DCCH_PWR_MEAS_INCL - Forward Dedicated Control Channel power measurement
43 included.
2-586
3GPP2 C.S0005-A v6.0
1 If both Forward Fundamental Channel and Forward Dedicated

2 Control Channel are assigned, the mobile station shall set this
3 field equal to ‘1’; otherwise, the mobile shall set this field to
4 ‘0’.
5 DCCH_PWR-
6 _MEAS_FRAMES - Number of received Dedicated Control Channel frames.
7 If DCCH_PWR_MEAS_INCL is set to ‘0’, the mobile station
8 shall omit this field; otherwise, the mobile station shall set
9 this field to the number of frames received on the Dedicated
10 Control Channel within the measurement period
11 (DCCH_TOT_FRAMESs, see 2.6.4.1.1).
12 DCCH_ERRORS-
13 _DETECTED - Number of detected bad Dedicated Control Channel frames.
14 If DCCH_PWR_MEAS_INCL is set to ‘0’, the mobile station
16 this field to the number of bad frames (DCCH_BAD_FRAMESs]
17 detected on the Forward Dedicated Control Channel.
18 If DCCH_BAD_FRAMESs exceeds 31, the mobile station shall
19 set this field to ‘11111’; otherwise, the mobile station shall set
20 this field to DCCH_BAD_FRAMESs [see 2.6.4.1.1).
21 SCH_PWR_MEAS_INCL - Supplemental Channel power measurement included
22 indicator.
23 If FOR_SCH_FER_REPs is set to ‘1’ and this message is to
24 report the frame counts at the end of the burst on an assigned
25 Supplemental Channel, the mobile station shall set this field
26 to ‘1’; otherwise, the mobile station shall set this field to
27 SCH_ID - Forward Supplemental Channel identifier.
28 If the SCH_PWR_MEAS_INCL is set to ‘0’, the mobile station
29 shall omit this field; otherwise, the mobile shall set this field
30 to the Identifier of the Forward Supplemental Channel of
31 which the frame counts are being reported in this message.
32 SCH_PWR-
33 _MEAS_FRAMES - Number of received Supplemental Channel frames.
34 If SCH_PWR_MEAS_INCL is set to ‘0’, the mobile station shall
35 omit this field; otherwise, the mobile station shall set this field
36 to the total number of frames (SCH_TOT_FRAMESs] received
37 during the burst duration on the Supplemental Channel
38 specified by SCH_ID. If this measurement is greater than or
39 equal to 216 - 1, the mobile station shall set this field to
40 ‘1111111111111111’.
41 SCH_ERRORS-
42 _DETECTED - Number of detected bad Supplemental Channel frames.
2-587
3GPP2 C.S0005-A v6.0
1 If SCH_PWR_MEAS_INCL is set to ‘0’, the mobile station shall

3 to the number of bad frame detected on the Forward
4 Supplemental Channel of the SCH_ID for the duration of the
5 forward burst on this channel.
6 If the number of bad frames (SCH_BAD_FRAMESs) detected
7 on the SCH_ID Supplemental Channel during the burst is
8 greater than 1023, the mobile station shall set this field to
9 ‘1111111111’.
2-588
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.7 Send Burst DTMF Message
2 MSG_TAG: BDTMFM
Field Length (bits)
NUM_DIGITS 8
DTMF_ON_LENGTH 3
DTMF_OFF_LENGTH 3
NUM_DIGITS occurrences of the following field:
DIGITi 4
CON_REF_INCL 1
CON_REF 0 or 8
5 NUM_DIGITS – Number of DTMF digits.

6 The mobile station shall set this field to the number of DTMF
8 DTMF_ON_LENGTH – DTMF pulse width code.
9 The mobile station shall set this field to the DTMF_ON_LENGTH
11 requested width of DTMF pulses to be generated by the base
12 station.
13 Table 2.7.2.3.2.7-1. Recommended DTMF Pulse Width
DTMF_ON_LENGTH Recommended Pulse Width

Field (binary)
000 95 ms
001 150 ms
010 200 ms
011 250 ms
100 300 ms
101 350 ms
All other DTMF_ON_LENGTH codes are reserved.
14
2-589
3GPP2 C.S0005-A v6.0
1 DTMF_OFF_LENGTH – DTMF inter-digit interval code.

3 DTMF_OFF_LENGTH value shown in Table 2.7.2.3.2.7-2
4 corresponding to the requested minimum interval between
5 DTMF pulses to be generated by the base station.
6
7 Table 2.7.2.3.2.7-2. Recommended Minimum Inter-digit

8 Interval
DTMF_OFF_LENGTH Recommended Minimum

Field (binary) Inter-digit Interval
000 60 ms
001 100 ms
010 150 ms
011 200 ms
All other DTMF_OFF_LENGTH codes are reserved.
9
10 DIGITi – DTMF digit.

12 for each DTMF digit to be generated by the base station. The
13 mobile station shall set each occurrence of this field to the
14 code value shown in Table 2.7.1.3.2.4-4 corresponding to the
15 dialed digit.
21 If the CON_REF_INCL field is set to ‘0’, the mobile station

23 include this field and shall set it to the value of the connection
24 reference assigned to the service option connection of the call,
25 to which this message corresponds.
2-590
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.8 Status Message
2 MSG_TAG: STM
Field Length (bits)
RECORD_TYPE 8
RECORD_LEN 8

14 for this type of record.
2-591
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.9 Origination Continuation Message
2 MSG_TAG: ORCM
Field Length (bits)
DIGIT_MODE 1
NUM_FIELDS 8
CHARi 4 or 8
RECORD TYPE 8
RECORD_LEN 8

6 The mobile station shall set this field to the DIGIT_MODE
7 value from the Origination Message for which this message is
8 a continuation.
14 this field. The mobile station shall include occurrences of this
15 field for all dialed digits after those sent in the Origination
16 Message of which this message is a continuation. If the
17 DIGIT_MODE field is set to ‘0’, the mobile station shall set
18 each occurrence of this field to the code value shown in Table
19 2.7.1.3.2.4-4 corresponding to the dialed digit. If the
21 each occurrence of this field to the ASCII representation
24 If the MORE_RECORDS field in the last Origination Message, of which this message is a
25 continuation, is set to ‘1’, the mobile station shall include one or more occurrences of the
26 following three-field record; otherwise, the mobile station shall not include the following
27 record.
30 shown in Table 2.7.4-1.
2-592
3GPP2 C.S0005-A v6.0
1 The mobile station shall not include the record type for QoS
2 Parameters information record if MOB_QOSs is equal to ‘0’.
5 in the type-specific fields included in this record.
7 The mobile station shall include type-specific fields as
2-593
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.10 Handoff Completion Message
2 MSG_TAG: HOCM
Field Length (bits)
LAST_HDM_SEQ 2
One or more occurrences of the following field:
PILOT_PN 9
5 LAST_HDM_SEQ – Extended Handoff Direction Message, General Handoff

7 sequence number.
8 The mobile station shall set this field to the value of the
9 HDM_SEQ field from the Extended Handoff Direction Message,
10 General Handoff Direction Message, or the Universal Handoff
12 PILOT_PN – Pilot PN sequence offset.
14 for each pilot in the current Active Set. The mobile station
15 shall set this field to the pilot PN sequence offset, relative to
16 the zero offset pilot PN sequence in units of 64 PN chips, for
17 this pilot. If the Active Set contains more than one pilot, the
18 mobile station shall include the pilot offsets in the same order
19 as in the Extended Handoff Direction Message, the General
20 Handoff Direction Message, or the Universal Handoff Direction
21 Message that determined the current Active Set.
2-594
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.11 Parameters Response Message
2 MSG_TAG: PRSM
Field Length (bits)

PARAMETER_ID 16
PARAMETER_LEN 10
PARAMETER 0 or
PARAMETER_LEN + 1
5 The mobile station shall include one occurrence of the following three-field record for each
6 occurrence of the PARAMETER_ID field in the Forward Traffic Channel Retrieve Parameters
7 Message to which this message is a response. See Annex E.
8 PARAMETER_ID – Parameter identification.
10 PARAMETER_ID field for this parameter from the Retrieve
11 Parameters Message to which this message is a response.
12 PARAMETER_LEN – Parameter length.
13 The mobile station shall set this field to the length shown in
14 Table E-1 corresponding to this PARAMETER_ID.
15 If the mobile station is unable to return the value of this
16 parameter, or if the parameter identification is unknown, the
18 PARAMETER – Parameter value.
19 The mobile station shall set this field equal to the value of the
20 parameter shown in Table E-1 corresponding to the
21 PARAMETER_ID field of the record.
22 If the mobile station is unable to return the value of this
23 parameter, or if the parameter identification is unknown, the
24 mobile station shall omit this field.
2-595
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.12 Service Request Message
2 MSG_TAG: SRQM
Field Length (bits)
SERV_REQ_SEQ 3
REQ_PURPOSE 4
Zero or one occurrence of the following record:
RECORD_TYPE 8
RECORD_LEN 8
5 SERV_REQ_SEQ – Service request sequence number.

6 The mobile station shall set this field to the service request
7 sequence number pertaining to this request message as
8 specified in 2.6.4.1.2.1.1.
9 REQ_PURPOSE – Request purpose.
10 The mobile station shall set this field to the appropriate
11 REQ_PURPOSE code from Table 2.7.2.3.2.12-1 to indicate the
12 purpose of the message.
13 Table 2.7.2.3.2.12-1. REQ_PURPOSE Codes
REQ_PURPOSE
(binary) Meaning
0000 Indicates that the purpose of the

message is to accept a proposed
service configuration.
message is to reject a proposed service
configuration.
message is to propose a service
configuration.
All other REQ_PURPOSE codes are reserved.
14
15 If the REQ_PURPOSE code is set to ‘0010’, the mobile station shall include one occurrence
16 of the following three-field record to specify the proposed service configuration; otherwise,
17 the mobile station shall not include the following record:
2-596
3GPP2 C.S0005-A v6.0
2 shown in Table 2.7.4-1 corresponding to the Service
3 Configuration information record.
6 included in the type-specific fields of the Service Configuration
9 The mobile station shall set these fields as specified in 3.7.5.7
10 for the Service Configuration information record.
2-597
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.13 Service Response Message
2 MSG_TAG: SRPM
Field Length (bits)
SERV_REQ_SEQ 3
RESP_PURPOSE 4
RECORD_TYPE 8
RECORD_LEN 8
5 SERV_REQ_SEQ – Service request sequence number.

7 SERV_REQ_SEQ field of the Service Request Message to which
8 it is responding.
9 RESP_PURPOSE – Response purpose.
10 The mobile station shall set this field to the appropriate
11 RESP_PURPOSE code from Table 2.7.2.3.2.13-1 to indicate
12 the purpose of the message.
13
14 Table 2.7.2.3.2.13-1. RESP_PURPOSE Codes
RESP_PURPOSE
(binary) Meaning

message is to accept a proposed
service configuration.
configuration.
configuration.
All other RESP_PURPOSE codes are reserved.
15
16 If the RESP_PURPOSE field is set to ‘0010’, the mobile station shall include one occurrence
17 of the following record to specify the proposed service configuration; otherwise, the mobile
18 station shall not include the following record:
2-598
3GPP2 C.S0005-A v6.0

10 The mobile station shall set these fields as specified in 3.7.5.7
2-599
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.14 Service Connect Completion Message
2 MSG_TAG: SCCM
Field Length (bits)
RESERVED 1
SERV_CON_SEQ 3
5 RESERVED Reserved bit.

7 SERV_CON_SEQ – Service connect sequence number.
9 SERV_CON_SEQ field of the Service Connect Message to which
10 it is responding.
2-600
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.15 Service Option Control Message
2 MSG_TAG: SOCM
Field Length (bits)
CON_REF 8
SERVICE_OPTION 16
RESERVED 7
CTL_REC_LEN 8
Type-specific fields 8 × CTL_REC_LEN
5 CON_REF – Service option connection reference.

6 The mobile station shall set this field to the reference for the
7 target service option (see 2.6.4.1.2).
9 The mobile station shall set this field to the service option in
10 use with the service option connection.
11 RESERVED – Reserved bits.
13 CTL_REC_LEN – Control record length.
15 included in the type-specific fields of this service option
16 control record.
18 The mobile station shall set these fields as specified by the
19 requirements for the service option.
2-601
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.16 Status Response Message
2 MSG_TAG: STRPM
Field Length (bits)
QUAL_INFO_TYPE 8
QUAL_INFO_LEN 3
Type-specific fields. 8 × QUAL_INFO_LEN
RECORD_TYPE 8
RECORD_LEN 8

14 The mobile station shall include all the records requested in the corresponding Status
15 Request Message. The mobile station shall include one occurrence of the following fields for
16 each information record that is included:
26 for this type of record, according to the mobile station’s
27 capabilities under the qualification information included in
28 this message.
2-602
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.17 TMSI Assignment Completion Message
2 MSG_TAG: TACM
2-603
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.18 Supplemental Channel Request Message
2 MSG_TAG: SCRM
Field Length (bits)
SIZE_OF_REQ_BLOB 4
REQ_BLOB 8 × SIZE_OF_REQ_BLOB
USE_SCRM_SEQ_NUM 1
SCRM_SEQ_NUM 0 or 4
REF_PN 0 or 9
PILOT_STRENGTH 0 or 6
NUM_ACT_PN 0 or 3
If NUM_ACT_PN is included, the mobile station shall include
NUM_ACT_PN occurrences of the following record:
ACT_PN_PHASE 15
ACT_PILOT_STRENGTH 6
NUM_NGHBR_PN 0 or 3
If NUM_NGHBR_PN is included, the mobile station shall
include NUM_NGHBR_PN occurrences of the following record:
NGHBR_PN_PHASE 15
NGHBR_PILOT_STRENGTH 6
REF_PILOT_REC_INCL 0 or 1
REF_PILOT_REC_TYPE 0 or 3
2-604
3GPP2 C.S0005-A v6.0
Field Length (bits)
REF_RECORD_LEN 0 or 3
Type-specific fields 0 or 8 × RECORD_LEN
If NUM_ACT_PN is included, the mobile station shall include
NUM_ACT_PN occurrences of the following record:
PILOT_REC_INCL 1
PILOT_REC_TYPE 0 or 3
RECORD_LEN 0 or 3
If NUM_NGHBR_PN is included, the mobile station shall
include NUM_NGHBR_PN occurrences of the following record:
PILOT_REC_INCL 1
RECORD_LEN 0 or 3
3 SIZE_OF_REQ_BLOB – Size of the request information block of bytes (REQ_BLOB).

4 The mobile station shall set this field to the number of bytes
5 in the Reverse Supplemental Code Channel or the Reverse
6 Supplemental Channel request block of bytes (REQ_BLOB).
7 REQ_BLOB – Reverse Supplemental Code Channel request block of bytes.
8 The mobile station shall include information in this field
9 containing the parameters that specify the characteristics of
10 the Reverse Supplemental Code Channels or the Reverse
11 Supplemental Channel request. The mobile station shall set
12 this field in accordance with the connected Service Option.
13 USE_SCRM_SEQ_NUM – Use Supplemental Channel Request Message sequence number
14 indicator.
15 The mobile station shall set this field to ‘1’ if the Supplemental
16 Channel Request Message sequence number is included in
18 to '0'.
19 SCRM_SEQ_NUM – Supplemental Channel Request Message sequence number.
2-605
3GPP2 C.S0005-A v6.0
1 If USE_SCRM_SEQ_NUM is set to ’1’, the mobile station shall

2 set this field to the Supplemental Channel Request Message
3 sequence number that the base station is to include in a
4 Supplemental Channel Assignment Message or Extended
5 Supplemental Channel Assignment Message which is in
6 response to this message; otherwise, the mobile station shall
7 omit this field.
9 If SIZE_OF_REQ_BLOB is set to ‘0000’ and
10 USE_SCRM_SEQ_NUM is set to ‘0’, the mobile station shall
12 to the PN sequence offset of the pilot used by the mobile
13 station to derive its time reference, relative to the zero offset
14 pilot PN sequence in units of 64 PN chips.
15 PILOT_STRENGTH – Reference pilot strength.
19 to
20 - 2 × 10 × log10 PS,

22 station to derive its time reference (see 2.1.5 of [2]), measured
23 as specified in 2.6.6.2.2. If this value (-2 × 10 log10 PS) is
24 less than 0, the mobile station shall set this field to ‘000000’.
25 If this value is greater than ‘111111’, the mobile station shall
27 NUM_ACT_PN – Number of reported pilots in the Active Set.
31 to the number of reported pilots in the Active Set other than
32 the pilot identified by the REF_PN field.
33 If SIZE_OF_REQ_BLOB is set to ‘0000’ and USE_SCRM_SEQ_NUM is set to ‘0’, the mobile
34 station shall not include any occurrence of the following record; otherwise, the mobile
35 station shall include one occurrence of the following two-field record for each pilot in the
36 Active Set other than the pilot identified by the REF_PN field:
37 ACT_PN_PHASE – Active pilot measured phase.
38 The mobile station shall set this field to the phase of this pilot
39 PN sequence relative to the zero offset pilot PN sequence, in
40 units of one PN chip, as specified in 2.6.6.2.4.
41 ACT_PILOT_STRENGTH – Active pilot strength.
43 - 2 × 10 × log10 PS,
2-606
3GPP2 C.S0005-A v6.0

5 ‘111111’.
6 NUM_NGHBR_PN – Number of reported neighbor pilots in the Candidate Set and
7 the Neighbor Set.
8 If SIZE_OF_REQ_BLOB is set to ‘0000’, the mobile station
10 this field as follows:
12 reported pilots which are not in the Active Set and have
13 measurable strength that exceeds (T_ADDs - T_MULCHANs).
14 (NUM_ACT_PN + NUM_NGHBR_PN) shall not exceed 8. If
15 there are more than (8 - NUM_ACT_PN) pilots not in the Active
16 Set with strength exceeding (T_ADDs - T_MULCHANs),
17 the mobile station shall set NUM_NGHBR_PN to
18 (8 - NUM_ACT_PN) and report the NUM_NGHBR_PN strongest
19 pilots not in the Active Set.
22 station shall include one occurrence of the following two-field record for each of the
23 NUM_NGHBR_PN reported pilots.
24 NGHBR_PN_PHASE – Neighbor pilot measured phase.
25 The mobile station shall set this field to the phase of this pilot
26 PN sequence relative to the zero offset pilot PN sequence, in
27 units of one PN chip, as specified in 2.6.6.2.4.
28 NGHBR_PILOT-
29 _STRENGTH – Neighbor pilot strength.
31 - 2 × 10 × log10 PS,
36 ‘111111’.
37 REF_PILOT_REC_INCL – Additional pilot information included indicator.
38 If SIZE_OF_REQ_BLOB is set to ‘0000’, the mobile station
40 include this field and set it as follows:
41 The mobile station shall set this field to ‘1’ if additional
42 reference pilot information listed in the
43 REF_PILOT_REC_TYPE and REF_RECORD_LEN fields are
44 included. The mobile station shall set this field to ‘0’ if the
45 corresponding pilot is the common pilot and there is no
46 additional pilot information included.
2-607
3GPP2 C.S0005-A v6.0
1 REF_PILOT_REC_TYPE – Reference pilot record type.

2 If REF_PILOT_REC_INCL is included and set to ‘0’, the mobile
3 station shall omit this field. If REF_PILOT_REC_INCL is
4 included and set to ‘1’, the mobile station shall set this field to
5 the REF_PILOT_REC_TYPE value shown in Table 2.7.2.3.2.
6 3334-1 corresponding to the type of Pilot Record specified by
7 this record.
8 REF_RECORD_LEN – Pilot record length for the reference pilot.
11 included and set to ‘1’, the mobile station shall set this field to
12 the number of octets in the type-specific fields of this pilot
13 record.
14 Type-specific fields – Pilot record type-specific fields for the reference pilot.
17 included and set to ‘1’, the mobile station shall include type-
18 specific fields based on the REF_PILOT_REC_TYPE of this pilot
19 record.
20
21 If REF_PILOT_REC_TYPE is equal to ‘000’, the mobile station shall include the following
22 fields:
23
Field Length (bits)
QOF 2
WALSH_LENGTH 3
PILOT_WALSH (WALSH_LENGTH +
6)
RESERVED 0 to 7 (as needed)
24
25 QOF – Quasi-orthogonal function index.

26 The mobile station shall set this field to the index of the
27 Quasi-orthogonal function of the corresponding Auxiliary
28 Pilot.
29 WALSH_LENGTH – Length of the Walsh code for the reference pilot.
30 The mobile station shall set this field to the WALSH_LENGTH
32 length of the Walsh code for the pilot that is used as the
33 Auxiliary Pilot.
34 PILOT_WALSH – Walsh code for the Auxiliary Pilot used by the mobile station
35 to derive its time reference.
2-608
3GPP2 C.S0005-A v6.0
1 The mobile station shall set this field to the Walsh code
2 corresponding to the Auxiliary Pilot.
4 The base station shall set all the bits of this field to ‘0’ to make
5 the entire record octet-aligned.
8 station shall include one occurrence of the following record for each pilot in the Active Set
9 other than the pilot identified by the REF_PN field:
10 PILOT_REC_INCL – Additional pilot information included indicator.
11 The mobile station shall set this field to ‘1’ if additional pilot
12 information listed in the PILOT_REC_TYPE and RECORD_LEN
13 fields are included. The mobile station shall set this field to ‘0’
14 if the corresponding pilot is the common pilot and there is no
16 PILOT_REC_TYPE – Reference pilot record type.
17 If PILOT_REC_INCL is set to ‘0’, the mobile station shall omit
18 this field; otherwise, the mobile station shall set this field to
19 the PILOT_REC_TYPE value shown in Table 32.7.2.3.2. 3334-
20 1 corresponding to the type of Pilot Record specified by this
21 record.
22 RECORD_LEN – Pilot record length.
26 record.
27 Type-specific fields – Pilot record type-specific fields.
29 this field; otherwise, the mobile station shall include type-
30 specific fields based on the PILOT_REC_TYPE of this pilot
31 record as described in 3.7.6.1.
32

35 station shall include one occurrence of the following record for each of the NUM_NGHBR_PN
36 reported pilots.
43 PILOT_REC_TYPE – Reference pilot record type.
2-609
3GPP2 C.S0005-A v6.0

3 the PILOT_REC_TYPE value shown in Table 3.7.2.3.2.33-1
4 corresponding to the type of Pilot Record specified by this
5 record.
10 record.
16
2-610
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.19 Candidate Frequency Search Response Message
2 MSG_TAG: CFSRSM
Field Length (bits)
LAST_CFSRM_SEQ 2
TOTAL_OFF_TIME_FWD 6
MAX_OFF_TIME_FWD 6
TOTAL_OFF_TIME_REV 6
MAX_OFF_TIME_REV 6
PCG_OFF_TIMES 1
ALIGN_TIMING_USED 1
MAX_NUM_VISITS 0 or 5
INTER_VISIT_TIME 0 or 6
5 LAST_CFSRM_SEQ – Candidate Frequency Search Request Message sequence

6 number.
8 CFSRM_SEQ field from the Candidate Frequency Search
9 Request Message to which this message is a response.
10 TOTAL_OFF_TIME_FWD – Total time that the mobile station is off the Forward Traffic
11 Channel.
12 The mobile station shall set this field to the mobile station’s
13 estimate of the total number of frames or power control
14 groups for which the mobile station will need to suspend its
16 the Candidate Frequency, to perform the requested search,
17 and to re-tune to the Serving Frequency. If the mobile station
18 requires multiple visits to the Candidate Frequency to
19 complete the requested search, the mobile station shall set
20 this field to the total number of frames (if PCG_OFF_TIME is
21 set to ‘0’) or power control groups (if PCG_OFF_TIME is set to
22 ‘1’) for all visits to the Candidate Frequency in a search
23 period.
24 MAX_OFF_TIME_FWD – Maximum time the mobile station is away from the Forward
25 Traffic Channel.
2-611
3GPP2 C.S0005-A v6.0
2 estimate of the maximum number of frames (if
3 PCG_OFF_TIME is set to ‘0’) or power control groups (if
4 PCG_OFF_TIME is set to ‘1’) for which the mobile station will
5 need to suspend its current Forward Traffic Channel
6 processing during a visit to the Candidate Frequency, to
7 perform a part of the requested search, and to re-tune to the
9 TOTAL_OFF_TIME_REV – Total time that the mobile station is away from the Reverse
10 Traffic Channel.
12 estimate of the total number of frames or power control
15 the Candidate Frequency, to perform the requested search,
16 and to re-tune to the Serving Frequency. If the mobile station
17 requires multiple visits to the Candidate Frequency to
18 complete the requested search, the mobile station shall set
19 this field to the total number of frames or power control
20 groups for all visits to the Candidate Frequency in a search
21 period.
22 MAX_OFF_TIME_REV – Maximum time the mobile station is away from the Reverse
23 Traffic Channel.
25 estimate of the maximum number of frames or power control
27 current Forward Traffic Channel processing during a visit to
28 the Candidate Frequency, to perform a part of the requested
29 search, and to re-tune to the Serving Frequency.
30 PCG_OFF_TIMES – Indicator if off times are expressed in units of power control
31 groups.
32 If P_REV_IN_USEs is less than six, the mobile station shall set
33 this field to ‘0’; otherwise, the mobile station shall set this field
34 as follows:
35 The mobile station shall set this field to ‘1’ if it expresses
36 TOTAL_OFF_TIME_FWD, MAX_OFF_TIME_FWD,
37 TOTAL_OFF_TIME_REV, and MAX_OFF_TIME_REV in units of
38 power control groups; otherwise, the mobile station shall set
39 this field to ‘0’ so that TOTAL_OFF_TIME_FWD,
40 MAX_OFF_TIME_FWD, TOTAL_OFF_TIME_REV, and
41 MAX_OFF_TIME_REV are expressed in units of frames.
42 ALIGN_TIMING_USED – Alignment timing used indicator.
43 The mobile station shall set this field to ‘1’ if it will align the
44 times of its visits away from the Serving Frequency, as
45 requested by the base station; otherwise, the mobile station
47 MAX_NUM_VISITS – Maximum number of visits per search period.
2-612
3GPP2 C.S0005-A v6.0
1 If the ALIGN_TIMING_USED field is set to ‘0’, the mobile

3 include this field and set it to the maximum number of visits
4 per search period minus one.
5 INTER_VISIT_TIME – Inter-visit time.
6 If the mobile station includes the MAX_NUM_VISITS field and
7 sets it to a value other than 0, the mobile station shall include
8 this field and set it as described below; otherwise, the mobile
10 The mobile station shall set INTER_VISIT_TIME to
11 min ( 63, inter_visit_time / search_time_resolution  )
12 where
13 search_time_resolution is equal to 0.02 if the mobile
14 station sets PCG_OFF_TIMES to ‘0’; otherwise,
15 search_time_resolution is equal to 0.00125,
16 and
17 inter_visit_time is the mobile station’s estimate of the
18 time, in seconds, between the beginning of consecutive
19 visits away from the Serving Frequency.
2-613
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.20 Candidate Frequency Search Report Message
2 MSG_TAG: CFSRPM
Field Length (bits)
LAST_SRCH_MSG 1
LAST_SRCH_MSG_SEQ 2
SEARCH_MODE 4
MODE_SPECIFIC_LEN 8
Mode-specific fields 8×
MODE_SPECIFIC_LEN
5 LAST_SRCH_MSG – Indicator for the type of message that started the search being
6 reported.
7 If this message is being sent to report the results of a single
8 search or a periodic search started by a Candidate Frequency
9 Search Control Message or by a Candidate Frequency Search
10 Request Message, the mobile station shall set this field to ‘0’;
12 LAST_SRCH_MSG_SEQ – Sequence number received in the message that started the
13 search being reported.
14 If this message is being sent in response to a Candidate
15 Frequency Search Control Message, the mobile station shall set
16 this field to the value of the CFSCM_SEQ field from the
17 Candidate Frequency Search Control Message.
18 If this message is being sent in response to a Candidate
19 Frequency Search Request Message, the mobile station shall
20 set this field to the value of the CFSRM_SEQ field from the
21 Candidate Frequency Search Request Message.
22 If this message is being sent in response to a General Handoff
23 Direction Message or a Universal Handoff Direction Message,
24 the mobile station shall set this field to the value of the
25 HDM_SEQ field from the General Handoff Direction Message or
26 the Universal Handoff Direction Message.
27 SEARCH_MODE – Search mode.
28 The mobile station shall set this field to the SEARCH_MODE
29 value shown in Table 3.7.3.3.2.27-2 corresponding to the type
30 of search specified by the Candidate Frequency Search Request
31 Message that specified the search parameters.
32 MODE_SPECIFIC_LEN – Length of mode-specific fields included in this message.
33 Mode-specific fields – Search mode-specific fields.
2-614
3GPP2 C.S0005-A v6.0
1 The mobile station shall include mode-specific fields based on

2 the SEARCH_MODE of this message.
3 If SEARCH_MODE is equal to ‘0000’, the mobile station shall include the following fields:
Field Length (bits)
BAND_CLASS 5
CDMA_FREQ 11
SF_TOTAL_RX_PWR 5
CF_TOTAL_RX_PWR 5
NUM_PILOTS 6
NUM_PILOTS occurrences of the following record:
PILOT_PN_PHASE 15
PILOT_STRENGTH 6
RESERVED_1 3
PILOT_REC_INCL 1
RECORD_LEN 0 or 3
6 BAND_CLASS - Band class.

7 If this message is being sent to report an unsuccessful hard
8 handoff attempt, the mobile station shall set this field to the
9 CDMA band class corresponding to the CDMA Frequency
10 Assignment for the Target Frequency, as specified in [30]. If
11 this message is being sent to report measurements on a
12 Candidate Frequency, the mobile station shall set this field to
13 the CDMA band class corresponding to the CDMA Frequency
14 Assignment for the Candidate Frequency, as specified in [30].
15 CDMA_FREQ – Frequency assignment.
17 handoff attempt, the mobile station shall set this field to the
18 CDMA Channel number, in the specified CDMA band class,
19 corresponding to the CDMA Frequency Assignment for the
20 Target Frequency, as specified in 3.1.1.1 of [2]. If this
21 message is being sent to report measurements on a Candidate
22 Frequency, the mobile station shall set this field to the CDMA
23 Channel number, in the specified CDMA band class,
24 corresponding to the CDMA Frequency Assignment for the
25 Candidate Frequency, as specified in 3.1.1.1 of [2].
2-615
3GPP2 C.S0005-A v6.0
1 SF_TOTAL_RX_PWR – Total received power on the Serving Frequency.

3 min (31,  (10 × log10(total_received_power) + 110) / 2  )
4 where total_received_power is the mean input power received

5 by the mobile station on the Serving Frequency, in mW/1.23
6 MHz.
7 CF_TOTAL_RX_PWR – Indicates the total received power on the Target Frequency or
8 the Candidate Frequency.
10 handoff attempt, the mobile station shall include the total
11 received power on the Target Frequency; if this message is
12 being sent to report measurements on a Candidate Frequency,
13 the mobile station shall include the total received power on

18 by the mobile station on the Target Frequency or the
19 Candidate Frequency, in mW/1.23 MHz.
20 NUM_PILOTS – Number of pilots.
22 included in this message. The mobile station shall set this
23 field to a value from 0 to N8m, inclusive.
24
25 The mobile station shall include NUM_PILOTS occurrences of the following three-field
26 record:
33 - 2 × 10 × log10 PS,

38 ‘111111’.
39 RESERVED_1 – Reserved bits.
2-616
3GPP2 C.S0005-A v6.0
1 The mobile station shall include NUM_PILOTS occurrences of the following record in the
2 same order as the pilots listed above.
9 PILOT_REC_TYPE – Reference Pilot record type
14 record.
19 record.
25 If SEARCH_MODE is equal to ‘0001’, the mobile station shall include the following fields:
26
Field Length (bits)
BAND_CLASS 5
SF_TOTAL_RX_PWR 5
NUM_ANALOG_FREQS 3
RESERVED_2 5
NUM_ANALOG_FREQS occurrences of the following record:
ANALOG_FREQ 11
SIGNAL_STRENGTH 6
27
RESERVED_3 0 - 7 (as needed)
28
29 BAND_CLASS – Band class.

30 The mobile station shall set this field to the CDMA band class
31 corresponding to the analog frequencies that are being
32 reported in this message, as specified in [30].
2-617
3GPP2 C.S0005-A v6.0
1 SF_TOTAL_RX_PWR – Indicates the total received power on the Serving Frequency.


5 by the mobile station on the Serving Frequency, in mW/1.23
6 MHz.
7 NUM_ANALOG_FREQS – Number of analog frequencies.
8 The base station shall set this field to the number of analog
9 frequencies included in this message.
10 RESERVED_2 – Reserved bits.
12
13 The message will include NUM_ANALOG_FREQS occurrences of the following threetwo-field

14 record, one for each neighbor on the candidate frequency.
15 ANALOG_FREQ – Analog frequency channel number.
16 The base station shall set this field analog frequency channel
17 number to search.
18 SIGNAL_STRENGTH – Signal strength.
20 - 0.5 × SS,
21 where SS is the strength of this signal, measured in dBm as
22 specified in 2.6.6.2.10.3. If this value (- 0.5 × SS) is less
24 this value is greater than 63, the mobile station shall set this
25 field to ‘111111’.
26
27 RESERVED_3 – The mobile station shall add reserved bits as needed in order
28 to make the length of the entire message record equal to an
29 integer number of octets. The mobile station shall set each of
2-618
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.21 Periodic Pilot Strength Measurement Message
2 MSG_TAG: PPSMM
Field Length (bits)
REF_PN 9
PILOT_STRENGTH 6
KEEP 1
SF_RX_PWR 5
NUM_PILOT 4
NUM_PILOT occurrences of the following record:
PILOT_PN_PHASE 15
PILOT_STRENGTH 6
KEEP 1
PILOT_REC_INCL 1
RECORD_LEN 0 or 3
SETPT_INCL 1
FCH_INCL 0 or 1
FPC_FCH_CURR_SETPT 0 or 8
DCCH_INCL 0 or 1
FPC_DCCH_CURR_SETPT 0 or 8
NUM_SUP 0 or 2
If NUM_SUP is included, include NUM_SUP occurrences of
the following fields:
SCH_ID 1
FPC_SCH_CURR_SETPT 8
5 REF_PN - Time reference PN sequence offset.
2-619
3GPP2 C.S0005-A v6.0
4 of 64 PN chips.
5 PILOT_STRENGTH - Pilot strength.
7 - 2 × 10 × log10PS ,
10 specified in 2.6.6.2.2. If this value is less than 0, the mobile
11 station shall set this field to ‘000000’. If this value is greater
12 than ‘111111’, the mobile station shall set this field to
13 ‘111111’.
14 KEEP - Keep pilot indicator.
17 (see [2]) has expired, the mobile station shall set this field to
18 ‘0’; otherwise, the mobile station shall set this field to ‘1’.
19 SF_RX_PWR - The received power spectral density of the Serving Frequency.
21 min (31,  (10 × log10(spec_density) + 120) / 2  )
22 where spec_density is the mobile station received power

23 spectral density of the Serving Frequency, in mW/1.23MHz.
24 If this value is less than 0, the mobile station shall set this
25 field to ‘00000’.
26 NUM_PILOT - Number of Pilots.
27 The mobile station shall set this field to the number of other
28 reported pilots of the Active Set and the Candidate Set.
29
30 The mobile station shall include NUM_PILOT occurrences of the following three-field record,
31 one for each pilot in the Active Set and one for each pilot in the Candidate Set, other than
32 the pilot identified by the REF_PN field.
33 PILOT_PN_PHASE - Pilot measured phase.
37 PILOT_STRENGTH - Pilot strength.
39  - 2 × 10 × log10PS ,
2-620
3GPP2 C.S0005-A v6.0

2 2.6.6.2.2. If this value is less than 0, the mobile station shall
3 set this field to ‘000000’. If this value is greater than
4 ‘111111’, the mobile station shall set this field to ‘111111’.
5 KEEP - Keep pilot indicator.
9 The mobile station shall include NUM_PILOTS occurrences of the following record in the
10 same order as the pilots listed above.
11 PILOT_REC_INCL - Additional pilot information included indicator.
17 PILOT_REC_TYPE - Reference Pilot record type
22 record.
23 RECORD_LEN - Pilot record length.
27 record.
28 Type-specific fields - Pilot record type-specific fields.
32 record as described in 2.7.2.3.2.34.
33 SETPT_INCL - Setpoint information included indicator.
34 The mobile station shall set this field to ‘1’ if setpoint
35 information is included in this message; otherwise, the mobile
37 FCH_INCL - Fundamental Channel included indicator.
38 If SETPT_INCL is equal to ‘1’, the mobile station shall include
39 this field and set it as follows; otherwise, the mobile station
41 The mobile station shall set this field to ‘1’ if FPC_PRI_CHANs
42 is equal to ‘0’; otherwise, the mobile station shall set this field
43 to ‘0’.
2-621
3GPP2 C.S0005-A v6.0
1 FPC_FCH-
2 _CURR_SETPT - The outer loop Eb/Nt setpoint of the Fundamental Channel.
3 If SETPT_INCL is equal to ‘1’ and if FCH_INCL is set to ‘1’, the
4 mobile station shall set this field to the value of the Eb/Nt
5 setpoint, in units of 0.125 dB, currently in use in the
6 Fundamental Channel power control outer loop estimation;
8 DCCH_INCL - Dedicated Control Channel included indicator.
12 The mobile station shall set this field to ‘1’ if FPC_PRI_CHANs
13 is equal to ‘1’; otherwise, the mobile station shall set this field
14 to ‘0’.
15 FPC_DCCH-
16 _CURR_SETPT - The outer loop Eb/Nt setpoint of the Forward Dedicated
17 Channel.
18 If SETPT_INCL is equal to ‘1’, and if DCCH_INCL is set to ‘1’,
19 the mobile station shall set this field to the value of the Eb/Nt
20 setpoint, in units of 0.125 dB, currently in use in the
21 Dedicated Channel power control outer loop estimation;
23 NUM_SUP - The number of Supplemental Channels.
27 The mobile station shall set this field to the total number of
28 the Supplemental Channels reported by this message.
29 The mobile station shall include NUM_SUP occurrences of the following two fields:
30 SCH_ID - The Supplemental Channel index.
31 The mobile station shall set this field to the Supplemental
32 Channel index to indicate the Forward Supplemental Channel
33 that is to be reported.
34 FPC_SCH-
35 _CURR _SETPT - The supplemental channel outer loop Eb/Nt setpoint.
36 The mobile station shall set this field to the value of the power
37 control outer loop Eb/Nt setpoint, in units of 0.125 dB,
38 currently in use in the Channel specified by SCH_ID.
39
2-622
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.22 Outer Loop Report Message
2 MSG_TAG: OLRM
Field Length (bits)
FCH_INCL 1
FPC_FCH_CURR_SETPT 0 or 8
DCCH_INCL 1
FPC_DCCH_CURR_SETPT 0 or 8
NUM_SUP 2
Include NUM_SUP occurrences of the following fields:
SCH_ID 1
FPC_SCH_CURR_SETPT 8
5 FCH_INCL – Fundamental Channel included indicator.

7 CURR_FCH_SETPT FPC_FCH_CURR_SETPT is included;
8 otherwise the mobile station shall set this field to ‘0’.
9 FPC_FCH-
10 _CURR_SETPT – The outer loop Eb/Nt setpoint of the Fundamental Channel.
11 If FCH_INCL is set to ‘1’, the mobile station shall set this field
12 to the value of the Eb/Nt setpoint, in units of 0.125 dB,
13 currently in use in the Fundamental Channel power control
14 outer loop estimation; otherwise, the mobile station shall omit
15 this field.
16 DCCH_INCL – Dedicated Control Channel included indicator.
17 The mobile station shall set this field to ‘1’ if the
18 CURR_DCCH_SETPT FPC_DCCH_CURR_SETPT field is
19 included; otherwise the mobile station shall set this field to ‘0’.
20 FPC_DCCH-
21 _CURR_SETPT – The outer loop Eb/Nt setpoint of the Forward Dedicated
22 Channel.
23 If DCCH_INCL is set to ‘1’, the mobile station shall set this
24 field to the value of the Eb/Nt setpoint, in units of 0.125 dB,
25 currently in use in the Dedicated Channel power control outer
26 loop estimation; otherwise, the mobile station shall omit this
27 field.
2-623
3GPP2 C.S0005-A v6.0
1 NUM_SUP – The number of Supplemental Channels.

2 The mobile station shall set this field to the total number of
3 the Supplemental Channels reported by this message.
4 The mobile station shall in NUM_SUP occurrences of the following two fields:
5 SCH_ID – The Supplemental Channel index.
7 Channel index to indicate the Forward Supplemental Channel
8 that to be reported
9 FPC_SCH-
10 _CURR _SETPT – The supplemental outer loop Eb/Nt setpoint.
11 The mobile station shall set this field to the value of the power
12 control outer loop Eb/Nt setpoint, in units of 0.125 dB,
13 currently in use in the Channel specified by SCH_ID.
14
2-624
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.23 Resource Request Message
2 MSG_TAG: RRM
2-625
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.24 Resource Request Mini Message
2 MSG_TAG: RRMM
2-626
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.25 Extended Release Response Message
2 MSG_TAG: ERRM
2-627
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.26 Extended Release Response Mini Message
2 MSG_TAG: ERRMM
2-628
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.27 Pilot Strength Measurement Mini Message
2 MSG_TAG: PSMMM
Field Length (bits)
PSMM_POS 3
PILOT_STRENGTH 6
RANK 3
4
5 PSMM_POS – Pilot Strength Measurement Message position.

6 The mobile station shall set this field to an index
7 corresponding to the position, within the last sent Pilot
8 Strength Measurement Message (see 2.7.2.3.2.5) or Extended
9 Pilot Strength Measurement Message (see 2.7.2.3.2.343), of the
10 Active-Set pilot whose strength is being reported. The mobile
11 station shall use a value of 0 to report the pilot represented by
12 the REF_PN field in the last sent Pilot Strength Measurement
13 Message or Extended Pilot Strength Measurement Message.
14 The mobile station shall use a value of n, where n is an
15 integer greater than 0, to report the pilot represented by the
th
16 n occurrence of the PILOT_PN_PHASE field in the last sent
17 Pilot Strength Measurement Message or Extended Pilot Strength
18 Measurement Message.
21 -2 × 10 × log10 PS,
22 where PS is the strength of this Active-Set pilot, measured as
23 specified in [2]. If this value is less than 0, the mobile station
24 shall set this field to ‘000000’. If this value is greater than
25 ‘111111’, the mobile station shall set this field to ‘111111’.
26 RANK – Rank order.
27 The mobile station shall set this field to the rank order of the
28 pilot whose strength is being reported, relative to all other
29 pilots in the current Active Set. The mobile station shall use a
30 value of 0 to report the strongest pilot in the current Active
31 Set.
2-629
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.28 Supplemental Channel Request Mini Message
2 MSG_TAG: SCRMM
Field Length (bits)
REQ_BLOB 16
4
5 REQ_BLOB – Reverse Supplemental Channel request block of bytes.

6 The mobile station shall include information in this field
7 containing the parameters that specify the characteristics of
8 the Reverse Supplemental Channels request. The mobile
9 station shall set this field in accordance with the connected
10 Service Options.
2-630
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.29 Resource Release Request Message
2 MSG_TAG: RRRM
GATING_DISCONNECT_IND 1
CON_REF 0 or 8
PURGE_SERVICE 0 or 1
5 GATING-
6 _DISCONNECT_IND - Reverse pilot gating or service disconnect indicator.
7 If the mobile station requests that reverse pilot gating

8 operation to be performed, the mobile station shall set this
9 field to ‘1’; otherwise (if the mobile station requests that the
10 service option connection specified by CON_REF to be
11 released), the mobile station shall set this field to ‘0’.
12 CON_REF - Connection reference.
13 If the GATING_DISCONNECT_IND field is set to ‘1’, the mobile

16 The mobile station shall set this field to the connection

17 reference corresponding to the service option connection that
18 is requested to be released.
19 PURGE_SERVICE - Purge service instance indicator.

23 If the packet data service instance identified by CON_REF has

24 been inactivated, the mobile station shall set this field to ‘1’;
2-631
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.30 Resource Release Request Mini Message
2 MSG_TAG: RRRMM
GATING_DISCONNECT_IND 1
CON_REF 0 or 8
PURGE_SERVICE 0 or 1
5 GATING-
6 _DISCONNECT_IND - Reverse pilot gating or service disconnect indicator.
7 If the mobile station requests that reverse pilot gating

8 operation to be performed, the mobile station shall set this
9 field to ‘1’; otherwise (if the mobile station requests that the
10 service option connection specified by CON_REF to be
11 released), the mobile station shall set this field to ‘0’.
12 CON_REF - Connection reference.

16 The mobile station shall set this field to the connection

17 reference corresponding to the service option connection that
18 is requested to be released.
19 PURGE_SERVICE - Purge service instance indicator.

23 If the packet data service instance identified by CON_REF has

24 been inactivated, the mobile station shall set this field to ‘1’;
2-632
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.31 User Zone Update Request Message
2 MSG_TAG: UZURM
Field Length (bits)
UZID 16
5 UZID - User Zone identifiers.

6 The mobile station shall set this field to the UZIDs.
2-633
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.32 Enhanced Origination Message
2 MSG_TAG: EOM
Field Length (bits)
TAG 4
CH_IND 3
SR_ID 3
GLOBAL_EMERGENCY_CALL 1
MS_INIT_POS_LOC_IND 0 or 1
ENC_INFO_INCL 1
SERVICE_OPTION 16
MORE_SO_INFO_INCL 1
NUM_ALT_SO 0 or 3
ALT_SO 16
SO_GROUP_NUM 0 or 5
SO_BITMAP 0 or 4 x
SO_BITMAP_IND
DRS 1
PREV_SID_INCL 1
PREV_SID 0 or 15
PREV_NID_INCL 1
PREV_NID 0 or 16
2-634
3GPP2 C.S0005-A v6.0
PREV_PZID_INCL 1
PREV_PZID 0 or 8
DIALED_DIGS_INCL 1
DIGIT_MODE 0 or 1
NUMBER_TYPE 0 or 3
NUMBER_PLAN 0 or 4
NUM_FIELDS 0 or 8
CHARi 4 or 8
NUM_RECS 5
NUM_RECS occurrences of the following three-field records:
RECORD_TYPE 8
RECORD_LEN 8
3 TAG – Transaction identifier.
4 The mobile station shall set this field to the identifier for this
5 transaction.
6 CH_IND – Channel indicator.
7 The mobile station shall set this field as shown in Table

8 2.7.2.3.2.32-1, to request physical resources.
2-635
3GPP2 C.S0005-A v6.0

(binary)
000 No additional channels requested.
011 Reserved.
100 Continuous Reverse Pilot Channel.
101 Fundamental Channel and

Continuous Reverse Pilot Channel.
110 Reserved.
111 Reserved.
4 If the service instance provides a service reference identifier,

5 the mobile station shall set this field to the service reference
6 identifier specified by the service instance. If the service
7 instance does not provide a service reference identifier, the
8 mobile station shall set this field to the smallest unused
9 service reference identifier value between 1 and 6 (inclusive).
10 GLOBAL-
11 _EMERGENCY_CALL – Global emergency call indicator.
12 The mobile station shall set this field to ‘1’, if the mobile
13 station recognizes that this is an emergency call; otherwise,

16 If the GLOBAL_EMERGENCY_CALL field is set to ‘0’, the
17 mobile station shall omit this field; otherwise, the mobile
18 station shall include this field and shall set it as follows:

2-636
3GPP2 C.S0005-A v6.0

9 the base station.
11 indicator.
12 If ENC_INFO_INCL is set to ‘1’, the mobile station shall
15 field to ‘1’ to request user information encryption, and to ‘0’ to
16 request no user information encryption.
17 UI_ENCRYPT_SUP – User information Encryption supported indicator.
18 If ENC_INFO_INCL is set to ‘1’, the mobile station shall
21 field to indicate the supported user information encryption
22 algorithms.
24 9.
30 ‘0000000’.
31 SERVICE_OPTION – Requested service option for this origination.
32 The mobile station shall set this field to the value specified in
33 [30], corresponding to the requested service option.
34 MORE_SO_INFO_INCL – More service option information included.
35 If MAX_NUM_ALT_SOs is equal to ‘000’, the mobile station

36 shall set this field to ‘0; otherwise, the mobile station shall set
38 If any alternate service option number or/and service option

39 bitmap is to be included in this message, the mobile station
40 shall set this field to ‘1’, otherwise, the mobile station shall set
41 this field to ‘0’. In other words, MORE_SO_INFO_INCL is set to
42 ‘1’, if NUM_ALT_SO is included and not set to ‘000’ or/and
43 SO_BITAMP_IND is included and not set to ‘00’.
2-637
3GPP2 C.S0005-A v6.0
2 If MORE_SO_INFO_INCL is set to ‘0’, the mobile station shall

4 to the number of supported alternative service options which
5 either have no service option group number assigned or do not
6 belong to the same service option group whose bitmap is
7 include in the message.
8 The mobile station shall include NUM_ALT_SO occurrences of the following field:
11 [30], corresponding to the alternative service option supported
12 by the mobile station. These alternate service options are
13 either have not service option group number assigned or do
14 not belong to the same service option group whose bitmap is
15 included in this message.
16 SO_BITMAP_IND – SO bitmap indicator.

17 If MORE_SO_INFO_INCL is set to ‘0’, the mobile station shall
19 field and set it as defined in Table 2.7.1.3.2.4-10.
20 SO_GROUP_NUM – Service option group number.
21 If the field SO_BITMAP_IND is included and not set to ‘00’, the
22 mobile station shall include this field and set this field to the
23 service option group number of which the bitmap is to be
24 included; otherwise, the mobile station shall omit this field.
25 SO_BITMAP – Service option bitmap.
26 If the field SO_BITMAP_IND is included and not set to ‘00’, the
27 mobile station shall include the bitmap of size 4 ×
28 SO_BITMAP_IND bits of the service option group number
29 (SO_GROUP_NUM); otherwise, the mobile station shall omit
30 this field;
32 than (4 × SO_BITMAP_IND) service options defined for the
33 service option group, the mobile station shall include the
34 bitmap containing the least significant bits (4 ×
35 SO_BITMAP_IND) of the service option group.
36 The mobile station shall set abit in this bitmap to ‘1’, if the
37 mobile station is capable of supporting the SO for which this
38 bit represents; otherwise, the mobile station shall set a bit in
39 this bitmap to ‘0’.
40 DRS – Data ready to send indicator.
2-638
3GPP2 C.S0005-A v6.0
1 The mobile station shall set this field to ‘1’ if it is requesting a

2 packet data service option and it has data to send; otherwise,
4 PREV_SID_INCL - Previous System Identification (SID) included indicator.

6 station determines that the SID has been changed after a
7 packet data dormant handoff and the PREV_SID field is
10 PREV_SID - Previous System Identification.
11 If PREV_SID_INCL is set to ‘0’, the mobile station shall omit
13 and set it as follows:
14 If the mobile station determines SID has been changed after a
16 field to the previous SID.
17 PREV_NID_INCL - Previous Network Identification (NID) included indicator.
19 station determines that NID has been changed after a packet
20 data dormant handoff and the PREV_NID field is included in
22 to ‘0’.
23 PREV_NID - Previous Network Identification.
24 If PREV_NID_INCL is set to ‘0’, the mobile station shall omit
27 If the mobile station determines NID has been changed after a
29 field to the previous NID.
30 PREV_PZID_INCL - Previous Packet Zone ID (PZID) included indicator.
32 station determines that the Packet Zone ID has been changed
33 after a packet data dormant handoff and the PREV_PZID field
36 PREV_PZID - Previous Packet Zone ID.
37 If PREV_PZID_INCL is set to ‘0’, the mobile station shall omit
40 If the mobile station determines PZID has been changed after
41 a packet data dormant handoff, the mobile station shall set
42 this field to the previous PZID.
43 DIALED_DIGS_INCL – Dialed digits included indicator.
2-639
3GPP2 C.S0005-A v6.0
1 The mobile station shall set this field to ‘1’ if the dialed digits
2 related fields are included in this message; otherwise, the
5 If the DIALED_DIGS_INCL field is set to ‘0’, the mobile station

8 This field indicates whether the dialed digits are 4-bit DTMF
9 codes or 8-bit ASCII codes using a specified numbering plan.

15 If the DIALED_DIGS_INCL field is set to ‘0’ or if the

16 DIGIT_MODE field is set to ‘0’, the mobile station shall omit
18 and shall set it as follows:
19 The mobile station shall set this field to the NUMBER_TYPE

21 of the number as defined in [7], Section 4.5.9.
23 If the DIALED_DIGS_INCL field is set to ‘0’ or if the

24 DIGIT_MODE field is set to ‘0’, the mobile station shall omit
26 and shall set it as follows:
27 The mobile station shall set this field to the NUMBER_PLAN

29 requested numbering plan as defined in [7], Section 4.5.9.
31 If the DIALED_DIGS_INCL field is set to ‘0’, the mobile station

2-640
3GPP2 C.S0005-A v6.0
1 The mobile station shall include NUM_FIELDS occurrences of the following field:

4 set each occurrence of this field to the code value shown in
5 Table 2.7.1.3.2.4-4 corresponding to the dialed digit. If the
10 NUM_RECS – Number of records.

12 information records included with this message.
13
14 The mobile station shall include NUM_RECS occurrences of the following three-field record.
17 shown in Table 2.7.4-1.
18 The mobile station shall not include the record type for QoS
19 Parameters information record if MOB_QOSs is equal to ‘0’.
22 in the type-specific fields included in this record.
24 The mobile station shall include type-specific fields as

2-641
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.33 Extended Flash With Information Message
2 MSG_TAG: EFWIM
Field Length (bits)
CON_REF_INCL 1
CON_REF 0 or 8
NUM_REC 4
NUM_REC occurrences of the following three-field record:
RECORD_TYPE 8
RECORD_LEN 8
10 If the CON_REF_INCL field is set to ‘0’, the mobile station

12 include this field and shall set it to the value of the connection
13 reference assigned to the service option connection of the call,
14 to which this message corresponds.
15 NUM_REC – Number of records.

18 The mobile station shall include NUM_REC occurrence of the following three-field record:
2-642
3GPP2 C.S0005-A v6.0

2-643
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.34 Extended Pilot Strength Measurement Message
2 MSG_TAG: EPSMM
Field Length (bits)
REF_PN 9
PILOT_STRENGTH 6
KEEP 1
REF_PILOT_REC_INCL 1
REF_PILOT_REC_TYPE 0 or 3
REF_RECORD_LEN 0 or 3
Type-specific fields 0 or 8 ×
REF_RECORD_LEN
SF_RX_PWR 5
NUM_PILOTS 4
PILOT_PN_PHASE 15
PILOT_STRENGTH 6
KEEP 1
PILOT_REC_INCL 1
RECORD_LEN 0 or 3

9 of 64 PN chips.
12 -2 × 10 log10 PS,
2-644
3GPP2 C.S0005-A v6.0

3 specified in 2.6.6.2.2. If this value (-2 × 10 log10 PS) is less
5 this value is greater than ‘111111’, the mobile station shall set
10 (see 2.1.5 of [2]) has expired, the mobile station shall set this
12 ‘1’.
13 REF_PILOT_REC_INCL - Reference pilot information included indicator.
14 The mobile station shall set this field to ‘1’ if additional
15 reference pilot information listed in the
16 REF_PILOT_REC_TYPE and REF_RECORD_LEN fields are
17 included. The mobile station shall set this field to ‘0’ if the
18 corresponding pilot is the common pilot and there is no
20 REF_PILOT_REC_TYPE - Reference pilot record type.
21 If REF_PILOT_REC_INCL is set to ‘1’, the mobile station shall
22 set this field to the REF_PILOT_REC_TYPE value shown in
23 Table 2.7.2.3.2.34-1 corresponding to the type of Pilot Record
24 specified by this record.
25
26 Table 2.7.2.3.2.34-1. Pilot Record Types
REF_PILOT_REC_TYPE
Description PILOT_REC_TYPE
(binary)
Auxiliary Pilot 000

All other REF_PILOT_REC_TYPE or PILOT_REC_TYPE values are
reserved
27

29 omit this field.
30 REF_RECORD_LEN - Reference pilot record length.
32 set this field to the number of octets in the type-specific fields
33 of this pilot record.
35 omit this field.
2-645
3GPP2 C.S0005-A v6.0

2 include type-specific fields based on the
3 REF_PILOT_REC_TYPE of this pilot record.
5 omit this field.
7 If REF_PILOT_REC_TYPE is equal to ‘000’, the mobile station shall include the following
8 fields:
Field Length (bits)
QOF 2
WALSH_LENGTH 3
PILOT_WALSH (WALSH_LENGTH +
6)
10
11 QOF - Quasi-orthogonal function index.

12 The mobile station shall set this field to the index of the
13 Quasi-orthogonal function of the corresponding Auxiliary
14 Pilot.
15 WALSH_LENGTH - Length of the Walsh code for the reference pilot.
16 The mobile station shall set this field to the WALSH_LENGTH
19 Auxiliary Pilot.
20 Table 2.7.2.3.2.34-2. Walsh Code Length
Length of the Walsh Code

WALSH_LENGTH (binary)
64 ‘000’
128 ‘001’
256 ‘010’
512 ‘011’
Reserved ‘100’ – ‘111’
21
22 PILOT_WALSH - Walsh code for the Auxiliary Pilot used by the mobile station
23 to derive its time reference.
24 The mobile station shall set this field to the Walsh code
2-646
3GPP2 C.S0005-A v6.0
1 RESERVED - Reserved bits.

5 SF_RX_PWR – The received power spectral density of the Serving Frequency.

7  (10 × log10(spec_density) + 120) / 2 
8 where spec_density is the mobile station received power

9 spectral density of the Serving Frequency, in mW/1.23MHz,
10 averaged over the last N12m frames (see 2.6.6.2.5.1).
11 If this value is less than 0, the mobile station shall set this
12 field to ‘00000’.
15 being reported other than the reference pilot.
16 The mobile station shall include NUM_PILOTS occurrences of the following record: one
17 occurrence for each pilot in the Active Set, for each pilot in the Candidate Set whose
18 strength exceeds T_ADD, and for each pilot in the Candidate Set whose strength satisfies
19 the following inequality:
SOFT_SLOPE s ADD_INTERCEPTs
20 10 × log 10 PS > × 10 × log 10 ∑ PS i +
8 i∈A 2
21 where the summation is performed over all pilots currently in the Active Set. The mobile
22 station shall not include these fields for the pilot identified by the REF_PN field.
23 The mobile station shall order any occurrences of the following record which correspond to
24 pilots in the Active Set such that they occur before any occurrences of the following record
25 which correspond to pilots in the Candidate Set.
32 -2 × 10 log10 PS,
37 ‘111111’.
2-647
3GPP2 C.S0005-A v6.0

11 PILOT_REC_TYPE - Reference pilot record type.
12 If PILOT_REC_INCL is set to ‘1’, the mobile station shall set
13 this field to the PILOT_REC_TYPE value shown in Table
14 2.7.2.3.2.343-1 corresponding to the type of Pilot Record
17 this field.
19 If PILOT_REC_INCL is set to ‘1’, the mobile station shall set
20 this field to the number of octets in the type-specific fields of
21 this pilot record.
23 this field.
25 If PILOT_REC_INCL is set to ‘1’, the mobile station shall
26 include type-specific fields based on the PILOT_REC_TYPE of
27 this pilot record as described in 3.7.6.1.
29 this field.
30
2-648
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.35 Extended Handoff Completion Message
2 MSG_TAG: EHOCM
Field Length (bits)
LAST_HDM_SEQ 2
NUM_PILOTS 4
PILOT_PN 9
PILOT_REC_INCL 1
RECORD_LEN 0 or 3
5 LAST_HDM_SEQ – Extended Handoff Direction Message, General Handoff

7 sequence number.
9 HDM_SEQ field from the Extended Handoff Direction Message,
10 General Handoff Direction Message, or the Universal Handoff
14 in the current Active Set.
15 The mobile station shall include NUM_PILOTS occurrences of the following record: one
16 occurrence for each pilot in the Active Set. If the Active Set contains more than one pilot,
17 the mobile station shall include the pilot information in the same order as in the Extended
18 Handoff Direction Message, the General Handoff Direction Message, or the Universal Handoff
20 PILOT_PN - Pilot PN sequence offset.
21 The mobile station shall set this field to the pilot PN sequence
22 offset, relative to the zero offset pilot PN sequence in units of
23 64 PN chips, for this pilot.
30 PILOT_REC_TYPE - Reference pilot record type.
2-649
3GPP2 C.S0005-A v6.0

5 record.
10 record.
15 record as described in 2.7.2.3.2.34.
16
17
2-650
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.36 Security Mode Request Message
2 MSG_TAG: SMRM
UI_ENC_INCL 1
NUM_RECS 0 or 3
NUM_RECS + 1 occurrences of the following two field record
CON_REF 0 or 8
SIG_ENC_INCL 1
ENC_SEQ_H_INCL 1
ENC_SEQ_H 0 or 24
5 UI_ENC_INCL – User information encryption fields included.

6 The mobile station shall set this field to ‘1’ if the user
7 information encryption related fields are included in this
9 ‘0’.
14 indicate the supported user information encryption
15 algorithms.
2-651
3GPP2 C.S0005-A v6.0

2 9.
8 ‘0000000’
9 NUM_REC – Number of user information encryption records.
13 number of user information encryption records included in
14 this message minus 1.
15 The mobile station shall include NUM_REC + 1 occurrences of the following two field record
16 CON_REF – Connection reference corresponding to the service instance
17 requesting for encryption.
21 the connection reference of the service option connection
22 corresponding to this user information encryption request
23 record.
25 indicator.
26 The mobile station shall set this field to ‘1’ to request user
27 information encryption for the user information corresponding
28 to the service option connection identified by CON_REF;
30 SIG_ENC_INCL – Signaling encryption fields included.
31 The mobile station shall set this field to ‘1’ if the following two
32 fields related to signaling encryption fields are included in this
33 message. Otherwise, the mobile station shall set this field to
34 ‘0’.
38 field. If this field is included, the mobile shall set this field to
39 indicate the supported signaling encryption algorithms
2-652
3GPP2 C.S0005-A v6.0

2 5.
11 ‘000000’.
13 indicator.
16 field. If included the mobile station shall set this field to ‘1’ to
17 request signaling encryption to be turned on for signaling
18 messages sent on f-dsch, and r-dsch, f-csch, and r-csch, and
19 to ‘0’ to request signaling encryption to be turned off for
20 signaling messages sent on f-dsch ,and r-dsch, f-csch, and r-
21 csch.
22 ENC_SEQ_H_INCL – The 24 MSB of the EXT_ENC_SEQ included.
23 The mobile station shall set this field to ‘1’ if ENC_SEQ_H is
27 If ENC_SEQ_H_INCL is set to ‘1’, the mobile station shall
30 field to the 24 most significant bits of the EXT_ENC_SEQ to be
31 used as the initial value of crypto sync for both forward and
32 reverse link encryptions.
39
40
2-653
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.37 Call Cancel Message
2 MSG_TAG: CLCM
TAG 4

6 The mobile station shall set this field to the TAG value in the
7 Enhanced Origination Message sent to originate this call.
2-654
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.38 Device Information Message
2 MSG_TAG: DIM
Field Length (bits)
WLL_DEVICE_TYPE 3
NUM_INFO_RECORDS 5
RECORD_TYPE 8
RECORD_LEN 8

11 information records which are included.
2-655
3GPP2 C.S0005-A v6.0
1 2.7.2.3.2.39 Base Station Status Request Message
2 MSG_TAG: BSSREQM
Field Length (bits)
QUAL_INFO_TYPE 8
QUAL_INFO_LEN 3
NUM_RECORD 4
NUM_RECORD occurrences of the following variable length
record:
RECORD_TYPE 8
RECORD_LENGTH 8
Record type specific fields variable
RESERVED 0-7 (as required)
3 QUAL_INFO_TYPE - Qualification information type.

5 Table 3.7.2.3.2.15-1 to show the inclusion of qualification
6 information in the type-specific fields.
7 QUAL_INFO_LEN - Qualification information length.
9 included in the type-specific fields of the qualification
10 information.
11 Type-specific fields - Type-specific fields.
13 information according to the QUAL_INFO_TYPE field.
14 If QUAL_INFO_TYPE is equal to ‘00000000’, the type-specific
15 fields are omitted.
16 If QUAL_INFO_TYPE is equal to ‘00000001’, the mobile station
17 shall use the following fixed-length format for the type-specific
18 fields:
Type-specific Field Length (bits)
BAND_CLASS 5
RESERVED 3
19
20 If QUAL_INFO_TYPE is equal to ‘00000010’, the mobile station

22 fields:
2-656
3GPP2 C.S0005-A v6.0
BAND_CLASS 5
OP_MODE 8
RESERVED 3

3 The mobile station shall set this field to the CDMA band class,
4 as specified in [30].
5 OP_MODE - Operating mode.
6 The mobile station shall set this field as shown in
7 Table 3.7.2.3.2.15-3 to specify the operating mode
8 qualification information.
11 NUM_RECORD - Number of requested record fields in this message.
13 occurrences of RECORD_TYPE field in this message.
14 The mobile station shall include NUM_RECORD occurrences of the following variable-length
15 record, one for each information record that is requested:
16 RECORD_TYPE - Information record type.
18 shown in Table 2.7.2.3.2.39-1 corresponding to the
19 information record requested.
20 Table 2.7.2.3.2.39-1. Base Station Status Request Information Record Types
Information Record Requested Record Type

Pilot Information 00000000
Reserved 00000001-
11111111
21 RECORD_LENGTH - Information record length.
22 The mobile station shall set this field to the length, in octets,
23 of the record type specific fields included in this record.
24 Record type specific

25 fields - Record type specific fields
26 The mobile station shall set this field to the type specific fields
27 corresponding to this record type.
28 If the RECORD_TYPE field is set to ‘00000000’, the mobile
2-657
3GPP2 C.S0005-A v6.0
1 station shall set the record type specific field as follows:
Field Length (bits)
NUM_PILOTS 4
SID_NID_REQ 1
NUM_PILOTS occurrences of the following one field record
PILOT_PN 9
2 NUM_PILOTS - Number of Pilots reported.
4 whose information is requested in this message.
5 The mobile station shall set this field to a number equal or

6 greater than one.
7 SID_NID_REQ - SID, NID information requested indicator.
8 The mobile station shall set this field to ‘1’ if it also requests
9 the SID and NID information for these pilots; otherwise, the
11 The mobile station shall include NUM_PILOTS occurrences of the following one-field
12 record:
13 PILOT_PN - Pilot PN sequence offset index.
14 The mobile station shall set this field to the pilot PN sequence
15 offset for the base station, in units of 64 PN chips, whose Base
16 Station identification number information is being requested.
17
19 The mobile station shall add reserved bits as needed in order

20 to make the length of the record equal to an integer number of
21 octets. The mobile station shall set these bits to ‘0’.
22
2-658
3GPP2 C.S0005-A v6.0
1 2.7.3 Orders
2 Order Messages are sent by the mobile station on the r-csch and on the r-dsch. The
3 general PDU format used on the r-csch is defined in 2.7.1.3.2.2, and the general PDU
4 format used on the r-dsch is defined in 2.7.2.3.2.1. There are many specific types of Order
5 Messages, as shown in Table 2.7.3-1.
6 The mobile station may send on the r-csch any type of order shown in Table 2.7.3-1 with a
7 ‘Y’ in the first column, but shall not send on the r-csch any type of order with an ‘N’ in the
8 first column. The mobile station may send on the r-dsch any type of order shown in
9 Table 2.7.3-1 with a ‘Y’ in the second column, but shall not send on the r-dsch any type of
10 order with an ‘N’ in the second column. The mobile station shall be capable of sending all
11 types of orders shown in Table 2.7.3-1 with a ‘Y’ in the sixth column.
12 An order consists of a 6-bit order code and zero or more order-specific fields. The mobile
13 station shall set the ORDER field in the Order Message to the order code shown in Table
14 2.7.3-1 corresponding to the type of order being sent.
15 If the order qualification code in the fourth column of Table 2.7.3-1 is ‘00000000’ and there
16 are no other additional fields as shown by an ‘N’ in the fifth column, the mobile station
17 shall include no order qualification code or other order-specific fields in the Order Message.
18 The order qualification code of such a message is implicitly ‘00000000’.
19 If the order qualification code is not ‘00000000’ and there are no other additional fields as
20 shown in Table 2.7.3-1 by an ‘N’ in the fifth column, the mobile station shall include the
21 order qualification code as the only order-specific field in the Order Message.
22 If there are other additional fields as shown in Table 2.7.3-1 by a ‘Y’ in the fifth column, the
23 mobile station shall include order-specific fields as specified in the corresponding
24 subsection of this section.
2-659
3GPP2 C.S0005-A v6.0
2 (Part 1 of 4)
Order Order More

r-csch r-dsch Fields
Order Order Code, Qualification Support
ORDER Code, ORDQ other Req’d Name/Function
(binary) (binary) than
ORDQ
Y Y 000010 00000000 Y Y Base Station Challenge Order

(see 2.7.3.1)
Y Y 000011 00000000 N Y SSD Update Confirmation
Order
Y Y 000011 00000001 N Y SSD Update Rejection Order
N Y 000101 0000nnnn N Y Parameter Update
Confirmation Order (where
‘nnnn’ is the Request
Number)
N Y 001011 00000000 N N Request Wide Analog Service
Order
N Y 001011 00000001 N N Request Narrow Analog
Service Order
N Y 001011 00000010 N N Request Analog Service Order
Y Y 010000 00000000 N Y Mobile Station
Acknowledgment Order (see
[4])
N Y 010011 00000000 Y N Service Option Request Order
(Band Class 0 only)
(see 2.7.3.2)
N Y 010100 00000000 Y Y Service Option Response
Order (Band Class 0 only)
(see 2.7.3.3)
Y Y 010101 00000000 N Y Release Order (normal
release)
Y Y 010101 00000001 N Y Release Order (with power-
down indication)
N Y 010101 00000010 N Y Release Order (with service
inactive indication)
N Y 010111 00000000 N N Long Code Transition Request
Order (request public)
N Y 010111 00000001 N N Long Code Transition Request
Order (request private)
2-660
3GPP2 C.S0005-A v6.0
2 (Part 2 of 4)
r-dsch Order Order More

r-csch Order Code, Qualification Fields Support
Order ORDER Code, ORDQ other Req’d Name/Function
(binary) (binary) than
ORDQ
N Y 010111 00000010 N Y Long Code Transition

Response Order (use public)
N Y 010111 00000011 N N Long Code Transition
Response Order (use
private)
N Y 011000 00000000 N Y Connect Order
N Y 011001 0000nnnn N Y Continuous DTMF Tone
Order (where ‘nnnn’ is the
tone per Table 2.7.1.3.2.4-
4).
N Y 011001 11111111 N Y Continuous DTMF Tone
Order (Stop continuous
DTMF tone)
N Y 011101 nnnnnnnn N Y Service Option Control Order
(Band Class 0 only)
(the specific control is
designated by ‘nnnnnnnn’
as determined by each
service option)
Y Y 011110 nnnnnnnn N N Local Control Response
Order (specific response as
designated by ‘nnnnnnnn’
as determined by each
system)
Y Y 011111 00000001 Y Y Mobile Station Reject Order
(unspecified reason; see
2.7.3.4)
(message not accepted in
this state; see 2.7.3.4)
(message structure not
acceptable; see 2.7.3.4)
2-661
3GPP2 C.S0005-A v6.0
2 (Part 3 of 4)
More
r-csch r-dsch Order Order Fields
other Name/Function
ORDER Code, ORDQ Req’d
than
(binary) (binary) ORDQ

(message field not in valid
range; see 2.7.3.4)
N Y 011111 00000101 Y Y Mobile Station Reject Order
(message type or order code
not understood; see
2.7.3.4)
(message requires a
capability that is not
supported by the mobile
station; see 2.7.3.4)
(message cannot be
handled by the current
mobile station
configuration; see 2.7.3.4)
(response message would
exceed allowable length;
see 2.7.3.4)
(information record is not
supported for the specified
band class and operating
mode; see 2.7.3.4)
(search set not specified;
see 2.6.6.2.5.1)
(invalid search request; see
2.6.6.2.5.1)
2-662
3GPP2 C.S0005-A v6.0
2 (Part 4 of 4)
More
r-csch r-dsch Order Order Fields
other Name/Function
ORDER Code, ORDQ Req’d
than
(binary) (binary) ORDQ

(invalid Frequency
Assignment; see
2.6.6.2.5.1)
(search period too short;
see 2.6.6.2.5.1)
Y N 011111 00001110 NY Y Mobile Station Reject Order
(RC does not match with
the value in the field
DEFAULT_CONFIG; see
2.6.3.3 and 2.6.3.5)
Y N 011111 00001111 N Y Mobile Station Reject Order
(Encryption key with the
specified KEY_SEQ not
stored)
(call assignment not
accepted; see 2.7.3.4)
(no call control instance
present with the specified
identifier; see 2.7.3.4)
(a call control instance is
already present with the
specified identifier; see
2.7.3.4)
(TAG received does not
match any of the TAG
stored; see 2.7.3.4)
2-663
3GPP2 C.S0005-A v6.0
1 2.7.3.1 Base Station Challenge Order
ORDQ 8
RANDBS 32
4 ORDQ – Order qualification code.

6 RANDBS – Random challenge data.
8 2.3.12.1.5.
2-664
3GPP2 C.S0005-A v6.0
1 2.7.3.2 Service Option Request Order
ORDQ 8
SERVICE_OPTION 16

7 The mobile station shall set this field to the service option
8 code specified in [30], corresponding to the requested or
9 alternative service option.
2-665
3GPP2 C.S0005-A v6.0
1 2.7.3.3 Service Option Response Order
ORDQ 8
SERVICE_OPTION 16

7 The mobile station shall set this field to the service option
8 code specified in [30], corresponding to the accepted service
9 option, or to ‘0000000000000000’ to reject the proposed
10 service option. See 2.6.4.1.2.2.1.
2-666
3GPP2 C.S0005-A v6.0
1 2.7.3.4 Mobile Station Reject Order
2-667
3GPP2 C.S0005-A v6.0
ORDQ 8
REJECTED_TYPE 8
If the order is sent on the Access Channel or Enhanced
Access Channel and
REJECTED_TYPE is ‘00000111’,
or if the order is sent on the Reverse Traffic Channel and
the order-specific fields also include the following two fields:
RESERVED_1 2
REJECTED_ORDER 68
REJECTED_ORDQ 8
If the order is sent on the Reverse Traffic Channel and
the order-specific fields also include the following field:
REJECTED_PARAM_ID 16
If the order is sent on the Access Channel or Enhanced
Access Channel and
or if the order is sent on the Reverse Traffic Channel and
REJECTED_TYPE is ‘00000011’, ‘00101000’, or
REJECTED_TYPE is ‘00001110’, or ‘00101010’,
the order-specific fields also include the following field:
REJECTED_RECORD 8
If the ORDQ is ‘00010000’, ‘00010001’, or ‘00010010’, the
order-specific fields also include the following fields:
CON_REF 8
If the ORDQ is ‘00010011’, the order-specific fields also
include the following fields:
CON_REF 8
TAG 4
REJECTED_PDU_TYPE 0 or 2
2-668
3GPP2 C.S0005-A v6.0
1 The mobile station shall set this field to the ORDQ value
2 shown in Table 2.7.3-1 corresponding to the reason for
3 rejecting the message.
4 REJECTED_TYPE – Message type of rejected message.
6 MSG_TYPE field of the message being rejected.
7 If the MSG_TYPE field is not 8 bits, the mobile station shall
8 set the least significant bits of this field to the value of the
9 MSG_TYPE field and set all the remaining bits to ‘0’.
10 RESERVED_1 - Reserved bits.
12 REJECTED_ORDER – Order type of rejected message.

13 If the rejected message was an Order Message, the mobile
14 station shall set this field to the value of the ORDER field in
15 the rejected message.
16 Otherwise, the mobile station shall omit this field.
17 REJECTED_ORDQ – Order qualification code of rejected message.
18 If the rejected message was an Order Message including an
19 ORDQ field, the mobile station shall set this field to the value
20 of the ORDQ field in the rejected message. If the rejected
21 message was an Order Message not including an ORDQ field,
24 REJECTED_PARAM_ID – Parameter identification of the rejected parameter.
25 If the rejected message was a Set Parameters Message, the
26 mobile station shall set this field to the PARAMETER_ID of the
27 first parameter for which the requested operation could not be
28 completed.
30 REJECTED_RECORD – Record type of the rejected information record.
31 If the rejected message was a Feature Notification Message, an
32 Alert With Information Message, Extended Alert With
33 Information Message, Extended Flash With Information
34 Message, or a Flash With Information Message, the mobile
35 station shall set this field to the RECORD_TYPE field of the
36 first information record that could not be accepted.

40 connection reference of the service option connection
41 corresponding to the call.
2-669
3GPP2 C.S0005-A v6.0
1 The mobile station shall set this field to the transaction

2 identifier (received from the base station) of the call
3 assignment being rejected.
6 connection reference of the service option connection
7 corresponding to the call.
8 REJECTED_PDU_TYPE – PDU type of the rejected message.

11 to the REJECTED_PDU_TYPE code shown in Table 2.7.3.4-1
12 corresponding to the PDU type of the message being rejected.
13
14 Table 2.7.3.4-1. REJECTED_PDU_TYPE codes
REJECTED_PDU_ Description
TYPE (binary)
00 20 ms regular message
01 5 ms mini message
01 Reserved
11 Reserved

17 to make the total length of this record containing order-
18 specific fields equal to an integer number of octets. The
19 mobile station shall set these bits to ‘0’.
20
2-670
3GPP2 C.S0005-A v6.0
1 2.7.4 Information Records

2 On the r-csch, information records may be included in the Status Response Message, the
3 Extended Status Response Message, the Origination Message, and the Device Information
4 Message. On the r-dsch, information records may be included in the Origination
5 Continuation Message, the Enhanced Origination Message, the Flash With Information
6 Message, the Extended Flash With Information Message, the Service Request Message, the
7 Service Response Message, the Status Message, and the Status Response Message. Table
8 2.7.4-1 lists the information record type values that may be used with each message type.
9 The following sections describe the contents of each of the record types in detail.
10
11 Table 2.7.4-1. Information Record Types (Part 1 of 2)
Record r-csch r-dsch

Information Record Type Message
(binary) Type
Reserved 00000001 None - -
Reserved for Obsolete Identification 00000010
Keypad Facility 00000011 Flash N Y
Called Party Number 00000100 Flash N Y
Calling Party Number 00000101 Flash N Y
Origination N Y
Continuation
Reserved for Obsolete Identification 00000110 - - -
Call Mode 00000111 Status [1] N Y
Terminal Information 00001000 Status [1] Y Y
Roaming Information 00001001 Status [1] Y Y
Security Status 00001010 Status [1] N Y
Connected Number 00001011 Flash N Y
IMSI 00001100 Status [1] Y Y
ESN 00001101 Status [1] Y Y
Band Class Information 00001110 Status [2] Y Y
Power Class Information 00001111 Status [2] Y Y
Operating Mode Information 00010000 Status [2] Y Y
Service Option Information 00010001 Status [2] Y Y
Multiplex Option Information 00010010 Status [2] Y Y
Status [2] N Y
Service
Service Configuration Information 00010011 N Y
Request
Service
N Y
Response
2-671
3GPP2 C.S0005-A v6.0
Record r-csch r-dsch

Information Record Type Message
(binary) Type
Called Party Subaddress 00010100 Flash N Y

Origination N Y
Continuation
Calling Party Subaddress 00010101 Flash N Y
Origination N Y
Continuation
Connected Subaddress 00010110 Flash N Y
Power Control Information 00010111 Status [2] Y Y
IMSI_M 00011000 Status [2] Y Y
IMSI_T 00011001 Status [2] Y Y
Capability Information 00011010 Status [2] Y Y
Channel Configuration Capability 00011011 Status [2] Y Y
Information
Extended Multiplex Option 00011100 Status [2] Y Y
Information
Reserved for Obsolete Identification 00011101 - - -
Geo-location Information 00011110 Status [2] Y Y
Band Subclass Information 00011111 Status [2] Y Y
Global Emergency Call 00100000 Flash N Y
Hook Status 00100001 DIM Y Y
Status [2] Y Y
QoS Parameters 00100010 Origination N Y
Continuation
Enhanced N Y
Origination
Encryption Capability 00100011 Status [2] Y Y
Extended Record Type — 11111110 Country-Specific

International
All other record type values are reserved.
“Flash” refers to either the Flash With Information Message or the Extended Flash With
Information Message.
“DIM” refers to the Device Information Message.
[1] This information record may be included in a Status Message, a Status Response
Message, or an Extended Status Response Message.
[2] This information record may be included in a Status Response Message or an
Extended Status Response Message.
2-672
3GPP2 C.S0005-A v6.0
1 2.7.4.1 Reserved
2-673
3GPP2 C.S0005-A v6.0
1 2.7.4.2 Keypad Facility

2 This information record can be included in a Flash With Information Message and allows the
3 user to send characters entered via a keyboard or other such terminal.
Type-Specific Field Length (bits)

CHARi 8
8 for each character entered. The mobile station shall set each
9 occurrence of this field to the ASCII representation
10 corresponding to the character entered, as specified in [9],
11 with the most significant bit set to ‘0’.
2-674
3GPP2 C.S0005-A v6.0
1 2.7.4.3 Called Party Number
2 This information record identifies the called party's number.

NUMBER_TYPE 3
NUMBER_PLAN 4
Zero or more occurrences of the following field:
CHARi 8
RESERVED 1

7 of the called number, as defined in [7], Section 4.5.9.
11 numbering plan used for the called number, as defined in [7],
12 Section 4.5.9.
14 The mobile stations shall include one occurrence of this field
15 for each character in the called number. The mobile station
16 shall set each occurrence of this field to the ASCII
17 representation corresponding to the character, as specified in
18 [9], with the most significant bit set to ‘0’.
19 RESERVED – Reserved bit.
2-675
3GPP2 C.S0005-A v6.0
1 2.7.4.4 Calling Party Number

2 This information record can be included in a Flash With Information Message and identifies
3 the calling party's number.
NUMBER_TYPE 3
NUMBER_PLAN 4
PI 2
SI 2
CHARi 8
RESERVED 5

8 of the calling number, as defined in [7], Section 4.5.9.
12 numbering plan used for the calling number, as defined in [7],
13 Section 4.5.9.
14 PI – Presentation indicator.
15 This field indicates whether or not the calling number should
16 be displayed.
17 The mobile station shall set this field to the PI value shown in
18 Table 2.7.4.4-1 corresponding to the presentation indicator,
19 as defined in [7], Section 4.5.9.
20
21 Table 2.7.4.4-1. Presentation Indicators
Description PI (binary)
Presentation allowed 00
Presentation restricted 01
Number not available 10
Reserved 11
22
2-676
3GPP2 C.S0005-A v6.0
1 SI – Screening indicator.
2 This field indicates how the calling number was screened.
3 The mobile station shall set this field to the SI value shown in
4 Table 2.7.4.4-2 corresponding to the screening indicator
5 value, as defined in [7], Section 4.5.9.
7 Table 2.7.4.4-2. Screening Indicators
Description SI (binary)
User-provided, not screened 00

User-provided, verified and passed 01
User-provided, verified and failed 10
Network-provided 11
10 The mobile stations shall include one occurrence of this field
11 for each character in the calling number. The mobile station
2-677
3GPP2 C.S0005-A v6.0
1 2.7.4.5 Reserved
2-678
3GPP2 C.S0005-A v6.0
1 2.7.4.6 Call Mode

2 This information record can be included in a Status Message or a Status Response Message
3 to return the mobile station's preferred call mode and call-related information.
4 If P_REV_IN_USEs is equal to or greater than seven, this information record will not be
5 requested by the base station (see 3.7.2.3.2.15 & 3.7.4.4).
ORIG_MODE 1
PRI_SERVICE 16
SEC_SERVICE 16
RESERVED 7
8 ORIG_MODE – Origination mode indicator.

9 If the current call is a mobile-originated call, the mobile
10 station shall set this field to ‘0’. If the current call is a mobile-
11 terminated call, the mobile station shall set this field to ‘1’.
12 PRI_SERVICE – Primary service option.
14 [30], corresponding to the current primary service option. If
15 no primary service option is active, the mobile station shall set
16 this field to ‘0000000000000000’.
17 SEC_SERVICE – Secondary service option.
19 [30], corresponding to the current secondary service option. If
20 no secondary service option is active, the mobile station shall
21 set this field to ‘0000000000000000’.
2-679
3GPP2 C.S0005-A v6.0
1 2.7.4.7 Terminal Information

2 This information record can be included in a Status Message, a Status Response Message,
3 or an Extended Status Response Message to return configuration information about the
4 mobile station.
MOB_P_REV 8
MOB_MFG_CODE 8
MOB_MODEL 8
MOB_FIRM_REV 16
SCM 8
LOCAL_CTRL 1
SLOT_CYCLE_INDEX 3
SERVICE_OPTION 16
RESERVED 4

7 If the status request does not specify a band class, the mobile
8 station shall set this field to ‘00000111’; otherwise, the
9 mobile station shall set this field to the MOB_P_REV
10 associated with the requested band class and operating mode.
11 MOB_MFG_CODE – Manufacturer code.
12 This field identifies the manufacturer of the mobile station.
13 The mobile station shall set this field to the manufacturer
14 code assigned to its manufacturer.
15 MOB_MODEL – Model number.
16 This number is assigned by the manufacturer for a particular
17 model.
18 The mobile station shall set this field to the model number
19 assigned by the manufacturer for this mobile station.
20 MOB_FIRM_REV – Firmware revision number.
21 This number is assigned by the manufacturer for a particular
22 firmware version.
23 The mobile station shall set this field to the revision number
24 assigned by the manufacturer for the firmware version
25 running in this mobile station.
2-680
3GPP2 C.S0005-A v6.0

2 The mobile station shall set this field to its station class mark.
3 See 2.3.3.
4 LOCAL_CTRL – Local control indicator.
5 If local control is enabled, the mobile station shall set this
6 field to ‘1’. If local control is disabled, the mobile station shall
7 set this field to ‘0’. See [6].
9 If the requested operating mode is CDMA and the mobile
10 station is configured for slotted mode operation, the mobile
11 station shall set this field to the preferred slot cycle index,
12 SLOT_CYCLE_INDEXp (see 2.6.2.1.1); otherwise, the mobile
14 SERVICE_OPTION – Supported service option.
15 If the requested operating mode is CDMA, the mobile station
16 shall include one occurrence of this field for each service
17 option supported by the mobile station (see [30]); otherwise,
18 the mobile station shall include one occurrence of this field
19 with the value set to ‘0000000000000000’.
2-681
3GPP2 C.S0005-A v6.0
1 2.7.4.8 Roaming Information

3 or an Extended Status Response Message to return roaming information about the mobile
4 station.
ACCOLC 4
MOB_TERM_HOME 1
MOB_TERM_FOR_SID 1
MOB_TERM_FOR_NID 1
SID 15
NID 16
RESERVED 0 - 7 (as needed)
6 ACCOLC – Overload class.

7 The mobile station shall set this field to the access overload
8 class assigned to the mobile station.
9 MOB_TERM_HOME – Home (non-roaming) registration enable indicator.
10 If the mobile station is configured to receive mobile station
11 terminated calls when not roaming, the mobile station shall
12 set this field to ‘1’; otherwise, the mobile station shall set this
13 field to ‘0’. See 2.6.5.3.
14 MOB_TERM_FOR_SID – Foreign SID roaming registration enable indicator.
16 terminated calls when it is a foreign SID roamer, the mobile
17 station shall set this field to ‘1’; otherwise, the mobile station
18 shall set this field to ‘0’. See 2.6.5.3.
19 MOB_TERM_FOR_NID – Foreign NID roaming registration enable indicator.
21 terminated calls when it is a foreign NID roamer, the mobile
23 shall set this field to ‘0’. See 2.6.5.3.
24
2-682
3GPP2 C.S0005-A v6.0
1 The mobile station shall include one occurrence of the following two-field record for each
2 home (non-roaming) (SID, NID) pair (see 2.6.5.2):
3 SID – System identification.
4 The mobile station shall set this field to the SID value for this
5 (SID, NID) pair.
6 NID – Network identification.
7 The mobile station shall set this field to the NID value for this
8 (SID, NID) pair.
11 to make the length of the entire information record equal to an
12 integer number of octets. The mobile station shall set these
13 bits to ‘0’.
2-683
3GPP2 C.S0005-A v6.0
1 2.7.4.9 Security Status

2 This information record can be included in a Status Message or a Status Response Message
3 to return the authentication, encryption, and voice privacy modes of the mobile station.
AUTH_MODE 2
ENCRYPT_MODE 2
PRIVATE_LCM 1
RESERVED 3
6 AUTH_MODE – Authentication mode.

7 If the mobile station provided standard authentication
8 information at the initiation of this call, the mobile station
9 shall set this field to ‘01’; otherwise, the mobile station shall
10 set this field to ‘00’. All other values are reserved.
11 ENCRYPT_MODE – Message encryption mode.
13 Table 3.7.2.3.2.8-2 corresponding to the message encryption
14 mode currently in use for this call.
15 PRIVATE_LCM – Private long code mask indicator.
16 If the mobile station is using the private long code mask for
17 this call, the mobile station shall set this field to ‘1’. If the
18 mobile station is using the public long code mask for this call,
2-684
3GPP2 C.S0005-A v6.0
1 2.7.4.10 Connected Number

2 This information record can be included in a Flash With Information Message to identify the
3 responding party to a call.
NUMBER_TYPE 3
NUMBER_PLAN 4
PI 2
SI 2
CHARi 8
RESERVED 5

7 of the connected number as defined [7], Section 4.5.9.
11 numbering plan used for the connected number, as defined,
12 in [7], Section 4.5.9.
13 PI – Presentation indicator.
14 This field indicates whether or not the connected number
15 should be displayed. The mobile station shall set this field to
16 the PI value shown in Table 2.7.4.4-1 corresponding to the
17 presentation indicator, as defined in [7], Section 4.5.9.
18 SI – Screening indicator.
19 This field indicates how the connected number was screened.
20 The mobile station shall set this field to the SI value shown in
25 for each character in the connected number. The mobile
26 station shall set each occurrence of this field to the ASCII
2-685
3GPP2 C.S0005-A v6.0
1 2.7.4.11 IMSI
3 or an Extended Status Response Message to return the mobile station’s operational IMSI.
IMSI_CLASS 1
IMSI_ADDR_NUM 3
MCC_O 10
IMSI_O_11_12 7
IMSI_O_S 34
RESERVED 1
5 IMSI_CLASS – If IMSI_O is a class 0 IMSI, the mobile station shall set this
7 ‘1’.
8 IMSI_ADDR_NUM – Number of IMSI_O address digits.
9 If IMSI_O is a class 1 IMSI, the mobile station shall set this
10 field to four less than the number of digits in the NMSI;
12 MCC_O – Mobile Country Code of the operational IMSI.
13 The mobile station shall set this field to MCC_Os. (see 2.3.1).
14 IMSI_O_11_12 – The 11th and 12th digits of the operational IMSI.

15 The mobile station shall set this field to IMSI_O_11_12s.
16 (see 2.3.1).
17 IMSI_O_S – Last ten digits of the operational IMSI.
18 The mobile station shall set this field to IMSI_O_S. (see 2.3.1.)
2-686
3GPP2 C.S0005-A v6.0
1 2.7.4.12 ESN
3 or an Extended Status Response Message to return the mobile station ESN.
ESN 32
5 ESN – Mobile station electronic serial number.

6 The mobile station shall set this field to its electronic serial
7 number (see 2.3.2).
2-687
3GPP2 C.S0005-A v6.0
1 2.7.4.13 Band Class Information

2 This information record can be included in a Status Response Message, or an Extended
3 Status Response Message to return band class information about the mobile station.
BAND_CLASS_INFO 8 × RECORD_LEN
5 BAND_CLASS_INFO – Band class information.

6 This field indicates which band classes are supported by the
7 mobile station.
8 This field currently consists of the following subfields which
9 are included in the information record in the order shown:
10
Length
BAND_CLASS_0 1 800 MHz cellular band

BAND_CLASS_1 1 1.8 to 2.0 GHz PCS band
BAND_CLASS_2 1 872 to 960 MHz TACS band
BAND_CLASS_3 1 832 to 925 MHz JTACS
band
BAND_CLASS_4 1 1.75 to 1.87 GHz Korean
PCS band
BAND_CLASS_5 1 450 MHz NMT band
BAND_CLASS_6 1 2 GHz IMT-2000 band
BAND_CLASS_7 1 700 MHz band
BAND_CLASS_10 1 Secondary 800 MHz band
RESERVED 65 Reserved Bits
11

13 corresponding band class (see [2] and [30]) is supported by the
14 mobile station; otherwise, the mobile station shall set the
2-688
3GPP2 C.S0005-A v6.0
1 When more band classes are defined, the reserved bits will be
2 used for the new corresponding subfields. Sufficient octets
3 will be added to this field to accommodate the new subfields.
4 All the undefined bits in an additional octet will be reserved
5 bits.
6 The mobile station shall set all the reserved bits to ‘0’. If all
7 bits are set to ‘0’ in an octet and all succeeding octets, the
8 mobile station shall omit the octet and the succeeding octets.
2-689
3GPP2 C.S0005-A v6.0
1 2.7.4.14 Power Class Information

3 Status Response Message to return power class information about the mobile station.
MAX_EIRP 8
6 MAX_EIRP – Maximum effective isotropic radiated power (EIRP).

7 The mobile station shall set this field to the minimum EIRP at
8 maximum output (in dBW) for the mobile station plus 60 (see
9 [11]). When the mobile station output power is expressed in
10 ERP, it may be converted to EIRP by adding 2 dB to the ERP
11 value.2
2 For example, if a mobile station has a minimum ERP at maximum output of -4 dBW, then the
mobile station sets this field to 58.
2-690
3GPP2 C.S0005-A v6.0
1 2.7.4.15 Operating Mode Information

2 This information record can be included in a Status Response Message or an Extended
3 Status Response Message to return operating mode information about the mobile station.
OP_MODE_INFO 8 × RECORD_LEN
7 OP_MODE_INFO – Operating mode information.

8 This field indicates which operating modes are supported by
9 the mobile station in the band class for which information is
10 requested.
11 This field currently consists of the following subfields which
12 are included in the information record in the order shown in
13 Table 2.7.4.15-1 for P_REV_IN_USEs less than or equal to
14 three and in Table 2.7.4.15-2 for P_REV_IN_USEs greater
15 than three.
16
17 Table 2.7.4.15-1. OP_MODE for P_REV_IN_USEs Less Than or Equal

18 to Three
Length
OP_MODE0 1 CDMA mode in Band Class 1 and Band Class

4
OP_MODE1 1 CDMA mode in Band Class 0 and Band Class
3
OP_MODE2 1 Analog mode [6]
OP_MODE3 1 wide analog mode [22]
OP_MODE4 1 narrow analog mode [22]
RESERVED 3 –Reserved Bits
19
2-691
3GPP2 C.S0005-A v6.0
1 Table 2.7.4.15-2. OP_MODE for P_REV_IN_USEs Greater Than

2 Three
Standards
Length
OP_MODE0 1 CDMA mode [5]

OP_MODE1 1 CDMA mode3 [5]
OP_MODE2 1 Analog mode [65]
OP_MODE3 1 Wide analog mode [22]
OP_MODE4 1 Narrow analog mode [22]
OP_MODE5 1 DS-41 [32]
OP_MODE6 1 MC-MAP [31]
RESERVED 1 – –
4 The mobile station shall set each subfield to ‘1’, if the

5 corresponding operating mode is supported by the mobile
6 station; otherwise, the mobile station shall set the subfield to
7 ‘0’.
9 The mobile station shall set each bit in this field to ‘0’.
10 When more operating modes are defined, the reserved bits will
11 be used for the new corresponding subfields. Sufficient octets
12 will also be added to this field to accommodate the
13 corresponding new subfields. All the undefined bits in an
14 additional octet will be reserved bits.
15 If all bits are set to ‘0’ in an octet and all succeeding octets,
16 the mobile station shall omit the octet and the succeeding
17 octets.
3 The mobile station shall set OP_MODE1 as the same as OP_MODE0.
2-692
3GPP2 C.S0005-A v6.0
1 2.7.4.16 Service Option Information

3 Status Response Message to return service option information about the mobile station.

RESERVED 6
FORWARD_SUPPORT 1
REVERSE_SUPPORT 1
SERVICE_OPTION 16
6 The mobile station shall include one occurrence of the following record for each service
7 option supported:
10 FORWARD_SUPPORT – Support indicator for Forward Traffic Channel.
11 The mobile station shall set this field to ‘1’ if the service option
12 specified in the SERVICE_OPTION field is supported on the
13 Forward Traffic Channel.
14 REVERSE_SUPPORT – Support indicator for Reverse Traffic Channel.
15 The mobile station shall set this field to ‘1’ if the service option
16 specified in the SERVICE_OPTION field is supported on the
20 [30] for the service option supported.
21
2-693
3GPP2 C.S0005-A v6.0
1 2.7.4.17 Multiplex Option Information

3 Status Response Message to return multiplex option information about the mobile station.
4 The mobile station shall include at least one, and not more than six, instances of the record
5 within the type-specific field according to the following rules:
6 • Within the type-specific field, the mobile station may include one instance of a
7 record in which MULTIPLEX_OPTION is set to 1. If this instance is included, the
8 mobile station shall support Multiplex Option 1 for forward and reverse operation.
10 record in which MULTIPLEX_OPTION is set to 2. If this instance is included, the
11 mobile station shall support Multiplex Option 2 for forward and reverse operation.
13 record in which MULTIPLEX_OPTION is set to 3, 5, 7, 9, 11, 13, or 15 and with
14 FOR_NUM_BITSRATES set to ‘00000000’. If this instance is included, the mobile
15 station shall set MULTIPLEX_OPTION to the highest numbered multiplex option
16 from the set {3, 5, 7, 9, 11, 13, 15} which the mobile station supports for reverse
17 operation, and the mobile station shall support all multiplex options less than or
18 equal to MULTIPLEX_OPTION from that set for reverse operation.
21 FOR_NUM_BITSRATES set to ‘00000000’. If this instance is included, the mobile
23 from the set {4, 6, 8, 10, 12, 14, 16} which the mobile station supports for reverse
25 equal to MULTIPLEX_OPTION from that set for reverse operation.
28 REV_NUM_BITSRATES set to ‘00000000’. If this instance is included, the mobile
30 from the set {3, 5, 7, 9, 11, 13, 15} which the mobile station supports for forward
32 equal to MULTIPLEX_OPTION from that set for forward operation.
35 REV_NUM_BITSRATES set to ‘00000000’. If this instance is included, the mobile
37 from the set {4, 6, 8, 10, 12, 14, 16} which the mobile station supports for forward
39 equal to MULTIPLEX_OPTION from that set for forward operation.
40 • Within the type-specific field, the mobile station shall include at least one instance
41 of a record in which FOR_NUM_BITSRATES is set to a value other than ‘00000000’.
2-694
3GPP2 C.S0005-A v6.0
1 • Within the type-specific field, the mobile station shall include at least one instance
2 of a record in which REV_RATES is set to a value other than ‘00000000’.

MULTIPLEX_OPTION 16
FOR_NUM_BITS 8
REV_NUM_BITS 8
5 The mobile station shall include one occurrence of the following record for each specified
6 multiplex option according to the previously stated rules:
7 MULTIPLEX_OPTION – Supported multiplex option.
8 The mobile station shall set this field to the number of the
9 supported multiplex option from the set {1, 2, 3, 4, 5, 6, 7, 8,
10 9, 10, 11, 12, 13, 14, 15, 16} (e.g., 1 corresponds to Multiplex
11 Option 1).
12 FOR_NUM_BITS – Forward Traffic Channel number of bits per frame.
13 If FOR_NUM_BITS = ‘00000000’, then the specified multiplex
14 option in this record shall indicate the supported multiplex
15 option for the Reverse Traffic Channel only. In this case, no
16 further interpretation of the FOR_NUM_BITS field shall be
17 made. The mobile station shall not set both FOR_NUM_BITS
18 and REV_NUM_BITS equal to ‘00000000’ in the same
20 If MULTIPLEX_OPTION is equal to 1, 3, 5, 7, 9, 11, 13, or 15,
21 this field consists of the subfields specified in Table 2.7.4.17-1
22 which are included in the information record in the order
23 shown in the table. The subfields in Table 2.7.4.17-1 refer to
24 the number of bits per frame supported on the Fundamental
25 Code Channel of the Forward Traffic Channel.
26
2-695
3GPP2 C.S0005-A v6.0
1 Table 2.7.4.17-1. Forward Fundamental Traffic Channel

2 Number of Bits per Frame for Forward Multiplex Option 1
Length
RS1_9600_FOR 1 172 bits per F-FCH frame

RS1_4800_FOR 1 80 bits per F-FCH
3

9 Code Channel of the Forward Traffic Channel.
10
11 Table 2.7.4.17-2. Forward Fundamental Traffic Channel

12 Number of Bits per Frame for Forward Multiplex Option
13 MO_FOR_FCH equal to 2
Length

14
15 The mobile station shall set the subfields specified in Tables

16 2.7.4.17-1 and 2.7.4.17-2, corresponding to the Forward
17 Traffic Channel number of bits per frame supported by the
18 mobile station for this multiplex option to ‘1’, and shall set the
19 remaining subfields to ‘0’. The mobile station shall set
20 RESERVED to ‘0000’.
21 REV_NUM_BITS – Reverse Traffic Channel transmission rates.
22 If REV_NUM_BITS is equal to ‘00000000’, then the specified
23 multiplex option in this record indicate the supported
24 multiplex option for the Forward Traffic Channel only. In this
25 case, no further interpretation of the REV_NUM_BITS field
26 shall be made. The mobile station shall not set both
27 FOR_NUM_BITS and REV_NUM_BITS equal to ‘00000000’ in
28 the same information record.
2-696
3GPP2 C.S0005-A v6.0

6 Code Channel of the Reverse Traffic Channel.
7
8 Table 2.7.4.17-3. Reverse Fundamental Traffic Channel

9 Number of Bits per Frame for Reverse Multiplex Option
10 MO_REV_FCH equal to 1
Length
RS1_9600_REV 1 172 bits per R-FCH frame

11

17 Code Channel of the Reverse Traffic Channel.
18
19 Table 2.7.4.17-4. Reverse Fundamental Traffic Channel

20 Number of Bits per Frame for Reverse Multiplex Option
21 MO_REV_FCH equal to 21
Length

22
2-697
3GPP2 C.S0005-A v6.0
1 The mobile station shall set the subfields specified in Table

2 2.7.4.17-3 and Table 2.7.4.17-4 corresponding to the Reverse
3 Traffic Channel transmission number of bits per frame
4 supported by the mobile station for this multiplex option to ‘1’,
5 and shall set the remaining subfields to ‘0’. The mobile
6 station shall set RESERVED to ‘0000’.
2-698
3GPP2 C.S0005-A v6.0
1 2.7.4.18 Service Configuration
2 The format of the Service Configuration information record is defined in 3.7.5.7.
2-699
3GPP2 C.S0005-A v6.0
1 2.7.4.19 Called Party Subaddress
2 This information record identifies the called party subaddress.

EXTENSION_BIT 1
SUBADDRESS_TYPE 3
ODD/EVEN_INDICATOR 1
RESERVED 3
CHARi 8
4 EXTENSION_BIT – The extension bit.

6 SUBADDRESS_TYPE – Type of subaddress.
8 SUBADDRESS_TYPE value shown in Table 2.7.4.19-1
9 corresponding to the type of the subaddress, as defined in [7],
10 Section 4.5.8.
11
12 Table 2.7.4.19-1. Subaddress Types
SUBADDRESS
TYPE
Description (binary)
NSAP (CCITT Recommendation 000

X.213/ISO 8348 AD2see [34])
User specified 010
Reserved others
13
14 ODD/EVEN_INDICATOR – The indicator of odd/even bits.

16 ODD/EVEN_INDICATOR value shown in Table 2.7.4.19-2
17 corresponding to the indicator of even/odd bits, as defined in
18 [7], Section 4.5.8. This field is only used when the type of
19 subaddress is “User specified” and the coding is BCD.
20
2-700
3GPP2 C.S0005-A v6.0
1 Table 2.7.4.19-2. Odd/Even Indicator
ODD/EVEN
INDICATOR
Even number of address signals 0

Odd number of address signals 1

5
8 for each character in the called party subaddress.
9 When the SUBADDRESS_TYPE field is equal to ‘000’, the
10 NSAP address shall be encoded using the preferred binary
11 encoding specified in CCITT Recommendation X.213 or ISO
12 8348 AD2[35].
13 When the SUBADDRESS_TYPE field is set to ‘010’, the user-
14 specified subaddress field is encoded according to the user
15 specification, subject to a maximum length of 20 octets.
16 When interworking with CCITT Recommendation X.25
17 networks, BCD coding should be applied.
2-701
3GPP2 C.S0005-A v6.0
1 2.7.4.20 Calling Party Subaddress
2 This information record identifies the calling party subaddress.

EXTENSION_BIT 1
SUBADDRESS_TYPE 3
RESERVED 3
CHARi 8

10 Section 4.5.10.
15 [7], Section 4.5.10. It is only used when the type of
21 for each character in the calling party subaddress.
25 8348 AD2[35].
26 When the SUBADDRESS_TYPE field is set to ‘010’, user-
29 When interworking with CCITT Recommendation X.25[36]
2-702
3GPP2 C.S0005-A v6.0
1 2.7.4.21 Connected Subaddress
2 This information record identifies the subaddress of the responding party.

3
EXTENSION_BIT 1
SUBADDRESS_TYPE 3
RESERVED 3
CHARi 8
4

11 Section 4.5.14.
22 for each character in the connected subaddress.
26 8348 AD2[35].
2-703
3GPP2 C.S0005-A v6.0
1 2.7.4.22 Power Control Information

3 Status Response Message to return the minimum power control step size supported by the
4 mobile station (see 2.1.2.3.2).
MIN_PWR_CNTL_STEP 3
RESERVED 5
6 MIN_PWR_CNTL_STEP – Minimum power control step size

7 The mobile station shall set this field to the PWR_CNTL_STEP
8 value associated with the minimum closed loop power control
9 step size shown in Table 3.7.3.3.2.25-1 that the mobile station
10 supports.
2-704
3GPP2 C.S0005-A v6.0
1 2.7.4.23 IMSI_M
3 Status Response Message to return the mobile station’s IMSI_Mp.
IMSI_M_CLASS 1
IMSI_M_ADDR_NUM 3
MCC_M 10
IMSI_M_11_12 7
IMSI_M_S 34
RESERVED 1
5 IMSI_M_CLASS – IMSI_M Class assignment of the mobile station.

6 If the mobile station’s IMSI_M is a class 0 IMSI, the mobile
9 IMSI_M_ADDR_NUM – Number of IMSI_Mp address digits.
10 If the mobile station’s IMSI_M is a class 1 IMSI, the mobile
11 station shall set this field to four less than the number of
12 digits in the NMSI; otherwise, the mobile station shall set this
13 field to ‘000’.
14 MCC_M – Mobile Country Code of the MIN based IMSI.
15 The mobile station shall set this field the MCC_Mp. See 2.3.1.
16 IMSI_M_11_12 – The 11th and 12th digits of IMSI_M.

17 The mobile station shall set this field to IMSI_M_11_12p.
18 See 2.3.1.
19 IMSI_M_S – Last ten digits of the IMSI_M.
20 The mobile station shall set this field to IMSI_M_Sp. See
21 2.3.1.
2-705
3GPP2 C.S0005-A v6.0
1 2.7.4.24 IMSI_T
3 Status Response Message to return the mobile station’s IMSI_T.
IMSI_T_CLASS 1
IMSI_T_ADDR_NUM 3
MCC_T 10
IMSI_T_11_12 7
IMSI_T_S 34
RESERVED 1
5 IMSI_T_CLASS – IMSI_T Class assignment of the mobile station.

6 If the mobile station’s IMSI_T is a class 0 IMSI, the mobile
9 IMSI_T_ADDR_NUM – Number of IMSI_Tp address digits.
10 If the mobile station’s IMSI_T is a class 1 IMSI, the mobile

11 station shall set this field to four less than the number of
12 digits in the NMSI; otherwise, the mobile station shall set this
13 field to ‘000’.
14 MCC_T – Mobile Country Code of the IMSI_T.
15 The mobile station shall set this field to the MCC_Tp.
16 See 2.3.1.
17 IMSI_T_11_12 – The 11th and 12th digits of the IMSI_Tp.
18 The mobile station shall set this field to IMSI_T_11_12p.
19 See 2.3.1.
20 IMSI_T_S – Last ten digits of the IMSI_Tp.
21 The mobile station shall set this field to IMSI_T_Sp. See 2.3.1.

2-706
3GPP2 C.S0005-A v6.0
1 2.7.4.25 Capability Information
2 This information record identifies whether the following optional or MOB_P_REV dependent
3 features are supported by the mobile station.
ACCESS_ENTRY_HO 1
ACCESS_PROBE_HO 1
ANALOG_SEARCH 1
HOPPING_BEACON 1
MAHHO 1
PUF 1
ANALOG_553A 1
QPCH 1
SLOTTED_TIMER 1
CHS_SUPPORTED 1
GATING_RATE_SET 0 or 2
EXT_CAP_INCLUDED 1
If EXT_CAP_INCLUDED is set to ‘1’, include the following
two-field record:
MABO 0 or 1
SDB 0 or 1
RLP_INFO_LEN 3
RLP_BLOB 8 X RLP_INFO_LEN
FLEX_SUPPORTED 1
F_FCH_FLEX_SUPPORTED 0 or 1
R_FCH_FLEX_SUPPORTED 0 or 1
2-707
3GPP2 C.S0005-A v6.0
F_DCCH_FLEX_SUPPORTED 0 or 1
R_DCCH_FLEX_SUPPORTED 0 or 1
F_SCH_FLEX_SUPPORTED 0 or 1
R_SCH_FLEX_SUPPORTED 0 or 1
VAR_SUPPORTED 1
F_SCH_VAR_SUPPORTED 0 or 1
R_SCH_VAR_SUPPORTED 0 or 1
MAX_SUM_NUM_BITS_C 0 or 16
MAX_SUM_NUM_BITS_T 0 or 16
CS_SUPPORTED 1
F_SCH_LTU_TAB_SUPPORTED 1
R_SCH_LTU_TAB_SUPPORTED 1
3 ACCESS_ENTRY_HO – Access Entry Handoff Support.

4 This field identifies the mobile station’s support for access
5 entry handoff (see 2.6.2.3). The mobile station shall set this
6 field to ‘1’ if access entry handoff is supported; otherwise, the
8 ACCESS_PROBE_HO – Access Probe Handoff Support.
9 This field identifies the mobile station’s support for access
10 probe handoff (see 2.6.3.1.3.3). The mobile station shall set
11 this field to ‘1’ if access probe handoff is supported; otherwise,
13 ANALOG_SEARCH – Analog Search Support.
14 This field identifies the mobile station’s support for analog
15 searching (see 2.6.6.2.10). The mobile station shall set this
16 field to ‘1’ if analog searching is supported; otherwise, the
18 HOPPING_BEACON – Hopping Beacon Support.
19 This field identifies the mobile station’s support for hopping pilot
20 beacons. The mobile station shall set this field to ‘1’ if hopping
21 pilot beacons are supported; otherwise, this field shall be set to
22 ‘0’.
2-708
3GPP2 C.S0005-A v6.0
1 MAHHO – Mobile Assisted Hard Handoff Support.

2 This field identifies the mobile station’s support for mobile
3 assisted hard handoff. The mobile station shall set this field to
4 ‘1’.
5 PUF – Location Power Up Function Support.
6 This field identifies the mobile station’s support for location
7 power up function (see 2.6.4.1.7).
8 If MOB_P_REVp is equal to ‘00000101’, the mobile station shall
9 set this field to ‘1’; otherwise the mobile station shall set this
10 field as follows:
11 If the mobile station supports location power up function, the
12 mobile station shall set this field to ‘1’, otherwise, the mobile
14 ANALOG_553A – Analog Support.
15 This field identifies the mobile station’s compatibility with [12].
17 QPCH – Quick Paging Channel Support.
18 This field identifies the mobile station’s support for the Quick
19 Paging Channel. The mobile station shall set this field to ‘1’ if
20 the Quick Paging Channel is supported; otherwise, the mobile
22 SLOTTED_TIMER – Slotted Timer Support.
23 This field identifies the mobile station’s support for the Slotted
24 Timer. The mobile station shall set this field to ‘1’ if the Slotted
25 Timer is supported; otherwise, the mobile station shall set this
26 field to ‘0’.
27 CHS_SUPPORTED – Control Hold Mode supported indicator.
28 The mobile station shall set this field to ‘1’ to indicate that the
29 mobile station supports the Control Hold Mode; otherwise, the
31 GATING_RATE_SET – Set of supported Reverse Pilot gating rates.
32 If CHS_SUPPORTED is included and is set to ‘1’, the mobile
33 station shall set this field to value shown in Table 2.7.4.25-1
34 corresponding to the set of supported reverse pilot gating
35 rates; otherwise the mobile station shall omit this field.
36
2-709
3GPP2 C.S0005-A v6.0
1 Table 2.7.4.25-1. Set of supported Reverse Pilot Gating Rates
GATING_RATE SET Gating Rates Capability

field (binary)
00 Gating rates 1
01 Gating rates 1 and ½
10 Gating rates 1, ½ and ¼
11 Reserved
3 EXT_CAP_INCLUDED – Extended Capabilities Included indicator.

4 The mobile station shall set this field to ‘1’ to indicate that
5 extended capability indicators are included in this record;
7 MABO – Mobile Assisted Burst Operation capability indicator.
8 If EXT_CAP_INCLUDED is set to ‘0’, the mobile station shall omit
11 If EXT_CAP_INCLUDED is set to ‘1’, tThe mobile station shall set
12 this field to ‘1’ to indicate that if it supports the Mobile Assisted
13 Burst Operation capability; otherwise, the mobile station shall
15 SDB – Short Data Burst supported indicator.
16 If EXT_CAP_INCLUDED is set to ‘0’, the mobile station shall
19 If EXT_CAP_INCLUDED is set to ‘1’, tThe mobile station shall
20 set this field to ’1’ to indicate that if it supports Short Data
21 Burst capability; otherwise, the mobile station shall set this
23 RLP_INFO_LEN - RLP capability information length.
24 The mobile station shall set this field to ‘000’ if the RLP_BLOB
25 field is not included in this record; otherwise, it shall set this
26 field to the size of the RLP_BLOB field in integer number of
27 octets.
28 RLP_BLOB - Radio Link Protocol information block of bits.
29 If the RLP_INFO_LEN field is set to ‘000’, the mobile station
32 The mobile station shall set this field to the Radio Link
33 Protocol information block of bits.
34 FLEX_SUPPORTED – Flexible rate feature supported indicator.
2-710
3GPP2 C.S0005-A v6.0
1 The mobile station shall set this field to ‘1’ if it supports the
2 flexible rate feature (the capability to support a non-listed
3 frame format) on any of the forward or reverse Fundamental,
4 Supplemental or Dedicated Control channels; otherwise, the
6
7 F_FCH_FLEX-
8 _SUPPORTED – Forward Fundamental channel flexible rate feature supported
9 indicator.
10 The mobile station shall include this field only if
11 FLEX_SUPPORTED is equal to ‘1’. If this field is included, the
12 mobile station shall set this field to ‘1’ if it supports the
13 flexible rate feature for the Forward Fundamental Channel;
15 R_FCH_FLEX-
16 _SUPPORTED – Reverse Fundamental channel flexible rate feature supported
17 indicator.
21 flexible rate feature for the Reverse Fundamental Channel;
23 F_DCCH_FLEX-
24 _SUPPORTED – Forward Dedicated Control channel flexible rate feature
29 flexible rate feature for the Forward Dedicated Control
30 Channel; otherwise, the mobile station shall set this field to
31 ‘0’.
32 R_DCCH_FLEX-
33 _SUPPORTED – Reverse Dedicated Control channel flexible rate feature
38 flexible rate feature for the Reverse Dedicated Control
39 Channel; otherwise, the mobile station shall set this field to
40 ‘0’.
41
42 F_SCH_FLEX-
43 _SUPPORTED – Forward Supplemental channel flexible rate feature supported
44 indicator.
2-711
3GPP2 C.S0005-A v6.0

4 flexible rate feature for the Forward Supplemental Channel;
6 R_SCH_FLEX-
7 _SUPPORTED – Reverse Supplemental channel flexible rate feature supported
8 indicator.
12 flexible rate feature for the Reverse Supplemental Channel;
14 VAR_SUPPORTED – Variable rate feature supported indicator.
15 The mobile station shall set this field to ‘1’ if it supports the
16 variable rate feature (the capability to support rate
17 determination) on any of the forward or reverse Supplemental
18 or Dedicated Control channels; otherwise, the mobile station
20 F_SCH_VAR-
21 _SUPPORTED – Forward Supplemental Channel Variable Rate supported
22 indicator.
24 FLEXVAR_SUPPORTED is equal to ‘1’. If this field is included,
25 the mobile station shall set this field to ‘1’ if it supports the
26 rate determination feature on the Forward Supplemental
27 Channels.
28 R_SCH_VAR-
29 _SUPPORTED – Reverse Supplemental Channel Variable Rate supported
30 indicator.
32 FLEXVAR_SUPPORTED is equal to ‘1’. If this field is included,
33 the mobile station shall set this field to ‘1’ if it supports the
34 variable rate determination feature on the Reverse
35 Supplemental Channels.
36 MAX_SUM-
37 _NUM_BITS_C – Maximum sum of number of bits corresponding to
38 Convolutional rates in the variable rate set.
40 F_SCH_VAR_SUPPORTED is equal to ‘1’. If this field is
41 included, the mobile station shall set this field to the
42 maximum of the sum of possible information bits per 20 ms
43 corresponding to the Convolutional Code rates in the Variable
44 Rate Set for a Forward Supplemental Channel below which
45 the mobile station is capable of performing rate determination
46 on the forward supplemental channel when Convolutional
47 coding is used.
2-712
3GPP2 C.S0005-A v6.0
1 MAX_SUM-
2 _NUM_BITS_T – Maximum sum of number of bits corresponding to Turbo Code
3 rates in the variable rate set
5 F_SCH_VAR_SUPPORTED is equal to ‘1’. If this field is
6 included, the mobile station shall set this field to the
7 maximum of the sum of possible information bits per 20 ms
8 corresponding to the Turbo Code rates in the Variable Rate
9 Set for a Forward Supplemental Channel below which the
10 mobile station is capable of performing rate determination on
11 the forward supplemental channel when Turbo coding is used.
12 CS_SUPPORTED – Concurrent Services supported indicator.
13 If the mobile station supports concurrent services, the mobile
16 F_SCH_LTU_TAB
17 _SUPPORTED – Forward Supplemental Channel Downloadable LTU tables
19 If the mobile station supports downloadable LTU Tables for
20 Forward Supplemental Channel, the mobile station shall set
22 to ‘0’.
23 R_SCH_LTU_TAB
24 _SUPPORTED – Reverse Supplemental Channel Downloadable LTU tables
26 If the mobile station supports downloadable LTU Tables for
27 Reverse Supplemental Channel, the mobile station shall set
29 to ‘0’.
34 bits to ‘0’.
2-713
3GPP2 C.S0005-A v6.0
1 2.7.4.26 Extended Record Type - International
2 The use of this record type is country-specific. The first ten bits of the type-specific fields
3 shall include the Mobile Country Code (MCC) associated with the national standards
4 organization administering the use of the record type. Encoding of the MCC shall be as
5 specified in 2.3.1.3. The remaining six bits of the first two octets of the type-specific fields
6 shall be used to specify the country-specific record type.
2-714
3GPP2 C.S0005-A v6.0
1 2.7.4.27 Channel Configuration Capability Information

3 Status Response Message to return channel configuration capability information about the
4 mobile station.
OTD_SUPPORTED 1
FCH_SUPPORTED 1
FCH Type-specific fields 0 or Variable
DCCH_SUPPORTED 1
DCCH Type-specific fields 0 or Variable
FOR_SCH_SUPPORTED 1
FOR_SCH Type-specific fields 0 or Variable
REV_SCH_SUPPORTED 1
REV_SCH Type-specific fields 0 or Variable
NONOCTET_ALIGNED_DATARESE 0 or 2 1
RVED_1
OCTET_ALIGNED_DATA 1
STS_SUPPORTED 1
3X_CCH_SUPPORTED 1
7 OTD_SUPPORTED – OTD supported indicator.

9 station supports orthogonal transmission diversity; otherwise,
12 The mobile station shall set this field to ‘1’, if the mobile
13 station supports the Fundamental Channel; otherwise, the
15 FCH Type-specific fields – Fundamental Channel configuration capability information.
16 If the FCH_SUPPORTED field is set to ‘1’, the mobile station
17 shall include this field and set it as described in 2.7.4.27.1;
18 otherwise the mobile station shall omit this field.
2-715
3GPP2 C.S0005-A v6.0
2 station supports the Dedicated Control Channel; otherwise,
4 DCCH Type-
5 specific fields – Fundamental Channel configuration capability information.
6 If the DCCH_SUPPORTED field is set to ‘1’, the mobile station
7 shall include this field and set it as described in 2.7.4.27.2;
8 otherwise the mobile station shall omit this field.
9 FOR_SCH_SUPPORTED – Forward Supplemental Channel supported indicator.
11 station supports the Forward Supplemental Channel;
13 FOR_SCH Type-
14 specific fields – Forward Supplemental Channel Configuration Capability
15 Information.
16 If the FOR_SCH_SUPPORTED field is set to ‘1’, the mobile
17 station shall include this field and set it as described in
18 2.7.4.27.3; otherwise the mobile station shall omit this field.
19 REV_SCH_SUPPORTED – Reverse Supplemental Channel supported indicator.
21 station supports the Reverse Supplemental Channel;
23 REV_SCH Type-
24 specific fields – Reverse Supplemental Channel Configuration capability
25 information.
26 If the REV_SCH_SUPPORTED field is set to ‘1’, the mobile
27 station shall include this field and set it as described in
28 2.7.4.27.4; otherwise the mobile station shall omit this field.
29 NONOCTET_ALIGNED-
30 _DATARESERVED_1 – Non-octet Aligned Data Block supported indicator. Reserved
31 bits.
32 If both the FOR_SCH_SUPPORTED and
33 REV_SCH_SUPPORTED fields are set to ‘0’, the mobile station
34 shall omit this field. Otherwise, the mobile station shall
35 include this field and set this field to ‘1’ if it supports use of
36 non-octet aligned data blocks on a SCH '00'.
37 OCTET_ALIGNED_DATA – Octet Aligned Data Block supported indicator.
38 If both the FOR_SCH_SUPPORTED and
39 REV_SCH_SUPPORTED fields are set to ‘0’, the mobile station
40 shall omit this field. Otherwise, the mobile station shall set
41 this field to ‘1’ if it supports use of octet aligned data blocks
42 on a SCH.
2-716
3GPP2 C.S0005-A v6.0
4 3X_CCH_SUPPORTED – 3X Common Channel supported.
13 bits to ‘0’.
14
2-717
3GPP2 C.S0005-A v6.0
1 2.7.4.27.1 FCH Type-specific Fields
2 The Fundamental Channel configuration capability information included in the FCH Type-
3 specific fields contains the following subfields:
FCH_FRAME_SIZE 1
FOR_FCH_LEN 3
FOR_FCH_RC_MAP 3 x FOR_FCH_LEN
REV_FCH_LEN 3
REV_FCH_RC_MAP 3 x REV_FCH_LEN
6 FCH_FRAME_SIZE – Fundamental Channel Frame Size capability indicator.

7 If in addition to the 20 ms frame size the mobile station also
8 supports the 5 ms frame size on the Fundamental Channel,
9 the mobile station shall set this field to ‘1’; otherwise, the
11 FOR_FCH_LEN – Forward Fundamental Channel Configuration information
12 length.
13 The mobile station shall set this field to the number of 3 bit
14 units required to specify the length, in bits, of the
15 FOR_FCH_RC_MAP field.
16 FOR_FCH_RC_MAP – Forward Fundamental Radio Configuration information.
17 The mobile station shall set this field as described below to
18 indicate which Radio Configurations (see [2] Table 3.1.3.1-1)
19 are supported by the mobile station on the Forward
21 This field consists of the sequence of 1-bit indicators, each
22 indicating the mobile station support for specific Radio
23 Configuration. Bit positions of these indicators in the field
24 and corresponding Radio Configurations are specified in Table
25 2.7.4.27.1-1.
26 The mobile station shall set each indicator to ‘1’ if the
27 corresponding Radio Configuration on the Forward
28 Fundamental Channel is supported by the mobile station;
29 otherwise, the mobile station shall set the indicator to ‘0’. The
30 mobile station shall set any unused bits in the field to ‘0’.
2-718
3GPP2 C.S0005-A v6.0
1 Table 2.7.4.27.1-1. Forward Channel Radio Configurations Supported
Subfield Length (bits) Subfield Description
RC1 1 Radio Configuration 1

3 REV_FCH_LEN – Reverse Fundamental Channel Configuration information

4 length.
5 The mobile station shall this field to the number of 3 bit units
6 required to specify the length, in bits, of the
7 REV_FCH_RC_MAP field.
8 REV_FCH_RC_MAP – Reverse Fundamental Radio Configuration information.
11 are supported by the mobile station on the Reverse
17 2.7.4.27.1-2.
19 corresponding Radio Configuration on the Reverse
23
2-719
3GPP2 C.S0005-A v6.0
1 Table 2.7.4.27.1-2. Reverse Channel Radio Configurations Supported

2-720
3GPP2 C.S0005-A v6.0
1 2.7.4.27.2 DCCH Type-Specific Fields
2 The Dedicated Control Channel configuration capability information included in the DCCH
3 Type-specific fields contains the following subfields:
DCCH_FRAME_SIZE 2
FOR_DCCH_LEN 3
FOR_DCCH_RC_MAP 3 x FOR_DCCH_LEN
REV_DCCH_LEN 3
REV_DCCH_RC_MAP 3 x REV_DCCH_LEN
5 DCCH_FRAME_SIZE – Frame Size supported indicator on the Dedicated Control

6 Channel.
7 The mobile station shall set this field to the frame size
8 supported for the forward and reverse DCCH, as shown in
9 Table 2.7.4.27.2-1.
10 Table 2.7.4.27.2-1. DCCH Frame Size Supported
DCCH_FRAME_SIZE
(binary) Description
00 Either 5 ms or 20 ms frame sizes

(not dynamically switchable)
01 20 ms frame size only
11 Both 5 ms and 20 ms frame sizes
(Dynamically switchable)
11
12 FOR_DCCH_LEN – Forward Dedicated Control Channel Configuration information

13 length.
16 FOR_DCCH_RC_MAP field.
17 FOR_DCCH_RC_MAP – Forward Dedicated Channel Radio Configuration information.
19 indicate which Radio Configurations (See (see [2] Table
20 3.1.3.1-1) are supported by the mobile station on the Forward
26 2.7.4.27.1-1.
2-721
3GPP2 C.S0005-A v6.0

2 corresponding Radio Configuration on the Forward Dedicated
3 Control Channel is supported by the mobile station;
6 REV_DCCH_LEN – Reverse Dedicated Control Channel Configuration information
7 length.
10 REV_DCCH_RC_MAP field.
11 REV_DCCH_RC_MAP – Reverse Dedicated Control Channel Radio Configuration
12 information.
15 are supported by the mobile station on the Reverse Dedicated
16 Control Channel.
21 2.7.4.27.1-2.
23 corresponding Radio Configuration on the Reverse Dedicated
24 Control Channel is supported by the mobile station;
2-722
3GPP2 C.S0005-A v6.0
1 2.7.4.27.3 FOR_SCH Type-Specific Fields.
2 The Forward Supplemental Channel configuration capability information included in the

3 FOR_SCH Type-specific fields contains the following subfields:
FOR_SCH_LEN 3
FOR_SCH_RC_MAP 3 x FOR_SCH_LEN
FOR_SCH_NUM 2
5 FOR_SCH_NUM occurrences of the following fields:

FOR_TURBO_SUPPORTED 1
FOR_MAX_TURBO_BLOCK_SIZE 0 or 4
FOR_CONV_SUPPORTED 1
FOR_MAX_CONV_BLOCK_SIZE 0 or 4
FOR_FRAME_40_SUPPORTED 1
FOR_FRAME_80_SUPPORTED 1
FOR_MAX_RATE 4
7 FOR_SCH_LEN – Forward Supplemental Channel information length in units of

8 3 bits.
11 FOR_SCH_RC_MAP field.
12 FOR_SCH_RC_MAP – Forward Supplemental Channel Radio Configuration
13 capability.
16 are supported by the mobile station on the Forward
22 2.7.4.27.1-1.
24 corresponding Radio Configuration on the Forward
25 Supplemental Channel is supported by the mobile station;
28 FOR_SCH_NUM – Number of Forward Supplemental Channels.
2-723
3GPP2 C.S0005-A v6.0

2 Forward Supplemental Channels supported by the mobile
3 station.
4 If the FOR_SCH_NUM field is greater than zero, the mobile
5 station shall include one occurrence of the following 8 fields
6 for each Forward Supplemental Channel supported by the
7 mobile station. The first occurrence is SCH0 related
8 information. The second occurrence (if any) is SCH1 related
9 information.
10 FOR_TURBO-
11 _SUPPORTED – Forward Turbo Coding supported indicator.
12 If the mobile station supports Turbo Coding on this Forward
13 Supplemental Channel, it shall set this field to ‘1’; otherwise,
15 FOR_MAX_TURBO-
16 _BLOCK_SIZE – Forward maximum Turbo Coding block size.
17 If the field FOR_TURBO_SUPPORTED is set to ‘0’, the mobile
18 station shall omit this field; otherwise the mobile station shall
19 include this field and set it to the maximum block size allowed
20 for Turbo coding (see Table 2.7.4.27.3-1).
21 Table 2.7.4.27.3-1. Block Size
FOR_MAX_TURBO_BLOCK_SIZE Block Size
REV_MAX_TURBO_BLOCK_SIZE
FOR_MAX_CONV_BLOCK_SIZE
REV_MAX_CONV_BLOCK_SIZE
(binary)
R-SCH RC R-SCH RC 4
3 and 5 and 6
F-SCH RC F-SCH RC
3, 4, 6, 5, 8 and 9
and 7 Rate Set 2
Rate Set 1
0000 172 267
0001 360 552
0010 744 1128
0011 1512 2280
0100 3048 4584
0101 6120 9192
2-724
3GPP2 C.S0005-A v6.0
0110 12264 20712
RESERVED All other values are

reserved
1
2 FOR_CONV-
3 _SUPPORTED – Forward Convolutional Coding supported indicator.
4 If the mobile station supports Convolutional Coding on this
5 Forward Supplemental Channel, it shall set this field to ‘1’;
7 FOR_MAX_CONV-
8 _BLOCK_SIZE – Forward maximum Convolutional Coding block size.
9 If the field FOR_CONV_SUPPORTED is set to ‘0’, the mobile
12 for Convolutional coding. (see Table 2.7.4.27.3-1)
13 FOR_FRAME_40-
14 _SUPPORTED – Forward 40ms frame indicator.
15 If the mobile station supports 40 ms frames on this Forward
18 FOR_FRAME_80-
19 _SUPPORTED – Forward 80ms frame Indicator.
20 If the mobile station supports 80 ms frames on this Forward
23 FOR_MAX_RATE - Maximum forward supplemental channels rate
24 The mobile station shall set this field according to Table
25 2.7.4.27.3-2 to indicate the maximum forward supplemental
26 channel frame rate supported.
27
2-725
3GPP2 C.S0005-A v6.0
2 Table 2.7.4.27.3-2. SCH Data Rate
REV_MAX_RATE Max Rate (kbps)
FOR_MAX_RATE
R-SCH RC R-SCH RC
(binary) 3, 5 4, 6
F-SCH RC F-SCH RC
3, 4, 6, 7 5, 8, 9
0000 9.6 14.4
0001 19.2 28.8
0010 38.4 57.6
0011 76.8 115.2
0100 153.6 230.4
0101 307.2 259.2
0110 614.4 460.8
0111 Reserved 518.4
1000 Reserved 1036.8
RESERVED All other values are

reserved
2-726
3GPP2 C.S0005-A v6.0
1 2.7.4.27.4 REV_SCH Type-Specific Fields.
2 The Reverse Supplemental Channel configuration capability information included in the

3 REV_SCH Type-specific fields contains the following subfields:
REV_SCH_LEN 3
REV_SCH_RC_MAP 3 x REV_SCH_LEN
REV_SCH_NUM 2
5 REV_SCH_NUM occurrences of the following fields:

REV_TURBO_SUPPORTED 1
REV_MAX_TURBO_BLOCK_SIZE 0 or 4
REV_CONV_SUPPORTED 1
REV_MAX_CONV_BLOCK_SIZE 0 or 4
REV_FRAME_40_SUPPORTED 1
REV_FRAME_80_SUPPORTED 1
REV_MAX_RATE 4
7 REV_SCH_LEN – Reverse Supplemental Channel information length in units of

8 3 bits.
11 REV_SCH_RC_MAP field.
12 REV_SCH_RC_MAP – Reverse Supplemental Channel Radio Configuration
13 capability.
15 indicate which Radio Configurations (See [2] Table 2.1.3.1-1)
16 are supported by the mobile station on the Reverse
22 2.7.4.27.1-12.
24 corresponding Radio Configuration on the Reverse
25 Supplemental Channel is supported by the mobile station;
28 REV_SCH_NUM – Number of Reverse Supplemental Channels
29 The mobile station shall set this field to the number of Reverse
30 Supplemental Channels supported by the mobile station.
2-727
3GPP2 C.S0005-A v6.0
1 If the REV_SCH_NUM field is greater than zero, the mobile

2 station shall include one occurrence of the following 8 fields
3 for each Reverse Supplemental Channel supported by the
4 mobile station. The first occurrence is SCH0 related
5 information. The second occurrence (if any) is SCH1 related
6 information.
7 REV_TURBO-
8 _SUPPORTED – Reverse Turbo Coding supported indicator.
9 If the mobile station supports Turbo Coding on this Reverse
12 REV_MAX_TURBO-
13 _BLOCK_SIZE – Reverse maximum Turbo Coding block size.
14 If the field REV_TURBO_SUPPORTED is set to ‘0’, the mobile
16 include this field and set it to the maximum block size
17 allowed for Turbo coding (see Table 2.7.4.27.3-1).
18 REV_CONV_SUPPORTED – Reverse Convolutional Coding supported indicator.
19 If the mobile station supports Convolutional Coding on this
20 Reverse Supplemental Channel, it shall set this field to ‘1’;
22 REV_MAX_CONV-
23 _BLOCK_SIZE – Reverse maximum Convolutional Coding block size.
24 If the field REV_CONV_SUPPORTED is set to ‘0’, the mobile
27 for Convolutional coding (see Table 2.7.4.27.3-1).
28 REV_FRAME_40-
29 _SUPPORTED – Reverse 40ms frame indicator.
30 If the mobile station supports 40 ms frames on this Reverse
33 REV_FRAME_80-
34 _SUPPORTED – Reverse 80ms frame indicator.
35 If the mobile station supports 80 ms frames on this Reverse
38 REV_MAX_RATE – Maximum reverse supplemental channels rate
39 The mobile station shall set this field according to Table
40 2.7.4.27.3-2 to indicate the maximum reverse supplemental
41 channel frame rate supported.
2-728
3GPP2 C.S0005-A v6.0
1 2.7.4.28 Extended Multiplex Option Information

3 Status Response Message to return multiplex option information about the mobile station.
2-729
3GPP2 C.S0005-A v6.0
NUM_MO_FOR_FCH 4
NUM_MO_FOR_FCH occurrences of the following two-field
record:
MO_FOR_FCH 16
FOR_NUM_BITS_FCH 8
NUM_MO_REV_FCH 4
NUM_MO_REV_FCH occurrences of the following two-field
record:
MO_REV_FCH 16
REV_NUM_BITS_FCH 8
NUM_MO_FOR_DCCH 4
NUM_MO_FOR_DCCH occurrences of the following one-field
record:
MO_FOR_DCCH 16
NUM_MO_REV_DCCH 4
NUM_MO_REV_DCCH occurrences of the following one-field
record:
MO_REV_DCCH 16
NUM_MO_FOR_SCH 4
NUM_MO_FOR_SCH occurrences of the following two-field
record:
FOR_SCH_ID 1
MO_FOR_SCH 16
NUM_MO_REV_SCH 4
NUM_MO_REV_SCH occurrences of the following two-field
record:
REV_SCH_ID 1
MO_REV_SCH 16
2-730
3GPP2 C.S0005-A v6.0
2 NUM_MO_FOR_FCH – Number of Forward Fundamental Channel Multiplex Options.

4 Forward Fundamental Channel Multiplex Options supported
6 If NUM_MO_FOR_FCH is not equal to ‘0000’, the mobile

7 station shall include NUM_MO_FOR_FCH occurrences of the
8 following two fields for each supported Forward Fundamental
9 Channel multiplex option:
10 MO_FOR_FCH – Forward Fundamental Channel multiplex option.
11 The mobile station shall set this field to the Forward
12 Fundamental Channel multiplex option.
13 FOR_NUM-
14 _BITS_FCH – Forward Fundamental Channel number of bits per frame.
16 indicate which number of bits per frameare supported by the
17 mobile station on the Forward Fundamental Channel.
19 indicating the mobile station support for specific number of
20 bits per frame. Bit positions of these indicators in the field
21 and corresponding number of bits per frameare specified in
22 Table 2.7.4.28-1 if MO_FOR_FCH is equal to 1, Table 2.7.4.28-
23 2 if MO_FOR_FCH is equal to 2, and Table 2.7.4.28-3 if
24 MO_FOR_FCH is equal to 0x704.
26 corresponding number of bits per frameon the Forward
28 otherwise, the mobile station shall set the indicator to ‘0’.
29
30 Table 2.7.4.28-1. Forward Fundamental Channel Number of

31 Bits per Frame for MO_FOR_FCH equal to 1
Length

RS1_1200_FOR 1 16bits per F-FCH frame
32
2-731
3GPP2 C.S0005-A v6.0

2 Bits per Frame for MO_FOR_FCH equal to 2
Length


5 Bits per Frame for MO_FOR_FCH equal to 0x704
Length
R1 1 Highest possible number of bits on F-FCH (specified

by NUM_BITSs[FFCH_NBIT_TABLE_ID][0000])
R2 1 Second highest possible number of bits on F-FCH

(specified by
NUM_BITSs[FFCH_NBIT_TABLE_ID][0001])
R3 1 Third highest possible number of bits on F-FCH

(specified by
R4 1 Forth highest possible number of bits on F-FCH

(specified by
R5 1 Fifth Second highest possible number of bits on

F-FCH (specified by
R6 1 Sixth highest possible number of bits on F-FCH

(specified by
R7 1 Seventh highest possible number of bits on F-FCH

(specified by
R8 1 Eighth highest possible number of bits on F-FCH

(specified by
7 NUM_MO_REV_FCH – Number of Reverse Fundamental Channel Multiplex Options.
2-732
3GPP2 C.S0005-A v6.0
2 Reverse Fundamental Channel Multiplex Options supported
4 If NUM_MO_REV_FCH is not equal to ‘0000’, the mobile

5 station shall include NUM_MO_REV_FCH occurrences of the
6 following two fields for each supported Reverse Fundamental
7 Channel multiplex option:
8 MO_REV_FCH – Reverse Fundamental Channel multiplex option.
9 The mobile station shall set this field to the Reverse
10 Fundamental Channel multiplex option.
11 REV_NUM-
12 _BITS_FCH – Reverse Fundamental Channel number of bits per frame.
14 indicate which number of bits per frame are supported by the
15 mobile station on the Reverse Fundamental Channel.
17 indicating the mobile station support for number of bits per
18 frame. Bit positions of these indicators in the field and
19 corresponding number of bits per frame are specified in Table
20 2.7.4.28-4 if MO_REV_FCH is equal to 1, Table 2.7.4.28-5 if
21 MO_REV_FCH is equal to 2, and Table 2.7.4.28-6 if
22 MO_REV_FCH is equal to 0x704.
24 corresponding number of bits per frameon the Reverse
26 otherwise, the mobile station shall set the indicator to ‘0’.
27
28 Table 2.7.4.28-4. Reverse Fundamental Channel Number of

29 Bits per Frame for MO_REV_FCH equal to 1
Length

30
2-733
3GPP2 C.S0005-A v6.0

2 Bits per Frame for MO_REV_FCH equal to 2
Length


5 Bits per Frame for MO_REV_FCH equal to 0x704
Length
R1 1 Highest possible number of bits on R-FCH (specified

by NUM_BITSs[RFCH_NBIT_TABLE_ID][0000])
R2 1 Second highest possible number of bits on R-FCH

(specified by
NUM_BITSs[RFCH_NBIT_TABLE_ID][0001])
R3 1 Third highest possible number of bits on R-FCH

(specified by
R4 1 Forth highest possible number of bits on R-FCH

(specified by
R5 1 Fifth Second highest possible number of bits on

R-FCH (specified by
R6 1 Sixth highest possible number of bits on R-FCH

(specified by
R7 1 Seventh highest possible number of bits on R-FCH

(specified by
R8 1 Eighth highest possible number of bits on R-FCH

(specified by
2-734
3GPP2 C.S0005-A v6.0
1 NUM_MO_FOR_DCCH – Number of Forward Dedicated Control Channel Multiplex

2 Options.
4 Forward Dedicated Control Channel Multiplex Options
6 If NUM_MO_FOR_DCCH is not equal to ‘0000’, the mobile

7 station shall include NUM_MO_FOR_DCCH occurrence of the
8 following one field for each supported Forward Dedicated
9 Control Channel multiplex option:
10 MO_FOR_DCCH – Forward Dedicated Control Channel multiplex option.
12 Dedicated Control Channel multiplex option.
13 NUM_MO_REV_DCCH – Number of Reverse Dedicated Control Channel Multiplex
14 Options.
16 Reverse Dedicated Control Channel Multiplex Options
18 If NUM_MO_REV_DCCH is not equal to ‘0000’, the mobile

19 station shall include NUM_MO_REV_DCCH occurrence of the
20 following one field for each supported Reverse Dedicated
21 Control Channel multiplex option:
22 MO_REV_DCCH – Reverse Dedicated Control Channel multiplex option.
23 The mobile station shall set this field to the Reverse Dedicated
24 Control Channel multiplex option.
25 NUM_MO_ FERFOR_SCH – Number of Forward Supplemental Channel Multiplex Options.
27 Reverse Forward Supplemental Channel Multiplex Options
28 supported by the mobile station included in this message.
29 The mobile station shall include the multiplex option
30 associated with the highest data rate it supports for each
31 combination of MuxPDU type, rate set, and block size4.
32 If NUM_MO_FERFOR_SCH is not equal to ‘0000’, the mobile

33 station shall include NUM_MO_FERFOR_SCH occurrence of
34 the following two fields:
35 FOR_SCH_ID – Forward Supplemental Channel identifier.
4 If any Rate Set 1 multiplex option is included, then mobile station support of MuxPDU Type 1 is
implied and the mobile station is not required to include multiplex option 0x03. If any Rate Set 2
multiplex option is included, then mobile station support of MuxPDU Type 2 is implied and the
mobile station is not required to include multiplex option 0x04 (see [3]).
2-735
3GPP2 C.S0005-A v6.0
1 The mobile station shall set this field to specify the Forward
2 Supplemental Channel to which the Forward Supplemental
3 multiplex option supported by the mobile station corresponds.
4 MO_FOR_SCH – Forward Supplemental Channel multiplex option.

6 Supplemental Channel multiplex option associated with the
7 maximum data rate (see [3]) that the mobile station supports5.
8 NUM_MO_REV_SCH – Number of Reverse Supplemental Channel Multiplex Options.
10 Reverse Supplemental Channel Multiplex Options supported
11 by the mobile stationincluded in this message. The mobile
12 station shall include the multiplex option associated with the
13 highest data rate it supports for each combination of MuxPDU
14 type, rate set, and block size6.
15 If NUM_MO_REV_SCH is not equal to ‘0000’, the mobile

16 station shall include NUM_MO_REV_SCH occurrence of the
17 following two fields:
18 REV_SCH_ID – Reverse Supplemental Channel identifier.
19 The mobile station shall set this field to specify the Reverse
20 Supplemental Channel to which the Reverse Supplemental
21 multiplex option supported by the mobile station corresponds.
22 MO_REV_SCH – Reverse Supplemental Channel multiplex option.
23 The mobile station shall set this field to the Reverse
24 Supplemental Channel multiplex option associated with the
25 maximum data rate (see [3]) that the mobile station supports7.
30 bits to ‘0’.
5 1 If the mobile station supports the multiplex option associated with the maximum data rate, the
mobile station shall support all lower data rates as specified in Table 2-46 of [3].
6 If any Rate Set 1 multiplex option is included, then mobile station support of MuxPDU Type 1 is
implied and the mobile station is not required to include multiplex option 0x03. If any Rate Set 2
multiplex option is included, then mobile station support of MuxPDU Type 2 is implied and the
mobile station is not required to include multiplex option 0x04 (see [3]).
7 If the mobile station supports the multiplex option associated with the maximum data rate, the
mobile station shall support all lower data rates as specified in Table 2-46 of [3].
2-736
3GPP2 C.S0005-A v6.0
1 2.7.4.29 Geo-Location Capability
2 This information record identifies the geo-location capabilities of the mobile station. The
3 mobile station shall use the following fixed-length format for the type-specific fields:
GEO_LOC 3
RESERVED 5
6 GEO_LOC – Geo-location.
7 The mobile station shall set this field to the value shown in Table
8 2.7.4.34-1.
9 Table 2.7.4.34-1. Geo-location Codes
GEO_LOC
(binary) Type of Wireless Assisted GPS
Identifiers
000 No mobile station assisted geo-location

capabilities
Triangulation only)
Triangulation and Global Positioning
Systems)
011 Global Positioning Systems only
All other GEO_LOC_TYPE values are reserved.

12
2-737
3GPP2 C.S0005-A v6.0
1 2.7.4.30 Band Subclass Information

3 Status Response Message to return band subclass information about the mobile station.
BAND_SUBCLASS_INFO 8 × RECORD_LEN
6 BAND_SUBCLASS_INFO – Band subclass information.

7 This field indicates which band subclasses are supported by
9 If BAND_CLASS specified in the Status Request Message is
10 equal to ‘00000’ (Cellular Band), this field consists of the
11 following subfields which are included in the information
12 record in the order shown:
13
Length
BAND_SUBCLASS_0 1 Band Subclass 0

14

16 equal to ‘00010’ (TACS Band), this field consists of the
17 following subfields which are included in the information
19
Length

20

22 equal to ‘00101’ (450 MHz NMT Band), this field consists of
23 the following subfields which are included in the information
25
2-738
3GPP2 C.S0005-A v6.0
Length


2 equal to ‘01010’ (Secondary 800 MHz band), this field consists
3 of the following subfields which are included in the
4 information record in the order shown:
Length


8 corresponding sub-band class is supported by the mobile
9 station; otherwise, the mobile station shall set the subfield to
10 ‘0’.
12 The mobile station shall set all reserved bits to ‘0’.
13 When more band subclasses are defined, the reserved bits will
14 be used for the new corresponding subfields. Sufficient octets
15 will be added to this field to accommodate the new subfields.
16 All the undefined bits in an additional octet will be reserved
17 bits.
18 The mobile station shall set all the reserved bits to ‘0’. If all
19 bits are set to ‘0’ in an octet and all succeeding octets, the
20 mobile station shall omit the octet and the succeeding octets.
21
2-739
3GPP2 C.S0005-A v6.0
1 2.7.4.31 Global Emergency Call
2 This information record identifies that an emergency call is being originated. This record
3 may be included in a Flash With Information Message or an Extended Flash With Information
4 Message and allows the user to originate an emergency call.
NUM_INCL 1
DIGIT_MODE 0 or 1
NUMBER_TYPE 0 or 3
NUMBER_PLAN 0 or 4
NUM_CHAR 0 or 8
If NUM_INCL is set to ‘1’ , include NUM_CHAR occurrences of
the following field:
CHARi 4 or 8
MS_ORIG_POS_LOC_IND 1
7 NUM_INCL – Dialed number included indicator.

8 The mobile station shall set this field to ‘1’ to indicate that the
9 dialed digits are included in this information record;
12 If NUM_INCL is set to ‘1’, the mobile station shall set this field
13 to indicate whether the dialed digits are 4-bit DTMF codes or
14 8-bit ASCII codes using a specified numbering plan;
21 If NUM_INCL is set to ‘1’ and the DIGIT_MODE field is set to
22 ‘1’, the mobile station shall set this field to the
23 NUMBER_TYPE value shown in Table 2.7.1.3.2.4-2
24 corresponding to the type of the called number, as defined in
25 [7], Section 4.5.9; otherwise, the mobile station shall omit this
26 field.
2-740
3GPP2 C.S0005-A v6.0
1 If NUM_INCL is set to ‘1’ and the DIGIT_MODE field is set to

2 ‘1’, the mobile station shall set this field to the
3 NUMBER_PLAN value shown in Table 2.7.1.3.2.4-3
4 corresponding to the numbering plan used for the called
5 number, as defined in [7], Section 4.5.9; otherwise, the mobile
7 NUM_CHAR – Number of characters.
8 If NUM_INCL is set to ‘1’, the mobile station shall set this field
9 to the number of characters included in this record;
12 If the NUM_INCL is set to ‘1’,The the mobile stations shall

13 include oneNUM_CHAR occurrences of this field for each
14 character in the called number.

16 set each occurrence of this field to the code value shown in
17 Table 2.7.1.3.2.4-4 corresponding to the dialed digit. If the
18 DIGIT_MODE field is set to ‘1’, Tthe mobile station shall set
20 corresponding to the character, as specified in [9], with the

32 bits to ‘0’.
2-741
3GPP2 C.S0005-A v6.0
1 2.7.4.32 Hook Status
2 This information record shall indicate the status of the hook switch in Wireless Local Loop
3 mobile stations. The mobile station shall use the following fixed-length format for the type-
4 specific fields:
HOOK_STATUS 4
RESERVED 4

8 The mobile station shall set this sub-field to the value shown
9 in Table 2.7.1.3.2.1-4 corresponding to the hook state.
2-742
3GPP2 C.S0005-A v6.0
1 2.7.4.33 QoS Parameters
2 This information record conveys to the user the QoS parameters associated with the service
3 to be provided:
QoS Parameters variable

5 QoS Parameters - Block containing the QoS Parameters.

6 The mobile station shall set this field to the QoS parameters
7 associated with the user (per subscription), service type (e.g.,
8 assured vs. non-assured services) and the service option. The
9 details of the QoS parameters may be found in documents
10 describing the service options.
11 RESERVED - Reserved bits for octet alignment.
12 The mobile station shall add the minimum number of bits
13 necessary to make the record length in bits an integral
14 multiple of 8. The mobile station shall set these bits to ‘0’.
2-743
3GPP2 C.S0005-A v6.0
1 2.7.4.34 Encryption Capability
2 This information record identifies the encryption capability of the mobile station.
SIG_ENCRYPT_SUP 8
UI_ENCRYPT_SUP 8
5 SIG_ENCRYPT_SUP – Signaling Encryption supported indicator.

6 The mobile station shall set this field to indicate which
7 signaling encryption algorithms are supported by the mobile
8 station, as shown in Table 2.7.1.3.2.1-5.
9 The mobile station shall set the subfields as follows:
16 ‘000000’.
18 The mobile station shall shall set this field to indicate the
19 supported user information encryption algorithms, as shown
20 in Table 2.7.1.3.2.4-9.

26 ‘000000’.
27
2-744
3GPP2 C.S0005-A v6.0
1 3. REQUIREMENTS FOR BASE STATION CDMA OPERATION
2 This section defines requirements that are specific to CDMA base station equipment and
3 operation.
4 3.1 Reserved
5 3.2 Reserved
6 3.3 Security and Identification
7 3.3.1 Authentication
8 The base station may be equipped with a database that includes unique mobile station
9 authentication keys, shared secret data, or both for each registered mobile station in the
10 system. This database is used for authentication of mobile stations that are equipped for
11 authentication operation.
12 If the base station supports mobile station authentication, it shall provide the following
13 capabilities: The base station shall send and receive authentication messages and perform
14 the authentication calculations described in 2.3.12.1. If the base station supports 800 MHz
15 analog operation, the base station should set the RAND parameter of the Access Parameters
16 Message to the same value transmitted on the forward analog control channel (see [6]).
17 3.3.2 Encryption
18 If the base station supports mobile station authentication (see 3.3.1), it may also support
19 message encryption by providing the capability to send encryption control messages and
20 the ability to perform the operations of encryption and decryption as specified in 2.3.12.2.
21 3.3.3 Voice Privacy
23 voice privacy using the private long code mask, as specified in 2.3.12.3.
24 3.3.4 Extended-Encryption
26 Extended-Encryption for Signaling Messages and User Information as specified in 2.3.12.4.
27 3.4 Supervision
28 3.4.1 Access Channel or Enhanced Access Channel
29 The base station shall continually monitor each active Access Channel or Enhanced Access
30 Channel or both. The base station should provide control in cases of overload by using
31 either the Access Parameters Message or the Enhanced Access Parameters Message.
32 3.4.2 Reverse Traffic Channel
33 The base station shall continually monitor each active Reverse Traffic Channel to determine
3-1
3GPP2 C.S0005-A v6.0
1 if the call is active. If the base station detects that the call is no longer active, the base
2 station shall declare loss of Reverse Traffic Channel continuity (see 3.6.4).
3 3.5 Reserved
4 3.6 Layer 3 Processing
5 This section describes base station layer 3Layer 3 processing. It contains frequent
6 references to the messages that flow between the base station and the mobile station.
7 While reading this section, it may be helpful to refer to the message formats (see 2.7 and
8 3.7), and to the call flow examples (see Annex B). The values for the time and numeric
9 constants used in this section (e.g., T1b and N4m) are specified in Annex D.
10 Base station processing consists of the following types of processing:
11 • Pilot and Sync Channel Processing - During Pilot and Sync Channel Processing, the
12 base station transmits the Pilot Channel and Sync Channel which the mobile station
13 uses to acquire and synchronize to the CDMA system while the mobile station is in
14 the Mobile Station Initialization State.
15 • Common Channel Processing - During Common Channel Processing, the base station
16 transmits the Paging Channel and/or the Forward Common Control
17 Channel/Broadcast Control Channel which the mobile station monitors to receive
18 messages while the mobile station is in the Mobile Station Idle State and the System
19 Access State.
20 • Access Channel and Enhanced Access Channel Processing - During Access Channel
21 and Enhanced Access Channel Processing, the base station monitors the Access
22 Channel and/or the Enhanced Access Channel to receive messages which the
23 mobile station sends while the mobile station is in the System Access State.
24 • Traffic Channel Processing - During Traffic Channel Processing, the base station uses
25 the Forward and Reverse Traffic Channels to communicate with the mobile station
26 while the mobile station is in the Mobile Station Control on the Traffic Channel State.
27 3.6.1 Pilot and Sync Channel Processing
28 During Pilot and Sync Channel Processing, the base station transmits the Pilot and Sync
29 Channels which the mobile station uses to acquire and synchronize to the CDMA system
30 while the mobile station is in the Mobile Station Initialization State.
31 3.6.1.1 Preferred Set of CDMA Channels
32 The preferred set of frequency assignments are the CDMA Channels on which the mobile
33 station attempts to acquire the CDMA system (see [2]).
34 The base station shall support at least one member of the preferred set of frequency
35 assignments. The base station may support additional CDMA Channels.
3-2
3GPP2 C.S0005-A v6.0
1 3.6.1.2 Pilot Channel Operation
2 The Pilot Channel (see [2]) is a reference channel which the mobile station uses for
3 acquisition, timing, and as a phase reference for coherent demodulation.
4 The base station shall continually transmit a Pilot Channel for every CDMA Channel
5 supported by the base station, unless the base station is classified as a hopping pilot
6 beacon.
7 3.6.1.3 Sync Channel Operation
8 The Sync Channel (see [2]) provides the mobile station with system configuration and
9 timing information.
10 The base station shall transmit at most one Sync Channel for each supported CDMA
11 Channel. The base station shall support a Sync Channel on at least one member of the
12 preferred set of frequency assignments that it supports. The base station should support a
13 Sync Channel on every member of the preferred set of frequency assignments that it
14 supports.
15 If the base station operates in Band Class 0 or Band Class 3, and supports the Primary
16 CDMA Channel, then the base station shall transmit a Sync Channel on the Primary CDMA
17 Channel.
18 The base station shall continually send the Sync Channel Message on each Sync Channel
19 that the base station transmits.
20 3.6.2 Common Channel Processing
21 3.6.2.1 Paging Channel and Forward Common Control Channel Procedures
22 During Common Channel Processing, the base station transmits the Paging Channel or the
23 Forward Common Control Channel (see [2]) which the mobile station monitors to receive
24 messages while the mobile station is in the Mobile Station Idle State and the System Access
25 State.
26 The base station may transmit up to seven Paging Channels on each supported CDMA
27 Channel. The base station may transmit up to seven Forward Common Control Channels
28 and one Primary Broadcast Control Channel on each supported CDMA Channel.
29 For each Paging Channel that the base station transmits, the base station shall continually
30 send valid Paging Channel messages (see 3.7.2), which may include the Null Message (see
31 [4]).
32 The base station shall not send any message which is not completely contained within two
33 consecutive Paging Channel or Forward Common Control Channel slots, unless the
34 processing requirements for the message explicitly specify a different size limitation.1
1See, for example, [14] which specifies processing requirements for the Data Burst Message.
3-3
3GPP2 C.S0005-A v6.0
1 3.6.2.1.1 CDMA Channel Determination
2 The base station may send the CDMA Channel List Message and the Extended CDMA
3 Channel List Message on the Paging Channel. When the base station supports Broadcast
4 Control Channel, the base station shall send the Extended CDMA Channel List Message on
6 To determine the mobile station’s assigned CDMA Channel, the base station first
7 determines a subset of CDMA channels in the Extended CDMA Channel List Message. The
8 subset of CDMA channels is based on where the mobile station receives the Extended CDMA
9 Channel List Message and the mobile station’s capabilities of supporting RC greater than 2,
10 Quick Paging Channel and transmit diversity, with which the mobile station is registered.
11 When the base station sends the CDMA Channel List Message on the Paging Channel, the
12 base station shall determine the assigned CDMA Channel for MOB_P_REVs less than six
13 using the hash function specified in 2.6.7.1 with the following inputs:
14 • IMSI_S based on the IMSI with which the mobile station registered (see 2.3.1)
15 • Number of CDMA Channels in the CDMA Channel List Message in accordance with
16 the procedures defined in 2.6.2.2.12.1 for mobile stations with:
17 – MOB_P_REVs less than six.
18 – MOB_P_REVs equal to six if the base station does not send the Extended CDMA
19 Channel List Message on the Paging Channel.
20 – MOB_P_REVs greater than or equal to seven, if the base station does not send
21 the Extended CDMA Channel List Message on the paging channel and does not
22 support Primary Broadcast Control Channel.
23 When the base station sends the Extended CDMA Channel List Message on the Paging
24 Channel, the base station shall determine the assigned CDMA Channel using the hash
25 function specified in 2.6.7.1 with the following inputs:
27 • Number of CDMA Channels of the selected channel subset of CDMA channels in the
28 Extended CDMA Channel List Message in accordance with the procedures defined in
29 2.6.2.2.12.1 for mobile stations with:
30 – MOB_P_REVs equal to six.
31 – MOB_P_REVs greater than or equal to seven, if the base station does not support
33 When the base station sends the Extended CDMA Channel List Message on the Primary
34 Broadcast Control Channel, the base station shall determine the assigned CDMA Channel
35 for MOB_P_REVs greater than or equal to seven using the hash function specified in 2.6.7.1
36 with the following inputs:
3-4
3GPP2 C.S0005-A v6.0
1 • Number of CDMA Channels of the selected channel subset of CDMA channels in the
2 Extended CDMA Channel List Message in accordance with the procedures defined in
3 2.6.2.2.12.2.
4 3.6.2.1.2 Common Channel Determination
5 To determine the mobile station’s assigned Paging Channel or Forward Common Control
6 Channel, the base station shall use the hash function specified in 2.6.7.1 with the following
7 inputs:
9 • Number of Paging Channels or Forward Common Control Channels which the base
10 station transmits on the mobile station’s assigned CDMA Channel.
11 3.6.2.1.3 Paging Slot Determination
12 To determine the assigned Paging Channel or Forward Common Control Channel slots for a
13 mobile station with a given slot cycle index, the base station shall select a number PGSLOT
14 using the hash function specified in 2.6.7.1 with the following inputs:
16 • Maximum number of Paging Channel or Forward Common Control Channel slots

17 (2048).
18 The assigned Paging Channel or Forward Common Control Channel slots for the mobile
19 station are those slots for which
20 (t/4  − PGSLOT) mod (16 × T) = 0,
21 where t is the System Time in frames, and T is the slot cycle length in units of 1.28 seconds
22 given by
23 T = 2i,
24 where i is the slot cycle index.
25 When the base station is able to determine that the mobile station is operating in the
26 slotted mode and is able to determine the mobile station’s preferred slot cycle index, the
27 base station uses for the mobile station’s slot cycle index the smaller of the mobile station’s
28 preferred slot cycle index and the maximum slot cycle index.
29 When the base station is not able to determine whether the mobile station is operating in
30 the slotted mode, or the base station is not able to determine the mobile station’s preferred
31 slot cycle index, the base station uses for the mobile station’s slot cycle index the smaller of
32 the maximum slot cycle index and 1.
33 3.6.2.1.4 Message Transmission and Acknowledgment Procedures
34 The Paging Channel or Forward Common Control Channel acknowledgment procedures

35 facilitate the reliable exchange of messages between the base station and the mobile station
36 on the f-csch and r-csch. The acknowledgment procedures and requirements are described
37 in 3.1.1.2 and 3.1.2.1 of [4].
3-5
3GPP2 C.S0005-A v6.0
1 3.6.2.2 Overhead Information
2 The base station sends overhead messages to provide the mobile station with the
3 information that it needs to operate with the base station. If the base station supports the
4 Primary Broadcast Control Channel for overhead messages and is not a pilot beacon, it
5 shall support the Forward Common Control Channel for all other general page information.
6 The base station with a P_REV greater than six that supports Broadcast Control Channel
7 shall send overhead messages on the Primary Broadcast Control Channel. The base station
8 with a P_REV greater than six that does not support the Broadcast Control Channel shall
9 send overhead messages on each Paging Channel. The overhead messages sent on the
10 Primary Broadcast Control Channel are:
12 2. User Zone Identification Message
13 3. Private Neighbor List Message
15 5. Extended CDMA Channel List Message
19 9. ANSI-41 RAND Message
20 The overhead messages on the Paging Channel are:

22 2. Neighbor List Message (Band Class 0 only)
24 4. CDMA Channel List Message
26 6. Extended Neighbor List Message (band classes other than Band Class 0)
33 The base station shall maintain a configuration sequence number (CONFIG_SEQ) for
34 configuration messages transmitted on the Paging Channel, and shall increment
35 CONFIG_SEQ modulo 64 whenever the base station modifies the following messages:
3-6
3GPP2 C.S0005-A v6.0
2 2. Neighbor List Message (Band Class 0 only)
5 5. Extended Neighbor List Message (band classes other than Band Class 0)
12 The base station shall maintain a configuration sequence number (CONFIG_SEQ) for
13 configuration messages transmitted on the Primary Broadcast Control Channel, and shall
14 increment CONFIG_SEQ modulo 64 whenever the base station modifies the following
15 messages:
23 The base station shall maintain an access configuration sequence number

24 (ACC_CONFIG_SEQ) for the Access Channel, and shall increment ACC_CONFIG_SEQ
25 modulo 64 whenever the base station modifies the Access Parameters Message.
26 The base station shall maintain an access configuration sequence number

27 (ACC_CONFIG_SEQ) for the Enhanced Access Channel, and shall increment
28 ACC_CONFIG_SEQ modulo 64 whenever the base station modifies the Enhanced Access
29 Parameters Message.
30 On each Primary Broadcast Control Channel which the base station transmits, the base
31 station shall send each of the following system overhead messages at least once per T1b
32 seconds:
3-7
3GPP2 C.S0005-A v6.0
3 If the base station supports Primary Broadcast Control Channels, and the base station is
4 sending the ANSI-41 RAND Message, it shall send it at least once per T1b seconds.
5 On each of the Paging Channels the base station transmits, the base station shall send
6 each of the following system overhead messages at least once per T1b seconds:
11 For the messages sent on the Paging Channel, if the base station is operating in Band Class
12 1, Band Class 3, or Band Class 4 BAND_CLASS is equal to ‘00001’ or BAND_CLASS is equal
13 to ‘00011’ and MIN_P_REV is less than seven six, the base station shall send the Extended
14 Neighbor List Message, and may also send the General Neighbor List Message. If the base
15 station is operating in Band Class 0 and MIN_P_REV is less than sevenBAND_CLASS is
16 equal to ‘00000’, the base station shall send the Neighbor List Message, and may also send
17 the General Neighbor List Message. If the base station is sending the Neighbor List Message,
18 it shall send it at least once per T1b seconds. If the base station is sending the Extended
19 Neighbor List Message, it shall send it at least once per T1b seconds. If the base station is
20 sending the General Neighbor List Message, it shall send it at least once per T1b seconds.
21 Overhead Messages sent on the Primary Broadcast Control Channel shall be transmitted on
22 a continuous basis, consecutively.
23 If the base station uses addressing modes requiring use of only the IMSI_M_S, independent
24 of values of the IMSI_M_11_12 and MCC_M, the base station shall set IMSI_T_SUPPORTED
25 to ‘0’, MCC to ‘1111111111’, and IMSI_11_12 to ‘1111111’ in the Extended System
26 Parameters Message, MC-RR Parameters Message, and ANSI-41 System Parameters
27 Message.
28 If the base station sets IMSI_T_SUPPORTED to ‘1’, the base station shall not set
29 PREF_MSID_TYPE to ‘00’ in the Extended System Parameters Message and ANSI-41 System
30 Parameters Message.
31 The base station may send a Global Service Redirection Message on any given Paging
32 Channel. If the message is sent, the base station shall send it at least once per T1b
33 seconds.
34 If P_REV is greater than or equal to six, the base station may send an Extended Global
35 Service Redirection Message. If the message is sent, the base station shall send it at least
36 once per T1b seconds. The base station may send this message to redirect only those
37 mobile stations with MOB_P_REV equal to or greater than six.
38 When both the Global Service Redirection Message and the Extended Global Service
39 Redirection Message are sent, the base station shall use the Global Service Redirection
40 Message for mobile stations with MOB_P_REV less than six, and shall use the Extended
3-8
3GPP2 C.S0005-A v6.0
1 Global Service Redirection Message for mobile stations with MOB_P_REV equal to or greater
2 than six. When only the Global Service Redirection Message is sent and this message is for
3 mobile station with MOB_P_REV less then six, the base station shall set EXCL_P_REV_MS
4 to ‘1’.
5 If only the Global Service Redirection Message is sent and this message is for redirecting all
6 mobile stations, the base station shall set EXCL_P_REV_MS to ‘0’.
7 The base station may send a User Zone Identification Message. If the message is sent, the
8 base station shall send it at least once per T1b seconds.
9 The base station may send a Private Neighbor List Message. If the message is sent, the base
10 station shall send it at least once per T1b seconds.
11 The base station may send an Extended CDMA Channel List Message. If the message is sent,
12 the base station shall send it at least once per T1b seconds.
13 3.6.2.3 Mobile Station Directed Messages
14 The base station may send the following messages directed to a mobile station on the f-
15 csch. If the base station sends a message, the base station shall comply with the specified
16 requirements for sending the message, if any:
17 1. Abbreviated Alert Order
18 2. Audit Order
19 3. Authentication Challenge Message
20 4. Base Station Challenge Confirmation Order
21 5. Channel Assignment Message
23 7. Extended Channel Assignment Message
24 8. Feature Notification Message
25 9. General Page Message
26 10. Intercept Order
28 12. Lock Until Power-Cycled Order
29 13. Maintenance Required Order
30 14. PACA Message
31 15. Registration Accepted Order
32 16. Registration Rejected Order
33 17. Registration Request Order
34 18. Release Order
35 19. Reorder Order
3-9
3GPP2 C.S0005-A v6.0
1 20. Retry Order
2 21. Security Mode Command Message
3 22. Service Redirection Message
4 23. Service Release Message
5 24. Slotted Mode Order
6 25. SSD Update Message
7 26. Status Request Message
8 27. TMSI Assignment Message
9 28. Universal Page Message (Forward Common Control Channel Only)
10 29. Unlock Order
12 The base station should send at least one General Page Message in each Paging Channel
13 slot. The base station shall not omit a General Page Message in two adjacent Paging
14 Channel slots.
15 The base station should send at least one General Page Message or Universal Page Message
16 in each Forward Common Control Channel slot. The base station shall not omit both a
17 General Page Message and a Universal Page Message in two adjacent slots.
18 3.6.2.3.1 Processing when the General Page Message is Used
19 The base station shall use the following rules for selecting the Paging Channel or Forward
20 Common Control Channel slot in which to send a message to a mobile station:
21 • If the base station is able to determine that the mobile station is operating in the
22 non-slotted mode, the base station may send the message to the mobile station in
23 any Paging Channel or Forward Common Control Channel slot.
25 slotted mode and is able to determine the mobile station’s slot cycle index (see
26 2.6.2.1.1.3), the base station shall send the message at least once in an assigned
27 Paging Channel slot for the mobile station (see 3.6.2.1.3), with the position within
28 the slot subject to the following limitations:
29 – If the mobile station has registered with a class 0 IMSI, the base station shall
30 not send the message in the assigned Paging Channel slot after sending a
31 General Page Message with CLASS_0_DONE set to ‘1’ in that slot.
33 not send the message in the assigned Paging Channel slot after sending a
34 General Page Message with CLASS_1_DONE set to ‘1’ in that slot.
35 – If the mobile station has been assigned a TMSI, the base station shall not send
36 the message in the assigned Paging Channel slot after sending a General Page
37 Message with TMSI_DONE set to ‘1’ in that slot.
3-10
3GPP2 C.S0005-A v6.0
2 slotted mode and that the mobile station is not waiting for a priority access channel
3 assignment and that the slotted timer in the mobile station is not active, and the
4 base station is able to determine the mobile station’s slot cycle index (see
5 2.6.2.1.1.3), the base station shall send the message at least once in an assigned
6 Forward Common Control Channel slot for the mobile station (see 3.6.2.1.3), with
7 the position within the slot subject to the following limitations:
9 not send the message in the assigned Forward Common Control Channel slot
10 after sending a General Page Message with CLASS_0_DONE set to ‘1’ in that slot.
12 not send the message in the assigned Forward Common Control Channel slot
13 after sending a General Page Message with CLASS_1_DONE set to ‘1’ in that slot.
15 the message in the assigned Forward Common Control Channel slot after
16 sending a General Page Message with TMSI_DONE set to ‘1’ in that slot.
18 slotted mode and that the mobile station is waiting for a priority access channel
19 assignment, or that the slotted timer in the mobile station is active, the base station
20 may send the message to the mobile station in any Forward Common Control
21 Channel slot with the position within the slot subject to the following limitation:
23 not send the message in any Forward Common Control Channel slot after
24 sending a General Page Message with CLASS_0_DONE set to ‘1’ in that slot.
26 not send the message in any Forward Common Control Channel slot after
27 sending a General Page Message with CLASS_1_DONE set to ‘1’ in that slot.
29 the message in any Forward Common Control Channel slot after sending a
30 General Page Message with TMSI_DONE set to ‘1’ in that slot.
31 • If the base station is not able to determine whether the mobile station is operating in
32 the non-slotted mode, or the base station is not able to determine the mobile
33 station’s slot cycle index, the base station shall assume that the mobile station is
34 operating in the slotted mode with a slot cycle index which is the smaller of
35 MAX_SLOT_CYCLE_INDEX and 1. The base station shall send the message at least
36 once in an assigned Paging Channel or Forward Common Control Channel slot for
37 the mobile station (see 3.6.2.1.3), with the position within the slot subject to the
38 following limitations:
40 not send the message in the assigned Paging Channel or Forward Common
41 Control Channel slot after sending a General Page Message with CLASS_0_DONE
42 set to ‘1’ in that slot.
3-11
3GPP2 C.S0005-A v6.0
2 not send the message in the assigned Paging Channel or Forward Common
3 Control Channel slot after sending a General Page Message with CLASS_1_DONE
4 set to ‘1’ in that slot.
6 the message in the assigned Paging Channel or Forward Common Control
7 Channel slot after sending a General Page Message with TMSI_DONE set to ‘1’ in
8 that slot.
9 The base station should send messages directed to mobile stations operating in the slotted
10 mode as the first messages in the slot.
11 If the base station sends a General Page Message with ORDERED_TMSIS set to ‘1’ in a slot,
12 the base station shall order page records with PAGE_CLASS equal to ‘10’ in ascending order
13 such that if a particular TMSI_CODE value for one page record is greater than the
14 TMSI_CODE value for another page record, the page record with the greater TMSI_CODE
15 value is sent later in the slot.
16 3.6.2.3.2 Processing when the Universal Page Message is Used
17 The base station shall use the following rules for selecting the Forward Common Control
18 Channel slot in which to send a message to a mobile station:
20 non-slotted mode, the base station may send the message to the mobile station in
21 any Forward Common Control Channel slot.
22 • If the base station is able to determine that the mobile station is capable of
23 operating in the slotted mode and that the mobile station is waiting for a priority
24 access channel assignment, or that the slotted timer in the mobile station is active,
25 the base station may send the message to the mobile station in any Forward
26 Common Control Channel slot with the position within the slot subject to the
27 following limitation:
28 – The base station shall not send the message later in the slot than a Universal
29 Page Message which lacks a mobile station-directed message announcement and
30 which lacks a mobile station-addressed page (see 3.7.2.3.2.25) for that mobile
31 station.
33 slotted mode and that the mobile station is not waiting for a priority access channel
34 assignment and that the slotted timer in the mobile station is not active and the
35 base station is able to determine the mobile station’s slot cycle index (see
36 2.6.2.1.1.3.3), the base station shall send the message at least once in an assigned
37 Forward Common Control Channel slot for the mobile station (see 3.6.2.1.3) or in
38 the following slot, with the position within these two slots subject to the following
39 limitation:
3-12
3GPP2 C.S0005-A v6.0
2 Page Message that lacks a mobile station-directed message announcement and
4 station.
5 • If the base station is not able to determine whether the mobile station is operating in
6 the non-slotted mode, or the base station is not able to determine the mobile
7 station’s slot cycle index, the base station shall assume that the mobile station is
8 operating in the slotted mode with a slot cycle index which is the smaller of
9 MAX_SLOT_CYCLE_INDEX and 1. The base station shall send the message at least
10 once in an assigned Forward Common Control Channel slot for the mobile station
11 (see 3.6.2.1.3), or in the following slot, with the position within these two slots
12 subject to the following limitation:
14 Page Message that lacks a mobile station-directed message announcement and
16 station.
17 The base station should send messages directed to both mobile stations operating in the
18 slotted mode and mobile stations operating in the non-slotted mode later in the slot than
19 the Universal Page Message.
20 3.6.2.4 Broadcast Messages
21 3.6.2.4.1 Broadcast Messages Sent on the Paging Channel
22 The base station may transmit Data Burst Messages directed to broadcast addresses. When
23 transmitting broadcast messages that are to be received by mobile stations operating in the
24 slotted mode, the base station may use broadcast page records (see 3.7.2.3.2.17) in
25 accordance with the broadcast procedures specified in 3.6.2.4.1 to announce the presence
26 of broadcast Data Burst Messages on the Paging Channel. The base station should use the
27 rules specified in 3.6.2.4.1.1 for selecting the Paging Channel slot in which to send a
28 broadcast Data Burst Message.
29 3.6.2.4.1.1 Broadcast Procedures for Slotted Mode
30 The base station may announce the presence of broadcast Data Burst Messages on the
31 Paging Channel by paging, using a broadcast address with PAGE_CLASS equal to ‘11’ and
32 PAGE_SUBCLASS equal to ‘00’.
33 3.6.2.4.1.1.1 General Overview
34 The base station may transmit Data Burst Messages directed to broadcast addresses. Since
35 mobile stations operating in slotted mode do not constantly monitor a Paging Channel, it is
36 necessary to use special procedures to ensure that mobile stations operating in the slotted
37 mode are able to receive the message. The base station may either send a broadcast
38 message in many slots, or may send a broadcast message in a predetermined paging slot.
39 This single transmission of the pending broadcast message may be announced by a
3-13
3GPP2 C.S0005-A v6.0
1 preceding “broadcast page”. A broadcast page is a General Page Message record with the
2 PAGE_CLASS field set to ‘11’.
3 If pending transmission of the broadcast message is announced by the broadcast page,

4 mobile stations use the BC_ADDR and the BURST_TYPE fields of the broadcast page record
5 to determine whether or not to receive the announced broadcast message. The base station
6 sets the value of the BC_ADDR according to the requirements of the standards related to
7 the BURST_TYPE. There is a predetermined timing relationship between the sending of the
8 broadcast page and the sending of the related broadcast message. This timing relationship
9 allows mobile stations to determine which slot to monitor in order to receive the broadcast
10 message.
11 To reduce the overhead for sending broadcast pages or broadcast messages, a base station
12 may use periodic broadcast paging (see 3.6.2.4.1.2.1.2). When periodic broadcast paging is
13 enabled, broadcast pages or broadcast messages are sent only once during a broadcast
14 paging cycle. Mobile stations that are operating in the slotted mode and are configured to
15 receive broadcast messages monitor the paging channel during the slot in which the
16 broadcast pages or broadcast messages are sent. For the purpose of periodic broadcast
17 paging, system time is divided into broadcast paging cycles, each having a duration of (B +
18 3) Paging Channel slots, where B is a power of two. In each broadcast paging cycle, the
19 first paging slot may contain broadcast pages or broadcast messages.
20 3.6.2.4.1.1.2 Requirements for Sending Broadcast Messages
21 3.6.2.4.1.1.2.1 Broadcast Delivery Options
22 When transmitting broadcast messages that are to be received by mobile stations operating
23 in the slotted mode and monitoring the Paging Channel, the base station shall use one of
24 the two following procedures to transmit a broadcast message.
25 3.6.2.4.1.1.2.1.1 Method 1: Multi-Slot Broadcast Message Transmission
26 The base station may send a broadcast message using this method without regard to
27 whether periodic broadcast paging is enabled or disabled (see 3.6.2.4.1.2.3).
28 When using this method, the base station shall send the broadcast message in a sufficient
29 number of paging slots such that it may be received by any mobile station that is operating
30 in the slotted mode. For example, the base station may send the broadcast message in M
31 successive paging slots where M is the number of slots in a maximum paging cycle as
32 defined in 2.6.2.1.1.3.3.
33 3.6.2.4.1.1.2.1.2 Method 2: Periodic Broadcast Paging
34 If the base station sends a broadcast message using this method, then the base station
35 shall enable periodic broadcast paging (see 3.6.2.4.1.2.3).
36 To deliver a broadcast message using this method, the base station should perform the
37 following:
3-14
3GPP2 C.S0005-A v6.0
1 • If the number and size of the broadcast messages waiting to be sent are such that
2 the messages can be sent in a single slot, the base station should send the
3 broadcast messages in the first slot of the next broadcast paging cycle (see
4 2.6.2.1.1.3.3).
5 • If there is a single broadcast message waiting to be sent, the base station should
6 send the broadcast message beginning in the first slot of the next broadcast paging
7 cycle (see 2.6.2.1.1.3.3).
8 • Otherwise, the base station should first include a broadcast page for each broadcast
9 message to be sent, in a General Page Message that is sent in the first slot of the
10 next broadcast paging cycle (see 2.6.2.1.1.3.3). The base station should then send
11 the related broadcast messages in the paging slots specified in 3.6.2.4.1.2.4.
12 3.6.2.4.1.1.2.2 Duplicate Broadcast Message Transmission
13 If the base station sends a broadcast message or a broadcast page and an associated
14 broadcast message more than once when periodic broadcast paging is enabled (see
15 3.6.2.4.1.2.3), then all repetitions of the broadcast message or the broadcast page and the
16 associated broadcast message should be sent within 4 × (B + 3) paging slots of the paging
17 slot in which the broadcast message or broadcast page was first sent. (B + 3 is the duration
18 of the broadcast paging cycle as defined in 2.6.2.1.1.3.3).
19 When a base station sends a broadcast message or a broadcast page when periodic
20 broadcast paging is enabled (see 3.6.2.4.1.2.3), and the base station has a second, different
21 broadcast message to send which contains identical BURST_TYPE and BC_ADDR fields,
22 then the base station shall wait 4 × (B + 3) paging slots after the first slot of the broadcast
23 paging cycle containing the final sending of the first broadcast message or broadcast page
24 before sending the second, different broadcast message or related broadcast page.
25 3.6.2.4.1.1.2.3 Periodic Broadcast Paging

26 The base station uses the BCAST_INDEX field of the Extended System Parameters Message
27 to specify the current state of periodic broadcast paging to all mobile stations.
28 To enable periodic broadcast paging, the base station shall set the BCAST_INDEX field of
29 the Extended System Parameters Message to an unsigned 3-bit number in the range 1-7,
30 equal to the broadcast slot cycle index as defined in 2.6.2.1.1.3.3. The value of the
31 BCAST_INDEX field may exceed the value of the MAX_SLOT_CYCLE_INDEX field sent in the
32 System Parameters Message.
33 To indicate that periodic broadcast paging is either disabled or is not supported by the base
34 station, the base station shall set the BCAST_INDEX field to ‘000’.
35 3.6.2.4.1.1.2.4 Broadcast Message Slot Determination
36 When a base station uses broadcast paging, it shall determine the slot in which to send the
37 corresponding broadcast message using the following procedures:
38 • The base station shall consider a broadcast page to have been sent in the paging
39 slot in which the General Page Message containing the broadcast page began.
3-15
3GPP2 C.S0005-A v6.0
1 • The reference slot is defined as the paging slot in which the broadcast page was
2 sent.
3 • Let n represent the ordinal number of the broadcast page relative to other broadcast
4 pages that are contained in the same General Page Message (n = 1, 2, 3,...). The
5 base station shall send the broadcast message announced by broadcast page n in
6 the paging slot that occurs n × 3 paging slots after the reference slot.
7 3.6.2.4.2 Broadcast Messages Sent on the Broadcast Control Channel

8 The base station may transmit Data Burst Messages directed to broadcast addresses. When
9 transmitting broadcast messages that are to be received by mobile stations operating in the
10 slotted mode, the base station may use enhanced broadcast pages (see 3.7.2.3.2.17) in
11 accordance with the broadcast procedures specified in 3.6.2.4.2 to announce the presence
12 of broadcast Data Burst Messages on the Broadcast Control Channel. The base station
13 should use the rules specified in 3.6.2.4.2.1 for selecting the Broadcast Control Channel
14 slot in which to send a broadcast Data Burst Message.
15 3.6.2.4.2.1 Broadcast Procedures for Slotted Mode
16 The base station may announce the presence of broadcast Data Burst Messages on the
17 Broadcast Control Channel by sending an enhanced broadcast page.
18 3.6.2.4.2.1.1 General Overview

19 The base station may transmit Data Burst Messages directed to broadcast addresses. Since
20 mobile stations operating in slotted mode do not constantly monitor a Broadcast Control
21 Channel, it is necessary to use special procedures to ensure that mobile stations operating
22 in the slotted mode are able to receive the message. The base station may either send an
23 enhanced broadcast page in many Forward Common Control Channel slots, directing the
24 mobile station to the appropriate Broadcast Control Channel slot, or the base station may
25 also send an enhanced broadcast page in a predetermined slot, called a broadcast slot, on
26 the Forward Common Control Channel, directing the mobile station to a specified Broadcast
27 Control Channel slot.
28 If pending transmission of the broadcast message is announced by the enhanced broadcast

29 page, mobile stations use the BC_ADDR and the BURST_TYPE fields of the enhanced
30 broadcast page record to determine whether or not to receive the announced broadcast
31 message. The base station sets the value of the BC_ADDR according to the requirements of
32 the standards related to the BURST_TYPE. The timing relationship between the sending of
33 the enhanced broadcast page and the sending of the related broadcast message is specified
34 in the enhanced broadcast page. This timing relationship allows mobile stations to
35 determine which Broadcast Control Channel slot to monitor in order to receive the
36 broadcast message.
37 To reduce the overhead for sending broadcast pages or broadcast messages, a base station
38 may use Periodic Enhanced Broadcast Paging (see 3.6.2.4.2.2.1.2). When Periodic
39 Enhanced Broadcast Paging is enabled, enhanced broadcast pages are sent only once
40 during a broadcast paging cycle. Mobile stations that are operating in the slotted mode and
41 are configured to receive broadcast messages monitor the Forward Common Control
3-16
3GPP2 C.S0005-A v6.0
1 Channel during the broadcast slot in which the enhanced broadcast pages are sent. For
2 the purpose of Periodic Enhanced Broadcast Paging, system time is divided into broadcast
3 paging cycles, each having a duration of (B + 7) Forward Common Control Channel slots,
4 where B is a power of two. In each broadcast paging cycle, the first Forward Common
5 Control Channel slot may contain enhanced broadcast pages.
6 3.6.2.4.2.1.2 Requirements for Sending Broadcast Messages
7 3.6.2.4.2.1.2.1 Broadcast Delivery Options
8 When transmitting broadcast messages that are to be received by mobile stations operating
9 in the slotted mode and monitoring the Forward Common Control Channel/Broadcast
10 Control Channel, the base station shall use one of the two following procedures to transmit
11 a broadcast message.
12 3.6.2.4.2.1.2.1.1 Method 1: Multi-Slot Enhanced Broadcast Paging
13 The base station may send a broadcast message using this method without regard to
14 whether Periodic Enhanced Broadcast Paging is enabled or disabled (see 3.6.2.4.2.2.3).
15 When using this method, the base station shall send the enhanced broadcast page in a
16 sufficient number of Forward Common Control Channel slots such that it may be received
17 by any mobile station that is operating in the slotted mode. The enhanced broadcast page
18 then directs mobile stations to a subsequent Broadcast Control Channel slot.
19 The base station shall not send an enhanced broadcast page that directs a mobile station to
20 receive a broadcast message on the Primary Broadcast Control Channel.
21 The base station shall not send a broadcast message on the Forward Common Control
22 Channel.
23 3.6.2.4.2.1.2.1.2 Method 2: Periodic Enhanced Broadcast Paging
24 If the base station sends a broadcast message using this method, then the base station
25 shall enable Periodic Enhanced Broadcast Paging (see 3.6.2.4.2.2.3).
26 To deliver a broadcast message using this method, the base station should perform the
27 following:
28 • The base station should first include an enhanced broadcast page for each
29 broadcast message to be sent, in a page that is sent on the Forward Common
30 Control Channel in the first slot of the next broadcast paging cycle (see
31 2.6.2.1.1.3.3). The base station should then send the corresponding broadcast
32 messages in the Broadcast Control Channel slots specified in 3.6.2.4.2.2.4.
33 The base station shall not send an enhanced broadcast page that directs a mobile station to
34 receive a broadcast message on the Primary Broadcast Control Channel.
35 The base station shall not send a broadcast message on the Forward Common Control
36 Channel.
3-17
3GPP2 C.S0005-A v6.0
1 3.6.2.4.2.1.2.2 Duplicate Broadcast Message Transmission
2 If the base station sends an enhanced broadcast page and an associated broadcast message
3 more than once when Periodic Enhanced Broadcast Paging is enabled (see 3.6.2.4.2.2.3),
4 then all repetitions of the enhanced broadcast page should be sent within 4 × (B + 7) slots
5 of the slot in which the enhanced broadcast page was first sent. (B + 7 is the duration of
6 the broadcast paging cycle as defined in 2.6.2.1.1.3.3).
7 When a base station sends an enhanced broadcast page when Periodic Enhanced Broadcast
8 Paging is enabled (see 3.6.2.4.2.2.3), and the base station has a second, different broadcast
9 message to send which contains identical BURST_TYPE and BC_ADDR fields, then the base
10 station shall wait 4 × (B + 7) paging slots after the first slot of the broadcast paging cycle
11 containing the final sending of the first broadcast message or enhanced broadcast page
12 before sending the second, different enhanced broadcast page.
13 3.6.2.4.2.1.2.3 Periodic Enhanced Broadcast Paging

14 The base station uses the BCAST_INDEX fields of the MC-RR Parameters Message to specify
15 the current state of Periodic Enhanced Broadcast Paging to all mobile stations.
16 To enable Periodic Enhanced Broadcast Paging, the base station shall set the
17 BCAST_INDEX field to a non-zero unsigned 3-bit number equal to the broadcast slot cycle
18 index as defined in 2.6.2.1.1.3.3.
19 To indicate that Periodic Enhanced Broadcast Paging is either disabled or is not supported
20 by the base station, the base station shall set the BCAST_INDEX field to ‘000’.
21 3.6.2.4.2.1.2.4 Broadcast Message Slot Determination
22 When a base station uses broadcast message announcement, it shall determine the slot in
23 which to send the corresponding broadcast message using the following procedures:
24 • The base station shall consider an enhanced broadcast page to have been sent in
25 the Forward Common Control Channel slot in which the page message containing
26 the enhanced broadcast page began.
27 • The reference slot is defined as the Forward Common Control Channel slot in which
28 the enhanced broadcast page was sent.
29 • The base station shall send a first transmission of the broadcast message
30 announced by the enhanced broadcast page in the Broadcast Control Channel slot
31 which begins 40 ms × (1 + TIME_OFFSET) later than the beginning of the slot in
32 which the page message containing the enhanced broadcast page began. The base
33 station may send a repetition of the broadcast message announced by the enhanced
34 broadcast page in the Broadcast Control Channel slot which begins 40 ms × (1 +
35 REPEAT_TIME_OFFSET) later than the Broadcast Control Channel slot in which the
36 first transmission began.
37 3.6.2.5 Quick Paging Channel Processing
38 The base station may support a Quick Paging Channel. The base station may transmit up
39 to three Quick Paging Channels on each supported CDMA Channel.
3-18
3GPP2 C.S0005-A v6.0
1 When a Quick Paging Channel is supported, the base station shall transmit paging
2 indicators to the mobile station in the assigned positions in the assigned Quick Paging
3 Channel slot. The base station shall set the paging indicators to “ON” if the mobile station
4 is operating in the slotted mode and is to receive the Paging Channel or Forward Common
5 Control Channel in the assigned Paging Channel or Forward Common Control Channel slot
6 following its assigned Quick Paging Channel slot.
7 When the base station changes CONFIG_MSG_SEQ, the base station should set the paging
8 indicators for all mobile stations to “ON” for each Quick Paging Channel slot for a time
9 interval T (in units of 1.28 seconds), such that
10 T = N × 2MAX_SLOT_CYCLE_INDEX,
11 where N is an integer greater than or equal to one.
12 If the base station supports configuration change indicators on the Quick Paging Channel,
13 when the base station changes CONFIG_MSG_SEQ, the base station shall set all
14 configuration change indicators to “ON” for each Quick Paging Channel slot for a time
15 interval of T31m seconds. At all other times, the base station shall set all configuration
16 change indicators to “OFF”.
17 If the base station does not support configuration change indicators on the Quick Paging
18 Channel, then the base station shall set all configuration change indicators to “OFF”.
19 When the base station sends a broadcast message using Multi-Slot Broadcast Message
20 Transmission (see 3.6.2.4.1.1.2.1.1 3.6.2.4.1.2.1.1), the base station should set all paging
21 indicators to “ON” for the Quick Paging Channel slot which begins 100 ms prior to the
22 beginning of the Paging Channel slot in which the broadcast message begins.
23 When the base station sends an enhanced broadcast page using Multi-Slot Enhanced
24 Broadcast Paging (see 3.6.2.4.2.1.2.1.1), the base station should set all paging indicators to
25 “ON” for the Quick Paging Channel slot which begins 100 ms prior to the beginning of the
26 Forward Common Control Channel slot in which the message containing the enhanced
27 broadcast page begins.
28 When the base station sends an enhanced broadcast page using Periodic Enhanced
29 Broadcast Paging (see 3.6.2.4.2.1.2.1.2), the base station should set all broadcast indicators
30 to “ON” for the Quick Paging Channel broadcast slot which begins 100 ms prior to the
31 beginning of the Forward Common Control Channel slot in which the message containing
32 the enhanced broadcast page begins. At all other times, the base station shall set all
33 broadcast indicators for a Quick Paging Channel broadcast slot to “OFF”.
34 The base station shall set all reserved indicators to “OFF”.
35 3.6.2.5.1 Quick Paging Channel Determination
36 To determine the mobile station’s assigned Quick Paging Channel, the base station shall
37 use the hash function specified in 2.6.7.1 with the following inputs:
39 • Number of Quick Paging Channels which the base station transmits on the mobile
40 station’s assigned CDMA Channel.
3-19
3GPP2 C.S0005-A v6.0
1 3.6.2.5.2 Quick Paging Channel Slot Determination
2 The mobile station’s assigned Quick Paging Channel slots are those slots for which
3 ((t+5)/4 − PGSLOT) mod (16 × T) = 0,
4 where t is the System Time in frames, PGSLOT is selected in the range 0 to 2047 by using
5 the hash function specified in 2.6.7.1, and T is the slot cycle length in units of 1.28 seconds
6 such that
7 T = 2i,
8 and i is the slot cycle index.
9 3.6.2.5.3 Paging Indicator Position Determination
10 To determine the mobile station’s assigned paging indicators, the base station shall use the
11 same formula as used by the mobile station (see 2.6.2.1.2.2).
12 3.6.2.5.4 Configuration Change Indicator Position Determination
13 Configuration change indicators are transmitted on the first Quick Paging Channel.
15 positions of the first pair of configuration change indicators in a Quick Paging Channel slot
16 shall be the last two bits in the first 40 ms half of the Quick Paging Channel slot. The bit
17 positions of the second pair of configuration change indicators in a Quick Paging Channel
18 slot shall be the last two bits in the Quick Paging Channel slot.
20 positions of the first four configuration change indicators in a Quick Paging Channel slot
21 shall be the last four bits in the first 40 ms half of the Quick Paging Channel slot. The bit
22 position of the second four configuration change indicators in a Quick Paging Channel slot
23 shall be the last four bits in the Quick Paging Channel slot.
24 3.6.2.5.5 Broadcast Indicator Position Determination
25 Broadcast indicators are transmitted on the first Quick Paging Channel.
26 On the first Quick Paging Channel, if the Quick Paging Channel data rate is 2400 bps
27 (indicator rate is 4800 bps), the broadcast indicator positions are described as follows:
28 • The two Quick Paging Channel bit positions prior to the last two bits in the first 40
29 ms half of a Quick Paging Channel broadcast slot are broadcast indicators. The two
30 Quick Paging Channel bit positions prior to the last two bits in a Quick Paging
31 Channel broadcast slot are also broadcast indicators.
33 (indicator rate is 9600 bps), the broadcast indicator positions are described as follows:
34 • The four Quick Paging Channel bit positions prior to the last four bits in the first 40
35 ms half of a Quick Paging Channel broadcast slot are broadcast indicators. The four
36 Quick Paging Channel bit positions prior to the last four bits in a Quick Paging
37 Channel broadcast slot are also broadcast indicators.
3-20
3GPP2 C.S0005-A v6.0
1 3.6.2.5.6 Reserved Indicator Positions
3 (indicator rate is 4800 bps), the reserved indicator positions are described as follows:
4 • The two Quick Paging Channel bit positions prior to the last two bits in the first 40
5 ms half of a Quick Paging Channel slot that is not a Quick Paging Channel
6 Broadcast slot are reserved. The two Quick Paging Channel bit positions prior to
7 the last two bits in a Quick Paging Channel slot that is not a Quick Paging Channel
8 Broadcast slot are also reserved.
10 (indicator rate is 9600 bps), the reserved indicator positions are described as follows:
11 • The four Quick Paging Channel bit positions prior to the last four bits in the first 40
12 ms half of a Quick Paging Channel slot that is not a Quick Paging Channel
13 Broadcast slot are reserved. The four Quick Paging Channel bit positions prior to
14 the last four bits in a Quick Paging Channel slot that is not a Quick Paging Channel
15 Broadcast slot are also reserved.
16 On Quick Paging Channels other than the first Quick Paging Channel, if the Quick Paging
17 Channel data rate is 2400 bps (indicator rate is 4800 bps), the reserved indicator positions
18 are described as follows:
19 • The last four Quick Paging Channel bit positions in the first 40 ms half of a Quick
20 Paging Channel slot are reserved. The last four Quick Paging Channel bit positions
21 in a Quick Paging Channel slot are also reserved.
22 On Quick Paging Channels other than the first Quick Paging Channel, if the Quick Paging
23 Channel data rate is 4800 bps (indicator rate is 9600 bps), the reserved indicator positions
24 are described as follows:
25 • The last eight Quick Paging Channel bit positions in the first 40 ms half of a Quick
26 Paging Channel slot are reserved. The last eight Quick Paging Channel bit positions
27 in a Quick Paging Channel slot are also reserved.
28 3.6.3 Access Channel and Enhanced Access Channel Processing

29 During Access Channel Processing, the base station monitors the Access Channel to receive
30 messages which the mobile station sends while the mobile station is in the System Access
31 State.
32 Each Access Channel is associated with a Paging Channel. Up to 32 Access Channels can
33 be associated with a Paging Channel. The number of Access Channels associated with a
34 particular Paging Channel is specified in the Access Parameters Message sent on that
35 Paging Channel.
36 If the base station supports Access Channels, the base station shall continually monitor all
37 Access Channels associated with each Paging Channel that the base station transmits.
38 If the base station supports Enhanced Access Channels, then during Enhanced Access
39 Channel Processing, the base station monitors the Enhanced Access Channel to receive
3-21
3GPP2 C.S0005-A v6.0
1 messages which the mobile station sends while the mobile station is in the System Access
2 State.
3 Each Enhanced Access Channel is associated with a Forward Common Control Channel.
4 Up to 32 Enhanced Access Channels can be associated with a Forward Common Control
5 Channel. The number of Enhanced Access Channels associated with a particular Forward
6 Common Control Channel is specified in the Enhanced Access Parameters Message sent on
8 If the base station supports Enhanced Access Channel, the base station shall continually
9 monitor all Enhanced Access Channels associated with each Forward Common Control
10 Channel that the base station transmits.
11 3.6.3.1 Reserved
12 3.6.3.2 Reserved
13 3.6.3.3 Response to Page Response Message

14 If the base station receives a Page Response Message, the base station should send a
15 Channel Assignment Message, an Extended Channel Assignment Message, or a Release
16 Order. The base station may also start authentication procedures (see 2.3.12), start TMSI
17 assignment procedures (see 2.3.15), send a Data Burst Message, or request status
18 information records with the Status Request Message. If the base station is operating with
19 the mobile station in Band Class 0, the base station may also request the status
20 information records with the Status Request Order.
21 If the base station sends the Extended Channel Assignment Message, the base station may
22 include more than one pilot to be in the Active Set.
23 If the base station sends a Channel Assignment Message or an Extended Channel

24 Assignment Message, the base station shall perform the following:
25 • If the message directs the mobile station to a CDMA Traffic Channel, the base
26 station shall begin Traffic Channel Processing (see 3.6.4) for the mobile station.
27 • If the message directs the mobile station to an 800 MHz wide analog voice channel,
28 the base station shall follow the procedure described in [6].
29 • If the message directs the mobile station to an 800 MHz narrow analog voice
30 channel, the base station shall follow the procedure described in 3.6.5A of [22].
31 • Layer 3 shall send a mobile station inactive on common channel indication to Layer 2
32 (see 3.1.1.2.2 of [4]).
33 3.6.3.4 Response to Orders
34 No requirements.
35 3.6.3.5 Response to Origination Message

36 If the base station receives an Origination Message, the base station should send a Channel
37 Assignment Message, an Extended Channel Assignment Message, an Intercept Order, a
3-22
3GPP2 C.S0005-A v6.0
1 Reorder Order, a Release Order, a Retry Order, a PACA Message, or a Service Redirection
2 Message. The base station may also commence authentication procedures (see 2.3.12) or
3 TMSI assignment procedures (see 2.3.15). The base station may also request status
4 information records with the Status Request Message. If the base station is operating with
5 the mobile station in Band Class 0, the base station may also request status information
6 records with the Status Request Order.
7 If the base station sends the Extended Channel Assignment Message, the base station may
8 include more than one pilot to be in the Active Set.
9 If the base station sends a Channel Assignment Message or an Extended Channel
10 Assignment Message, the base station shall perform the following:
11 • If the message directs the mobile station to a CDMA Traffic Channel, the base
12 station shall begin Traffic Channel Processing (see 3.6.4) for the mobile station.
13 • If the message directs the mobile station to an 800 MHz wide analog voice channel,
14 the base station shall follow the procedure described in [2].
15 • If the message directs the mobile station to an 800 MHz narrow analog voice
16 channel, the base station shall follow the procedure described in 3.6.5A of [22].
17 • The base station shall raise a mobile station inactive on common channel indication
18 for the mobile station.
19 If the base station sends a Channel Assignment Message, the base station shall not set
20 RESPOND equal to ‘0’ when ASSIGN_MODE = ‘001’, ASSIGN_MODE = ‘010’, or
21 ASSIGN_MODE = ‘101’. If the base station sends an Extended Channel Assignment
22 Message, the base station shall not set RESPOND equal to ‘0’ when ASSIGN_MODE = ‘001’
23 or ASSIGN_MODE = ‘010’.
24 If the base station receives an Origination Message and the GLOBAL_EMERGENCY_CALL

25 indicator is set to ‘1’ and the service associated with this origination is a voice service, the
26 base station shall recognize this as an emergency call and should process the message
27 using an implementation-dependent procedure which may include ignoring the dialed
28 digits. If the base station receives an Origination Message and the
29 GLOBAL_EMERGENCY_CALL indicator is set to ‘1’ and the service associated with this
30 origination is not a voice service, the base station may recognize this as an emergency call
31 and should process the message using an implementation-dependent procedure which may
32 include ignoring the dialed digits.
33 3.6.3.6 Response to Registration Message
34 If the base station receives a Registration Message, the base station may send a Registration
35 Accepted Order, a Registration Rejected Order, or a Service Redirection Message. The base
36 station may also start authentication procedures (see 2.3.12), may start TMSI assignment
37 procedures (see 2.3.15), or may request status information records with the Status Request
38 Message. If the base station is operating with the mobile station in Band Class 0, the base
39 station may also request the status information records with a Status Request Order.
40 If the Registration Message specifies a power-down registration, Layer 3 shall send a mobile
41 station inactive on common channel indication to Layer 2 (see 3.1.1.2.2 of [4]).
3-23
3GPP2 C.S0005-A v6.0
1 When responding to a Registration Message that requests extended encryption, if the base
2 station decides to turn on extended encryption and the CMEAKEY is available at the base
3 station, the base station shall send a Registration Accepted Order with encryption
4 information. Before the CMEAKEY is available, the base station may send a Registration
5 Accepted Order without any encryption information. When the CMEAKEY becomes
6 available, if the base station decides to turn on extended encryption, the base station shall
7 send a Registration Accepted Order with encryption information.
8 3.6.3.7 Response to Data Burst Message
9 No requirements.
10 3.6.3.8 Reserved
11 3.6.3.9 Reserved
12 3.6.3.10 Service Redirection
13 If the base station sends a Service Redirection Message to the mobile station, Layer 3 shall
14 send a mobile station inactive on common channel indication to Layer 2 (see 3.1.1.2.2 of [4]).
15 3.6.4 Traffic Channel Processing
16 During Traffic Channel Processing, the base station uses the Forward and Reverse Traffic
17 Channels to communicate with the mobile station while the mobile station is in the Mobile
19 Traffic Channel processing consists of the following substates:

20 • Traffic Channel Initialization Substate - In this substate, the base station begins
21 transmitting on the Forward Traffic Channel and receiving on the Reverse Traffic
22 Channel.
23 • Traffic Channel Substate - In this substate, the base station exchanges Traffic
24 Channel frames with the mobile station in accordance with the current service
25 configuration. While in this substate, one or more Call Control instances can be
26 activated (see 3.6.8).
27 • Release Substate - In this substate, the base station disconnects the calls and the
29 3.6.4.1 Special Functions and Actions
30 The base station performs the following special functions and actions in one or more of the
31 Traffic Channel processing substates:
32 3.6.4.1.1 Forward Traffic Channel Power Control
33 When the base station enables Forward Traffic Channel power control, the mobile station
34 reports frame error rate statistics to the base station using the Power Measurement Report
35 Message.
3-24
3GPP2 C.S0005-A v6.0
1 The base station may enable Forward Traffic Channel power control using the System
2 Parameters Message sent on the Paging Channel and the Power Control Parameters Message
3 sent on the Forward Traffic Channel. The base station may enable Forward Traffic Channel
4 power control using the MC-RR Parameters Message sent on the Primary Broadcast Control
5 Channel and the Power Control Parameters Message sent on the Forward Traffic Channel.
6 The base station may enable periodic reporting which causes the mobile station to report
7 frame error rate statistics at specified intervals. The base station may also enable threshold
8 reporting which causes the mobile station to report frame error rate statistics when the
9 frame error rate reaches a specified threshold.2
10 The base station may use the reported frame error rate statistics to adjust the transmit
11 power of the Forward Traffic Channel.
12 3.6.4.1.2 Service Configuration and Negotiation
13 During Traffic Channel operation, the mobile station and base station communicate
14 through the exchange of Forward and Reverse Traffic Channel Configurations. The mobile
15 station and base station use a common set of attributes for building and interpreting Traffic
16 Channel frames. This set of attributes, referred to as a service configuration, consists of
17 both negotiable and non-negotiable parameters.
18 The set of negotiable service configuration parameters consists of the following:
19 1. Forward and Reverse Multiplex Options: These control the way in which the
20 information bits of the Forward and Reverse Traffic Channel frames, respectively,
21 are divided into various types of traffic, such as signaling traffic, primary traffic
22 and secondary traffic. A multiplex option together with a radio configuration
23 specifies the frame structures and transmission rates (see [3]). The Multiplex
24 Options which support Supplemental Code Channel transmission and
25 Supplemental Channel transmission on the Forward and Reverse Traffic Channels
26 are included in [3]. Invocation of Supplemental Code Channel operation on the
27 Forward or Reverse Traffic Channels occurs by transmission of the Supplemental
28 Channel Request Message, the Supplemental Channel Assignment Message, and
29 the General Handoff Direction Message. The Multiplex Options which support
30 Supplemental Code Channel transmission and Supplemental Channel
31 transmission on the Forward and Reverse Traffic Channels are included in [3].
32 The multiplex option used for the Forward Traffic Channel can be the same as
33 that used for the Reverse Traffic Channel, or it can be different.
34 2. Forward and Reverse Traffic Channel Configurations: These include the radio
35 configurations and other necessary attributes for the Forward and Reverse Traffic
36 Channels. The Traffic Channel Configuration used can be different for the
37 Forward and Reverse Traffic Channels or it can be the same.
2In this section the term base station may imply multiple cells or sectors.
3-25
3GPP2 C.S0005-A v6.0
1 3. Forward and Reverse Traffic Channel Transmission Rates: These are the
2 transmission rates actually used for the Forward and Reverse Traffic Channels,
3 respectively. The transmission rates for the Forward Traffic Channel can include
4 all of the transmission rates supported by the radio configuration associated with
5 the Forward Traffic Channel multiplex option, or a subset of the supported rates.
6 Similarly, the transmission rates used for the Reverse Traffic Channel can include
7 all rates supported by the radio configuration associated with the Reverse Traffic
8 Channel multiplex option, or a subset of the supported rates. The transmission
9 rates used for the Forward Traffic Channel can be the same as those used for the
10 Reverse Traffic Channel, or they can be different.
11 4. Service Option Connections: These are the services in use on the Traffic Channel.
12 There can be multiple service option connections. It is also possible that there is
13 no service option connection, in which case the base station uses the Forward
14 Traffic Channel as follows:
15 • Sends signaling traffic and null traffic on the Forward Fundamental

16 Channel.
17 • Sends signaling traffic on the Forward Dedicated Control Channel.
18 • Sends power control bits on the Forward Fundamental Channel if

19 FPC_PRI_CHAN is set to ‘0’; sends power control bits on the Forward
20 Dedicated Control Channel if FPC_PRI_CHAN is set to ‘1’.
21 Associated with each service option connection are a service option, a Forward
22 Traffic Channel traffic type, a Reverse Traffic Channel traffic type, and a service
23 option connection reference. The associated service option formally defines the
24 way in which traffic bits are processed by the mobile station and base station. The
25 associated Forward and Reverse Traffic Channel traffic types specify the types of
26 traffic used to support the service option. A service option can require the use of a
27 particular type of traffic, such as primary or secondary, or it can accept more than
28 one traffic type. A service option can be one-way, in which case it can be
29 supported on the Forward Traffic Channel only or the Reverse Traffic Channel
30 only. Alternatively, a service option can be two-way, in which case it can be
31 supported on the Forward and Reverse Traffic Channels simultaneously.
32 Connected service options can also invoke operation on Supplemental Code
33 Channels in either one or both of the Forward and Reverse Traffic Channels by
34 negotiating a multiplex option that supports operation on Supplemental Code
35 Channels (see [3] for Multiplex Options applicable to Supplemental Code
36 Channels), and by using the appropriate Supplemental Code Channel related
37 messages (i.e., the Supplemental Channel Request Message, the Supplemental
38 Channel Assignment Message, and the General Handoff Direction Message). After
39 Supplemental Code Channels have been assigned by the base station, the
40 connected service option can transmit primary and/or secondary traffic on
41 Supplemental Code Channels. Connected service options can also invoke
42 operation on Supplemental Channels in either one or both of the Forward and
43 Reverse Traffic Channels by negotiating a multiplex option that supports operation
44 on Supplemental Channels (see [3] for Multiplex Options applicable to
3-26
3GPP2 C.S0005-A v6.0
1 Supplemental Channels) and by using the appropriate Supplemental Channel

2 related messages (i.e., the Supplemental Channel Request Message, the Universal
3 Handoff Direction Message, the Supplemental Channel Request Mini Message, the
5 Channel Assignment Mini Message, and the Reverse Supplemental Channel
6 Assignment Mini Message). After Supplemental Channels have been assigned by
7 the base station, the connected service option can transmit primary and/or
8 secondary traffic on Supplemental Channels. The associated service option
9 connection reference provides a means for uniquely identifying the service option
10 connection. The reference serves to resolve ambiguity when there are multiple
11 service option connections in use.
12 The non-negotiable service configuration parameters are sent from the base station to the
13 mobile stations only, and consist of the following:
14 1. Reverse Pilot Gating Rate: This controls the way in which the reverse pilot is gated
15 on the Reverse Pilot Channel. The base station specifies the reverse pilot gating rate
16 to be used in the Service Connect Message, the General Handoff Direction Message,
17 and the Universal Handoff Direction Message.
18 2. Forward and Reverse Power Control Parameters: These consist of forward power
19 control operation mode, outer loop power control parameters (e.g. target frame error
20 rate, minimum Eb/Nt setpoint, and maximum Eb/Nt setpoint) for the Forward
21 Fundamental Channel and Forward Dedicated Control Channel, and Power Control
22 Subchannel indicator which indicates where the mobile station is to perform the
23 primary inner loop estimation and the base station is to multiplex the Power Control
24 Subchannel.
25 3. Logical to Physical Mapping: This is a table of logical to physical mapping entries,

26 consisting of service reference identifier, logical resource, physical resource, forward
27 flag, reverse flag, and priority.
28 4. Partition Table: The base station may include this table to specify the number of bits
29 allocated for each service in the Fundamental Channel or Dedicated Control
30 Channel.
31 5. SCH LTU Size Table: The base station may include this table to specify the number
32 of bits per supplemental channel LTU.
33 6. Information related to Variable Rate feature (the capability to support rate

34 determination) on Forward and Reverse Supplemental Channels
35 7. Information related to Flexible Rate feature (the capability to support non-listed

36 rates) on Forward and Reverse Fundamental Channel, Dedicated Control Channel,
37 and Supplemental Channels
38 The mobile station can request a default service configuration associated with a service
39 option at call origination, and can request new service configurations during Traffic
40 Channel operation. A requested service configuration can differ greatly from its predecessor
41 or it can be very similar. For example, the mobile station can request a service
42 configuration in which all of the service option connections are different from those of the
3-27
3GPP2 C.S0005-A v6.0
1 existing configuration; or the mobile station can request a service configuration in which
2 the existing service option connections are maintained with only minor changes, such as a
3 different set of transmission rates or a different mapping of service option connections to
4 Forward and Reverse Traffic Channel traffic types.
5 If the mobile station requests a service configuration that is acceptable to the base station,
6 they both begin using the new service configuration. If the mobile station requests a
7 service configuration that is not acceptable to the base station, the base station can reject
8 the requested service configuration or propose an alternative service configuration. If the
9 base station proposes an alternative service configuration, the mobile station can accept or
10 reject the base station’s proposed service configuration, or propose yet another service
11 configuration. This process, called service negotiation, ends when the mobile station and
12 base station find a mutually acceptable service configuration, or when either the mobile
13 station or base station rejects a service configuration proposed by the other.
14 It is also possible for the base station to request a default service configuration, associated
15 with a service option, when paging the mobile station and to request new service
16 configurations during Traffic Channel operation. The service negotiation proceeds as
17 described above, but with the roles of the mobile station and base station reversed.
18 For CDMA mode operation in Band Class 0, the mobile station and base station can also
19 use an alternative method for negotiating a service configuration known as service option
20 negotiation. Service option negotiation is similar to service negotiation, but offers less
21 flexibility for specifying the attributes of the service configuration. During service option
22 negotiation, the base station or mobile station specifies only which service option is to be
23 used. There is no facility for explicitly specifying the multiplex options, traffic types or
24 transmission rates to be used on the Forward and Reverse Traffic Channels in conjunction
25 with the service option. Instead, implicit service configuration attributes are assumed. In
26 particular, the Forward and Reverse Multiplex Options and transmission rates are assumed
27 to be the default multiplex options and transmission rates associated with the requested
28 service option, and the traffic type for both the Forward and Reverse Traffic Channels is
29 assumed to be primary traffic. Furthermore, a service configuration established using
30 service option negotiation is restricted to having only a single service option connection.
31 At mobile station origination and termination, the type of negotiation to use, either service
32 negotiation or service option negotiation, is indicated in the Channel Assignment Message.
33 Service negotiation is always used with the Extended Channel Assignment Message. If a
34 CDMA-to-CDMA hard handoff occurs during the call, the type of negotiation to use
35 following the handoff is indicated in the Extended Handoff Direction Message, General
36 Handoff Direction Message, or Universal Handoff Direction Message.
37 For CDMA mode operation in band classes other than Band Class 0, only service
38 negotiation is to be used.
39 The following messages are used to support service negotiation:
40 1. Service Request Message: The mobile station can use this message to propose a
41 service configuration, or to accept or reject a service configuration proposed in a
42 Service Response Message. The base station can use this message to propose a
3-28
3GPP2 C.S0005-A v6.0
1 service configuration, or to reject a service configuration proposed in a Service

2 Response Message.
3 2. Service Response Message: The mobile station can use this message to accept or
5 an alternative service configuration. The base station can use this message to
7 an alternative service configuration.
8 3. Service Connect Message: The base station can use this message to accept a service
9 configuration proposed in a Service Request Message or Service Response Message,
10 and instruct the mobile station to begin using the service configuration. The base
11 station may use this message to instruct the mobile station to use the stored
12 service configuration (that is, both the Service Configuration information record
13 and the Non-negotiable Service Configuration information record) if based on the
14 value of 16-bit CRC computed over the new service configuration (see 2.6.11)
15 matches the SYNC_ID that the mobile station has reported in the Origination
16 Message or Page Response Message.
17 4. Service Connect Completion Message: The mobile station can use this message to
18 acknowledge the transition to a new service configuration.
19 5. Service Option Control Message: The mobile station and base station can use this
21 6. Extended Channel Assignment Message: The base station can use this message to
22 accept or reject the initial service configuration proposed by the mobile station in
23 an Origination Message or a Page Response Message.
24 The following messages are used to support service option negotiation:
25 1. Service Option Request Order: The mobile station and base station can use this
26 message either to request a service option or suggest an alternative service option.
27 2. Service Option Response Order: The mobile station and base station can use this
28 message to accept or reject a service option request.
29 3. Service Option Control Order: The mobile station and base station can use this
31 The following messages are used to support both service negotiation and service option
32 negotiation:
33 1. Origination Message: The mobile station can use this message to propose an initial
35 2. Channel Assignment Message: The base station can use this message to accept or
36 reject the initial service configuration proposed by the mobile station in an
37 Origination Message or a Page Response Message, and to indicate which type of
38 negotiation, either service negotiation or service option negotiation, is to be used
39 during the call.
3-29
3GPP2 C.S0005-A v6.0
1 3. Extended Handoff Direction Message: The base station can use this message to
3 negotiation, is to be used following a CDMA-to-CDMA hard handoff.
4 4. General Handoff Direction Message: The base station can use this message to
10 5. General Page Message or Universal Page Message: The base station can use a
11 mobile-station-addressed page in a General Page Message or Universal Page
12 Message to propose an initial service configuration.
13 6. Page Response Message: The mobile station can use this message to accept or reject
14 the initial service configuration proposed by the base station in a mobile-station-
15 addressed page, or to propose an alternative initial service configuration.
16 7. Status Request Message: The base station can use this message to request service
17 capability information from the mobile station.
18 8. Status Response Message: The mobile station can use this message to return the
19 service capability information requested by the base station in a Status Request
20 Message.
21 9. Extended Status Response Message: The mobile station can use this message to
22 return the service capability information requested by the base station in a Status
23 Request Message.
24 10. Universal Handoff Direction Message: The base station can use this message to
30 3.6.4.1.2.1 Use of Variables
31 3.6.4.1.2.1.1 Maintaining the Service Request Sequence Number
32 The base station shall maintain a service request sequence number variable,
33 SERV_REQ_NUM, for use with service negotiation. Upon beginning Traffic Channel
34 processing, the base station shall set SERV_REQ_NUM to 0. Each time the base station
35 sends a new Service Request Message, it shall set the SERV_REQ_SEQ field of the message
36 to the current value of SERV_REQ_NUM and shall then set SERV_REQ_NUM equal to
37 (SERV_REQ_NUM + 1) modulo 8.
3-30
3GPP2 C.S0005-A v6.0
1 3.6.4.1.2.1.2 Maintaining the Service Connect Sequence Number
2 The base station shall maintain a service connect sequence number variable,
3 SERV_CON_NUM, for use with service negotiation. Upon beginning Traffic Channel
4 processing, the base station shall set SERV_CON_NUM to 0. Each time the base station
5 sends a new Service Connect Message, a General Handoff Direction Message, or a Universal
6 Handoff Direction Message containing a service configuration record, it shall set the
7 SERV_CON_SEQ field of the message to the current value of SERV_CON_NUM and shall
8 then set SERV_CON_NUM equal to (SERV_CON_NUM + 1) modulo 8.
9 3.6.4.1.2.1.3 Assigning Service Option Connection References
10 When the base station assigns a service option connection reference for use in identifying a
11 new service option connection during service negotiation, the base station shall use the
12 following criteria:
13 1. The base station shall not assign a reference equal to ‘00000000’; and
14 2. The base station shall not assign a reference that is associated with a service option
15 connection of the current service configuration; and
16 3. If there was a previous service configuration, the base station shall not assign a
17 reference that was associated with a service option connection of the previous
19 3.6.4.1.2.1.4 Maintaining the Service Negotiation Indicator Variable
20 The base station shall maintain a service negotiation indicator variable, SERV_NEG, to
21 indicate which type of negotiation to use, either service negotiation or service option
22 negotiation. The base station shall set SERV_NEG to enabled whenever service negotiation
23 is to be used, and shall set SERV_NEG to disabled whenever service option negotiation is to
24 be used. The precise rules for setting SERV_NEG are specified in 3.6.4.2 and 3.6.6.2.2.2.
25 For CDMA operation in band classes other than Band Class 0, the base station shall set
26 SERV_NEG to enabled.
27 3.6.4.1.2.1.5 Maintaining the Service Option Request Number
28 The base station shall maintain a service option request number variable, SO_REQ, for use
29 with service option negotiation. The base station shall set SO_REQ to a special value,
30 NULL, if the base station does not have an outstanding service option request. If the base
31 station has an outstanding service option request, the base station shall set SO_REQ to the
32 number of the service option associated with the outstanding request.
33 3.6.4.1.2.2 Service Subfunctions
34 As illustrated in Figure 3.6.4.1.2.2-1, the base station supports service configuration and
35 negotiation by performing the following set of service subfunctions.
36 • Normal Service Subfunction - While this subfunction is active, the base station
37 processes service configuration requests from the mobile station and sends service
38 configuration requests to the mobile station.
3-31
3GPP2 C.S0005-A v6.0
1 • Waiting for Service Request Message Subfunction - While this subfunction is active,
2 the base station waits to receive a Service Request Message.
3 • Waiting for Service Response Message Subfunction - While this subfunction is active,
4 the base station waits to receive a Service Response Message.
5 • Waiting for Service Action Time Subfunction - While this subfunction is active, the
6 base station waits for the action time associated with a new service configuration.
7 • Waiting for Service Connect Completion Message Subfunction - While this subfunction
8 is active, the base station waits to receive a Service Connect Completion Message, a
9 Handoff Completion Message, or an Extended Handoff Completion Message.
10 • SO Negotiation Subfunction - While this subfunction is active and the base station is
11 operating in Band Class 0, the base station supports service option negotiation with
13 The SO Negotiation Subfunction supports service option negotiation. All of the other service
14 subfunctions support service negotiation.
15 At any given time during Traffic Channel processing, only one of the service subfunctions is
16 active. For example, when the base station first begins Traffic Channel processing, either
17 the Normal Service Subfunction or the SO Negotiation Subfunction is active. Each of the
18 other service subfunctions may become active in response to various events which occur
19 during the Traffic Channel substates. Typically, the base station processes events
20 pertaining to service configuration and negotiation in accordance with the requirements for
21 the active service subfunction. However, some Traffic Channel substates do not allow for
22 the processing of certain events pertaining to service configuration and negotiation, or
23 specify requirements for processing such events which supersede the requirements of the
24 active service subfunction.
3-32
3GPP2 C.S0005-A v6.0
negotiation
Receives Service For service option SO

Request Message negotiation Negotiation
proposing; sends Subfunction
Service Response
Message rejecting.
Normal
Service
Receives Service
Subfunction
Request Message Receives Service
proposing; sends Request Message Needs to request new
Service Response proposing; sends service configuration;
Message proposing Service Response sends Service Request Receives Service
Message proposing. Message proposing. Response Message
proposing; sends
Service Request
Message proposing.
Receives Service
Receives Service Response Message
Request Message rejecting.
Waiting for rejecting. - or - Waiting for
Service - or - Receives Service Service
Request Receives Service Response Message Response
Message Request Message proposing; sends Message
Sends SCM,
Subfunction proposing; sends Service Request Subfunction
GHDM, or UHDM
Service Response Message rejecting. - or -
Message rejecting. Receives Service
Request Message
proposing; sends
Receives Service Connect SCM, GHDM,
Completion Message, Handoff or UHDM
Completion Message, or Extended
Handoff Completion Message.
Waiting for
Service
Connect
Completion
Message
Subfunction
Receives Service
Request Message
either accepting or Action time passes; uses new service Receives Service
proposing; sends configuration. Response Message
SCM, GHDM, or UHDM. either accepting
or proposing; sends
SCM, GHDM, or UHDM.
Waiting for
Service
Action Time
Subfunction
Notes:
SCM stands for Service Connect Message.
GHDM stands for General Handoff Direction Message.
UHDM stands for Universal Handoff Direction Message.
Processing for special cases, such as timeouts and errors, is not shown in this diagram.
1
2 Figure 3.6.4.1.2.2-1. Base Station Service Subfunctions
3-33
3GPP2 C.S0005-A v6.0
1 3.6.4.1.2.2.1 Normal Service Subfunction
2 While this subfunction is active, the base station processes service configuration requests
3 from the mobile station and sends service configuration requests to the mobile station.
4 While the Normal Service Subfunction is active, the base station shall perform the following:
5 • The base station shall process Forward and Reverse Traffic Channel frames in
6 accordance with the current service configuration. The base station shall discard
7 any Reverse Traffic Channel frame which has a format that is not supported by the
8 base station. The base station may discard any type of Reverse Traffic Channel
10 configuration.
11 • To initiate service negotiation for a new service configuration, the base station shall
12 send a Service Request Message to propose the new service configuration and shall
13 activate the Waiting for Service Response Message Subfunction.
15 the base station may send a Service Option Control Message to invoke a service
17 service option.
18 • The base station may send a Service Connect Message, a General Handoff Direction
19 Message, or a Universal Handoff Direction Message containing a service
20 configuration record. If the base station sends this message, the base station shall
22 • If SERV_NEG changes from enabled to disabled (see 3.6.6.2.2.2, 3.6.6.2.2.10, and

23 3.6.6.2.2.11), the base station shall activate the SO Negotiation Subfunction.
24 • If the base station receives one of the following service negotiation messages, the
25 base station shall process the message according to the specified requirements, if
26 any:
27 1. Service Connect Completion Message
31 service option connection, the base station shall process the message in
32 accordance with the requirements for the service option.
33 3. Service Request Message: The base station shall process the message as follows:
34 • If the purpose of the message is to propose a service configuration, the base

35 station shall process the message as follows:
3-34
3GPP2 C.S0005-A v6.0
1 − If the base station accepts the proposed service configuration, the base
2 station shall send a Service Connect Message, a General Handoff Direction
4 configuration record and shall activate the Waiting for Service Action Time
5 Subfunction.
6 – If the base station does not accept the proposed service configuration and
7 does not have an alternative service configuration to propose, the base
8 station shall send a Service Response Message to reject the proposed
10 − If the base station does not accept the proposed service configuration and
11 has an alternative service configuration to propose, the base station shall
12 perform one of the following actions:
13 ο Ssend a Service Response Message to propose the alternative
14 service configuration. The base station shall and shall activate
15 the Waiting for Service Request Message Subfunction, or.
16 ο Send a Service Connect Message, a General Handoff Direction

17 Message, or a Universal Handoff Direction Message containing a
18 service configuration record and shall activate the Waiting for
19 Service Action Time Subfunction
21 • If the base station receives one of the following service option negotiation messages,
22 the base station shall process the message according to the specified requirements,
23 if any:
27 3.6.4.1.2.2.2 Waiting for Service Request Message Subfunction
28 While this subfunction is active, the base station waits to receive a Service Request
29 Message.
30 While the Waiting for Service Request Message Subfunction is active, the base station shall
32 • If the base station does not receive a Service Request Message, the base station shall
33 activate the Normal Service Subfunction.
39 configuration.
3-35
3GPP2 C.S0005-A v6.0
4 service option.

9 any:
16 3. Service Request Message: The base station shall process the message as follows:
17 • If the purpose of the message is to accept a proposed service configuration,

18 the base station shall perform one of the following actions:
19 – The base station shall send a Service Connect Message, General Handoff
20 Direction Message, or Universal Handoff Direction Message and shall
22 – The base station shall send a Service Request Message to propose an

23 alternative service configuration and shall activate the Waiting for Service
24 Response Message Subfunction.
25 • If the purpose of the message is to reject a proposed service configuration,

26 the base station shall activate the Normal Service Subfunction.

29 – If the base station accepts the proposed service configuration, the base
33 Subfunction.
36 station shall send a Service Response Message to reject the proposed
37 service configuration. The base station shall activate the Normal Service
38 Subfunction.
3-36
3GPP2 C.S0005-A v6.0
4 ο Ssend a Service Response Message to propose the alternative service
5 configuration, or.

8 service configuration record and shall activate the Waiting for Service
9 Action Time Subfunction
13 if any:
17 3.6.4.1.2.2.3 Waiting for Service Response Message Subfunction
18 While this subfunction is active, the base station waits to receive a Service Response
19 Message.
20 While the Waiting for Service Response Message Subfunction is active, the base station shall
22 • If the base station does not receive a Service Response Message, the base station
29 configuration.
33 service option.

38 any:
3-37
3GPP2 C.S0005-A v6.0
7 3. Service Request Message: The base station should not process the layer 3Layer 3
8 fields of the message.
9 4. Service Response Message: The base station shall process the message as
10 follows:
11 • If the service request sequence number (SERV_REQ_SEQ) from the message

12 does not match the sequence number of the Service Request Message for
13 which the base station is expecting a response, the base station shall not
14 process the layer 3Layer 3 fields of the message.
15 • If the purpose of the message is to accept a proposed service configuration,

16 the base station shall perform one of the following actions:
17 – The base station shall send a Service Connect Message, a General

18 Handoff Direction Message, or a Universal Handoff Direction Message
19 containing a service configuration record and shall activate the Waiting
20 for Service Action Time Subfunction. Or
21 – The base station shall send a Service Request Message to propose an

22 alternative service configuration.
23 • If the purpose of the message is to reject a proposed service configuration,

24 the base station shall activate the Normal Service Subfunction.

27 – If the base station accepts the proposed service configuration, the base
31 Subfunction.
34 station shall send a Service Request Message to reject the proposed
35 service configuration. The base station shall activate the Normal Service
36 Subfunction.
3-38
3GPP2 C.S0005-A v6.0
1 ο Ssend a Service Request Message to propose the alternative service

2 configuration, or.
5 service configuration record and shall activate the Waiting for Service
6 Action Time Subfunction
9 if any:
13 3.6.4.1.2.2.4 Waiting for Service Action Time Subfunction
14 While this subfunction is active, the base station waits for the action time associated with a
15 new service configuration.
16 While the Waiting for Service Action Time Subfunction is active, the base station shall
18 • Prior to the action time associated with the Service Connect Message, a General
19 Handoff Direction Message, or Universal Handoff Direction Message containing a
20 service configuration record, the base station shall process Forward and Reverse
21 Traffic Channel frames in accordance with the current service configuration. The
22 base station shall discard any Reverse Traffic Channel frame which has a format
23 that is not supported by the base station. The base station may discard any type of
24 Reverse Traffic Channel traffic that is not signaling traffic and is not part of the
26 • At the action time associated with the Service Connect Message, General Handoff
27 Direction Message, or Universal Handoff Direction Message containing a service
28 configuration record, the base station shall begin to use the service configuration
29 specified by the Service Connect Message, the General Handoff Direction Message, or
30 the Universal Handoff Direction Message containing a service configuration record,
31 as the current service configuration and shall begin to process Forward and Reverse
32 Traffic Channel frames accordingly. The base station shall activate the Waiting for
33 Service Connect Completion Message Subfunction.

38 any:
3-39
3GPP2 C.S0005-A v6.0
2 message is part of the current or pending service configuration, and the service
3 option specified by the message is the same as the service option associated with
4 the service option connection, the base station shall process the message in
10 if any:
14 3.6.4.1.2.2.5 Waiting for Service Connect Completion Message Subfunction

15 While this subfunction is active, the base station waits to receive a Service Connect
16 Completion Message, a Handoff Completion Message, or an Extended Handoff Completion
17 Message.
18 While the Waiting for Service Connect Completion Message Subfunction is active, the base
20 • If the base station has sent a Service Connect Message and does not receive a Service
21 Connect Completion Message, or if the base station has sent a General Handoff
22 Direction Message or a Universal Handoff Direction Message containing a Service
23 Configuration record and does not receive a Handoff Completion Message, or an
24 Extended Handoff Completion Message, the base station shall activate the Normal
25 Service Subfunction.
31 configuration.
32 • The base station shall not initiate service negotiation for a new service configuration.

37 any:
3-40
3GPP2 C.S0005-A v6.0
1 1. Service Connect Completion Message, Handoff Completion Message, or Extended

2 Handoff Completion Message: The base station shall activate the Normal Service
3 Subfunction.
13 if any:
17 3.6.4.1.2.2.6 SO Negotiation Subfunction
18 While this subfunction is active, the base station supports service option negotiation with
20 Upon activating the SO Negotiation Subfunction, the base station shall set SO_REQ to NULL.
21 The base station shall delete from the current service configuration any service option
22 connection which does not use primary traffic on both the Forward and Reverse Traffic
23 Channels.
24 While the SO Negotiation Subfunction is active, the base station shall perform the following:
25 • If the current service configuration includes a service option connection, the base
26 station shall process the received primary traffic bits in accordance with the
27 requirements for the service option associated with the service option connection;
28 otherwise, the base station shall discard the received primary traffic bits.
30 station shall transmit primary traffic bits in accordance with the requirements for
31 the service option associated with the service option connection; otherwise, the base
32 station shall transmit null traffic and power control bits on the Forward
33 Fundamental Channel, if the Fundamental channel is present to transmit power
34 control bits on the Forward Dedicated Control Channel, if only the Dedicated
35 Control Channel is present.
37 station may send a Service Option Control Order to invoke a service option specific
38 function in accordance with the requirements for the service option associated with
39 the service option connection.
3-41
3GPP2 C.S0005-A v6.0
1 • To initiate service option negotiation, the base station shall set SO_REQ to the
2 number of the requested service option and shall send a Service Option Request
3 Order containing the requested service option number.
4 • If SERV_NEG changes from disabled to enabled (see 3.6.6.2.2.2, 3.6.6.2.2.10, and

5 3.6.6.2.2.11), the base station shall activate the Normal Service Subfunction.
6 • The base station shall process a service option request received in an Origination
7 Message, a Page Response Message, or a Service Option Request Order as follows:
8 – If the base station accepts the requested service option, the base station shall
9 set SO_REQ to NULL and shall send a Service Option Response Order accepting
10 the requested service option within T4b seconds. The base station shall begin
11 using the service configuration implied by the requested service option in
12 accordance with the requirements for the requested service option. The implied
13 service configuration shall include the default Forward and Reverse Multiplex
14 Options and transmission radio configurations associated with the requested
15 service option. This implied service configuration shall include one service
16 option connection for which the service option connection reference is 1, for
17 which the service option is the requested service option, and for which the
18 Forward and Reverse Traffic Channel types are both primary traffic.
19 – If the base station does not accept the requested service option and has an
20 alternative service option to request, the base station shall set SO_REQ to the
21 alternative service option number and shall send a Service Option Request Order
22 requesting the alternative service option within T4b seconds.
23 – If the base station does not accept the requested service option and does not
24 have an alternative service option to request, the base station shall set SO_REQ
25 to NULL and shall send a Service Option Response Order to reject the request
26 within T4b seconds. The base station shall continue to use the current service
27 configuration.
28 • If the base station receives a Service Option Response Order, it shall process the
30 – If the service option number specified in the order is equal to SO_REQ, the base
31 station shall set SO_REQ to NULL and shall begin using the service
32 configuration implied by the specified service option in accordance with the
33 requirements for the service option. The implied service configuration shall
34 include the default Forward and Reverse Multiplex Options and radio
35 configurations associated with the requested service option. This implied service
36 configuration shall include one service option connection for which the service
37 option connection reference is 1, for which the service option is the requested
38 service option, and for which the Forward and Reverse Traffic Channel types are
39 both primary traffic.
40 – If the order indicates a service option rejection, the base station shall set
41 SO_REQ to NULL. The base station shall continue to use the current service
42 configuration.
3-42
3GPP2 C.S0005-A v6.0
1 – If the order does not indicate a service option rejection and the service option
2 specified in the order is not equal to SO_REQ, the base station shall set SO_REQ
3 to NULL, should send a Release Order (ORDQ = ‘00000010’), and should enter
4 the Release Substate.
5 • If the base station receives a Service Option Control Order, the base station shall
6 process the order as follows:
7 – If the current service configuration includes a service option connection, the

8 base station shall process the received Service Option Control Order in
9 accordance with the requirements for the service option associated with the
10 service option connection.
13 any:
15 2. Service Option Control Message
18 3.6.4.1.3 Ordering of Messages
19 The Layer 2 protocol does not guarantee delivery of messages in any order. If the base
20 station requires that the mobile station receive a set of messages in a certain order, the
21 base station shall send each message in assured mode requiring confirmation of delivery
22 and shall wait for the confirmation of delivery of each message before transmitting the next
23 message in the set.
24 3.6.4.1.4 Message Action Times
25 A Forward Traffic Channel message without a USE_TIME field or with a USE_TIME field set
26 to ‘0’ has an implicit action time. A message that has its USE_TIME field set to ‘1’ has an
27 explicit action time that is specified in the ACTION_TIME field of the message.
28 A message with an explicit action time is called a pending message.
29 Unless otherwise specified, a message having an implicit action time shall take effect no
30 later than the first 80 ms boundary (relative to System Time) occurring at least 80 ms after
31 the end of the frame containing the last bit of the message. A message with an explicit
32 action time, except for a Power Up Function Message, shall take effect when System Time (in
33 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME field. A Power Up
34 Function Message shall take effect ACTION_TIME_FRAME frames after the time when
35 System Time (in 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME
36 field. The difference in time between ACTION_TIME and the end of the frame containing the
37 last bit of the message shall be at least 80 ms.
38 The base station shall support two pending messages at any given time, not including
39 pending Service Option Control Orders, Service Option Control Messages, or Power Up
3-43
3GPP2 C.S0005-A v6.0
1 Function Messages. The number of pending Service Option Control Orders or Service Option
2 Control Messages that the base station is required to support is specific to the service
3 option (see the relevant service option descriptions). In addition, the base station shall
4 support one pending Power Up Function Message.
5 3.6.4.1.5 Long Code Transition Request Processing
6 If a request for voice privacy is specified in the Origination Message or Page Response
7 Message, the base station may send a Long Code Transition Request Order (ORDQ =
8 ‘00000001’) requesting a transition to the private long code.
9 The base station shall process the Long Code Transition Request Order as follows:
10 • If the Long Code Transition Request Order requests a transition to the private long
11 code and the base station accepts the request, the base station shall send a Long
12 Code Transition Request Order (ORDQ = ‘00000001’). If the base station does not
13 accept the private long code transition request, the base station shall send a Long
14 Code Transition Request Order (ORDQ = ‘00000000’).
15 • If the Long Code Transition Request Order requests a transition to the public long
16 code and the base station accepts the request, the base station shall send a Long
17 Code Transition Request Order (ORDQ = ‘00000000’). If the base station does not
18 accept the public long code transition request, the base station shall send a Long
19 Code Transition Request Order (ORDQ = ‘00000001’).
20 The base station shall process the Long Code Transition Response Order as follows:
21 • If the Long Code Transition Response Order indicates that the mobile station accepts
22 the long code transition requested in the Long Code Transition Request Order sent by
23 the base station, the base station shall use the requested long code mask on both
24 the Forward Traffic Channel and the Reverse Traffic Channel. The base station
25 shall specify an explicit action time in the Long Code Transition Request Order. The
26 base station shall begin using the requested long code mask using the explicit action
27 time (see 3.6.4.1.4).
28 3.6.4.1.6 Processing Resource Request Messages

29 The base station shall process Resource Request Message and Resource Request Mini
30 Message, as follows:
31 • The base station may send one of the messages that assign appropriate resources
32 (e.g. Extended Supplemental Channel Assignment Message, Resource Allocation
33 Message, Resource Allocation Mini Message, Universal Handoff Direction Message,
34 Retry Order, etc) to the mobile station. If the base station sends one of these
35 messages, the base station shall set PILOT_GATING_USE_RATE to ‘0’ and start
36 transmitting the Forward Power Control Subchannel with the maximum rate at the
38 • The base station may send a Retry Order to the mobile station.
3-44
3GPP2 C.S0005-A v6.0
1 3.6.4.1.7 Response to Enhanced Origination Message
2 If the base station receives an Enhanced Origination Message, the base station should
4 • If the base station does not accept this call request from the mobile station, the base
5 station should send one of the following messages:
6 + A Call Assignment Message to the mobile station, with the RESPONSE_IND field
7 set to ‘1’, the ACCEPT_IND field set to ‘0’, and the TAG field set to the value of
8 the TAG field of the Enhanced Origination Message.
9 + A Retry Order if the Enhanced Origination Message is for a packet data service
10 option.
11 • If the base station accepts this call request from the mobile station, the base station
12 should send a Call Assignment Message, Service Connect Message, General Handoff
13 Direction Message (with the Service Configuration information record included), or
14 Universal Handoff Direction Message (with the Service Configuration information
15 record included) to assign the call:
16 − If the GLOBAL_EMERGENCY_CALL indicator is set to ‘1’ and the service

17 associated with this origination is a voice service, the base station shall
18 recognize this as an emergency call and should process the message using an
19 implementation-dependent procedure which may include ignoring the dialed
20 digits. If the base station receives an Origination Message and the
21 GLOBAL_EMERGENCY_CALL indicator is set to ‘1’ and the service associated
22 with this origination is not a voice service, the base station may recognize this as
23 an emergency call and should process the message using an implementation-
24 dependent procedure which may include ignoring the dialed digits.
25 – If the base station sends a Call Assignment Message to assign the call, the base
27 + The base station shall set the RESPONSE_IND field to ‘1’, the ACCEPT_IND
28 field to ‘1’, and the TAG field to the value of the TAG field of the Enhanced
29 Origination Message. The base station shall set the CON_REF_INCL field of
30 the message to ‘1’ and the CON_REF field of the message to the value of the
31 connection reference of the service option connection corresponding to this
32 call.
33 + A service option connection corresponding to this call (if not already

34 established) shall be established by performing service negotiation; the base
35 station should initiate service negotiation to establish the service option
36 connection, if permitted by the current service negotiation subfunction.
37 + At the action time corresponding to this message, the layer 3Layer 3 shall
38 instantiate a Call Control instance (as specified in 3.6.8). The layer 3Layer 3
39 shall identify this Call Control instance by the value of the CON_REF field
3-45
3GPP2 C.S0005-A v6.0
1 included in the Call Assignment Message.
2 – If the base station sends a Service Connect Message, General Handoff Direction
3 Message (with the Service Configuration information record included), or a
5 record included), to assign the call, the base station shall perform the following:
6 + The base station shall set the call control parameters corresponding to this
7 call included in the message as follows: The base station shall set the
8 RESPONSE_IND field to ‘1’, and the TAG field to the value of the TAG field of
9 the Enhanced Origination Message.
12 shall identify this Call Control instance by the value of the CON_REF
13 assigned to the service option connection corresponding to this call.
14 3.6.4.1.8 Processing Resource Release Request Message and Resource Release Request Mini
15 Message
16 The base station may perform the following in response to receiving aResource Release
17 Request Message or a Resource Release Request Mini Message from the mobile station:
18 • If the mobile station requests to release a service option connection, the base station
19 may send a Service Connect Message, General Handoff Direction Message, or a
20 Universal Handoff Direction Message to release the service option connection.
21 • If the mobile station requests to commence reverse pilot gating operation, the base
22 station may send a Extended Release Message, Extended Release Mini Message, or a
23 Universal Handoff Direction Message to instruct the mobile station to commence the
24 reverse pilot gating operation.
25 3.6.4.1.9 Processing Base Station Status Request Message
26 If the requested RECORD_TYPE equals ‘00000000’ (Pilot Information), the base station
27 should send a Base Station Status Response Message with a RECORD_TYPE of ‘00000000’
28 (Pilot Information) to the mobile station:
29 • For each pilot being requested by the mobile station, the base station shall include
30 the corresponding Base Station Identification number.
31 • If SID and NID information is being requested by the mobile station, the base station
32 shall include the SID and NID information corresponding to these pilots.
3-46
3GPP2 C.S0005-A v6.0
1 3.6.4.2 Traffic Channel Initialization Substate
2 In this substate, the base station begins transmitting on the Forward Traffic Channel and
3 acquires the Reverse Traffic Channel.
4 Upon entering the Traffic Channel Initialization Substate, the base station shall perform the
5 following:
6 • Layer 3 shall send an L2-Supervision.Request primitive to Layer 2 to reset the

7 message acknowledgment procedures as specified in 3.2.1.1 and 3.2.2.1 of [4].
8 • The base station shall set its Forward and Reverse Traffic Channel long code masks
9 to the public long code mask (see [2]).
10 • The base station shall set its Forward and Reverse Traffic Channel frame offsets (see
11 [2]) to the frame offset assigned to the mobile station.
12 • If the base station set the ASSIGN_MODE field of the Channel Assignment Message
13 to ‘000’, the base station shall set SERV_NEG to disabled. If the base station set the
14 ASSIGN_MODE field of the Channel Assignment Message to ‘100’, the base station
15 shall set SERV_NEG to enabled. For operation in band classes other than Band
16 Class 0, SERV_NEG is always equal to enabled.
17 • If the base station uses the Extended Channel Assignment Message, the base station
18 shall set the SERV_NEG to enabled.
19 • The base station shall determine the initial service configuration as follows:
20 – If SERV_NEG is equal to disabled, the initial service configuration shall include

21 Multiplex Option 1 and Radio Configuration 1 for both the Forward and Reverse
22 Traffic Channels, and shall include no service option connections.
23 – If SERV_NEG is equal to enabled and the base station set the GRANTED_MODE
24 field of the Channel Assignment Message or the Extended Channel Assignment
25 Message to ‘00’, the initial service configuration shall include the multiplex
26 option and radio configuration for the Forward and Reverse Traffic Channels as
27 specified by the DEFAULT_CONFIG field, and shall include no service option
28 connections.
31 Message to ‘01’ or ‘10’, the initial service configuration shall include the default
32 Forward and Reverse Traffic Channel multiplex options that are derived from the
33 radio configurations corresponding to Table 3.7.2.3.2.21-7and transmission
34 rates corresponding to the service option requested by the mobile station in the
35 Origination Message, in the case of a mobile-station-originated call, or the Page
36 Response Message, in the case of a mobile station terminated call, and shall
37 include no service option connections.
3-47
3GPP2 C.S0005-A v6.0
2 field of the Channel Assignment Message to ‘01’ or ‘10’, the initial service
4 multiplex options and transmission rates corresponding to the service option
5 requested by the mobile station in the Origination Message, in the case of a
6 mobile station originated call, or the Page Response Message, in the case of a
7 mobile station terminated call, and shall include no service option connections.
8 • If SERV_NEG is equal to disabled, the base station shall activate the SO Negotiation
9 Subfunction (see 3.6.4.1.2.2.6); otherwise, the base station shall activate the Normal
10 Service Subfunction (see 3.6.4.1.2.2.1).
11 • The base station shall set PILOT_GATING_USE_RATE to ‘0’.

12 While in the Traffic Channel Initialization Substate, the base station shall perform the
13 following:
14 • If the Forward Fundamental Channel is assigned, the base station shall transmit
15 null Traffic Channel data on the Forward Fundamental Channel, except when
16 transmitting signaling traffic.
17 • If FPC_PRI_CHAN is set to ‘0’, the base station shall transmit power control bits on
18 the Forward Fundamental Channel. If FPC_PRI_CHAN is set to ‘1’, the base station
19 shall transmit power control bits on the Forward Dedicated Control Channel.
20 • If the base station acquires the Reverse Traffic Channel, Layer 3 shall send a reverse
21 dedicated channel acquired indication to Layer 2 (see 2.2.2.1.2 of [4]). The layer
22 3Layer 3 shall instantiate a Call Control instance (as specified in 3.6.8). The layer
23 3Layer 3 shall assign the default identifier of NULL to this Call Control instance. The
24 layer 3Layer 3 shall enter the Traffic Channel Substate.
25 • If the base station fails to acquire the Reverse Traffic Channel, the base station
26 should perform one of the following:
27 - retransmit the Channel Assignment Message or the Extended Channel
28 Assignment Message on the Paging Channel and remain in the Traffic Channel
29 Initialization Substate
30 - retransmit the Extended Channel Assignment Message on the Forward Common

31 Control Channel and remain in the Traffic Channel Initialization Substate, or
32 - disable transmission on the Forward Traffic Channel and discontinue the Traffic
33 Channel Processing for the mobile station.
34 3.6.4.3 Traffic Channel Substate
35 In this substate, the base station may exchange Traffic Channel frames with the mobile
36 station in accordance with the current service configuration.
37 Upon entering the Traffic Channel Substate, the base station shall perform the following:
38 • If the call is a mobile station terminated call and the base station set
39 BYPASS_ALERT_ANSWER to ‘0’, the base station shall perform the following:
3-48
3GPP2 C.S0005-A v6.0
1 – If SERV_NEG is equal to disabled, the base station shall process the service
2 option request specified in the Page Response Message in accordance with the
4 – If SERV_NEG is equal to enabled and the base station sets the GRANTED_MODE
6 Message to ‘00’ or ‘01’, the base station should initiate service negotiation to
7 request a service configuration in accordance with the requirements for the
8 active service subfunction (see 3.6.4.1.2.2).
11 Message to ‘10’, the base station should send a Service Connect Message in
13 3.6.4.1.2.2).
14 • Otherwise, the base station shall perform the following:
15 – If SERV_NEG equals enabled, the call is mobile-station-originated and the base

16 station sets the GRANTED_MODE field of the Channel Assignment Message or
17 the Extended Channel Assignment Message to ‘10’, the base station should send
18 a Service Connect Message in accordance with the requirements for the active
19 service subfunction (see 3.6.4.1.2.2).
20 – If SERV_NEG equals disabled and the call is mobile-station-originated, the base

21 station shall process the service option request specified in the Origination
22 Message in accordance with the requirements for the active service subfunction
23 (see 3.6.4.1.2.2).
24 While in the Traffic Channel Substate, the base station shall perform the following:
25 • The base station shall transmit the power control subchannel as specified in [2].
28 3.6.4.1.2.2).
29 • When PILOT_GATING_USE_RATE is equal to ‘0’ and the base station is to establish

30 a Fundamental Channel or a Dedicated Control Channel, the base station shall send
31 a Universal Handoff Direction Message to the mobile station.
32 • When PILOT_GATING_USE_RATE is equal to ‘1’ and the base station has data to
33 send, the base station may send a Resource Allocation Message, Resource Allocation
34 Mini Message, Extended Supplemental Channel Assignment Message, Forward
35 Supplemental Channel Assignment Mini Message, Reverse Supplemental Channel
36 Assignment Mini Message, or Universal Handoff Direction Message to start
37 transmitting the Forward Power Control Subchannel with the maximum rate at the
38 action time of the message and start exchange of user information.
3-49
3GPP2 C.S0005-A v6.0
1 • If both the Fundamental Channel and the Dedicated Control Channel are currently
2 established, and the base station is to release one of these two channels, the base
3 station shall send a Universal Handoff Direction Message, Extended Release
4 Message, or an Extended Release Mini Message to the mobile station.
5 • When PILOT_GATING_USE_RATE is equal to ‘0’ and the base station does not have
6 any data to send and the base station has determined that the mobile station does
7 not have any data to send (see the RLP out-of-data indication in TIA/EIA/IS-707-A),
8 then the base station may send an Extended Release Message, Extended Release
9 Mini Message or Universal Handoff Direction Message to start transmitting the
10 Forward Power Control Subchannel with the specified rate at the action time of the
11 message and stop the exchange of user information.
12 • If the base station declares a loss of Reverse Traffic Channel continuity (see 3.4), the
13 base station should send a Release Order to the mobile station. If the base station
14 sends a Release Order, the layer 3Layer 3 shall send a “release indication” to all Call
15 Control instances, and shall enter the Release Substate.
16 • The base station may perform Forward Traffic Channel power control as specified in
17 3.6.4.1.1.
18 • The base station may request a new service configuration by initiating service
19 negotiation or service option negotiation in accordance with the requirements for the
20 active service subfunction (see 3.6.4.1.2.2).
21 • The base station may send a Service Option Control Message or Service Option
22 Control Order to invoke a service option specific function in accordance with the
24 • The base station may request a long code transition, as specified in 3.6.4.1.5, either
25 autonomously or in response to a request for voice privacy specified in the
26 Origination Message or Page Response Message.
27 • The base station may perform authentication procedures as specified in 3.3.1.
28 • The base station may perform TMSI assignment procedures (see 2.3.15).
29 • For the first call, if the call is mobile-station-originated and the PACA_REORIG field
30 of the Origination Message is equal to ‘1’, the layer 3Layer 3 shall send a “paca reorig
31 indication” to the Call Control instance.
32 • The base station may control operation of the Forward or Reverse Supplemental
33 Code Channels by including Supplemental Code Channel assignment information in
34 the Supplemental Channel Assignment Message, or the General Handoff Direction
35 Message.
36 • The base station may control operation of the Forward or Reverse Supplemental
37 Channels by including Supplemental Channel assignment information in the
39 Channel Assignment Mini Message, or the Reverse Supplemental Channel Assignment
40 Mini Message.
3-50
3GPP2 C.S0005-A v6.0
1 • The base station may assign a new call by sending a Call Assignment Message,
2 Service Connect Message, General Handoff Direction Message (with the Service
3 Configuration information record included), or Universal Handoff Direction Message
4 (with the Service Configuration information record included) to assign the call:
5 – If the base station sends a Call Assignment Message to assign the call, the base
7 + The base station shall set the RESPONSE_IND field to ‘0’.
8 + The base station shall set the CON_REF_INCL field of the message to ‘1’ and
9 the CON_REF field of the message to the value of the connection reference of
10 the service option connection corresponding to this call.
11 + A service option connection corresponding to this call (if not already

12 established) shall be established by performing service negotiation; the base
13 station should initiate service negotiation to establish the service option
14 connection, if permitted by the current service negotiation subfunction.
17 shall identify this Call Control instance by the value of the CON_REF field
18 included in the Call Assignment Message.
19 – If the base station sends a Service Connect Message, General Handoff Direction
20 Message (with the Service Configuration information record included), or
22 record included) to assign the call, the base station shall perform the following:
23 + The base station shall set the call control parameters corresponding to this
24 call included in the message as follows: The base station shall set the
25 RESPONSE_IND field to ‘0’, and the BYPASS_ALERT_ANSWER field as
26 required.
29 shall identify this Call Control instance by the value of the CON_REF
30 assigned to the service option connection corresponding to this call.
31 • If the layer 3Layer 3 receives a ‘call release request’ from a Call Control instance, the
32 layer 3Layer 3 shall perform the following:
33 – If the service option connection corresponding to this call is the only one
34 connected, the base station should send the mobile station a Release Order and
35 enter the Release Substate.
3-51
3GPP2 C.S0005-A v6.0
1 – If the service option connection corresponding to this call is not the only one
2 connected, the base station should release this service option connection. At the
3 action time of the message, the layer 3Layer 3 shall terminate this Call Control
4 instance.
5 • The base station may send the following messages. Some of these messages are
6 generated by the Call Control Instance. If the base station sends a message, the
7 base station shall comply with the specified requirements for sending the message,
8 if any:
9 1. Alert With Information Message:
10 2. Analog Handoff Direction Message: The base station shall perform the following:
11 – If the CON_REF_INCL field was set to ‘0’, the layer 3Layer 3 shall terminate
12 all Call Control instances (if there are any) except the one identified by NULL;
13 otherwise, the layer 3Layer 3 shall terminate all Call Control instances (if
14 there are any) except the one identified by CON_REF field set in the message.
15 The base station shall perform the following (see [6] for handoff to a wide
16 analog channel and [22] for handoff to an 800 MHz narrow analog channel):
17 + If this Call Control instance is in the Waiting for Order Substate, the base
18 station shall enter the Waiting for Order Task.
19 + If this Call Control instance is in the Waiting for Answer Substate, the
20 base station shall enter the Waiting for Answer Task.
21 + If this Call Control instance is in the Conversation Substate, the base

22 station shall enter the Conversation Task.
23 3. Audit Order
24 4. Authentication Challenge Message
25 5. Base Station Challenge Confirmation Order
26 6. Base Station Status Response Message
27 6.7. Call Assignment Message
28 7.8. Candidate Frequency Search Request Message
29 8.9. Candidate Frequency Search Control Message
30 9.10. Continuous DTMF Tone Order
32 11.12. Extended Alert With Information Message
33 12.13. Extended Flash With Information Message
34 13.14. Extended Handoff Direction Message
35 14.15. Extended Neighbor List Update Message
3-52
3GPP2 C.S0005-A v6.0
1 15.16. Extended Release Message: If the physical channels indicated in CH_IND

2 field of this message includes all the physical channels currently being
3 processed by the mobile station, the layer 3Layer 3 shall send a “release
4 indication” to all Call Control instances, and shall enter the Release Substate.
5 16.17. Extended Release Mini Message: If the physical channels indicated in

6 CH_IND field of this message includes all the physical channels currently being
7 processed by the mobile station, the layer 3Layer 3 shall send a “release
9 17.18. Extended Supplemental Channel Assignment Message
10 18.19. Forward Supplemental Channel Assignment Mini Message
11 19.20. General Handoff Direction Message
12 20.21. Flash With Information Message
13 21.22. In-Traffic System Parameters Message
15 23.24. Lock Until Power-Cycled Order: The base station should send this order in
16 unassured mode.
17 24.25. Long Code Transition Request Order
18 25.26. Maintenance Order:
19 26.27. Maintenance Required Order
20 27.28. Message Encryption Mode Order
21 28.29. Mobile Assisted Burst Operation Parameters Message
22 29.30. Mobile Station Registered Message
23 30.31. Neighbor List Update Message
24 31.32. Parameter Update Order (see 2.3.12.1.3).
25 32.33. Periodic Pilot Measurement Request Order
26 33.34. Pilot Measurement Request Order
27 34.35. Power Control Message
28 35.36. Power Control Parameters Message
29 36.37. Power Up Function Message
30 37.38. Power Up Function Completion Message
31 38.39. Resource Allocation Message
32 39.40. Resource Allocation Mini Message
33 40.41. Release Order: The layer 3Layer 3 shall send a “release indication” to all Call
34 Control instances, and shall enter the Release Substate.
35 41.42. Retrieve Parameters Message
3-53
3GPP2 C.S0005-A v6.0
1 42.43. Retry Order
2 43.44. Reverse Supplemental Channel Assignment Mini Message
3 44.45. Security Mode Command Message
4 45.46. Send Burst DTMF Message
5 46.47. Service Connect Message: The base station shall send the message in
7 3.6.4.1.2.2).
8 47.48. Service Option Control Message: The base station shall send the message in
10 3.6.4.1.2.2).
11 48.49. Service Option Control Order
12 49.50. Service Option Request Order
13 50.51. Service Option Response Order
14 51.52. Service Redirection Message: The layer 3Layer 3 shall send a “release
16 52.53. Service Request Message: The base station shall send the message in
18 3.6.4.1.2.2).
19 53.54. Service Response Message: The base station shall send the message in
21 3.6.4.1.2.2).
22 54.55. Set Parameters Message
23 55.56. SSD Update Message
24 56.57. Status Request Message
25 57.58. Status Request Order
26 58.59. Supplemental Channel Assignment Message
27 59.60. TMSI Assignment Message
28 60.61. Universal Handoff Direction Message
30 62.63. User Zone Update Message
31 • If the base station receives one of the following messages from the mobile station,
33 if any:
34 1. Base Station Challenge Order: The base station shall process the message as
3-54
3GPP2 C.S0005-A v6.0
1 2. Base Station Status Request Message: The base station shall process the message
2 as described in 3.6.4.1.9
3 2.3. Call Cancel Message
4 3.4. Candidate Frequency Search Report Message: The base station shall process
5 the message as described in 3.6.6.2.2.6.
6 4.5. Candidate Frequency Search Response Message: The base station shall
7 process the message as described in 3.6.6.2.2.4.
8 5.6. Connect Order: If the CON_REF_INCL field is not included in this message or
9 if the CON_REF_INCL field equals ‘0’, the layer 3Layer 3 shall deliver this
12 CON_REF.
13 6.7. Continuous DTMF Tone Order: If the CON_REF_INCL field is not included in
14 this message or if the CON_REF_INCL field equals ‘0’, the layer 3Layer 3 shall
17 identified by CON_REF.
19 8.9. Enhanced Origination Message: The base station shall process the message
20 as described in 3.6.4.1.7.
21 9.10. Extended Flash With Information Message: If CON_REF_INCL equals ‘0’, the
23 by NULL; otherwise, the layer 3Layer 3 shall deliver this message to the Call
24 Control instance identified by CON_REF.
25 10.11. Extended Handoff Completion Message: The base station shall process the
26 message as described in 3.6.6.2.2.7.
27 11.12. Extended Pilot Strength Measurement Message: The base station shall
28 process the message as described in 3.6.6.2.2.1.
29 12.13. Extended Release Response Message.
30 13.14. Extended Release Response Mini Message.
31 14.15. Flash With Information Message: The layer 3Layer 3 shall deliver this
32 message to the Call Control instance identified by NULL.
33 15.16. Handoff Completion Message: The base station shall process the message as
34 described in 3.6.6.2.2.7.
35 16.17. Local Control Response Order
36 17.18. Long Code Transition Request Order: The base station shall process the
37 message as described in 3.6.4.1.5.
38 18.19. Long Code Transition Response Order
3-55
3GPP2 C.S0005-A v6.0
1 19.20. Mobile Station Reject Order: If the CON_REF_INCL field is included in this
2 message, layer 3Layer 3 shall perform the following: if the CON_REF_INCL field
3 equals ‘0’, layer 3Layer 3 shall send a ‘messages rejected indication’ to the Call
4 Control instance identified by NULL; otherwise, layer 3Layer 3 shall send a
5 ‘messages rejected indication’ to the Call Control instance identified by
6 CON_REF.
7 20.21. Origination Continuation Message: The layer 3Layer 3 shall deliver this
8 message to the Call Control instance identified by NULL.
9 21.22. Outer Loop Report Message
10 22.23. Parameters Response Message
11 23.24. Parameter Update Confirmation Order
12 24.25. Periodic Pilot Strength Measurement Message
13 25.26. Pilot Strength Measurement Message: The base station shall process the
15 26.27. Pilot Strength Measurement Mini Message
16 27.28. Power Measurement Report Message: The base station may process the
18 28.29. Release Order: The base station shall send the mobile station a Release
19 Order within T2b seconds, and the layer 3Layer 3 shall send a “release
20 indication” to all Call Control instances, and enter the Release Substate;
21 otherwise, the layer 3Layer 3 shall send a “send alert with info message
22 indication” to all Call Control instances.
23 29.30. Resource Release Request Message: The base station shall process the
25 30.31. Resource Release Request Mini Message: The base station shall process the
27 31.32. Resource Request Message: The base station shall process the message as
29 32.33. Resource Request Mini Message: The base station shall process the message
30 as described in 3.6.4.1.6.
31 33.34. Request Analog Service Order: The base station may respond with an Analog
33 34.35. Request Narrow Analog Service Order: The base station may respond with an
34 Analog Handoff Direction Message.
35 35.36. Request Wide Analog Service Order: The base station may respond with an
36 Analog Handoff Direction Message.
37 36.37. Send Burst DTMF Message: If the CON_REF_INCL field is not included in this
38 message or if the CON_REF_INCL field equals ‘0’, the layer 3Layer 3 shall deliver
3-56
3GPP2 C.S0005-A v6.0
1 this message to the Call Control instance identified by NULL; otherwise, the
3 by CON_REF.
4 37.38. Service Connect Completion Message: The base station shall process the
6 (see 3.6.4.1.2.2).
7 38.39. Service Option Control Message: The base station shall process the message
9 3.6.4.1.2.2).
10 39.40. Service Option Control Order: The base station shall process the message in
12 3.6.4.1.2.2).
13 40.41. Service Option Request Order: The base station shall process the message in
15 3.6.4.1.2.2).
16 41.42. Service Option Response Order: The base station shall process the message
18 3.6.4.1.2.2).
19 42.43. Service Request Message: The base station shall process the message in
21 3.6.4.1.2.2).
22 43.44. Service Response Message: The base station shall process the message in
24 3.6.4.1.2.2).
25 44.45. SSD Update Confirmation Order
26 45.46. SSD Update Rejection Order
27 46.47. Status Response Message
28 47.48. Status Message
29 48.49. Supplemental Channel Request Message: The base station may respond with
30 a Supplemental Channel Assignment Message, an Extended Supplemental
31 Channel Assignment Message, or a Retry Order.
32 49.50. Supplemental Channel Request Mini Message: The base station may respond
33 with a Forward Supplemental Channel Assignment Mini Message or a Reverse
34 Supplemental Channel Assignment Mini Message, or both. The base station may
35 also respond with a Retry Order.
36 50.51. TMSI Assignment Completion Message
37 51.52. User Zone Update Request Message: The base station shall process this
38 message as specified in 3.6.7.2.
3-57
3GPP2 C.S0005-A v6.0
1 3.6.4.4 Release Substate
2 In this substate, the base station disconnects all calls and physical channels.
3 While in the Release Substate, the base station shall perform the following:
4 • The base station shall transmit the power control subchannel as specified in [2].
5 • The base station shall transmit on the Forward Traffic Channel for at least T3b
6 seconds. The base station shall transmit null traffic and power control bits on the
7 Forward Fundamental Channel, except when transmitting signaling traffic, if the
8 Fundamental Channel is present or transmit power control bits on the Forward
9 Dedicated Control Channel, if only the dedicated Control Channel is present. After
10 T3b seconds, the base station should stop transmitting on the Forward Traffic
11 Channel.
12 • The base station shall process Reverse Traffic Channel signaling traffic and may
13 discard other types of Reverse Traffic Channel traffic.
14 • The base station may perform TMSI assignment procedures (see 2.3.15).
15 • The base station may perform Forward Traffic Channel power control as specified in
16 3.6.4.1.1.
17 • The base station may send a Service Option Control Message to invoke a service
18 option specific function in accordance with the requirements for the active service
19 subfunction (see 3.6.4.1.2.2).
20 • The base station may send the following messages. Some of these messages are
21 generated by the Call Control Instance. If the base station sends a message, the
22 base station shall comply with the specified requirements for sending the message,
23 if any.
24 1. Alert With Information Message
25 2. Audit Order
26 3. Candidate Frequency Search Request Message
27 4. Candidate Frequency Search Control Message
29 6. Extended Alert With Information Message
30 7. Extended Handoff Direction Message
31 8. Extended Neighbor List Update Message
32 9. Extended Release Message
33 10. Extended Supplemental Channel Assignment Message
34 11. Forward Supplemental Channel Assignment Mini Message
35 12. General Handoff Direction Message
36 13. In-Traffic System Parameters Message
3-58
3GPP2 C.S0005-A v6.0
2 15. Lock Until Power-Cycled Order: The base station should send this order in
3 unassured mode.
4 16. Maintenance Order
5 17. Maintenance Required Order
6 18. Mobile Assisted Burst Operation Parameters Message
7 19. Mobile Station Registered Message
8 20. Neighbor List Update Message
9 21. Parameter Update Order (see 2.3.12.1.3 or 3.7.4).
10 22. Power Control Message
11 23. Power Control Parameters Message
12 24. Power Up Function Message
13 25. Power Up Function Completion Message
15 27. Resource Allocation Message
16 28. Resource Allocation Mini Message
17 29. Resource Release Request Message
18 30. Resource Release Request Mini Message
19 31. Resource Request Message
20 32. Resource Request Mini Message
21 33. Retrieve Parameters Message
22 34. Reverse Supplemental Channel Assignment Mini Message
23 35. Service Option Control Message: The base station shall send the message in
25 3.6.4.1.2.2).
27 37. Status Request Message
28 38. Status Request Order
29 39. Supplemental Channel Assignment Message
30 40. TMSI Assignment Message
31 41. Universal Handoff Direction Message
33 43. User Zone Update Message
3-59
3GPP2 C.S0005-A v6.0
1 • If the base station receives one of the following messages from the mobile station,
3 if any:
4 1. Base Station Challenge Order: The base station shall process the message as
6 2. Call Cancel Message
7 3. Candidate Frequency Search Report Message: The base station shall process the
9 4. Candidate Frequency Search Response Message: The base station shall process
11 5. Connect Order: If the CON_REF_INCL field is not included in this message or if

12 the CON_REF_INCL field equals ‘0’, the layer 3Layer 3 shall deliver this message
13 to the Call Control instance identified by NULL; otherwise, the layer 3Layer 3
14 shall deliver this message to the Call Control instance identified by CON_REF.
15 6. Continuous DTMF Tone Order: If the CON_REF_INCL field is not included in this
19 by CON_REF.
21 8. Enhanced Origination Message
22 9. Extended Flash With Information Message: If CON_REF_INCL equals ‘0’, the layer
24 NULL; otherwise, the layer 3Layer 3 shall deliver this message to the Call
25 Control instance identified by CON_REF.
26 10. Extended Handoff Completion Message: The base station shall process the
28 11. Extended Pilot Strength Measurement Message: The base station shall process
30 12. Extended Release Response Message:
31 13. Flash With Information Message: The layer 3Layer 3 shall deliver this message to
32 the Call Control instance identified by NULL.
33 14. Handoff Completion Message: The base station shall process the message as
34 described in 3.6.6.2.2.7.
35 15. Local Control Response Order
36 16. Long Code Transition Request Order
37 17. Long Code Transition Response Order
3-60
3GPP2 C.S0005-A v6.0
1 18. Mobile Station Reject Order: If the CON_REF_INCL field is included in this
2 message, layer 3Layer 3 shall perform the following: if the CON_REF_INCL field
3 equals ‘0’, layer 3Layer 3 shall send a ‘messages rejected indication’ to the Call
4 Control instance identified by NULL; otherwise, layer 3Layer 3 shall send a
5 ‘messages rejected indication’ to the Call Control instance identified by
6 CON_REF.
7 19. Origination Continuation Message: The layer 3Layer 3 shall deliver this message
8 to the Call Control instance identified by NULL.
9 20. Parameter Update Confirmation Order
10 21. Parameters Response Message
11 22. Periodic Pilot Strength Measurement Message
12 23. Pilot Strength Measurement Message: The base station shall process the message
14 24. Power Measurement Report Message
16 26. Request Analog Service Order
17 27. Request Narrow Analog Service Order
18 28. Request Wide Analog Service Order
19 29. Send Burst DTMF Message: If the CON_REF_INCL field is not included in this
23 by CON_REF.
25 31. Service Option Control Message: The base station shall process the message in
27 3.6.4.1.2.2).
32 36. Service Response Message:
33 37. SSD Update Confirmation Order
34 38. SSD Update Rejection Order
35 39. Status Response Message
36 40. Status Message
3-61
3GPP2 C.S0005-A v6.0
1 41. TMSI Assignment Completion Message
2 42. User Zone Update Request Message: The base station shall process this message
3 as specified in 3.6.7.2.
4 3.6.5 Registration
5 Registration is the process by which a mobile station notifies the base station of its location,
6 status, identification, slot cycle, and other characteristics. The base station can make use
7 of location information to efficiently page the mobile station when establishing a mobile
8 station terminated call. Registration also provides the mobile station’s
9 SLOT_CYCLE_INDEX parameter so that the base station can determine which Paging
10 Channel or Forward Common Control Channel slots a mobile station operating in the
11 slotted mode is monitoring. Registration also provides the protocol revision number so that
12 the base station knows the capabilities of the mobile station.
13 The CDMA system supports ten different forms of registration:
14 1. Power-up registration. The mobile station registers when it powers on, or switches
15 from using the analog system.
16 2. Power-down registration. The mobile station registers when it powers off if

17 previously registered in the current serving system.
18 3. Timer-based registration. The mobile station registers when a timer expires.
19 4. Distance-based registration. The mobile station registers when the distance

20 between the current base station and the base station in which it last registered
21 exceeds a threshold.
22 5. Zone-based registration. The mobile station registers when it enters a new zone.
23 6. Parameter-change registration. The mobile station registers when certain of its

24 stored parameters change or when it enters a new system.
25 7. Ordered registration. The mobile station registers when the base station requests
26 it.
27 8. Implicit registration. When a mobile station successfully sends an Origination

28 Message or Page Response Message, the base station can infer the mobile station’s
29 location. This is considered an implicit registration.
30 9. Traffic Channel registration. Whenever the base station has registration

31 information for a mobile station that has been assigned to a Traffic Channel, the
32 base station can notify the mobile station that it is registered.
33 10. User Zone Registration. The mobile station registers when it selects an active User
34 Zone (see 2.6.9.1.2).
35 The first five forms of registration, as a group, are called autonomous registration and are
36 conditioned, in part, by roaming status and by indicators contained in the System
37 Parameters Message and ANSI-41 System Parameters Message (see 2.6.5.3). The base
38 station may initiate ordered registration through the Registration Request Order.
3-62
3GPP2 C.S0005-A v6.0
1 The base station can obtain registration information by sending the Status Request Message
2 to the mobile station on the Paging Channel, the Forward Common Control Channel, or the
3 Forward Traffic Channel. If the base station is operating with the mobile station in Band
4 Class 0, the base station can also obtain registration information by sending the Status
5 Request Order to the mobile station on the Forward Traffic Channel. The base station may
6 notify the mobile station that it is registered through the Mobile Station Registered Message.
7 3.6.5.1 Registration on the Common Channels
8 The base station shall specify the forms of registration that are enabled, the corresponding
9 registration parameters, and the roaming status conditions for which registration is enabled
10 in the System Parameters Message and ANSI-41 System Parameters Message. If any of the
11 autonomous registration forms are enabled, the base station should also enable parameter-
12 change registration.
13 The base station should process an Origination Message or Page Response Message sent on
14 the r-csch as an implicit registration of the mobile station sending the message. The base
15 station can obtain complete registration information about the mobile station at any time
16 by sending a Registration Request Order to the mobile station.
17 3.6.5.2 Registration on the Traffic Channels
18 The base station can obtain registration information from a mobile station on the Traffic
19 Channel by means of the Status Request Message or the Status Request Order. When the
20 base station has registration information for a mobile station, the base station may send a
21 Mobile Station Registered Message to the mobile station, specifying the base station’s
22 registration system, zone, and location information.
23 3.6.6 Handoff Procedures
24 3.6.6.1 Overview
25 3.6.6.1.1 Types of Handoff
26 The base station supports the following three handoff procedures:

27 • Soft Handoff: A handoff in which a new base station commences communications
28 with the mobile station without interrupting the communications with the old base
29 station. The base station3 can direct the mobile station to perform a soft handoff
30 only when all Forward Traffic Channels assigned to the mobile station have identical
31 band classes, frequency assignments and frame offsets. Soft handoff provides
32 diversity of Forward Traffic Channels and Reverse Traffic Channel paths on the
33 boundaries between base stations.
3In this section the term base station may imply multiple cells or sectors.
3-63
3GPP2 C.S0005-A v6.0
1 • CDMA-to-CDMA Hard Handoff: A handoff in which the base station directs the
2 mobile station to transition between disjoint sets of base stations, different band
3 classes, different frequency assignments, different radio configuration, or different
4 frame offsets.
5 • CDMA-to-Analog Handoff: A handoff in which the base station directs the mobile
6 station from a Forward Traffic Channel to an analog voice channel.
7 Base station support of CDMA-to-CDMA hard handoff between different band classes and
8 support of CDMA-to-analog handoff is optional.
9 Section 2.6.6 describes the mobile station requirements during handoff.
10 3.6.6.1.2 Active Set
11 The Active Set contains the pilots (see 2.6.6.1.2) associated with the Forward Traffic
12 Channels assigned to the mobile station. Initially the base station informs the mobile
13 station of the contents of the Active Set using the Channel Assignment Message or the
14 Extended Channel Assignment Message; subsequent changes to the contents of the Active
15 Set are provided using the Extended Handoff Direction Message, General Handoff Direction
16 Message, or Universal Handoff Direction Message.
18 3.6.6.2.1 Overhead Information
19 The base station sends the following messages governing the pilot search procedures
20 performed by the mobile station:
22 • In-Traffic System Parameters Message
25 • Neighbor List Update Message
26 • Extended Neighbor List Update Message
28 • General Handoff Direction Message
29 • Extended Handoff Direction Message
30 • Candidate Frequency Search Request Message
31 • Candidate Frequency Search Control Message
32 • Universal Handoff Direction Message
3-64
3GPP2 C.S0005-A v6.0
1 3.6.6.2.1.1 System Parameters
2 The base station sends handoff related parameters on the Paging Channel in the System
3 Parameters Message and the Extended System Parameters Message, and on the Primary
4 Broadcast Control Channel in the MC-RR Parameters Message.
5 The base station may revise handoff related parameters for a mobile station operating on
6 the Traffic Channel by sending the In-Traffic System Parameters Message.
7 The base station may modify the values of the parameters SRCH_WIN_A, T_ADD, T_DROP,
8 T_COMP, and T_TDROP through the Extended Handoff Direction Message, the General
9 Handoff Direction Message, or the Universal Handoff Direction Message. In addition, the
10 base station may also modify the values of the parameters SRCH_WIN_N, SRCH_WIN_R,
11 SOFT_SLOPE, ADD_INTERCEPT, and DROP_INTERCEPT through the General Handoff
12 Direction Message or the Universal Handoff Direction Message.
13 3.6.6.2.1.2 Neighbor List

14 The base station sends a Neighbor List on the Paging Channel in the Neighbor List Message,
15 the Extended Neighbor List Message, or the General Neighbor List Message. The base station
16 should list the pilots in the Neighbor List Message in descending priority order (see
17 2.6.6.2.6.3).
18 The base station may revise the Neighbor List for a mobile station operating on the Traffic
19 Channel by sending a Neighbor List Update Message or an Extended Neighbor List Update
20 Message.
21 The base station shall not include a pilot that is a member of the mobile station’s Active Set
22 in a Neighbor List Update Message or an Extended Neighbor List Update Message. The base
23 station shall not specify more than N8m pilots in the Neighbor List Message, Extended
24 Neighbor List Message, General Neighbor List Message, or in the Extended Neighbor List
25 Update Message. The base station shall not specify more than 20 pilots in the Neighbor List
26 Update Message. The base station should list the pilots in the Neighbor List Update
27 Message in descending priority order (see 2.6.6.2.6.3).
28 The base station may also indicate the availability of neighboring analog systems in the
29 General Neighbor List Message to assist the mobile station in performing system reselection
30 (see 2.6.2.1.6).
31 3.6.6.2.1.3 Candidate Frequency Neighbor List
32 The base station sends a Candidate Frequency Neighbor List and inter-frequency hard
33 handoff related parameters in the Candidate Frequency Search Request Message. The base
34 station shall not specify more than N8m pilots in the Candidate Frequency Search Request
35 Message.
36 3.6.6.2.1.4 Candidate Frequency Search List
37 The base station designates a subset of the Candidate Frequency Neighbor List included in
38 the Candidate Frequency Search Request Message as the Candidate Frequency Search List.
39 For each pilot belonging to the Candidate Frequency Search List, the base station shall set
3-65
3GPP2 C.S0005-A v6.0
1 the corresponding SEARCH_SET field of the Candidate Frequency Search Request Message
2 to ‘1’.
3 3.6.6.2.2 Call Processing During Handoff
4 3.6.6.2.2.1 Processing the Pilot Strength Measurement Message
5 The base station should use the pilot strength measurements in the Pilot Strength
6 Measurement Message or the Extended Pilot Strength Measurement Message to determine a
7 new Active Set.
8 The base station may also use the PN phase measurements in the Pilot Strength
9 Measurement Message or the Extended Pilot Strength Measurement Message to estimate the
10 propagation delay to the mobile station. This estimate can be used to reduce Reverse
11 Traffic Channel acquisition time.
12 The base station may respond to a Pilot Strength Measurement Message or an Extended Pilot
13 Strength Measurement Message received from the mobile station by sending the Extended
14 Handoff Direction Message, the General Handoff Direction Message, or the Universal Handoff
16 3.6.6.2.2.2 Processing the Extended Handoff Direction Message
17 The base station shall maintain a handoff message sequence number. If the base station
18 specifies that the mobile station is to use service negotiation, the base station shall set the
19 SERV_NEG variable (see 3.6.4.1.2.1.4) to be enabled at the action time of the message. The
20 sequence number shall be initialized to zero prior to the transmission of the first Extended
21 Handoff Direction Message, General Handoff Direction Message (see 3.6.6.2.2.10), or the
22 Universal Handoff Direction Message to the mobile station. The base station shall increment
23 the sequence number modulo 4 each time the base station modifies the pilot list (including
24 the order in which pilots are specified within the list) or the code channels (including a
25 change in the ordering such that the first code channel occurrence for any pilot is changed)
26 sent to the mobile station in an Extended Handoff Direction Message, a General Handoff
27 Direction Message, or a Universal Handoff Direction Message.
28 Following a hard handoff, the base station should set the handoff message sequence
29 number to the value of the LAST_HDM_SEQ field of the Handoff Completion Message or
30 Extended Handoff Completion Message and should use the pilot order contained in the
31 Handoff Completion Message or Extended Handoff Completion Message to interpret the
32 contents of subsequent Power Measurement Report Messages.
33 The base station shall set the contents of an Extended Handoff Direction Message according
34 to the following rules:
35 • An Extended Handoff Direction Message shall list no more than N6m pilots in the
36 new Active Set.
37 • An Extended Handoff Direction Message shall identify the identical power control
38 subchannels (i.e., those carrying identical power control bits).
3-66
3GPP2 C.S0005-A v6.0
1 • An Extended Handoff Direction Message may change the code channel associated
2 with an Active Set pilot that remains in the new Active Set.
3 • The base station specifies the long code mask to be used on the new Forward Traffic
4 Channel by using the PRIVATE_LCM field of the Extended Handoff Direction
5 Message. The base station may change the long code mask to be used on the new
6 Forward Traffic Channel via the PRIVATE_LCM field of the Extended Handoff
7 Direction Message only for CDMA-to-CDMA hard handoffs. If a change of long code
8 mask is specified and the base station does not specify an explicit action time in the
9 Extended Handoff Direction Message, the base station shall begin using the new long
10 code mask on the first 80 ms boundary (relative to System Time) occurring at least
11 80 ms after the end of the frame containing the last bit of the message.
12 • For CDMA-to-CDMA handoffs, the base station may require the mobile station to
13 perform a reset of the acknowledgment procedures by using the RESET_L2 field of
14 the Extended Handoff Direction Message. If the base station requires the mobile
15 station to reset the acknowledgment procedures, Layer 3 shall send an indication to
16 Layer 2 to reset the acknowledgment procedures (see 3.2.1.1 and 3.2.2.1 of [4]). The
17 acknowledgment procedures shall be reset immediately after the action time of the
18 Extended Handoff Direction Message.
19 • For CDMA-to-CDMA hard handoffs, the base station may alter the frame offset by
20 setting the FRAME_OFFSET field to a new value. If the base station specifies a new
21 frame offset and does not specify an explicit action time, the base station shall
22 change its Forward and Reverse Traffic Channel frame offsets at the second 80 ms
23 boundary (relative to System Time) after the end of transmission of the Extended
24 Handoff Direction Message, unless the end of transmission of the message coincides
25 with an 80 ms boundary, in which case the change in frame offsets shall occur 80
26 ms after the end of transmission.
27 • For CDMA-to-CDMA hard handoffs to Band Class 0 or Band Class 3, the base
28 station may alter the nominal transmit power offset after handoff by setting the
29 NOM_PWR field to the new nominal transmit power offset. For CDMA-to-CDMA
30 hard handoffs to band classes other than Band Class 0 and Band Class 3, the base
31 station may alter the nominal transmit power offset after handoff by setting both the
32 NOM_PWR and NOM_PWR_EXT fields to the new nominal transmit power offset.
33 • The base station may specify a different band class by setting the BAND_CLASS and
34 CDMA_FREQ fields to the band class and CDMA frequency assignment respectively.
35 The base station shall not specify a band class not supported by the mobile station.
36 • If the base station sends the Extended Handoff Direction Message in assured mode,
37 the base station should set the action time of the message such that there is
38 sufficient time for the mobile station to transmit a message containing the
39 acknowledgment prior to the action time.
3-67
3GPP2 C.S0005-A v6.0
1 • For CDMA-to-CDMA hard handoffs, the base station may specify whether the mobile
2 station is to use service negotiation or service option negotiation by setting the
3 SERV_NEG_TYPE field of the Extended Handoff Direction Message. If the base
4 station specifies that the mobile station is to use service negotiation, the base
5 station shall set the SERV_NEG variable (see 3.6.4.1.2.1.4) to enabled at the action
6 time of message. If the base station specifies that the mobile station is to use
7 service option negotiation, the base station shall set SERV_NEG to disabled at the
9 3.6.6.2.2.3 Processing the Candidate Frequency Search Request Message

10 The base station may send a Candidate Frequency Search Request Message to direct the
11 mobile station to perform a single or periodic search on the Candidate Frequency.
12 The base station may request the mobile station to perform an aligned search of the
13 Candidate Frequency Search Set (see 2.6.6.2.8.3). If the base station requests the mobile
14 station to perform an aligned search, the base station shall specify an explicit action time
15 for the Candidate Frequency Search Request Message.
16 The base station shall maintain a search message sequence number. The sequence number
17 shall be initialized to zero prior to the transmission of the first Candidate Frequency Search
18 Request Message to the mobile station. Each time the base station sends a new Candidate
19 Frequency Search Request Message to the mobile station, it shall set the CFSRM_SEQ field
20 to the current value of the sequence number, and increment the sequence number modulo
21 4.
22 3.6.6.2.2.4 Processing the Candidate Frequency Search Response Message
23 The base station should use the mobile station’s search capabilities as reported in the
24 Candidate Frequency Search Response Message to determine an appropriate period for the
25 mobile station’s periodic search on the Candidate Frequency.
26 3.6.6.2.2.5 Processing the Candidate Frequency Search Control Message
27 The base station may send a Candidate Frequency Search Control Message to direct the
28 mobile station to perform a single search, or to start or stop a periodic search on the
30 The base station may request the mobile station to perform an aligned search of the
31 Candidate Frequency Search Set (see 2.6.6.2.8.3). If the base station requests the mobile
32 station to perform an aligned search, the base station shall specify an explicit action time
33 for the Candidate Frequency Search Control Message.
34 Each time the base station sends a new Candidate Frequency Search Control Message to the
35 mobile station, it shall set the CFSCM_SEQ field to the current value of the sequence
36 number, and increment the sequence number modulo 4.
3-68
3GPP2 C.S0005-A v6.0
1 3.6.6.2.2.6 Processing the Candidate Frequency Search Report Message
2 The base station should use the value of the LAST_SRCH_MSG field and of the
3 LAST_SRCH_MSG_SEQ field of the Candidate Frequency Search Report Message to interpret
4 the contents of the message.
5 If the SEARCH_MODE field of the Candidate Frequency Search Report Message is equal to
6 ‘0000’, the base station should use the pilot strength measurements in the message to
7 determine whether to direct the mobile station to perform a CDMA-to-CDMA inter-
8 frequency handoff, and to determine the new Active Set. If the SEARCH_MODE field of the
9 Candidate Frequency Search Report Message is equal to ‘0001’, the base station should use
10 the analog frequency strength measurements in the message to determine whether to direct
11 the mobile station to perform a CDMA-to-Analog handoff.
12 3.6.6.2.2.7 Transmitting During Handoff
13 The base station shall continue transmission to the mobile station on the Fundamental
14 Channel or the Dedicated Control Channel of a Forward Traffic Channel removed from the
15 Active Set until it receives the Handoff Completion Message or Extended Handoff Completion
16 Message from the mobile station or determines that the call has been released.
17 The base station should discontinue transmission to the mobile station on the
18 Fundamental Channel or the Dedicated Control Channel of a Forward Traffic Channel
19 removed from the Active Set after it receives the Handoff Completion Message or Extended
20 Handoff Completion Message.
21 For Forward Multiplex Options 3 through 16, the base station should discontinue
22 transmission of Forward Supplemental Code Channels removed from the Code Channel List
23 according to the following rules:
24 • If a General Handoff Direction Message is used to remove one or more Forward

25 Supplemental Code Channels, the base station should discontinue transmission on
26 those code channels no later than the action time of the General Handoff Direction
27 Message.
28 • If a Supplemental Channel Assignment Message is used to remove one or more

29 Forward Supplemental Code Channels, the base station should discontinue
30 transmission on those Forward Supplemental Code Channels no later than the
31 implicit action time of the Supplemental Channel Assignment Message.
32 3.6.6.2.2.8 Ordering Pilot Measurements From the Mobile Station

33 The base station may direct the mobile station to send a Pilot Strength Measurement
34 Message by sending a Pilot Measurement Request Order.
35 The base station may send a Periodic Pilot Measurement Request Order to direct the mobile
36 station to send pilot strength measurements one time or periodically. In response to the
37 order, the mobile station reports the pilot strength measurements using the Periodic Pilot
38 Strength Measurement Message.
3-69
3GPP2 C.S0005-A v6.0
1 3.6.6.2.2.9 Processing the Supplemental Channel Assignment Message
2 The base station may use this message to specify Supplemental Code Channel assignment
3 parameters for the mobile station’s Forward Traffic Channel, Reverse Traffic Channel, or
4 both. This information includes the parameters that control the timing of the Supplemental
5 Code Channel assignment (e.g., starting time and duration), and parameters that control
6 the number of Supplemental Code Channels which will be used during the assignment
7 (e.g., the number of Reverse Supplemental Code Channels on which the mobile station may
8 transmit and the set of Walsh codes on which the mobile station receives Forward
9 Supplemental Code Channels for each pilot in the mobile station’s Active Set). The
10 Supplemental Channel Assignment Message shall be used only with Multiplex Options 3
11 through 16.
12 The base station shall set the content of a Supplemental Channel Assignment Message
13 according to the following rules:
14 • The base station may set USE_RETRY_DELAY to ‘1’ and RETRY_DELAY to a delay in
15 320 ms units starting at the next 80 ms system time boundary during which the
16 mobile station is to refrain from sending subsequent Supplemental Channel Request
17 Messages. The base station may set RETRY_DELAY to ‘11111111’ to indicate that
18 the mobile station is to refrain from transmitting Supplemental Channel Request
19 Messages indefinitely. Otherwise, the base station shall set USE_RETRY_DELAY to
20 ‘0’ and omit RETRY_DELAY in which case the mobile station is to reset any
21 previously set RETRY_DELAY indication.
22 • The base station shall set REV_DTX_DURATION to the maximum duration of time in
23 units of 20 ms that the mobile station is allowed to stop transmission on a Reverse
24 Supplemental Code Channel before resuming transmission on the Reverse
25 Supplemental Code Channel within the reverse assignment duration. The base
26 station shall set this field to ‘0000’ if the mobile station is to stop using a Reverse
27 Supplemental Code Channel once it has stopped transmitting on that Reverse
28 Supplemental Code Channel. The base station shall set this field to ‘1111’ if the
29 mobile station is allowed to resume transmission on a Reverse Supplemental Code
30 Channel at any time within the reverse assignment duration.
31 • A Supplemental Channel Assignment Message may specify Reverse Supplemental
32 Code Channel assignments. If Reverse Supplemental Code Channel assignment
33 information is included, the base station shall set REV_INCLUDED to ‘1’ and include
34 the appropriate Reverse Supplemental Code Channel assignment information.
35 Otherwise, the base station shall set REV_INCLUDED to ‘0’.
36 • The base station shall indicate the implicit, explicit, or linked start time for a
37 Reverse Supplemental Code Channel assignment as follows:
38 – The base station may set EXPL_REV_START_TIME to ‘1’ and set

39 REV_START_TIME to the System Time, in units of 80 ms (modulo 64), at which
40 the mobile station is to start transmitting on the Reverse Supplemental Code
41 Channels.
3-70
3GPP2 C.S0005-A v6.0
1 – The base station may set USE_REV_HDM_SEQ to ‘1’ and set

2 REV_LINKED_HDM_SEQ to the sequence number of the General Handoff
3 Direction Message (HDM_SEQ) with which this message is linked to indicate that
4 the mobile station is to start processing the Reverse Supplemental Code
5 Channels at the action time of the linked General Handoff Direction Message.
6 – The base station may set EXPL_REV_START_TIME to ‘0’ and

7 USE_REV_HDM_SEQ to ‘0’ to indicate that the mobile station is to start
8 processing Reverse Supplemental Code Channels at the implicit action time of
9 this message.
10 – The base station shall not set both EXPL_REV_START_TIME and

11 USE_REV_HDM_SEQ to ‘1’.
12 • The base station may set USE_REV_DURATION to ‘1’ and REV_DURATION to the
13 time interval, in units of 80 ms, after the implicit, explicit, or linked action time for
14 the message (as specified in 2.6.6.2.5.1), during which the mobile station is to
15 transmit on the specified Reverse Supplemental Code Channels. The base station
16 may set USE_REV_DURATION to ‘0’ to indicate an infinite duration for the
17 assignment of Reverse Supplemental Code Channels. If NUM_REV_CODES is ‘000’,
18 then the base station shall set USE_REV_DURATION to ‘0’.
19 • If Reverse Supplemental Code Channel assignment information is included, the base

20 station shall set NUM_REV_CODES to the number of Reverse Supplemental Code
21 Channels to be used in this Reverse Supplemental Code Channel assignment. The
22 base station shall not set NUM_REV_CODES to be greater than the number of codes
23 supported by the currently negotiated multiplex option.
24 • The base station may set USE_T_ADD_ABORT, the Reverse Supplemental Code
25 Channel assignment T_ADD abort indicator, to ‘1’ to indicate that the mobile station
26 is to abort Reverse Supplemental Code Channel assignments implicitly when a
27 T_ADD trigger occurs. Otherwise, the base station shall set USE_T_ADD_ABORT to
28 ‘0’. If NUM_REV_CODES is set to ‘000’, the base station shall set
29 USE_T_ADD_ABORT to ‘0’.
30 • If the base station is sending this message in response to a Supplemental Channel
31 Request Message which includes a Supplemental Channel Request Message sequence
32 number and the mobile station is to clear the IGNORE_SCAM field, the base station
33 shall set USE_SCRM_SEQ_NUM to ‘1’ and set SCRM_SEQ_NUM to the sequence
34 number corresponding to the SCRM_SEQ_NUM field in a Supplemental Channel
35 Request Message to which the mobile station is to match this message. Otherwise,
36 the base station shall set USE_SCRM_SEQ_NUM to ‘0’ and omit SCRM_SEQ_NUM.
37 • A Supplemental Channel Assignment Message may specify Forward Supplemental
38 Code Channel assignments. If Forward Supplemental Code Channel assignment
39 information is included, the base station shall set FOR_INCLUDED to ‘1’ and include
40 the appropriate Forward Supplemental Code Channel assignment information.
41 Otherwise, the base station shall set FOR_INCLUDED to ‘0’.
3-71
3GPP2 C.S0005-A v6.0
1 • The base station shall set FOR_SUP_CONFIG to ‘00’ if the mobile station is to stop
2 processing the forward supplemental code after the action time of the Supplemental
3 Channel Assignment Message. The base station should not transmit to the mobile
4 station on the Forward Supplemental Code Channels after the message takes effect.
5 • The base station shall set FOR_SUP_CONFIG to ‘01’ if the mobile station is to start
6 processing the Forward Supplemental Code Channels in the Code Channel List at
7 the implicit, explicit, or linked action time for the message as specified in
8 2.6.6.2.5.1.
9 • The base station shall set FOR_SUP_CONFIG to ‘10’ if the Forward Supplemental
10 Code Channels associated with the pilots in the Active set are specified in the
11 Supplemental Channel Assignment Message and is to stop processing Forward
12 Supplemental Code Channels at the implicit action time of the message. The base
13 station should not transmit to the mobile station on the Forward Supplemental
14 Code Channels after the message takes effect.
17 Supplemental Channel Assignment Message and the mobile station is to start
18 processing the Forward Supplemental Code Channels at the implicit, explicit, or
19 linked action time for the message as specified in 2.6.6.2.5.1.
20 • The base station shall set FOR_DURATION to the time interval, in units of 80 ms,
21 after the implicit, explicit, or linked action time for the message (as specified in
22 2.6.6.2.5.1), during which the mobile station is to process the specified Forward
23 Supplemental Code Channels. The base station may set USE_FOR_DURATION to ‘0’
24 to indicate an infinite duration for the allocation of Forward Supplemental Code
25 Channels. The base station should not transmit to the mobile station on the
26 Forward Supplemental Code Channels outside the time interval specified by
27 FOR_DURATION.
28 • The base station may set EXPL_FOR_START_TIME to ‘1’ and set FOR_START_TIME
29 to the System Time, in units of 80 ms (modulo 64), at which the mobile station is to
30 start processing the Forward Supplemental Code Channels.
31 • The base station may set USE_FOR_HDM_SEQ to ‘1’ and set

32 FOR_LINKED_HDM_SEQ to the sequence number of the General Handoff Direction
33 Message (HDM_SEQ) with which this message is linked to indicate that the mobile
34 station is to start processing the Forward Supplemental Code Channels at the action
35 time of the linked General Handoff Direction Message.
36 • The base station shall not set both USE_FOR_HDM_SEQ and

37 EXPL_FOR_START_TIME within a Supplemental Channel Assignment Message to ‘1’.
38 • The number of Supplemental Code Channels assigned by Supplemental Channel

39 Assignment Message shall not exceed the maximum number of Supplemental Code
40 Channels for the negotiated Forward Multiplex Option.
3-72
3GPP2 C.S0005-A v6.0
1 • The base station may set EXPL_FOR_START_TIME to ‘0’ and USE_FOR_HDM_SEQ

2 to ‘0’ to indicate that the mobile station is to start processing Forward Supplemental
3 Code Channels at the implicit action time of this message.
4 3.6.6.2.2.10 Processing the General Handoff Direction Message
5 The base station shall maintain a handoff message sequence number. The sequence
6 number shall be initialized to zero prior to the transmission of the first Extended Handoff
7 Direction Message, General Handoff Direction Message, or Universal Handoff Direction
8 Message (see 3.6.6.2.2.11) to the mobile station (see 2.6.6.2.2.2). The base station shall
9 increment the sequence number modulo 4 each time the base station modifies the pilot list
10 (including the order in which pilots are specified within the list) or the code channels
11 (including a change in the ordering such that the first code channel occurrence for any pilot
12 is changed) sent to the mobile station in an Extended Handoff Direction Message, or a
13 General Handoff Direction Message, or a Universal Handoff Direction Message.
19 The base station shall set the contents of a General Handoff Direction Message according to
21 • A General Handoff Direction Message shall list no more than N6m pilots in the new
22 Active Set.
23 • The base station may include a Service Configuration Information Record in the
24 General Handoff Direction Message to accept a service configuration proposed in a
25 Service Request Message or Service Response Message, and instruct the mobile
26 station to begin using the service configuration.
27 • A General Handoff Direction Message shall identify the identical power control
29 • A General Handoff Direction Message shall identify the transmit power level of the
30 power control subchannels to the transmit power level of 20 ms frames at a 9600
31 bps or 14400 bps rate on their respective associated channels (Forward
32 Fundamental Channel or Forward Dedicated Control Channel).
33 • For CDMA-to-CDMA handoffs, the base station may specify Power Control
34 Subchannel Gain action time (PC_ACTION_TIME]. If PC_ACTION_TIME is included
35 in this message, the base station shall apply the new FPC_SUBCHAN_GAIN at the
36 time specified by PC_ACTION_TIME. If the PC_ACTION_TIME is not included in this
37 message but the explicit action time is included, the base station shall apply the
38 new FPC_SUBCHAN_GAIN at the action time of the General Handoff Direction
39 Message. If the implicit action time is used, the base station should gradually apply
40 any change in FPC_SUBCHAN_GAIN.
3-73
3GPP2 C.S0005-A v6.0
1 • A General Handoff Direction Message may change the code channel associated with
2 an Active Set pilot that remains in the new Active Set.
4 Channel by using the PRIVATE_LCM field of the General Handoff Direction Message.
5 The base station may change the long code mask to be used on the new Forward
6 Traffic Channel via the PRIVATE_LCM field of the General Handoff Direction Message
7 only for CDMA-to-CDMA hard handoffs. If a change of long code mask is specified
8 and the base station does not specify an explicit action time in the General Handoff
9 Direction Message, the base station shall begin using the new long code mask on the
10 first 80 ms boundary (relative to System Time) occurring at least 80 ms after the end
11 of the frame containing the last bit of the message.
14 the General Handoff Direction Message. If the base station requires the mobile
17 acknowledgment procedures of the base station that the mobile station is to handoff
18 to shall be reset immediately after the action time of the General Handoff Direction
19 Message.
24 boundary (relative to System Time) after the end of transmission of the General
37 • If the base station sends the General Handoff Direction Message in assured mode,
3-74
3GPP2 C.S0005-A v6.0
1 • For CDMA-to-CDMA hard handoffs, the base station may specify whether the mobile
3 SERV_NEG_TYPE field of the General Handoff Direction Message. If the base station
4 specifies that the mobile station is to use service negotiation, the base station shall
5 set the SERV_NEG variable (see 3.6.4.1.2.1.4) to enabled at the action time of
6 message. If the base station specifies that the mobile station is to use service option
7 negotiation, the base station shall set SERV_NEG to disabled at the action time of
8 the message.
9 • The base station may specify whether the mobile station is to restore its
10 configuration to what it was before the handoff attempt, if it fails in the handoff
11 attempt using criteria specified in the Candidate Frequency Search Request Message,
12 by using the RETURN_IF_HANDOFF_FAIL field of the General Handoff Direction
13 Message. The base station may specify whether the mobile station is to periodically
14 search a CDMA Candidate Frequency for useable pilots, using criteria specified in
15 the Candidate Frequency Search Request Message, by using the PERIODIC_SEARCH
16 field of the General Handoff Direction Message.
17 • The base station may include Forward Supplemental Code Channel assignment
18 information in the General Handoff Direction Message if the Forward Multiplex
19 Option for the currently connected service option is 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,
20 14, 15, or 16. If Forward Supplemental Code Channel assignment information is
21 included, the base station shall include FOR_INCLUDED, set FOR_INCLUDED to ‘1’,
22 and include the appropriate Forward Supplemental Code Channel assignment
23 information.
24 • The number of Forward Supplemental Code Channels assigned by the General

25 Handoff Direction Message shall not exceed the maximum number of Forward
26 Supplemental Code Channels for the negotiated Forward Multiplex Option.
27 • The base station shall set FOR_SUP_CONFIG to ‘00’ if the mobile station is to stop
28 processing the Forward Supplemental Code Channel after the action time of General
29 Handoff Direction Message. The base station should not transmit to the mobile
30 station on the Forward Supplemental Code Channels after the message takes effect.
31 • The base station shall set FOR_SUP_CONFIG to ‘01’ if the mobile station is to start
32 processing the Forward Supplemental Code Channels in the Code Channel List at
33 the action time of the message.
36 General Handoff Direction Message and the mobile station is to stop processing
37 Forward Supplemental Code Channels at the implicit action time of the message.
38 The base station should not transmit to the mobile station on the Forward
39 Supplemental Code Channels after the message takes effect.
42 General Handoff Direction Message and the mobile station is to start processing the
43 Forward Supplemental Code Channels at the action time of the message.
3-75
3GPP2 C.S0005-A v6.0
1 • The base station shall set FOR_DURATION to the time interval after the action time
2 of the message, in units of 80 ms, during which the mobile station is to process the
3 specified Forward Supplemental Code Channels. The base station may set
4 USE_FOR_DURATION to ‘0’ to indicate an infinite duration for the allocation of
5 Forward Supplemental Code Channels. The base station should not transmit to the
6 mobile station on the Forward Supplemental Code Channels outside the time
7 interval specified by FOR_DURATION.
8 • If FOR_INCLUDED is included in the message, the base station shall include

9 EXPL_CODE_CHAN for each pilot included in the message. If EXPL_CODE_CHAN is
10 included and set to ‘1’ for a pilot, the code channels associated with the pilot in the
11 General Handoff Direction Message shall be ordered such that the first code channel
12 occurrence is associated with the Forward Fundamental Channel and the successive
13 occurrences are associated with Forward Supplemental Code Channels. If
14 EXPL_CODE_CHAN is included and is set to ‘0’, for each pilot in the new Active Set,
15 the base station shall include BASE_CODE_CHAN and set it to the base code
16 channel index in the range of 1 to (63 - NUM_FOR_SUP + 1), inclusive, that the
17 mobile station is to use as the first Forward Supplemental Code Channel associated
18 with this pilot. The mobile station is to use NUM_FOR_SUP adjacent code channels
19 beginning with index BASE_CODE_CHAN (i.e., BASE_CODE_CHAN through
20 BASE_CODE_CHAN + NUM_FOR_SUP - 1) for the Forward Supplemental Code
21 Channels associated with this pilot.
22 • The base station may include Reverse Supplemental Code Channel assignment
23 information in the General Handoff Direction Message if the Reverse Multiplex
24 Option is 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, or 16. If Reverse Supplemental
25 Code Channel assignment information is included, the base station shall include
26 REV_INCLUDED, set REV_INCLUDED to ‘1’, and include the appropriate Reverse
27 Supplemental Code Channel assignment information in the additional fields.
28 • If Reverse Supplemental Code Channel assignment information is included, the base

29 station shall set NUM_REV_CODES to the number of Reverse Supplemental Code
30 Channels to be used by the mobile station. The base station shall not set
31 NUM_REV_CODES to be greater than the number of codes supported by the
32 currently negotiated multiplex option.
33 • The base station may set USE_T_ADD_ABORT, the Reverse Supplemental Code
34 Channel assignment T_ADD abort indicator, to ‘1’ to indicate that the mobile station
35 is to abort Reverse Supplemental Code Channel assignments implicitly when a
36 T_ADD trigger occurs. Otherwise, the base station shall set USE_T_ADD_ABORT to
37 ‘0’. If NUM_REV_CODES is set to ‘000’, the base station shall set
38 USE_T_ADD_ABORT to ‘0’.
3-76
3GPP2 C.S0005-A v6.0
1 • The base station shall set REV_DTX_DURATION to the maximum duration of time in
2 units of 20 ms that the mobile station is allowed to stop transmission on a Reverse
3 Supplemental Code Channel before resuming transmission on the Reverse
4 Supplemental Code Channel. The base station shall set this field to ‘0000’ if the
5 mobile station is to stop using a Reverse Supplemental Code Channel once it has
6 stopped transmitting on that Reverse Supplemental Code Channel. The base station
7 shall set this field to ‘1111’ if the mobile station is allowed to resume transmission
8 on a Reverse Supplemental Code Channel at any time within the reverse assignment
9 duration.
10 • The base station may set CLEAR_RETRY_DELAY to ‘1’ to indicate that the mobile
11 station is to cancel any previously stored retry delay. Otherwise, the base station
12 shall set CLEAR_RETRY_DELAY to ‘0’ to indicate that the mobile station is to
13 continue to honor any previously stored retry delay (see 2.6.6.2.5.1).
14 • The base station may indicate a duration for the Reverse Supplemental Code
15 Channel assignment (in 80 ms superframes) by setting USE_REV_DURATION to ‘1’
16 and indicating the desired duration in the REV_DURATION field. If
17 USE_REV_DURATION is set to ‘0’, a duration of infinity is indicated, and the base
18 station shall set the REV_DURATION to ‘00000000’. If NUM_REV_CODES is ‘000’,
19 then the base station shall set USE_REV_DURATION to ‘0’ and shall set
20 REV_DURATION to ‘00000000’.
21 • The base station may set USE_REV_DURATION to ‘1’ and REV_DURATION to the
22 time interval after the action time of the message, in units of 80 ms, during which
23 the mobile station may transmit on the assigned Reverse Supplemental Code
24 Channels. The base station may set USE_REV_DURATION to ‘0’ to indicate an
25 infinite duration for the allocation of Forward Supplemental Code Channels.
26 • The base station may specify a closed loop power control step size by setting
27 USE_PWR_CNTL_STEP to ‘1’ and indicating the desired power control step size in
28 the PWR_CNTL_STEP field (see 2.1.2.3.2). Otherwise, the base station shall set
29 USE_PWR_CNTL_STEP to ‘0’. The base station shall not specify a power control step
30 size not supported by the mobile station.
31 3.6.6.2.2.11 Processing the Universal Handoff Direction Message
32 The base station shall maintain a handoff message sequence number. The sequence
33 number shall be initialized to zero prior to the transmission of the first Extended Handoff
34 Direction Message (see 3.6.6.2.2.2), General Handoff Direction Message (see 3.6.6.2.2.10), or
35 Universal Handoff Direction Message to the mobile station. The base station shall increment
36 the sequence number modulo 4 each time the base station modifies the pilot list (including
37 the order in which pilots are specified within the list) or the code channels (including a
38 change in the ordering such that the first code channel occurrence for any pilot is changed)
39 sent to the mobile station in an Extended Handoff Direction Message, a General Handoff
40 Direction Message, or an Universal Direction Message.
3-77
3GPP2 C.S0005-A v6.0
4 The base station shall set the contents of a Universal Handoff Direction Message according
5 to the following rules:
6 • A Universal Handoff Direction Message shall list no more than N6m pilots in the new
7 Active Set.
8 • The base station may include a Service Configuration Information Record in the
9 Universal Handoff Direction Message to accept a service configuration proposed in a
10 Service Request Message or Service Response Message, and instruct the mobile
11 station to begin using the service configuration.
12 • A Universal Handoff Direction Message shall identify the identical power control
14 • A Universal Handoff Direction Message shall identify the transmit power level of the
15 power control subchannels to the transmit power level of 20 ms frames at a 9600
16 bps or 14400 bps rate on their respective associated channels (Forward
17 Fundamental Channel or Forward Dedicated Control Channel).
18 • For CDMA-to-CDMA handoffs, the base station may specify Power Control
19 Subchannel Gain action time (PC_ACTION_TIME]. If PC_ACTION_TIME is included
20 in this message, the base station shall apply the new FPC_SUBCHAN_GAIN at the
21 time specified by PC_ACTION_TIME. If the PC_ACTION_TIME is not included in this
22 message but the explicit action time is included, the base station shall apply the
23 new FPC_SUBCHAN_GAIN at the action time of the Universal Handoff Direction
24 Message. If the implicit action time is used, the base station should gradually apply
25 any change in FPC_SUBCHAN_GAIN.
26 • A Universal Handoff Direction Message may change the code channel associated with
28 • A Universal Handoff Direction Message may delete the code channel associated with
30 • A Universal Handoff Direction Message may add the code channel associated with an
31 Active Set pilot that remains in the new Active Set.
33 Channel by using the PRIVATE_LCM field of the Universal Handoff Direction
34 Message. The base station may change the contents of this field only for CDMA-to-
35 CDMA hard handoffs. If a change of long code mask is specified and the base
36 station does not specify an explicit action time in the Universal Handoff Direction
37 Message, the base station shall begin using the new long code mask on the first 80
38 ms boundary (relative to System Time) occurring at least 80 ms after the end of the
39 frame containing the last bit of the message.
3-78
3GPP2 C.S0005-A v6.0
3 the Universal Handoff Direction Message. If the base station requires the mobile
6 acknowledgment procedures of the base station that the mobile station is to handoff
7 to shall be reset immediately after the action time of the General Handoff Direction
8 Message.
13 boundary (relative to System Time) after the end of transmission of the Universal
26 • If the base station sends the Universal Handoff Direction Message in assured mode,
30 • For CDMA-to-CDMA handoffs, the base station may specify whether the mobile
32 SERV_NEG_TYPE field of the Universal Handoff Direction Message. If the base
33 station specifies that the mobile station is to use service negotiation, the base
34 station shall set the SERV_NEG variable (see 3.6.4.1.2.1.4) to enabled at the action
35 time of message. If the base station specifies that the mobile station is to use
36 service option negotiation, the base station shall set SERV_NEG to disabled at the
3-79
3GPP2 C.S0005-A v6.0
1 • The base station may specify whether the mobile station is to restore its
2 configuration to what it was before the handoff attempt, if it fails in the handoff
3 attempt using criteria specified in the Candidate Frequency Search Request Message,
4 by using the RETURN_IF_HANDOFF_FAIL field of the Universal Handoff Direction
5 Message. The base station may specify whether the mobile station is to periodically
6 search a CDMA Candidate Frequency for useable pilots, using criteria specified in
7 the Candidate Frequency Search Request Message, by using the PERIODIC_SEARCH
8 field of the Universal Handoff Direction Message.
9 • The base station specifies Active Set for the Fundamental Channel only, the
10 Dedicated Control Channel only, or both. The Active Set of the Dedicated Control
11 Channel shall be the same as the Active Set of the Fundamental Channel when both
12 the Fundamental Channel and Dedicated Control Channel are assigned.
13 • The base station may specify the Active Set of the Supplemental Channels. The
14 Active Set of the Supplemental Channels shall be a subset of the Active Set of the
15 Fundamental Channel or the Dedicated Control Channel.
16 • A Universal Handoff Direction Message may specify a Reverse Supplemental Channel

17 assignment. If Reverse Supplemental Channel assignment information is included,
18 this message contains information that specifies the start time, duration, and the
19 data transfer rate associated with this Reverse Supplemental Channel assignment.
20 • A Universal Handoff Direction Message may specify a Forward Supplemental
21 Channel assignment. If Forward Supplemental Channel assignment information is
22 included, this message contains the start time, duration, and SCCL_INDEX
23 associated with this Forward Supplemental Channel assignment.
24 • A Universal Handoff Direction Message may update the mapping between a

25 particular SCCL_INDEX and a set of fields that specifies the data transfer rate, QOF
26 index, Forward Supplemental Channel Walsh code for each PILOT_PN, and the
27 active set for the Forward Supplemental Channel associated with FOR_SCH_ID.
28 • A Universal Handoff Direction Message may update REV_WALSH_ID field which
29 specifies the Reverse Supplemental Walsh cover.
30 • The base station may set CLEAR_RETRY_DELAY to ‘1’ to indicate that the mobile
31 station is to cancel any previously stored retry delay. Otherwise, the base station
32 shall set CLEAR_RETRY_DELAY to ‘0’ to indicate that the mobile station is to
33 continue to honor any previously stored retry delay (see 2.6.6.2.5.1).
34 3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message
35 The base station may use this message to carry Forward Supplemental Channel assignment
36 information or Reverse Supplemental Channel assignment information.
37 If Forward Supplemental Channel assignment information is included, this message

38 contains the start time, duration, and SCCL_INDEX associated with this Forward
39 Supplemental Channel assignment. If Reverse Supplemental Channel assignment
40 information is included, this message contains information that specifies the start time,
41 duration, and the number of information bits per frame (or set of number of bits per frame
3-80
3GPP2 C.S0005-A v6.0
1 if RSCH_VAR_TABLE_IDs[REV_SCH_IDr] is not equal to ‘000’) associated with this Reverse

2 Supplemental Channel assignment.
3 This message may specify the mapping between a particular SCCL_INDEX and a set of
4 fields that specifies the number of information bits per frame (or set of number of bits per
5 frame if FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is not equal to ‘000’), QOF index, Forward
6 Supplemental Channel Walsh code for each PILOT_PN, and the active set for the Forward
7 Supplemental Channel associated with FOR_SCH_ID.
8 This message may also include REV_WALSH_ID field which specifies the Reverse
9 Supplemental Walsh cover.
10 This message also includes START_TIME_UNIT for this message, Forward Supplemental
11 Channel Assignment Mini Messages, or Reverse Supplemental Channel Assignment Mini
12 Messages, or Universal Handoff Direction Message.
13 The base station shall set the contents of an Extended Supplemental Channel Assignment
14 Message according to the following rules:
15 • An Extended Supplemental Channel Assignment Message may specify a Reverse

16 Supplemental Channel assignment. The base station shall set NUM_REV_SCH to
17 the number of Reverse Supplemental Channels to be assigned.
18 • An Extended Supplemental Channel Assignment Message may specify a Forward

19 Supplemental Channel assignment. The base station shall set NUM_FOR_SCH to
20 the number of Forward Supplemental Channels to be assigned..
21 • The base station shall set the START_TIME_UNIT field to indicate the unit of the
22 FOR_SCH_START_TIME included in this message and the Forward Supplemental
23 Channel Assignment Mini Messages and REV_SCH_START_TIME included in this
24 message and the Reverse Supplemental Channel Assignment Mini Messages. The
25 base station shall set this field to one less than the number of 20 ms intervals that
26 is to be used by the mobile station for calculating the start time included in Forward
27 Supplemental Channel assignments or Reverse Supplemental Channel assignments.
28 • An Extended Supplemental Channel Assignment Message may specify Forward
29 Supplemental Channel configuration information. The base station shall set
30 NUM_FOR_SCH_CFG to the number of Forward Supplemental Channel to be
31 configured.
32 • The base station shall set the NUM_REC field to the number of instances of the
33 following record minus one included in this message. The base station shall set the
34 fields within each record as follows:
35 – The base station shall set the SCCL_INDEX field to the index of the
36 Supplemental Channel Code Information Record in the Supplemental
37 Channel Code List Table.
38 – The base station shall set the FOR_SCH_NUM_BITS_IDX field to the Forward
39 Supplemental Channel number of information bits index associated with
40 SCCL_INDEX.
3-81
3GPP2 C.S0005-A v6.0
1 – The base station shall set the NUM_SUP_SHO field to the number of Forward
2 Supplemental Channels minus one, corresponding to the FOR_SCH_ID and
3 the SCCL_INDEX, for which the frames are to be soft-combined by the
4 mobile station. The base station shall set the fields within each record as
5 follows:
6 + The base station shall set the PILOT_PN field to the pilot PN sequence
7 offset for this pilot in units of 64 PN chips.
8 + The base station shall set the QOF_MASK_ID_SCH field to the ID of the
9 Quasi Orthogonal Function mask ID corresponding to the Forward
10 Supplemental Channel Code index.
11 + The base station shall set the CODE_CHAN_SCH field to the code
12 channel on the Supplemental Channel corresponding to the PILOT_PN.
13 • REV_SCH_DTX_DURATION: The base station shall set REV_SCH DTX_DURATION to

14 the maximum duration of time in units of 20 ms that the mobile station is allowed
15 to stop transmission on a Reverse Supplemental Channel before resuming
16 transmission on the Reverse Supplemental Channel within the reverse assignment
17 duration. The base station shall set this field to ‘0000’ if the mobile station is to
18 stop using a Reverse Supplemental Channel once it has stopped transmitting on
19 that Reverse Supplemental Channel. The base station shall set this field to ‘1111’ if
20 the mobile station is allowed to resume transmission on a Reverse Supplemental
21 Channel at any time within the reverse assignment duration.
22 • The base station may set USE_T_ADD_ABORT, the Reverse Supplemental Channel
23 assignment T_ADD abort indicator, to ‘1’ to indicate that the mobile station is to
24 abort Reverse Supplemental Channel assignments when a T_ADD trigger occurs.
25 Otherwise, the base station shall set USE_T_ADD_ABORT to ‘0’.
26 • If the base station is sending this message in response to a Supplemental Channel
27 Request Message which includes a Supplemental Channel Request Message sequence
28 number and the mobile station is to clear the IGNORE_ESCAM field, the base
29 station shall set USE_SCRM_SEQ_NUM to ‘1’ and set SCRM_SEQ_NUM to the
30 sequence number corresponding to the SCRM_SEQ_NUM field in a Supplemental
31 Channel Request Message to which the mobile station is to match this message.
32 Otherwise, the base station shall set USE_SCRM_SEQ_NUM to ‘0’ and omit
33 SCRM_SEQ_NUM.
34 3.6.6.2.2.13 Processing of Forward Supplemental Channel Assignment Mini Message
35 The base station may use this message to specify Forward Supplemental Channel
36 assignment parameters for the mobile station’s Forward Supplemental Channel. This
37 information includes the FOR_SCH_ID, duration, start time, and the index to the previously
38 specified Forward Supplemental Channel Code List, which determines number of
39 information bits per frame (or set of number of bits per frame if
40 FSCH_VAR_TABLE_IDs[FOR_SCH_IDr] is not equal to ‘000’), code channel index, and the
41 identifier of the Quasi Orthogonal Function corresponding to the assignment.
3-82
3GPP2 C.S0005-A v6.0
1 The base station shall set the content of a Forward Supplemental Channel Assignment Mini
3 • The base station shall set the FOR_SCH_ID to Forward Supplemental Channel
4 identifier of the burst assignment that this message carries.
5 • The base station shall set the FOR_SCH_DURATION field to '0000' to indicate that
6 the mobile station should stop processing the Forward Supplemental Channel
7 starting at the explicit start time of the message specified by
8 FOR_SCH_START_TIME. The base station shall set the FOR_SCH_DURATION field
9 to ‘1111’ to indicate that the mobile station should process the Forward
10 Supplemental Channel, starting at the explicit start time of the message specified by
11 FOR_SCH_START_TIME, until a subsequent Forward Supplemental Channel
12 Assignment Mini Message or an Extended Supplemental Channel Assignment
13 Message with the same FOR_SCH_ID field is received. The base station shall set the
14 FOR_SCH_DURATION field to the duration in units of 20 ms (see Table 3.7.3.3.2.37-
15 3), starting at the explicit start time of the message specified by
16 FOR_SCH_START_TIME, during which the mobile station is to process the Forward
18 • The base station shall set the FOR_SCH_START_TIME field to the System Time, in
19 units of time specified by START_TIME_UNIT, (modulo 32) at which the mobile
20 station is to start processing the Forward Supplemental Channel specified in this
21 message. The explicit start time for processing Forward Supplemental Channels is
22 the time for which:
23 (t/(START_TIME_UNIT+1) − FOR_SCH_START_TIME) mod 32 = 0,
25 • The base station shall set the SCCL_INDEX field to the index of the record in the
26 Forward Supplemental Channel Code list corresponding to the FOR_SCH_ID.
27 • If the PILOT_GATING_USE_RATE to equal to ‘1’, the base station shall set

28 PILOT_GATING_USE_RATE to ‘0’ and start transmitting the Forward Power Control
29 Subchannel with the maximum rate at the action time of the message.
30 3.6.6.2.2.14 Processing of Reverse Supplemental Channel Assignment Mini Message
31 The base station may use this message to specify Reverse Supplemental Channel
32 assignment parameters for the mobile station Reverse Supplemental Channel. This
33 information includes the reverse supplemental channel identifier (REV_SCH_ID), the
34 duration of transmission on the Reverse Supplemental Channel, the start time for the burst
35 assignment, and the number of information bits per frame that the mobile station may
36 transmit.
37 The base station shall set the content of the Reverse Supplemental Channel Assignment Mini
3-83
3GPP2 C.S0005-A v6.0
1 • The base station shall set the REV_SCH_DURATION field to ‘0000’ to indicate that
2 the mobile station should stop transmitting on the Reverse Supplemental Channel
3 specified by REV_SCH_ID at the start time specified by REV_SCH_START_TIME.
4 The base station shall set this field to ‘1111’ to indicate that the mobile station may
5 transmit on the Reverse Supplemental Channel specified by REV_SCH_ID, starting
6 at the start time specified by REV_SCH_START_TIME. The base station shall set the
7 REV_SCH_DURATION field to the allocated duration (see Table 3.7.3.3.2.37-3),
8 starting at the start time specified by REV_SCH_START_TIME, during which the
9 mobile station may transmit on the Reverse Supplemental Channel specified by
10 REV_SCH_ID.
11 • The base station shall set the REV_SCH_START_TIME field to the System Time, in
12 units of time specified by START_TIME_UNIT, (modulo 32) at which the mobile
13 station may start transmitting on the Reverse Supplemental Channel specified in
14 this message. The explicit start time for transmitting on the Reverse Supplemental
15 Channel is the time for which:
16 (t/(START_TIME_UNIT+1) − REV_SCH_START_TIME) mod 32 = 0,
18 • The base shall set the REV_SCH_BITS_IDX (see Table 3.7.3.3.2.37-21) to indicate
19 the Reverse Supplemental Channel number of information bits per frame index.
20 • If the PILOT_GATING_USE_RATE to equal to ‘1’, the base station shall set

21 PILOT_GATING_USE_RATE to ‘0’ and start transmitting the Forward Power Control
22 Subchannel with the maximum rate at the action time of the message.
23 3.6.6.2.2.15 Processing of the Mobile Assisted Burst Operation Parameters Message
24 The base station may use this message to specify the operating parameters in the mobile
25 station for Mobile Assisted Burst Operation procedures.
26 • A Mobile Assisted Burst Operation Parameters Message may specify pilot strength
27 order change reporting information. If order change reporting information is
28 included, the base station shall set ORDER_FLAG to ‘1’ and include the appropriate
29 order change reporting fields. Otherwise, the base station shall set ORDER_FLAG to
30 ‘0’. If ORDER_FLAG is set to ‘1’, the base station shall perform the following
31 procedures:
32 – The base station shall set PS_MIN_DELTA to one less than the minimum pilot
33 strength measurement difference between any two pilots in the Active Set (in
34 units of 0.5 dB) that must be measured in order for the mobile station to send a
35 Pilot Strength Measurement Mini Message.
36 – The base station shall set ORDER_INTERVAL to the minimum interval (in 20 ms
37 units) during which the indicated pilot strength measurement difference (greater
38 than or equal to PS_MIN_DELTA + 1, in units of 0.5 dB) must be measured by
39 the mobile station in order for the mobile station to send a Pilot Strength
40 Measurement Mini Message.
3-84
3GPP2 C.S0005-A v6.0
1 • A Mobile Assisted Burst Operation Parameters Message may specify periodic pilot
2 strength reporting. If periodic reporting information is included, the base station
3 shall set PERIODIC_FLAG to ‘1’ and include the appropriate periodic reporting fields.
4 Otherwise, the base station shall set PERIODIC_FLAG to ‘0’. If PERIODIC_FLAG is
5 set to ‘1’, the base station shall perform the following procedures:
6 – The base station shall set NUM_PILOTS to the number of pilots for which the
7 mobile station is to send Pilot Strength Measurement Mini Messages.
8 – The base station shall set PERIODIC_INTERVAL to the interval (in 20 ms units)
9 between Pilot Strength Measurement Mini Messages.
10 • A Mobile Assisted Burst Operation Parameters Message may specify threshold based
11 pilot strength reporting. If threshold based reporting information is included, the
12 base station shall set THRESHOLD_FLAG to ‘1’ and include the appropriate
13 threshold based reporting fields. Otherwise, the base station shall set
14 THRESHOLD_FLAG to ‘0’. If THRESHOLD_FLAG is set to ‘1’, the base station shall
15 perform the following procedures:
16 – The base station shall set PS_FLOOR_HIGH to the high water mark for lower
17 limit threshold for which the mobile station is to send Pilot Strength Measurement
18 Mini Messages.
19 – The base station shall set PS_FLOOR_LOW to the low water mark for lower limit
20 threshold for which the mobile station is to send Pilot Strength Measurement Mini
21 Messages.
22 – The base station shall set PS_CEILING_HIGH to the high water mark for upper
24 Mini Messages.
25 – The base station shall set PS_CEILING_LOW to the low water mark for upper
27 Mini Messages.
28 – The base station shall set THRESHOLD_INTERVAL to the interval (in 20 ms

29 units) between Pilot Strength Measurement Mini Messages.
30 3.6.6.2.3 Active Set Maintenance
31 The base station shall maintain an Active Set for each mobile station under its control as
32 follows:
33 • When the base station sends the Channel Assignment Message, it shall initialize the
34 Active Set to contain only the pilot associated with the assigned Forward Traffic
35 Channel.
36 • When the base station sends the Extended Channel Assignment Message, it shall
37 initialize the Active Set to contain all pilots included in the message.
3-85
3GPP2 C.S0005-A v6.0
1 • When the base station sends an Extended Handoff Direction Message, General
2 Handoff Direction Message, or Universal Handoff Direction Message, it shall add to
3 the Active Set, before the action time of the message, all pilots included in the
4 message, if they are not already in the Active Set.
5 • The base station shall delete the pilots that were not included in the most recent
6 Extended Handoff Direction Message, General Handoff Direction Message, or
7 Universal Handoff Direction Message, from the Active Set upon receipt of the Handoff
8 Completion Message or Extended Handoff Completion Message.
9 3.6.6.2.4 Soft Handoff
10 The base station should use soft handoff when directing a mobile station from one Forward
11 Traffic Channel to another Forward Traffic Channel having the same frequency assignment.
12 3.6.6.2.4.1 Receiving During Soft Handoff
13 Each base station in the Active Set shall demodulate the Reverse Traffic Channel. The base
14 station should provide diversity combining of the demodulated signals obtained by each
15 base station in the Active Set.
16 3.6.6.2.4.2 Transmitting During Soft Handoff
17 The base station shall begin transmitting identical modulation symbols on all Forward
18 Traffic Channels specified in an Extended Handoff Direction Message or General Handoff
19 Direction Message, or Universal Handoff Direction Message (with the possible exception of
20 the power control subchannel) by the action time of the message.
21 The base station shall transmit identical power control bits on all identical power control
22 subchannels that were identified as such in the last Extended Handoff Direction Message, or
23 General Handoff Direction Message, or Universal Handoff Direction Message.
24 The base station shall use the same long code mask on all Forward Traffic Channels whose
25 associated pilots are in the Active Set.
26 3.6.6.2.5 CDMA-to-Analog Hard Handoff
27 The base station may direct the mobile station to perform a handoff from the CDMA system
28 to an analog system in a band class that the mobile station supports by sending an Analog
30 3.6.7 CDMA Tiered Services
31 3.6.7.1 Overview
32 3.6.7.1.1 Definition
33 The base station may support Tiered Services to provide individual users or groups of users
34 with custom services and special features based upon their location. The base station may
35 also support Tiered Services to provide private network support. Important to the operation
36 of CDMA Tiered Services is the concept of User Zones. It is via User Zones by which the
37 base station offers custom services based upon the mobile station location.
3-86
3GPP2 C.S0005-A v6.0
1 User Zones are associated with a set of features and services, plus a geographic area in
2 which the User Zone features/services are made available to the customers that have
3 subscribed to that User Zone. The boundary of the User Zone Geographic area may be
4 established based on the coverage area of a public or private base station, or it may be
5 established independent of RF topology.
6 User Zones may be supported by the public system on the same frequency as the serving
7 base station, or they may be supported on a private system operating on a different
8 frequency.
9 3.6.7.1.2 Types of User Zones
10 User Zones may be of two basic types:
11 • Broadcast User Zones: Broadcast User Zones are identified to the mobile station
12 using the Paging Channel or the Primary Broadcast Control Channel. In this case,
13 the base station broadcasts messages on the Paging Channel or the Primary
14 Broadcast Control Channel identifying the User Zones that fall within the coverage
15 area of the particular cell/sector. A mobile station, as part of its monitoring of the
16 Paging Channel or the Primary Broadcast Control Channel, will identify the
17 presence of a particular User Zone.
18 • Mobile Specific User Zones: Mobile Specific User Zones are not broadcast by the base
19 station. A mobile station may use other overhead message parameters and compare
20 them with internally stored User Zone parameters to identify the presence of a
21 particular User Zone. These parameters may include: SID, NID, BASE_ID,
22 BASE_LAT, and BASE_LONG.
24 If the base station supports CDMA Tiered Services, the base station sends the following
25 messages to assist the mobile station in identifying the presence of User Zones and to
26 validate the User Zone requested by a mobile station:
29 • User Zone Reject Message
30 • User Zone Update Message
31 3.6.7.2.1 User Zone Identification Message
32 The base station identifies Broadcast User Zones supported by the base station by sending
33 the User Zone Identification Message on the Paging Channel or the Primary Broadcast
34 Control Channel. The base station should list the UZID of each Broadcast User Zone
35 supported by the base station.
36 3.6.7.2.2 Private Neighbor List Message
37 The base station sends a Private Neighbor List and identifies the User Zones supported by
3-87
3GPP2 C.S0005-A v6.0
1 its private neighbor base stations by sending the Private Neighbor List Message on the
2 Paging Channel or the Primary Broadcast Control Channel. The Private Neighbor List
3 Message shall list no more than N8m private neighbors.
4 3.6.7.2.3 User Zone Update Message and User Zone Reject Message on f-dsch
5 For a mobile station operating in the Traffic Channel Substate or Release Substate of the
6 Mobile Station Control on the Traffic Channel State, the base station may update the User
7 Zone associated with the mobile station by sending a User Zone Update Message. The base
8 station may also send a User Zone Reject Message to reject the User Zone requested by the
9 mobile station in the Origination Message, Page Response Message, or User Zone Update
10 Request Message. The base station may include the ASSIGN_UZID field in the User Zone
11 Reject Message to assign a User Zone to the mobile station to replace the rejected User
12 Zone.
13 3.6.7.2.4 User Zone Reject Message on f-csch

14 The base station may send the User Zone Reject Message on the Paging Channel or the
15 Forward Common Control Channel to reject the User Zone requested by the mobile station
16 in the Registration Message, Origination Message, or Page Response Message. The base
17 station may include the ASSIGN_UZID field in the User Zone Reject Message record to
18 assign a User Zone to the mobile station to replace the rejected User Zone.
19 3.6.8 Call Control Processing
20 The Call Control consists of the following states:
21 • Waiting for Order Substate - In this substate, the Call Control instance sends the
22 Alert With Information Message or the Extended Alert With Information Message to the
23 mobile station.
24 • Waiting for Answer Substate - In this substate, the Call Control instance waits for
25 the Connect Order from the mobile station.
26 • Conversation Substate - In this substate, the parties involved in this call exchanges
27 Traffic Channel frames in accordance with the current service configuration.
28 • Call Release Substate - In this substate, the Call Control instance waits for the call
29 to be disconnected.
30 The following messages are processed by the Call Control:
31 • Alert With Information Message
32 • Extended Alert with Information Message:
33 • Flash With Information Message
34 • Extended Flash With Information Message
3-88
3GPP2 C.S0005-A v6.0
1 • Send Burst DTMF Message
2 • Origination Continuation Message
3 The following orders are processed by the Call Control:
4 • Continuous DTMF Tone Order
5 • Maintenance Order
6 • Connect Order
7 Upon instantiation, the Call Control instance shall perform the following:
8 • If the call is a mobile station terminated call and the base station set
9 BYPASS_ALERT_ANSWER to ‘1’, the Call Control instance shall enter the
10 Conversation Substate (see 3.6.8.2). If the call is a mobile station terminated call
11 and the base station set BYPASS_ALERT_ANSWER to ‘0’, the Call Control instance
12 shall enter the Waiting for Order Substate (see 3.6.8.1.1).
13 • If the call is a mobile-station-originated call, the Call Control instance shall enter
14 the Conversation Substate (see 3.6.8.2).
15 3.6.8.1 Alerting
16 3.6.8.1.1 Waiting for Order Substate
17 In this substate, the Call Control instance sends an Alert With Information Message or an
18 Extended Alert With Information Message to the mobile station.
19 While in the Waiting for Order Substate, the Call Control instance shall perform the
20 following:
23 • If the Call Control instance receives a “send alert with info message indication” from
24 the layer 3Layer 3, the Call Control instance shall send an Alert with Information
25 Message or an Extended Alert With Information Message to the mobile station within
26 T2b seconds, and enter the Waiting for Answer Substate.
27 • The Call Control instance may send the following messages:
28 1. Alert With Information Message: The Call Control instance shall enter the
29 Waiting for Answer Substate.
30 2. Extended Alert With Information Message: The Call Control instance shall enter
31 the Waiting for Answer Substate.
3-89
3GPP2 C.S0005-A v6.0
1 3. Maintenance Order: The Call Control instance shall enter the Waiting for Answer
2 Substate.
3 3.6.8.1.2 Waiting for Answer Substate

4 In this substate, the Call Control instance waits for a Connect Order from the mobile
5 station.
6 While in the Waiting for Answer Substate, the Call Control instance shall perform the
7 following:
11 the layer 3Layer 3, the Call Control instance shall send an Alert with Information
12 Message or an Extended Alert with Information Message to the mobile station, within
15 1. Alert With Information Message
16 2. Extended Alert With Information Message
17 3. Maintenance Order
18 • If the Call Control instance receives one of the following messages from the layer
19 3Layer 3, the Call Control instance shall process the message according to the
20 specified requirements, if any:
21 1. Connect Order: The Call Control instance shall enter the Conversation Substate.
22 2. Flash With Information Message: If the message contains a Keypad Facility

23 record with feature codes indicating User Selective Call Forwarding with a pre-
24 registered number, a stored number, or voice mail, the Call Control instance
25 may send a ‘call release request’ to the layer 3Layer 3. If this message contains
26 the Global Emergency Call information record and the call associated with this
27 Call Control instance is a voice call, the base station shall recognize this as an
28 emergency call and should process the message using an implementation-
29 dependent procedure which may include ignoring the dialed digits. If this
30 message contains the Global Emergency Call information record and the call
31 associated with this Call Control instance is not a voice call, the base station
32 may recognize this as an emergency call and should process the message using
33 an implementation-dependent procedure which may include ignoring the dialed
34 digits.
3-90
3GPP2 C.S0005-A v6.0
1 3. Extended Flash With Information Message: If the message contains a Keypad

2 Facility record with feature codes indicating User Selective Call Forwarding with
3 a pre-registered number, a stored number, or voice mail, the Call Control
4 instance may send a ‘call release request’ to the layer 3Layer 3. If this message
5 contains the Global Emergency Call information record and the call associated
6 with this Call Control instance is a voice call, the base station shall recognize
7 this as an emergency call and should process the message using an
8 implementation-dependent procedure which may include ignoring the dialed
9 digits. If this message contains the Global Emergency Call information record
10 and the call associated with this Call Control instance is not a voice call, the
11 base station may recognize this as an emergency call and should process the
12 message using an implementation-dependent procedure which may include
13 ignoring the dialed digits.
14 4. Origination Continuation Message
15 3.6.8.2 Conversation Substate
16 While in the Conversation Substate, the Call Control instance shall perform the following:
19 • If the Call Control instance receives a “paca reorig indication” from the layer 3Layer
20 3, the Call Control instance should send either an Alert With Information
21 Message/Extended Alert With Information Message which contains a signal
22 information record with the SIGNAL_TYPE field set to ‘01’ or ‘10’, or an Alert With
23 Information Message/Extended Alert With Information Message which does not
24 contain a signal information record.
26 layer 3Layer 3, the Call Control instance shall send an Alert with Information
27 Message or an Extended Alert With Information Message to the mobile station within
30 1. Alert With Information Message: If the message contains a signal information

32 contain a signal information record, the Call Control instance shall enter the
33 Waiting for Answer Substate.
34 2. Extended Alert With Information Message: If the message contains a signal

36 message does not contain a signal information record, the Call Control instance
37 shall enter the Waiting for Answer Substate.
3-91
3GPP2 C.S0005-A v6.0
2 4. Flash With Information Message
3 5. Extended Flash With Information Message
5 Substate.
6 7. Send Burst DTMF Message
7 • If the Call Control instance receives one of the following messages from layer 3Layer
8 3, the Call Control instance shall process the message according to the specified
9 requirements, if any:
11 2. Flash With Information Message: If this message contains the Global Emergency
12 Call information record and the call associated with this Call Control instance is
13 a voice call, the base station shall recognize this as an emergency call and
14 should process the message using an implementation-dependent procedure
15 which may include ignoring the dialed digits. If this message contains the Global
16 Emergency Call information record and the call associated with this Call Control
17 instance is not a voice call, the base station may recognize this as an emergency
18 call and should process the message using an implementation-dependent
19 procedure which may include ignoring the dialed digits.
20 3. Extended Flash With Information Message: If this message contains the Global
22 instance is a voice call, the base station shall recognize this as an emergency call
23 and should process the message using an implementation-dependent procedure
31 3.6.8.3 Call Release Substate
33 1. Alert With Information Message: If the message contains a signal information

3-92
3GPP2 C.S0005-A v6.0
1 contain a signal information record, the base station shall enter the Waiting for
2 Answer Substate.
3 2. Extended Alert With Information Message: If the message contains a signal

5 message does not contain a signal information record, the base station shall
6 enter the Waiting for Answer Substate.
8 Substate.
9 • If the Call Control instance receives one of the following messages from layer 3Layer
10 3, the Call Control instance shall process the message according to the specified
11 requirements, if any:
12 1. Connect Order
14 3. Flash With Information Message: If this message contains the Global Emergency
15 Call information record and the call associated with this Call Control instance is
16 a voice call, the base station shall recognize this as an emergency call and
17 should process the message using an implementation-dependent procedure
23 4. Extended Flash With Information Message: If this message contains the Global
25 instance is a voice call, the base station shall recognize this as an emergency call
26 and should process the message using an implementation-dependent procedure
3-93
3GPP2 C.S0005-A v6.0
1 No text.
3-94
3GPP2 C.S0005-A v6.0
1 3.7 PDU Formats for Messages
2 The following sections specify the requirements on the PDU formats transmitted on the f_-
3 csch, and the f-dsch.
4 In any multi-bit field in the following messages, the most significant bit (MSB) shall be
5 transmitted first.
6 3.7.1 Reserved
7 3.7.2 f-csch
8 The f-csch is used to send control information to mobile stations that have not been
9 assigned to a Traffic Channel.
10 3.7.2.1 Reserved
11 3.7.2.2 Reserved
3-95
3GPP2 C.S0005-A v6.0
1 3.7.2.3 PDU Formats for Messages on the f-csch
2 The messages sent on the f-csch are summarized in Table 3.7.2.3-1.
3-96
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3-1. f-csch Messages (Part 1 of 2)
Message Name MSG_TAG Section Primary F-CCCH PCH

Number BCCH
System Parameters Message SPM 3.7.2.3.2.1 N N Y

Access Parameters Message APM 3.7.2.3.2.2 N N Y
Neighbor List Message (Band NLM 3.7.2.3.2.3 N N Y
Class 0 only)
CDMA Channel List Message CCLM 3.7.2.3.2.4 N N Y
Order Message ORDM 3.7.2.3.2.7 N Y Y
Channel Assignment Message CAM 3.7.2.3.2.8 N N Y
Data Burst Message4 DBM 3.7.2.3.2.9 N Y Y
Authentication Challenge Message AUCM 3.7.2.3.2.10 N Y Y
SSD Update Message SSDUM 3.7.2.3.2.11 N Y Y
Feature Notification Message FNM 3.7.2.3.2.12 N Y Y
Extended System Parameters ESPM 3.7.2.3.2.13 N N Y
Message
Extended Neighbor List Message ENLM 3.7.2.3.2.14 N N Y
(band classes other than Band
Class 0)
Status Request Message STRQM 3.7.2.3.2.15 N Y Y
Service Redirection Message SRDM 3.7.2.3.2.16 N Y Y
General Page Message GPM 3.7.2.3.2.17 N Y Y
Global Service Redirection GSRDM 3.7.2.3.2.18 N N Y
Message
TMSI Assignment Message TASM 3.7.2.3.2.19 N Y Y
PACA Message PACAM 3.7.2.3.2.20 N Y Y
Extended Channel Assignment ECAM 3.7.2.3.2.21 N Y Y
Message
General Neighbor List Message GNLM 3.7.2.3.2.22 N N Y
User Zone Identification Message UZIM 3.7.2.3.2.23 Y N Y
4 When the Data Burst Message is used as a broadcast message, it can be sent on a Broadcast
Control Channel other than the Primary Broadcast Control Channel (see 2.6.2.1.1.3).
3-97
3GPP2 C.S0005-A v6.0
Private Neighbor List Message PNLM 3.7.2.3.2.24 Y N Y
3-98
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3-1. f-csch Messages (Part 2 of 2)
Message Name MSG_TAG Section Primary F-CCCH PCH

Number BCCH
Sync Channel Message SCHM 3.7.2.3.2.26 N N N
Extended Global Service EGSRDM 3.7.2.3.2.27 Y N Y
Redirection Message
Extended CDMA Channel List ECCLM 3.7.2.3.2.28 Y N Y
Message
User Zone Reject Message UZRM 3.7.2.3.2.29 N Y Y
ANSI-41 System Parameters A41SPM 3.7.2.3.2.30 Y N N
Message
MC-RR Parameters Message MCRRPM 3.7.2.3.2.31 Y N N
ANSI-41 RAND Message A41RANDM 3.7.2.3.2.32 Y N N
Enhanced Access Parameters EAPM 3.7.2.3.2.33 Y N N
Message
Universal Neighbor List UNLM 3.7.2.3.2.34 Y N N
Message
Security Mode Command SMCM 3.7.2.3.2.35 N Y Y
Message
Universal Page Message UPM 3.7.2.3.2.36 N Y N
3-99
3GPP2 C.S0005-A v6.0
3 The following sections specify the contents of message body for each message that may be
4 sent on the f-csch.
3-100
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.1 System Parameters Message
2 MSG_TAG: SPM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
SID 15
NID 16
REG_ZONE 12
TOTAL_ZONES 3
ZONE_TIMER 3
MULT_SIDS 1
MULT_NIDS 1
BASE_ID 16
BASE_CLASS 4
PAGE_CHAN 3
MAX_SLOT_CYCLE_INDEX 3
HOME_REG 1
FOR_SID_REG 1
FOR_NID_REG 1
POWER_UP_REG 1
POWER_DOWN_REG 1
PARAMETER_REG 1
REG_PRD 7
BASE_LAT 22
BASE_LONG 23
REG_DIST 11
SRCH_WIN_A 4
3 (continues on next page)
3-101
3GPP2 C.S0005-A v6.0
Field Length (bits)
SRCH_WIN_N 4
SRCH_WIN_R 4
NGHBR_MAX_AGE 4
PWR_REP_THRESH 5
PWR_REP_FRAMES 4
PWR_THRESH_ENABLE 1
PWR_PERIOD_ENABLE 1
PWR_REP_DELAY 5
RESCAN 1
T_ADD 6
T_DROP 6
T_COMP 4
T_TDROP 4
EXT_SYS_PARAMETER 1
EXT_NGHBR_LIST 1
GEN_NGHBR_LIST 1
GLOBAL_REDIRECT 1
PRI_NGHBR_LIST 1
USER_ZONE_ID 1
EXT_GLOBAL_REDIRECT 1
EXT_CHAN_LIST 1

4 The base station shall set this field to the pilot PN sequence
5 offset for this base station, in units of 64 PN chips.
6 CONFIG_MSG_SEQ - Configuration message sequence number.
7 The base station shall set this field to CONFIG_SEQ
8 (see 3.6.2.2).
9 SID - System identification.
10 The base station shall set this field to the system identification
11 number for this system (see 2.6.5.2).
12 NID - Network identification.
13 This field serves as a sub-identifier of a system as defined by
14 the owner of the SID.
3-102
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the network

2 identification number for this network (see 2.6.5.2).
3 REG_ZONE - Registration zone.
4 The base station shall set this field to its registration zone
5 number (see 2.6.5.1.5).
6 TOTAL_ZONES - Number of registration zones to be retained.
7 The base station shall set this field to the number of
8 registration zones the mobile station is to retain for purposes
9 of zone-based registration (see 2.6.5.1.5).
10 If zone-based registration is to be disabled, the base station
12 ZONE_TIMER - Zone timer length.
13 The base station shall set this field to the ZONE_TIMER value
14 shown in Table 3.7.2.3.2.1-1 corresponding to the length of
15 the zone registration timer to be used by mobile stations.
16
17 Table 3.7.2.3.2.1-1. Value of Zone Timer
ZONE_TIMER Timer Length

Value (binary) (Minutes)
000 1
001 2
010 5
011 10
100 20
101 30
110 45
111 60
18
19 MULT_SIDS - Multiple SID storage indicator.

20 If mobile stations may store entries of SID_NID_LIST
21 containing different SIDs, the base station shall set this field
22 to ‘1’; otherwise the base station shall set this field to ‘0’.
23 MULT_NIDS - Multiple NID storage indicator.
24 If mobile stations may store multiple entries of SID_NID_LIST
25 having the same SID (with different NIDs), the base station
26 shall set this field to ‘1’; otherwise the base station shall set
28 BASE_ID - Base station identification.
3-103
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to its identification

2 number.
3 BASE_CLASS - Base station class.
4 The base station shall set this field to the value shown in
5 Table 3.7.2.3.2.1-2 corresponding to the class of service
6 provided by this base station.as follows:
7 For Band Class 1 and 4, the base station shall set this field to
8 ‘0001’; otherwise, the base station shall set this field to ‘0000’.
9
10 Table 3.7.2.3.2.1-2. Base Station Classes
Value
Class of Service Provided
(binary)
0000 Public Macrocellular System

0001 Public PCS System
All other values are reserved.

11
12 PAGE_CHAN - Number of Paging Channels.

13 The base station shall set this field to the number of Paging
14 Channels on this CDMA Channel. The base station shall not
16 MAX_SLOT_CYCLE- - Maximum slot cycle index.
17 _INDEX The base station shall set this field to the
18 SLOT_CYCLE_INDEX value corresponding to the maximum
19 slot cycle length permitted (see 2.6.2.1.1).
20 HOME_REG - Home registration indicator.
21 If mobile stations that are not roaming (see 2.6.5.3) and have
22 MOB_TERM_HOME equal to ‘1’ are to be enabled for
23 autonomous registrations, the base station shall set this field
24 to ‘1’. If such mobile stations are not to be enabled for
25 autonomous registration, the base station shall set this field
26 to ’0’.
27 FOR_SID_REG - SID roamer registration indicator.
28 If mobile stations that are foreign SID roamers (see 2.6.5.3)
29 and have MOB_TERM_FOR_SID equal to ‘1’ are to be enabled
30 for autonomous registration, the base station shall set this
31 field to ‘1’. If such mobile stations are not to be enabled for
33 to ’0’.
34 FOR_NID_REG - NID roamer registration indicator.
3-104
3GPP2 C.S0005-A v6.0
1 If mobile stations that are foreign NID roamers (see 2.6.5.3)

2 and have MOB_TERM_FOR_NID equal to ‘1’ are to be enabled
6 to ‘0’.
7 POWER_UP_REG - Power-up registration indicator.
8 If mobile stations enabled for autonomous registration are to
9 register immediately after powering on and receiving the
10 system overhead messages, the base station shall set this field
11 to ‘1’; otherwise, the base station shall set this field to ‘0’.
12 POWER_DOWN_REG - Power-down registration indicator.
14 register immediately before powering down, the base station
15 shall set this field to ‘1’; otherwise, the base station shall set
17 PARAMETER_REG - Parameter-change registration indicator.
18 If mobile stations are to register on parameter change events
19 as specified in 2.6.5.1.6, the base station shall set this field to
20 ‘1’. If not, the base station shall set this field to ‘0’.
21 REG_PRD - Registration period.
22 If mobile stations are not to perform timer-based registration,
23 the base station shall set this field to ‘0000000’. If mobile
24 stations are to perform timer-based registration, the base
25 station shall set this field to the value in the range 29 to 85
26 inclusive, such that the desired timer value is
27 2REG_PRD/4 × 0.08 seconds.

28 BASE_LAT - Base station latitude.
29 The base station shall set this field to its latitude in units of
30 0.25 second, expressed as a two’s complement signed number
31 with positive numbers signifying North latitudes. The base
32 station shall set this field to a value in the range -1296000 to
33 1296000 inclusive (corresponding to a range of -90° to +90°).
34 BASE_LONG - Base station longitude.
35 The base station shall set this field to its longitude in units of
37 with positive numbers signifying East longitude. The base
39 2592000 inclusive (corresponding to a range of -180° to
40 +180°).
41 REG_DIST - Registration distance.
42 If mobile stations are to perform distance-based registration,
43 the base station shall set this field to the non-zero “distance”
44 beyond which the mobile station is to re-register (see
45 2.6.5.1.4). If mobile stations are not to perform distance-
46 based registration, the base station shall set this field to 0.
3-105
3GPP2 C.S0005-A v6.0
1 SRCH_WIN_A - Search window size for the Active Set and Candidate Set.
3 Table 2.6.6.2.1-1 corresponding to the search window size to
4 be used by mobile stations for the Active Set and Candidate
5 Set.
6 SRCH_WIN_N - Search window size for the Neighbor Set.
9 be used by mobile stations for the Neighbor Set.
10 SRCH_WIN_R - Search window size for the Remaining Set.
13 be used by mobile stations for the Remaining Set.
14 NGHBR_MAX_AGE - Neighbor Set maximum AGE.
15 The base station shall set this field to the maximum AGE
16 value beyond which mobile stations are to drop members from
17 the Neighbor Set (see 2.6.6.2.6.3).
18 PWR_REP_THRESH - Power control reporting threshold.
19 The base station shall set this field to the number of bad
20 frames (see [2]) to be received in a measurement period on the
21 channel which carries the Power Control Subchannel before
22 mobile stations are to generate a Power Measurement Report
23 Message (see 2.6.4.1.1). If the base station sets
24 PWR_THRESH_ENABLE to ‘1’, it shall not set this field to
25 ‘00000’.
26 PWR_REP_FRAMES - Power control reporting frame count.
27 The base station shall set this field to the value such that the
28 number given by
29 2(PWR_REP_FRAMES/2) × 5 frames
30 is the number of frames over which mobile stations are to
31 count frame errors.
32 PWR_THRESH- - Threshold report mode indicator.
33 _ENABLE If mobile stations are to generate threshold Power
34 Measurement Report Messages, the base station shall set this
35 field to ‘1’. If mobile stations are not to generate threshold
36 Power Measurement Report Messages, the base station shall
38 PWR_PERIOD- - Periodic report mode indicator.
39 _ENABLE If mobile stations are to generate periodic Power Measurement
40 Report Messages, the base station shall set this field to ‘1’. If
41 mobile stations are not to generate periodic Power
44 PWR_REP_DELAY - Power report delay.
3-106
3GPP2 C.S0005-A v6.0
1 The period that mobile stations wait following a Power

2 Measurement Report Message before restarting frame counting
3 for power control purposes.
4 The base station shall set this field to the power report delay
5 value, in units of 4 frames (see 2.6.4.1.1).
6 RESCAN - Rescan indicator.
7 If mobile stations are to re-initialize and re-acquire the system
8 upon receiving this message, the base station shall set this
9 field to ‘1’; otherwise, the base station shall set this field to ’0’.
10 T_ADD - Pilot detection threshold.
11 This value is used by the mobile station to trigger the transfer
12 of a pilot from the Neighbor Set or Remaining Set to the
13 Candidate Set (see 2.6.6.2.6) and to trigger the sending of the
15 Measurement Message initiating the handoff process (see
16 2.6.6.2.5.2).
17 The base station shall set this field to the pilot detection
18 threshold, expressed as an unsigned binary number equal to
19 - 2 × 10 × log10 Ec/Io .
20 T_DROP - Pilot drop threshold.

21 This value is used by mobile stations to start a handoff drop
22 timer for pilots in the Active Set and the Candidate Set (see
23 2.6.6.2.3).
24 The base station shall set this field to the pilot drop threshold,
25 expressed as an unsigned binary number equal to
26 - 2 × 10 × log10 Ec/Io .
27 T_COMP - Active Set versus Candidate Set comparison threshold.
28 Mobile stations transmit a Pilot Strength Measurement
29 Message or an Extended Pilot Strength Measurement Message
30 when the strength of a pilot in the Candidate Set exceeds that
31 of a pilot in the Active Set by this margin (see 2.6.6.2.5.2).
32 The base station shall set this field to the threshold Candidate
33 Set pilot to Active Set pilot ratio, in units of 0.5 dB.
34 T_TDROP - Drop timer value.
35 Timer value after which an action is taken by mobile stations
36 for a pilot that is a member of the Active Set or Candidate Set,
37 and whose strength has not become greater than T_DROP. If
38 the pilot is a member of the Active Set, a Pilot Strength
39 Measurement Message or an Extended Pilot Strength
40 Measurement Message is issued. If the pilot is a member of
41 the Candidate Set, it will be moved to the Neighbor Set.
42 The base station shall set this field to the T_TDROP value
43 shown in Table 2.6.6.2.3-1 corresponding to the drop timer
44 value to be used by mobile stations.
45 EXT_SYS_PARAMETER - Extended System Parameters Message indicator.
3-107
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to ‘1’.

2 EXT_NGHBR_LIST - Extended Neighbor List Message indicator.
3 The base station sets this field to ‘1’ when it sends the
4 Extended Neighbor List Message on the Paging Channel;
5 otherwise the base station sets this field to ‘0’.
6 If the base station is operating in Band Class 1, Band Class 3,
7 or Band Class 4 with MIN_P_REV less than sixseven, it shall
8 set this field to ‘1’. If the base station is operating in Band
9 Class 0, it shall set this field to ‘0’.
10 GEN_NGHBR_LIST - General Neighbor List Message indicator.
11 If the base station is sending the General Neighbor List
12 Message on the Paging Channel, it shall set this field to ‘1’;
13 otherwise, it shall set this field to ‘0’.
15 or Band Class 4 with MIN_P_REV greater than or equal to
16 sixseven, and if EXT_NGHBR_LIST is set to ‘0’, the base
18 If the base station is operating in Band Class 0 with

19 MIN_P_REV greater than or equal to seven and if the Neighbor
20 List Message is not sent, the base station shall set this field to
21 ‘1’.
23 Band Class 6, Band Class 7, Band Class 8, or Band Class 9,
24 or Band Class 10, and if EXT_NGHBR_LIST is set to ‘0’, the
25 base station shall set this field to ‘1’.
26 GLOBAL_REDIRECT - Global Service Redirection Message indicator.
27 If the base station is sending the Global Service Redirection
30 PRI_NGHBR_LIST - Private Neighbor List Message indicator.
31 If the base station is sending the Private Neighbor List Message
32 on the Paging Channel, it shall set this field to ‘1’; otherwise,
33 it shall set this field to ‘0’.
34 USER_ZONE_ID - User Zone Identification Message indicator.
35 If the base station is sending the User Zone Identification
38 EXT_GLOBAL-
39 _REDIRECT - Extended Global Service Redirection Message indicator.
40 If the base station is sending the Extended Global Service
41 Redirection Message on the Paging Channel, it shall set this
42 field to ‘1’; otherwise, the base station shall set this field to ‘0’.
43 EXT_CHAN_LIST - Extended CDMA Channel List Message indicator.
3-108
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to ‘1’, if the Extended
2 Channel List Message is sent on the Paging Channel,
3-109
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.2 Access Parameters Message
2 MSG_TAG: APM
Field Length (bits)
PILOT_PN 9
ACC_MSG_SEQ 6
ACC_CHAN 5
NOM_PWR 4
INIT_PWR 5
PWR_STEP 3
NUM_STEP 4
MAX_CAP_SZ 3
PAM_SZ 4
PSIST(0-9) 6
PSIST(10) 3
PSIST(11) 3
PSIST(12) 3
PSIST(13) 3
PSIST(14) 3
PSIST(15) 3
MSG_PSIST 3
REG_PSIST 3
PROBE_PN_RAN 4
ACC_TMO 4
PROBE_BKOFF 4
BKOFF 4
3-110
3GPP2 C.S0005-A v6.0
Field Length (bits)
MAX_REQ_SEQ 4
MAX_RSP_SEQ 4
AUTH 2
RAND 0 or 32
NOM_PWR_EXT 1
PSIST_EMG_INCL 1
PSIST_EMG 0 or 3
ACCT_INCL 1
ACCT_INCL_EMG 0 or 1
ACCT_AOC_BITMAP_INCL 0 or 1
ACCT_SO_INCL 0 or 1
NUM_ACCT_SO 0 or 4
If ACCT_SO_INCL is equal to ‘1’, NUM_ACCT_SO + 1
occurrences of the following variable-field record:
ACCT_AOC_BITMAP1 0 or 5
ACCT_SO 16
ACCT_SO_GRP_INCL 0 or 1
NUM_ACCT_SO_GRP 0 or 3
If ACCT_SO_GRP_INCL is equal to ‘1’, NUM_ACCT_SO_GRP
+ 1 occurrences of the following variable-field record:
ACCT_SO_GRP 5
4 The base station shall set this field to the pilot PN

5 sequence offset for this base station, in units of 64 PN chips.
6 ACC_MSG_SEQ - Access parameters message sequence number.
7 The base station shall set this field to

8 ACC_CONFIG_SEQ (see 3.6.2.2).
9 ACC_CHAN - Number of Access Channels.
3-111
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to one less than the
2 number of Access Channels associated with this Paging
3 Channel.
4 NOM_PWR - Nominal transmit power offset.
5 The base station shall set this field to the correction factor to
6 be used by mobile stations in the open loop power estimate,
7 expressed as a two’s complement value in units of 1 dB
8 (see [2]).
9 INIT_PWR - Initial power offset for access.
11 be used by mobile stations in the open loop power estimate for
12 the initial transmission on an Access Channel, expressed as a
13 two’s complement value in units of 1 dB (see [2]).
14 PWR_STEP - Power increment.
15 The base station shall set this field to the value by which
16 mobile stations are to increase their transmit power between
17 successive access probes in an access probe sequence, in
18 units of 1 dB.
19 NUM_STEP - Number of access probes.
21 maximum number of access probes mobile stations are to
22 transmit in a single access probe sequence.
23 MAX_CAP_SZ - Maximum Access Channel message capsule size.
24 The base station shall set this field to the value in the range 0
25 to 7, three less than the maximum number of Access Channel
26 frames in an Access Channel message capsule.
27 PAM_SZ - Access Channel preamble length.
29 number of Access Channel frames that mobile stations are to
30 transmit in each Access Channel preamble.
31 PSIST(0-9) - Persistence value for access overload classes 0 through 9.
32 If mobile stations in access overload classes 0 through 9 are
33 permitted to transmit requests on the Access Channel, the
34 base station shall set this field to the persistence value to be
35 used. If such mobile stations are not permitted to transmit
36 requests on the Access Channel, the base station shall set
38 PSIST(10) - Persistence value for access overload class 10 (test mobile
39 stations).
40 If mobile stations in access overload class 10 are permitted to
41 transmit requests on the Access Channel, the base station
42 shall set this field to the persistence value to be used. If such
43 mobile stations are not permitted to transmit requests on the
44 Access Channel, the base station shall set this field to ‘111’.
3-112
3GPP2 C.S0005-A v6.0
1 PSIST(11) - Persistence value for access overload class 11 (emergency

2 mobile stations).
8 PSIST(12) - Persistence value for access overload class 12.
32 MSG_PSIST - Persistence modifier for Access Channel attempts for message
33 transmissions.
34 A mobile station multiplies its transmission probability by
35 2-MSG_PSIST for such attempts.
36 The base station shall set this field to the persistence modifier
37 for Access Channel attempts for message transmissions.
38 REG_PSIST - Persistence modifier for Access Channel attempts for
39 registrations which are not responses to the Registration
40 Request Order.
41 A mobile station multiplies its transmission probability by
42 2-REG_PSIST for such attempts.
43 The base station shall set this field to the persistence modifier
44 for Access Channel attempts for registrations which are not
45 responses to the Registration Request Order.
3-113
3GPP2 C.S0005-A v6.0
1 PROBE_PN_RAN - Time randomization for Access Channel probes.

2 A mobile station delays its transmission from System Time by
3 RN PN chips, where RN is a number determined by hashing
4 between 0 and 2PROBE_PN_RAN - 1 PN chips.
6 to 9 inclusive such that the time randomization range is
7 2PROBE_PN_RAN - 1 PN chips.
8 ACC_TMO - Acknowledgment timeout.
9 The base station shall set this field to two less than the length
10 of time mobile stations are to wait after the end of an Access
11 Channel transmission before determining that the base
12 station did not receive the transmission, in units of 80 ms.
13 PROBE_BKOFF - Access Channel probe backoff range.
15 maximum number of slots mobile stations are to delay due to
16 random backoff between consecutive access probes.
17 BKOFF - Access Channel probe sequence backoff range.
19 maximum number of slots mobile stations are to delay due to
20 random backoff between successive access probe sequences
21 and before the first access probe sequence of a response
22 access.
23 MAX_REQ_SEQ - Maximum number of access probe sequences for an Access
24 Channel request.
25 The base station shall set this field to the maximum number
26 of access probe sequences mobile stations are to transmit for
27 an Access Channel request. The base station shall set this
28 field to a value greater than 0.
29 MAX_RSP_SEQ - Maximum number of access probe sequences for an Access
30 Channel response.
32 of access probe sequences mobile stations are to transmit for
33 an Access Channel response. The base station shall set this
34 field to a value greater than 0.
35 AUTH - Authentication mode.
36 If mobile stations are to include standard authentication data
37 in Access Channel messages, the base station shall set this
38 field to ‘01’. If mobile stations are not to include
39 authentication data in Access Channel messages, the base
40 station shall set this field to ‘00’. All other values are
41 reserved.
42 RAND - Random challenge value.
3-114
3GPP2 C.S0005-A v6.0
1 If the AUTH field is set to ‘01’, the base station shall set this
2 field to the random challenge value to be used by mobile
3 stations for authentication. If the AUTH field is set to any
4 other value, the base station shall omit this field.
5 NOM_PWR_EXT - Extended nominal transmit power.
6 If the base station is operating in Band Class 0 or Band Class
7 3, it shall set this field to ‘0’;.
8 If the base station is operating in a band class other than
9 Band Class 0 or Band Class 3otherwise, then it shall set this
10 field as follows:
11 If the correction factor to be used by mobile stations in the
12 open loop power estimate is between -24 dB and -9 dB
13 inclusive, the base station shall set this field to ‘1’; otherwise
14 (the correction factor is in the range -8 dB to 7 dB inclusive),
15 the base station shall set this field to ‘0’.
16 PSIST_EMG_INCL - Emergency persistence included indicator.
17 If PSIST_EMG is included in this message, the base station

19 this field to ‘0’. The base station shall not include PSIST_EMG
20 in this message if the base station supports the Enhanced
21 Access Channel.
22 If the base station does not support Common Channel
23 operation and if the base station includes PSISIT_EMG, which
24 is applicable to mobile stations with MOB_P_REV equal to or
25 greater than 7, the base station shall set this field to ‘1’.
26 PSIST_EMG - Persistence value for emergency call for access overload
27 classes 0 through 9.
28 If PSIST_EMG_INCL is set to ‘0’, the base station shall omit
29 this field; otherwise, the base station shall set this field as
30 follows:
31 If a mobile station in access overload classes 0 through 9 is
32 permitted to transmit emergency requests on the Access
33 Channel, the base station shall set this field to the persistence
34 value to be used for the emergency calls. If such a mobile
35 station is not permitted to transmit emergency requests on
36 the Access Channel, the base station shall set this field to
37 ‘111’.
38 ACCT_INCL - Access Control based on Call Type (ACCT) information
40 If the base station enables ACCT for at least one service
41 option, the base station shall set this field to ‘1’; otherwise,
43 If the base station sets this field to ‘1’, then the base station
44 shall also set at least one of ACCT_SO_INCL or
45 ACCT_SO_GRP_INCL to ‘1’.
3-115
3GPP2 C.S0005-A v6.0
1 ACCT_INCL_EMG - Access Control based on Call Type (ACCT) includes emergency

2 calls indicator.
3 If ACCT_INCL is set to ‘0’, the base station shall omit this
4 field; otherwise, the base station shall include this field and
5 set it as follows:
6 The base station shall set this field to ‘0’ if the mobile station
7 is not to apply ACCT to a call that is recognized by the mobile
8 station to be an emergency call; otherwise, the base station
10 ACCT_AOC_
11 BITMAP_INCL - Access Control based on Call Type (ACCT) access overload
12 class bitmap included indicator.
16 The base station shall set this field to ‘0’ if all mobile stations
17 are to apply ACCT regardless of their access overload classes;
18 otherwise, the base station shall set this field to ‘1’ to indicate
19 that the mobile station is to apply ACCT according to its
21 ACCT_SO_INCL - Access Control based on Call Type (ACCT) service option
26 The base station shall set this field to ‘1’ if at least one
27 occurrence of the ACCT_SO field is included in this message;
28 otherwise, the base station shall set this field to ‘0’.
29 NUM_ACCT_SO - Number of service options for Access Control based on Call
30 Type (ACCT).
31 If ACCT_SO_INCL is not included, or is included and set to ‘0’,
32 then the base station shall omit this field; otherwise, the base
33 station shall include this field and set it to one less than the
34 number of occurrences of the ACCT_SO field included in this
35 message.
36 If ACCT_SO_INCL is included and set to ‘1’, then the base station shall include
37 NUM_ACCT_SO + 1 occurrences of the following variable-field record:
38 ACCT_AOC_BITMAP1 - Access Control based on Call Type (ACCT) access overload
39 class bitmap.
40 If ACCT_AOC_BITMAP_INCL is set to ‘0’, then the base station
41 shall omit this field; otherwise, the base station shall include
42 this field and set it as follows:
43 This field consists of the subfields defined in Table
44 3.7.2.3.2.2-1.
3-116
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.2-1. ACCT access overload class bitmap subfields.
Length
Subfield Subfield Description
(bits)
ACCOLC_0_1 1 Access overload classes 0 and 1

3 The base station shall set a subfield to ‘1’ to indicate that

4 mobile stations having the corresponding access overload
5 class are not permitted to perform access attempts using the
6 associated service option ACCT_SO; otherwise, the base
7 station shall set the subfield to ‘0’.
8 ACCT_SO - Access Control based on Call Type (ACCT) service option
9 number.
10 The base station shall set this field to the value of the service
11 option number (as specified in [30]) that has ACCT enabled.
12 ACCT_SO_GRP_INCL - Access Control based on Call Type (ACCT) service option group
18 occurrence of the ACCT_SO_GRP field is included in this
19 message; otherwise, the base station shall set this field to ‘0’.
20 NUM_ACCT_SO_GRP - Number of service option groups for Access Control based on
21 Call Type (ACCT).
22 If ACCT_SO_GRP_INCL is not included, or is included and set
23 to ‘0’, then the base station shall omit this field; otherwise, the
24 base station shall include this field and set it to one less than
25 the number of occurrences of the ACCT_SO_GRP field
27 If ACCT_SO_GRP_INCL is included and set to ‘1’, then the base station shall include
28 NUM_ACCT_SO_GRP + 1 occurrences of the following variable-field record:
30 class bitmap.
3-117
3GPP2 C.S0005-A v6.0

2 3.7.2.3.2.2-1. The base station shall set a subfield to ‘1’ to
3 indicate that mobile stations having the corresponding access
4 overload class are not permitted to perform access attempts
5 using a service option specified by the associated
6 ACCT_SO_GRP field; otherwise, the base station shall set the
8 ACCT_SO_GRP - Access Control based on Call Type (ACCT) service option group
9 number.
11 option group number (as specified in [30]) whose members all
12 have ACCT enabled.
13
3-118
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.3 Neighbor List Message
2 MSG_TAG: NLM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
PILOT_INC 4
NGHBR_CONFIG 3
NGHBR_PN 9

9 (see 3.6.2.2).
10 PILOT_INC - Pilot PN sequence offset index increment.
11 A mobile station searches for Remaining Set pilots at pilot PN
12 sequence index values that are multiples of this value.
14 increment, in units of 64 PN chips, that mobile stations are to
15 use for searching the Remaining Set. The base station should
16 set this field to the largest increment such that the pilot PN
17 sequence offsets of all its neighbor base stations are integer
18 multiples of that increment.
19 The base station shall set this field to a value in the range 1 to
20 15 inclusive.
21
22 The base station shall include one occurrence of the following two-field record for each
23 member mobile stations are to place in their Neighbor Sets. The base station may include
24 zero or more occurrences of the following record.
25 NGHBR_CONFIG - Neighbor configuration.
27 Table 3.7.2.3.2.3-1 corresponding to the configuration of this
28 neighbor.
29
3-119
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.3-1. Neighbor Configuration Field
Value Neighbor Configuration

(binary)
000 The neighbor base station has the same number of frequencies having
Paging Channels as the current base station.
The neighbor base station has a CDMA frequency assignment that is

same as this current CDMA frequency assignment and with the same
number of Paging Channels.
The position of the neighbor CDMA frequency assignment in the CDMA

Channel List Message or the Extended CDMA Channel List Message
transmitted by the neighbor base station is the same as the position of
this current CDMA frequency assignment in the CDMA Channel List
Message or the Extended CDMA Channel List Message transmitted by
the current base station.
The neighbor base station has a CDMA frequency assignment that is

same as this current CDMA frequency assignment but possibly with a
different number of Paging Channels.

transmitted by the neighbor base station is the same as the position of
this current CDMA frequency assignment in the CDMA Channel List
Message or the Extended CDMA Channel List Message transmitted by
This corresponding neighbor CDMA frequency assignment does have a

Primary Paging Channel.
010 The neighbor base station may have a different number of frequencies
having Paging Channels as the current base station.
The neighbor base station has a Primary Paging Channel on the first
CDMA Channel listed in the CDMA Channel List Message or the
Extended CDMA Channel List Message transmitted by the current base
station.
3-120
3GPP2 C.S0005-A v6.0
011 The neighbor base station configuration is unknown but the neighbor
base station has a Pilot Channel on the CDMA frequency assignment
that is same as this current CDMA frequency assignment.
100-111 Reserved.
2 NGHBR_PN - Neighbor pilot PN sequence offset index.

4 offset for this neighbor, in units of 64 PN chips.
3-121
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.4 CDMA Channel List Message
2 MSG_TAG: CCLM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
CDMA_FREQ 11

9 (see 3.6.2.2).
10
11 CDMA_FREQ - CDMA Channel frequency assignment.

12 The order in which occurrences of this field are included gives
13 the designations of the supported CDMA Channels as CDMA
14 Channel 1 through CDMA Channel N.
15 The base station shall include one occurrence of this field for
16 each CDMA Channel containing a Paging Channel that is
17 supported by this base station. If the supported CDMA
18 Channels are in the preferred set of CDMA frequency
19 assignments (see [2]), the base station shall include their
20 occurrences of this field first.
21 The base station shall set each occurrence of this field to the
22 CDMA channel number corresponding to the CDMA frequency
23 assignment for that CDMA Channel (see [2]).
3-122
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.5 Reserved
2 No text.
3-123
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.6 Reserved
2 No text.
3-124
3GPP2 C.S0005-A v6.0
2 MSG_TAG: ORDM
Field Length (bits)
ORDER 6
ADD_RECORD_LEN 3
Order-specific fields (if used) 8
× ADD_RECORD_LEN
4 ORDER - Order code.

5 The base station shall set this field to the ORDER code
6 (see 3.7.4) for this type of order.
7 ADD_RECORD_LEN - Additional record length.
8 The base station shall set this field to the number of octets in
9 the order-specific fields included in this order record.
10 Order-specific fields - Order-specific fields.
11 The base station shall include order-specific fields as specified
12 in 3.7.4 for this type of order.
3-125
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.8 Channel Assignment Message
2 MSG_TAG: CAM
Field Length (bits)
ASSIGN_MODE 3
ADD_RECORD_LEN 3
Additional record fields 8×
ADD_RECORD_LEN
4 If ASSIGN_MODE = ‘000’, the additional record fields shall be:
FREQ_INCL 1
CODE_CHAN 8
CDMA_FREQ 0 or 11
FRAME_OFFSET 4
ENCRYPT_MODE 2
D_SIG_ENCRYPT_MODE 0 or 3
USE_NEW_KEY 0 or 1
ENC_KEY_SIZE 0 or 3
KEY_SEQ 0 or 4
C_SIG_ENCRYPT_MODE_INCL 1
C_SIG_ENCRYPT_MODE 0 or 3
RESPOND 1
FREQ_INCL 1
CDMA_FREQ 0 or 11
PILOT_PN 9
3-126
3GPP2 C.S0005-A v6.0
RESPOND 1
ANALOG_SYS 1
USE_ANALOG_SYS 1
BAND_CLASS 5
SID 15
VMAC 3
ANALOG_CHAN 11
SCC 2
MEM 1
AN_CHAN_TYPE 2
DSCC_MSB 1
BAND_CLASS 5
3-127
3GPP2 C.S0005-A v6.0
FREQ_INCL 1
RESERVED 3
BYPASS_ALERT_ANSWER 1
DEFAULT_CONFIG 3
GRANTED_MODE 2
CODE_CHAN 8
FRAME_OFFSET 4
ENCRYPT_MODE 2
BAND_CLASS 0 or 5
CDMA_FREQ 0 or 11
USE_NEW_KEY 0 or 1
ENC_KEY_SIZE 0 or 3
KEY_SEQ 0 or 4
RESPOND 1
FREQ_INCL 1
BAND_CLASS 0 or 5
CDMA_FREQ 0 or 11
PILOT_PN 9
7 ASSIGN_MODE - Assignment mode.
3-128
3GPP2 C.S0005-A v6.0
2 Table 3.7.2.3.2.8-1 corresponding to the assignment mode for
3 this assignment.
4
5 Table 3.7.2.3.2.8-1. Assignment Mode
Value
Assignment Mode
(binary)
000 Traffic Channel Assignment

(Band Class 0 only)
001 Paging Channel Assignment
(Band Class 0 only)
010 Acquire Analog System
011 Analog Voice Channel Assignment
100 Extended Traffic Channel
Assignment
101 Extended Paging Channel
Assignment

9 the additional record fields included in this assignment
10 record.
11 Additional record fields - Additional record fields.
12 The additional record fields are determined by the value of
13 ASSIGN_MODE, as described below.
14
15 If the ASSIGN_MODE field is set to ‘000’, the base station shall include the following fields:
16 FREQ_INCL - Frequency included indicator.
17 If the CDMA_FREQ field is included in this assignment record,
18 the base station shall set this bit to ‘1’. If the CDMA_FREQ
19 field is not included in this assignment record, the base
21 CODE_CHAN - Code channel.
22 The base station shall set this field to the code channel index
23 (see [2]) in the range 1 to 63 inclusive that the mobile station
24 is to use on the Fundamental Channel of the Forward Traffic
25 Channel.
26 CDMA_FREQ - Frequency assignment.
3-129
3GPP2 C.S0005-A v6.0
1 If the FREQ_INCL bit is set to ‘1’, the base station shall set
2 this field to the CDMA Channel number corresponding to the
3 CDMA frequency assignment for the CDMA Channel
4 containing the Forward Traffic Channel the mobile station is
5 to use. If the FREQ_INCL bit is set to ‘0’, the base station
7 FRAME_OFFSET - Frame offset.
8 The Forward and Reverse Traffic Channel frames are delayed
9 FRAME_OFFSET × 1.25 ms relative to system timing (see [2]).
10 The base station shall set this field to the Forward and
11 Reverse Traffic Channel frame offset.
12 ENCRYPT_MODE - Message encryption mode.
13 The base station shall set this field to the ENCRYPT_MODE
15 encrypting mode that is to be used for signaling messages, as
17
18 Table 3.7.2.3.2.8-2. Message Encryption Modes
ENCRYPT_MODE Field
Encryption Mode Used
(binary)
00 Encryption disabled
01 Basic encryption of call control
messages
10 Enhanced encryption of call
control messages
11 Extended encryption of call
control messages
19
20 D_SIG_ENCRYPT-
21 _MODE - General Dedicated channel signaling encryption mode indicator.
22 If ENCRYPT_MODE is set to ‘11’, the base station shall include
23 this field and shall set it to the dedicated channel signaling
24 message encryption mode, as shown in Table 3.7.4.5-1; otherwise
25 the base station shall omit this field.
26 USE_NEW_KEY - Use new encryption key indication
27 If ENCRYPT_MODE is set to ‘10’ or ‘11’, the base station shall
28 include this field; otherwise, the base station shall omit this field.
29 If this field is included, the base station shall set this field to ‘0’ to
30 indicate that the stored encryption key is to be used by the mobile
31 stationand to ‘1’ to indicate that the new encryption key is to be
32 used by the mobile station.
33 ENC_KEY_SIZE - Encryption key size indication.
3-130
3GPP2 C.S0005-A v6.0
1 If ENCRYPT_MODE is set to ‘10’ or ‘11’,USE_NEW_KEY is

2 included and is set to ‘0’, the base station shall omit this field;
3 otherwise, the base station shall include this field and shall set it
4 to the encryption key size, as shown in Table 3.7.4.5-2; otherwise,
6 KEY_SEQ - Encryption key sequence number.
7 If USE_NEW_KEY is included and is set to ‘0’, the base station
8 shall include this field; otherwise, the base station shall omit this
9 field. If this field is included, the base station shall set it to the
10 encryption key sequence number to be used by the mobile
11 station.
12 C_SIG_ENCRYPT_
13 _MODE_INCL - Common channel signaling encryption mode included
14 indicator.
15 If P_REV_IN_USE is less than seven, the base station shall set
16 this field to ‘0’; otherwise, the base station shall set this field
17 as follows:
18 If common channel signaling encryption information is
19 included in this message, the base station shall set this field
21 C_SIG_ENCRYPT_
22 _MODE - Common channel signaling encryption mode indicator.
23 If C_SIG_ENCRYPT_MODE_INCL is set to ‘1’, the base station
24 shall include this field and shall set it to the common channel
25 signaling encryption mode, as shown in Table 3.7.4.5-1;
26 otherwise, the base station shall omit this field.
27

29 The base station shall add reserved bits as needed in order to
30 make the total length of the fields after the preceding
31 ADD_RECORD_LEN field through this RESERVED field equal
32 to an integer number of octets. The base station shall set
34
36 RESPOND - Respond on new Access Channel indicator.
37 If the mobile station is to retransmit an Origination Message or
38 Page Response Message after processing this channel
39 assignment, the base station shall set this field to ‘1’. The
40 base station may set this field to ‘0’ only in response to a Page
3-131
3GPP2 C.S0005-A v6.0

2 If the CDMA_FREQ field is included in this assignment record,
3 the base station shall set this bit to ‘1’. If the CDMA_FREQ
4 field is not included in this assignment record, the base
8 this field to the CDMA Channel number corresponding to the
9 CDMA frequency assignment for the CDMA Channel
10 containing the Paging Channel the mobile station is to use. If
11 the FREQ_INCL bit is set to ‘0’, the base station shall omit this
12 field.
15 each base station whose Paging Channel may be monitored by
16 the mobile station. For each occurrence, the base station
17 shall set this field to the pilot PN sequence offset for a base
18 station, in units of 64 PN chips. The base station having this
19 pilot PN sequence offset should support a Primary Paging
20 Channel with the same Paging Channel rate as the current
21 base station.
24 make the total length of the fields, after the preceding
25 ADD_RECORD_LEN field through this RESERVED field, equal
28
30 RESPOND - Respond on analog control channel indicator.
32 Page Response Message on the analog control channel (see [6])
33 after processing this channel assignment, the base station
34 shall set this field to ‘1’. The base station may set this field to
35 ‘0’ only in response to a Page Response Message.
36 ANALOG_SYS - System indicator.
37 If USE_ANALOG_SYS is equal to ‘0’, the base station shall set
38 this field to ‘0’. Otherwise, the base station shall set this field
39 to ‘0’ if the mobile station is to use analog system A, or to ‘1’ if
40 the mobile station is to use analog system B.
41 USE_ANALOG_SYS - Use analog system indicator.
42 The base station shall set this field to ‘1’ to direct the mobile
43 station to the analog system specified by ANALOG_SYS;
3-132
3GPP2 C.S0005-A v6.0
1 The base station shall set this field according to values defined
2 in [30].
3
5 SID - System identification of the analog system.
7 of the analog system supporting the assigned voice channel
8 for this assignment (see [6]).
9 VMAC - Voice mobile station attenuation code.
10 The base station shall set this field to the mobile station
11 power level associated with the assigned voice channel for this
12 assignment (see [6]).
13 ANALOG_CHAN - Voice channel number.
14 The base station shall set this field to the voice channel
15 number for this assignment (see [6]).
16 SCC - SAT color code.
17 The base station shall set this field to the supervisory audio
18 tone color code associated with the assigned voice channel. If
19 the assignment is to a narrow analog channel, the base
20 station shall set this field to the two least significant bits of
21 the DSCC.
22 MEM - Message encryption mode indicator.
23 If analog control message encryption is to be enabled on the
24 assigned forward and reverse analog voice channels, the base
25 station shall set this bit to ‘1’; otherwise, the base station
26 shall set this bit to ‘0’.
27 AN_CHAN_TYPE - Analog voice channel type.
28 The base station shall set this field to the analog channel type
29 as specified in Table 3.7.3.3.2.6-1. If the mobile station does
30 not have narrow analog capability, the base station shall set
32 DSCC_MSB - Digital supervisory audio tone color code most significant bit.
33 The base station shall set this field to ‘0’ when directing
34 handoff to a wide analog channel. The base station shall set
35 this field to the most significant bit of the DSCC when
36 directing handoff to a narrow analog channel.

39 in [30].
40
3-133
3GPP2 C.S0005-A v6.0

2 If the BAND_CLASS and CDMA_FREQ fields are included in
3 this assignment record, the base station shall set this bit to
4 ‘1’. If the BAND_CLASS and CDMA_FREQ fields are not
5 included in this assignment record, the base station shall set
6 this bit to ‘0’.
9 BYPASS_ALERT-
10 _ANSWER - Bypass alert indicator.
11 If the MOB_P_REV of the current band class of the mobile
12 station is less than or equal to three, the base station shall set
14 as follows.
15 If the base station has received a Page Response Message that
16 specifies a packet data service option, and the mobile station
17 is to bypass the Waiting for Order Substate and the Waiting for
18 Mobile Station Answer Substate, the base station shall set this
20 DEFAULT_CONFIG - Default Configuration.
21 If the GRANTED_MODE field is set to ‘00’, the base station
22 shall set this field as specified in Table 3.7.2.3.2.8-3 to
23 indicate an initial multiplex option and radio configuration for
24 the Forward and Reverse Traffic Channels.
3-134
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.8-3. Default Configuration
Value
Default Configuration
(binary)
000 Multiplex Option 1 and Radio

Configuration 1 for both the Forward
Traffic Channel and the Reverse
Traffic Channel
Configuration 2 for both the Forward
Traffic Channel and the Reverse
Traffic Channel
Configuration 1 for the Forward
Traffic channel; Multiplex Option 2
and Radio Configuration 2 for the
Reverse Traffic channel
Configuration 2 for the Forward
Traffic channel; Multiplex Option 1
and Radio Configuration 1 for the
3 GRANTED_MODE - Granted mode.

4 The base station shall set this field to ‘00’ to indicate that the
5 mobile station is to use an initial service configuration
6 consisting of the multiplex option and radio configuration
7 defined by the DEFAULT_CONFIG field for the Forward and
8 Reverse Traffic Channels, and to indicate that service
9 negotiation is to take place before the base station sends the
10 first Service Connect Message.
13 consisting of the default multiplex option and transmission
14 rates corresponding to the service option requested by the
15 mobile station either in the Origination Message or Page
16 Response Message, and to indicate that service negotiation is
17 to take place before the base station sends the first Service
18 Connect Message.
3-135
3GPP2 C.S0005-A v6.0
5 mobile station either in the Origination Message or Page
6 Response Message, and to indicate that service negotiation is
7 not to take place before the base station sends the first Service
8 Connect Message.
9 CODE_CHAN - Code channel.
12 is to use on the Fundamental Channel of the Forward Traffic
13 Channel.
26 this field to the CDMA band class, as specified in [30],
27 corresponding to the CDMA frequency assignment for the
28 CDMA Channel containing the Forward Traffic Channel the
29 mobile station is to use. If the FREQ_INCL bit is set to ‘0’, the
30 base station shall omit this field.
33 this field to the CDMA Channel number, in the specified
34 CDMA band class, corresponding to the CDMA frequency
35 assignment for the CDMA Channel containing the Forward
36 Traffic Channel the mobile station is to use. If the
37 FREQ_INCL bit is set to ‘0’, the base station shall omit this
38 field.
39 D_SIG_ENCRYPT_MODE - Dedicated channel signalingGeneral encryption mode indicator.
42 messageencryption encryption mode, as shown in Table 3.7.4.5-1;
43 otherwise the base station shall omit this field.
3-136
3GPP2 C.S0005-A v6.0

5 stationand to ‘1’ to indicate that the new encryption key is to be
8 If ENCRYPT_MODE is set to ‘10’ or ‘11’USE_NEW_KEY is included
9 and is set to ‘0’, the base station shall omit this field; otherwise,
10 the base station shall include this field and shall set it to the
11 encryption key size, as shown in Table 3.7.4.5-2; otherwise, the
18 station.
19 C_SIG_ENCRYPT_
21 indicator.
24 as follows:
28 C_SIG_ENCRYPT_
34

3-137
3GPP2 C.S0005-A v6.0

6 Response Message.
17 CDMA Channel containing the Paging Channel the mobile
18 station is to use. If the FREQ_INCL bit is set to ‘0’, the base
24 assignment for the CDMA Channel containing the Paging
25 Channel the mobile station is to use. If the FREQ_INCL bit is
26 set to ‘0’, the base station shall omit this field.
35 base station.
3-138
3GPP2 C.S0005-A v6.0
2 MSG_TAG: DBM
Field Length (bits)
MSG_NUMBER 8
BURST_TYPE 6
NUM_MSGS 8
NUM_FIELDS 8

CHARi 8
4 MSG_NUMBER - Message number.

5 The base station shall set this field to the number of this
7 BURST_TYPE - Data burst type.
8 The base station shall set the value of this field for the type of
9 this data burst as defined in [30]. If the mobile station sets
13 the definition of CHARi below. If the base station sets this
17 NUM_MSGS - Number of messages in the data burst stream.
18 The base station shall set this field to the number of messages
19 in this data burst stream.
20 NUM_FIELDS - Number of characters in this message.
22 occurrences of the CHARi field included in this message.
23 CHARi - Character.
24 The base station shall include NUM_FIELDS occurrences of
25 this field. The base station shall set these fields to the
3-139
3GPP2 C.S0005-A v6.0

9 remaining six bits of the EXTENDED_BURST_TYPE_INTER-
10 NATIONAL field shall specify the COUNTRY_BURST_TYPE.
11 The base station shall set the value of the
12 COUNTRY_BURST_TYPE according to the type of this data
13 burst as defined in standards governed by the country where
14 this data burst type is to be used.
15
Field Length (bits)

16

19 EXTENDED_BURST_TYPE field, as shown below. The base
22
Field Length (bits)
Remaining CHARi fields 8 x (NUM_FIELDS - 2)
3-140
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.10 Authentication Challenge Message
2 MSG_TAG: AUCM
Field Length (bits)
RANDU 24
4 RANDU - Random challenge data.

5 The base station shall set this field to the random challenge
6 data (see 2.3.12.1.4).
3-141
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.11 SSD Update Message
2 MSG_TAG: SSDUM
Field Length (bits)
RANDSSD 56
4 RANDSSD - Random data for the computation of SSD.

5 The base station shall set this field as specified in 2.3.12.1.5.
3-142
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.12 Feature Notification Message
2 MSG_TAG: FNM
Field Length (bits)
RELEASE 1
RECORD_TYPE 8
RECORD_LEN 8
4 RELEASE - Origination completion indicator.

5 The base station shall set this field to ‘1’ if this message is
6 used to complete an origination request from the mobile
7 station (see 2.6.3.5); otherwise, the base station shall set this
8 field to ‘0’.
9
10 The base station shall include occurrences of the following three-field record as specified in
11 3.7.5.
13 The base station shall set this field as specified in 3.7.5.
14 RECORD_LEN - Information record length.
16 the type-specific fields included in this record.
18 The base station shall include type-specific fields as specified
19 in 3.7.5.
3-143
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.13 Extended System Parameters Message
2 MSG_TAG: ESPM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
DELETE_FOR_TMSI 1
USE_TMSI 1
PREF_MSID_TYPE 2
MCC 10
IMSI_11_12 7
TMSI_ZONE_LEN 4
TMSI_ZONE 8 × TMSI_ZONE_LEN
BCAST_INDEX 3
IMSI_T_SUPPORTED 1
P_REV 8
MIN_P_REV 8
SOFT_SLOPE 6
ADD_INTERCEPT 6
DROP_INTERCEPT 6
PACKET_ZONE_ID 8
MAX_NUM_ALT_SO 3
RESELECT_INCLUDED 1
EC_THRESH 0 or 5
EC_IO_THRESH 0 or 5
PILOT_REPORT 1
NGHBR_SET_ENTRY_INFO 1
ACC_ENT_HO_ORDER 0 or 1
NGHBR_SET_ACCESS_INFO 1
ACCESS_HO 0 or 1
ACCESS_HO_MSG_RSP 0 or 1
3-144
3GPP2 C.S0005-A v6.0
Field Length (bits)
ACCESS_PROBE_HO 0 or 1
ACC_HO_LIST_UPD 0 or 1
ACC_PROBE_HO_OTHER_MSG 0 or 1
MAX_NUM_PROBE_HO 0 or 3
NGHBR_SET_SIZE 0 or 6
If NGHBR_SET_ENTRY_INFO = 1, NGHBR_SET_SIZE
occurrences of the following field; otherwise, no occurrence
of the following field:
ACCESS_ENTRY_HO 1
If NGHBR_SET_ACCESS_INFO = 1, NGHBR_SET_SIZE
occurrences of the following field; otherwise, no occurrence
of the following field:
ACCESS_HO_ALLOWED 1
BROADCAST_GPS_ASST 1
QPCH_SUPPORTED 1
NUM_QPCH 0 or 2
QPCH_RATE 0 or 1
QPCH_POWER_LEVEL_PAGE 0 or 3
QPCH_CCI_SUPPORTED 0 or 1
QPCH_POWER_LEVEL_CONFIG 0 or 3
SDB_SUPPORTED 1
RLGAIN_TRAFFIC_PILOT 6
REV_PWR_CNTL_DELAY_INCL 1
REV_PWR_CNTL_DELAY 0 or 2
AUTO_MSG_SUPPORTED 1
AUTO_MSG_INTERVAL 0 or 3
3-145
3GPP2 C.S0005-A v6.0
Field Length (bits)
MOB_QOS 1
ENC_SUPPORTED 1
STORE_KEY 0 or 1
USE_SYNC_ID 1
CS_SUPPORTED 1
BCCH_SUPPORTED 1
MS_INIT_POS_LOC_SUP_IND 1
PILOT_INFO_REQ_SUPPORTED 1

8 (see 3.6.2.2).
9 DELETE_FOR_TMSI - Delete foreign TMSI.
10 The base station shall set this field to ‘1’ to cause the mobile
11 station to delete its TMSI if the TMSI was assigned in a
12 different TMSI zone from that specified by the TMSI_ZONE
13 field of this message; otherwise, the base station shall set this
15 USE_TMSI - Use TMSI indicator.
17 Table 3.7.2.3.2.13-1 corresponding to the type of MSID that
18 the mobile station is to use on the Access Channel.
19 PREF_MSID_TYPE - Preferred Access Channel Mobile Station Identifier Type.
22 the mobile station is to use on the Access Channel.
23
3-146
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.13-1. Preferred MSID Types
USE_TMSI PREF_MSID_TYPE
(binary) (binary) Description
0 00 IMSI_S and ESN
0 10 IMSI
0 11 IMSI and ESN
1 10 TMSI (valid TMSI is
assigned);
IMSI (TMSI not assigned)
assigned);
IMSI and ESN (TMSI not
assigned)
3 MCC - Mobile Country Code.

4 The base station shall set this field to the MCC (see 2.3.1)
th th
5 IMSI_11_12 - 11 and 12 digits of the IMSI.
6 The base station shall set this field to the IMSI_11_12 (see
7 2.3.1).
8 TMSI_ZONE_LEN - TMSI zone length.
9 The base station shall set this field to the number of octets
10 included in the TMSI_ZONE. The base station shall set this
11 field to a value in the range 1 to 8 inclusive.
12 TMSI_ZONE - TMSI zone.
13 The base station shall set this field to the TMSI zone number
15 BCAST_INDEX - Broadcast slot cycle index.
16 To enable periodic broadcast paging, the base station shall set
17 this field to an unsigned 3-bit number in the range 1-7, equal
18 to the broadcast slot cycle index as defined in 2.6.2.1.1.3.3.
19 To disable periodic broadcast paging, the base station shall
21 IMSI_T_SUPPORTED - IMSI_T support indicator.
22 The base station shall set this field to ‘1’ to indicate support
23 for a 15-digit IMSI_T addressing according to [18].
24 P_REV - Protocol revision level.
26 MIN_P_REV - Minimum protocol revision level.
3-147
3GPP2 C.S0005-A v6.0
1 The base station sets this field to prevent mobile stations

2 which cannot be supported by the base station from accessing
3 the system.
4 The base station shall set this field to the minimum protocol
5 revision level that it supports. For Band Class 0 operation,
6 the base station should set this field to a value of ‘00000010’
7 or greater. For Band Class 1 or Band Class 4 operation, the
8 base station should set this field to a value of ‘00000001’ or
9 greater. For Band Class 3 operation, the base station should
10 set this field to a value of ‘00000011’ or greater. For Band
11 Class 2 or Band Class 5 operation, the base station should set
12 this field to ‘00000101’, or greater. For Band Class 6, Band
13 Class 7, Band Class 8, or Band Class 9, or Band Class 10
14 operation, the base station should set this field to ‘00000110’,
15 or greater.
16 SOFT_SLOPE - The slope in the inequality criterion for adding a pilot to the
17 Active Set, or dropping a pilot from the Active Set (see
18 2.6.6.2.3 and 2.6.6.2.5.2).
19 The base station shall set this field as an unsigned binary
20 number.
21 ADD_INTERCEPT - The intercept in the inequality criterion for adding a pilot to
22 the Active Set (see 2.6.6.2.5.2).
23 The base station shall set this field as a two’s complement
24 signed binary number, in units of dB.
25 DROP_INTERCEPT - The intercept in the inequality criterion for dropping a pilot
26 from the Active Set (see 2.6.6.2.3).
29 PACKET_ZONE_ID - Packet data services zone identifier.
30 If the base station supports a packet data service zone, the
31 base station shall set this field to its non-zero packet data
32 services zone identifier.
33 If the base station does not support a packet data service
34 zone, the base station shall set this field to ‘00000000’.
35 MAX_NUM_ALT_SO - Maximum number of alternative service options.
37 of alternative service option numbers that the mobile station
38 is allowed to include in the Origination Message or the Page
40 For mobile stations with MOB_P_REVs less than seven, the
41 alternative service options are those service options defined in
42 [30] and related to SERVICE_OPTION in Origination Message
43 and the Page Response Message.
3-148
3GPP2 C.S0005-A v6.0
1 For mobile stations with MOB_P_REVs equal to or greater

2 than seven, the alternative service options are those service
3 options defined in [30] without service group number assigned
4 and related to SERVICE_OPTION in Origination Message and
5 the Page Response Message.
6 If the base station sets this field to a value greater than zero,
7 in addition, the base station shall allow the mobile station
8 with MOB_P_REVs equal to or greater than 7 to include
9 • a 4 or 8-bit service option bitmap in the Origination
10 Message and the Page Response Message;
11 • alternate service option numbers, not limited to
12 MAX_ALT_SO_NUM, in the Enhanced Origination Message.
13 RESELECT_INCLUDED - System reselection parameters included.
14 If the base station is including system reselection parameters,
15 the base station shall set this field to ‘1’; otherwise, the base
17 EC_THRESH - Pilot power threshold.
18 If RESELECT_INCLUDED is set to ‘1’, the base station shall
19 include the field EC_THRESH and set this field to:
20  (pilot_power_threshold + 115) 
21 where pilot_power_threshold is the pilot power, Ec, in
22 dBm/1.23 MHz, below which the mobile station is to perform
23 system reselection; otherwise, the base station shall omit this
24 field.
25 EC_IO_THRESH - Pilot Ec/ Io threshold.
26 If RESELECT_INCLUDED is set to ‘1’, the base station shall
27 include the field EC_IO_THRESH and set this field to:
28  - 20 × log10 (pilot_threshold ) 
29 where pilot_threshold is the pilot Ec/Io below which the mobile
30 station is to perform system reselection; otherwise, the base
32 PILOT_REPORT - Pilot reporting indicator.
34 is to report the additional pilots which have pilot strengths
35 exceeding T_ADD in all Access Channel messages. The base
36 station shall set this field to ‘0’ if the mobile station is to
37 report the additional pilots which have pilot strengths
38 exceeding T_ADD only in the Origination Message and the
39 Page Response Message.
40 NGHBR_SET-
41 _ENTRY_INFO - Neighbor Set access entry handoff information included
42 indicator.
43 If the base station is including information on the Neighbor
44 Set access entry handoff, the base station shall set this field
3-149
3GPP2 C.S0005-A v6.0
1 ACC_ENT_HO_ORDER - Access entry handoff permitted indicator.

2 If NGHBR_SET_ENTRY_INFO is set to ‘1’, the base station
3 shall include this field and set it as described below;
6 is permitted to perform an access entry handoff after receiving
7 a message while performing the Mobile Station Order and
8 Message Processing Operation in the Mobile Station Idle State
9 (see 2.6.2.4); otherwise, the base station shall set this field to
10 ‘0’.
11 NGHBR_SET-
12 _ACCESS_INFO - Neighbor Set access handoff included indicator.
14 Set access handoff or access probe handoff, the base station
15 shall set this field to ‘1’, otherwise, the base station shall set
17 ACCESS_HO - Access handoff permitted indicator.
18 If NGHBR_SET_ACCESS_INFO is set to ‘1’, the base station
22 is permitted to perform an access handoff (see 2.6.3.1.3.2);
24 ACCESS_HO_MSG_RSP - Access handoff permitted for message response indicator.
25 If ACCESS_HO is set to ‘1’, the base station shall include this
26 field and set it as described below; otherwise, the base station
29 is permitted to perform an access handoff after receiving a
30 message and before responding to that message in the System
31 Access State; otherwise, the base station shall set this field to
32 ‘0’.
33 ACCESS_PROBE_HO - Access probe handoff permitted indicator.
34 If NGHBR_SET_ACCESS_INFO is set to ‘1’, the base station
38 is permitted to perform an access probe handoff (see
39 2.6.3.1.3.3); otherwise, the base station shall set this field to
40 ‘0’.
41 ACC_HO_LIST_UPD - Access handoff list update permitted indicator.
42 If ACCESS_PROBE_HO is included and is set to ‘1’, the base
43 station shall include this field and set it as described below;
3-150
3GPP2 C.S0005-A v6.0
2 is permitted to update the access handoff list during an
3 access attempt (see 2.6.3.1.7.2); otherwise, the base station
5 ACC_PROBE_HO-
6 _OTHER_MSG - Access probe handoff permitted for messages other than the
7 Origination Message and the Page Response Message.
8 If ACCESS_PROBE_HO is set to ‘1’, the base station shall
9 include this field and set it as described below; otherwise, the
12 is permitted to perform an access probe handoff for messages
13 other than the Origination Message and the Page Response
14 Message. The base station shall set this field to ‘0’ if the
15 mobile station is permitted to perform an access probe
16 handoff only for the Origination Message and the Page
17 Response Message. See 2.6.3.1.3.3.
18 MAX_NUM_PROBE_HO - Maximum number of times that the mobile station is
20 If ACCESS_PROBE_HO is set to ‘1’, the base station shall
24 of times the mobile station is allowed to perform an access
25 probe handoff within an access attempt minus one.
26 NGHBR_SET_SIZE - Size of the Neighbor Set.
27 If NGHBR_SET_ENTRY_INFO or NGHBR_SET_ACCESS_INFO
28 is equal to ‘1’, the base station shall set this field to the
29 number of pilots included in the Neighbor List Message,
30 Extended Neighbor List Message, or General Neighbor List
31 Message; otherwise, the base station shall omit this field.
32 If NGHBR_SET_ENTRY_INFO is equal to ‘1’, the base station shall include
33 NGHBR_SET_SIZE occurrences of the following field:
34 ACCESS_ENTRY_HO - Access entry handoff permitted when entering the System
35 Access State.
3-151
3GPP2 C.S0005-A v6.0
2 is permitted to perform an access entry handoff to the base
3 station associated with the corresponding pilot between the
4 time it receives a message on the Paging Channel when in the
5 Mobile Station Idle State and it enters the System Access State
6 to respond to the message; otherwise, the base station shall
7 set this field to ‘0’. The base station shall use the same order
8 for the ACCESS_ENTRY_HO fields in this message as is used
9 for pilots which are listed in the Neighbor List Message,
11 Message. Specifically, the ith occurrence of the
12 ACCESS_ENTRY_HO field shall correspond the ith pilot in the
13 Neighbor List Message, Extended Neighbor List Message, or
14 General Neighbor List Message.
15 If NGHBR_SET_ACCESS_INFO is equal to ‘1’, the base station shall include
16 NGHBR_SET_SIZE occurrences of the following field:
17 ACCESS_HO_ALLOWED - Access handoff and access probe handoff permitted for the
18 corresponding pilot while in the System Access State.
20 is permitted to perform an access handoff or access probe
21 handoff to the base station associated with the corresponding
22 pilot when the mobile station is in the System Access State
23 (see 2.6.3.1.8 and 2.6.3.1.9); otherwise, the base station shall
24 set this field to ‘0’. The base station shall use the same order
25 for the ACCESS_HO_ALLOWED fields in this message as is
26 used for pilots which are listed in the Neighbor List Message,
28 Message. Specifically, the ith occurrence of the
29 ACCESS_HO_ALLOWED field shall correspond the ith pilot in
30 the Neighbor List Message, Extended Neighbor List Message, or
31 General Neighbor List Message.
32 BROADCAST_GPS_ASST - Broadcast GPS Assist Indicator.
33 The base station shall set this field to ‘1’ if it supports
34 Broadcast GPS Assist capability; otherwise, the base station
36 QPCH_SUPPORTED - Quick Paging Channel Supported Indication.
37 If the base station supports Quick Paging Channel operation,
38 the base station shall set this field to ‘1’; otherwise the base
40 NUM_QPCH - Number of Quick Paging Channels.
41 If the base station sets QPCH_SUPPORTED to ‘1’, the base
44 The base station shall set this field to the number of Quick
45 Paging Channels on this CDMA Channel. The base station
46 shall not set this field to ‘00’.
47 QPCH_RATE - Quick Paging Channel indicator rate.
3-152
3GPP2 C.S0005-A v6.0

4 The base station shall set this field to the QPCH_RATE field
6 indicator rate used by the Quick Paging Channel in the
7 system.
8 Table 3.7.2.3.2.13-2. QPCH Indicator Data Rate
QPCH_RATE Field QPCH indicator data rate

(binary)
0 4800 bps
1 9600 bps
9 QPCH_POWER-
10 _LEVEL_PAGE - Quick Paging Channel paging indicator transmit power level.
14 The base station shall set this field to the Quick Paging
15 Channel paging indicator transmit power level relative to that
16 of the Pilot Channel as specified in Table 3.7.2.3.2.13-3.
3-153
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.13-3 Quick Paging Channel Transmit

2 Power Level
3 QPCH_POWER_LEVEL_PAGE Transmit Power Level
QPCH_POWER_LEVEL_CONFIG
(binary)
000 5 dB below the Pilot

Channel Transmit Power
101 Same as the Pilot Channel
Transmit Power
110 1 dB above the Pilot
111 2 dB above the Pilot
3-154
3GPP2 C.S0005-A v6.0
1 QPCH_CCI_SUPPORTED - Quick Paging Channel configuration change indicator

2 supported.
3 If QPCH_SUPPORTED is set to ‘1’, the base station shall
6 If the base station supports configuration change indicators
7 on the Quick Paging Channel, the base station shall set this
8 field to ‘1’; otherwise the base station shall set this field to ‘0’.
9 QPCH_POWER_LEVEL- - Quick Paging Channel configuration change indicator
10 _CONFIG transmit power level.
11 If the base station includes the QPCH_CCI_SUPPORTED field
12 and sets it to ‘1’, the base station shall include this field and
13 set it as described below; otherwise, the base station shall
14 omit this field.
16 Channel configuration change indicator transmit power level
17 relative to that of the Pilot Channel as specified in Table
18 3.7.2.3.2.13-3.
19 SDB_SUPPORTED - Short Data Burst supported indicator.
21 is permitted to send a Short Data Burst; otherwise, the base
23 RLGAIN_TRAFFIC_PILOT - Gain adjustment of the Reverse Traffic Channel relative to the
24 Reverse Pilot Channel for Radio Configurations greater than 2.
26 be used by mobile stations in setting the power of a reverse
27 traffic channel, expressed as a two’s complement value in
28 units of 0.125 dB (see 2.1.2.3.3 of [2]).
29 REV_PWR-
30 _CNTL_DELAY_INCL - Reverse Power Control Delay included indicator.
31 The base station shall set this field to ‘1’ if the base station
32 includes the REV_PWR_CNTL_DELAY field in this message;
34 REV_PWR-
35 _CNTL_DELAY - The reverse power control delay.
36 If REV_PWR_CNTL_DELAY_INCL is set to ‘0’, the base station
39 The base station shall set this field to the closed-loop reverse
40 power control delay minus one (the closed-loop reverse power
41 control delay is the time between the end of a gated-on reverse
42 PCG and the beginning of the reverse PCG where the
43 corresponding feedback is sent on the Forward Power Control
44 Subchannel, see 2.1.2.3.2 of [2]), in units of 1.25 ms.
45 AUTO_MSG-
3-155
3GPP2 C.S0005-A v6.0
1 _SUPPORTED - Autonomous message supported indicator.

2 If the base station allows the autonomous delivery of the
3 Device Information Message on the r-csch, the base station
6 AUTO_MSG-
7 _INTERVAL - Autonomous message interval.
8 If AUTO_MSG_SUPPORTED is set to ‘01’, the base station
10 this field and shall set this field to the AUTO_MSG_INTERVAL
11 value shown in Table 3.7.2.3.2.13-4 to indicate the minimum
12 time interval between autonomous messages sent by a mobile
13 station to the infrastructure. This parameter is intended to
14 allow the infrastructure to limit the frequency of autonomous
15 messages sent by a mobile station on the r-csch.
16 Table 3.7.2.3.2.13-4. AUTO_MSG_INTERVAL Values
AUTO_MSG_INTERVAL Interval Length

(binary) (milliseconds)
000 200
001 500
010 1000
011 1500
100 2000
101 5000
110 10000
111 15000
17
18 MOB_QOS - Indicator granting permission to the mobile station to request

19 QoS parameter settings in the Origination Message, Origination
20 Continuation Message, or Enhanced Origination Message.
21 The base station shall set this field to ‘1’, if the mobile station
22 is allowed to include a QoS record in the Origination Message,
23 Origination Continuation Message, or Enhanced Origination
24 Message;, or to ‘0’, otherwise, the base station shall set this
3-156
3GPP2 C.S0005-A v6.0
1 ENC_SUPPORTED – Encryption fields included.

2 The base station shall set this field to ‘1’ if the encryption
3 related fields are included; otherwise the base station shall set
6 If ENC_SUPPORTED is equal to ‘1’, the base station shall
7 include this field; otherwise, the base station shall omit this
8 field. If this field is included, this field indicates which
9 signaling encryption algorithms are supported by the base
10 station.
12 5.
13 If this field is included, the base station shall set the subfields
14 as follows:
15 The base station shall set the CMEA subfield to ‘1’.
16 The base station shall set each other subfield to ‘1’ if the
18 the base station; otherwise, the base station shall set the
20 The base station shall set the RESERVED subfield to ‘000000’.
24 field. If this field is included, the base station shall set this
26 algorithms.
28 9.
29 The base station shall set each subfield to ‘1’ if the
31 supported by the base station; otherwise, the base station
33 STORE_KEY – Store session key indicator
34 If ENC_SUPPORTED is equal to ‘1’, , the base station shall
37 field to ‘1’ to indicate that the mobile station is to store the
38 session key; otherwise the base station shall set this field to
39 ‘0’.
40 USE_SYNC_ID - Sync ID supported indicator.
42 mobile station is permitted to include the SYNC_ID field in the
43 Page Response Message and the Origination Message.
44 Otherwise, the base station shall set this field to ‘0’.
45 CS_SUPPORTED - Concurrent Services supported indicator.
3-157
3GPP2 C.S0005-A v6.0
1 If the base station supports concurrent services, the base

2 station shall set this field to ‘1’; otherwise, the base station
4 BCCH_SUPPORTED - Primary Broadcast Channel Supported Indicator.
5 If the base station supports Primary Broadcast Control

6 Channel, the base station shall set this field to ‘1’; otherwise,
8 MS_INIT_POS_LOC - Mobile station initiated position location determination
9 _SUP_IND supported indicator.
10 If the base station supports mobile station initiated position
11 determination, the base station shall set this field to ‘1’;
13 PILOT_INFO_REQ
14 _SUPPORTED - Pilot information request supported indicator.
15 If the base station supports mobile station request for pilot
16 information using the “Pilot Information” record in the Base
17 Station Status Request Message, the base station shall set this
19
20
21
3-158
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.14 Extended Neighbor List Message
2 MSG_TAG: ENLM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
PILOT_INC 4
NGHBR_CONFIG 3
NGHBR_PN 9
SEARCH_PRIORITY 2
FREQ_INCL 1
NGHBR_BAND 0 or 5
NGHBR_FREQ 0 or 11

9 (see 3.6.2.2).
20 15 inclusive.
3-159
3GPP2 C.S0005-A v6.0
1 The base station shall include one occurrence of the following record for each pilot that a
2 mobile station is to place in its Neighbor Set.
6 neighbor.
7
Value
(binary) Neighbor Configuration
000 The neighbor base station has the same number of frequencies having Paging
Channels as the current base station.
The neighbor base station has a CDMA frequency assignment corresponding

to this CDMA frequency assignment with the same number of Paging
Channels, and the neighbor CDMA frequency is given as follows:
• If FREQ_INCL equals ‘0’ for this record, this corresponding CDMA

frequency assignment is the current CDMA frequency assignment.

frequency assignment is given by NGHBR_BAND and NGHBR_FREQ.

transmitted by the neighbor base station is the same as the position of this
current CDMA frequency assignment in the CDMA Channel List Message or
the Extended CDMA Channel List Message transmitted by the current base
station.
3-160
3GPP2 C.S0005-A v6.0

to this CDMA frequency assignment with a different number of Paging



station.

010 The neighbor base station may have a different number of frequencies having
The neighbor base station has a Primary Paging Channel on the following
CDMA frequency:
• If FREQ_INCL equals ‘0’ for this record, the neighbor base station has a
Primary Paging Channel on the first CDMA Channel listed in the CDMA
transmitted by the current base station.
Primary Paging Channel on the CDMA frequency assignment given by
NGHBR_BAND and NGHBR_FREQ.
3-161
3GPP2 C.S0005-A v6.0
011 The neighbor base station configuration is unknown but the neighbor base
station has a Pilot Channel on the following frequency:
• If FREQ_INCL equals ‘0’ for this record, the neighbor CDMA frequency
assignment is the same as the current CDMA frequency assignment
and has a Pilot Channel.
• If FREQ_INCL equals ‘1’ for this record, the CDMA frequency
assignment given by NGHBR_BAND and NGHBR_FREQ has a Pilot
Channel.
100-111 Reserved.

5 SEARCH_PRIORITY - Pilot Channel search priority.
6 The base station shall set this field to the search priority for
7 the Pilot Channel corresponding to NGHBR_PN. The base
8 station shall set the search priority as shown in Table
9 3.7.2.3.2.14-2.
10 Table 3.7.2.3.2.14-2. Search Priority Field
Value
(binary) Search Priority
00 Low
01 Medium
10 High
11 Very high
11

13 If the NGHBR_BAND and NGHBR_FREQ fields are included
14 for this neighbor base station, the base station shall set this
15 bit to ‘1’. If the NGHBR_BAND and NGHBR_FREQ fields are
16 not included for this neighbor base station, the base station
18 NGHBR_BAND - Neighbor band class.
23 station is to search. If the FREQ_INCL bit is set to ‘0’, the
3-162
3GPP2 C.S0005-A v6.0
1 NGHBR_FREQ - Neighbor frequency assignment.

6 Channel the mobile station is to search. If the FREQ_INCL bit
7 is set to ‘0’, the base station shall omit this field.
3-163
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.15 Status Request Message
2 MSG_TAG: STRQM
Field Length (bits)
RESERVED 4
QUAL_INFO_TYPE 8
QUAL_INFO_LEN 3
NUM_FIELDS 4
RECORD_TYPE 8

9 information in the type-specific fields. The base station shall
10 include the required qualification information in this message.
11 Table 3.7.2.3.2.15-1. Qualification Information Type
Value (binary) Included Information
00000000 None
00000001 BAND_CLASS
00000010 BAND_CLASS and OP_MODE
12
3-164
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.15-2. Status Information Record Types
Record Type
(see Table 2.7.4-1) QUAL_INFO_TYPE
Information Record Requested (binary) (binary)
Reserved for obsolete Identification 00000110 -

Call Mode 00000111 00000000
Terminal Information 00001000 00000010
Roaming Information 00001001 00000010
Security Status 00001010 00000000
IMSI 00001100 00000000
ESN 00001101 00000000
Band Class Information 00001110 00000000
Power Class Information 00001111 00000010
Operating Mode Information 00010000 00000001
Service Option Information 00010001 00000010
Multiplex Option Information 00010010 00000010
Service Configuration 00010011 00000000
Power Control Information 00010111 00000000
IMSI_M 00011000 00000000
IMSI_T 00011001 00000000
Capability Information 00011010 00000000
Channel Configuration Capability 00011011 00000000
Information 00011100
Extended Multiplex Option 00011100 00000000
Information 00011101
Geo-location Information 00011110 00000000
Band Subclass Information 00011111 00000001
Hook Status 00100001 00000000
00100000
Encryption Capability 00100011 00000000
00100001
3-165
3GPP2 C.S0005-A v6.0

4 information.
6 The base station shall set these fields to the qualification
10 If QUAL_INFO_TYPE is equal to ‘00000001’, the base station
12 fields:
13
BAND_CLASS 5
RESERVED 3
14

17 fields:
18
BAND_CLASS 5
OP_MODE 8
RESERVED 3
19

21 The base station shall set this field as defined in [30] to
22 specify the band class qualification information.
24 The base station shall set this field as shown in
26 qualification information if MOB_P_REV of the current band
27 class is less than or equal to three. The base station shall set
28 this field as shown in Table 3.7.2.3.2.15-4 to specify the
29 operating mode qualification information if MOB_P_REV of the
30 current band class is greater than three.
31
3-166
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.15-3. Operating Mode for MOB_P_REV

2 Less Than or Equal to Three
Description Value (binary)
CDMA mode in Band Class 1 or Band 00000000

Class 4
CDMA mode in Band Class 0 or Band 00000001
Class 3
analog mode [6] 00000010
wide analog mode [22] 00000011
Narrow analog mode [22] 00000100
4 Table 3.7.2.3.2.15-4. Operating Mode for MOB_P_REV

5 Greater Than Three
Standards
Description Value (binary)
CDMA mode [5] 00000000 or

00000001
Analog mode [6] 00000010
Wide analog mode [22] 00000011
Narrow analog mode [22] 00000100
DS-41 mode [32] 00000101
MC-MAP mode [31] 00000110
7 NUM_FIELDS - Number of requested fields in this message.

9 occurrences of RECORD_TYPE in this message.
10 The base station shall only request the status information records qualified by the included
11 qualification information in this message. The base station shall include one occurrence of
12 the following field for each information record that is requested:
14 The base station shall set this field to the record type value
3-167
3GPP2 C.S0005-A v6.0
1 If MOB_P_REV is equal to or greater than seven, the base

2 station shall not request the Call Mode information record
3 (record type 00000111in Table 3.7.2.3.2.15-2).
4
3-168
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.16 Service Redirection Message
2 MSG_TAG: SRDM
Field Length (bits)
RETURN_IF_FAIL 1
DELETE_TMSI 1
REDIRECT_TYPE 1
One occurrence of the following record:
RECORD_TYPE 8
RECORD_LEN 8
4 RETURN_IF_FAIL - Return if fail indicator.

6 is required to return to the system from which it is being
7 redirected upon failure to obtain service using the redirection
8 criteria specified in this message; otherwise, the base station
10 DELETE_TMSI - Delete TMSI indicator.
12 is required to delete the TMSI assigned to the mobile station;
14 REDIRECT_TYPE - Redirect indicator.

15 The base station shall set this field to the REDIRECT_TYPE
16 value shown in table 3.7.2.3.2.16-2 corresponding to the
17 redirection type.
18 Table 3.7.2.3.2.16-1. Redirection Types
REDIRECT_TYPE
Description
(binary)
Normal redirection 0
NDSS redirection 1
19
20 The base station shall include one occurrence of the following record:
21 RECORD_TYPE - Redirection record type.
22 The base station shall set this field to the RECORD_TYPE
24 of redirection specified by this record.
25
3-169
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.16-2. Redirection Record Types
RECORD_TYPE
NDSS off indication 00000000

Redirection to an analog system as 00000001
defined in [12], [21], [22], [25], [24], and
[6]
Redirection to a CDMA system as defined 00000010
in [24] and [2]
Redirection to a TACS analog system as 00000011
defined in Department of Trade and
Industry’s TACS Mobile Station-Land
Station Compatibility Specification,
Issue 4, Amendment 1.
Redirection to a JTACS analog system as 00000100
defined in ARIB’s RCR STD-36.
Redirection to a DS-41 system as defined 00000101
in [32].
All other RECORD_TYPE values are reserved
3 RECORD_LEN - Redirection record length.

4 If RECORD_TYPE equals to ‘00000000’, the base station shall
5 set this field to ‘00000000’; otherwise, the base station shall
7 of this redirection record.
8 Type-specific fields - Redirection record type-specific fields.
9 The base station shall include type-specific fields based on the
10 RECORD_TYPE of this redirection record.
11 If RECORD_TYPE is equal to ‘00000000’, the base station shall not include the type-specific
12 fields.
13 If RECORD_TYPE is equal to ‘00000001’, the base station shall include the following fields:
14
Field Length (bits)
EXPECTED_SID 15
IGNORE_CDMA 1
SYS_ORDERING 3
RESERVED 5
15
3-170
3GPP2 C.S0005-A v6.0
1 EXPECTED_SID - Expected SID.

2 If the base station is redirecting the mobile station to a
3 specific system, the base station shall set this field to the SID
4 of that system; otherwise, the base station shall set this field
5 to 0.
6 IGNORE_CDMA - Ignore CDMA Available indicator.
8 mobile station is to ignore the CDMA Capability Message on
9 the analog system to which it is being redirected. The base
10 station shall set this field to ‘0’ to indicate that the mobile
11 station may discontinue service on the system to which it is
12 being redirected if the mobile station receives a CDMA
13 Capability Message with CDMA_AVAIL equal to ‘1’, and the
14 preferred mode of the mobile station is CDMA.
15 SYS_ORDERING - System ordering.
16 The base station shall set this field to the SYS_ORDERING
18 order in which the mobile station is to attempt to obtain
19 service on an analog system.
20
3-171
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.16-3. SYS_ORDERING
SYS_ORDERING
Description
(binary)
Attempt to obtain service on either 000

System A or B in accordance with the
custom system selection process (see
2.6.1.1.1).
Attempt to obtain service on System A 001
only.
Attempt to obtain service on System B 010
only.
Attempt to obtain service on System A 011
first. If unsuccessful, attempt to
obtain service on System B.
Attempt to obtain service on System B 100
first. If unsuccessful, attempt to
obtain service on System A.
Attempt to obtain service on either 101
System A or System B. If
unsuccessful, attempt to obtain
service on the alternate system
(System A or System B).
All other SYS_ORDERING values are reserved

3-172
3GPP2 C.S0005-A v6.0
Subfield Length (bits)
BAND_CLASS 5
EXPECTED_SID 15
EXPECTED_NID 16
RESERVED 4
NUM_CHANS 4
NUM_CHANS occurrences of the following field:

CDMA_CHAN 11
RESERVED 0-7 (as needed)

4 The base station shall set this field to the CDMA band class,
10 to 0.
11 EXPECTED_NID - Expected NID.
13 specific network, the base station shall set this field to the
14 NID of that network; otherwise, the base station shall set this
15 field to 65535.
18 NUM_CHANS - Number of CDMA Channels.
20 occurrences of the CDMA_CHAN field in this record.
21 CDMA_CHAN - CDMA Channel number.
22 For each CDMA Channel on which the mobile station is to
23 attempt to acquire a CDMA system, the base station shall
24 include one occurrence of this field specifying the associated
25 CDMA Channel number.
28 make the length of the record equal to an integer number of
29 octets. The base station shall set these bits to ‘0’.
3-173
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.17 General Page Message
2 MSG_TAG: GPM
3 When Layer 3 at the base station sends a PDU corresponding to the General Page Message
4 to Layer 2, it also sends the GPM Common fields to Layer 2. These GPM Common fields
5 and PDUs are used by Layer 2 to assemble a Layer 2 PDU corresponding to the General
6 Page Message (see 3.1.2.3 of [4]).
7 GPM Common Fields:
Field Length (bits)
CONFIG_MSG_SEQ 6
ACC_MSG_SEQ 6
CLASS_0_DONE 1
CLASS_1_DONE 1
TMSI_DONE 1
ORDERED_TMSIS 1
BROADCAST_DONE 1
RESERVED 4
ADD_LENGTH 3
ADD_PFIELD 8 × ADD_LENGTH
10 PDU Format for a mobile station-addressed page:
11
Field Length (bits)
SERVICE_OPTION 0 or 16
12
13 PDU Format for a broadcast page:
14
Field Length (bits)
- 0
15
16 PDU Format for an enhanced broadcast page:
17
3-174
3GPP2 C.S0005-A v6.0
Field Length (bits)
BCCH_INDEXBCN 3
TIME_OFFSET 10
REPEAT_TIME_OFFSET 0 or 5
ADD_BCAST_RECORD 0 or 8 × EXT_BCAST_-
SDU_LENGTH (see [4])

4 (see 3.6.2.2).
6 The base station shall set this field to ACC_CONFIG_SEQ
7 (see 3.6.2.2).
8 CLASS_0_DONE - Class 0 pages are done.
9 If all messages and records directed to mobile stations
10 operating in the slotted mode, active in this slot, and having
11 an assigned class 0 IMSI have been sent by the end of this
12 General Page Message, the base station shall set this field to
14 CLASS_1_DONE - Class 1 pages are done.
16 operating in the slotted mode, active in this slot, and having
17 an assigned class 1 IMSI have been sent by the end of this
18 General Page Message, the base station shall set this field to
20 TMSI_DONE - TMSI pages are done.
21 If all the page records having PAGE_CLASS equal to ‘10’ or
22 other directed messages for mobile stations operating in the
23 slotted mode, active in this slot, and having an assigned TMSI
24 have been sent by the end of this General Page Message, the
25 base station shall set this field to ‘1’; otherwise, the base
27 ORDERED_TMSIS - TMSIs sent in numerical order.
28 If all the page records of PAGE_CLASS equal to ‘10’ are sent
29 such that the TMSI code values of the TMSI_CODE_ADDR
30 fields for the mobile stations operating in the slotted mode are
31 in ascending numerical order in all the General Page
32 Messages sent within this slot, the base station shall set this
34 BROADCAST_DONE - Broadcast pages are done.
3-175
3GPP2 C.S0005-A v6.0
1 If all broadcast page records (PAGE_CLASS equal to ‘11’) have

2 been sent by the end of this General Page Message, the base
7 ADD_LENGTH - Number of octets in the page message specific fields.
8 If there are no additional page message specific fields, the
10 ADD_PFIELD - Additional page message specific fields.
11 The base station shall not include any additional page
12 message specific fields, if ADD_LENGTH is ‘000’.
13 SERVICE_OPTION - Service option.
14 If the base station requests a special service option in the page

15 type-specific fields(i.e., the SDU_INCLUDED field, see [4], is
16 set to ‘1’), the base station shall set this field to the service
17 option code shown in [30], corresponding to the requested
18 service option; otherwise, the base station shall omit this field.
19 BCCH_INDEX BCN - BCCH indexBroadcast Control Channel Number.
20 The base station shall set this field to the index of the BCCH
21 to which the mobile station is being redirected.
22 TIME_OFFSET - BCCH time offset.
23 The base station shall set this field to one less than the time
24 offset, in units of 40 ms, from the beginning of the slot in
25 which this message began to the beginning of the Broadcast
26 Control Channel slot to which the mobile station is being
27 directed.
28 REPEAT_TIME-
29 _OFFSET - BCCH offset of repeat.
30 If EXT_BCAST_SDU_LENGTH_IND (see [4]) is set to ‘01’ or ‘11’

31 this field is included, the base station shall set this field to
32 one less than the time offset, in units of 40 ms, from the time
33 specified by TIME_OFFSET to the beginning of the Broadcast
35 directed for a repeat of the broadcast message. Otherwise, the
37 ADD_BCAST_RECORD - Additional broadcast information record.
38 The base station shall omit this field if
39 EXT_BCAST_SDU_LENGTH_IND (see 3.1.2.3.1.8 of [4]) is set
40 to ‘00’ or ‘01’; otherwise, the base station shall include
41 EXT_BCAST_SDU_LENGTH (see 3.1.2.3.1.8 of [4]) octets in
42 this field.
3-176
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.18 Global Service Redirection Message
2 MSG_TAG: GSRDM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
REDIRECT_ACCOLC 16
RETURN_IF_FAIL 1
DELETE_TMSI 1
EXCL_P_REV_MS 1
RECORD_TYPE 8
RECORD_LEN 8

9 (see 3.6.2.2).
3-177
3GPP2 C.S0005-A v6.0
1 REDIRECT_ACCOLC - Redirected access overload classes.

2 This field consists of the following subfields:
Length
Subfield Subfield Description
(bits)
ACCOLC_0 1 Access overload class 0

4 The base station shall set the subfields corresponding to the

5 access overload classes of mobile stations which are to be
6 redirected to ‘1’, and shall set the remaining subfields to ‘0’.
14 The base station shall set this field to ‘1’ if the mobile station,
15 which the corresponding REDIRECT_ACCOLC subfield is set
16 to ‘1’, is required to delete the TMSI assigned to the mobile
17 station; otherwise, the base station shall set this field to ‘0’.
18 EXCL_P_REV_MS - Exclude redirection indicator.
3-178
3GPP2 C.S0005-A v6.0
1 If this message does not apply to mobile stations with

2 MOB_P_REV greater than or equal to six, the base station
5
6 The base station shall include one occurrence of the following three-field record:
13 the type-specific fields of this redirection record.
18
Field Length (bits)
EXPECTED_SID 15
IGNORE_CDMA 1
SYS_ORDERING 3
MAX_REDIRECT_DELAY 5
19

24 to 0.
3-179
3GPP2 C.S0005-A v6.0

5 MAX_REDIRECT_DELAY - Maximum delay upon redirection.
6 The base station shall set this field to the maximum delay
7 time, in units of 8 second increments, to be used by mobile
8 stations in the event of a global redirection to analog mode.
9 This operation can be invoked to avoid overloading an
10 underlying analog cell’s reverse control channel.
11
13
BAND_CLASS 5
EXPECTED_SID 15
EXPECTED_NID 16
RESERVED 4
NUM_CHANS 4
CDMA_CHAN 11
14

22 to 0.
27 field to 65535.
3-180
3GPP2 C.S0005-A v6.0

3-181
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.19 TMSI Assignment Message
2 MSG_TAG: TASM
Field Length (bits)
RESERVED 5
TMSI_ZONE_LEN 4
TMSI_CODE 32
TMSI_EXP_TIME 24

11 The base station shall set this field to the TMSI zone number,
13 TMSI_CODE - Temporary mobile station identity code.
14 The base station shall set this field to the 32-bit TMSI code
15 assigned to the mobile station.
16 If the base station is to deassign the TMSI, the base station
17 shall set all the bits in this field to ‘1’.
18 TMSI_EXP_TIME - TMSI expiration time.
19 The base station shall set this field to the System Time in the
20 units of 80 ms × 212 when the TMSI is to expire.
3-182
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.20 PACA Message
2 MSG_TAG: PACAM
Field Length (bits)
RESERVED 7
PURPOSE 4
Q_POS 8
PACA_TIMEOUT 3

6 PURPOSE - Purpose of the PACA Message.
7 The base station shall set this field to the appropriate
8 PURPOSE code from Table 3.7.2.3.2.20-1 to indicate the
10
11 Table 3.7.2.3.2.20-1. Purpose of PACA Message
PURPOSE
(binary) Meaning

message is to respond to an Origination
Message.
message is to provide the queue position
of the PACA call.
message is to instruct the mobile station
to re-originate the PACA call.
message is to cancel the PACA call.
12
13 Q_POS - PACA queue position.

14 If the PURPOSE field of this message is set to ‘0000’ or ‘0001’,
15 the base station shall set this field to the queue position of the
16 PACA call. If the queue position exceeds 255, the base station
17 shall set this field to ‘11111111’. If the queue position is
18 unknown or the PURPOSE field of this message is set to ‘0010’
19 or ‘0011’, the base station shall set this field to ‘00000000’.
3-183
3GPP2 C.S0005-A v6.0
1 PACA_TIMEOUT - PACA state timer duration.

2 The base station shall set this field to the PACA_TIMEOUT
4 length of the PACA state timer to be used by the mobile
5 stations.
6 Table 3.7.2.3.2.20-2. Value of PACA State Timer
PACA_TIMEOUT Timer Length

000 1
001 2
010 5
011 10
100 20
101 30
110 45
111 60
3-184
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.21 Extended Channel Assignment Message
2 MSG_TAG: ECAM
Field Length (bits)

ASSIGN_MODE 3
RESERVED_2 5
Additional record fields 8×
(ADD_RECORD_LEN –
1) See [4]
3-185
3GPP2 C.S0005-A v6.0
FREQ_INCL 1
DEFAULT_CONFIG 3
RESERVED 1
NUM_PILOTS 3
GRANTED_MODE 2
FRAME_OFFSET 4
ENCRYPT_MODE 2
BAND_CLASS 0 or 5
CDMA_FREQ 0 or 11
NUM_PILOTS plus one occurrence of the following record:
PILOT_PN 9
PWR_COMB_IND 1
CODE_CHAN 8
FOR_FCH_RC 5
REV_FCH_RC 5
FPC_FCH_INIT_SETPT 8
FPC_SUBCHAN_GAIN 5
RLGAIN_ADJ 4
FPC_FCH_FER 5
FPC_FCH_MIN_SETPT 8
FPC_FCH_MAX_SETPT 8
REV_FCH_GATING_MODE 1
REV_PWR_CNTL_DELAY_INCL 0 or 1
USE_NEW_KEY 0 or 1
ENC_KEY_SIZE 0 or 3
KEY_SEQ 0 or 4
3-186
3GPP2 C.S0005-A v6.0
RESERVED 0 – 7 (as needed)
3-187
3GPP2 C.S0005-A v6.0
RESPOND 1
FREQ_INCL 1
BAND_CLASS 0 or 5
CDMA_FREQ 0 or 11
NUM_PILOTS 6
NUM_PILOTS plus one occurrence of the following field:
PILOT_PN 9
RESPOND 1
ANALOG_SYS 1
USE_ANALOG_SYS 1
BAND_CLASS 5
SID 15
VMAC 3
ANALOG_CHAN 11
SCC 2
MEM 1
AN_CHAN_TYPE 2
DSCC_MSB 1
BAND_CLASS 5
3-188
3GPP2 C.S0005-A v6.0
FREQ_INCL 1
BAND_CLASS 0 or 5
CDMA_FREQ 0 or 11
GRANTED_MODE 2
DEFAULT_CONFIG 3
FOR_RC 5
REV_RC 5
FRAME_OFFSET 4
ENCRYPT_MODE 2
FPC_SUBCHAN_GAIN 5
RLGAIN_ADJ 4
NUM_PILOTS 3
CH_IND 2
CH_RECORD_LEN 5
CH_RECORD_FIELDS 8 × CH_RECORD_LEN
USE_NEW_KEY 0 or 1
ENC_KEY_SIZE 0 or 3
KEY_SEQ 0 or 4
3XFL_1XRL_INCL 1
1XRL_FREQ_OFFSET 0 or 2
3-189
3GPP2 C.S0005-A v6.0
1 If CH_IND = ‘01’, the CH_RECORD_FIELDS shall be:
FPC_FCH_FER 5
FPC_FCH_MIN_SETPT 8
FPC_FCH_MAX_SETPT 8

PILOT_PN 9
ADD_PILOT_REC_INCL 1
RECORD_LEN 0 or 3
Type-specific fields 0 or (8 ×
RECORD_LEN)
PWR_COMB_IND 1
CODE_CHAN_FCH 11
QOF_MASK_ID_FCH 2
3X_FCH_INFO_INCL 1
NUM_PILOTS plus one occurrence of the following record if

3X_FCH_INFO_INCL is set to ‘1’:
3X_FCH_LOW_INCL 1
QOF_MASK_ID_FCH_LOW 0 or 2
CODE_CHAN_FCH_LOW 0 or 11
3X_FCH_HIGH_INCL 1
QOF_MASK_ID_FCH_HIGH 0 or 2
CODE_CHAN_FCH_HIGH 0 or 11
3-190
3GPP2 C.S0005-A v6.0
FPC_DCCH_INIT_SETPT 8
FPC_DCCH_FER 5
FPC_DCCH_MIN_SETPT 8
FPC_DCCH_MAX_SETPT 8
PILOT_PN 9
RECORD_LEN 0 or 3
RECORD_LEN)
PWR_COMB_IND 1
CODE_CHAN_DCCH 11
QOF_MASK_ID_DCCH 2
3X_DCCH_INFO_INCL 1

3X_DCCH_INFO_INCL is set to ‘1’:
3X_DCCH_LOW_INCL 1
QOF_MASK_ID_DCCH_LOW 0 or 2
CODE_CHAN_DCCH_LOW 0 or 11
3X_DCCH_HIGH_INCL 1
QOF_MASK_ID_DCCH_HIGH 0 or 2
CODE_CHAN_DCCH_HIGH 0 or 11
3-191
3GPP2 C.S0005-A v6.0
FPC_DCCH_INIT_SETPT 8
FPC_PRI_CHAN 1
FPC_FCH_FER 5
FPC_FCH_MIN_SETPT 8
FPC_FCH_MAX_SETPT 8
FPC_DCCH_FER 5
FPC_DCCH_MIN_SETPT 8
FPC_DCCH_MAX_SETPT 8
PILOT_PN 9
RECORD_LEN 0 or 3
RECORD_LEN)
PWR_COMB_IND 1
CODE_CHAN_FCH 11
QOF_MASK_ID_FCH 2
CODE_CHAN_DCCH 11
QOF_MASK_ID_DCCH 2
3X_FCH_INFO_INCL 1

3X_FCH_LOW_INCL 1
CODE_CHAN_ FCH_LOW 0 or 11
3-192
3GPP2 C.S0005-A v6.0
3X_FCH_HIGH_INCL 1
CODE_CHAN_ FCH_HIGH 0 or 11
3X_DCCH_INFO_INCL 1

3X_DCCH_LOW_INCL 1
3X_DCCH_HIGH_INCL 1
CODE_CHAN_ DCCH_HIGH 0 or 11
3 ASSIGN_MODE - Assignment mode.

5 Table 3.7.2.3.2.21-1 corresponding to the assignment mode
6 for this assignment.
7
8 Table 3.7.2.3.2.21-1. Assignment Mode
Value
Assignment Mode
(binary)
000 Traffic Channel Assignment

001 Paging Channel Assignment
010 Acquire Analog System
011 Analog Voice Channel Assignment
100 Enhanced Traffic Channel Assignment

12 Additional record fields - Additional record fields.
3-193
3GPP2 C.S0005-A v6.0
1 The additional record fields are determined by the value of

2 ASSIGN_MODE, as described below.
13 indicate an initial multiplex option and radio configuration for
14 the Forward and Reverse Traffic Channels.
15 If MOB_P_REV is less than six, the base station shall not set
3-194
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.21-2. Default Configuration
Value
(binary) Default Configuration
000 Multiplex Option 1 and Radio Configuration 1

for both the Forward Traffic Channel and the
Reverse Traffic Channel
for both the Forward Traffic Channel and the
Reverse Traffic Channel
for the Forward Traffic channel; Multiplex
Option 2 and Radio Configuration 2 for the
for the Forward Traffic channel; Multiplex
Option 1 and Radio Configuration 1 for the
100 FOR_FCH_RC or FOR_RC included in this
message for the Forward Fundamental Channel
or the Forward Dedicated Control Channel and
REV_FCH_RC or REV_RC included in this
message for the Reverse Fundamental or the
Reverse Dedicated Control Channel. Use 20ms
frames. Use Multiplex Option 1 for radio
configurations that include the bit rate of 9600
bps; Use Multiplex Option 2 for radio
configurations that include the bit rate of
14400 bps.
3 BYPASS_ALERT-
10 RESERVED - Reserved bit.
3-195
3GPP2 C.S0005-A v6.0
1 NUM_PILOTS - Number of pilots in the Active Set.

2 The base station shall set this field to number of pilots that
3 are to be in the mobile station’s Active Set on the Traffic
4 Channel minus one. The base station shall set this field to
5 the value in the range 0 to N6m-1 inclusive.
9 consisting of the multiplex option and radio configuration
11 Reverse Traffic Channels, and to indicate that service
12 negotiation may take place before the base station sends the
18 that is derived from the radio configuration corresponding to
19 Table 3.7.2.3.2.21-7mobile station either in the Origination
20 Message or Page Response Message, and to indicate that
21 service negotiation may take place before the base station
22 sends the first Service Connect Message.
26 that is derived from the radio configuration corresponding to
27 Table 3.7.2.3.2.21-7rates corresponding to the service option
28 requested by the mobile station either in the Origination
30 service negotiation is not to take place before the base station
32 Table 3.7.2.3.2.21-7. Mapping between Multiplex Options

33 and Radio Configurations
Multiplex Option
Radio Configuration
Multiplex Option 1 Forward link: RC1, RC3, RC4,

RC6, or RC7
Reverse Link: RC1, RC3 or RC5
Multiplex Option2 Forward link: RC2, RC5, RC 8, or
RC9
Reverse Link: RC2, RC4 or RC 6
34

3-196
3GPP2 C.S0005-A v6.0
12 CDMA Channel containing the Forward Traffic Channel the
19 assignment for the CDMA Channel containing the Forward
20 Traffic Channel the mobile station is to use. If the
21 FREQ_INCL bit is set to ‘0’, the base station shall omit this
22 field.
23 The base station shall include NUM_PILOTS plus one occurrence of the following three-field
24 record, one for each member of the mobile station’s Active Set on the Traffic Channel.
28 PWR_COMB_IND - Power control symbol combining indicator.
29 If the Forward Traffic Channel associated with this pilot will
30 carry the same closed-loop power control subchannel bits as
31 that of the previous pilot in this message, the base station
33 this field to ‘0’. For the first occurrence of this record in the
34 message, the base station shall set this field to ‘0’.
35 CODE_CHAN - Code channel index.
37 (see 2.1.3.1.9 and 3.1.3.1.13 of [2]) that the mobile station is
38 to use on the Forward Traffic Channel associated with this
39 pilot. If Radio Configuration 1, 2, 3, or 5 (see 3.1.3.1.2 of [2])
40 is used, the base station shall set this field in the range 1 to
41 63 inclusive. If Radio Configuration 4, 6 or 8 is used, the base
42 station shall set this field in the range 1 to 127 inclusive. If
43 Radio Configuration 7 or 9 is used, the base station shall set
44 this field in the range 1 to 255 inclusive.
45 FOR_FCH_RC - Forward Fundamental Channel radio configuration
3-197
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the radio configuration
2 (see Table 3.7.2.3.2.21-3) to be used by the mobile station on
3 the Forward Fundamental Channel before the first Service
4 Connect Message is sent to the mobile station.
5 If GRANTED_MODE is set to ‘00’, and DEFAULT_CONFIG is
6 not set to ‘100’ (see Table 3.7.2.3.2.21-2), the base station
7 shall set this field to either ‘00001’ or ‘00010’ (see Table
8 3.7.2.3.2.21-3).
9 REV_FCH_RC - Reverse Fundamental Channel radio configuration
12 the Reverse Fundamental Channel before the first Service
13 Connect Message is sent to the mobile station.
17 3.7.2.3.2.21-3).
18 Table 3.7.2.3.2.21-3. Radio Configurations
Value
(binary) Radio Configuration
00001 RC 1
00010 RC 2
00011 RC 3
00100 RC 4
00101 RC 5
00110 RC 6
00111 RC 7
01000 RC 8
01001 RC 9

19
20 FPC_FCH_INIT_SETPT - Initial Fundamental Channel outer loop Eb/Nt setpoint.
21 The base station shall set this field to initial Fundamental

22 Channel outer loop Eb/Nt setpoint, in units of 0.125 dB.
23 FPC_SUBCHAN_GAIN - Forward power control subchannel relative gain.
3-198
3GPP2 C.S0005-A v6.0
1 The base station shall set FPC_SUBCHAN_GAIN equal to the

2 power level of the forward link power control subchannel
3 relative to the power level of 20 ms frames at a 9600 bps or
4 14400 bps rate of the Forward Fundamental Channel that the
5 Forward Power Control Subchannel is punctured on. The
6 base station shall set the value in units of 0.25 dB.
7 RLGAIN_ADJ - Reverse Traffic Channel power relative to access power.
8 The base station shall set this field to adjust the initial Traffic
9 Channel transmission power relative to the Access Channel or
10 Enhanced Access Channel transmission power. The base
11 station shall set this field as a two’s complement signed
12 binary number, in units of 1 dB.
13 FPC_FCH_FER - Fundamental Channel target Frame Error Rate.
14 The base station shall set this field to the target Frame Error
15 Rate on the Forward Fundamental Channel, as specified in
16 Table 3.7.3.3.2.25-2.
17 FPC_ FCH_MIN_SETPT - Minimum Fundamental Channel Outer Loop Eb/Nt setpoint.
18 The base station shall set this field to minimum Fundamental

19 Channel Outer Loop Eb/Nt setpoint, in units of 0.125 dB.
20 FPC_ FCH_MAX_SETPT - Maximum Fundamental Channel Outer Loop Eb/Nt setpoint.
21 The base station shall set this field to maximum Fundamental
23 REV_FCH-
24 _GATING_MODE - Reverse eighth gating mode indicator.
26 is allowed to perform the reverse eighth gating mode where
th
27 the 1/8 rate frames on the Reverse Fundamental Channel
28 are gated off for 10 ms per frame (see 2.1.2.3.2 of [2]);
30 The base station shall not set this field to ‘1’ if
31 REV_FCH_GATING_REQ included in the Origination Message
32 or Page Response Message is set to ‘0’.
33 REV_PWR-
34 _CNTL_DELAY_INCL - Reverse power control delay included indicator.
35 If REV_FCH_GATING_MODE is set to ‘0’, the base station shall
36 omit this field; otherwise, the base station shall include this
38 The base station shall set this field to ‘1’ if
39 REV_PWR_CNTL_DELAY is included in this message;
41 If the REV_FCH_GATING_MODE field in this message is set to
42 ‘1’ and the REV_PWR_CNTL_DELAY_INCL field in the
43 Extended System Parameters Message or MC-RR Parameters
44 Message is set to ‘0’, the base station shall set this field to ‘1’.
3-199
3GPP2 C.S0005-A v6.0
1 REV_PWR-
11 Subchannel, see 2.1.2.3.2 of [2]) used by the mobile station
12 after handoff, in units of 1.25 ms.
13 D_SIG_ENCRYPT_MODE - General Dedicated channel signaling encryption mode indicator.
16 message encryption mode, as shown in Table 3.7.4.5-1; otherwise
20 include this field. If this field is included, the base station shall
21 set this field to ‘0’ to indicate that the stored encryption key to be
22 used by the mobile station. Otherwise, the base station shall set
23 this field to ‘1’ to indicate that the new encryption key to be used
36 station.
37 C_SIG_ENCRYPT_
39 indicator.
42 as follows:
46 C_SIG_ENCRYPT_
3-200
3GPP2 C.S0005-A v6.0

6

31 station is to use. If the FREQ_INCL bit is set to ‘0’, the base
38 Channel the mobile station is to use. If the FREQ_INCL bit is
39 set to ‘0’, the base station shall omit this field.
3-201
3GPP2 C.S0005-A v6.0
1 NUM_PILOTS - Number of pilots whose Paging Channel may be monitored.

2 The base station shall set this field to the number of pilots
3 whose Paging Channel may be monitored by the mobile
4 station minus one. The base station shall set this field to the
5 value in the range 0 to N8m – 1 inclusive.
6 The base station shall include NUM_PILOTS plus one occurrence of the following field
7 record for each pilot whose Paging Channel may be monitored by the mobile station.
16 base station.
23
25 RESPOND - Respond on analog control channel indicator.
27 Page Response Message on the analog control channel (see [6])
28 after processing this channel assignment, the base station
29 shall set this field to ‘1’. The base station may set this field to
30 ‘0’ only in response to a Page Response Message.
31 ANALOG_SYS - System indicator.
32 If USE_ANALOG_SYS is equal to ‘0’, the base station shall set
34 to ‘0’ if the mobile station is to use analog system A, or to ‘1’ if
35 the mobile station is to use analog system B.
36 USE_ANALOG_SYS - Use analog system indicator.
37 The base station shall set this field to ‘1’ to direct the mobile
38 station to the analog system specified by ANALOG_SYS;

42 in [30].
43
3-202
3GPP2 C.S0005-A v6.0
4 of the analog system supporting the assigned voice channel
5 for this assignment (see [6]).
7 The base station shall set this field to the mobile station
8 power level associated with the assigned voice channel for this
9 assignment (see [6]).
10 ANALOG_CHAN - Voice channel number.
11 The base station shall set this field to the voice channel
12 number for this assignment (see [6]).
14 The base station shall set this field to the supervisory audio
15 tone color code associated with the assigned voice channel. If
16 the assignment is to a narrow analog channel, the base
17 station shall set this field to the two least significant bits of
18 the DSCC.
20 If analog control message encryption is to be enabled on the
21 assigned forward and reverse analog voice channels, the base
36 in [30].
3-203
3GPP2 C.S0005-A v6.0

5 CDMA Channel containing the Forward Traffic Channel(s) the
9 If the FREQ_INCL bit is set to ‘0’, the base station shall omit
11 follows:
12 If FOR_RC is set to a Radio Configuration associated with
13 Spreading Rate 1, the FREQ_INCL bit is set to ‘1’, the base
14 station shall set this field to the CDMA Channel number, in
15 the specified CDMA band class, corresponding to the CDMA
16 frequency assignment for the CDMA Channel containing the
17 Forward Traffic Channel(s) the mobile station is to use. If
18 FOR_RC is set to a Radio Configuration associated with
19 Spreading Rate 3, the base station shall set this field to the
20 center SR3 frequency assignment containing the Forward
21 Traffic Channel(s) the mobile station is to use.
22 BYPASS_ALERT-
32 consisting of the multiplex option and Radio Configuration
34 Reverse Traffic channels, and to indicate that service
35 negotiation may take place before the base station sends the
39 consisting of the default multiplex option that is derived from
40 the radio configuration corresponding to Table 3.7.2.3.2.21-7
41 and transmission rates corresponding to the service option
44 service negotiation may take place before the base station
3-204
3GPP2 C.S0005-A v6.0
3 consisting of the default multiplex option that is derived from
4 the radio configuration corresponding to Table 3.7.2.3.2.21-7
5 and transmission rates corresponding to the service option
8 service negotiation is not to take place before the base station
13 indicate an initial multiplex option and Radio Configuration
14 for the Forward and Reverse Traffic Channels.
15 FOR_RC - Forward Traffic Channel radio configuration.
18 the Forward Traffic (Fundamental and Dedicated Control)
19 Channel before the first Service Connect Message is sent to the
20 mobile station.
24 3.7.2.3.2.21-3).
25 REV_RC - Reverse Traffic Channel radio configuration.
28 the Reverse Traffic (Fundamental and Dedicated Control)
29 Channel before the first Service Connect Message is sent to the
30 mobile station.
34 3.7.2.3.21-3).
45 FPC_SUBCHAN_GAIN - Forward Power Control Subchannel relative gain.
3-205
3GPP2 C.S0005-A v6.0

3 relative to the power level of of 20 ms frames at a 9600 bps or
4 14400 bps rate on the Forward Fundamental Channel or the
5 Forward Dedicated Control Channel that the Forward Power
6 Control Subchannel is punctured on. The base station shall
7 set the value in units of 0.25 dB.
8 RLGAIN_ADJ - Reverse Traffic Channel power relative to access power.
9 The base station shall set this field to adjust the initial Traffic
10 Channel transmission power relative to the Access Channel or
11 Enhanced Access Channel transmission power. The base
12 station shall set this field as a two’s complement signed
13 binary number, in units of 1 dB.
14 NUM_PILOTS - Number of pilots in the Active Set.
15 The base station shall set this field to number of pilots that
16 are to be in the mobile station’s Active Set on the Traffic
17 Channel minus one. The base station shall set this field to
18 the value in the range 0 to N6m-1 inclusive.
19 CH_IND - Channel indicator.

20 The base station shall set this field as shown in Table
21 3.7.2.3.2.21-4.
Value Channels Being Assigned

(Binary)
00 Reserved
01 Fundamental Channel only
10 Dedicated Control Channel only
11 Both Fundamental Channel and Dedicated
Control Channel
23
24 CH_RECORD_LEN - Channel record length.

26 the CH_RECORD_FIELDS included in this channel record.
27 CH_RECORD_FIELDS - Channel record fields.
28 The channel record fields are determined by the value of
29 CH_IND, as described below.
30 REV_FCH-
3-206
3GPP2 C.S0005-A v6.0
2 is allowed to perform the reverse eighth gating mode where
th
3 the 1/8 rate frames on the Reverse Fundamental Channel
4 are gated off for 10 ms per frame (see 2.1.2.3.2 of [2]);
6 The base station shall not set this field to ‘1’ if
7 REV_FCH_GATING_REQ included in the Origination Message
8 or Page Response Message is set to ‘0’.
9 REV_PWR-
17 If the REV_FCH_GATING_MODE field in this message is set to
18 ‘1’ and the REV_PWR_CNTL_INCL field in the Extended
19 System Parameters Message is set to ‘0’, the base station shall
21
22 REV_PWR-
34 D_SIG_ENCRYPT_MODE - Dedicated channelGeneral encryption mode indicator.
37 messageencryption encryption mode, as shown in Table 3.7.4.5-1;
41 include this field. If this field is included, the base station shall
42 set this field to ‘0’ to indicate that the stored encryption key to be
43 used by the mobile station. Otherwise, the base station shall set
44 this field to ‘1’ to indicate that the new encryption key to be used
3-207
3GPP2 C.S0005-A v6.0

12 station.
13 C_SIG_ENCRYPT_
15 indicator.
18 as follows:
22 C_SIG_ENCRYPT_
28
29 3XFL_1XRL_INCL - 3X Forward Link and 1X Reverse Link indicator.

30 The base station shall set this field to ‘1’ if the base station is
31 assigning 3X traffic channel on the Forward Link and 1X
32 traffic channel on the Reverse Link; otherwise, the base
34 1XRL_-
35 FREQ_OFFSET - 1X Reverse Link frequency offset.
36 If 3XFL_1XRL_INCL is set to ‘0’, the base station shall omit
38 follows:
40 Table 3.7.2.3.2.21-5 corresponding to the frequency offset of
41 the 1X reverse link.
3-208
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.21-5. 1X Reverse Link Frequency Offset
1XRL_FREQ_OFFSET 1X Reverse Link
(Binary) frequency offset
00 The Reverse Link is on

the lowest SR3
frequency
the center SR3
frequency
the highest SR3
frequency
11 Reserved

6
7 If the CH_IND field is set to ‘01’, the base station shall include the following fields:

11 FPC_FCH_FER - Fundamental channel target Frame Error Rate.
13 Rate on the Forward Fundamental Channel, as specified in
14 Table 3.7.3.3.2.25-2.


21
22 The base station shall include NUM_PILOTS plus one occurrence of the following record,
23 one for each member of the mobile station’s Active Set on the Traffic Channel.
3-209
3GPP2 C.S0005-A v6.0
1 ADD_PILOT_REC_INCL - Additional pilot information included indicator.

2 The base station shall set this field to ‘1’ if additional pilot
3 information listed in PILOT_REC_TYPE and RECORD_LEN
4 fields are included. The base station shall set this field to ‘0’ if
5 the corresponding pilot is the common pilot and there is no
7 PILOT_REC_TYPE - Pilot record type.
8 If ADD_PILOT_REC_INCL is set to ‘1’, the base station shall
9 set this field to the PILOT_REC_TYPE value shown in Table
13 omit this field.
14
15 Table 3.7.2.3.2.21-6. Pilot Record Types
PILOT_REC_TYPE
1X Common Pilot with Transmit 000

Diversity
1X Auxiliary Pilot 001
1X Auxiliary Pilot with Transmit 010
Diversity
3X Common Pilot 011
All other PILOT_REC_TYPE values are reserved
16

22 omit this field.
28 omit this field.
29
3-210
3GPP2 C.S0005-A v6.0
1 If the Forward Fundamental Traffic Channel associated with

2 this pilot will carry the same closed-loop power control
3 subchannel bits as that of the previous pilot in this message,
5 station shall set this field to ‘0’. For the first occurrence of
6 this record in the message, the base station shall set this field
7 to ‘0’.
8 CODE_CHAN_FCH - Code channel index for the Fundamental Channel.
11 code channel index (see 2.1.3.1.9 and 3.1.3.1.13 of [2]) that
12 the mobile station is to use on the Forward Fundamental
13 Channel associated with this pilot. If FOR_RC is set to a Radio
14 Configuration associated with Spreading Rate 3, the base
15 station shall set this field to the code channel index that the
16 mobile station is to use on the Forward Fundamental on the
17 center SR3 frequency.
18 If Radio Configuration 1, 2, 3, or 5 (see 3.1.3.1.2 of [2]) is
19 used, the base station shall set this field in the range 1 to 63
20 inclusive. If Radio Configuration 4, 6 or 8 is used, the base
24 QOF_MASK_ID_FCH - Quasi-Orthogonal Function Mask Identifier for the
28 quasi-orthogonal function mask identifier (see Table
29 3.1.3.1.12-2 of [2]) that the mobile station is to use on the
30 Forward Fundamental Channel associated with this pilot. If
33 quasi-orthogonal function mask identifier that the mobile
34 station is to use on the Forward Fundamental Channel on the
36 3X_FCH_INFO_INCL – 3X FCH information included indicator.
37 If the 3X Fundamental Channel information is included, the
40 The base station shall include NUM_PILOTS plus one occurrence of the following record if
41 3X_FCH_INFO_INCL is set to ‘1’. The base station shall use the same order for the following
42 fields as is used for the PILOT_PN fields listed in this message.
43 3X_FCH_LOW_INCL – FCH code channel on the lowest SR3 frequency included
44 indicator.
45 If the FCH on the lowest SR3 frequency has a different code
46 channel than the FCH on the center SR3 frequency, the base
3-211
3GPP2 C.S0005-A v6.0
1 QOF_MASK_ID-
2 _FCH_LOW – QOF index for the FCH on the lowest SR3 frequency.
3 If 3X_FCH_LOW_INCL is set to ‘0’, the base station shall omit
5 follows:
6 The base station shall set this field to the index of the Quasi-
7 orthogonal function (see Table 3.1.3.1.12-2 of [2])
8 corresponding to the QOF index for the FCH on the lowest
9 SR3 frequency.
10 CODE_CHAN-
11 _FCH_LOW - Code channel for the FCH on the lowest SR3 frequency.
14 follows:
17 to use on the FCH on the lowest SR3 frequency. If Radio
18 Configuration 6 or 8 is used, the base station shall set this
19 field in the range 1 to 127 inclusive. If Radio Configuration 7
20 or 9 is used, the base station shall set this field in the range 1
21 to 255 inclusive.
22 3X_FCH_HIGH_INCL – FCH code channel on the highest SR3 frequency included
23 indicator.
24 If the FCH on the highest SR3 frequency has a different code
28 QOF_MASK_ID-
29 _FCH_HIGH – QOF index for the FCH on the highest SR3 frequency.
30 If 3X_FCH_HIGH_INCL is set to ‘0’, the base station shall omit
32 follows:
34 orthogonal function (see Table 3.1.3.1.12-2 of [2]
35 corresponding to the QOF index for the FCH on the highest
36 SR3 frequency.
37 CODE_CHAN-
38 _FCH_HIGH – Code channel for the FCH on the highest SR3 frequency.
41 follows:
3-212
3GPP2 C.S0005-A v6.0
3 to use on the FCH on the highest SR3 frequency. If Radio
7 to 255 inclusive.
11 CH_RECORD_LEN field through this RESERVED field equal to
12 an integer number of octets. The base station shall set these
13 bits to ‘0’.
15 FPC_DCCH_INIT_SETPT - Initial Dedicated Control Channel outer loop Eb/Nt setpoint.
16 The base station shall set this field to initial Dedicated Control
18 FPC_DCCH_FER - Dedicated Control Channel target Frame Error Rate.

20 Rate on the Dedicated Control Channel, as specified in Table
21 3.7.3.3.2.25-2.
22 FPC_ DCCH_MIN_SETPT - Minimum Dedicated Control Channel Outer Loop Eb/Nt
23 setpoint.
24 The base station shall set this field to minimum Dedicated
25 Control Channel Outer Loop Eb/Nt setpoint, in units of 0.125
26 dB.
27 FPC_ DCCH_MAX_SETPT - Maximum Dedicated Control Channel Outer Loop Eb/Nt
28 setpoint.
29 The base station shall set this field to maximum Dedicated
31 dB.
33 record for each member of the mobile station’s Active Set on the Traffic Channel.
3-213
3GPP2 C.S0005-A v6.0

6 omit this field.
12 omit this field.
16 this pilot record.
18 omit this field as described in 3.7.6.1.
19
20

22 If the Forward Dedicated Control Traffic Channel associated
23 with this pilot will carry the same closed-loop power control
28 to ‘0’.
29 CODE_CHAN_DCCH - Code channel index for the Dedicated Control Channel.
33 the mobile station is to use on the Forward Dedicated Control
34 Channel associated with this pilot. If FOR_RC is set to a Radio
37 mobile station is to use on the Forward Dedicated Control
38 Channel on the center SR3 frequency.
45 QOF_MASK_ID_DCCH - Quasi-Orthogonal Function Mask Identifier for the Dedicated
46 Control Channel.
3-214
3GPP2 C.S0005-A v6.0

5 Forward Dedicated Control Channel associated with this pilot.
10 Forward Dedicated Control Channel on the center SR3
11 frequency.
12 3X_DCCH_INFO_INCL – 3X DCCH information included indicator.
13 If the 3X Dedicated Control Channel information is included,
17 3X_DCCH_INFO_INCL is set to ‘1’. The base station shall use the same order for the
18 following fields as is used for the PILOT_PN fields listed in this message.
19 3X_DCCH_LOW_INCL – DCCH code channel on the lowest SR3 frequency included
20 indicator.
21 If the DCCH on the lowest SR3 frequencies has a different
22 code channel than the DCCH on the center SR3 frequency,
25 QOF_MASK_ID-
26 _DCCH_LOW – QOF index for the DCCH on the lowest SR3 frequency.
27 If 3X_DCCH_LOW_INCL is set to ‘0’, the base station shall
28 omit this field; otherwise, the base station shall set this field
29 as follows:
32 corresponding to the QOF index for the DCCH on the lowest
33 SR3 frequency.
34 CODE_CHAN-
35 _DCCH_LOW - Code channel for the DCCH on the lowest SR3 frequency.
38 as follows:
41 to use on the DCCH on the lowest SR3 frequency. If Radio
46 3X_DCCH_HIGH_INCL – DCCH code channel on the highest SR3 frequency included
47 indicator.
3-215
3GPP2 C.S0005-A v6.0
1 If the DCCH on the highest SR3 frequencies has a different

5 QOF_MASK_ID-
6 _DCCH_HIGH – QOF index for the DCCH on the highest SR3 frequency.
7 If 3X_DCCH_HIGH_INCL is set to ‘0’, the base station shall
9 as follows:
12 corresponding to the QOF index for the DCCH on the highest
13 SR3 frequency.
14 CODE_CHAN-
15 _DCCH_HIGH – Code channel for the DCCH on the highest SR3 frequency.
18 as follows:
21 to use on the DCCH on the highest SR3 frequency. If Radio
31 bits to ‘0’.
32
37 FPC_DCCH_INIT_SETPT - Initial Dedicated Control Channel outer loop Eb/Nt setpoint.
38 The base station shall set this field to initial Dedicated Control
40 FPC_PRI_CHAN - Power Control Subchannel indicator.
3-216
3GPP2 C.S0005-A v6.0
2 is to perform the primary inner loop estimation on the
3 received Forward Fundamental Channel and the base station
4 is to multiplex the Power Control Subchannel on the Forward
5 Fundamental Channel. The base station shall set this field to
6 ‘1’ if the mobile station is to perform the primary inner loop
7 estimation on the received Forward Dedicated Control
8 Channel and the base station is to multiplex the Power
9 Control Subchannel on the Forward Dedicated Control
10 Channel.
13 Rate on the Forward Fundamental Channel.
22 Rate on the Dedicated Control Channel.
23 FPC_ DCCH_MIN_SETPT - Minimum Dedicated Control Channel Outer Loop Eb/Nt
24 setpoint.
25 The base station shall set this field to minimum Dedicated
27 dB.
28 FPC_ DCCH-
29 _MAX_SETPT - Maximum Dedicated Control Channel Outer Loop Eb/Nt
30 setpoint.
31 The base station shall set this field to maximum Dedicated

33 dB.
35 record, one for each member of the mobile station’s Active Set on the Traffic Channel.
3-217
3GPP2 C.S0005-A v6.0
12 omit this field.
18 omit this field.
24 omit this field.
25

27 If the Forward Fundamental Traffic Channel associated with
28 this pilot will carry the same closed-loop power control
33 to ‘0’.
34 CODE_CHAN_FCH - Code channel index for the Fundamental Channel.
38 the mobile station is to use on the Forward Channel
39 associated with this pilot. If FOR_RC is set to a Radio
42 mobile station is to use on the Forward Channel on the center
43 SR3 frequency.
3-218
3GPP2 C.S0005-A v6.0

7 QOF_MASK_ID_FCH - Quasi-Orthogonal Function Mask Identifier for the
13 Forward Fundamental Channel associated with this pilot. If
17 station is to use on the Forward Fundamental Channel on the
19 CODE_CHAN_DCCH - Code channel index for the Dedicated Control channel.
22 code channel index (see 2.1.3.1.9 and 3.1.3.1.13 of [2]), in the
23 range of 1 to 255 inclusive, that the mobile station is to use
24 on the Dedicated Control Channel associated with this pilot. If
27 code channel index in the range of 1 to 255 inclusive, that the
28 mobile station is to use on the Dedicated Control Channel on
29 the center SR3 frequency.
36 QOF_MASK_ID_DCCH - Quasi-Orthogonal Function Mask Identifier for the Dedicated
37 Control Channel.
42 Forward Dedicated Control Channel associated with this pilot.
46 station is to use on the Forward Dedicated Control Channel
47 on the center SR3 frequency.
3-219
3GPP2 C.S0005-A v6.0

8 indicator.
9 If the FCH on the lowest SR3 frequencies has a different code
13 QOF_MASK_ID-
17 follows:
21 SR3 frequency.
22 CODE_CHAN-
26 follows:
35 indicator.
36 If the FCH on the highest SR3 frequencies has a different code
40 QOF_MASK_ID-
44 follows:
3-220
3GPP2 C.S0005-A v6.0
4 SR3 frequency.
5 CODE_CHAN-
9 follows:
25 indicator.
30 QOF_MASK_ID-
34 as follows:
38 SR3 frequency.
39 CODE_CHAN-
43 as follows:
3-221
3GPP2 C.S0005-A v6.0
7 to 255 inclusive.
9 indicator.
14 QOF_MASK_ID-
18 as follows:
22 SR3 frequency.
23 CODE_CHAN-
27 as follows:
40 bits to ‘0’.
3-222
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.22 General Neighbor List Message
2 MSG_TAG: GNLM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
PILOT_INC 4
NGHBR_SRCH_MODE 2
NGHBR_CONFIG_PN_INCL 1
FREQ_FIELDS_INCL 1
USE_TIMING 1
GLOBAL_TIMING_INCL 0 or 1
GLOBAL_TX_DURATION 0 or 4
GLOBAL_TX_PERIOD 0 or 7
NUM_NGHBR 6
NUM_NGHBR occurrences of the following record:
NGHBR_CONFIG 0 or 3
NGHBR_PN 0 or 9
SEARCH_PRIORITY 0 or 2
SRCH_WIN_NGHBR 0 or 4
FREQ_INCL 0 or 1
NGHBR_BAND 0 or 5
NGHBR_FREQ 0 or 11
TIMING_INCL 0 or 1
NGHBR_TX_OFFSET 0 or 7
NGHBR_TX_DURATION 0 or 4
NGHBR_TX_PERIOD 0 or 7
3-223
3GPP2 C.S0005-A v6.0
Field Length (bits)
NUM_ANALOG_NGHBR 3
NUM_ANALOG_NGHBR occurrences of the following record:
BAND_CLASS 5
SYS_A_B 2
SRCH_OFFSET_INCL 1
NGHBR_PILOT_REC_TYPE 0 or 3
RECORD_LEN 0 or 3
SRCH_OFFSET_NGHBR 0 or 3
BCCH_IND_INCL 1
NUM_NGHBR occurrences of the following field:
BCCH_SUPPORT 0 or 1

8 (see 3.6.2.2).
19 15 inclusive.
20 NGHBR_SRCH_MODE - Search mode.
3-224
3GPP2 C.S0005-A v6.0
2 Table 3.7.2.3.2.22-1 corresponding to the search mode.
4 Table 3.7.2.3.2.22-1. Search Mode Field
Value
00 No search priorities or search windows

01 Search priorities
10 Search windows
11 Search windows and search priorities
6 NGHBR_CONFIG-
7 _PN_INCL - Neighbor configuration and PN offset included.
8 If neighbor configuration and PN offset fields are included in
9 this message, the base station shall set this field to ‘1’;
11 FREQ_FIELDS_INCL - Frequency fields included.
12 If frequency fields are included in this message, the base
15 USE_TIMING - Use timing indicator.
16 If base station timing information is included for neighbor
17 base stations, the base station shall set this field to ‘1’;
19 GLOBAL_TIMING-
20 _INCL - Global timing included.
21 If USE_TIMING is set to ‘1’, the base station shall include the
22 field GLOBAL_TIMING_INCL and set this field as described
23 below; otherwise, the base station shall omit this field.
24 If base station timing information is included globally for all
25 neighbor base stations with TIMING_INCL equal to ‘1’, the
28 GLOBAL_TX-
29 _DURATION - Global neighbor transmit time duration.
30 If GLOBAL_TIMING_INCL is included and is set to ‘1’, the base
31 station shall include the field GLOBAL_TX_DURATION and
32 shall set this field as described below; otherwise, the base
3-225
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the duration of the base
2 station transmit window, during each period, in units of 80
3 ms. The base station should set this field to a value of 3 or
4 greater.
5 GLOBAL_TX-
6 _PERIOD - Global neighbor transmit time period.
8 station shall include the field GLOBAL_TX_PERIOD and shall
9 set this field as described below; otherwise, the base station
11 The base station shall set this field to duration of the period,
12 in units of 80 ms.
13 NUM_NGHBR - Number of neighbor pilot PN sequences.
15 neighbors included in the message.
16
18 mobile station is to place in its Neighbor Set. The base station shall use the same order for
19 the following record in this message as is used for pilots which are listed in the Neighbor
20 List Message or Extended Neighbor List Message. Specifically, the ith occurrence of the
21 following record shall correspond the ith pilot in the Neighbor List Message or in the
22 Extended Neighbor List Message.
23

25 If NGHBR_CONFIG_PN_INCL = ‘1’, the base station shall set
26 this field to the value shown in Table 3.7.2.3.2.22-2
27 corresponding to the configuration of this neighbor; otherwise,
29
3-226
3GPP2 C.S0005-A v6.0
Value

to this current CDMA frequency assignment with the same number of Paging



station.

to this current CDMA frequency assignment but possibly with a different
number of Paging Channels, and the neighbor CDMA frequency is given as
follows:



station.

3-227
3GPP2 C.S0005-A v6.0
The neighbor base station has a Primary Paging Channel on the following
CDMA frequency:
Primary Paging Channel on the first CDMA Channel listed in the CDMA
transmitted by the current base station.
Primary Paging Channel on the CDMA frequency assignment given by
NGHBR_BAND and NGHBR_FREQ.
Channel.
100-111 Reserved.

3 If NGHBR_CONFIG_PN_INCL = ‘1’, the base station shall set
4 this field to the pilot PN sequence offset for this neighbor, in
5 units of 64 PN chips; otherwise, the base station shall omit
6 this field.
8 If NGHBR_SRCH_MODE = ‘01’ or NGHBR_SRCH_MODE = ‘11’,
9 then the base station shall set this field to the search priority
10 for the Pilot Channel corresponding to NGHBR_PN. The base
12 3.7.2.3.2.22-3. If NGHBR_SRCH_MODE is set to any other
13 value, the base station shall omit this field.
14
3-228
3GPP2 C.S0005-A v6.0
Value Search Priority

(binary)
00 Low
01 Medium
10 High
11 Very High
3 SRCH_WIN_NGHBR - Neighbor pilot channel search window size.

4 If NGHBR_SRCH_MODE = ‘10’ or ‘11’, then the base station
5 shall set this field to the value shown in Table 2.6.6.2.1-1
6 corresponding to the search window size to be used by mobile
7 stations for this neighbor. If NGHBR_SRCH_MODE is set to
8 any other value, the base station shall omit this field.
10 If FREQ_FIELDS_INCL is set to ‘0’, the base station shall omit
12 follows:
16 not included in this assignment record, the base station shall
17 set this bit to ‘0’.
19 If the FREQ_INCL bit is included and is set to ‘1’, the base
20 station shall set this field to the CDMA band class, as
21 specified in [30], corresponding to the CDMA frequency
23 Channel the mobile station is to search. If the FREQ_INCL bit
24 is omitted or is set to ‘0’, the base station shall omit this field.
26 If the FREQ_INCL bit is omitted or is set to ‘0’, the base
28 If the FREQ_INCL bit is included and is set to ‘1’ and the
29 corresponding neighbor has a 1X neighbor pilot record type,
30 the base station shall set this field to the CDMA Channel
31 number, in the specified CDMA band class, corresponding to
32 the CDMA frequency assignment for the CDMA Channel
33 containing the Paging Channel the mobile station is to search.
3-229
3GPP2 C.S0005-A v6.0
1 If the FREQ_INCL bit is included and is set to ‘1’ and the

5 the center SR3 frequency assignment containing the Paging
6 Channel the mobile station is to search.
7 TIMING_INCL - Timing included indicator.
9 field TIMING_INCL and set this field as described below;
11 If base station timing information is included for this neighbor
12 base station, the base station shall set this field to ‘1’;
14 NGHBR_TX_OFFSET - Neighbor transmit time offset.
15 If TIMING_INCL is included and is set to ‘1’, the base station
16 shall include the field NGHBR_TX_OFFSET and set this field
17 as described below; otherwise, the base station shall omit this
18 field.
19 The base station shall set this field to the time offset, in units
20 of 80 ms, from the beginning of the neighbor timing period to
21 the beginning of the first base station transmit window within
22 the period. The beginning of the neighbor timing period
23 occurs when t/4 mod (16384)= 0.
24 NGHBR_TX_DURATION - Neighbor transmit time duration.
25 If TIMING_INCL is included and is set to ‘1’ and
26 GLOBAL_TIMING_INCL is set to ‘0’, the base station shall
27 include the field NGHBR_TX_DURATION and set this field as
28 described below; otherwise, the base station shall omit this
29 field.
30 The base station shall set this field to duration of the base
31 station transmit window, during each period, in units of
32 80 ms. The base station should set this field to a value of 3 or
33 greater.
34 NGHBR_TX_PERIOD - Neighbor transmit time period.
37 include the field NGHBR_TX_PERIOD and set this field as
39 field.
42 NUM_ANALOG_NGHBR - Number of neighboring analog systems.
44 neighboring analog systems included in the message.
45
3-230
3GPP2 C.S0005-A v6.0
1 The base station shall include one occurrence of the following record for each neighboring
2 analog system included in the message:

6 SYS_A_B - System A/B.
7 If BAND_CLASS is set to ‘00000’ or to ‘00011’, the base station
8 shall set this field to the value shown in Table 3.7.2.3.2.22-4
9 corresponding to the availability of neighboring analog
10 systems; otherwise, the base station shall set this field to ‘00’.
11 Table 3.7.2.3.2.22-4. Cellular System A/B
Cellular System A/B Value
RESERVED 00
System A 01
System B 10
System A and B 11
12
13 SRCH_OFFSET_INCL - Neighbor pilot channel search window offset included.

14 If NGHBR_SRCH_MODE = ‘10’ or ‘11’ and if the
15 SRCH_OFFSET_NGHBR field is included in the following
16 records, the base station shall set this bit to ‘1’; otherwise, the
17 base station shall set this bit to ‘0’.
20 the following record in this message as is used for pilots which are listed in the Neighbor
21 List Message or Extended Neighbor List Message. Specifically, the ith occurrence of the
22 following record shall correspond the ith pilot in the Neighbor List Message or in the
23 Extended Neighbor List Message.
26 information listed in the NGHBR_PILOT_REC_TYPE and
27 RECORD_LEN fields are included. The base station shall set
28 this field to ‘0’ if the corresponding pilot is the common pilot
29 and there is no additional pilot information included.
30 NGHBR_PILOT_REC_TYPE - Neighbor Pilot record type
32 set this field to the NGHBR_PILOT_REC_TYPE value shown in
35
3-231
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.22-5. Neighbor Pilot Record Types
NGHBR_PILOT_REC_TYPE

Diversity
Diversity
3X Common Pilot 011
All other NGHBR_PILOT_REC_TYPE values are reserved

4 omit this field.
10 omit this field.
14 NGHBR_PILOT_REC_TYPE of this pilot record.
16 omit this field.
17
18 If NGHBR_PILOT_REC_TYPE is equal to ‘000’, the base station shall include the following
19 fields:
20
Field Length (bits)
TD_POWER_LEVEL 2
TD_MODE 2
RESERVED 4
21
22 TD_POWER_LEVEL - TD Transmit Power Level.
3-232
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the TD transmit power
2 level relative to that of the Forward Pilot Channel as specified
3 in Table 3.7.2.3.2.26-4.
4 TD_MODE - Transmit Diversity mode.
5 The base station shall set this field to the Transmit Diversity
6 mode, as specified in Table 3.7.2.3.2.26-3.
10 fields:
Field Length (bits)
QOF 2
WALSH_LENGTH 3
AUX_PILOT_WALSH WALSH_LENGTH+6
11

14 orthogonal function (see Table 3.1.3.1.12-2 of [2].
15 WALSH_LENGTH - Length of the Walsh Code.
16 The base station shall set this field to the WALSH_LENGTH
17 value shown in Table 3.7.2.3.2.22–6 corresponding to the
18 length of the Walsh code for the pilot that is used in as the
19 Auxiliary pilot.
20 Table 3.7.2.3.2.22-6. Walsh Code Length
WALSH_LENGTH Length of the Walsh

(binary) Code
‘000’ 64
‘001’ 128
‘010’ 256
‘011’ 512
‘100’ – ‘111’ Reserved
21
22 AUX_PILOT_WALSH - Walsh Code for the Auxiliary Pilot.

23 The base station shall set this field to the Walsh code
24 corresponding to the Auxiliary pilot.
3-233
3GPP2 C.S0005-A v6.0
4 fields:
Field Length (bits)
QOF 2
WALSH_LENGTH 3
AUX_WALSH WALSH_LENGTH+6
AUX_TD_POWER_LEVEL 2
TD_MODE 2
7 QOF - Quasi-orthogonal function index for the Auxiliary Transmit

8 Diversity Pilot.
13 value shown in 3.7.2.3.2.22-6 corresponding to the length of
14 the Walsh code for the pilots that are used as Auxiliary pilot
15 in the transmit diversity mode.
16 AUX_WALSH - Walsh Code for the Auxiliary Pilot.
19 AUX_ TD-
20 _POWER_LEVEL - Auxiliary Transmit Diversity Pilot Power Level.
21 The base station shall set this field to the Auxiliary Transmit
22 Diversity Pilot transmit power level relative to that of the
23 Auxiliary Pilot as specified in Table 3.7.2.3.2.22-7.
3-234
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.22-7. Auxiliary Transmit Diversity Pilot

2 Transmit Power Level
AUX_TD_POWER_LEVEL Transmit Power Level
00 9 dB below the Auxiliary Pilot

Channel transmit power
11 Same as the Auxiliary Pilot

10 fields:
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
11
12 SR3_PRIMARY_PILOT – Primary SR3 pilot.

14 Table 3.7.2.3.2.26-5 corresponding to the position of the
15 primary SR3 pilot.
16 SR3_PILOT_POWER1 – The primary SR3 pilot power level relative to that of the pilot
17 on the lower frequency of the two remaining SR3 frequencies.
19 Table 3.7.2.3.2.26-6 corresponding to the power level of the
20 primary pilot with respect to the pilot on the lower frequency
21 of the two remaining SR3 frequencies.
23 on the higher frequency of the two remaining SR3 frequencies.
26 primary pilot with respect to the pilot on the higher frequency
3-235
3GPP2 C.S0005-A v6.0

5 fields:
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
QOF 2
WALSH_LENGTH 3
ADD_INFO_INCL1 1
QOF1 0 or 2
WALSH_LENGTH1 0 or 3
AUX_PILOT_WALSH1 0 or
WALSH_LENGTH1+6
ADD_INFO_INCL2 1
QOF2 0 or 2
WALSH_LENGTH2+6

3-236
3GPP2 C.S0005-A v6.0

3 orthogonal function (see Table 3.1.3.1.12-2 of [2] on the
4 frequency of the primary pilot.
9 Auxiliary pilot on the frequency of the primary pilot.
12 corresponding to the Auxiliary pilot on the frequency of the
13 primary pilot.
14 ADD_INFO_INCL1 - Additional information included for the pilot on the lower
15 frequency of the two remaining SR3 frequencies.
16 If the additional information for the pilot on the lower
17 frequencies of the two remaining SR3 frequencies is the same
18 as pilot on the primary frequency, the base station shall set
20 to ‘1’.
21 QOF1 - Quasi-orthogonal function index for the pilot on the lower
23 If ADD_INFO_INCL1 is set to ‘0’, the base station shall omit
25 follows:
27 orthogonal function (see Table 3.1.3.1.12-2 of [2]) on the lower
29 WALSH_LENGTH1 - Length of the Walsh Code for the pilot on the lower frequency
33 follows:
37 Auxiliary pilot on the lower frequency of the two remaining
38 SR3 frequencies.
39 AUX_PILOT_WALSH1 - Walsh Code for the Auxiliary Pilot on the lower frequency of
40 the two remaining SR3 frequencies.
43 follows:
45 corresponding to the Auxiliary pilot on the lower frequency of
3-237
3GPP2 C.S0005-A v6.0
1 ADD_INFO_INCL2 - Additional information included for the pilot on the higher

3 If the additional information for the pilot on the higher
7 to ‘1’.
8 QOF2 - Quasi-orthogonal function index for the pilot on the higher
12 follows:
14 orthogonal function (see Table 3.1.3.1.12-2 of [2]) on the
16 WALSH_LENGTH2 - Length of the Walsh Code for the pilot on the higher frequency
20 follows:
24 Auxiliary pilot on the higher frequency of the two remaining
25 SR3 frequencies.
26 AUX_PILOT_WALSH2 - Walsh Code for the Auxiliary Pilot on the higher frequency of
30 follows:
32 corresponding to the Auxiliary pilot on the higher frequency of
37 SRCH_OFFSET_NGHBR - Neighbor pilot channel search window size offset.
38 If SRCH_OFFSET_INCL equals to ‘1’, then the base station
40 corresponding to the search window offset to be used by
41 mobile stations for this neighbor; otherwise, the base station
43 BCCH_IND_INCL - BCCH support included indicator.
44 If the BCCH_SUPPORT field is included in the following
45 records, the base station shall set this field to ‘1’; otherwise,
3-238
3GPP2 C.S0005-A v6.0
1 If BCCH_IND_INCL is set to ‘1’, the base station shall include one occurrence of the
2 following field for each pilot that a mobile station is to place in its Neighbor Set. The base
3 station shall use the same order for the following record in this message as is used for
4 pilots which are listed in the Neighbor List Message or Extended Neighbor List Message.
5 Specifically, the ith occurrence of the following record shall correspond the ith pilot in the
6 Neighbor List Message or in the Extended Neighbor List Message.
7 BCCH_SUPPORT - BCCH support indicator.
8 If this neighbor base station supports Broadcast Control
11
3-239
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.23 User Zone Identification Message
2 MSG_TAG: UZIM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
UZ_EXIT 4
NUM_UZID 4
NUM_UZID occurrences of the following record:
UZID 16
UZ_REV 4
TEMP_SUB 1

9 (see 3.6.2.2).
10 UZ_EXIT - User Zone Exit parameter.
11 The base station shall set this field to the User Zone exit
12 parameter (see 2.6.9.2.1). The base station shall set this field
13 to a value (in dB) in the range 0 to 15.
14 NUM_UZID - Number of User Zone identifiers.
15 The base station shall set this field to the number of user zone
16 identifiers included in this message.
17 The base station shall include NUM_UZID occurrences of the following record.
18 UZID - User Zone identifier.
19 The base station shall set this field to the User Zone identifier
20 (see 3.6.7) supported by the base station.
21 UZ_REV - User Zone update revision number.
22 The base station shall set this field to the User Zone update
23 revision number.
24 TEMP_SUB - Temporary subscription flag.
25 If the corresponding User Zone allows for temporary
26 subscription, the base station shall set this field to ‘1’;
3-240
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.24 Private Neighbor List Message
2 MSG_TAG: PNLM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
NUM_RADIO_INTERFACE 4
NUM_RADIO_INTERFACE occurrences of the following

record:
RADIO_INTERFACE_TYPE 4
RADIO_INTERFACE_LEN 8
Radio Interface Type-specific fields 8×
RADIO_INTERFACE_L
EN

9 (see 3.6.2.2).
10 NUM_RADIO-
11 _INTERFACE - Number of interface types.
12 The base station shall set this field to the number of radio
13 interface types for which private neighbors are included in
14 this message.
15 The base station shall include NUM_RADIO_INTERFACE occurrences of the following
16 record, one occurrence for each radio interface for which private neighbors are included in
17 this message.
18 RADIO-
19 _INTERFACE_TYPE - The radio interface type.
20 The base station shall set this field to the radio interface type
21 of this record as specified in Table 3.7.2.3.2.24-1.
3-241
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.24-1. Radio Interface Type
RAIO_INTERAFCE_TYPE Descriptions
(binary)
0000 MC system
0001-1111 Reserved
2 RADIO-
3 _INTERFACE_LEN - The length of the Radio Interface Type-specific fields.
5 the Radio Interface Type-specific fields of this record.
6 If RADIO_INTERFACE_TYPE is equal to ‘0000’, the base station shall set the radio interface
7 type-specific fields as followsinclude the following fields:
3-242
3GPP2 C.S0005-A v6.0
Field Length (bits)

COMMON_INCL 1
COMMON_BAND_CLASS 0 or 5
COMMON_NGHBR_FREQ 0 or 11
SRCH_WIN_PN 4
NUM_PRI_NGHBR 6
NUM_PRI_NGHBR occurrences of the following record:

SID 15
NID 16
PRI_NGHBR_PN 9
RECORD_LEN 0 or 3
Type-specific fields 0 or 8× RECORD_LEN
BAND_CLASS 0 or 5
NGHBR_FREQ 0 or 11
UZID_INCL 1
NUM_UZID 0 or 4
If UZID_INCL = 1, NUM_UZID occurrences of the following

subrecord; otherwise, no occurrence of the following
subrecord:
UZID 0 or 16
UZ_REV 0 or 4
TEMP_SUB 0 or 1
3 COMMON_INCL - Common configuration included indicator.

4 If all private neighbor base stations included in this message
5 are on the same CDMA band class and CDMA Channel
6 number as specified in the COMMON_BAND_CLASS and
7 COMMON_NGHBR_FREQ fields, the base station shall set this
9 COMMON_BAND_CLASS - Neighbor band class.
3-243
3GPP2 C.S0005-A v6.0
1 If COMMON_INCL is set to ‘1’, the base station shall set this

2 field to the CDMA band class as specified in [30] in Table
3 3.7.2.3.2.8-3 corresponding to the CDMA frequency
5 Channel or the Forward Common Control Channel for all
6 private neighbors; otherwise, the base station shall omit this
7 field.
8 COMMON_NGHBR_FREQ - Neighbor frequency assignment.
9 If the COMMON_INCL bit is set to ‘1’, the base station shall
10 set this field to the CDMA Channel number, in the specified
13 Channel or the Forward Common Control Channel for all
14 private neighbor base station; otherwise, the base station
16 SRCH_WIN_N - Search window size for the Private Neighbor Set.
19 be used by mobile stations for the Private Neighbor Set.
20 NUM_PRI_NGHBR - Number of private neighbor pilot PN sequences.
21 The base station shall set this field to the number of private
23
24 The base station shall include NUM_PRI_NGHBR occurrences of the following record.
25 SID - System Identification.
27 number for this private neighbor system (see 2.6.5.2).
28 NID - Network Identification.
32 number for this private neighbor network (see 2.6.5.2).
33 PRI_NGHBR_PN - Private neighbor pilot PN sequence offset index.
35 offset for this private neighbor, in units of 64 PN chips.
3-244
3GPP2 C.S0005-A v6.0

6 omit this field.
12 omit this field.
18 omit this field.
20 fields:
21
Field Length (bits)
TD_POWER_LEVEL 2
TD_MODE 2
RESERVED 4
22

26 in Table 3.7.2.3.2.26-4.
33 fields:
3-245
3GPP2 C.S0005-A v6.0
Field Length (bits)
QOF 2
WALSH_LENGTH 3

4 orthogonal function (see Table 3.1.3.1.12-2 of [2]).
9 Auxiliary pilot.
17 fields:
18
Field Length (bits)
QOF 2
WALSH_LENGTH 3
TD_MODE 2
19

21 Diversity Pilot.
3-246
3GPP2 C.S0005-A v6.0

8 AUX_ TD-
20 fields:
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
21

3-247
3GPP2 C.S0005-A v6.0
4 fields:
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
QOF 2
WALSH_LENGTH 3
ADD_INFO_INCL1 1
QOF1 0 or 2
WALSH_LENGTH1+6
ADD_INFO_INCL2 1
QOF2 0 or 2
WALSH_LENGTH2+6

3-248
3GPP2 C.S0005-A v6.0
12 primary pilot.
19 to ‘1’.
24 follows:
32 follows:
37 SR3 frequencies.
42 follows:
3-249
3GPP2 C.S0005-A v6.0

7 to ‘1’.
12 follows:
20 follows:
25 SR3 frequencies.
30 follows:
37 BAND_CLASS - Neighbor band class.
38 If COMMON_INCL is set to ‘0’, the base station shall set this
39 field to the CDMA band class as specified in [30] in Table
40 3.7.2.3.2.8-3 corresponding to the CDMA frequency
42 Channel for the private neighbor; otherwise, the base station
3-250
3GPP2 C.S0005-A v6.0
1 If the COMMON_INCL bit is set to ‘0’, the base station shall

2 set this field to the CDMA Channel number, in the specified
5 Channel for the private neighbor base station; otherwise, the
7 UZID_INCL - User Zone identifier included indicator.
8 If the UZID information is included, the base station shall set
10 to ‘0’.
11 NUM_UZID - Number of User Zone identifiers.
12 If UZID_INCL is set to ‘1’, the base station shall set this field
13 to the number of occurrences of UZID supported by the
14 private neighbor base station; otherwise, the base station
16 If UZID_INCL is set to ‘1’, the base station shall include NUM_UZID occurrences of the
17 following three-field subrecord; otherwise, the base station shall omit this subrecord.
18 UZID - User Zone identifiers.
20 supported by the private neighbor base station.
21 UZ_REV - User Zone update revision number.
22 The base station shall set this field to the User Zone update
23 revision number.
24 TEMP_SUB - Temporary subscription flag.
25 If the corresponding User Zone allows for temporary
26 subscription, the base station shall set this field to ‘1’;

30 make the length of the entire record equal to an integer
31 number of octets. The base station shall set these bits to ‘0’.
32
3-251
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.25 Reserved
3-252
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.26 Sync Channel Message
2 MSG_TAG: SCHM
Field Length (bits)
P_REV 8
MIN_P_REV 8
SID 15
NID 16
PILOT_PN 9
LC_STATE 42
SYS_TIME 36
LP_SEC 8
LTM_OFF 6
DAYLT 1
PRAT 2
CDMA_FREQ 11
EXT_CDMA_FREQ 11
SR1_BCCH_NON_TD_INCL 1
BCCH_SUPPORTED
SR1 SR1_NON_TD_FREQ_INCL 0 or 1
SR1_CDMA_FREQ_NON_TD 0 or 11
SR1_BRAT_NON_TD 0 or 2
SR1_CRAT_NON_TD 0 or 1
SR1_BCCH_CODE_CHAN_NON_TD 0 or 6
SR1_TD_INCL 0 or 1
SR1_CDMA_FREQ_TD 0 or 11
SR1_BRAT_TD 0 or 2
SR1_CRAT_TD 0 or 1
SR1_BCCH_CODE_CHAN_TD 0 or 6
3-253
3GPP2 C.S0005-A v6.0
Field Length (bits)
SR1_TD_MODE 0 or 2
SR1_TD_POWER_LEVEL 0 or 2
SR3_INCL 1
SR3_CENTER_FREQ_INCL 0 or 1
SR3_CENTER_FREQ 0 or 11
SR3_BRAT 0 or 2
SR3_BCCH_CODE_CHAN 0 or 7
SR3_PRIMARY_PILOT 0 or 2
SR3_PILOT_POWER1 0 or 3
DS_INCL 1
DS_BLOB 0 or 24

5 The base station sets this field to prevent mobile stations
7 the system.
17 Class 7, Band Class 8, or Band Class 9, or Band_Class 10
18 operation, the base station should set this field to ‘00000110’
19 or greater.
3-254
3GPP2 C.S0005-A v6.0

4 LC_STATE - Long code state.
5 The base station shall set this field to the long code state at
6 the time given by the SYS_TIME field of this message.
7 SYS_TIME - System time.
8 The base station shall set this field to the System Time as of
9 four Sync Channel superframes (320 ms) after the end of the
10 last superframe containing any part of this Sync Channel
11 Message, minus the pilot PN sequence offset, in units of 80
12 ms (see 1.3 of [2]).
13 LP_SEC - The number of leap seconds that have occurred since the start
14 of System Time.
15 The base station shall set this field to the number of leap
16 seconds that have occurred since the start of System Time, as
17 of the time given by the SYS_TIME field of this message.
18 LTM_OFF - Offset of local time from System Time.
19 The base station shall set this field to the two’s complement
20 offset of local time from System Time, in units of 30 minutes.
21 The local time of day, in units of 80 ms, as of four Sync
22 Channel superframes (320 ms) after the end of the last
23 superframe containing any part of this Sync Channel Message,
24 minus the pilot PN sequence offset, is equal to SYS_TIME -
25 (LP_SEC × 12.5) + (LTM_OFF × 22500).
26 DAYLT - Daylight savings time indicator.
27 If daylight savings time is in effect, the base station shall set
29 to ‘0’.
30 PRAT - Paging Channel data rate.
31 The base station shall set this field to the PRAT field value
32 shown in Table 3.7.2.3.2.26-1 corresponding to the data rate
33 used by the Paging Channels in the system.
34 Table 3.7.2.3.2.26-1. Paging Channel Data Rate
PRAT Field (binary) Paging Channel data rate
00 9600 bps
01 4800 bps
10 Reserved
11 Reserved
35
3-255
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the CDMA Channel
2 number corresponding to the CDMA frequency assignment for
3 the CDMA Channel containing a Primary Paging Channel.5
4 EXT_CDMA_FREQ - Extended frequency assignment.
7 the CDMA Channel containing a Primary Paging Channel that
8 a mobile station capable of Radio Configurations greater than
9 2 or capable of supporting Quick Paging Channel will use.
10 SR1_BCCH_NON_TD_INCLSUPPORTED - Common Channel in non TD mode on
11 Spreading Rate 1 supported information included indicator.
13 supports includes common channels (BCCH/F-CCCH/EACH)
14 information in non TD mode; otherwise, the base station shall
16 SR1_NON_TD-
17 _FREQ_INCL - Non Transmit Diversity frequency included indicator.
18 If SR1_BCCH_NON_TD_INCLSUPPORTED is set to ‘0’, the
19 base station shall omit this field; otherwise, the base station
22 SR1_CDMA_FREQ_NON_TD is included in the message. The
23 base station shall set this field to ‘0’ if the frequency specified
24 by the EXT_CDMA_FREQ field is used for BCCH frequency
25 assignment.
26 SR1_CDMA-
27 _FREQ_NON_TD - Frequency assignment for non-transmit diversity operation.
28 If SR1_NON_TD_FREQ_INCL is not included, or is included
29 and set to ‘0’, the base station shall omit this field; otherwise,
30 the base station shall set this field as follows:
33 the CDMA Channel containing a Broadcast Control Channel
34 that does not support the TD operation.
35 SR1_BRAT_NON_TD - BCCH data rate in non-TD mode for Spreading Rate 1.
5 If compatibility with IS-95-A mobile stations is desired in a Band Class 0 system, the CDMA_FREQ
field is set to the CDMA frequency assignment containing this Sync Channel.
3-256
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the BRAT field value
3 used by the Primary Broadcast Control Channel in the
4 system.
5 Table 3.7.2.3.2.26-2. Broadcast Control Channel Data Rate
BRAT Field (binary) Broadcast Control Channel

data rate
00 4800 bps
01 9600 bps
10 19200bps
11 Reserved
7 SR1_CRAT_NON_TD – BCCH code rate in non Transmit Diversity mode for Spreading
8 Rate 1.
12 The base station shall set this field to ‘0’ if the BCCH Code
13 Rate is 1/4 (see 3.1.3.1.2.1 of [2]). The base station shall set
14 this field to ‘1’ if the BCCH code rate is 1/2 (see 3.1.3.1.2.1 of
15 [2]).
16 SR1_BCCH_CODE-
17 _CHAN_NON_TD – Walsh code for the Spreading Rate 1 BCCH in non Transmit
18 Diversity mode.
23 corresponding to the Spreading Rate 1 BCCH in non Transmit
24 Diversity mode.
25 SR1_TD_INCL - Spreading Rate 1 Transmit Diversity frequency information
27 If SR1_BCCH_SUPPORTED is set to ‘0’, the base station shall
29 as follows:
31 SR1_CDMA_FREQ_TD, SR1_BRAT_TD, SR1_CRAT_TD,
32 SR1_TD_MODE, and SR1_TD_POWER_LEVEL are included in
33 the message; otherwise, the base station shall set this field to
34 ‘0’.
35 SR1_CDMA_FREQFREQ_TD - Spreading Rate 1 frequency assignment for Transmit
36 Diversity operation.
3-257
3GPP2 C.S0005-A v6.0
1 If SR1_TD_INCL is not included in this message or is included

2 but is set to ‘0’, the base station shall omit this field;
3 otherwise, the base station shall set this field as follows:
6 the CDMA Channel containing a BCCH Channel that supports
7 the TD operation.
8 SR1_BRAT_TD - BCCH data rate in Transmit Diversity mode for Spreading
9 Rate 1.
15 used by the Primary Broadcast Control Channel in the
16 system.
17 SR1_CRAT_TD – BCCH code rate in Transmit Diversity mode for Spreading
18 Rate 1.
22 The base station shall set this field to ‘0’ if the BCCH Code
23 Rate is 1/4 (see 3.1.3.1.2.1 of [2]). The base station shall set
24 this field to ‘1’ if the BCCH Code Rate is 1/2 (see 3.1.3.1.2.1 of
25 [2]).
26 SR1_BCCH-
27 _CODE_CHAN_TD – Walsh code for the Spreading Rate 1 BCCH in Transmit
28 Diversity mode.
33 corresponding to the Spreading Rate 1 BCCH in Transmit
34 Diversity mode.
35 SR1_TD_MODE - Spreading Rate 1 Transmit Diversity Mode.
39 The base station shall set this field corresponding to Table
40 3.7.2.3.2.26-3.
3-258
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.26-3. TD Mode
TD_MODE Descriptions
00 OTD (Orthogonal Transmit

Diversity) mode
01 STS (Space Time Spreading)
mode
10-11 Reserved
3 SR1_TD-
4 _POWER_LEVEL - Spreading Rate 1 TD transmit power level.
9 level relative to that of the Forward Pilot Channel, as specified
10 in Table 3.7.2.3.2.26-4.
11 Table 3.7.2.3.2.26-4. TD Transmit Power Level
TD_POWER_LEVEL Transmit Power Level
00 9 dB below the Forward Pilot

11 Same as the Forward Pilot
12
13 SR3_INCL - Spreading Rate 3 information included indicator.

14 The base station shall set this field to ‘1’ if the Spreading Rate
15 3 information is included in this message; otherwise, the base
17 SR3_CENTER-
18 _FREQ_INCL - Center SR3 frequency assignment included.
19 If SR3_INCL is set to ‘0’, the base station shall omit this field;
3-259
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to ‘1’, if the CDMA
2 Channel number corresponding to the SR3 center frequency
3 assignment for the CDMA Channel containing a Broadcast
4 Control Channel is different to EXT_CDMA_FREQ. Otherwise,
6 SR3_CENTER_FREQ - Center SR3 frequency assignment.
7 If SR3_CENTER_FREQ_INCL is not included or is included but
8 is set to ‘0’, the base station shall omit this field; otherwise,
11 number corresponding to the SR3 center frequency
13 Control Channel.
14 SR3_BRAT – Spreading Rate 3 BCCH data rate.
17 The base station shall set this field to the BCCH rate field
18 value shown in Table 3.7.2.3.2.26-2 corresponding to the data
19 rate used by the Primary Broadcast Control Channel in the
20 system.
21 SR3_BCCH-
22 _CODE_CHAN – Spreading Rate 3 BCCH Walsh code.
26 corresponding to the Spreading Rate 3 BCCH.
3-260
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.26-5. The Position of the Primary SR3

2 Pilot
SR3_PRIMARY_PILOT Position
(Binary)
00 The primary pilot is on the

lowest SR3 frequency
center SR3 frequency
highest SR3 frequency
11 Reserved
7 otherwise, the base station shall set this field to the value
8 shown in Table 3.7.2.3.2.26-6 corresponding to the power
9 level of the primary pilot with respect to the pilot on the lower
11
12 Table 3.7.2.3.2.26-6. Pilot Transmission Power
SR3_PILOT_POWER1, Relative Transmission Power

SR3_PILOT_POWER2
(Binary)
000 0dB
001 1dB
010 2dB
011 3dB
100 4dB
101 5dB
110 6dB
111 7dB
13
3-261
3GPP2 C.S0005-A v6.0
4 level of the primary pilot with respect to the pilot on the
6 DS_INCL - Direct Spread (DS) System and Information Available.
7 If the base station is a pilot beacon and includes the
8 DS_BLOB field (containing information on how to access a DS
9 system, see [32]), the base station shall set this field to ‘1’;
10 otherwise the base shall set this field to ‘0’.
11 DS_BLOB - Access Information about a Direct Spread (DS) System.
12 If DS_INCL is set to ‘1’, the base station shall include this field
13 and set it as described in [32].
14 If DS_INCL is set to ‘0’, the base station shall omit this field.
15
3-262
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.27 Extended Global Service Redirection Message
2 MSG_TAG: EGSRDM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
REDIRECT_ACCOLC 16
RETURN_IF_FAIL 1
DELETE_TMSI 1
REDIRECT_P_REV_INCL 1
EXCL P_REV_IND 0 or 1
REDIRECT_P_MIN 0 or 8
REDIRECT_P_MAX 0 or 8

RECORD_TYPE 8
RECORD_LEN 8

10 (see 3.6.2.2).
11 REDIRECT_ACCOLC - Redirected access overload classes.
12 See REDIRECT_ACCOLC field defined in 3.7.2.3.2.18.
13 The base station shall set the subfields corresponding to the

14 access overload classes of mobile stations which are to be
15 redirected to ‘1’, and shall set the remaining subfields to ‘0’.
3-263
3GPP2 C.S0005-A v6.0

11 REDIRECT_P_REV_INCL - Redirection mobile protocol revision included.
12 If the redirection specified in this message applies to the
13 mobile stations of some specific protocol revisions, the base
14 station shall set this field to ‘1’; otherwise, if this redirection
15 applies to all mobile stations, the base station shall set this
17 EXCL_P_REV_IND - Excluding mobile protocol revision indicator.
18 If the REDIRECT_P_REV_INCL is set to ‘1’, the base station
19 shall include this field and set this field as described below;
21 If mobile stations with MOB_P_REV in the range between
22 REDIRECT_P_MIN and REDIRECT_P_MAX inclusive are
23 excluded from this Global Service Redirection, the base
24 station shall set this field to ‘1’. Otherwise, if the mobile
25 stations with MOB_P_REV in the protocol revision range
26 specified in DIRECT_P_MIN and DIRECT_P_MAX are subjected
27 to the redirection, the base station shall set this field to ‘0’.
28 REDIRECT_P_MIN - Minimum redirection protocol revision.
29 If REDIRECT_P_REV_INCL is set to ‘0’, the base station shall
33 revision of which mobile stations are subjected to as specified
34 by the action contained in EXCL_P_REV_IND (i.e., to be
35 redirected or excluded from redirection). The base station shall
36 set this field to a protocol revision equal to or greater than six.
37 REDIRECT_P_MAX - Maximum direction protocol revision.
38 If REDIRECT_P_REV_INCL is set to ‘0’, the base station shall
41 The base station shall set this field to the maximum protocol
42 revision of which mobile stations are subjected to as specified
43 by the action contained in EXCL_P_REV_IND (i.e., to be
44 redirected or excluded from redirection). The base station shall
45 set this field to a protocol revision equal to or greater than six.
46
3-264
3GPP2 C.S0005-A v6.0
1 The base station shall include one occurrence of the following three-field record:
8 the type-specific fields of this redirection record.
12
14
Field Length (bits)
EXPECTED_SID 15
IGNORE_CDMA 1
SYS_ORDERING 3
MAX_REDIRECT_DELAY 5
15

20 to 0.
35 MAX_REDIRECT_DELAY - Maximum delay upon redirection.
3-265
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the maximum delay
2 time, in units of 8 seconds, to be used by mobile stations in
3 the event of a global redirection to analog mode. This
4 operation can be invoked to avoid overloading an underlying
5 analog cell’s reverse control channel.
6
BAND_CLASS 5
EXPECTED_SID 15
EXPECTED_NID 16
RESERVED 4
NUM_CHANS 4
CDMA_CHAN 11

17 to ‘0’.
22 field to 65535.
24 The base station shall set this field to ‘0’
3-266
3GPP2 C.S0005-A v6.0


9
3-267
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.28 Extended CDMA Channel List Message
2 MSG_TAG: ECCLM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
NUM_FREQ 4
NUM_FREQ occurrences of the following field:
CDMA_FREQ 11
RC_QPCH_SEL_INCL 1
If RC_QPCH_SEL_INCL is equal to ‘1’, include NUM_FREQ
occurrences of the following field:
RC_QPCH_HASH_IND 1
TD_SEL_INCL 1
TD_MODE 0 or 2
If TD_SEL_INCL is equal to ‘1’, include NUM_FREQ
occurrences of the following fields:
TD_HASH_IND 1
TD_POWER_LEVEL 0 or 2

10 (see 3.6.2.2).
11 NUM_FREQ - Number of CDMA Frequencies
13 supported CDMA frequencies included in this message.
14 The base station shall not set this field to ‘0000’.
15
3-268
3GPP2 C.S0005-A v6.0
1 CDMA_FREQ - CDMA Channel frequency assignment.

3 each CDMA Channel, containing either a Paging Channel, or a
4 Broadcast Control Channel and Forward Common Control
5 Channel.
6 The base station shall set each occurrence of this field to the
7 CDMA channel number corresponding to the CDMA frequency
8 assignment for that CDMA Channel (see [2]).
9 If the base station supports a CDMA frequency assignment
10 without transmit diversity, the base station should not set the
11 first occurrence of this field to a CDMA channel number
12 corresponding to a transmit diversity frequency assignment.
13 RC_QPCH_SEL_INCL - RC and QPCH Selection included indicator
14 The base station shall set this field to ‘1’, if NUM_FREQ
15 occurrences of RC_QPCH_HASH_IND are included; otherwise,
16 it shall set this field to ‘0’.
17 If the base station sets this field to ‘1’, the base station shall set the RC_QPCH_HASH_IND
18 field to ‘1’ in at least one of the following one-field records:
19 RC_QPCH-
20 _HASH_IND - RC_QPCH channel hashing indicator
21 If RC_QPCH_SEL_INCL is set to ‘1’, the base station shall
22 include NUM_FREQ occurrences of this field and set this field
23 as follow; otherwise, the base station shall omit this field.
24 When the Extended CDMA Channel List Message is sent on the
25 Paging Channel, the base station shall perform the following:
26 If the associated CDMA_FREQ is to be selected for CDMA
27 channel hashing by mobile stations capable of RC greater
28 than two or capable of supporting Quick Paging Channel, the
29 base station shall set the field to ‘1’; otherwise, the base
30 station shall set this field to ‘0 ’.
32 Primary Broadcast Control Channel, tThe base station shall
33 set this field to ‘1’, if the corresponding CDMA channel is to be
34 selected for channel hashing by mobile stations capable of
35 Radio Configurations greater than two or capable of
36 supporting Quick Paging Channel with Quick Paging Channel
37 capability.
38 TD_SEL_INCL - Transmit diversity selection indicator included.
39 The base station shall set this field to ‘1’, if the base station
40 includes transmit diversity selection information in this

43 Paging Channel, the base station shall set this field to ‘0’.
3-269
3GPP2 C.S0005-A v6.0
2 TD_MODE - Transmit diversity mode.

3 If the field TD_SEL_INCL is set to ‘0’, the base station shall
8 If the TD_SEL_INCL is set to ‘1’, the base station shall include NUM_FREQ occurrences of
9 the following two-field record, and shall set the TD_HASH_IND field to ‘1’ in at least one of
10 the records:
11 TD_HASH_IND - Transmit diversity hash indicator.
12 If the associated CDMA_FREQ is to be selected for CDMA
13 channel hashing by mobile stations capable of supporting
14 transmit diversity [TD_MODE], the base station shall set the
16 TD_POWER_LEVEL - Transmit diversity power level.
17 If TD_HASH_IND is set to ‘0’, the base station shall omit this
19 set it to the transmit diversity transmission power level
20 relative to that of the Forward Pilot Channel, as specified in
21 Table 3.7.2.3.2.26-4.
22
3-270
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.29 User Zone Reject Message
2 MSG_TAG: UZRM
Field Length (bits)
REJECT_UZID 16
REJECT_ACTION_INDI 3
UZID_ASSIGN_INCL 1
ASSIGN_UZID 0 or 16
3 REJECT_UZID - Rejected User Zone identifier.
5 of the User Zone rejected by the base station.
6 REJECT_ACTION_INDI - Rejection action indicator.
8 Table 3.7.2.3.2.29-1 corresponding to the User Zone rejection
9 action field to identify the mobile station action.
10 Table 3.7.2.3.2.29-1. Rejection Action Indicators
Description REJECT_ACTION_INDI
(binary)
Disable UZID until Next 000
Update
Disable UZID until next 001
power cycle
Disable UZID until new 010
SID
Disable UZID until new 011
SID/NID
Disable UZID until next 100
BASE_ID
All other REJECT_ACTION_INDI values are reserved
11
12 UZID_ASSIGN_INCL - User Zone identifier assignment included indicator.
13 If assigned UZID information is included, the base station

3-271
3GPP2 C.S0005-A v6.0
1 ASSIGN_UZID - Assigned User Zone identifiers.
3 of the User Zone assigned to the mobile station.
3-272
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.30 ANSI-41 System Parameters Message
2 MSG_TAG: A41SPM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
SID 15
NID 16
PACKET_ZONE_ID 8
REG_ZONE 12
TOTAL_ZONES 3
ZONE_TIMER 3
MULT_SIDS 1
MULT_NIDS 1
HOME_REG 1
FOR_SID_REG 1
FOR_NID_REG 1
POWER_UP_REG 1
POWER_DOWN_REG 1
PARAMETER_REG 1
REG_PRD 7
DIST_REG_INCL 1
REG_DIST 0 or 11
DELETE_FOR_TMSI 1
USE_TMSI 1
PREF_MSID_TYPE 2
3-273
3GPP2 C.S0005-A v6.0
Field Length (bits)
TMSI_ZONE_LEN 4
IMSI_T_SUPPORTED 1
MAX_NUM_ALT_SO 3
AUTO_MSG_SUPPORTED 1
AUTO_MSG_INTERVAL 0 or 3
OTHER_INFO_INCL 1
BASE_ID 0 or 16
MCC 0 or 10
IMSI_11_12 0 or 7
BROADCAST_GPS_ASST 0 or 1
STORE_KEY 0 or 1
CS_SUPPORTED 1
MS_INIT_POS_LOC_SUP_IND 1

8 (see 3.6.2.2).
3-274
3GPP2 C.S0005-A v6.0

5 number (see 2.6.5.1.5).
16
17 Table 3.7.2.3.2.30-1. Value of Zone Timer
ZONE_TIMER Timer Length

000 1
001 2
010 5
011 10
100 20
101 30
110 45
111 60
18

3-275
3GPP2 C.S0005-A v6.0
1 HOME_REG - Home registration indicator.

2 If mobile stations that are not roaming (see 2.6.5.3) and have
3 MOB_TERM_HOME equal to ‘1’ are to be enabled for
4 autonomous registrations, the base station shall set this field
5 to ‘1’. If such mobile stations are not to be enabled for
7 to ’0’.
8 FOR_SID_REG - SID roamer registration indicator.
9 If mobile stations that are foreign SID roamers (see 2.6.5.3)
10 and have MOB_TERM_FOR_SID equal to ‘1’ are to be enabled
14 to ’0’.
15 FOR_NID_REG - NID roamer registration indicator.
16 If mobile stations that are foreign NID roamers (see 2.6.5.3)
17 and have MOB_TERM_FOR_NID equal to ‘1’ are to be enabled
21 to ‘0’.
22 POWER_UP_REG - Power-up registration indicator.
24 register immediately after powering on and receiving the
25 system overhead messages, the base station shall set this field
27 POWER_DOWN_REG - Power-down registration indicator.
29 register immediately before powering down, the base station
32 PARAMETER_REG - Parameter-change registration indicator.
33 If mobile stations are to register on parameter change events
34 as specified in 2.6.5.1.6, the base station shall set this field to
35 ‘1’. If not, the base station shall set this field to ‘0’.
36 REG_PRD - Registration period.
37 If mobile stations are not to perform timer-based registration,
38 the base station shall set this field to ‘0000000’. If mobile
39 stations are to perform timer-based registration, the base
40 station shall set this field to the value in the range 29 to 85
41 inclusive, such that the desired timer value is
42 2REG_PRD/4 × 0.08 seconds.
3-276
3GPP2 C.S0005-A v6.0
1 DIST_REG_INCL - Distance-Based Registration Information Included.

2 The base station shall set this field to ‘1’ if it includes
3 distance-based registration information in the message and
4 mobile stations are to perform distance-based registration;
5 otherwise the base station shall set this field to ‘0’.
7 If DIST_REG_INCL is set to ‘1’, the base station shall include
8 the field REG_DIST and shall set this field as shown below;
10 The base station shall set this field to the non-zero “distance”
12 2.6.5.1.4).
13 DELETE_FOR_TMSI - Delete foreign TMSI.
14 The base station shall set this field to ‘1’ to cause the mobile
15 station to delete its TMSI if the TMSI was assigned in a
16 different TMSI zone from that specified by the TMSI_ZONE
17 field of this message; otherwise, the base station shall set this
19 USE_TMSI - Use TMSI indicator.
22 the mobile station is to use on the Enhanced Access Channel.
23 PREF_MSID_TYPE - Preferred Enhanced Access Channel Mobile Station Identifier
24 Type.
27 the mobile station is to use on the Enhanced Access Channel.
28
29 Table 3.7.2.3.2.30-2. Preferred MSID Types
USE_TMSI PREF_MSID_TYPE
(binary) (binary) Description
0 00 IMSI_S and ESN
0 10 IMSI
0 11 IMSI and ESN
assigned);
IMSI (TMSI not assigned)
assigned);
IMSI and ESN (TMSI not
assigned)
3-277
3GPP2 C.S0005-A v6.0

7 The base station shall set this field to the TMSI zone number
9 IMSI_T_SUPPORTED - IMSI_T support indicator.
10 The base station shall set this field to ‘1’ to indicate support
11 for a 15-digit IMSI_T addressing according to [18].
12 MAX_NUM_ALT_SO - Maximum number of alternative service options.
14 of service option numbers defined in [30], corresponding to
15 alternative service options with no service option group
16 number assigned, that the mobile station is allowed to include
17 in the Origination Message, and the Page Response.
18 If the base station sets this field to a value greater than zero,
19 in addition, the base station shall allow the mobile station to
20 include
21 • a 4-bit or 8-bit service option bitmap in the Origination
22 Message and the Page Response Message;
23 • alternate service option numbers, not limited to
24 MAX_ALT_SO_NUM, in the Enhanced Origination Message.
25 AUTO_MSG-
26 _SUPPORTED - Autonomous message supported indicator.
27 If the base station allows the autonomous delivery of the
28 Device Information Message on the r-csch, the base station
31 AUTO_MSG-
32 _INTERVAL - Autonomous message interval.
33 If AUTO_MSG_SUPPORTED is set to ‘01’, the base station
35 this field and shall set this field to the AUTO_MSG_INTERVAL
36 value shown in Table 3.7.2.3.2.13-4 to indicate the minimum
37 time interval between autonomous messages sent by a mobile
38 station to the infrastructure. This parameter is intended to
39 allow the infrastructure to limit the frequency of autonomous
40 messages sent by a mobile station on the r-csch.
41 OTHER_INFO_INCL - Other information included indicator.
42 The base station shall set this field to ‘1’ if the MC-RR
43 Parameters Message is not sent; otherwise, the base station
3-278
3GPP2 C.S0005-A v6.0

2 If OTHER_INFO_INCL is set to ‘1’, the base station shall
3 include this field and set it as follows; otherwise, the base
6 number.
th th
17 2.3.1).
30 5.
32 as follows:
3-279
3GPP2 C.S0005-A v6.0
2 mobile station is to store the session key; otherwise the base
4 CS_SUPPORTED – Concurrent Services supported indicator.
8 MS_INIT_POS_LOC - Mobile station initiated position location determination
9 _SUP_IND supported indicator.
10 If the base station supports mobile station initiated position
11 determination, the base station shall set this field to ‘1’;
13
3-280
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.31 MC-RR Parameters Message
2 MSG_TAG: MCRRPM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
BASE_ID 16
P_REV 8
MIN_P_REV 8
SR3_INCL 1
SR3_CENTER_FREQ_INCL 0 or 1
SR3_CENTER_FREQ 0 or 11
SR3_BRAT 0 or 2
SR3_BCCH_CODE_CHAN 0 or 7
SR3_PRIMARY_PILOT 0 or 2
SRCH_WIN_A 4
SRCH_WIN_R 4
T_ADD 6
T_DROP 6
T_COMP 4
T_TDROP 4
NGHBR_MAX_AGE 4
SOFT_SLOPE 6
ADD_INTERCEPT 6
DROP_INTERCEPT 6
ENC_SUPPORTED 1
STORE_KEY 0 or 1
3
3-281
3GPP2 C.S0005-A v6.0
Field Length (bits)

ADD_FIELDS_LEN 8
ADD_FIELDS 8 × ADD_FIELDS_LEN
CCH_INFO_INCL 1
MCC 0 or 10
IMSI_11_12 0 or 7
MAX_SLOT_CYCLE_INDEX 0 or 3
PWR_REP_THRESH 0 or 5
PWR_REP_FRAMES 0 or 4
PWR_THRESH_ENABLE 0 or 1
PWR_PERIOD_ENABLE 0 or 1
PWR_REP_DELAY 0 or 5
RESELECT_INCLUDED 0 or 1
EC_THRESH 0 or 5
EC_IO_THRESH 0 or 5
BASE_LAT 0 or 22
BASE_LONG 0 or 23
PILOT_REPORT 0 or 1
ACC_ENT_HO_ORDER 0 or 1
ACCESS_HO 0 or 1
ACCESS_HO_MSG_RSP 0 or 1
ACCESS_PROBE_HO 0 or 1
ACC_HO_LIST_UPD 0 or 1
ACC_PROBE_HO_OTHER_MSG 0 or 1
MAX_NUM_PROBE_HO 0 or 3
NUM_FCCCH 0 or 3
FCCCH_RATE 0 or 3
FCCCH_CODE_RATE 0 or 1
NUM_FCCCH occurrences of the following one field record:
FCCCH_CODE_CHAN 8
3-282
3GPP2 C.S0005-A v6.0
Field Length (bits)

BCAST_INDEX 0 or 3
NUM_BCCH_BCAST 0 or 3
NUM_BCCH_BCAST occurrences of the following three-field
record:
BCCH_CODE_CHAN 7
BRAT 2
BCCH_CODE_RATE 1
NUM_QPCH 0 or 2
QPCH_RATE 0 or 1
QPCH_POWER_LEVEL_PAGE 0 or 3
QPCH_CCI_SUPPORTED 0 or 1
QPCH_POWER_LEVEL_CONFIG 0 or 3
NUM_QPCH occurrences of the following one field record if
operating in Spreading Rate 3 common channel:
QPCH_CODE_CHAN 0 or 8
QPCH_BI_SUPPORTED 0 or 1
QPCH_POWER_LEVEL_BCAST 0 or 3
SDB_SUPPORTED 0 or 1
BROADCAST_GPS_ASST 0 or 1
RLGAIN_TRAFFIC_PILOT 0 or 6
MOB_QOS 0 or 1
USE_SYNC_ID 0 or 1
NUM_OPT_MSG 0 or 4
3-283
3GPP2 C.S0005-A v6.0
Field Length (bits)

SENDING_RAND 0 or 1
PRI_NGHBR_LIST 0 or 1
USER_ZONE_ID 0 or 1
EXT_GLOBAL_REDIRECT 0 or 1
RESERVED 0 or (NUM_OPT_MSG –
4)
PILOT_INFO_REQ_SUPPORTED 0 or 1

7 (see 3.6.2.2).
10 number.
14 The base station sets this field to prevent mobile stations,
16 the system.
26 Class 7, Band Class 8, or Band Class 9, or Band Class 10
27 operation, the base station should set this field to ‘00000110’
28 or greater.
29 SR3_INCL - Spreading Rate 3 common channel parameters included
30 indicator.
3-284
3GPP2 C.S0005-A v6.0
2 includes SR3 related parameters in this message; otherwise,
4 If the base station is operating in SR3 mode, the base station
6 SR3_CENTER-
7 _FREQ_INCL - Center SR3 frequency assignment included.
10 The base station shall set this field to ‘1’, if the CDMA
11 Channel number corresponding to the SR3 center frequency
13 Control Channel is different from the current SR1 frequency
14 assignment. Otherwise, the base station shall set this field to
15 ‘0’.
16 SR3_CENTER_FREQ - Center SR3 frequency assignment.
17 If SR3_CENTER_FREQ_INCL is not included or is included but
21 number corresponding to the SR3 center frequency
23 Control Channel.
24 SR3_BRAT - Spreading Rate 3 BCCH data rate.
27 The base station shall set this field to the BCCH rate field
29 rate used by the Primary Broadcast Control Channel in the
30 system.
31 SR3_BCCH-
32 _CODE_CHAN - Spreading Rate 3 BCCH Walsh code index.
35 The base station shall set this field to the Walsh code index
36 corresponding to the Spreading Rate 3 BCCH.
37 SR3_PRIMARY_PILOT - Primary SR3 pilot.
43 SR3_PILOT_POWER1 - The primary SR3 pilot power level relative to that of the pilot
3-285
3GPP2 C.S0005-A v6.0
6 SR3_PILOT_POWER2 - The primary SR3 pilot power level relative to that of the pilot
16 be used by mobile stations for the Active Set and Candidate
17 Set.
21 be used by mobile stations for the Remaining Set.
28 2.6.6.2.5.2).
31 - 2 × 10 × log10 Ec/Io .
35 2.6.6.2.3).
38 - 2 × 10 × log10 Ec/Io .

40 Mobile stations transmit a Pilot Strength Measurement
41 Message or Extended Pilot Strength Measurement Message
3-286
3GPP2 C.S0005-A v6.0

2 Timer value after which an action is taken by mobile stations
3 for a pilot that is a member of the Active Set or Candidate Set,
4 and whose strength has not become greater than T_DROP. If
5 the pilot is a member of the Active Set, a Pilot Strength
6 Measurement Message or Extended Pilot Strength Measurement
7 Message is issued. If the pilot is a member of the Candidate
8 Set, it will be moved to the Neighbor Set.
11 value to be used by mobile stations.
12 NGHBR_MAX_AGE - Neighbor Set maximum AGE.
13 The base station shall set this field to the maximum AGE
14 value beyond which mobile stations are to drop members from
15 the Neighbor Set (see 2.6.6.2.6.3).
18 2.6.6.2.3 and 2.6.6.2.5.2).
20 number.
30 The base station shall set this field to ‘1’ if the encryption
38 station.
3-287
3GPP2 C.S0005-A v6.0

2 5.
4 as follows:
16 algorithms.
18 9.
27 field to ‘1’ to indicate that the mobile station is to store the
28 session key; otherwise the base station shall set this field to
29 ‘0’.
30 ADD_FIELDS_LEN - Additional fields length.
32 included in the ADD_FIELDS. The base station shall set this
33 field to ‘00000000’.
34 ADD_FIELDS - Additional fields.
35 The base station shall include 8 x ADD_FIELDS_LEN bits to
36 support additional fields, if any.
37 CCH_INFO_INCL - Common Channel information included indicator.
38 If the message is sent on the f-csch and additional information
39 is included, the base station shall set this field to ‘1’;
3-288
3GPP2 C.S0005-A v6.0

2 If CCH_INFO_INCL is set to ‘1’, the base station shall include
3 this field and set it as follows; otherwise, the base station
th th
8 this field and set it as follows; otherwise, the base station
11 2.3.1).
12 MAX_SLOT_CYCLE- - Maximum slot cycle index.
13 _INDEX If CCH_INFO_INCL is set to ‘1’, the base station shall include
14 the field MAX_SLOT_CYCLE_INDEX and shall set this field as
15 shown below; otherwise, the base station shall omit this field.
16 The base station shall set this field to the
17 SLOT_CYCLE_INDEX value corresponding to the maximum
18 slot cycle length permitted (see 2.6.2.1.1).
21 the field PWR_REP_THRESH and shall set this field as shown
26 mobile stations are to generate a Power Measurement Report
29 ‘00000’.
32 the field PWR_REP_FRAMES and shall set this field as shown
35 number given by
37 is the number of frames over which mobile stations are to
40 _ENABLE If CCH_INFO_INCL is set to ‘1’, the base station shall include
41 the field PWR_THRESH_ENABLE and shall set this field as
3-289
3GPP2 C.S0005-A v6.0
1 If mobile stations are to generate threshold Power

3 field to ‘1’. If mobile stations are not to generate threshold
7 _ENABLE If CCH_INFO_INCL is set to ‘1’, the base station shall include
8 the field PWR_PERIOD_ENABLE and shall set this field as
10 If mobile stations are to generate periodic Power Measurement
11 Report Messages, the base station shall set this field to ‘1’. If
12 mobile stations are not to generate periodic Power
16 The period that mobile stations wait following a Power
20 the field PWR_REP_DELAY and shall set this field as shown
24 RESELECT_INCLUDED - System reselection parameters included.
26 the field RESELECT_INCLUDED and shall set this field as
28 If the base station is including system reselection parameters,
31 EC_THRESH - Pilot power threshold.
32 If RESELECT_INCLUDED is included and is set to ‘1’, the base
33 station shall include the field EC_THRESH and shall set this
34 field as shown below; otherwise, the base station shall omit
35 this field.
36 The base station shall set this field to:
37  (pilot_power_threshold + 115) 
38 where pilot_power_threshold is the pilot power, Ec, in
39 dBm/1.23 MHz, below which the mobile station is to perform
40 system reselection.
41 EC_IO_THRESH - Pilot Ec/ Io threshold.
42 If RESELECT_INCLUDED is included and is set to ‘1’, the base

43 station shall include the field EC_IO_THRESH and shall set
44 this field as shown below; otherwise, the base station shall
45 omit this field.
3-290
3GPP2 C.S0005-A v6.0

2  - 20 × log10 (pilot_threshold ) 
3 where pilot_threshold is the pilot Ec/Io below which the mobile
4 station is to perform system reselection.
7 this field and set it as shown below; otherwise, the base
23 +180°).
24 PILOT_REPORT - Pilot reporting indicator.
26 the field PILOT_REPORT and shall set this field as shown
30 exceeding T_ADD in all Enhanced Access Channel messages.
33 exceeding T_ADD only in the Origination Message and the
35 ACC_ENT_HO_ORDER - Access entry handoff permitted indicator.
37 this field and set it as described below; otherwise, the base
40 is permitted to perform an access entry handoff after receiving
41 a message while performing the Mobile Station Order and
42 Message Processing Operation in the Mobile Station Idle State
43 (see 2.6.2.4); otherwise, the base station shall set this field to
44 ‘0’.
3-291
3GPP2 C.S0005-A v6.0
1 ACCESS_HO - Access handoff permitted indicator.

6 is permitted to perform an access handoff (see 2.6.3.1.3.2);
8 ACCESS_HO_MSG_RSP - Access handoff permitted for message response indicator.
9 If ACCESS_HO is included and set to ‘1’, the base station shall
13 is permitted to perform an access handoff after receiving a
14 message and before responding to that message in the System
15 Access State; otherwise, the base station shall set this field to
16 ‘0’.
17 ACCESS_PROBE_HO - Access probe handoff permitted indicator.
22 is permitted to perform an access probe handoff (see
24 ‘0’.
25 ACC_HO_LIST_UPD - Access handoff list update permitted indicator.
26 If ACCESS_PROBE_HO is included and is set to ‘1’, the base
30 is permitted to update the access handoff list during an
31 access attempt (see 2.6.3.1.7.2); otherwise, the base station
33 ACC_PROBE_HO-
34 _OTHER_MSG - Access probe handoff permitted for messages other than the
35 Origination Message and the Page Response Message.
36 If ACCESS_PROBE_HO is included and set to ‘1’, the base
40 is permitted to perform an access probe handoff for messages
41 other than the Origination Message and the Page Response
42 Message. The base station shall set this field to ‘0’ if the
43 mobile station is permitted to perform an access probe
44 handoff only for the Origination Message and the Page
45 Response Message. See 2.6.3.1.3.3.
46 MAX_NUM_PROBE_HO - Maximum number of times that the mobile station is
3-292
3GPP2 C.S0005-A v6.0
1 If ACCESS_PROBE_HO is included and set to ‘1’, the base

5 of times the mobile station is allowed to perform an access
6 probe handoff within an access attempt minus one.
7 NUM_FCCCH - Total number of Forward Common Control Channels.
9 this field and shall set it as shown below; otherwise, the base
11 The base station shall set this field to the total number of
12 Forward Common Control Channels on this CDMA Channel.
13 If this is not a pilot beacon base station, the base station shall
14 set this field to an integer value greater than 0.
15 FCCCH_RATE – Rate words for the Forward Common Control Channels.
16 If CCH_INFO_INCL is set to ‘1’ and NUM_FCCCH is not

17 equal to ‘0’, the base station shall include this field and shall
18 set it as shown below; otherwise, the base station shall omit
19 this field.
20 The base station shall set this field to the FCCCH rate field
22 rate used on the Forward Common Control Channels in the
23 system.
24 Table 3.7.2.3.2.31-1. Forward Common Control Channel

25 Rate Words
FCCCH Rate Field Forward Common Control

(binary) Channel rate word
000 9600 bps, 20 ms frame size

26
27 FCCCH_CODE_RATE - Code Rate for the Forward Common Control Channels.
28 If CCH_INFO_INCL is set to ‘1’ and NUM_FCCCH is not

29 equal to ‘0’, the base station shall include this field and shall
30 set it as shown below; otherwise, the base station shall omit
3-293
3GPP2 C.S0005-A v6.0
1 this field.
2 If the FCCCH is operating in Spreading Rate 1, the base
3 station shall set this field to ‘0’ if the FCCCH Code Rate is 1/4
4 (see 3.1.3.1.2.1 of [2]). The base station shall set this field to
5 ‘1’ if the FCCCH Code Rate is 1/2 (see 3.1.3.1.2.1 of [2]).
6 If the FCCCH is operating in Spreading Rate 3, the base
8 The base station shall include NUM_FCCCH occurrences of the following one field record:
9 FCCCH_CODE_CHAN - Code channel index for the Forward Common Control
10 Channel.
13 is to use on the Forward Common Control Channel.
14 BCAST_INDEX - Broadcast index.
16 the field BCAST_INDEX and shall set this field as shown
18 If Periodic Enhanced Broadcast Paging is disabled, the base
20 shall set this field to the Broadcast Index (see
21 2.6.2.1.1.3.3.21).
22 NUM_BCCH_BCAST - The number of Broadcast Control Channels used for
23 transmitting broadcast messages.
27 If the base station supports transmission of broadcast
28 messages, the base station shall set this field to the number of
29 Broadcast Control Channels used for transmitting broadcast
30 messages. If the base station supports transmission of
31 broadcast messages, the base station shall not set this field to
32 ‘000’.
33 If the NUM_BCCH_BCAST field is included, Tthe base station shall set NUM_BCCH_BCAST
34 occurrences of the following three-field record, where the ith occurrence corresponds to a
35 BCCH indexed by BCN of i+1:
36 BCCH_CODE_CHAN - The Walsh Code index for the Broadcast Control Channel
37 specified by BCCH_ID.
39 corresponding to the Broadcast Control Channel specified by
40 BCCH_ID.
41 BRAT - BCCH data rate.
44 used by the Broadcast Control Channel to which the mobile
45 station is being directed.
3-294
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.31-2. Broadcast Control Channel Data Rate
BRAT Field (binary) Broadcast Control Channel

data rate
00 4800 bps
01 9600 bps
10 19200 bps
11 Reserved
3 BCCH_CODE_RATE - BCCH code rate.

4 For spreading rate 1, the base station shall set this field to ‘0’
5 if the BCCH Code Rate is 1/4 (see 3.1.3.1.2.1 of [2]). For
6 spreading rate 1, the base station shall set this field to ‘1’ if
7 the BCCH code rate is 1/2 (see 3.1.3.1.2.1 of [2]). For
8 spreading rate 3, the base station shall set this field to ‘0’.
9 QPCH_SUPPORTED - Quick Paging Channel Supported Indication.
11 the field QPCH_SUPPORTED and shall set this field as shown
13 If the base station supports Quick Paging Channel operation,
14 the base station shall set this field to ‘1’; otherwise the base
16 NUM_QPCH - Number of Quick Paging Channels.
17 If QPCH_SUPPORTED is included and set to ‘1’, the base
20 The base station shall set this field to the number of Quick
21 Paging Channels on this CDMA Channel. The base station
22 shall not set this field to ‘00’.
23 QPCH_RATE - Quick Paging Channel indicator rate.
27 The base station shall set this field to the QPCH_RATE field
29 indicator rate used by the Quick Paging Channel in the
30 system.
31 QPCH_POWER-
32 _LEVEL_PAGE - Quick Paging Channel paging indicator transmit power level.
3-295
3GPP2 C.S0005-A v6.0
2 Channel paging indicator transmit power level relative to that
3 of the Pilot Channel as specified in Table 3.7.2.3.2.31-3.
4 Table 3.7.2.3.2.31-3. Quick Paging Channel Transmit Power

5 Level
QPCH_POWER_LEVEL_PAGE Transmit Power Level

QPCH_POWER_LEVEL_CONFIG
QPCH_POWER_LEVEL_BCAST
(binary)
000 5 dB below the Pilot Channel

Transmit Power
Transmit Power
Transmit Power
Transmit Power
Transmit Power
101 Same as the Pilot Channel
Transmit Power
110 1 dB above the Pilot Channel
Transmit Power
111 2 dB above the Pilot Channel
Transmit Power
7 QPCH_CCI_SUPPORTED - Quick Paging Channel configuration change indicator

8 supported.
12 If the base station supports configuration change indicators
13 on the Quick Paging Channel, the base station shall set this
14 field to ‘1’; otherwise the base station shall set this field to ‘0’.
15 QPCH_POWER_LEVEL- - Quick Paging Channel configuration change indicator
16 _CONFIG transmit power level.
17 If QPCH_CCI_SUPPORTED is included and set to ‘1’, the base
3-296
3GPP2 C.S0005-A v6.0
2 Channel configuration change indicator transmit power level
3 relative to that of the Pilot Channel as specified in Table
4 3.7.2.3.2.31-3.
5 If the base station is operating in Spreading Rate 3 BCCH channel, the base station shall
6 include NUM_QPCH occurrences of the following one field record:
7 QPCH_CODE_CHAN - Code channel index of the Quick Paging Channel for
8 Spreading Rate 3.
11 is to use on the Quick Paging Channel for Spreading Rate 3.
12
13 QPCH_BI_SUPPORTED - Quick Paging Channel broadcast indicator supported.

17 If the base station supports broadcast indicators on the Quick
18 Paging Channel, the base station shall set this field to ‘1’;
19 otherwise the base station shall set this field to ‘0’.
20 QPCH_POWER_LEVEL- - Quick Paging Channel broadcast indicator
21 _BCAST transmit power level.
22 If QPCH_BI_SUPPORTED is included and set to ‘1’, the base
26 Channel broadcast indicator transmit power level relative to
27 that of the Pilot Channel as specified in Table 3.7.2.3.2.31-3.
28 SDB_SUPPORTED - Short Data Burst supported indicator.
30 the field SDB_SUPPORTED and shall set this field as shown
33 is permitted to send a Short Data Burst; otherwise, the base
37 the field BROADCAST_GPS_ASST and shall set this field as
43 Reverse Pilot Channel for Radio Configurations greater than 2.
3-297
3GPP2 C.S0005-A v6.0

2 the field RLGAIN_TRAFFIC_PILOT and shall set this field as
5 be used by mobile stations in setting the power of a reverse
6 traffic channel, expressed as a two’s complement value in
7 units of 0.125 dB (see 2.1.2.3.3 of [2]).
8 REV_PWR-
9 CNTL_DELAY_INCL - Reverse Power Control Delay included indicator.
14 includes the REV_PWR_CNTL_DELAY field in this message;
16 REV_PWR-
18 If REV_PWR_CNTL_DELAY_INCL is included and set to ‘1’, the
19 base station shall include this field and set it as follows;
26 Subchannel, see 2.1.2.3.2 of [2]), in units of 1.25 ms.
27 MOB_QOS - Indicator granting permission to the mobile station to request
28 QoS parameter settings in the Origination Message, Origination
29 Continuation Message, or Enhanced Origination Message.
33 The base station shall set this field to ‘1’, if the mobile station
34 is allowed to include a QoS record in the Origination Message,
35 Origination Continuation Message, or Enhanced Origination
36 Message;, or to ‘0’, otherwise, the base station shall set this
38 USE_SYNC_ID - Sync ID supported indicator.
43 mobile station is permitted to include the SYNC_ID field in the
44 Page Response Message and the Origination Message.
45 Otherwise, the base station shall set this field to ‘0’.
3-298
3GPP2 C.S0005-A v6.0
1 NUM_OPT_MSG - Number of optional overhead messages to be sent.

2 If CCH_INFO_INCL is set to ‘1, the base station shall include
3 this field and shall set this field as shown below; otherwise,
5 The base station shall set this field to the number of optional
6 overhead messages to be sent.
7 SENDING_RAND - ANSI-41 RAND Message indicator.
8 If NUM_OPT_MSG is included and is equal to or greater than
9 1, the base station shall include the field SENDING_RAND and
10 shall set this field as shown below; otherwise, the base station
12 If the base station is sending the ANSI-41 RAND Message on
13 the Primary Broadcast Control Channel, it shall set this field
14 to ‘1’; otherwise, it shall set this field to ‘0’.
15 PRI_NGHBR_LIST - Private Neighbor List Message indicator.
17 2, the base station shall include the field PRI_NGHBR_LIST
18 and shall set this field as shown below; otherwise, the base
20 If the base station is sending the Private Neighbor List Message
21 on the Primary Broadcast Control Channel, it shall set this
22 field to ‘1’; otherwise, it shall set this field to ‘0’.
23 USER_ZONE_ID - User Zone Identification Message indicator.
25 3, the base station shall include the field USER_ZONE_ID and
28 If the base station is sending the User Zone Identification
29 Message on the Primary Broadcast Control Channel, it shall
30 set this field to ‘1’; otherwise, it shall set this field to ‘0’.
31 EXT_GLOBAL-
32 _REDIRECT - Extended Global Service Redirection Message indicator.
34 4, the base station shall include the field
35 EXT_GLOBAL_REDIRECT and shall set this field as shown
37 If the base station is sending the Extended Global Service
38 Redirection Message on the Primary Broadcast Control
39 Channel, it shall set this field to ‘1’; otherwise, the base
43 5, the base station shall include the field RESERVED and
3-299
3GPP2 C.S0005-A v6.0
1 The base station shall add (NUM_OPT_MSG – 4) reserved bits.

2 The base station shall set these bits to ‘0’.
3 PILOT_INFO_REQ
4 _SUPPORTED - Pilot information request supported indicator.
8 If the base station supports mobile station request for pilot
9 information using the “Pilot Information” record in the Base
10 Station Status Request Message, the base station shall set this
12
13
3-300
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.32 ANSI-41 RAND Message
2 MSG_TAG: A41RANDM
Field Length (bits)
PILOT_PN 9
RESERVED 6
RAND 32

10 RAND - Random challenge value.
11 The base station shall set this field to the random challenge
12 value to be used by mobile stations for authentication.
3-301
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.33 Enhanced Access Parameters Message
2 MSG_TAG: EAPM
Field Length (bits)

PILOT_PN 9
ACC_MSG_SEQ 6
PSIST_PARMS_INCL 1
PSIST_PARMS_LEN 0 or 5
PSIST(0-9)_EACH 0 or 6
PSIST(10)_EACH 0 or 3
PSIST_EMG 0 or 3
MSG_PSIST_EACH 0 or 3
REG_PSIST_EACH 0 or 3
LAC_PARMS_LEN 4
ACC_TMO 6
PROBE_PN_RAN RESERVED_1 4
MAX_REQ_SEQ 4
MAX_RSP_SEQ 4
3-302
3GPP2 C.S0005-A v6.0
Field Length (bits)

NUM_MODE_SELECTION_ENTRIES 3
NUM_MODE_SELECTION_ENTRIES + 1 occurrences of the
following record:
ACCESS_MODE 3
ACCESS_MODE_MIN_DURATION 10
ACCESS_MODE_MAX_DURATION 10
RLGAIN_COMMON_PILOT 6
IC_THRESH 4
IC_MAX 4
NUM_MODE_PARM_REC 3
NUM_MODE_PARM_REC + 1 occurrences of the following
record:
EACH_PARM_REC_LEN 4
APPLICABLE_MODES 8
EACH_NOM_PWR 5
EACH_INIT_PWR 5
EACH_PWR_STEP 3
EACH_NUM_STEP 4
EACH_PREAMBLE_ENABLED 1
EACH_PREAMBLE_NUM_FRAC 0 or 4
EACH_PREAMBLE_FRAC_DURATION 0 or 4
EACH_PREAMBLE_OFF_DURATION 0 or 4
EACH_PREAMBLE_ADD_DURATION 0 or 4
EACH_ACCESS_THRESHRESERVED 6
EACH_PROBE_BKOFF 4
EACH_BKOFF 4
EACH_SLOT 6
EACH_SLOT_OFFSET1 6
3-303
3GPP2 C.S0005-A v6.0
Field Length (bits)

EACH_SLOT_OFFSET2 6
BA_PARMS_LEN 32
NUM_EACH_BA 0 or 5
EACH_BA_RATES_SUPPORTED 0 or 8
RA_PARMS_LEN 5
NUM_EACH_RA 0 or 5
NUM_CACH 0 or 3
CACH_CODE_RATE 0 or 1
If RA_PARMS_LEN is not equal to ‘00000’, the base station
shall include (NUM_CACH + 1) occurrences of the following
one field record:
CACH_CODE_CHAN 8
NUM_RCCCH 0 or 5
RCCCH_RATES_SUPPORTED 0 or 8
RCCCH_PREAMBLE_ENABLED 0 or 1
RCCCH_PREAMBLE_NUM_FRAC 0 or 4
RCCCH_PREAMBLE- 0 or 4
_FRAC_DURATION
RCCCH_PREAMBLE_OFF_DURATION 0 or 4
RCCCH_PREAMBLE_ADD_DURATION 0 or 4
RCCCH_SLOT 0 or 6
RCCCH_SLOT_OFFSET1 0 or 6
RCCCH_SLOT_OFFSET2 0 or 6
RCCCH_NOM_PWR 0 or 5
RCCCH_INIT_PWR 0 or 5
RA_PC_DELAY 0 or 5
3-304
3GPP2 C.S0005-A v6.0
Field Length (bits)

EACAM_CACH_DELAY 0 or 4
RCCCH_HO_SUPPORTED 0 or 1
RCCCH_HO_THRESH 0 or 4
EACAM_PCCAM_DELAY 0 or 5
NUM_CPCCH 0 or 2
CPCCH_RATE 0 or 2
If RA_PARMS_LEN is not equal to ‘00000’, the base station
shall include (NUM_CPCCH + 1) occurrences of the
following one field record:
CPCCH_CODE_CHAN 8
NUM_PCSCH_RA 0 or 7
ACCT_INCL 1
ACCT_INCL_EMG 0 or 1
ACCT_AOC_BITMAP_INCL 0 or 1
ACCT_SO_INCL 0 or 1
NUM_ACCT_SO 0 or 4
If ACCT_SO_INCL is equal to ‘1’, NUM_ACCT_SO + 1
occurrences of the following variable-field record:
ACCT_SO 16
ACCT_SO_GRP_INCL 0 or 1
NUM_ACCT_SO_GRP 0 or 3
If ACCT_SO_GRP_INCL is equal to ‘1’,
NUM_ACCT_SO_GRP + 1 occurrences of the following
variable-field record:
ACCT_SO_GRP 5
3-305
3GPP2 C.S0005-A v6.0
3 ACC_MSG_SEQ - Enhanced Access Parameters Message sequence number.
5 (see 2.6.2.2.15).
6 PSIST_PARMS_INCL - Persistence parameters included indicator.

7 If persistence parameters are included in this message, the
10 PSIST_PARMS_LEN - Length of persistence parameters record.
11 If PSIST_PARMS_INCL is set to ‘0’, the base station shall omit
12 this field; otherwise, the base station shall set this field to the
13 total length, in octets, of persistence parameters included in
14 the message, including the PSIST_PARMS_LEN and
15 RESERVED fields.
16 PSIST(0-9)_EACH - Persistence value for access overload classes 0 through 9.
19 follows:
21 permitted to transmit requests on the Enhanced Access
22 Channel, the base station shall set this field to the persistence
23 value to be used. If such a mobile stations is not permitted to
24 transmit requests on the Enhanced Access Channel, the base
26 PSIST(10)_EACH - Persistence value for access overload class 10 (test mobile
27 stations).
30 follows:
31 If a mobile station in access overload class 10 is permitted to
33 station shall set this field to the persistence value to be used.
34 If such a mobile station is not permitted to transmit requests
35 on the Enhanced Access Channel, the base station shall set
37 PSIST(11)_EACH - Persistence value for access overload class 11 (emergency
38 mobile stations).
41 follows:
3-306
3GPP2 C.S0005-A v6.0

7 PSIST(12)_EACH - Persistence value for access overload class 12.
10 follows:
20 follows:
30 follows:
40 follows:
44 If such a mobile stations is not permitted to transmit requests
3-307
3GPP2 C.S0005-A v6.0
1 PSIST_EMG - Persistence value for emergency call for access overload

2 classes 0 through 9.
5 follows:
7 permitted to transmit emergency requests on the Enhanced
8 Access Channel, the base station shall set this field to the
9 persistence value to be used for the emergency calls. If such a
10 mobile station is not permitted to transmit emergency
11 requests on the Enhanced Access Channel, the base station
13 MSG_PSIST_EACH - Persistence modifier for Enhanced Access Channel attempts
14 for message transmissions.
17 persistence modifier for Enhanced Access Channel attempts
18 for message transmissions.
19 REG_PSIST_EACH - Persistence modifier for Enhanced Access Channel attempts
20 for registrations which are not responses to the Registration
21 Request Order.
24 persistence modifier for Enhanced Access Channel attempts
25 for registrations which are not responses to the Registration
26 Request Order.
29 this field; otherwise, the base station shall include as many
30 bits as required to make the length of the persistence
31 parameters record an integral number of octets. If this field is
32 included, the base station shall set each of these bits to ‘0.
33
34 LAC_PARMS_LEN - Length of Link Access Control parameter fields.

35 The base station shall set this field to the total length, in
36 octets, of Link Access Control parameters included in the
37 message, including the LAC_PARMS_LEN and RESERVED
38 fields.
39 ACC_TMO - Acknowledgment timeout.
40 The base station shall set this field to one less than the length
41 of time, in units of 20 ms, that a mobile station is to wait to
42 receive a Layer 2 acknowledgment after the end of an
43 Enhanced Access Channel transmission.
44 PROBE_PN_RAN - Time randomization for Enhanced Access Channel probes.
3-308
3GPP2 C.S0005-A v6.0
2 to 9 inclusive, so that the time randomization range to be
3 used by a mobile station is 0 to 2PROBE_PN_RAN_EACH - 1 PN
4 chips.
5 RESERVED_1 - The reserved bits
6 The base station shall set this field to ‘0000’
7 MAX_REQ_SEQ - Maximum number of access probe sequences for an Enhanced
8 Access Channel request.
10 of access probe sequences a mobile station is to transmit for
11 an Enhanced Access Channel request. The base station shall
12 set this field to a value greater than 0.
13 MAX_RSP_SEQ - Maximum number of access probe sequences for an Enhanced
14 Access Channel response.
16 of access probe sequences a mobile station is to transmit for
17 an Enhanced Access Channel response. The base station
18 shall set this field to a value greater than 0.
19 RESERVED - Reserved Bits.
20 The base station shall include as many bits as required to
21 make the length of the Link Access Control parameters record
22 an integral number of octets. The base station shall set each
23 of these bits to ‘0.
24 NUM_MODE_
25 SELECTION_ENTRIES - Number of entries of the Mode Selection Table.
26 The base station shall set this field to the number of entries of
27 the Mode Selection Table, minus one.
28 The base station shall include NUM_MODE_SELECTION_ENTRIES + 1 occurrences of the
29 following three-field record:
30 ACCESS_MODE - Access Mode used for the Enhanced Access Channel.
31 The base station shall set this field to the Access Mode value
32 shown in Table 3.7.2.3.2.33-1 corresponding to the Access
33 Mode used.
34 Table 3.7.2.3.2.33-1. Enhanced Access Modes
35
ACCESS_MODE (binary) Access Mode
000 Basic Access Mode

001 Reservation Access Mode
36 ACCESS_MODE_MIN-
3-309
3GPP2 C.S0005-A v6.0
1 _DURATION - The minimum message duration for the corresponding Access

2 Mode.
3 The base station shall set this field to the minimum message
4 duration for the corresponding Access Mode, in units of 5 ms.
5 See [3].
6 ACCESS_MODE_MAX-
7 _DURATION - The maximum message duration for the corresponding Access
8 Mode.
9 The base station shall set this field to the maximum message
10 duration for the corresponding Access Mode, in units of 5 ms.
11 See [3].
12 RLGAIN_COMMON-
13 _PILOT - Gain adjustment of the Enhanced Access Channel or Reverse
14 Common Control Channel relative to the Reverse Pilot
15 Channel.
17 be used by mobile stations in setting the power of a code
18 channel, expressed as a two’s complement value in units of
19 0.125 dB (see 2.1.2.3.3 of [2]).
20 IC_THRESH - Interference correction threshold.
21 The threshold level at which the interference correction begins
22 to be applied.
23 The base station shall set this field to the negative of the
24 interference correction threshold to be used by mobile stations
25 to determine the interference correction, in units of 1 dB
26 (see 2.1.2.3.1.2 of [2]).
27 IC_MAX - The maximum interference correction that can be applied.
28 The base station shall set this field to the maximum
29 interference correction that can be applied, in units of 1 dB
30 (see 2.1.2.3.1.2 of [2]).
31 NUM_MODE_PARM-
32 _REC - The number of mode-specific parameter records.
33 The base station shall set this field to the number of mode-
34 specific parameter records included in the message, minus
35 one.
36 The base station shall include NUM_MODE_PARM_REC + 1 occurrences of the following
37 record:
38 EACH_PARM_REC-
39 _LEN - Length of the mode-specific parameters record.
41 octets, of the mode-specific parameters record, including the
42 EACH_PARM_REC_LEN and RESERVED fields.
43 APPLICABLE_MODES - Access modes to which the access parameters specified in this
44 record apply.
3-310
3GPP2 C.S0005-A v6.0
1 The base station shall set each subfield of the

2 APPLICABLE_MODES field as follows: the base station shall
3 set the subfield to ‘1’ if the access parameters included in this
4 record are applicable to the corresponding Access Mode in
5 Table 3.7.2.3.2.33-2; otherwise, the base station shall set the
7
8 Table 3.7.2.3.2.33-2. Applicable Modes
ACC_MODE_1 1 Basic Access Mode

ACC_MODE_2 1 Reservation Access Mode
RESERVED 6
10 EACH_NOM_PWR - Nominal transmit power offset for the Enhanced Access

11 Channels.
13 be used by a mobile station in the open loop power estimate,
15 (see [2]).
16 EACH_INIT_PWR - Initial power offset for the Enhanced Access Channels.
18 be used by a mobile station in the open loop power estimate
19 for the initial transmission on an Enhanced Access Channel,
20 expressed as a two’s complement value in units of 1 dB (see
21 [2]).
22 EACH_PWR_STEP - Power increment for the Enhanced Access Channels.
23 The base station shall set this field to the value by which a
24 mobile station is to increase their transmit power between
25 successive access probes in an access probe sequence, in
26 units of 1 dB.
27 EACH_NUM_STEP - Number of access probes.
29 maximum number of access probes a mobile station is to
30 transmit in a single access probe sequence.
31 EACH_PREAMBLE-
32 _ENABLED - Preamble enabled indicator for the Enhanced Access Channel.
33 The base station shall set this field to ‘1’ if EACH preambles
34 related information is included in this message; otherwise, the
36 EACH_PREAMBLE-
37 _NUM_FRAC - The number of fractional preambles on the Enhanced Access
38 Channels.
3-311
3GPP2 C.S0005-A v6.0
1 If EACH_PREAMBLE_ENABLED is set to ‘1’, the base station

2 shall set this field to the number of fractional preambles
3 minus one on the Enhanced Access Channels; otherwise, the
5 EACH_PREAMBLE-
6 _FRAC_DURATION - Fractional preamble duration on the Enhanced Access
7 Channels.
9 shall set this field to the fractional preamble duration minus
10 one on an Enhanced Access Channel, in units of 1.25 ms;
12 EACH_PREAMBLE-
13 _OFF_DURATION - Fractional preamble gated-off duration on the Enhanced
14 Access Channels.
16 shall set this field to the fractional preamble gated-off
17 duration (in units of 1.25 ms) after the transmission of each
18 fractional preamble on an Enhanced Access Channel;
20 EACH_PREAMBLE-
21 _ADD_DURATION - Additional preamble duration on the Enhanced Access
22 Channels.
24 shall set this field to the additional preamble duration on an
25 Enhanced Access Channel, in units of 1.25 ms; otherwise, the
27 EACH_ACCESS-
28 _THRESH - Pilot Ec/Io threshold for transmission on the Enhanced
29 Access Channels.
31  - 20 × log10 pilot_threshold 
32 where pilot_threshold is the pilot Ec/Io threshold below which

33 the mobile station is not to transmit a probe on an Enhanced
34 Access Channel.
37 EACH_PROBE_BKOFF - Enhanced Access Channel probe backoff range.
39 maximum number of slots a mobile station is to delay due to
40 random backoff between consecutive enhanced access probes.
3-312
3GPP2 C.S0005-A v6.0
1 EACH_BKOFF - Enhanced Access Channel probe sequence backoff range.

3 maximum number of slots a mobile station is to delay due to
4 random backoff between successive enhanced access probe
5 sequences and before the first enhanced access probe
6 sequence of a response access.
7 EACH_SLOT - Slot duration for the Enhanced Access Channels.
8 The base station shall set this field to N where the slot
9 duration of the Enhanced Access Channel is (N+1) × 1.25 ms.
10 The base station shall set this field to a value between 0 and
11 63.
12 EACH_SLOT_OFFSET1 - First slot offset for the Enhanced Access Channels.
13 The base station shall set this field so that the Enhanced
14 Access Channel has a slot offset equal to (EACH_ID ×
15 EACH_SLOT_OFFSET2 + EACH_SLOT_OFFSET1) mod
16 (EACH_SLOT+1), where EACH_ID is the Enhanced Access
17 Channel Index. The base station shall set this field to a value
18 between 0 and 63, in units of 1.25 ms.
19 EACH_SLOT_OFFSET2 - Relative slot offset for the Enhanced Access Channels.
20 The base station shall set this field so that the Enhanced
21 Access Channel has a slot offset equal to (EACH_ID ×
22 EACH_SLOT_OFFSET2 + EACH_SLOT_OFFSET1) mod
23 (EACH_SLOT+1), where EACH_ID is the Enhanced Access
24 Channel Index. The base station shall set this field to a value
25 between 0 and 63, in units of 1.25 ms.
27 The base station shall include as many bits as required to
28 make the length of the mode-specific parameters record an
29 integral number of octets. The base station shall set each of
30 these bits to ‘0.
31
32 BA_PARMS_LEN - Length of Basic Access Mode parameter record.

34 octets, of Basic Access Mode parameters record included in
35 the message, inexcluding the BA_PARMS_LEN andbut
36 including the RESERVED fields. If there are no fields other
37 than the BA_PARMS_LEN in this record, the base station shall
39 NUM_EACH_BA - Number of Enhanced Access Channels used for the Basic
40 Access Mode.
41 If BA_PARMS_LEN is equal to ‘000’, the base station shall
42 omit this field; otherwise, Tthe base station shall include this
43 field and set this fieldit to the number of Enhanced Access
44 Channels used for the Basic Access mode minus one.
45 EACH_BA_RATES-
3-313
3GPP2 C.S0005-A v6.0
1 _SUPPORTED - Supported rate words for the Basic Access mode on the
2 Enhanced Access Channels.
5 field and set each subfield of the
6 EACH_BA_RATES_SUPPORTED field as follows: the base
7 station shall set the subfield to ‘1’ if the corresponding mode
8 in Table 3.7.2.3.2.33-3 is allowed; otherwise the base station
10
11 Table 3.7.2.3.2.33-3. EACH and RCCCH Data Rate and Frame Size
RATE_SIZE_1 1 9600 bps, 20 ms frame size

RESERVED 2 Reserved
12

15 omit this field; otherwise, Tthe base station shall include as
16 many bits as required to make the length of the Basic Access
17 Mode record (excluding the BA_PARMS_LEN field but
18 including the RESERVED field) an integral number of octets.
19 The base station shall set each of these bits to ‘0’.
20
21 RA_PARMS_LEN - Length of Reservation Access Mode parameters record.

23 octets, of Reservation Access Mode parameters record
24 included in the message, inexcluding the RA_PARMS_LEN
25 andbut including the RESERVED fields.
26 NUM_EACH_RA - Number of Enhanced Access Channels used for the
27 Reservation Access Mode.
28 If RA_PARMS_LEN is equal to ‘00000’, the base station shall
30 field and set this fieldit to the number of Enhanced Access
31 Channels used for the Reservation Access mode minus one.
32 NUM_CACH - Number of Common Assignment Channels.
3-314
3GPP2 C.S0005-A v6.0

3 field and set this fieldit to the number of Common Assignment
4 Channels supported by the system minus one.
5 CACH_CODE_RATE – Code Rate for the Common Assignment Channels.
9 If the CACH is operating in Spreading Rate 1, the base station
10 shall set this field to ‘0’ if the CACH Code Rate is 1/4 (see
11 3.1.3.1.2.1 of [2]). The base station shall set this field to ‘1’ if
12 the CACH Code Rate is 1/2 (see 3.1.3.1.2.1 of [2]).
13 If the CACH is operating in Spreading Rate 3, the base station
15 If RA_PARMS_LEN is not equal to ‘00000’, Tthe base station shall include (NUM_CACH + 1)
16 occurrences of the following one field record:
17 CACH_CODE_CHAN - Code channel index for the Common Assignment Channel.
20 is to use on the Common Assignment Channel.
21
22 NUM_RCCCH - Number of Reverse Common Control Channels used for the

23 Reservation Mode.
26 field and set this fieldit to the number of Reverse Common
27 Control Channels used for the Reservation mode minus one.
28 RCCCH_RATES-
29 _SUPPORTED - Supported rate words on the Reverse Common Control
30 Channels.
33 field and set each bit of the RCCCH_RATES_SUPPORTED field
34 as follows: the base station shall set the bit to ‘1’ if the
35 corresponding mode in Table 3.7.2.3.2.332-3 is allowed;
36 otherwise the base station shall set the bit to ‘0’.
37 RCCCH_PREAMBLE-
38 _ENABLED - Preamble enabled indicator for the Reverse Common Control
39 Channel.
42 field and set this fieldit as follows:
43 to ‘1’ iIf RCCCH preambles related information is included in
3-315
3GPP2 C.S0005-A v6.0
1 RCCCH_PREAMBLE-
2 _NUM_FRAC - Number of fractional preambles on the Reverse Common
3 Control Channels.
4 If RCCCH_PREAMBLE_ENABLED is included and is set to ‘1’,
5 the base station shall set this field to the number of fractional
6 preambles minus one on the Reverse Common Control
7 Channels; otherwise, the base station shall omit this field.
8 RCCCH_PREAMBLE-
9 FRAC_DURATION - Fractional preamble duration for the Reverse Common Control
10 Channels.
12 the base station shall set this field to the fractional preamble
13 duration minus one on a Reverse Common Control Channel,
14 in units of 1.25 ms; otherwise, the base station shall omit this
15 field.
16 RCCCH_PREAMBLE_-
17 OFF_DURATION - Fractional preamble gated-off duration on Reverse Common
18 Control Channels.
20 the base station shall set this field to the fractional preamble
21 gated-off duration (in units of 1.25 ms) after the transmission
22 of each fractional preamble on a Reverse Common Control
23 Channel; otherwise, the base station shall omit this field.
24 RCCCH_PREAMBLE_-
25 ADD_DURATION - Additional preamble duration on the Reverse Common Control
26 Channels.
28 the base station shall set this field to the additional preamble
29 duration on a Reverse Common Control Channel, in units of
30 1.25 ms; otherwise, the base station shall omit this field.
31 RCCCH_SLOT - Slot interval for the Reverse Common Control Channels.
34 field and set this fieldit to N where the slot duration on the
35 Reverse Common Control Channel is (N+1) × 1.25 ms. The
36 base station shall set this field to a value between 0 and 63.
37 RCCCH_SLOT_OFFSET1 - First slot offset for the Reverse Common Control Channels.
40 field and set this fieldit so that Reverse Common Control
41 Channel has a slot offset equal to (RCCCH_ID ×
42 RCCCH_SLOT_OFFSET2 + RCCCH_SLOT_OFFSET1) mod
43 (RCCCH_SLOT+1), where RCCCH_ID is the Reverse Common
44 Control Channel Index. The base station shall set this field to
45 a value between 0 and 63, in units of 1.25 ms.
3-316
3GPP2 C.S0005-A v6.0
1 RCCCH_SLOT_OFFSET2 - Second slot offset for the Reverse Common Control Channels.
4 field and set this fieldit so that Reverse Common Control
5 Channel has a slot offset equal to (RCCCH_ID ×
6 RCCCH_SLOT_OFFSET2 + RCCCH_SLOT_OFFSET1) mod
7 (RCCCH_SLOT+1), where RCCCH_ID is the Reverse Common
8 Control Channel Index. The base station shall set this field to
9 a value between 0 and 63, in units of 1.25 ms.
10 RCCCH_NOM_PWR - Nominal transmit power offset for the Reverse Common
11 Control Channels.
14 field and set this fieldit to the correction factor to be used by a
15 mobile station in the open loop power estimate, expressed as a
16 two’s complement value in units of 1 dB (see [2]).
17 RCCCH_INIT_PWR - Initial power offset for the Reverse Common Control Channels.
20 field and set this fieldit to the correction factor to be used by a
21 mobile station in the open loop power estimate for the initial
22 transmission on a Reverse Common Control Channel,
23 expressed as a two’s complement value in units of 1 dB (see
24 [2]).
25 RA_PC_DELAY - Power control delay for the Reverse Common Control Channel.
28 field and set this fieldit to the number of power control bits
29 the mobile is to disregard after initiating transmission on a
30 Reverse Common Control Channel.
31 EACAM_CACH_DELAY - Maximum time after an Enhanced Access Channel header
32 transmission for receiving a response on the Common
33 Assignment Channel when Reverse Common Control Channel
34 soft handoff has not been requested.
37 field and set this fieldit to the number of complete Common
38 Assignment Channel frames minus one, from the end of the R-
39 EACH Header, for which a mobile station is to wait for the
40 Early Acknowledgement Channel Assignment Message if the
41 mobile station has not requested Reverse Common Control
42 Channel soft handoff .
43 RCCCH_HO-
44 _SUPPORTED - Reverse Common Control Channel handoff supported
45 indicator.
3-317
3GPP2 C.S0005-A v6.0

4 The base station shall set this field to ‘1’ if Reverse Common
5 Control Channel handoff is supported by the base station;
7 RCCCH_HO_THRESH - Reverse Common Control Channel soft handoff threshold.
8 If RCCCH_HO_SUPPORTED is included and is set to ‘1’, the

9 base station shall include this field; otherwise the base station
10 shall omit this field.set to ‘0’, the base station shall omit this
11 field; otherwise, the base station shall set this field to:
12 If included, the base station shall set this field to:

13  - 20 × log10 pilot_threshold 
14 where pilot_threshold is the pilot Ec/Io threshold used to

15 determine whether the mobile station requests Reverse
16 Common Control Channel in soft handoff.
17 This is a positive value in units of 0.5 dB.

18 EACAM_PCCAM_DELAY - Maximum time after an Enhanced Access Channel header
19 transmission for receiving a response on the Common
20 Assignment Channel when Reverse Common Control Channel
21 soft handoff has been requested.
22 If RCCCH_HO_SUPPORTED is included and is set to ‘1’, the
23 base station shall include this field; otherwise the base station
24 shall omit this field.set to ‘0’, the base station shall omit this
25 field; otherwise;
26 If included, the base station shall set this field to the number
27 of complete Common Assignment Channel frames minus one,
28 from the end of the R-EACH Header, for which a mobile
29 station is to wait for the Early Acknowledgement Channel
30 Assignment Message and Power Control Channel Assignment
31 Message if the mobile station has requested Reverse Common
32 Control Channel soft handoff (see [3]).
33 NUM_CPCCH - Number of Common Power Control Channels.
36 field and set this fieldit to the number of Common Power
37 Control Channels supported minus one.
38 CPCCH_RATE - Power control rate for the Common Power Control Channels.
41 field and set this fieldit to the value shown in Table
42 3.7.2.3.2.33-4 corresponding to the power control rate for the
43 Common Power Control Channels.
44
3-318
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.33-4. CPCCH Power Control Rate
CPCCH_RATE (Binary) Power Control Rate
00 200 bps
01 400 bps
10 800 bps
11 Reserved
3 If RA_PARMS_LEN is not equal to ‘00000’, Tthe base station shall include (NUM_CPCCH +
4 1) occurrences of the following one field record:
5 CPCCH_CODE_CHAN - Code channel index for the Common Power Control Channel.
8 is to use on the Common Power Control Channel.
9
10 NUM_PCSCH_RA - Number of Power Control Subchannels used for the

11 Reservation Access Mode.
14 field and set this fieldit to the number of Power Control
15 Subchannels used for the Reservation Access Mode minus
16 one.
19 omit this field; otherwise, Tthe base station shall include as
20 many bits as required to make the length of the Reservation
21 Access Mode record (excluding the RA_PARMS_LEN but
22 including the RESERVED field) an integral number of octets.
23 The base station shall set each of these bits to ‘0’.
24 ACCT_INCL - Access Control based on Call Type (ACCT) information
26 If the base station enables ACCT for at least one service
27 option, the base station shall set this field to ‘1’; otherwise,
29 If the base station sets this field to ‘1’, then the base station
30 shall also set at least one of ACCT_SO_INCL or
31 ACCT_SO_GRP_INCL to ‘1’.
32 ACCT_INCL_EMG - Access Control based on Call Type (ACCT) includes emergency
33 calls indicator.
3-319
3GPP2 C.S0005-A v6.0
2 is not to apply ACCT to a call that is recognized by the mobile
3 station to be an emergency call; otherwise, the base station
5 ACCT_AOC_
6 BITMAP_INCL - Access Control based on Call Type (ACCT) access overload
7 class bitmap included indicator.
11 The base station shall set this field to ‘0’ if all mobile stations
12 are to apply ACCT regardless of their access overload classes;
13 otherwise, the base station shall set this field to ‘1’ to indicate
14 that the mobile station is to apply ACCT according to its
16 ACCT_SO_INCL - Access Control based on Call Type (ACCT) service option
22 occurrence of the ACCT_SO field is included in this message;
24 NUM_ACCT_SO - Number of service options for Access Control based on Call
25 Type (ACCT).
26 If ACCT_SO_INCL is not included, or is included and set to ‘0’,
27 then the base station shall omit this field; otherwise, the base
28 station shall include this field and set it to one less than the
29 number of occurrences of the ACCT_SO field included in this
30 message.
31 If ACCT_SO_INCL is included and set to ‘1’, then the base station shall include
32 NUM_ACCT_SO + 1 occurrences of the following variable-field record:
34 class bitmap.
39 3.7.2.3.2.2-1.
40 The base station shall set a subfield to ‘1’ to indicate that

41 mobile stations having the corresponding access overload
42 class are not permitted to perform access attempts using the
43 associated service option ACCT_SO; otherwise, the base
44 station shall set the subfield to ‘0’.
3-320
3GPP2 C.S0005-A v6.0
1 ACCT_SO - Access Control based on Call Type (ACCT) service option

2 number.
4 option number (as specified in [30]) that has ACCT enabled.
5 ACCT_SO_GRP_INCL - Access Control based on Call Type (ACCT) service option group
11 occurrence of the ACCT_SO_GRP field is included in this
13 NUM_ACCT_SO_GRP - Number of service option groups for Access Control based on
14 Call Type (ACCT).
15 If ACCT_SO_GRP_INCL is not included, or is included and set
16 to ‘0’, then the base station shall omit this field; otherwise, the
17 base station shall include this field and set it to one less than
18 the number of occurrences of the ACCT_SO_GRP field
20 If ACCT_SO_GRP_INCL is included and set to ‘1’, then the base station shall include
21 NUM_ACCT_SO_GRP + 1 occurrences of the following variable-field record:
23 class bitmap.
28 3.7.2.3.2.2-1. The base station shall set a subfield to ‘1’ to
29 indicate that mobile stations having the corresponding access
30 overload class are not permitted to perform access attempts
31 using a service option specified by the associated
32 ACCT_SO_GRP field; otherwise, the base station shall set the
34 ACCT_SO_GRP - Access Control based on Call Type (ACCT) service option group
35 number.
37 option group number (as specified in [30]) whose members all
38 have ACCT enabled.
3-321
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.34 Universal Neighbor List Message
2 MSG_TAG: UNLM
Field Length (bits)
PILOT_PN 9
CONFIG_MSG_SEQ 6
NUM_RADIO_INTERFACE 4
NUM_RADIO_INTERFACE occurrences of the following
record:
RADIO_INTERFACE_TYPE 4
RADIO_INTERFACE_LEN 8
Radio Interface Type-specific fields 8
× RADIO_INTERFACE_
LEN

8 The base station shall set this field to CONFIG_SEQ (see
9 3.6.2.2).
10 NUM_RADIO-
11 _INTERFACE - Number of interface types.
12 The base station shall set this field to the number of radio
13 interface types for which neighbors are included in this
14 message.
15 The base station shall include NUM_RADIO_INTERFACE occurrences of the following
16 record, one occurrence for each radio interface for which neighbors are included in this
17 message.
18 RADIO-
19 _INTERFACE_TYPE - The radio interface type.
20 The base station shall set this field to the radio interface type
21 of this record as specified in Table 3.7.2.3.2.34-1.
3-322
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.34-1. Radio Interface Type
RADIO_INTERFACE_TYPE Descriptions
(binary)
0000 MC system
0001 Analog system
0010-1111 Reserved
3 RADIO-
4 _INTERFACE_LEN - The length of the Radio Interface Type-specific fields.
6 the Radio Interface Type-specific fields of this record.
7 If RADIO_INTERFACE_TYPE is equal to ‘0000’, the base station shall include the following
8 fields:
3-323
3GPP2 C.S0005-A v6.0
Field Length (bits)
PILOT_INC 4
NGHBR_SRCH_MODE 2
SRCH_WIN_N 0 or 4
SRCH_OFFSET_INCL 1
FREQ_FIELDS_INCL 1
USE_TIMING 1
NGHBR_SET_ENTRY_INFO 1
NGHBR_SET_ACCESS_INFO 1
NUM_NGHBR 6
NUM_NGHBR occurrences of the following subrecord:
NGHBR_CONFIG 3
NGHBR_PN 9
BCCH_SUPPORT 0 or 1
RECORD_LEN 0 or 3
3-324
3GPP2 C.S0005-A v6.0
Field Length (bits)
FREQ_INCL 0 or 1
NGHBR_BAND 0 or 5
NGHBR_FREQ 0 or 11
TIMING_INCL 0 or 1
ACCESS_ENTRY_HO 0 or 1
ACCESS_HO_ALLOWED 0 or 1

3 A mobile station searches for Remaining-Set pilots at pilot PN
12 15 inclusive.
16
3-325
3GPP2 C.S0005-A v6.0
1 Table 3.7.2.3.2.34-2. Search Mode Field
Value

10 Search windows

5 the base station shall include the field SRCH_WIN_N and shall
10 be used by mobile stations for the Neighbor Set.
16 FREQ_FIELDS_INCL - Frequency fields included.
17 If frequency fields are included in this message, the base
24 GLOBAL_TIMING-
27 field GLOBAL_TIMING_INCL and shall set this field as
29 field.
34 GLOBAL_TX-
3-326
3GPP2 C.S0005-A v6.0

8 greater.
9 GLOBAL_TX-
17 NGHBR_SET-
18 _ENTRY_INFO - Neighbor Set access entry handoff information included
19 indicator.
21 Set access entry handoff, the base station shall set this field
23 NGHBR_SET-
24 _ACCESS_INFO - Neighbor Set access handoff included indicator.
26 Set access handoff or access probe handoff, the base station
27 shall set this field to ‘1’, otherwise, the base station shall set
32
33 The base station shall include one occurrence of the following subrecord for each pilot that
34 a mobile station is to place in its Neighbor Set.
35
3-327
3GPP2 C.S0005-A v6.0

4 neighbor.
Value
Primary Broadcast Control Channel/Forward Common Control Channels as

to this CDMA frequency assignment with the same number of Forward
Common Control Channels, and the neighbor frequency is given as follows:


The position of the neighbor CDMA frequency assignment in the Extended

CDMA Channel List Message transmitted by the neighbor base station is the
same as the position of this current CDMA frequency assignment in the
station.
The rate, code rate, and code channel of the Primary Broadcast Control
Channel on this corresponding CDMA frequency are the same values as the
current ones.
The rate, code rate, and code channel of the corresponding Forward Common
Control Channel on this corresponding CDMA frequency are the same values
as the current ones.
3-328
3GPP2 C.S0005-A v6.0
001 The neighbor base station does not have any frequencies with Primary
Broadcast Control Channel/Forward Common Control Channel.
The neighbor base station has the same number of frequencies having Paging
Channels as the current base station has frequencies having Primary
Broadcast Control Channel/Forward Common Control Channel.

to this CDMA frequency assignment but possibly with a different number of
Paging Channels, and the neighbor frequency is given as follows:



station.

Primary Paging Channel, at 9600 bps.
Primary Broadcast Control Channel/Forward Common Control Channel as
The neighbor base station has a Primary Broadcast Control Channel on the
following frequency:
Primary Broadcast Control Channel on the first CDMA Channel listed
in the Extended CDMA Channel List Message transmitted by the
current base station.
Primary Broadcast Control Channel on the CDMA frequency
assignment given by NGHBR_BAND and NGHBR_FREQ.
current ones.
3-329
3GPP2 C.S0005-A v6.0

Channel.
Primary Broadcast Control Channel/Forward Common Control Channel as

to this CDMA frequency assignment with a Primary Broadcast Control
Channel, and the neighbor CDMA frequency is given as follows:



station.
current ones.
101-111 Reserved.

5 BCCH_SUPPORT - BCCH support indicator.
6 If the NGHBR_CONFIG field is not set to ‘011’, the base

7 station shall omit this field; otherwise, the base station shall
3-330
3GPP2 C.S0005-A v6.0
1 If this neighbor base station supports Broadcast Control

15
16 Table 3.7.2.3.2.34-4. Neighbor Pilot Record Types
NGHBR_PILOT_REC_TYPE

Diversity
Diversity
3X Common Pilot 011
All other NGHBR_PILOT_REC_TYPE values are reserved
17

19 omit this field.
25 omit this field.
31 omit this field.
3-331
3GPP2 C.S0005-A v6.0
3 fields:
Field Length (bits)
TD_POWER_LEVEL 2
TD_MODE 2
RESERVED 4

9 in Table 3.7.2.3.2.26-4.
16 fields:
Field Length (bits)
QOF 2
WALSH_LENGTH 3
17

25 Auxiliary pilot.
3-332
3GPP2 C.S0005-A v6.0
4 fields:
Field Length (bits)
QOF 2
WALSH_LENGTH 3
TD_MODE 2

8 Diversity Pilot.
19 AUX_ TD-
31 fields:
3-333
3GPP2 C.S0005-A v6.0
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3

20
22 fields:
3-334
3GPP2 C.S0005-A v6.0
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
QOF 2
WALSH_LENGTH 3
ADD_INFO_INCL1 1
QOF1 0 or 2
WALSH_LENGTH1+6
ADD_INFO_INCL2 1
QOF2 0 or 2
WALSH_LENGTH2+6

19 orthogonal function (see Table 3.1.3.1.12-2 of [2] on the
3-335
3GPP2 C.S0005-A v6.0

8 primary pilot.
15 to ‘1’.
20 follows:
22 orthogonal function (see Table 3.1.3.1.12-2 of [2] on the lower
28 follows:
33 SR3 frequencies.
38 follows:
3-336
3GPP2 C.S0005-A v6.0

5 to ‘1’.
10 follows:
18 follows:
23 SR3 frequencies.
28 follows:
35

38 the base station shall include the field SEARCH_PRIORITY
39 and shall set this field as described below; otherwise, the base
41 The base station shall set this field to the search priority for
42 the Pilot Channel corresponding to NGHBR_PN. The base
44 3.7.2.3.2.34-4.
45
3-337
3GPP2 C.S0005-A v6.0

(binary)
00 Low
01 Medium
10 High
11 Very High

5 the base station shall include the field SRCH_WIN_NGHBR
6 and shall set this field as described below; otherwise, the base
10 be used by mobile stations for this neighbor.
11 SRCH_OFFSET_NGHBR - Neighbor pilot channel search window size offset.
13 shall include the field SRCH_OFFSET_NGHBR and shall set
14 this field as described below; otherwise, the base station shall
15 omit this field.
17 Table 2.6.6.2.1-2 corresponding to the search window offset to
18 be used by mobile stations for this neighbor.
20 If FREQ_FIELDS_INCL is set to ‘1’, the base station shall
21 include the field FREQ_INCL and shall set this field as
23 field.
27 not included in this assignment record, the base station shall
28 set this bit to ‘0’.
30 If the FREQ_INCL field is included and is set to ‘1’, the base
31 station shall include the field NGHBR_BAND and shall set this
32 field as described below; otherwise, the base station shall omit
33 this field.
3-338
3GPP2 C.S0005-A v6.0
2 as specified in [30], corresponding to the CDMA frequency
3 assignment for the CDMA Channel containing the Broadcast
4 Control Channel/Forward Common Control Channel the
5 mobile station is to search.
7 If the FREQ_INCL field is omitted or is set to ‘0’, the base
9 If the FREQ_INCL field is included and is set to ‘1’ and the
13 the CDMA frequency assignment for the CDMA Channel
14 containing the Broadcast Control Channel/Forward Common
15 Control Channel the mobile station is to search.
16 If the FREQ_INCL field is included and is set to ‘1’ and the
20 the center SR3 frequency assignment containing the
21 Broadcast Control Channel/Forward Common Control
22 Channel the mobile station is to search.
32 shall include the field NGHBR_TX_OFFSET and shall set this
34 this field.
39 occurs when t/4 mod (16384)= 0.
43 include the field NGHBR_TX_DURATION and shall set this
45 this field.
3-339
3GPP2 C.S0005-A v6.0
4 greater.
8 include the field NGHBR_TX_PERIOD and shall set this field
10 field.
13 ACCESS_ENTRY_HO - Access entry handoff permitted when entering the System
14 Access State.
15 If NGHBR_SET_ENTRY_INFO is equal to ‘1’, the base station
16 shall include the field ACCESS_ENTRY_HO and shall set this
18 this field.
20 is permitted to perform an access entry handoff to the base
21 station associated with the corresponding pilot between the
22 time it receives a message on the Paging Channel when in the
23 Mobile Station Idle State and it enters the System Access State
24 to respond to the message; otherwise, the base station shall
26 ACCESS_HO_ALLOWED - Access handoff and access probe handoff permitted for the
27 corresponding pilot while in the System Access State.
28 If NGHBR_SET_ACCESS_INFO is equal to ‘1’, the base station
29 shall include the field ACCESS_HO_ALLOWED and shall set
30 this field as described below; otherwise, the base station shall
31 omit this field.
33 is permitted to perform an access handoff or access probe
34 handoff to the base station associated with the corresponding
35 pilot when the mobile station is in the System Access State
36 (see 2.6.3.1.8 and 2.6.3.1.9); otherwise, the base station shall
40 make the length of the entire RADIO_INTERFACE_TYPE
41 record equal to an integer number of octets. The base station
42 shall set these bits to ’0’.
43 If RADIO_INTERFACE_TYPE is equal to ‘0001’, the base station shall include the following
44 fields:
3-340
3GPP2 C.S0005-A v6.0
Field Length (bits)
NUM_ANALOG_NGHBR 3
NUM_ANALOG_NGHBR occurrences of the following
subrecord:
BAND_CLASS 5
SYS_A_B 2
2 NUM_ANALOG_NGHBR - Number of neighboring analog systems.

4 neighboring analog systems included in the message.
5
6 The base station shall include one occurrence of the following subrecord for each
7 neighboring analog system included in the message:

11 SYS_A_B - System A/B.
12 If BAND_CLASS is set to ‘00000’ or to ‘00011’, the base station
13 shall set this field to the value shown in Table 3.7.2.3.2.34-5
14 corresponding to the availability of neighboring analog
15 systems; otherwise, the base station shall set this field to ‘00’.
16 Table 3.7.2.3.2.34-5. Cellular System A/B
Cellular System A/B Value

(Binary)
RESERVED 00
System A 01
System B 10
System A and B 11

19 make the length of the entire RADIO_INTERFACE_TYPE
20 record equal to an integer number of octets. The base station
21 shall set these bits to ’0’.
22
3-341
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.35 Security Mode Command Message
2 MSG_TAG: SMCM
Field Length (bits)
C_SIG_ENCRYPT_MODE 3
USE_NEW_KEY 0 or 1
ENC_KEY_SIZE 0 or 3
KEY_SEQ 0 or 4
4 C_SIG_ENCRYPT_MODE - Common channel encryption mode indicator.

5 The base station shall set it this field to the common channel
6 signaling message encryption mode, as shown in Table 3.7.4.5-1.
8 If SIG_ENCRYPT_MODE is equal to ‘001’, the base station shall
12 station, and to ‘1’ to indicate that the new encryption key is to be
14 ENC_KEY_SIZE - Key sSize used for user information and signaling encryption
15 If C_SIG_ENCRYPT_MODE is equal to ‘001’,USE_NEW_KEY is
16 included and is set to ‘0’, the base station shall omit this field;
17 otherwise, the base station shall include this field and set this
18 field to the encryption key_-size for user information
19 encryption and signaling encryption according to as shown in
20 Table 3.7.4.5-2; otherwise, the base station shall omit this
21 field.
27 station.
3-342
3GPP2 C.S0005-A v6.0
1 3.7.2.3.2.36 Universal Page Message
2 MSG_TAG: UPM
3 When Layer 3 at the base station sends a PDU corresponding to the Universal Page Message
4 to Layer 2, it also sends the UPM Common fields to Layer 2. These UPM Common fields
5 and PDUs are used by Layer 2 to assemble the Layer 2 PDU or PDUs corresponding to the
6 Universal Page Message (see 3.1.2.3 of [4]).
7 UPM Common Fields:
Field Length (bits)
CONFIG_MSG_SEQ 6
ACC_MSG_SEQ 6
READ_NEXT_SLOT 1
READ_NEXT_SLOT_BCAST 1
10 PDU Format for a mobile station-addressed page:
11
Field Length (bits)
SERVICE_OPTION 16
ADD_MS_RECORD 0 or 8 × EXT_MS_SDU-
_LENGTH (see [4])
12
13 PDU Format for a mobile station-directed message announcement:
14
Field Length (bits)
- 0
15
16 PDU Format for an enhanced broadcast page:
17
3-343
3GPP2 C.S0005-A v6.0
Field Length (bits)
BCCH_INDEXBCN 3
TIME_OFFSET 10
REPEAT_TIME_OFFSET 0 or 5
ADD_BCAST_RECORD 0 or 8 × EXT_BCAST_-
SDU_LENGTH (see [4])

4 (see 3.6.2.2).
7 (see 3.6.2.2).
8 READ_NEXT_SLOT - Pages carried into next slot indicator.
10 operating in the slotted mode and active in this slot, are
11 included in this slot, the base station shall set this field to ‘0’;
13 READ_NEXT-
14 _SLOT_BCAST - Enhanced Broadcast Pages carried into next slot indicator.
15 If all enhanced broadcast pages directed to mobile stations
16 operating in the slotted mode and active in this slot to receive
17 enhanced broadcast pages are included in this slot, the base
21 The base station shall set this field to the service option code
22 shown in [30]TSB58-B, corresponding to the requested service
23 option.
24 ADD_MS_RECORD - Additional mobile station-addressed information record.
26 EXT_MS_SDU_LENGTH_INCL (see 3.1.2.3.1.8 of [4]) is set to
27 ‘0’; otherwise, the base station shall include
28 EXT_MS_SDU_LENGTH (see 3.1.2.3.1.8 of [4]) octets in this
29 field.
30 BCCH_INDEX BCN - BCCH time indexBroadcast Control Channel Number.
31 The base station shall set this field to the index of the BCCH
32 to which the mobile station is being redirected.
33 TIME_OFFSET - BCCH offset.
3-344
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to one less than the time
2 offset, in units of 40 ms, from the beginning of the slot in
3 which this message began to the beginning of the Broadcast
5 directed.
6 REPEAT_TIME-
7 _OFFSET - BCCH offset of repeat.
8 If EXT_BCAST_SDU_LENGTH_IND (see [4]) is set to ‘01’ or ‘11’

10 one less than the time offset, in units of 40 ms, from the time
11 specified by TIME_OFFSET to the beginning of the Broadcast
13 directed for a repeat of the broadcast message. Otherwise, the
15 ADD_BCAST_RECORD - Additional broadcast information record.
17 EXT_BCAST_SDU_LENGTH_IND (see 3.1.2.3.1.8 of [4]) is set
18 to ‘00’ or ‘01’; otherwise, the base station shall include
19 EXT_BCAST_SDU_LENGTH (see 3.1.2.3.1.8 of [4]) octets in
20 this field.
3-345
3GPP2 C.S0005-A v6.0
1 3.7.3 f-dsch
2 During Traffic Channel operation, the base station sends signaling messages to the mobile
3 station using the f-dsch.
4 3.7.3.1 Reserved
5 3.7.3.2 Reserved
3-346
3GPP2 C.S0005-A v6.0
1 3.7.3.3 PDU Formats on the f-dsch
2 The signaling messages sent over the f-dsch are summarized in Table 3.7.3.3-1.
3
4 Table 3.7.3.3-1. f-dsch Messages (Part 1 of 2)
Section
Message Name MSG_TAG Number
Order Message ORDRM 3.7.3.3.2.1

Authentication Challenge Message AUCM 3.7.3.3.2.2
Alert With Information Message AWIM 3.7.3.3.2.3
Analog Handoff Direction Message AHDM 3.7.3.3.2.6
In-Traffic System Parameters Message ITSPM 3.7.3.3.2.7
Neighbor List Update Message NLUM 3.7.3.3.2.8
Send Burst DTMF Message BDTMFM 3.7.3.3.2.9
Power Control Parameters Message PCNPM 3.7.3.3.2.10
Retrieve Parameters Message RTPM 3.7.3.3.2.11
Set Parameters Message STPM 3.7.3.3.2.12
SSD Update Message SSDUM 3.7.3.3.2.13
Flash With Information Message FWIM 3.7.3.3.2.14
Mobile Station Registered Message MSRM 3.7.3.3.2.15
Status Request Message STRQM 3.7.3.3.2.16
Extended Handoff Direction Message EHDM 3.7.3.3.2.17
Service Request Message SRQM 3.7.3.3.2.18
Service Response Message SRPM 3.7.3.3.2.19
Service Connect Message SCM 3.7.3.3.2.20
Service Option Control Message SOCM 3.7.3.3.2.21
TMSI Assignment Message TASM 3.7.3.3.2.22
Service Redirection Message SRDM 3.7.3.3.2.23
Supplemental Channel Assignment Message SCAM 3.7.3.3.2.24
Power Control Message PCNM 3.7.3.3.2.25
3-347
3GPP2 C.S0005-A v6.0
1 Table 3.7.3.3-1. f-dsch Messages (Part 2 of 2)
Section
Message Name MSG_TAG Number
Extended Neighbor List Update Message ENLUM 3.7.3.3.2.26

Candidate Frequency Search Request Message CFSRQM 3.7.3.3.2.27
Candidate Frequency Search Control Message CFSCNM 3.7.3.3.2.28
Power Up Function Message PUFM 3.7.3.3.2.29
Power Up Function Completion Message PUFCM 3.7.3.3.2.30
General Handoff Direction Message GHDM 3.7.3.3.2.31
Resource Allocation Message RAM 3.7.3.3.2.32
Resource Allocation Mini Message RAMM 3.7.3.3.2.33
Extended Release Message ERM 3.7.3.3.2.34
Extended Release Mini Message ERMM 3.7.3.3.2.35
Universal Handoff Direction Message UHDM 3.7.3.3.2.36
Extended Supplemental Channel Assignment ESCAM 3.7.3.3.2.37
Message
Forward Supplemental Channel Assignment Mini FSCAMM 3.7.3.3.2.38
Message
Reverse Supplemental Channel Assignment Mini RSCAMM 3.7.3.3.2.39
Message
Mobile Assisted Burst Operation Parameters MABOPM 3.7.3.3.2.40
Message
User Zone Reject Message UZRM 3.7.3.3.2.41
User Zone Update Message UZUM 3.7.3.3.2.42
Call Assignment Message CLAM 3.7.3.3.2.43
Extended Alert With Information Message EAWIM 3.7.3.3.2.44
Extended Flash With Information Message EFWIM 3.7.3.3.2.45
Security Mode Command Message SMCM 3.7.3.3.2.46
Base Station Status Response Message BSSRSPM 3.7.3.3.2.47
4 The following sections specify the contents of the message body for each message that may
5 be sent on the f-dsch.
3-348
3GPP2 C.S0005-A v6.0
2 MSG_TAG: ORDRM
Field Length (bits)
USE_TIME 1
ACTION_TIME 6
ORDER 6
ADD_RECORD_LEN 3
CON_REF_INCL 0 or 1
CON_REF 0 or 8
4
5 USE_TIME - Use action time indicator.

6 This field indicates whether an explicit action time is specified
7 in this order.
8 If an explicit action time can be specified for this order code,
9 as shown in Table 3.7.4-1, the base station may set this field
11 ACTION_TIME - Action time.
12 If the USE_TIME field is set to ‘1’, the base station shall set
13 this field to the System Time, in units of 80 ms (modulo 64),
14 at which the order is to take effect. If the USE_TIME field is
15 set to ‘0’ the base station shall set this field to ‘000000’.
16 ORDER - Order code.
17 The base station shall set this field to the ORDER code for this
18 type of Order Message (see 3.7.4).
21 the order-specific fields included in this message.
22 Order-specific fields - Order-specific fields.
23 The base station shall include order-specific fields as specified
24 in 3.7.4.
26 If the order carried by this message is not a Call Control order

27 (see 3.6.8), the base station shall omit this field; otherwise,
28 the base station shall include this field and set it as follows:
3-349
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to ‘1’ if the connection
5 If the CON_REF_INCL field is not included or is included but

8 value of the connection reference assigned to the service
9 option connection of the call, to which this message
10 corresponds.
3-350
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.2 Authentication Challenge Message
2 MSG_TAG: AUCM
Field Length (bits)
RANDU 24
5 RANDU - Random challenge data.

3-351
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.3 Alert With Information Message
2 MSG_TAG: AWIM
Field Length (bits)

RECORD_TYPE 8
RECORD_LEN 8
6 3.7.5.
14 in 3.7.5.
3-352
3GPP2 C.S0005-A v6.0
2 MSG_TAG: DBM
Field Length (bits)
MSG_NUMBER 8
BURST_TYPE 6
NUM_MSGS 8
NUM_FIELDS 8

CHARi 8
5 MSG_NUMBER - Message number.

6 The base station shall set this field to the number of this
8 BURST_TYPE - Data burst type.
9 The base station shall set the value of this field for the type of
10 this data burst as defined in [30]. If the base station sets this
12 this message equal to the
13 EXTENDED_BURST_TYPE_INTERNATIONAL field as described
14 in the definition of CHARi below. If the base station sets this
18 NUM_MSGS - Number of messages in the data burst stream.
20 in this data burst stream.
21 NUM_FIELDS - Number of characters in this message.
23 occurrences of the CHARi field included in this message.
26 this field. The base station shall set these fields to the
3-353
3GPP2 C.S0005-A v6.0

11 the COUNTRY_BURST_TYPE. The base station shall set the
15
Field Length (bits)

Remaining CHARi fields 8 × (NUM_FIELDS – 2)
16

19 EXTENDED_BURST_TYPE field, as shown below. The base
21 field according to the type of this data burst as defined in [30].
22
Field Length (bits)
Remaining CHARi fields 8 x (NUM_FIELDS – 2)
3-354
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.5 Reserved
2 No text.
3-355
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.6 Analog Handoff Direction Message
2 MSG_TAG: AHDM
Field Length (bits)
USE_TIME 1
ACTION_TIME 6
SID 15
VMAC 3
ANALOG_CHAN 11
SCC 2
MEM 1
AN_CHAN_TYPE 2
DSCC_MSB 1
BAND_CLASS 5
CON_REF_INCL 1
CON_REF 0 or 8
4

7 in this message.
8 If an explicit action time is specified in this message, the base
14 at which the handoff is to take effect. If the USE_TIME field is
18 number for the analog system (see [6]).
20 This field indicates the mobile station’s power level associated
21 with the designated voice channel.
22 The base shall set this field to the MAC value shown in Table
23 2.1.2-1 of [12] corresponding to the nominal power for this
24 mobile station.
3-356
3GPP2 C.S0005-A v6.0
1 ANALOG_CHAN - Analog voice channel number.

2 The base station shall set this field to the channel number of
3 the analog voice channel, as specified in Table 2.1.1-1 of [12].
5 This indicates the supervisory audio tone associated with the
6 designated analog voice channel.
7 The base station shall set this field to the SAT value shown in
8 Table 3.7.1-2 of [12] and 2.4.1 of [12].
9 If the assignment is to a narrow analog channel, the base station
10 shall set this field to the two least significant bits of the DSCC.
12 To enable analog control message encryption on the assigned
13 forward and reverse analog voice channels, the base station
14 shall set this bit to ‘1’. To disable analog control message
15 encryption, the base station shall set this bit to ‘0’.
21
22 Table 3.7.3.3.2.6-1. Analog Channel Type
Analog AN_CHAN_TYPE
Description Ch (Binary)
Wide channel on N 00
ANALOG_CHAN
Narrow channel 10 kHz below NL 01
ANALOG_CHAN
Narrow channel 10 kHz above NU 10
ANALOG_CHAN
Narrow channel centered on NM 11
ANALOG_CHAN
23
31 in [30].
3-357
3GPP2 C.S0005-A v6.0
6 If the CON_REF_INCL field is set to ‘0’, the base station shall

8 field and shall set it to the value of the connection reference
9 assigned to the service option connection of the call which is
10 to be transferred to the analog system.
3-358
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.7 In-Traffic System Parameters Message
2 MSG_TAG: ITSPM
Field Length (bits)
SID 15
NID 16
SRCH_WIN_A 4
SRCH_WIN_N 4
SRCH_WIN_R 4
T_ADD 6
T_DROP 6
T_COMP 4
T_TDROP 4
NGHBR_MAX_AGE 4
P_REV 8
SOFT_SLOPE 6
ADD_INTERCEPT 6
DROP_INTERCEPT 6
PACKET_ZONE_ID 8
EXTENSION 1
T_MULCHAN 0 or 3
BEGIN_PREAMBLE 0 or 3
RESUME_PREAMBLE 0 or 3
T_SLOTTED_INCL 1
T_SLOTTED 0 or 8
ENC_SUPPORTED 1
CS_SUPPORTED 1

7 number for this cellular system (see 2.6.5.2).
3-359
3GPP2 C.S0005-A v6.0

7 The base station shall set this field to the window size
8 parameter shown in Table 2.6.6.2.1-1 corresponding to the
9 number of PN chips that the mobile station is to search for
10 pilots in the Active Set and Candidate Set.
15 pilots in the Neighbor Set.
20 pilots in the Remaining Set.
27 2.6.6.2.5.2).
30 -2 × 10 × log10 Ec/Io .
32 This value is used by the mobile station to start a handoff
33 drop timer for pilots in the Active Set and the Candidate Set
34 (see 2.6.6.2.3).
37 -2 × 10 × log10 Ec/Io .

39 The mobile station transmits a Pilot Strength Measurement
3-360
3GPP2 C.S0005-A v6.0

2 Timer value after which an action is taken by the mobile
3 station for a pilot that is a member of the Active Set or
4 Candidate Set, and whose strength has not become greater
5 than T_DROP. If the pilot is a member of the Active Set, a
6 Pilot Strength Measurement Message or an Extended Pilot
7 Strength Measurement Message is issued. If the pilot is a
8 member of the Candidate Set, it will be moved to the Neighbor
9 Set.
12 value to be used by the mobile station.
13 NGHBR_MAX_AGE - Maximum age for retention of Neighbor Set members.
14 The mobile station drops neighbor set members whose AGE
15 count exceeds this field.
16 The base station shall set this field to the Neighbor Set
17 maximum age retention value (see 2.6.6.2.6.3).
19 The base station shall set this field to the base station
20 protocol revision level.
23 2.6.6.2.3 and 2.6.6.2.5.2).
25 number.
40 EXTENSION - Indicator that extension fields are present.
41 If Reverse Supplemental Code Channel or Reverse Supple-
42 mental Channel system parameters are included in this
43 message, the base station shall set this field to ‘1’; otherwise,
3-361
3GPP2 C.S0005-A v6.0
1 T_MULCHAN - Supplemental Channel Request Message pilot strength

2 reporting offset.
3 If EXTENSION is set to ‘1’, the base station shall include this
4 field and set this field to the threshold offset that the mobile
5 station is to use when reporting neighbor pilot strength
6 measurements in a Supplemental Channel Request Message.
7 The mobile station is to interpret this field as an offset to
8 T_ADD ranging from 0.5 dB (corresponding to T_MULCHAN =
9 ‘000’) to 4.0 dB (corresponding to T_MULCHAN = ‘111’) in 0.5
10 dB increments.
11 BEGIN_PREAMBLE - Number of preamble frames on Reverse Supplemental Code
12 Channels at the beginning of transmission on Reverse
13 Supplemental Code Channel.
15 field and set this field to the number of Reverse Supplemental
16 Code Channel preamble frames that the mobile station is to
17 send when beginning transmission on Reverse Supplemental
18 Code Channels.
19 RESUME_PREAMBLE - Number of preamble frames on Reverse Supplemental Code
20 Channels at the resumption of transmission.
22 field and set this field to the number of Reverse Supplemental
23 Code Channel preamble frames that the mobile station is to
24 send when resuming transmission on a Reverse Supplemental
25 Code Channel following an autonomous suspension of
26 transmission on an allocated Supplemental Code Channel.
27 T_SLOTTED_INCL - Slotted timer value included indicator.
28 The base station shall set this field to ‘1’ if the slotted timer
29 value is included; otherwise, the base station shall set this
31 T_SLOTTED - Slotted timer value
32 If T_SLOTTED_INCL is set to ‘1’, the base station shall include

33 this field and set this field to the value of the TMS_Slotted
34 timer to be used by the mobile station in units of 80 ms;
37 The base station shall set this field to ‘1’ in the encryption
40 SIG_ENCRYPT_SUP – Signaling Encryption supported indicator.
45 station.
3-362
3GPP2 C.S0005-A v6.0

2 5.
4 as follows:
7 corresponding signaling algorithm is supported by the base
8 station; otherwise, the base station shall set the subfield to ‘0’.
15 algorithms.
17 9.

26
3-363
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.8 Neighbor List Update Message
2 MSG_TAG: NLUM
Field Length (bits)
PILOT_INC 4
One to 20 occurrences of the following field:

NGHBR_PN 9

6 The mobile station searches for Remaining Set pilots at pilot
7 PN sequence offset index values that are multiples of this
8 value.
10 increment, in units of 64 PN chips, that the mobile station is
11 to use for searching the Remaining Set. The base station
12 should set this field to the largest increment such that the
13 pilot PN sequence offsets of all its neighbor base stations are
14 integer multiples of that increment.
17 each pilot in its neighbor list. The base station shall set this
18 field to the pilot’s PN sequence offset, in units of 64 PN chips.
19 The base station shall include no more than 20 occurrences of
20 this field.
3-364
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.9 Send Burst DTMF Message
2 MSG_TAG: BDTMFM
Field Length (bits)
NUM_DIGITS 8
DTMF_ON_LENGTH 3
DTMF_OFF_LENGTH 3
NUM_DIGITS occurrences of the following field:

DIGITi 4
CON_REF_INCL 1
CON_REF 0 or 8
5 NUM_DIGITS - Number of DTMF digits.

6 The base station shall set this field to the number of DTMF
8 DTMF_ON_LENGTH - DTMF pulse width code.
9 The base station shall set this field to the DTMF_ON_LENGTH
11 requested pulse width of the DTMF pulse to be generated by
13 DTMF_OFF_LENGTH - DTMF interdigit interval code.
15 DTMF_OFF_LENGTH value shown in Table 2.7.2.3.2.7-2
16 corresponding to the requested minimum interdigit interval
17 between DTMF pulses to be generated by the mobile station.
18 DIGITi - DTMF digit.
20 each DTMF digit to be generated by the mobile station. The
21 base station shall set each occurrence of this field to the code
22 value shown in Table 2.7.1.3.2.4-4 corresponding to the dialed
23 digit.
3-365
3GPP2 C.S0005-A v6.0

5 assigned to the service option connection of the call, to which
6 this message corresponds.
3-366
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.10 Power Control Parameters Message
2 MSG_TAG: PCNPM
Field Length (bits)
PWR_REP_THRESH 5
PWR_REP_FRAMES 4
PWR_THRESH_ENABLE 1
PWR_PERIOD_ENABLE 1
PWR_REP_DELAY 5

9 the mobile station is to generate a Power Measurement Report
12 ‘00000’.
15 number given by
17 is the number of frames over which the mobile station is to
20 _ENABLE If the mobile station is to generate threshold Power
22 field to ‘1’. If the mobile station is not to generate threshold
26 _ENABLE If the mobile station is to generate periodic Power
28 field to ‘1’. If the mobile station is not to generate periodic
32 The period that the mobile station waits following a Power
3-367
3GPP2 C.S0005-A v6.0
3-368
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.11 Retrieve Parameters Message
2 MSG_TAG: RTPM
Field Length (bits)

PARAMETER_ID 16
5 PARAMETER_ID - Parameter identification.

6 The base station can request the mobile station to report any
7 parameter specified in Table E-1.
9 each parameter requested. The base station shall set this
10 field to the parameter identification number specified in
11 Table E-1 corresponding to the parameter requested.
3-369
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.12 Set Parameters Message
2 MSG_TAG: STPM
Field Length (bits)

PARAMETER_ID 16
PARAMETER_LEN 10
PARAMETER PARAMETER_LEN + 1
5 The base station shall include one occurrence of the following three-field record for each
6 parameter to be set.
7 PARAMETER_ID - Parameter identification.
8 The base station shall set this field to the identification shown
9 in Table E-1 corresponding to the settable parameter to be set.
10 PARAMETER_LEN - Parameter length.
11 The base station shall set this field to the length shown in
12 Table E-1 corresponding to the parameter to be set.
13 PARAMETER - Parameter value.
14 The base station shall set this field to the value of the
15 parameter specified by the PARAMETER_ID field.
3-370
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.13 SSD Update Message
2 MSG_TAG: SSDUM
Field Length (bits)
RANDSSD 56
5 RANDSSD - Random data.

3-371
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.14 Flash With Information Message
2 MSG_TAG: FWIM
Field Length (bits)

RECORD_TYPE 8
RECORD_LEN 8
6 3.7.5.
14 in 3.7.5.
3-372
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.15 Mobile Station Registered Message
2 MSG_TAG: MSRM
Field Length (bits)
SID 15
NID 16
REG_ZONE 12
TOTAL_ZONES 3
ZONE_TIMER 3
MULT_SIDS 1
MULT_NIDS 1
BASE_LAT 22
BASE_LONG 23
REG_DIST 11

7 number for this system.
12 identification number for this network. The NID value of
13 65,535 is reserved.
16 number (see 2.6.5.1.5).
3-373
3GPP2 C.S0005-A v6.0

22 +180°).
24 If mobile stations are to perform distance-based registration,
25 the base station shall set this field to the non-zero “distance”
27 2.6.5.1.4). If mobile stations are not to perform distance-
28 based registration, the base station shall set this field to 0.
3-374
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.16 Status Request Message
2 MSG_TAG: STRQM
Field Length (bits)
QUAL_INFO_TYPE 8
QUAL_INFO_LEN 3
NUM_FIELDS 4
RECORD_TYPE 8

8 information in the type-specific fields.
12 information.
20 fields:
BAND_CLASS 5
RESERVED 3
21

24 fields:
3-375
3GPP2 C.S0005-A v6.0
BAND_CLASS 5
OP_MODE 8
RESERVED 3

6 The base station shall set this field as shown in
8 qualification information.
11 NUM_FIELDS - Number of requested record fields in this message.
13 occurrences of RECORD_TYPE in this message.
14 The base station shall only request the status information records qualified by the included
15 qualification information in this message. The base station shall include one occurrence of
16 the following field for each information record that is requested:
3-376
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.17 Extended Handoff Direction Message
2 MSG_TAG: EHDM
Field Length (bits)
USE_TIME 1
ACTION_TIME 6
HDM_SEQ 2
SEARCH_INCLUDED 1
SRCH_WIN_A 0 or 4
T_ADD 0 or 6
T_DROP 0 or 6
T_COMP 0 or 4
T_TDROP 0 or 4
HARD_INCLUDED 1
FRAME_OFFSET 0 or 4
PRIVATE_LCM 0 or 1
RESET_L2 0 or 1
RESET_FPC 0 or 1
SERV_NEG_TYPE 0 or 1
ENCRYPT_MODE 0 or 2
NOM_PWR_EXT 0 or 1
NOM_PWR 0 or 4
NUM_PREAMBLE 0 or 3
BAND_CLASS 0 or 5
CDMA_FREQ 0 or 11
3-377
3GPP2 C.S0005-A v6.0
Field Length (bits)
ADD_LENGTH 3
Additional fields 8 × ADD_LENGTH
PILOT_PN 9
PWR_COMB_IND 1
CODE_CHAN 8

5 in this message.
14 HDM_SEQ - Extended Handoff Direction Message sequence number.
15 This field is used by the mobile station in the Power
16 Measurement Report Message to identify the order in which
17 the reported pilot strengths are sent.
18 The base station shall set this field as specified in 2.6.6.2.2.2.
19 SEARCH_INCLUDED - Pilot search parameters included.
20 If the mobile station is to change its pilot search parameters,
24 If SEARCH_INCLUDED is set to ‘1’, the base station shall
25 include the field SRCH_WIN_A and set this field to the window
26 size parameter shown in Table 2.6.6.2.1-1 corresponding to
27 the number of PN chips that the mobile station is to search for
28 pilots in the Active Set and Candidate Set; otherwise, the base
3-378
3GPP2 C.S0005-A v6.0

6 2.6.6.2.5.2).
8 include the field T_ADD and set this field to the pilot detection
10 -2 × 10 × log10 Ec/Io ; otherwise, the base station shall omit
11 this field.
15 2.6.6.2.3).
17 include the field T_DROP and set this field to the pilot drop
20 this field.
27 include the field T_COMP and set this field to the threshold
28 Candidate Set pilot to Active Set pilot ratio, in units of 0.5 dB;
35 Pilot Strength Measurement Message or an Extended Pilot
36 Strength Measurement Message is issued. If the pilot is a
37 member of the Candidate Set, it will be moved to the Neighbor
38 Set.
40 include the field T_TDROP and set this field to the T_TDROP
41 value shown in Table 2.6.6.2.3-1 corresponding to the drop
42 timer value to be used by the mobile station; otherwise, the
44 HARD_INCLUDED - Hard handoff parameters included.
3-379
3GPP2 C.S0005-A v6.0
1 If the mobile station is to change FRAME_OFFSET,

2 PRIVATE_LCM, ENCRYPT_MODE, SERV_NEG_TYPE,
3 NOM_PWR_EXT, NUM_PREAMBLE, NOM_PWR,
4 BAND_CLASS, or CDMA_FREQ, or the mobile station is to
5 perform a reset of the acknowledgment procedures, or the
6 mobile station is to reset Forward Traffic Channel power
7 control counters, the base station shall set this field to ‘1’;
12 If HARD_INCLUDED is set to ‘1’, the base station shall include
13 the field FRAME_OFFSET and set it to the Forward and
14 Reverse Traffic Channel frame offset; otherwise, the base
16 PRIVATE_LCM - Private long code mask indicator.
17 This field is used to change the long code mask after a hard
18 handoff.
20 the field PRIVATE_LCM and set it as described below;
22 If the private long code mask is to be used after the handoff,
23 the base station shall set this field to ’1’; otherwise, the base
25 RESET_L2 - Reset acknowledgment procedures command.
26 This field is used to reset acknowledgment processing in the
27 mobile station.
29 the field RESET_L2 and set it as described below; otherwise,
31 If the field is included and the mobile station is to reset its
32 acknowledgment procedures, the base station shall set this
34 RESET_FPC - Reset Forward Traffic Channel power control.
35 This field is used to reset the Forward Traffic Channel power
36 control counters.
38 the field RESET_FPC and set it as described below; otherwise,
40 The base station shall set this field to ‘0’ if the Forward Traffic
41 Channel power control counters are to be maintained after
42 completion of the handoff. If the counters are to be initialized
43 as specified in 2.6.4.1.1.1, then the base station shall set this
3-380
3GPP2 C.S0005-A v6.0
1 SERV_NEG_TYPE - Service negotiation type.

3 the field SERV_NEG_TYPE and set it as described below;
5 If the mobile station is to use service negotiation, the base
6 station shall set this field to ‘1’. If the mobile station is to use
7 service option negotiation, the base station shall set this field
8 to ‘0’.
11 the field ENCRYPT_MODE and set it to the ENCRYPT_MODE
13 encrypting mode that is to be used for messages sent on the
14 Forward and Reverse Traffic Channels, as specified
15 in 2.3.12.2; otherwise, the base station shall omit this field.
20 If this field is included and the mobile station is being handed
21 off to a base station operating in Band Class 0 or Band Class
22 3, the base station shall set this field to ‘0’; otherwise,.
24 off to a base station operating in a band class other than
25 Band Class 0 or Band Class 3, the base station shall set this
26 field to ‘1’ if the correction factor to be used by the mobile
27 station in the open loop power estimate is between –24 dB and
28 –9 dB inclusive; otherwise (the correction factor is in the
29 range –8 dB to 7 dB inclusive), the base station shall set this
33 the field NOM_PWR and set it to the correction factor to be
34 used by the mobile station in the open loop power estimate,
36 (see [2]); otherwise, the base station shall omit this field.
37 NUM_PREAMBLE - Traffic Channel preamble length.
38 If HARD_INCLUDED is set to ‘0’, the base station shall omit
39 the NUM_PREAMBLE field; otherwise, the base station shall
40 include this field and set it to the length of Traffic Channel
41 preamble that the mobile station is to send when performing a
42 handoff; as follows:
3-381
3GPP2 C.S0005-A v6.0
1 If, after the handoff, radio configuration 1 or radio

2 configuration 2 is to be used, the base station shall set
3 NUM_PREAMBLE to the Traffic Channel preamble length in
4 20 ms units; otherwise, the base station shall set
5 NUM_PREAMBLE to the value shown in Table 3.7.3.3.2.17-1
6 corresponding to the Traffic Channel preamble length in 1.25
7 ms units.
8 Table 3.7.3.3.2.17-1. Traffic Channel Preamble Length
NUM_PREAMBLE Preamble Length in l.25 ms

(binary) Increments
000 0
001 2
010 4
011 6
100 8
101 10
110 12
111 16

12 the field BAND_CLASS and set it to the CDMA band class
14 CDMA Channel as specified in [30]; otherwise, the base
18 the field CDMA_FREQ and set it to the CDMA Channel
20 the CDMA frequency assignment for the CDMA Channel as
21 specified in [2]; otherwise, the base station shall omit this
22 field.
23 ADD_LENGTH - Number of octets in the additional fields.
25 included in the Additional fields. If Additional fields are not
27 to ‘000’.
28
29 Additional fields - Additional fields.

30 If the ADD_LENGTH field is not equal to ‘000’, the base station
31 shall include the following fields as additional fields.
3-382
3GPP2 C.S0005-A v6.0
Field Length (bits)
P_REV 8

3 The base station shall set this field to the base station protocol
4 revision level that the mobile station is to use after completion of
5 the handoff.
7 The base station shall include one occurrence of the following three-field record for each
8 member of the mobile station’s new Active Set.
17 this field to ‘0’. For the first occurrence of this record in the
18 message, the base station shall set this field to ‘0’.
19 CODE_CHAN - Code channel index.
20 The base station shall set this field to the code channel index (see
21 2.1.3.1.9 and 3.1.3.1.13 of [2]) that the mobile station is to use as
22 the Forward Fundamental Channel associated with this pilot. If
23 Radio Configuration 1, 2, 3, or 5 (see 3.1.3.1.2 of [2]) is used, the
24 base station shall set this field in the range 1 to 63 inclusive. If
25 Radio Configuration 4, 6 or 8 is used, the base station shall set
26 this field in the range 1 to 127 inclusive. If Radio Configuration 7
27 or 9 is used, the base station shall set this field in the range 1 to
28 255 inclusive.
3-383
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.18 Service Request Message
2 MSG_TAG: SRQM
Field Length (bits)
SERV_REQ_SEQ 3
REQ_PURPOSE 4
RECORD_TYPE 8
RECORD_LEN 8
5 SERV_REQ_SEQ - Service request sequence number.

6 The base station shall set this field to the service request
7 sequence number pertaining to this request message as
8 specified in 3.6.4.1.2.1.1.
9 REQ_PURPOSE - Request purpose.
11 REQ_PURPOSE code from Table 3.7.3.3.2.18-1 to indicate the
13
14 Table 3.7.3.3.2.18-1. REQ_PURPOSE Codes
REQ_PURPOSE
(binary) Meaning
0001 Indicates that the purpose of this

configuration.
0010 Indicates that the purpose of this
configuration.
All other REQ_PURPOSE codes are reserved.
15
16 If the REQ_PURPOSE code is set to ‘0010’, the base station shall include one occurrence of
17 the following three-field record to specify the proposed service configuration; otherwise, the
18 base station shall not include the following record.
3-384
3GPP2 C.S0005-A v6.0
9 The base station shall set these fields as specified in 3.7.5.7
3-385
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.19 Service Response Message
2 MSG_TAG: SRPM
Field Length (bits)
SERV_REQ_SEQ 3
RESP_PURPOSE 4
RECORD_TYPE 8
RECORD_LEN 8
5 SERV_REQ_SEQ - Service request sequence number.

6 The base station shall set this field to the value of the
7 SERV_REQ_SEQ field in the Service Request Message to which
8 it is responding.
9 RESP_PURPOSE - Response purpose.
11 RESP_PURPOSE code from Table 3.7.3.3.2.19-1 to indicate
12 the purpose of the message.
13
14 Table 3.7.3.3.2.19-1. RESP_PURPOSE Codes
RESP_PURPOSE
(binary) Meaning

configuration.
configuration.
All other RESP_PURPOSE codes are reserved.
15
16 If the RESP_PURPOSE code is set to ‘0010’, the base station shall include one occurrence of
17 the following three-field record to specify the proposed service configuration; otherwise, the
18 base station shall not include the following record.
3-386
3GPP2 C.S0005-A v6.0
3-387
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.20 Service Connect Message
2 MSG_TAG: SCM
Field Length (bits)
USE_TIME 1
ACTION_TIME 6
SERV_CON_SEQ 3
RESERVED 42
USE_OLD_SERV_CONFIG 12
SYNC_ID_INCL 1
SYNC_ID_LEN 0 or 4
SYNC_ID 0 or (8 x
SYNC_ID_LEN)
Zero or one occurrence of the following three-field record:
RECORD_TYPE 8
RECORD_LEN 8
Zero or one occurrence of the following three-field record:
RECORD_TYPE 8
RECORD_LEN 8
CC_INFO_INCL 0 or 1
NUM_CALLS_ASSIGN 0 or 8
NUM_CALLS_ASSIGN occurrences of the following variable

length record:
CON_REF 8
RESPONSE_IND 1
TAG 0 or 4
BYPASS_ALERT_ANSWER 0 or 1
3-388
3GPP2 C.S0005-A v6.0

2 in this message.
9 at which the specified service configuration is to take effect. If
10 the USE_TIME field is set to ‘0’ the base station shall set this
11 field to ‘000000’.
12 SERV_CON_SEQ - Connect sequence number.
13 The base station shall set this field to the connect sequence
14 number pertaining to this connect message as specified in
15 3.6.4.1.2.1.2.
18 USE_OLD-
19 _SERV_CONFIG - Use stored service configuration indicator.
20 This field may be used by the base station to instruct the

21 mobile station to use the stored service configuration (that is,
22 both the Service Configuration information record and the
23 Non-negotiable Service Configuration information record)
24 ifbased on the value of the 16-bit CRC computed over the new
25 service configuration (see 2.6.11) matches the SYNC_ID that
26 the mobile station has reported in the Origination Message or
28 If MOB_P_REV is less than seven, the base station shall set

30 or iIf a service configuration has been sent successfully to the

31 mobile station upon entering the Traffic Channel Substate, the
33 station shall set this field according to Table 3.7.3.3.2.20-1 as
34 follows:
3-389
3GPP2 C.S0005-A v6.0
2 Table 3.7.3.3.2.20-1. USE_OLD_SERV_CONFIG values
USE_OLD_SERV_CONFIG Field Description

(binary)
00 Mobile Station is to use the SCR and

NNSCR included in this message
01 Mobile Station is to use the stored service
configuration
10 Mobile Station is to use the stored service
configuration but with the modifications
specified by the SCR and NNSCR included
in this message
11 Reserved
5 If the base station is to direct the mobile station to use the

6 stored service configuration (that is, both the Service
7 Configuration information record and the Non-negotiable
8 Service Configuration information record), the base station
11 SYNC_ID_INCL - Service Configuration synchronization identifier included

12 indicator.
13 If MOB_P_REV is less than seven or USE_OLD_SERV_CONFIG

14 field is set to ‘01’, the base station shall set this field to ‘0’. The
15 base station shall set this field to ‘1’ if the SYNC_ID field is
16 included in this message; otherwise, the base station shall set
18 SYNC_ID_LEN - Service Configuration synchronization identifier length.
19 If the SYNC_ID_INCL field is set to ‘0’, the base station shall

3-390
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the length (in octets) of
2 the SYNC_ID field included in this message. The base station
3 shall set this field to a value larger than zero.
4 SYNC_ID - Service Configuration synchronization identifier.
5 If the SYNC_ID_INCL field is set to ‘0’, the base station shall

8 The base station shall set this field to the synchronization

9 identifier corresponding to the service configuration conveyed
10 by this message.
11 If USE_OLD_SERV_CONFIG is equal to ‘01’, the base station shall omit the following record;
12 otherwise the base station shall include one occurrence of the following three-field record to
13 specify the service configuration.
25
26 If USE_OLD_SERV_CONFIG is equal to ‘01’, the base station shall omit the following record;
27 otherwise the base station shall include one occurrence of the following three-field record to
28 specify the non-negotiable service configuration parameters.
31 shown in Table 3.7.5-1 corresponding to the Non-Negotiable
35 included in the type-specific fields of the Non-Negotiable
39 for the Non-Negotiable Service Configuration information
40 record.
3-391
3GPP2 C.S0005-A v6.0
1 CC_INFO_INCL – Call Control information included indicator.
2 If the USE_OLD_SERV_CONFIG field is set to ‘01’ or ‘10’, the

4 shall include this field and set it as follows:
5 The base station shall set this field to ‘1’ if Call Control related
6 parameters (to assign new call(s)) are included in this
8 NUM_CALLS_ASSIGN - Number of call assignments.
9 If the CC_INFO_INCL field is not included or is included but is

10 set to ‘0’, the base station shall omit this field; otherwise, the
11 base station shall include this field and set it as follows:
12 The base station shall set this field to the number of new call
13 assignments included in this message.
14 The base station shall include NUM_CALLS_ASSIGN occurences of the following variable
15 length record.
17 The base station shall set this field to the connection reference
19 RESPONSE_IND – Response indicator.
20 The base station shall set this field to ‘1’ if this call
21 assignment is a response to an Enhanced Origination Message
22 from the mobile station; otherwise, the base station shall set
25 If the RESPONSE_IND field is set to ‘0’, the base station shall

28 The base station shall set this field to the value of the TAG
29 field received in the Enhanced Origination Message to which
30 this call assignment is the response.
31 BYPASS_ALERT-
3-392
3GPP2 C.S0005-A v6.0

4 If the mobile station is to bypass the Waiting for Order

5 Substate and the Waiting for Mobile Station Answer Substate
6 for this call, the base station shall set this field to ‘1’;
3-393
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.21 Service Option Control Message
2 MSG_TAG: SOCM
Field Length (bits)
USE_TIME 1
ACTION_TIME 6
CON_REF 8
SERVICE_OPTION 16
CTL_REC_LEN 8
Type-specific fields 8 × CTL_REC_LEN

7 in this message.
14 at which the message is to take effect. If the USE_TIME field
15 is set to ‘0’ the base station shall set this field to ‘000000’.
16 CON_REF - Service option connection reference.
17 The base station shall set this field to the reference for the
20 The base station shall set this field to the service option in use
21 with the service option connection.
22 CTL_REC_LEN - Service option control record length.
24 included in the type-specific fields of this service option
25 control record.
27 The base station shall set these fields as specified by the
28 requirements for the service option, which are defined
29 external to this specification. See relevant service option
30 specification.
3-394
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.22 TMSI Assignment Message
2 MSG_TAG: TASM
Field Length (bits)
TMSI_ZONE_LEN 4
TMSI_CODE 32
TMSI_EXP_TIME 24

10 The base station shall set this field to the TMSI zone number,
12 TMSI_CODE - Temporary mobile station identity code.
13 The base station shall set this field to the 32-bit TMSI code
14 assigned to the mobile station.
15 If the base station is to deassign the TMSI, the base station
16 shall set all the bits in this field to ‘1’.
17 TMSI_EXP_TIME - TMSI expiration time.
18 The base station shall set this field to the System Time in the
19 units of 80 ms × 212 when the TMSI is to expire.
3-395
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.23 Service Redirection Message
2 MSG_TAG: SRDM
Field Length (bits)
RETURN_IF_FAIL 1
DELETE_TMSI 1
REDIRECT_TYPE 1

RECORD_TYPE 8
RECORD_LEN 8

15 REDIRECT_TYPE - Redirect indicator.

16 The base station shall set this field to the REDIRECT_TYPE value
17 shown in Table 3.7.2.3.2.16-1 corresponding to the redirection
18 type.
19
20 The base station shall include one occurrence of the following record:
22 The base station shall set this field to the RECORD_TYPE value
24 redirection specified by this record.
26 If RECORD_TYPE equals to ‘00000000’, the base station shall
27 set this field to ‘00000000’; otherwise, the base station shall
29 of this redirection record.
3-396
3GPP2 C.S0005-A v6.0

3 If RECORD_TYPE is equal to ‘00000000’, the base station shall not include the type-specific
4 fields.
Field Length (bits)
EXPECTED_SID 15
IGNORE_CDMA 1
SYS_ORDERING 3
RESERVED 5

12 to 0.
30
3-397
3GPP2 C.S0005-A v6.0
BAND_CLASS 5
EXPECTED_SID 15
EXPECTED_NID 16
RESERVED 4
NUM_CHANS 4

CDMA_CHAN 11

3 The base station shall set this field to the CDMA band class, as
4 specified in [30].
9 to 0.
14 field to 65535.
3-398
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.24 Supplemental Channel Assignment Message
2 MSG_TAG: SCAM
Field Length (bits)
USE_RETRY_DELAY 1
RETRY_DELAY 0 or 8
REV_INCLUDED 1
Include the following record only if REV_INCLUDED is set to
‘1’:
REV_DTX_DURATION 4
EXPL_REV_START_TIME 1
REV_START_TIME 0 or 6
USE_REV_DURATION 1
REV_DURATION 0 or 8
USE_REV_HDM_SEQ 1
REV_LINKED_HDM_SEQ 0 or 2
NUM_REV_CODES 3
USE_T_ADD_ABORT 1
USE_SCRM_SEQ_NUM 1
SCRM_SEQ_NUM 0 or 4
REV_PARMS_INCLUDED 1
T_MULCHAN 0 or 3
FOR_INCLUDED 1
3-399
3GPP2 C.S0005-A v6.0
Field Length (bits)
Include the following record only if FOR_INCLUDED is set to

‘1’:
FOR_SUP_CONFIG 2
EXPL_FOR_START_TIME 0 or 1
FOR_START_TIME 0 or 6
USE_FOR_DURATION 1
FOR_DURATION 0 or 8
USE_FOR_HDM_SEQ 0 or 1
FOR_LINKED_HDM_SEQ 0 or 2
Include the following fields and records only if
FOR_INCLUDED is set to ‘1’ and
FOR_SUP_CONFIG is set to ‘10’ or ‘11’:
NUM_SUP_PILOTS 3
NUM_FOR_SUP 3
Include NUM_SUP_PILOTS occurrences of the following
record only if FOR_INCLUDED is set to ‘1’ and
FOR_SUP_CONFIG is set to ‘10’ or ‘11’:
PILOT_PN 9
EXPL_CODE_CHAN 1
If EXPL_CODE_CHAN is set to ‘1’, for each PILOT_PN
include NUM_FOR_SUP occurrences of the following field:
SUP_CODE_CHAN 0 or 8
If EXPL_CODE_CHAN is set to ‘0’, the following field is
included:
BASE_CODE_CHAN 0 or 8
3 USE_RETRY_DELAY - Assign or Retry Indicator.

4 The base station shall set this field to ‘1’ to indicate that this
5 message contains a retry delay time; otherwise, the base
6 station shall set this field to ‘0’ to indicate that no
7 RETRY_DELAY has been included.
8 RETRY_DELAY - Supplemental Channel Request Message retry delay.
3-400
3GPP2 C.S0005-A v6.0
1 If USE_RETRY_DELAY is set to ‘1’, the base station shall

2 include and set this field to the duration of the delay interval
3 in units of 320 ms (4 frames) from the next 80 ms system time
4 boundary during which the mobile station is not permitted to
5 send a Supplemental Channel Request Message. The base
6 station shall set RETRY_DELAY to ‘11111111’ to indicate that
7 the mobile station is to refrain from sending Supplemental
8 Channel Request Messages indefinitely.
9 REV_INCLUDED - Reverse Supplemental Code Channel configuration indicator.
11 message contains assignment information for Reverse
12 Supplemental Code Channels; otherwise, the base station
14 If REV_INCLUDED is set to ‘1’, then the base station shall include the following fields,
15 otherwise the base station shall omit the following fields:
16 REV_DTX_DURATION - Reverse Discontinuous Transmission Duration.
17 The base station shall set this field to the maximum duration
18 of time in units of 20 ms that the mobile station is allowed to
19 stop transmission on a Reverse Supplemental Code Channel
20 within the reverse assignment duration. The base station
21 shall set this field to ‘0000’ if the mobile station is to stop
22 using a Reverse Supplemental Code Channel once it has
23 stopped transmitting on that Reverse Supplemental Code
24 Channel. The base station shall set this field to ‘1111’ if the
25 mobile station is allowed to resume transmission on a Reverse
26 Supplemental Code Channel at any time within the reverse
27 assignment duration.
28 EXPL_REV_START_TIME - Explicit Reverse Supplemental Code Channel assignment start
29 time indicator.
30 This field indicates whether a start time for the specified
31 Reverse Supplemental Channel Assignment is specified in this
32 message. If a REV_START_TIME is specified in this message,
34 station shall set this field to ‘0’. If EXPL_REV_START_TIME is
35 set to ‘1’, then the base station shall set USE_REV_HDM_SEQ
36 to ‘0’.
37 REV_START_TIME - Explicit start time for Reverse Supplemental Code Channel
38 assignment.
39 If EXPL_REV_START_TIME is included and set to ‘1’, the base
40 station shall include and set this field to the System Time, in
41 units of 80 ms (modulo 64), at which the mobile station may
42 start transmitting on the specified number of Reverse
43 Supplemental Code Channels. If EXPL_REV_START_TIME is
44 omitted or set to ‘0’, the base station shall omit this field.
45 USE_REV_DURATION - Use reverse duration indicator.
3-401
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to ‘1’ if the

2 REV_DURATION field is included in the message; otherwise,
3 the base station shall set this field to ‘0’. If the mobile station
4 is granted permission to transmit on Reverse Supplemental
5 Code Channels (i.e., NUM_REV_CODES is not ‘000’) then a
6 value of ‘0’ for this field indicates an infinite Reverse
7 Supplemental Code Channel assignment duration (i.e., the
8 mobile station may transmit on Reverse Supplemental Code
9 Channels until it receives a subsequent Supplemental Channel
10 Assignment Message or a General Handoff Direction Message
11 that specifies an updated REV_DURATION or an updated
12 value of NUM_REV_CODES).
13 REV_DURATION - Duration of Reverse Supplemental Code Channel assignment.
14 The base station shall include this field only if the
15 USE_REV_DURATION field is included and set to ‘1’. If this
16 field is included, this field indicates the allocated duration, in
17 units of 80 ms, during which the mobile station may transmit
18 on Reverse Supplemental Code Channels.
19 USE_REV_HDM_SEQ - Use Reverse General Handoff Direction Message sequence
20 number indicator.
22 Reverse Supplemental Code Channel assignment shall take
23 effect at the same time as a corresponding General Handoff
24 Direction Message; otherwise, the base station shall set this
25 field to ‘0’. If USE_REV_HDM_SEQ is set to ‘1’, then the base
26 station shall set EXPL_REV_START_TIME to ‘0’.
27 REV_LINKED_HDM_SEQ - Sequence number of the reverse linked General Handoff
29 If USE_REV_HDM_SEQ is included and set to ‘1’, then the
30 base station shall set this field to the sequence number of the
31 General Handoff Direction Message (HDM_SEQ) to which this
32 Reverse Supplemental Code Channel assignment is linked.
33 NUM_REV_CODES - Number of Reverse Supplemental Code Channels.
34 The base station shall set this field to the number of Reverse
35 Supplemental Code Channels that are assigned to the mobile
36 station.
37 USE_T_ADD_ABORT - Reverse use T_ADD abort indicator.
39 mobile station is to utilize the T_ADD Reverse Supplemental
40 Code Channel abort feature for this reverse assignment;
42 USE_SCRM_SEQ_NUM - Use Supplemental Channel Request Message sequence number
43 indicator.
45 SCRM_SEQ_NUM field is included in this message; otherwise,
47 SCRM_SEQ_NUM - Supplemental Channel Request Message sequence number.
3-402
3GPP2 C.S0005-A v6.0
1 If USE_SCRM_SEQ_NUM is set to ‘1’, the base station shall

2 set this field to the sequence number corresponding to the
3 SCRM_SEQ_NUM field in a Supplemental Channel Request
4 Message to which the mobile station is to match this message;
6 REV_PARMS_INCLUDED - Reverse additional parameters included flag.
7 The base station shall set this field to ‘1’ if the following three
8 fields (T_MULCHAN, BEGIN_PREAMBLE, and
9 RESUME_PREAMBLE) are included in this message;
12 reporting offset.
13 If REV_PARMS_INCLUDED is set to ‘1’, the base station shall
14 include this field and set this field to the threshold offset that
15 the mobile station is to use when reporting neighbor pilot
16 strength measurements in a Supplemental Channel Request
17 Message. The mobile station is to interpret this field as an
18 offset to T_ADD ranging from 0.5 dB (corresponding to
19 T_MULCHAN = ‘000’) to 4.0 dB (corresponding to T_MULCHAN
20 = ‘111’) in 0.5 dB increments.
25 include this field and set this field to the number of Reverse
26 Supplemental Code Channel preamble frames that the mobile
27 station is to send when beginning transmission on Reverse
28 Supplemental Code Channels.
32 include this field and set this field to the number of Reverse
33 Supplemental Code Channel preamble frames that the mobile
34 station is to send when resuming transmission on a Reverse
35 Supplemental Code Channel following an autonomous
36 suspension of transmission on an allocated Supplemental
37 Code Channel.
38 FOR_INCLUDED - Forward Supplemental Code Channel configuration indicator.
40 message contains assignment information for Forward
41 Supplemental Code Channels; otherwise, the base station
43 If FOR_INCLUDED is set to ‘1’, then the base station shall
44 include the remaining fields in this message, otherwise the
45 base station shall omit all of the following except for
46 RESERVED.
47 FOR_SUP_CONFIG - Forward Supplemental Code Channel configuration indicator.
3-403
3GPP2 C.S0005-A v6.0
2 mobile station is to stop processing the Forward Supplemental
3 Code Channels at the implicit action time of the message.
5 mobile station is to start processing the Forward
6 Supplemental Code Channels in the Code Channel List at the
7 implicit, explicit, or linked start time specified by this message
8 (see 2.6.6.2.5.1).
9 The base station shall set this field to ‘10’ if the Forward
10 Supplemental Code Channels are specified in the message and
11 the mobile station is to update its Code Channel List and stop
12 processing the Forward Supplemental Code Channels at the
13 implicit action time of the message.
15 Supplemental Code Channels are specified in the message and
16 the mobile station is to start processing the Forward
17 Supplemental Code Channels at the implicit, explicit, or
18 linked start time specified by this message (see 2.6.6.2.5.1).
19 EXPL_FOR_START_TIME - Explicit forward start time indicator.
20 This field indicates whether an explicit Forward Supplemental
21 Code Channel start time is specified in this message.
22 The base station shall include this field only if
23 FOR_SUP_CONFIG is set to ’01 or ‘11’. If a FOR_START_TIME
24 is specified in this message, the base station shall set this
26 If EXPL_FOR_START_TIME is set to ‘1’, then the base station
27 shall set USE_FOR_HDM_SEQ to ‘0’.
28 The following field is included only if EXPL_FOR_START_TIME is included and set to ‘1’:
29 FOR_START_TIME - Start time of the Forward Supplemental Code Channel
30 assignment.
32 FOR_SUP_CONFIG is set to ‘01’ or ‘11’. If the
33 EXPL_FOR_START_TIME field is set to ‘1’, the base station
34 shall set this field to the System Time, in units of 80 ms
35 (modulo 64), at which the mobile station is to start processing
36 the Forward Supplemental Code Channels. If
37 EXPL_FOR_START_TIME is set to ‘0’ the base station shall
38 omit this field.
39 USE_FOR_DURATION - Use forward duration indicator.
40 The base station shall set this field to ‘1’ if FOR_DURATION is
41 included in the message; otherwise, the base station shall set
3-404
3GPP2 C.S0005-A v6.0
1 If FOR_SUP_CONFIG is set to ‘01’ or ‘11’, then the base

2 station may set this field to ‘0’ to indicate that the mobile
3 station is to be assigned an infinite Forward Supplemental
4 Code Channel assignment duration (i.e., the mobile station is
5 to continue processing Forward Supplemental Code Channels
6 until it receives a subsequent Supplemental Channel
8 that specifies an updated FOR_DURATION). Otherwise, the
9 base station may set this field to ‘1’ to indicate that the mobile
10 station is to be given a Forward Supplemental Code Channel
11 assignment for the duration specified by the FOR_DURATION
12 field.
13 If FOR_SUP_CONFIG is set to ‘00’ or ‘10’, then the base
14 station shall set USE_FOR_DURATION to ‘0’.
15 FOR_DURATION - Duration of Forward Supplemental Code Channel assignment.
17 USE_FOR_DURATION is included and set to ‘1’. If this field is
18 included, this field indicates allocated duration, in units of 80
19 ms, during which the mobile station is to process the Forward
21 USE_FOR_HDM_SEQ - Use Forward General Handoff Direction Message sequence
23 This field indicates whether processing of the Forward
24 Supplemental Code Channels shall take effect at the same
25 time as a corresponding General Handoff Direction Message.
27 FOR_SUP_CONFIG is equal to ‘01’ or ‘11’. If this message is
28 linked with a General Handoff Direction Message, the base
30 shall set this field to ‘0’. If USE_FOR_HDM_SEQ is set to ‘1’,
31 then the base station shall set EXPL_FOR_START_TIME to ‘0’.
32 FOR_LINKED_HDM_SEQ - Sequence number of the General Handoff Direction Message.
33 If the USE_FOR_HDM_SEQ field is included and set to ‘1’, the
34 base station shall set this field to the sequence number of the
35 General Handoff Direction Message (HDM_SEQ) to which this
36 Forward Supplemental Code Channel assignment is linked;
37 otherwise, if USE_FOR_HDM_SEQ is not included or is set to
38 ‘0’, then base station shall omit this field.
39 NUM_SUP_PILOTS - Number of pilots in the Active Set which have at least one
40 associated Supplemental Code Channel.
41 If FOR_SUP_CONFIG is included and is set to ‘10’ or ‘11’, the
42 base station shall include this field and shall set this field to
43 the number of pilots for which there is at least one associated
44 Supplemental Code Channel. This field shall not be included
45 if FOR_SUP_CONFIG is omitted or is set to ‘01’ or ‘00’.
46 NUM_FOR_SUP - Number of Forward Supplemental Code Channels.
3-405
3GPP2 C.S0005-A v6.0

2 base station shall include this field and shall set this field to
3 the number of Forward Supplemental Code Channels assigned
4 to the mobile station. NUM_FOR_SUP shall not exceed the
5 maximum number of Forward Supplemental Code Channels
6 for the negotiated multiplex option. This field shall not be
7 included if FOR_SUP_CONFIG is omitted or is set to ‘01’ or
8 ‘00’.
9 If FOR_SUP_CONFIG is included and is set to ‘10’ or ‘11’, the base station shall include
10 NUM_SUP_PILOTS occurrences of the following record, one for each pilot for which there is
11 at least one associated Supplemental Code Channel:
15 EXPL_CODE_CHAN - Explicit code channel indicator
16 The base station shall set this field to ‘1’ to indicate explicit
17 assignment of each Forward Supplemental Code Channel.
19 is to use NUM_FOR_SUP successive code channels beginning
20 with index BASE_CODE_CHAN (i.e., BASE_CODE_CHAN
21 through BASE_CODE_CHAN + NUM_FOR_SUP – 1). In both
22 cases (i.e., the explicit code channel list format and range
23 format), the order of the code channel indices is the same for
24 all the pilots specified in this message (i.e., the ith code
25 channel index in the list for each pilot PN sequence offset
26 indicates the appropriate code channel to be used for the ith
27 Forward Supplemental Code Channel).
28 If EXPL_CODE_CHAN is set to ‘1’, then the base station shall include NUM_FOR_SUP
29 occurrences of the following field, one for each pilot which has been included:
30 SUP_CODE_CHAN - Supplemental Code Channel index.
32 (see [2]) in the range 1 to 63 inclusive of the Supplemental
33 Code Channel associated with this pilot.
34 If EXPL_CODE_CHAN is set to ‘0’ then the base station shall include the following field:
35 BASE_CODE_CHAN - Base code channel index.
36 If EXPL_CODE_CHAN is equal to ‘0’ the base station shall
37 include this field and set it to the base code channel index
38 (see [2]) in the range of 1 to (63 – NUM_FOR_SUP + 1),
39 inclusive, that the mobile station is to use as the first Forward
40 Supplemental Code Channel associated with this pilot. The
41 mobile station is to use NUM_FOR_SUP successive code
42 channels beginning with index BASE_CODE_CHAN (i.e.,
43 BASE_CODE_CHAN through BASE_CODE_CHAN +
44 NUM_FOR_SUP – 1) for the Forward Supplemental Code
3-406
3GPP2 C.S0005-A v6.0
1 The base station shall not include this field if

2 EXPL_CODE_CHAN is equal to ‘1’ or if EXPL_CODE_CHAN is
3 not included.
3-407
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.25 Power Control Message
2 MSG_TAG: PCNM
Field Length (bits)
PWR_CNTL_STEP 3
USE_TIME 1
ACTION_TIME 0 or 6
FPC_INCL 1
FPC_MODE 0 or 3
FPC_PRI_CHAN 0 or 1
FPC_OLPC_FCH_INCL 0 or 1
FPC_FCH_FER 0 or 5
FPC_FCH_MIN_SETPT 0 or 8
FPC_FCH_MAX_SETPT 0 or 8
FPC_OLPC_DCCH_INCL 0 or 1
FPC_DCCH_FER 0 or 5
FPC_DCCH_MIN_SETPT 0 or 8
FPC_DCCH_MAX_SETPT 0 or 8
FPC_SEC_CHAN 0 or 1
NUM_SUP 0 or 2
Include NUM_SUP occurrence of the following four fields:
SCH_ID 1
FPC_SCH_FER 5
FPC_SCH_MIN_SETPT 8
FPC_SCH_MAX_SETPT 8
FPC_THRESH_INCL 0 or 1
3-408
3GPP2 C.S0005-A v6.0
Field Length (bits)
FPC_SETPT_THRESH 0 or 8
FPC_THRESH_SCH_INCL 0 or 1
FPC_SETPT_THRESH_SCH 0 or 8
RPC_INCL 1
RPC_NUM_REC 0 or 2
If RPC INCL is set to ‘1’, RPC_NUM_REC occurrences of the
following record:
RPC_ADJ_REC_TYPE 4
RPC_ADJ_REC_LEN 5
Type-specific fields 8× RPC_ADJ_REC_LEN
3 PWR_CNTL_STEP - Power control step size

4 The base station shall set this field to the closed loop power
5 control step size parameter shown in Table 3.7.3.3.2.25-1
6 corresponding to the power control step size that the mobile
7 station is to use for closed loop power control.
8
9 Table 3.7.3.3.2.25-1. Closed Loop Power Control

10 Step Size
PWR_CNTL_STEP Power Control Step Size

(binary) (dB nominal)
000 1
001 0.5
010 0.25
All other PWR_CNTL_STEP values are reserved.

12 This field indicates whether an ACTION_TIME is specified in
13 this message.
14 If an ACTION_TIME is specified in this message, the base
21 is set to ‘0’ the base station shall omit this field.
3-409
3GPP2 C.S0005-A v6.0
1 FPC_INCL - Forward Link Power Control parameter included indicator.

2 If the forward power control related information is included in
5 FPC_MODE - Forward Power Control Operation Mode Indicator
6 If FPC_INCL is set to ‘0’ the base station shall omit this field;
8 The base station shall set the value to the forward power
9 control operation mode (see [2]).
22 Channel.
23 If only the Fundamental Channel is assigned, the base station
24 shall set this field to ‘0’. If only the Dedicated Control
25 Channel is assigned, the base station shall set this field to ‘1’.
26 FPC_OLPC_FCH_INCL - Fundamental Channel Outer Loop Power Control parameter
30 If the forward link fundamental channel outer loop power
31 control parameters are included in this message, the base
35 If FPC_OLPC_FCH_INCL is included and set to ‘1’, the base
36 station shall set this field to the target Frame Error Rate on
37 the Forward Fundamental Channel, as specified in Table
38 3.7.3.3.2.25-2; otherwise, the base station shall omit this
39 field.
3-410
3GPP2 C.S0005-A v6.0
1 Table 3.7.3.3.2.25-2. Target Frame Error Rate
FER Frame Error Rate

(Binary)
00000 0.2%
00001-10100 0.5% -10% (in units of 0.5%)
10101-11001 11% - 15% (in units of 1.0%)
11010-11110 18% - 30% (in units of 3.0%)
11111 Reserved
2 FPC_ FCH_MIN_SETPT - Minimum Fundamental Channel Outer Loop Eb/Nt setpoint

4 station shall set this field to minimum Fundamental Channel
5 Outer Loop Eb/Nt setpoint, in units of 0.125 dB; otherwise,
7 The base station shall set this field to ‘11111111’, when it
8 directs the mobile station to set this Eb/No setpoint to the
9 current setpoint used at the mobile station on this channel.
10 FPC_FCH_MAX_SETPT - Maximum Fundamental Channel Outer Loop Eb/Nt setpoint
12 station shall set this field to maximum Fundamental Channel
13 Outer Loop Eb/Nt setpoint, in units of 0.125 dB; otherwise,
18 FPC_OLPC_DCCH_INCL - Dedicated Control Channel Outer Loop Power Control
19 parameter included indicator.
22 If the forward link Dedicated Control Channel outer loop
23 power control parameters are included in this message, the
27 If FPC_OLPC_DCCH_INCL is included and set to ‘1’, the base
29 the Forward Dedicated Control Channel, as specified in Table
31 field.
32 FPC_DCCH_MIN_SETPT - Minimum Dedicated Control Channel Outer Loop Eb/Nt
33 setpoint.
3-411
3GPP2 C.S0005-A v6.0

2 station shall set this field to minimum Dedicated Control
3 Channel Outer Loop Eb/Nt setpoint, in units of 0.125 dB;
8 FPC_DCCH_MAX_SETPT - Maximum Dedicated Control Channel Outer Loop Eb/Nt
9 setpoint.
11 station shall set this field to maximum Dedicated Control
12 Channel Outer Loop Eb/Nt setpoint, in units of 0.125 dB;
17 FPC_SEC_CHAN - Master Supplemental channel index.
18 If FPC_INCL is set to '1' and FPC_MODE is set to '001', '010',
19 ‘101’, or ‘110’, the base station shall set this field to the
20 master Supplemental Channel index; otherwise, the base
22 NUM_SUP – Number of Supplemental Channels.
24 otherwise, the base station shall set this field to the total
25 number of the Supplemental Channels.
26 The base station shall include NUM_SUP occurrences of the following record:
27 SCH_ID - Supplemental channel index.
28 The base station shall set this field to the Supplemental
29 Channel index.
30 FPC_SCH_FER - Supplemental channel target Frame Error Rate.
32 Rate on the Supplemental Channel, as specified in Table
33 3.7.3.3.2.25-2.
34 FPC_MIN_SCH_SETPT - Minimum Supplemental Channel outer loop Eb/Nt setpoint.
35 The base station shall set this field to minimum Supplemental
40 FPC_MAX_SCH_SETPT - Maximum Supplemental Channel outer loop Eb/Nt setpoint.
41 The base station shall set this field to maximum Supplemental
3-412
3GPP2 C.S0005-A v6.0

4 FPC_THRESH_INCL - Setpoint Report Threshold included indicator.
5 If FPC_INCL is set to ‘0’, the base station shall omit this field;
7 If FPC_SETPT_THRESH is included in this message, the base
10 FPC_SETPT_THRESH - Setpoint Report Threshold.
11 If FPC_THRESH_INCL is set to ‘1’, the base station shall set
12 the value to FPC_SETPT_THRESH (in units of 0.125 dB) above
13 which the outer loop report message will be sent by the mobile
14 station; otherwise, the base station shall omit this field.
15 FPC_THRESH_SCH_INCL - SCH Setpoint Report Threshold included indicator.
18 If FPC_SETPT_THRESH_SCH is included in this message, the
21 FPC_SETPT-
22 _THRESH_SCH - SCH Setpoint Report Threshold.
23 If FPC_THRESH_SCH_INCL is set to ‘1’, the base station shall
24 set the value to FPC_SETPT_THRESH_SCH (in units of 0.125
25 dB) above which the outer loop report message will be sent by
26 the mobile station; otherwise, the base station shall omit this
27 field.
28 RPC_INCL - Reverse Link Power Control parameter included indicator.
29 If the reverse power control related information is included in
32 RPC_NUM_REC - Number of records for Reverse Link Power Control.
33 If RPC_INCL is set to ‘0’, the base station shall omit this field;
34 otherwise, the base station shall set this field to one less than
35 the number of records included in this message.
36 If RPC_NUM_REC is included in this message, the base station shall include
37 RPC_NUM_REC occurrences of the following record:
38 RPC_ADJ_REC_TYPE - Reverse Link Power Control adjustment record type.
40 Table 3.7.2.3.2.25-3 corresponding to the type of adjustment
41 that is to be used.
3-413
3GPP2 C.S0005-A v6.0
1 Table 3.7.3.3.2.25-3. RPC_ADJ_REC_TYPE and

2 RPC_ADJ_REC_LEN fields
Description RPC_ADJ_REC_TYPE RPC_ADJ_REC_LEN

(binary)
Reverse Channel 0000 2-5
Adjustment Gain
Attribute Adjustment 0001 2-26
Gain for Basic Rates
Attribute Adjustment 0010 2-31
Gain for Higher Rates
4 RPC_ADJ_REC_LEN - Reverse Link Power Control adjustment record length.

6 the type-specific fields of this adjustment record as given in
7 Table 3.7.2.3.2.25-3.
8 Type-specific fields - Reverse Link Power Control adjustment record type-specific
9 fields.
11 RPC_ADJ_REC_TYPE of this adjustment record, as specified
12 as below.
3-414
3GPP2 C.S0005-A v6.0
1 If RPC_ADJ_REC_TYPE is equal to ‘0000’, the base station shall set type-specific fields as
3 Table 3.7.2.3.2.25-4. Type Specific Fields for

4 RECORD_TYPE = ‘0000’
Length (Bits)
Fields
FCH_INCL 1
FCH_CHAN_ADJ_GAIN 0 or 8
DCCH_INCL 1
DCCH_CHAN_ADJ_GAIN 0 or 8
SCH0_INCL 1
SCH0_CHAN_ADJ_GAIN 0 or 8
SCH1_INCL 1
SCH1_CHAN_ADJ_GAIN 0 or 8
RESERVED 0-7 (if needed)
7 FCH_INCL - FCH channel adjustment gain included indicator.

8 If FCH_CHAN_ADJ_GAIN is included in this message, the base
11 FCH_CHAN_ADJ_GAIN - Channel adjustment gain for Reverse Fundamental Channel.
12 If FCH_INCL is set to ‘0’, the base station shall omit this field;
13 otherwise, the base station shall set each field to the value of
14 the gain adjustment that the mobile station is to make for the
15 Reverse Fundamental Channel. The base station shall set
16 this field to the correction factor expressed as a two’s
17 complement value in units of 0.125 dB. The base station
18 shall set the value in the range from –48 to 48 inclusive.
19 DCCH_INCL - DCCH channel adjustment gain included indicator.
20 If DCCH_CHAN_ADJ_GAIN is included in this message, the
23 DCCH_CHAN_ADJ_GAIN - Channel adjustment gain for the Reverse Dedicated Control
24 Channel.
3-415
3GPP2 C.S0005-A v6.0
1 If DCCH_INCL is set to ‘0’, the base station shall omit this

2 field; otherwise, the base station shall set each field to the
3 value of the gain adjustment that the mobile station is to
4 make for the Reverse Dedicated Control Channel. The base
5 station shall set this field to the correction factor expressed as
6 a two’s complement value in units of 0.125 dB. The base
7 station shall set the value in the range from –48 to 48
8 inclusive.
9 SCH0_INCL - SCH0 channel adjustment gain included indicator.
10 If SCH0_CHAN_ADJ_GAIN is included in this message, the
13 SCH0_CHAN_ADJ_GAIN - Channel adjustment gain for Reverse Supplemental Channel
14 0.
15 If SCH0_INCL is set to ‘0’, the base station shall omit this
18 make for the Reverse Supplemental Channel 0. The base
19 station shall set this field to the correction factor expressed as
20 a two’s complement value in units of 0.125 dB. The base
22 inclusive.
23 SCH1_INCL - SCH1 channel adjustment gain included indicator.
24 If SCH1_CHAN_ADJ_GAIN is included in this message, the
27 SCH1_CHAN_ADJ_GAIN - Channel adjustment gain for Reverse Supplemental Channel
28 1.
29 If SCH1_INCL is set to ‘0’, the base station shall omit this
32 make for the Supplemental Channel 1. The base station shall
33 set this field to the correction factor expressed as a two’s
34 complement value in units of 0.125 dB. The base station
35 shall set the value in the range from –48 to 48 inclusive.
3-416
3GPP2 C.S0005-A v6.0

Fields Length (Bits)
RL_ATT_ADJ_GAIN_TYPE 1
RC3_RC5_20MS_INCL 1
RL_ATT_ADJ_GAIN_1500 0 or 8
RC4_RC6_20MS_INCL 1
5MS_INCL 1
RL_ATT_ADJ_GAIN_9600_5MS 0 or 8
RC3_RC5_40MS_INCL 1
RC4_RC6_40MS_INCL 1
RC3_RC5_80MS_INCL 1

4
3-417
3GPP2 C.S0005-A v6.0
RC4_RC6_80MS_INCL 1
3 RL_ATT_ADJ-
4 _GAIN_TYPE - Reverse Link Attribute Adjustment Gain value type indicator.
5 If the following fields are set to the nominal attribute gain
6 adjustment values that the mobile station is to use for the
7 transmission attributes (relative to Nominal_Attribute_Gain
8 specified in Table 2.1.2.3.3.2-1 of [2]), the base station shall
9 set this field to ‘0’. If the following fields are set to the pilot
10 reference level adjustment values that the mobile station is to
11 use for the transmission attributes (relative to
12 Pilot_Reference_Level specified in Table 2.1.2.3.3.2-1 of [2]),
14 RC3_RC5-
15 _20MS_INCL - Reverse Link Attribute Adjustment Gain for Radio
16 Configuration 3 or 5 of 20 ms frame included indicator.
17 If Reverse Link Attribute adjustment Gain for Radio
18 Configuration 3 or 5 of 20 ms frame is included in this
21 RL_ATT_ADJ_GAIN_1500 - Reverse Link Attribute Adjustment Gain for the transmission
22 rate 1500 bits/s.
23 If RC3_RC5_20MS_INCL is set to ‘0’, the base station shall
24 omit this field.
25 If RC3_RC5_20MS_INCL is set to ‘1’ and
26 RL_ATT_ADJ_GAIN_TYPE is set to ‘0’, the base station shall
27 set this field to the value of the nominal attribute gain
28 adjustment that the mobile station is to make for the
29 transmission attributes with transmission rate 1500 bits/s,
30 convolutional code and 20ms frame. The base station shall
31 set the value in the range from –48 to 48 inclusive.
3-418
3GPP2 C.S0005-A v6.0

3 set this field to the value of the pilot reference level
7 set the value in the range from 0 to 63 inclusive.
8 The base station shall set this field to the correction factor
9 expressed as a two’s complement value in units of 0.125 dB.
13 omit this field.
30 RL_ATT_ADJ_GAIN_4800 - Reverse Link Attribute Gain Adjustment for the transmission
33 omit this field.
3-419
3GPP2 C.S0005-A v6.0
4 rate 9600 bits/s.
6 omit this field.
23 RC4_RC6-
25 Configuration 4 or 6 of 20ms frame included indicator.
26 If Reverse Link Attribute Adjustment Gain for Radio
27 Configuration 4 or 6 of 20ms frame is included in this
33 omit this field.
3-420
3GPP2 C.S0005-A v6.0
4 rate 3600 bits/s.
6 omit this field.
26 omit this field.
35 NORM_ATT_GAIN_TYPE is set to ‘1’, the base station shall set
36 this field to the value of the pilot reference level adjustment
37 that the mobile station is to make for the transmission
38 attributes with transmission rate 7200 bits/s, convolutional
39 code and 20ms frame. The base station shall set the value in
40 the range from 0 to 63 inclusive.
43 RL_ATT_ADJ_GAIN_14400- Reverse Link Attribute Adjustment Gain for the transmission
46 omit this field.
3-421
3GPP2 C.S0005-A v6.0

3 set this field to the value of the nominal gain adjustment that
4 the mobile station is to make for the transmission attributes
5 with transmission rate 14400 bits/s, convolutional code and
6 20ms frame. The base station shall set the value in the range
7 from –48 to 48 inclusive.
17 5MS_INCL - 5ms frame Reverse Link Attribute Adjustment Gain included
18 indicator.
19 If Reverse Link Attribute Adjustment Gain for 5ms frame is
22 RL_ATT_ADJ_GAIN-
23 _9600_5MS - Reverse Link Attribute Adjustment Gain for the transmission
24 rate 9600 bits/s with 5ms frame.
25 If 5MS_INCL is set to ‘0’, the base station shall omit this field.
26 If 5MS_INCL is set to ‘1’ and RL_ATT_ADJ_GAIN_TYPE is set
27 to ‘0’, the base station shall set this field to the value of the
28 nominal attribute gain adjustment that the mobile station is
29 to make for the transmission attributes with transmission rate
30 9600 bits/s, convolutional code and 5ms frame. The base
32 inclusive.
33 If 5MS_INCL is set to ‘1’ and RL_ATT_ADJ_GAIN_TYPE is set
34 to ‘1’, the base station shall set this field to the value of the
35 pilot reference level adjustment that the mobile station is to
36 make for the transmission attributes with transmission rate
37 9600 bits/s, convolutional code and 5ms frame. The base
38 station shall set the value in the range from 0 to 63 inclusive.
41 RC3_RC5_40MS_INCL - Reverse Link Attribute Adjustment Gain for Radio
47 RL_ATT_ADJ_GAIN-
3-422
3GPP2 C.S0005-A v6.0

2 rate 1350 bits/s.
4 omit this field.
21 RL_ATT_ADJ_GAIN-
25 omit this field.
42 RL_ATT_ADJ_GAIN-
43 _4800_40MS - Reverse Link Attribute Gain Adjustment for the transmission
46 omit this field.
3-423
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
44 RL_ATT_ADJ_GAIN-
3-424
3GPP2 C.S0005-A v6.0

2 omit this field.
19 RL_ATT_ADJ_GAIN-
23 omit this field.
40 RL_ATT_ADJ_GAIN-
44 omit this field.
3-425
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
44 RL_ATT_ADJ_GAIN-
3-426
3GPP2 C.S0005-A v6.0

2 omit this field.
19 RL_ATT_ADJ_GAIN-
23 omit this field.
40 RL_ATT_ADJ_GAIN-
44 omit this field.
3-427
3GPP2 C.S0005-A v6.0

13 convolutional code and 840ms 80ms frame. The base station
14 shall set the value in the range from 0 to 63 inclusive.
17 RL_ATT_ADJ_GAIN-
21 omit this field.
44 RL_ATT_ADJ_GAIN-
3-428
3GPP2 C.S0005-A v6.0

2 omit this field.
19 RL_ATT_ADJ_GAIN-
23 omit this field.
40 RL_ATT_ADJ_GAIN-
44 omit this field.
3-429
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
41 number of octets. The base station shall set these bits to ’0’.
3-430
3GPP2 C.S0005-A v6.0

CODE_TYPE 1
RL_ATT_ADJ_GAIN_TYPE 1
RC3_RC5_20MS_INCL 1
RC4_RC6_20MS_INCL 1
RC3_RC5_40MS_INCL 1
RC4_RC6_40MS_INCL 1

4
3-431
3GPP2 C.S0005-A v6.0
RC3_RC5_80MS_INCL 1
RC4_RC6_80MS_INCL 1
3 CODE_TYPE - Coding type indicator.

4 If the following corresponding gain adjustment fields apply for
5 the convolutonal code, the base station shall set this field to
6 ‘0’. If the following corresponding gain adjustment fields apply
7 for the Turbo code, the base station shall set this field to ‘1’.
8 RL_ATT_ADJ-
9 _GAIN_TYPE - Reverse Link Attribute adjustment Gain value type indicator.
10 If the following corresponding gain adjustment fields are set to
11 the value of the nominal attribute gain adjustment that the
12 mobile station is to make for the corresponding transmission
13 attributes (relative to Nominal_Attribute_Gain specified in
14 Table 2.1.2.3.3-1 of [2]), the base station shall set this field to
15 ‘0’. If the following corresponding gain adjustment fields are
16 set to the value of the pilot reference level adjustment that the
17 mobile station is to use for the corresponding transmission
18 attributes (relative to Pilot_Reference_Level specified in Table
19 2.1.2.3.3-1 of [2]), the base station shall set this field to ‘1’.
20 RC3_RC5-
3-432
3GPP2 C.S0005-A v6.0
1 RL_ATT_ADJ_GAIN-
2 _19200 - Reverse Link Attribute Adjustment Gain for the transmission
5 omit this field.
11 and 20ms frame. The base station shall set the value in the
12 range from –48 to 48 inclusive.
17 transmission attributes with transmission rate 19200 bits/s
19 range from 0 to 63 inclusive.
22 RL_ATT_ADJ_GAIN-
26 omit this field.
38 attributes with transmission rate 38400 bits/s and 20ms
39 frame. The base station shall set the value in the range from
40 0 to 63 inclusive.
43 RL_ATT_ADJ_GAIN-
47 omit this field.
3-433
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
24 this field to the value of the nominal attribute gain adjustment
26 attributes with transmission rate 153600 bits/s, and 20ms
28 –48 to 48 inclusive.
38 RL_ATT_ADJ_GAIN-
42 omit this field.
3-434
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
38 RC4_RC6-
45 RL_ATT_ADJ_GAIN-
3-435
3GPP2 C.S0005-A v6.0

2 omit this field.
19 RL_ATT_ADJ_GAIN-
23 omit this field.
40 RL_ATT_ADJ_GAIN-
44 omit this field.
3-436
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
38 RL_ATT_ADJ_GAIN-
42 omit this field.
3-437
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
19 rate 1036800 bits/s.
21 omit this field.
26 transmission attributes with transmission rate 1036800
27 bits/s, and 20ms frame. The base station shall set the value
28 in the range from –48 to 48 inclusive.
33 transmission attributes with transmission rate 1306800
34 bits/s and 20ms frame. The base station shall set the value
35 in the range from 0 to 63 inclusive.
44 RL_ATT_ADJ_GAIN-
3-438
3GPP2 C.S0005-A v6.0

2 omit this field.
19 RL_ATT_ADJ_GAIN-
23 omit this field.
40 RL_ATT_ADJ_GAIN-
44 omit this field.
3-439
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
38 RL_ATT_ADJ_GAIN-
42 omit this field.
3-440
3GPP2 C.S0005-A v6.0

23 RL_ATT_ADJ_GAIN-
27 omit this field.
44 RL_ATT_ADJ_GAIN-
3-441
3GPP2 C.S0005-A v6.0

2 omit this field.
19 RL_ATT_ADJ_GAIN-
23 omit this field.
40 RL_ATT_ADJ_GAIN-
44 omit this field.
3-442
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
44 RL_ATT_ADJ_GAIN-
3-443
3GPP2 C.S0005-A v6.0

2 omit this field.
19 RL_ATT_ADJ_GAIN-
23 omit this field.
40 RL_ATT_ADJ_GAIN-
44 omit this field.
3-444
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
44 RL_ATT_ADJ_GAIN-
3-445
3GPP2 C.S0005-A v6.0

2 omit this field.
19 RL_ATT_ADJ_GAIN-
23 omit this field.
40 RL_ATT_ADJ_GAIN-
44 omit this field.
3-446
3GPP2 C.S0005-A v6.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
3-447
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.26 Extended Neighbor List Update Message
2 MSG_TAG: ENLUM
Field Length (bits)
PILOT_INC 4
NGHBR_SRCH_MODE 2
SRCH_WIN_N 4
USE_TIMING 1
NUM_NGHBR 6
NUM_NGHBR occurrences of the following field:
NGHBR_PN 9
TIMING_INCL 0 or 1
SRCH_OFFSET_INCL 1

RECORD_LEN 0 or 3

3-448
3GPP2 C.S0005-A v6.0
8 15 inclusive.
10 The base station shall set this field to the value specified in
12
13 Table 3.7.3.3.2.26-1. NGHBR_SRCH_MODE Field
Value

10 Search windows
14
15 SRCH_WIN_N - Default search window size for the Neighbor Set.

17 Table 2.6.6.2.1-1 corresponding to the default search window
18 size to be used by the mobile station for its Neighbor Set. The
19 mobile station uses the default search window size for all
20 pilots in its Neighbor Set when the search window is not
21 specified for each pilot individually (NGHBR_SRCH_MODE is
22 set to a value other than ‘10’ and ‘11’).
27 GLOBAL_TIMING-
30 field GLOBAL_TIMING_INCL and set this field as described
36 GLOBAL_TX-
3-449
3GPP2 C.S0005-A v6.0

9 greater.
10 GLOBAL_TX-
22 mobile station is to place in its Neighbor Set
25 each pilot in its neighbor list. The base station shall set this
26 field to the pilot’s PN sequence offset, in units of 64 PN chips.
28 If NGHBR_SRCH_MODE is set to ‘01’ or ‘11’, then the base
29 station shall set this field to the search priority for this
30 neighbor. The base station shall set the search priority as
31 specified in Table 3.7.3.3.2.26-2. If NGHBR_SRCH_MODE is
32 set to any other value, the base station shall omit this field.
33
3-450
3GPP2 C.S0005-A v6.0
1 Table 3.7.3.3.2.26-2. SEARCH_PRIORITY Field

(binary)
00 Low
01 Medium
10 High
11 Very High

4 If NGHBR_SRCH_MODE is set to ‘10’ or ‘11’, then the base
5 station shall set this field to the value specified in Table
6 2.6.6.2.1-1 corresponding to the search window size to be
7 used by the mobile stations for this neighbor. If
8 NGHBR_SRCH_MODE is set to any other value, the base
19 shall include the field NGHBR_TX_OFFSET and set this field
21 field.
26 occurs when t/4 mod (16384)= 0.
30 include the field NGHBR_TX_DURATION and set this field as
32 field.
36 greater.
3-451
3GPP2 C.S0005-A v6.0

3 include the field NGHBR_TX_PERIOD and set this field as
5 field.
15 the following record as is used for previous pilots which are listed in this message.
16 Specifically, the ith occurrence of the following record shall correspond the ith pilot in this
17 message.
20 information listed in NGHBR_PILOT_REC_TYPE and
24 NGHBR_PILOT-
25 _REC_TYPE - Neighbor Pilot record type
31 omit this field.
37 omit this field.
43 omit this field.
44
3-452
3GPP2 C.S0005-A v6.0
2 fields:
Field Length (bits)
TD_POWER_LEVEL 2
TD_MODE 2
RESERVED 4

8 in Table 3.7.2.3.2.26-4.
15 fields:
Field Length (bits)
QOF 2
WALSH_LENGTH 3
16

20 WALSH_LENGTH - Length of the Walsh code.
24 Auxiliary Pilot.
25 AUX_PILOT_WALSH - Walsh code for the Auxiliary Pilot.
3-453
3GPP2 C.S0005-A v6.0
4 fields:
Field Length (bits)
QOF 2
WALSH_LENGTH 3
TD_MODE 2

8 Diversity Pilot.
16 AUX_WALSH - Walsh code for the Auxiliary Pilot.
19 AUX_ TD-
20 _POWER_LEVEL - Auxiliary Transmit Diversity Pilot power level.
31 fields:
3-454
3GPP2 C.S0005-A v6.0
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
RESERVED 7

20
22 fields:
3-455
3GPP2 C.S0005-A v6.0
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
QOF 2
WALSH_LENGTH 3
ADD_INFO_INCL1 1
QOF1 0 or 2
WALSH_LENGTH1+6
ADD_INFO_INCL2 1
QOF2 0 or 2
WALSH_LENGTH2+6

3-456
3GPP2 C.S0005-A v6.0

8 primary pilot.
15 to ‘1’.
20 follows:
28 follows:
33 SR3 frequencies.
38 follows:
3-457
3GPP2 C.S0005-A v6.0

5 to ‘1’.
10 follows:
18 follows:
23 SR3 frequencies.
28 follows:
35 SRCH_OFFSET_NGHBR - Neighbor pilot channel search window offset.
38 corresponding to the search window offset to be used by the
39 mobile station for this neighbor; otherwise, the base station
3-458
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.27 Candidate Frequency Search Request Message
2 MSG_TAG: CFSRQM
Field Length (bits)
USE_TIME 1
ACTION_TIME 6
RESERVED_1 4
CFSRM_SEQ 2
SEARCH_TYPE 2
SEARCH_PERIOD 4
SEARCH_MODE 4
MODE_SPECIFIC_LEN 8
Mode-specific fields 8×
MODE_SPECIFIC_LEN
ALIGN_TIMING 1
SEARCH_OFFSET 0 or 6

7 in this message.
11 If the base station requests the mobile station to perform an
12 aligned search (see 2.6.6.2.8.3), the base station shall specify
13 an explicit action time for the message.
21 CFSRM_SEQ - Candidate Frequency Search Request Message sequence
22 number.
23 The base station shall set this field to the Candidate
24 Frequency Search Request Message sequence number, as
25 specified in 2.6.6.2.2.3.
3-459
3GPP2 C.S0005-A v6.0
1 SEARCH_TYPE - Search command.

3 SEARCH_TYPE code from Table 3.7.3.3.2.27-1 to indicate the
5
6 Table 3.7.3.3.2.27-1. SEARCH_TYPE Codes
SEARCH_TYPE
(binary) Meaning
00 Directs the mobile station to stop any

periodic search in progress
(see 2.6.6.2.8.3.4 and 2.6.6.2.10.4)
01 Directs the mobile station to perform a single
search (see 2.6.6.2.8.3.1 and 2.6.6.2.10.1).
11 Directs the mobile station to perform a
periodic search (see 2.6.6.2.8.3.2 and
2.6.6.2.10.2).
10 Reserved.
8 SEARCH_PERIOD - Time between successive searches on the Candidate

9 Frequency for periodic searches.
10 The base station shall set this field to the SEARCH_PERIOD
11 value shown in Table 2.6.6.2.8.3.2-1 corresponding to the
12 search period to be used by the mobile station, i.e., the time
13 between the beginning of successive searches on the
15 SEARCH_MODE - Search mode.
16 The base station shall set this field to the SEARCH_MODE
17 value specified in Table 3.7.3.3.2.27-2 corresponding to the
18 type of search specified by this message.
19
20 Table 3.7.3.3.2.27-2. SEARCH_MODE Types
SEARCH_MODE
0000 Searches for CDMA pilots on a

Candidate Frequency.
0001 Searches for analog channels.
0010 Searches for Direct Spread (DS)
neighbor cell.
0011-1111 Reserved
21
3-460
3GPP2 C.S0005-A v6.0
1 MODE_SPECIFIC_LEN - Length of mode-specific fields.

3 the mode-specific fields of this message.
4 Mode-specific fields - Search mode-specific fields.
5 The base station shall include mode-specific fields based on
6 the SEARCH_MODE field.
7 If SEARCH_MODE is equal to ‘0000’, the base station shall include the following fields:
Field Length (bits)
BAND_CLASS 5
CDMA_FREQ 11
SF_TOTAL_EC_THRESH 5
SF_TOTAL_EC_IO_THRESH 5
DIFF_RX_PWR_THRESH 5
MIN_TOTAL_PILOT_EC_IO 5
CF_T_ADD 6
TF_WAIT_TIME 4
CF_PILOT_INC 4
CF_SRCH_WIN_N 4
CF_SRCH_WIN_R 4
RESERVED_2 5
PILOT_UPDATE 1
If PILOT_UPDATE is set to ‘1’ the base station shall include
the following record:
NUM_PILOTS 6
CF_NGHBR_SRCH_MODE 2
If PILOT_UPDATE is set to ‘1’, the base station shall include
NGHBR_PN 9
SEARCH_SET 1
the following field:
CF_SRCH_OFFSET_INCL 1
3-461
3GPP2 C.S0005-A v6.0
Field Length (bits)

RECORD_LEN 0 or 3

4 The base station shall set this field to the CDMA band class of
7 The base station shall set this field to the CDMA frequency
8 assignment for the Candidate Frequency.
9 SF_TOTAL_EC-
10 _THRESH - Serving Frequency total pilot Ec threshold.
11 If the mobile station is not to use the measurement of total Ec
12 of the pilots in the Serving Frequency Active Set in the
13 Candidate Frequency periodic search procedure, the base
14 station shall set this field to ‘11111’; otherwise, the base
15 station shall set this field to
16  (10 × log10 (total_ec_thresh) + 120) / 2 
17 where total_ec_thresh is defined by the following rule: The

18 mobile station is not to visit the CDMA Candidate Frequency
19 to search for pilots if the total Ec of the pilots in the Serving
20 Frequency Active Set is greater than total_ec_thresh.
21 SF_TOTAL_EC-
22 _IO_THRESH - Serving Frequency total pilot Ec/Io threshold.
23 If the mobile station is not to use the measurement of total
24 Ec/ Io of the pilots in the Serving Frequency Active Set in the
25 Candidate Frequency periodic search procedure, the base
28  - 20 × log10 (total_ec_io_thresh) 
3-462
3GPP2 C.S0005-A v6.0
1 where total_ec_io_thresh is defined by the following rule: The

2 mobile station is not to visit the CDMA Candidate Frequency
3 to search for pilots if the total Ec/Io of the pilots in the
4 Serving Frequency Active Set is greater than
5 total_ec_io_thresh.
6 DIFF_RX_PWR-
7 _THRESH - Minimum difference in received power.
8 If this message is used for the Candidate Frequency single or
9 periodic search procedure:
10 If the mobile station is to search for pilots on the CDMA
11 Candidate Frequency irrespective of the received power on
12 the Candidate Frequency, the base station shall set this
13 field to ‘00000’; otherwise, the base station shall set this
14 field to
15  (minimum_power_diff + 30) / 2 
16 where minimum_power_diff is determined by the following
17 rule: The mobile station is not to search for pilots on the
18 CDMA Candidate Frequency if (cand_freq_pwr -
19 serving_freq_pwr) is less than minimum_power_diff (in dB),
20 where cand_freq_pwr is the received power on the CDMA
21 Candidate Frequency, in dBm / 1.23 MHz, and
22 serving_freq_pwr is the received power on the Serving
23 Frequency, in dBm / 1.23 MHz.
24 If this message is used for the Hard Handoff with Return on
25 Failure procedure:
26 If the mobile station is to continue hard handoff
27 procedures irrespective of the received power on the Target
28 Frequency, the base station shall set this field to ‘00000’;
29 otherwise, the base station shall set this field to
30  (minimum_power_diff + 30) / 2 
31 where minimum_power_diff is determined by the following
32 rule: The mobile station is to declare the handoff attempt
33 to be unsuccessful if (target_freq_pwr - serving_freq_pwr) is
34 less than minimum_power_diff (in dB), where
35 target_freq_pwr is the received power on the CDMA Target
36 Frequency, in dBm / 1.23 MHz, and serving_freq_pwr is
37 the received power on the Serving Frequency, in dBm /
38 1.23 MHz.
39 MIN_TOTAL_PILOT-
40 _EC_IO - Minimum total pilot Ec/ Io.
41 If this message is used for the Candidate Frequency periodic
42 search procedure:
3-463
3GPP2 C.S0005-A v6.0
1 If the mobile station is to search for pilots on the CDMA

2 Candidate Frequency irrespective of the strength of pilots
3 in the Candidate Frequency Search Set, the base station
4 shall set this field to ‘00000’; otherwise, the base station
5 shall set this field to
6  - 20 × log10 total_pilot_threshold 
7 where total_pilot_threshold is defined by the following rule:

8 The mobile station is not to send the Candidate Frequency
9 Search Report Message if the sum of Ec/Io of all pilots in
10 the mobile station’s Candidate Frequency Search Set that
11 measure above CF_T_ADD is less than
12 total_pilot_threshold.
13 If this message is used for the Hard Handoff with Return on

14 Failure procedure:
15 If the mobile station is to attempt to demodulate the
16 Forward Traffic Channels irrespective of the strength of
17 pilots in the Active Set, the base station shall set this field
18 to ‘00000’; otherwise, the base station shall set this field to
19  - 20 × log10 total_pilot_threshold 
20 where total_pilot_threshold is defined by the following rule:

21 The mobile station is not to attempt to demodulate the
22 Forward Traffic Channels if the sum of Ec/Io of all pilots
23 in the mobile station’s Active Set is less than
24 total_pilot_threshold.
25 CF_T_ADD - Pilot detection threshold for the CDMA Candidate Frequency.
26 This value is used by the mobile station to trigger the sending
27 of the Candidate Frequency Search Report Message during a
28 periodic search of the CDMA Candidate Frequency (see
29 2.6.6.2.8.3.2).
32 -2 × 10 × log10 Ec/Io .
33 TF_WAIT_TIME - The total maximum wait time on the CDMA Target Frequency.
34 The base station shall set this field to the maximum wait time,
35 in units of 80 ms, that the mobile station is to spend waiting
36 for a period of (N11m × 20) ms with sufficient signal quality
37 (e.g. good frames) on the CDMA Target Frequency.
38 CF_PILOT_INC - Pilot PN sequence offset index increment to be used on the
39 CDMA Candidate Frequency after handoff.
3-464
3GPP2 C.S0005-A v6.0
2 increment, in units of 64 PN chips, that the mobile station is
3 to use for searching the Remaining Set, after a handoff to the
4 CDMA Candidate Frequency is successfully completed. The
5 base station should set this field to the largest increment such
6 that the pilot PN sequence offsets of all its neighbor base
7 stations are integer multiples of that increment.
8 CF_SRCH_WIN_N - Default search window size for the Candidate Frequency
9 Search Set.
11 Table 2.6.6.2.1-1 corresponding to the default search window
12 size to be used by the mobile station for its Candidate
13 Frequency Neighbor Search Set. The mobile station uses the
14 default search window size for all pilots in its Candidate
15 Frequency Neighbor Search Set when the search window has
16 not been specified for each pilot individually.
17 CF_SRCH_WIN_R - Search window size for the Remaining Set on the CDMA
22 pilots in the Remaining Set on the CDMA Candidate
23 Frequency after a handoff is successfully completed.
26 PILOT_UPDATE - Pilot search parameter update indicator.
30 NUM_PILOTS - Number of pilots included in the message.
31 The base station shall set this field to the number of the
32 CDMA Candidate Frequency pilots included in this message.
33 The base station shall set this field to a value from 0 to N8m,
34 inclusive.
35 CF_NGHBR_SRCH-
36 _MODE - Search mode for Candidate Frequency Search Set.
39
3-465
3GPP2 C.S0005-A v6.0
1 Table 3.7.3.3.2.27-3. CF_NGHBR_SRCH_MODE Field
Value
00 No search priorities or search windows specified

01 Search priorities specified
10 Search windows specified
11 Search windows and search priorities specified
3 The base station shall include NUM_PILOTS occurrences of the following four-field record,
4 one for each included CDMA Candidate Frequency pilot.
6 The base station shall set this field to the pilot’s PN sequence
7 offset, in units of 64 PN chips.
8 SEARCH_SET - Flag to indicate if the corresponding pilot is to be searched.
10 should add the corresponding pilot to its Candidate Frequency
11 Search Set; otherwise, the base station shall set this field to
12 ‘0’.
14 If CF_NGHBR_SRCH_MODE is set to ‘01’ or ‘11’, then the base
15 station shall set this field to the search priority for this
16 neighbor. The base station shall set the search priority as
17 specified in Table 3.7.3.3.2.26-2. If CF_NGHBR_SRCH_MODE
18 is set to any other value, the base station shall omit this field.
20 If CF_NGHBR_SRCH_MODE is set to ‘10’ or ‘11’, then the base
21 station shall set this field to the value specified in
23 be used by mobile stations for this neighbor. If the
24 CF_NGHBR_SRCH_MODE is set to any other value, the base
26 CF_SRCH_OFFSET_INCL - Neighbor pilot channel search window offset included.
27 If PILOT_UPDATE is set to ‘0’, the base station shall omit this
30 If CF_NGHBR_SRCH_MODE is set to ‘10’ or ‘11’ and if
31 SRCH_OFFSET_NGHBR is included in the message, the base
34 If PILOT_UPDATE is set to ‘1’, the base station shall include NUM_PILOTS occurrences of
35 the following four-field record, one for each included CDMA Candidate Frequency Pilot.
3-466
3GPP2 C.S0005-A v6.0
2 information listed in NGHBR_PILOT_REC_TYPE and
6 NGHBR_PILOT-
7 _REC_TYPE - Neighbor Pilot record type
13 omit this field.
19 omit this field.
25 omit this field.
27 fields:
28
Field Length (bits)
TD_POWER_LEVEL 2
TD_MODE 2
RESERVED 4
29

33 in Table 3.7.2.3.2.26-4.
3-467
3GPP2 C.S0005-A v6.0
3 fields:
Field Length (bits)
QOF 2
WALSH_LENGTH 3

12 Auxiliary pilot.
13 AUX_PILOT_WALSH - Walsh code for the Auxiliary Pilot.
20 fields:
21
Field Length (bits)
QOF 2
WALSH_LENGTH 3
TD_MODE 2
22

24 Diversity Pilot.
3-468
3GPP2 C.S0005-A v6.0

6 AUX_WALSH - Walsh code for the Auxiliary Pilot.
9 AUX_ TD-
10 _POWER_LEVEL - Auxiliary Transmit Diversity Pilot power level.
21 fields:
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
22

3-469
3GPP2 C.S0005-A v6.0

5 fields:
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
QOF 2
WALSH_LENGTH 3
ADD_INFO_INCL1 1
QOF1 0 or 2
WALSH_LENGTH1+6
ADD_INFO_INCL2 1
QOF2 0 or 2
WALSH_LENGTH2+6

3-470
3GPP2 C.S0005-A v6.0

13 primary pilot.
20 to ‘1’.
25 follows:
33 follows:
38 SR3 frequencies.
43 follows:
3-471
3GPP2 C.S0005-A v6.0

7 to ‘1’.
12 follows:
20 follows:
25 SR3 frequencies.
30 follows:
37 SRCH_OFFSET_NGHBR - Neighbor pilot channel search window offset.
38 If CF_SRCH_OFFSET_INCL is included and equals to ‘1’, then
39 the base station shall set this field to the value specified in
40 Table 2.6.6.2.1-2 corresponding to the search window offset to
41 be used by the mobile station for this neighbor; otherwise, the
45 make the length of the Mode-specific fields equal to an integer
3-472
3GPP2 C.S0005-A v6.0
1 If SEARCH_MODE is equal to ‘0001’, the base station shall include the following fields:
Field Length (bits)
BAND_CLASS 5
SF_TOTAL_EC_THRESH 5
SF_TOTAL_EC_IO_THRESH 5
RESERVED_4 6
NUM_ANALOG_FREQS 3
NUM_ANALOG_FREQS occurrences of the following record:
ANALOG_FREQ 11
RESERVED_5 0-7

5 The base station shall set this field to the CDMA band class
6 associated with the analog frequencies included in this
7 message.
8 SF_TOTAL_EC-
9 _THRESH - Serving Frequency total pilot Ec threshold.
10 If the mobile station is not to use the measurement of total Ec
11 of the pilots in the Serving Frequency Active Set in the Analog
12 Frequencies periodic search procedure, the base station shall
13 set this field to ‘11111’; otherwise, the base station shall set
14 this field to
15  (10 × log10 (total_ec_thresh) + 120) / 2 
16 where total_ec_thresh is defined by the following rule: The

17 mobile station is not to visit any analog frequency if the total
18 Ec of the pilots in the Serving Frequency Active Set is greater
19 than total_ec_thresh.
20 SF_TOTAL_EC-
21 _IO_THRESH - Serving Frequency total pilot Ec/Io threshold.
22 If the mobile station is not to use the measurement of total

23 Ec/Io of the pilots in the Serving Frequency Active Set in the
24 Analog Frequencies periodic search procedure, the base
27  - 20 × log10 (total_ec_io_thresh) 
3-473
3GPP2 C.S0005-A v6.0
1 where total_ec_io_thresh is defined by the following rule: The

2 mobile station is not to visit any analog frequency if the total
3 Ec/Io of the pilots in the Serving Frequency Active Set is
4 greater than total_ec_io_thresh.
7 NUM_ANALOG_FREQS - Number of analog frequencies.
9 neighbors on the candidate frequency. The base station shall
10 set this field to a value from 1 to 7, inclusive.
11
12 The message will include NUM_ANALOG_FREQS occurrences of the following one-field

13 record, one for each neighbor on the candidate frequency.
14 ANALOG_FREQ - Analog frequency channel number.
15 The base station shall set this field to the analog frequency
16 channel number to search.
19 make the length of the Mode-specific fields equal to an integer
21 ALIGN_TIMING - Align timing indicator.
22 If the base station requests that the mobile station offset the
23 start of the first search from the action time of this message
24 (or of a subsequent Candidate Frequency Search Control
25 Message that starts a search) by a delay specified by the
26 SEARCH_OFFSET field, the base station shall set this field to
28 SEARCH_OFFSET - Search offset.
29 If the ALIGN_TIMING field is set to ‘0’, the base station shall
31 field and set it to
32 min ( 63, search_offset_time / 0.00125  )
33 where search_offset_time is the time offset, in seconds, of the
35 (or of a subsequent Candidate Frequency Search Control
36 Message that starts a search).
3-474
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.28 Candidate Frequency Search Control Message
2 MSG_TAG: CFSCNM
Field Length (bits)
USE_TIME 1
ACTION_TIME 6
CFSCM_SEQ 2
SEARCH_TYPE 2
ALIGN_TIMING 1

7 in this message.
11 If the base station requests the mobile station to perform an
12 aligned search (see 2.6.6.2.8.3), the base station shall specify
13 an explicit action time for the message.
19 CFSCM_SEQ - Candidate Frequency Search Control Message sequence
20 number.
21 The base station shall set this field to the Candidate
22 Frequency Search Control Message sequence number, as
23 specified in 3.6.6.2.2.5.
24 SEARCH_TYPE - Search command.
26 SEARCH_TYPE code from Table 3.7.3.3.2.27-1 to indicate the
28 ALIGN_TIMING - Align timing indicator.
29 If the base station requests that the mobile station offset the
31 by a delay specified by the SEARCH_OFFSET field of the last
32 Candidate Frequency Search Request Message sent to the
33 mobile station, the base station shall set this field to ‘1’;
3-475
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.29 Power Up Function Message
2 MSG_TAG: PUFM
Field Length (bits)
USE_TIME 1
ACTION_TIME 6
ACTION_TIME_FRAME 2
PUF_SETUP_SIZE 6
PUF_PULSE_SIZE 7
PUF_INTERVAL 10
PUF_INIT_PWR 6
PUF_PWR_STEP 5
TOTAL_PUF_PROBES 4
MAX_PWR_PUF 4
PUF_FREQ_INCL 1
PUF_BAND_CLASS 0 or 5
PUF_CDMA_FREQ 0 or 11

8 The base station shall set this field to the System Time, in
9 units of 80 ms (modulo 64), used in calculating the start of
10 the first PUF probe.
11 ACTION_TIME_FRAME - Action time frame.
12 The base station shall set this field to the number of frames
13 after ACTION_TIME that the mobile station is to begin the first
14 PUF probe.
15 PUF_SETUP_SIZE - Number of PUF setup power control groups.
17 number of power control groups that the mobile station is to
18 transmit at nominal power prior to transmitting a PUF pulse.
19 The base station shall set the values of PUF_SETUP_SIZE and
20 PUF_PULSE_SIZE so that [PUF_SETUP_SIZE + 1 +
21 PUF_PULSE_SIZE + 1] mod 16 is not equal to 0.
22 PUF_PULSE_SIZE - Number of PUF pulse power control groups.
3-476
3GPP2 C.S0005-A v6.0
2 number of power control groups that the mobile station is to
3 transmit at elevated power level during the PUF pulse. The
4 base station shall set the values of PUF_SETUP_SIZE and
5 PUF_PULSE_SIZE so that [PUF_SETUP_SIZE + 1 +
6 PUF_PULSE_SIZE + 1] mod 16 is not equal to 0.
7 PUF_INTERVAL - PUF interval.
8 The base station shall set this field to the number of frames
9 between the start of each PUF probe.
10 PUF_INIT_PWR - Power increase of initial PUF pulse.
11 The base station shall set this field to the amount (in dB) that
12 the mobile station is to increase its mean output power for the
13 first PUF pulse.
14 PUF_PWR_STEP - PUF power step.
15 The base station shall set this field to the value (in dB) by
16 which the mobile station is to increment the power of a PUF
17 pulse above nominal power from one PUF pulse to the next.
18 TOTAL_PUF_PROBES - Total number of PUF probes.
20 maximum number of PUF probes the mobile station is to
21 transmit in a PUF attempt.
22 MAX_PWR_PUF - Maximum number of PUF probes transmitted at full power.
24 number of PUF pulses that the mobile station is to transmit at
25 maximum power level.
26 PUF_FREQ_INCL - Frequency included indicator.
27 If the mobile station is to change PUF_BAND_CLASS or
28 PUF_CDMA_FREQ, the base station shall set this field to ‘1’;
30 PUF_BAND_CLASS - Band class.
31 If PUF_FREQ_INCL is set to ‘1’, the base station shall include
32 this field and set it to the CDMA band class corresponding to
35 field.
36 PUF_CDMA_FREQ - Frequency assignment.
37 If PUF_FREQ_INCL is set to ‘1’, the base station shall include
38 this field and set it to the CDMA Channel number, in the
39 specified CDMA band class, corresponding to the CDMA
40 frequency for the CDMA Channel as specified in [2]; otherwise,
3-477
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.30 Power Up Function Completion Message
2 MSG_TAG: PUFCM
Field Length (bits)
RESERVED 6
LOC_IND 1
RESERVED_1 0 or 3
MS_LAT 0 or 22
MS_LONG 0 or 23
MS_LOC_TSTAMP 0 or 24

7 LOC_IND - Location indicator
8 If the base station is to include MS_LAT, MS_LONG, and
9 MS_LOC_TSTAMP in this message, the base station shall set
11 to ‘0’.
13 If LOC_IND is equal to ‘1’, the base station shall set these bits
14 to ‘000’; otherwise, the base station shall not include this
15 field.
16 MS_LAT - Mobile station latitude.
17 If LOC_IND is equal to ‘1’, the base station shall set this field
18 to the mobile station’s latitude in units of 0.25 second,
19 expressed as a two’s complement signed number with positive
20 numbers signifying North latitudes. The base station shall set
21 this field to a value in the range -1296000 to 1296000
22 inclusive (corresponding to a range of -90° to +90°).
23 Otherwise, the base station shall not include this field.
24 MS_LONG - Mobile station longitude.
26 to the mobile station’s longitude in units of 0.25 second,
27 expressed as a two’s complement signed number with positive
28 numbers signifying East longitude. The base station shall set
29 this field to a value in the range -2592000 to 2592000
30 inclusive (corresponding to a range of -180° to +180°).
31 Otherwise, the base station shall not include this field.
32 MS_LOC_TSTAMP - Time stamp.
3-478
3GPP2 C.S0005-A v6.0
2 to the time at which the mobile station’s location parameters
3 were received; otherwise, the base station shall not include
4 this field.
5 This field is formatted as shown below.
6
Field Length (bits)
HOURS 8
MINUTES 8
SECONDS 8
Note: All subfields contain two 4-bit BCD numbers giving
the decimal value of the subfield. For example, if the minute
is 53, the MINUTES subfield contains ‘01010011’.
7
8 HOURS - Current hour (UTC).

9 The base station shall set this field to the current hour (UTC),
10 in the range 0-23.
11 MINUTES - Current minutes (UTC).
12 The base station shall set this field to the current minutes
13 (UTC), in the range 0-59.
14 SECONDS - Current seconds (UTC).
15 The base station shall set this field to the current seconds
16 (UTC), in the range 0-59.
3-479
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.31 General Handoff Direction Message
2 MSG_TAG: GHDM
Field Length (bits)
USE_TIME 1
ACTION_TIME 0 or 6
HDM_SEQ 2
SEARCH_INCLUDED 1
SRCH_WIN_A 0 or 4
SRCH_WIN_N 0 or 4
SRCH_WIN_R 0 or 4
T_ADD 0 or 6
T_DROP 0 or 6
T_COMP 0 or 4
T_TDROP 0 or 4
SOFT_SLOPE 0 or 6
ADD_INTERCEPT 0 or 6
DROP_INTERCEPT 0 or 6
EXTRA_PARMS 1
P_REV 0 or 8
PACKET_ZONE_ID 0 or 8
FRAME_OFFSET 0 or 4
PRIVATE_LCM 0 or 1
RESET_L2 0 or 1
RESET_FPC 0 or 1
3-480
3GPP2 C.S0005-A v6.0
Field Length (bits)
ENCRYPT_MODE 0 or 2
NOM_PWR_EXT 0 or 1
NOM_PWR 0 or 4
NUM_PREAMBLE 0 or 3
BAND_CLASS 0 or 5
CDMA_FREQ 0 or 11
RETURN_IF_HANDOFF_FAIL 0 or 1
COMPLETE_SEARCH 0 or 1
PERIODIC_SEARCH 0 or 1
SCR_INCLUDED 0 or 1
SERV_CON_SEQ 0 or 3
RECORD_TYPE 0 or 8
RECORD_LEN 0 or 8
Type-specific fields 0 or 8 x RECORD_LEN
SUP_CHAN_PARMS_INCLUDED 1
FOR_INCLUDED 0 or 1
FOR_SUP_CONFIG 0 or 2
NUM_FOR_SUP 0 or 3
USE_FOR_DURATION 0 or 1
FOR_DURATION 0 or 8
REV_INCLUDED 0 or 1
REV_DTX_DURATION 0 or 4
CLEAR_RETRY_DELAY 0 or 1
USE_REV_DURATION 0 or 1
REV_DURATION 0 or 8
NUM_REV_CODES 0 or 3
USE_T_ADD_ABORT 0 or 1
REV_PARMS_INCLUDED 0 or 1
T_MULCHAN 0 or 3
3-481
3GPP2 C.S0005-A v6.0
Field Length (bits)
USE_PWR_CNTL_STEP 1
PWR_CNTL_STEP 0 or 3
NUM_PILOTS 3
PILOT_PN 9
PWR_COMB_IND 1
FOR_FUND_CODE_CHAN 8
FOR_SUP_INCLUDED 0 or 1
FOR_SUP_CHAN_REC Record 0 or 9 or
(1 + 8 ×
NUM_FOR_SUP)
FPC_SUBCHAN_GAIN 5
USE_PC_TIME 1
PC_ACTION_TIME 0 or 6
DEFAULT_RLAG 0 or 1
NNSCR_INCLUDED 0 or 1
RECORD_TYPE 0 or 8
RECORD_LEN 0 or 8
3-482
3GPP2 C.S0005-A v6.0
Field Length (bits)
USE_NEW_KEY 0 or 1
ENC_KEY_SIZE 0 or 3
KEY_SEQ 0 or 4
SYNC_ID_INCL 0 or 1
SYNC_ID_LEN 0 or 4
SYNC_ID 0 or (8 x
SYNC_ID_LEN)
CC_INFO_INCL 0 or 1

length record
CON_REF 8
RESPONSE_IND 1
TAG 0 or 4
CS_SUPPORTED 1

5 in this message.
13 set to ‘0’ the base station shall omit this field.
14 HDM_SEQ - General Handoff Direction Message sequence number.
3-483
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the handoff message
2 sequence number, as specified in 3.6.6.2.2.10.
12 pilots in the Active Set and the Candidate Set; otherwise, the
16 include the field SRCH_WIN_N and set this field to the window
18 the search window size to by used by mobile stations for the
19 Neighbor Set after completion of the handoff; otherwise, the
23 include the field SRCH_WIN_R and set this field to the window
26 Remaining Set after completion of the handoff; otherwise, the
34 2.6.6.2.5.2).
39 this field.
43 2.6.6.2.3).
3-484
3GPP2 C.S0005-A v6.0

5 this field.
29 active set, or dropping a pilot from the active set (see 2.6.6.2.3
30 and 2.6.6.2.5.2).
32 include the field SOFT_SLOPE in the additional fields and set
33 this field as an unsigned binary number; otherwise, the base
36 the active set (see 2.6.6.2.5.2).
38 include the field ADD_INTERCEPT in the additional fields and
39 set this field as a two's complement signed binary number;
42 from the active set (see 2.6.6.2.3).
44 include the field DROP_INTERCEPT in the additional fields
45 and set this field as a two' complement signed binary number;
47 EXTRA_PARMS - Extra parameters included.
3-485
3GPP2 C.S0005-A v6.0
1 If the mobile station is to change FRAME_OFFSET,

2 PRIVATE_LCM, ENCRYPT_MODE, NOM_PWR, BAND_CLASS,
3 or CDMA_FREQ, or the mobile station is to perform a reset of
4 the acknowledgment procedures, or the mobile station is to
5 reset Forward Traffic Channel power control counters, the
9 If EXTRA_PARMS is set to ‘1’, the base station shall set this
10 field to the base station protocol revision level that the mobile
11 station is to use after completion of the handoff; otherwise,
14 If EXTRA_PARMS is set to ‘1’, the base station shall include
15 the field PACKET_ZONE_ID and set this field as described
18 base station shall set this field to the non-zero packet data
19 services zone identifier that the mobile station is to use after
20 completion of the handoff.
25 FRAME_OFFSET × 1.25 ms relative to system timing (see of
26 [2]).
28 the field FRAME_OFFSET and set this field to the Forward
29 and Reverse Traffic Channel frame offset; otherwise, the base
33 handoff.
35 the field PRIVATE_LCM and set this field as described below;
42 mobile station.
44 the field RESET_L2 and set this field as described below;
3-486
3GPP2 C.S0005-A v6.0

6 control counters.
8 the field RESET_FPC and set this field as described below;
17 the field SERV_NEG_TYPE and set this field as described
22 to ‘0’.
25 the field ENCRYPT_MODE and set this field to the
26 ENCRYPT_MODE value shown in Table 3.7.2.3.2.8-2
27 corresponding to the encryption mode that is to be used for
28 messages sent on the Forward and Reverse Traffic Channels,
29 as specified in 2.3.12.2; otherwise, the base station shall omit
30 this field.
33 this field and set this field as described below; otherwise, the
37 3, the base station shall set this field to ‘0’;.otherwise,
42 station in the open loop power estimate is between -24 dB and
43 -9 dB inclusive; otherwise (the correction factor is in the range
44 -8 dB to 7 dB inclusive), the base station shall set this field to
45 ‘0’.
3-487
3GPP2 C.S0005-A v6.0

2 the field NOM_PWR and set this field to the correction factor
3 to be used by the mobile station in the open loop power
4 estimate, expressed as a two’s complement value in units of 1
5 dB (see [2]); otherwise, the base station shall omit this field.
6 NUM_PREAMBLE - Traffic Channel preamble length.
7 If EXTRA_PARMS is set to ‘0’, the base station shall omit the
8 NUM_PREAMBLE field; otherwise, the base station shall
18 ms units.
21 the field BAND_CLASS and set this field to the CDMA band
22 class corresponding to the CDMA frequency assignment for
23 the CDMA Channel as specified in [30]; otherwise, the base
27 the field CDMA_FREQ and set this field to the CDMA Channel
31 field.
32 RETURN_IF_HANDOFF- - Return on failure flag.
33 _FAIL If EXTRA_PARMS is set to ‘1’, the base station shall include
34 the field RETURN_IF_HANDOFF_FAIL and set this field as
36 field.
37 If the base station includes this field, it shall set this field to
38 ‘1’ if the mobile station is to resume the use of the Active Set
39 on the Serving Frequency following an unsuccessful hard
40 handoff attempt, as specified in 2.6.6.2.8.2; otherwise, the
42 COMPLETE_SEARCH - Flag to complete search.
43 If RETURN_IF_HANDOFF_FAIL is included and is set to ‘1’,
44 the base station shall include the field COMPLETE_SEARCH
45 and set this field as described below; otherwise, the base
3-488
3GPP2 C.S0005-A v6.0
2 ‘1’ if the mobile station is to complete the search of the
3 Candidate Frequency Search Set before resuming the use of
4 the Active Set on the Serving Frequency when an inter-
5 frequency handoff attempt is unsuccessful, as specified in
6 2.6.6.2.8.2; otherwise, the base station shall set this field to
7 ‘0’.
8 PERIODIC_SEARCH - Flag to search the Candidate Frequency periodically.
10 the field PERIODIC_SEARCH and set this field as described
13 ‘1’ if the mobile station is to periodically search the Candidate
14 Frequency, as specified in 2.6.6.2.8.3; otherwise, the base
16 SCR_INCLUDED - Service Configuration Record included indicator.
18 the field SCR_INCLUDED and shall set this field as described
20 The base station shall set this field to ‘1’ if it includes Service
21 Configuration Record in the message; otherwise, the base
24 If SCR_INCLUDED is included and is set to ‘1’, the base
25 station shall include the field SERV_CON_SEQ and shall set
26 this field to the connect sequence number pertaining to this
27 service configuration as specified in 3.6.4.1.2.1.2.
28 If SCR_INCLUDED is included and is set to ‘1’, the base station shall include one
29 occurrence of the following three-field record to specify the service configuration.
32 station shall include the field RECORD_TYPE and shall set
33 this field to the record type value shown in Table 3.7.5-1
34 corresponding to the Service Configuration information
35 record.
38 station shall include the field RECORD_LEN and shall set this
39 field to the number of octets included in the type-specific
40 fields of the Service Configuration information record.
43 station shall include the type specific fields and shall set these
44 fields as specified in 3.7.5.7 for the Service Configuration
3-489
3GPP2 C.S0005-A v6.0
1 SUP_CHAN_PARAMS- - Supplemental channel parameters included indicator.

2 _INCLUDED The base station shall set this field to ‘1’ if the base station
3 includes the FOR_INCLUDED, REV_INCLUDED, and
4 REV_PARMS_INCLUDED fields in the message; otherwise, the
6 FOR_INCLUDED - Forward assignment information included indicator.
7 If SUP_CHAN_PARMS_INCLUDED is set to ‘1’, the base station
8 shall include the field FOR_INCLUDED and set this field as
10 field.
12 ‘1’ if Forward Supplemental Code Channel assignment
13 information is included in the message; otherwise, the base
15 FOR_SUP_CONFIG - Forward Supplemental Code Channel configuration indicator.
16 If FOR_INCLUDED is included and is set to ‘1’, the base
17 station shall include the field FOR_SUP_CONFIG and set this
18 field according to the following rules:
19 The base station shall set this field to ‘00’ if Forward
20 Supplemental Code Channels are not specified in the
21 message, and the mobile station is to stop processing all
22 Forward Supplemental Code Channels.
23 The base station shall set this field to ‘01’ if Forward
24 Supplemental Code Channels are not specified in the
25 message, and the mobile station is to start processing the
26 Forward Supplemental Code Channels previously stored in its
27 Code Channel List, CODE_CHAN_LISTs.
29 Supplemental Code Channels are specified in the message,
30 and the mobile station is to stop processing all Forward
31 Supplemental Code Channels in CODE_CHAN_LISTs, and to
32 update the CODE_CHAN_LISTs, according to the information
33 contained in the message.
35 Supplemental Code Channels are specified in the message,
36 and the mobile station is to update its Code Channel List,
37 CODE_CHAN_LISTs, according to the information contained in
38 the message and to start processing the Forward
40
41 NUM_FOR_SUP - Number of Forward Supplemental Code Channels.
3-490
3GPP2 C.S0005-A v6.0

2 base station shall include the field NUM_FOR_SUP and set it
3 to the number of Forward Supplemental Code Channels
4 assigned to the mobile station; otherwise, the base station
5 shall omit this field. NUM_FOR_SUP shall not exceed the
6 maximum number of Forward Supplemental Code Channels
7 for the negotiated multiplex option.
8 USE_FOR_DURATION - Use forward duration indicator.
9 If FOR_SUP_CONFIG is included and is set to ‘01’ or ‘11’ the
10 base station shall include the field USE_FOR_DURATION and
11 set this field as described below; otherwise the base station
14 FOR_DURATION field is included in the message and the
15 mobile station is to process the Forward Supplemental Code
16 Channels for a time duration indicated by FOR_DURATION.
18 is to process the Forward Supplemental Code Channels for an
19 indefinite duration (i.e., the mobile station is to continue
20 processing Forward Supplemental Code Channels until it
21 receives a subsequent Supplemental Channel Assignment
22 Message or a General Handoff Direction Message that specifies
23 a different Forward Supplemental Code Channel assignment.
24 FOR_DURATION - Duration of Forward Supplemental Code Channel assignment.
25 If USE_FOR_DURATION is included and is set to ‘1’ the base
26 station shall include the field FOR_DURATION and set this
27 field to the allocated duration, in units of 80 ms, for which the
28 mobile station is to process the Forward Supplemental Code
29 Channels; otherwise, the base station shall omit this field.
30 REV_INCLUDED - Reverse assignment information included indicator.
32 shall include the field REV_INCLUDED and set this field as
34 field.
36 ‘1’ if Reverse Supplemental Code Channel assignment
37 information is included in the message; otherwise, the base
39 REV_DTX_DURATION - Reverse Discontinuous Transmission Duration.
40 If REV_INCLUDED is included and is set to ‘1’, the base
41 station shall include the field REV_DTX_DURATION; otherwise
3-491
3GPP2 C.S0005-A v6.0
2 the maximum duration of time in units of 20 ms that the
3 mobile station is allowed to stop transmission on a Reverse
4 Supplemental Code Channel within the reverse assignment
5 duration. The base station shall set this field to ‘0000’ if the
6 mobile station is to stop using a Reverse Supplemental Code
7 Channel once it has stopped transmitting on that Reverse
8 Supplemental Code Channel. The base station shall set this
9 field to ‘1111’ if the mobile station is allowed to resume
10 transmission on a Reverse Supplemental Code Channel at any
11 time within the reverse assignment duration.
12 CLEAR_RETRY_DELAY - Clear retry delay indicator.
14 station shall include the field CLEAR_RETRY_DELAY and set
15 this field as described below; otherwise the base station shall
16 omit this field.
18 mobile station is to clear any existing retry delay which it has
19 stored (see 2.6.6.2.5.1); otherwise, the base station shall set
21 USE_REV_DURATION - Use reverse duration indicator.
23 station shall include the field USE_REV_DURATION and set
25 omit this field.
27 REV_DURATION field is included in the message and the
28 mobile station is allowed to transmit on the Reverse
29 Supplemental Code Channels for a time duration indicated by
30 REV_DURATION.
32 is allowed to transmit on the Reverse Supplemental Code
33 Channels for an indefinite duration (i.e., the mobile station
34 may continue to transmit on the Reverse Supplemental Code
35 Channels until it receives a subsequent Supplemental Channel
37 that specifies a different Reverse Supplemental Code Channel
38 assignment.
39 REV_DURATION - Duration of Reverse Supplemental Code Channel Assignment.
40 If USE_REV_DURATION is included and is set to ‘1’, the base
41 station shall include the field REV_DURATION and set this
42 field to the allocated duration, in units of 80 ms, for which the
43 mobile station may transmit on Reverse Supplemental Code
44 Channels; otherwise the base station shall omit this field.
45 NUM_REV_CODES - Number of Reverse Supplemental Code Channels.
3-492
3GPP2 C.S0005-A v6.0

2 station shall include the field NUM_REV_CODES and set this
3 field to the number of Reverse Supplemental Code Channels
4 which are assigned to the mobile station; otherwise the base
8 station shall include the field USE_T_ADD_ABORT and set
10 omit this field.
12 mobile station is to use the T_ADD Reverse Supplemental
13 Code Channel abort feature for this reverse assignment;
15 REV_PARMS-
16 _INCLUDED - Reverse assignment parameters included indicator.
18 shall include the field REV_PARMS_INCLUDED and set this
20 this field.
22 ‘1’ if the following three fields are included in the message;
25 reporting offset.
26 If REV_PARMS_INCLUDED is included and is set to ‘1’, the
27 base station shall include the field T_MULCHAN and set this
28 field as described below; otherwise the base station shall omit
29 this field.
30 The base station shall set this field to the threshold offset that
31 the mobile station is to use when reporting neighbor pilot
32 strength measurements in a Supplemental Channel Request
33 Message. The mobile station is to interpret this field as an
34 offset to T_ADD ranging from 0.5 dB (corresponding to
35 T_MULCHAN = ‘000’) to 4.0 dB (corresponding to T_MULCHAN
36 = ‘111’), in 0.5 dB increments.
41 base station shall include the field BEGIN_PREAMBLE and set
42 this field to the number of Reverse Supplemental Code
43 Channel preamble frames that the mobile station is to send
44 when beginning transmission on Reverse Supplemental Code
45 Channels; otherwise the base station shall omit this field.
3-493
3GPP2 C.S0005-A v6.0

2 base station shall include the field RESUME_PREAMBLE and
3 set this field to the number of Reverse Supplemental Code
4 Channel preamble frames that the mobile station is to send
5 when resuming transmission on a Reverse Supplemental Code
6 Channel following an autonomous suspension of transmission
7 on an allocated Supplemental Code Channel; otherwise the
9 USE_PWR_CNTL_STEP - Power control step size indicator.
10 The base station shall set this field to ‘1’ if the field
11 PWR_CNTL_STEP is included in the message.
12 PWR_CNTL_STEP - Power control step size.
13 If USE_PWR_CNTL_STEP is set to ‘1’, then the base station
14 shall include the field PWR_CNTL_STEP and set this field to
15 the step size that the mobile station is to use for closed loop
16 power control, according to Table 3.7.3.3.2.25-1; otherwise,
20 included in the message. The base station shall set this field
21 to an integer that is equal to or greater than 1.
22
23 The base station shall include one occurrence of the following four-part record for each of
24 the NUM_PILOTS pilots included in the message:
33 this field to ‘0’. The base station shall set this field to ‘0’ in
34 the first record in the pilot list.
35 FOR_FUND_CODE- - Forward Fundamental Channel.
36 _CHAN The base station shall set this field to the code channel index
37 to be used for the Forward Fundamental Channel associated
38 with this pilot.
39 FOR_SUP_INCLUDED - Forward Supplemental Code Channel included.
40 The base station shall include this field if FOR_SUP_CONFIG
41 is included and is set to ‘10’ or ‘11’. If included, the base
42 station shall set this field to ‘1’ if there are Supplemental Code
44 FOR_SUP_CHAN_REC - Forward Supplemental Code Channel record
3-494
3GPP2 C.S0005-A v6.0
1 If FOR_SUP_INCLUDED is set to ‘1’, the base station shall

2 include the record FOR_SUP_CHAN_REC and set its fields as
4 record.
5 FOR_SUP_CHAN_REC contains information about Forward
6 Supplemental Code Channels associated with this pilot, and
7 consists of the field EXPL_CODE_CHAN, and either the
8 BASE_CODE_CHAN field or NUM_FOR_SUP occurrences of
9 the FOR_SUP_CODE_CHAN field, as shown below.
10
EXPL_CODE_CHAN 1
BASE_CODE_CHAN 0 or 8
11
12 If EXPL_CODE_CHAN is equal to ‘1’, NUM_FOR_SUP
13 occurrences of the following field:
FOR_SUP_CODE_CHAN 8
14 EXPL_CODE_CHAN - Explicit code channel indicator.

15 The base station shall set this field to ‘1’ to indicate explicit
16 assignment of each Forward Supplemental Code Channel by
17 means of the field FOR_SUP_CODE_CHAN. The base station
18 shall set this field to ‘0’ if the mobile station is to use
19 NUM_FOR_SUP adjacent code channels beginning with index
20 BASE_CODE_CHAN (i.e., BASE_CODE_CHAN through
21 BASE_CODE_CHAN + NUM_FOR_SUP - 1).
22 In both cases (i.e., the explicit code channel list format and
23 range format), the order of the code channel indices is the
24 same for all pilots specified in this message (i.e., for each pilot,
25 the ith entry in the list indicates the code channel index to be
26 used for the ith Forward Supplemental Code Channel
27 associated with that pilot).
28 BASE_CODE_CHAN - Base code channel index.
29 If the EXPL_CODE_CHAN field is included and is set to ‘0’ the
30 base station shall include the field BASE_CODE_CHAN and
31 set this field as described below; otherwise the base station
33 The base station shall set this field to the base code channel
34 index (see [2]) in the range of 1 to (63 - NUM_FOR_SUP + 1),
35 inclusive, that the mobile station is to use as the first Forward
36 Supplemental Code Channel associated with this pilot. The
37 mobile station is to use code channel index
38 (BASE_CODE_CHAN + i - 1), where i ranges from 1 to
39 NUM_FOR_SUP, for the ith Forward Supplemental Code
40 Channel associated with this pilot.
41 FOR_SUP_CODE_CHAN - Forward Supplemental Code Channel.
3-495
3GPP2 C.S0005-A v6.0
1 If EXPL_CODE_CHAN is included and is set to ‘1, the base

2 station shall include NUM_FOR_SUP occurrences of the field
3 FOR_SUP_CODE_CHAN and set this field as described below;
5 The base station shall set the ith occurrence of this field to the
6 code channel index (see [2]), in the range 1 to 63 inclusive,
7 that the mobile station is to use for the ith Forward Code
8 Channel associated with this pilot.
12 relative to that of 20 ms frames at a 9600 bps or 14400 bps
13 rate on the Forward Fundamental Channel or the Forward
14 Dedicated Control Channel that the Forward Power Control
15 Subchannel is punctured on. The base station shall set the
16 value in units of 0.25 dB.
17 USE_PC_TIME - Use power control action time indicator.
18 This field indicates whether an explicit time
19 [PC_ACTION_TIME] at which a new value for Power Control
20 Subchannel to traffic ratio (FPC_SUBCHAN_GAIN] takes effect
21 is specified in the message.
25 PC_ACTION_TIME - Power Control Subchannel gain action time.
26 If the USE_PC_TIME field is set to ‘1’, the base station shall
27 set this field to the System Time, in units of 80 ms (modulo
28 64), at which FPC_SUBCHAN_GAIN specified in this message
29 is to take effect. If the USE_PC_TIME field is set to ‘0’ the
31 RLGAIN_TRAFFIC-
32 _PILOT - Gain adjustment of the Reverse Traffic Channel relative to the
33 Reverse Pilot Channel power for Radio Configurations greater
34 than 2.
36 this field and set it to the correction factor to be used by
37 mobile stations in setting the power of a code channel,
38 expressed as a two’s complement value in units of 0.125 dB
39 (see 2.1.2.3.3 of [2]); otherwise, the base station shall omit
40 this field.
41 DEFAULT_RLAG - Default reverse link attribute gain used indicator.
42 If EXTRA_PARMS is set to ‘0’, the base station shall omit this
43 field; otherwise, the base station set this field as follows.
3-496
3GPP2 C.S0005-A v6.0
1 If the mobile station is to use the default values for the reverse
2 link attribute gain, as specified in [2] after completion of
3 handoff, the base station shall set this field to ‘1’; otherwise,
5 NNSCR_INCLUDED - Non-negotiable Service Configuration Record included
6 indicator.
7 The base station shall omit this field, if EXTRA_PARMS is set
8 to ‘0’; otherwise, the base station shall include this field and
9 set this field as described below:
10 The base station shall set this field to ‘1’, if the Non-negotiable
11 Service Configuration record is included in this message;
13 If NNSCR_INCLUDED is included and is set to ‘1’, the base station shall include one
14 occurrence of the following three-field record to specify the non-negotiable service
15 configuration parameters.
17 If NNSCR_INCLUDED is included and is set to ‘1’, the base
20 corresponding to the Non-Negotiable Service Configuration
26 fields of the Non-Negotiable Service Configuration information
27 record.
31 fields as specified in 3.7.5.20 for the Non-Negotiable Service
33 .
34 REV_FCH-
37 is allowed to perform the reverse eighth gating mode after
38 handoff; otherwise, the base station shall set this field to ‘0’.
39 REV_PWR-
3-497
3GPP2 C.S0005-A v6.0

4 REV_PWR-
15 after handoff, in units of 1.25 ms. To disable the gating on the
16 reverse Fundamental Channel, the base station shall set this
17 field to ‘000’.
18 D_SIG_ENCRYPT_MODE - Dedicated channel General encryption mode indicator.
19 If ENCRYPT_MODE is included and is set to ‘11’, the base station
20 shall include this field and shall set it to the dedicated channel
21 signaling message encryption mode, as shown in Table 3.7.4.5-1;
24 If ENCRYPT_MODE is included and is set to ‘10’ or ‘11’, the base
25 station shall include this field. If this field is included, the base
26 station shall set this field to ‘0’ to indicate that the stored
27 encryption key to be used by the mobile station. Otherwise, the
28 base station shall set this field to ‘1’ to indicate that the new
29 encryption key to be used by the mobile station.
31 If ENCRYPT_MODE is included and is set to ‘10’ or
32 ‘11’USE_NEW_KEY is included and is set to ‘0’, the base
34 include this field and set it to the encryption key size, as
35 shown in Table 3.7.4.5-2;this field as described below
37 The base station shall set this field to the encryption key size, as
38 shown in Table 3.7.4.5-2.
44 station.
45 CC_INFO_INCL - Call Control information included indicator.
3-498
3GPP2 C.S0005-A v6.0
1 If the SCR_INCLUDED field is not included or is included but


8 indicator.
9 If either the SCR_INCLUDED field is included and is set to ‘1’

10 or the NNSCR_INCLUDED field is included and is set to ‘1’,
11 the base station shall include this field; otherwise, the base
12 station shall omit this field. If included, the base station shall
13 set this field as follows:
14 The base station shall set this field to ‘1’ if the SYNC_ID field
15 is included in this message; otherwise, the base station shall



30 by this message.

3-499
3GPP2 C.S0005-A v6.0
4 length record (CON_REF, RESPONSE_IND, TAG, BYPASS_ALERT_ANSWER as per the
5 following requirements).

21 BYPASS_ALERT-

26 If the mobile station is to bypass the Waiting for Order Substate

27 and the Waiting for Mobile Station Answer Substate for this call,
30

3-500
3GPP2 C.S0005-A v6.0
3-501
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.32 Resource Allocation Message
2 MSG_TAG: RAM
Field Length (bits)
USE_TIME 1
ACTION_TIME 0 or 6
FPC_PRI_CHAN 1

7 in this message.
14 at which this message is to take effect. If the USE_TIME field
26 Channel.
3-502
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.33 Resource Allocation Mini Message
2 MSG_TAG: RAMM
Field Length (bits)
USE_TIME 1
ACTION_TIME 0 or 6
FPC_PRI_CHAN 1

7 this message.
26 Channel.
3-503
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.34 Extended Release Message
2 MSG_TAG: ERM
Field Length (bits)
USE_TIME 1
ACTION_TIME 0 or 6
CH_IND 3
GATING_RATE_INCL 1
PILOT_GATING_RATE 0 or 2

7 in this message.
16 CH_IND - Channel Indicator.

18 3.7.3.3.2.34-1, to release physical resources.
3-504
3GPP2 C.S0005-A v6.0
CH_IND Physical Resource(s) Released

(binary)
000 Reserved
011 Reserved
100 Continuous Reverse Pilot Channel
Fundamental Channel and
101
Continuous Reverse Pilot Channel
110 Dedicated Control Channel and Continuous
Reverse Pilot Channel
111 Fundamental Channel, Dedicated Control

Channel, and Continuous Reverse Pilot
Channel
2
3 GATING_RATE_INCL - Reverse pilot gating rate included flag.

5 PILOT_GATING_RATE field is included, otherwise it shall set
7 PILOT_GATING_RATE - Actual Reverse Pilot gating Rate.
8 If the GATING_RATE_INCL field is set to ‘1’ then the base
9 station shall set this field to the PILOT_GATING_RATE field
10 shown in Table 3.7.3.3.2.34-2 corresponding to the actual
11 gating rate on the Reverse Pilot Channel; otherwise, the base
13
14 Table 3.7.3.3.2.34-2. Actual Reverse Pilot Gating rate
PILOT_GATING_RATE field Meaning

(binary)
00 Gating rate 1
01 Gating rate ½
10 Gating rate ¼
11 Reserved
3-505
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.35 Extended Release Mini Message
2 MSG_TAG: ERMM
Field Length (bits)
USE_TIME 1
ACTION_TIME 0 or 6
CH_IND 3
GATING_RATE_INCL 1

7 this message.

18 3.7.3.3.2.34-1, to release physical resources.
19 GATING_RATE_INCL - Reverse pilot gating rate included flag.
21 PILOT_GATING_RATE field is included, otherwise it shall set
23 PILOT_GATING_RATE - Actual Reverse Pilot gating Rate.
24 If the GATING_RATE_INCL field is set to ‘1’ then the base
25 station shall set this field to the PILOT_GATING_RATE field
26 shown in Table 3.7.3.3.2.34-2 corresponding to the actual
27 gating rate on the Reverse Pilot Channel; otherwise, the base
3-506
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.36 Universal Handoff Direction Message
2 MSG_TAG: UHDM
Field Length (bits)
USE_TIME 1
ACTION_TIME 0 or 6
HDM_SEQ 2
PARMS_INCL 1
P_REV 0 or 8
SEARCH_INCLUDED 1
SRCH_WIN_A 0 or 4
SRCH_WIN_N 0 or 4
SRCH_WIN_R 0 or 4
T_ADD 0 or 6
T_DROP 0 or 6
T_COMP 0 or 4
T_TDROP 0 or 4
SOFT_SLOPE 0 or 6
ADD_INTERCEPT 0 or 6
DROP_INTERCEPT 0 or 6
EXTRA_PARMS 1
PACKET_ZONE_ID 0 or 8
FRAME_OFFSET 0 or 4
PRIVATE_LCM 0 or 1
RESET_L2 0 or 1
RESET_FPC 0 or 1
3-507
3GPP2 C.S0005-A v6.0
Field Length (bits)
ENCRYPT_MODE 0 or 2
NOM_PWR_EXT 0 or 1
NOM_PWR 0 or 4
DEFAULT_RLAG 0 or 1
NUM_PREAMBLE 0 or 3
BAND_CLASS 0 or 5
CDMA_FREQ 0 or 11
RETURN_IF_HANDOFF_FAIL 0 or 1
COMPLETE_SEARCH 0 or 1
PERIODIC_SEARCH 0 or 1
SCR_INCLUDED 0 or 1
SERV_CON_SEQ 0 or 3
RECORD_TYPE 0 or 8
RECORD_LEN 0 or 8
NNSCR_INCLUDED 0 or 1
RECORD_TYPE 0 or 8
RECORD_LEN 0 or 8
3-508
3GPP2 C.S0005-A v6.0
Field Length (bits)
USE_PWR_CNTL_STEP 1
PWR_CNTL_STEP 0 or 3
CLEAR_RETRY_DELAY 1
SCH_INCL 1
NUM_FOR_ASSIGN 0 or 2
The base station shall include NUM_FOR_ASSIGN
occurrences of the following fields
FOR_SCH_ID 1
FOR_SCH_DURATION 4
FOR_SCH_START_TIME_INCL 1
FOR_SCH_START_TIME 0 or 5
SCCL_INDEX 4
NUM_REV_ASSIGN 0 or 2
The base station shall include NUM_REV_ASSIGN
occurrences of the following fields
REV_SCH_ID 1
REV_SCH_DURATION 4
REV_SCH_START_TIME_INCL 1
REV_SCH_START_TIME 0 or 5
REV_SCH_NUM_BITS_IDX 4
FPC_SUBCHAN_GAIN 5
USE_PC_TIME 1
PC_ACTION_TIME 0 or 6
3-509
3GPP2 C.S0005-A v6.0
Field Length (bits)
CH_IND 3
ACTIVE_SET_REC_LEN 8
ACTIVE_SET_REC_FIELDS 8x
ACTIVE_SET_REC_LEN
USE_NEW_KEY 0 or 1
ENC_KEY_SIZE 0 or 3
KEY_SEQ 0 or 4
3XFL_1XRL_INCL 1
1XRL_FREQ_OFFSET 0 or 2
SYNC_ID_INCL 0 or 1
SYNC_ID_LEN 0 or 4
SYNC_ID 0 or (8 x SYNC_ID_LEN)
CC_INFO_INCL 0 or 1

length record:
CON_REF 8
RESPONSE_IND 1
TAG 0 or 4
CS_SUPPORTED 1
2 If CH_IND = ‘101’, the ACTIVE_SET_REC_FIELDS shall be:

3
3-510
3GPP2 C.S0005-A v6.0
NUM_FOR_SCH 0 or 5
NUM_FOR_SCH occurrences of the following three fields:
FOR_SCH_ID 1
SCCL_INDEX 4
FOR_SCH_NUM_BITS_IDX 4
NUM_REV_SCH 0 or 5
NUM_REV_SCH occurrences of the following three fields:
REV_SCH_ID 1
REV_WALSH_ID 1
NUM_PILOTS 3
SRCH_OFFSET_INCL 1
PILOT_PN 9
SRCH_OFFSET 0 or 3
RECORD_LEN 0 or 3
PWR_COMB_IND 1
CODE_CHAN_FCH 11
QOF_MASK_ID_FCH 2
NUM_SCH 0 or 5
NUM_SCH occurrences of the following record
FOR_SCH_ID 1
SCCL_INDEX 4
PILOT_INCL 1

2
3-511
3GPP2 C.S0005-A v6.0
CODE_CHAN_SCH 0 or 11
QOF_MASK_ID_SCH 0 or 2
3X_FCH_INFO_INCL 1
NUM_PILOTS occurrences of the following record if

3X_FCH_LOW_INCL 1
CODE_CHAN_FCH_LOW 0 or 11
3X_FCH_HIGH_INCL 1
CODE_CHAN_FCH_HIGH 0 or 11
3X_SCH_INFO_INCL 0 or 1
NUM_SCH occurrences of the following record if
3X_SCH_INFO_INCL is included and set to ‘1’:
FOR_SCH_ID 1
3X_SCH_LOW_INCL 1
QOF_MASK_ID_SCH_LOW 0 or 2
CODE_CHAN_SCH_LOW 0 or 11
3X_SCH_HIGH_INCL 1
QOF_MASK_ID_SCH_HIGH 0 or 2
CODE_CHAN_SCH_HIGH 0 or 11
3 If CH_IND = ‘010’ or ‘110’, the ACTIVE_SET_REC_FIELDS shall be:

4
3-512
3GPP2 C.S0005-A v6.0
NUM_FOR_SCH 0 or 5
FOR_SCH_ID 1
SCCL_INDEX 4
NUM_REV_SCH 0 or 5
REV_SCH_ID 1
REV_WALSH_ID 1
NUM_PILOTS 3
SRCH_OFFSET_INCL 1
PILOT_PN 9
SRCH_OFFSET 0 or 3
RECORD_LEN 0 or 3
PWR_COMB_IND 1
CODE_CHAN_DCCH 11
QOF_MASK_ID_DCCH 2
NUM_SCH 0 or 5
NUM_SCH occurrences of the following five fields:
FOR_SCH_ID 1
SCCL_INDEX 4
PILOT_INCL 1
3-513
3GPP2 C.S0005-A v6.0
3X_DCCH_INFO_INCL 1

3X_DCCH_LOW_INCL 1
3X_DCCH_HIGH_INCL 1
CODE_CHAN_DCCH_HIGH 0 or 11
FOR_SCH_ID 1
3X_SCH_LOW_INCL 1
3X_SCH_HIGH_INCL 1
4 If CH_IND = ‘111’, the ACTIVE_SET_REC_FIELDS shall be:

5
3-514
3GPP2 C.S0005-A v6.0
NUM_FOR_SCH 0 or 5
FOR_SCH_ID 1
SCCL_INDEX 4
NUM_REV_SCH 0 or 5
REV_SCH_ID 1
REV_WALSH_ID 1
NUM_PILOTS 3
SRCH_OFFSET_INCL 1
PILOT_PN 9
SRCH_OFFSET 0 or 3
RECORD_LEN 0 or 3
PWR_COMB_IND 1
CODE_CHAN_FCH 11
QOF_MASK_ID_FCH 2
CODE_CHAN_DCCH 11
QOF_MASK_ID_DCCH 2
NUM_SCH 0 or 5
NUM_SCH occurrences of the following five field record:
FOR_SCH_ID 1

2
3-515
3GPP2 C.S0005-A v6.0
SCCL_INDEX 4
PILOT_INCL 1
3X_FCH_INFO_INCL 1
3X_DCCH_INFO_INCL 1

3X_FCH_INFO_INCL or 3X_DCCH_INFO_INCL is set to ‘1’:
3X_FCH_LOW_INCL 0 or 1
CODE_CHAN_ FCH_ LOW 0 or 11
3X_FCH_HIGH_INCL 0 or 1
QOF_MASK_ID_FCH_ HIGH 0 or 2
CODE_CHAN_ FCH_ HIGH 0 or 11
3X_DCCH_LOW_INCL 0 or 1
CODE_CHAN_ DCCH_LOW 0 or 11
3X_DCCH_HIGH_INCL 0 or 1
CODE_CHAN_ DCCH_HIGH 0 or 11
FOR_SCH_ID 1
3X_SCH_LOW_INCL 1
3X_SCH_HIGH_INCL 1
3-516
3GPP2 C.S0005-A v6.0

2 in this message.
10 set to ‘0’ the base station shall omit this field.
11 HDM_SEQ - Universal Handoff Direction Message sequence number.
15 The base station shall set this field to the handoff message
16 sequence number, as specified in 2.6.6.2.2.10.
17 PARMS_INCL - Parameters included indicator.
18 The base station shall set this field to ‘1’, if P_REV and
19 SERV_NEG_TYPE are included; otherwise, the base station
20 shall set this field ‘0’.
22 If PARMS_INCL is set to ‘1’, the base station shall set this field
23 to the base station protocol revision level that the mobile
24 station is to use after completion of the handoff; otherwise,
27 If PARMS_INCL is set to ‘1’, the base station shall include the
28 field SERV_NEG_TYPE and set this field as described below;
33 to ‘0’.
43 pilots in the Active Set and the Candidate Set; otherwise, the
3-517
3GPP2 C.S0005-A v6.0

3 include the field SRCH_WIN_N and set this field to the window
6 Neighbor Set after completion of the handoff; otherwise, the
10 include the field SRCH_WIN_R and set this field to the window
13 Remaining Set after completion of the handoff; otherwise, the
21 2.6.6.2.5.2).
26 this field.
30 2.6.6.2.3).
35 this field.
3-518
3GPP2 C.S0005-A v6.0

16 2.6.6.2.3 and 2.6.6.2.5.2).
18 include the field SOFT_SLOPE in the additional fields and set
19 this field as an unsigned binary number; otherwise, the base
24 include the field ADD_INTERCEPT in the additional fields and
25 set this field as a two's complement signed binary number;
30 include the field DROP_INTERCEPT in the additional fields
31 and set this field as a two's complement signed binary
32 number; otherwise, the base station shall omit this field.
33 EXTRA_PARMS - Extra parameters included.
34 If the base station includes the fields PACKET_ZONE_ID,
35 FRAME_OFFSET, PRIVATE_LCM, RESET_L2, RESET_FPC,
36 SERV_NEG_TYPE, ENCRYPT_MODE, NOM_PWR_EXT,
37 NOM_PWR, RLGAIN_TRAFFIC_PILOT, DEFAULT_RLAG,
38 NUM_PREAMBLE, BAND_CLASS, PERIODIC_SEARCH, or
39 CDMA_FREQ in this message, the base station shall set this
43 the field PACKET_ZONE_ID and set this field as described
3-519
3GPP2 C.S0005-A v6.0

2 base station shall set this field to the non-zero packet data
3 services zone identifier that the mobile station is to use after
4 completion of the handoff.
11 the field FRAME_OFFSET and set this field to the Forward
12 and Reverse Traffic Channel frame offset; otherwise, the base
16 handoff.
18 the field PRIVATE_LCM and set this field as described below;
25 mobile station.
27 the field RESET_L2 and set this field as described below;
34 control counters.
36 the field RESET_FPC and set this field as described below;
3-520
3GPP2 C.S0005-A v6.0

3 the field ENCRYPT_MODE and set this field to the
4 ENCRYPT_MODE value shown in Table 3.7.2.3.2.8-2
5 corresponding to the encryption mode that is to be used for
6 messages sent on the Forward and Reverse Traffic Channels,
7 as specified in 2.3.12.2; otherwise, the base station shall omit
8 this field.
11 this field and set this field as described below; otherwise, the
15 3, the base station shall set this field to ‘0’; otherwise,.
20 station in the open loop power estimate is between -24 dB and
21 -9 dB inclusive; otherwise (the correction factor is in the range
22 -8 dB to 7 dB inclusive), the base station shall set this field to
23 ‘0’.
26 the field NOM_PWR and set this field to the correction factor
27 to be used by the mobile station in the open loop power
28 estimate, expressed as a two’s complement value in units of 1
29 dB (see [2]); otherwise, the base station shall omit this field.
31 Reverse Pilot Channel power for Radio configurations greater
32 than 2.
34 this field and set it to the correction factor to be used by
35 mobile stations in setting the power of a reverse traffic
36 channel, expressed as a two’s complement value in units of
37 0.125 dB (see 2.1.2.3.3 of [2]; otherwise, the base station shall
38 omit this field.
39 DEFAULT_RLAG - Default reverse link attribute gain used indicator.
41 field; otherwise, the base station set this field as follows:
42 If the mobile station is to use the default values for the reverse
43 link attribute gain, as specified in Table 2.1.2.3.3-1 of [2] after
44 completion of handoff, the base station shall set this field to
46 NUM_PREAMBLE - Number of Traffic Channel preamble.
3-521
3GPP2 C.S0005-A v6.0
1 If EXTRA_PARMS is set to ‘0’, the base station shall omit the

2 NUM_PREAMBLE field; otherwise, the base station shall
12 ms units.
15 the field BAND_CLASS and set this field to the CDMA band
16 class corresponding to the CDMA frequency assignment for
17 the CDMA Channel as specified in [30]; otherwise, the base
21 field; otherwise, the base station shall set this field as follows:
22 If a Radio Configuration associated with Spreading Rate 1 is
23 used, the base station shall set this field to the CDMA
24 Channel number, in the specified CDMA band class,
26 CDMA Channel as specified in [2]. If a Radio Configuration
27 associated with Spreading Rate 3 is used, the base station
28 shall include the field CDMA_FREQ and set this field to the
29 CDMA Channel number, in the specified CDMA band class,
30 corresponding to the CDMA center SR3 frequency assignment
31 for the CDMA Channel..
32 RETURN_IF-
33 _HANDOFF_FAIL - Return on failure flag.
35 the field RETURN_IF_HANDOFF_FAIL and set this field as
37 field.
39 ‘1’ if the mobile station is to resume the use of the Active Set
40 on the Serving Frequency following an unsuccessful hard
41 handoff attempt, as specified in 2.6.6.2.8.2; otherwise, the
43 COMPLETE_SEARCH - Flag to complete search.
44 If RETURN_IF_HANDOFF_FAIL is included and is set to ‘1’,
45 the base station shall include the field COMPLETE_SEARCH
46 and set this field as described below; otherwise, the base
3-522
3GPP2 C.S0005-A v6.0
2 ‘1’ if the mobile station is to complete the search of the
3 Candidate Frequency Search Set before resuming the use of
4 the Active Set on the Serving Frequency when an inter-
5 frequency handoff attempt is unsuccessful, as specified in
6 2.6.6.2.8.2; otherwise, the base station shall set this field to
7 ‘0’.
8 PERIODIC_SEARCH - Flag to search the Candidate Frequency periodically.
10 the field PERIODIC_SEARCH and set this field as described
13 ‘1’ if the mobile station is to periodically search the Candidate
14 Frequency, as specified in 2.6.6.2.8.3; otherwise, the base
16 SCR_INCLUDED - Service Configuration Record included indicator.
18 the field SCR_INCLUDED and shall set this field as described
20 The base station shall set this field to ‘1’ if it includes the
21 Service Configuration Record in the message; otherwise, the
25 station shall include the field SERV_CON_SEQ and shall set
26 this field to the connect sequence number pertaining to this
27 service configuration as specified in 3.6.4.1.2.1.2.
28 If SCR_INCLUDED is included and is set to ‘1’, the base station shall include one
29 occurrence of the following three-field record to specify the service configuration.
34 corresponding to the Service Configuration information
35 record.
40 fields of the Service Configuration information record.
44 fields as specified in 3.7.5.7 for the Service Configuration
3-523
3GPP2 C.S0005-A v6.0
1 NNSCR_INCLUDED - Non-negotiable Service Configuration Record Included

2 indicator
3 The base station shall omit this field, if EXTRA_PARMS is set
4 to ‘0’; otherwise, the base station shall include this field and
5 set this field as described below:
6 The base station shall set this field to ‘1’, if the Non-negotiable
7 Service Configuration record is included in this message;
9 If NNSCR_INCLUDED is included and is set to ‘1’, the base station shall include one
10 occurrence of the following three-field record to specify the non-negotiable service
11 configuration.
16 corresponding to the Non-Negotiable Service Configuration
22 fields of the Non-Negotiable Service Configuration information
23 record.
27 fields as specified in 3.7.5.20 for the Non-Negotiable Service
29 USE_PWR_CNTL_STEP - Power control step size indicator.
30 The base station shall set this field to ‘1’ if the field
31 PWR_CNTL_STEP is included in the message.
32 PWR_CNTL_STEP - Power control step size.
33 If USE_PWR_CNTL_STEP is set to ‘1’, then the base station
34 shall include the field PWR_CNTL_STEP and set this field to
35 the step size that the mobile station is to use for closed loop
36 power control, according to Table 3.7.3.3.2.25-1; otherwise,
38 CLEAR_RETRY_DELAY - Clear retry delay indicator.
40 is to clear any existing retry delay which it has stored (see
42 ‘0’.
43 SCH_INCL - SCH related parameters included indicator.
3-524
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to '1' if this message
2 include the NUM_FOR_ASSIGN, NUM_REV_ASSIGN,
3 NUM_FOR_SCH, NUM_REV_SCH, and NUM_SCH fields.
4 Otherwise, the base station shall set this field to '0'.
5 NUM_FOR-
6 _ASSIGN - Number of Forward Supplemental Channel assigned.
7 If SCH_INCL is set to ‘0’, the base station shall omit this field;
8 otherwise, the base station shall set this field to the number of
9 Forward Supplemental Channel assigned.
10 The base station shall include NUM_FOR_ASSIGN occurrences of the following five fields
11 (FOR_SCH_ID, FOR_SCH_DURATION, FOR_SCH_START_TIME_INCL,
12 FOR_SCH_START_TIME, and SCCL_INDEX).
13
14 FOR_SCH_ID - Forward Supplemental Channel identifier.

15 The base station shall set this field to the Identifier of the
16 Forward Supplemental Channel.
17 FOR_SCH_DURATION - Duration of Forward Supplemental Channel assignment.

18 The base station shall set this field to the duration (see Table
19 3.7.3.3.2.37-3), starting at the start time of the message
20 specified by FOR_START_TIME, during which the mobile
21 station is to process the Forward Supplemental Channel.
22 The base station shall set this field to ‘0000’ to indicate that
23 the mobile station should stop processing the Forward
24 Supplemental Channel starting at the explicit start time of the
25 message specified by FOR_SCH_START_TIME or at the
26 implicit start time if FOR_SCH_START_TIME_INCL is set to ‘0’.
28 the mobile station should process the Forward Supplemental
29 Channel, starting at the start time of the message specified by
30 FOR_SCH_START_TIME, until the start time specified by a
31 subsequent Forward Supplemental Channel assignment
32 corresponding to the same forward Supplemental Channel
33 (see 2.6.6.2.5.1.1).
34 FOR_SCH_
35 START_TIME_INCL - Start time included indicator.
36 If FOR_SCH_DURATION is not equal to ‘0000’, the base

37 station shall set this field to ‘1’. If FOR_SCH_DURATION is
38 equal to ‘0000’, the base station shall set this field as follows:
3-525
3GPP2 C.S0005-A v6.0

2 FOR_SCH_START_TIME is included in this message;
4 FOR_SCH_START_TIME - Start time for Forward Supplemental Channel Assignment.
5 If FOR_SCH_START_TIME INCL is set to ‘0’, the base station

6 shall omit this field; otherwise, the base station shall set this
7 field to the System Time, in units of time specified by
8 START_TIME_UNIT, (modulo 32) at which the mobile station is
9 to start processing the Forward Supplemental Channel
10 specified in this message. The explicit start time for
11 processing Forward Supplemental Channels is the time for
12 which
13 (t/(START_TIME_UNIT+1) − FOR_SCH_START_TIME) mod 32

14 = 0,
16 SCCL_INDEX - Supplemental Channel Code list index.
17 The base station shall set this field to the index of the record
18 in the Forward Supplemental Channel Code list corresponding
19 to the FOR_SCH_ID. The base station shall include an
20 SCCL_INDEX whose SCH Active Set is a subset of the Active
21 Set of the Fundamental Channel, Dedicated Control Channel,
22 or both.
23 NUM_REV-
24 _ASSIGN - Number of Reverse Supplemental Channel assigned.
26 otherwise, the base station shall set this field to the number of
27 Reverse Supplemental Channel assigned.
28 The base station shall include NUM_REV_ASSIGN occurrences of the following five fields
29 (REV_SCH_ID, REV_SCH_DURATION, REV_SCH_START_TIME_INCL,
30 REV_SCH_START_TIME, and REV_SCH_NUM_BITS_IDX).
31 REV_SCH_ID - Reverse Supplemental Channel Identifier.

32 The base station shall set this field to the identifier of the
33 Reverse Supplemental Channel.
34 REV_SCH-
35 _DURATION - Duration of Reverse Supplemental Channel assignment.
3-526
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to '0000' to indicate that
2 the mobile station is to stop transmitting on the Reverse
3 Supplemental Channel specified by REV_SCH_ID at the
4 explicit action time specified by REV_SCH_START_TIME or at
5 the implicit start time if REV_SCH_START_TIME_INCL is set
6 to ‘0’. The base station shall set this field to '1111' to indicate
7 that the mobile station may transmit on the Reverse
8 Supplemental Channel specified by REV_SCH_ID, starting at
9 the explicit start time specified by REV_SCH_START_TIME in
10 this message, until the start time specified by a subsequent
11 Reverse Supplemental Channel assignment corresponding to
12 the same Supplemental Channel (see 2.6.6.2.5.1.1). The base
13 station shall set this field to the duration according to Table
14 3.7.3.3.2.37-3, starting at the explicit start time specified by
15 REV_SCH_START_TIME, during which the mobile station may
16 transmit on the Reverse Supplemental Channel specified by
17 REV_SCH_ID.
18 REV_SCH-
19 _START_TIME_INCL - Start time included indicator.

20 If REV_SCH_DURATION is not equal to ‘0000’, the base
21 station shall set this field to ‘1’. If REV_SCH_DURATION is

24 REV_SCH_START_TIME is included in this message;
26 REV_SCH_START_TIME - Start time for Reverse Supplemental Channel Assignment.
27 If REV_SCH_START_TIME_INCL is set to ‘0’, the base station

30 START_TIME_UNIT, (modulo 32) at which the mobile station
31 may start transmitting on the Reverse Supplemental Channel
33 transmitting on the Reverse Supplemental Channel is the time
34 for which
35 (t/(START_TIME_UNITs+1) − REV_SCH_START_TIME) mod

36 32 = 0,
38 REV_SCH-
39 _ NUM_BITS_IDX - Reverse Supplemental Channel number of bits per frame
40 index granted by the base station.
3-527
3GPP2 C.S0005-A v6.0
1 If USE_FLEX_NUM_BITS is equal to '0' or if

2 USE_FLEX_NUM_BITS is equal to '1' and
3 RSCH_NBIT_TABLE_ID[REV_SCH_ID] is equal to ‘0000’, then
4 the base station shall set this field according to Table
5 3.7.3.3.2.37-2 to indicate the Reverse Supplemental Channel
6 number of information bits per frame and the number of CRC
7 bits per frame, that the mobile station may transmit on the
8 reverse Supplemental Channel identified by REV_SCH_ID.
9 If USE_FLEX_NUM_BITS is equal to '1' and

10 RSCH_NBIT_TABLE_ID[REV_SCH_ID] is not equal to ‘0000’,
11 then the base station shall set the REV_SCH_NUM_BITS_IDX
12 this field to indicate the Reverse Supplemental Channel
13 number of information bits per frame that the mobile station
14 may transmit on the Reverse Supplemental Channel identified
15 by REV_SCH_ID to be
16 NUM_BITS[RSCH_NBIT_TABLE_ID[REV_SCH_ID]]
17 [REV_SCH_NUM_BITS_IDX] and the Reverse Supplemental
18 Channel number of CRC bits per frame that the mobile station
21 CRC_LEN_IDX[RSCH_NBIT_TABLE_ID[REV_SCH_ID]]
22 [REV_SCH_NUM_BITS_IDX].
23 The REV_SCH_NUM_BITS_IDX field also specifies the number
24 of CRC bits per frame for the Reverse Supplemental Channel
25 identified by REV_SCH_ID. The number of CRC bits per frame
26 is specified by
27 CRC_LEN_IDX[RSCH_NBIT_TABLE_ID[REV_SCH_ID]][REV_SC
28 H_NUM_BITS_IDX] and Table 3.7.5.20-4.
32 relative to that of 20 ms frames at a 9600 bps or 14400 bps
33 rate on the Forward Fundamental Channel or the Forward
34 Dedicated Control Channel that the Forward Power Control
35 Subchannel is punctured on. The base station shall set the
36 value in units of 0.25 dB.
37 USE_PC_TIME - Use power control action time indicator.
38 This field indicates whether an explicit time
39 [PC_ACTION_TIME] at which a new value for power control
40 sub-channel to traffic ratio (FPC_SUBCHAN_GAIN] takes effect
41 is specified in the message.
45 PC_ACTION_TIME - Power Control Subchannel gain action time.
3-528
3GPP2 C.S0005-A v6.0
1 If the USE_PC_TIME field is set to ‘1’, the base station shall

2 set this field to the System Time, in units of 80 ms (modulo
3 64), at which FPC_SUBCHAN_GAIN specified in this message
4 is to take effect. If the USE_PC_TIME field is set to ‘0’ the
8 3.7.3.3.2.36-1.
CH_IND Physical Resource(s) Allocated

(Binary)
000 Reserved.
001 Reserved
011 Reserved
100 Reserved
101 For Radio Configuration greater than 2,
Fundamental Channel and Continuous
Reverse Pilot Channel;
For Radio Configuration 1 or 2,
Fundamental Channel only.
110 Dedicated Control Channel and
Continuous Reverse Pilot Channel
111 Fundamental Channel, Dedicated
Control Channel and Continuous
Reverse Pilot Channel
10
11 ACTIVE_SET_REC_LEN - Active Set record length.

13 the ACTIVE_SET_REC_FIELDS included in this message.
14 ACTIVE_SET-
15 _REC_FIELDS - Active Set record fields.
16 The Active Set record fields are determined by the value of
17 CH_IND, as described below.
18 REV_FCH-
21 is allowed to perform the reverse eighth gating mode after
22 handoff; otherwise, the base station shall set this field to ‘0’.
3-529
3GPP2 C.S0005-A v6.0
1 REV_PWR-
9 REV_PWR-
21 D_SIG_ENCRYPT_MODE - Dedicated channel signaling General encryption mode indicator.
22 If ENCRYPT_MODE is included and is set to ‘11’, the base station
23 shall include this field and shall set it to the dedicated channel
24 signaling message encryption mode, as shown in Table 3.7.4.5-1;
27 If ENCRYPT_MODE is included and is set to ‘10’ or ‘11’, the base
28 station shall include this field. If this field is included, the base
29 station shall set this field to ‘0’ to indicate that the stored
30 encryption key to be used by the mobile station. Otherwise, the
31 base station shall set this field to ‘1’ to indicate that the new
32 encryption key to be used by the mobile station.
34 If ENCRYPT_MODE is included and is set to ‘10’ or
35 ‘11’USE_NEW_KEY is included and is set to ‘0’, the base
37 include this field and set it to the encryption key size, as
38 shown in Table 3.7.4.5-2; otherwise, the base station shall
39 omit this field.this field as described below.
40 The base station shall set this field to the encryption key size, as
3-530
3GPP2 C.S0005-A v6.0

5 station.
6 3XFL_1XRL_INCL - 3X Forward Link and 1X Reverse Link indicator.
7 The base station shall set this field to ‘1’ if the base station is
8 assigning 3X traffic channel on the Forward Link and 1X
9 traffic channel on the Reverse Link; otherwise, the base
11 1XRL_FREQ_OFFSET - 1X Reverse Link frequency offset.
12 If 3XFL_1XRL_INCL is set to ‘0’, the base station shall omit
14 follows:
16 Table 3.7.2.3.2.21-5 corresponding to the frequency offset of
17 the 1X reverse link.
3-531
3GPP2 C.S0005-A v6.0

2 indicator.
3 If either the SCR_INCLUDED field is included and is set to ‘1’

4 or the NNSCR_INCLUDED field is included and is set to ‘1’,
5 the base station shall include this field; otherwise, the base
6 station shall omit this field. If included, the base station shall
7 set this field as follows:
8 The base station shall set this field to ‘1’ if the SYNC_ID field
9 is included in this message; otherwise, the base station shall



24 by this message.
25 CC_INFO_INCL - Call Control information included indicator.
26 If the SCR_INCLUDED field is not included or is included but


3-532
3GPP2 C.S0005-A v6.0
4 length record (CON_REF, RESPONSE_IND, TAG, BYPASS_ALERT_ANSWER as per the
5 following requirements).

21 BYPASS_ALERT-


30

3-533
3GPP2 C.S0005-A v6.0
4 NUM_FOR_SCH - Number of Forward Supplemental Channel records.
8 Forward Supplemental Channel records need to be updated.
9 If NUM_FOR_SCH is included and not equal to ‘00000’, the base station shall include
10 NUM_FOR_SCH occurrence of the following three fields:
16 in the Supplemental Channel Code list.
17 FOR_SCH-
18 _NUM_BITS_IDX - Forward Supplemental Channel number of information bits
19 index.
22 FSCH_NBIT_TABLE_ID for FOR_SCH_ID is equal to ‘0000’,
23 then the base station shall set this field according to Table
24 3.7.3.3.2.37-4 to indicate the number of information bits per
25 frame and the length of the CRC field for the Forward
26 Supplemental Channel identified by FOR_SCH_ID
27 corresponding to SCCL_INDEX.
28 If USE_FLEX_NUM_BITSs is equal to '1' and

29 FSCH_NBIT_TABLE_ID[FOR_SCH_ID] is not equal to ‘0000’,
30 then the base station shall set the FOR_SCH_NUM_BITS_IDX
31 this field to indicate that the number of information bits per
32 frame for the Forward Supplemental channel identified by
33 FOR_SCH_ID to be
34 NUM_BITS[FSCH_NBIT_TABLE_ID[FOR_SCH_ID]][FOR_SCH_N
35 UM_BITS_IDX] and the number of CRC bits per frame for the
36 Forward Supplemental channel identified by FOR_SCH_ID to
37 be
38 CRC_LEN_IDX[FSCH_NBIT_TABLE_ID[FOR_SCH_ID]][FOR_SC
39 H_NUM_BITS_IDX].
3-534
3GPP2 C.S0005-A v6.0
1 The FOR_SCH_NUM_BITS_IDX field also specifies the number

2 of CRC bits per frame for the Forward Supplemental Channel
3 identified by FOR_SCH_ID. The number of CRC bits per frame
4 is specified by CRC_LEN_IDX
5 [FSCH_NBIT_TABLE_ID[FOR_SCH_ID]][FOR_SCH_NUM_BITS_
6 IDX] and Table 3.7.5.20-4.
7 NUM_REV_SCH - Number of Reverse Supplemental Channel records.
11 Reverse Supplemental Channels need to be updated.
12 If NUM_REV_SCH is included and not equal to ‘00000’, the base station shall include
13 NUM_REV_SCH occurrence of the following three fields:
14 REV_SCH_ID - Reverse Supplemental Channel identifier.
17 REV_WALSH_ID - Reverse Supplemental Channel Walsh cover Identifier.
18 The base station shall set this field according to Table
19 3.7.3.3.2.37-1 to indicate the Walsh cover ID that the mobile
20 station is to use when transmitting at the rate specified by
21 REV_SCH_NUM_BITS_IDX on the Reverse Supplemental
22 Channel specified by REV_SCH_ID. If only one reverse
23 supplemental channel is assigned, the base station should set
24 this field to the default value for the REV_WALSH_ID as
26 REV_SCH-
27 _NUM_BITS_IDX - Reverse Supplemental Channel number of bits per frame
28 index.
34 number of information bits per frame and the CRC bits per
35 frame, corresponding to REV_WALSH_ID field.

40 number of information bits per frame, corresponding to
41 REV_WALSH_ID field to be
44 Channel number of CRC bits per frame corresponding to
3-535
3GPP2 C.S0005-A v6.0

8 SRCH_OFFSET_INCL - Target pilot channel search window offset included.
9 If the SRCH_OFFSET field is included in the following records,
12 The base station shall include one occurrence of the following record for each of the
13 NUM_PILOTS pilots included in the message:
17 SRCH_OFFSET - Target pilot channel search window offset.
21 mobile station for this target pilot. Otherwise, the base
35 omit this field.
41 omit this field.
3-536
3GPP2 C.S0005-A v6.0

5 omit this field.

14 CODE_CHAN_FCH - Code channel on the Fundamental Channel.
16 used, the base station shall set this field to the code channel
17 index (see 2.1.3.1.9 and 3.1.3.1.13 of [2]) that the mobile
18 station is to use on the Fundamental Channel of the Forward
19 Traffic Channel. If a Radio Configuration associated with
20 Spreading Rate 3 is used, the base station shall set this field
21 to the code channel index that the mobile station is to use for
22 the Fundamental Channel on the center SR3 frequency.
29 QOF_MASK_ID_FCH - Quasi-orthogonal function index on the Fundamental
30 Channel.
32 used, the base station shall set this field to the index of the
33 Quasi-orthogonal function (see Table 3.1.3.1.12-2 of [2]). If a
34 Radio Configuration associated with Spreading Rate 3 is used,
35 the base station shall set this field to the index of the Quasi-
36 orthogonal function on the center SR3 frequency.
37 NUM_SCH - Number of Supplemental Channel records.
41 Supplemental Channel records need to be updated.
42 If NUM_SCH is included and not equal to ‘00000’, the base station shall include NUM_SCH
43 occurrence of the following five fields:
3-537
3GPP2 C.S0005-A v6.0
1 The base station shall set this field the identifier of the
2 Forward Supplemental Channel pertaining to this record.
6 PILOT_INCL - The corresponding pilot included in Supplemental Channel
7 Active Set indicator.
8 The base station shall set this field to ‘1’ if the corresponding
9 pilot is included in the Active Set of Supplemental Channel;
11 CODE_CHAN_SCH - Code channel on the Supplemental Channel.
12 If PILOT_INCL is included and set to ‘1’, the base station shall
13 set this field as follows; otherwise, the base station shall omit
14 this field.
17 to use on the Supplemental Channel of the Forward Traffic
18 Channel indexed by SCCL_INDEX.
19 QOF_MASK_ID_SCH - Quasi-orthogonal function index on the Supplemental
20 Channel.
21 If PILOT_INCL is included and set to ‘1’, the base station shall
22 set this field as follows; otherwise, the base station shall omit
23 this field.
30 The base station shall include NUM_PILOTS occurrences of the following record if
34 indicator.
39 QOF_MASK_ID-
43 follows:
3-538
3GPP2 C.S0005-A v6.0
4 SR3 frequency.
5 CODE_CHAN-
9 follows:
18 indicator.
23 QOF_MASK_ID-
27 follows:
31 SR3 frequency.
32 CODE_CHAN-
36 follows:
44 3X_SCH_INFO_INCL – 3X SCH information included indicator.
3-539
3GPP2 C.S0005-A v6.0
1 If the 3X Supplemental Channel information is included, the

4 The base station shall include NUM_SCH occurrences of the following seven fields record if
5 3X_SCH_INFO_INCL is included and set to ‘1’.
9 3X_SCH_LOW_INCL – SCH code channel on the lowest SR3 frequency included
10 indicator.
11 If the SCH on the lowest SR3 frequencies has a different code
12 channel than the SCH on the center SR3 frequency, the base
15 QOF_MASK_ID-
16 _SCH_LOW – QOF index for the SCH on the lowest SR3 frequency.
17 If 3X_SCH_LOW_INCL is set to ‘0’, the base station shall omit
19 follows:
22 corresponding to the QOF index for the SCH on the lowest
23 SR3 frequency.
24 CODE_CHAN-
25 _SCH_LOW - Code channel for the SCH on the lowest SR3 frequency.
28 follows:
31 to use on the SCH on the lowest SR3 frequency. If Radio
36 3X_SCH_HIGH_INCL – SCH code channel on the highest SR3 frequency included
37 indicator.
38 If the SCH on the highest SR3 frequencies has a different code
42 QOF_MASK_ID-
43 _SCH_HIGH – QOF index for the SCH on the highest SR3 frequency.
3-540
3GPP2 C.S0005-A v6.0
1 If 3X_SCH_HIGH_INCL is set to ‘0’, the base station shall omit

3 follows:
6 corresponding to the QOF index for the SCH on the highest
7 SR3 frequency.
8 CODE_CHAN-
9 _SCH_HIGH – Code channel for the SCH on the highest SR3 frequency.
12 follows:
15 to use on the SCH on the highest SR3 frequency. If Radio
20
21 If the CH_IND field is set to ‘010’ or ‘110’, the base station shall include the following fields:
30 The base station shall set this field to identifier of the Forward
35 FOR_SCH-
37 index.
3-541
3GPP2 C.S0005-A v6.0


14 FOR_SCH_ID to be
18 be
20 H_NUM_BITS_IDX].
24 is specified by
3-542
3GPP2 C.S0005-A v6.0

9 REV_SCH-
11 index.
18 bits per frame, corresponding to REV_WALSH_ID field.

22 field to indicate the Reverse Supplemental Channel number of
23 information bits per frame, corresponding to REV_WALSH_ID
24 field to be NUM_BITS[RSCH_NBIT_TABLE_ID[REV_SCH_ID]]
25 [REV_SCH_NUM_BITS_IDX]and the Reverse Supplemental
26 Channel number of CRC bits per frame, corresponding to
30

3-543
3GPP2 C.S0005-A v6.0

19 omit this field.
25 omit this field.
31 omit this field.
32

3-544
3GPP2 C.S0005-A v6.0
1 CODE_CHAN_DCCH - Code channel on the Dedicated Control Channel.

4 index (see 2.1.3.1.9 and 3.1.3.1.13 of [2] that the mobile
5 station is to use on the Dedicated Control Channel of the
6 Forward Traffic Channel. If a Radio Configuration associated
7 with Spreading Rate 3, the base station shall set this field to
8 the code channel index (see 2.1.3.1.9 and 3.1.3.1.13 of [2])
9 that the mobile station is to use for the Dedicated Control
10 Channel on the center SR3 frequency.
17 QOF_MASK_ID_DCCH - Quasi-orthogonal function index on the Dedicated Control
18 Channel.
31 occurrence of the following five fields:
32 FOR_SCH_ID - Forward Supplemental Channel identifier
3-545
3GPP2 C.S0005-A v6.0

7 Channel.
20 indicator.
25 QOF_MASK_ID-
29 as follows:
33 SR3 frequency.
34 CODE_CHAN-
38 as follows:
3-546
3GPP2 C.S0005-A v6.0

2 indicator.
7 QOF_MASK_ID-
11 as follows:
15 SR3 frequency.
16 CODE_CHAN-
20 as follows:
40 indicator.
45 QOF_MASK_ID-
3-547
3GPP2 C.S0005-A v6.0
4 follows:
8 SR3 frequency.
9 CODE_CHAN-
13 follows:
22 indicator.
27 QOF_MASK_ID-
31 follows:
35 SR3 frequency.
36 CODE_CHAN-
40 follows:
3-548
3GPP2 C.S0005-A v6.0
7 to 255 inclusive.
23 FOR_SCH-
25 index.
39 FOR_SCH_ID to be
43 be
3-549
3GPP2 C.S0005-A v6.0
1 H_NUM_BITS_IDX].
5 is specified by
27 REV_SCH-
29 index.

41 information bits per frame, corresponding to REV_WALSH_ID
42 field to be NUM_BITS[RSCH_NBIT_TABLE_ID[REV_SCH_ID]]
44 Channel number of information bits per frame, corresponding
3-550
3GPP2 C.S0005-A v6.0
1 to REV_WALSH_ID field to be to be

36 omit this field.
42 omit this field.
3-551
3GPP2 C.S0005-A v6.0

5 omit this field.

14 CODE_CHAN_FCH - Code Channel on the Fundamental Channel.
18 station is to use on the Fundamental Channel of the Forward
19 Traffic Channel. If a Radio Configuration associated with
20 Spreading Rate 3 is used, the base station shall set this field
21 to the code channel index that the mobile station is to use for
22 the Fundamental Channel on the center SR3 frequency.
29 QOF_MASK_ID_FCH - Quasi-orthogonal function index on the Fundamental
30 Channel.
37 CODE_CHAN_DCCH - Code channel on the DCCH.
41 station is to use on the Dedicated Control Channel of the
42 Forward Traffic Channel. If a Radio Configuration associated
43 with Spreading Rate 3 is used, the base station shall set this
44 field to the code channel index that the mobile station is to
45 use for the Dedicated Control Channel on the center SR3
46 frequency.
3-552
3GPP2 C.S0005-A v6.0

7 QOF_MASK_ID_DCCH - Quasi-orthogonal function index on the DCCH.
18 occurrence of the following fields:
24 in the Supplemental Channel Code List Table.
30 CODE_CHAN_SCH - Code Channel on the Supplemental Channel.
38 Channel.
3-553
3GPP2 C.S0005-A v6.0

9 3X_FCH_INFO_INCL or 3X_FCH_INFO_INCL is set to ‘1’. The base station shall use the
10 same order for the following fields as is used for the PILOT_PN fields listed in this message.
12 indicator.
13 If 3X_FCH_INFO_INCL is set to ‘0’, the base station shall set
15 as follows:
20 QOF_MASK_ID-
22 If 3X_FCH_LOW_INCL is included and set to ‘1’, the base
23 station shall set this field as follows; otherwise, the base
24 station shall omit this field:
28 SR3 frequency.
29 CODE_CHAN-
31 If 3X_FCH_LOW_INCL is included and set to ‘1’, the base
42 indicator.
43 If 3X_FCH_INFO_INCL is set to ‘0’, the base station shall omit
45 follows:
3-554
3GPP2 C.S0005-A v6.0

5 QOF_MASK_ID-
7 If 3X_FCH_HIGH_INCL is included and set to ‘1’, the base
13 SR3 frequency.
14 CODE_CHAN-
16 If 3X_FCH_HIGH_INCL is included and set to ‘1’, the base
27 indicator.
28 If 3X_DCCH_INFO_INCL is set to ‘0’, the base station shall
30 as follows:
35 QOF_MASK_ID-
37 If 3X_DCCH_LOW_INCL is included and set to ‘1’, the base
43 SR3 frequency.
3-555
3GPP2 C.S0005-A v6.0
1 CODE_CHAN-
3 If 3X_DCCH_LOW_INCL is included and set to ‘1’, the base
14 indicator.
15 If 3X_DCCH_INFO_INCL is set to ‘0’, the base station shall
17 as follows:
22 QOF_MASK_ID-
24 If 3X_DCCH_HIGH_INCL is included and set to ‘1’, the base
30 SR3 frequency.
31 CODE_CHAN-
33 If 3X_DCCH_HIGH_INCL is included and set to ‘1’, the base
3-556
3GPP2 C.S0005-A v6.0

10 indicator.
15 QOF_MASK_ID-
19 follows:
23 SR3 frequency.
24 CODE_CHAN-
28 follows:
37 indicator.
42 QOF_MASK_ID-
3-557
3GPP2 C.S0005-A v6.0

3 follows:
7 SR3 frequency.
8 CODE_CHAN-
12 follows:
3-558
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.37 Extended Supplemental Channel Assignment Message
2 MSG_TAG: ESCAM
Field Length (bits)
START_TIME_UNIT 3
REV_SCH_DTX_DURATION 4
USE_T_ADD_ABORT 1
USE_SCRM_SEQ_NUM 1
SCRM_SEQ_NUM 0 or 4
ADD_INFO_INCL 1
FPC_PRI_CHAN 0 or 1
REV_CFG_INCLUDED 1
The base station shall include the following field if
REV_CFG_INCLUDED is set to ‘1’
NUM_REV_CFG_RECS 5
The base station shall the include (NUM_REV_CFG_RECS
+1) occurrences of the following three fields if
REV_CFG_INCLUDED is set to ‘1’
REV_SCH_ID 1
REV_WALSH_ID 1
NUM_REV_SCH 2
The base station shall include NUM_REV_SCH occurrences
of the following fields
REV_SCH_ID 1
REV_SCH_DURATION 4
REV_SCH_START_TIME_INCL 1
REV_SCH_START_TIME 0 or 5
3-559
3GPP2 C.S0005-A v6.0
Field Length (bits)
FOR_CFG_INCLUDED 1
FOR_SCH_FER_REP 0 or 1
The base station shall include the following field if
FOR_CFG_INCLUDED is set to ‘1’
NUM_FOR_CFG_RECS 5
The base station shall the include (NUM_FOR_CFG_RECS
+1) occurrences of the following fields if
FOR_CFG_INCLUDED is set to ‘1’
FOR_SCH_ID 1
SCCL_INDEX 4
NUM_SUP_SHO 3
NUM_SUP_SHO+1 occurrences of the following fields
PILOT_PN 9
ACTIVE_PILOT_REC_TYPE 0 or 3
RECORD_LEN 0 or 3
CODE_CHAN_SCH 11
QOF_MASK_ID_SCH 2
NUM_FOR_SCH 2
The base station shall include NUM_FOR_SCH occurrences
of the following fields
FOR_SCH_ID 1
FOR_SCH_DURATION 4
FOR_SCH_START_TIME_INCL 1
FOR_SCH_START_TIME 0 or 5
SCCL_INDEX 4
3-560
3GPP2 C.S0005-A v6.0
Field Length (bits)
FPC_INCL 1
FPC_MODE_SCH 0 or 3
FPC_SCH_INIT_SETPT_OP 0 or 1
FPC_SEC_CHAN 0 or 1
NUM_SUP 0 or 2
Include NUM_SUP occurrences of the following fields:
SCH_ID 1
FPC_SCH_FER 5
FPC_SCH_INIT_SETPT 8
FPC_SCH_MIN_SETPT 8
FPC_SCH_MAX_SETPT 8
FPC_THRESH_SCH_INCL 0 or 1
FPC_SETPT_THRESH_SCH 0 or 8
RPC_INCL 1
RPC_NUM_SUP 0 or 1
Include RPC_NUM_SUP +1 occurrences of the following two
fields record:
SCH_ID 1
RLGAIN_SCH_PILOT 6

3
3-561
3GPP2 C.S0005-A v6.0
Field Length (bits)
3X_SCH_INFO_INCL 1
NUM_3X_CFG 0 or 2
NUM_3X_CFG occurrences of the following record if
FOR_SCH_ID 1
NUM_3X_REC 5
(NUM_3X_REC + 1) occurrences of the following record:
SCCL_INDEX 4
(NUM_SUP_SHO + 1) occurrences of the following record for
each corresponding SCCL_INDEX field:
3X_SCH_LOW_INCL 1
3X_SCH_HIGH_INCL 1
3-562
3GPP2 C.S0005-A v6.0
2 START_TIME_UNIT - Unit for start time.
3 The base station shall set this field to indicate the units of
4 start time included in Extended Supplemental Channel
5 Assignment Message, Forward Supplemental Channel
6 Assignment Mini Message, Reverse Supplemental Channel
7 Assignment Mini Message, and Universal Handoff Direction
8 Message. The base station shall set this field to one less than
9 the number of 20 ms frames that determines the
10 START_TIME_UNIT.
11 REV_SCH_DTX-
12 _DURATION - Discontinuous Transmission on Reverse Supplemental

13 Channel.
14 The base station shall set this field to the maximum duration
15 of time in units of 20 ms that the mobile station is allowed to
16 stop transmission on a Reverse Supplemental Channel within
17 the reverse assignment duration. The base station shall set
18 this field to ‘0000’ if the mobile station is to stop using a
19 Reverse Supplemental Channel once it has stopped
20 transmitting on that Reverse Supplemental Channel. The base
21 shall set this field to ‘1111’ if the mobile station is allowed to
22 resume transmission on a Reverse Supplemental Channel at
23 any time within the reverse assignment duration.
26 mobile station is to utilize the T_ADD Reverse Supplemental
27 Channel abort feature for this reverse assignment; otherwise,
29 USE_SCRM-
30 _SEQ_NUM - Use Supplemental Channel Request Message sequence


33 SCRM_SEQ_NUM field is included in this message; otherwise,
35 SCRM_SEQ_NUM - Supplemental Channel Request Message sequence number.
36 If USE_SCRM_SEQ_NUM is set to ‘1’, the base station shall set

37 this field to the sequence number corresponding to the
38 SCRM_SEQ_NUM field in a Supplemental Channel Request
39 Message to which the mobile station is to match this message;
41 ADD_INFO_INCL - Additional information included indicator.

42 If the message is to contain the FPC_PRI_CHAN field, the
3-563
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to ‘0’ if any of the following
2 conditions holds:
3 - The message does not contain any Supplemental Channel
4 assignment.
5 - The mobile station is currently in the Control Hold Active
6 mode.
7 FPC_PRI_CHAN - Power Control Subchannel Indicator.
8 If the ADD_INFO_INCL field is set to ’0’, the base station shall
10 as follows:
20 Channel.
21 REV_CFG_INCLUDED - Reverse Supplemental Channel configuration included.
23 contains a Reverse Supplemental Channel configuration.
25 NUM_REV_CFG_RECS - Number of the Reverse Supplemental Channel configuration
26 Records.
27 If REV_CFG_INCLUDED is set to ‘1’, Tthe base station shall
28 set this field to one less than the number of reverse
29 supplemental channel configuration records consisting of the
30 following three fields that are included in this message;
32 The base station shall include NUM_REV_CFG_RECS+1 occurrences of the following three
33 fields only if the REV_CFG_INCLUDED field is set to ‘1’.
40 station is to use when transmitting number of bits per frame
41 specified by REV_NUM_BITS_IDX on the Reverse
42 Supplemental Channel specified by REV_SCH_ID. If only one
43 reverse supplemental channel is assigned, the base station
44 should set this field to the default value for the
45 REV_WALSH_ID as specified in 2.6.4.2.
3-564
3GPP2 C.S0005-A v6.0
1 Table 3.7.3.3.2.37-1. REV_WALSH_ID Field
Walsh Cover
REV_WALSH_ID
(binary) SCH_ID = '0' SCH_ID = '1'
0 +- ++--
1 ++-- ++----++
2
3 REV_SCH-
5 index.

25
26 Table 3.7.3.3.2.37-2. R-SCH Number of Information Bits per Frame
REV_SCH_NUM_ Number of information bits Number of

BITS_IDX per frame CRC bits
RC 3, 5 RC 4, 6 per frame
(binary)
0000 172 267 12
0001 360 552 16
0010 744 1,128 16
0011 1,512 2,280 16
0100 3,048 4,584 16
3-565
3GPP2 C.S0005-A v6.0
Number of information bits

per frame
0101 6,120 5,178 16
0110 12,264 9,192 16
0111 Reserved 10,356 16
1000 Reserved 20,712 16
RESERVED All other values are reserved
1
2 NUM_REV_SCH - Number of Reverse Supplemental Channels assigned.

3 The base station shall set this field to the number of Reverse
4 Supplemental Channel assigned. The base station shall set
5 this field to ‘00’ if the assignment of Supplemental Channel is
6 not included.
7 The base station shall include NUM_REV_SCH occurrences of the following five fields
8 (REV_SCH_ID, REV_SCH_DURATION, REV_SCH_START_TIME_INCL,
9 REV_SCH_START_TIME, and REV_SCH_NUM_BITS_IDX).

13 REV_SCH_DURATION - Duration of Reverse Supplemental Channel assignment
16 Supplemental Channel specified by REV_SCH_ID at the
17 explicit start time specified by REV_SCH_START_TIME or at
18 the implicit start time if REV_SCH_START_TIME_INCL is set
19 to ‘0’. The base station shall set this field to '1111' to indicate
20 that the mobile station may transmit on the Reverse
21 Supplemental Channel specified by REV_SCH_ID, starting at
22 the explicit start time specified by REV_SCH_START_TIME in
23 this message, until the start time specified by a subsequent
24 Reverse Supplemental Channel assignment corresponding to
25 the same Supplemental Channel (see 2.6.6.2.5.1.1). The base
26 station shall set this field to the duration according to Table
27 3.7.3.3.2.37-3, starting at the start time specified by
28 REV_SCH_START_TIME, during which the mobile station may
29 transmit on the Reverse Supplemental Channel specified by
30 REV_SCH_ID.
31 Table 3.7.3.3.2.37-3. FOR_SCH_DURATION and

32 REV_SCH_DURATION Fields
FOR_SCH_DURATION Duration in 20 ms
REV_SCH_DURITION
(binary)
3-566
3GPP2 C.S0005-A v6.0
0001 1
0010 2
0011 3
0100 4
0101 5
0110 6
0111 7
1000 8
1001 16
1010 32
1011 64
1100 96
1101 128
1110 256
1111 Infinity
1 REV_SCH-
3 If REV_SCH_DURATION is not equal to ‘0000’, the base

4 station shall set this field to ‘1’. If REV_SCH_DURATION is
7 REV_SCH_START_TIME is included in this message;
9 REV_SCH-
10 _START_TIME - Start time for Reverse Supplemental Channel assignment.
11 If REV_SCH_START_TIME_INCL is set to ‘0’, the base station

14 START_TIME_UNIT, (modulo 32) at which the mobile station
15 may start transmitting on the Reverse Supplemental Channel
17 transmitting on the Reverse Supplemental Channel is the time
18 for which
19 (t/(START_TIME_UNITs+1) − REV_SCH_START_TIME) mod
20 32 = 0,
22 REV_SCH-
3-567
3GPP2 C.S0005-A v6.0

2 index.

22
23 FOR_CFG_INCLUDED - Forward Supplemental Channel configuration included.

25 contains a Forward Supplemental Channel configuration.
27 FOR_SCH_FER_REP - Forward Supplemental Channel FER report indicator.
28 If FOR_CFG_INCLUDED is set to ‘0’, the base station shall
29 omit this field, otherwise, the base station shall include this
32 is to report the Supplemental Channel frame counts (see
33 2.6.4.1.1); otherwise, the base station shall set this field to ‘0’.
34 NUM_FOR_CFG_RECS - Number of the Forward Supplemental Channel configuration
35 Records.
36 If REVFOR_CFG_INCLUDED is set to ‘1’, Tthe base station
37 shall set this field to one less than the number of forward
38 supplemental channel configuration records consisting of the
39 following three fields that are included in this message;
41 The base station shall include NUM_FOR_CFG_RECS+1 occurrences of the following fields
42 only if the FOR_CFG_INCLUDED field is set to ‘1’.
43 FOR_SCH_ID - Forward Supplemental Channel identifier
3-568
3GPP2 C.S0005-A v6.0

4 FOR_SCH-
6 index.
15
16 Table 3.7.3.3.2.37-4. F-SCH Number of

17 Information Bits per Frame
FOR_SCH_NUM_ Number of information bits Number of

BITS_IDX per frame CRC bits
RC 3, 4, 6, 7 RC 5, 8, 9 per frame
(binary)
0000 172 267 12
0001 360 552 16
0010 744 1,128 16
0011 1,512 2,280 16
0100 3,048 4,584 16
0101 6,120 5,178 16
0110 12,264 9,192 16
0111 Reserved 10,356 16
1000 Reserved 20,712 16
RESERVED All other values are reserved
23 FOR_SCH_ID to be
25 UM_BITS_IDX] that the number of CRC bits per frame for the
27 be
3-569
3GPP2 C.S0005-A v6.0
2 H_NUM_BITS_IDX].
6 is specified by
9
10 NUM_SUP_SHO - Number of Forward Supplemental Channels in Soft Handoff

11 The base station shall set this field to the size of the Forward
12 Supplemental Channel Active Set minus one.
13 The base station shall include NUM_SUP_SHO+1 occurrences of the following fields for each
14 Forward Supplemental channel corresponding to the FOR_SCH_ID and the SCCL_INDEX
15 whose frames may be soft-combined by the mobile station:
16

26 PILOT_REC_TYPE - Pilot record type
32 omit this field.
38 omit this field.
42 ACTIVE_PILOT_REC_TYPE of this pilot record as described in
43 3.7.6.1.
3-570
3GPP2 C.S0005-A v6.0

2 omit this field.
9 Channel.
11 orthogonal function (see 3.1.3.1.13 of [2]).
12
13 NUM_FOR_SCH - Number of Forward Supplemental Channels assigned.

14 The base station shall set this field to the number of forward
15 Supplemental Channel assigned. The base station shall set
16 this field to ‘00’ if the assignment of Supplemental Channel is
17 not included.
18 The base station shall include NUM_FOR_SCH occurrences of the following five fields
19 (FOR_SCH_ID, FOR_SCH_DURATION, FOR_SCH_START_TIME_INCL,
20 FOR_SCH_START_TIME, and SCCL_INDEX).
21

28 specified by FOR_SCH_START_TIME, during which the mobile
32 Supplemental Channel starting at the explicit start time of the
33 message specified by FOR_SCH_START_TIME or at the
34 implicit start time if FOR_SCH_START_TIME_INCL is set to ‘0’.
37 Channel, starting at the start time of the message specified by
38 FOR_SCH_START_TIME, until the start time specified by a
40 corresponding to the same Supplemental Channel (see
41 2.6.6.2.5.1.1).
3-571
3GPP2 C.S0005-A v6.0
1 FOR_SCH-
3 If FOR_SCH_DURATION is not equal to ‘0000’, the base

4 station shall set this field to ‘1’. If FOR_SCH_DURATION is
7 FOR_SCH_START_TIME is included in this message;
9 FOR_SCH-
10 _START_TIME - Start time for Forward Supplemental Channel assignment.
11 If FOR_SCH_START_TIME_INCL is set to ‘0’, the base station
14 START_TIME_UNIT, (modulo 32) at which the mobile station is
15 to start processing the Forward Supplemental Channel
16 specified in this message. The start time for processing
17 Forward Supplemental Channels is the time for which
19 = 0,
27 or both.
28 FPC_INCL - Forward Link Power Control parameter included indicator.
29 If the forward power control related information is included in
32 FPC_MODE_SCH - Forward Power Control operational mode indicator used
33 during forward Supplemental Channel assignment interval.
34 If FPC_INCL is set to ‘1’, the base station shall set the value to
35 the forward power control operation mode (see [2]); otherwise,
37 FPC_SCH-
38 _INIT_SETPT_OP - Initial Supplemental Channel Outer Loop Eb/Nt setpoint
39 option.
3-572
3GPP2 C.S0005-A v6.0
2 FPC_SCH_INIT_SETPT contains the absolute value of the
3 initial F-SCH Eb/Nt setpoint. The base station shall set this
4 field to ‘1’ to indicate that FPC_SCH_INIT_SETPT contains the
5 offset value of the initial F-SCH Eb/Nt setpoint relative to the
6 current value used in the mobile station for the channel
7 carrying the Forward Power Control Subchannel.
8 FPC_SEC_CHAN - Master Supplemental channel index.
9 If FPC_INCL is set to ‘1’ and FPC_MODE_SCH is set to ‘001’,
10 ‘010’, ‘101’, or ‘110’, the base station shall set this field to the
11 master Supplemental Channel index; otherwise, the base
13 NUM_SUP - Number of Supplemental Channels.
15 otherwise, the base station shall set this field to the total
16 number of the Supplemental Channels.
17 The base station shall include NUM_SUP occurrences of the following record:
20 Channel index.
21 FPC_SCH_FER - Supplemental channel target Frame Error Rate.
23 Rate on the Supplemental Channel, as specified in Table
24 3.7.3.3.2.25-2.
25 FPC_SCH_INIT_SETPT - Initial Supplemental Channel Output Loop Eb/Nt setpoint
26 The base station shall set this field to initial Supplemental
27 Channel Outer Loop Eb/Nt setpoint (absolute value or offset
28 value as indicated by FPC_SCH_INIT_SETPT_OP) as follows:
29 • If FPC_SCH_INIT_SETPT_OP is set to '0', the unit is 0.125

30 dB;
31 • If FPC_SCH_INIT_SETPT_OP is set to '1', the unit is 0.125

32 dB and the offset is expressed as two's complement signed
33 number.
34 FPC_SCH_MIN_SETPT - Minimum Supplemental Channel outer loop Eb/Nt setpoint.
35 The base station shall set this field to minimum Supplemental
37 FPC_SCH_MAX_SETPT - Maximum Supplemental Channel outer loop Eb/Nt setpoint.
38 The base station shall set this field to maximum Supplemental
40 FPC_THRESH_SCH_INCL - SCH Setpoint Report Threshold Included Indicator.
3-573
3GPP2 C.S0005-A v6.0
1 If SCH setpoint report threshold is included in this message,

4 FPC_SETPT-
5 _THRESH_SCH - SCH Setpoint Report Threshold.
6 If FPC_THRESH_SCH_INCL is set to ‘1’, the base station shall
7 set this field the value to the value of SETPT_THRESH_SCH
8 the Supplemental Channel setpoint threshold (in units of
9 0.125 dB) above which the outer loop report message will be
10 sent by the mobile station; otherwise, the base station shall
11 omit this field.
12 RPC_INCL - Reverse Power Control parameter included indicator.
13 The base station shall set this field to ‘1’ if RPC_NUM_SUP is
14 included in this message; otherwise the base station shall set
16 RPC_NUM_SUP - Number of Supplemental Channels.
17 If RPC_INCL is set to ‘1’, the base station shall set this field to
18 the total number of the Supplemental Channels minus one;
20 The base station shall include RPC_NUM_SUP +1 occurrences of the following two fields
21 record:
24 Channel index.
25 RLGAIN_SCH_PILOT - Supplemental channel power offset adjustment relative to
26 Reverse Pilot Channel power for radio configurations greater
27 than 2.
29 be used by mobile stations setting the power of a
30 supplemental channel, expressed as a two’s complement value
31 in units of 0.125 dB.
36 If FOR_CFG_INCLUDED is set to ‘0’, the base station shall set
38 NUM_3X_CFG – Number of 3X Supplemental Channels to be configured
39 If 3X_SCH_INFO_INCL is set to ‘0’, the base station shall omit
41 follows:
42 The base station shall set this field to the number of 3X
43 Forward Supplemental Channels to be configured. The base
44 station shall set this field to ‘00’ if the configuration of
45 Supplemental Channel is not included.
3-574
3GPP2 C.S0005-A v6.0
1 The base station shall include NUM_3X_CFG occurrences of the following record if
6 NUM_3X_REC - Number of 3X records
7 The base station shall set this field to the number of instances
8 of the following record minus one included in this message.
9 The base station shall include NUM_3X_REC+1 occurrences of the following variable-length
10 record.
11

15 The base station shall include NUM_SUP_SHO+1 occurrences of the following fields for each
16 Forward Supplemental channel corresponding to the FOR_SCH_ID and the SCCL_INDEX
17 whose frames may be soft-combined by the mobile station:
19 indicator.
24 QOF_MASK_ID-
28 follows:
32 SR3 frequency.
33 CODE_CHAN-
37 follows:
3-575
3GPP2 C.S0005-A v6.0

2 indicator.
7 QOF_MASK_ID-
11 follows:
15 SR3 frequency.
16 CODE_CHAN-
20 follows:
3-576
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.38 Forward Supplemental Channel Assignment Mini Message
2 MSG_TAG: FSCAMM
Field Length (bits)
FOR_SCH_ID 1
FOR_SCH_DURATION 4
FOR_SCH_START_TIME 5
SCCL_INDEX 4
3-577
3GPP2 C.S0005-A v6.0
8 specified by FOR_SCH_START_TIME, during which the mobile
12 Supplemental Channel starting at the start time of the
13 message specified by FOR_SCH_START_TIME.
16 Channel, starting at the explicit start time of the message
17 specified by FOR_SCH_START_TIME, until the start time of a
19 corresponding to the same Forward Supplemental Channel
20 (see 2.6.6.2.5.1.1).
21 FOR_SCH-
22 _START_TIME - Start time for Forward Supplemental Channel assignment.
24 units of time specified by START_TIME_UNIT, (modulo 32) at
25 which the mobile station is to start processing the Forward
26 Supplemental Channel specified in this message. The start
27 time for processing Forward Supplemental Channels is the
28 time for which

30 = 0,
38 or both.
3-578
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.39 Reverse Supplemental Channel Assignment Mini Message
2 MSG_TAG: RSCAMM
Field Length (bits)
REV_SCH_ID 1
REV_SCH_DURATION 4
REV_SCH_START_TIME 5
3-579
3GPP2 C.S0005-A v6.0
5 REV_SCH_DURATION - Duration of Reverse Supplemental Channel assignment.
8 Supplemental Channel specified by REV_SCH_ID at the start
9 time specified by START_TIME. The base station shall set this
10 field to '1111' to indicate that the mobile station may transmit
11 on the Reverse Supplemental Channel specified by
12 REV_SCH_ID, starting at the start time specified by
13 REV_SCH_START_TIME in this message, until the start time
14 specified by a subsequent Reverse Supplemental Channel
15 assignment corresponding to the same Supplemental Channel
16 (see 2.6.6.2.5.1.1). The base station shall set this field to the
17 duration according to Table 3.7.3.3.2.37-3, starting at the
18 explicit start time specified by REV_SCH_START_TIME, during
19 which the mobile station may transmit on the Reverse
20 Supplemental Channel specified by REV_SCH_ID.
21 REV_SCH-
22 _START_TIME - Start time for Reverse Supplemental Channel Assignment Mini

23 Message.
25 units of time specified by START_TIME_UNIT, (modulo 32) at
26 which the mobile station may start transmitting on the
27 Reverse Supplemental Channel specified in this message. The
28 explicit start time for transmitting on the Reverse
29 Supplemental Channel is the time for which
30 (t/(START_TIME_UNIT+1) − REV_SCH_START_TIME) mod 32

31 = 0,
33 REV_SCH-
34 _NUM_BITS_IDX - Reverse Supplemental Channel number of information bits per

35 frame index.

42 bits per frame, that the mobile station may transmit on the
43 reverse Supplemental Channel identified by REV_SCH_ID.
3-580
3GPP2 C.S0005-A v6.0

4 information bits per frame that the mobile station may
5 transmit on the Reverse Supplemental Channel identified by
6 REV_SCH_ID to be
9 Channel number of CRC bits per frame that the mobile station
13 [REV_SCH_NUM_BITS_IDX.
14 The REV_SCH_NUM_BITS_IDX field also specifies the number
15 of CRC bits per frame for the Reverse Supplemental Channel
16 identified by REV_SCH_ID. The number of CRC bits per frame
17 is specified by
18 CRC_LEN_IDX[RSCH_NBIT_TABLE_ID[REV_SCH_ID]][REV_SC
3-581
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.40 Mobile Assisted Burst Operation Parameters Message
2 MSG_TAG: MABOPM
Field Length (bits)
ORDER_FLAG 1
If ORDER_FLAG is set to ‘1’, the base station shall include

following record:
PS_MIN_DELTA 3
ORDER_INTERVAL 3
PERIODIC_FLAG 1
If PERIODIC_FLAG is set to ‘1’, the base station shall include

following record:
NUM_PILOTS 3
PERIODIC_INTERVAL 6
THRESHOLD_FLAG 1
If THRESHOLD_FLAG is set to ‘1’, the base station shall

include following record:
PS_FLOOR_HIGH 6
PS_FLOOR_LOW 6
PS_CEILING_HIGH 6
PS_CEILING_LOW 6
THRESHOLD_INTERVAL 6
3-582
3GPP2 C.S0005-A v6.0
2 ORDER_FLAG - Order change reporting flag.
4 mobile station is to send a Pilot Strength Measurement Mini
5 Message to the base station whenever a received pilot strength
6 measurement changes its relative order with respect to all
7 other reported pilot strength measurements during
8 supplemental channel burst operations; otherwise, the base
10 If ORDER_FLAG is set to ‘1’, the base stations shall include the following two-field record:
11 PS_MIN_DELTA - Minimum power strength delta.
13 minimum pilot strength measurement difference between two
14 pilots (in units of 0.5 dB) that must be measured in order for
15 the mobile station to send a Pilot Strength Measurement Mini
16 Messages when the rank order mode is enabled. A difference
17 in pilot strength of at least (PS_MIN_DELTA + 1), in units of
18 0.5 dB, must be measured for ORDER_INTERVAL successive
19 20 ms intervals before a rank order based Pilot Strength
20 Measurement Mini Message is generated.
21 ORDER_INTERVAL - Order interval.
22 The base station shall set this field to the minimum interval (in
23 20 ms units) during which the indicated pilot strength
24 measurement difference greater than or equal to
25 (PS_MIN_DELTA + 1), in units of 0.5 dB, must be measured by
26 the mobile station in order for the mobile station to send a
27 Pilot Strength Measurement Mini Messages when the rank order
28 mode is enabled.
29 PERIODIC_FLAG - Periodic report flag.
31 mobile station is to send Pilot Strength Measurement Mini
32 Messages periodically during supplemental channel burst
33 operations; otherwise the base station shall set this field to ‘0’.
34 If PERIODIC_FLAG is set to ‘1’, the base station shall include the following two-field record:
35 NUM_PILOTS - Number of pilots.
36 The base station shall set this field to the number of pilots for
37 which the mobile station is to send Pilot Strength Measurement
38 Mini Messages when the periodic mode is enabled.
39 PERIODIC_INTERVAL - Periodic interval.
40 The base station shall set this field to the interval (in 20 ms
41 units) between Pilot Strength Measurement Mini Messages when
42 the periodic mode is enabled.
43 THRESHOLD_FLAG - Threshold reporting flag.
3-583
3GPP2 C.S0005-A v6.0
2 mobile station is to send Pilot Strength Measurement Mini
3 Messages whenever a measured pilot crosses below a lower
4 bound or exceeds an upper bound during Supplemental
5 channel burst operations; otherwise the base station shall set
7 If THRESHOLD_FLAG is set to ‘1’, the base station shall include the following five-field
8 record:
9 PS_FLOOR_HIGH - Lower bound reporting high water mark.
10 The base station shall set this field to the high water mark for
11 the lower bound below which the mobile station is to send Pilot
12 Strength Measurement Mini Messages when the threshold mode
13 is enabled.

15 number equal to - 2 × 10 × log10 Ec/Io .
16 PS_FLOOR_LOW - Lower bound reporting low water mark.
17 The base station shall set this field to the low water mark for
18 the lower bound below which the mobile station is to send Pilot
19 Strength Measurement Mini Messages when the threshold mode
20 is enabled.

23 PS_CEILING_HIGH - Upper bound reporting high water mark.
24 The base station shall set this field to the high water mark for
25 the upper bound above which the mobile station is to send
26 Pilot Strength Measurement Mini Messages when the threshold
27 mode is enabled.

30 PS_CEILING_LOW - Upper bound reporting low water mark.
31 The base station shall set this field to the low water mark for
32 the upper bound above which the mobile station is to send
33 Pilot Strength Measurement Mini Messages when the threshold
34 mode is enabled.

37 THRESHOLD-
38 _INTERVAL - Threshold reporting interval.
39 The base station shall set this field to the interval (in 20 ms
40 units) between Pilot Strength Measurement Mini Messages when
41 the threshold reporting mode is enabled.
3-584
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.41 User Zone Reject Message
2 MSG_TAG: UZRM
Field Length (bits)
REJECT_UZID 16
REJECT_ACTION_INDI 3
UZID_ASSIGN_INCL 1
ASSIGN_UZID 0 or 16
3 REJECT_UZID - Rejected User Zone identifier.
5 of the User Zone rejected by the base station.
6 REJECT_ACTION_INDI - Rejection action indicator.
8 Table 3.7.2.3.2.29-1 3.7.5.19-1 corresponding to the User
9 Zone rejection action field to identify the mobile station action.
10 UZID_ASSIGN_INCL - User Zone identifier assignment included indicator.
11 If assigned UZID information is included, the base station

14 ASSIGN_UZID - Assigned User Zone identifiers.
16 of the User Zone assigned to the mobile station.
3-585
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.42 User Zone Update Message
2 MSG_TAG: UZUM
Specific Field Length (bits)
UZID 16
4 UZID - User Zone identifier.
6 supported by the base station.
3-586
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.43 Call Assignment Message
2 MSG_TAG: CLAM
Field Length (bits)
RESPONSE_IND 1
TAG 0 or 4
ACCEPT_IND 0 or 1
REJECT_PKTDATA_IND 0 or 1
SO_INCL 1
SO 0 or 16
CON_REF_INCL 1
CON_REF 0 or 8
6 The base station shall set this field to ‘1’ if this message is a
7 response to an Enhanced Origination Message from the mobile

14 field of the Enhanced Origination Message to which this
15 message is the response.
16 ACCEPT_IND – Accepted indicator.

3-587
3GPP2 C.S0005-A v6.0
1 If the base station accepts the call request from the mobile
2 station, the base station shall set this field to ‘1’; otherwise,
4 REJECT_PKTDATA_IND – Packet data service option rejection indicator.
5 If the ACCEPT_IND field is not included or is included and is

7 base station shall include this field and shall set it as follows:
8 The base station shall set this field to ‘1’ to indicate rejection
9 of the packet data service option requested by the mobile
11 BYPASS_ALERT-
12 _ANSWER – Bypass alert indicator.


20 SO_INCL – Service option included indicator.
21 The base station shall set this field to ‘1’ if the service option
22 field is included in this message; otherwise, it the base station
24 SO – Service option.
25 If the SO_INCL field is set to ‘0’, the base station shall omit
26 this field; otherwise, the base station shall include this field
27 and shall set it to the value of the service option number (as
28 specified in [30]) that the base station proposes for this call.
30 If the ACCEPT_IND field is not included or is included but is

31 set to ‘1’, the base station shall set this field to ‘1’; otherwise,
3-588
3GPP2 C.S0005-A v6.0

4 that was/will be assigned to the service option connection
3-589
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.44 Extended Alert With Information Message
2 MSG_TAG: EAWIM
Field Length (bits)
CON_REF_INCL 1
CON_REF 0 or 8
NUM_REC 4
RECORD_TYPE 8
RECORD_LEN 8


18 The base station shall include NUM_REC occurrences of the following three-field record as
3-590
3GPP2 C.S0005-A v6.0

6 in 3.7.5.
3-591
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.45 Extended Flash With Information Message
2 MSG_TAG: EFWIM
Field Length (bits)
CON_REF_INCL 1
CON_REF 0 or 8
NUM_REC 4
RECORD_TYPE 8
RECORD_LEN 8


18 The base station shall include NUM_REC occurrences of the following three-field record as
3-592
3GPP2 C.S0005-A v6.0

6 in 3.7.5.
3-593
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.46 Security Mode Command Message
2 MSG_TAG: SMCM
Field Length (bits)
USE_TIME 1
ACTION_TIME 0 or 6
D_SIG_ENCRYPT_MODE 3
NUM_RECS 3
NUM_RECS occurrences of the following two-field record
CON_REF 8
UI_ENCRYPT_MODE 3
USE_NEW_KEY 0 or 1
ENC_KEY_SIZE 0 or 3
KEY_SEQ 0 or 4

6 this message.
15 D_SIG_ENCRYPT_MODE - Dedicated channel Common Channel encryption mode indicator.
16 The base station shall set it to signaling message encryption
17 mode, as shown in Table 3.7.4.5-1.
18 NUM_REC - Number of user information encryption records.
19 The base station shall set this field to the number of user
20 information encryption records included in this message.
21 The base station shall include NUM_REC occurrences of the following two-field record
22 CON_REF - Connection reference corresponding to the service option
23 connection requesting for encryption.
3-594
3GPP2 C.S0005-A v6.0
1 If this field is included, the base station shall set this field to
2 the connection reference of the service option connection
3 corresponding to this user information encryption.
4 UI_ENCRYPT_MODE - Encryption mode indicator for user information privacy.
5 The base station shall set this field to user information
6 encryption mode for the service option connection identified
7 by CON_REF as shown in Table 3.7.5.7-3.
8 USE_NEW_KEY - Use new encryption key indication.
9 If both of UI_ENCRYPT_MODE and SIG_ENCRYPT_MODE are
10 equal to ‘000’ or any reserved value, the base station shall omit
11 this field; otherwise, the base station shall include this field. If
12 included, the base station shall set this field to ‘0’ to indicate that
13 the stored encryption key is to be used by the mobile station and
14 to ‘1’ to indicate that the new encryption key is to be used by the
15 mobile station.
16 ENC_KEY_SIZE - Key Size used for user information and signaling encryption
17 If D_SIG_ENCRYPT_MODE is equal to ‘001’ If USE_NEW_KEY
18 is included and is set to ‘0’, the base station shall omit this
20 set this field to the encryption key size for user information
21 encryption and signaling encryption according to as shown in
22 Table 3.7.4.5-2; otherwise, the base station shall omit this
23 field.
25 If USE_NEW_KEY is not included, or if USE_NEW_KEY is
26 included and is set to ‘0’, the base station shall include this field;
27 otherwise, the base station shall omit this field. If this field is
28 included, the base station shall set it to the encryption key
29 sequence number to be used by the mobile station.
30 C_SIG_ENCRYPT_
32 indicator.
33 If C_SIG_ENCRYPT_MODE is included in this message, the
36 C_SIG_ENCRYPT_
3-595
3GPP2 C.S0005-A v6.0
1 3.7.3.3.2.47 Base Station Status Response Message
2 MSG_TAG: BSSRSPM
Field Length (bits)
QUAL_INFO_TYPE 8
QUAL_INFO_LEN 3
Type-specific fields. 8 × QUAL_INFO_LEN
NUM_RECORDS 4
NUM_RECORD occurrences of the following variable length
record:
RECORD_TYPE 8
RECORD_LENGTH 8
Record type specific fields variable
RESERVED 0-7 (as required)

4 The base station shall set this field to the QUAL_INFO_TYPE
5 field in the corresponding Base Station Status Request
6 Message.
8 The base station shall set this field to the QUAL_INFO_LEN
9 field in the corresponding Base Station Status Request
10 Message.
13 information in the corresponding Base Station Status Request
14 Message.
15 NUM_RECORD - Number of records included in this message.
17 occurrences of RECORD_TYPE field in this message.
18 The base station shall include one occurrence of the following variable-length record for
19 each information record that is included:
23 information record included.
3-596
3GPP2 C.S0005-A v6.0
1 Table 3.7.3.3.3.47-1. Base Station Status Response Information Record

2 Types
Information Record Requested Record Type
Pilot Information 00000000

Reserved 00000001-
11111111
3 RECORD_LENGTH - Information record length.
4 The base station shall set this field to the length, in octets, of
5 the record type specific fields included in this record.
6 Record type specific

7 fields - Record type specific fields
8 The base station shall set this field to the type specific fields
9 corresponding to this record type.
10 If the RECORD_TYPE field is set to ‘00000000’, the base

11 station shall set the record type specific field as follows:
12
Field Length (bits)
NUM_PILOTS 4
SID_NID_IND 1
NUM_PILOTS occurrences of the

following variable-length record
RECORD_LEN 4
PILOT_PN 9
BASE_ID 16
SID_NID_INCL 0 or 1
SID 0 or 15
NID 0 or 16
RESERVED_1 0–7 (as required)
13
14 NUM_PILOTS - Number of Pilots reported.
3-597
3GPP2 C.S0005-A v6.0
2 whose information is reported in this message.
3 The base station shall set this field to a number equal or

4 greater than one.
5 SID_NID_IND - SID, NID included indicator.
6 The base station shall set this field to ‘1’ if SID, NID
7 information is included in this message; otherwise, it shall set
9 The base station shall include NUM_PILOTS occurrences of the following variable
10 length record:
11 RECORD_LEN - Record Length
12 The base station shall set this field to the length in octets of
13 this record.
18 The base station shall set this field to the Base Station
19 identification number corresponding to this pilot.
20 SID_NID_INCL - SID, NID included indicator.
21 If the SID_NID_IND field is set to ‘0’, the base station shall

24 If this is the first pilot included in this message, the base

27 If the SID and NID of this pilot are same as the SID and NID
28 of the previous pilot, the base station shall set this field to ‘0’;
3-598
3GPP2 C.S0005-A v6.0
1 If the SID_NID_INCL field is not included or is included and is

5 number of the system corresponding to this pilot (see
6 2.6.5.2).
8 If the SID_NID_INCL field is not included or is included and is


12 identification number of the network corresponding to this
13 pilot (see 2.6.5.2).

16 make the length of the pilot specific record equal to an integer
18

23
24
3-599
3GPP2 C.S0005-A v6.0
1 3.7.4 Orders
2 Order Messages are sent by the base station on the f-csch and the f-dsch. The general PDU
3 format used on the f-csch is defined in 3.7.2.3.2.7, and the general PDU format used on the
4 f-dsch is defined in 3.7.3.3.2.1. There are many specific types of Order Messages, as shown
5 in Table 3.7.4-1.
6 The base station may send on the f-csch any type of order shown in Table 3.7.4-1 with a ‘Y’
7 in the first column, but shall not send on the f-csch any type of order with an ‘N’ in the first
8 column. The base station may send on the f-dsch any type of order shown in Table 3.7.4-1
9 with a ‘Y’ in the second column, but shall not send on the f-dsch any type of order with an
10 ‘N’ in the second column.
11 An order consists of a 6-bit order code and zero or more order-specific fields. The base
12 station shall set the ORDER field in the Order Message to the order code shown in Table
13 3.7.4-1 corresponding to the type of order being sent.
14 If the order qualification code in the fourth column of Table 3.7.4-1 is ‘00000000’ and there
15 are no other additional fields as shown by an ‘N’ in the sixth column, the base station shall
16 include no order qualification code or other order-specific fields in the Order Message. The
17 order qualification code of such a message is implicitly ‘00000000’.
18 If the order qualification code is not ‘00000000’ and there are no other additional fields as
19 shown in Table 3.7.4-1 by an ‘N’ in the sixth column, the base station shall include the
20 order qualification code as the only order specific field in the Order Message.
21 If there are other additional fields as shown in Table 3.7.4-1 by a ‘Y’ in the sixth column,
22 the base station shall include order-specific fields as specified in the corresponding
23 subsection of this section.
3-600
3GPP2 C.S0005-A v6.0
2 (Part 1 of 4)
Order Qual-
Addi-
f-csch f-dsch Order ification ACTION_ tional
Order Order Code, Code, TIME Fields Name/Function
other than
ORDER ORDQ can be
ORDQ
(binary) (binary) specified
Y N 000001 00000000 N N Abbreviated Alert Order

Y Y 000010 00000000 N Y Base Station Challenge
Confirmation Order
(see 3.7.4.1)
N Y 000011 000000nn Y N Message Encryption
Mode Order (where nn is
the mode per Table
3.7.2.3.2.8-2)
Y N 000100 00000000 N N Reorder Order
N Y 000101 0000nnnn N N Parameter Update Order
(where ‘nnnn’ is the
Request Number)
Y Y 000110 00000000 N N Audit Order
Y N 001001 00000000 N N Intercept Order
N Y 001010 00000000 N N Maintenance Order
Y Y 010000 00000000 N N Base Station
Acknowledgment Order
(see [4])
N Y 010001 00000000 N N Pilot Measurement
Request Order
N Y 010001 Nnnnnnnn N Y Periodic Pilot
(in the Measurement Request
range of Order
00000001 (see 3.7.4.6)
to
11111111)
Y Y 010010 0001nnnn N N Lock Until Power-Cycled
Order (where nnnn is
the lock reason)
Y Y 010010 0010nnnn N N Maintenance Required
Order (where nnnn is
the maintenance reason)
Y N 010010 11111111 N N Unlock Order
3-601
3GPP2 C.S0005-A v6.0
2 (Part 2 of 4)
Order Qual-
Addi-
f-dsch Order ification ACTION_ tional
f-csch Order Code, Code, TIME Fields Name/Function
other than
Order ORDER ORDQ can be
ORDQ
N Y 010011 00000000 Y Y Service Option Request

Order (Band Class 0
only) (see 3.7.4.2)
N Y 010100 00000000 Y Y Service Option Response
Order (Band Class 0
only; see 3.7.4.3)
Y Y 010101 00000000 N N Release Order (no reason
given)
Y Y 010101 00000010 N N Release Order (indicates
that requested service
option is rejected)
N Y 010110 00000000 N N Outer Loop Report
Request Order
N Y 010111 00000000 Y N Long Code Transition
Request Order (request
public)
N Y 010111 00000001 Y N Long Code Transition
Request Order (request
private)
N Y 011001 0000nnnn N N Continuous DTMF Tone
Order (where the tone is
designated by ‘nnnn’ as
defined in Table
2.7.1.3.2.4-4)
N Y 011001 11111111 N N Continuous DTMF Tone
Order (stop continuous
DTMF tone)
N Y 011010 nnnnnnnn N N Status Request Order
(see 3.7.4.4)
Y N 011011 00000000 N N Registration Accepted
Order (ROAM_INDI not
included; see 3.7.4.5)
3-602
3GPP2 C.S0005-A v6.0
2 (Part 3 of 4)
Order Qual-
Additional
f-dsch Order ification ACTION_ Fields
f-csch Order Code, Code, TIME can other than Name/Function
ORDQ
Order ORDER ORDQ be
Y N 011011 00000001 N N Registration Request

Order
Y N 011011 00000010 N N Registration Rejected
Order
Y N 011011 00000100 N N Registration Rejected
Order (delete TMSI)
Y N 011011 00000101 N Y Registration Accepted
Order (ROAM_INDI
included but the
signaling encryption
related fields are not
Y N 011011 00000111 N Y Registration Accepted
0 Order (ROAM_INDI, and
the signaling encryption
related fields
EXT_ENC_MSB,
SIG_ENCRYPT_MODE,
and KEY_SIZE are
N Y 011101 nnnnnnnn Y N Service Option Control
Order (Band Class 0
only) (the specific
control is designated by
‘nnnnnnnn’ as
determined by each
service option)
Y Y 011110 nnnnnnnn N N Local Control Order
(the specific order is
designated by
‘nnnnnnnn’ as
determined by each
system)
3-603
3GPP2 C.S0005-A v6.0
Y N 011111 00000000 N N Slotted Mode Order

(transition to the slotted
mode operation.)
3-604
3GPP2 C.S0005-A v6.0
2 (Part 4 of 4)
Order Qual-
Additional
f-dsch Order ification ACTION_ Fields
f-csch Order Code, Code, TIME can other than Name/Function
ORDQ
Order ORDER ORDQ be
Y Y 100000 00000000 N Y Retry Order (indicates

that the requested
operation is rejected
and retry delay is
included, see 3.7.4.7)
Y Y 100001 00000000 Y N Base Station Reject

Order (indicates that
the base station can not
decrypt an Origination
Message from the
mobile station)
Y Y 100001 00000001 Y N Base Station Reject

Order (indicates that
the base station can not
decrypt any message
(other than an
Origination Message)
from the mobile station)
3-605
3GPP2 C.S0005-A v6.0
1 3.7.4.1 Base Station Challenge Confirmation Order

2 The Base Station Challenge Confirmation Order can be sent on either the f-csch or on the f-
3 dsch.
Order Specific Field Length (bits)
ORDQ 8
AUTHBS 18
RESERVED 6
6 ORDQ - Order qualification code.

8 AUTHBS - Challenge response.
3-606
3GPP2 C.S0005-A v6.0
1 3.7.4.2 Service Option Request Order

2 The Service Option Request Order can be sent only on the f-dsch.
ORDQ 8
SERVICE_OPTION 16

9 shown in [30], corresponding to the requested or alternative
10 service option.
3-607
3GPP2 C.S0005-A v6.0
1 3.7.4.3 Service Option Response Order

2 The Service Option Response Order can be sent only on the f-dsch.
ORDQ 8
SERVICE_OPTION 16

9 shown in [30], corresponding to the accepted service option, or
10 to ‘0000000000000000’ to reject the last service option
11 requested by the mobile station.
3-608
3GPP2 C.S0005-A v6.0
1 3.7.4.4 Status Request Order

2 The Status Request Order can be sent only on the f-dsch. The ORDQ field of the Status
3 Request Order specifies the information record to be returned by the mobile station in the
4 Status Message.
ORDQ 8

8 The base station shall set this field to the order qualification
9 code corresponding to the information record type to be
10 returned by the mobile station in the Status Message, as
12 If MOB_P_REV is equal to or greater than seven, the base

13 station shall not request the Call Mode information record
14 (record type ‘00000111’ in Table 3.7.2.3.2.15-2).
15
16 Table 3.7.4.4-1. Status Request ORDQ Values
Information Record Requested ORDQ (binary)
Reserved 00000110
Call Mode 00000111
Terminal Information 00001000
Roaming Information 00001001
Security Status 00001010
IMSI 00001100
ESN 00001101
IMSI_M 00001110
IMSI_T 00001111
All other ORDQ values are reserved.
3-609
3GPP2 C.S0005-A v6.0
1 3.7.4.5 Registration Accepted Order
2 The Registration Accepted Order can be sent only on the f-csch.

3
ORDQ 8
ROAM_INDI 0 or 8
USE_NEW_KEY 0 or 1
ENC_KEY_SIZE 0 or 3
KEY_SEQ 0 or 4

6 If only ORDQ is included in the order, the base station shall set
7 this field to ‘00000000’. If only ORDQ and ROAM_INDI are
8 included in the order, the base station shall set this field to
9 ‘00000101’. If ORDQ, ROAM_INDI, and the signaling encryption
10 related fields are included in the order, the base station shall set
11 this field to ‘00000111’.
12 ROAM_INDI - Roaming display indication.
13 If ORDQ is set to ‘00000000’, the base station shall omit this field.
14 If ORDQ is set to ‘00000101’ or ‘00000111’, the base station shall
15 include this field and shall set it to the appropriate ROAM_INDI
16 code corresponding to the MS roaming condition. These values
17 are defined in [30].
18 C_SIG_ENCRYPT_MODE - Common channel sSignaling message encryption mode indicator.
19 If ORDQ is set to ‘00000111’, the base station shall include this
20 field and shall set it to the common channel signaling message
21 encryption mode, as shown in Table 3.7.4.5-1; otherwise the base
3-610
3GPP2 C.S0005-A v6.0
1 Table 3.7.4.5-1. (Part 1 of 2) Signaling Message Encryption Modes
C_SIG_ENCRYPT_MOD
E Field
(binary)
000 Common Channel Signaling eEncryption disabled

001 Enhanced Cellular Message Encryption Algorithm
enabled
010 Rijndael Encryption Algorithm enabled
011010 - 111 Reserved
3-611
3GPP2 C.S0005-A v6.0
2 Table 3.7.4.5-1 (Part 2 of 2). Signaling Message Encryption Modes
D_SIG_ENCRYPT_MOD
E Field6
(binary)
000 If D_SIG_ENCRYPT_MODEr is included and is set to

‘000’ in a Channel Assignment Message or Extended
Channel Assignment Message, the mobile station is to
cContinue to use the current common channel
encryption mode and algorithm for the dedicated
channel.
If D_SIG_ENCRYPT_MODEr is included and is set to
‘000’ in a Security Mode Command Message, General
Handoff Direction Message or Universal Handoff Direction
Message, the mobile station is to disable dedicated
channel Signaling encryption.
001 Enhanced Cellular Message Encryption Algorithm
enabled
010 Rijndael Encryption Algorithm enabled
011010 - 111 Reserved
5 USE_NEW_KEY - Use new encryption key indication.

6 If SIG_ENCRYPT_MODE is set to ‘001’, the base station shall
8 If this field is included, the base station shall set this field as
9 follows:
11 stored encryption key is to be used by the mobile station, and to
12 ‘1’ to indicate that the new encryption key is to be used by the
13 mobile station.
14 ENC_KEY_SIZE – Key sSize used for encryption
6 D_SIG_ENCRYPT_MODE = ‘000’ is used to indicate to the mobile station that the current common
r
channel encryption mode (and encryption algorithm, if encryption is turned on) shall be used for
dedicated channel encryption. D_SIG_ENCRYPT_MODEs = ‘000’ means that no dedicated channel
extended encryption shall be performed in the mobile station.
3-612
3GPP2 C.S0005-A v6.0
1 If C_SIG_ENCRYPT_MODE is set to ‘001’If USE_NEW_KEY is

2 not included, or if USE_NEW_KEY is included and is set to ‘0’,
3 the base station shall omit this field; otherwise, the base
4 station shall include this field and set this field to the
5 encryption key_-size used for encryption according to as
6 shown in Table 3.7.4.5-2; otherwise, the base station shall
7 omit this field.
8 Table 3.7.4.5-2. ENC_KEY_SIZE Values
ENC_KEY_SIZE (binary) Descriptions
000 40 bits Reserved

001 64 bits
010 128 bits
011-111 Reserved

14 station.
17 make the total length of the fields included in this order equal
3-613
3GPP2 C.S0005-A v6.0
1 3.7.4.6 Periodic Pilot Measurement Request Order

2 The Periodic Pilot Measurement Request Order can be sent only on the f-dsch.
ORDQ 8
MIN_PILOT_PWR_THRESH 5
MIN_PILOT_EC_IO_THRESH 5
INCL_SETPT 1
RESERVED 65

6 If INCL_SETPT equals ‘0’, the base station shall set this field
7 to a report period, in units of 0.08 seconds, in the range of
8 ‘00001010’ to ‘1111110’ inclusive; otherwise, the base station
9 shall set this field to a report period, in units of 0.08 seconds,
10 in the range of ‘00000001’ to ‘11111110’ inclusive. The base
11 station shall set this field to ‘11111111’ to request a one time
12 Periodic Pilot Strength Measurement Message.
13 MIN_PILOT_PWR-
14 _THRESH - The threshold of the total received Ec of the pilots in the
15 Active Set.
16 If the mobile station is to report pilot strength measurements
17 periodically to the base station irrespective of the pilot power
18 of the Active Set, the base station shall set this field to
19 ‘11111’; otherwise, the base station shall set this field to the
20 total Ec threshold, expressed as an unsigned binary number
21 equal to:
22  (10 × log10(pilot_ec_thresh) + 120) / 2 
23 where pilot_ec_thresh is the threshold of the mobile station

24 received total Ec (in mW) of the pilots in the Active Set below
25 which the mobile station is to send the pilot strength
26 measurements periodically to the base station.
27 MIN_PILOT_EC-
28 _IO_THRESH - Pilot Strength Threshold of Serving Frequency.
29 If the mobile station is to ignore this threshold, the base
31 station shall set this field to the total Ec/Io threshold,
32 expressed as an unsigned binary number equal to:
33 - 20 × log10 pilot_streng_thresh ,
3-614
3GPP2 C.S0005-A v6.0
1 where pilot_streng_thresh is the threshold of the total received

2 Ec/Io of the pilots in Active Set (see 2.6.6.2.2) below which the
3 mobile station is to send the pilot strength measurements
4 periodically to the base station.
5 INCL_SETPT - Include Setpoint information indicator.
7 mobile station shall include outer loop Eb/Nt setpoint
8 information in the Periodic Pilot Strength Measurement
9 Message; otherwise, the base station shall set this field to ‘0’.
3-615
3GPP2 C.S0005-A v6.0
1 3.7.4.7 Retry Order

2 The Retry Order can be sent on either the f-csch or on the f-dsch to indicate the requested
3 service is rejected and specify the retry delay.
ORDQ 8
RETRY_TYPE 3
RETRY_DELAY 0 or 8
RESERVED 5

7 RETRY_TYPE - Retry delay type.
8 The base station shall set this field specified as in Table
9 3.7.4.7-1.
10 Table 3.7.4.7-1 Retry Delay Type
Value Retry Type Usage

(binary)
000 Clear all The Retry Order is used to clear

any existent retry delay
001 Origination The Retry Order specifies the
RETRY_DELAY for a Packet Data
Origination Message or Enhanced
Origination Message
010 Resource The Retry Order specifies the
Request RETRY_DELAY for a Resource
Request Message or Resource
Request Mini Message
011 Supplement The Retry Order specifies the
al Channel RETRY_DELAY for a Supplemental
Request Channel Request Message or
Supplemental Channel Request
Mini Message
100-111 Reserved
11
12 RETRY_DELAY - Retry delay.
3-616
3GPP2 C.S0005-A v6.0
1 If RETRY_TYPE is set to ‘000’ the base station shall omit this

2 field. Otherwise the base station shall include this field and
4 If RETRY_TYPE is set to ‘001’, the base station shall set this
5 field to the duration of the delay interval, as shown in Table
6 3.7.4.7-2, during which the mobile station is not permitted to
7 send an Origination Message or an Enhanced Origination
8 Message with the same Packet Data Service Option. The base
9 station shall set this field to ‘00000000’ to indicate that there
10 is no retry delay or to clear a previously set retry delay.
11 Table 3.7.4.7-2 Retry Delay for RETRY_TYPE ‘001’
Bits Description
7 (MSB) Unit for the Retry Delay
‘0’ – unit is 1s
‘1’ – unit is 1 min
6 to 0 Retry Delay interval
12
13 If RETRY_TYPE is set to ‘010’ or ‘011’, the base station shall

14 set this field to the duration of the delay interval in units of
15 320 ms during which the mobile station is not permitted to
16 send another Supplemental Channel Request (Mini) Message or
17 Resource Request (Mini) Message. The base station shall set
18 RETRY_DELAY to ‘00000000’ to indicate that there is no retry
19 delay or to clear a previously set retry delay. The base station
20 shall set RETRY_DELAY to ‘11111111’ to indicate that the
21 mobile station is to refrain from sending the request
22 indefinitely.
25
26
27
3-617
3GPP2 C.S0005-A v6.0
1 3.7.5 Information Records
2 On the f-csch, information records may be included in the Feature Notification Message. On
3 the f-dsch, information records may be included in the Alert with Information Message, the
4 Flash with Information Message, the Extended Alert with Information Message, and the
5 Extended Flash with Information Message, the Service Request Message, the Service
6 Response Message, the Service Connect Message, the General Handoff Direction Message,
7 and the Universal Handoff Direction Message. Table 3.7.5-1 lists the information record
8 type values that may be used with each message type. The following sections describe the
9 contents of each of the record types in detail.
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-618
3GPP2 C.S0005-A v6.0
Record
Type
Information Record (binary) Message Type f-csch f-dsch
Display 00000001 FNM Y N

AWI N Y
FWI N Y
Called Party Number 00000010 FNM Y N
AWI N Y
FWI N Y
Calling Party Number 00000011 FNM Y N
AWI N Y
FWI N Y
Connected Number 00000100 FWI N Y
Signal 00000101 FNM Y N
AWI N Y
FWI N Y
Message Waiting 00000110 FNM Y N
AWI N Y
FWI N Y
Service Configuration 00000111 SRQM N Y
SRPM N Y
SCM N Y
GHDM N Y
UHDM N Y
Called Party Subaddress 00001000 FNM Y N
AWI N Y
FWI N Y
3-619
3GPP2 C.S0005-A v6.0
Record
Type
Calling Party Subaddress 00001001 FNM Y N

AWI N Y
FWI N Y
Connected Subaddress 00001010 FWI N Y
Redirecting Number 00001011 FNM Y N
AWI N Y
FWI N Y
Redirecting Subaddress 00001100 FNM Y N
AWI N Y
FWI N Y
Meter Pulses 00001101 AWI N Y
FWI N Y
Parametric Alerting 00001110 FNM Y N
AWI N Y
FWI N Y
Line Control 00001111 AWI N Y
FWI N Y
Extended Display 00010000 FNM Y N
AWI N Y
FWI N Y
3-620
3GPP2 C.S0005-A v6.0
Record
Type
Non-Negotiable Service 00010011 SCM N Y

Configuration
GHDM N Y
UHDM N Y
Multiple Character 00010100 FNM Y N
Extended Display
AWI N Y
FWI N Y
Call Waiting Indicator 00010101 AWI N Y
FWI N Y
Extended Record Type - 11111110 Country-Specific

International

“AWI” refers to either the Alert With Information Message or the Extended Alert With
“FWI” refers to either the Flash With Information Message or the Extended Flash With
3-621
3GPP2 C.S0005-A v6.0
1 3.7.5.1 Display
2 This information record allows the network to supply display information that may be
3 displayed by the mobile station.

CHARi 8
8 each character to be displayed. The base station shall set
10 corresponding to the character entered, as specified in [9],
11 with the most significant bit set to ‘0’.
3-622
3GPP2 C.S0005-A v6.0
1 3.7.5.2 Called Party Number
2 This information record identifies the called party’s number.
NUMBER_TYPE 3
NUMBER_PLAN 4
CHARi 8
RESERVED 1
5 NUMBER_TYPE - Type of number.

6 The base station shall set this field to the NUMBER_TYPE
8 of the called number, as defined in [7], Section 4.5.9.
9 NUMBER_PLAN - Numbering plan.
10 The base station shall set this field to the NUMBER_PLAN
12 numbering plan used for the called number, as defined in [7],
13 Section 4.5.9.
16 each character in the called number. The base station shall
3-623
3GPP2 C.S0005-A v6.0
1 3.7.5.3 Calling Party Number
2 This information record identifies the calling party’s number.
NUMBER_TYPE 3
NUMBER_PLAN 4
PI 2
SI 2
CHARi 8
RESERVED 5

8 of the calling number, as defined in [7], Section 4.5.9.
12 numbering plan used for the calling number, as defined in [7],
13 Section 4.5.9.
14 PI - Presentation indicator.
15 This field indicates whether or not the calling number should
16 be displayed.
17 The base station shall set this field to the PI value shown in
20 SI - Screening indicator.
21 This field indicates how the calling number was screened.
22 The base station shall set this field to the SI value shown in
26 The base stations shall include one occurrence of this field for
27 each character in the calling number. The base station shall
3-624
3GPP2 C.S0005-A v6.0

3-625
3GPP2 C.S0005-A v6.0
1 3.7.5.4 Connected Number
2 This information record identifies the responding party to a call.
NUMBER_TYPE 3
NUMBER_PLAN 4
PI 2
SI 2
CHARi 8
RESERVED 5

8 of the connected number, as defined in [7], Section 4.5.9.
12 numbering plan used for the connected number, as defined in
13 [7], Section 4.5.9.
15 This field indicates whether or not the connected number
16 should be displayed.
17 The base station shall set this field to the PI value shown in
21 This field indicates how the connected number was screened.
22 The base station shall set this field to the SI value shown in
27 each character in the connected number. The base station
3-626
3GPP2 C.S0005-A v6.0

3-627
3GPP2 C.S0005-A v6.0
1 3.7.5.5 Signal
2 This information record allows the network to convey information to a user by means of
3 tones and other alerting signals.
4 The Standard Alert is defined as SIGNAL_TYPE = ‘10’, ALERT_PITCH = ‘00’ and SIGNAL =
5 ‘000001’.
SIGNAL_TYPE 2
ALERT_PITCH 2
SIGNAL 6
RESERVED 6
8 SIGNAL_TYPE - Signal type.

9 The base station shall set this field to the signal type value
11
12 Table 3.7.5.5-1. Signal Type
SIGNAL_TYPE
Description
(binary)
Tone signal 00
ISDN Alerting 01
IS-54B Alerting 10
Reserved 11
13
14 ALERT_PITCH - Pitch of the alerting signal.

15 This field is ignored unless SIGNAL_TYPE is ‘10’, IS-54B
16 Alerting.
17 If SIGNAL_TYPE is ‘10’, the base station shall set this field to
18 the alert pitch shown in Table 3.7.5.5-2; otherwise, the base
20
3-628
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.5-2. Alert Pitch
ALERT_PITCH
Description
(binary)
Medium pitch (standard alert) 00

High pitch 01
Low pitch 10
Reserved 11
3 SIGNAL - Signal code.

4 The base station shall set this field to the specific signal
5 desired. If SIGNAL_TYPE is ‘00’, the base station shall set this
6 field as described in Table 3.7.5.5-3. If SIGNAL_TYPE is ‘01’,
7 the base station shall set this field as described in
8 Table 3.7.5.5-4. If SIGNAL_TYPE is ‘10’, the base station shall
9 set this field as described in Table 3.7.5.5-5.
10
3-629
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.5-3. Tone Signals (SIGNAL_TYPE = ‘00’)
SIGNAL
Description
(binary)
Dial tone on: a continuous 350 Hz tone 000000

added to a 440 Hz tone.
Ring back tone on: a 440 Hz tone added 000001
to a 480 Hz tone repeated in a 2 s on, 4 s
off pattern.
Intercept tone on: alternating 440 Hz and 000010
620 Hz tones, each on for 250 ms.
Abbreviated intercept: alternating 440 Hz 000011
and 620 Hz tones, each on for 250 ms,
repeated for four seconds.
Network congestion (reorder) tone on: a 000100
480 Hz tone added to a 620 Hz tone
repeated in a 250 ms on, 250 ms off cycle.
Abbreviated network congestion (reorder): 000101
a 480 Hz tone added to a 620 Hz tone
repeated in a 250 ms on, 250 ms off cycle
for four seconds.
Busy tone on: a 480 Hz tone added to a 000110
620 Hz tone repeated in a 500 ms on,
500 ms off cycle.
Confirm tone on: a 350 Hz tone added to 000111
a 440 Hz tone repeated 3 times in a 100
ms on, 100 ms off cycle.
Answer tone on: answer tone is not 001000
presently used in North American
networks.
Call waiting tone on: a 300 ms burst of 001001
440 Hz tone.
Pip tone on: four bursts of 480 Hz tone 001010
(0.1 s on, 0.1 s off).
Tones off 111111
All other SIGNAL values are reserved
3-630
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.5-4. ISDN Alerting (SIGNAL_TYPE = ‘01’)
SIGNAL
Description
(binary)
Normal Alerting: 2.0 s on, 4.0 s off, 000000

repeating
Intergroup Alerting: 0.8 s on, 0.4 s off, 000001
0.8 s on, 4.0 s off, repeating
Special/Priority Alerting: 0.4 s on, 0.2 s 000010
off, 0.4 s on, 0.2 s off, 0.8 s on, 4.0 s off,
repeating
Reserved (ISDN Alerting pattern 3) 000011
“Ping ring”: single burst of 500 ms 000100
Alerting off 001111
3-631
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.5-5. IS-54B Alerting (SIGNAL_TYPE = ‘10’)
SIGNAL
Description
(binary)
No Tone: Off 000000

Long: 2.0 s on, 4.0 s off, repeating 000001
(standard alert)
Short-Short: 0.8 s on, 0.4 s off, 0.8 s on, 000010
4.0 s off, repeating
Short-Short-Long: 0.4 s on, 0.2 s off, 0.4 s 000011
on, 0.2 s off, 0.8 s on, 4.0 s off, repeating
Short-Short-2: 1.0 s on, 1.0 s off, 1.0 s on, 000100
3.0 s off, repeating.
Short-Long-Short: 0.5 s on, 0.5 s off, 1.0 s 000101
on, 0.5 s off, 0.5 s on, 3.0 s off, repeating.
Short-Short-Short-Short: 0.5 s on, 0.5 s 000110
off, 0.5 s on, 0.5 s off, 0.5 s on, 0.5 s off,
0.5 s on, 2.5 s off, repeating.
PBX Long: 1.0 s on, 2.0 s off, repeating. 000111
PBX Short-Short: 0.4 s on, 0.2 s off, 0.4 s 001000
on, 2.0 off, repeating.
PBX Short-Short-Long: 0.4 s on, 0.2 s off, 001001
0.4 s on, 0.2 s off, 0.8 s on, 1.0 s off,
repeating.
PBX Short-Long-Short: 0.4 s on, 0.2 s off, 001010
0.8 s on, 0.2 s off, 0.4 s on, 1.0 s off,
repeating.
PBX Short-Short-Short-Short: 0.4 s on, 001011
0.2 s off, 0.4 s on, 0.2 s off, 0.4 s on, 0.2 s
off, 0.4 s on, 0.8 s off, repeating.
Pip-Pip-Pip-Pip: 0.1 s on, 0.1 s off, 0.1 s 001100
on, 0.1 s off, 0.1 s on, 0.1 s off, 0.1 s on.

3-632
3GPP2 C.S0005-A v6.0
1 3.7.5.6 Message Waiting
2 This information record conveys to the user the number of messages waiting.
MSG_COUNT 8
5 MSG_COUNT - Number of waiting messages.

7 waiting.
3-633
3GPP2 C.S0005-A v6.0
1 3.7.5.7 Service Configuration

2 For the mobile station, this record is included in a Status Response Message to return the
3 current service configuration, and in a Service Request Message and a Service Response
4 Message to propose a service configuration.
5 For a base station, this record is included in a Service Request Message and a Service
6 Response Message to propose a service configuration. It is included in a Service Connect
7 Message to specify an actual service configuration to be used. It can be included in a
8 General Handoff Direction Message and Universal Handoff Direction Message to specify an
9 actual service configuration to be used.
10
FOR_MUX_OPTION 16
REV_MUX_OPTION 16
FOR_NUM_BITS 8
REV_NUM_BITS 8
NUM_CON_REC 8
NUM_CON_REC occurrences of the following variable-length

record:
3-634
3GPP2 C.S0005-A v6.0
RECORD_LEN 8
CON_REF 8
SERVICE_OPTION 16
FOR_TRAFFIC 4
REV_TRAFFIC 4
UI_ENCRYPT_MODE 3
SR_ID 3
RLP_INFO_INCL 1
RLP_BLOB_LEN 0 or 4
RLP_BLOB 0 or (8 ×
RLP_BLOB_LEN)
QOS_PARMS_INCL 1
QOS_PARMS_LEN 0 or 5
QOS_PARMS 0 or variable
QOS_RESERVED 0-7
FCH_CC_INCL 1
FCH_FRAME_SIZE 0 or 1
FOR_FCH_RC 0 or 5
REV_FCH_RC 0 or 5
DCCH_CC_INCL 1
DCCH_FRAME_SIZE 0 or 2
FOR_DCCH_RC 0 or 5
REV_DCCH_RC 0 or 5
3-635
3GPP2 C.S0005-A v6.0
FOR_SCH_CC_INCL 1
NUM_FOR_SCH 0 or 2
NUM_FOR_SCH occurrences of the following three-field
record
FOR_SCH_ID 2
FOR_SCH_MUX 16
SCH_CC_Type-specific field Variable (see 3.7.5.7.1)
REV_SCH_CC_INCL 1
NUM_REV_SCH 0 or 2
NUM_REV_SCH occurrences of the following three-field
record
REV_SCH_ID 2
REV_SCH_MUX 16
SCH_CC_Type-specific field Variable (see 3.7.5.7.1)
3 FOR_MUX_OPTION - Forward Fundamental and Dedicated Control Channel

4 multiplex option.
5 The mobile station shall set this field as follows:
6 For a Status Response Message, the mobile station shall

7 set this field to the number of the multiplex option for the
8 Forward Fundamental Channel, Forward Dedicated
9 Control Channel, or both, if both present (e.g., 1
10 corresponds to Multiplex Option 1).
11 For a Service Request Message and a Service Response
12 Message, the mobile station shall set this field to the
13 number of the multiplex option for the Forward
14 Fundamental Channel, Forward Dedicated Control
15 Channel, or both, if both present.
16 The base station shall set this field as follows:
3-636
3GPP2 C.S0005-A v6.0

2 Message, the base station shall set this field to the
3 number of the multiplex option for the Forward
4 Fundamental Channel, Forward Dedicated Control
6 For a Service Connect Message, General Handoff Direction
7 Message, and a Universal Handoff Direction Message, the
8 base station shall set this field to the number of multiplex
9 option for the Forward Fundamental Channel, Forward
10 Dedicated Control Channel, or both, if both present.
11 REV_MUX_OPTION - Reverse Fundamental and Dedicated Control Channel
12 multiplex option.

15 set this field to the number of the multiplex option for the
16 Reverse Fundamental Channel, Reverse Dedicated Control
17 Channel, or both, if both present(e.g., 1 corresponds to
18 Multiplex Option 1).
21 number of the multiplex option for the Reverse
22 Fundamental Channel, Reverse Dedicated Control

27 number of the multiplex option for the Reverse
28 Fundamental Channel, Reverse Dedicated Control
32 base station shall set this field to the number of the
33 multiplex option for the Reverse Fundamental Channel,
34 Reverse Dedicated Control Channel, or both, if both
35 present.
36 FOR_NUM_BITS - Set of number of bits per frame of the Forward Fundamental
37 Channel.
39 The mobile station shall use the Forward Fundamental

40 Channel transmission set of number of bits per frame
41 specified in 2.7.4.28 for the specified Forward Traffic
42 Channel multiplex option.
3-637
3GPP2 C.S0005-A v6.0

2 set the subfields corresponding to the Forward Traffic
3 Channel transmission set of number of bits per frame of
4 the current service configuration to ‘1’, and shall set the
5 remaining subfields to ‘0’. If FOR_MUX_OPTION is equal
6 to 1 or 2, the mobile station shall set RESERVED to
7 ‘0000’.
9 Message, the mobile station shall set the subfields
10 corresponding to the Forward Traffic Channel
11 transmission set of number of bits per frame of the
12 proposed service configuration to ‘1’, and shall set the
15 ‘0000’.
17 The base station shall set this field to the Forward

18 Fundamental Channel transmission set of number of bits
19 per framespecified in 2.7.4.28 for the specified Forward
20 Traffic Channel multiplex option.
21 For a Service Request Message or a Service Response
22 Message, the base station shall set the subfields
23 corresponding to the Forward Fundamental Channel
27 to 1 or 2, the base station shall set RESERVED to ‘0000’.
30 base station shall set the subfields corresponding to the
31 Forward Fundamental Channel transmission set of
32 number of bits per frame of the actual service
33 configuration to be used to ‘1’, and shall set the remaining
34 subfields to ‘0’. If FOR_MUX_OPTION is equal to 1 or 2,
35 the base station shall set RESERVED to ‘0000’.
36 REV_NUM_BITS - Set of number of bits per frameof the Reverse Fundamental
37 Channel.
39 The mobile station shall use the Reverse Fundamental

40 Channel transmission set of number of bits per frame
41 specified in 2.7.4.28 for the specified Reverse Traffic
42 Channel multiplex option.
3-638
3GPP2 C.S0005-A v6.0

2 set the subfields corresponding to the Reverse Traffic
3 Channel transmission set of number of bits per frame of
4 the current service configuration to ‘1’, and shall set the
5 remaining subfields to ‘0’. If REV_MUX_OPTION is equal
7 ‘0000’.
9 Message, the mobile station shall set the subfields
10 corresponding to the Reverse Traffic Channel transmission
11 set of number of bits per frame of the proposed service
12 configuration to ‘1’, and shall set the remaining subfields
13 to ‘0’. If REV_MUX_OPTION is equal to 1 or 2, the mobile
14 station shall set RESERVED to ‘0000’.
16 The base station shall set this field to the Reverse

17 Fundamental Channel transmission set of number of bits
18 per frame specified in 2.7.4.28 for the specified Reverse
19 Traffic Channel multiplex option.
21 Message, the base station shall set the subfields
22 corresponding to the Reverse Fundamental Channel
25 remaining subfields to ‘0’. If REV_MUX_OPTION is equal
26 to 1 or 2, the base station shall set RESERVED to ‘0000’.
29 base station shall set the subfields corresponding to the
30 Reverse Fundamental Channel transmission set of
31 number of bits per frame of the actual service
32 configuration to be used to ‘1’, and shall set the remaining
33 subfields to ‘0’. If REV_MUX_OPTION is equal to 1 or 2,
34 the base station shall set RESERVED to ‘0000’.
35 NUM_CON_REC - Number of service option connection records.

38 service option connection records included in the message.

41 service option connection records included in the message.
42 For a Status Response Message, the mobile station shall include one occurrence of the
43 following variable-length record for each service option connection of the current service
44 configuration. For a Service Request Message and a Service Response Message, the mobile
3-639
3GPP2 C.S0005-A v6.0
1 station shall include one occurrence of the following variable-length record for each service
2 option connection of the proposed service configuration.
3 For a Service Request Message or a Service Response Message, the base station shall
4 include one occurrence of the following variable-length record for each service option
5 connection of the proposed service configuration.
6 For a Service Connect Message, a General Handoff Direction Message, or a Universal Handoff
7 Direction Message, the base station shall include one occurrence of the following variable-
8 length record for each service option connection of the actual service configuration to be
9 used.
10 RECORD_LEN - Service option connection record length.

13 octets included in this service option connection record
14 including this field.
17 included in this service option connection record including
18 this field.
19 CON_REF - Service option connection reference.

22 set this field to the service option connection reference.

24 Message, if the service option connection is part of the
25 current service configuration, the mobile station shall set
26 this field to the service option connection reference;
27 otherwise, the mobile station shall set this field to
28 ‘00000000’.

31 Message: if the service option connection is part of the
32 current service configuration, the base station shall set
33 this field to the service option connection reference;
34 otherwise, the base station shall set this field to
35 ‘00000000’.
3-640
3GPP2 C.S0005-A v6.0

3 base station shall set this field to the service option
4 connection reference assigned to the service option
5 connection.

9 set this field to the service option in use with the service
10 option connection.
13 service option to be used with the service option
14 connection.
16 The base station shall set this field to the service option to
17 be used with the service option connection.
18 FOR_TRAFFIC - Forward Traffic Channel traffic type.

21 set this field to the FOR_TRAFFIC code shown in
22 Table 3.7.5.7-1 corresponding to the Forward Traffic
23 Channel traffic type in use with the service option
24 connection.
27 FOR_TRAFFIC code shown in Table 3.7.5.7-1
28 corresponding to the Forward Traffic Channel traffic type
29 to be used with the service option connection.
31 The base station shall set this field to the FOR_TRAFFIC

32 code shown in Table 3.7.5.7-1 corresponding to the
33 Forward Traffic Channel traffic type to be used with the
35
3-641
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.7-1. FOR_TRAFFIC Codes
FOR_TRAFFIC
0000 The service option connection does not

use Forward Traffic Channel traffic.
0001 The service option connection uses
primary traffic on the Forward Traffic
Channel.
secondary traffic on the Forward Traffic
Channel.
All other FOR_TRAFFIC codes are reserved.
3 REV_TRAFFIC - Reverse Traffic Channel traffic type.

6 set this field to the REV_TRAFFIC code shown in
7 Table 3.7.5.7-2 corresponding to the Reverse Traffic
8 Channel traffic type in use with the service option
9 connection.
12 REV_TRAFFIC code shown in Table 3.7.5.7-2
13 corresponding to the Reverse Traffic Channel traffic type
14 to be used with the service option connection.
16 The base station shall set this field to the REV_TRAFFIC

17 code shown in Table 3.7.5.7-2 corresponding to the
18 Reverse Traffic Channel traffic type to be used with the
20
3-642
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.7-2. REV_TRAFFIC Codes
REV_TRAFFIC
0000 The service option connection does not

use Reverse Traffic Channel traffic.
primary traffic on the Reverse Traffic
Channel.
secondary traffic on the Reverse Traffic
Channel.
All other REV_TRAFFIC codes are reserved.

2
3 UI_ENCRYPT_MODE - Encryption mode indicator for user information privacy.

6 set this field to indicate the current user information
7 encryption mode as shown in Table 3.7.5.7-3.
9 Message, the mobile station shall set this field to indicate
10 the proposed user information encryption mode as shown
11 in Table 3.7.5.7-3.

14 Message: the base station shall set this field to the
15 proposed user information encryption mode, as shown in
16 Table 3.7.5.7-3.
19 base station shall set this field to the assigned user
20 information encryption mode, as shown in Table 3.7.5.7-3.
3-643
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.7-3. User information Encryption Modes
UI_ENCRYPT_MODE
Field
(binary)
000 User information Encryption

disabled
001 User information Encryption with

ORYX encryption algorithm
enabled (not applicable to voice
service option). Encryption
procedures specified in the
service option standard shall be
performed.
010 User information Encryption

using the Rijndael encryption
algorithm. Encryption procedures
defined in 2.3.12.4.2.1 shall be
performed.
010011- 111 Reserved

5 set this field to the service reference identifier in use.
7 Message, the mobile station shall set this field as follows:
8 If the service option connection is a part of the current
9 service configuration, the mobile station shall set this field
10 to the service reference identifier in use.
11 If the service option connection is not a part of the current
12 service configuration, the mobile station shall perform the
13 following:
14 − If this service option connection request is initiated by
15 the base station, the mobile station shall set this field
16 to the value sent by the base station.
3-644
3GPP2 C.S0005-A v6.0

2 the mobile station, the mobile station shall perform the
3 following: if the service instance provides a service
4 reference identifier, the mobile station shall set this
5 field to the service reference identifier specified by the
6 service instance; otherwise, the mobile station shall set
7 this field to the smallest unused service reference
8 identifier number value between 1- and 6 inclusive.
10 For a Service Request Message, or a Service Response

11 Message, a Service Connect Message, a General Handoff
12 Direction Message, or a Universal Handoff Direction
13 Message, the base station shall set this field as follows:
14 If the service option connection is a part of the current
15 service configuration, the base station shall set this field
16 to the service reference identifier in use.
17 If the service option connection is not a part of the current
18 service configuration, the base station shall perform the
19 following:
21 the mobile station, the base station shall set this field
22 to the value sent by the mobile station.
24 the base station, the base station shall perform the
25 following: if the service instance provides a service
26 reference identifier, the base station shall set this field
27 to the service reference identifier specified by the
28 service instance; otherwise, the base station shall set
29 this field to the highest unused service reference
30 identifier number value between 1- and 6 inclusive.
33 base station shall set this field to the service reference
34 identifier to be used for the service instance corresponding
35 to this record.
36 RLP_INFO_INCL - RLP information included indicator.
38 The mobile station shall set this field to ‘1’ if the

39 RLP_BLOB field is included in this record; otherwise, it
3-645
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to ‘1’ if the RLP_BLOB
2 field is included in this record; otherwise, it shall set this
3 field to ‘0’.
4 RLP_BLOB_LEN - RLP information block of bits length.
6 If the RLP_INFO_INCL field is set to ‘0’, the mobile station

7 shall omit this field; otherwise, it shall include this field
9 The mobile station shall set this field to the size of the
10 RLP_BLOB field in integer number of octets.
12 If the RLP_INFO_INCL field is set to ‘0’, the base station

13 shall omit this field; otherwise, it shall include this field
15 The base station shall set this field to the size of the
16 RLP_BLOB field in integer number of octets.
17 RLP_BLOB - Radio Link Protocol block of bits.
19 If the RLP_INFO_INCL field is set to ‘0’, the mobile station


23 set this field to the Radio Link Protocol block of bits for
24 this service option connection.
25 For a Service Request Message or Service Response

27 proposed Radio Link Protocol block of bits for this service
28 option connection, and shall add ‘0’ bits to the end of the
29 field as needed in order to make the length of this field
30 equal to an integer number of octets.
32 If the RLP_INFO_INCL field is set to ‘0’, the base station

33 shall omit this field; otherwise, the base station shall
3-646
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the Radio Link
2 Protocol block of bits for this service option connection,
3 and shall add ‘0’ bits to the end of the field as needed in
4 order to make the length of this field equal to an integer
5 number of octets.
6 QOS_PARMS_INCL - Presence indicator for the QoS parameters.
8 The mobile station shall set this field to ‘1’, if QOS_PARMS

9 field is included in the record; otherwise the base station
12 The base station shall set this field to ‘1’, if QOS_PARMS

13 field is included in the record; otherwise, the base station
15 QOS_PARMS_LEN - Length of the block of QoS parameters.
17 If QOS_PARMS_INCL is set to ‘1’, the mobile station shall

18 set this field to the combined length in octets, of the
20 QOS_RESERVED field; otherwise, the mobile station shall
21 omit this field.
23 If QOS_PARMS_INCL is set to ‘1’, the base station shall set

24 this field to the combined length in octets, of the
26 QOS_RESERVED field; otherwise, the base station shall
27 omit this field.
28 QOS_PARMS - QoS parameters block.

31 include this field in the record as follows:
33 set this field to the set of QoS parameters configured for
34 this service option connection.

36 Message, the mobile station shall set this field and set it to
37 the set of QoS parameters requested for the respective
38 connection.
3-647
3GPP2 C.S0005-A v6.0
2 If QOS_PARMS_INCL is set to ‘1’, the base station shall

3 include this field in the record and set it to the set of QoS
4 parameters requested or required for the respective
5 connection.
6 QOS_RESERVED - Padding bits.

9 include the minimum number of ‘0’ bits necessary to
10 ensure that the combined length of the QOS_PARMS field
11 and of this field is an integer number of octets; otherwise,
12 the mobile station shall omit this field.
14 If QOS_PARMS_INCL is set to ‘1’, the base station shall

15 include the minimum number of ‘0’ bits necessary to
16 ensure that the combined length of the QOS_PARMS field
17 and of this field is an integer number of octets; otherwise,
21 The mobile station shall add reserved bits as needed in

22 order to make the length of the entire record equal to an
23 integer number of octets. The mobile station shall set
26 The base station shall add reserved bits as needed in order

27 to make the length of this record equal to an integer
28 number of octets. The base station shall set these bits to
29 ‘0’.
30 FCH_CC_INCL - Channel configuration for the Fundamental Channel included

31 indicator.
33 The mobile station shall set this field to ‘1’, if Fundamental

34 Channel Configuration information is included in the
35 record; otherwise, the mobile station shall set this field to
36 ‘0’.
3-648
3GPP2 C.S0005-A v6.0
2 The base station shall set this field to ‘1’, if the channel
3 configuration information for the Fundamental Channel is
4 included in this Service Configuration Record; otherwise,
6 FCH_FRAME_SIZE - Fundamental Channel frame size supported indicator.
8 If FCH_CC_INCL field is set to ‘1’, the mobile station shall

9 include this field and set it as described below; otherwise,
12 set this field to ‘1’, if the 5ms frame size is used in the
13 Forward and Reverse Fundamental Channel, in addition to
14 20ms frame, for the current service configuration;
17 Message, the mobile station shall set this field to ‘1’ to
18 propose that the 5 ms frame size in addition to the 20 ms
19 frame size is used for the proposed service configuration;
20 otherwise the mobile station shall set this field to ‘0’
22 If the FCH_CC_INCL field is set to ‘0’, the base station

25 The base station shall set this field to ‘1’ if the service
26 configuration includes the use of 5 ms frame size in
27 addition to 20ms frame size for the Forward and Reverse
28 Fundamental Channel; otherwise, the base station shall
30 FOR_FCH_RC - Forward Fundamental Channel Radio Configuration.

36 set this field to the Forward Fundamental Channel Radio
37 Configuration for the current service configuration.
40 Forward Fundamental Channel Radio Configuration for
41 the proposed service configuration.
42 (see [2] Table 3.1.3.1-1)
3-649
3GPP2 C.S0005-A v6.0

7 Forward Fundamental Channel Radio Configuration (see
8 Table 3.1.3.1-1 of [2]) in the proposed service
9 configuration.
10 For a Service Connect Message, a General Handoff
12 Message, the base station shall set this field to the actual
13 Forward Fundamental Channel Radio Configuration to be
14 used.
15 REV_FCH_RC - Reverse Fundamental Channel Radio Configuration.

21 set field to the Reverse Fundamental Channel Radio
22 Configuration for the current service configuration.
25 Reverse Fundamental Channel Radio Configuration for the
26 proposed service configuration.
27 (see [2] Table 2.1.3.1-1)

34 Reverse Fundamental Channel Radio Configuration (see
35 Table 2.1.3.1-1 of [2]) in the proposed service
36 configuration.
40 Reverse Fundamental Channel Radio Configuration to be
41 used.
42 DCCH_CC_INCL - Channel configuration for the Dedicated Control Channel
3-650
3GPP2 C.S0005-A v6.0
2 The mobile station shall set this field to ‘1’, if DCCH

3 channel configuration information is included in this
4 record; otherwise, the mobile station shall set this field to
5 ‘0’.
7 The base station shall set this field to ‘1’, if channel

8 configuration information for the Dedicated Control
9 Channel is included in this Service Configuration Record;
11 DCCH_FRAME_SIZE - Dedicated Control Channel frame size.
13 If DCCH_CC_INCL field is set to ‘1’, the mobile station

17 set this field to the frame size, as defined in Table 3.7.5.7-
18 4, for the current service configuration.

21 frame size, as defined in Table 3.7.5.7-4, for the proposed
24 If the DCCH_CC_INCL field is set to ‘0’, the base station

26 include this field and set it according to the Table 3.7.5.7-
27 4 as follows:
31 Dedicated Control Channel frame size(s) to be used in the
35 Dedicated Control Channel frame size for the proposed
36 service configuration message.
37
3-651
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.7-4. DCCH Frame Size
DCCH_FRAME_SIZE
00 Reserved
11 Both 5 ms and 20 ms frame sizes
3 FOR_DCCH_RC - Forward Dedicated Control Channel Radio Configuration.

9 set this field to the Forward Dedicated Control Channel
10 Radio Configuration for the current service configuration.

13 forward Dedicated Control Channel Radio Configuration
14 (see [2] Table 3.1.3.1-1) for the proposed service
15 configuration.

23 Forward Dedicated Control Channel Radio Configuration
24 to be used (see Table 3.1.3.1-1 of [2]).
27 Forward Dedicated Control Channel Radio Configuration
28 for the proposed service configuration.
29 REV_DCCH_RC - Reverse Dedicated Control Channel Radio Configuration.

3-652
3GPP2 C.S0005-A v6.0

2 set this field to the Reverse Dedicated Control Channel
3 Radio Configuration (see Table 2.1.3.1-1 of [2]) for the
7 Reverse Dedicated Control Channel Radio Configuration
8 for the proposed service configuration.

16 Reverse Dedicated Control Channel Radio Configuration to
17 be used (see Table 2.1.3.1-1 of [2]).
19 Message, the base station shall set this field to the reverse
20 Dedicated Control Channel Radio Configuration for the
21 proposed service configuration.
22 FOR_SCH-
23 _CC_INCL - Channel configuration for the Forward Suppemental Channel
26 The mobile station shall set this field to ‘1’, if the Forward
27 Supplemental Channel Configuration information is
28 included; otherwise, the mobile station shall set this field
29 to ‘0’.
31 The base station shall set this field to ‘1’, if the channel
32 configuration information for the forward Supplemental
33 Channel is included in this Service Configuration Record;
35 NUM_FOR_SCH - Number of Forward Supplemental Channels.
37 If FOR_SCH_CC_INCL field is set to ‘1’, the mobile station

38 shall include this field and set it as describe below;
3-653
3GPP2 C.S0005-A v6.0

2 set this field to the number of Forward Supplemental
3 Channels for the current service configuration and include
4 one occurrence of the following three-field SCH record for
5 each Supplemental Channel Configuration.
8 number of Forward Supplemental Channels for the
9 proposed service configuration and include one occurrence
10 of the following three-field SCH record for each
11 Supplemental Channel Configuration.
13 If the FOR_SCH_CC_INCL field is set to ‘0’, the base

14 station shall omit this field; otherwise, the base station
15 shall set this field to the number of Forward Supplemental
16 Channels associated with this service configuration.
17 If the NUM_FOR_SCH field is present and is set to any value other than ‘00’, the base
18 station shall include one occurrence of the following three-field record for each Forward
19 Supplemental Channel included in this record:
20 FOR_SCH_ID - Forward Supplemental Channel Identification
22 The mobile station shall set this field to the identification

23 of the Supplemental Channel included in this Forward
24 Supplemental Channel Configuration record.

26 Channel identifier, shown in Table 3.7.5.7-5.
27 Table 3.7.5.7-5. SCH Identifier
FOR_SCH_ID
Description
REV_SCH_ID
(binary)
00 Supplemental Channel 0
01 Supplemental Channel 1
10-11 Reserved
33
34 FOR_SCH_MUX - Forward Supplemental Channel Multiplex Option.
3-654
3GPP2 C.S0005-A v6.0
2 The mobile station shall set this field to the Multiplex

3 Option associated with the maximum data rate for this
4 Forward SCH Supplemental Channel (see [3]).
6 The base station shall set this field to the Multiplex Option
7 associated with the maximum data rate for this Forward
8 Supplemental Channel (see [3]).
9 SCH_CC-
10 _Type-specific field - Supplemental Channel Configuration Information.
12 The mobile station shall set this field to the subfields of

13 the Channel Configuration record defined in 3.7.5.7.1, for
14 this Forward Supplemental Channel included in the
17 The base station shall set this field as defined in 3.7.5.7.1

18 for this Forward Supplemental Channel.
19 REV_SCH_CC_INCL - Channel configuration for the Reverse Supplemental Channel
22 The mobile station shall set this field to ‘1’, if the Reverse
23 Supplemental Channel Configuration information is
24 included; otherwise, the mobile station shall set this field
25 to ‘0’.
27 The base station shall set this field to ‘1’ if the channel
28 configuration information for the Rreverse Supplemental
29 Channel is included in this service configuration record;
31 NUM_REV_SCH - Number of Reverse Supplemental Channels.
33 If REV_SCH_CC_INCL field is set to ‘1’, the mobile station

3-655
3GPP2 C.S0005-A v6.0

2 set this field to the number of Reverse Supplemental
3 Channels for the current service configuration and include
4 one occurrence of the following three-field record for each
5 reverse Supplemental Channel Configuration.
8 number of Reverse Supplemental Channels for the
9 proposed service configuration and include one occurrence
10 of the following three-field record for each reverse
11 Supplemental Channel Configuration.
13 If the REV_SCH_CC_INCL field is set to ‘0’, the base

14 station shall omit this field; otherwise, the base station
15 shall set this field to the number of Reverse Supplemental
16 Channels associated with this service configuration.
17 If the NUM_REV_SCH field is present and is set to any value other than ‘00’, the base
18 station shall include one occurrence of the following three-field record for each Reverse
20 REV_SCH_ID - Reverse Supplemental Channel Identification
22 The mobile station shall set this field to the identifier of

23 the Supplemental Channel included in this Reverse
24 Supplemental Channel Configuration record.

29 Reverse Supplemental Channel pertaining to this record.
32 REV_SCH_MUX - Reverse Supplemental Channel Multiplex Option
34 The mobile station shall set this field to the Multiplex

35 Option associated with the maximum data rate for this
36 Reverse SCH (see [3]).
3-656
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the Multiplex Option
2 associated with the maximum data rate for this Reverse
3 Supplemental Channel (see [3]).
4 SCH_CC-
5 _Type-specific field - Supplemental Channel Configuration Information.
7 The mobile station shall set this field to the subfields of

8 the Channel Configuration record defined in 3.7.5.7.1, for
9 this Reverse Supplemental Channel included in the service
10 configuration.
12 The base station shall set this field as defined in 3.7.5.7.1

13 for this Reverse Supplemental Channel.
16 The mobile station shall add reserved bits as needed in

17 order to make the length of the entire information record
18 equal to an integer number of octets. The mobile station
19 shall set these bits to ‘0’.
21 The base station shall add reserved bits as needed in order

22 to make the length of the entire message equal to an
23 integer number of octets. The base station shall set these
24 bits to ‘0’.
3-657
3GPP2 C.S0005-A v6.0
1 3.7.5.7.1 Channel Configuration for the Supplemental Channel
2 The channel configuration information for the Supplemental Channel consists of the
3 following subfields:
Subfields Length (bits)
SCH_REC_LEN 4
SCH_RC 5
CODING 1
FRAME_40_USED 1
FRAME_80_USED 1
MAX_RATE 4
6 SCH_REC_LEN - Supplemental Channel channel configuration record length.

7 The mobile station or base station shall set this field to the
8 number of octets included in this Supplemental Channel
9 channel configuration record including this SCH_REC_LEN
10 field.
11 SCH_RC - Supplemental Channel Radio Configuration.
12 The mobile station or base station shall set this field to the
13 Radio Configuration for this Supplemental Channel. Radio
14 Configurations are defined Table 3.1.3.1-1 of [2] for the
15 Forward Supplemental Channel and Table 2.1.3.1-1 of [2] for
16 the Reverse Supplemental Channel.
17 CODING - Coding type.
18 The mobile station or base station shall set this field to ‘1’ if
19 the mobile station or the base station is to use Convolutional
20 Coding when the number of channel bits per frame is less
21 than 360 and Turbo Coding when the number of channel bits
22 per frame is equal to or greater than 360. The mobile station
23 or base station shall set this field to ‘0’ if the mobile station or
24 the base station uses Convolution Coding for all block sizes.
25 FRAME_40_USED - 40ms frame used indicator
27 40ms frame is used; otherwise, the mobile station or base
29 If a f-dtch logical channel corresponding to the same sr_id is
30 mapped to both forward Supplemental Channels 0 and 1,
31 then the mobile station or base station shall specify the same
32 frame length for both forward Supplemental Channels 0 and
33 1.
3-658
3GPP2 C.S0005-A v6.0
1 If a r-dtch logical channel corresponding to the same sr_id is

2 mapped to both reverse Supplemental Channels 0 and 1, then
3 the mobile station or base station shall specify the same frame
4 length for both forward Supplemental Channels 0 and 1.
5 The base station shall not set both FRAME_40_USED and
6 FRAME_80_USED fields set to ‘1’.
8 FRAME_80_USED - 80ms frame used indicator.

10 80ms frame is to be used; otherwise, the mobile station or
12 If a f-dtch logical channel corresponding to the same sr_id is
13 mapped to both forward Supplemental Channels 0 and 1,
14 then the mobile station or base station shall specify the same
15 frame length for both forward Supplemental Channels 0 and
16 1.
17 If a r-dtch logical channel corresponding to the same sr_id is
18 mapped to both reverse Supplemental Channels 0 and 1, then
19 the mobile station or base station shall specify the same frame
20 length for both reverse Supplemental Channels 0 and 1.
21 Then the base station shall not set both FRAME_40_USED
22 and FRAME_80_USED fields set to ‘1’.
23 MAX_RATE - Maximum supplemental channel rate
24 The mobile station or base station shall set this field according
25 to Table 2.7.4.27.3-2 to indicate the maximum forward or
26 reverse supplemental channel data rate supported.
3-659
3GPP2 C.S0005-A v6.0
1 3.7.5.8 Called Party Subaddress
2 This information record identifies the called party subaddress.
EXTENSION_BIT 1
SUBADDRESS_TYPE 3
RESERVED 3
CHARi 8
5 EXTENSION_BIT - The extension bit.

7 SUBADDRESS_TYPE - Type of subaddress.
11 Section 4.5.8.
12 ODD/EVEN_INDICATOR - The indicator of odd/even bits.
16 [7], Section 4.5.8. It is only used when the type of subaddress
17 is “User specified” and the coding is BCD.
22 each character in the called party subaddress.
26 8348 AD2 [35].
3-660
3GPP2 C.S0005-A v6.0
1 3.7.5.9 Calling Party Subaddress
2 This information record identifies the calling party subaddress.
EXTENSION_BIT 1
SUBADDRESS_TYPE 3
RESERVED 3
CHARi 8

11 Section 4.5.10.
12 ODD/EVEN INDICATOR - The indicator of odd/even bits.
22 each character in the calling party subaddress.
26 8348 AD2 [35].
3-661
3GPP2 C.S0005-A v6.0
1 3.7.5.10 Connected Subaddress
EXTENSION_BIT 1
SUBADDRESS_TYPE 3
RESERVED 3
CHARi 8

11 Section 4.5.14.
12 ODD/EVEN INDICATOR - The indicator of odd/even bits.
22 each character in the connected subaddress.
26 8348 AD2 [35].
3-662
3GPP2 C.S0005-A v6.0
1 3.7.5.11 Redirecting Number
2 This information record identifies the Redirecting Number.
EXTENSION_BIT_1 1
NUMBER_TYPE 3
NUMBER_PLAN 4
EXTENSION_BIT_2 0 or 1
PI 0 or 2
RESERVED 0 or 3
SI 0 or 2
EXTENSION_BIT_3 0 or 1
RESERVED 0 or 3
REDIRECTION_REASON 0 or 4
CHARi 8
5 EXTENSION_BIT_1 - The extension bit.

6 If the PI and SI are included in this record, the base station
12 of the redirecting number, as defined in ANSI T1.625 §6.1.3.7
13 [34].
17 numbering plan used for the redirecting number, as defined in
18 ANSI T1.625 §6.1.3.7[34].
20 If the EXTENSION_BIT_1 is set to ‘0’ and
21 REDIRECTION_REASON is included in this record, the base
22 station shall set this field to ‘0’. If the EXTENSION_BIT_1 is
23 set to ‘0’ and REDIRECTION_REASON is not included in this
24 record, the base station shall set this field to ‘1’. If the
25 EXTENSION_BIT_1 is set to ‘1’, the base station shall omit
26 this field.
3-663
3GPP2 C.S0005-A v6.0
2 This field indicates whether or not the redirecting number
3 should be displayed.
4 if the EXTENSION_BIT_1 is set to ‘0’, the base station shall set
5 this field to the PI value shown in Table 2.7.4.4-1
6 corresponding to the presentation indicator, as defined in
7 ANSI T1.625 §6.1.3.7[34]; otherwise, the base station shall
8 omit this field.
10 If the EXTENSION_BIT_1 is set to ‘0’, the base station shall set
11 this field to ‘000’; otherwise, the base station shall omit this
12 field.
14 This field indicates how the redirecting number was screened.
16 this field to the SI value shown in Table 2.7.4.4-2
17 corresponding to the screening indicator value, as defined in
18 ANSI T1.625 6.1.3.7[34]; otherwise, the base station shall
19 omit this field.
23 field.
27 field.
28 REDIRECTION_REASON - The reason for redirection.
30 this field to the REDIRECTION_REASON value shown in Table
31 3.7.5.5.11-1 corresponding to the redirection reason, as
32 defined in ANSI T1.625 6.1.3.7 [34]; otherwise, the base
34
3-664
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.11-1. Redirection Reason
REDIRECTION-
REASON
Unknown 0000
Call forwarding busy or called DTE busy 0001
Call forwarding no reply (circuit-mode 0010
only)
Called DTE out of order (packet-mode 1001
only)
Call forwarding by the called DTE 1010
(packet-mode only)
Call forwarding unconditional or 1111
Systematic call redirection
Reserved others
4 The base stations shall include one occurrence of this field for
5 each character in the Redirecting Number. The base station
3-665
3GPP2 C.S0005-A v6.0
1 3.7.5.12 Redirecting Subaddress
EXTENSION_BIT 1
SUBADDRESS_TYPE 3
RESERVED 3
CHARi 8

10 corresponding to the type of the subaddress, as defined in
11 ANSI T1.625 §6.1.3.8[34].
12 ODD/EVEN INDICATOR - The indicator of odd /even bits.
16 ANSI T1.625 §6.1.3.8[34]. It is only used when the type of
22 each character in the redirecting subaddress.
26 8348 AD2 [35].
3-666
3GPP2 C.S0005-A v6.0
1 3.7.5.13 Meter Pulses
2 This information record identifies the number of meter pulses and frequency of the alert
3 tone.
PULSE_FREQUENCY 11
PULSE_ON_TIME 8
PULSE_OFF_TIME 8
PULSE_COUNT 4
RESERVED 1
6 PULSE_FREQUENCY - Pulse frequency.

7 The base station shall set this field to the frequency of the
8 alert signals in units of 10 Hz or to zero to indicate that line
9 polarity control is to be used. If this field is set to zero, the
10 PULSE_ON_TIME and PULSE_OFF_TIME shall be the period of
11 line polarity reversal and normal line polarity, respectively.
12 PULSE_ON_TIME - Pulse on time.
13 The base station shall set this field to the period of the meter
14 pulses in units of 5 ms.
15 PULSE_OFF_TIME - Pulse off time.
16 The base station shall set this field to the period of the inter-
17 pulse spacing in units of 5 ms.
18 PULSE_COUNT - Pulse count.
19 The base station shall set this field to the number of meter
20 pulses.
3-667
3GPP2 C.S0005-A v6.0
1 3.7.5.14 Parametric Alerting
2 This information record allows the network to convey information to a user by means of
3 programmable alerting signals.
CADENCE_COUNT 8
NUM_GROUPS 4
NUM_GROUPS occurrences of the following record:

AMPLITUDE 8
FREQ_1 10
FREQ_2 10
ON_TIME 8
OFF_TIME 8
REPEAT 4
DELAY 8
CADENCE_TYPE 2
RESERVED 2
6 CADENCE_COUNT - Cadence count.

7 The base station shall set this field to the number of times the
8 cadence of tone groups will be generated between 0x01 and
9 0xFE. The base station shall set this field to 0x00 to indicate
10 that the mobile station should end alert tone generation. The
11 base station shall set this field to 0xFF to indicate that the
12 cadence will repeat indefinitely.
13 NUM_GROUPS - Number of groups.
14 The base station shall set this field to the number of groups.
15
16 AMPLITUDE - Amplitude.
17 The base station shall set this field to the amplitude level of
18 the tone group in units of -1 dBm.
19 FREQ_1 - Tone frequency 1.
20 The base station shall set this field to the first frequency of
21 the tone group in units of 5 Hz.
22 FREQ_2 - Tone frequency 2.
3-668
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the second frequency of
2 the tone group in units of 5 Hz. Setting this field to zero
3 creates a single frequency tone.
4 ON_TIME - On time.
5 The base station shall set this field to the duration of the tone
6 group in units of 50 ms.
7 OFF_TIME - Off time.
8 The base station shall set this field to the duration of the
9 spacing between tones in units of 50 ms.
10 REPEAT - Repeat.
11 The base station shall set this field to the number of times the
12 tone group should repeat. The base station shall set this field
13 to 0xFF to indicate that the tone group will repeat indefinitely.
14 DELAY - Delay.
15 The base station shall set this field to the length of time before
16 the next tone group begins in units of 50 ms.
17 CADENCE_TYPE - Parametric Alerting cadence type.
18 The base station shall set this field to indicate that the alert
19 should be conveyed to the user as specified in Table 3.7.5.14.
20
21 Table 3.7.5.14. Cadence Types
CADENCE_TYPE Meaning
00 Not specified
01 Acoustic earpiece or similar
device
10 Device other than acoustic
earpiece or similar device (Eg.
Ringer)
11 Reserved
3-669
3GPP2 C.S0005-A v6.0
1 3.7.5.15 Line Control
2 This information record allows the network to convey line control information.
POLARITY_INCLUDED 1
TOGGLE_MODE 0 or 1
REVERSE_POLARITY 0 or 1
POWER_DENIAL_TIME 8
5 POLARITY_INCLUDED - Polarity parameter included.

6 If the mobile station is to change the line polarity, the base
9 TOGGLE_MODE - If POLARITY_INCLUDED is set to ‘1’, the base station shall
10 include this field and set it to ‘1’ to toggle the line polarity or
11 to ‘0’ to set the polarity to the absolute value indicated in the
12 REVERSE_POLARITY field.
13 REVERSE_POLARITY - Reverse polarity.
14 If POLARITY_INCLUDED is set to ‘1’ and TOGGLE_MODE is
15 equal to ‘0’, the base station shall include this field and set it
16 to ‘1’ to reverse the tip and ring polarity or to ‘0’ to use normal
17 polarity. If POLARITY_INCLUDED is set to ‘1’ and
18 TOGGLE_MODE is set to ‘1’, the base station shall include
19 this field and set it to ‘0’; otherwise, the base station shall
20 omit this field.
21 POWER_DENIAL_TIME - Power denial timeout.
22 The base station shall include this field and set it to the
23 duration of the power denial in increments of 5 ms.
26 make the length of the entire message equal to an integer
3-670
3GPP2 C.S0005-A v6.0
1 3.7.5.16 Extended Display
2 This information record allows the network to supply supplementary service display
3 information that may be displayed by the mobile station.
EXT_DISPLAY_IND 1
DISPLAY_TYPE 7
DISPLAY_TAG 8
DISPLAY_LEN 8
DISPLAY_LEN occurrences of the following field if the
DISPLAY_TAG field is not equal to ‘10000000’ or
‘10000001’:
CHARi 8
6 EXT_DISPLAY_IND - The indicator of Extended Display Information record.

8 DISPLAY_TYPE - The type of display.
9 The base station shall set this field to the DISPLAY_TYPE
10 value shown in Table 3.7.5.16-1 corresponding to the type of
11 display, as defined in [8] Annex D.
12
13 Table 3.7.5.16-1. Display Type
DISPLAY_TYPE
Description
(binary)
Normal 0000000
All other DISPLAY_TYPE values are reserved.
14
15 DISPLAY_TAG - The indicator of the display information.

16 There are three types of display tags: mandatory control tags
17 (Blank and Skip), display text tags, and optional control tags,
18 see [8] Annex D.
19 The base station shall set this field to the DISPLAY_TAG value
20 shown in Table 3.7.5.16-2 corresponding to the type of
21 information contained in the following CHARi field, as defined
22 in [8] Annex D.
23
3-671
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.16-2. Mandatory Control Tags and

2 Display Text Tags
DISPLAY_TAG
Description
(binary)
Blank 10000000
Skip 10000001
Continuation 10000010
Called Address 10000011
Cause 10000100
Progress Indicator 10000101
Notification Indicator 10000110
Prompt 10000111
Accumulated Digits 10001000
Status 10001001
Inband 10001010
Calling Address 10001011
Reason 10001100
Calling Party Name 10001101
Called Party Name 10001110
Original Called Name 10001111
Redirecting Name 10010000
Connected Name 10010001
Originating Restrictions 10010010
Date & Time of Day 10010011
Call Appearance ID 10010100
Feature Address 10010101
Redirection Name 10010110
Redirection Number 10010111
Redirecting Number 10011000
Original Called Number 10011001
Connected Number 10011010
Text (e.g., ASCII) 10011110
3-672
3GPP2 C.S0005-A v6.0
1 DISPLAY_LEN - The display length.

2 The base station shall set this field to the number of octets of
3 display text. See [8] Annex D.
5 The base station shall include DISPLAY_LEN occurrences of
6 this field, one for each character to be displayed, except for
7 blank and skip. The base station shall set each occurrence of
8 this field to the ASCII representation corresponding to the
9 character entered, as specified in [9], with the most significant
10 bit set to ‘0’.
3-673
3GPP2 C.S0005-A v6.0
1 3.7.5.17 Extended Record Type - International
2 The use of this record type is country-specific. The first ten bits of the type-specific fields
3 shall include the Mobile Country Code (MCC) associated with the national standards
4 organization administering the use of the record type. Encoding of the MCC shall be as
5 specified in 2.3.1.3. The remaining six bits of the first two octets of the type-specific fields
6 shall be used to specify the country-specific record type.
3-674
3GPP2 C.S0005-A v6.0
1 3.7.5.18 Reserved
3-675
3GPP2 C.S0005-A v6.0
1 3.7.5.19 Reserved
3-676
3GPP2 C.S0005-A v6.0
1 3.7.5.20 Non-Negotiable Service Configuration

2 This record is included in a Service Connect Message to specify the non-negotiable service
3 configuration parameters to be used by the mobile station. This record can be included in a
4 General Handoff Direction Message or a Universal Handoff Direction Message to specify the
5 non-negotiable service configuration parameters to be used by the mobile station.
Type Specific Field Length (bits)

FPC_INCL 1
FPC_PRI_CHAN 0 or 1
FPC_MODE 0 or 3
FPC_OLPC_FCH_INCL 0 or 1
FPC_FCH_FER 0 or 5
FPC_FCH_MIN_SETPT 0 or 8
FPC_FCH_MAX_SETPT 0 or 8
FPC_OLPC_DCCH_INCL 0 or 1
FPC_DCCH_FER 0 or 5
FPC_DCCH_MIN_SETPT 0 or 8
FPC_DCCH_MAX_SETPT 0 or 8
GATING_RATE_INCL 1
FOR_SCH_INCL 1
NUM_FOR_SCH 0 or 2
If FOR_SCH_INCL = ‘1’, include NUM_FOR_SCH occurrences
of the following two-field record
FOR_SCH_ID 2
FOR_SCH_FRAME_OFFSET 2
3-677
3GPP2 C.S0005-A v6.0

REV_SCH_INCL 1
NUM_REV_SCH 0 or 2
If REV_SCH_INCL = ‘1’, include NUM_REV_SCH occurrences
of the following two-field record
REV_SCH_ID 2
REV_SCH_FRAME_OFFSET 2
LPM_IND 2
NUM_LPM_ENTRIES 0 or 4
If LPM_IND = ‘01’, include NUM_LPM_ENTRIES occurrences
of the following six-field record:
SR_ID 3
LOGICAL_RESOURCE 4
PHYSICAL_RESOURCE 4
FORWARD_FLAG 1
REVERSE_FLAG 1
PRIORITY 4
NUM_REC 3
NUM_REC occurrences of the following variable-length
record:
RECORD_LEN 8
SR_ID 3
SDB_SO_OMIT 1
3-678
3GPP2 C.S0005-A v6.0

USE_FLEX_NUM_BITS 1
USE_OLD_FLEX_NUM_BITS_TABL 0 or 1
ES_INCL
NUM_BITS_TABLES_COUNT 0 or 3
If USE_FLEX_NUM_BITS is equal to '1' and
NUM_BITS_TABLES_INCL is equal to ‘1’, then include
NUM_BITS_TABLES_COUNT+1 occurrences of the following
record
NUM_BITS_TABLE_ID 4
NUM_RECS 4
If USE_FLEX_NUM_BITS is equal to '1', then NUM_RECS +1
occurrences of the following record
NUM_BITS_IDX 4
NUM_BITS 16
CRC_LEN_IDX 3
USE_VAR_RATE 1
USE_OLD_VAR_TABLES_INCL 0 or 1
VAR_RATE_TABLES_COUNT 0 or 3
If USE_VAR_RATE is equal to ‘1’ and VAR_TABLES_INCL is
equal to ‘1’, then include VAR_RATE_TABLES_COUNT+1
occurrences of the following record
VAR_RATE_TABLE_ID 3
NUM_RECS 4
For each of the above record, Iif USE_VAR_RATENUM_BITS
is equal to '1', then include NUM_RECS +1 occurrences of
the following record
NUM_BITS_IDX 4
MASK NUM_BITS_IDX
If USE_FLEX_NUM_BITS is equal to ‘1’, include the following
fields
USE_OLD_FLEX_MAPPING 1
FSCH0_NBIT_TABLE_ID 0 or 4
3-679
3GPP2 C.S0005-A v6.0
3-680
3GPP2 C.S0005-A v6.0

RSCH0_NBIT_TABLE_ID 0 or 4
FSCH1_NBIT_TABLE_ID 0 or 4
RSCH1_NBIT_TABLE_ID 0 or 4
FFCH_NBIT_TABLE_ID 0 or 4
RFCH_NBIT_TABLE_ID 0 or 4
FDCCH_NBIT_TABLE_ID 0 or 4
FDCCH_NBITS_IDX 0 or 4
RDCCH_NBIT_TABLE_ID 0 or 4
RDCCH_NBITS_IDX 0 or 4
If USE_VAR_RATE is equal to ‘1’, include the following fields
USE_OLD_VAR_MAPPING 1
FSCH0_VAR_TABLE_ID 0 or 3
RSCH0_VAR_TABLE_ID 0 or 3
FSCH1_VAR_TABLE_ID 0 or 3
RSCH1_VAR_TABLE_ID 0 or 3
R_INC_RATE_ALLOWED 0 or 1
F_INC_RATE_ALLOWED 0 or 1
LTU_INFO_INCL 1
USE_OLD_LTU_TABLES_INCL 0 or 1
If LTU_INFO_INCL is equal to ‘1’ and
USE_OLD_LTU_TABLES_INCL is equal to ‘10’, then include
the following fields related to the LTU Size Table shall be
included
NUM_LTU_TABLES 0 or 2
Include NUM_LTU_TABLES + 1 instances occurrences of the
following records
LTU_TABLE_ID 3
3-681
3GPP2 C.S0005-A v6.0

NUM_ROWS 4
For each occurrence of the above record, include Include
NUM_ROWS + 1 instances occurrences of the following
records
NBITS_IDX 4
NUM_LTUS_LEN 164
USE_OLD_LTU_MAPPING 0 or 1
FSCH0_LTU_TAB_ID 0 or 3
RSCH0_LTU_TAB_ID 0 or 3
FSCH1_LTU_TAB_ID 0 or 3
RSCH1_LTU_TAB_ID 0 or 3
If USE_FLEX_NUM_BITS is equal to ‘1’ and at least one of
FFCH_NBIT_TABLE_ID, RFCH_NBIT_TABLE_ID,
FDCCH_NBIT_TABLE_ID, or RDCCH_NBIT_TABLE_ID is not
equal to ‘0000’, then include the following fields
PARTITION_TABLES_INFO_INCL 0 or 1
USE_OLD_PARTITION_TABLES_IN 0 or 1
CL
NUM_PARTITION_TABLES 0 or 2
Include NUM_PARTITION_TABLES + 1 instances occurences
of the following records
PARTITION_TABLE_ID 3
NUM_ROWS 5
For each occurrence of the above record, include Include
NUM_ROWS + 1 instances occurences of the following
records
CATEGORY 5
MUX_HEADER_LEN 3
MUX_HEADER MUX_HEADER_LEN
3-682
3GPP2 C.S0005-A v6.0

NUM_PARTITIONS 3
Include NUM_PARTITIONS + 1 instances occurrences of the
following record
SR_ID 3
SRV_NUM_BITS 9
USE_OLD_PART_MAPPING 0 or 1
FFCH_PART_TAB_ID 0 or 3
RFCH_PART_TAB_ID 0 or 3
FDCCH_PART_TAB_ID 0 or 3
RDCCH_PART_TAB_ID 0 or 3
5 FPC_INCL - Forward power control information included indicator.

6 The base station shall set this field to ‘1’ if the forward power
7 control information parameters are included in this record;
10 If the FPC_INCL field is set to ‘0’, the base station shall omit
16 is to multiplex the Power Control Subchannel on Forward
17 Fundamental Channel; the base station shall set this field to
21 Control Subchannel on Forward Dedicated Control Channel.
22 If only Fundamental Channel is assigned, the base station
23 shall set this field to ‘0’. If only the Dedicated Control
24 Channel is assigned, the base station shall set this field to ‘1’.
25 FPC_MODE - Forward Power Control operation mode indicator.
3-683
3GPP2 C.S0005-A v6.0
4 The base station shall set this field to the value of the forward
5 power control operation mode (see [2]).
6 FPC_OLPC_FCH_INCL - Fundamental Channel Outer Loop Power Control parameter
11 If the forward link Fundamental Channel outer loop power
12 control parameters are included in this record, the base
15 FPC_FCH_FER - Fundamental Channel target Frame Error Rate.
18 the Forward Fundamental Channel, as specified in Table
20 field.
23 station shall set this field to minimum Fundamental Channel
24 Outer Loop Eb/Nt setpoint, in units of 0.125dB; otherwise,
27 If FPC_OLPC_FCH_INCL is set to ‘1’, the base station shall set
28 this field to maximum Fundamental Channel Outer Loop
29 Eb/Nt setpoint, in units of 0.125dB; otherwise, the base
31 FPC_OLPC_DCCH_INCL - Dedicated Control Channel Outer Loop Power Control
32 parameter included indicator.
36 If the forward link Dedicated Control Channel outer loop
37 power control parameters are included in this message, the
43 the Forward Dedicated Control Channel, as specified in Table
45 field.
3-684
3GPP2 C.S0005-A v6.0
1 FPC_DCCH_MIN_SETPT - Minimum Dedicated Control Channel Outer Loop Eb/Nt

2 setpoint.
4 station shall set this field to minimum Dedicated Control
5 Channel Outer Loop Eb/Nt setpoint, in units of 0.125dB;
7 FPC_DCCH_MAX_SETPT - Maximum Dedicated Control Channel Outer Loop Eb/Nt
8 setpoint.
10 station shall set this field to maximum Dedicated Control
11 Channel Outer Loop Eb/Nt setpoint, in units of 0.125dB;
13 GATING_RATE_INCL- Reverse Pilot Channel Gating rate included flag.
15 PILOT_GATING_RATE field is included; otherwise, it shall set
17 PILOT_GATING_RATE - Reverse Pilot Channel Gating rate.
18 If the GATING_RATE_INCL field is set to ‘0’, the base station
20 field as follows: The base station shall set this field to the
21 PILOT_GATING_RATE field shown in Table 3.7.5.20-1
22 corresponding to the gating rate on the Reverse Pilot Channel.
23 Table 3.7.5.20-1. Reverse Pilot Gating rate
PILOT_GATING_RATE field Meaning

(binary)
00 Gating rate 1
01 Gating rate ½
10 Gating rate ¼
11 Reserved
24
25 FOR_SCH_INCL - Forward Supplemental Channel information included

26 indicator.
27 The base station shall set this field to ‘1’, if the forward
28 Supplemental Channel information is included; otherwise, the
30 NUM_FOR_SCH - Number of Forward Supplemental Channels.
31 If the FOR_SCH_INCL field is set to ‘0’, the base station shall
33 to the number of Forward Supplemental Channels associated
34 with this service configuration.
35 If the NUM_FOR_SCH field is present and is set to any value other than ‘00’, the base
36 station shall include one occurrence of the following two field record for each Forward
3-685
3GPP2 C.S0005-A v6.0
1 FOR_SCH_ID - Forward Supplemental Channel Identification.

4 FOR_SCH-
5 _FRAME_OFFSET - Forward Supplemental Channel multiple frame offset.
6 The base station shall set this field to the multiple frame offset
7 of this Forward Supplemental Channel. The frames of this
8 Forward Supplemental Channel are delayed by
9 (FRAME_OFFSET × 1.25 + FOR_SCH_FRAME_OFFSET × 20)
10 ms relative to system timing (see [2]).
11
12 REV_SCH_ INCL - Reverse Supplemental Channel information included

13 indicator.
14 The base station shall set this field to ‘1’ if tthe reverse
15 Supplemental Channel information is included; otherwise, the
17 NUM_REV_SCH - Number of Reverse Supplemental Channels.
18 If the REV_SCH_INCL field is set to ‘0’, the base station shall
20 to the number of Reverse Supplemental Channels associated
21 with this service configuration.
22 If the NUM_REV_SCH field is present and is set to any value other than ‘00’, the base
23 station shall include one occurrence of the following four field record for each Reverse
25 REV_SCH_ID - Reverse Supplemental Channel Identification.
27 Reverse Supplemental Channel pertaining to this record.
28 REV_SCH-
29 _FRAME_OFFSET - Reverse Supplemental Channel multiple frame offset.
30 The base station shall set this field to the multiple frame offset
31 with this Reverse Supplemental Channel. The frames of this
32 Reverse Supplemental Channel are delayed by
33 (FRAME_OFFSET × 1.25 + REV_SCH_FRAME_OFFSET × 20)
34 ms relative to system timing (see [2]).
35
36 LPM_IND - Logical to Physical Mapping indicator.

37 The base station shall set this field to the LPM_IND field value
38 shown in Table 3.7.5.20-2 corresponding to the Logical to
39 Physical Mapping indicator.
40 The base station shall not set this field to ‘00’ if there is more
41 than one service option connection in the current Service
3-686
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.20-2. Logical to Physical Mapping indicator
LPM_IND Field (binary) Logical-to-Physical 2
Mapping indicator
00 Use the default Logic-to-

Physical Mapping
01 Use the Logic-to-Physical
Mapping included in this
record
10 Use the previous stored
Logic-to-Physical Mapping
11 Reserved
3 NUM_LPM_ENTRIES - Number of Logical-to-Physical Mapping entries.

4 If the LPM_IND field is set to ‘01’, the base station shall
7 The base station shall set this field to the number of Logical-
8 to-Physical Mapping entries that are included in this record.
9 If the NUM_LPM_ENTRIES field is included and is not equal to ‘0000’, the base station shall
10 include NUM_LPM_ENTRIES occurrences of the following six-field record for each Logical-
11 to-Physical Mapping entry:
12 SR_ID - Service reference identifier.
14 service reference to which this Logical to Physical Mapping
15 entry applies.
16 LOGICAL_RESOURCE - Logical resource identifier.
17 The base station shall set this field to the logical resource
18 identifier shown in Table 3.7.5.20-3 which is to be mapped by
19 this Logical to Physical Mapping entry.
20 Table 3.7.5.20-3. Logical Resource Identifier.
LOGICAL_RESOURCE Logical Resource

(binary)
0000 dtch
0001 dsch
21 PHYSICAL_RESOURCE - Physical resource identifier.
3-687
3GPP2 C.S0005-A v6.0
1 The base station shall set this field to the physical resource
2 identifier shown in Table 3.7.5.20-4 to which the logical
3 channel specified in this Logical to Physical Mapping entry is
4 to be mapped.
5 Table 3.7.5.20-4. Physical Resource Identifier.
PHYSICAL_RESOURCE Physical Resource
(binary)
0000 FCH
0001 DCCH
0010 SCH0
0011 SCH1

6
7 FORWARD_FLAG - Forward mapping indicator.

8 The base station shall set this field to ‘1’ if the logical to
9 physical channel mapping specified in this record applies to
10 forward logical channels; otherwise, the base station shall set
12 REVERSE_FLAG - Reverse mapping indicator.
13 The base station shall set this field to ‘1’ if the logical to
14 physical channel mapping specified in this record applies to
15 reverse logical channels; otherwise, the base station shall set
17 PRIORITY - Multiplexing priority.
19 NUM_REC - Number of service-specific records.
21 following variable-length records included in the message.
22 The base station shall include one occurrence of the following variable-length record for
23 each service option connection for which this record needs to be specified.
24 RECORD_LEN - Record length.
26 included in this variable-length record including this field.
29 service reference associated with this service-specific record.
30 SDB_SO_OMIT - Short Data Burst service option number omitted indicator.
3-688
3GPP2 C.S0005-A v6.0
2 is required to omit the service option number when sending
3 Short Data Burst (see IS-707-A-2) for this service option
4 connection; otherwise, the base station shall set this field to
5 ‘0’.

8 make the length of this record equal to an integer number of
10 USE_FLEX_NUM_BITS - Use flexible (non-default) number of bits per frame indicator.

11 The base station shall set this field to '0' to indicate that the
12 mapping between the number of information bits per frame
13 [NUM_BITS], and a four-bit index field [NUM_BITS_IDX], shall
14 follow the default mapping identified in Table 3.7.3.3.2.37-2
15 and Table 3.7.3.3.2.37-4.
16 The base station shall set this field to '1' to indicate a non-
17 default mapping between the number of information bits per
18 frame, [NUM_BITS], and a four-bit index field
19 [NUM_BITS_IDX] is specified in this message used for at least
20 a forward or reverse traffic channel.
21 USE_OLD_FLEXNUM_BITS_TABLES_INCL - Use the previously downloaded Flexible
22 Rate Tables included indicator.
23
24 If the USE_FLEX_NUM_BITS field is equal to ‘0’, the base

26 include this field and set this field as follows:

28 USE_FLEX_NUM_BITS is equal to ‘1’. If this field is included,
29 the base station shall set this field to ‘1’ to indicate that the
30 mobile station is to use the previously downloaded Flexible
31 Rate Table. The base station shall set this field to ‘0’ if the
32 fields related to downloading the Flexible Rate Table are
33 included in this message. If the Flexible Rate Tables are
36
37 NUM_BITS-
38 _TABLES_COUNT - Number of instances of the Flexible Rate Table included in
39 this message.
3-689
3GPP2 C.S0005-A v6.0
1 If the NUM_BITS_TABLES_INCL field is included and is equal

2 to ‘1’, theThe base station shall include this field only if
3 USE_OLD_FLEX_TABLE field is included and is set to '0'. If
4 this field is included, the base station shall and set this field
5 to one less than the number of instances of the Flexible Rate
6 Table included in this message; otherwise, the base station
8 If USE_OLD_FLEXNUM_TABLES_INCL is included and is equal to ‘01’, the base station

9 shall include NUM_BITS_TABLES_COUNT+1 instances of the Flexible Rate Table
10 NUM_BITS_TABLE_ID - Flexible Rate Table ID.
11 The base station shall set this field to the ID of the Flexible
12 Rate Table that follows. The value of ‘0000’ is reserved to
13 indicate the default table. The base station shall not set this
14 field to ‘0000’.
15 NUM_RECS - Number of records in the Flexible Rate Table.
17 number of three-field records that follows
18 The base station shall include NUM_RECS+1 instances of the following three- fields record:
19 NUM_BITS_IDX - Index to the number of bits array.
20 The base station shall set this field to the index to the array
21 that identifies the number of bits per frame.
22 NUM_BITS - Number of bits array.
24 information bits per frame corresponding to the index
25 specified by NUM_BITS_IDX. The base station shall set the
26 number of information bits per frame in accordance with the
27 number of information bits per frame specified by the service
28 option numbers included in the service configuration record.
29 CRC_LEN_IDX - Array of Number of CRC bits.
30 The base station shall set this field to specify the number of
31 CRC bits per frame corresponding to the index specified by
32 NUM_BITS_IDX according to Table 3.7.5.20-4. The base
33 station shall not specify more than one value of the CRC
34 length for the same number of bits per frame for a specific
35 channel (i.e., for a given channel, the number of information
36 bits per frame uniquely specifies the length of the CRC field).
3-690
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.20-4. CRC_LEN_IDX
CRC_LEN_IDX Number of CRC

(binary) bits per frame
000 0
001 6
010 8
011 10
100 12
101 16
110-111 Reserved
2
3 USE_VAR_RATE - Use variable rate on supplemental channels indicator.

4 The base station shall set this field to ‘1’ to indicate that at
5 least one of the forward or reverse supplemental channels is
6 to operate in the variable rate mode (i.e., the rate of the
7 supplemental channel can be picked from a pre-determined
8 set of rates autonomously).
9 The base station shall set this bit to '0' to indicate that
10 variable rate on supplemental channels are not allowed.
11 USE_OLD_VAR_TABLES_INCL - Use the previously downloaded Variable Rate Tables
13 If the USE_VAR_RATE field is equal to ‘0’, the base station

15 this field and set this field as follows:
16

18 USE_VAR_RATE is equal to ‘1’. If this field is included, the
19 base station shall set this field to ‘1’ to indicate that the
20 mobile station is to use the previously downloaded Variable
21 Rate Mask Table. The base station shall set this field to ‘0’ if
22 the fields related to downloading the Variable Rate Mask Table
23 are included in this message. If the Variable Rate Tables are
26
27 VAR_RATE-
28 _TABLES_COUNT - Number of instances of the Variable Rate Mask Table included
29 in this message.
3-691
3GPP2 C.S0005-A v6.0
1 If VAR_TABLES_INCL is included and is equal to ‘1’, the base

2 station shall include this field and set this field to one less
3 than the number of instances of the Variable Rate Mask table
4 included in this message as follows; otherwise, the base

9 USE_OLD_VAR_TABLE field is included and is set to ‘0’. If
11 one less than the number of instances of the Variable Rate
12 Mask table included in this message as follows.
13 If USE_OLD_VAR_TABLES_INCL is included and is equal to ‘10’, the base station shall

14 include VAR_RATE_TABLES_COUNT +1 instances of the Variable Rate Mask table
15 VAR_RATE_TABLE_ID - Variable Rate Mask table ID.
16 The base station shall set this field to the ID of the Variable
17 Rate Mask table that follows. The value of '000' is reserved to
18 indicate no variable rate operation. The base station shall not
20 NUM_RECS - Number of records in the Variable Rate Mask table.
22 number of two-field records that follows
23 The base station shall include NUM_RECS+1 instances of the following two fields:
24 NUM_BITS_IDX - Index to the number of bits array.
25 The base station shall set this field to the index to the array
26 that identifies the number of bits per supplemental channel
27 frame.
28 MASK - Number of bits array.
29 The base station shall set this field to a mask that identifies
30 the other members of the Variable Rate Set. The base station
th
31 shall set the i LSB bit (i=1, …, NUM_BITS_IDX) of this field to
32 ‘1’ to indicates that the number of bits per frame specified by
33 the index NUM_BITS_IDX-i is to be included in the
34 Supplemental Variable Rate Set.
35 USE_OLD-
36 _FLEX_MAPPING - Use the previously downloaded mapping between the channels
37 and Flexible Rate Tables.
38 If the USE_FLEX_NUM_BITS field is equal to ‘0’, the base

41
3-692
3GPP2 C.S0005-A v6.0

2 USE_FLEX_NUM_BITS field is set to '1'. If this field is
3 included, the base station shall set this field to ‘1’ to indicate
4 that the mobile station is to use the previously downloaded
5 mapping between the channels and Flexible Rate Tables. The
6 base station shall set this field to ‘0’, if the following eight
7 fields are included in this message.
8 FSCH0_NBIT_TABLE_ID - Forward Supplemental Channel 0 Flexible Rate Table ID.
9 If the USE_OLD_FLEX_MAPPING field is included and is equal

10 to ‘0’, the base station shall include this field and set this field
11 as follows; otherwise, the base station shall omit this field:
12

14 USE_OLD_FLEX_MAPPING field is included and is set to ‘0’. If
15 this field is included, the base station shall set this field to the
16 ID of the Flexible Rate Table corresponding to Forward
17 Supplemental Channel 0. The base station shall set this field
18 to ‘0000’ to indicate that the Flexible Rate feature is not used
19 for Forward Supplemental 0 and the default table specified in
20 3.7.3.3.2.37-4 shall be used.
21 RSCH0_NBIT_TABLE_ID - Reverse Supplemental Channel 0 Flexible Rate Table ID.
28 ID of the Flexible Rate Table corresponding to Reverse
31 for Reverse Supplemental 0 and the default table specified in
32 3.7.3.3.2.37-2 shall be used.
33 FSCH1_NBIT_TABLE_ID - Forward Supplemental Channel 1 Flexible Rate Table ID.
37

41 ID of the Flexible Rate Table corresponding to Forward
44 for Forward Supplemental 1 and the default table specified in
45 3.7.3.3.2.37-4 shall be used.
46 RSCH1_NBIT_TABLE_ID - Reverse Supplemental Channel 1 Flexible Rate Table ID.
3-693
3GPP2 C.S0005-A v6.0

4

8 ID of the Flexible Rate Table corresponding to Reverse
11 for Reverse Supplemental 1 and the default table specified in
12 3.7.3.3.2.37-2 shall be used.
13 .
14 FFCH_NBIT_TABLE_ID - Forward Fundamental Channel Flexible Rate Table ID.
21 ID of the Flexible Rate Table corresponding to the Forward
23 ‘0000’ to indicate that the Flexible Rate feature is not used for
24 the Forward Fundamental Channel.
25 RFCH_NBIT_TABLE_ID - Reverse Fundamental Channel Flexible Rate Table ID.
32 ID of the Flexible Rate Table corresponding to the Reverse
34 ‘0000’ to indicate that the Flexible Rate feature is not used for
35 the Reverse Fundamental Channel.
36 FDCCH_NBIT_TABLE_ID - Forward Dedicated Control Channel Flexible Rate Table ID.
43 ID of the Flexible Rate Table corresponding to the Forward
44 Dedicated Control Channel. The base station shall set this
45 field to ‘0000’ to indicate that the Flexible Rate feature is not
46 used for the Forward Dedicated Control Channel.
3-694
3GPP2 C.S0005-A v6.0
1 FDCCH_NBITS_IDX - Forward Dedicated Control Channel number of information

2 bits per frame index.
3 If the FDCCH_NBIT_TABLE_ID field is included and is not

4 equal to ‘0000’,
5 The base station shall include this field only if the

6 FDCCH_NBITS_TABLE_ID field is included and is not equal to
7 ‘0000’. If included, the base station shall include this field
8 and set this field to indicate the number of information bits
9 per Forward Dedicated Control Channel frame; otherwise, the
11 The number of information bits per frame is specified by the

12 Flexible Rate Table associated with Forward Dedicated Control
13 Channel and FDCCH_NBITS_IDX as the index to the table
14 (i.e.,
15 NUM_BITSs[FDCCH_NBITS_TABLE_IDr][FDCCH_NBITS_IDX].
16 RDCCH_NBIT_TABLE_ID - Reverse Dedicated Control Channel Flexible Rate Table ID.

20

24 ID of the Flexible Rate Table corresponding to the Reverse
26 field to ‘0000’ to indicate that the Flexible Rate feature is not
27 used for the Reverse Dedicated Control Channel.
28 RDCCH_NBITS_IDX - Reverse Dedicated Control Channel number of information
29 bits per frame index.
30 If the RDCCH_NBIT_TABLE_ID field is included and is not

31 equal to ‘0000’,
32 The base station shall include this field only if the RDCCH_NBITS_TABLE_ID field is
33 included and is not equal to ‘0000’. If included, the base
34 station shall include this field and set this field to indicate the
35 number of information bits per Reverse Dedicated Control
36 Channel frame; otherwise, the base station shall omit this
37 field.
38 The number of information bits per frame is specified by the
39 Flexible Rate Table associated with Reverse Dedicated Control
40 Channel and RDCCH_NBITS_IDX as the index to the table
41 (i.e.,
42 NUM_BITSs[RDCCH_NBITS_TABLE_IDr][RDCCH_NBITS_IDX].
43 USE_OLD_VAR_MAPPING - Use the previously downloaded mapping between the channels
44 and Variable Rate Mask Tables.
3-695
3GPP2 C.S0005-A v6.0
1 If the USE_VAR_RATE field is equal to ‘0’, the The base station

3 this field and set this field as follows: only if USE_VAR_RATE
4 field is set to ‘1’. If this field is included, the The base station
5 shall set this field to ‘1’ to indicate that the mobile station is to
6 use the previously downloaded mapping between the channels
7 and Variable Rate Mask Tables. The base station shall set
8 this field to ‘0’, if the following four fields are included in this
9 message.
10 FSCH0_VAR_TABLE_ID - Forward Supplemental Channel 0 Variable Rate Mask Table
11 ID.
12 If the USE_OLD_VAR_MAPPING field is included and is equal

15

17 USE_OLD_VAR_MAPPING field is included and is set to ‘1’. If
19 ID of the Variable Rate Mask Table corresponding to Forward
21 to ‘000’ to indicate that no variable rate operation is performed
22 on the F-SCH0.
23 RSCH0_VAR_TABLE_ID - Reverse Supplemental Channel 0 Variable Rate Mask Table
24 ID.

28

32 ID of the Variable Rate Mask Table corresponding to Reverse
34 to ‘000’ to indicate that the mobile station is not to
35 autonomously change the rate of the R-SCH0.
36 FSCH1_VAR_TABLE_ID - Forward Supplemental Channel 1 Variable Rate Mask Table
37 ID.

41
3-696
3GPP2 C.S0005-A v6.0

4 ID of the Variable Rate Mask Table corresponding to Forward
6 to ‘000’ to indicate that no variable rate operation is performed
7 on the F-SCH1.
8 RSCH1_VAR_TABLE_ID - Reverse Supplemental Channel 1 Variable Rate Mask Table
9 ID.
16 ID of the Variable Rate Mask Table corresponding to Reverse
18 to ‘000’ to indicate that the mobile station is not to
19 autonomously change the rate of the R-SCH1.
20 R_INC_RATE_ALLOWED - Reverse increase rate within Variable Rate Set Allowed
21 indicator.
22 If the USE_VAR_RATE field is included and is equal to ‘1’, the
23 base station shall include this field and set this field as
24 follows; otherwise, the base station shall omit this field:
25

27 USE_VAR_RATE field is included and is set to '1'. If this field
28 is included, the base station shall set this field to ‘1’ to
29 indicate that the mobile station is allowed to switch between
30 any of the rates (i.e., number of bits per frame) in the Variable
31 Rate Set for the Reverse Supplemental channels. The base
32 station shall set this field to ‘0’ to indicate that only a
33 downward transition in rate within the rates (i.e., number of
34 bits per frame) in the Variable Rate Set for the Reverse
35 Supplemental channels is allowed.
36 F_INC_RATE_ALLOWED - Forward increase rate within Variable Rate Set Allowed
37 indicator.
38 If the USE_VAR_RATE field is included and is equal to ‘1’, the
39 base station shall include this field and set this field as
3-697
3GPP2 C.S0005-A v6.0

2 USE_VAR_RATE field is included and is set to '1'. If this field
3 is included, the base station shall set this field to ‘1’ to
4 indicate that the base station is allowed to switch between any
5 of the rates (i.e., number of bits per frame) in the Variable
6 Rate Set for the Forward Supplemental channels. The base
7 station shall set this field to ‘0’ to indicate that only a
8 downward transition in rate within the rates (i.e., number of
9 bits per frame) in the Variable Rate Set for the Forward
10 Supplemental channels is possible.
11 LTU_INFO_INCL - LTU Size Tables included indicator.
12
14 includes to indicate that LTU Size Table information LTU
15 related information is included in this message; otherwise, the
16 base station shall set this field to ‘0’. The base station shall
17 include at least one LTU Size Table if USE_FLEX_NUM_BITS is
18 equal to ‘1’ and at least one of FSCH0_NBIT_TABLE_ID,
19 FSCH1_NBIT_TABLE_ID, RSCH0_NBIT_TABLE_ID, or
20 RSCH1_NBIT_TABLE_ID is not equal to ‘0000’ (i.e., the base
21 station is to specify the LTU size table for the supplemental
22 channels that are using the flexible rate feature).
24 indicates that it does not support downloadable LTU Table in
25 the capability information (i.e., the
26 F_SCH_LTU_TAB_SUPPORTED and
27 R_SCH_LTU_TAB_SUPPORTED fields in the capability
28 information are equal to ‘0’:).
29
30 USE_OLD_LTU_TABLES_INCL - Use the previously downloaded LTU Tables included

31 indicator.
32 If the LTU_INFO_INCL field is equal to ‘0’, the base station

33 shall omit this field; otherwise, the base stations shall include
35

37 USE_FLEX_NUM_BITS is equal to ‘1’ and LTU_INFO_INC is
38 equal to ‘1’. If this field is included, the base station shall set
39 this field to ‘1’ to indicate that the mobile station is to use the
40 previously downloaded LTU Table. The base station shall set
41 this field to ‘0’ if the fields related to downloading the LTU
42 Table are included in this message.If the LTU Tables are
45
3-698
3GPP2 C.S0005-A v6.0
3 If USE_OLD_LTU_TABLES_INCL is included and is equal to ‘01’, the base station shall

4 include the following fields related to the LTU Size Table
5 information:
6 NUM_LTU_TABLES - Number of LTU tables included.
7 If USE_OLD_LTU_TABLE is equal to ‘0’, the base station shall
8 include this field. If this field is included, the The base station
9 shall set this field to the number of LTU Tables minus one
11 If USE_OLD_LTU_TABLES_INCL is included and is equal to ‘01’, then the base station shall
12 include NUM_LTU_TABLES + 1 occurrences of the following fields:
13 LTU_TABLE_ID - LTU Table ID.
14 The base station shall set this field to the ID of the LTU Table
15 that follows. The base station shall not set this field to ‘000’.
16 NUM_ROWS - Number of configurations associated with the LTU Table
17 identified by LTU_TABLE_ID.
19 number of rows of the LTU Table identified by LTU_TABLE_ID.
20 If USE_OLD_LTU_TABLES_INCL is included and is equal to ‘01’, then the base station shall
21 include the NUM_ROWS + 1 occurrences of the following fields:
22 NBITS_IDX - Number of bits per frame index.
23 The base station shall set this field to the 4-bit index that
24 specified the number of information bits per supplemental
25 channel frame.
26 NUM_LTUS_LEN - Length Number of the LTUs per physical layer supplemental
27 channel frame.
28 The base station shall set this field to the length specify the
29 number of an LTUs per physical layer supplemental channel
30 frame (in units of bits) corresponding to the number of
31 information bits per supplemental channel frame specified by
32 NBITS_IDX according to Table 3.7.5.20-5. The base station
33 shall set this field to zero ‘0000’ to indicate that no LTUs are
34 supported for the number of information bits per frame
35 specified by NBITS_IDX.
3-699
3GPP2 C.S0005-A v6.0
1 Table 3.7.5.20-5. NUM_LTUS
NUM_LTUS Number of LTUS

(binary) per supplemental
channel frame
0000 0
0001 2
0010 3
0011 4
0100 5
0101 6
0110 7
0111 8
1000-1111 Reserved
4 USE_OLD-
5 _LTU_MAPPING - Use the previously downloaded mapping between the channels
6 and LTU Tables.
7 If the LTU_INFO_INCL field is equal to ‘0’, the base station

10

12 USE_FLEX_NUM_BITS is equal to ‘1’ and at least one of
13 FSCH0_NBIT_TABLE_ID, FSCH1_NBIT_TABLE_ID,
14 RSCH0_NBIT_TABLE_ID, or RSCH1_NBIT_TABLE_ID is not
15 equal to ‘0000’ (i.e., the base station is to specify the LTU size
16 table for the supplemental channels that are using the flexible
17 rate feature). If this field is included, the The base station
18 shall set this field to ‘1’ to indicate that the mobile station is to
19 use the previously downloaded mapping between the channels
20 and LTU Tables. The base station shall set this field to ‘0’, if
21 the following four fields are included in this message.
22 FSCH0_LTU_TAB_ID - Forward Supplemental Channel LTU Size Table ID.
3-700
3GPP2 C.S0005-A v6.0
1 If USE_OLD_LTU_MAPPING is included and is equal to ‘0’,

2 the base station shall include this field and set this field as
3 follows; otherwise, the base station shall omit this field:. If
4 this field is included, the The base station shall set this field
5 to the LTU Table ID to be used for the Forward Supplemental
6 Channel 0. The base station shall set this field to ‘000’ to
7 indicate that the default number of LTUs sizes are to be used
8 (see [3]) (The default LTU size is not applicable to
9 supplemental channels with multiplex options that use
10 MuxPDU Type 5; see [3]). The base station shall set this field
11 to ‘000’ if MuxPDU Type 5 is not used on this channel (see
12 [3]).
13
14
15 RSCH0_LTU_TAB_ID - Reverse Supplemental Channel LTU Size Table ID.

19 this field is included, the The base station shall set this field
20 to the LTU Table ID to be used for the Reverse Supplemental
23 (see [3]) (The default LTU size is not applicable to
27 [3]).
28
29 FSCH1_LTU_TAB_ID - Forward Supplemental Channel LTU Size Table ID.

33 this field is included, theThe base station shall set this field to
34 the LTU Table ID to be used for the Forward Supplemental
37 {see [3]) (The default LTU size is not applicable to
41 [3]).
42
43 RSCH1_LTU_TAB_ID - Reverse Supplemental Channel LTU Size Table ID.
3-701
3GPP2 C.S0005-A v6.0

4 this field is included, theThe base station shall set this field to
5 the LTU Table ID to be used for the Reverse Supplemental
8 (see [3]).(The default LTU size is not applicable to
12 [3]).
13 USE_OLD-
14 _PARTITION_TABLES_INFO_INCL - Use the previously downloaded Partition Tables
15 information included indicator.
16 If USE_FLEX_NUM_BITS is equal to ‘0’, the base station shall
18 field and set this field as follows:
19 If Partition Tables information is included in this message, the
22
23

25 USE_FLEX_NUM_BITS is equal to ‘1’ and at least one of
26 FFCH_NBIT_TABLE_ID, RFCH_NBIT_TABLE_ID,
27 FDCCH_NBIT_TABLE_ID, or RDCCH_NBIT_TABLE_ID is not
28 equal to ‘0000’. If this field is included, the base station shall
29 set this field to ‘1’ to indicate that the mobile station is to use
30 the previously downloaded Partition Table. The base station
31 shall set this field to ‘0’ if the fields related to downloading the
32 Partition Table are included in this message.
33 PARTITION_TABLES _INCL - Partition Tables included indicator.
34 If PARTITION_TABLES_INFO_INCL is equal to ‘0’, the base
37 If the Partition Tables are included in this message, the base
40
41
42 If USE_OLD_PARTITION_TABLES_INCL is included and is equal to ‘01’, then the base

43 station shall include the following fields
44 NUM-
45 _PARTITION_TABLES - Number of partition tables.
3-702
3GPP2 C.S0005-A v6.0
1 If USE_OLD_PARTITION_TABLE is equal to ‘0’, then the base

2 station shall include this field. If this field is included, The
3 the base station shall set this field to one less than the
4 number of Partition Tables corresponding to an FCH or DCCH

7 station shall include the NUM_PARTITION_TABLES + 1 occurrences of the following fields:
8 PARTITION_TABLE_ID - Partition Table ID.
9 The base station shall set this field to the ID of the Partition
10 Table that follows. The base station shall not set this field to
11 ‘000’.
12 NUM_ROWS - Number of configurations associated with the Partition Table
13 identified by PARTITION_TABLE_ID.
15 number of rows of the Partition Table identified by
16 PARTITION_TABLE_ID.

18 station shall include NUM_ROWS + 1 occurrences of the following fields:
19 CATEGORY - Category number.
20 The base station shall set this field to the category number of
21 the entry of the Partition Table identified by number of bits
22 per each service as specified below. The base station shall not
23 set this field to ‘00001’ or ‘00010’. The base station shall
24 place rows of the Partition Table corresponding to the same
25 number of total information bits per frame consecutively. See
26 [3].
27 MUX_HEADER_LEN - Multiplex Sublayer Header Length.
28 The base station shall set this field to the length of the
29 multiplex sublayer header corresponding to the entry of the
30 Partition Table identified by number of bits per each service as
31 specified below.
32 MUX_HEADER - Multiplex Sublayer Header.
33 The base station shall set this field to the multiplex sublayer
34 header corresponding to the entry of the Partition Table
35 identified by number of bits per each service as specified
36 below.7
7 The values of the MUX_HEADER corresponding to a specific number of bits per frame, shall be
encoded using prefix-free codes. Prefix-free code is defined to be a code constructed so that any
partial code word, beginning at the start of a code word but terminating prior to the end of that code
word, is not a valid code word.
3-703
3GPP2 C.S0005-A v6.0
1 NUM_PARTITIONS - Number of partitions.

3 number of partitions corresponding to each service (including
4 signaling) included in the entry of the Partition Table
5 identified by CATEGORY.

7 station shall include NUM_PARTITIONS + 1 occurrences of the following fields:
8 SR_ID - Service Reference ID.
9 The base station shall set this field to the sr_id of the service
10 (sr_id = ‘000’ for signaling) present in this category.
11 SRV_NUM_BITS - Number of bits allocated to the service.
12 The base station shall set this field to the number of bits
13 allocated to the service (including signaling) identified by
14 SR_ID.
15 USE_OLD-
16 _PART_MAPPING - Use the previously downloaded mapping between the channels
17 and Partition Tables.

19 USE_FLEX_NUM_BITS is equal to ‘1’
20 PARTITION_TABLES_INFO_INCL is equal to ‘1’ and the base
23 and at least one of FFCH_NBIT_TABLE_ID,
24 RFCH_NBIT_TABLE_ID, FDCCH_NBIT_TABLE_ID, or
25 RDCCH_NBIT_TABLE_ID is not equal to ‘0000’. If this field is
26 included, the The base station shall set this field to ‘1’ to
27 indicate that the mobile station is to use the previously
28 downloaded mapping between the channels and Partition
29 Tables. The base station shall set this field to ‘0’, if the
30 following four fields are included in this message.
31 FFCH_PART_TAB_ID - Forward Fundamental Channel Partition Table ID.
32 If USE_OLD_PART_MAPPING is included and is equal to ‘0’,
35
36 . If this field is included, the The base station shall set this
37 field to the Partition Table ID to be used for the Forward
39 ‘000’ to indicate that the default number of bits per service is
3-704
3GPP2 C.S0005-A v6.0
1 to be used (see MuxPDU Type 1 and 2 Categories and Formats

2 for the FCH and DCCH in [3]). The base station shall set this
3 field to a value other than ‘000’ if the FFCH_NBIT_TABLE_ID
4 field is included in this message and is not set to ‘0000’.
5 RFCH_PART_TAB_ID - Reverse Fundamental Channel Partition Table ID.

10 field to the Partition Table ID to be used for the Reverse
12 ‘000’ to indicate that the default number of bits per service is
13 to be used (see MuxPDU Type 1 and 2 Categories and Formats
14 for the FCH and DCCH in [3]). The base station shall set this
15 field to a value other than ‘000’ if the RFCH_NBIT_TABLE_ID
16 is included in this message and field is not set to ‘0000’.
17 FDCCH_PART_TAB_ID - Forward Dedicated Control Channel Partition Table ID.

22 field to the Partition Table ID to be used for the Forward
24 field to ‘000’ to indicate that the default number of bits per
25 service is to be used (see MuxPDU Type 1 and 2 Categories
26 and Formats for the FCH and DCCH in [3]). The base station
27 shall set this field to a value other than ‘000’ if the
28 FDCCH_NBIT_TABLE_ID field is included in this message and
29 is not set to ‘0000’.
30 RDCCH_PART_TAB_ID - Reverse Dedicated Control Channel Partition Table ID.
31 If USE_OLD_PART_MAPPING is included and is

32 equal to ‘0’, the base station shall include this field and set
33 this field as follows; otherwise, the base station shall omit this
34 field:
36 field to the Partition Table ID to be used for the Reverse
38 field to ‘000’ to indicate that the default number of bits per
39 service is to be used (see MuxPDU Type 1 and 2 Categories
40 and Formats for the FCH and DCCH in [3]). The base station
41 shall set this field to a value other than ‘000’ if the
42 RDCCH_NBIT_TABLE_ID field is included in this message and
3-705
3GPP2 C.S0005-A v6.0
1 is not set to ‘0000’.

3-706
3GPP2 C.S0005-A v6.0
1 3.7.5.21 Multiple Character Extended Display
2 This information record allows the network to supply supplementary service multiple
3 character display information that may be displayed by the mobile station.
MC_EXT_DISPLAY_IND 1
DISPLAY_TYPE 7
DISPLAY_TAG 8
NUM_RECORD 8
NUM_RECORD occurrences of the following record if the
DISPLAY_TAG field is not equal to ‘10000000’ or
‘10000001’:
DISPLAY_ENCODING 8
NUM_FIELDS 8
CHARi Variable
6 MC_EXT_DISPLAY_IND - The indicator of Multiple Character Extended Display

9 DISPLAY_TYPE - The type of display.
10 The base station shall set this field to the DISPLAY_TYPE
11 value shown in Table 3.7.5.16-1 corresponding to the type of
12 display, as defined in [8] Annex D.
13 DISPLAY_TAG - The indicator of the display information.
14 There are three types of display tags: mandatory control tags
15 (Blank and Skip), display text tags, and optional control tags,
16 see [8] Annex D.
17 The base station shall set this field to the DISPLAY_TAG value
18 shown in Table 3.7.5.16-2 corresponding to the type of
19 information contained in the following CHARi field, as defined
20 in [8] Annex D.
21 NUM_RECORD - The number of records displaying.
22 The base station shall set this field to the number of records
23 of display text.
3-707
3GPP2 C.S0005-A v6.0
1 DISPLAY_ENCODING - Display encoding.
2 See [30].
3 Support of an encoding method does not imply that the entire

4 encodable character set must be supported. In general, once
5 the supported character set is determined, various subsets of
6 the character set can be supported. If a message is comprised
7 entirely of characters from a supported subset of a character
8 set, it can be displayed. If a message contains an
9 unsupported character of a character set, it can be discarded.
10 NUM_FIELDS - Number of occurrences of the CHARi field.

12 characters included in this record.
15 this field, one for each character to be displayed, except for
16 blank and skip.
3-708
3GPP2 C.S0005-A v6.0
1 3.7.5.22 Call Waiting Indicator
2 This information record allows the base station to inform the mobile station that a call
3 waiting call is available. This indicator may be used to suppress the generation of the local
4 dial tone in mobile stations that provide locally generated dial tone.
CALL_WAITING_INDICATOR 1
RESERVED 7
7 CALL_WAITING-
8 _INDICATOR - Call waiting indicator.
9 The base station shall set this field to a ‘1’ to indicate to the
10 mobile station that a call is waiting. The base station shall set
11 this field to a ‘0’ if the call waiting call is not answered by the
12 mobile station and the call waiting call goes away.
3-709
3GPP2 C.S0005-A v6.0
1 3.7.6 Information Elements
2 3.7.6.1 Pilot Record Type Specific Fields
3 If PILOT_REC_TYPE is equal to ‘000’, the Pilot Record Type Specific fields include the
4 following fields:
Field Length (bits)
TD_POWER_LEVEL 2
TD_MODE 2
RESERVED 4
7 TD_POWER_LEVEL - TD transmit power level.

8 The base station or mobile station shall set this field to the TD
9 transmit power level relative to that of the Forward Pilot
10 Channel, as specified in Table 3.7.6.1-1.
11 Table 3.7.6.1-1. TD Transmit Power Level
TD_POWER_LEVEL Transmit Power Level

11 Same as the Forward Pilot
12

14 The base station or mobile station shall set this field to the
15 Transmit Diversity mode, as specified in Table 3.7.6.1-2.
3-710
3GPP2 C.S0005-A v6.0
1 Table 3.7.6.1-2. TD Mode
TD_MODE Descriptions
00 OTD (Orthogonal Transmit

Diversity) mode
01 STS (Space Time Spreading)
mode
10-11 Reserved

4 The base station or mobile station shall set this field to
5 ‘000000’.
7 If PILOT_REC_TYPE is equal to ‘001’, the base station or mobile station shall include the
8 following fields:
Field Length (bits)
QOF 2
WALSH_LENGTH 3

12 index of the Quasi-orthogonal function (see Table 3.1.3.1.12-2
13 of [2]).
16 WALSH_LENGTH value shown in Table 3.7.6.1-3
17 corresponding to the length of the Walsh code for the pilot
18 that is used as the Auxiliary pilot.
3-711
3GPP2 C.S0005-A v6.0
1 Table 3.7.6.1-3. Walsh Code Length
WALSH_LENGTH Length of the Walsh

(binary) Code
‘000’ 64
‘001’ 128
‘010’ 256
‘011’ 512
‘100’ – ‘111’ Reserved

5 Walsh code corresponding to the Auxiliary pilot.
7 The base station or mobile station shall set all the bits of this
8 field to ‘0’ to make the entire record octet-aligned.
10 following fields:
11
Field Length (bits)
QOF 2
WALSH_LENGTH 3
TD_MODE 2
12

14 Diversity Pilot.
17 of [2]).
20 WALSH_LENGTH value shown in 3.7.6.1-3 corresponding to
21 the length of the Walsh code for the pilots that are used as
22 Auxiliary pilot in the transmit diversity mode.
3-712
3GPP2 C.S0005-A v6.0
2 Walsh code corresponding to the Auxiliary Pilot.
3 AUX_ TD-
6 Auxiliary Transmit Diversity Pilot transmit power level relative
7 to that of the Auxiliary Pilot as specified in Table 3.7.6.1-4.
8 Table 3.7.6.1-4. Auxiliary Transmit Diversity Pilot

9 Transmit Power Level
AUX_TD_POWER_LEVEL Transmit Power Level

11 Same as the Auxiliary Pilot
10

13 Transmit Diversity mode, as specified in Table 3.7.6.1-2.
17
19 following fields:
20
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
21

24 value shown in Table 3.7.6.1-5 corresponding to the position
25 of the primary SR3 pilot.
3-713
3GPP2 C.S0005-A v6.0
1 Table 3.7.6.1-5. The Position of the Primary SR3 Pilot
SR3_PRIMARY_PILOT Position
(Binary)

lowest SR3 frequency
center SR3 frequency
highest SR3 frequency
11 Reserved
6 value shown in Table 3.7.6.1-6 corresponding to the power
9 Table 3.7.6.1-6. Pilot Transmission Power
SR3_PILOT_POWER1, Relative Transmission Power

SR3_PILOT_POWER2
(Binary)
000 0dB
001 1dB
010 2dB
011 3dB
100 4dB
101 5dB
110 6dB
111 7dB
10
3-714
3GPP2 C.S0005-A v6.0
3 following fields:
Field Length (bits)
SR3_PRIMARY_PILOT 2
SR3_PILOT_POWER1 3
SR3_PILOT_POWER2 3
QOF 2
WALSH_LENGTH 3
ADD_INFO_INCL1 1
QOF1 0 or 2
WALSH_LENGTH1+6
ADD_INFO_INCL2 1
QOF2 0 or 2
WALSH_LENGTH2+6

8 value shown in Table 3.7.6.1-5 corresponding to the position
9 of the primary SR3 pilot.
3-715
3GPP2 C.S0005-A v6.0
1 QOF – Quasi-orthogonal function index.

4 of [2]) on the frequency of the primary pilot.
5 WALSH_LENGTH – Length of the Walsh Code.
9 that is used as the Auxiliary pilot on the frequency of the
10 primary pilot.
11 AUX_PILOT_WALSH – Walsh Code for the Auxiliary Pilot.
13 Walsh code corresponding to the Auxiliary pilot on the
15 ADD_INFO_INCL1 – Additional information included for the pilot on the lower
19 as pilot on the primary frequency, the base station or mobile
20 station shall set this field to ‘0’; otherwise, the base station or
22 QOF1 – Quasi-orthogonal function index for the pilot on the lower
24 If ADD_INFO_INCL1 is set to ‘0’, the base station or mobile
25 station shall omit this field; otherwise, the base station or
26 mobile station shall set this field as follows:
29 of [2]) on the lower frequency of the two remaining SR3
30 frequencies.
39 that is used as the Auxiliary pilot on the lower frequency of
3-716
3GPP2 C.S0005-A v6.0
2 Walsh code corresponding to the Auxiliary pilot on the lower
8 as pilot on the primary frequency, the base station or mobile
9 station shall set this field to ‘0’; otherwise, the base station or
18 of [2]) on the higher frequency of the two remaining SR3
19 frequencies.
28 that is used as the Auxiliary pilot on the higher frequency of
36 Walsh code corresponding to the Auxiliary pilot on the higher
3-717
3GPP2 C.S0005-A v6.0
2 No text.
3
3-718
3GPP2 C.S0005-A v6.0
1 ANNEX A RESERVED
A-1
3GPP2 C.S0005-A v6.0
2 No text.
3
A-2
3GPP2 C.S0005-A v6.0
1 ANNEX B CDMA CALL FLOW EXAMPLES
2 This is an informative annex which contains examples of call flow. The diagrams follow
3 these conventions:
4 • All messages are received without error
5 • Receipt of messages is not shown except in the handoff examples
6 • Acknowledgments are not shown
7 • Optional authentication procedures are not shown
8 • Optional private long code transitions are not shown
9 For the call flow diagrams B-22 through B-31, the following conventions hold:
10 • The following message acronyms are defined:
11 ERRM: Extended Release Response Message
12 ERRMM: Extended Release Response Mini Message
13 RRM: Resource Request Message
14 RRMM: Resource Request Mini Message
15 RRRM: Resource Release Request Message
16 RRRMM: Resource Release Request Mini Message
17 SreqM: Service Request Message
18 SCRM: Supplemental Channel Request Message
19 SCRMM: Supplemental Channel Request Mini Message
20 ERM: Extended Release Message
21 ERMM: Extended Release Mini Message
22 RAM: Resource Allocation Message
23 RAMM: Resource Allocation Mini Message
24 SCM: Service Connect Message
25 GHDM: General Handoff Direction Message
26 UHDM: Universal Handoff Direction Message
27 ESCAM: Extended Supplemental Channel Assignment Message
28 FSCAMM: Forward Supplemental Channel Assignment Mini Message
B-1
3GPP2 C.S0005-A v6.0
1 RSCAMM: Reverse Supplemental Channel Assignment Mini Message
2 HCM: (Extended) Handoff Complete Message
Mobile Station Base Station

• Detects user-initiated call.
• Sends Origination Message. > Access Channel > • Sets up Traffic Channel.
• Begins sending null Traffic
Channel data.
• Sets up Traffic Channel. < Paging Channel < • Sends Channel Assignment
Message.
• Receives N5m consecutive
valid frames.
• Begins sending the Traffic • Acquires the Reverse Traffic
Channel preamble. Channel.
• Begins transmitting null < Forward Traffic < • Sends Base Station
Traffic Channel data. Channel Acknowledgment Order.
• Begins processing primary < Forward Traffic < • Sends Service Option
traffic in accordance with Channel Response Order.
Service Option 1.
Optional Optional
• Sends Origination > Reverse Traffic >
Continuation Message. Channel
Optional Optional
• Applies ring back in audio < Forward Traffic < • Sends Alert With Information
path. Channel Message (ring back tone).
Optional Optional
• Removes ring back from < Forward Traffic < • Sends Alert With Information
audio path. Channel Message (tones off).
(User conversation) (User conversation)
4 Figure B-1A. Simple Call Flow, Mobile Station Origination Example Using
5 Service Option Negotiation with Service Option 1
B-2
3GPP2 C.S0005-A v6.0

• Detects user-initiated call.
• Sends Origination Message. > Access Channel > • Sets up Traffic Channel.
Channel data.
Message.
valid frames.
• Begins processing primary < Forward Traffic < • Sends Service Connect
traffic in accordance with Channel Message.
Service Option 1.
• Sends Service Connect > Reverse Traffic >
Completion Message. Channel
Optional Optional
Optional Optional
Optional Optional
2 Figure B-1B. Simple Call Flow, Mobile Station Origination Example Using Service
3 Negotiation with Service Option 1
B-3
3GPP2 C.S0005-A v6.0

< Paging Channel < • Sends General Page
Message.
• Sends Page Response > Access Channel > • Sets up Traffic Channel.
Message. • Begins sending null Traffic
Channel data.
Message.
valid frames.
• Begins processing primary < Forward Traffic < • Sends Service Option
traffic in accordance with Channel Response Order.
Service Option 1.
• Starts ringing. < Forward Traffic < • Sends Alert With Information
Channel Message (ring).
• User answers call.
• Stops ringing.
• Sends Connect Order. > Reverse Traffic >
Channel
• Begins sending primary
traffic packets from the
Service Option 1 application.
2 Figure B-2A. Simple Call Flow, Mobile Station Termination Example Using
3 Service Option Negotiation with Service Option 1
B-4
3GPP2 C.S0005-A v6.0

Message.
Channel data.
Message.
valid frames.
Service Option 1.
• Starts ringing. < Forward Traffic < • Sends Alert With Information
Channel Message (ring).
• Stops ringing.
• Sends Connect Order. > Reverse Traffic >
Channel
• Begins sending primary
traffic packets from the
Service Option 1 application.
2 Figure B-2B. Simple Call Flow, Mobile Station Termination Example Using Service
3 Negotiation with Service Option 1
B-5
3GPP2 C.S0005-A v6.0

• Detects user-initiated
disconnect.
• Sends Release Order. > Reverse Traffic >
Channel
< Forward Traffic < • Sends Release Order.
Channel
• Enters the System
Determination Substate of the
Mobile Station Initialization
State.
2 Figure B-3. Simple Call Flow, Mobile Station Initiated Call Disconnect Example
3

• Detects call disconnect.
< Forward Traffic < • Sends Release Order.
Channel
• Sends Release Order. > Reverse Traffic >
Channel
• Enters the System
Determination Substate of the
Mobile Station Initialization
State.
8 Figure B-4. Simple Call Flow, Base Station Initiated Call Disconnect Example
B-6
3GPP2 C.S0005-A v6.0

• Detects request for third
party to be added to
conversation.
• Sends Flash With Information > Reverse Traffic > • MSC mutes speech.
Message (dialed digits). Channel
Optional Optional
(Called party answers)
Optional Optional
• Removes ring back tone from < Forward Traffic < • Sends Alert With Information
• MSC unmutes speech from
added party.
(Two-way conversation with (Two-way conversation with
added party; original party added party; original party
held) held)
• Detects user request to
establish three-way
conversation.
• Sends Flash With Information > Reverse Traffic > • MSC reconnects original
Message. Channel party.
(Three-way conversation) (Three-way conversation)
2 Figure B-5. Simple Call Flow, Three-Party Calling Example
B-7
3GPP2 C.S0005-A v6.0

(User conversation with first (User conversation with first
party) party)
• Detects incoming call.
Optional Optional
• Applies call waiting tone in < Forward Traffic < • Sends Alert or Flash With
audio path. Channel Information Message (call
waiting tone).
change parties.
• Sends Flash With Information > Reverse Traffic > • MSC mutes speech path to
Message. Channel first party, connects second
party.
(User conversation with second (User conversation with

party; first party held) second party; first party held)
change parties.
• Sends Flash With Information > Reverse Traffic > • MSC mutes speech path to
Message. Channel second party, connects first
party.
(User conversation with first (User conversation with first
party; second party held) party; second party held)
2 Figure B-6. Simple Call Flow, Call-Waiting Example
6 Figure B-7 illustrates call processing operations during a soft handoff from base station A
7 to base station B. Figure B-8 illustrates call processing operations during a sequential soft
8 handoff in which the mobile station is transferred from a pair of base stations A and B
9 through a pair of base stations B and C to base station C.
10
B-8
3GPP2 C.S0005-A v6.0

(User conversation using A) (User conversation using A)
• Pilot B strength exceeds
T_ADD.
• Sends Pilot Strength > Reverse Traffic > • A receives Pilot Strength
Measurement Message. Channel Measurement Message.
• B begins transmitting traffic
on the Forward Traffic
Channel and acquires the
Reverse Traffic Channel.
• Receives Extended Handoff < Forward Traffic < • A and B send Extended
Direction Message. Channel Handoff Direction Message
to use A and B.
• Acquires B; begins using
Active Set {A,B}.
• Sends Handoff Completion > Reverse Traffic > • A and B receive Handoff
Message. Channel Completion Message.
• Handoff drop timer of pilot A

expires.
• Sends Pilot Strength > Reverse Traffic > • A and B receive Pilot
Measurement Message. Channel Strength Measurement
Message.
• Receives Extended Handoff < Forward Traffic < • A and B send Extended
to use B only.
• Stops diversity combining;
begins using Active Set {B}.
• Sends Handoff Completion > Reverse Traffic > • A and B receive Handoff
• A stops transmitting on the
Forward Traffic Channel and
receiving on the Reverse
Traffic Channel.
(User conversation using B) (User conversation using B)
2 Figure B-7. Call Processing During Soft Handoff
B-9
3GPP2 C.S0005-A v6.0

(User conversation using (User conversation using
A and B) A and B)
• Handoff drop timer of pilot A
expires and pilot C strength
exceeds T_ADD.
• Sends Pilot Strength > Reverse Traffic > • A and B receive Pilot
Message, determine that
new Active Set should
contain B and C.
• C begins transmitting traffic
on the Forward Traffic
Channel and acquires the
Reverse Traffic Channel.
• Receives Extended Handoff < Forward Traffic < • A, B, and C send Extended
to use B and C.
• Stops diversity combining A
and B; starts diversity
combining B and C.
• Sends Handoff Completion > Reverse Traffic > • A, B, and C receive Handoff
• A stops transmitting on the
Traffic Channel.
• Handoff drop timer of pilot B
expires.
• Sends Pilot Strength > Reverse Traffic > • B and C receive Pilot
Message.
(Continued on next page) (Continued on next page)
2 Figure B-8. Call Processing During Sequential Soft Handoff (Part 1 of 2)
B-10
3GPP2 C.S0005-A v6.0

(Continued from previous page) (Continued from previous page)
• Receives Extended Handoff < Forward Traffic < • B and C send Extended
to use C only.
• Stops diversity combining;
begins using Active Set {C}.
• Sends Handoff Completion > Reverse Traffic > • B and C receive Handoff
• B stops transmitting on the
Traffic Channel.
(User conversation using C) (User conversation using C)
2 Figure B-8. Call Processing During Sequential Soft Handoff (Part 2 of 2)
B-11
3GPP2 C.S0005-A v6.0

• User initiates priority call.
• Sends Origination Message. > Access Channel > • Determines that no Traffic
Channels are available and
that call is a priority call.
• Indicates to user that priority < Paging Channel < • Sends PACA Message to
call has been queued as a inform user that priority call
PACA call, and indicates has been queued as a PACA
queue position. call, and to indicate queue
Uses non-slotted mode position.
operation while waiting for
channel assignment.
• Indicates updated queue < Paging Channel < • Sends PACA Message
position to user. periodically to update PACA
call queue position.
< Paging Channel < • Sends PACA Message to
instruct mobile station to
re-originate PACA call.
• Sends Origination Message > Access Channel > • Sets up Traffic Channel.
again.
• Indicates to user that PACA < Paging Channel < • Sends Channel Assignment
call is proceeding, sets up Message.
Traffic Channel.
valid frames.
• Begins sending Traffic • Acquires the Reverse Traffic
Service Option 1.
2 Figure B-9. PACA Call Processing (Part 1 of 2)
B-12
3GPP2 C.S0005-A v6.0

Optional Optional
• Alerts user with distinct < Forward Traffic < • Sends Alert With Information
PACA alert. Channel Message (distinct PACA
alert).
• Stops alerting.
• Sends Connect Order. > Reverse Traffic > • Dials out PACA call.
Channel
Optional Optional
Optional Optional
2 Figure B-9. PACA Call Processing (Part 2 of 2)

3
4 Figure B-10 illustrates call processing operations for failure recovery for hard handoff on
5 the same frequency. Figure B-11 illustrates call flow for failure recovery for inter-frequency
6 handoff when the mobile station does not search the Candidate Frequency. Figures B-12
7 and B-13 show the call flow for mobile-assisted inter-frequency handoff (handoff preceded
8 by searching of the Candidate Frequency Search Set by the mobile station), where the
9 search is started by using the Candidate Frequency Search Control Message. Figures B-14
10 and B-15 illustrate call flow for inter-frequency handoff when failure recovery also includes
11 searching the Candidate Frequency Search Set. In the periodic search examples (Figures
12 B-13 and B-15), it is assumed that the mobile station performs a search of the Candidate
13 Frequency Search Set in a single visit to the Candidate Frequency. Figures B-16 and B-17
14 illustrate the interaction of inter-frequency handoff operations with an ongoing periodic
15 search of the Candidate Frequency Search Set.
16
B-13
3GPP2 C.S0005-A v6.0

(Serving Frequency = F1) (Serving Frequency = F1)
(Decides to hand off mobile
station to new Active Set)
(Starts transmitting on Forward
Traffic Channel corresponding
to target Active Set)
• Receives General Handoff < Forward Traffic < • Sends General Handoff
Direction Message. Channel Direction Message
Saves current configuration. (target Active Set disjoint
Discontinues use of serving from serving Active Set;
Active Set. RETURN_IF_HO_FAIL = ‘1’;
Target Frequency = F1).
(Maintains Forward and
Reverse Traffic Channels
corresponding to serving Active
Set)
• Attempts to hand off to target
Active Set.
(Handoff attempt fails)
• Restores old configuration.
Resumes use of serving
Active Set.
• Sends Candidate Frequency > Reverse Traffic > • Receives Candidate
Search Report Message Channel Frequency Search Report
reporting pilots in target Message.
Active Set. (Discontinues use of target
Active Set)
(Continues communication (Continues communication

using serving Active Set) using serving Active Set)
2 Figure B-10. Call Flow for Same Frequency Hard Handoff Failure Recovery
B-14
3GPP2 C.S0005-A v6.0

(Candidate Frequency Search station to Active Set on F2)
Set is empty) (Starts transmitting on
Forward Traffic Channel on
F2)
Direction Message. Channel on F1 Direction Message
Saves current configuration. (target Active Set;
Discontinues use of serving RETURN_IF_HO_FAIL = ‘1’;
Active Set. Target Frequency = F2).
on F1)
• Tunes to F2.
Attempts to hand off to target
Active Set.
• Re-tunes to F1.
Restores old configuration.
Active Set.
Search Report Message Channel on F1 Frequency Search Report
Active Set. (Discontinues use of Active Set
on F2)

on F1) on F1)
2 Figure B-11. Call Flow for Inter-Frequency Hard Handoff Failure Recovery
3 without Search
B-15
3GPP2 C.S0005-A v6.0

• Receives Candidate < Forward Traffic < • Sends Candidate Frequency
Frequency Search Request Channel on F1 Search Request Message
Message. (non-empty Search Set;
Candidate Frequency = F2).
• Computes search time for
Candidate Frequency Search
Set.
Sends Candidate Frequency > Reverse Traffic > • Receives Candidate
Search Response Message. Channel on F1 Frequency Search Response
Message.
(Decides to initiate single
search)
Frequency Search Control Channel on F1 Search Control Message
Message. (perform single search;
• Saves current configuration.
Discontinues use of serving
Active Set.
• Tunes to F2.
• Searches pilots in Candidate
Frequency Search Set.
• Re-tunes to F1.
Active Set.
reporting pilots in Candidate Message.
Frequency Search Set above
CF_T_ADD.
on F1) on F1)
3 Frequency Search Control Message) (Part 1 of 2)
B-16
3GPP2 C.S0005-A v6.0


station to Active Set on F2)
(Starts transmitting on
F2)
Saves current configuration. (RETURN_IF_HO_FAIL = ‘1’;
Discontinues use of serving Target Frequency = F2).
Active Set. (Maintains Forward and
on F1)
• Tunes to F2.
Active Set.
(Handoff attempt succeeds)
(Starts transmitting on Reverse (Starts receiving on Reverse
Traffic Channel on F2) Traffic Channel on F2)
• Sends Handoff Completion > Reverse Traffic > • Receives Handoff Completion
Message. Channel on F2 Message.
(Discontinues use of Active Set
on F1)

on F2) on F2)
B-17
3GPP2 C.S0005-A v6.0

Set.
Message.
(Decides to initiate periodic
search)
Message. (start periodic search;
Initializes and enables Candidate Frequency = F2).
periodic search timer.
(Periodic search timer running)
• Performs a search of Candi-

date Frequency Search Set
by executing the following
actions before periodic
search timer expires:
− Saves current
configuration.
Discontinues use of
serving Active Set.
− Tunes to F2.
− Searches pilots in
Candidate Frequency
Search Set.
B-18
3GPP2 C.S0005-A v6.0

− Re-tunes to F1.
Restores old
configuration.
Active Set.
− Sends Candidate > Reverse Traffic > • Receives Candidate
Frequency Search Report Channel on F1 Frequency Search Report
Message reporting pilots Message.
in Candidate Frequency
Search Set above
CF_T_ADD.
on F1) on F1)
(Periodic search timer expires)

• Initializes and enables
(Continues periodic search on

F2 by repeating the search
described above, once every
search period)

F2)
B-19
3GPP2 C.S0005-A v6.0

Disables periodic search (RETURN_IF_HO_FAIL = ‘1’;
timer. Target Frequency = F2).
Saves current configuration. (Maintains Forward and
Discontinues use of serving Reverse Traffic Channels
Active Set. on F1)
• Tunes to F2.
Active Set.
on F1)

on F2) on F2)
B-20
3GPP2 C.S0005-A v6.0

Candidate Frequency
Search Set.
Search Response Message. Channel on F1 Frequency Search
Response Message.
F2)
Active Set. PERIODIC_SEARCH = ‘0’;
on F1)
• Tunes to F2.
Active Set.
2 Figure B-14. Call Flow for Inter-Frequency Handoff (Single Search Using
3 General Handoff Direction Message) (Part 1 of 3)
B-21
3GPP2 C.S0005-A v6.0

• Re-tunes to F1.
Active Set.
Active Set and pilots in (Discontinues use of Active Set
Candidate Frequency Search on F2)
Set above CF_T_ADD.

on F1) on F1)

station to new Active Set
on F2)
F2)
• Saves current configuration. < Forward Traffic < • Sends General Handoff
Discontinues use of serving Channel on F1 Direction Message
Active Set. (new target Active Set;
RETURN_IF_HO_FAIL = ‘1’;
on F1)
• Tunes to F2.
Active Set.
B-22
3GPP2 C.S0005-A v6.0


on F1)

on F2) on F2)
B-23
3GPP2 C.S0005-A v6.0

Candidate Frequency
Search Set.
Message.
F2)
Active Set. PERIODIC_SEARCH = ‘1’;
(Maintains Forward and Rev-
erse Traffic Channels on F1)
• Tunes to F2.
Active Set.
• Re-tunes to F1.
Active Set.
3 Handoff Direction Message) (Part 1 of 4)
B-24
3GPP2 C.S0005-A v6.0


Active Set and pilots in (Discontinues use of Active Set
Candidate Frequency Search on F2)
Set above CF_T_ADD.

on F1) on F1)
(Periodic search timer running)
• Performs a search of Candi-

date Frequency Search Set
by executing the following
actions before periodic
search timer expires:
− Saves current
configuration.
Discontinues use of
serving Active Set.
− Tunes to F2.
− Searches pilots in
Candidate Frequency
Search Set.
− Re-tunes to F1.
Restores old
configuration.
Active Set.
B-25
3GPP2 C.S0005-A v6.0

− Sends Candidate > Reverse Traffic > • Receives Candidate

Frequency Search Report Channel on F1 Frequency Search Report
Message reporting pilots Message.
in Candidate Frequency
Search Set above
CF_T_ADD.
on F1) on F1)
(Periodic search timer expires)
(Continues periodic search on

F2 by repeating the search
described above, once every
search period)
station to new Active Set
on F2)
F2)
Disables periodic search (new target Active Set;
timer. RETURN_IF_HO_FAIL = ‘1’;
Saves current configuration. Target Frequency = F2).
Discontinues use of serving (Maintains Forward and Rev-
Active Set. erse Traffic Channels on F1)
• Tunes to F2.
Active Set.
B-26
3GPP2 C.S0005-A v6.0


on F1)

on F2) on F2)
B-27
3GPP2 C.S0005-A v6.0

Candidate Frequency
Search Set.
Search Response Message. Channel on F1 Frequency Search
Response Message.
search)
.
.
(Performs periodic search
on F2)
. (Decides to hand off mobile
. station to Active Set on F3)
(Starts transmitting on Forward
Traffic Channel on F3)
2 Figure B-16. Call Flow for Periodic Search on F2 from F1, Failed Handoff
3 Attempt to F3, Continued Periodic Search of F2 from F1 (Part 1 of 3)
B-28
3GPP2 C.S0005-A v6.0

Disables periodic search (target Active Set;
Saves current configuration. PERIODIC_SEARCH = ‘1’;
Active Set. (Maintains Forward and
Reverse Traffic Channels on
F1)
• Tunes to F3.
Active Set.

• Re-tunes to F1.
Active Set.
Initializes and enables
B-29
3GPP2 C.S0005-A v6.0


Active Set. (Discontinues use of Active Set
on F3)

on F1) on F1)
.
.
on F2)
.
.
(Continues communication
on F1)
B-30
3GPP2 C.S0005-A v6.0

Set.
Message.
search)
.
.
on F2)
. (Decides to hand off mobile
. station to Active Set on F3)
. (Starts transmitting on Forward

Traffic Channel on F3)
Disables periodic search (target Active Set;
Saves current configuration. PERIODIC_SEARCH = ‘1’;
Active Set. (Maintains Forward and Rev-
erse Traffic Channels on F1)
2 Figure B-17. Call Flow for Periodic Search on F2 from F1, Successful Handoff
3 to F3, Continued Periodic Search on F2 from F3 (Part 1 of 2)
B-31
3GPP2 C.S0005-A v6.0

• Tunes to F3.
Active Set.
Initializes and enables (Discontinues use of Active Set
periodic search timer. on F1)

on F3) on F3)
.
.
on F2)
.
.
(Continues communication
on F3)
2 Figure B-17. Call Flow for Periodic Search on F2 from F1, Successful Handoff
3 to F3, Continued Periodic Search on F2 from F3 (Part 2 of 2)
B-32
3GPP2 C.S0005-A v6.0

• Packet arrives.
with “High Speed Packet
Service Option.”
Channel data.
Message
(GRANTED_MODE = ‘01’).
valid frames.
• Sends Service Request > Reverse Traffic >
Message (FOR_MUX_OPTION Channel
and REV_MUX_OPTION
indicates max number of
Supplemental Code
Channels).
Service Option n.
• Sends packet. > Reverse >
Fundamental
Channel
< Forward < • Sends packet.
Fundamental
Channel
3 on Forward Supplemental Code Channels (Part 1 of 2)
B-33
3GPP2 C.S0005-A v6.0

• Base station decides that it

requires to change the
number of Supplemental
Channels (e.g., it has a
“large” packet to send).
< Forward < • Send Supplemental Channel
Fundamental Assignment Message.
Channel
< Forward < • Begin transmitting on the
Fundamental Supplemental Code Channels
and for the duration specified in
Supplemental Supplemental Channel
Code Channels Assignment Message.
(User traffic) (User traffic)
3 on Forward Supplemental Code Channels (Part 2 of 2)
B-34
3GPP2 C.S0005-A v6.0

• Packet arrives.
with “High Speed Packet
Service Option.”
Channel data.
Message
valid frames.
• Sends Service Request > Reverse Traffic >
Message (FOR_MUX_OPTION Channel
and REV_MUX_OPTION
indicates max number of
Supplemental Code
Channels).
Service Option n.
• Sends packet. > Reverse >
Fundamental
Channel
< Forward < • Sends packet.
Fundamental
Channel
3 on Reverse Supplemental Code Channels (Part 1 of 2)
B-35
3GPP2 C.S0005-A v6.0

• Mobile station has a “large”

packet to send.
• Continue transmitting on the > Reverse >
Fundamental Channel. Fundamental
Channel
• Sends Supplemental Channel > Reverse >
Request Message. Fundamental
Channel
Channel
• Begins transmitting on the > Reverse >
Reverse Supplemental Code Fundamental &
Channels. Supplemental
Code Channels
3 on Reverse Supplemental Code Channels (Part 2 of 2)
B-36
3GPP2 C.S0005-A v6.0

• Packet arrives.
Message with “High Speed
Packet Service Option.”
• Sends Page Response > Access Channel > • Sets up Traffic Channel
Message.
Channel data.
• Sets up Traffic Channel. < Paging Channel < • Sends Extended Channel
Assignment Message
valid frames.
• Begins sending the Traffic • Acquires the Reverse
Channel preamble. Fundamental Channel.
• Begins transmitting null < Forward < • Sends Base Station
Traffic Channel data. Fundamental Acknowledgment Order.
Channel
• Processes Service Request < Forward • Sends Service Request
Message. Fundamental Message
Channel (FOR_MUX_OPTION and
REV_MUX_OPTION
indicates the maximum
Forward and Reverse Code
Channels).
2 Figure B-20. Simple Call Flow, Mobile Station Termination Example with
3 Transmission on Forward Supplemental Code Channel(s) (Part 1 of 3)
B-37
3GPP2 C.S0005-A v6.0

• Sends Service Response > Reverse >

Message to accept Service Fundamental
Option with Channel
FOR_MUX_OPTION and
REV_MUX_OPTION to
indicate the maximum
Channels supported by the
mobile station.
• Begins processing primary < Forward < • Sends Service Connect
traffic in accordance with Fundamental Message.
Service Option and multiplex Channel
option.
• Sends Service Connect > Reverse >
Completion Message. Fundamental
Channel
• Sends packet, if any, on the > Reverse >
Fundamental Channel. Fundamental
Channel
< Forward < • Sends packet, if any, on the
Fundamental Fundamental Channel.
Channel
B-38
3GPP2 C.S0005-A v6.0

(Continued from previous page) (Continued from previous
page)
• Base station decides

that it requires to use
Supplemental Channels
to send a “large” packet.
< Forward < • Sends Supplemental
Fundamental Channel Assignment
Channel Message.
• Begins processing packet data < Forward < • Begins transmitting on the
received from Forward Fundamental & Supplemental Code
Fundamental and Supplemental Channel(s) for the duration
Supplemental Code Code Channels specified in Supplemental
Channel(s). Channel Assignment
Message.
B-39
3GPP2 C.S0005-A v6.0

• Packet arrives
Message with “High Speed
Packet Service Option.”
Channel data.
• Sets up Traffic Channel. < Paging Channel < • Sends Extended Channel
Assignment Message
valid frames.
• Begins sending the Traffic
Channel preamble. • Acquires the Reverse
Fundamental Channel.
• Begins transmitting null < Forward < • Sends Base Station
Traffic Channel data. Fundamental Acknowledgment Order.
Channel
• Processes Service Request < Forward < • Sends Service Request
Message. Fundamental Message
Channel (FOR_MUX_OPTION and
REV_MUX_OPTION
proposes the maximum
Channels to be used).
3 Transmission on Reverse Supplemental Code Channel(s) (Part 1 of 3)
B-40
3GPP2 C.S0005-A v6.0

page)
• Sends Service Response > Reverse >

Message to accept Service Fundamental
Option, with Channel
FOR_MUX_OPTION and
REV_MUX_OPTION to
indicate the maximum
Code Channels supported by
the mobile station.
• Begins processing primary < Forward < • Sends Service Connect
traffic in accordance with the Fundamental Message to connect
service configuration. Channel corresponding SO, with
FOR_MUX_OPTION and
REV_MUX_OPTION to
specify the maximum
Code Channel(s) mutually
supported.
• Sends Service Connect > Reverse >

Completion Message. Fundamental
Channel
• Sends packet data. > Reverse >
Fundamental
Channel
< Forward < • Sends packet data.
Fundamental
Channel
• Mobile station has a “large” > Reverse >
packet to send, so begins Fundamental
transmitting packet. Channel
B-41
3GPP2 C.S0005-A v6.0

page)
• Sends Supplemental Channel > Reverse >

Request Message, and Fundamental
continues transmitting on Channel
the Reverse Fundamental
Channel.
Channel
• Begins transmitting on the > Reverse >
Reverse Supplemental Code Fundamental
Channel(s), in addition to and
continuing on the Reverse Supplemental
Fundamental Channel. Code Channels
B-42
3GPP2 C.S0005-A v6.0
MS L3 BS L3
Active/Control Hold Active/Control Hold
ERM (CH_IND) /
ERMM (CH_IND) /
Release Order
CH_IND includes all
channels currently
being processed
ERRM /
ERRMM /
Release Order
MS releases the BS releases the
physical channels physical channels
Idle Idle
1
2
3 Figure B-22. Active/Control Hold to Idle State Transition; Release all services (BS
4 Initiated)
B-43
3GPP2 C.S0005-A v6.0
MS L3 BS L3
Active/Control Hold Active/Control Hold
Release Order
Release Order
MS releases the BS releases the

physical channels physical channels
Idle Idle
1
2
3 Figure B-23. Active/Control Hold to Idle State Transition; Release all services (MS
4 Initiated)
B-44
3GPP2 C.S0005-A v6.0
MS L3 BS L3
Active Active
ERM (CH_IND) /
ERMM (CH_IND) /
UHDM (CH_IND) CH_IND is a subset of
the channles currently
being processed
ERRM /
ERRMM /
MS stops transmitting/ HCM
processing on the
indicated channels
and starts reverse pilot
gating at the action time
Control Hold Control Hold
2 Figure B-24. Active to Control Hold State Transition (BS Initiated)
B-45
3GPP2 C.S0005-A v6.0
MS L3 BS L3
Active Active
RRRM (GATING_DISCONNECT_IND=1)/
RRRMM (GATING_DISCONNECT_IND=1)
ERM (CH_IND) /
ERMM (CH_IND) /
CH_IND is a subset of
UHDM (CH_IND)
the channles currently
being processed
ERRM /
ERRMM/
MS stops transmitting/ HCM
processing on the
indicated channels
and starts reverse pilot
gating at the action time
2 Figure B-25. Active to Control Hold State Transition (MS Initiated)
B-46
3GPP2 C.S0005-A v6.0
MS L3 BS L3
RAM /
RAMM /
UHDM /
ESCAM /
FSCAMM /
RSCAMM
MS starts transmitting/
processing on the
indicated channels and
starts continuous reverse
pilot at action time
Active Active
2 Figure B-26. Control Hold to Active Transition (BS Initiated)

3
B-47
3GPP2 C.S0005-A v6.0
MS L3
BS L3
RRM /
RRMM /
SCRM /
SCRMM
RAM /
RAMM /
UHDM /
ESCAM /
FSCAMM /
MS starts transmitting/ RSCAMM
processing on the indicated
channels and starts
continuous reverse pilot at
the action time
Active Active
4 Figure B-27. Control Hold to Active Transition (MS Initiated)
B-48
3GPP2 C.S0005-A v6.0
MS L3 BS L3
Traffic Traffic
Enhanced Origination Message

(SOY, TAGY, {Dialed Digits})
L3 instantiates a
CC state machine, Call Assignment Message
identified by (RESPONSE_IND=1,
CON_REFY TAGY, CON_REFY)
SCM / GHDM / UHDM

(SCR += (SOY, CON_REFY)
OR
L3 instantiates a
CC state machine SCM / GHDM / UHDM
identified by (CC_INFO_INCL=1,
RESPONSE_IND=1, TAGY
CON_REFY SCR += (SOY, CON_REFY))
Traffic Traffic
3 Figure B-28. Connecting an Additional Service (MS Initiated)
B-49
3GPP2 C.S0005-A v6.0
MS L3 BS L3
Traffic Traffic
L3 instantiates a
CC state machine Call Assignment Message
identified by (RESPONSE_IND=0,
CON_REFY SOY, CON_REFY)
SCM / GHDM / UHDM

(SCR += (SOY, CON_REFY)
OR
L3 instantiates a
CC state machine SCM / GHDM / UHDM
identified by (CC_INFO_INCL=1, RESPONSE_IND=0,
CON_REFY SCR += (SOY, CON_REFY))
Traffic Traffic
2 Figure B-29. Connecting an Additional Service (BS Initiated)
B-50
3GPP2 C.S0005-A v6.0
MS L3 BS L3
Traffic Traffic
SReqM (SCR -= CON_REFY) /

RRRM (CON_REFY) /
RRRMM (CON_REFY)
L3 terminates CC state
machine identified by SCM / GHDM / UHDM
CON_REFY (SCR -= CON_REFY)
Traffic Traffic
3 Figure B-30. Releasing a Service that is not the last one connected (MS Initiated)
B-51
3GPP2 C.S0005-A v6.0
MS L3 BS L3
Traffic Traffic
L3 terminates CC state
machine identified by SCM / GHDM / UHDM
CON_REFY (SCR -= CON_REFY)
Traffic Traffic
3 Figure B-31. Releasing a Service that is not the last one connected (BS Initiated)
B-52
3GPP2 C.S0005-A v6.0
1 ANNEX C RESERVED
C-1
3GPP2 C.S0005-A v6.0
1 No text.
C-2
3GPP2 C.S0005-A v6.0
1 ANNEX D CDMA CONSTANTS
2 Annex D is a normative annex which contains tables that give specific values for the
3 constant identifiers. These identifiers take the forms such as T20m and N5m. The
4 subscripted numbers vary to identify the particular constant. Typically the subscripted
5 letter “m” refers to the mobile station and the subscripted letter “b” refers to the base
6 station. The following tables provide values for identifiers given in the text:
7 Table D-1. Time Limits
8 Table D-2. Other Constants

9
10 Table D-1. Time Limits (Part 1 of 5)
Time
Description Value References
Limit
T5m Limit of the Forward Traffic Channel fade timer 5s 2.6.4.1.8
T20m Maximum time to remain in the Pilot Channel 15 s 2.6.1.2
Acquisition Substate of the Mobile Station
Initialization State
T21m Maximum time to receive a valid Sync Channel 1s 2.6.1.3
message
T30m Maximum time to receive a valid Paging Channel or 3s 2.6.2.1.1.1
Forward Common Control Channel/Broadcast
Control Channel message
T31m Maximum time for which configuration parameters 600 s 2.6.2.2
are considered valid
11
D-1
3GPP2 C.S0005-A v6.0
Time
Limit
T32m Maximum time to enter the Update Overhead 5s 2.6.2.4
Information Substate of the System Access State to 2.6.4
respond to an SSD Update Message, Base Station
Challenge Confirmation Order, and Authentication
Challenge Message
T33m Maximum time to enter the Update Overhead 0.3 s 2.6.2
Information Substate of the System Access State 2.6.5.5.2.3
(except in response to authentication messages)
T34m 3s 2.6.3.3
Maximum time to enter the Update Overhead
Information Substate or the Mobile Station Idle State
after receiving a Channel Assignment Message with
ASSIGN_MODEr equal to ‘001’ or ‘101’ or Extended
Channel Assignment Message with ASSIGN_MODEr
equal to ‘001’
T40m Maximum time to receive a valid Paging Channel or 3s 2.6.3.1.8
Control Channel message before aborting an access
attempt (see T72m)
T41m Maximum time to obtain updated overhead 4s 2.6.3.2
messages arriving on the Paging Channel or
Broadcast Control Channel
T42m Maximum time to receive a delayed lLayer 3 12 s 2.6.3.1.1.2
response following the receipt of an 2.6.3.3
acknowledgment for an access probe in the System 2.6.3.5
Access State. 2.6.4
The maximum time to receive a lLayer 3 response to
an Enhanced Origination Message on the Mobile
Station Control on the Traffic Channel State.
T50m Maximum time to obtain N5m consecutive good 1s 2.6.4.2
Forward Traffic Channel frames when in the Traffic
Channel Initialization Substate of the Mobile Station
Control on the Traffic Channel State
T51m Maximum time for the mobile station to receive a 2s 2.6.4.2
Base Station Acknowledgment Order after the first
occurrence of receiving N5m consecutive good
frames when in the Traffic Channel Initialization
Substate of the Mobile Station Control on the Traffic
Channel State
D-2
3GPP2 C.S0005-A v6.0
T52m Maximum time to receive a message in the Waiting 5s 2.6.10.1.1

for Order Substate of the Call Control processing
that transits Call Control instance to a different
substate or state
D-3
3GPP2 C.S0005-A v6.0
Time
Limit
T53m Maximum time to receive a message in the Waiting 65 s 2.6.10.1.2
for Mobile Station Answer Substate of Call Control
processing that transits the Call Control instance to
a different substate or state
T54m Maximum time for the Call Control instance to send 0.2 s 2.6.10.2
an Origination Continuation Message upon entering
the Conversation Substate
T55m Maximum time to receive a message in the Release 2s 2.6.4.5
Substate of the Mobile Station Control on the Traffic
Channel State that transits the mobile station to a
different substate or state
T56m Default maximum time to respond to a received 0.2 s 2.6.4
message or order on the Forward Traffic Channel 2.6.6
T57m Limit of the power-up registration timer 20 s 2.6.5.1.1
2.6.5.5.1.3
T58m Maximum time for the mobile station to respond to 5s 2.6.4.1.2.2
a service option request
T59m Maximum time for the mobile station to respond to 5s 2.6.4.1.2.2
a Service Request Message or a Service Response
Message
T60m Maximum time to execute a hard handoff without 0.06 s 2.6.6.2.8.1
return on failure involving a new frequency
assignment using the same base station
return on failure involving a new frequency
assignment using a different base station
D-4
3GPP2 C.S0005-A v6.0
Time
Limit
return on failure involving the same frequency
assignment
T63m Maximum time to execute a CDMA-to-Analog 0.1 s 2.6.6.2.9
handoff
T64m Maximum time to wait for a Base Station Challenge 10 s 2.3.12.1.5
Confirmation Order
T65m Maximum time for the mobile station to wait for a 5s 2.6.4.1.2.2.4
Service Connect Message while the Waiting for
Service Connect Message Subfunction is active
T66m Maximum time for the mobile station to delete the 200 s 2.6.2
TMSI after TMSI expiration time has exceeded the
System Time
T68m Maximum time for the mobile station to wait for a 5s 2.6.4.1.2.2.2
Service Request Message, Service Response 2.6.4.1.2.2.3
Message, or Service Connect Message while the
Waiting for Service Request Message Subfunction or
Waiting for Service Response Message Subfunction is
active
T69m Fixed portion of the full-TMSI timer 24 s 2.6.3.1.6
T70m Maximum time between the mobile station’s 0.8 s 2.6.6.2.8.3
obtaining a measurement and sending a Candidate 2.6.6.2.10
Frequency Search Report Message which contains
that measurement
T71m Maximum time for the mobile station to send a 0.04 s 2.6.6.2.8.3
Candidate Frequency Search Report Message after
completing a search
T72m Maximum time to receive a valid Paging Channel or 1s 2.6.3.1.8
Control Channel message before aborting an access
attempt, when there exists at least one access
handoff candidate pilot for the access attempt (see
also T40m)
T73m Maximum time for the mobile station to send a 0.3s 2.6.6.2.5.2
Handoff Completion Message after the action time of
a received handoff message directing the mobile
station to perform a hard handoff without return on
failure
T74m Default value of the slotted timer 0.0s 2.6.4.2
D-5
3GPP2 C.S0005-A v6.0
Time
Limit
T1b Maximum period between subsequent 1.28 s 3.6.2.2
transmissions of an overhead message on the
Paging Channel by the base station
T2b Maximum time for the base station to send a 0.8 s 3.6.4
Release Order after receiving a Release Order
T3b Minimum time the base station continues to 0.3 s 3.6.4.5
transmit on a code channel after sending or
receiving a Release Order
T4b Maximum time for the base station to respond to a 5s 3.6.4.1.2.2.1
service option request
D-6
3GPP2 C.S0005-A v6.0
1 Table D-2. Other Constants
Con-
stant Description Value References
N2m The duration, of insufficient signal quality (e.g. bad 12 2.6.4.1.8

frames), in units of 20ms, received on the Forward
Traffic Channel before a mobile station must disable
its transmitter
N3m The duration, of sufficient signal quality (e.g. good 2
frames), in units of 20ms, received on the Forward 2.6.4.1.8
Traffic Channel before a mobile station is allowed to
re-enable its transmitter after disabling its
transmitter
N4m Reserved
N5m The duration, of sufficient signal quality (e.g. good 2 2.6.4.2
Traffic Channel before a mobile station is allowed to
enable its transmitter after entering the Traffic
Channel Initialization Substate of the Mobile Station
Control on the Traffic Channel State
N6m Supported Traffic Channel Active Set size 6 2.6.6.2.6.1
3.6.6.2.2.2
3.6.6.2.2.10
N7m Supported Traffic Channel Candidate Set size 10 2.6.6.2.6.2
N8m Minimum supported Neighbor Set size 40 2.6.2.1.4.1
2.6.2.2.3
2.6.6.2.6.3
3.6.6.2.1.2
3.6.6.2.1.3
N9m Minimum supported zone list size 7 2.6.5.1.5
N10m SID/NID list size 4 2.6.5
N11m The duration, of sufficient signal quality (e.g. good 1 2.6.6.2.8
Traffic Channel before a mobile station re-enables
its transmitter after disabling its transmitter during
a CDMA-to-CDMA Hard Handoff
N12m Number of frames over which the mobile station 10 2.6.6.2.8.3
maintains a running average of the total received
power
N13m Maximum number of pilots reported in an Access 6 2.6.3.1.7
Channel message 2.7.1.3.1.3
D-7
3GPP2 C.S0005-A v6.0
2 No text.
3
D-8
3GPP2 C.S0005-A v6.0
1 ANNEX E CDMA RETRIEVABLE AND SETTABLE PARAMETERS
2 This is a normative annex which describes the parameters that can be retrieved and set in
3 the mobile station using the Retrieve Parameters Message, the Parameters Response
4 Message, and the Set Parameters Message.
5 PARAMETER_ID values from 0 through 32767 are reserved for definition by this standard
6 and shall not be defined by mobile station manufacturers. PARAMETER_ID values from
7 32768 through 65535 may be defined by mobile station manufacturers.
E-1
3GPP2 C.S0005-A v6.0
Table E-1. Retrievable and Settable Parameters (Part 1 of 19)
Value of Length (bits)

Parameter Identifier PARA- (PARA- Support Settable
Reference
METER_ID METER_LEN is Required? Parameter?
Section
(decimal) Length - 1) (Y or N) (Y or N)
MUX1_REV_FCH_1 1 24 Y Y [3]
MUX1_REV_FCH_9 9 N/A N/A N/A [3]
MUX1_REV_FCH_11 11 24 N Y [3]
MUX1_REV_FCH_12 12 24 N Y [3]
MUX1_REV_FCH_13 13 24 N Y [3]
MUX1_REV_FCH_14 14 24 N Y [3]
MUX1_FOR_FCH_1 15 24 Y Y [3]
MUX1_FOR_FCH_2 16 24 Y Y [3]
MUX1_FOR_FCH_3 17 24 Y Y [3]
MUX1_FOR_FCH_4 18 24 Y Y [3]
MUX1_FOR_FCH_5 19 24 Y Y [3]
MUX1_FOR_FCH_6 20 24 Y Y [3]
MUX1_FOR_FCH_7 21 24 Y Y [3]
MUX1_FOR_FCH_8 22 24 Y Y [3]
E-2
3GPP2 C.S0005-A v6.0

Reference
METER_ID METER_LEN Required? Parameter?
Section
(decimal) is Length - 1) (Y or N) (Y or N)
MUX1_FOR_FCH_9 23 24 Y Y [3]
MUX1_FOR_FCH_10 24 24 Y Y [3]
MUX1_FOR_FCH_11 25 24 N Y [3]
MUX1_FOR_FCH_12 26 24 N Y [3]
MUX1_FOR_FCH_13 27 24 N Y [3]
MUX1_FOR_FCH_14 28 24 N Y [3]
PAG_1 29 24 Y Y [4]
PAG_2 30 24 Y Y [4]
PAG_3 31 16 Y Y [4]
PAG_4 32 24 Y Y [4]
PAG_5 33 24 Y Y [4]
PAG_6 34 16 Y Y 2.4
PAG_7 35 16 Y Y 2.4
ACC_1 36 16 Y Y [4]
ACC_2 37 16 Y Y [4]
ACC_3 38 16 Y Y [4]
ACC_4 39 16 Y Y [4]
ACC_5 40 16 Y Y [4]
ACC_6 41 16 Y Y [4]
ACC_7 42 16 Y Y [4]
ACC_8 43 16 Y Y [4]
LAYER2_RTC1 44 16 Y Y [4]
OTHER_SYS_TIME 49 36 Y N 2.4
E-3
3GPP2 C.S0005-A v6.0

Reference
Section
MUX2_REV_FCH_1 50 24 Y Y [3]
MUX2_REV_FCH_2 51 24 Y Y [3]
MUX2_REV_FCH_3 52 24 Y Y [3]
MUX2_REV_FCH_4 53 24 Y Y [3]
MUX2_REV_FCH_5 54 24 Y Y [3]
MUX2_REV_FCH_6 55 24 Y Y [3]
MUX2_REV_FCH_7 56 24 Y Y [3]
MUX2_REV_FCH_8 57 24 Y Y [3]
MUX2_REV_FCH_9 58 24 Y Y [3]
MUX2_REV_FCH_10 59 24 Y Y [3]
MUX2_REV_FCH_11 60 24 Y Y [3]
MUX2_REV_FCH_12 61 24 Y Y [3]
MUX2_REV_FCH_13 62 24 Y Y [3]
MUX2_REV_FCH_14 63 24 Y Y [3]
MUX2_REV_FCH_15 64 24 Y Y [3]
MUX2_REV_FCH_16 65 24 Y Y [3]
MUX2_REV_FCH_17 66 24 Y Y [3]
MUX2_REV_FCH_18 67 24 Y Y [3]
MUX2_REV_FCH_19 68 24 Y Y [3]
MUX2_REV_FCH_20 69 24 Y Y [3]
MUX2_REV_FCH_21 70 24 Y Y [3]
MUX2_REV_FCH_22 71 24 Y Y [3]
MUX2_REV_FCH_23 72 24 Y Y [3]
MUX2_REV_FCH_24 73 24 Y Y [3]
MUX2_REV_FCH_25 74 24 Y Y [3]
E-4
3GPP2 C.S0005-A v6.0

Reference
Section
MUX2_FOR_FCH_1 76 24 Y Y [3]
MUX2_FOR_FCH_2 77 24 Y Y [3]
MUX2_FOR_FCH_3 78 24 Y Y [3]
MUX2_FOR_FCH_4 79 24 Y Y [3]
MUX2_FOR_FCH_5 80 24 Y Y [3]
MUX2_FOR_FCH_6 81 24 Y Y [3]
MUX2_FOR_FCH_7 82 24 Y Y [3]
MUX2_FOR_FCH_8 83 24 Y Y [3]
MUX2_FOR_FCH_9 84 24 Y Y [3]
MUX2_FOR_FCH_10 85 24 Y Y [3]
MUX2_FOR_FCH_11 86 24 Y Y [3]
MUX2_FOR_FCH_12 87 24 Y Y [3]
MUX2_FOR_FCH_13 88 24 Y Y [3]
MUX2_FOR_FCH_14 89 24 Y Y [3]
MUX2_FOR_FCH_15 90 24 Y Y [3]
MUX2_FOR_FCH_16 91 24 Y Y [3]
MUX2_FOR_FCH_17 92 24 Y Y [3]
MUX2_FOR_FCH_18 93 24 Y Y [3]
MUX2_FOR_FCH_19 94 24 Y Y [3]
MUX2_FOR_FCH_20 95 24 Y Y [3]
MUX2_FOR_FCH_21 96 24 Y Y [3]
MUX2_FOR_FCH_22 97 24 Y Y [3]
MUX2_FOR_FCH_23 98 24 Y Y [3]
MUX2_FOR_FCH_24 99 24 Y Y [3]
MUX2_FOR_FCH_25 100 24 Y Y [3]
MUX2_FOR_FCH_26 101 24 Y Y [3]
E-5
3GPP2 C.S0005-A v6.0

Reference
Section
SCCH1_REV_S 102 24 Y Y [3]

SCCH1_REV_P 103 24 Y Y [3]
SCCH2_REV_S 104 24 Y Y [3]
SCCH2_REV_P 105 24 Y Y [3]
SCCH3_REV_S 106 24 Y Y [3]
SCCH3_REV_P 107 24 Y Y [3]
SCCH4_REV_S 108 24 Y Y [3]
SCCH4_REV_P 109 24 Y Y [3]
SCCH5_REV_S 110 24 Y Y [3]
SCCH5_REV_P 111 24 Y Y [3]
SCCH6_REV_S 112 24 Y Y [3]
SCCH6_REV_P 113 24 Y Y [3]
SCCH7_REV_S 114 24 Y Y [3]
SCCH7_REV_P 115 24 Y Y [3]
SCCH1_FOR_S 116 24 Y Y [3]
SCCH1_FOR_P 117 24 Y Y [3]
SCCH2_FOR_S 118 24 Y Y [3]
SCCH2_FOR_P 119 24 Y Y [3]
SCCH3_FOR_S 120 24 Y Y [3]
SCCH3_FOR_P 121 24 Y Y [3]
SCCH4_FOR_S 122 24 Y Y [3]
SCCH4_FOR_P 123 24 Y Y [3]
SCCH5_FOR_S 124 24 Y Y [3]
SCCH5_FOR_P 125 24 Y Y [3]
SCCH6_FOR_S 126 24 Y Y [3]
SCCH6_FOR_P 127 24 Y Y [3]
SCCH7_FOR_S 128 24 Y Y [3]
SCCH7_FOR_P 129 24 Y Y [3]
E-6
3GPP2 C.S0005-A v6.0

Reference
Section
MM_RTC1 130 16 Y Y [4]

MM_RTC2 131 16 Y Y [4]
MM_RTC3 132 16 Y Y [4]
MM_RTC4 133 16 Y Y [4]
MM_RTC5 134 16 Y Y [4]
MUX1_REV_FCH_5_ms 136 24 N Y [3]
MUX1_FOR_FCH_15 137 N/A N/A N/A [3]
MUX1_FOR_FCH_5_ms 138 24 N Y [3]
MUX2_REV_FCH_5_ms 140 24 N Y [3]
MUX2_FOR_FCH_27 141 N/A N/A N/A [3]
MUX2_FOR_FCH_5_ms 142 24 N Y [3]
MUX1_REV_DCCH_1 143 24 Y Y [3]
MUX1_REV_DCCH_6 148 N/A N/A N/A [3]
MUX1_REV_DCCH_11 153 24 N Y [3]
MUX1_REV_DCCH_12 154 24 N Y [3]
MUX1_REV_DCCH_13 155 24 N Y [3]
MUX1_REV_DCCH_14 156 24 N Y [3]
E-7
3GPP2 C.S0005-A v6.0

Reference
Section
MUX1_REV_DCCH_15 157 24 Y Y [3]

MUX1_REV_DCCH_5_ms 158 24 N Y [3]
MUX1_FOR_DCCH_1 159 24 Y Y [3]
MUX1_FOR_DCCH_6 164 N/A N/A N/A [3]
MUX1_FOR_DCCH_9 167 24N/A YN/A YN/A [3]
MUX1_FOR_DCCH_10 168 24 Y Y [3]
MUX1_FOR_DCCH_11 169 24 N Y [3]
MUX1_FOR_DCCH_12 170 24 N Y [3]
MUX1_FOR_DCCH_13 171 24 N Y [3]
MUX1_FOR_DCCH_14 172 24 N Y [3]
MUX1_FOR_DCCH_15 173 24 Y Y [3]
MUX1_FOR_DCCH_5_ms 174 24 N Y [3]
E-8
3GPP2 C.S0005-A v6.0

Reference
Section
MUX2_REV_DCCH_10 184 24 Y Y [3]

MUX2_REV_DCCH_27 201 24 Y Y [3]
MUX2_REV_DCCH_5_ms 202 24 N Y [3]
E-9
3GPP2 C.S0005-A v6.0

Reference
Section
MUX2_FOR_DCCH_10 212 24 Y Y [3]

MUX2_FOR_DCCH_26 228 24 Y Y [3]
MUX2_FOR_DCCH_27 229 24 Y Y [3]
MUX2_FOR_DCCH_5_ms 230 24 N Y [3]
SCH0_REV_1X 231 24 Y Y [3]
SCH0_REV_2X 232 24 Y Y [3]
SCH0_REV_4X 233 24 Y Y [3]
SCH0_REV_8X 234 24 Y Y [3]
SCH0_REV_16X 235 24 Y Y [3]
SCH0_REV_LTU 236 24 Y Y [3]
SCH0_REV_LTUOK 237 N/A N/A N/A [3]
SCH1_REV_1X 238 24 Y Y [3]
SCH1_REV_2X 239 24 Y Y [3]
E-10
3GPP2 C.S0005-A v6.0

Reference
Section
SCH1_REV_4X 240 24 Y Y [3]

SCH1_REV_8X 241 24 Y Y [3]
SCH1_REV_16X 242 24 Y Y [3]
SCH1_REV_LTU 243 24 Y Y [3]
SCH1_REV_LTUOK 244 N/A N/A N/A [3]
SCH0_FOR_1X 245 24 Y Y [3]
SCH0_FOR_2X 246 24 Y Y [3]
SCH0_FOR_4X 247 24 Y Y [3]
SCH0_FOR_8X 248 24 Y Y [3]
SCH0_FOR_16X 249 24 Y Y [3]
SCH0_FOR_LTU 250 24 Y Y [3]
SCH0_FOR_LTUOK 251 24 Y Y [3]
SCH1_FOR_1X 252 24 Y Y [3]
SCH1_FOR_2X 253 24 Y Y [3]
SCH1_FOR_4X 254 24 Y Y [3]
SCH1_FOR_8X 255 24 Y Y [3]
SCH1_FOR_16X 256 24 Y Y [3]
SCH1_FOR_LTU 257 24 Y Y [3]
SCH1_FOR_LTUOK 258 24 Y Y [3]
BCCH_1 259 24 Y Y [4]
BCCH_2 260 24 Y Y [4]
BCCH_3 261 24 Y Y [4]
BCCH_4 262 24 Y Y [4]
BCCH_5 263 16 Y Y 2.4
FCCCH_1 264 24 Y Y [4]
FCCCH_2 265 24 Y Y [4]
FCCCH_3 266 16 Y Y [4]
FCCCH_4 267 24 Y Y 2.4
E-11
3GPP2 C.S0005-A v6.0

Reference
Section
MUX_FLEX_RFCH_1 268 24 N Y [3]

E-12
3GPP2 C.S0005-A v6.0

Reference
Section

MUX_FLEX_RDCCH_1 300 24 N Y [3]
E-13
3GPP2 C.S0005-A v6.0

Reference
Section

RSCH0_1 332 24 N Y [3]
RSCH0_2 333 24 N Y [3]
RSCH0_3 334 24 N Y [3]
RSCH0_4 335 24 N Y [3]
RSCH0_5 336 24 N Y [3]
RSCH0_6 337 24 N Y [3]
RSCH0_7 338 24 N Y [3]
RSCH0_8 339 24 N Y [3]
RSCH0_9 340 24 N Y [3]
RSCH0_10 341 24 N Y [3]
RSCH0_11 342 24 N Y [3]
RSCH0_12 343 24 N Y [3]
RSCH0_13 344 24 N Y [3]
RSCH0_14 345 24 N Y [3]
RSCH0_15 346 24 N Y [3]
RSCH0_16 347 24 N Y [3]
RSCH0_LTU 348 24 N Y [3]
E-14
3GPP2 C.S0005-A v6.0

Reference
Section
RSCH1_1 349 24 N Y [3]

RSCH1_2 350 24 N Y [3]
RSCH1_3 351 24 N Y [3]
RSCH1_4 352 24 N Y [3]
RSCH1_5 353 24 N Y [3]
RSCH1_6 354 24 N Y [3]
RSCH1_7 355 24 N Y [3]
RSCH1_8 356 24 N Y [3]
RSCH1_9 357 24 N Y [3]
RSCH1_10 358 24 N Y [3]
RSCH1_11 359 24 N Y [3]
RSCH1_12 360 24 N Y [3]
RSCH1_13 361 24 N Y [3]
RSCH1_14 362 24 N Y [3]
RSCH1_15 363 24 N Y [3]
RSCH1_16 364 24 N Y [3]
RSCH1_LTU 365 24 N Y [3]
E-15
3GPP2 C.S0005-A v6.0

Reference
Section
MUX_FLEX_FFCH_1 366 24 N Y [3]

E-16
3GPP2 C.S0005-A v6.0

Reference
Section

MUX_FLEX_FDCCH_1 398 24 N Y [3]
E-17
3GPP2 C.S0005-A v6.0

Reference
Section

FSCH0_1 430 24 N Y [3]
FSCH0_2 431 24 N Y [3]
FSCH0_3 432 24 N Y [3]
FSCH0_4 433 24 N Y [3]
FSCH0_5 434 24 N Y [3]
FSCH0_6 435 24 N Y [3]
FSCH0_7 436 24 N Y [3]
FSCH0_8 437 24 N Y [3]
FSCH0_9 438 24 N Y [3]
FSCH0_10 439 24 N Y [3]
FSCH0_11 440 24 N Y [3]
FSCH0_12 441 24 N Y [3]
FSCH0_13 442 24 N Y [3]
FSCH0_14 443 24 N Y [3]
E-18
3GPP2 C.S0005-A v6.0

Reference
Section
FSCH0_15 444 24 N Y [3]

FSCH0_16 445 24 N Y [3]
FSCH0_LTU 446 24 N Y [3]
FSCH0_LTUOK 447 24 N Y [3]
FSCH1_1 448 24 N Y [3]
FSCH1_2 449 24 N Y [3]
FSCH1_3 450 24 N Y [3]
FSCH1_4 451 24 N Y [3]
FSCH1_5 452 24 N Y [3]
FSCH1_6 453 24 N Y [3]
FSCH1_7 454 24 N Y [3]
FSCH1_8 455 24 N Y [3]
FSCH1_9 456 24 N Y [3]
FSCH1_10 457 24 N Y [3]
FSCH1_11 458 24 N Y [3]
FSCH1_12 459 24 N Y [3]
FSCH1_13 460 24 N Y [3]
FSCH1_14 461 24 N Y [3]
FSCH1_15 462 24 N Y [3]
FSCH1_16 463 24 N Y [3]
FSCH1_LTU 464 24 N Y [3]
FSCH1_LTUOK 465 24 N Y [3]
MUX_FLEX_RFCH_5_ms 466 24 N Y [3]
MUX_FLEX_FFCH_5_ms 467 24 N Y [3]
MUX_FLEX- 468 24 N Y [3]
_RDCCH_5_ms
MUX_FLEX- 469 24 N Y [3]
_FDCCH_5_ms
E-19
3GPP2 C.S0005-A v6.0
E-20
3GPP2 C.S0005-A v6.0

Reference
Section
EACH_BA_1 470 16 Y Y [4]

EACH_BA_2 471 16 Y Y [4]
EACH_BA_3 472 16 Y Y [4]
EACH_BA_4 473 16 Y Y [4]
EACH_BA_5 474 16 Y Y [4]
EACH_BA_6 475 16 Y Y [4]
EACH_BA_7 476 16 Y Y [4]
EACH_BA_8 477 16 Y Y [4]
EACH_RA_3 478 16 Y Y [4]
EACH_RA_4 479 16 Y Y [4]
EACH_RA_5 480 16 Y Y [4]
EACH_RA_6 481 16 Y Y [4]
EACH_RA_7 482 16 Y Y [4]
EACH_RA_8 483 16 Y Y [4]
RCCCH_1 484 16 Y Y [4]
RCCCH_2 485 16 Y Y [4]
RCCCH_3 486 16 Y Y [4]
RCCCH_4 487 16 Y Y [4]
RCCCH_5 488 16 Y Y [4]
RCCCH_6 489 16 Y Y [4]
RCCCH_7 490 16 Y Y [4]
RCCCH_8 491 16 Y Y [4]
RCCCH_9 492 16 Y Y [4]
BCCH_6 493 24 Y Y [3]
BCCH_7 494 24 Y Y [3]
BCCH_8 495 24 Y Y [3]
BCCH_9 496 24 Y Y [3]
CACH_1 497 24 Y Y [3]
CACH_2 498 24 Y Y [3]
FCCCH_5 499 24 Y Y [3]
E-21
3GPP2 C.S0005-A v6.0

Reference
Section
FCCCH_6 500 24 Y Y [3]

FCCCH_7 501 24 Y Y [3]
FCCCH_8 502 24 Y Y [3]
FCCCH_9 503 24 Y Y [3]
FCCCH_10 504 24 Y Y [3]
FCCCH_11 505 24 Y Y [3]
SCH0_FOR_32X 506 24 Y Y [3]
SCH1_FOR_32X 507 24 Y Y [3]
SCH0_REV_32X 508 24 Y Y [3]
SCH1_REV_32X 509 24 Y Y [3]
E-22
3GPP2 C.S0005-A v6.0
1 ANNEX F MOBILE STATION DATABASE
2 F.1 Introduction
3 This is an informative annex which lists the numeric indicators that are described by this
4 document and stored in the mobile station’s permanent or semi-permanent memory. Some
5 of these indicators are required; other indicators are optional and are so noted.
6 The indicators are organized in this annex according to two categories:
7 • Mobile station indicators These indicators are global to the mobile station and
8 independent of the mobile station’s NAMs.
9 • NAM indicators These indicators specify parameters associated with the
10 mobile station’s NAM.
11 The description of each indicator below includes the indicator’s name, the number of bits it
12 contains, and the section in this document where it is defined. Permanent indicators are
13 denoted by the “p” subscript; semi-permanent indicators are denoted by the “s-p”
14 subscript.
F-1
3GPP2 C.S0005-A v6.0
1 F.2 Mobile Station Indicators
2 Mobile station indicators are organized into permanent mobile station indicators and semi-
3 permanent mobile station indicators.
4 F.2.1 Permanent Mobile Station Indicators
5 Permanent mobile station indicators specify physical station configuration and attributes,
6 independent of NAM. The indicators are listed in Table F.2.1-1.
8 Table F.2.1-1. Permanent Mobile Station Indicators
Number Where
Indicator Notes
of Bits Defined
ESNp 32 2.3.2 See 2.3.2 for special ESN storage
and protection requirements.
Includes MOB_MFG_CODEp.
SCMp 8 2.3.3
SLOT_CYCLE_INDEXp 3 2.3.11
MOB_FIRM_REVp 16 2.3.14
MOB_MODELp 8 2.3.14
For each band class supported:
MOB_P_REVp 8 2.3.14
F-2
3GPP2 C.S0005-A v6.0
1 F.2.2 Semi-permanent Mobile Station Indicators
2 Semi-permanent mobile station indicators are retained when the mobile station power is
3 turned off. These indicators are associated with mobile station registration and lock. They
4 are independent of the NAM in use. CDMA indicators are listed in Table F.2.2-1.
6 Table F.2.2-1. CDMA Semi-permanent Mobile Station Indicators
Number Where
Indicator Notes
of Bits Defined
ZONE_LISTs-p 2.3.4
REG_ZONEs-p 12 2.3.4
SIDs-p 15 2.3.4
NIDs-p 16 2.3.4
SID_NID_LISTs-p 2.3.4
SIDs-p 15 2.3.4
NIDs-p 16 2.3.4
BASE_LAT_REGs-p 22 2.3.4
BASE_LONG_REGs-p 23 2.3.4
REG_DIST_REGs-p 11 2.3.4
LCKRSN_Ps-p 4 2.3.13
MAINTRSNs-p 4 2.3.13
F-3
3GPP2 C.S0005-A v6.0
1 F.3 NAM Indicators
2 Each mobile station contains one or more NAMs. Table F.3-1 lists the permanent and
3 semi-permanent values associated with each NAM.
5 Table F.3-1. NAM Indicators (Part 1 of 2)
Number Where
Indicator Notes
of Bits Defined
A_KEY 64 2.3.12.1.5
SSD_As-p 64 2.3.12.1.1 Shared Secret Data A
SSD_Bs-p 64 2.3.12.1.1 Shared Secret Data B
COUNTs-p 6 2.3.12.1.3 Call History Parameter
IMSI_M_CLASSp 1 2.3.1
IMSI_T_CLASSp 1 2.3.1
IMSI_M_Sp 34 2.3.1.1 Includes IMSI_M_S1p and
IMSI_M_S2p.
IMSI_T_Sp 34 2.3.1.1 Includes IMSI_T_S1p and IMSI_T_S2p.
IMSI_M_ADDR_NUMp 3 2.3.1 Applies to IMSI_M.
IMSI_T_ADDR_NUMp 3 2.3.1 Applies to IMSI_T.
IMSI_M_11_12p 7 2.3.1.2
IMSI_T_11_12p 7 2.3.1.1
MCC_Mp 10 2.3.1.1
MCC_Tp 10 2.3.1.1
MDNp See 2.3.1.4 An MDN consists of up to 15 digits
Notes based on manufacturer specific
coding.
ASSIGNING_TMSI_ZO 4 23.15.2
NE_LENs-p
ASSIGNING_TMSI_- 64 2.3.15.2
ZONEs-p
TMSI_CODEs-p 32 2.3.15.2
TMSI_EXP_TIMEs-p 24 2.3.15.2
HOME_SIDp 15 2.3.8
F-4
3GPP2 C.S0005-A v6.0
1 Table F.3-1. NAM Indicators (Part 2 of 2)
Number Where
Indicator Notes
of Bits Defined
SIDp 15 2.3.8
NIDp 16 2.3.8
MOB_TERM_HOMEp 1 2.3.8
MOB_TERM_FOR_SIDp 1 2.3.8
MOB_TERM_FOR_NIDp 1 2.3.8
F-5
3GPP2 C.S0005-A v6.0
1 ANNEX G CDMA EXTENDED ENCRYPTION CALL FLOW EXAMPLES
2 This is an informative annex, which contains examples of extended encryption call flow.
3 The diagrams follow these conventions:
4 • All messages are received without error
5 • Acknowledgments are not shown
6 For all the call flow diagrams, the following conventions hold:
7 • The following message acronyms are defined:
8 RGM: Registration Message
9 ORM: Origination Message
10 CAM: Channel Assignment Message
11 ECAM: Extended Channel Assignment Message
12 SMCM: Security Mode Command Message
13 • The following short forms are defined:
14 enc.k1: encrypt the message with key k1
15 csch_enc_req: C_SIG_ENCRYPT_REQ
16 dsch_enc_req: D_SIG_ENCRYPT_REQs
17 csch_enc: C_SIG_ENCRYPT_MODE
18 dsch_enc: D_SIG_ENCRYPT_MODE
19 A <- B: assign value B to variable A
20
G-1
3GPP2 C.S0005-A v6.0
Upon power-up:
C_SIG_ENCRYPT_MODEs <- '000'
ENC_KEY <- NULL MS BS
ENC_KEY = ENC_KEY
null = null
k1 Registration Msg (csch_enc_req = on)
OFF
k1
Reg. Accepted Order (csch_enc = on)
ENC_KEY<-k1
C_SIG_ENCRYPT_MODEs
enc.k1[Some Msg]
ENC_KEY <- k1
ON
enc.k1[ORM(dialed digits,
k2
dsch_enc_req = on)]
k2
enc.k1[CAM/ECAM(dsch_enc = on)]
ENC_KEY<-k2
D_SIG_ENCRYPT_MODEs
enc.k2[Some Msg]
ON
Initial value set by ENC_KEY <- k2

CAM/ECAM
enc.k2[Release Order]
ON
C_SIG_ENCRYPT_MODEs
= successful key exchange = unsuccessful key exchange k = CMEAKEY generated in MS
CMEAKEY obtained
from VLR or AuC
3 Figure G-1. Power-Up Registration, Origination, and Call Release (BS waits for the new
4 CMEKEY before sending CAM/ECAM)
G-2
3GPP2 C.S0005-A v6.0
CAM/ECAM specifies that dsch_enc

= '000' meaning the BS is waiting for
the new key. MS just continues with
the current encryption mode
MS BS
ENC_KEY = k0
ENC_KEY = k0
enc.k0[ORM(dialed digits, dsch_enc_req = on)]
k1
ON
C_SIG_ENCRYPT_MODEs
ON enc.k0[CAM/ECAM(dsch_enc = '000')]
k1
Security Mode Command Message
ENC_KEY<-k1 (dsch_enc = on)
D_SIG_ENCRYPT_MODEs
enc.k1[Some Msg] ENC_KEY <- k1
ON
3 Figure G-2. Quick channel assignment (BS does not wait for the new key before
4 sending CAM/ECAM)
G-3
3GPP2 C.S0005-A v6.0
MS BS
k1 Registration Msg (AUTHR)
Registration Access Substate
Origination Msg (AUTHR)

k2
MS Origination k1
MS sets Attempt Substate
ENC_KEY to the ENC_KEY Registration Accepted Order (csch_enc = '001')
CMEAKEY <- k1
associated with
the Registration
enc-k1(ECAM(dsch_enc = '000'))
Msg
k2
MS Contgrol On
Traffic Channel State Security Mode Command Msg
ENC_KEY (csch_enc/dsch_enc = on)
<- k2
MS BS
k1 Registration Msg (AUTHR)
Registration Access Substate
Origination Msg (AUTHR)

k2
MS Origination k1
Attempt Substate
enc-k1(ECAM(dsch_enc = '000'))
MS Contgrol On k2
Traffic Channel State Security Mode Command Msg
ENC_KEY (csch_enc/dsch_enc = on)
<- k2
BS could skip the Registration

Accepted Order and use the
Security Mode Command Msg
to complete the key exchange
3 Figure G-3. MS Initiates call origination during the Registration Access Substate
G-4
3GPP2 C.S0005-A v6.0
MS BS1 BS2
with new (SID, NID)
ENC_KEY ENC_KEY
KEY = k0
= k0 = null
ON
MS includes
ENC_KEY System Parameters Message csch_enc_req if
C_SIG_ENCRYPT_MODEs
<-null (new SID/NID) ENC_KEY = null
when sending
ORM
OFF
ORM(no dialed digits,

k1 csch_enc_req = on, dsch_enc_req = on)
CAM/ECAM(dsch_enc = '000')
OFF
Security Mode Command Msg k1

ENC_KEY (dsch_enc = on, csch_enc = on)
<- k1
D_SIG_ENCRYPT_MODEs
enc.k1[ORCM (dialed digits)] ENC_KEY <- k1
ON
ON
C_SIG_ENCRYPT_MODEs
3 Figure G-4. Implicit registration (MS crosses a SID/NID boundary during MS Idle
4 State. MS originates before registering)
G-5
3GPP2 C.S0005-A v6.0
MS BS
ENC_KEY = k0 ENC_KEY = k0
KEY lost and/or
KEY lost and/or
Crypto-sync out-
Crypto-sync
of-sync out-
of-sync
ON enc.k0[ORM(dialed digits,
k1 dsch_enc_req = on)]
C_SIG_ENCRYPT_MODEs
ENC_KEY
BS Reject Order (can not decrypt ORM)
<- null BS shall not use
k1 if BS Reject
ORM(no dialed digits, csch_enc_req = on,
Order is sent.
OFF
k2 dsch_enc_req = on)
CAM/ECAM(dsch_enc = '000')
OFF
Security Mode Command Msg k2

D_SIG_ENCRYPT_MODEs ENC_KEY (dsch_enc = on, csch_enc = on)
<- k2
enc.k2[ORCM (dialed digits)]
ON
ENC_KEY
<- k2
ON
C_SIG_ENCRYPT_MODEs
3 Figure G-5. BS lost the stored key (A rare out-of-sync case)
G-6
3GPP2 C.S0005-A v6.0
MS BS
enc.k0[Msg 1]
MS can not
MS can
decrypt msgnot
1
decrypt msg 1
ON
Security Mode Request Msg (24-bit crypto-sync,
csch_enc_req/dsch_enc_req = on)
C_SIG_ENCRYPT_MODEs
or D_SIG_ENCRYPT_MODEs
(csch_enc/dsch_enc = on)
ON
Can decrypt
Can decrypt
now.
now.
Recovered
Recovered
3 Figure G-6. MS fails to decrypt messages (MS recovers by re-synchronizing the crypt-
4 sync)
G-7
3GPP2 C.S0005-A v6.0
MS BS
enc.k0[Msg 1]
MS can not
MS can
decrypt msgnot
1
decrypt msg 1
ON
Security Mode Request Msg (24-bit crtypo-sync,

(dsch_enc/csch_enc = on)
enc.k0[Msg 2]
MS can not
ON
MS can
decrypt msgnot
2
decrypt msg 2
C_SIG_ENCRYPT_MODEs
or D_SIG_ENCRYPT_MODEs System Determination
ENC_KEY<-null
Substate (entered with an
encryption re-sync required
indication)
MS Idle State
OFF
k1 Reg. Msg (csch_enc_req = on)
k1
ENC_KEY Reg. Accepted Order (csch_enc = on)
<-k1
ON
Can decrypt
Can decrypt
now.
now.
Recovered
Recovered
1
3 Figure G-7. MS fails to decrypt messages (MS recovers by re-registering after failing
4 to re-synchronize the crypto-sync)
G-8
3GPP2 C.S0005-A v6.0
MS BS
enc.k0[Msg 1]
BS can not
BS can
decrypt msgnot
1
decrypt msg 1
ON
BS Reject Order (Can not decrypt msg)

C_SIG_ENCRYPT_MODEs csch_enc_req/dsch_enc_req = on)
(csch_enc/dsch_enc = on)
enc.k0[Msg 2]
ON
Can decrypt
Can decrypt
now.
now.
Recovered
Recovered
3 Figure G-8. BS fails to decrypt messages (BS recovers by re-synchronizing the crypt-
4 sync)
G-9
3GPP2 C.S0005-A v6.0
MS BS
enc.k0[Msg 1]
BS can not
BS can
decrypt msgnot
1
decrypt msg 1
ON
BS Reject Order (Can not decrypt msg)
Security Mode Command Msg (dsch_enc/csch_enc = on)
enc.k0[Msg 2]
BS can not
ON
BS can
decrypt msgnot
2
decrypt msg 2
C_SIG_ENCRYPT_MODEs BS Reject Order (Can not decrypt msg)

ENC_KEY<-null
System Determination
Substate (entered with an
encryption re-sync
required indication)
OFF
MS Idle State
k1 Reg. Msg (csch_enc_req = on)
ENC_KEY k1
<-k1
Reg. Accepted Order (csch_enc = on)
ON
Can decrypt
Can decrypt
now.
now.
Recovered
Recovered
4 Figure G-9. BS fails to decrypt messages (BS recovers by forcing the MS to re-register
5 after failing to re-synchronize the crypto-sync)
6
G-10
3GPP2 C.S0005-A v6.0
2 No text
G-11

tscs0005 A PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

tscs0005 A PDF

Uploaded by

Copyright:

Available Formats

TS-3GB-C.S0005-Av6.

Upper Layer (Layer 3)

May 28, 2002

THE TELECOMMUNICATION TECHNOLOGY COMMITTEE

2. Relationship with international recommendations and standards

3. Departures from international recommendations

Date: February 2002

Upper Layer (Layer 3) Signaling Standard for

2 NOTES .......................................................................................................................... xlii

4 1. GENERAL ................................................................................................................ 1-1

5 1.1 Terms and Numeric Information ............................................................................ 1-1

6 1.1.1 Terms ............................................................................................................. 1-1

7 1.1.2 Numeric Information ..................................................................................... 1-24

8 1.1.2.1 Reserved.................................................................................................. 1-24

9 1.1.2.2 CDMA Numeric Information ..................................................................... 1-24

10 1.2 Signaling Architecture......................................................................................... 1-45

11 1.3 Signaling and Functionality................................................................................. 1-45

12 1.3.1 General Architecture ..................................................................................... 1-45

13 1.3.2 Interface to Layer 2........................................................................................ 1-45

14 1.3.2.1 Message Control and Status Block (MCSB) ............................................... 1-45

15 1.3.2.2 Interface Primitives .................................................................................. 1-46

16 1.3.3 Reserved ....................................................................................................... 1-48

17 1.3.4 Functional Description ................................................................................. 1-48

18 1.3.5 PDU Transmission and Reception ................................................................. 1-48

19 2. REQUIREMENTS FOR MOBILE STATION CDMA OPERATION ................................... 2-1

20 2.1 Reserved ............................................................................................................... 2-1

21 2.2 Reserved ............................................................................................................... 2-1

22 2.3 Security and Identification .................................................................................... 2-1

23 2.3.1 Mobile Station Identification Number ............................................................... 2-1

24 2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S.......................................................... 2-3

25 2.3.1.2 Encoding of IMSI_M_11_12 and IMSI_T_11_12 ........................................... 2-6

26 2.3.1.3 Encoding of the MCC_M and MCC_T .......................................................... 2-6

27 2.3.1.4 Mobile Directory Number ........................................................................... 2-6

28 2.3.2 Electronic Serial Number ................................................................................. 2-6

29 2.3.3 Station Class Mark .......................................................................................... 2-6

30 2.3.4 Registration Memory........................................................................................ 2-7

31 2.3.5 Access Overload Class ..................................................................................... 2-8

1 2.3.6 Public Long Code Mask ................................................................................... 2-9

2 2.3.7 Reserved ......................................................................................................... 2-9

3 2.3.8 Home System and Network Identification......................................................... 2-9

4 2.3.9 Local Control Option ....................................................................................... 2-9

5 2.3.10 Preferred Operation Selection ........................................................................ 2-9

6 2.3.10.1 Preferred System ..................................................................................... 2-9

7 2.3.10.2 Preferred CDMA or Analog ..................................................................... 2-10

8 2.3.11 Discontinuous Reception ............................................................................. 2-10

9 2.3.12 Authentication, Encryption of Signaling Information/User Data and Voice

11 2.3.12.1 Authentication ...................................................................................... 2-10

12 2.3.12.1.1 Shared Secret Data (SSD)................................................................. 2-10

13 2.3.12.1.2 Random Challenge Memory (RAND) .................................................. 2-11

15 2.3.12.1.4 Unique Challenge-Response Procedure ............................................. 2-11

16 2.3.12.1.5 Updating the Shared Secret Data (SSD) ............................................ 2-12

17 2.3.12.2 Signaling Message Encryption ............................................................... 2-15

18 2.3.12.2.1 Encrypted Messages on the f-dsch.................................................... 2-16

19 2.3.12.2.2 Encrypted Messages on the r-dsch ................................................... 2-19

20 2.3.12.3 Voice Privacy ......................................................................................... 2-21

22 2.3.12.4.1 Extended Encryption for Signaling Messages .................................... 2-22

23 2.3.12.4.1.1 Extended Encryption for Signaling on f/r-csch............................ 2-23

24 2.3.12.4.1.2 Extended Encryption for Signaling on f/r-dsch ........................... 2-24

25 2.3.12.4.1.3 Signaling Encryption/Decryption Procedures.............................. 2-24

27 2.3.12.4.1.5 Duplicate Detection of Encrypted Messages ................................ 2-28

28 2.3.12.4.2 Extended Encryption for User Information........................................ 2-29

29 2.3.12.4.2.1 User Information Encryption/Decryption Procedures .................. 2-30

30 2.3.12.4.3 Interface to the Encryption Algorithms .......................................... 2-30