C.S0005 0 2

3GPP2 C.
S0005-0-2
Version 1.0
Date: April 24, 2001

1
2 Upper Layer (Layer 3) Signaling Standard for

3 cdma2000 Spread Spectrum Systems
4 Release 0 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.
10
C.S0005-0-2 v1.0
PREFACE
1 The technical requirements contained in cdma2000 form a compatibility standard for Code
2 Division Multiple Access (CDMA) systems. These technical requirements form a
3 compatibility standard for 800 MHz cellular mobile telecommunications systems and 1.8 to
4 2.0 GHz Code Division Multiple Access (CDMA) Personal Communications Services (PCS)
5 systems. They ensure that mobile stations manufactured in accordance with this standard
6 can obtain service from a system manufactured in accordance with this standard. These
7 requirements do not address the quality or reliability of that service, nor do they cover
8 equipment performance or measurement procedures.
9 To ensure compatibility (see Note 1), both radio-system parameters and call-processing
10 procedures must be specified. The sequence of call-processing steps that the mobile
11 stations and base stations execute to establish calls has been specified along with the
12 digital control messages and analog signals that are exchanged between the two stations.
13 The base station is subject to fewer compatibility requirements than the dual-mode mobile
14 station. Radiated power levels, both desired and undesired, are fully specified for dual-
15 mode mobile stations to control the RF interference that one mobile station can cause
16 another. Base stations are fixed in location and their interference is controlled by proper
17 layout and operation of the system in which the station operates. Detailed call-processing
18 procedures are specified for mobile stations to ensure a uniform response to all base
19 stations. Base station call procedures are not specified in detail because they are a part of
20 the overall design of the individual system. However, the base station call-processing
21 procedures must be compatible with those specified for the mobile station. This approach
22 to writing the compatibility specification provides the system designer with sufficient
23 flexibility to respond to local service needs and to account for local topography and
24 propagation conditions.
25 This specification includes provisions for future service additions and expansion of system
26 capabilities.
27 This standard is divided into multiple parts. This part details the Layer 3 call processing
28 and procedures.
i
C.S0005-0-2 v1.0
CONTENTS
1 1. GENERAL ............................................................................................................. 1-1
2 1.1 Terms and Numeric Information ........................................................................... 1-1
3 1.1.1 Terms ............................................................................................................. 1-1
4 1.1.2 Numeric Information ..................................................................................... 1-21
5 1.1.2.1 Reserved ................................................................................................. 1-22
6 1.1.2.2 CDMA Numeric Information..................................................................... 1-22
7 1.2 Signaling Architecture ........................................................................................ 1-40
8 1.3 Signaling and Functionality ................................................................................ 1-40
9 1.3.1 Control Plane and Data Plane ........................................................................ 1-40
10 1.3.2 Interface to Layer 2 ....................................................................................... 1-41
11 1.3.2.1 Message Control and Status Block (MCSB)............................................... 1-41
12 1.3.2.2 Interface Primitives.................................................................................. 1-42
13 1.3.3. Reserved ..................................................................................................... 1-44
14 1.3.4. Functional Description ................................................................................ 1-44
15 1.3.5. PDU Transmission and Reception ................................................................ 1-44
16 2. REQUIREMENTS FOR MOBILE STATION CDMA OPERATION ................................ 2-1
17 2.1 Reserved .............................................................................................................. 2-1
18 2.2 Reserved .............................................................................................................. 2-1
19 2.3 Security and Identification .................................................................................... 2-1
20 2.3.1 Mobile Station Identification Number............................................................... 2-1
21 2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S ......................................................... 2-3
22 2.3.1.2 Encoding of IMSI_M_11_12 and IMSI_T_11_12 ........................................... 2-5
23 2.3.1.3 Encoding of the MCC_M and MCC_T .......................................................... 2-5
24 2.3.1.4 Mobile Directory Number ........................................................................... 2-5
25 2.3.2 Electronic Serial Number................................................................................. 2-5
26 2.3.3 Station Class Mark.......................................................................................... 2-6
27 2.3.4 Registration Memory ....................................................................................... 2-6
28 2.3.5 Access Overload Class ..................................................................................... 2-7
29 2.3.6 Reserved ......................................................................................................... 2-8
30 2.3.7 Reserved ......................................................................................................... 2-8
31 2.3.8 Home System and Network Identification......................................................... 2-8
ii
C.S0005-0-2 v1.0
CONTENTS
1 2.3.9 Local Control Option........................................................................................ 2-9
2 2.3.10 Preferred Operation Selection......................................................................... 2-9
3 2.3.10.1 Preferred System...................................................................................... 2-9
4 2.3.10.2 Preferred CDMA or Analog........................................................................ 2-9
5 2.3.11 Discontinuous Reception ............................................................................... 2-9
6 2.3.12 Authentication, Encryption of Signaling Information/User Data and Voice

7 Privacy..................................................................................................................... 2-9
8 2.3.12.1 Authentication ......................................................................................... 2-9
9 2.3.12.1.1 Shared Secret Data (SSD) ................................................................. 2-10
10 2.3.12.1.2 Random Challenge Memory (RAND) .................................................. 2-10

11 2.3.12.1.3 Call History Parameter (COUNTs-p) ................................................... 2-10
12 2.3.12.1.4 Unique Challenge-Response Procedure ............................................. 2-10
13 2.3.12.1.5 Updating the Shared Secret Data (SSD) ............................................ 2-11
14 2.3.12.2 Signaling Message Encryption ................................................................ 2-15
15 2.3.12.2.1 Encrypted Messages on the f-dsch .................................................... 2-16
16 2.3.12.2.2 Encrypted Messages on the r-dsch.................................................... 2-18
17 2.3.12.3 Voice Privacy ......................................................................................... 2-21
18 2.3.13 Lock and Maintenance Required Orders ....................................................... 2-21
19 2.3.14 Mobile Station Revision Identification........................................................... 2-22
20 2.3.15 Temporary Mobile Station Identity................................................................ 2-22
21 2.3.15.1 Overview................................................................................................ 2-22
22 2.3.15.2 TMSI Assignment Memory...................................................................... 2-23
23 2.4 Accumulated Statistics........................................................................................ 2-24
24 2.4.1 Monitored Quantities and Statistics.................................................................. 2-24
25 2.4.2 Accumulated Paging Channel Statistics.......................................................... 2-24
26 2.5 Reserved ............................................................................................................. 2-25
27 2.6 Call Processing.................................................................................................... 2-27
28 2.6.1 Mobile Station Initialization State .................................................................. 2-29
29 2.6.1.1 System Determination Substate ............................................................... 2-31
30 2.6.1.1.1 Custom System Selection Process ....................................................... 2-36
31 2.6.1.1.2 System Selection Using Current Redirection Criteria ........................... 2-37
iii
C.S0005-0-2 v1.0
CONTENTS
1 2.6.1.1.3 System Selection Using System Reselection Criteria............................ 2-38
2 2.6.1.1.4 Acquiring the Selected System ........................................................... 2-39
3 2.6.1.2 Pilot Channel Acquisition Substate .......................................................... 2-39
4 2.6.1.3 Sync Channel Acquisition Substate.......................................................... 2-39
5 2.6.1.4 Timing Change Substate.......................................................................... 2-41
6 2.6.2 Mobile Station Idle State ............................................................................... 2-43
7 2.6.2.1 Idle Procedures........................................................................................ 2-44
8 2.6.2.1.1 Paging Channel Monitoring Procedures .............................................. 2-44
9 2.6.2.1.1.1 General Overview ......................................................................... 2-44
10 2.6.2.1.1.1.1 General Overview for Individually Addressed Messages ............ 2-45
11 2.6.2.1.1.1.2 General Overview for Broadcast Messages ............................... 2-47
12 2.6.2.1.1.1.2.1 Method 1: Multi-Slot Broadcast Message Transmission...... 2-48
13 2.6.2.1.1.1.2.2 Method 2: Periodic Broadcast Paging................................. 2-48
14 2.6.2.1.1.2 Non-Slotted Mode Requirements................................................... 2-49
15 2.6.2.1.1.3 Slotted Mode Requirements .......................................................... 2-49
16 2.6.2.1.1.3.1 Monitoring Assigned Slots....................................................... 2-50
17 2.6.2.1.1.3.2 Determination of the Slot Cycle Index ..................................... 2-51
18 2.6.2.1.1.3.3 Slot Cycles for Broadcast Paging ............................................. 2-51
19 2.6.2.1.1.3.4 Monitoring Paging Channel Broadcasts ................................... 2-51
20 2.6.2.1.1.3.5 Support of Broadcast Delivery Options.................................... 2-52
21 2.6.2.1.1.4 Paging Channel Supervision ......................................................... 2-52
22 2.6.2.1.2 Quick Paging Channel Monitoring Procedures .................................... 2-52
23 2.6.2.1.2.1 Overview...................................................................................... 2-52
24 2.6.2.1.2.2 Requirements............................................................................... 2-55
25 2.6.2.1.3 Registration ....................................................................................... 2-56
26 2.6.2.1.4 Idle Handoff....................................................................................... 2-56
27 2.6.2.1.4.1 Pilot Search ................................................................................. 2-56
28 2.6.2.1.4.2 Idle Handoff Procedures ............................................................... 2-58
29 2.6.2.1.5 Reserved............................................................................................ 2-63
30 2.6.2.1.6 System Reselection Procedures .......................................................... 2-63
31 2.6.2.1.7 Slotted Timer Expiration .................................................................... 2-64
32 2.6.2.2 Response to Overhead Information Operation........................................... 2-64
iv
C.S0005-0-2 v1.0
CONTENTS
1 2.6.2.2.1 System Parameters Message ............................................................... 2-67
2 2.6.2.2.1.1 Stored Parameters ........................................................................ 2-67
3 2.6.2.2.1.2 Paging Channel Assignment Change ............................................. 2-70
4 2.6.2.2.1.3 RESCAN Parameter ...................................................................... 2-71
5 2.6.2.2.1.4 Roaming Status............................................................................ 2-71
6 2.6.2.2.1.5 Registration.................................................................................. 2-71
7 2.6.2.2.1.6 Slot Cycle Index............................................................................ 2-71
8 2.6.2.2.1.7 PACA Disable for SID Change ....................................................... 2-71
9 2.6.2.2.1.8 Retry Delay Disable for Packet Zone ID or SID/NID Change........... 2-71
10 2.6.2.2.2 Access Parameters Message................................................................ 2-72
11 2.6.2.2.3 Neighbor List Message ........................................................................ 2-73
12 2.6.2.2.4 CDMA Channel List Message .............................................................. 2-74
13 2.6.2.2.5 Extended System Parameters Message................................................ 2-75
14 2.6.2.2.6 Global Service Redirection Message .................................................... 2-79
15 2.6.2.2.7 Extended Neighbor List Message......................................................... 2-80
16 2.6.2.2.8 General Neighbor List Message ........................................................... 2-82
17 2.6.2.2.9 User Zone Identification Message........................................................ 2-85
18 2.6.2.2.10 Private Neighbor List Message........................................................... 2-85
19 2.6.2.2.11 Extended Global Service Redirection Message ................................... 2-86
20 2.6.2.2.12 Extended CDMA Channel List Message ............................................. 2-87
21 2.6.2.3 Mobile Station Page Match Operation ....................................................... 2-89
22 2.6.2.4 Mobile Station Order and Message Processing Operation........................... 2-90
23 2.6.2.5 Mobile Station Origination Operation........................................................ 2-98
24 2.6.2.6 Mobile Station Message Transmission Operation....................................... 2-99
25 2.6.2.7 Mobile Station Power-Down Operation...................................................... 2-99
26 2.6.2.8 Mobile Station PACA Cancel Operation ..................................................... 2-99
27 2.6.3 System Access State ...................................................................................... 2-99
28 2.6.3.1 Access Procedures ................................................................................. 2-100
29 2.6.3.1.1 Access Attempts ............................................................................... 2-100
30 2.6.3.1.2 Reserved .......................................................................................... 2-101
v
C.S0005-0-2 v1.0
CONTENTS
1 2.6.3.1.3 Handoffs...........................................................................................2-101
2 2.6.3.1.3.1 Pilot Search ................................................................................2-102
3 2.6.3.1.3.2 Access Handoff ...........................................................................2-102
4 2.6.3.1.3.3 Access Probe Handoff ..................................................................2-103
5 2.6.3.1.4 System Access State Exit Procedures.................................................2-105
6 2.6.3.1.5 Reserved...........................................................................................2-105
7 2.6.3.1.6 Full-TMSI Timer ...............................................................................2-105
8 2.6.3.1.7 Monitoring Pilots ..............................................................................2-105
9 2.6.3.1.7.1 Generation of the Initial Access Handoff List ................................2-106
10 2.6.3.1.7.2 Update of the Access Handoff List................................................2-106
11 2.6.3.1.7.3 Generation of the Other Reported List..........................................2-107
12 2.6.3.1.7.4 Update of OTHER_REPORTED_LIST ............................................2-107
13 2.6.3.1.8 Paging Channel Monitoring ...............................................................2-107
14 2.6.3.2 Update Overhead Information Substate...................................................2-108
15 2.6.3.3 Page Response Substate .........................................................................2-111
16 2.6.3.4 Mobile Station Order/Message Response Substate ..................................2-133
17 2.6.3.5 Mobile Station Origination Attempt Substate...........................................2-137
18 2.6.3.6 Registration Access Substate ..................................................................2-162
19 2.6.3.7 Mobile Station Message Transmission Substate.......................................2-167
20 2.6.3.8 PACA Cancel Substate ............................................................................2-172
21 2.6.4 Mobile Station Control on the Traffic Channel State ......................................2-175
22 2.6.4.1 Special Functions and Actions ................................................................2-178
23 2.6.4.1.1 Forward Traffic Channel Power Control .............................................2-178
24 2.6.4.1.1.1 Forward Traffic Channel Power Control Initialization....................2-181
25 2.6.4.1.1.2 Processing the Power Control Parameters Message.......................2-181
26 2.6.4.1.1.3 Processing the Power Control Message.........................................2-182
27 2.6.4.1.2 Service Configuration and Negotiation ...............................................2-184
28 2.6.4.1.2.1 Use of Variables ..........................................................................2-189
29 2.6.4.1.2.1.1 Maintaining the Service Request Sequence Number................2-189
30 2.6.4.1.2.1.2 Maintaining the Service Negotiation Indicator Variable ...........2-189
31 2.6.4.1.2.1.3 Maintaining the Service Option Request Number....................2-189
32 2.6.4.1.2.2 Service Subfunctions ..................................................................2-189
vi
C.S0005-0-2 v1.0
CONTENTS
1 2.6.4.1.2.2.1 Normal Service Subfunction .................................................. 2-192
2 2.6.4.1.2.2.2 Waiting for Service Request Message Subfunction.................. 2-193
3 2.6.4.1.2.2.3 Waiting for Service Response Message Subfunction ............... 2-195
4 2.6.4.1.2.2.4 Waiting for Service Connect Message Subfunction ................. 2-198
5 2.6.4.1.2.2.5 Waiting for Service Action Time Subfunction ......................... 2-200
6 2.6.4.1.2.2.6 SO Negotiation Subfunction .................................................. 2-202
7 2.6.4.1.3 Ordering of Messages ....................................................................... 2-204
8 2.6.4.1.4 Processing the In-Traffic System Parameters Message ....................... 2-204
9 2.6.4.1.5 Message Action Times ...................................................................... 2-205
10 2.6.4.1.6 Long Code Transition Request Processing ......................................... 2-206
11 2.6.4.1.7 Power Up Function (PUF).................................................................. 2-206
12 2.6.4.1.7.1 Processing the Power Up Function Message................................. 2-207
13 2.6.4.1.7.2 Power Up Function Procedures ................................................... 2-208
14 2.6.4.1.7.2.1 PUF Probe On Serving Frequency .......................................... 2-208
15 2.6.4.1.7.2.2 PUF Probe On PUF Target Frequency..................................... 2-209
16 2.6.4.1.7.3 Processing the Power Up Function Completion Message............... 2-211
17 2.6.4.1.8 Forward Traffic Channel Supervision ................................................ 2-211
18 2.6.4.1.9 Processing the Extended Release Message and the Extended Release Mini
19 Message ......................................................................................................... 2-211
20 2.6.4.1.10 Processing the Resource Allocation Message and Resource Allocation Mini
21 Message ......................................................................................................... 2-213
22 2.6.4.1.11 Reserved ........................................................................................ 2-213
23 2.6.4.1.12 Processing the Service Configuration Record ................................... 2-213
24 2.6.4.1.13 Processing the Non-Negotiable Service Configuration Record ........... 2-215
25 2.6.4.2 Traffic Channel Initialization Substate.................................................... 2-218
26 2.6.4.3 Alerting ................................................................................................. 2-227
27 2.6.4.3.1 Waiting for Order Substate ............................................................... 2-227
28 2.6.4.3.2 Waiting for Mobile Station Answer Substate...................................... 2-234
29 2.6.4.4 Conversation Substate ........................................................................... 2-242
30 2.6.4.5 Release Substate.................................................................................... 2-254
31 2.6.5 Registration................................................................................................. 2-260
vii
C.S0005-0-2 v1.0
CONTENTS
1 2.6.5.1 Forms of Registration .............................................................................2-260
2 2.6.5.1.1 Power-Up Registration ......................................................................2-261
3 2.6.5.1.2 Power-Down Registration ..................................................................2-261
4 2.6.5.1.3 Timer-Based Registration ..................................................................2-261
5 2.6.5.1.4 Distance-Based Registration .............................................................2-262
6 2.6.5.1.5 Zone-Based Registration ...................................................................2-263
7 2.6.5.1.6 Parameter-Change Registration.........................................................2-265
8 2.6.5.1.7 Ordered Registration.........................................................................2-266
9 2.6.5.1.8 Implicit Registration .........................................................................2-266
10 2.6.5.1.9 Traffic Channel Registration..............................................................2-266
11 2.6.5.1.10 User Zone Registration....................................................................2-266
12 2.6.5.2 Systems and Networks ...........................................................................2-266
13 2.6.5.3 Roaming ................................................................................................2-267
14 2.6.5.4 Registration Timers and Indicators .........................................................2-269
15 2.6.5.5 Registration Procedures ..........................................................................2-269
16 2.6.5.5.1 Actions in the Mobile Station Initialization State................................2-269
17 2.6.5.5.1.1 Power-Up or Change to a Different Operating Mode, Band Class,

18 Serving System, or Frequency Block .............................................................2-269
19 2.6.5.5.1.2 Timer Maintenance .....................................................................2-270
20 2.6.5.5.1.3 Entering the Mobile Station Idle State..........................................2-270
21 2.6.5.5.2 Actions in the Mobile Station Idle State .............................................2-270
22 2.6.5.5.2.1 Idle Registration Procedures ........................................................2-270
23 2.6.5.5.2.2 Processing the Registration Fields of the System Parameters Message2-272
24 2.6.5.5.2.3 Ordered Registration ...................................................................2-272
25 2.6.5.5.2.4 Power Off ....................................................................................2-272
26 2.6.5.5.2.5 Full-TMSI Timer Expiration .........................................................2-273
27 2.6.5.5.3 Actions in the System Access State ...................................................2-273
28 2.6.5.5.3.1 Successful Access, Registration, or Implicit Registration ..............2-273
29 2.6.5.5.3.2 Unsuccessful Access ...................................................................2-275
30 2.6.5.5.3.3 Power Off ....................................................................................2-276
31 2.6.5.5.4 Actions in the Mobile Station Control on the Traffic Channel State.....2-276
32 2.6.5.5.4.1 Traffic Channel Initialization .......................................................2-276
viii
C.S0005-0-2 v1.0
CONTENTS
1 2.6.5.5.4.2 Timer Maintenance..................................................................... 2-276
2 2.6.5.5.4.3 Processing the Mobile Station Registered Message ....................... 2-276
3 2.6.5.5.4.4 Power Off ................................................................................... 2-278
4 2.6.6 Handoff Procedures ..................................................................................... 2-278
5 2.6.6.1 Overview................................................................................................ 2-278
6 2.6.6.1.1 Types of Handoff .............................................................................. 2-278
7 2.6.6.1.2 Pilot Sets ......................................................................................... 2-279
8 2.6.6.2 Requirements ........................................................................................ 2-280
9 2.6.6.2.1 Pilot Search ..................................................................................... 2-280
10 2.6.6.2.2 Pilot Strength Measurements............................................................ 2-282
11 2.6.6.2.3 Handoff Drop Timer.......................................................................... 2-282
12 2.6.6.2.4 Pilot PN Phase.................................................................................. 2-284
13 2.6.6.2.5 Handoff Messages ............................................................................ 2-284
14 2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages ............ 2-284
15 2.6.6.2.5.1.1 Processing of the Forward Supplemental Burst Assignment ... 2-334
16 2.6.6.2.5.1.2 Processing of the Reverse Supplemental Burst Assignment .... 2-336
17 2.6.6.2.5.2 Processing of Reverse Traffic Channel Handoff Messages ............. 2-338
18 2.6.6.2.6 Set Maintenance .............................................................................. 2-341
19 2.6.6.2.6.1 Maintenance of the Active Set ..................................................... 2-341
20 2.6.6.2.6.2 Maintenance of the Candidate Set............................................... 2-342
21 2.6.6.2.6.3 Maintenance of the Neighbor Set................................................. 2-342
22 2.6.6.2.7 Soft Handoff..................................................................................... 2-344
23 2.6.6.2.7.1 Forward Traffic Channel Processing ............................................ 2-344
24 2.6.6.2.7.2 Reverse Traffic Channel Power Control During Soft Handoff......... 2-344
25 2.6.6.2.7.3 Starting Periodic Search following Soft Handoff ........................... 2-344
26 2.6.6.2.8 CDMA-to-CDMA Hard Handoff.......................................................... 2-345
27 2.6.6.2.8.1 Hard Handoff without Return on Failure ..................................... 2-345
28 2.6.6.2.8.2 Hard Handoff with Return on Failure .......................................... 2-346
29 2.6.6.2.8.2.1 Restoring the Configuration .................................................. 2-350
30 2.6.6.2.8.3 Search of Pilots on the CDMA Candidate Frequency .................... 2-353
ix
C.S0005-0-2 v1.0
CONTENTS
1 2.6.6.2.8.3.1 CDMA Candidate Frequency Single Search.............................2-353
2 2.6.6.2.8.3.2 Candidate Frequency Periodic Search ....................................2-355
3 2.6.6.2.8.3.3 Candidate Frequency Pilot Measurements ..............................2-359
4 2.6.6.2.8.3.4 Aborting CDMA Candidate Frequency Periodic Search ............2-361
5 2.6.6.2.9 CDMA-to-Analog Handoff ..................................................................2-361
6 2.6.6.2.10 Search of Analog Frequencies..........................................................2-362
7 2.6.6.2.10.1 Analog Frequencies Single Search..............................................2-362
8 2.6.6.2.10.2 Analog Frequencies Periodic Search ...........................................2-363
9 2.6.6.2.10.3 Analog Frequency Measurements...............................................2-366
10 2.6.6.2.10.4 Aborting Analog Frequencies Periodic Search .............................2-368
11 2.6.6.2.11 Processing of Reverse Supplemental Code Channels and Reverse

12 Supplemental Channels ..................................................................................2-369
13 2.6.6.2.12 Periodic Serving Frequency Pilot Report Procedure...........................2-369
14 2.6.6.3 Examples ...............................................................................................2-371
15 2.6.7 Hash Functions and Randomization .............................................................2-376
16 2.6.7.1 Hash Function .......................................................................................2-376
17 2.6.7.2 Pseudorandom Number Generator ..........................................................2-377

18 2.6.8 CODE_CHAN_LISTs Maintenance .................................................................2-378
19 2.6.9 CDMA Tiered Services ..................................................................................2-379
20 2.6.9.1 Overview ................................................................................................2-380
21 2.6.9.1.1 Definition .........................................................................................2-380
22 2.6.9.1.2 Types of User Zones ..........................................................................2-380
23 2.6.9.2 Requirements .........................................................................................2-381
24 2.6.9.2.1 User Zone Operation in the Mobile Station Idle State: ........................2-381
25 2.6.9.2.2 User Zone Operation in the Mobile Station Control on the Traffic Channel
26 State...............................................................................................................2-382
27 2.7 PDU Formats for Mobile Stations .......................................................................2-385
28 2.7.1.1 Reserved ................................................................................................2-386
29 2.7.1.2 Reserved ................................................................................................2-386
30 2.7.1.3 PDU Formats on r-csch ..........................................................................2-386
31 2.7.1.3.1 Reserved...........................................................................................2-386
32 2.7.1.3.2 PDU Contents...................................................................................2-386
x
C.S0005-0-2 v1.0
CONTENTS
1 2.7.1.3.2.1 Registration Message .................................................................. 2-387
2 2.7.1.3.2.2 Order Message............................................................................ 2-390
3 2.7.1.3.2.3 Data Burst Message.................................................................... 2-391
4 2.7.1.3.2.4 Origination Message ................................................................... 2-393
5 2.7.1.3.2.5 Page Response Message .............................................................. 2-402
6 2.7.1.3.2.6 Authentication Challenge Response Message............................... 2-407
7 2.7.1.3.2.7 Status Response Message ........................................................... 2-408
8 2.7.1.3.2.8 TMSI Assignment Completion Message........................................ 2-409
9 2.7.1.3.2.9 PACA Cancel Message................................................................. 2-410
10 2.7.1.3.2.10 Extended Status Response Message .......................................... 2-411
11 2.7.2 r-dsch ........................................................................................................ 2-414
12 2.7.2.1 Reserved................................................................................................ 2-414
13 2.7.2.2 Reserved................................................................................................ 2-414
14 2.7.2.3 PDU Formats for Messages on r-dsch ..................................................... 2-414
15 2.7.2.3.1 Reserved .......................................................................................... 2-416
16 2.7.2.3.2 Message Body Contents.................................................................... 2-416
17 2.7.2.3.2.1 Order Message............................................................................ 2-417
18 2.7.2.3.2.2 Authentication Challenge Response Message............................... 2-418
19 2.7.2.3.2.3 Flash With Information Message ................................................. 2-419
21 2.7.2.3.2.5 Pilot Strength Measurement Message .......................................... 2-422
22 2.7.2.3.2.6 Power Measurement Report Message........................................... 2-424
23 2.7.2.3.2.7 Send Burst DTMF Message ......................................................... 2-428
24 2.7.2.3.2.8 Status Message .......................................................................... 2-430
25 2.7.2.3.2.9 Origination Continuation Message .............................................. 2-431
26 2.7.2.3.2.10 Handoff Completion Message .................................................... 2-433
27 2.7.2.3.2.11 Parameters Response Message .................................................. 2-434
28 2.7.2.3.2.12 Service Request Message........................................................... 2-435
29 2.7.2.3.2.13 Service Response Message ........................................................ 2-437
30 2.7.2.3.2.14 Service Connect Completion Message ........................................ 2-439
xi
C.S0005-0-2 v1.0
CONTENTS
1 2.7.2.3.2.15 Service Option Control Message.................................................2-440
2 2.7.2.3.2.16 Status Response Message..........................................................2-441
3 2.7.2.3.2.17 TMSI Assignment Completion Message ......................................2-442
4 2.7.2.3.2.18 Supplemental Channel Request Message ...................................2-443
5 2.7.2.3.2.19 Candidate Frequency Search Response Message ........................2-446
6 2.7.2.3.2.20 Candidate Frequency Search Report Message ............................2-449
7 2.7.2.3.2.21 Periodic Pilot Strength Measurement Message............................2-454
8 2.7.2.3.2.22 Outer Loop Report Message .......................................................2-456
9 2.7.2.3.2.23 Resource Request Message ........................................................2-458
10 2.7.2.3.2.24 Resource Request Mini Message ................................................2-459
11 2.7.2.3.2.25 Extended Release Response Message .........................................2-460
12 2.7.2.3.2.26 Extended Release Response Mini Message..................................2-461
13 2.7.2.3.2.27 Pilot Strength Measurement Mini Message .................................2-462
14 2.7.2.3.2.28 Supplemental Channel Request Mini Message............................2-463
15 2.7.2.3.2.29 Resource Release Request Message............................................2-464
16 2.7.2.3.2.30 Resource Release Request Mini Message ....................................2-465
17 2.7.2.3.2.31 User Zone Update Request Message...........................................2-466
18 2.7.3 Orders .........................................................................................................2-466
19 2.7.3.1 Base Station Challenge Order .................................................................2-471
20 2.7.3.2 Service Option Request Order .................................................................2-472
21 2.7.3.3 Service Option Response Order ...............................................................2-473
22 2.7.3.4 Mobile Station Reject Order ....................................................................2-474
23 2.7.4 Information Records.....................................................................................2-476
24 2.7.4.1 Reserved2.7.4.2 Keypad Facility..............................................................2-478
25 2.7.4.2 Keypad Facility.......................................................................................2-479
26 2.7.4.3 Called Party Number ..............................................................................2-480
27 2.7.4.4 Calling Party Number .............................................................................2-481
28 2.7.4.5 Reserved ................................................................................................2-483
29 2.7.4.6 Call Mode...............................................................................................2-484
30 2.7.4.7 Terminal Information..............................................................................2-485
31 2.7.4.8 Roaming Information..............................................................................2-487
32 2.7.4.9 Security Status ......................................................................................2-489
xii
C.S0005-0-2 v1.0
CONTENTS
1 2.7.4.10 Connected Number .............................................................................. 2-490
2 2.7.4.11 IMSI .................................................................................................... 2-491
3 2.7.4.12 ESN..................................................................................................... 2-492
4 2.7.4.13 Band Class Information ....................................................................... 2-493
5 2.7.4.14 Power Class Information ...................................................................... 2-495
6 2.7.4.15 Operating Mode Information................................................................. 2-496
7 2.7.4.16 Service Option Information................................................................... 2-498
8 2.7.4.17 Multiplex Option Information ............................................................... 2-499
9 2.7.4.18 Service Configuration ........................................................................... 2-504
10 2.7.4.19 Called Party Subaddress ...................................................................... 2-516
11 2.7.4.20 Calling Party Subaddress ..................................................................... 2-518
12 2.7.4.21 Connected Subaddress......................................................................... 2-519
13 2.7.4.22 Power Control Information ................................................................... 2-520
14 2.7.4.23 IMSI_M ................................................................................................ 2-521
15 2.7.4.24 IMSI_T................................................................................................. 2-522
16 2.7.4.25 Capability Information ......................................................................... 2-523
17 2.7.4.26 Extended Record Type - International ................................................... 2-527
18 2.7.4.27 Channel Configuration Capability Information ...................................... 2-528
19 The mobile station shall add reserved bits as needed in order to make the length of
20 the entire information record equal to an integer number of octets. The mobile
21 station shall set these bits to ‘0’. ..................................................................... 2-529
22 2.7.4.27.1 FCH Type-specific Fields................................................................. 2-529
23 2.7.4.27.2 DCCH Type-Specific Fields ............................................................. 2-533
24 2.7.4.27.3 FOR_SCH Type-Specific Fields. ....................................................... 2-535
25 2.7.4.27.4 REV_SCH Type-Specific Fields. ....................................................... 2-538
26 2.7.4.28 Extended Multiplex Option Information ................................................ 2-540
27 2.7.4.29 Geo-Location Information..................................................................... 2-547
28 2.7.4.30 Band Subclass Information .................................................................. 2-548
29 3.1 Reserved ............................................................................................................... 3-1
30 3.2 Reserved ............................................................................................................... 3-1
31 3.3 Security and Identification .................................................................................... 3-1
xiii
C.S0005-0-2 v1.0
CONTENTS
1 3.3.1 Authentication ................................................................................................ 3-1
2 3.3.2 Encryption...................................................................................................... 3-1
3 3.3.3 Voice Privacy................................................................................................... 3-1
4 3.4 Supervision .......................................................................................................... 3-1
5 3.4.1 Access Channel............................................................................................... 3-1
6 3.4.2 Reverse Traffic Channel................................................................................... 3-1
7 3.5 Reserved .............................................................................................................. 3-2
8 3.6 Call Processing ..................................................................................................... 3-2
9 3.6.1 Pilot and Sync Channel Processing .................................................................. 3-2
10 3.6.1.1 Preferred Set of CDMA Channels................................................................ 3-2
11 3.6.1.2 Pilot Channel Operation ............................................................................ 3-2
12 3.6.1.3 Sync Channel Operation............................................................................ 3-3
13 3.6.2 Paging Channel and Quick Paging Channel Processing..................................... 3-3
14 3.6.2.1 Paging Channel Procedures ....................................................................... 3-3
15 3.6.2.1.1 CDMA Channel Determination ............................................................. 3-3
16 3.6.2.1.2 Paging Channel Determination............................................................. 3-4
17 3.6.2.1.3 Paging Slot Determination.................................................................... 3-4
18 3.6.2.1.4 Message Transmission and Acknowledgment Procedures ...................... 3-4
19 3.6.2.2 Overhead Information................................................................................ 3-4
20 3.6.2.3 Mobile Station Directed Messages .............................................................. 3-6
21 3.6.2.4 Broadcast Messages .................................................................................. 3-8
22 3.6.2.4.1 Broadcast Procedures for Slotted Mode................................................. 3-8
23 3.6.2.4.1.1 General Overview ........................................................................... 3-9
24 3.6.2.4.1.2 Requirements for Sending Broadcast Messages ............................... 3-9
25 3.6.2.4.1.2.1 Broadcast Delivery Options....................................................... 3-9
26 3.6.2.4.1.2.1.1 Method 1: Multi-Slot Broadcast Message Transmission........ 3-9
27 3.6.2.4.1.2.1.2 Method 2: Periodic Broadcast Paging................................. 3-10
28 3.6.2.4.1.2.2 Duplicate Broadcast Message Transmission ............................ 3-10
29 3.6.2.4.1.2.3 Periodic Broadcast Paging....................................................... 3-10
30 3.6.2.4.1.2.4 Broadcast Message Slot Determination ................................... 3-11
31 3.6.2.5 Quick Paging Channel Processing ............................................................ 3-11
32 3.6.2.5.1 Quick Paging Channel Determination................................................. 3-11
xiv
C.S0005-0-2 v1.0
CONTENTS
1 3.6.2.5.2 Quick Paging Channel Slot Determination ......................................... 3-12
2 3.6.2.5.3 Paging Indicator Position Determination ............................................ 3-12
3 3.6.2.5.4 Configuration Change Indicator Position Determination ..................... 3-12
4 3.6.2.5.5 Reserved Indicator Positions .............................................................. 3-12
5 3.6.3 Access Channel Processing ............................................................................ 3-13
6 3.6.3.1 Reserved.................................................................................................. 3-13
7 3.6.3.2 Reserved.................................................................................................. 3-13
8 3.6.3.3 Response to Page Response Message ........................................................ 3-13
9 3.6.3.4 Response to Orders.................................................................................. 3-14
10 3.6.3.5 Response to Origination Message ............................................................. 3-14
11 3.6.3.6 Response to Registration Message ............................................................ 3-15
12 3.6.3.7 Response to Data Burst Message.............................................................. 3-15
13 3.6.3.8 Reserved.................................................................................................. 3-15
14 3.6.3.9 Reserved.................................................................................................. 3-15
15 3.6.3.10 Service Redirection ................................................................................ 3-15
16 3.6.4 Traffic Channel Processing............................................................................. 3-15
17 3.6.4.1 Special Functions and Actions ................................................................. 3-16
18 3.6.4.1.1 Forward Traffic Channel Power Control............................................... 3-16
19 3.6.4.1.2 Service Configuration and Negotiation ................................................ 3-16
20 3.6.4.1.2.1 Use of Variables............................................................................ 3-21
21 3.6.4.1.2.1.1 Maintaining the Service Request Sequence Number ................. 3-21
22 3.6.4.1.2.1.2 Maintaining the Service Connect Sequence Number................. 3-21
23 3.6.4.1.2.1.3 Assigning Service Option Connection References ..................... 3-21
24 3.6.4.1.2.1.4 Maintaining the Service Negotiation Indicator Variable............. 3-22
25 3.6.4.1.2.1.5 Maintaining the Service Option Request Number ..................... 3-22
26 3.6.4.1.2.2 Service Subfunctions .................................................................... 3-22
27 3.6.4.1.2.2.1 Normal Service Subfunction .................................................... 3-25
28 3.6.4.1.2.2.2 Waiting for Service Request Message Subfunction.................... 3-26
29 3.6.4.1.2.2.3 Waiting for Service Response Message Subfunction ................. 3-28
30 3.6.4.1.2.2.4 Waiting for Service Action Time Subfunction ........................... 3-29
xv
C.S0005-0-2 v1.0
CONTENTS
1 3.6.4.1.2.2.5 Waiting for Service Connect Completion Message Subfunction. 3-31
2 3.6.4.1.2.2.6 SO Negotiation Subfunction.................................................... 3-32
3 3.6.4.1.3 Ordering of Messages......................................................................... 3-34
4 3.6.4.1.4 Message Action Times ........................................................................ 3-34
5 3.6.4.1.5 Long Code Transition Request Processing ........................................... 3-34
6 3.6.4.1.6 Processing Resource Request Messages .............................................. 3-35
7 3.6.4.1.7 Reserved............................................................................................ 3-35
8 3.6.4.1.8 Processing Resource Release Request Message and Resource Release

9 Request Mini Message ...................................................................................... 3-35
10 3.6.4.2 Traffic Channel Initialization Substate ..................................................... 3-35
11 3.6.4.3 Alerting ................................................................................................... 3-37
12 3.6.4.3.1 Waiting for Order Substate ................................................................ 3-37
13 3.6.4.3.2 Waiting for Answer Substate .............................................................. 3-42
14 3.6.4.4 Conversation Substate............................................................................. 3-47
15 3.6.4.5 Release Substate ..................................................................................... 3-53
16 3.6.5 Registration .................................................................................................. 3-57
17 3.6.5.1 Registration on the Paging and Access Channels ...................................... 3-58
18 3.6.5.2 Registration on the Traffic Channels ........................................................ 3-58
19 3.6.6 Handoff Procedures ....................................................................................... 3-58
20 3.6.6.1 Overview ................................................................................................. 3-58
21 3.6.6.1.1 Types of Handoff ................................................................................ 3-58
22 3.6.6.1.2 Active Set .......................................................................................... 3-59
23 3.6.6.2 Requirements .......................................................................................... 3-59
24 3.6.6.2.1 Overhead Information ........................................................................ 3-59
25 3.6.6.2.1.1 System Parameters ...................................................................... 3-59
26 3.6.6.2.1.2 Neighbor List ............................................................................... 3-60
27 3.6.6.2.1.3 Candidate Frequency Neighbor List .............................................. 3-60
28 3.6.6.2.1.4 Candidate Frequency Search List ................................................. 3-60
29 3.6.6.2.2 Call Processing During Handoff .......................................................... 3-61
30 3.6.6.2.2.1 Processing the Pilot Strength Measurement Message..................... 3-61
31 3.6.6.2.2.2 Processing the Extended Handoff Direction Message ..................... 3-61
32 3.6.6.2.2.3 Processing the Candidate Frequency Search Request Message....... 3-63
xvi
C.S0005-0-2 v1.0
CONTENTS
1 3.6.6.2.2.4 Processing the Candidate Frequency Search Response Message..... 3-63
2 3.6.6.2.2.5 Processing the Candidate Frequency Search Control Message........ 3-63
3 3.6.6.2.2.6 Processing the Candidate Frequency Search Report Message ......... 3-64
4 3.6.6.2.2.7 Transmitting During Handoff ........................................................ 3-64
5 3.6.6.2.2.8 Ordering Pilot Measurements From the Mobile Station .................. 3-64
6 3.6.6.2.2.9 Processing the Supplemental Channel Assignment Message .......... 3-65
7 3.6.6.2.2.10 Processing the General Handoff Direction Message ...................... 3-68
8 3.6.6.2.2.11 Processing the Universal Handoff Direction Message.................... 3-72
9 3.6.6.2.2.12 Processing of Extended Supplemental Channel Assignment Message3-75
10 3.6.6.2.2.13 Processing of Forward Supplemental Channel Assignment Mini

11 Message......................................................................................................... 3-77
12 3.6.6.2.2.14 Processing of Reverse Supplemental Channel Assignment Mini

13 Message......................................................................................................... 3-78
14 3.6.6.2.2.15 Processing of the Mobile Assisted Burst Operation Parameters

15 Message......................................................................................................... 3-79
16 3.6.6.2.3 Active Set Maintenance ...................................................................... 3-80
17 3.6.6.2.4 Soft Handoff....................................................................................... 3-81
18 3.6.6.2.4.1 Receiving During Soft Handoff ...................................................... 3-81
19 3.6.6.2.4.2 Transmitting During Soft Handoff ................................................. 3-81
20 3.6.7 CDMA Tiered Services.................................................................................... 3-81
21 3.6.7.1 Overview.................................................................................................. 3-81
22 3.6.7.1.1 Definition........................................................................................... 3-81
23 3.6.7.1.2 Types of User Zones ........................................................................... 3-82
24 3.6.7.2 Requirements .......................................................................................... 3-82
25 3.6.7.2.1 User Zone Identification Message........................................................ 3-82
26 3.6.7.2.2 Private Neighbor List Message.......................................................... 3-82
27 3.6.7.2.3 User Zone Update Message and User Zone Reject Message on f-dsch ... 3-83
28 3.6.7.2.4 User Zone Reject Message on f-csch.................................................... 3-83
29 3.7 PDU Formats for Messages .................................................................................. 3-84
30 3.7.1 Reserved ....................................................................................................... 3-84
31 3.7.2 f-csch............................................................................................................ 3-84
xvii
C.S0005-0-2 v1.0
CONTENTS
1 3.7.2.1 Reserved ................................................................................................. 3-84
2 3.7.2.2 Reserved ................................................................................................. 3-84
3 3.7.2.3 PDU Formats for Messages on the f-csch.................................................. 3-85
4 3.7.2.3.1 Reserved............................................................................................ 3-87
5 3.7.2.3.2 Message Body Contents ..................................................................... 3-87
6 3.7.2.3.2.1 System Parameters Message......................................................... 3-88
7 3.7.2.3.2.2 Access Parameters Message.......................................................... 3-96
8 3.7.2.3.2.3 Neighbor List Message.................................................................3-101
9 3.7.2.3.2.4 CDMA Channel List Message .......................................................3-104
10 3.7.2.3.2.5 Reserved .....................................................................................3-105
11 3.7.2.3.2.6 Reserved .....................................................................................3-106
12 3.7.2.3.2.7 Order Message ............................................................................3-107
13 3.7.2.3.2.8 Channel Assignment Message .....................................................3-108
14 3.7.2.3.2.9 Data Burst Message ....................................................................3-119
15 3.7.2.3.2.10 Authentication Challenge Message.............................................3-121
16 3.7.2.3.2.11 SSD Update Message.................................................................3-122
17 3.7.2.3.2.12 Feature Notification Message .....................................................3-123
18 3.7.2.3.2.13 Extended System Parameters Message.......................................3-124
19 3.7.2.3.2.14 Extended Neighbor List Message................................................3-134
20 3.7.2.3.2.15 Status Request Message ............................................................3-139
21 3.7.2.3.2.16 Service Redirection Message ......................................................3-143
22 3.7.2.3.2.17 General Page Message ...............................................................3-148
23 3.7.2.3.2.18 Global Service Redirection Message ...........................................3-151
24 3.7.2.3.2.19 TMSI Assignment Message ........................................................3-156
25 3.7.2.3.2.20 PACA Message...........................................................................3-157
26 3.7.2.3.2.21 Extended Channel Assignment Message ....................................3-159
27 3.7.2.3.2.22 General Neighbor List Message ..................................................3-187
28 3.7.2.3.2.23 User Zone Identification Message...............................................3-197
29 3.7.2.3.2.24 Private Neighbor List Message ...................................................3-198
30 3.7.2.3.2.25 Reserved ...................................................................................3-203
31 3.7.2.3.2.26 Sync Channel Message ..............................................................3-204
32 3.7.2.3.2.27 Extended Global Service Redirection Message ............................3-207
xviii
C.S0005-0-2 v1.0
CONTENTS
1 3.7.2.3.2.28 Extended CDMA Channel List Message ..................................... 3-211
2 3.7.2.3.2.29 User Zone Reject Message ......................................................... 3-212
3 3.7.3 f-dsch ......................................................................................................... 3-214
4 3.7.3.1 Reserved................................................................................................ 3-214
5 3.7.3.2 Reserved................................................................................................ 3-214
6 3.7.3.3 PDU Formats on the f-dsch .................................................................... 3-215
7 3.7.3.3.1 Reserved .......................................................................................... 3-216
8 3.7.3.3.2 Message Body Contents.................................................................... 3-216
9 3.7.3.3.2.1 Order Message............................................................................ 3-217
10 3.7.3.3.2.2 Authentication Challenge Message .............................................. 3-218
11 3.7.3.3.2.3 Alert With Information Message .................................................. 3-219
13 3.7.3.3.2.5 Reserved .................................................................................... 3-222
14 3.7.3.3.2.6 Analog Handoff Direction Message .............................................. 3-223
15 3.7.3.3.2.7 In-Traffic System Parameters Message ........................................ 3-225
16 3.7.3.3.2.8 Neighbor List Update Message .................................................... 3-229
17 3.7.3.3.2.9 Send Burst DTMF Message ......................................................... 3-230
18 3.7.3.3.2.10 Power Control Parameters Message ........................................... 3-231
19 3.7.3.3.2.11 Retrieve Parameters Message .................................................... 3-233
20 3.7.3.3.2.12 Set Parameters Message ........................................................... 3-234
21 3.7.3.3.2.13 SSD Update Message ................................................................ 3-235
22 3.7.3.3.2.14 Flash With Information Message ............................................... 3-236
23 3.7.3.3.2.15 Mobile Station Registered Message ............................................ 3-237
24 3.7.3.3.2.16 Status Request Message ........................................................... 3-239
25 3.7.3.3.2.17 Extended Handoff Direction Message......................................... 3-241
26 3.7.3.3.2.18 Service Request Message........................................................... 3-248
27 3.7.3.3.2.19 Service Response Message ........................................................ 3-250
28 3.7.3.3.2.20 Service Connect Message .......................................................... 3-252
29 3.7.3.3.2.21 Service Option Control Message ................................................ 3-254
30 3.7.3.3.2.22 TMSI Assignment Message ........................................................ 3-255
xix
C.S0005-0-2 v1.0
CONTENTS
1 3.7.3.3.2.23 Service Redirection Message ......................................................3-256
2 3.7.3.3.2.24 Supplemental Channel Assignment Message..............................3-259
3 3.7.3.3.2.25 Power Control Message..............................................................3-268
4 3.7.3.3.2.26 Extended Neighbor List Update Message ....................................3-290
5 3.7.3.3.2.27 Candidate Frequency Search Request Message ..........................3-296
6 3.7.3.3.2.28 Candidate Frequency Search Control Message ...........................3-308
7 3.7.3.3.2.29 Power Up Function Message ......................................................3-310
8 3.7.3.3.2.30 Power Up Function Completion Message ....................................3-312
9 3.7.3.3.2.31 General Handoff Direction Message ...........................................3-314
10 3.7.3.3.2.32 Resource Allocation Message .....................................................3-332
11 3.7.3.3.2.33 Resource Allocation Mini Message..............................................3-333
12 The base station shall set this field to ‘0’ if the mobile station is to perform the
13 primary inner loop estimation on the received Forward Fundamental Channel and
14 the base station is to multiplex the Power Control Subchannel on the Forward
15 Fundamental Channel. The base station shall set this field to ‘1’ if the mobile
16 station is to perform the primary inner loop estimation on the received Forward
17 Dedicated Control Channel and the base station is to multiplex the Power Control
18 Subchannel on the Forward Dedicated Control Channel.3.7.3.3.2.34 Extended
19 Release Message...........................................................................................3-333
20 3.7.3.3.2.34 Extended Release Message ........................................................3-334
21 3.7.3.3.2.35 Extended Release Mini Message.................................................3-336
22 3.7.3.3.2.36 Universal Handoff Direction Message .........................................3-337
23 3.7.3.3.2.37 Extended Supplemental Channel Assignment Message...............3-369
24 3.7.3.3.2.38 Forward Supplemental Channel Assignment Mini Message.........3-382
25 3.7.3.3.2.39 Reverse Supplemental Channel Assignment Mini Message .........3-384
26 3.7.3.3.2.40 Mobile Assisted Burst Operation Parameters Message ................3-386
27 3.7.3.3.2.41 User Zone Reject Message .........................................................3-389
28 3.7.3.3.2.42 User Zone Update Message ........................................................3-390
29 3.7.4 Orders .........................................................................................................3-391
30 3.7.4.1 Base Station Challenge Confirmation Order ............................................3-396
31 3.7.4.2 Service Option Request Order .................................................................3-397
32 3.7.4.3 Service Option Response Order ...............................................................3-398
33 3.7.4.4 Status Request Order .............................................................................3-399
34 3.7.4.5 Registration Accepted Order ...................................................................3-400
xx
C.S0005-0-2 v1.0
CONTENTS
1 3.7.4.6 Periodic Pilot Measurement Request Order ............................................. 3-401
2 3.7.4.7 Retry Order ........................................................................................... 3-402
3 3.7.5 Information Records .................................................................................... 3-405
4 3.7.5.1 Display .................................................................................................. 3-409
5 3.7.5.2 Called Party Number .............................................................................. 3-410
6 3.7.5.3 Calling Party Number............................................................................. 3-411
7 3.7.5.4 Connected Number ................................................................................ 3-413
8 3.7.5.5 Signal.................................................................................................... 3-415
9 3.7.5.6 Message Waiting .................................................................................... 3-420
10 3.7.5.7 Service Configuration............................................................................. 3-421
11 3.7.5.7.1 Channel Configuration for the Supplemental Channel Type-specific Field3-432
12 3.7.5.8 Called Party Subadddress ...................................................................... 3-433
13 3.7.5.9 Calling Party Subadddress ..................................................................... 3-434
14 3.7.5.10 Connected Subadddress....................................................................... 3-435
15 3.7.5.11 Redirecting Number ............................................................................. 3-436
16 3.7.5.12 Redirecting Subadddress...................................................................... 3-439
17 3.7.5.13 Meter Pulses ........................................................................................ 3-440
18 3.7.5.14 Parametric Alerting .............................................................................. 3-441
19 3.7.5.15 Line Control......................................................................................... 3-443
20 3.7.5.16 Extended Display ................................................................................. 3-444
21 3.7.5.17 Extended Record Type - International ................................................... 3-447
22 3.7.5.18 Reserved.............................................................................................. 3-448
23 3.7.5.19 Reserved.............................................................................................. 3-449
24 3.7.5.20 Non-Negotiable Service Configuration ................................................... 3-450
25 F.1 Introduction.......................................................................................................... F-1
26 F.2 Mobile Station Indicators ...................................................................................... F-2
27 F.2.1 Permanent Mobile Station Indicators................................................................ F-2
28 F.2.2 Semi-permanent Mobile Station Indicators ....................................................... F-3
29 F.3 NAM Indicators ..................................................................................................... F-4
30
xxi
C.S0005-0-2 v1.0
FIGURES
1 Figure 1.3.1-1. IS-2000 Signaling – General Architecture ............................................ 1-41
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-10
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.15-1. TMSI Zone Example .......................................................................... 2-23
9 Figure 2.6-1. Mobile Station Call Processing States ..................................................... 2-28
10 Figure 2.6.1-1. Mobile Station Initialization State ........................................................ 2-30
11 Figure 2.6.1.4-1. Mobile Station Internal Timing ......................................................... 2-42
12 Figure 2.6.2.1.1.1-1. Mobile Station Idle Slotted Mode Structure Example ................... 2-46
13 Figure 2.6.2.1.1.1.2.1-1. Multi-Slot Broadcast Message Transmission Example............ 2-48
14 Figure 2.6.2.1.1.1.2.2-1. Periodic Broadcast Paging Example....................................... 2-49
15 Figure 2.6.2.1.2.1-1. Quick Paging Channel Timeline .................................................. 2-54
16 Figure 2.6.3-1. System Access State ..........................................................................2-100
17 Figure 2.6.4-1. Mobile Station Control on the Traffic Channel State............................2-177
18 Figure 2.6.4.1.2.2-1. Mobile Station Service Subfunctions ..........................................2-191
19 Figure 2.6.4.1.7-1. Structure of PUF Attempt .............................................................2-207
20 Figure 2.6.4.4-1. Mobile Station Modes ......................................................................2-243
21 Figure 2.6.5.2-1. Systems and Networks Example ......................................................2-267
22 Figure 2.6.6.2.5.1.1-1. New Supplemental Channel Assignment Received while a Previous

23 Supplemental Channel Assignment is in Progress ......................2-335
24 Figure 2.6.6.2.5.1.1-2. New Supplemental Channel Assignment Received before a Previous

25 Supplemental Channel Assignment starts .................................2-335
26 Figure 2.6.6.3-1. Handoff Threshold Example if P_REV_IN_USEs is Less Than or Equal to
27 Three, or SOFT_SLOPEs is Equal to ‘000000’ .............................2-372
28 Figure 2.6.6.3-2. Handoff Threshold Example if P_REV_IN_USEs is Greater Than Three,

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

31 P_REV_IN_USEs = 3 or SOFT_SLOPEs = ‘000000’.......................2-374
xxii
C.S0005-0-2 v1.0
FIGURES
1 P_REV_IN_USEs > 3 and SOFT_SLOPEs is Not Equal to‘000000’ 2-375
2 Figure B-1A. Simple Call Flow, Mobile Station Origination Example Using Service Option
3 Negotiation with Service Option 1 .................................................B-2
4 Figure B-1B. Simple Call Flow, Mobile Station Origination Example Using Service
6 Figure B-2A. Simple Call Flow, Mobile Station Termination Example Using Service Option
8 Figure B-2B. Simple Call Flow, Mobile Station Termination Example Using Service
10 Figure B-3. Simple Call Flow, Mobile Station Initiated Call Disconnect Example .............B-6
11 Figure B-4. Simple Call Flow, Base Station Initiated Call Disconnect Example................B-6
12 Figure B-5. Simple Call Flow, Three-Party Calling Example............................................B-7
13 Figure B-6. Simple Call Flow, Call-Waiting Example ......................................................B-8
14 Figure B-7. Call Processing During Soft Handoff ............................................................B-9
15 Figure B-8. Call Processing During Sequential Soft Handoff (Part 1 of 2) ......................B-10
16 Figure B-8. Call Processing During Sequential Soft Handoff (Part 2 of 2) ......................B-11
17 Figure B-9. PACA Call Processing (Part 1 of 2) .............................................................B-12
18 Figure B-9. PACA Call Processing (Part 2 of 2) .............................................................B-13
19 Figure B-10. Call Flow for Same Frequency Hard Handoff Failure Recovery ..................B-14
20 Figure B-11. Call Flow for Inter-Frequency Hard Handoff Failure Recovery without SearchB-15
21 Figure B-12. Call Flow for Inter-Frequency Handoff (Single Search Using Candidate
22 Frequency Search Control Message) (Part 1 of 2) .........................B-16
25 Figure B-13. Call Flow for Inter-Frequency Handoff (Periodic Search Using Candidate
31 Figure B-14. Call Flow for Inter-Frequency Handoff (Single Search Using General Handoff
32 Direction Message) (Part 1 of 3)...................................................B-21
34 Direction Message) (Part 2 of 3)...................................................B-22
xxiii
C.S0005-0-2 v1.0
FIGURES
2 Direction Message) (Part 3 of 3) .................................................. B-23
3 Figure B-15. Call Flow for Inter-Frequency Handoff (Periodic Search Using General Handoff
11 Figure B-16. Call Flow for Periodic Search on F2 from F1, Failed Handoff Attempt to F3,
12 Continued Periodic Search of F2 from F1 (Part 1 of 3) ................. B-28
17 Figure B-17. Call Flow for Periodic Search on F2 from F1, Successful Handoff to F3,
18 Continued Periodic Search on F2 from F3 (Part 1 of 2) ................ B-31
19 Figure B-17. Call Flow for Periodic Search on F2 from F1, Successful Handoff to F3,
20 Continued Periodic Search on F2 from F3 (Part 2 of 2) ................ B-32
21 Figure B-18. Simple Call Flow Mobile Station Origination Example with Transmission on
22 Forward Supplemental Code Channels (Part 1 of 2)..................... B-33
24 Forward Supplemental Code Channels (Part 2 of 2)..................... B-34
26 Reverse Supplemental Code Channels (Part 1 of 2)...................... B-35
28 Reverse Supplemental Code Channels (Part 2 of 2)...................... B-36
29 Figure B-20. Simple Call Flow, Mobile Station Termination Example with Transmission on
30 Forward Supplemental Code Channel(s) (Part 1 of 3) ................... B-37
36 Reverse Supplemental Code Channel(s) (Part 1 of 3).................... B-40
xxiv
C.S0005-0-2 v1.0
FIGURES
2 Reverse Supplemental Code Channel(s) (Part 2 of 3) ....................B-41
4 Reverse Supplemental Code Channel(s) (Part 3 of 3) ....................B-42
5 Figure B-22. Active/Control Hold to Idle State Transition (BS Initiated) ........................B-43
6 Figure B-23. Active/Control Hold to Idle State Transition (MS Initiated) .......................B-43
7 Figure B-24. Active to Control Hold Mode Transition (BS Initiated) ...............................B-44
8 Figure B-25. Active to Control Hold Mode Transition (MS Initiated) ..............................B-44
9 Figure B-26. Control Hold to Active Mode Transition (BS Initiated) ................................B-45
10 Figure B-27. Control Hold to Active Mode Transition (MS Initiated) ...............................B-46
11
12
xxv
C.S0005-0-2 v1.0
TABLES
1 Table 2.3.1.1-1. Decimal to Binary Conversion Table ..................................................... 2-3
2 Table 2.3.1.1-2. BCD Mapping ...................................................................................... 2-4
3 Table 2.3.3-1. Station Class Mark ................................................................................. 2-6

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-8
6 Table 2.3.12.1-1. Auth_Signature Input Parameters .................................................... 2-10
7 Table 2.4.1-1. Monitored Quantities and Statistics ....................................................... 2-24
8 Table 2.4.2-1. Accumulated PCH Channel Statistics.................................................... 2-24
9 Table 2.6.6.2.1-1. Searcher Window Sizes ..................................................................2-280
10 Table 2.6.6.2.1-2. Search Window Offset ....................................................................2-281
11 Table 2.6.6.2.3-1. Handoff Drop Timer Expiration Values ...........................................2-283
12 Table 2.6.6.2.5.1-1. Search Parameter Settings ..........................................................2-292
13 Table 2.6.6.2.8.3.2-1. Search Period Values ...............................................................2-357
14 Table 2.6.7.1-1. Hash Function Modifier ....................................................................2-377
15 Table 2.7.1.3-1. Messages on r-csch ..........................................................................2-386
16 Table 2.7.1.3.2.1-1. Registration Type (REG_TYPE) Codes...........................................2-387
17 Table 2.7.1.3.2.1-2. RETURN_CAUSE Codes ..............................................................2-388
18 Table 2.7.1.3.2.4-1. REQUEST_MODE Codes .............................................................2-395
19 Table 2.7.1.3.2.4-2. Number Types ............................................................................2-396
20 Table 2.7.1.3.2.4-3. Numbering Plan Identification .....................................................2-396
21 Table 2.7.1.3.2.4-4. Representation of DTMF Digits....................................................2-397
22 Table 2.7.1.3.2.4-5. Encryption Algorithms Supported ...............................................2-398
23 Table 2.7.1.3.2.4-6. Channel Indicator .......................................................................2-399
24 Table 2.7.1.3.2.5-1. Channel indicator .......................................................................2-405
25 Table 2.7.2.3-1. Messages on r-dsch ..........................................................................2-415
26 Table 2.7.2.3.2.7-1. Recommended DTMF Pulse Width ...............................................2-428
27 Table 2.7.2.3.2.7-2. Recommended Minimum Inter-digit Interval ................................2-429
28 Table 2.7.2.3.2.12-1. REQ_PURPOSE Codes...............................................................2-435
29 Table 2.7.2.3.2.13-1. RESP_PURPOSE Codes .............................................................2-437
30 Table 2.7.3-1. Order and Order Qualification Codes Used on the r-dsch and the r-csch
31 (Part 1 of 4)...............................................................................2-467
xxvi
C.S0005-0-2 v1.0
TABLES
2 (Part 2 of 4) .............................................................................. 2-468
4 (Part 3 of 4) .............................................................................. 2-469
6 (Part 4 of 4) .............................................................................. 2-470
7 Table 2.7.3.4-1. REJECTED_PDU_TYPE codes............................................................ 2-475
8 Table 2.7.4-1. Information Record Types (Part 1 of 2) ................................................. 2-476
9 Table 2.7.4-1. Information Record Types (Part 2 of 2) ................................................. 2-477
10 Table 2.7.4.4-1. Presentation Indicators .................................................................... 2-481
11 Table 2.7.4.4-2. Screening Indicators ........................................................................ 2-482

12 Table 2.7.4.15-1. OP_MODE for P_REV_IN_USEs Less Than or Equal to Three ........... 2-496
13 Table 2.7.4.15-2. OP_MODE for P_REV_IN_USEs Greater Than Three ........................ 2-497
14 Table 2.7.4.17-1. Forward Fundamental Traffic Channel Transmission Rates for Forward
15 Multiplex Option 1.................................................................... 2-501
16 Table 2.7.4.17-2. Forward Fundamental Traffic Channel Transmission Rates for Forward
18 Table 2.7.4.17-3. Reverse Fundamental Traffic Channel Transmission Rates for Reverse
20 Table 2.7.4.17-4. Reverse Fundamental Traffic Channel Transmission Rates for Reverse
22 Table 2.7.4.18-1. FOR_TRAFFIC Codes...................................................................... 2-508
23 Table 2.7.4.18-2. REV_TRAFFIC Codes...................................................................... 2-509
24 Table 2.7.4.18-3. User information Encryption Modes................................................ 2-509
25 Table 2.7.3.18-4. SCH Identifier ................................................................................ 2-514
26 Table 2.7.4.19-1. Subaddress Types .......................................................................... 2-516
27 Table 2.7.4.19-2. Odd/Even Indicator ....................................................................... 2-517
28 Table 2.7.4.25-1. Set of supported Reverse Pilot Gating Rates ..................................... 2-525
29 Table 2.7.4.25-2. RLP Capability Information Block .................................................... 2-526
30 Table 2.7.4.27.1-1. Forward Channel Radio Configurations Supported ....................... 2-531
31 Table 2.7.4.27.1-2. Reverse Channel Radio Configurations Supported ........................ 2-532
32 Table 2.7.4.27.2-1. DCCH Frame Size Supported ....................................................... 2-533
33 Table 2.7.4.27.3-1. Block Size .................................................................................... 2-536
xxvii
C.S0005-0-2 v1.0
TABLES
1 Table 2.7.4.28-1. Forward Fundamental Channel Transmission Rates for MO_FOR_FCH

2 equal to 1 .................................................................................2-543
3 Table 2.7.4.28-2. Forward Fundamental Channel Transmission Rates for MO_FOR_FCH

4 equal to 2 .................................................................................2-543
5 Table 2.7.4.28-3. Reverse Fundamental Channel Transmission Rates for MO_REV_FCH

6 equal to 1 .................................................................................2-544
7 Table 2.7.4.28-4. Reverse Fundamental Channel Transmission Rates for MO_REV_FCH

8 equal to 2 .................................................................................2-545
9 Table 2.7.4.34-1. Geo-location Codes .........................................................................2-547
10 Table 3.7.2.3-1. f-csch Messages................................................................................. 3-86
11 Table 3.7.2.3.2.1-1. Value of Zone Timer ..................................................................... 3-90
12 Table 3.7.2.3.2.1-2. Base Station Classes.................................................................... 3-91
13 Table 3.7.2.3.2.3-1. Neighbor Configuration Field.......................................................3-102
14 Table 3.7.2.3.2.8-1. Assignment Mode .......................................................................3-111
15 Table 3.7.2.3.2.8-2. Message Encryption Modes .........................................................3-112
16 Table 3.7.2.3.2.8-3. Default Configuration .................................................................3-116
17 Table 3.7.2.3.2.13-1. Preferred MSID Types................................................................3-126
18 Table 3.7.2.3.2.13-2. QPCH Indicator Data Rate..........................................................3-132
19 Table 3.7.2.3.2.13-3 Quick Paging Channel Transmit Power Level ...............................3-132
20 Table 3.7.2.3.2.14-1. Neighbor Configuration Field.....................................................3-135
21 Table 3.7.2.3.2.14-2. Search Priority Field .................................................................3-137
22 Table 3.7.2.3.2.15-1. Qualification Information Type ..................................................3-139
23 Table 3.7.2.3.2.15-2. Status Information Record Types...............................................3-140
24 Table 3.7.2.3.2.15-3. Operating Mode for MOB_P_REV Less Than or Equal to Three....3-142
25 Table 3.7.2.3.2.15-4. Operating Mode for MOB_P_REV Greater Than Three.................3-142
26 Table 3.7.2.3.2.16-1. Redirection Types......................................................................3-143
27 Table 3.7.2.3.2.16-2. Redirection Record Types ..........................................................3-144
28 Table 3.7.2.3.2.16-3. SYS_ORDERING .......................................................................3-146
29 Table 3.7.2.3.2.20-1. Purpose of PACA Message .........................................................3-157
30 Table 3.7.2.3.2.20-2. Value of PACA State Timer ........................................................3-158
31 Table 3.7.2.3.2.21-1. Assignment Mode......................................................................3-165
32 Table 3.7.2.3.2.21-2. Default Configuration................................................................3-166
xxviii
C.S0005-0-2 v1.0
TABLES
1 Table 3.7.2.3.2.21-3. Radio Configurations ................................................................ 3-169
2 Table 3.7.2.3.2.21-4. Channel Indicator ..................................................................... 3-176
3 Table 3.7.2.3.2.21-5. Pilot Record Types .................................................................... 3-178
4 Table 3.7.2.3.2.21-6. OTD Transmit Power Level........................................................ 3-179
5 Table 3.7.2.3.2.22-1. Search Mode Field .................................................................... 3-189
6 Table 3.7.2.3.2.22-2. Neighbor Configuration Field .................................................... 3-191
7 Table 3.7.2.3.2.22-3. Search Priority Field ................................................................. 3-193
8 Table 3.7.2.3.2.22-4. Cellular System A/B................................................................. 3-195
9 Table 3.7.2.3.2.22-5. Neighbor Pilot Record Types...................................................... 3-195
10 Table 3.7.2.3.2.24-1. Radio Interface Type ................................................................. 3-199
11 Table 3.7.2.3.2.26-1. Paging Channel Data Rate ........................................................ 3-206
12 Table 3.7.2.3.2.29-1. Rejection Action Indicators ........................................................ 3-213
13 Table 3.7.3.3-1. f-dsch Messages (Part 1 of 2) ............................................................ 3-215
14 Table 3.7.3.3-1. f-dsch Messages (Part 2 of 2) ............................................................ 3-216
15 Table 3.7.3.3.2.6-1. Analog Channel Type.................................................................. 3-224
16 Table 3.7.3.3.2.17-1. Traffic Channel Preamble Length .............................................. 3-246
17 Table 3.7.3.3.2.18-1. REQ_PURPOSE Codes .............................................................. 3-248
18 Table 3.7.3.3.2.19-1. RESP_PURPOSE Codes............................................................. 3-250
19 Table 3.7.3.3.2.25-1. Closed Loop Power Control Step Size......................................... 3-269
20 Table 3.7.3.3.2.25-2. Target Frame Error Rate........................................................... 3-271
21 Table 3.7.3.3.2.25-3. RPC_ADJ_REC_TYPE and RPC_ADJ_REC_LEN fields ................ 3-274
22 Table 3.7.2.3.2.25-4. Type Specific Fields for RECORD_TYPE = ‘0000’ ........................ 3-275
25 Table 3.7.3.3.2.26-1. NGHBR_SRCH_MODE Field...................................................... 3-291
26 Table 3.7.3.3.2.26-2. SEARCH_PRIORITY Field.......................................................... 3-293
27 Table 3.7.3.3.2.27-1. SEARCH_TYPE Codes............................................................... 3-297
28 Table 3.7.3.3.2.27-2. SEARCH_MODE Types ............................................................. 3-297
29 Table 3.7.3.3.2.27-3. CF_NGHBR_SRCH_MODE Field ................................................ 3-303
30 Table 3.7.3.3.2.34-1. Channel Indicator ..................................................................... 3-335
xxix
C.S0005-0-2 v1.0
TABLES
1 Table 3.7.3.3.2.34-2 Actual Reverse Pilot Gating rate ..................................................3-335
2 Table 3.7.3.3.2.36-1. Channel Indicator ......................................................................3-355
3 Table 3.7.3.3.2.37-2. REV_WALSH_ID Field ................................................................3-373
4 Table 3.7.3.3.2.37-1. SCH Data Rate ..........................................................................3-374
5 Table 3.7.3.3.2.37-3. FOR_SCH_DURATION and REV_SCH_DURATION Fields .............3-375
6 Table 3.7.4-1. Order and Order Qualification Codes Used on the f-csch and the f-dsch (Part
7 1 of 3) .......................................................................................3-392
9 2 of 3) .......................................................................................3-394
11 3 of 3) .......................................................................................3-395
12 Table 3.7.4.4-1. Status Request ORDQ Values ...........................................................3-399
13 Table 3.7.4.7-1 Retry Delay Type ................................................................................3-402
14 Table 3.7.4.7-1 Retry Delay for RETRY_TYPE ‘001’ ......................................................3-403
15 Table 3.7.5-1. Information Record Types (Part 1 of 3) .................................................3-406
18 Table 3.7.5.5-1. Signal Type ......................................................................................3-415
19 Table 3.7.5.5-2. Alert Pitch ........................................................................................3-416
20 Table 3.7.5.5-3. Tone Signals (SIGNAL_TYPE = ‘00’)....................................................3-417
21 Table 3.7.5.5-4. ISDN Alerting (SIGNAL_TYPE = ‘01’) ..................................................3-418
22 Table 3.7.5.5-5. IS-54B Alerting (SIGNAL_TYPE = ‘10’)................................................3-419
23 Table 3.7.5.7-1. FOR_TRAFFIC Codes ........................................................................3-425
24 Table 3.7.5.7-2. REV_TRAFFIC Codes ........................................................................3-426
25 Table 3.7.5.7-3. DCCH Frame Size..............................................................................3-429
26 Table 3.7.5.11-1. Redirection Reason .........................................................................3-438
27 Table 3.7.5.16-1. Display Type...................................................................................3-444
28 Table 3.7.5.16-2. Mandatory Control Tags and Display Text Tags ...............................3-445
29 Table 3.7.5.20-1. Reverse Pilot Gating rate..................................................................3-453
30 Table 3.7.5.20-2. Logical to Physical Mapping indicator ...............................................3-453
31 Table 3.7.5.20-3. Logical Resource Identifier. .............................................................3-454
32 Table 3.7.5.20-4. Physical Resource Identifier. ...........................................................3-454
xxx
C.S0005-0-2 v1.0
TABLES
1 Table D-1. Time Limits (Part 1 of 4) .............................................................................. D-1
5 Table D-2. Other Constants ......................................................................................... D-5
6 Table E-1. Retrievable and Settable Parameters (Part 1 of 10).........................................E-2
14 Table E-1. Retrievable and Settable Parameters (Part 9 of 10).......................................E-10
15 Table E-1. Retrievable and Settable Parameters (Part 10 of 10).....................................E-11
16 Table F.2.1-1. Permanent Mobile Station Indicators ....................................................... F-2
17 Table F.2.2-1. CDMA Semi-permanent Mobile Station Indicators.................................... F-3
18 Table F.3-1. NAM Indicators (Part 1 of 2) ....................................................................... F-4
19 Table F.3-1. NAM Indicators (Part 2 of 2) ....................................................................... F-5
20
xxxi
TIA/EIA/IS-2000.5-2
FOREWORD
1 1. General. This section defines the terms and numeric indications used in this
2 document. This section also describes the time reference used in the CDMA system and the
3 tolerances used throughout the document.
4 2. Requirements for Mobile Station CDMA Operation. This section describes the
5 requirements for CDMA-analog dual-mode mobile stations operating in the CDMA mode. A
6 mobile station complying with these requirements will be able to operate with CDMA base
7 stations complying with this document.
8 3. Requirements for Base Station CDMA Operation. This section describes the
9 requirements for CDMA base stations. A base station complying with these requirements
10 will be able to operate in the CDMA mode with mobile stations complying with this
11 document.
12 Annex A. Reserved.
13 Annex B. CDMA Call Flow Examples. This informative annex provides examples of
14 simple call flows in the CDMA system.
15 Annex C. Reserved.
16 Annex D. CDMA Constants. This normative annex contains tables that give specific
17 values for the constant identifiers found in Section 2 and Section 3.
18 Annex E. CDMA Retrievable and Settable Parameters. This normative annex describes
19 the mobile station parameters that the base station can set and retrieve.
20 Annex F. Mobile Station Database. This informative annex describes a database model
21 that can be used for dual-mode mobile stations complying with this document.
xxxii
C.S0005-0-2 v1.0
NOTES
1 1. Compatibility, as used in connection with cdma2000, is understood to mean: any

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

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

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

4 requirement to implement layering.
xxxiv
C.S0005-0-2 v1.0
REFERENCES
1 The following standards contain provisions which, through reference in this text, constitute
2 provisions of this Standard. At the time of publication, the editions indicated were valid.
3 All standards are subject to revision, and parties to agreements based on this Standard are
4 encouraged to investigate the possibility of applying the most recent editions of the
5 standards indicated below.
1. Reserved.
2. C.S0002-0-2, Physical Layer Standard for cdma2000 Spread Spectrum Systems,
Addendum 2.
3. C.S0003-0-2, Medium Access Control (MAC) Standard for cdma2000 Spread
Spectrum Systems, Addendum 2.
4. C.S0004-0-2, Signaling Link Access Control (LAC) Standard for cdma2000 Spread
Spectrum Systems, Addendum 2.
5. Reserved.
6. C.S0006-0-2, Analog Signaling Standard for cdma2000 Spread Spectrum
Systems, Addendum 2.
7. ANSI/EIA/TIA-691, ANSI Enhanced Analog IS-691, date pending.
8. 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.
9. ANSI TI.610-1994, Generic Procedures for the Control of ISDN Supplementary
Services, August, 1994.
10. ANSI J-STD-018, Recommended Minimum Performance Requirements for 1.8 to
2.0 GHz Code Division Multiple Access (CDMA) Personal Stations.
11. ANSI J-STD-019, Recommended Minimum Performance Requirements for Base
Stations Supporting 1.8 to 2.0 GHz Code Division Multiple Access (CDMA)
Personal Stations.
12. ANSI X3.4-1986, Coded Character Set - 7-bit American National Standard Code
for Information Interchange, 1992.
13. C.S0010-0, Recommended Minimum Performance Standards for Base Stations
Supporting Dual-Mode Spread Spectrum Mobile Stations.
14. C.S0011-0, Recommended Minimum Performance Standards for Dual-Mode
Spread Spectrum Mobile Stations.
15. TIA/EIA-553-A, Core Analog Standard 800 MHz Mobile Station - Land Station
Compatibility Specification with Authentication, date pending.
xxxv
C.S0005-0-2 v1.0
REFERENCES
16. TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem Operations,

December 1997.
17. C.S0015-0, Short Message Services for Spread Spectrum Cellular Systems.
18. Common Cryptographic Algorithms, Revision C, 1997. An EAR-controlled
document subject to restricted distribution. Contact the Telecommunications
Industry Association, Arlington, VA.
19. ITU-T Recommendation E.163, Numbering Plan for the International Telephone
Service, 1988. Note: merged with E.164.
20. ITU-T Recommendation E.164 (I.331), Numbering Plan for the ISDN Era, 1991.
21. ITU-T Recommendation E.212, Identification Plan for Land Mobile Stations,
1988.
22. ITU-T Recommendation F.69, The International Telex Service–Service and
Operational Provisions of Telex Destination Codes and Telex Network
Identifications Codes, 1994.
23. ITU-T Recommendation G.162, Characteristics of Compandors for Telephony.
24. ITU-T Recommendation X.121, International Numbering Plan for Public Data
Networks, 1992.
25. EIA/TIA/IS-54-B, Cellular System Dual-Mode Mobile Station - Base Station
Compatibility Standard, April 1992.
26. IEEE Standard 661-1979, Method for Determining Objective Loudness Ratings
of Telephone Connections, 1979.
27. Interface Specification for Common Cryptographic Algorithms, Rev C, 1997.
Contact the Telecommunications Industry Association, Arlington, VA.
28. TIA/EIA/IS-91, Mobile Station-Base Station Compatibility Standard for 800
MHz Analog Cellular, October 1994.
29. TIA/EIA/IS-125, Recommended Minimum Performance Standard for Digital
Cellular Spread Spectrum Speech Service Option 1, May 1995.
30. TIA/EIA-95-B, Mobile Station-Base Station Compatibility Standard for Dual-
Mode Spread Spectrum Cellular System, November 1998.
31. TIA/EIA/IS-136, 800 MHz TDMA Cellular-Radio Interface-Mobile Station-Base
Station Compatibility, December 1994.
32. C.S0016-0, Over-the-Air Service Provisioning of Mobile Stations in Spread
Spectrum Systems, June 1998.
33. TIA/EIA/IS-735, Enhancements to TIA/EIA-41-D & TIA/EIA-664 for Advanced
Features in Wideband Spread Spectrum Systems, January 1998.
34. TSB16, Assignment of Access Overload Classes in the Cellular.
Telecommunications Services, March 1985.
35. TSB29-C, International Implementation of Wireless Telecommunication.
xxxvi
C.S0005-0-2 v1.0
REFERENCES
Systems Compliant with TIA/EIA-41, date pending.

36. TSB39-A, Message Type Assignments for the Extended Protocol Facility of
ANSI/EIA/TIA-553, EIA/TIA/IS-54, TIA/EIA/IS-88 and TIA/EIA/IS-95, October
1994.
37. TSB50, User Interface for Authentication Key Entry, March 1993.
38. TSB58, Administration of Parameter Value Assignments for TIA/EIA Wideband
Spread Spectrum Standards.
39. TIA/EIA/IS-707-A-2, Data Service Options For Spread Spectrum Systems-
Addendum 2, June 2000.
1 The following standards contain provisions which, through reference in this text, constitute
2 provisions of this Standard. At the time of publication, the editions indicated were valid.
3 All standards are subject to revision, and parties to agreements based on this Standard are
4 encouraged to investigate the possibility of applying the most recent editions of the
5 standards indicated below. ANSI and TIA maintain registers of currently valid national
6 standards published by them.
7 —American National Standards:
8 1.ANSI/EIA/TIA-691, ANSI Enhanced Analog IS-691, date pending.
9 2.ANSI T1.607-1990, Integrated Services Digital Network (ISDN)–Layer 3 Signaling

10 Specification for Circuit Switched Bearer Service for Digital Subscriber Signaling
11 System Number 1 (DSS1), July 1990.
12 3.ANSI TI.610-1994, Generic Procedures for the Control of ISDN Supplementary

13 Services, August, 1994.
14 4.ANSI J-STD-018, Recommended Minimum Performance Requirements for 1.8 to 2.0

15 GHz Code Division Multiple Access (CDMA) Personal Stations.
16 5.ANSI J-STD-019, Recommended Minimum Performance Requirements for Base

17 Stations Supporting 1.8 to 2.0 GHz Code Division Multiple Access (CDMA) Personal
18 Stations.
19 6.ANSI X3.4-1986, Coded Character Set - 7-bit American National Standard Code for
20 Information Interchange, 1992.
21 7.TIA/EIA-97-C, Recommended Minimum Performance Standards for Base Stations

22 Supporting Dual-Mode Spread Spectrum Mobile Stations, date pending.
23 8.TIA/EIA-98-C, Recommended Minimum Performance Standards for Dual-Mode

24 Spread Spectrum Mobile Stations, date pending.
25 9.TIA/EIA-553-A, Core Analog Standard 800 MHz Mobile Station - Land Station
26 Compatibility Specification with Authentication, date pending.
27 10.TIA/EIA-41-D, Cellular Radiotelecommunications Intersystem Operations, December

28 1997.
xxxvii
C.S0005-0-2 v1.0
REFERENCES
1 11.TIA/EIA-637-A, Short Message Services for Spread Spectrum Cellular Systems.
2 —Other Standards:
3 12.Common Cryptographic Algorithms, Revision C, 1997. An EAR-controlled document

4 subject to restricted distribution. Contact the Telecommunications Industry
5 Association, Arlington, VA.
6 13.ITU-T Recommendation E.163, Numbering Plan for the International Telephone

7 Service, 1988. Note: merged with E.164.
8 14.ITU-T Recommendation E.164 (I.331), Numbering Plan for the ISDN Era, 1991.
9 15.ITU-T Recommendation E.212, Identification Plan for Land Mobile Stations, 1988.
10 16.ITU-T Recommendation F.69, The International Telex Service–Service and

11 Operational Provisions of Telex Destination Codes and Telex Network Identifications
12 Codes, 1994.
13 17.ITU-T Recommendation G.162, Characteristics of Compandors for Telephony.
14 18.ITU-T Recommendation X.121, International Numbering Plan for Public Data

15 Networks, 1992.
16 19.EIA/TIA/IS-54-B, Cellular System Dual-Mode Mobile Station - Base Station

17 Compatibility Standard, April 1992.
18 20.IEEE Standard 661-1979, Method for Determining Objective Loudness Ratings of

19 Telephone Connections, 1979.
20 21.Interface Specification for Common Cryptographic Algorithms, Rev C, 1997. Contact

21 the Telecommunications Industry Association, Arlington, VA.
22 22.TIA/EIA/IS-91, Mobile Station-Base Station Compatibility Standard for 800 MHz

23 Analog Cellular, October 1994.
24 23.TIA/EIA/IS-125, Recommended Minimum Performance Standard for Digital Cellular

25 Spread Spectrum Speech Service Option 1, May 1995.
26 24.TIA/EIA/IS-136, 800 MHz TDMA Cellular-Radio Interface-Mobile Station-Base

27 Station Compatibility, December 1994.
28 25.TIA/EIA/IS-683-A, Over-the-Air Service Provisioning of Mobile Stations in Spread

29 Spectrum Systems, June 1998.
30 26.TIA/EIA/IS-735, Enhancements to TIA/EIA-41-D & TIA/EIA-664 for Advanced

31 Features in Wideband Spread Spectrum Systems, January 1998.
32 27.TSB16, Assignment of Access Overload Classes in the Cellular Telecommunications

33 Services, March 1985.
34 28.TSB29-C, International Implementation of Wireless Telecommunication Systems

35 Compliant with TIA/EIA-41, date pending.
36 29.TSB39-A, Message Type Assignments for the Extended Protocol Facility of
xxxviii
C.S0005-0-2 v1.0
REFERENCES
1 ANSI/EIA/TIA-553, EIA/TIA/IS-54, TIA/EIA/IS-88 and TIA/EIA/IS-95, October

2 1994.
3 30.TSB50, User Interface for Authentication Key Entry, March 1993.
4 31.TSB58-A, Administration of Parameter Value Assignments for TIA/EIA Wideband

5 Spread Spectrum Standards.
xxxix
C.S0005-0-2 v1.0
1 1. GENERAL
2 1.1 Terms and Numeric Information
3 1.1.1 Terms
4 Abbreviated Alert. An abbreviated alert is used to remind the mobile station user that
5 previously selected alternative routing features are still active.
6 AC. See Authentication Center.
7 Access Attempt. The entire process of sending one message and receiving (or failing to
8 receive) an acknowledgment for that message, consisting of one or more access sub-
9 attempts. See also Access Probe, Access Probe Sequence, and Access Sub-attempt.
10 Access Channel. A Reverse CDMA Channel used by mobile stations for communicating to
11 the base station. The Access Channel is used for short signaling message exchanges such
12 as call originations, responses to pages, and registrations. The Access Channel is a slotted
13 random access channel.
14 Access Channel Message. The information part of an access probe consisting of the
15 message body, length field, and CRC.
16 Access Channel Message Capsule. An Access Channel message plus the padding.
17 Access Channel Preamble. The preamble of an access probe consisting of a sequence of

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

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

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

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

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

36 optionally transmitted by a CDMA base station.
37 Auxiliary Transmit Diversity Pilot Channel. A pilot channel, counterpart to an Auxiliary

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

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

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

14 contains 64 code channels. Code channel zero is assigned to the Pilot Channel. Code
15 channels 1 through 7 may be assigned to either the Paging Channels or the Traffic
16 Channels. Code channel 32 may be assigned to either a Sync Channel or a Traffic Channel.
17 The remaining code channels may be assigned to Traffic Channels.
18 Code Division Multiple Access (CDMA). A technique for spread-spectrum multiple-access

19 digital communications that creates channels through the use of unique code sequences.
20 Code Symbol. The output of an error-correcting encoder. Information bits are input to the
21 encoder and code symbols are output from the encoder. See Convolutional Code.
22 Configuration Change Indicator. A one-bit datum, sent on the Quick Paging Channel.
23 Appearance of the Configuration Change Indicator in the Quick Paging Channel serves to
24 alert a slotted mode mobile station, operating in the idle state, that, after performing an idle
25 handoff, it should monitor the Paging Channel, in order to determine if it should update its
26 stored parameters.
27 Confirmation of Delivery. A notification sent by the LAC sublayer to Layer 3 at the

28 sender, when the LAC entity at the sender receives the acknowledgment for a specific PDU
29 sent in assured mode.
30 Convolutional Code. A type of error-correcting code. A code symbol can be considered as

31 modulo 2 the convolution of the input data sequence with the impulse response of a
32 generator function.
33 CRC. See Cyclic Redundancy Code.
34 Cyclic Redundancy Code (CRC). A class of linear error detecting codes that generate
35 parity check bits by finding the remainder of a polynomial division. See also Frame Quality
36 Indicator.
37 dBc. The ratio (in dB) of the sideband power of a signal, measured in a given bandwidth at
38 a given frequency offset from the center frequency of the same signal, to the total inband
39 power of the signal.
40 dBm. A measure of power expressed in terms of its ratio (in dB) to one milliwatt.
1-4
C.S0005-0-2 v1.0
1 dBm/Hz. A measure of power spectral density. The ratio, dBm/Hz, is the power in one
2 Hertz of bandwidth, where power is expressed in units of dBm.
3 dBW. A measure of power expressed in terms of its ratio (in dB) to one Watt.
4 Dedicated Control Channel. A portion of a Traffic Channel (Forward or Reverse) that

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

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

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

17 tones, one from a group of low frequencies and another from a group of high frequencies.
18 Each group of frequencies consists of four frequencies.
19 Eb. A measure of the energy in a signal, at some point in a communication system, per
20 information bit conveyed by that signal, or an average value of such energies. Its relevance
21 to system performance is most often expressed by its ratio to additive noise and
22 interference, such as in Eb/N0 or Eb/I0. Such ratios are dimensionless, and are usually
23 expressed in dB units.
24 Ec/Io. A notation used to represent a dimensionless ratio of the average power of some
25 code-distinguished CDMA signal channel, typically a pilot, to the total power comprised of
26 signal plus interference, within the signal bandwidth. It is usually expressed in dB units.
27 Effective Radiated Power (ERP). The product of the power supplied to the antenna and
28 its gain relative to a half-wave dipole in a given direction.
29 EIRP. See Equivalent Isotropic Radiated Power.
30 Electronic Serial Number (ESN). A 32-bit number assigned by the mobile station
31 manufacturer, uniquely identifying the mobile station equipment.
32 Encoder Tail Bits. A fixed sequence of bits added to the end of a block of data to reset the
33 convolutional encoder to a known state.
34 Equivalent Isotropically Radiated Power (EIRP). The product of the power supplied to
35 the antenna and the antenna gain in a direction relative to an isotropic antenna.
36 Erasure Indicator Bit. A bit used in the Rate Set 2 Reverse Traffic Channel frame
37 structure to indicate an erased Forward Fundamental Code Channel or Forward Dedicated
38 Control Channel frame.
39 ERP. See Effective Radiated Power.
1-5
C.S0005-0-2 v1.0
1 ESN. See Electronic Serial Number.

2 f-csch. Forward common signaling logical channel.
3 f-dsch. Forward dedicated signaling logical channel.
4 Fade Timer. A timer kept by the mobile station as a measure of Forward Traffic Channel
5 continuity. If the fade timer expires, the mobile station drops the call.
6 Flash. An indication sent on the Reverse CDMA Channel indicating that the user directed
7 the mobile station to invoke special processing.
8 Foreign NID Roamer. A mobile station operating in the same system (SID) but in a
9 different network (NID) from the one in which service was subscribed. See also Foreign SID
10 Roamer and Roamer.
11 Foreign SID Roamer. A mobile station operating in a system (SID) other than the one from
12 which service was subscribed. See also Foreign NID Roamer and Roamer.
13 Forward CDMA Channel. A CDMA Channel from a base station to mobile stations. The
14 Forward CDMA Channel contains one or more code channels that are transmitted on a
15 CDMA Frequency Assignment using a particular pilot PN offset. The code channels are
16 associated with the Pilot Channel, Sync Channel, Paging Channels, and Traffic Channels.
17 The Forward CDMA Channel always carries a Pilot Channel and may carry up to one Sync
18 Channel, up to seven Paging Channels, and up to 63 Traffic Channels, as long as the total
19 number of channels, including the Pilot Channel, is no greater than 64.
20 Forward Dedicated Control Channel. A Dedicated Control Channel that is transmitted on

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

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

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

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

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

8 transmission data rate, the frame contents (primary traffic, secondary traffic, or signaling
9 traffic), and whether there are detected errors in the frame.
10 Frame Offset. A time skewing of Traffic Channel frames from System Time in integer
11 multiples of 1.25 ms. The maximum frame offset is 18.75 ms.
12 Frame Quality Indicator. The CRC check applied to 9.6 and 4.8 kbps Traffic Channel
13 frames (for Rate Set 1) and 14.4, 7.2, 3.6 and 1.8 kbps Traffic Channel frames (for Rate Set
14 2).
15 Full TMSI. The combination of TMSI_ZONE and TMSI_CODE. The full TMSI is a globally
16 unique address for the mobile station.
17 Fundamental Channel. A portion of a Traffic Channel that can carry a combination of

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

30 Channel. Hard handoffs occur when the mobile station is transferred between disjoint
31 Active Sets, when the CDMA Frequency Assignment changes, when the frame offset
32 changes, or when the mobile station is directed from a CDMA Traffic Channel to an analog
33 voice channel. See also Soft Handoff.
34 Hash Function. A function used by the mobile station to select one out of N available
35 resources. The hash function distributes the available resources uniformly among a
36 random sample of mobile stations.
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-7
C.S0005-0-2 v1.0
1 Home System. The cellular or PCS system in which the mobile station subscribes for
2 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 from one base
7 station to another, when the mobile station is in the Mobile Station Idle State.
8 Implicit Registration. A registration achieved by a successful transmission of an

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

21 or received information is transferred in pipeline fashion, within each station, in well-
22 defined encapsulated data units between otherwise decoupled processing entities (“layers”).
23 A layer is defined in terms of its communication protocol to a peer layer in another entity
24 and the services it offers to the next higher layer in its own entity.
25 Layer 1. Layer 1 provides for the transmission and reception of radio signals between the
26 base station and the mobile station. Also see Physical Layer.
27 Layer 2. Layer 2 provides for the correct transmission and reception of signaling messages,
28 including partial duplicate detection. Layer 2 makes use of the services provided by Layer
29 1. See also Layering and Layer 3.
30 Layer 3. Layer 3 provides the control messaging for the cellular or PCS telephone system.
31 Layer 3 originates and terminates signaling messages according to the semantics and
32 timing of the communication protocol between the base station and the mobile station.
33 Layer 3 makes use of the services provided by Layer 2. See also Layering and Layer 2.
34 Local Control. An optional mobile station feature used to perform manufacturer-specific

35 functions.
36 Logical Channel. A communication path between the mobile station and the base station,
37 described in terms of the intended use of, and access to, the transferred data, and direction
38 of transfer. A logical channel can be “mapped” to and from one or more physical channels.
1-8
C.S0005-0-2 v1.0
1 Logical-to-physical Mapping. The technique for forming associations between logical and
2 physical channels.
3 Long Code. A PN sequence with period 242 - 1 that is used for scrambling on the Forward
4 CDMA Channel and spreading on the Reverse CDMA Channel. The long code uniquely
5 identifies a mobile station on both the Reverse Traffic Channel and the Forward Traffic
6 Channel. The long code provides limited privacy. The long code also separates multiple
7 Access Channels on the same CDMA Channel. See also Public Long Code and Private Long
8 Code.
9 Long Code Mask. A 42-bit binary number that creates the unique identity of the long code.
10 See also Public Long Code, Private Long Code, Public Long Code Mask, and Private Long
11 Code Mask.
12 LSB. Least significant bit.
13 Maximal Length Sequence (m-Sequence). A binary sequence of period 2n - 1, n being a

14 positive integer, with no internal periodicities. A maximal length sequence can be
15 generated by a tapped n-bit shift register with linear feedback.
16 MCC. See Mobile Country Code.
17 Mcps. Megachips per second (106 chips per second).
18 MCSB. See Message Control and Status Block.
19 Mean Input Power. The total received calorimetric power measured in a specified
20 bandwidth at the antenna connector, including all internal and external signal and noise
21 sources.
22 Mean Output Power. The total transmitted calorimetric power measured in a specified
23 bandwidth at the antenna connector when the transmitter is active.
24 Message. A data structure that conveys control information or application information. A

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

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

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

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

21 cellular or PCS system. See also System Identification.
22 NID. See Network Identification.
23 NMSI. See National Mobile Station Identity.
24 Non-Autonomous Registration. A registration method in which the base station initiates

25 registration. See also Autonomous Registration.
26 Non-Slotted Mode. An operation mode of the mobile station in which the mobile station
27 continuously monitors the Paging Channel.
28 ns. Nanosecond (10-9 second).
29 NULL. Any value that is not in the specified range of a field.
30 Null Traffic Channel Data. One or more frames of a specified data sequence sent at the
31 lowest agreed-upon rate of the negotiated rate set. Null Traffic Channel data may be sent
32 when there is no primary, secondary, or signaling traffic available. Null Traffic Channel
33 data serves to maintain the connectivity between the mobile station and the base station.
34 Number Assignment Module (NAM). A set of MIN/IMSI-related parameters stored in the

35 mobile station.
36 Numeric Information. Numeric information consists of parameters that appear as

37 numeric fields in messages exchanged by the base station and the mobile station and
38 information used to describe the operation of the mobile station.
1-11
C.S0005-0-2 v1.0
1 Optional Field. A field defined within a message structure that is optionally transmitted to
2 the message recipient.
3 Order. A type of message that contains control codes for either the mobile station or the
4 base station.
5 Ordered Registration. A registration method in which the base station orders the mobile
6 station to send registration related parameters.
7 Orthogonal Transmit Diversity (OTD). An optional method of transmission of the

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

39 registers when certain of its stored parameters change.
1-12
C.S0005-0-2 v1.0
1 Parity Check Bits. Bits added to a sequence of information bits to provide error detection,
2 correction, or both.
3 Passive User Zone. A user zone in which the implicit registration that takes place at call
4 setup is sufficient to trigger a change in tiered service features. See also CDMA Tiered
5 Services, User Zone, and Active User Zone.
6 PCI. See Protocol Control Information.
7 PCS. See Personal Communications Services.
8 PCSC. See Personal Communications Switching Center.
9 PCS System. See Personal Communications Services System.
10 PDU. See Protocol Data Unit.
11 Personal Communications Services System. A configuration of equipment that provides

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

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

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

20 characteristics such as coding, power control policies, etc.
21 Physical Layer. The part of the communication protocol between the mobile station and
22 the base station that is responsible for the transmission and reception of data. The
23 physical layer in the transmitting station is presented a frame by the multiplex sublayer
24 and transforms it into an over-the-air waveform. The physical layer in the receiving station
25 transforms the waveform back into a frame and presents it to the multiplex sublayer above
26 it.
27 Pilot Beacon. A transmit-only base station that broadcasts a Pilot Channel, a Sync
28 Channel, optionally a Paging Channel, but no Forward Traffic Channels. The mobile station
29 measures the pilot beacon to assist in CDMA hard handoffs and inter-frequency idle-mode
30 handoffs.
31 Pilot Channel. A non-data-bearing signal transmitted by a CDMA station. See Forward

32 Pilot Channel, Transmit Diversity Pilot Channel, Auxiliary Pilot Channel, Auxiliary Transmit
33 Diversity Pilot Channel, and Reverse Pilot Channel.
34 Pilot PN Chip. One bit, or bit pair, of a pilot PN sequence, or the time interval
35 corresponding thereto.
36 Pilot PN Sequence. A pair of modified maximal length PN sequences used to spread the
37 quadrature components of a CDMA Channel.
38 Pilot PN Sequence Offset. The time offset of a Forward Pilot Channel from CDMA System
39 time, as transmitted by the base station, expressed modulo the pilot period.
1-13
C.S0005-0-2 v1.0
1 Pilot PN Sequence Offset Index. The pilot PN sequence offset in units of 64 PN chips of a
2 Forward Pilot Channel, relative to the zero offset pilot PN sequence.
3 Pilot Strength. The ratio of pilot power to total power in the signal bandwidth of a CDMA
4 Forward or Reverse Channel. See also Ec/Io.
5 PN. Pseudonoise.
6 PN Chip. One bit in a PN sequence, or the time duration of such a bit. It corresponds to
7 the smallest modulation interval in a CDMA system.
8 PN Sequence. Pseudonoise sequence. A deterministic, periodic binary sequence having

9 limited statistical similarity to a Bernoulli (coin-tossing).
10 Power Control Bit. A bit sent on the Forward Power Control Subchannel or Reverse Power
11 Control Subchannel to signal the mobile station or base station to increase or decrease its
12 transmit power.
13 Power Control Group. A 1.25 ms interval on the Forward Traffic Channel and the Reverse
14 Traffic Channel. See also Power Control Bit.
15 Power-Down Registration. An autonomous registration method in which the mobile

16 station registers on power-down.
17 Power Up Function. A method by which the mobile station increases its output power to
18 support location services.
19 Power-Up Registration. An autonomous registration method in which the mobile station

20 registers on power-up.
21 PPM. Parts per million.
22 Preamble. See Access Channel Preamble and Traffic Channel Preamble.
23 Primary CDMA Channel. A pre-assigned channel in a CDMA Cellular System used by the
24 mobile station for initial acquisition. See also Secondary CDMA Channel.
25 Primary Paging Channel (CDMA). The default code channel (code channel 1) assigned for
26 paging on a CDMA Channel.
27 Primary Traffic. The main traffic stream carried between the mobile station and the base
28 station on the Traffic Channel. See also Secondary Traffic and Signaling Traffic.
29 Primitive. An atomic, well-defined method of transferring data and control information

30 between two adjacent layers and sublayers. Conventionally represented as a function
31 invocation with the data and/or control information as parameters.
32 Private Long Code. The long code characterized by the private long code mask. See also
33 Long Code.
34 Private Long Code Mask. The long code mask used to form the private long code. See also
35 Public Long Code Mask and Long Code.
36 Private Neighbor Set. The set of pilots associated with the private system base stations
37 that are probable candidates for idle handoff. See also Active Set, Neighbor Set, Remaining
38 Set, and CDMA Tiered Services.
1-14
C.S0005-0-2 v1.0
1 Protocol Control Information (PCI). Data passed between adjacent layers in the protocol
2 stack, together with the SDU, to assist a layer to properly encapsulate/decapsulate the
3 SDU. Examples of PCI in this document are the MCSB and the PCSB.
4 Protocol Data Unit. Encapsulated data communicated between peer layers on the mobile
5 station and base station. Unless specified otherwise, in this document PDU refers to the
6 Layer 3 protocol data unit transferred at the interface between layer 3 and layer 2.
7 Protocol Stack. Conceptual model of the layered architecture for communication protocols
8 (see Layering) in which layers within a station are represented in the order of their numeric
9 designation and requiring that transferred data be processed sequentially by each layer, in
10 the order of their representation. Graphically, the “stack” is drawn vertically, with the layer
11 having the lowest numeric designation at the base.
12 Public Long Code. The long code characterized by the public long code mask.
13 Public Long Code Mask. The long code mask used to form the public long code. The mask
14 contains a permutation of the bits of the ESN, and also includes the channel number when
15 used for a Supplemental Code Channel. See also Private Long Code Mask and Long Code.
16 PUF. See Power Up Function.

17 PUF Attempt. A sequence of PUF probes sent by the mobile station in response to a Power
18 Up Function Message.
19 PUF Probe. One or more consecutive frames on the Reverse Traffic Channel within which
20 the mobile station transmits the PUF pulse.
21 PUF Pulse. Portion of PUF probe that may be transmitted at elevated output power.
22 PUF Target Frequency. The CDMA frequency assignment to which the base station directs
23 a mobile station for transmitting the PUF probe.
24 Punctured Code. An error-correcting code generated from another error-correcting code by

25 deleting (i.e., puncturing) code symbols from the coder output.
26 Quick Paging. A feature that permits mobile stations to further conserve battery power
27 beyond the savings achieved by slotted mode operation. See also Paging Indicator and
28 Configuration Change Indicator.
29 Quick Paging Channel. An uncoded, on-off-keyed (OOK) spread spectrum signal sent by
30 base stations to inform slotted mode mobile stations, operating in the idle state, whether to
31 monitor the Paging Channel. See also Quick Paging, Paging Indicator, and Configuration
32 Change Indicator.
33 Quick Paging Channel Slot. An 80 ms interval on the Quick Paging Channel. See also
34 Paging Indicator and Configuration Change Indicator.
35 Quick Repeats. Additional transmissions of identical copies of a message within a short

36 interval to increase the probability that the message is received correctly.
37 r-csch. Reverse common signaling logical channel.
38 r-dsch. Reverse dedicated signaling logical channel.
1-15
C.S0005-0-2 v1.0
1 Radio Configuration. A set of Forward Traffic Channel and Reverse Traffic Channel
2 transmission formats that are characterized by physical layer parameters such as
3 transmission rates, modulation characteristics and spreading rate. See Table 3.1.3.1-1 and
4 Table 2.1.3.1-1 of TIA/EIA/IS-2000-[2].
5 Radio Configuration Class. A group of Radio Configurations. All Radio Configurations, for
6 the Forward Traffic Channel and the Reverse Traffic Channel, are divided into three classes
7 by the types of pre-spreading symbols (BPSK and QPSK) and spreading rates. RC Class 1
8 consists of RC 1 and RC 2 for the Forward Traffic Channel and the Reverse Traffic Channel.
9 RC Class 2 consists of RC 3 and RC 4 of the Reverse Traffic Channel, and RC 3, RC 4 and
10 RC 5 of the Forward Traffic Channel. RC Class 3 consists of RC 5 and RC 6 of the Reverse
11 Traffic Channel, and RC 6, RC 7, RC 8, and RC 9 of the Forward Traffic Channel.
12 Rate Set. A set of Traffic Channel transmission formats that are characterized by physical
13 layer parameters such as transmission rates, modulation characteristics, and error
14 correcting coding schemes.
15 RC. See Radio Configuration.
16 Registration. The process by which a mobile station identifies its location and parameters
17 to a base station.
18 Registration Zone. A collection of one or more base stations treated as a unit when
19 determining whether a mobile station should perform zone-based registration. See also
20 User Zone, with which it should not be confused.
21 Release. A process that the mobile station and base station use to inform each other of call
22 disconnect.
23 Remaining Set. The set of all allowable pilot offsets as determined by PILOT_INC,
24 excluding the pilot offsets of the pilots in the Active Set, Candidate Set, and Neighbor Set.
25 See also Active Set, Candidate Set, and Neighbor Set.
26 Request. A layer 3 message generated by either the mobile station or the base station to
27 retrieve information, ask for service, or command an action.
28 Response. A layer 3 message generated as a result of another message, typically a request.
29 Reverse CDMA Channel. The CDMA Channel from the mobile station to the base station.
30 From the base station’s perspective, the Reverse CDMA Channel is the sum of all mobile
31 station transmissions on a CDMA Frequency Assignment.
32 Reverse Dedicated Control Channel. A Dedicated Control Channel that is transmitted on

33 the Reverse CDMA Channel.
34 Reverse Fundamental Channel. A Fundamental Channel that is transmitted on the

35 Reverse CDMA Channel.
36 Reverse Pilot Channel. A non-data-bearing direct-sequence spread spectrum signal

37 transmitted by each CDMA mobile station whenever the Enhanced Access Channel, Reverse
38 Common Control Channel, or Reverse Traffic Channel is enabled. The Reverse Pilot
39 Channel allows a base station to acquire the timing of the Reverse CDMA Channel and
40 provides a phase reference for coherent demodulation. The Reverse Pilot Channel may be
1-16
C.S0005-0-2 v1.0
1 transmitted either continuously or in gated mode.
2 Reverse Supplemental Channel. A Supplemental Channel that is transmitted on the

3 Reverse CDMA Channel.
4 Reverse Supplemental Code Channel. A Supplemental Code Channel that is transmitted

5 on the Reverse CDMA Channel.
6 Reverse Traffic Channel. A Traffic Channel on which data and signaling are transmitted
7 from a mobile station to a base station. The Reverse Traffic Channel is composed zero or
8 one Reverse Fundamental Channel, zero to seven Reverse Supplemental Code Channels,
9 zero to two Reverse Supplemental Channels, and zero or one Reverse Dedicated Control
10 Channel.
11 Roamer. A mobile station operating in a cellular system (or network) other than the one
12 from which service was subscribed. See also Foreign NID Roamer and Foreign SID Roamer.
13 SAP. See Service Access Point.
14 SCI. See Synchronized Capsule Indicator Bit.
15 SDU. See Service Data Unit.
16 Search Window. The range of PN sequence offsets that a mobile station searches for a
17 pilot.
18 Search Window Offset. PN sequence offset used by the mobile station to position the
19 search window when searching for a pilot.
20 Secondary CDMA Channel. A pre-assigned channel in a CDMA Cellular System used by

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

20 communicating with one or more base stations.
21 Shared Secret Data (SSD). A 128-bit pattern stored in the mobile station (in semi-
22 permanent memory) and known by the base station. SSD is a concatenation of two 64-bit
23 subsets: SSD_A, which is used to support the authentication procedures, and SSD_B,
24 which serves as one of the inputs to the process generating the encryption mask and
25 private long code.
26 Short Message Services (SMS). A suite of services such as SMS Text Delivery, Digital
27 Paging (i.e., Call Back Number - CBN), and Voice Mail Notification (VMN).
28 SID. See System Identification.
29 Signaling Traffic. Control messages that are carried between the mobile station and the
30 base station on the Traffic Channel. See also Primary Traffic and Secondary Traffic.
31 Slotted Mode. An operation mode of the mobile station in which the mobile station
32 monitors only selected slots on the Paging Channel when in the Mobile Station Idle State.
33 Soft Handoff. A handoff occurring while the mobile station is in the Mobile Station Control
34 on the Traffic Channel State. This handoff is characterized by commencing communications
35 with a new base station on the same CDMA Frequency Assignment before terminating
36 communications with an old base station. See also Hard Handoff.
37 SOM. Start-of-Message bit.
38 sps. Symbols per second.
39 SSD. See Shared Secret Data.
1-18
C.S0005-0-2 v1.0
1 Station Class Mark (SCM). An identification of certain characteristics of a mobile station.

2 Classes are defined in Table 2.3.3-1 of TIA/EIA-553-A and Table 6.3.3-1 of this
3 document[15].
4 Status Information. The following status information is used to describe mobile station
5 operation when using the analog system:
6 • Serving-System Status. Indicates whether a mobile station is tuned to channels

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

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

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

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

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

37 (each 26.666... ms in length).
38 Synchronized Capsule Indicator Bit (SCI). The first bit in any Paging Channel half frame,
39 which indicates whether a synchronized message capsule immediately follows.
1-19
C.S0005-0-2 v1.0
1 System. A system is a cellular telephone service or personal communications service that

2 covers a geographic area such as a city, metropolitan region, county, or group of counties.
3 See also Network.
4 System Identification (SID). A number uniquely identifying a cellular or PCS system.
5 System Time. The time reference used by the system. System Time is synchronous to
6 UTC time (except for leap seconds) and uses the same time origin as GPS time. All base
7 stations use the same System Time (within a small error). Mobile stations use the same
8 System Time, offset by the propagation delay from the base station to the mobile station.
9 See also Universal Coordinated Time.
10 Target Frequency. The CDMA frequency assignment to which the base station directs a
11 mobile station in a handoff using an Extended Handoff Direction Message, a General
12 Handoff Direction Message, or a Universal Handoff Direction Message.
13 Temporary Mobile Station Identity (TMSI). A temporary mobile station identification

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

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

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

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

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

6 identification memory.
7 1.1.2.1 Reserved
8 1.1.2.2 CDMA Numeric Information
9 The following are internal values that are stored by the mobile station in temporary memory
10 that are not sent over the air. See Annex F for values stored by the mobile station in
11 permanent and semi-permanent memory.
12 ACC_CHANs – Number of Access Channels supported by the current Paging Channel.
13 ACC_ENT_HO_ORDERs – Access entry handoff permitted from the Mobile Station Order and
14 Message Processing Operation of the Mobile Station Idle State.
15 ACCESS_ENTRY_HOs – Idle handoff permitted when entering the System Access State.
16 ACCESS_HOs – Handoff permitted after performing an access attempt while the mobile
17 station is in the System Access State.
18 ACCESS_HO_ALLOWEDs – Handoff permitted to the corresponding neighbor base station
19 while in the System Access State.
20 ACCESS_HO_LIST – List of pilots to which access handoff or access probe handoff is

21 permitted.
22 ACC_HO_LIST_UPDs – Access handoff list update permitted indicator.
23 ACCESS_HO_MSG_RSPs – Access handoff permitted in the System Access State between

24 the time that the mobile station receives a message and responds to that message.
25 ACCESS_PROBE_HOs – Access probe handoff permitted during an access attempt in the
26 Mobile Station Origination Attempt Substate or the Page Response Substate.
27 ACC_MSG_SEQs – Last received Access Parameters Message sequence number.
28 ACC_PROBE_HO_OTHER_MSGs – Access probe handoff permitted for Access Channel

29 messages other than the Origination Message and the Page Response Message.
30 ACC_TMOs – Access Channel acknowledgment timeout, in units of 80 ms.
31 ACK_WAITINGs[i] – Acknowledgment status indicator for message sequence number i. Set

32 to YES if an acknowledgment is pending for the message; otherwise, set to NO.
33 ADD_INTERCEPTs – The intercept in the inequality criterion for adding a pilot to the Active
34 Set.
35 AGEs – Neighbor list age. For each pilot in the Neighbor Set, the mobile station increments
36 this counter each time a Neighbor List Update Message or an Extended Neighbor List Updae
1-22
C.S0005-0-2 v1.0
1 Message is received. When AGEs exceeds NGBHR_MAX_AGE, the pilot is deleted from the
2 Neighbor Set.
3 ALIGN_TIMING_USEDs – Indicates whether the mobile station aligns the times of visits
4 away from the Serving Frequency, as requested by the base station, in the periodic search
5 procedures.
6 ANALOG_CHANs – Analog channel number for CDMA-to-analog handoff.
7 ANALOG_NGHBR_LIST – List containing information about neighboring analog systems.

8 AN_CHAN_TYPEs – Analog voice channel type.
9 ASSIGNED_QPAGECHs – Assigned Quick Paging Channel number.
10 AUTHs – Current authentication mode.
11 BAD_FRAMESs – Forward Fundamental Channel bad frames count. The number of

12 received bad forward Fundamental Channel frames.
13 BASE_CLASSs – Base station class of the current base station.
14 BASE_IDs – Base station identification of the current base station.
15 BASE_LATs – Latitude of the current base station, in units of 0.25 seconds.
16 BASE_LONGs – Longitude of the current base station, in units of 0.25 seconds.
17 BEGIN_PREAMBLEs – A stored variable in the mobile station that contains the size of the
18 preamble that shall be transmitted on a Reverse Supplemental Code Channel at the
19 beginning of a Reverse Supplemental Code Channel transmission.
20 BKOFFs – Access Channel probe sequence backoff range.
21 BYPASS_ALERT_ANSWERs – Mobile station termination bypass indicator. This is set to ‘1’

22 if the mobile station is to bypass the Waiting for Order Substate and the Waiting for Mobile
23 Station Answer Substate, and proceed directly to the Conversation Substate when Layer 3
24 receives a forward dedicated channel-acquired indication from Layer 2.
25 CDMABANDs. CDMA band class. The CDMA band class currently used by the mobile
26 station.
27 CDMACHs – CDMA Channel number. The CDMA Channel number currently used by the
28 mobile station.
29 CF_CDMABANDs – Candidate Frequency CDMA band class. The CDMA band class
30 specified in the Candidate Frequency Search Request Message.
31 CF_CDMACHs – Candidate Frequency CDMA Channel number. The CDMA Channel
32 number specified in the Candidate Frequency Search Request Message.
33 CF_PILOT_INCs – PILOT_INC to be used by the mobile station after an inter-frequency hard
34 handoff to the CDMA Candidate Frequency is successfully completed.
35 CF_SEARCH_PRIORITY_INCLs – Candidate Frequency neighbor pilots’ search priority
36 included indicator.
1-23
C.S0005-0-2 v1.0
1 CF_SRCH_OFFSET_INCLs – Candidate Frequency neighbor pilot search window offset

3 CF_SRCH_WIN_NGHBR_INCLs – Candidate Frequency neighbor pilots’ search window
5 CF_SRCH_WIN_Ns – Search window size for the Candidate Frequency Search Set.
6 CF_SRCH_WIN_Rs – Search window size to be used for the Remaining Set after an inter-
7 frequency hard handoff to the CDMA Candidate Frequency is successfully completed.
8 CF_T_ADDs – Pilot detection threshold to be used on the CDMA Candidate Frequency.
9 CH_INDs – A two-bit physical channel indicator, based on currently established physical

10 channels. The least significant bit denotes the Fundamental Channel and the most
11 significant bit denotes the Dedicated Control Channel.
12 CHAN_LST_MSG_SEQs – CDMA Channel List Message sequence number.
13 CODE_CHAN_LIST – Code Channel List. A descriptive structure used to manage the

14 Forward Fundamental Channel, and Forward Supplemental Code Channels, if any,
15 associated with the mobile station’s Active Set.
16 COMPLETE_PUF_FRAMEs – Number of power control groups required to make the PUF
17 probe an integer number of frames.
18 COMPLETE_SEARCHs – Flag to indicate if the mobile station is to complete the search of
19 the Candidate Frequency Search Set after it has determined that the inter-frequency
20 handoff attempt to the CDMA Candidate Frequency is unsuccessful.
21 CONFIG_MSG_SEQs – Current message sequence number for the System Parameters
22 Message, Neighbor List Message, Extended Neighbor List Message, General Neighbor List
23 Message, CDMA Channel List Message, Extended System Parameters Message, Global Service
24 Redirection Message, Private Neighbor List Message, User Zone Identification Message,
25 Extended CDMA Channel List Message, Extended Global Service Redirection Message.
26 COUNTER_ENABLEDs – Timer-based registration indicator. Set to YES if timer-based
27 registration is enabled; otherwise, set to NO.
28 CURR_ACC_MSG_SEQ – Current Access Parameter Message sequence number.
29 CURRENT_ACTIVE_PILOTs – Identifies the current pilot in the Active Set during an access
30 attempt.
31 CURRENT_PUF_PROBEs – Number of the next PUF probe to be transmitted within the PUF
32 attempt.
33 DAYLTs – Daylight Savings Time indicator.
34 DCCH_BAD_FRAMESs – Forward Dedicated Control Channel bad frames count. The

35 number of received bad forward Dedicated Control Channel frames.
36 DCCH_TOT_FRAMESs – Total forward Dedicated Control Channel frames received. The
37 total number of received forward Dedicated Control Channel frames, counted for Forward
38 Traffic Channel power control.
1-24
C.S0005-0-2 v1.0
1 DECORR – Hashing function input used to decorrelate hashing function applications for
2 the same mobile station.
3 DEFAULT_CONFIGs – Mobile station current default configuration.
4 DELETE_FOR_TMSIs – A storage variable in the mobile station that indicates whether the
5 mobile station should delete its current TMSI if the TMSI was assigned in a different TMSI
6 zone.
7 DIFF_RX_PWR_THRESHs – Threshold for the difference between the received power on the
8 Serving Frequency and the received power on the CDMA Candidate Frequency for the
9 mobile station to search for pilots on the CDMA Candidate Frequency.
10 DISTANCE – Distance from registered base station to current base station, used for
11 distance-based registration.
12 DROP_INTERCEPTs – The intercept in the inequality criterion for dropping a pilot from the
13 Active Set.
14 DSCCs – Digital supervisory color code.
15 DTXs – Discontinuous transmission mode for analog channel assignment and CDMA-to-
16 analog handoff.
17 EC_IO_THRESHs – Pilot Ec/Io threshold used for system reselection.
18 EC_THRESHs – Pilot power threshold used for system reselection.
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_GLOBAL_REDIRECTs – Extended Global Service Redirection Message sent indicator.
25 EXT_GLOB_SERV_REDIR_MSG_SEQs – Extended Global Service Redirection Message

26 sequence number.
27 EXT_SYS_PARAMETERs – Extended System Parameters Message sent indicator.
28 EXT_SYS_PAR_MSG_SEQs – Extended System Parameters Message sequence number.
29 FIRST_ACTIVE_PILOTs – While the mobile station is in the System Access State, identifies
30 the pilot to which the first access probe was transmitted, upon entering the System Access
31 State.
32 FOR_DURATIONs – A stored variable in the mobile station that contains the duration (in
33 units of 80 ms) of a forward Supplemental Code Channel transmission that begins at time
34 FOR_START_TIMEs.
35 FOR_FCH_RCs – Forward Fundamental Channel Radio Configuration.
36 FOR_FRAME_40_MAX_RATEs – The maximum data rate for the mobile station's
1-25
C.S0005-0-2 v1.0
1 transmission at 40 ms frame length on the Forward Supplemental Channel.

2 FOR_FRAME_80_MAX_RATEs – The maximum data rate for the mobile station's
3 transmission at 80 ms frame length on the Forward Supplemental Channel.
4 FOR_LINKED_HDM_SEQs – Storage variable containing the most recent forward sequence
5 number of the General Handoff Direction Message to which a Supplemental Channel
6 Assignment Message forward assignment was linked.
7 FOR_NID_REGs – Foreign NID roamer autonomous registration enable.
8 FOR_RCs – Forward Channel Radio Configuration.
9 FOR_SCH_DURATIONs – A stored variable in the mobile station which contains the

10 duration of a forward Supplemental Channel transmission which begins at time
11 FOR_SCH_START_TIMEs.
12 FOR_SCH_FRAME_LENGTHs – The Forward Supplemental Channel frame length.
13 FOR_SCH_START_TIMEs – A stored variable in the mobile station which contains the

14 System Time, in units of time specified by START_TIME_UNITs, (modulo 32) at which the
15 mobile station shall start (or resume) processing Forward Supplemental Channels.
16 FOR_SID_REGs – Foreign SID roamer autonomous registration enable.
17 FOR_START_TIMEs – A stored variable in the mobile station that contains the System
18 Time, in units of 80 ms, (modulo 64) at which the mobile station shall start (or resume)
19 processing Forward Supplemental Code Channels.
20 FPC_DCCH_CURR_SETPTs – Current power control subchannel outer loop setpoint for the
21 Forward Dedicated Control Channel.
22 FPC_DCCH_FERs – Target frame error rate for the Forward Dedicated Control Channel.
23 FPC_DCCH_MAX_SETPTs – Maximum value of the power control subchannel outer loop

24 setpoint for the Forward Dedicated Control Channel.
25 FPC_DCCH_MIN_SETPTs – Minimum value of the power control subchannel outer loop
26 setpoint for the Forward Dedicated Control Channel.
27 FPC_DELTA_SCH_SETPTs – The difference between the Fundamental Channel current
28 power control subchannel outer loop setpoint and the Supplemental Channel current power
29 control subchannel outer loop setpoint.
30 FPC_DELTA_SETPTs – The difference between the Fundamental Channel current power
31 control subchannel outer loop setpoint and the Dedicated Control Channel current power
32 control subchannel outer loop setpoint.
33 FPC_FCH_CURR_SETPTs – Current power control subchannel outer loop setpoint for the
34 Forward Fundamental Channel.
35 FPC_FCH_FERs – Target frame error rate for the Forward Fundamental Channel.
36 FPC_FCH_MAX_SETPTs – Maximum value of the power control subchannel outer loop

37 setpoint for the Forward Fundamental Channel.
1-26
C.S0005-0-2 v1.0
1 FPC_FCH_MIN_SETPTs – Minimum value of the power control subchannel outer loop

2 setpoint for the Forward Fundamental Channel.
3 FPC_MODEs – Forward power control operating mode.
4 FPC_PRI_CHANs – Primary power control subchannel measured channel.
5 FPC_SEC_CHANs – Index of Forward Supplemental Channel to be measured by the

6 secondary power control subchannel.
7 FPC_SCH_CURR_SETPTs[i] – Current power control subchannel outer loop setpoint for
8 Forward Supplemental Channel i.
9 FPC_SCH_FERs[i] – Target frame error rate for Forward Supplemental Channel i.
10 FPC_SCH_MAX_SETPTs[i] – Maximum value of the power control subchannel outer loop

11 setpoint for Forward Supplemental Channel i.
12 FPC_SCH_MIN_SETPTs[i] – Minimum value of the power control subchannel outer loop
13 setpoint for Forward Supplemental Channel i.
14 FPC_SETPT_THRESHs – Power control subchannel outer loop setpoint report threshold for
15 the Dedicated Control Channel.
16 FPC_SETPT_THRESH_SCHs – Power control subchannel outer loop setpoint report
17 threshold for the Supplemental Channel.
18 FRAME_OFFSETs – Current Traffic Channel frame offset, in units of 1.25 ms.
19 GEN_NGHBR_LST_MSG_SEQs – General Neighbor List Message sequence number.
20 GLOBAL_REDIRECTs – Global Service Redirection Message sent indicator.
21 GLOB_SERV_REDIR_MSG_SEQs – Global Service Redirection Message sequence number.
22 GRANTED_MODEs – Mobile station current granted mode.
23 HASH_KEY – Hashing function input that determines the return value. Derived from
24 IMSI_O.
25 HDM_SEQs – Last received Extended Handoff Direction Message, General Handoff Direction
26 Message, or Universal Handoff Direction Message sequence number.
27 HOME_REGs – Home (non-roaming) autonomous registration enable.
28 IGNORE_ESCAMs – Identifies whether a mobile station will process the reverse

29 supplemental channel assignment portion of the subsequent Supplemental Channel
30 Assignment Message or Reverse Supplemental Channel Assignment Mini Message.
31 IGNORE_SCAMs – Identifies whether a mobile station will process the reverse supplemental
32 code channel assignment portion of the subsequent Supplemental Channel Assignment
33 Message.
34 IMSI_11_12s – The 11th and 12th digits of the IMSI used for address matching.
35 IMSI_O_ADDR_NUMs- The number of digits in the NMSI of the Operational IMSI (IMSI_O)
36 minus four.
1-27
C.S0005-0-2 v1.0
1 IMSI_O_Ss – The last 10-digits of Operational IMSI (IMSI_O).
2 IMSI_O_11_12s – The 11th and 12th digits of the Operational IMSI (IMSI_O).
3 INIT_PWRs – Initial power offset for Access Channel probes.
4 LC_STATEs – Long code state obtained from the Sync Channel Message.
5 LOGICAL_TO_PHYSICAL_MAPPING_TABLE[]s – This table contains the logical to physical
6 mapping for signaling and user traffic.
7 LP_SECs – Leap seconds count (offset of CDMA system time from UTC).
8 LTM_OFFs – Local time offset from UTC, in units of 15 minutes.
9 MAX_CAP_SZs – Maximum number of Access Channel frames in an Access Channel

10 message capsule, less 3.
11 MAX_NUM_ALT_SOs – The maximum number of alternative service option numbers that
12 the mobile station is allowed to include in the Origination Message or in the Page Response
13 Message.
14 MAX_NUM_PROBE_HOs – The maximum number of times that a mobile station is
15 permitted to perform an access probe handoff.
16 MAX_PWR_PUFs – Maximum number of PUF probes to be transmitted at maximum mobile
17 station output power during a PUF attempt.
18 MAX_REQ_SEQs – Maximum number of access probe sequences for an Access Channel
19 request.
20 MAX_RSP_SEQs – Maximum number of access probe sequences for an Access Channel
21 response.
22 MAX_SLOT_CYCLEs – Maximum value of the slot cycle index allowed by the current base
23 station.
24 MCCs – The Mobile Country Code used for address matching.
25 MCC_Os – The Mobile Country Code of IMSI_O.
26 MEMs – Analog message encryption mode for CDMA-to-analog handoff.

27 MIN_PILOT_EC_IO_THRESHs – Threshold for total Ec/Io of pilots in the Serving Frequency
28 Active Set used in the Periodic Serving Frequency Pilot Report Procedure.
29 MIN_PILOT_PWR_THRESHs – Threshold for total Ec of pilots in the Serving Frequency
30 Active Set used in the Periodic Serving Frequency Pilot Report Procedure.
31 MIN_P_REVs – Minimum mobile station protocol revision level required for access to the
32 CDMA system.
33 MIN_TOTAL_PILOT_EC_IOs – Total pilot strength threshold for the mobile station to
34 attempt to demodulate the Forward Traffic Channel on the CDMA Candidate Frequency.
35 MOB_TERMs – Mobile station termination indicator. Set to ‘1’ if the mobile station will
36 accept mobile station terminated calls in its current roaming status.
1-28
C.S0005-0-2 v1.0
1 MSG_PSISTs – Persistence modifier for Access Channel message transmissions.
2 MS_LATs – The latitude of the mobile station as estimated by the base station.
3 MS_LOC_TSTAMPs – The time corresponding to the estimate of mobile station’s latitude

4 and longitude.
5 MS_LONGs – The longitude of the mobile station as estimated by the base station.
6 MULT_NIDSs – Multiple NID storage indicator. Set to ‘1’ if the mobile station may store
7 more than one entry in SID_NID_LISTs for each SID.
8 MULT_SIDSs – Multiple SID storage indicator. Set to ‘1’ if the mobile station may store
9 entries in SID_NID_LISTs having different SIDs.
10 NAR_AN_CAPs – Narrow analog voice channel capability.
11 NDSS_ORIGs – NDSS Origination Indicator. Indicator used when the mobile station is
12 NDSS-redirected while originating a call.
13 NGHBR_BANDs – Neighbor band class.
14 NGHBR_CONFIGs – Neighbor base station channel allocation configuration.
15 NGHBR_FREQs – Neighbor CDMA channel number.
16 NGHBR_LST_MSG_SEQs – Neighbor List Message sequence number.
17 NGHBR_MAX_AGEs – Neighbor set maximum age for retention in the set.
18 NGHBR_PNs – Neighbor base station Pilot Channel PN sequence offset in units of 64 PN

19 chips.
20 NGHBR_REC – Record containing information about a neighbor base station (see also
21 NGHBR_REC_LIST).
22 NGHBR_REC_LIST – Neighbor base station record list. A descriptive structure used to

23 manage the base station’s information records about neighbor base stations (see also
24 NGHBR_REC).
25 NGHBR_SET_ACCESS_INFOs – Neighbor Set access handoff or access probe handoff
26 information included indicator.
27 NGHBR_SET_ENTRY_INFOs – Neighbor Set access entry handoff information included
28 indicator.
29 NGHBR_SET_SIZEs – Size of the Neighbor Set.
30 NGHBR_TIMING_INCLs – Indicates that hopping pilot beacon timing information is

31 included.
32 NGHBR_TX_DURATIONs – Hopping pilot beacon transmit time duration.
33 NGHBR_TX_OFFSETs – Hopping pilot beacon transmit time offset.
34 NGHBR_TX_PERIODs – Hopping pilot beacon transmit time period.
35 NIDs – Network identification. A network is a subset of the base stations within a cellular
36 or PCS system.
1-29
C.S0005-0-2 v1.0
1 NOM_PWRs – Nominal transmit power offset. A correction factor to be used by mobile

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

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

36 connector, of the earliest arriving usable multipath component of the pilot. The arrival time
37 is measured relative to the mobile station’s time reference.
1-30
C.S0005-0-2 v1.0
1 PILOT_GATING_RATEs – Reverse pilot gating rate on the Reverse Pilot Channel.
2 PILOT_GATING_USE_RATE – Reverse pilot gating rate enable indicator. It indicates

3 whether or not the Reverse Pilot Channel is gated.
4 PILOT_INCs – Pilot PN sequence offset index increment. The interval between pilots, in
5 units of 64 PN chips, for base stations in a system.
6 PILOT_PNs – Pilot Channel PN sequence offset, in units of 64 PN chips, for a base station.
7 PILOT_PN_PHASE – Calculated Pilot Channel PN phase, in chips, including the PN

8 sequence offset and the arrival time relative to the mobile station’s time reference.
9 PILOT_REPORTs – Pilot reporting indicator.
10 POWER_DOWN_REGs – Power down registration enable indicator.
11 POWER_UP_REGs – Power up registration enable indicator.
12 PPSMM_PERIODs – The period used in the Periodic Serving Frequency Pilot Report
13 Procedure.
14 PRATs – Data rate of the Paging Channels.
15 P_REVs – Protocol revision level supported by a base station.
16 P_REV_IN_USEs – Protocol revision level currently in use by a mobile station.
17 PREF_MSID_TYPEs – Preferred mobile station identifier field type.
18 PREVIOUS_ACTIVE_PILOTs – Identifies the pilot, if any, which was in the Active Set
19 immediately prior to the current pilot in the Active Set, during the current access attempt.
20 PRI_NGHBR_LISTs – Private Neighbor List Message sent indicator.
21 PRI_NGHBR_PN – Private Neighbor base station Pilot Channel PN sequence offset in units
22 of 64 PN chips.
23 PRI_NGHBR_REC – Record containing information about a private neighbor base station

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

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

21 received in a measurement period before the mobile station is to generate a Power
22 Measurement Report Message.
23 PWR_STEPs – Power increment for successive access probes, in units of 1.0 dB.
24 PWR_THRESH_ENABLEs – Forward power control threshold reporting enabled indicator.
25 QPAGECHs – Current Quick Paging Channel number.
26 QPCH_CCI_SUPPORTEDs – Flag to indicate if configuration change indicators are

27 supported on the Quick Paging Channel.
28 QPCH_POWER_LEVEL_PAGEs – Relative power level of the transmitted Quick Paging
29 Channel Paging Indicator modulation symbols, relative to the Forward Pilot Channel.
30 QPCH_POWER_LEVEL_CONFIGs – Relative power level of the transmitted Quick Paging
31 Channel Configuration Change Indicator modulation symbols, relative to the Forward Pilot
32 Channel.
33 QPCH_RATEs – Indicator rate of the current Quick Paging Channel(s).
34 QPCH_SUPPORTEDs – Flag to indicate if the Quick Paging Channel is supported by the

35 base station.
1-32
C.S0005-0-2 v1.0
1 RA – Random access channel number. The Access Channel number generated (pseudo-
2 randomly) by the mobile station.
3 RANDs – Authentication random challenge value.
4 RANDC – The eight most-significant bits of the random challenge value used by the mobile
5 station.
6 RANDOM_TIME – Random time. A portion of SYS_TIME used to seed the random number
7 generator.
8 RC_CAP_REQUESTEDs – Radio Configuration Capability indicator. When set to “1” the
9 mobile station shall include the Radio Configuration capabilities that it supports in the
10 Origination Message and Page Response Message.
11 REDIRECTIONs – Service redirection indicator. Set to enabled to indicate that service
12 redirection is currently in effect; otherwise, set to disabled.
13 REDIRECT_RECs – Holds the service redirection criteria specified in the redirection record
14 of the most recently received Global Service Redirection Message or Service Redirection
15 Message.
16 REG_COUNTs – The timer-based registration counter.
17 REG_COUNT_MAXs – Timer-based registration count limit. The timer-based registration

18 counter expiration value computed from REG_PRDr.
19 REG_DISTs – Registration distance. Distance from last registration that causes a distance-
20 based registration to occur.
21 REG_ENABLEDs – Autonomous registrations enabled indicator.
22 REGISTEREDs – Mobile station registered indicator.
23 REG_PRDs – Registration period. The time interval between timer-based registrations.

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

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

21 Channel with Radio Configuration 3, 4, 5, or 6.
22 REV_FCH_RCs – Reverse Fundamental Channel Radio Configuration.
23 REV_PWR_CNTL_DELAYs – Reverse link power control loop delay when the Reverse
24 Fundamental Channel with Radio Configuration 3, 4, 5, or 6 is gated or when the Reverse
25 Common Control Channel preamble is gated.
26 REV_FRAME_40_MAX_RATEs – The maximum data rate for the mobile station's
27 transmission at 40 ms frame length on the Reverse Supplemental Channel.
28 REV_FRAME_80_MAX_RATEs – The maximum data rate for the mobile station's
29 transmission at 80 ms frame length on the Reverse Supplemental Channel.
30 REV_LINKED_HDM_SEQs – Storage variable containing the most recent reverse sequence
31 number of the General Handoff Direction Message to which a Supplemental Channel
32 Assignment Message reverse assignment was linked.
33 REV_RCs – Reverse Channel Radio Configuration.
34 REV_SCH_DTX_DURATIONs – Maximum duration of time in units of 20 ms that the mobile

35 station is allowed to stop transmitting on a Reverse Supplemental Channel within the
36 reverse assignment duration.
37 REV_SCH_DURATIONs – A stored variable in the mobile station which contains the
38 duration of the Reverse Supplemental Channel transmission which will begin at time
39 REV_SCH_START_TIMEs.
1-34
C.S0005-0-2 v1.0
1 REV_SCH_FRAME_LENGTHs – The Reverse Supplemental Channel frame length.
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 RN_HASH_KEYs – Name of an internal variable having the same value as the mobile
9 station's ESN. This variable is used by procedures defined in TIA/EIA/IS-2000-[3].
10 ROAM_INDIs – Enhanced roaming indicator used for mobile station roaming condition
11 display.
12 RS – Inter-probe sequence backoff. The delay in slots generated (pseudorandomly) by the

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

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

19 Supplemental Code Channel assignment duration.
20 SCAM_FOR_ORDERs – The stop or start command set by a Supplemental Channel
21 Assignment Message that is linked to a General Handoff Direction Message.
22 SCAM_REV_DURATION_MODEs – Indicator for a specific or an indefinite Reverse
23 Supplemental Code Channel assignment duration.
24 SCH_BAD_FRAMESs – Forward Supplemental Channel bad frames count. The number of
25 received bad forward Supplemental Channel frames.
26 SCH_TOT_FRAMESs – Total forward Supplemental Channel frames received. The total
27 number of received forward Supplemental Channel frames, counted for Forward Traffic
28 Channel power control.
29 SCRM_SEQ_NUMs – Storage variable containing the most recently transmitted
30 Supplemental Channel Request Message sequence number.
31 SEARCH_MODEs – Search mode to be used in a periodic search on the Candidate
32 Frequency.
33 SEARCH_OFFSETs – Time offset of the start of the first search from the action time of the
34 Candidate Frequency Search Request Message or the Candidate Frequency Search Control
35 Message that starts a search.
36 SEARCH_PERIODs – Period for search on the Candidate Frequency.
37 SEARCH_PRIORITYs – Neighbor Pilot Channel search priority.
38 SEARCH_PRIORITY_INCLs – Search priorities included indicator.
1-35
C.S0005-0-2 v1.0
1 SEARCH_TIME_RESOLUTIONs – Unit of delay used in the Candidate Frequency Search

2 Report Message to report the total and maximum times away from the Serving Frequency.
3 SERV_NEGs – Service negotiation indicator. Indicates whether the mobile station is to use
4 service negotiation or service option negotiation.
5 SERV_REQ_NUMs – Service request sequence number. Sequence number to use when
6 requesting a new service configuration.
7 SERVSYSs – Selected serving system indicator for Band Class 0. Set to SYS_A if the mobile
8 station operates in system A; otherwise, set to SYS_B.
9 SETTING_SEARCH_WIN – SRCH_WIN_NGHBR Setting flag. Set to ‘1’ if the mobile station

10 shall set the SRCH_WIN_NGHBR field of each NGHBR_REC to SEARCH_WIN_Ns for all
11 NGHBR_SET_SIZEs entries upon receiving the System Parameters Message.
12 SF_ADD_INTERCEPTs – Intercept of the handoff add criterion for the Serving Frequency,
13 stored during hard handoff.
14 SF_CDMABANDs – Serving Frequency CDMA band class, stored during hard handoff.
15 SF_CDMACHs – Serving Frequency CDMA Channel number, stored during hard handoff.
16 SF_CODE_CHAN_LISTs – Serving Frequency Code Channel List, stored during hard

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

27 SOFT_SLOPEs – The slope in the inequality criterion for adding a pilot to the Active Set, or
28 dropping a pilot from the Active Set.
29 SO_REQs – Service option request number. The number of the service option requested by
30 the mobile station during service option negotiation.
31 SRCH_OFFSET_INCLs – Neighbor pilot search window offset included indicator.
32 SRCH_OFFSET_NGHBRs – Neighbor pilot search window offset.
33 SRCH_WIN_As – Search window size for the Active Set and Candidate Set.
34 SRCH_WIN_NGHBRs – Neighbor Pilot Channel search window size.
35 SRCH_WIN_NGHBR_INCLs – Neighbor Pilot Channel search window size included indicator.
36 SRCH_WIN_Ns – Search window size for the Neighbor Set.
1-37
C.S0005-0-2 v1.0
1 SRCH_WIN_Rs – Search window size for the Remaining Set.
2 START_TIME_UNITs – A stored variable in the mobile station which contains the time unit
3 used for determining FOR_SCH_START_TIME and REV_SCH_START_TIME on Supplemental
4 Channels.
5 SYS_PAR_MSG_SEQs – System Parameters Message sequence number.
6 SYS_TIMEs – Current value of CDMA system time as received in the Sync Channel
7 Message.
8 TA – Acknowledgment response timeout.

9 T_ADDs – Pilot detection threshold.
10 T_COMPs – Active Set versus Candidate Set comparison threshold.
11 T_DROPs – Pilot drop threshold.
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.
22 TF_WAIT_TIMEs – Maximum time that the mobile station may wait to receive a period of
23 (N11m × 20) ms with sufficient signal quality (e.g. good frames) on the CDMA Target
24 Frequency.
25 TMSI_ZONEs – TMSI zone number of the base station.
26 TMSI_ZONE_LENs – The number of octets in TMSI zone.
27 T_MULCHANs – A storage variable in the mobile station that contains the Reverse
28 Supplemental Code Channel neighbor pilot strength measurement offset.
29 TOTAL_PUF_PROBESs – Maximum number of PUF probes transmitted in a PUF attempt.
30 TOTAL_ZONESs – Number of registration zones to be retained in ZONE_LISTs.
31 TOT_FRAMESs – Total forward Fundamental Channel frames received. The total number
32 of received forward Fundamental Channel frames, counted for Forward Traffic Channel
33 power control.
34 T_TDROPs – Pilot drop timer value.
1-38
C.S0005-0-2 v1.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.
27
1-39
C.S0005-0-2 v1.0
1 1.2 Signaling Architecture
2 Layer 3 signaling for cdma2000 is modeled as follows:
3 • Planes. There are two planes: the Data Plane1 (used for the signaling protocol) and
4 the Control Plane (used for supervision of the protocol according to functional
5 requirements).
6 • Protocol Layer. Layer 3 generates Layer 3 PDUs and passes these PDUs to Lower
7 Layers, where proper encapsulation into Lower Layer PDUs is performed. On the
8 receiving end, Lower Layer PDUs are decapsulated and the resulting SDUs are sent
9 from Lower Layers to Layer 3 for processing.
10 • Service Access Points. SAPs and corresponding communication primitives are

11 defined between the Layer 3 and Lower Layers over the data plane. No SAPs are
12 defined for communications through the control plane.
13 1.3 Signaling and Functionality
14 1.3.1 Control Plane and Data Plane
15 The general architecture is presented in two planes: Control Plane, where processing
16 decisions are made, and Data Plane, where the PDUs are generated and processed and
17 transferred. The Data Plane contains the protocol, and is layered.
1 User traffic of various types also passes through the Data Plane, but further description is outside
the scope of this document. Signaling is just another type of traffic whose users are the control
entities in the base station and mobile station.
1-40
C.S0005-0-2 v1.0
Control Data
Plane Plane
Layer 3
Layer 3
Signaling
Signaling
Control
Signaling
Configuration
Resource
Database
Data
SAP
Resource Lower Lower

Control Layer Layer
Control Signaling
2 Figure 1.3.1-1. IS-2000 Signaling – General Architecture
3 1.3.2 Interface to Layer 2
4 The interface between Layer 3 and Layer 2 is a Service Access Point (SAP). At the SAP,
5 Layer 3 and Layer 2 exchange Service Data Units (SDU) and interface control information in
6 the form of Message Control and Status Blocks (MCSB) using a set of primitives.
7 1.3.2.1 Message Control and Status Block (MCSB)
8 The MCSB is a parameter block for the defined primitives, containing relevant information
9 about an individual Layer 3 message (PDU), as well as instructions on how the message
10 may be handled or how it is to be (for transmission), or was (for reception), processed by
11 Layer 2. The MCSB is a conceptual construct and is not subject to detailed specification in
12 this document; however, it is envisioned the MCSB will contain information such as:
13 • The MSG_TAG. If the message is generated in response to a previously received

14 message, the MSG_TYPE of the previously received message is also stored.
15 • The length of the PDU.
16 • A unique instance identifier associated with the message, which enables

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

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

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

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

5 Layer 2. Details are indicated via the MCSB.
7 Name: L2-Supervision.Request
8 Type: Request
10 Parameters: MCSB
11 Action: Layer 2 executes a control command as directed by Layer 3. This could be,
12 for example, an order to abandon retransmission of a message or an order
13 for local reset for the message sequence number, acknowledgment sequence
14 number and duplicate detection.
15
1-43
C.S0005-0-2 v1.0
1 1.3.3. Reserved
2 1.3.4. Functional Description
3 In the Data Plane, Layer 3 originates and terminates signaling data units according to the
4 semantic and timing of the communication protocol between the base station and the
5 mobile station. From a semantic point of view the signaling data units are referred to as
6 “messages” (or “orders”). From a protocol point of view, the signaling data units are PDUs.
7 In general, the language of this specification does not explicitly distinguish between
8 semantics and the protocol viewpoints, and the terms “PDU” and “Message”. It is
9 considered that the context provides enough information to allow the reader to make the
10 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 layer 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, layer 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 assured mode PDU received from the transmitting Layer
28 3 entity is delivered to the receiving Layer 3 entity. Thus, Layer 2 acknowledgments may
29 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-44
C.S0005-0-2 v1.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).2 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).
2 See CCITT Blue Book, Volume II-Fascicle II.2, Recommendation E.212, November 1988.
2-1
C.S0005-0-2 v1.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
C.S0005-0-2 v1.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 NMSI 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
22 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
23
2-3
C.S0005-0-2 v1.0
1 2. The second three digits of IMSI_M_S and the second three digits of IMSI_T_S are
2 mapped into the ten most significant bits of IMSI_M_S1p and IMSI_T_S1p,
3 respectively, by the coding algorithm indicated in 1.
4 3. The last four digits of IMSI_M_S and the last four digits of IMSI_T_S are mapped into
5 the 14 least significant bits of IMSI_M_S1p and IMSI_T_S1p, respectively, as follows:
6 a. The thousands digit is mapped into four bits by a Binary-Coded-Decimal (BCD)

7 conversion, as shown in Table 2.3.1.1-2.
8 b. The last three digits are mapped into ten bits by the coding algorithm indicated
9 in 1.
10
11 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
12
13 The following example illustrates the IMSI_T_S2p and IMSI_T_S1p calculation procedure.
14 Let the IMSI_T be the 9-digit number 123456789. Since the IMSI_T has fewer than ten
15 digits, the nine least significant digits of the IMSI_T_S are equal to the IMSI_T digits and the
16 most significant IMSI_T_S digit is set to zero. So the 10-digit IMSI_T_S is 012 345 6 789.
17 IMSI_T_S2p and IMSI_T_S1p are calculated as follows:
18 • IMSI_T_S2p. The ten-bit IMSI_T_S2p is derived from the first three digits of the
19 IMSI_T_S (i.e., 012):
20 a. D1 = 10; D2 = 1; D3 = 2.
21 b. 100 × D1 + 10 × D2 + D3 - 111 = 100 × 10 + 10 × 1 + 2 - 111 = 901.
22 c. 901 in binary is ‘11 1000 0101’.

23 Therefore, IMSI_T_S2p is ‘11 1000 0101’.
24 • IMSI_T_S1p. The ten most significant bits of IMSI_T_S1p are derived from the
25 second three digits of the IMSI_T_S (i.e., 345):
2-4
C.S0005-0-2 v1.0
1 a. D1= 3; D2 = 4; D 3 = 5.
2 b. 100 × D1 + 10 × D2 + D3 - 111 = 100 × 3 + 10 × 4 + 5 - 111 = 234.
3 c. 234 in binary is ‘0011 1010 10’.

4 The next four most significant bits of IMSI_T_S1p are derived from the thousands digit of
5 the IMSI_T_S (i.e., 6) by BCD conversion: 6 in BCD is ‘0110’.
6 The ten least significant bits of IMSI_T_S1p are derived from the last three digits of the
7 IMSI_T_S (i.e., 789):
8 a. D1 = 7; D2 = 8; D3 = 9.
9 b. 100 × D1 + 10 × D2 + D3 - 111 = 100 × 7 + 10 × 8 + 9 - 111 = 678.
10 c. 678 in binary is ‘10 1010 0110’.

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

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

18 described in Table 6.3.1.1-1 and limit the resulting number to the 7 least significant
19 bits.
20 2.3.1.3 Encoding of the MCC_M and MCC_T
21 The MCC_M and MCC_T binary mapping is defined as follows:

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

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

4 Class-of-station information referred to as the station class mark (SCMp) must be stored in
5 a mobile station. The digital representation of this class mark is specified in Table 2.3.3-1.
7 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
9 If the mobile station supports analog mode operation in Band Class 0, the mobile station
10 shall set the Power Class function bits to reflect its analog power class at Band Class 0,
11 regardless of the band class in which it is operating; otherwise, the mobile station shall set
12 these bits to ‘00’.
13 2.3.4 Registration Memory
14 The mobile station shall have memory to store one element in the zone-based registration
15 list ZONE_LISTs-p (see 2.6.5.1.5 and 2.6.5.5). This stored element shall include both
16 REG_ZONE and the corresponding (SID, NID) pair. The data retention time under power-off
17 conditions shall be at least 48 hours. If, after 48 hours, the data integrity cannot be
18 guaranteed, then the entry in ZONE_LISTs-p shall be deleted upon power-on.
19 The mobile station shall have memory to store one element in the system/network
20 registration list SID_NID_LISTs-p (see 2.6.5.1.5 and 2.6.5.5). The data retention time under
2-6
C.S0005-0-2 v1.0
1 power-off conditions shall be at least 48 hours. If, after 48 hours, the data integrity cannot
2 be guaranteed, then the entry in SID_NID_LISTs-p shall be deleted upon power-on.
3 The mobile station shall have memory to store the distance-based registration variables
4 BASE_LAT_REGs-p, BASE_LONG_REGs-p, and REG_DIST_REGs-p (see 2.6.5.1.4 and
5 2.6.5.5). The data retention time under power-off conditions shall be at least 48 hours. If,
6 after 48 hours, the data integrity cannot be guaranteed, then REG_DIST_REGs-p shall be
7 set to zero upon power-on.
8 2.3.5 Access Overload Class

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

Representation of the ACCOLCp
IMSI
0 0000
1 0001
2 0010
3 0011
4 0100
5 0101
6 0110
7 0111
8 1000
9 1001
3 Table 2.3.5-2. ACCOLCp Mapping for ACCOLC 10 through ACCOLC 15
Overload Class ACCOLCp
10 1010
11 1011
12 1100
13 1101
14 1110
15 1111
5 2.3.6 Reserved
6 2.3.7 Reserved
7 2.3.8 Home System and Network Identification

8 In addition to the HOME_SIDp parameter that the mobile station stores for 800 MHz analog
9 operation, the mobile station shall provide memory to store at least one home (SIDp, NIDp)
10 pair. The mobile station shall also provide memory to store the 1-bit parameters
11 MOB_TERM_HOMEp, MOB_TERM_FOR_SIDp, and MOB_TERM_FOR_NIDp (see 2.6.5.3).
2-8
C.S0005-0-2 v1.0
1 2.3.9 Local Control Option
2 If the mobile station supports the local control option, a means shall be provided within the
3 mobile station to enable or disable the local control option.
4 2.3.10 Preferred Operation Selection
5 2.3.10.1 Preferred System
6 If the mobile station supports operation in Band Class 0 or Band Class 3 (see TIA/EIA/IS-
7 2000-[2]), a means shall be provided within the mobile station to identify the preferred
8 system. In addition, the mobile station may provide a means for allowing operation only
9 with System A or only with System B.
10 2.3.10.2 Preferred CDMA or Analog
11 If the mobile station supports operation in Band Class 0 (see TIA/EIA/IS-2000-[2]), a

12 means may be provided within the mobile station to identify the preferred operation type as
13 either CDMA mode or analog mode. In addition, the mobile station may provide a means
14 for allowing operation only in the preferred mode.
15 2.3.11 Discontinuous Reception
16 The mobile station shall provide memory to store the preferred slot cycle index,
17 SLOT_CYCLE_INDEXp (see 2.6.2.1.1.3.2).
18 2.3.12 Authentication, Encryption of Signaling Information/User Data and Voice Privacy
19 2.3.12.1 Authentication
20 Authentication is the process by which information is exchanged between a mobile station

21 and base station for the purpose of confirming the identity of the mobile station. A
22 successful outcome of the authentication process occurs only when it can be demonstrated
23 that the mobile station and base station possess identical sets of shared secret data.
24 The authentication algorithms are described in “Common Cryptographic Algorithms.” The

25 interface (input and output parameters) for the algorithms is described in “Interface
26 Specification for Common Cryptographic Algorithms.” Table 2.3.12.1-1 summarizes the
27 setting of the input parameters of the Auth_Signature procedure for each of its uses in this
28 standard.
29 For authentication purposes, the mobile station shall use IMSI_M if it is programmed;
30 otherwise, the mobile station shall use IMSI_T. The base station uses the IMSI selected
31 according to the same criteria.
32
2-9
C.S0005-0-2 v1.0
1 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)
3 2.3.12.1.1 Shared Secret Data (SSD)
4 SSD is a 128-bit quantity that is stored in semi-permanent memory in the mobile station
5 and is readily available to the base station. As depicted in Figure 2.3.12.1.1-1, SSD is
6 partitioned into two distinct subsets. Each subset is used to support a different process.
Contents SSD_A SSD_B
Length (bits) 64 64
8 Figure 2.3.12.1.1-1. Partitioning of SSD
10 SSD_A is used to support the authentication procedures and SSD_B is used to support
11 voice privacy (see 2.3.12.3) and message encryption (see 2.3.12.2). SSD is generated
12 according to the procedure specified in 2.3.12.1.5. The SSD shall not be accessible to the
13 user.
14 2.3.12.1.2 Random Challenge Memory (RAND)
15 RAND is a 32-bit value held in the mobile station. When operating in CDMA mode, it is
16 equal to the RAND value received in the last Access Parameters Message (see 3.7.2.3.2.2) of
17 the CDMA f-csch.
18 RANDs is used in conjunction with SSD_A and other parameters, as appropriate, to
19 authenticate mobile station originations, terminations and registrations.
20 2.3.12.1.3 Call History Parameter (COUNTs-p)
21 COUNTs-p is a modulo-64 count held in the mobile station. COUNTs-p is updated by the
22 mobile station when a Parameter Update Order is received on the f-dsch (see 3.7.4).
23 2.3.12.1.4 Unique Challenge-Response Procedure
24 The Unique Challenge-Response Procedure is initiated by the base station and can be
25 carried out either on the f-csch and r-csch, or on the f-dsch and r-dsch. The procedure is
26 as follows:
2-10
C.S0005-0-2 v1.0
1 The base station generates the 24-bit quantity RANDU and sends it to the mobile station in
2 the Authentication Challenge Message on either the f-csch or f-dsch. Upon receipt of the
3 Authentication Challenge Message, the mobile station shall set the input parameters of the
4 Auth_Signature procedure (see “Interface Specification for Common Cryptographic
5 Algorithms,” section 2.3) as illustrated in Figure 2.3.12.1.4-1. The 24 most significant bits
6 of the RAND_CHALLENGE input parameter shall be filled with RANDU, and the 8 least
7 significant bits of RAND_CHALLENGE shall be filled with the 8 least significant bits of
8 IMSI_S2.
9 The mobile station shall set the SAVE_REGISTERS input parameter to FALSE.
10 The mobile station shall then execute the Auth_Signature procedure. The 18-bit output
11 AUTH_SIGNATURE shall be used to fill the AUTHU field of the Authentication Challenge
12 Response Message, which shall be sent to the base station.
13 The base station computes the value of AUTHU in the same manner as the mobile station,
14 but using its internally stored value of SSD_A. The base station compares its computed
15 value of AUTHU to the value received from the mobile station. If the comparison fails, the
16 base station may deny further access attempts by the mobile station, drop the call in
17 progress, or initiate the process of updating SSD (see 2.3.12.1.5).
18 2.3.12.1.5 Updating the Shared Secret Data (SSD)
19 SSD is updated using the SSD_Generation procedure (see “Interface Specification for
20 Common Cryptographic Algorithms,” section 2.2.1), initialized with mobile station specific
21 information, random data, and the mobile station’s A-key. The A-key is 64 bits long. It is
22 assigned to the mobile station and is stored in the mobile station’s permanent security and
23 identification memory. The A-key is known only to the mobile station and to its associated
24 Home Location Register/Authentication Center (HLR/AC) (see TIA/EIA-41-D[16]). Non-
25 manual methods, such as described in TIA/EIA/IS-683-A[32], are preferred for entry of the
26 A-key into the mobile station. TSB50 describes a manual method of entry that may be used
27 when automated methods are not available.
28 The SSD update procedure is performed as follows (see Figure 2.3.12.1.5-1):

29 The base station sends an SSD Update Message on either the f-csch or the f-dsch. The
30 RANDSSD field of the SSD Update Message contains the same value used for the HLR/AC
31 computation of SSD.
32 Upon receipt of the SSD Update Message the mobile station shall set the input parameters
33 of the SSD_Generation procedure (see “Interface Specification for Common Cryptographic
34 Algorithms,” section 2.2.1) as illustrated in Figure 2.3.12.1.5-2. The mobile station shall
35 then execute the SSD_Generation procedure. The mobile station shall set SSD_A_NEW and
36 SSD_B_NEW to the outputs of the SSD_Generation procedure.
37 The mobile station shall then select a 32-bit random number, RANDBS, and shall send it to
38 the base station in a Base Station Challenge Order on the r-csch or r-dsch.
39 Both the mobile station and the base station shall then set the input parameters of the
40 Auth_Signature procedure (see “Interface Specification for Common Cryptographic
2-11
C.S0005-0-2 v1.0
1 Algorithms,” section 2.3) as illustrated in Figure 2.3.12.1.5-3 and shall execute the
2 Auth_Signature procedure.
3 The mobile station and base station shall set the SAVE_REGISTERS input parameter to
4 FALSE.
5 The mobile station and base station shall execute the Auth_Signature procedure. AUTHBS
6 is set to the 18-bit result AUTH_SIGNATURE. The base station sends its computed value of
7 AUTHBS to the mobile station in a Base Station Challenge Confirmation Order on the f-csch
8 or the f-dsch.
9 Upon receipt of the Base Station Challenge Confirmation Order the mobile station shall
10 compare the received value of AUTHBS to its internally computed value. (If the mobile
11 station receives a Base Station Challenge Confirmation Order when an SSD update is not in
12 progress, the mobile station shall respond with an SSD Update Rejection Order.)
13 If the comparison is successful, the mobile station shall execute the SSD_Update procedure
14 (see “Interface Specification for Common Cryptographic Algorithms,” section 2.2.2) to set
15 SSD_A and SSD_B to SSD_A_NEW and SSD_B_NEW, respectively. The mobile station shall
16 then send an SSD Update Confirmation Order to the base station, indicating successful
17 completion of the SSD update.
18 If the comparison is not successful, the mobile station shall discard SSD_A_NEW and
19 SSD_B_NEW. The mobile station shall then send an SSD Update Rejection Order to the base
20 station, indicating unsuccessful completion of the SSD update.
21 Upon receipt of the SSD Update Confirmation Order, the base station sets SSD_A and SSD_B
22 to the values received from the HLR/AC (see EIA/TIA/IS-41).
23 If the mobile station fails to receive the Base Station Challenge Confirmation Order within
24 T64m seconds of when the acknowledgment to the Base Station Challenge Order was
25 received, the mobile station shall discard SSD_A_NEW and SSD_B_NEW. The mobile
26 station shall then terminate the SSD update process.
27
28
2-12
C.S0005-0-2 v1.0
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)
1
2 Figure 2.3.12.1.5-1. SSD Update Message Flow

3
2-13
C.S0005-0-2 v1.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

9
2-14
C.S0005-0-2 v1.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 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 §2.5.1, “Common Cryptographic Algorithms,” Revision C) or the Enhanced Cellular Message
8 Encryption Algorithm (see §2.5.2, “Common Cryptographic Algorithms,” Revision C). The
9 availability of encryption algorithm information is governed under the U.S. Export
10 Administration Regulations. TIA acts as the focal point and facilitator for making such
11 information available.
12 For each message, the enciphered fields are identified. The messages are grouped by
13 channel designation.
14 Messages shall not be encrypted if authentication is not performed (AUTHs is set to ‘00’).
15 See “Interface Specification for Common Cryptographic Algorithms” for details of the
16 initialization and use of the encryption procedure.
17 Signaling message encryption is controlled for each call individually. The mobile station
18 identifies its encryption capability in the ENCRYPTION_SUPPORTED field in the Origination
19 Message and the Page Response Message as shown in Table 2.7.1.3.2.4-5. The initial
20 encryption mode for the call is established by the value of the ENCRYPT_MODE field in the
21 Channel Assignment Message or in the Extended Channel Assignment Message. If
22 ENCRYPT_MODE is set to ‘00’, message encryption is off. To turn encryption on after
23 channel assignment, the base station sends one of the following f-dsch messages to the
24 mobile station:
25 • Extended Handoff Direction Message with the ENCRYPT_MODE field set to ‘01’ or
26 ‘10’
27 • General Handoff Direction Message with the ENCRYPT_MODE field set to ‘01’ or ‘10’
28 • Universal Handoff Direction Message with the ENCRYPT_MODE field set to ‘01’ or
29 ‘10’
30 • Analog Handoff Direction Message with the MEM field set to ‘1’
31 • Message Encryption Mode Order with the ENCRYPT_MODE field set to ‘01’ or ‘10’
32 To turn signaling message encryption off, the base station sends one of the following f-dsch
33 messages to the mobile station:
34 • Extended Handoff Direction Message with the ENCRYPT_MODE field set to ‘00’
35 • General Handoff Direction Message with the ENCRYPT_MODE field set to ‘00’
36 • Universal Handoff Direction Message with the ENCRYPT_MODE field set to ‘00’
37 • Analog Handoff Direction Message with the MEM field set to ‘0’
38 • Message Encryption Mode Order with the ENCRYPT_MODE field set to ‘00’
2-15
C.S0005-0-2 v1.0
1 Encryption shall apply only to the part of the Layer 3 message specified below.
2 When encryption is off, all fields of all Layer 3 messages sent by the mobile station and base
3 station are unencrypted.
4 When additional octets are inserted, the overall Lower Layers message length is updated to
5 reflect the addition. Specific Layer 3 record length fields (e.g., RECORD_LEN,
6 NUM_FIELDS, or NUM_DIGITS) shall not be affected by the insertion of additional bits.
7 If the Enhanced Cellular Message Encryption Algorithm is used, the following requirements
8 apply:
9 • The mobile station and base station shall each maintain an 8-bit encryption
10 sequence counter. The encryption sequence counter shall be incremented modulo
11 256 for each new encryption. The counter value, hereafter called ES_COUNT, shall
12 be used to form the SYNC parameter of the Enhanced Cellular Message Encryption
13 Algorithm as described below.
14 • As part of each encryption, an additional octet of value ES_COUNT shall be inserted

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

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

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

27 4. Continuous DTMF Tone Order (see 3.7.3.3.2.1) is encrypted.
28 The 16 bits comprised of ADD_RECORD_LEN, the order-specific fields and the first five
29 (5) bits of the RESERVED field shall be encrypted. These fields shall be treated by the
30 encryption procedure as a new single message.
36 – SYNC[1] = MSG_TYPE = ‘00000001’

37 5. Data Burst Message (see 3.7.3.3.2.4) is encrypted.
2-17
C.S0005-0-2 v1.0
1 If BURST_TYPE is equal to ‘111110’ or ‘111111’, all CHARi fields after the first two shall
2 be encrypted; otherwise, all CHARi fields shall be encrypted.
3 If the CHARi field consists of a single octet (NUM_FIELDS field equal to 1), an
4 additional octet of value ‘00000000’ shall be inserted following the information record
5 and shall be encrypted as if part of the record. (If the NUM_FIELDS field is 0, the
6 information record contains no type-specific fields, and the record contains no
7 encrypted data.)
8 If the Cellular Message Encryption Algorithm is used (ENCRYPT_MODEs equal to binary
9 ‘01’), the following requirements apply:
10 • If BURST_TYPE is equal to ‘000011’ (SMS) or ‘000100’ (OTASP), the message

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

18 set to ‘0’. Otherwise, the DATA_TYPE parameter shall be set to ‘1’.
21 – SYNC[1] = MSG_TYPE = ‘00000100’

22 6. Power Up Function Completion Message (see 3.7.3.3.2.30) is encrypted.
23 If the LOC_IND field is set to ‘1’, the fields RESERVED (3 bits), MS_LAT (22 bits),
24 MS_LONG (23 bits), and MS_LOC_TSTAMP (24 bits) are encrypted. These fields shall be
25 treated by the encryption procedure as a new single message.
26 Otherwise, if the LOC_IND field is set to ‘0’, no fields in this message are encrypted.

32 – SYNC[1] = MSG_TYPE = ‘00011110’
33 2.3.12.2.2 Encrypted Messages on the r-dsch

34 When encryption is on (ENCRYPT_MODEs equal to binary ‘01’ or ‘10’) the encryptable fields
35 of the following rdsch layer 3 messages, as listed below, shall be encrypted. All other r-dsch
36 messages shall be unencrypted.
37 1. Origination Continuation Message (see 2.7.2.3.2.9) is encrypted.
2-18
C.S0005-0-2 v1.0
1 The CHARi fields of the Origination Continuation Message shall be encrypted. These
2 fields shall be treated by the encryption procedure as a new single message, with the
3 character codes packed into consecutive octets. If DIGIT_MODE is ‘0’ and the
4 NUM_FIELDS field contains an odd number, four bits of value ‘0000’ shall follow the
5 last digit and shall be included in the encrypted part of the message. In addition, if
6 ENCRYPT_MODEs is equal to ‘01’, the following requirement applies
7 !" If DIGIT_MODE is ‘0’ and NUM_FIELDS is less than 3, or if DIGIT_MODE is ‘1’ and
8 NUM_FIELDS is less than 2, an additional eight bits of value ‘00000000’ shall follow
9 the CHARi fields and shall be included in the encrypted part of the message.
15 – SYNC[1] = MSG_TYPE = ‘00001001’

16 The type-specific fields of all information records (see 2.7.4) in the Origination
17 Continuation Message shall be encrypted. For each information record, the type-specific
18 fields shall be treated by the encryption procedure as a new single message. If the type-
19 specific fields of an information record consist of a single octet (RECORD_LEN field
20 equal to 1), an additional octet of value ‘00000000’ shall be inserted following the
21 information record and shall be encrypted as if part of the record. (If the RECORD_LEN
22 field is 0, the information record contains no type-specific fields, and the record
23 contains no encrypted data.)
30 2. Flash With Information Message (see 2.7.2.3.2.3) is encrypted.
38 No other fields in the Flash With Information Message are encrypted.
2-19
C.S0005-0-2 v1.0
6 3. Send Burst DTMF Message (see 2.7.2.3.2.7) is encrypted.
7 The DIGITi fields of the Send Burst DTMF Message shall be encrypted. These fields shall
8 be treated by the encryption procedure as a new single message, with the 4-bit digit
9 codes packed into consecutive octets. If the NUM_DIGITS field contains an odd
10 number, four bits of value ‘0000’ shall follow the last digit and shall be included in the
11 encrypted message. If NUM_DIGITS is less than 3, an additional eight bits of value
12 ‘00000000’ shall follow the DIGITi fields and shall be included in the encrypted part of
13 the message.
19 – SYNC[1] = MSG_TYPE = ‘00000111’

20 4. Continuous DTMF Tone Order (see 2.7.2.3.2.1) is encrypted.
21 The 16 bits comprised of ADD_RECORD_LEN, the order-specific fields and the first five
22 (5) bits of the RESERVED field shall be encrypted. These fields shall be treated by the
23 encryption procedure as a new single message.
29 – SYNC[1] = MSG_TYPE = ‘00000001’

30 5. Data Burst Message (see 2.7.2.3.2.4) is encrypted.
31 If BURST_TYPE is equal to ‘111110’ or ‘111111’, all CHARi fields after the first two shall
32 be encrypted; otherwise, all CHARi fields shall be encrypted.
33 If the CHARi field consists of a single octet (NUM_FIELDS field equal to 1), an
34 additional octet of value ‘00000000’ shall be inserted following the information record
35 and shall be encrypted as if part of the record. (If the NUM_FIELDS field is 0, the
36 information record contains no type-specific fields, and the record contains no
37 encrypted data.)
2-20
C.S0005-0-2 v1.0
1 If the Cellular Message Encryption Algorithm is used (ENCRYPT_MODEs equal to binary

2 ‘01’), the following requirements apply:
3 • If BURST_TYPE is equal to ‘000011’ (SMS) or ‘000100’ (OTASP), the message

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

11 set to ‘0’. Otherwise, the DATA_TYPE parameter shall be set to ‘1’.
14 – SYNC[1] = MSG_TYPE = ‘00000100’
15 2.3.12.3 Voice Privacy
16 Also see TIA/EIA/IS-2000-[2].
17 Voice privacy is provided in the CDMA system by means of the private long code mask used
18 for PN spreading.
19 Voice privacy is provided on the Traffic Channels only. All calls are initiated using the
20 public long code mask for PN spreading. The mobile station user may request voice privacy
21 during call setup using the Origination Message or Page Response Message, and during
22 Traffic Channel operation using the Long Code Transition Request Order.
23 The transition to private long code mask shall not be performed if authentication is not
24 performed (AUTHs is set to ‘00’ or mobile station unable to perform authentication).
25 To initiate a transition to the private or public long code mask, either the base station or
26 the mobile station sends a Long Code Transition Request Order on the f-dsch or r-dsch. The
27 mobile station actions in response to receipt of this order are specified in 2.6.4, and the
28 base station actions in response to receipt of this order are specified in 3.6.4.
29 The base station can also cause a transition to the private or public long code mask by
30 sending the Extended Handoff Direction Message, the General Handoff Direction Message, or
31 the Universal Handoff Direction Message with the PRIVATE_LCM bit set appropriately.
32 2.3.13 Lock and Maintenance Required Orders

33 The mobile station shall have memory to store the lock reason code (LCKRSN_Ps-p) received
34 in the Lock Until Power-Cycled Order. The data retention time under power-off conditions
35 shall be at least 48 hours.
36 The mobile station shall have memory to store the maintenance reason code (MAINTRSNs-p)
37 received in the Maintenance Required Order. The data retention time under power-off
38 conditions shall be at least 48 hours.
2-21
C.S0005-0-2 v1.0
1 There are no requirements on the use of the lock and maintenance reason codes, and
2 interpretation and use are implementation dependent.
3 2.3.14 Mobile Station Revision Identification
4 The mobile station shall provide memory to store the following parameters sent in the
5 Status Message, the Status Response Message, or the Extended Status Response Message
6 (Terminal Information information record):
7 • Mobile manufacturer code (MOB_MFG_CODEp)
8 • Manufacturer’s model number (MOB_MODELp)
9 • Firmware revision number (MOB_FIRM_REVp)
10 In addition, the mobile station shall provide memory to store the following parameter for
11 each supported band class:
12 • Protocol revision number (MOB_P_REVp)
13 2.3.15 Temporary Mobile Station Identity
14 2.3.15.1 Overview
15 The Temporary Mobile Station Identity (TMSI) is a temporary locally assigned number used
16 for addressing the mobile station. The mobile station obtains a TMSI when assigned by the
17 base station. The TMSI as a number does not have any association with the mobile
18 station’s IMSI, ESN, or directory number all of which are permanent identifications.
19 A TMSI zone is an arbitrary set of base stations for the administrative assignment of TMSIs.
20 A TMSI_CODE is uniquely assigned to a mobile station inside a TMSI zone. A TMSI zone is
21 identified by the TMSI_ZONE field. The same TMSI_CODE may be reused to identify a
22 different mobile station in a different TMSI zone. The pair (TMSI_ZONE, TMSI_CODE) is a
23 globally unique identity for the mobile station. This pair is called the full TMSI. The
24 TMSI_CODE can be two, three, or four octets in length. The TMSI_ZONE can range from 1
25 to 8 octets in length. Figure 2.3.15-1 shows an example of a TMSI_ZONE where the
26 TMSI_ZONE is a subset of the NID (see 2.6.5.2).
27
2-22
C.S0005-0-2 v1.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-23
C.S0005-0-2 v1.0
2 2.4 Accumulated Statistics
3 2.4.1 Monitored Quantities and Statistics
4 The mobile station shall store the value described in Table 2.4.1-1.
6 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
7 2.4.2 Accumulated Paging Channel Statistics
8 The mobile station shall maintain the counters shown in Table 2.4.2-1. The counters shall
9 have the length as specified in Table 2.4.2-1. The mobile station shall initialize each
10 counter described herein to zero upon power-on; the mobile station shall not re-initialize
11 any counter described herein at any other time except upon command from the base
12 station. Each counter shall be maintained modulo 2Length, where Length is specified in
13 Table 2.4.2-1.
14 The mobile station shall increment the counter PAG_6 each time that it declares a loss of
15 the Paging Channel (see 2.6.2.1.1.4). The mobile station shall increment the counter
16 PAG_7 for each idle handoff it performs.
17 Table 2.4.2-1. Accumulated PCH 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
18
2-24
C.S0005-0-2 v1.0
1 2.5 Reserved
2
2-25
C.S0005-0-2 v1.0
1 No text.
2
2-26
C.S0005-0-2 v1.0
1 2.6 Call Processing
2 This section describes mobile station call processing. It contains frequent references to the
3 messages that flow between the mobile station and base station. While reading this
4 section, it may be helpful to refer to the SDU 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 call processing consists of the following states:
11 • Mobile Station Initialization State - In this state, the mobile station selects and
12 acquires a system.
13 • Mobile Station Idle State - In this state, the mobile station monitors messages on the
14 f-csch.
15 • System Access State - In this state, the mobile station sends messages to the base
16 station on the r-csch.
17 • Mobile Station Control on the Traffic Channel State - In this state, the mobile station
18 communicates with the base station using the f-dsch and r-dsch.
19 After power is applied to the mobile station, it shall enter the System Determination Substate
20 of the Mobile Station Initialization State with a power-up indication (see 2.6.1.1).
21
2-27
C.S0005-0-2 v1.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 Mobile station
NGHBR_CONFIG has fully
equal to acquired
'011' or unable to system timing
receive Paging
Channel message
Mobile
Station
Idle State
(2.6.2)
Receives an
acknowledgment Receives a Paging
to an Access Channel message
Channel requiring an
transmission acknowledgment or
other than an response; originates a
Origination call or performs
Message or a registration.
Page Response
Message
System
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 Call Processing States

3
2-28
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-[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.
18
2-29
C.S0005-0-2 v1.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

3
2-30
C.S0005-0-2 v1.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, and T_SLOTTEDs to T74m. If the mobile station
9 supports analog mode operation in Band Class 0, the mobile station shall set the First-Idle
10 ID status to enabled (see 2.6.3.11 of TIA/EIA/IS-2000-6[6]). The mobile station shall select
11 a system in accordance with the custom system selection process (see 2.6.1.1.1), and shall
12 attempt to acquire the selected system (see 2.6.1.1.4).
13 If the mobile station enters the System Determination Substate with any indication other
14 than a power-up indication, and if PACAs is equal to enabled, the mobile station shall also
15 set PACAs to disabled, PACA_CANCEL to ‘0’, the PACA state timer to disabled, and should
16 indicate to the user that the PACA call has been canceled.
17 If the mobile station enters the System Determination Substate with an acquisition failure
18 indication, the mobile station shall perform the following:
19 • If REDIRECTIONs is equal to enabled, the mobile station shall attempt to select
20 another system in accordance with the current redirection criteria (see 2.6.1.1.2). If
21 the mobile station is able to select another system, the mobile station shall attempt
22 to acquire the selected system (see 2.6.1.1.4). Otherwise, if the mobile station has
23 exhausted all possible selections using the current redirection criteria, the mobile
24 station shall perform the following:
25 – The mobile station shall set REDIRECTIONs to disabled.
26 – The mobile station shall set RETURN_CAUSEs to ‘0001’.
27 – If RETURN_IF_FAILs is equal to ‘1’, the mobile station shall attempt to select the
28 system from which it was redirected, and shall attempt to acquire the selected
29 system (see 2.6.1.1.4). The precise process for determining how to select the
30 system from which the mobile station was redirected is left to the mobile station
31 manufacturer.
32 – If RETURN_IF_FAILs is equal to ‘0’, the mobile station shall select a system other
33 than the system from which it was redirected in accordance with the custom
34 system selection process (see 2.6.1.1.1), and shall attempt to acquire the
35 selected system (see 2.6.1.1.4). The precise process that the mobile station uses
36 to avoid selecting the system from which it was redirected is left to the mobile
37 station manufacturer.
38 • If REDIRECTIONs is equal to disabled, the mobile station shall select a system in
39 accordance with the custom system selection process (see 2.6.1.1.1), and shall
2-31
C.S0005-0-2 v1.0
1 If the mobile station enters the System Determination Substate with a new system
2 indication, the mobile station shall set REDIRECTIONs to disabled. If NDSS_ORIGs is
3 enabled, the mobile station shall set NDSS_ORIGs to disabled and should indicate to the
4 user that the call origination has been canceled. The mobile station shall select a system in
5 accordance with the custom system selection process (see 2.6.1.1.1), and shall attempt to
6 acquire the selected system (see 2.6.1.1.4).
7 If the mobile station enters the System Determination Substate with a CDMA available
10 user that the call origination is canceled. The mobile station should set CDMACHs to the
11 CDMA Channel (CDMA_FREQ) specified in the CDMA Capability Global Action Message and
12 should attempt to acquire a CDMA system on the specified CDMA channel (see 2.6.1.1.4).
13 If the mobile station does not attempt to acquire a CDMA system on the specified CDMA
14 Channel, the mobile station shall select a system in accordance with the custom system
15 selection process (see 2.6.1.1.1), and shall attempt to acquire the selected system (see
16 2.6.1.1.4).
17 If the mobile station enters the System Determination Substate with an additional CDMA
18 available indication, the mobile station shall set REDIRECTIONs to disabled. If
19 NDSS_ORIGs is enabled, the mobile station shall set NDSS_ORIGs to disabled and should
20 indicate to the user that the call origination is canceled. The mobile station should set
21 CDMACHs to the CDMA Channel (CDMA_FREQ) specified in the CDMA Info Order and
22 should attempt to acquire a CDMA system on the specified CDMA channel (see 2.6.1.1.4).
23 If the mobile station does not attempt to acquire a CDMA system on the specified CDMA
24 Channel, the mobile station shall select a system in accordance with the custom system
25 selection process (see 2.6.1.1.1), and shall attempt to acquire the selected system (see
26 2.6.1.1.4).
27 If the mobile station enters the System Determination Substate with a reselection indication,
28 the mobile station shall set REDIRECTIONs to disabled. If NDSS_ORIGs is enabled, the
29 mobile station shall set NDSS_ORIGs to disabled and should indicate to the user that the
30 call origination is canceled. The mobile station shall select a system in accordance with the
31 custom system selection process (see 2.6.1.1.1), and shall attempt to acquire the selected
32 system (see 2.6.1.1.4).
33 If the mobile station enters the System Determination Substate with a system reselection
36 user that the call origination is canceled. The mobile station should attempt to select a
37 system available for system reselection as specified in 2.6.1.1.3, and should attempt to
38 acquire the selected system (see 2.6.1.1.4). The precise process for determining how to
39 select such a system is left to the mobile station manufacturer. If the mobile station does
40 not attempt to select such a system, the mobile station shall select a system in accordance
41 with the custom system selection process (see 2.6.1.1.1), and shall attempt to acquire the
42 selected system (see 2.6.1.1.4).
43 If the mobile station enters the System Determination Substate with a rescan indication, the
44 mobile station shall set REDIRECTIONs to disabled. If NDSS_ORIGs is enabled, the mobile
2-32
C.S0005-0-2 v1.0
1 station shall set NDSS_ORIGs to disabled and should indicate to the user that the call
2 origination is canceled. The mobile station shall select a system in accordance with the
4 system (see 2.6.1.1.4).
5 If the mobile station enters the System Determination Substate with a protocol mismatch
19 manufacturer.
23 selected system (see 2.6.1.1.4). The precise process for determining how to avoid
24 the system from which the mobile station was redirected is left to the mobile
29 If the mobile station enters the System Determination Substate with a system lost indication,
32 call origination is canceled. The mobile station should attempt to select the same system
33 that was lost, and should attempt to acquire the selected system (see 2.6.1.1.4). The
34 precise process for determining how to select the same system is left to the mobile station
35 manufacturer. If the mobile station does not attempt to select the same system, the mobile
36 station shall select a system in accordance with the custom system selection process (see
37 2.6.1.1.1), and shall attempt to acquire the selected system (see 2.6.1.1.4).
38 If the mobile station enters the System Determination Substate with a lock indication, the
2-33
C.S0005-0-2 v1.0
2 system (see 2.6.1.1.4).
3 If the mobile station enters the System Determination Substate with an unlock indication,
8 system (see 2.6.1.1.4).
9 If the mobile station enters the System Determination Substate with an access denied
12 user that the call origination is canceled. The mobile station shall select a system in
13 accordance with the custom system selection process (see 2.6.1.1.1), and shall attempt to
15 If the mobile station enters the System Determination Substate with an NDSS off indication,
20 system (see 2.6.1.1.4).
21 If the mobile station enters the System Determination Substate with a release indication and
22 REDIRECTIONs is equal to enabled, the mobile station shall attempt to select the same
23 system on which the release occurred, and shall attempt to acquire the selected system (see
24 2.6.1.1.4). The precise process for determining how to select the same system is left to the
25 mobile station manufacturer. If REDIRECTIONs is equal to disabled, the mobile station
26 shall select a system in accordance with the custom system selection process (see
27 2.6.1.1.1), and shall attempt to acquire the selected system (see 2.6.1.1.4). If NDSS_ORIGs
28 is enabled, the mobile station shall set NDSS_ORIGs to disabled.
29 If the mobile station enters the System Determination Substate with an error indication, the
34 system (see 2.6.1.1.4).
35 If the mobile station enters the System Determination Substate with a redirection indication,
36 the mobile station shall set REDIRECTIONs to enabled. The mobile station shall delete all
37 entries from the ZONE_LISTs and SID_NID_LISTs. The mobile station shall select a system
38 in accordance with the current redirection criteria (see 2.6.1.1.2), and shall attempt to
40 If the mobile station enters the System Determination Substate with a registration rejected
42 • If REDIRECTIONs is equal to enabled, the mobile station shall perform the following:
2-34
C.S0005-0-2 v1.0
7 manufacturer.
17 If the mobile station enters the System Determination Substate with a wrong system
31 manufacturer.
2-35
C.S0005-0-2 v1.0
1 If the mobile station enters the System Determination Substate with a wrong network
15 manufacturer.
25 2.6.1.1.1 Custom System Selection Process
26 The precise process for custom system selection is left to the mobile station
27 manufacturer typically influenced by a set of expressed user preferences.
28 The mobile station shall perform the custom system selection process as follows:
29 • The mobile station shall determine which system to use.

30 • If the mobile station is to use a CDMA system, it shall set CDMABANDs to the band
31 class (see TSB58-A) for the selected system.
32 • If the mobile station is to use a CDMA system with CDMABANDs = ‘00000’ or
33 CDMABANDs = ‘00011’, it shall perform the following:
34 – If the mobile station is to use System A, it shall set SERVSYSs to SYS_A. If the
35 mobile station is to use System B, it shall set SERVSYSs to SYS_B.
2-36
C.S0005-0-2 v1.0
1 – The mobile station shall set CDMACHs either to the Primary or Secondary CDMA
2 Channel number (see 2.1.1.1.1 of TIA/EIA/IS-2000-2[2]) for the selected serving
3 system (SERVSYSs). If the mobile station fails to acquire a CDMA system on the
4 first CDMA Channel it tries, the mobile station should attempt to acquire on the
5 alternate CDMA Channel (Primary or Secondary) before attempting other
6 alternatives.
7 • If the mobile station is to use a CDMA system with CDMABANDs = ‘00001’,
8 CDMABANDs = ‘00010’, CDMABANDs = ‘00100’, CDMABANDs = ‘00101’,
9 CDMABANDs = ‘00110’, or CDMABANDs = ‘00111’, CDMABANDs = ‘01000’, or
10 CDMABANDs = ‘01001’, it shall set CDMACHs to the CDMA Channel number (see
11 2.1.1.1.1 of TIA/EIA/IS-2000-2[2]) for the selected system.
12 If the mobile station is to use System A of the 800 MHz analog system, it shall set
13 SERVSYSs to SYS_A. If the mobile station is to use System B of the 800 MHz analog
14 system, it shall set SERVSYSs to SYS_B.
15 2.6.1.1.2 System Selection Using Current Redirection Criteria
16 To perform system selection using current redirection criteria, the mobile station shall use
17 information received either in a Service Redirection Message, a Global Service Redirection
18 Message, or a Extended Global Service Redirection Message and stored in the variable
19 REDIRECT_RECs.
20 If the RECORD_TYPE field of REDIRECT_RECs is equal to ‘00000001’ and the mobile

21 station supports Band Class 0, the mobile station shall perform system selection as follows:
22 • If the SYS_ORDERING field is equal to ‘000’, the mobile station shall make
23 sequential system selections as follows:
24 – The mobile station shall set SERVSYSs either to SYS_A or SYS_B. The precise
25 process for determining how many system selections to make and for
26 determining whether to use SYS_A or SYS_B is left to the mobile station
27 manufacturer.
28 • If the SYS_ORDERING field is equal to ‘001’, the mobile station shall select no more
29 than one system selection as follows:
30 – The mobile station shall set SERVSYSs to SYS_A.
31 • If the SYS_ORDERING field is equal to ‘010’, the mobile station shall select no more
32 than one system selection as follows:
33 – The mobile station shall set SERVSYSs to SYS_B.
34 • If the SYS_ORDERING field is equal to ‘011’, the mobile station shall make at most
35 two sequential system selections as follows:
36 – For the first system selection, the mobile station shall set SERVSYSs to SYS_A.
37 – For the second system selection, the mobile station shall set SERVSYSs to
38 SYS_B.
2-37
C.S0005-0-2 v1.0
1 • If the SYS_ORDERING field is equal to ‘100’, the mobile station shall make at most 2
3 – For the first system selection, the mobile station shall set SERVSYSs to SYS_B.
5 SYS_A.
6 • If the SYS_ORDERING field is equal to ‘101’, the mobile station shall make at most 2
8 – For the first system selection, the mobile station shall set SERVSYSs either to
9 SYS_A or SYS_B. The precise process for determining whether to use SYS_A or
10 SYS_B first is left to the mobile station manufacturer.
12 SYS_B if SYS_A was used for the first selection, or to SYS_A if SYS_B was used
13 for the first selection.
14 If the RECORD_TYPE field of REDIRECT_RECs is equal to ‘00000010’, the mobile station
15 shall perform system selection as follows:
16 • If the mobile station supports CDMA mode operation in the band class identified by
17 the BAND_CLASS field, the mobile station shall make at most n sequential system
18 selections, where n is equal to the value of the NUM_CHANS field, as follows:
19 – For the ith system selection, where i ranges from 1 to n, if the mobile station
20 supports operation on the CDMA channel associated with the value of the ith
21 occurrence of the CDMA_CHAN field, the mobile station shall set CDMACHs to
22 the value of the ith occurrence of the CDMA_CHAN field and shall set
23 CDMABANDs to the value specified in the BAND_CLASS field. If the mobile
24 station does not support operation on the CDMA Channel associated with the
25 value of the ith occurrence of the CDMA_CHAN field, the mobile station shall not
26 make the ith system selection.
27 2.6.1.1.3 System Selection Using System Reselection Criteria
28 The precise process for selecting a system using system reselection criteria is left to the
29 mobile station manufacturer. The mobile station should use information received in the
30 Neighbor List Message, Extended Neighbor List Message or the General Neighbor List
31 Message to perform the system reselection process as follows:
32 • If there are pilots in the Neighbor List on a different Frequency Assignment than
33 that of the mobile station, the mobile station may select the CDMA system
34 consisting of these neighbor pilots. If the mobile station is to use a CDMA system, it
35 shall set CDMABANDs to the band class (see TSB58-A) for the selected system and
36 shall set CDMACHs to the CDMA Channel number (see 2.1.1.1 of TIA/EIA/IS-2000-
37 2[2]) for the selected system.
2-38
C.S0005-0-2 v1.0
1 • If NUM_ANALOG_NGHBRs is not equal to ‘000’, the mobile station may select an

2 analog system as specified by ANALOG_NGHBR_LIST. If the mobile station is to use
3 System A of the 800 MHz analog system, it shall set SERVSYSs to SYS_A. If the
4 mobile station is to use System B of the 800 MHz analog system, it shall set
5 SERVSYSs to SYS_B.
6 2.6.1.1.4 Acquiring the Selected System
7 The mobile station shall attempt to acquire the selected system as follows:
8 • If the selected system is an analog system, the mobile station shall enter the
9 Initialization Task (see 2.6.1 of TIA/EIA/IS-2000-6[6]).
10 • If the selected system is a CDMA system, the mobile station shall enter the Pilot
11 Channel Acquisition Substate.
12 2.6.1.2 Pilot Channel Acquisition Substate
13 In this substate, the mobile station acquires the Pilot Channel of the selected CDMA
14 system.
15 Upon entering the Pilot Channel Acquisition Substate, the mobile station shall tune to the
16 CDMA Channel number equal to CDMACHs, shall set its code channel for the Pilot Channel
17 (see 3.1.3.1.10 of TIA/EIA/IS-2000-2[2]), and shall search for the Pilot Channel for no
18 longer than T20m seconds (see Annex D). If the mobile station acquires the Pilot Channel,
19 the mobile station shall enter the Sync Channel Acquisition Substate.
20 If the mobile station determines that it is unlikely to acquire the Pilot Channel within T20m
21 seconds, the mobile station may enter the System Determination Substate with an
22 acquisition failure indication (see 2.6.1.1). The time, to either acquire the Pilot Channel or
23 determine that Pilot Channel acquisition is unlikely, shall not exceed T20m seconds (see
24 Annex D), after which the mobile station shall enter the System Determination Substate with
25 an acquisition failure indication (see 2.6.1.1).
26 2.6.1.3 Sync Channel Acquisition Substate

27 In this substate, the mobile station receives and processes the Sync Channel Message to
28 obtain system configuration and timing information.
29 Upon entering the Sync Channel Acquisition Substate, the mobile station shall set its code
30 channel for the Sync Channel (see TIA/EIA/IS-2000-[2]).
31 If the mobile station does not receive a valid Sync Channel Message within T21m seconds,
32 the mobile station shall enter the System Determination Substate with an acquisition failure
33 indication.
34 If the mobile station receives a valid Sync Channel Message within T21m seconds but the
35 protocol revision level supported by mobile station (MOB_P_REVp of the current band class)
36 is less than the minimum protocol revision level supported by the base station
37 (MIN_P_REVr), the mobile station shall enter the System Determination Substate with a
38 protocol mismatch indication (see 2.6.1.1).
2-39
C.S0005-0-2 v1.0
1 If the mobile station receives a valid Sync Channel Message within T21m seconds but the
2 value of the PRATr field is designated as reserved by the protocol revision level supported by
3 the mobile station (MOB_P_REVp of the current band class), the mobile station shall enter
4 the System Determination Substate with a protocol mismatch indication (see 2.6.1.1).
5 If the mobile station receives a valid Sync Channel Message within T21m seconds and the
6 protocol revision level supported by the mobile station (MOB_P_REVp of the current band
7 class) is greater than or equal to the minimum protocol revision level supported by the base
8 station (MIN_P_REVr), the mobile station shall store the following information from the
9 message:
10 • Protocol revision level (P_REVs = P_REVr)
11 • Minimum protocol revision level (MIN_P_REVs = MIN_P_REVr)
12 • System identification (SIDs = SIDr)
13 • Network identification (NIDs = NIDr)
14 • Pilot PN sequence offset index (PILOT_PNs = PILOT_PNr)
15 • Long code state (LC_STATEs = LC_STATEr)
16 • System Time (SYS_TIMEs = SYS_TIMEr)
17 • Paging Channel data rate (PRATs = PRATr)
18 • Protocol revision level currently in use (P_REV_IN_USEs = the lesser value of P_REVs
19 and MOB_P_REVp of the current band class)
20 The mobile station shall ignore any fields at the end of the Sync Channel Message that are
21 not defined according to the protocol revision level (MOB_P_REVp of the current band class)
22 being used by the mobile station.
23 The mobile station may store the following information from the message:
24 • Number of leap seconds that have occurred since the start of System Time
25 (LP_SECs = LP_SECr)
26 • Offset of local time from System Time (LTM_OFFs = LTM_OFFr)
27 • Daylight savings time indicator (DAYLTs = DAYLTr)
28 If REDIRECTIONs and NDSS_ORIGs are equal to disabled, the mobile station may enter the
29 System Determination Substate with a reselection indication (see 2.6.1.1).
30 If REDIRECTIONs is equal to enabled, the EXPECTED_SID field of REDIRECT_RECs is not
31 equal to 0, and SIDr is not equal to EXPECTED_SID, the mobile station shall enter the
32 System Determination Substate with a wrong system indication (see 2.6.1.1). If
33 REDIRECTIONs is equal to enabled, the EXPECTED_NID field of REDIRECT_RECs is not
34 equal to 65535, and NIDr is not equal to EXPECTED_NID, the mobile station shall enter the
35 System Determination Substate with a wrong network indication.
36 If the mobile station does not support both the Quick Paging Channel and any radio
37 configuration in the Radio Configuration Class 2 (see 1.1.1), and CDMACHs is different from
2-40
C.S0005-0-2 v1.0
1 CDMA_FREQr, the mobile station shall set CDMACHs = CDMA_FREQr and shall then tune
2 to the CDMA Channel.
3 If P_REV_IN_USEs is greater than or equal to 6, the mobile station supports either the
4 Quick Paging Channel or any radio configuration in the Radio Configuration Class 2 (see
5 1.1.1), and CDMACHs is different from EXT_CDMA_FREQr, the mobile station shall set
6 CDMACHs = EXT_CDMA_FREQr and shall then tune to the CDMA Channel.
7 The mobile station shall enter the Timing Change Substate.
8 2.6.1.4 Timing Change Substate
9 Figure 2.6.1.4-1 illustrates the mobile station timing changes that occur in this substate.
10 The mobile station synchronizes its long code timing and system timing to those of the
11 CDMA system, using the PILOT_PNs, LC_STATEs, and SYS_TIMEs values obtained from the
12 received Sync Channel Message. SYS_TIMEs is equal to the System Time (see 1.2)
13 corresponding to 320 ms past the end of the last 80 ms superframe (see Figure 3.1.3.2.1-1
14 of TIA/EIA/IS-2000-2[2]) of the received Sync Channel Message minus the pilot PN
15 sequence offset. LC_STATEs is equal to the system long code state (see 2.1.3.1.12 of
16 TIA/EIA/IS-2000-[2]) corresponding to SYS_TIMEs.
17 In the Timing Change Substate, the mobile station shall synchronize its long code timing to
18 the CDMA system long code timing derived from LC_STATEs, and synchronize its system
19 timing to the CDMA system timing derived from SYS_TIMEs.
20 The mobile station shall:

21 • Set PAGECHs to the Primary Paging Channel (see 3.1.3.4 of TIA/EIA/IS-2000-[2]);
22 • Set PAGE_CHANs to ‘1’;
23 • Set the stored message sequence numbers CONFIG_MSG_SEQs,

24 SYS_PAR_MSG_SEQs, ACC_MSG_SEQs, NGHBR_LST_MSG_SEQs,
25 GEN_NGHBR_LST_MSG_SEQs, EXT_NGHBR_LST_MSG_SEQs,
26 CHAN_LST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs,
27 GLOB_SERV_REDIR_MSG_SEQs, EXT_GLOB_SERV_REDIR_MSG_SEQs,
28 EXT_CHAN_LST_MSG_SEQs USER_ZONE_ID_MSG_SEQs and
29 PRI_NGHBR_LST_MSG_SEQs variables to NULL (see 2.6.2.2);
30 • Set IMSI_11_12s and MCCs to NULL;
31 • Perform registration initialization as specified in 2.6.5.5.1.3; and

32 • If the bits of TMSI_CODEs-p are not all equal to ‘1’ and if SYS_TIMEs exceeds
33 TMSI_EXP_TIMEs-p × 212, the mobile station shall set all the bits of TMSI_CODEs-p
34 to ‘1’.
35 The mobile station shall enter the Mobile Station Idle State.
2-41
C.S0005-0-2 v1.0
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
1
2
3 Figure 2.6.1.4-1. Mobile Station Internal Timing
2-42
C.S0005-0-2 v1.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 The mobile station can receive messages, receive an incoming call (mobile station
4 terminated call), initiate a call (mobile station originated call), cancel a PACA call, initiate a
5 registration, or initiate a message transmission.
6 Upon entering the Mobile Station Idle State, the mobile station shall perform the following:
7 • Set its code channel to PAGECHs,
8 • Set the Paging Channel data rate as determined by PRATs,
9 • Set SLOTTEDs to YES if T_SLOTTEDs is equal to ‘00000000’; or if the mobile station

10 does not support the slotted timer; otherwise enable the TMS_Slotted timer with the
11 duration specified by T_SLOTTEDs, and
12 • Perform Paging Channel supervision as specified in 2.6.2.1.1.4.

13 If REDIRECTIONs, PACAs, and NDSS_ORIGs are equal to disabled, the mobile station may
14 exit the Mobile Station Idle State at any time and enter the System Determination Substate of
15 the Mobile Station Initialization State with a reselection indication (see 2.6.1.1).
16 While in the Mobile Station Idle State, the mobile station shall perform the following
17 procedures:
18 • The mobile station shall perform Paging Channel monitoring procedures as specified
19 in 2.6.2.1.1.
20 • The mobile station shall perform message acknowledgment procedures as specified

21 in 2.1.1.2 and 2.1.2.1 of TIA/EIA/IS-2000-4[4].
22 • The mobile station shall perform registration procedures as specified in 2.6.2.1.3.
23 • The mobile station shall perform idle handoff procedures as specified in 2.6.2.1.4.
24 • The mobile station shall perform system reselection procedures as specified in

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

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

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

17 which has a class 0 IMSI assigned, and is operating in the slotted mode and has a TMSI
18 assigned (the bits of TMSI_CODEs-p are not all equal to ‘1’) may stop monitoring the Paging
19 Channel after processing a page record with a TMSI_CODE value of higher numerical value
20 than TMSI_CODEs-p.
21 If ORDERED_TMSIS is equal to ‘1’ and CLASS_1_DONE is equal to ‘1’, a mobile station

22 which has a class 1 IMSI assigned, is operating in the slotted mode and has a TMSI
23 assigned (the bits of TMSI_CODEs-p are not all equal to ‘1’) may stop monitoring the Paging
24 Channel after processing a page record with a TMSI_CODE value of higher numerical value
25 than TMSI_CODEs-p.
26 The mobile station continues to monitor the Paging Channel for one additional slot unless,
27 within its assigned slot, the mobile station receives a General Page Message containing the
28 appropriate indicator permitting it to stop monitoring the Paging Channel (CLASS_0_DONE,
29 CLASS_1_DONE, TMSI_DONE, or ORDERED_TMSIS equal to ‘1’, whichever is appropriate).
30 This allows the base station to carry over a message begun in the assigned slot into the
31 following slot if necessary.
32 2.6.2.1.1.1.2 General Overview for Broadcast Messages
33 The Paging Channel protocol provides two methods for the transmission of broadcast
34 messages. Each method enables mobile stations operating in the slotted mode or in the
35 non-slotted mode to receive broadcast messages. A broadcast message on the Paging
36 Channel is a Data Burst Message that has a broadcast address type. A mobile station
37 operating in the slotted mode has assigned slots that it monitors to receive Paging Channel
38 messages (see 2.6.2.1.1.1). A broadcast page is a record within a General Page Message
39 that has a broadcast address type. A base station may transmit a broadcast page in an
40 assigned slot to inform mobile stations monitoring that slot that a broadcast message will
41 be transmitted in a predetermined subsequent slot. A slot that a mobile station monitors in
42 order to receive either a broadcast page or a broadcast message is referred to as a broadcast
43 slot.
2-47
C.S0005-0-2 v1.0
1 2.6.2.1.1.1.2.1 Method 1: Multi-Slot Broadcast Message Transmission
2 According to this method, a broadcast message is sent in a sufficient number of assigned

3 slots such that it may be received by all mobile stations that are operating in the slotted
4 mode.
5 Figure 2.6.2.1.1.1.2.1-1 shows an example for the case when the maximum slot cycle index
6 is equal to 0. In this example, the broadcast message fits in a single slot. The Data Burst
7 Message is transmitted in 16 consecutive slots.
1.28 seconds (16

slots)
... ...
Paging Channel Slots Data Burst Message is sent in 16
9
consecutive slots
10 Figure 2.6.2.1.1.1.2.1-1. Multi-Slot Broadcast Message Transmission Example
11
12 2.6.2.1.1.1.2.2 Method 2: Periodic Broadcast Paging
13 According to this method, mobile stations configured to receive broadcast messages monitor
14 a specific broadcast slot (the first slot of a broadcast paging cycle; see 2.6.2.1.1.3.3.). There
15 are two methods of sending broadcast messages used with Periodic Broadcast Paging.
16 If all of the broadcast messages to be transmitted fit within the first slot of a broadcast
17 paging cycle, they may all be transmitted in this broadcast slot. If there is a single
18 broadcast message to be transmitted, it may be transmitted beginning in this broadcast
19 slot.
20 Alternately, one or more broadcast pages may be transmitted in the first slot of a broadcast
21 paging cycle. Each broadcast page is associated with a subsequent broadcast slot. For
22 each broadcast page, an associated broadcast message may be transmitted in the
23 associated subsequent broadcast slot. The broadcast slot for the associated broadcast
24 message is determined according to the position of the broadcast page within the General
25 Page Message transmitted in the first slot of the broadcast paging cycle.
26 Figure 2.6.2.1.1.1.2.2-1 shows an example of Periodic Broadcast Paging when the broadcast
27 index is set to 1. A General Page Message containing three broadcast pages is transmitted
28 in the first slot of the broadcast paging cycle. For each of the three broadcast pages, a Data
29 Burst Message is transmitted in a subsequent slot.
2-48
C.S0005-0-2 v1.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
2
3 Figure 2.6.2.1.1.1.2.2-1. Periodic Broadcast Paging Example
5 2.6.2.1.1.2 Non-Slotted Mode Requirements
6 A mobile station operating in the non-slotted mode shall monitor the Paging Channel at all
7 times. If the mobile station declares a loss of the Paging Channel (see 2.6.2.1.1.4), the
8 mobile station shall enter the System Determination Substate of the Mobile Station
9 Initialization State with a system lost indication (see 2.6.1.1).
10 The mobile station shall operate in the non-slotted mode when PACAs is equal to enabled.
11 When a mobile station monitors the Paging Channel in any state other than the Mobile
12 Station Idle State, it shall operate in the non-slotted mode.
13 The mobile station shall operate in the non-slotted mode when SLOTTEDs is equal to NO.
14 2.6.2.1.1.3 Slotted Mode Requirements
15 The mobile station shall not operate in the slotted mode if any of the of the following
16 conditions are true:
17 • SLOTTEDs is equal to NO,
18 • Bit 5 of the station class mark is set to ‘0’ (see 2.3.3),

19 • PACAs is equal to enabled, or
20 • The mobile station’s configuration parameters are not current (see 2.6.2.2).
21 During operation in the slotted mode, the mobile station shall ensure that its stored
22 configuration parameter values are current (see 2.6.2.2).
23 If the mobile station declares a loss of the Paging Channel (see 2.6.2.1.1.4), the mobile
24 station shall enter the System Determination Substate of the Mobile Station Initialization State
25 with a system lost indication (see 2.6.1.1).
2-49
C.S0005-0-2 v1.0
1 2.6.2.1.1.3.1 Monitoring Assigned Slots
2 If the mobile station does not support Quick Paging Channel operation or if
3 QPCH_SUPPORTEDs = ‘0’, the mobile station shall monitor the Paging Channel in each of
4 its assigned slots.
5 If the mobile station supports Quick Paging Channel operation and if QPCH_SUPPORTEDs
6 = ‘1‘, for each of its assigned slots, the mobile station shall perform the following:
7 • The mobile station should check its assigned paging indicators in the complete
8 Quick Paging Channel slot immediately preceding its assigned Paging Channel slot,
9 as specified in 2.6.2.1.2.1; the mobile station shall monitor the assigned Paging
10 Channel slot if the paging indicators meet the conditions specified in 2.6.2.1.2.2.
11 • If the mobile station does not check its assigned paging indicators, the mobile
12 station shall monitor its assigned Paging Channel slot.
13 If the mobile station monitors an assigned Paging Channel slot, it shall begin monitoring
14 the Paging Channel in time to receive the first bit of the slot. If the mobile station is not
15 configured to receive broadcast addresses, the mobile station shall continue to monitor the
16 Paging Channel until one of the following conditions is satisfied:
17 • Layer 3 receives an address mismatch indication from Layer 2 (see 2.1.2.2.2.4 of

18 TIA/EIA/IS-2000.[4]); or
19 • The mobile station monitors the assigned slot and the slot following the assigned
20 slot, and the mobile station receives at least one valid message (see 2.1.2.4.2 of
21 TIA/EIA/IS-2000-[4]).
22 If the mobile station is configured to receive broadcast addresses, the mobile station shall
23 continue to monitor the Paging Channel until one of the preceding conditions is satisfied
24 and should monitor the Paging Channel until Layer 3 receives a broadcast address
25 mismatch indication from Layer 2 (see 2.1.2.2.2.4 of TIA/EIA/IS-2000.[4]).
26 For each broadcast slot monitored to receive broadcast pages or broadcast messages that is
27 not one of its assigned slots, the mobile station should begin monitoring the Paging
28 Channel in time to receive the first bit of the broadcast slot. The mobile station should
29 continue to monitor the Paging Channel until one of the following conditions is satisfied:
30 • Layer 3 receives a broadcast address mismatch indication from Layer 2; or
31 • The mobile station monitors the Paging Channel to receive all messages beginning in
32 the broadcast slot and in the slot following the broadcast slot, and the mobile
33 station receives at least one valid message (see 2.2.2.3.2 of TIA/EIA/IS-2000-[4]).
34 To determine its assigned slots, the mobile station shall use the hash function specified in
35 2.6.7.1 to select a number, PGSLOT, in the range 0 to 2047 (spanning the maximum slot
36 cycle length, which is 163.84 seconds). The mobile station’s assigned slots shall be those
37 slots in which
38 (t/4 − PGSLOT) mod (16 × T) = 0,
39 where t is the System Time in frames and T is the slot cycle length in units of 1.28 seconds
40 given by
2-50
C.S0005-0-2 v1.0
1 T = 2i,
2 where i is the slot cycle index.
3 2.6.2.1.1.3.2 Determination of the Slot Cycle Index

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

22 Broadcast paging cycle: A broadcast paging cycle is a Paging Channel slot cycle (see
23 2.6.2.1.1.3.1) having a duration of B + 3 slots where:
24 B = 2i × 16, 1 ≤ i ≤ 7
25 where i = BCAST_INDEXs as received in the Extended System Parameters Message, or set

26 by default when the Extended System Parameters Message is not sent.
27 The first slot of each broadcast paging cycle is any Paging Channel slot in which
28 t/4 mod (B + 3) = 0,
29 where t represents system time in frames.
30 2.6.2.1.1.3.4 Monitoring Paging Channel Broadcasts
31 The following requirements apply to mobile stations supporting the reception of broadcast
32 messages.
2-51
C.S0005-0-2 v1.0
1 If BCAST_INDEXs is equal to ‘000’, the mobile station shall monitor only its assigned Paging
2 Channel slots (see 2.6.2.1.1.3.1).
3 If BCAST_INDEXs is not equal to ‘000’, and the mobile station is configured to receive
4 messages addressed to broadcast addresses, the mobile station should also monitor the
5 Paging Channel beginning with the first slot of each broadcast paging cycle (see
6 2.6.2.1.1.3.3).
7 If the mobile station receives a broadcast page containing a burst type and broadcast
8 address that the mobile station has been configured to receive (see 2.6.2.3), the mobile
9 station should monitor the slot in which the corresponding broadcast Paging Channel
10 message will be sent, determined as follows:
11 • The mobile station shall consider a broadcast page to have been received in the
12 paging slot in which the General Page Message containing the broadcast page
13 began.
14 • If BCAST_INDEXs is not equal to ‘000’, the paging slot containing the broadcast
15 page is defined as the reference slot.
16 • Let n represent the ordinal number of the broadcast page relative to other broadcast
17 pages that are contained in the same General Page Message (n = 1, 2, 3,…). The
18 mobile station should monitor the Paging Channel slot that occurs n × 3 paging
19 slots after the reference slot.
20
21 2.6.2.1.1.3.5 Support of Broadcast Delivery Options
22 A mobile station configured to receive broadcast messages shall support reception of

23 broadcast messages transmitted using Multi-Slot Broadcast Message Transmission (see
24 3.6.2.4.1.2.1.1).
25 A mobile station configured to receive broadcast messages shall support reception of

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

2 reserved 2 configuration change
indicators indicators for the first
QPCH;
QPCH;
2 reserved indicators for
QPCHs other than the first
9600bps
paging indicators paging indicators

QPCH;
QPCH;
1
2
3 Figure 2.6.2.1.2.1-1. Quick Paging Channel Timeline

4
2-54
C.S0005-0-2 v1.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.
7 The mobile station’s assigned Quick Paging Channel slots shall be those slots in which
8 ((t+5)/4 − PGSLOT) mod (16 × T) = 0.
9 where t is the System Time in frames, PGSLOT is selected in the range 0 to 2047 by using
10 the hash function specified in 2.6.7.1, and T is the slot cycle length in units of 1.28 seconds
11 such that
12 T = 2i,
13 and i is the slot cycle index.
14 To determine the position of the mobile station’s two assigned paging indicators respective
15 to the beginning of the mobile station’s assigned Quick Paging Channel slot, the mobile
16 station shall use the hash function specified in 2.6.7.1. The R1 and R2 outputs of the
17 hashing algorithm correspond to an indicator bit position relative to the beginning of the
18 Quick Paging Channel slot. The hashing algorithm is so devised that two paging indicators
19 (R1 and R2) for a mobile station will be in the first and third quarter slot or the second and
20 fourth quarter slot.
21 If the mobile station checks assigned paging indicators, the mobile station shall perform the
22 following:
23 • If the mobile station detects that one of the paging indicators is set to “OFF”, the
24 mobile station need not detect another paging indicator.
25 • If the mobile station does not detect that at least one of the paging indicators is set
26 to “OFF”, the mobile station shall receive its assigned Paging Channel slot
27 immediately following its assigned Quick Paging Channel slot.2
28 When performing an idle handoff to a base station whose Paging Channel was previously
29 monitored, a mobile station operating in the slotted mode should monitor one or more
30 configuration change indicators on the first Quick Paging Channel for the new base station
31 if all of the following conditions hold:
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-55
C.S0005-0-2 v1.0
1 • The mobile station supports the Quick Paging Channel,
2 • The mobile station has knowledge that the new base station supports the Quick
3 Paging Channel,
4 • The mobile station has knowledge that the new base station supports configuration
5 change indicators,
6 • The mobile station is not monitoring the Paging Channel, and

7 • No more than T31m seconds have elapsed since the mobile station last received a
8 valid message on the new Paging Channel.
9 Before monitoring a configuration change indicator, the mobile station shall perform the
10 following:
11 • The mobile station shall set ASSIGNED_QPAGECHs equal to QPAGECHs, and
12 • The mobile station shall set QPAGECHs equal to 1.
13 Before monitoring a paging indicator subsequent to monitoring a configuration change

14 indicator, the mobile station shall set QPAGECHs equal to ASSIGNED_QPAGECHs.
15 If the Quick Paging Channel data rate is 2400 bps (indicator rate is 4800 bps), the bit
16 positions of the mobile station’s first pair of configuration change indicators shall be the
17 last two bits in the first 40 ms half of a Quick Paging Channel slot. The bit positions of the
18 mobile station’s second pair of configuration change indicators shall be the last two bits in
19 a Quick Paging Channel slot.
21 positions of the mobile station’s first four configuration change indicators shall be the last
22 four bits in the first 40 ms half of a Quick Paging Channel slot. The bit positions of the
23 mobile station’s second four configuration change indicators shall be the last four bits in a
24 Quick Paging Channel slot.
25 If the mobile station monitors a configuration change indicator and determines that it is set
26 to “OFF”, the mobile station can enter or remain in the slotted mode after an idle handoff
27 (see 2.6.2.1.4.2).
28 2.6.2.1.3 Registration
29 While in the Mobile Station Idle State, the mobile station shall perform the registration
30 procedures specified in 2.6.5.5.2.1.
31 2.6.2.1.4 Idle Handoff
32 2.6.2.1.4.1 Pilot Search
33 An idle handoff occurs when a mobile station has moved from the coverage area of one base
34 station into the coverage area of another base station during the Mobile Station Idle State. If
35 the mobile station detects a Pilot Channel signal from another base station, that is
36 sufficiently stronger than that of the current base station, the mobile station determines
37 that an idle handoff should occur.
2-56
C.S0005-0-2 v1.0
1 Pilot Channels are identified by their offsets relative to the zero offset pilot PN sequence (see
2 3.1.3.2.1). Pilot offsets are grouped into sets describing their status with regard to pilot
3 searching.
4 The following sets of pilot offsets are defined for a mobile station in the Mobile Station Idle
5 State. Each pilot offset is a member of only one set.
6 • Active Set: The pilot offset of the Forward CDMA Channel whose Paging Channel is
7 being monitored.
8 • Neighbor Set: The offsets of the Pilot Channels that are likely candidates for idle
9 handoff. The members of the Neighbor Set are specified in the Neighbor List
10 Message, Extended Neighbor List Message, and the General Neighbor List Message.
11 • Remaining Set: The set of all possible pilot offsets in the current system (integer
12 multiples of PILOT_INCs) on the current CDMA Frequency Assignment, excluding
13 the pilots in the Neighbor Set and the Active Set.
14 • Private Neighbor Set: The offsets of the Pilot Channels for the private systems that
15 are likely candidates for idle handoff. The members of the Private Neighbor Set are
16 specified in the Private Neighbor List Message.
17 The mobile station shall support a Neighbor Set size of at least N8m pilots (see Annex D).
18 In the Mobile Station Idle State, the mobile station shall continuously search for the
19 strongest Pilot Channel signal on the corresponding CDMA Frequency Assignment
20 whenever it monitors the Paging Channel.
21 The mobile station may search other frequencies and band classes. For example, if a pilot
22 in the Neighbor Set or in the Private Neighbor Set is on a different Frequency Assignment
23 than that of the mobile station, this frequency should be included in the search criteria.
24 Search performance criteria are defined in TIA/EIA-98-C[14] and ANSI J-STD-018[10].
25 This search should be governed by the following:
26 • Active Set: The search window size for the pilot in the Active Set shall be the
27 number of PN chips specified in Table 2.6.6.2.1-1 corresponding to SRCH_WIN_As.
28 The mobile station should center the search window for the pilot of the Active Set
29 around the earliest arriving usable multipath component of the pilot. If the mobile
30 station receives a value greater than or equal to 13 for SRCH_WIN_Ar, it may store
31 and use the value 13 in SRCH_WIN_As.
2-57
C.S0005-0-2 v1.0
1 • Neighbor Set: The search window size for each pilot in the Neighbor Set shall be the
2 number of PN chips specified in Table 2.6.6.2.1-1 corresponding to
3 SRCH_WIN_NGHBRs field of the NGHBR_REC for the pilot. The mobile station
4 should center the search window for each pilot in the Neighbor Set around the
5 pilot’s PN sequence offset plus the corresponding SRCH_OFFSET_NGHBRs (see
6 Table 2.6.6.2.1-2) using timing defined by the mobile station’s time reference (see
7 2.1.5 of TIA/EIA/IS-2000-[2]). The mobile station should use the
8 SEARCH_PRIORITY field of the NGHBR_REC for the corresponding pilot to schedule
9 its neighbor search. If ADD_PILOT_REC_INCL field of the NGHBR_REC for the
10 corresponding pilot is equal to ‘1’, the mobile station shall use the information
11 included in the NGHBR_PILOT_REC field for searching the neighbor.
12 If the mobile station supports hopping pilot beacons and the TIMING_INCL field of
13 the NGHBR_REC for the corresponding pilot is equal to ‘1’, then the mobile station
14 shall use the information included in the NGHBR_TX_OFFSET,
15 NGHBR_TX_DURATION, and NGHBR_TX_PERIOD fields of the NGHBR_REC for the
16 corresponding pilot to schedule the time for searching the neighbor.
17 • Remaining Set: The search window size for each pilot in the Remaining Set shall be
18 the number of PN chips specified in Table 2.6.6.2.1-1 corresponding to
19 SRCH_WIN_Rs. The mobile station should center the search window for each pilot
20 in the Remaining Set around the pilot’s PN sequence offset using timing defined by
21 the mobile station’s time reference (see 2.1.5 of TIA/EIA/IS-2000-[2]). The mobile
22 station should only search for Remaining Set pilots whose pilot PN sequence offset
23 indices are equal to integer multiples of PILOT_INCs.
24 • Private Neighbor Set: The search window size for each pilot in the Private Neighbor
25 Set shall be the number of PN chips specified in Table 2.6.6.2.1-1 corresponding to
26 SRCH_WIN_PRI_NGHBRs field of the PRI_NGHBR_REC for the pilot. The mobile
27 station should center the search window for each pilot in the Private Neighbor Set
28 around the pilot’s PN sequence offset using timing defined by the mobile station’s
29 time reference (see 2.1.5 of TIA/EIA/IS-2000-[2]).
30 If the mobile station determines that one of the Neighbor Set, Private Neighbor Set or
31 Remaining Set Pilot Channel signals is sufficiently stronger (see TIA/EIA-98-C[14] and ANSI
32 J-STD-018[10]) than the Pilot Channel of the Active Set, the mobile station should perform
33 an idle handoff as specified in 2.6.2.1.4.2.
34 A mobile station operating in slotted mode, which is successfully demodulating the Paging
35 Channel, should not perform an idle handoff while it is required to monitor its assigned slot
36 (see 2.6.2.1.1.3.1).
37 2.6.2.1.4.2 Idle Handoff Procedures
38 While performing an idle handoff, the mobile station should not begin operating in the non-
39 slotted mode after the idle handoff if all of the following conditions hold:
40 • The mobile station supports the Quick Paging Channel,
41 • The mobile station has knowledge that the new base station supports configuration
2-58
C.S0005-0-2 v1.0
1 change indicators,
2 • The mobile station determines that the Quick Paging Channel configuration change
3 indicator for the new Quick Paging Channel is set to “OFF” (see 2.6.2.1.2.1), and
4 • No more than T31m seconds have elapsed since the mobile station last received a
5 valid message on the new Paging Channel.
6 Otherwise, the mobile station shall operate in the non-slotted mode until the mobile station
7 has received at least one valid configuration message or General Page Message on the new
8 Paging Channel. Following the reception of this message the mobile station may resume
9 slotted mode operation in accordance with 2.6.2.1.1.3. After performing an idle handoff,
10 the mobile station shall discard all unprocessed messages received on the old Paging
11 Channel.
12 If the new base station is listed in NGHBR_REC_LIST for the old base station (see 2.6.2.2.3,
13 2.6.2.2.7, and 2.6.2.1.4.1), the mobile station shall use the corresponding 3-bit
14 NGHBR_CONFIG field to determine the actions required to transition to the new base
15 station. If the new base station is not listed in NGHBR_REC_LIST, the mobile station shall
16 perform the handoff operation using the same procedure as for a pilot in NGHBR_REC_LIST
17 with the NGHBR_CONFIG field set to ‘011’.
18 If the NGHBR_CONFIG field is ‘000’, the mobile station shall perform the following:
19 • The mobile station shall set ACC_MSG_SEQs and CURR_ACC_MSG_SEQ to NULL
20 (see 2.6.2.2) and shall set PILOT_PNs to the pilot offset index of the base station
21 transmitting the new Paging Channel.
22 • If the mobile station has not stored configuration parameters for the new Paging
23 Channel, or if the stored information is not current (see 2.6.2.2), the mobile station
24 shall set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,
25 EXT_NGHBR_LST_MSG_SEQs, GEN_NGHBR_LST_MSG_SEQs, CHAN_LST-
26 _MSG_SEQs, EXT_SYS_PAR_MSG_SEQs, GLOB_SERV_REDIR_MSG_SEQs,
27 EXT_GLOB_SERV_REDIR_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
28 USER_ZONE_ID_MSG_SEQs, and PRI_NGHBR_LST_MSG_SEQs to NULL.
29 • Otherwise (if the stored information for the new Paging Channel is current), the
30 mobile station shall set CONFIG_MSG_SEQs to the stored information for the new
31 Paging Channel and the mobile station shall set NGHBR_REC_LIST to the stored
32 information for the new Paging Channel.
33 • If the associated NGHBR_BANDs or NGHBR_FREQs of the new base station in
34 NGHBR_REC_LIST of the old base station is not equal to CDMABANDs and
35 CDMACHs respectively, the mobile station shall set CDMABANDs to NGHBR_BANDs,
36 CDMACHs to NGHBR_FREQs, and tune to the new CDMA Channel. The mobile
37 station shall begin monitoring the Paging Channel of the new base station, using the
38 same rate, code rate, and code channel.
2-59
C.S0005-0-2 v1.0
1 • If PACAs is equal to enabled, the mobile station shall enter the Update Overhead
2 Information Substate of the System Access State (see 2.6.3) with an origination
3 indication within T33m seconds to re-originate the PACA call using the new base
4 station.
7 and shall set PILOT_PNs to the pilot offset index of the base station transmitting the
8 new Paging Channel.
9 • If the stored information for the Primary Paging Channel or any of the Paging
10 Channels on the associated NGHBR_FREQs of the new base station in
11 NGHBR_REC_LIST of the old base station is current, the mobile station shall
12 perform the following:
13 - The mobile station shall use the hash algorithm specified in 2.6.7.1 to select a
14 new Paging Channel number in the range 1 to PAGE_CHANs, where
15 PAGE_CHANs is the value stored for the Paging Channel whose stored
16 information is current. The mobile station shall store the new Paging Channel
17 number as PAGECHs. The mobile station shall perform the following:
18 + If the mobile station has not stored configuration parameters for the new
19 Paging Channel, or if the stored parameters are not current (see 2.6.2.2), the
20 mobile station shall set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs,
21 NGHBR_LST_MSG_SEQs, EXT_NGHBR_LST_MSG_SEQs,
22 GEN_NGHBR_LST_MSG_SEQs, CHAN_LST_MSG_SEQs,
23 EXT_SYS_PAR_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
24 PRI_NGHBR_LST_MSG_SEQs, and EXT_GLOB_SERV_REDIR_MSG_SEQs,
25 EXT_CHAN_LST_MSG_SEQs, and GLOB_SERV_REDIR_MSG_SEQs to NULL.
26 + Otherwise (if the stored information for the new Paging Channel is current),
27 the mobile station shall set CONFIG_MSG_SEQs to the stored information for
28 the new Paging Channel and set NGHBR_REC_LIST to the stored information
29 for the new Paging Channel.
30 - If the associated NGHBR_BANDs or NGHBR_FREQs of the new base station in

31 NGHBR_REC_LIST of the old base station is not equal to CDMABANDs and
32 CDMACHs respectively, the mobile station shall set CDMABANDs to
33 NGHBR_BANDs, CDMACHs to NGHBR_FREQs, and tune to the new CDMA
34 Channel. The mobile station shall begin monitoring the new Paging Channel of
35 the new base station.
36 • Otherwise, the mobile station shall perform the following:
2-60
C.S0005-0-2 v1.0
1 - The mobile station shall set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs,

4 EXT_SYS_PAR_MSG_SEQs, GLOB_SERV_REDIR_MSG_SEQs,
7 - The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the Primary
8 Paging Channel. If the associated NGHBR_BANDs or NGHBR_FREQs of the new
9 base station in NGHBR_REC_LIST of the old base station is not equal to
10 CDMABANDs and CDMACHs respectively, the mobile station shall set
11 CDMABANDs to NGHBR_BANDs, CDMACHs to NGHBR_FREQs, and tune to the
12 new CDMA Channel. The mobile station shall begin monitoring the Primary
13 Paging Channel of the new base station.
17 station.
20 and shall set PILOT_PNs to the pilot offset index of the base station transmitting the
21 new Paging Channel.
22 • If the stored information for the Primary Paging Channel or any of the Paging
23 Channels on the target frequency or any of the frequencies of the new base station
24 is current, the mobile station shall perform the following:
25 + The mobile station shall use the hash algorithm specified in 2.6.7.1 and the
26 stored value of the number of CDMA channels to determine the new CDMA
27 Channel and shall set FREQ_NEW to this new CDMA Channel. The mobile
29 ο If the stored information for any of the Paging Channels on the CDMA
30 channel specified by FREQ_NEW is current, the mobile station shall
32 - The mobile station shall use the hash algorithm specified in 2.6.7.1 to
33 select a new Paging Channel number in the range 1 to PAGE_CHANs,
34 where PAGE_CHANs is the value stored for the Paging Channel whose
35 stored information is current. The mobile station shall store the new
36 Paging Channel number as PAGECHs. The mobile station shall
2-61
C.S0005-0-2 v1.0
1 + If the mobile station has not stored configuration parameters for

2 the new Paging Channel, or if the stored parameters are not
3 current (see 2.6.2.2), the mobile station shall set CONFIG-
4 _MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,
5 EXT_NGHBR_LST_MSG_SEQs, GEN_NGHBR_LST_MSG_SEQs,
7 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LST_MSG_SEQs, and
8 EXT_GLOB_SERV_REDIR_MSG_SEQs,
9 EXT_CHAN_LST_MSG_SEQs, and
10 GLOB_SERV_REDIR_MSG_SEQs to NULL.
11 + Otherwise (if the stored information for the new Paging Channel is
12 current), the mobile station shall set CONFIG_MSG_SEQs to the
13 stored information for the new Paging Channel and set
14 NGHBR_REC_LIST to the stored information for the new Paging
15 Channel.
16 - If the band class corresponding to FREQ_NEW is not equal to

17 CDMABANDs of the old base station or FREQ_NEW is not equal to
18 CDMACHs of the old base station, the mobile station shall set
19 CDMABANDs to band class corresponding to FREQ_NEW and shall
20 set CDMACHs to FREQ_NEW, and tune to the new CDMA Channel.
21 The mobile station shall begin monitoring the new Paging Channel of
22 the new base station
23 ο If none of the Paging Channel stored information on the CDMA channel

24 specified by FREQ_NEW are current, the mobile station shall perform the
25 following:
26 - The mobile station shall set CONFIG_MSG_SEQs, SYS_PAR-
27 _MSG_SEQs, NGHBR_LST_MSG_SEQs,
30 GLOB_SERV_REDIR_MSG_SEQs,
32 USER_ZONE_ID_MSG_SEQs, and PRI_NGHBR_LST_MSG_SEQs to
33 NULL.
34 - The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the
35 Primary Paging Channel. If the band class corresponding to
36 FREQ_NEW is not equal to CDMABANDs of the old base station or
37 FREQ_NEW is not equal to CDMACHs of the old base station, the
38 mobile station shall set CDMABANDs to band class corresponding to
39 FREQ_NEW and shall set CDMACHs to FREQ_NEW, and tune to the
40 new CDMA Channel. The mobile station shall begin monitoring the
41 Primary Paging Channel of the new base station.
42 • Otherwise, the mobile station shall perform the following:
2-62
C.S0005-0-2 v1.0
1 - The mobile station shall set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs,

7 - The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the Primary
8 Paging Channel. If the associated NGHBR_BANDs or NGHBR_FREQs of the new
9 base station in NGHBR_REC_LIST of the old base station is not equal to
10 CDMABANDs and CDMACHs of the old base station respectively, the mobile
11 station shall set CDMABANDs to NGHBR_BANDs, and CDMACHs to
12 NGHBR_FREQs; Otherwise, the mobile station shall set CDMACHs as follows:
13 + If the Extended CDMA Channel List Message is being sent on the old base
14 station, set CDMACHs to the first CDMA Channel given in the Extended
15 CDMA Channel List Message for the old base station.
16 + Otherwise, set CDMACHs to the first CDMA Channel given in the CDMA
17 Channel List Message for the old base station.
18 Then the mobile station shall tune to the new CDMA channel and begin
19 monitoring the Primary Paging Channel of the new base station.
23 station.
25 • Enter the System Determination Substate of the Mobile Station Initialization State with
26 a new system indication (see 2.6.1.1).
27 2.6.2.1.5 Reserved
28 2.6.2.1.6 System Reselection Procedures
29 If the mobile station supports more than one operating mode or the Remaining
30 Set/Neighbor Set contains pilots on frequencies different from the current frequency, the
31 mobile station shall enter the System Determination Substate of the Mobile Station
32 Initialization State with a system reselection indication (see 2.6.1.1) if the following are true:
33 • RESELECT_INCLUDEDs is equal to ‘1’;
34 • The following inequality is satisfied:

35 20 × log10 (Ec/Io) > EC_IO_THRESHs
36 where Ec/Io is the measured Ec/Io of the active pilot; and
2-63
C.S0005-0-2 v1.0
1 • The following inequality is satisfied:

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

6 Upon expiration of the slotted TMS Slotted timer, the mobile station shall disable the timer
7 and set SLOTTEDs to YES.
8 2.6.2.2 Response to Overhead Information Operation
9 The overhead messages on the Paging Channel are:

10 • System Parameters Message
11 • Access Parameters Message
12 • Neighbor List Message
13 • CDMA Channel List Message
14 • Extended System Parameters Message
15 • Global Service Redirection Message
16 • Extended Neighbor List Message
17 • General Neighbor List Message
18 • User Zone Identification Message
19 • Private Neighbor List Message
20 • Extended Global Service Redirection Message
21 • Extended CDMA Channel List Message
22 The Response to Overhead Information Operation is performed whenever the mobile station
23 receives an overhead message. The mobile station updates internally stored information
24 from the received message’s data fields.
25 Configuration parameters and access parameters are received in the configuration

26 messages and the Access Parameters Message. The configuration messages are:
29 • CDMA Channel List Message
30 • Extended System Parameters Message
31 • Global Service Redirection Message
2-64
C.S0005-0-2 v1.0
3 • Extended Global Service Redirection Message
4 • Extended CDMA Channel List Message
5 Associated with the set of configuration messages sent on each Paging Channel is a
6 configuration message sequence number (CONFIG_MSG_SEQ). When the contents of one
7 or more of the configuration messages change, the configuration message sequence number
8 is incremented. For each of the configuration messages received, the mobile station stores
9 the configuration message sequence number contained in the configuration message
10 (SYS_PAR_MSG_SEQs, NGHBR_LIST_MSG_SEQs, EXT_NGHBR_LST_MSG_SEQs,
11 GEN_NGHBR_LST_MSG_SEQs, CHAN_LIST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs,
12 GLOB_SERV_REDIR_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
13 EXT_CHAN_LST_MSG_SEQs, EXT_GLOB_SERV_REDIR_MSG_SEQs, or
14 PRI_NGHBR_LST_MSG_-SEQs). The mobile station also stores the most recently received
15 configuration message sequence number (CONFIG_MSG_SEQs) contained in any message
16 (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,
17 2.6.2.2.10, 2.6.2.2.11, 2.6.2.2.12 and 2.6.2.3). The mobile station examines the stored
18 values of the configuration message sequence numbers to determine whether the
19 configuration parameters stored by the mobile station are current.
20 The field EXT_SYS_PARAMETER in the System Parameters Message, when set equal to ‘0’,
21 indicates that the base station is not sending the Extended System Parameters Message.
22 When the mobile station receives the System Parameters Message with the
23 EXT_SYS_PARAMETER field set equal to ‘0’, the mobile station shall set
24 EXT_SYS_PAR_MSG_SEQs to CONFIG_MSG_SEQs to indicate that the Extended System
25 Parameters Message is current.
26 The field GEN_NGBR_LST in the System Parameters Message, when set equal to ‘0’,
27 indicates that the base station is not sending the General Neighbor List Message. When the
28 mobile station receives the System Parameters Message with the GEN_NGBR_LST field set
29 equal to ‘0’, the mobile station shall set the GEN_NGBR_LST_MSG_SEQs to
30 CONFIG_MSG_SEQs to indicate that the General Neighbor List Message is current.
31 The field EXT_NGBR_LST in the System Parameters Message, when set equal to ‘0’,
32 indicates that the base station is not sending the Extended Neighbor List Message. When
33 the mobile station receives the System Parameters Message with the EXT_NGBR_LST field
34 set equal to ‘0’, the mobile station shall set EXT_NGBR_LST_SEQs to CONFIG_MSG_SEQs
35 to indicate that the Extended Neighbor List Message is current.
36 The field GLOBAL_REDIRECT in the System Parameters Message, when set equal to ‘0’,
37 indicates that the base station is not sending the Global Service Redirection Message. When
38 the mobile station receives the System Parameters Message with the GLOBAL_REDIRECT
39 field set equal to ‘0’, the mobile station shall set GLOB_SERV_REDIR_MSG_SEQs to
40 CONFIG_MSG_SEQs to indicate that the Global Service Redirection Message is current.
41 The field EXT_GLOBAL_REDIRECT in the System Parameters Message, when set equal to
42 ‘0’, indicates that the base station is not sending the Extended Global Service Redirection
2-65
C.S0005-0-2 v1.0
1 Message. When the mobile station receives the System Parameters Message with the
2 EXT_GLOBAL_REDIRECT field set equal to ‘0’, the mobile station shall set
3 EXT_GLOB_SERV_REDIR_MSG_SEQs to CONFIG_MSG_SEQs to indicate that the Extended
4 Global Service Redirection Message is current.
5 The field USER_ZONE_ID in the System Parameters Message, when set equal to ‘0’,
6 indicates that the base station is not sending the User Zone Identification Message. When
7 the mobile station receives the System Parameters Message with the USER_ZONE_ID field
8 set equal to ‘0’, the mobile station shall set USER_ZONE_ID_MSG_SEQs to
9 CONFIG_MSG_SEQs to indicate that the User Zone Identification Message is current.
10 The field PRI_NGHBR_LIST in the System Parameters Message, when set equal to ‘0’,
11 indicates that the base station is not sending the Private Neighbor List Message. When the
12 mobile station receives the System Parameters Message with the PRI_NGHBR_LIST field set
13 equal to ‘0’, the mobile station shall set PRI_NGHBR_LIST_MSG_SEQs to
14 CONFIG_MSG_SEQs to indicate that the Private Neighbor List Message is current.
15 The configuration message sequence number is also included in the General Page Message.
16 This allows the mobile station to determine whether the stored configuration parameters
17 are current without waiting for a configuration message.
18 Access Parameters Messages are independently sequence-numbered by the ACC_MSG_SEQ
19 field. The mobile station stores the most recently received Access Parameters Message
20 sequence number (ACC_MSG_SEQs).
21 Paging Channels shall be considered different if they are transmitted by different base
22 stations, if they are transmitted on different code channels, or if they are transmitted on
23 different CDMA Channels. Configuration and access parameters from one Paging Channel
24 shall not be used while monitoring a different Paging Channel except for registration and
25 authentication parameters while the mobile station is performing an access probe handoff
26 or access handoff. The mobile station shall ignore any overhead message whose PILOT_PNr
27 field is not equal to the pilot offset index (PILOT_PNs) of the base station whose Paging
28 Channel is being monitored.
29 The mobile station may store the configuration parameters from Paging Channels it has
30 recently monitored. When a mobile station starts monitoring a Paging Channel that it has
31 recently monitored, the mobile station can determine whether the stored parameters are
32 current by examining the CONFIG_MSG_SEQs in a configuration message or a General
33 Page Message.
34 The mobile station shall use a special value, NULL, to be stored in place of sequence
35 numbers for messages that have not been received or are marked as not current. The
36 special value NULL shall be unequal to any valid message sequence number.
37 The mobile station shall consider the stored configuration parameters to be current only if
38 all of the following conditions are true:
2-66
C.S0005-0-2 v1.0
1 • All stored configuration message sequence numbers (SYS_PAR_MSG_SEQs,

2 NGHBR_LIST_MSG_SEQs, EXT_NGHBR_LIST_MSG_SEQs, CHAN_LIST_MSG_SEQs,
3 EXT_SYS_PAR_MSG_SEQs, GEN_NGHBR_LIST_MSG_SEQs,
4 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LST_MSG_SEQs,
5 EXT_CHAN_LST_MSG_SEQs, EXT_GLOB_SERV_REDIR_MSG_SEQs and
6 GLOB_SERV_REDIR_MSG_SEQs) are equal to CONFIG_MSG_SEQs; and
7 • CONFIG_MSG_SEQs is not equal to NULL; and
8 • No more than T31m seconds (see Annex D) have elapsed since the mobile station last
9 received a valid message on the Paging Channel for which the parameters were
10 stored.
11 If the configuration parameters are not current, the mobile station shall process the stored
12 parameters upon receipt of the configuration messages as described in 2.6.2.2.1, 2.6.2.2.3,
13 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,
14 2.6.2.2.12.
15 2.6.2.2.1 System Parameters Message

16 Whenever a System Parameters Message is received on the Paging Channel, the
17 configuration message sequence number, CONFIG_MSG_SEQr, shall be compared to that
18 stored in SYS_PAR_MSG_SEQs. If the comparison results in a match, the mobile station
19 may ignore the message. If the comparison results in a mismatch, then the mobile station
20 shall process the remaining fields in the message as described in 2.6.2.2.1.1, 2.6.2.2.1.2,
21 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.
22 If PAGE_CHAN, REG_PRD, BASE_LAT, BASE_LONG, or PWR_REP_THRESH are not within

23 the valid ranges specified in 3.7.2.3.2.1, then the mobile station shall ignore the System
24 Parameters Message that contains them.
25 If BAND_CLASS is equal to ‘00001’ and if either EXT_SYS_PARAMETERSr is not equal to ‘1’
26 or EXT_NGHBR_LSTr is not equal to ‘1’, or both, the mobile station shall ignore the System
27 Parameters Message containing these fields.
28 2.6.2.2.1.1 Stored Parameters
29 The mobile station shall store the following parameters:
30 • Configuration message sequence number

31 (CONFIG_MSG_SEQs = CONFIG_MSG_SEQr,
32 SYS_PAR_MSG_SEQs = CONFIG_MSG_SEQr)
33 • Base station identification (BASE_IDs = BASE_IDr)
34 • Base station class (BASE_CLASSs = BASE_CLASSr)
35 • Maximum slot cycle index

36 (MAX_SLOT_CYCLE_INDEXs = MAX_SLOT_CYCLE_INDEXr)
37 • Home registration indicator (HOME_REGs = HOME_REGr)
38 • SID roamer registration indicator (FOR_SID_REGs = FOR_SID_REGr)
2-67
C.S0005-0-2 v1.0
1 • NID roamer registration indicator (FOR_NID_REGs = FOR_NID_REGr)
2 • Power-up registration indicator (POWER_UP_REGs = POWER_UP_REGr)
3 • Power-down registration indicator (POWER_DOWN_REGs = POWER_DOWN_REGr)
4 • Parameter-change registration indicator (PARAMETER_REGs = PARAMETER_REGr)
5 • Search window size for the Active Set and Candidate Set
6 (SRCH_WIN_As = SRCH_WIN_Ar)
7 • Search window size for the Neighbor Set (SRCH_WIN_Ns = SRCH_WIN_Nr)
8 • Search window size for the Remaining Set (SRCH_WIN_Rs = SRCH_WIN_Rr)
9 • Maximum age for retention of Neighbor Set members

10 (NGHBR_MAX_AGEs = NGHBR_MAX_AGEr)
11 • Power control reporting threshold (PWR_REP_THRESHs = PWR_REP_THRESHr)
12 • Power control reporting frame count (PWR_REP_FRAMESs = PWR_REP_FRAMESr)
13 • Threshold report mode indicator

14 (PWR_THRESH_ENABLEs = PWR_THRESH_ENABLEr)
15 • Periodic report mode indicator (PWR_PERIOD_ENABLEs = PWR_PERIOD_ENABLEr).
16 • Power report delay (PWR_REP_DELAYs = PWR_REP_DELAYr)
17 • Pilot detection threshold (T_ADDs = T_ADDr)
18 • Pilot drop threshold (T_DROPs = T_DROPr)
19 • Active Set versus Candidate Set comparison threshold (T_COMPs = T_COMPr)
20 • Drop timer value (T_TDROPs = T_TDROPr)
21 • Extended System Parameters Message sent

22 (EXT_SYS_PARAMETERs = EXT_SYS_PARAMETERr)
23 • Global Service Redirection Message sent

24 (GLOBAL_REDIRECTs = GLOBAL_REDIRECTr)
25 • Extended Global Service Redirection Message sent

26 (EXT_GLOBAL_REDIRECTs = EXT_GLOBAL_REDIRECTr)
27 • Extended Neighbor List Message sent

28 (EXT_NGHBR_LSTs = EXT_NGHBR_LSTr)
29 • General Neighbor List Message sent

30 (GEN_NGHBR_LSTs = GEN_NGHBR_LSTr)
31 • User Zone Identification Message sent

32 (USER_ZONE_IDs = USER_ZONE_IDr)
33 • Private Neighbor List Message sent

34 (PRI_NGHBR_LSTs = PRI_NGHBR_LSTr)
2-68
C.S0005-0-2 v1.0
1 • Extended CDMA Channel List Message sent

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

21 to IMSI_M_S1p and IMSI_O_S2s to IMSI_M_S2p), MCC_Os to MCC_Mp,
22 IMSI_O_11_12s to IMSI_M_11_12p, and IMSI_O_ADDR_NUMs to
23 IMSI_M_ADDR_NUMp,
24 • Set RESELECT_INCLUDEDs to ‘0’,
25 • For Band Class 0, if the mobile station determines it is operating in Korea, set
26 P_REVs to ‘00000010’; otherwise, set P_REVs to ‘00000011’. For Band Class 3, set
27 P_REVs to ‘00000011’. For Band Class 1 and Band Class 4, set P_REVs to
28 ‘00000001’, and
29 • Set P_REV_IN_USEs to the lesser value of P_REVs and MOB_P_REVp of the current
30 band class.
31 If EXT_CHAN_LISTs is equal to ‘0’, then the mobile station shall set
32 EXT_CHAN_LST_MSG_SEQs to CONFIG_MSG_SEQs.
33 If GLOBAL_REDIRECTs is equal to ‘0’, then the mobile station shall set GLOB_SERV-
34 _REDIR_MSG_SEQs to CONFIG_MSG_SEQs.
35 If EXT_GLOBAL_REDIRECTs is equal to ‘0’, then the mobile station shall set

36 EXT_GLOB_SERV_REDIR_MSG_SEQs to CONFIG_MSG_SEQs.
2-69
C.S0005-0-2 v1.0
1 If EXT_NGHBR_LSTs is equal to ‘0’, then the mobile station shall set

2 EXT_NGHBR_LST_MSG_SEQs to CONFIG_MSG_SEQs.
3 If GEN_NGHBR_LSTs is equal to ‘0’, then the mobile station shall perform the following:
4 • Set GEN_NGHBR_LST_MSG_SEQs to CONFIG_MSG_SEQs.
5 • Set the SRCH_WIN_NGHBR field of NGHBR_REC to SRCH_WIN_Ns for all entries.
6 • Set the SRCH_OFFSET_NGHBR field of NGHBR_REC to ‘000’ for all entries.
7 • Set the TIMING_INCL field of NGHBR_REC to ‘0’ for all entries.

8 • Set NUM_ANALOG_NGHBRs to ‘000’ and ANALOG_NGHBR_LIST to NULL.
9 • If EXT_NGHBR_LSTs is equal to ‘0’:
10 – Set the SEARCH_PRIORITY field of the NGHBR_REC to ‘10’ (high) for all entries.
11 – Set the NGHBR_BAND field of the NGHBR_REC to CDMABANDs for all entries.
12 – Set the NGHBR_FREQ field of the NGHBR_REC to CDMACHs for all entries.
13 If GEN_NGHBR_LSTs is equal to ‘1’, GEN_NGHBR_LST_MSG_SEQs is equal to

14 CONFIG_MSG_SEQs, and SETTING_SEARCH_WIN is equal to ‘1’, the mobile station shall
16 • Set the SRCH_WIN_NGHBR field of each NGHBR_REC to SEARCH_WIN_Ns for all
17 NGHBR_SET_SIZEs entries.
18 • Set SETTING_SEARCH_WIN to ‘0’.

19 If USER_ZONE_IDs is equal to ‘0’, then the mobile station shall perform the following:
20 • Set USER_ZONE_ID_MSG_SEQs to CONFIG_MSG_SEQs.
21 • Set the UZID field of the UZ_REC to ‘0000000000000000’ for all entries.
22 • Set the UZ_REV field of the UZ_REC to ‘0000’ for all entries.
23 • Set the TEMP_SUB field of the UZ_REC to ‘0’ for all entries.
24 If USER_ZONE_IDs is equal to ‘1’ and the mobile station does not support Tiered Services,
25 then the mobile station shall set USER_ZONE_ID_MSG_SEQs to CONFIG_MSG_SEQs.
26 If PRI_NGHBR_LISTs is equal to ‘0’, then the mobile station shall set

27 PRI_NGHBR_LIST_MSG_SEQs to CONFIG_MSG_SEQs.
28 If PRI_NGHBR_LISTs is equal to ‘1’ and the mobile station does not support Tiered Services,
29 then the mobile station shall set PRI_NGHBR_LIST_MSG_SEQs to CONFIG_MSG_SEQs.
30 The mobile station shall ignore any fields at the end of the System Parameters Message that
31 are not defined according to the protocol revision level (MOB_P_REVp of the current band
32 class) being used by the mobile station.
33 2.6.2.2.1.2 Paging Channel Assignment Change

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

14 If the RESCANr field in the System Parameters Message equals ‘1’, the mobile station shall
15 enter the System Determination Substate of the Mobile Station Initialization State with a
16 rescan indication (see 2.6.1.1).
17 2.6.2.2.1.4 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.1.5 Registration
21 The mobile station shall update stored variables and perform other registration procedures
22 as specified in 2.6.5.5.2.2.
23 2.6.2.2.1.6 Slot Cycle Index

24 The mobile station shall set SLOT_CYCLE_INDEXs to the smaller of: the preferred slot cycle
25 index SLOT_CYCLE_INDEXp and the maximum slot cycle index
26 MAX_SLOT_CYCLE_INDEXs. If the mobile station is operating in the slotted mode, it shall
27 set its slot cycle length as described in 2.6.2.1.1.3.
28 2.6.2.2.1.7 PACA Disable for SID Change

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

33 The mobile station shall set RETRY_DELAYs[RETRY_TYPE] to 0 when the mobile station
34 determines that the Packet Zone Identification or the System Identification/Network
35 Identification (SID/NID pair) has been changed, where RETRY_TYPE is equal to ‘001’, ‘010’,
36 or ‘011’.
2-71
C.S0005-0-2 v1.0
1 2.6.2.2.2 Access Parameters Message
2 Whenever an Access Parameters Message is received on the Paging Channel, the sequence
3 number, ACC_MSG_SEQr, shall be compared to ACC_MSG_SEQs. If the comparison
4 results in a match, the mobile station may ignore the message. If the comparison results in
5 a mismatch, then the mobile station shall process the remaining fields in the message as
6 follows.
7 If PROBE_PN_RAN, MAX_REQ_SEQ, or MAX_RSP_SEQ are not within the valid ranges

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

11 • Access Parameters Message sequence number (ACC_MSG_SEQs = ACC_MSG_SEQr)
12 • Number of Access Channels (ACC_CHANs = ACC_CHANr)
13 • Nominal transmit power offset (NOM_PWRs = NOM_PWRr)
14 • Initial power offset for access (INIT_PWRs = INIT_PWRr)
15 • Power increment (PWR_STEPs = PWR_STEPr)
16 • Number of access probes (NUM_STEPs = NUM_STEPr)
17 • Maximum Access Channel message capsule size (MAX_CAP_SZs = MAX_CAP_SZr)
18 • Access Channel preamble length (PAM_SZs = PAM_SZr)
19 • Persistence modifier for Access Channel attempts for registrations which are not
20 responses to the Registration Request Order (REG_PSISTs = REG_PSISTr)
21 • Persistence modifier for Access Channel attempts for message transmissions

22 (MSG_PSISTs = MSG_PSISTr)
23 • Time randomization for Access Channel probes

24 (PROBE_PN_RANs = PROBE_PN_RANr)
25 • Acknowledgment timeout (ACC_TMOs = ACC_TMOr)
26 • Access Channel probe backoff range (PROBE_BKOFFs = PROBE_BKOFFr)
27 • Access Channel probe sequence backoff range (BKOFFs = BKOFFr)
28 • Maximum number of probe sequences for an Access Channel request

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

31 (MAX_RSP_SEQs = MAX_RSP_SEQr)
32 • If CDMABANDs is equal to ‘0’, the mobile station shall set extended nominal
33 transmit power NOM_PWR_EXTs to ‘0’; otherwise, the mobile station shall store
34 extended nominal transmit power (NOM_PWR_EXTs = NOM_PWR_EXTr).
35 • IC threshold (IC_THRESHs = -7)
2-72
C.S0005-0-2 v1.0
1 The mobile station shall also store the following parameters if the mobile station is not in
2 the Origination Attempt Substate or Page Response Substate:
3 • Authentication mode (if AUTHr is equal to ‘00’ or ‘01’, then AUTHs = AUTHr;
4 otherwise AUTHs = ‘01’)
5 • Random challenge value (RANDs = RANDr)
6 The mobile station shall ignore any fields at the end of the Access Parameters Message
7 which are not defined according to the protocol revision level (MOB_P_REVp of the current
8 band class) being used by the mobile station.
9 The mobile station shall store the persistence parameter number according to the following
10 rule: If the mobile station’s access overload class is in the range 0-9, set PSISTs equal to
11 PSIST(0-9)r; otherwise set PSISTs equal to PSIST(n)r, where n is equal to the mobile station
12 access overload class.
13 The mobile station shall set CURR_ACC_MSG_SEQ to ACC_MSG_SEQs.
14 2.6.2.2.3 Neighbor List Message

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

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

36 shall perform the following:
37 • Set the SEARCH_PRIORITY field of the NGHBR_REC to ‘10’ (high) for all
2-73
C.S0005-0-2 v1.0
1 • Set the NGHBR_BAND field of NGHBR_REC to CDMABANDs for all

3 • Set the NGHBR_FREQ field of NGHBR_REC to CDMACHs for all NGHBR_SET_SIZEs

4 entries.
5 • Set the SRCH_WIN_NGHBR field of NGHBR_REC to SRCH_WIN_Ns for all

8 • Set NUM_ANALOG_NGHBRs to ‘000’ and set ANALOG_NGHBR_LIST to NULL.
9 The mobile station shall set the ACCESS_ENTRY_HO field of the NGHBR_REC to ‘0’ for all
10 NGHBR_SET_SIZEs entries if any of the following conditions are met:
11 • EXT_SYS_PARAMETERs is equal to ‘0’,
12 • NGHBR_SET_ENTRY_INFOs is equal to ‘0’, or
13 • EXT_SYS_PAR_MSG_SEQs is not equal to CONFIG_MSG_SEQs.
14 The mobile station shall set the ACCESS_HO_ALLOWED field of the NGHBR_REC to ‘0’ for
15 all NGHBR_SET_SIZEs entries if any of the following conditions are met:
17 • NGHBR_SET_ACCESS_INFOs is equal to ‘0’, or
19 The mobile station shall update the idle handoff Neighbor Set (see 2.6.2.1.4) so that it
20 consists only of pilot offsets listed in the Neighbor List Message. If the Neighbor List
21 Message contains more pilot offsets than the mobile station can store, the mobile station
22 shall store the pilot offsets beginning at the start of the Neighbor List Message, up to the
23 limits of the mobile station’s Neighbor Set storage capacity.
24 2.6.2.2.4 CDMA Channel List Message

25 Whenever a CDMA Channel List Message is received on the Paging Channel, the
27 stored in CHAN_LST_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 follows.

33 CHAN_LST_MSG_SEQs = CONFIG_MSG_SEQr)
34 The mobile station shall perform the following:

35 • If both SYS_PAR_MSG_SEQs and EXT_SYS_PAR_MSG_SEQs are current,
36 – If EXT_CHAN_LISTs is equal to ‘1’, the mobile station shall ignore this message.
2-74
C.S0005-0-2 v1.0
1 – If EXT_CHAN_LISTs is equal to ‘0’, the mobile station shall process this message
2 as described below.
3 • Otherwise, the mobile station shall process this message after SYS_PAR_MSG_SEQs
4 and EXT_SYS_PAR_MSG_SEQs become current.
5 The mobile station shall use the hash algorithm specified in 2.6.7.1 and the number of
6 channels listed in the CDMA Channel List Message to determine the CDMA Channel
7 (Frequency Assignment) for its Paging Channel.
8 If the CDMA Frequency Assignment has changed (the computed CDMA Channel is different
9 from CDMACHs), the mobile station shall perform the following actions:
10 • If the stored configuration parameters is not current (see 2.6.2.2) for the
11 corresponding base station and frequency assignment, the mobile station shall
12 perform the following actions:
13 – Set CDMACHs to the new CDMA Channel.
14 – Set PAGE_CHANs to ‘1’.
15 – Set PAGECHs to the Primary Paging Channel.
16 – Set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,

17 CHAN_LST_MSG_SEQs, EXT_NGHBR_LST_MSG_SEQs,
18 GEN_NGHBR_LST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs,
19 GLOB_SERV_REDIR_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
20 PRI_NGHBR_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
21 EXT_GLOB_SERV_REDIR_MSG_SEQs, and ACC_MSG_SEQs to NULL.
22 – Tune to the new CDMA Channel.
23 • Otherwise, the mobile station shall perform the following actions:

25 – The mobile station shall use the hash algorithm specified in 2.6.7.1 to select
26 a new Paging Channel number in the range 1 to PAGE_CHANs, where
28 information is current. The mobile station shall store the new Paging
29 Channel number as PAGECHs.
30 – Tune to the new CDMA Channel and shall begin monitoring the new Paging
31 Channel.
32 2.6.2.2.5 Extended System Parameters Message

33 Whenever an Extended System Parameters Message is received on the Paging Channel, the
35 stored in EXT_SYS_PAR_MSG_SEQs. If the comparison results in a match, the mobile
36 station may ignore the message. If the comparison results in a mismatch, then the mobile
37 station shall process the remaining fields in the message as follows.
2-75
C.S0005-0-2 v1.0
1 If the protocol revision level supported by the mobile station (MOB_P_REVp) is less than the
2 minimum protocol revision level supported by the base station (MIN_P_REVr), the mobile
3 station shall enter the System Determination Substate of the Mobile Station Initialization State
4 with a protocol mismatch indication (see 2.6.1.1). Otherwise, the mobile station shall store
5 the following parameters:

8 EXT_SYS_PAR_MSG_SEQs= CONFIG_MSG_SEQr)
9 • Preferred Access Channel MSID type (PREF_MSID_TYPEs = PREF_MSID_TYPEr)
10 • Broadcast slot cycle index (BCAST_INDEXs = BCAST_INDEXr)
11 • The mobile station shall set its operational IMSI, IMSI_O, as follows:
12 – If IMSI_T_SUPPORTEDr is equal to ‘0’, the mobile station shall set IMSI_O to
13 IMSI_Mp.
14 – If IMSI_T_SUPPORTEDr is equal to ‘1’ and the mobile station’s IMSI_Tp has been
15 programmed, the mobile station shall set IMSI_O to IMSI_Tp.
16 – If IMSI_T_SUPPORTEDr is equal to ‘1’ and the mobile station’s IMSI_Tp has not
17 been programmed, the mobile station shall set IMSI_O to IMSI_Mp.
18 – If IMSI_O has been changed, the mobile station shall set SYS_PAR_MSG_SEQs
19 and CHAN_LST_MSG_SEQs and EXT_CHAN_LST_MSG_SEQs to NULL and set
20 PAGE_CHANs to ‘1’.
21 • If MCCr = ‘1111111111’ and IMSI_11_12r = ‘1111111’, the mobile station shall set
22 the IMSI_O to IMSI_Mp and store:
23 – Mobile Country Code (MCCs = MCC_Mp) and
24 – IMSI 11th and 12th digits (IMSI_11_12s = IMSI_M_11_12p);
25 otherwise, the mobile station shall store:

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

29 – IMSI_O_Ss to IMSI_M_Sp (i.e., IMSI_O_S1s to IMSI_M_S1p and IMSI_O_S2s to
30 IMSI_M_S2p)
31 – IMSI_O_11_12s to IMSI_M_11_12p
32 – MCC_Os to MCC_Mp
33 – IMSI_O_ADDR_NUMs to IMSI_M_ADDR_NUMp
34 • If IMSI_O is set to the IMSI_T, the mobile station shall set:

35 – IMSI_O_Ss to IMSI_T_Sp (i.e., IMSI_O_S1s to IMSI_T_S1p and IMSI_O_S2s to
36 IMSI_T_S2p).
2-76
C.S0005-0-2 v1.0
1 – IMSI_O_11_12s to IMSI_T_11_12p
2 – MCC_Os to MCC_Tp
3 – IMSI_O_ADDR_NUMs to IMSI_T_ADDR_NUMp
4 • Protocol revision level (P_REVs = P_REVr) if included in the message; otherwise, set
5 P_REVs as follows:
6 – For Band Class 0, if the mobile station determines it is operating in Korea, set
7 P_REVs to ‘00000010’; otherwise, set P_REVs to ‘00000011’.
8 – For Band Class 3, set P_REVs to ‘00000011’.
9 – For Band Class 1 and Band Class 4, set P_REVs to ‘00000001’.
10 • Minimum protocol revision level (MIN_P_REVs = MIN_P_REVr) if included in the

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

17 in the message; otherwise, SOFT_SLOPEs = ‘000000’.
18 • Intercept of the handoff add criterion (ADD_INTERCEPTs = ADD_INTERCEPTr)
19 • Intercept of the handoff drop criterion (DROP_INTERCEPTs = DROP_INTERCEPTr)
20 • Delete foreign TMSI (DELETE_FOR_TMSIs = DELETE_FOR_TMSIr)
21 • Use TMSI (USE_TMSIs = USE_TMSIr)
22 • TMSI zone length (TMSI_ZONE_LENs = TMSI_ZONE_LENr)
23 • TMSI zone number (TMSI_ZONEs = TMSI_ZONEr)
24 • Maximum number of alternative service options (MAX_NUM_ALT_SOs =

25 MAX_NUM_ALT_SOr) if included in the message; otherwise, MAX_NUM_ALT_SOs =
26 ‘000’.
27 • System reselection indicator (RESELECT_INCLUDEDs = RESELECT_INCLUDEDr) if
28 included in the message; otherwise, RESELECT_INCLUDEDs = ‘0’.
29 • Pilot reporting indicator (PILOT_REPORTs = PILOT_REPORTr)
30 • Neighbor Set access entry handoff information indicator

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

34 NGHBR_SET_ACCESS_INFOr) if included in the message; otherwise,
35 NGHBR_SET_ACCESS_INFOs = ‘0’.
36 • Short Data Burst supported indicator (SDB_SUPPORTEDs = SDB_SUPPORTEDr)
2-77
C.S0005-0-2 v1.0
1 • Nominal reverse traffic channel output power offset relative to Reverse Pilot Channel
2 power (RLGAIN_TRAFFIC_PILOTs = RLGAIN_TRAFFIC_PILOTr)
3 • Reverse Power Control Delay (REV_PWR_CNTL_DELAYs = REV_PWR_CNTL_DELAYr)

4 if included
5 • Broadcast GPS Assist Indicator (BROADCAST_GPS_ASSTs =
6 BROADCAST_GPS_ASSTr)
7 If P_REV_IN_USEs has been changed, the mobile station shall set ACC_MSG_SEQs,
8 CURR_ACC_MSG_SEQ, SYS_PAR_MSG_SEQs, EXT_NGHBR_LST_MSG_SEQs,
9 GEN_NGHBR_LST_MSG_SEQs, and GLOB_SERV_REDIR_MSG_SEQs to NULL.
10 If NGHBR_SET_ENTRY_INFO is equal to ‘1’, the mobile station shall store the access entry
11 handoff in order and message processing operation indicator (ACC_ENT_HO_ORDERs =
12 ACC_ENT_HO_ORDERr).
13 If the mobile station supports packet data service options and the PACKET_ZONE_ID field is
14 included in the message, the mobile station shall store the packet data services zone
15 identifier (PACKET_ZONE_IDs = PACKET_ZONE_IDr); otherwise, the mobile station shall set
16 PACKET_ZONE_IDs to ‘00000000’.
17 If RESELECT_INCLUDEDs is equal to ‘1’, the mobile station shall store:
18 • Pilot power threshold (EC_THRESHs = EC_THRESHr)
19 • Pilot Ec/Io threshold (EC_IO_THRESHs = EC_IO_THRESHr)
20 If NGHBR_SET_ACCESS_INFOs is equal to ‘1’, the mobile station shall store:
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 NGHBR_SET_ENTRY_INFOs or NGHBR_SET_ACCESS_INFOs is equal to ‘1’, the mobile

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

35 ACCESS_ENTRY_HO, the mobile station shall set the ACCESS_ENTRY_HO field of
36 NGHBR_REC[i] to ‘0’.
2-78
C.S0005-0-2 v1.0
1 If NGHBR_SET_ENTRY_INFOs is equal to ‘1’, then for all NGHBR_SET_SIZEs occurrences of

2 ACCESS_ENTRY_HO, the mobile station shall set the ACCESS_ENTRY_HO field of
3 NGHBR_REC[i] to the ith occurrence of ACCESS_ENTRY_HOr.
4 If NGHBR_SET_ACCESS_INFOs is equal to ‘0’, then for all NGHBR_SET_SIZEs occurrences

5 of ACCESS_HO_ALLOWED, the mobile station shall set the ACCESS_HO_ALLOWED field of
6 NGHBR_REC[i] to ‘0’.
7 If NGHBR_SET_ACCESS_INFOs is equal to ‘1’, then for all NGHBR_SET_SIZEs occurrences
8 of ACCESS_HO_ALLOWED, the mobile station shall set the ACCESS_HO_ALLOWED field of
9 NGHBR_REC[i] to the ith occurrence of ACCESS_HO_ALLOWEDr.
10 The mobile station shall set all bits of TMSI_CODEs-p to ‘1’ if all of the following conditions
11 are met:
12 • The bits of TMSI_CODEs-p are not all equal to ‘1’,
13 • DELETE_FOR_TMSIs is equal to ‘1’, and
14 • ASSIGNING_TMSI_ZONE_LENs-p is not equal to TMSI_ZONE_LENs, or the least

15 significant ASSIGNING_TMSI_ZONE_LENs-p octets of ASSIGNING_TMSI_ZONEs-p
16 are not equal to TMSI_ZONEs.
17 If the mobile station supports the Quick Paging Channel operation:

18 • The mobile station shall set QPCH_SUPPORTEDs to QPCH_SUPPORTEDr.
19 • If QPCH_SUPPORTEDr = ‘1’:
20 – The mobile station shall set QPCH_RATEs to QPCH_RATEr.
21 – If the number of Quick Paging Channels specified in the received message

22 (NUM_QPCHr) is different from NUM_QPCHs, the mobile station shall use the
23 hash algorithm specified in 2.6.7.1 to select a new Quick Paging Channel
24 number in the range 1 to NUM_QPCHr. The mobile station shall store the new
25 Quick Paging Channel number as QPAGECHs and as ASSIGNED_QPAGECHs.
26 The mobile station shall then set NUM_QPCHs to NUM_QPCHr.
27 • The mobile station shall set QPCH_POWER_LEVEL_PAGEs to

28 QPCH_POWER_LEVEL_PAGEr.
29 • The mobile station shall set QPCH_CCI_SUPPORTEDs to QPCH_CCI_SUPPORTEDr.
30 • If QPCH_CCI_SUPPORTEDr = ‘1’, the mobile station shall set

31 QPCH_POWER_LEVEL_CONFIGs to QPCH_POWER_LEVEL_CONFIGr.
32 2.6.2.2.6 Global Service Redirection Message

33 Whenever a Global Service Redirection Message is received on the Paging Channel, the
35 stored in GLOB_SERV_REDIR_MSG_SEQs. If the comparison results in a match or if
36 SYS_PAR_MSG_SEQs is not current, the mobile station may ignore the message; otherwise,
37 the mobile station shall store the following parameters:
2-79
C.S0005-0-2 v1.0

3 GLOB_SERV_REDIR_MSG_SEQs= CONFIG_MSG_SEQr)
4 • If the P_REV_IN_USEs is equal to or greater than 6, the mobile station shall ignore
5 this message, if any of the following conditions is true:
6 – EXT_GLOBAL_REDIRECTs = ‘1’
7 – EXCL_P_REV_MSr = ‘1’
8 If the subfield corresponding to the access overload class, ACCOLCp, of the mobile station
9 is set equal to ‘1’ in the REDIRECT_ACCOLCr field of the received message, the mobile
10 station shall store the following parameters and then shall enter the System Determination
11 Substate of the Mobile Station Initialization State with a redirection indication (see 2.6.1.1):
12 • Return if fail indicator (RETURN_IF_FAILs = RETURN_IF_FAILr)
13 • If DELETE_TMSIr is equal to ‘1’, the mobile station shall set all the bits of
14 TMSI_CODEs-p to ‘1’
15 • Redirection record (REDIRECT_RECs = redirection record from received message)
16 • If RECORD_TYPEr = ‘00000001’, the mobile station shall:
17 − Set CDMA_MODEs to ‘1’
18 − Set DIGITAL_REGs-p to ‘00000000’
19 − Max delay upon redirection (MAX_REDIRECT_DELAYs =

20 MAX_REDIRECT_DELAYr)
21 2.6.2.2.7 Extended Neighbor List Message

22 Whenever a valid Extended Neighbor List Message is received on the current Paging Channel
23 (PAGECHs), the configuration message sequence number, CONFIG_MSG_SEQr, shall be
24 compared to that stored in EXT_NGHBR_LST_MSG_SEQs. If the comparison results in a
25 match, the mobile station may ignore the message. 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 Extended Neighbor List Message that contains it.

33 EXT_NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr,
34 NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr)
35 • Pilot PN sequence offset increment (PILOT_INCs = PILOT_INCr)
2-80
C.S0005-0-2 v1.0
2 contained in the Extended Neighbor List Message.
3 For each of the neighboring base stations contained in the Extended Neighbor List Message,
4 if FREQ_INCLr equals ‘0’, or if FREQ_INCLr equals ‘1’ and NGHBR_BANDr is supported, the
6 • If the ith occurrence of NGHBR_CONFIGr is equal to ‘000’, ‘001’, or ‘010’, set the
7 NGHBR_CONFIG field of NGHBR_REC[i] to the ith occurrence of NGHBR_CONFIGr;
8 otherwise, set the NGHBR_CONFIG field of NGHBR_REC [i] to ‘011’.
9 • Set the NGHBR_PN field of NGHBR_REC[i] to the ith occurrence of NGHBR_PNr.
10 • Set the SEARCH_PRIORITY field of NGHBR_REC[i] to the ith occurrence of

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

16 NGHBR_BANDr.
17 • Set the NGHBR_FREQ field of NGHBR_REC[i] to the ith occurrence of

18 NGHBR_FREQr.
20 if FREQ_INCLr equals ‘0’, the mobile station shall also do the following:
21 • Set the NGHBR_BAND field of NGHBR_REC[i] to CDMABANDs.
22 • Set the NGHBR_FREQ field of NGHBR_REC[i] to CDMACHs.
23 If GEN_NGHBR_LST_MSG_SEQs is not equal to CONFIG_MSG_SEQs, the mobile station

24 shall do the following:
25 • Set the SRCH_WIN_NGHBR field of NGHBR_REC to SRCH_WIN_Ns for all

28 • Set NUM_ANALOG_NGHBRs to ‘000’ and set ANALOG_NGHBR_LIST to NULL.
2-81
C.S0005-0-2 v1.0
4 consists only of pilot offsets listed in the Extended Neighbor List Message. If the Extended
5 Neighbor List Message contains more pilot offsets than the mobile station can store, the
6 mobile station shall store the pilot offsets beginning at the start of the Extended Neighbor
7 List Message, up to the limits of the mobile station’s Neighbor Set storage capacity.
8 2.6.2.2.8 General Neighbor List Message

9 Whenever a valid General Neighbor List Message is received on the current Paging Channel
10 (PAGECHs), the configuration message sequence number, CONFIG_MSG_SEQr shall be
11 compared to that stored in GEN_NGHBR_LST_MSG_SEQs. If the comparison results in a
12 mismatch, then the mobile station shall process the remaining fields in the message as
13 follows.
15 station shall ignore the General Neighbor List Message that contains it.

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

22 mobile station shall store the following parameters:

24 (EXT_NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr,
25 NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr).
27 contained in the General Neighbor List Message.
28 For each of the neighboring base stations contained in the General Neighbor List Message, if
29 FREQ_INCLr equal ‘0’, or if FREQ_INCLr equal ‘1’ and NGHBR_BANDr is supported, the
31 • If NGHBR_CONFIG_PN_INCLr is equal to ‘1’, set the NGHBR_CONFIG and
32 NGHBR_PN fields as follows:
33 – If the ith occurrence of NGHBR_CONFIGr is equal to ‘000’, ‘001’, or ‘010’, set the
34 NGHBR_CONFIG field of NGHBR_REC[i] to the ith occurrence of
35 NGHBR_CONFIGr; otherwise, set the NGHBR_CONFIG field of NGHBR_REC[i] to
36 ‘011’.
37 – Set the NGHBR_PN field of NGHBR_REC[i] to the ith occurrence of NGHBR_PNr.
2-82
C.S0005-0-2 v1.0
1 • If NGHBR_SRCH_MODEr = ‘00’ or ‘10’ and EXT_NGHBR_LST_MSG_SEQs is not

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

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

7 NGHBR_REC to SEARCH_WINs for all NGHBR_SET_SIZEs entries if
8 SYS_PAR_MSG_SEQs is equal to CONFIG_MSG_SEQs; otherwise, set
9 SETTING_SEARCH_WIN to ‘1’.
10 • If NGHBR_SRCH_MODEr = ‘00’ or ‘01’, set the SRCH_OFFSET_NGHBR field of each
11 NGHBR_REC to ‘000’.
12 • If NGHBR_SRCH_MODEr = ‘10’ or ‘11’:
13 – set the SRCH_WIN_NGHBR field of NGHBR_REC[i] to the ith occurrence of

14 SRCH_WIN_NGHBRr
15 – if SRCH_OFFSET_INCLr equals to ‘1’, set the SRCH_OFFSET_NGHBR field of

16 NGHBR_REC[i] to the ith occurrence of SRCH_OFFSET_NGHBRr, and
17 – if SRCH_OFFSET_INCLr equals to ‘0’, set the SRCH_OFFSET_NGHBR field of

18 each NGHBR_REC to ‘000’.
19 • If USE_TIMINGr is equal to ‘1’, set the TIMING_INCL field of NGHBR_REC[i] to the
20 ith occurrence of TIMING_INCLr; otherwise, set the TIMING_INCL field of
21 NGHBR_REC to ‘0’ for all entries.
23 FREQ_FIELDS_INCLr equals ‘1’, FREQ_INCLr equals ‘1’, and NGHBR_BANDr is supported,
24 the mobile station shall also perform the following:
25 • Set the NGHBR_BAND field of NGHBR_REC[i] to the ith occurrence of

26 NGHBR_BANDr.
27 • Set the NGHBR_FREQ field of NGHBR_REC[i] to the ith occurrence of

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

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

36 GLOBAL_TX_DURATIONr for all entries.
37 – Set the NGHBR_TX_PERIOD field of NGHBR_REC to GLOBAL_TX_PERIODr for

38 all entries.
2-83
C.S0005-0-2 v1.0
1 • If GLOBAL_TIMING_INCLr is equal to ‘0’, then the mobile station shall:
2 – Set the NGHBR_TX_DURATION field of NGHBR_REC[i] to the ith occurrence of

3 NGHBR_TX_DURATIONr.
4 – Set the NGHBR_TX_PERIOD field of NGHBR_REC[i] to the ith occurrence of

5 NGHBR_TX_PERIODr.
7 FREQ_FIELDS_INCLr equals ‘1’ and FREQ_INCLr equals ‘0’, or if FREQ_FIELDS_INCLr
8 equals ‘0’ and EXT_NGHBR_LST_MSG_SEQs is not equal to CONFIG_MSG_SEQr, the
9 mobile station shall also do the following:
10 • Set the NGHBR_BAND field of NGHBR_REC[i] to CDMABANDs.
11 • Set the NGHBR_FREQ field of NGHBR_REC[i] to CDMACHs.
14 • EXT_SYS_PARAMETERs is equal to ‘0’
19 • EXT_SYS_PARAMETERs is equal to ‘0’
23 consists only of pilot offsets listed in the General Neighbor List Message. If the General
24 Neighbor List Message contains more pilot offsets than the mobile station can store, the
25 mobile station shall store the pilot offsets beginning at the start of the General Neighbor List
26 Message, up to the limits of the mobile station’s Neighbor Set storage capacity.
27 The mobile station shall set NUM_ANALOG_NGHBRs to NUM_ANALOG_NGHBRr, the
28 number of neighboring analog systems contained in the General Neighbor List Message. For
29 each of the neighboring analog systems contained in the General Neighbor List Message, the
30 mobile station shall perform the following:
31 • Set the BAND_CLASS field of ANALOG_NGHBR_LIST[i] to the ith occurrence of

32 BAND_CLASSr.
33 • Set the SYS_A_B field of ANALOG_NGHBR_LIST[i] to the ith occurrence of SYS_A_Br.
34 For each of the neighboring base stations contained in the General Neighbor List Message,
35 the mobile station shall set the ADD_PILOT_REC_INCL field of NGHBR_REC[i] to the ith
36 occurrence of ADD_PILOT_REC_INCr. If ADD_PILOT_REC_INCr equals ‘1’, for each pilot
37 included in the message, the mobile station shall also perform the following:
2-84
C.S0005-0-2 v1.0
1 • Set the NGHBR_PILOT_REC_TYPE field of NGHBR_PILOT_REC to

2 NGHBR_PILOT_REC_TYPEr.
3 • If NGHBR_PILOT_REC_TYPEr is equal to ‘000’. The mobile station shall:
4 – Set the OTD_POWER_LEVEL field of NGHBR_PILOT_REC to

5 OTD_POWER_LEVELr.
6 2.6.2.2.9 User Zone Identification Message

7 Whenever a User Zone Identification Message is received on the Paging Channel, and if the
8 mobile station supports Tiered Services, the mobile station shall compare the configuration
9 message sequence number, CONFIG_MSG_SEQr, to that stored in
10 USER_ZONE_ID_MSG_SEQs. If the comparison results in a match, the mobile station may
11 ignore the message. If the comparison results in a mismatch, then the mobile station shall
12 process the remaining fields in the message as follows.

16 USER_ZONE_ID_MSG_SEQs = CONFIG_MSG_SEQr)
17 • UZ_EXIT_RCVDs = UZ_EXITr
18 The mobile station shall set NUM_UZIDs to the number of User Zones contained in the User
19 Zone Identification Message.
20 For each User Zone contained in the User Zone Identification Message, the mobile station
22 • Set the UZID field of UZ_REC(i) to the ith occurrence of UZIDr.
23 • Set the UZ_REV field of the UZ_REC(i) to the ith occurrence of UZ_REVr.
24 • Set the TEMP_SUB field of the UZ_REC(i) to the ith occurrence of TEMP_SUBr.
25 2.6.2.2.10 Private Neighbor List Message

26 Whenever a Private Neighbor List Message is received on the Paging Channel, and if the
27 mobile station supports Tiered Services, the mobile station shall compare the configuration
28 message sequence number, CONFIG_MSG_SEQr, to that stored in
29 PRI_NGHBR_LST_MSG_SEQs. If the comparison results in a match, the mobile station may
30 ignore the message. If the comparison results in a mismatch, then the mobile station shall
31 process the remaining fields in the message as follows.

35 PRI_NGHBR_LST_MSG_SEQs = CONFIG_MSG_SEQr)
36 • Common configuration included indicator (COMMON_INCLs = COMMON_INCLr)
37 The mobile station shall set NUM_PRI_NGHBRs to the number of Private Neighbor base
2-85
C.S0005-0-2 v1.0
1 stations contained in the Private Neighbor List Message.
2 For each Private Neighbor base station contained in the Private Neighbor List Message the
4 • Set the SRCH_WIN_PRI_NGHBR field of PRI_NGHBR_REC(i) to SRCH_WIN_PNr.
5 • Set the SID field of PRI_NGHBR_REC(i) to the ith occurrence SIDr.
6 • Set the NID field of PRI_NGHBR_REC(i) to the ith occurrence NIDr.
7 • Set the PRI_NGHBR_PN field of PRI_NGHBR_REC(i) to the ith occurrence

8 PRI_NGHBR_PNr.
9 • If COMMON_INCLr is equal to ‘1’, then the mobile station shall:
10 – Set the BAND_CLASS field of PRI_NGHBR_REC(i) to COMMON_BAND_CLASSr.
11 – Set the NGHBR_FREQ field of PRI_NGHBR_REC(i) to COMMON_NGHBR_FREQr.
12 • If COMMON_INCLr is equal to ‘0’, then the mobile station shall:
13 – Set the BAND_CLASS field of PRI_NGHBR_REC(i) to the ith occurrence of

14 BAND_CLASSr.
15 – Set the NGHBR_FREQ field of PRI_NGHBR_REC(i) to the ith occurrence of

16 NGHBR_FREQr.
17 • If ith occurrence of UZID_INCLr is equal to ‘0’, then the mobile station shall set the
18 PS_NUM_UZID field of PRI_NGHBR_REC(i) to ‘0000’.
19 • If ith occurrence of UZID_INCLr is equal to ‘1’, then the mobile station shall set the
20 PS_NUM_UZID field of PRI_NGHBR_REC(i) to the NUM_UZIDr associated with the ith
21 occurrence of UZID_INCLr.
22 • For each User Zone supported by the ith private system, the mobile station shall do
23 the following:
24 – Set the PS_UZID(j) field of PRI_NGHBR_REC(i) to the jth occurrence of UZIDr.
25 – Set the PS_UZ_REV(j) field of PRI_NGHBR_REC(i) to the jth occurrence of

26 UZ_REVr.
27 – Set the PS_TEMP_SUB(j) field of PRI_NGHBR_REC(i) to the jth occurrence of

28 TEMP_SUBr.
29 2.6.2.2.11 Extended Global Service Redirection Message

30 Whenever an Extended Global Service Redirection Message is received on the Paging
31 Channel, the configuration message sequence number, CONFIG_MSG_SEQr, shall be
32 compared to that stored in EXT_GLOB_SERV_REDIR_MSG_SEQs. If the comparison
34 a mismatch, the mobile station shall store the following parameters:
2-86
C.S0005-0-2 v1.0

3 GLOB_SERV_REDIR_MSG_SEQs= CONFIG_MSG_SEQr,
4 EXT_GLOB_SERV_REDIR_MSG_SEQs= CONFIG_MSG_SEQr)
5 The mobile station shall ignore the rest of the message if any of the following conditions is
6 satisfied:
7 • If the subfield corresponding to the access overload class, ACCOLCp, of the mobile
8 station is set equal to ‘0’ in the REDIRECT_ACCOLCr field of the received message,
9 • If MOB_P_REVp is not in the redirection mobile protocol revision range (i.e.,

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

13 REDIRECT_P_REV_INCLr = ‘1’ and EXCL_P_REV_INDr = ‘1’ and (REDIRECT_P_MINr
14 ≤ MOB_P_REVp ≤ REDIRECT_P_MAXr)).
15 Otherwise, the mobile station shall store the following parameters and then shall enter the
16 System Determination Substate of the Mobile Station Initialization State with a redirection
17 indication (see 2.6.1.1):
19 TMSI_CODEs-p to ‘1’.
20 • Return if fail indicator (RETURN_IF_FAILs = RETURN_IF_FAILr).
21 • Redirection record (REDIRECT_RECs = redirection record from received message)
22 • If RECORD_TYPEr = ‘00000001’, the mobile station shall:
23 − Set CDMA_MODEs to ‘1’
24 − Set DIGITAL_REGs-p to ‘00000000’
25 − Max delay upon redirection (MAX_REDIRECT_DELAYs =

26 MAX_REDIRECT_DELAYr)
27 2.6.2.2.12 Extended CDMA Channel List Message

28 Whenever an Extended CDMA Channel List Message is received on the Paging Channel, the
29 mobile station shall compare the configuration message sequence number,
30 CONFIG_MSG_SEQr, to that stored in EXT_CHAN_LST_MSG_SEQs. If the comparison
32 a mismatch, then the mobile station shall process the remaining fields in the message as
33 follows:

37 EXT_CHAN_LST_MSG_SEQs = CONFIG_MSG_SEQr,
38 CHAN_LST_MSG_SEQs = CONFIG_MSG_SEQr).
2-87
C.S0005-0-2 v1.0
1 The mobile station shall determine the CDMA Channel (Frequency Assignment) for its
2 Paging Channel as follows:
3 • If RC_QPCH_SEL_INCLr is equal to ‘1’ and the mobile station is capable of RC greater
4 than 2 or capable of supporting Quick Paging Channel, the mobile station shall
5 eliminate those channels with RC_QPCH_HASH_INDr = ‘0’ from the CDMA channel list
6 and use the hash algorithm specified in 2.6.7.1 and the number of channels whose
7 RC_QPCH_HASH_INDr is equal to ‘1’ in the Extended CDMA Channel List Message to
8 determine the CDMA Channel (Frequency Assignment) for its Paging Channel.
9 • If RC_QPCH_SEL_INCLr is equal to ‘1’ and the mobile station is not capable of RC
10 greater than 2 and not capable of supporting Quick Paging Channel, the mobile station
11 shall use the hash algorithm specified in 2.6.7.1 and the number of channels in the
12 Extended CDMA Channel List Message to determine the CDMA Channel (Frequency
13 Assignment) for its Paging Channel.
14 • If RC_QPCH_SEL_INCLr is equal to ‘0’, the mobile station shall use the hash algorithm
15 specified in 2.6.7.1 and the number of channels in the Extended CDMA Channel List
16 Message to determine the CDMA Channel (Frequency Assignment) for its Paging
17 Channel.
18 If the CDMA Frequency Assignment has changed (the computed CDMA Channel is different
19 from CDMACHs), the mobile station shall perform the following actions:
20 • If the stored configuration parameters is not current (see 2.6.2.2) for the corresponding
21 base station and frequency assignment, the mobile station shall perform the following
22 actions:
24 – Set PAGE_CHANs to ‘1’.
25 – Set PAGECHs to the Primary Paging Channel.
26 – Set CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,

27 CHAN_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
30 EXT_GLOB_SERV_REDIR_MSG_SEQs, USER_ZONE_IDMSG_SEQs,
31 PRI_NGHBR_LST_MSG_SEQs, and ACC_MSG_SEQs to NULL.
32 – Tune to the new CDMA Channel.
33 • Otherwise, the mobile station shall perform the following actions:

35 – The mobile station shall use the hash algorithm specified in 2.6.7.1 to select
36 a new Paging Channel number in the range 1 to PAGE_CHANs, where
38 information is current. The mobile station shall store the new Paging
39 Channel number as PAGECHs.
2-88
C.S0005-0-2 v1.0
1 – Tune to the new CDMA Channel and shall begin monitoring the new Paging
2 Channel.
3 2.6.2.3 Mobile Station Page Match Operation

4 The Mobile Station Page Match Operation is performed whenever the mobile station receives
5 a General Page Message. If the mobile station receives a General Page Message that
6 contains the IMSI or TMSI assigned to the mobile station (see 2.1.2.2.2.1 of TIA/EIA/IS-
7 2000-[4]), the mobile station transmits a Page Response Message on the Access Channel. If
8 the mobile station is configured to receive broadcast messages and it receives a General
9 Page Message that contains a burst type and broadcast address that the mobile station has
10 been configured to receive (see 2.1.2.2.2.1 of TIA/EIA/IS-2000-[4]), the mobile station
11 performs the broadcast page procedures as described in 2.6.2.1.1.3.4.
12 The mobile station shall compare the configuration message sequence number,
13 CONFIG_MSG_SEQr, to CONFIG_MSG_SEQs. If the comparison results in a mismatch,
14 then the mobile station shall set CONFIG_MSG_SEQs to CONFIG_MSG_SEQr. The mobile
15 station shall also compare the Access Parameters Message sequence number,
16 ACC_MSG_SEQr, with that stored in ACC_MSG_SEQs. If the comparison results in a
17 mismatch, then the mobile station shall set ACC_MSG_SEQs to NULL (see 2.6.2.2). The
18 mobile station shall set CURR_ACC_MSG_SEQ to ACC_MSG_SEQs.
19 The mobile station shall process each record for which it declares a page match (see
20 2.1.2.2.2.1 of TIA/EIA/IS-2000-[4]).
21 If the mobile station receives a broadcast page that contains a burst type and broadcast
22 address that the mobile station has been configured to receive, the mobile station should
23 perform the broadcast page procedures described in 2.6.2.1.1.3.4.
24 If a page match is declared, the mobile station shall enter the Update Overhead Information
25 Substate of the System Access State (see 2.6.3.2) with a page response indication within
26 T33m seconds after the page message is received.
27 If a page match is declared and the mobile station determines that it should be monitoring
28 a neighboring base station, the mobile station may perform an access entry handoff to the
29 neighboring base station, if all of the following conditions hold:
30 • The neighboring base station is listed in NGHBR_REC.
31 • The ACCESS_ENTRY_HO field of the NGHBR_REC corresponding to the neighboring

32 base station is equal to ‘1’.
33 • None of CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,
35 CHAN_LST_MSG_SEQs, EXT_SYS_PAR_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs,
36 USER_ZONE_ID_MSG_SEQs, and PRI_NGHBR_LST_MSG_SEQs are equal to NULL.
37 Otherwise, the mobile station shall not perform an access entry handoff to the neighboring
38 base station.
39 The mobile station need not perform an access entry handoff to a base station operating on
40 another frequency.
2-89
C.S0005-0-2 v1.0
1 If the mobile station performs an access entry handoff, it shall follow the procedures
2 specified in 2.6.2.1.4.2 and shall perform the access entry handoff before entering the
3 Update Overhead Information Substate of the System Access State (see 2.6.3.2).
4 If PACA is enabled, and if the mobile station performs an access entry handoff, the mobile
5 station shall respond to the General Page Message first, and shall then re-originate the
6 PACA call on the new base station.
7 2.6.2.4 Mobile Station Order and Message Processing Operation

8 During the Mobile Station Order and Message Processing Operation, the mobile station
9 processes all messages except overhead messages (see 2.6.2.2) and page messages (see
10 2.6.2.3).
11 The mobile station shall set CURR_ACC_MSG_SEQ to NULL.
12 The mobile station shall perform address matching as described in 2.1.2.2 of TIA/EIA/IS-
13 2000-[4].
14 If Layer 3 receives a message that requires acknowledgement, the mobile station shall enter
15 the Update Overhead Information Substate of the System Access State with an
16 order/message response indication within T33m seconds, unless otherwise specified for a
17 particular message.
18 If Layer 3 receives a message that does not require acknowledgement, the mobile station
19 shall transmit a response only if it is required by the message or order. If a response is
20 required, the mobile station shall enter the Update Overhead Information Substate of the
21 System Access State with an order/message response indication within T33m seconds,
22 unless otherwise specified for a particular message.
23 If the mobile station is to enter the Update Overhead Information Substate of the System
24 Access State with an order/message response indication and the mobile station determines
25 that it should be monitoring a neighboring base station, the mobile station may perform an
26 access entry handoff to the neighboring base station, if all of the following conditions hold:
27 • The neighboring base station is listed in NGHBR_REC.
28 • The ACCESS_ENTRY_HO field of the NGHBR_REC corresponding to the neighboring

29 base station is equal to ‘1’.
30 • ACC_ENT_HO_ORDERs is equal to ‘1’.
31 • None of CONFIG_MSG_SEQs, SYS_PAR_MSG_SEQs, NGHBR_LST_MSG_SEQs,

33 CHAN_LST_MSG_SEQs, EXT_CHAN_LST_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
34 PRI_NGHBR_LST_MSG_SEQs, and EXT_SYS_PAR_MSG_SEQs are equal to NULL.
35 Otherwise, the mobile station shall not perform an access entry handoff to the neighboring
36 base station.
37 The mobile station need not perform an access entry handoff to a base station operating on
38 another frequency.
2-90
C.S0005-0-2 v1.0
1 If the mobile station performs an access entry handoff, it shall follow the procedures
2 specified in 2.6.2.1.4.2 and shall perform the access entry handoff before entering the
3 Update Overhead Information Substate of the System Access State (see 2.6.3.2). If PACA is
4 enabled and the mobile station performs an access entry handoff, the mobile station shall
5 respond to the order/message first and then re-originate the PACA call in the new base
6 station.
7 The following directed messages and orders can be received. If any field value of the
8 message or order is outside its permissible range, the mobile station shall send a Mobile
9 Station Reject Order with ORDQ equal to ‘00000100’ (message field not in valid range).
10 1. Abbreviated Alert Order: The mobile station may alert the user.
11 2. Audit Order
12 3. Authentication Challenge Message: The mobile station shall process the message
13 and shall respond with an Authentication Challenge Response Message as specified
14 in 2.3.12.1.4, regardless of the value of AUTHs. The mobile station shall enter the
15 Update Overhead Information Substate of the System Access State with an
16 order/message response indication within T32m seconds.
17 4. Base Station Challenge Confirmation Order: The mobile station shall process the
18 message and shall respond with an SSD Update Confirmation Order or SSD Update
19 Rejection Order as specified in 2.3.12.1.5. The mobile station shall enter the Update
20 Overhead Information Substate of the System Access State with an order/message
21 response indication within T32m seconds.
22 5. Channel Assignment Message: The mobile station shall process the message as
23 follows:
24 • If ASSIGN_MODEr equals ‘001’, the mobile station shall perform the following
25 actions:
26 - If the message requires acknowledgement, the mobile station shall wait until
27 Layer 3 receives an indication from Layer 2 that the acknowledgement to the
28 message has been sent and acknowledged.
29 - If a CDMA channel (CDMA_FREQ) is specified in the assignment, the mobile

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

38 (PURPOSEr is equal to ‘0000’), the mobile station shall enter the Update
41 Station Reject Order with the ORDQ field set to ‘00000010’ (message not
42 accepted in this state).
2-95
C.S0005-0-2 v1.0
1 – If the purpose of the message is to provide the queue position of the PACA
2 call (PURPOSEr is equal to ‘0001’), the mobile station shall set the PACA
3 state timer to the duration shown in Table 3.7.2.3.2.20-2, corresponding to
4 the value of PACA_TIMEOUTs, should indicate to the user that the PACA call
5 is still queued, and should indicate the current queue position (Q_POSr) of
6 the call.
7 – If the purpose of the message is to instruct the mobile station to re-originate

8 the PACA call (PURPOSEr is equal to ‘0010’), the mobile station shall set the
9 PACA state timer to the duration shown in Table 3.7.2.3.2.20-2
10 corresponding to the value of PACA_TIMEOUTs, and the mobile station shall
11 enter the Update Overhead Information Substate of the System Access State
12 (see 2.6.3) with a PACA response indication within T33m seconds to re-
13 originate the PACA call.
14 – If the purpose of the message is to cancel the PACA call (PURPOSEr is equal
15 to ‘0011’), the mobile station shall set PACAs to disabled and PACA_CANCEL
16 to ‘0’, shall disable the PACA state timer, and should indicate to the user
17 that the PACA call has been canceled.
18 13. Registration Accepted Order: If ORDQr is equal to ‘00000101’, the mobile station
19 shall set ROAM_INDIs = ROAM_INDIr and should display the roaming condition.
20 14. Registration Rejected Order: This order indicates that normal service is not
21 available on this system. The mobile station shall disable the full-TMSI timer. If
22 the received order specifies to delete the TMSI (ORDQ = ‘00000100’), the mobile
23 station shall set all the bits of the TMSI_CODEs-p to ‘1’. The mobile station shall
24 enter the System Determination Substate of the Mobile Station Initialization State
25 with a registration rejected indication (see 2.6.1.1).
26 15. Registration Request Order: The mobile station shall process the message and
27 perform registration procedures as specified in 2.6.5.5.2.3.
28 16. Retry Order: The mobile station shall process the message as follows:
29 • If RETRY_TYPEr is equal to ‘000’, the mobile station shall set
30 RETRY_DELAYs[RETRY_TYPE] to ‘0’, where RETRY_TYPE is equal to ‘001’, ‘010’,
31 or ‘011’.
32 • If RETRY_TYPEr is equal to ‘001’, the mobile station shall perform the following:
33 – If RETRY_DELAYr is equal to ‘00000000’, then the mobile station shall set

34 RETRY_DELAYs to ‘0’.
35 – If RETRY_DELAYr is not equal to ‘00000000’, the mobile station shall set

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

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

41 significant bits of RETRY_DELAYr.
2-96
C.S0005-0-2 v1.0
1 + The mobile station shall store the next system time 80 ms boundary +
2 RETRY_DELAY_VALUEs × RETRY_DELAY_UNITs ms as
3 RETRY_DELAYs[RETRY_TYPEr].
4 17. Service Redirection Message: The mobile station shall process the message as
5 follows:
6 • If the mobile station is directed to an unsupported operation mode or band class,

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

14 System Determination Substate of the Mobile Station Initialization State with an
15 NDSS off indication (see 2.6.1.1); otherwise, the mobile station shall store the
16 redirection record received in the message as REDIRECT_RECs and shall enter
17 the System Determination Substate of the Mobile Station Initialization State with a
18 redirection indication (see 2.6.1.1).
19 18. Slotted Mode Order: After receiving this order, the mobile station shall set
20 SLOTTEDs to YES. The mobile station shall disable the TMS_Slotted timer.
21 19. SSD Update Message: The mobile station shall process the message and shall
22 respond with a Base Station Challenge Order as specified in 2.3.12.1.5. The mobile
23 station shall enter the Update Overhead Information Substate of the System Access
24 State with an order/message response indication within T32m seconds.
25 20. Status Request Message: The mobile station shall process the message. If
26 P_REV_IN_USEs is less than or equal to three, the mobile station shall respond
27 with a Status Response Message. If P_REV_IN_USEs is greater than three, the
28 mobile station shall respond with an Extended Status Response Message. The
29 mobile station shall enter the Update Overhead Information Substate of the System
30 Access State with an order/message response indication within T33m seconds. If
31 the message does not specify any qualification information (QUAL_INFO_TYPEr is
32 equal to ‘00000000’), the mobile station shall include the requested information
33 records in the response. If the message specifies a band class (QUAL_INFO_TYPEr
34 is equal to ‘00000001’), the mobile station shall only include the requested
35 information records for the specified band class (BAND_CLASSr) in the response. If
36 the message specifies a band class and an operating mode (QUAL_INFO_TYPEr is
37 equal to ‘00000010’), the mobile station shall only include the requested
38 information records for the specified band class (BAND_CLASSr) and operating
39 mode (OP_MODEr) in the response. If the message specifies a band class or a band
40 class and an operating mode which is not supported by the mobile station, the
41 mobile station shall send a Mobile Station Reject Order with ORDQ set to ‘00000110’
42 (message requires a capability that is not supported by the mobile station). If the
2-97
C.S0005-0-2 v1.0
1 response to this message exceeds the allowable length, the mobile station shall
2 send a Mobile Station Reject Order with ORDQ set to ‘00001000’ (response message
3 would exceed the allowable length). If the message specifies an information record
4 which is not supported by the mobile station for the specified band class and
5 operating mode, the mobile station shall send a Mobile Station Reject Order with
6 ORDQ set to ‘00001001’ (information record is not supported for the specified band
7 class and operating mode).
8 21. TMSI Assignment Message: The mobile station shall store the TMSI zone and code
9 as follows:
10 • The mobile station shall store the length of the TMSI zone field by setting
11 ASSIGNING_TMSI_ZONE_LENs-p to TMSI_ZONE_LENr,
12 • The mobile station shall store the assigning TMSI zone number by setting the
13 ASSIGNING_TMSI_ZONE_LENs-p least significant octets of
14 ASSIGNING_TMSI_ZONEs-p to TMSI_ZONEr, and
15 • The mobile station shall store the TMSI code by setting TMSI_CODEs-p to
16 TMSI_CODEr.
17 The mobile station shall set the TMSI expiration time by setting TMSI_EXP_TIMEs-p
18 to TMSI_EXP_TIMEr. The mobile station shall disable the full-TMSI timer. The
19 mobile station shall then respond with a TMSI Assignment Completion Message
20 within T56m seconds.
21 22. Unlock Order: After receiving this order, the mobile station is no longer locked. The
22 mobile station should notify the user that the locked condition has been removed.
23 The mobile station shall enter the System Determination Substate of the Mobile
24 Station Initialization State with an unlock indication (see 2.6.1.1).
25 23. User Zone Reject Message
26 The mobile station shall ignore all other messages and orders.
27 2.6.2.5 Mobile Station Origination Operation

28 The Mobile Station Origination Operation is performed when the mobile station is directed by
29 the user to initiate a call, or if the Mobile Station Idle State is entered with NDSS_ORIGs
30 enabled.
31 If the mobile station is directed by the user to initiate a call, the mobile station shall
33 • If PACAs is equal to enabled, the mobile station shall set PACAs to disabled and
34 PACA_CANCEL to ‘0’, shall disable the PACA state timer, and should indicate to the
35 user that the PACA call has been canceled.
36 • The mobile station shall set CURR_ACC_MSG_SEQ to NULL.

37 The mobile station shall enter the Update Overhead Information Substate of the System
38 Access State (see 2.6.3) with an origination indication within T33m seconds.
2-98
C.S0005-0-2 v1.0
1 2.6.2.6 Mobile Station Message Transmission Operation
2 Support of this operation is optional. If the mobile station supports the Mobile Station
3 Message Transmission Operation, the operation is performed when the user directs the
4 mobile station to transmit a Data Burst Message.
5 If the mobile station supports this operation, the mobile station shall set
6 CURR_ACC_MSG_SEQ to NULL.
7 If the mobile station supports this operation, the mobile station shall enter the Update
8 Overhead Information Substate of the System Access State (see 2.6.3.2) with a message
9 transmission indication within T33m seconds.
10 2.6.2.7 Mobile Station Power-Down Operation

11 The Mobile Station Power-Down Operation is performed when the user directs the mobile
12 station to power down.
13 The mobile station shall update stored parameters and perform other registration
14 procedures as specified in 2.6.5.5.2.4.
15 If no power-down registration is performed (see 2.6.5.5.2.4), the mobile station may power
16 down.
17 2.6.2.8 Mobile Station PACA Cancel Operation

18 The Mobile Station PACA Cancel Operation is performed when the user directs the mobile
19 station to cancel a PACA call.
20 If PACAs is equal to enabled, the mobile station shall perform the following:
21 • The mobile station shall set PACAs to disabled.
22 • The mobile station shall set PACA_CANCEL to ‘0’, if PACA_CANCEL is equal to ‘1’.
23 • The mobile station shall disable the PACA state timer.
24 • The mobile station should indicate to the user that the PACA call has been canceled.
25 • The mobile station shall set CURR_ACC_MSG_SEQ to NULL.

26 • The mobile station shall enter the Update Overhead Information Substate of the
27 System Access State (see 2.6.3) with a PACA cancel indication within T33m seconds.
28 2.6.3 System Access State

29 In this state, the mobile station sends messages to the base station on the r-csch and
30 receives messages from the base station on the f-csch.
31 As illustrated in Figure 2.6.3-1, the System Access State consists of the following substates:
32 • Update Overhead Information Substate - In this substate, the mobile station monitors
33 the Paging Channel until it has a current set of overhead messages.
34 • Mobile Station Origination Attempt Substate - In this substate, the mobile station
35 sends an Origination Message to the base station.
2-99
C.S0005-0-2 v1.0
1 • Page Response Substate - In this substate, the mobile station sends a Page
2 Response Message to the base station.
3 • Mobile Station Order/Message Response Substate - In this substate, the mobile

4 station sends a response to a message received from the base station.
5 • Registration Access Substate - In this substate, the mobile station sends a
6 Registration Message to the base station.
7 • Mobile Station Message Transmission Substate - In this substate, the mobile station
8 sends a Data Burst Message to the base station.
9 • PACA Cancel Substate - In this substate, the mobile station sends a PACA Cancel
10 Message to the base station.
11
(Enter from Mobile Station Idle State )
GPM= Received a
Note:Transitions arising General Page
from error conditions and Update Overhead
Information Message
lock orders are not shown.
Substate
(2.6.3.2)
GPM
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 GPM
User
Registration Access
PM
Mobile Station initiated
Substate
GPM
G
Order/Message a call
(2.6.3.6)
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
12 or go to analog)
13 Figure 2.6.3-1. System Access State
14
15 2.6.3.1 Access Procedures
16 2.6.3.1.1 Access Attempts
17 The mobile station transmits on the Access Channel using a random access procedure.
18 Many parameters of the random access procedure are supplied by the base station in the
19 Access Parameters Message. The random access procedure is described in section 2.1.1.2.2
20 of TIA/EIA/IS-2000-[4] and 2.2.4.4.2 of TIA/EIA/IS-2000-[3].
2-100
C.S0005-0-2 v1.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, the mobile
35 station shall update parameters based on the System Parameters Message, the Access
36 Parameters Message and the Extended System Parameters Message on the associated new
37 Paging Channel and process parameters from the messages (see 2.6.2.2.1, 2.6.2.2.2, and
38 2.6.2.2.5). The mobile station shall update parameters based on the Neighbor List Message,
2-101
C.S0005-0-2 v1.0
1 Extended Neighbor List Message, or the General Neighbor List Message on the associated
2 new Paging Channel and process parameters from the message (see 2.6.2.2.3, 2.6.2.2.7,
3 and 2.6.2.2.8). If the mobile station receives the User Zone Identification Message or the
4 Private Neighbor List Message, the mobile station shall update parameters based on these
5 messages on the associated new Paging Channel and process parameters from the
6 messages (see 2.6.2.2.9 and 2.6.2.2.10). If the mobile station receives a Global Service
7 Redirection Message (see 2.6.2.2.6) which directs the mobile station away from the new base
8 station, the mobile station shall not access the new base station. If the mobile station
9 receives an Extended Global Service Redirection Message (see 2.6.2.2.11) which directs the
10 mobile station away from the new base station, the mobile station shall not access the new
11 base station. The mobile station shall process these messages only once after each access
12 handoff.
13 2.6.3.1.3.1 Pilot Search

14 The following sets of pilot offsets are defined for a mobile station in the System Access State.
15 Each pilot offset is a member of only one set.
16 • Active Set: The pilot offset of the Forward CDMA Channel whose Paging Channel is
17 being monitored.
18 • Neighbor Set: The pilots that are not currently in the Active Set and are likely
19 candidates for access handoff or access probe handoff. The members of the
20 Neighbor Set are specified in the Neighbor List Message, the Extended Neighbor List
21 Message, and the General Neighbor List Message.
22 • Remaining Set: The set of all possible pilot offsets in the current system (integer
23 multiples of PILOT_INCs) on the current CDMA Frequency Assignment, excluding
24 the pilots in the Neighbor Set and the Active Set.
25 2.6.3.1.3.2 Access Handoff
26 The mobile station is permitted to perform an access handoff to use the Paging Channel
27 with the best pilot strength and an associated Access Channel. The mobile station is
28 permitted to perform an access handoff when waiting for a response from the base station
29 or before sending a response to the base station. An access handoff is permitted after an
30 access attempt while the mobile station is in the Page Response Substate or the Mobile
31 Station Origination Attempt Substate.
32 When the mobile station declares a loss of the Paging Channel while waiting for a response
33 from the base station in the Page Response Substate or in the Mobile Station Origination
34 Attempt Substate, the mobile station shall perform an access handoff, if all of the following
35 conditions hold:
36 • The pilot corresponding to the new base station is in the list ACCESS_HO_LIST,
37 • ACCESS_HOs is equal to ‘1’, and
38 • The mobile station is not already in the process of performing an access attempt.
39 When the mobile station declares a loss of the Paging Channel, after receiving a message
40 but before responding to that message while in the Page Response Substate or in the Mobile
2-102
C.S0005-0-2 v1.0
1 Station Origination Attempt Substate, the mobile station shall perform an access handoff if
2 the following conditions hold:
4 • ACCESS_HOs is equal to ‘1’,
5 • ACCESS_HO_MSG_RSPs is equal to ‘1’, and
7 When the mobile station declares an insufficiency of the Paging Channel3, while waiting for
8 a response from the base station in the Page Response Substate or in the Mobile Station
9 Origination Attempt Substate, the mobile station may perform an access handoff if the
10 following conditions hold:
12 • ACCESS_HOs is equal to ‘1’, and
14 When the mobile station declares an insufficiency of the Paging Channel4, after receiving a
15 message but before responding to that message while in the Page Response Substate or in
16 the Mobile Station Origination Attempt Substate, the mobile station may perform an access
17 handoff if all of the following conditions hold:
19 • ACCESS_HOs is equal to ‘1’,
20 • ACCESS_HO_MSG_RSPs is equal to ‘1’, and
22 If ACCESS_PROBE_HOs is equal to ‘0’ and ACCESS_HOs is equal to ‘1’, and the mobile
23 station declares a loss of the Paging Channel during an access attempt, after sending at
24 least one complete access probe, the mobile station may monitor other Paging Channels
25 which are in ACCESS_HO_LIST for T42m seconds after the loss of the Paging Channel on
26 which the access attempt was made5.
27 2.6.3.1.3.3 Access Probe Handoff
28 The mobile station is permitted to perform an access probe handoff when the mobile station
29 is in the Page Response Substate or the Mobile Station Origination Attempt Substate.
3 Insufficiency of the Paging Channel is implementor-defined.
5 The mobile station would be waiting for a response to the message transmitted in the access probe.
2-103
C.S0005-0-2 v1.0
1 The mobile station may perform an access probe handoff during an access attempt to a
2 pilot in ACCESS_HO_LIST when the message being sent is the Origination Message or the
3 Page Response Message, if all of the following conditions hold:
4 • ACCESS_PROBE_HOs is equal to ‘1’,
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.
9 The mobile station may also perform an access probe handoff during an access attempt to a
10 pilot 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’.
14 pilot not in ACCESS_HO_LIST when the message being sent is the Origination Message or
15 the Page Response Message, if all of the following conditions hold:
16 • ACC_HO_LIST_UPDs is equal to ‘1’,
17 • ACCESS_PROBE_HOs is equal to ‘1’,
18 • The new pilot is stronger than any pilot in ACCESS_HO_LIST,
19 • The new pilot has the corresponding ACCESS_HO_ALLOWED field in the

20 NGHBR_REC equal to ‘1’,
21 • Inclusion of the new pilot in ACCESS_HO_LIST does not cause the Access Channel
22 message to exceed the maximum capsule size,
23 • Inclusion of the new pilot in ACCESS_HO_LIST does not cause the number of
24 members to exceed N13m,
25 • The mobile station is in the Page Response Substate or the Mobile Station Origination
26 Attempt Substate, and
27 • The mobile station has performed fewer than (MAX_NUM_PROBE_HOs +1) access
28 probe handoffs during the current access attempt.
30 pilot not in ACCESS_HO_LIST when the message being sent is a message other than the
31 Origination Message or the Page Response Message, if all of the preceding conditions hold
32 and ACC_PROBE_HO_OTHER_MSGs is equal to ‘1’.
33 If the above conditions are met, the mobile station may perform an access probe handoff
34 when the mobile station declares a loss of the Paging Channel (see 2.6.2.1.1.43.1.8); the
35 mobile station may also perform an access probe handoff after getting an indication that
2-104
C.S0005-0-2 v1.0
1 the TA timer expired (see 2.1.1.2.2 of TIA/EIA/IS-2000-[4]) and the mobile station declares
2 an insufficiency of the Paging Channel6.
3 If the mobile station performs an access probe handoff, the mobile station shall suspend
4 the access attempt on the old pilot and shall restart the access attempt on the new pilot (i.e.
5 starting with the first probe of the first probe sequence of the access sub-attempt), as
6 specified in 2.1.1.2.2 of TIA/EIA/IS-2000-[4]. The mobile station shall record the identity of
7 the pilots to which access probes have been transmitted within the current access attempt.
8 The mobile station shall not reset its access probe handoff count until the access attempt
9 ends.
10 Layer 3 shall send an L2-Supervision.Request primitive to Layer 2 to cancel the access

11 attempt if the length of the message to be sent exceeds MAX_CAP_SIZE of the new base
12 station. The mobile station may monitor other Paging Channels which are in
13 ACCESS_HO_LIST for T42m seconds after aborting the access attempt7.
14 2.6.3.1.4 System Access State Exit Procedures

15 Upon exiting the System Access State, the mobile station shall direct Layer 2 to cancel (see
16 2.1.1.2.2 of TIA/EIA/IS-2000-[4]) any access attempt in progress and discard the associated
17 message. The mobile station shall then disable the System Access State timer.
18 2.6.3.1.5 Reserved
19 2.6.3.1.6 Full-TMSI Timer
20 Whenever the mobile station sends its full TMSI, the mobile station enables a timer, called
21 the full-TMSI timer. If the full-TMSI timer expires, the mobile station deletes the TMSI by
22 setting all of the bits in the TMSI_CODEs-p field to ‘1’.
23 The mobile station shall maintain the full-TMSI timer. The mobile station shall provide a
24 means for enabling or disabling the full-TMSI timer.
25 If the mobile station sends a message with an address including the

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

33 defined as a set of at most N13m pilots, having the greatest pilot strength in comparison
34 with other qualifying pilots and for which the following apply:
35 • The strength of each member to which access probes have not been transmitted
36 exceeds T_ADD.
2-106
C.S0005-0-2 v1.0
1 • Each member other than the pilot to which the first access probe in the System
2 Access State was transmitted has the corresponding ACCESS_HO_ALLOWED field
3 in the NGHBR_REC equal to ‘1’.
4 • The Active Set pilot to which the next access probe is to be transmitted is a member.
5 • All pilots to which access probes have been transmitted since entering the System
6 Access State are members.
9 2.6.3.1.7.3 Generation of the Other Reported List

10 OTHER_REPORTED_LIST is defined as a set of no more than N13m minus the number of
11 pilots in ACCESS_HO_LIST pilots, having the greatest pilot strength in comparison with
12 other qualifying pilots and for which the following apply:
13 • The strength of each member exceeds T_ADD.
14 • No member is included in ACCESS_HO_LIST.
17 2.6.3.1.7.4 Update of OTHER_REPORTED_LIST
18 Before transmitting each access probe, the mobile station shall generate
19 OTHER_REPORTED_LIST according to section 2.6.3.1.7.3, using the most recent pilot
20 strength information available from its searcher element (see 2.2.2.1 of TIA/EIA/IS-2000-
21 [2]). If the mobile station updates ACCESS_HO_LIST before transmitting an access probe, it
22 shall update OTHER_REPORTED_LIST after updating ACCESS_HO_LIST.
23 2.6.3.1.8 Paging Channel Monitoring

24 When in the System Access State, the mobile station shall monitor the Paging Channel at all
25 times.
26 The mobile station shall set a timer for T72m seconds, when it begins to monitor the Paging
27 Channel and whenever it gets an indication that a valid message was received on the Paging
28 Channel, whether addressed to the mobile station or not (see 2.1.2.3.2 of IS-2000-[4]).
29 If the T72m timer expires:
30 • The mobile station shall first finish transmitting the access probe in progress, if any.
31 • If by declaring a loss of the Paging Channel, the eligibility requirements for

32 performing access handoff are met (see 2.6.3.1.3.2), then the mobile station shall
33 declare a loss of the Paging Channel and perform an access handoff. If by declaring
34 a loss of the Paging Channel, the eligibility requirements for performing access
35 probe handoff are met (see 2.6.3.1.3.3), then the mobile station may declare a loss of
36 the Paging Channel and perform an access probe handoff. If the mobile station
37 performs an access handoff or an access probe handoff, the mobile station restarts
38 the Paging Channel monitoring procedure for the new base station.
2-107
C.S0005-0-2 v1.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 and shall disable its transmitter.
4 • If an access attempt was in progress when the timer expired and that access
5 attempt had not been suspended and resumed before and the mobile station does
6 not perform access probe handoff, the mobile station shall declare a temporary loss
7 of the Paging Channel, shall direct Layer 2 to suspend the access attempt (see
8 2.1.1.2.2 of TIA/EIA/IS-2000-[4].), and shall perform the following:
9 – The mobile station shall set the timer to (T40m-T72m) seconds.
10 – If the mobile station receives an indication that a valid message on the Paging
11 Channel, whether addressed to the mobile station or not, was received (see
12 2.1.2.3.2 of IS-2000-[4]) prior to the expiration of the (T40m-T72m) timer, the
13 mobile station shall re-enable the transmitter, shall direct Layer 2 to resume
14 operation from the beginning of the interrupted access probe sequence of the
15 access sub-attempt (see 2.1.1.2.2 of TIA/EIA/IS-2000-[4].), and shall transmit
16 the first probe of the new access probe sequence immediately after re-enabling
17 the transmitter.
18 – If the (T40m-T72m) timer expires, the mobile station shall direct Layer 2 to cancel
19 any access attempt (see 2.1.1.2.2 of TIA/EIA/IS-2000-[4].) and shall declare a
20 loss of the Paging Channel.
21 • If an access attempt was not in progress when the timer expired and the mobile
22 station does not perform access handoff, the mobile station shall perform the
23 following:
24 – The mobile station shall set the timer to (T40m-T72m) seconds.
25 – If the (T40m-T72m) timer expires, the mobile station shall declare a loss of the
26 Paging Channel.
27 2.6.3.2 Update Overhead Information Substate
28 In this substate, the mobile station monitors the Paging Channel until it has received the
29 current configuration messages. The mobile station compares sequence numbers to
30 determine whether all of the configuration messages are up-to-date. To make sure it has
31 the latest access parameters, the mobile station receives at least one message containing
32 the ACC_MSG_SEQ field (except in case of a page response, since the initiating General
33 Page Message contains ACC_MSG_SEQ), and waits, if necessary, for an Access Parameters
34 Message.
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-108
C.S0005-0-2 v1.0
1 Upon entering the Update Overhead Information Substate, the mobile station shall set the
2 System Access State timer to a value of T41m seconds. The mobile station shall set PAGED
3 to NO.
4 If the System Access State timer expires while in this substate, the mobile station shall
5 enter the System Determination Substate of the Mobile Station Initialization State with a
6 system lost indication (see 2.6.1.1).
7 While in the Update Overhead Information Substate, the mobile station shall monitor the
8 Paging Channel. If the mobile station declares a loss of the Paging Channel (see
9 2.6.2.1.1.43.1.8), the mobile station shall perform the following:
13 • The mobile station shall declare an access attempt failure and update its
14 registration variables as specified in 2.6.5.5.3.2.
15 • The mobile station shall enter the Mobile Station Idle State.
16 If PACAs is equal to enabled, the mobile station shall set PACA_CANCEL to ‘1’ when the
17 user directs the mobile station to cancel a PACA call.
18 If the mobile station receives any of the following messages, it shall process the message as
19 follows:
20 1. System Parameters Message: The mobile station shall process the parameters from
21 the message (see 2.6.2.2.1).
22 2. Access Parameters Message: The mobile station shall process the parameters from
24 3. Neighbor List Message: The mobile station shall process the parameters from the
25 message (see 2.6.2.2.3).
26 4. CDMA Channel List Message: The mobile station shall process the parameters from
28 5. Extended System Parameters Message: The mobile station shall process the
29 parameters from the message (see 2.6.2.2.5).
30 6. Global Service Redirection Message: The mobile station shall process the
32 7. Extended Neighbor List Message: The mobile station shall process the parameters
33 from the message (see 2.6.2.2.7).
34 8. General Neighbor List Message: The mobile station shall process the parameters
36 9. Lock Until Power-Cycled Order: The mobile station shall record the reason for the
37 Lock Until Power-Cycled Order in the mobile station’s semi-permanent memory
38 (LCKRSN_Ps-p equals the least-significant four bits of ORDQr). The mobile station
39 should notify the user of the locked condition. The mobile station shall then enter
2-109
C.S0005-0-2 v1.0
2 lock indication (see 2.6.1.1), and shall not enter the System Access State again until
3 after the next mobile station power-up or until it has received an Unlock Order.
4 This requirement shall take precedence over any other mobile station requirement
5 specifying entry to the System Access State.
6 10. General Page Message: If CURR_ACC_MSG_SEQ is equal to NULL, the mobile

7 station shall set CURR_ACC_MSG_SEQ to ACC_MSG_SEQr. The mobile station
8 shall compare CONFIG_MSG_SEQs to CONFIG_MSG_SEQr. If the comparison
9 results in a mismatch, the mobile station shall set CONFIG_MSG_SEQs to
10 CONFIG_MSG_SEQr. The mobile station may ignore the rest of the message. If
11 this substate was not entered with an origination or page response indication, the
12 mobile station may also determine whether there is a page match. If the mobile
13 station attempts to determine whether there is a page match, it shall use the
14 procedure as defined in 2.6.2.3. If a match is declared, the mobile station shall set
15 PAGED to YES.
16 11. User Zone Identification Message: The mobile station shall process the parameters
18 12. Private Neighbor List Message: The mobile station shall process the parameters from
20 13. Extended Global Service Redirection Message: The mobile station shall process the
22 14. Extended CDMA Channel List Message: The mobile station shall process the
24 If the mobile station receives a message which is not included in the above list, the mobile
25 station shall ignore the message.
26 When the stored configuration parameters are current (see 2.6.2.2) and
27 CURR_ACC_MSG_SEQ and ACC_MSG_SEQs are equal and are not NULL, the mobile
28 station shall disable the System Access State timer and shall do one of the following:
29 • If PAGED is equal to YES, the mobile station shall determine whether the message
30 resulting in the page match was received on the current Paging Channel. If the
31 message was received on the current Paging Channel, the mobile station shall enter
32 the Page Response Substate; otherwise, the mobile station shall enter the Mobile
33 Station Idle State.
34 • If this substate was entered with a page response indication and the mobile station
35 has not performed an access entry handoff, the mobile station shall determine
36 whether the message resulting in the page match was received on the current
37 Paging Channel. If the message was received on the current Paging Channel, the
38 mobile station shall enter the Page Response Substate; otherwise, the mobile station
39 shall enter the Mobile Station Idle State.
2-110
C.S0005-0-2 v1.0
1 • If this substate was entered with a page response indication and the mobile station
2 has performed an access entry handoff, the mobile station shall enter the Page
3 Response Substate.
4 • If this substate was entered with a page response retransmission indication, the
5 mobile station shall enter the Page Response Substate.
6 • If this substate was entered with an origination indication, the mobile station shall
7 enter the Mobile Station Origination Attempt Substate with an origination indication.
8 • If this substate was entered with a PACA response indication, the mobile station
9 shall enter the Mobile Station Origination Attempt Substate with a PACA response
10 indication.
11 • If this substate was entered with an order/message response indication and the
12 mobile station has not performed an access entry handoff, the mobile station shall
13 determine whether the message resulting in the response was received on the
14 current Paging Channel. If the message was received on the current Paging
15 Channel, the mobile station shall enter the Mobile Station Order/Message Response
16 Substate; otherwise, the mobile station shall discard the response and enter the
17 Mobile Station Idle State.
18 • If this substate was entered with an order/message response indication and the
19 mobile station has performed an access entry handoff, the mobile station shall enter
20 the Mobile Station Order/Message Response Substate.
21 • If this substate was entered with a registration indication, the mobile station shall
22 enter the Registration Access Substate.
23 • If this substate was entered with a message transmission indication, the mobile
24 station shall enter the Mobile Station Message Transmission Substate with a message
25 transmission indication.
26 • If this substate was entered with a PACA cancel indication, the mobile station shall
27 enter the PACA Cancel Substate.
28 2.6.3.3 Page Response Substate

29 In this substate, the mobile station sends a Page Response Message in response to a
30 General Page Message from a base station. If a base station responds to the Page Response
31 Message with an authentication request, the mobile station responds in this substate.
32 If a message received from the base station requires a Layer 2 acknowledgment and does
33 not require a Layer 3 response, Layer 3 shall indicate to Layer 2 that no response is
34 outstanding (see 2.1.1.2.2.1 of TIA/EIA/IS-2000-[4]).
35 If a message received from the base station requires a Layer 2 acknowledgment and also a
36 Layer 3 response, Layer 3 shall indicate to Layer 2 that a response is outstanding (see
37 2.1.1.2.2.1 of TIA/EIA/IS-2000-[4]).
38 When transmitting a response to a message received from the base station, Layer 3 shall
39 indicate to Layer 2 that the type of the message is a response (see 2.1.1.2.2.1 of
40 TIA/EIA/IS-2000-[4]).
2-111
C.S0005-0-2 v1.0
1 When transmitting an autonomous message (i.e., a message that is not sent as a response
2 to a message received from the base station), Layer 3 shall indicate to Layer 2 that the type
3 of the message is a request other than a registration request or a message transmission
4 request (see 2.1.1.2.2.1 of TIA/EIA/IS-2000-[4]).
5 In the Page Response Substate, the mobile station shall send each message in assured
6 mode requiring confirmation of delivery.
7 Upon entering the Page Response Substate, the mobile station shall set RLGAIN_ADJs to
8 ‘0000’ and send a Page Response Message.
9 While in this substate, the mobile station shall monitor the Paging Channel. The mobile
10 station may perform an access probe handoff or access handoff as described in 2.6.3.1.3.2
11 and 2.6.3.1.3.3. If the mobile station declares a loss of the Paging Channel (see
12 2.6.2.1.1.43.1.8) during an access attempt, the mobile station may perform an access probe
13 handoff; otherwise, it shall declare an access attempt failure and shall perform the following
14 actions:
15 • The mobile station shall update its registration variables as specified in 2.6.5.5.3.2,
16 • The mobile station shall set SYS_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL,
20 • The mobile station shall disable its transmitter, and

22 If the mobile station receives confirmation of delivery of any message sent by the mobile
23 station in this substate, the mobile station shall perform an access handoff if all of the
25 • The mobile station declares a loss of the Paging Channel, and
26 • The mobile station is permitted to perform an access handoff (see 2.6.3.1.3.2), and
27 there are pilots other than the active pilot in the access handoff list (see 2.6.3.1.3.2).
28 If the mobile station declares a loss of the Paging Channel and does not perform an access
29 handoff, the mobile station shall perform the following:
32 PACA_CANCEL to 0, shall disable the PACA state timer, and should indicate to the
33 user that the PACA call has been canceled,
34 • The mobile station shall disable its transmitter, and

2-112
C.S0005-0-2 v1.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 and shall enter the Mobile Station Idle State.
12 The mobile station shall set and disable the System Access State timer as follows:
13 • The mobile station shall disable the timer whenever it begins an access attempt.
14 • The mobile station shall set the timer to T42m seconds whenever it ends an access
15 attempt.
16 • The mobile station shall disable the timer whenever it exits the System Access State.
17 If the mobile station receives a Channel Assignment Message or the Extended Channel
18 Assignment Message, Layer 3 shall send a dedicated channel assignment indication to Layer
19 2 (see 2.1.2.1.2 of TIA/EIA/IS-2000-[4]). If the mobile station has not received confirmation
20 of delivery of the Page Response Message, before receiving the Channel Assignment Message
21 or the Extended Channel Assignment Message, the mobile station shall update its
22 registration variables with respect to the base station to which the first access probe was
23 transmitted after entering the System Access State, as specified in 2.6.5.5.3.1.
24 If the mobile station is to exit the System Access State as a result of processing Layer 3
25 fields of a message requiring an acknowledgment, the mobile station shall exit the System
26 Access State after Layer 3 receives an indication from Layer 2 that the acknowledgment to
27 the message has been sent and acknowledged.
28 If Layer 3 receives a message other than a Channel Assignment Message or an Extended

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

5 FRAME_OFFSETr), the message encryption mode indicator
6 (ENCRYPT_MODEs = ENCRYPT_MODEr), and, if FREQ_INCLr equals ‘1’, the
7 Frequency Assignment (CDMACHs = CDMA_FREQr).
8 − The mobile station shall set SERV_NEGs to disabled.
9 − If PACAs is equal to enabled, the mobile station shall set PACAs to disabled
10 and PACA_CANCEL to ‘0’, shall disable the PACA state timer, and should
12 − The mobile station shall initialize CODE_CHAN_LIST as described in 2.6.8.

13 − The mobile station shall enter the Traffic Channel Initialization Substate of
14 the Mobile Station Control on the Traffic Channel State.
16 actions:
17 − If FREQ_INCLr equals ‘1’, the mobile station shall perform the following:
18 + If the message requires acknowledgement, the mobile station shall

19 wait until Layer 3 receives an indication from Layer 2 that the
20 acknowledgement to the message has been sent and acknowledged.
21 + The mobile station shall set CDMACHs to CDMA_FREQr, tune to the
22 new Frequency Assignment, and measure the strength of each pilot
23 listed in the assignment using the Neighbor Set search procedures
24 specified in 2.6.6.2.1 and 2.6.6.2.2.
25
26 − The mobile station shall set CONFIG_MSG_SEQs and ACC_MSG_SEQs to

29 − If the mobile station has not stored configuration parameters for the Primary
33 GEN_NGHBR_LIST_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
34 PRI_NGHBR_LST_MSG_SEQs, CHAN_LST_MSG_SEQs,
38 to NULL.
2-114
C.S0005-0-2 v1.0
1 − The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the Primary
2 Paging Channel. The mobile station shall then begin monitoring the Primary
3 Paging Channel of the selected base station.
4 − If RESPONDr is equal to ‘1’, the mobile station shall enter the Update
5 Overhead Information Substate with a page response retransmission
6 indication within T34m seconds after receiving the Channel Assignment
7 Message.
8 − If RESPONDr is equal to ‘0’, the mobile station shall enter the Mobile Station
9 Idle State within T34m seconds after receiving the Channel Assignment
10 Message.
12 actions:
13 − If the mobile station does not support analog operation in the requested
14 band class, the mobile station shall send a Mobile Station Reject Order with
15 ORDQ field set to ‘00000110’ (capability not supported by the mobile station)
16 and shall remain in the Page Response Substate.
17 − If the mobile station supports analog operation in the requested band class,
18 the mobile station shall perform the following actions:
19 + If USE_ANALOG_SYSr equals ‘1’, the mobile station shall set SERVSYSs
20 to SYS_A if ANALOG_SYSr is equal to ‘0’, or shall set SERVSYSs to SYS_B
21 if ANALOG_SYSr is equal to ‘1’.
22 + If PACAs is equal to enabled, the mobile station shall set PACAs to

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

2 2.6.8 and shall then enter the Traffic Channel Initialization Substate of
5 actions:
6 + If the band class is not supported by the mobile station, the mobile
7 station shall send a Mobile Station Reject Order with ORDQ field set to
8 ‘00000110’ (capability not supported by the mobile station) and shall
9 remain in the Page Response Substate.
10 + If the band class is supported by the mobile station, the mobile station
12 ο The mobile station shall store the frame offset (FRAME_OFFSETs =
14 (ENCRYPT_MODEs = ENCRYPT_MODEr), the bypass indicator
15 (BYPASS_ALERT_ANSWERs = BYPASS_ALERT_ANSWERr), the
16 granted mode (GRANTED_MODEs = GRANTED_MODEr), the default
17 configuration (DEFAULT_CONFIGs = DEFAULT_CONFIGr), the band
18 class (CDMABANDs = BAND_CLASSr), and the Frequency Assignment
19 (CDMACHs = CDMA_FREQr).
20 ο The mobile station shall initialize CODE_CHAN_LIST as described in

21 2.6.8, and shall set SERV_NEGs to enabled.
22 ο The mobile station shall then tune to the new Frequency Assignment
23 and shall enter the Traffic Channel Initialization Substate of the Mobile
24 Station Control on the Traffic Channel State.
26 actions:
28 actions:
29 + If the message requires acknowledgement, the mobile station shall wait

30 until Layer 3 receives an indication from Layer 2 that the
32 + The mobile station shall set CONFIG_MSG_SEQs and ACC_MSG_SEQs to
33 NULL (see 2.6.2.2) and shall set PILOT_PNs to the pilot PN sequence
34 offset of the strongest pilot in the list (PILOT_PNr).
2-117
C.S0005-0-2 v1.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
9 PRI_NGHBR_LST_MSG_SEQs, GLOB_SERV_REDIR_MSG_SEQs, and
10 EXT_GLOB_SERV_REDIR_MSG_SEQs to NULL.
11 + The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the
12 Primary Paging Channel. The mobile station shall then begin monitoring
14 + If RESPONDr is equal to ‘1’, the mobile station shall perform the
15 following:
16 ο Ιf the Channel Assignment Message does not require an
17 acknowledgment, the mobile station shall enter the Update Overhead
18 Information Substate with a page response retransmission indication
19 within T34m seconds after receiving the Channel Assignment
20 Message.
21 ο Ιf the Channel Assignment Message requires an acknowledgment, the

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

34 mobile station shall enter the Mobile Station Idle State within T34m
35 seconds after Layer 3 receives an indication from Layer 2 that the
39 actions:
2-118
C.S0005-0-2 v1.0
3 ‘00000110’ (capability not supported by the mobile station) and shall
4 remain in the Page Response Substate.
7 ο If the message requires acknowledgement, the mobile station shall

10 ο The mobile station shall set CDMACHs to CDMA_FREQr and
11 CDMABANDs to BAND_CLASSr. Then the mobile station shall tune
12 to the new Frequency Assignment, measure the strength of each pilot
14 specified in 2.6.6.2.1 and 2.6.6.2.2, set PILOT_PNs to the pilot PN
15 sequence offset of the strongest pilot in the list (PILOT_PNr), and set
16 CONFIG_MSG_SEQs and ACC_MSG_SEQs to NULL (see 2.6.2.2).
17 ο If the mobile station has not stored configuration parameters for the
21 EXT_NGHBR_LST_MSG_SEQs, GEN_NGHBR_LIST_MSG_SEQs,
27 ο The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the
28 Primary Paging Channel. The mobile station shall then begin
29 monitoring the Primary Paging Channel of the selected base station.
30 ο If RESPONDr is equal to ‘1’, the mobile station shall perform the
31 following:
32 ◊ If the Channel Assignment Message does not require an
33 acknowledgment, the mobile station shall enter the Update
34 Overhead Information Substate with a page response
35 retransmission indication within T34m seconds after receiving the
36 Channel Assignment Message.
37 ◊ Ιf the Channel Assignment Message requires an acknowledgment,

38 the mobile station shall enter the Update Overhead Information
39 Substate with a page response retransmission indication within
40 T34m seconds after Layer 3 receives an indication from Layer 2
41 that the acknowledgement to the Channel Assignment Message
42 has been sent and acknowledged.
2-119
C.S0005-0-2 v1.0

2 following:
3 ◊ Ιf the Channel Assignment Message does not require an
4 acknowledgment, the mobile station shall enter the Mobile Station
5 Idle State within T34m seconds after receiving the Channel
6 Assignment Message .
8 the mobile station shall enter the Mobile Station Idle State within
16 actions:
22 configuration specified in the DEFAULT_CONFIG field are not supported by
23 the mobile station, the mobile station shall send a Mobile Station Reject Order
24 with ORDQ field set to ‘00000110’ (capability not supported by the mobile
25 station) and shall remain in the Page Response Substate.
26 − If GRANTED_MODEr is equal to ‘00’ and DEFAULT_CONFIGr is not equal to
27 ‘100’, the mobile station shall send a Mobile Station Reject Order with ORDQ
28 field set to ‘00001110’ (RC does not match with DEFAULT_CONFIGr) and
29 shall remain in the Page Response Substate if any of the following conditions
30 is true:
31 + FOR_FCH_RCr is not equal to the RC associated with
32 DEFAULT_CONFIGr (see Table 3.7.2.3.2.21-2).
33 + REV_FCH_RCr is not equal to the RC associated with DEFAULT_CONFIGr

34 (see Table 3.7.2.3.2.21-2).
35 − If the mobile station does not support either of the Fundamental Channel
36 Radio Configurations (FOR_FCH_RC or REV_FCH_RC), the mobile shall send
37 a Mobile Station Reject Order with the ORDQ field set to ‘00000110’
38 (capability not supported by the mobile station) and remain in the Page
39 Response Substate.
2-120
C.S0005-0-2 v1.0
1 − If P_REV_IN_USEs is equal to or greater than 6, the mobile station shall store

2 the Forward Fundamental Channel Radio Configuration (FOR_FCH_RCs =
3 FOR_FCH_RCr) and the Reverse Fundamental Channel Radio Configuration
4 (REV_FCH_RCs = REV_FCH_RCr).
6 actions:
8 FRAME_OFFSETr); the message encryption mode indicator
9 (ENCRYPT_MODEs = ENCRYPT_MODEr); the bypass indicator
10 (BYPASS_ALERT_ANSWERs = BYPASS_ALERT_ANSWERr); the granted
11 mode (GRANTED_MODEs = GRANTED_MODEr); the default configuration
12 (DEFAULT_CONFIGs = DEFAULT_CONFIGr); and the occurrences of
13 PILOT_PN and PWR_COMB for each included member of the Active Set.

16 + The mobile station shall set FPC_FCH_INIT_SETPTs to

17 FPC_FCH_INIT_SETPTr, FPC_FCH_CURR_SETPTs to
18 FPC_FCH_INIT_SETPTs, FPC_FCH_FERs to FPC_FCH_FERr,
19 FPC_FCH_MIN_SETPTs to FPC_FCH_MIN_SETPTr,
20 FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr, and FPC_PRI_CHANs
21 to ‘0’ if the mobile station supports any Radio Configuration greater than
22 2.
23 + The mobile station shall set FPC_SUBCHAN_GAINs to
24 FPC_SUBCHAN_GAINr.
25 + The mobile station shall set RLGAIN_ADJs to RLGAIN_ADJr.
26 + The mobile station shall set REV_FCH_GATING_MODEs to

27 REV_FCH_GATING_MODEr.
28 + The mobile station shall set REV_PWR_CNTL_DELAYs to

29 REV_PWR_CNTL_DELAYr if REV_PWR_CNTL_DELAY_INCLr is equal to
30 ‘1’.
31 + The mobile station shall then enter the Traffic Channel Initialization
32 Substate of the Mobile Station Control on the Traffic Channel State.
33 − If FREQ_INCLr equals ‘1’, and the band class is not supported by the mobile
34 station, the mobile station shall send a Mobile Station Reject Order with
37 − If FREQ_INCLr equals ‘1’, and the band class is supported by the mobile
38 station, the mobile station shall perform the following actions:
2-121
C.S0005-0-2 v1.0

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); the band class
7 (CDMABANDs = BAND_CLASSr); the Frequency Assignment
8 (CDMACHs = CDMA_FREQr); and the occurrences of PILOT_PN and
9 PWR_COMB_IND for each included member of the Active Set.
16 2.


23 REV_PWR_CNTL_DELAYr if REV_PWR_CNTL_DELAY_INCLr is equal to
24 ‘1’.

27 + The mobile station shall then tune to the new Frequency Assignment and
28 shall enter the Traffic Channel Initialization Substate of the Mobile Station
29 Control on the Traffic Channel State.
31 actions:
33 actions:

2-122
C.S0005-0-2 v1.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,
8 GEN_NGHBR_LIST_MSG_SEQs, USER_ZONE_ID_MSG_SEQs,
9 PRI_NGHBR_LST_MSG_SEQs CHAN_LST_MSG_SEQs,
12 GLOB_SERV_REDIR_MSG_SEQs, and
18 following:
19 ο Ιf the Extended Channel Assignment Message does not require an
22 within T34m seconds after receiving the Extended Channel
23 Assignment Message.
24 ο Ιf the Extended Channel Assignment Message requires an

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

38 State within T34m seconds after Layer 3 receives an indication from
39 Layer 2 that the acknowledgement to the Extended Channel
40 Assignment Message has been sent and acknowledged.
2-123
C.S0005-0-2 v1.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
31 following:

2-124
C.S0005-0-2 v1.0

2 following:

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).
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).
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).
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
40 actions:
2-125
C.S0005-0-2 v1.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 IS-91) 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-126
C.S0005-0-2 v1.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-127
C.S0005-0-2 v1.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).
8 − The mobile station shall store the Forward power control subchannel relative
9 gain [FPC_SUBCHAN_GAINs = FPC_SUBCHAN_GAINr).
10 − The mobile station shall set RLGAIN_ADJs to RLGAIN_ADJr.
11 − The mobile station shall set REV_FCH_GATING_MODEs to

13 − The mobile station shall set REV_PWR_CNTL_DELAYs to

14 REV_PWR_CNTL_DELAYr if REV_PWR_CNTL_DELAY_INCLr is equal to ‘1’.
15 − The mobile station shall store the channel indicator (CH_INDs = CH_INDr) and
17 + If CH_INDr equals ‘01’, the mobile station shall set FPC_FCH_INIT_SETPTs to
18 FPC_FCH_INIT_SETPTr, FPC_FCH_CURR_SETPTs to FPC_FCH_INIT_SETPTs,
19 FPC_FCH_FERs to FPC_FCH_FERr, FPC_FCH_MIN_SETPTs to
20 FPC_FCH_MIN_SETPTr, FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr,
21 and FPC_PRI_CHANs to ‘0’ if the mobile station supports any Radio
22 Configuration greater than 2. Then for each included member of the Active
23 Set, the mobile station shall store the following:
24 ο Set the PILOT_PN field to PILOT_PNr.
25 ο Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC_INCLr. If

26 ADD_PILOT_REC_INCLr equals ‘1’, the mobile station shall store the
27 following:
28 ◊ Set the PILOT_REC_TYPE field of PILOT_REC to PILOT_REC_TYPEr.
29 ◊ If PILOT_REC_TYPEr equals ‘000’, the mobile station shall set the

30 OTD_POWER_LEVEL field of PILOT_REC to OTD_POWER_LEVELr.
31 ο Set the PWR_COMB_IND field to PWR_COMB_INDr.
32 ο Set the CODE_CHAN_FCH field to CODE_CHAN_FCHr.
33 ο Set the QOF_MASK_ID_FCH field to QOF_MASK_ID_FCHr.
2-128
C.S0005-0-2 v1.0
1 + If CH_INDr equals ‘10’, the mobile station shall set FPC_DCCH_INIT_SETPTs

2 to FPC_DCCH_INIT_SETPTr, FPC_DCCH_CURR_SETPTs to
3 FPC_DCCH_INIT_SETPTs, FPC_DCCH_FERs to FPC_DCCH_FERr,
4 FPC_DCCH_MIN_SETPTs to FPC_DCCH_MIN_SETPTr,
5 FPC_DCCH_MAX_SETPTs to FPC_DCCH_MAX_SETPTr, and FPC_PRI_CHANs
6 to ‘1’ if the mobile station supports any Radio Configuration greater than 2.
7 Then for each included member of the Active Set, the mobile station shall
8 store the following:
9 ο Set the PILOT_PN to PILOT_PNr.
10 ο Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC_INCr. If

11 ADD_PILOT_REC_INCL is equal to ‘1’, the mobile station shall store the
12 following:

19 ο Set the DCCH_INCL field to DCCH_INCLr. If DCCH_INCLr equals ‘1’, the

20 mobile station shall store the following:
21 ◊ Set the CODE_CHAN_DCCH field to CODE_CHAN_DCCHr.
22 ◊ Set the QOF_MASK_ID_DCCH field to QOF_MASK_ID_DCCHr.
23 + If CH_INDr equals ‘11’, the mobile station shall set FPC_FCCH_INIT_SETPTs

24 to FPC_FCH_INIT_SETPTr, FPC_FCH_CURR_SETPTs to
26 FPC_FCH_MIN_SETPTs to FPC_FCH_MIN_SETPTr, FPC_FCH_MAX_SETPTs to
27 FPC_FCH_MAX_SETPTr, FPC_DCCH_INIT_SETPTs to
28 FPC_DCCH_INIT_SETPTr, FPC_DCCH_CURR_SETPTs to
29 FPC_DCCH_INIT_SETPTs, FPC_DCCH_FERs to FPC_DCCH_FERr,
30 FPC_DCCH_MIN_SETPTs to FPC_DCCH_MIN_SETPTr,
31 FPC_DCCH_MAX_SETPTs to FPC_DCCH_MAX_SETPTr and FPC_PRI_CHANs
32 to FPC_PRI_CHANr. Then for each included member of the Active Set, the
33 mobile station shall store the following:
35 ο Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC. If

36 ADD_PILOT_REC_INCL is equal to ‘1’, the mobile station shall store the
37 following:
2-129
C.S0005-0-2 v1.0

6 ο Set the CODE_CHAN_DCCH field to CODE_CHAN_DCCHr.
7 ο Set the QOF_MASK_ID_DCCH field to QOF_MASK_ID_DCCH.
8 − The mobile station shall initialize CODE_CHAN_LIST as described in 2.6.8, and

9 shall set SERV_NEGs to enabled.
10 − If FREQ_INCLr equals ‘1’, the mobile station shall then tune to the new
11 frequency assignment.
12 − The mobile station shall then enter the Traffic Channel Initialization Substate of
16 8. Lock Until Power-Cycled Order: The mobile station shall disable its transmitter and
17 record the reason for the Lock Until Power-Cycled Order in the mobile station’s semi-
18 permanent memory (LCKRSN_Ps-p equals the least significant four bits of ORDQr).
19 The mobile station should notify the user of the locked condition. The mobile
20 station shall enter the System Determination Substate of the Mobile Station
21 Initialization State with a lock indication (see 2.6.1.1), and shall not enter the System
22 Access State again until after the next mobile station power-up or until it has
23 received an Unlock Order. This requirement shall take precedence over any other
24 mobile station requirement specifying entry to the System Access State.
27 (MAINTRSNs-p equals the least significant four bits of ORDQr). The mobile station
28 shall remain in the unlocked condition. The mobile station should notify the user of
29 the maintenance required condition.
30 10. Registration Accepted Order: If ORDQr = ‘00000101’, the mobile station shall set
31 ROAM_INDIs = ROAM_INDIr and should display the roaming condition.
32 11. Registration Rejected Order: This order indicates that normal service is not available
33 on this system. The mobile station shall disable the full-TMSI timer. If the received
34 order specifies to delete the TMSI (ORDQ = ‘00000100’), the mobile station shall set
35 all the bits of the TMSI_CODEs-p to ‘1’. The mobile station shall enter the System
36 Determination Substate of the Mobile Station Initialization State with a registration
37 rejected indication (see 2.6.1.1).
38 12. Release Order: If NDSS_ORIGs is equal to enabled, the mobile station shall set
39 NDSS_ORIGs to disabled, and should indicate to the user that the call origination
2-130
C.S0005-0-2 v1.0
1 has been canceled. The mobile station shall enter the Mobile Station Idle State or the
2 System Determination Substate of the Mobile Station Initialization State with a release
3 indication (see 2.6.1.1). If the mobile station enters the Mobile Station Idle State,
4 and if PACAs is equal to enabled, the mobile station shall set PACAs to disabled and
9 RETRY_DELAYs[RETRY_TYPE] to 0, where RETRY_TYPE is equal to ‘001’, ‘010’,
10 or ‘011’.
12 − If RETRY_DELAYr is equal to ‘00000000’, then the mobile station shall set

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



25 follows:

29 mobile station).

39 15. SSD Update Message: The mobile station shall respond to the message as specified
40 in 2.3.12.1.5.
2-131
C.S0005-0-2 v1.0
1 16. Status Request Message: The mobile station shall disable the System Access State
2 timer and respond to the message. If P_REV_IN_USEs is less than or equal to three,
3 the mobile station shall respond with a Status Response Message. If
4 P_REV_IN_USEs is greater than three, the mobile station shall respond with an
5 Extended Status Response Message. If the message does not specify any
6 qualification information (QUAL_INFO_TYPEr is equal to ‘00000000’), the mobile
7 station shall include the requested information records in the response. If the
8 message specifies a band class (QUAL_INFO_TYPEr is equal to ‘00000001’), the
9 mobile station shall only include the requested information records for the specified
10 band class (BAND_CLASSr) in the response. If the message specifies a band class
11 and an operating mode (QUAL_INFO_TYPEr is equal to ‘00000010’), the mobile
12 station shall only include the requested information records for the specified band
13 class (BAND_CLASSr) and operating mode (OP_MODEr) in the response. If the
14 message specifies a band class or a band class and an operating mode which is not
15 supported by the mobile station, the mobile station shall send a Mobile Station Reject
16 Order with ORDQ set to ‘00000110’ (message requires a capability that is not
17 supported by the mobile station). If the response to this message exceeds the
18 allowable length, the mobile station shall send a Mobile Station Reject Order with
19 ORDQ set to ‘00001000’ (response message would exceed the allowable length). If
20 the message specifies an information record which is not supported by the mobile
21 station for the specified band class and operating mode, the mobile station shall
22 send a Mobile Station Reject Order with ORDQ set to ‘00001001’ (information record
23 is not supported for the specified band class and operating mode).
25 as follows:
27 ASSIGNING_TMSI_ZONE_LENs-p to TMSI_ZONE_LENr;
32 TMSI_CODEr.
38 19. Any other message: If the mobile station receives any other message specified in
39 Table 3.7.2.3-1, it shall ignore all Layer 3 fields. The mobile station shall ignore all
40 other messages.
41 If the mobile station performs an access probe handoff or access handoff and receives any
42 of the following messages, it shall process the message as specified in 2.6.3.1.3:
2-132
C.S0005-0-2 v1.0
1 1. System Parameters Message
2 2. Access Parameters Message
3 3. Neighbor List Message
4 4. Extended System Parameters Message
5 5. Extended Neighbor List Message
6 6. General Neighbor List Message
7 7. Global Service Redirection Message
8 8. Extended Global Service Redirection Message
9 2.6.3.4 Mobile Station Order/Message Response Substate
10 In this substate, the mobile station sends a message that is a response to a message
11 received from the base station. If the base station responds to the mobile station’s message
12 with an authentication request, the mobile station responds in this substate.
18 2.1.1.2.2.1 of TIA/EIA/IS-2000-[4]).
21 TIA/EIA/IS-2000-[4]).
26 In the Mobile Station Order/Message Response Substate, the mobile station shall send each
27 message in assured mode requiring confirmation of delivery.
28 Upon entering the Mobile Station Order/Message Response Substate, the mobile station
29 shall send the response message.
30 While in this substate, the mobile station shall monitor the Paging Channel. If the mobile
31 station declares a loss of the Paging Channel (see 2.6.2.1.1.4), the mobile station shall
2-133
C.S0005-0-2 v1.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
5 enter the Mobile Station Idle State.
12 If Layer 3 receives a message with an indication from Layer 2 that an access attempt for a
2-134
C.S0005-0-2 v1.0
10 or ‘011’.

13 RETRY_DELAYs[RETRY_TYPEr] to 0.



25 follows:

29 mobile station).

40 in 2.3.12.1.5.
2-135
C.S0005-0-2 v1.0
14 message specifies a band class or a band class and an operating mode which is not
25 as follows:
32 TMSI_CODEr.
39 other messages.
2-136
C.S0005-0-2 v1.0
1 2.6.3.5 Mobile Station Origination Attempt Substate
2 In this substate, the mobile station sends an Origination Message. If the base station
3 responds to the Origination Message with an authentication request, the mobile station
4 responds in this substate.
10 2.1.1.2.2.1 of TIA/EIA/IS-2000-[4]).
13 TIA/EIA/IS-2000-[4]).
18 In the Mobile Station Origination Attempt Substate, the mobile station shall send each
20 Upon entering the Mobile Station Origination Attempt Substate, the mobile station shall set
21 RLGAIN_ADJs to ‘0000’ and perform the following:
22 • If the substate was entered with an origination indication, the mobile station shall
23 send the Origination Message as an r-csch request.
24 • If the substate was entered with a PACA response indication, the mobile station
25 shall send the Origination Message as an r-csch response using the access
26 procedures specified in 2.6.3.1. The mobile station shall include the dialed digits
27 from the previous origination attempt in the Origination Message.
28 • If the origination is a result of NDSS_ORIGs being equal to enabled, the mobile
29 station shall include in the Origination Message the dialed digits recorded from the
30 previous origination attempt.
31 • The mobile station shall include in the Origination Message as many of the dialed
32 digits as possible without exceeding the message capsule size. When calculating the
33 number of dialed digits to be included in the Origination Message, the mobile station
34 shall assume the following if P_REV_IN_USEs is greater than three:
35 − The number of additional reported pilots (NUM_ADD_PILOTS) is equal to five (see

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

39 equal to the maximum alternative service option numbers (MAX_NUM_ALT_SOs).
2-137
C.S0005-0-2 v1.0
1 • If PACAs is equal to enabled, the mobile station shall set the PACA_REORIG field of
2 the Origination Message to ‘1’; otherwise, the mobile station shall set the field to ‘0’.
3 While in this substate, the mobile station shall monitor the Paging Channel. The mobile
4 station may perform an access probe handoff or an access handoff as described in
5 2.6.3.1.3.2 and 2.6.3.1.3.3. If the mobile station declares a loss of the Paging Channel (see
6 2.6.2.1.1.43.1.8) during an access attempt, the mobile station may perform an access probe
7 handoff; otherwise, it shall declare an access attempt failure and shall perform the
8 following:
9 • The mobile station shall set SYS_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL.
13 • If NDSS_ORIGs is equal to enabled, the mobile station shall set NDSS_ORIGs to
14 disabled, and should indicate to the user that the call origination is canceled.
15 • The mobile station shall update its registration variables as specified in 2.6.5.5.3.2.
16 • The mobile station shall disable its transmitter and enter the Mobile Station Idle
17 State.
19 station in this substate, the mobile station shall perform an access handoff if all of the
21 • The mobile station declares a loss of the Paging Channel,
22 • The mobile station is permitted to perform an access handoff (see 2.6.3.1.3.2) and
23 there are pilots other than the active pilot in the access handoff list (see 2.6.3.1.3.2).
24 If the mobile station declares a loss of the Paging Channel and does not perform an access
25 handoff, the mobile station shall perform the following:
26 • The mobile station shall set SYS_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL.
33 State.
34 If the mobile station receives confirmation of delivery of the Origination Message, the mobile
35 station shall update its registration variables with respect to the base station to which the
36 first access probe was transmitted after entering the System Access State as specified in
37 2.6.5.5.3.1.
38 The mobile station shall set and disable the System Access State timer as follows:
2-138
C.S0005-0-2 v1.0
1 • The mobile station shall disable the timer whenever it begins an access attempt.
2 • The mobile station shall set the timer to T42m seconds whenever it ends an access
3 attempt.
4 • The mobile station shall disable the timer whenever it exits the System Access State.
12 • The mobile station shall set SYS_PAR_MSG_SEQs and ACC_MSG_SEQs to NULL and
14 If the mobile station is directed by the user to disconnect the call, the mobile station shall
16 • Layer 3 shall send an L2-Supervision.Request primitive to Layer 2 to abort any

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

26 • The mobile station shall send a Release Order (with power-down indication).
27 • After receiving confirmation of delivery of the Release Order, the mobile station shall
28 perform power-down registration procedures (see 2.6.5.1.2).
29 • The mobile station may power off.

30 If the mobile station receives a Channel Assignment Message or the Extended Channel
31 Assignment Message, Layer 3 shall send a dedicated channel assignment indication to Layer
32 2 (see 2.1.2.1.2 of TIA/EIA/IS-2000-[4]). If the mobile station has not received confirmation
33 of delivery of the Origination Message before receiving the Channel Assignment Message or
34 the Extended Channel Assignment Message, the mobile station shall update its registration
35 variables with respect to the base station to which the first access probe was transmitted
36 after entering the System Access State, as specified in 2.6.5.5.3.1.
2-139
C.S0005-0-2 v1.0
3 If Layer 3 receives a message other than a Channel Assignment Message or an Extended

4 Channel Assignment Message with an indication from Layer 2 that an access attempt for a
15 follows:
17 actions:

21 (ENCRYPT_MODEs = ENCRYPT_MODEr), and, if FREQ_INCLr equals ‘1’, the
22 Frequency Assignment (CDMACHs = CDMA_FREQr).
25 indicate to the user that the PACA call is proceeding.
26 − The mobile station shall initialize the CODE_CHAN_LIST as described in

27 2.6.8, shall set SERV_NEGs to disabled, and shall enter the Traffic Channel
28 Initialization Substate of the Mobile Station Control on the Traffic Channel
29 State.
31 actions:
32 − If the message requires acknowledgement, the mobile station shall wait until
35 − If a CDMA channel (CDMA_FREQ) is specified in the assignment, the mobile

36 station shall set CDMACHs = CDMA_FREQr, tune to the new Frequency
37 Assignment, and measure the strength of each pilot listed in the assignment
39 2.6.6.2.2.
2-140
C.S0005-0-2 v1.0
1 − The mobile station shall set CONFIG_MSG_SEQs and ACC_MSG_SEQs to

3 the strongest pilot in the list.
4 − If the mobile station has not stored configuration parameters for the Primary
10 USER_ZONE_ID_MSG_SEQs, PRI_NGHBR_LIST_MSG_SEQs,
12 to NULL.
13 − The mobile station shall set PAGE_CHANs to ‘1’ and PAGECHs to the Primary
14 Paging Channel. The mobile station shall then begin monitoring the Primary
15 Paging Channel of the selected base station.
16 − If RESPONDr is equal to ‘1’, the mobile station shall enter the Update
17 Overhead Information Substate with an origination indication.
19 actions:
20 – If the mobile station does not support analog operation in the requested
22 the ORDQ field set to ‘00000110’ (capability not supported by the mobile
23 station) and the mobile station shall remain in the Mobile Station Origination
24 Attempt Substate.
25 − If the mobile station supports analog operation in the requested band class
26 and RESPONDr equals ‘1’, the mobile station shall perform the following
27 actions:
28 + If USE_ANALOG_SYSr equals ‘0’, the mobile station shall perform the
29 following actions:
30 ο If PACAs is equal to enabled, the mobile station shall set PACAs to
33 ο The mobile station shall enter the analog Initialization Task with an
34 origination indication (see 2.6.1).
35 + If USE_ANALOG_SYSr equals ‘1’ the mobile station shall perform the
37 ο The mobile station shall set SERVSYSs to SYS_A if ANALOG_SYSr is
38 equal to ‘0’, or shall set SERVSYSs to SYS_B if ANALOG_SYSr is equal
39 to ‘1’.
2-141
C.S0005-0-2 v1.0

4 ο The mobile station shall then enter the analog Initialization Task with
5 an origination indication (see 2.6.1).
7 actions:
13 − If the mobile station supports analog operation in the requested band class:
14 + If the analog channel type is ‘00’, the mobile station shall perform the
16 ο The mobile station shall store the system identification (SIDs = SIDr),
17 the voice mobile station attenuation code (VMACs = VMACr), the voice
18 channel number (ANALOG_CHANs = ANALOG_CHANr), the SAT color
19 code (SCCs = SCCr), and the message encryption mode indicator
20 (MEMs = MEMr).
21 ο The mobile station shall set DTXs to ‘00’.

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

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

16 configuration specified in the DEFAULT_CONFIG field is not supported by
19 station) and remain in Mobile Station Origination Attempt Substate.
21 actions:
25 (GRANTED_MODEs = GRANTED_MODEr), and the default configuration
26 (DEFAULT_CONFIGs = DEFAULT_CONFIGr).
28 + If PACAs is equal to enabled, the mobile station shall set PACAs equal to

32 2.6.8.
36 actions:
39 ‘00000110’ (capability not supported by the mobile station) and remain in
40 the Mobile Station Origination Attempt Substate.
2-143
C.S0005-0-2 v1.0
6 (GRANTED_MODEs = GRANTED_MODEr), the default configuration
7 (DEFAULT_CONFIGs = DEFAULT_CONFIGr), the band class
8 (CDMABANDs = BAND_CLASSr), and the Frequency Assignment
9 (CDMACHs = CDMA_FREQr).
10 ο The mobile station shall set SERV_NEGs to enabled.

14 ο The mobile station shall initialize the CODE_CHAN_LIST as described

15 in 2.6.8.
17 and enter the Traffic Channel Initialization Substate of the Mobile
20 actions:
22 actions:

2-144
C.S0005-0-2 v1.0

2 following:
6 within T34m seconds after receiving the Channel Assignment
7 Message.

9 mobile station shall enter the Update Overhead Information Substate
10 with a page response retransmission indication within T34m seconds
11 after Layer 3 receives an indication from Layer 2 that the
15 following:
18 State within T34m seconds after receiving the Channel Assignment
19 Message.

21 mobile station shall enter the Mobile Station Idle State within T34m
22 seconds after Layer 3 receives an indication from Layer 2 that the
26 actions:

2-145
C.S0005-0-2 v1.0

21 following:.

28 the mobile station shall enter the Update Overhead Information
29 Substate with a page response retransmission indication within
34 following:
36 acknowledgment, the mobile station shall enter the Mobile Station
37 Idle State within T34m seconds after receiving the Channel
2-146
C.S0005-0-2 v1.0

2 the mobile station shall enter the Mobile Station Idle State within
10 actions:
12 − If P_REV_IN_USEs is equal to or greater than six, the mobile station shall

13 store the Forward Fundamental Channel Radio Configuration
14 (FOR_FCH_RCs = FOR_FCH_RCr) and the Reverse Fundamental Channel
15 Radio Configuration (REV_FCH_RCs = REV_FCH_RCr)
17 actions:
21 (GRANTED_MODEs = GRANTED_MODEr), the default configuration
22 (DEFAULT_CONFIGs = DEFAULT_CONFIGr), and the occurrences of
23 PILOT_PN and PWR_COMB for each included member of the Active Set.
25 + If PACAs is equal to enabled, the mobile station shall set PACAs equal to

29 2.6.8.
36 2.
2-147
C.S0005-0-2 v1.0


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.
23 ο The mobile station shall set SERV_NEGs to enabled.
24 ο The mobile station shall initialize CODE_CHAN_LIST as described in

25 2.6.8.
26 ο The mobile station shall set FPC_FCH_INIT_SETPTs to
30 FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr, and
31 FPC_PRI_CHANs to ‘0’ if the mobile station supports any Radio
32 Configuration greater than 2.
33 ο The mobile station shall set FPC_SUBCHAN_GAINs to
35 ο The mobile station shall set RLGAIN_ADJs to RLGAIN_ADJr.

38 ο The mobile station shall set REV_PWR_CNTL_DELAYs to

39 REV_PWR_CNTL_DELAYr if REV_PWR_CNTL_DELAY_INCLr is equal
40 to ‘1’.
2-148
C.S0005-0-2 v1.0
2 and enter the Traffic Channel Initialization Substate of the Mobile
5 configuration specified in the DEFAULT_CONFIG field is not supported by
8 station) and 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 the
11 ORDQ field set to ‘00001110’ (RC does not match with DEFAULT_CONFIGr)
12 and shall remain in the Mobile Station Origination Attempt Substate if any of
13 the following conditions is true:
14 + FOR_FCH_RCr is not equal to the Radio Configuration associated with
16 + REV_FCH_RCr is not equal to the Radio Configuration associated with

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

30 + The mobile station shall set CONFIG_MSG_SEQs and ACC_MSG_SEQs
31 to NULL (see 2.6.2.2) and shall set PILOT_PNs to the pilot PN sequence
2-149
C.S0005-0-2 v1.0
5 following:

18 following:

29 actions:

2-150
C.S0005-0-2 v1.0

21 following:
22 ◊ Ιf the Extended Channel Assignment Message does not require an
26 Extended Channel Assignment Message.
27 ◊ Ιf the Extended Channel Assignment Message requires an

30 retransmission indication within T34m seconds after Layer 3
31 receives an indication from Layer 2 that the acknowledgement to
32 the Extended Channel Assignment Message has been sent and
33 acknowledged.
35 actions:
39 and remain in the Mobile Station Origination Attempt Substate.
2-151
C.S0005-0-2 v1.0
1 + If RESPONDr equals ‘1’ and USE_ANALOG_SYSr equals ‘0’, the mobile

2 station shall enter the analog Initialization Task with an origination
4 + If RESPONDr equals ‘1’ and USE_ANALOG_SYSr equals ‘1’, the mobile
5 station shall perform the following actions:
6 ο The mobile station shall set SERVSYSs to SYS_A if ANALOG_SYSr is
7 equal to ‘0’, or set SERVSYSs to SYS_B if ANALOG_SYSr is equal to
8 ‘1’.
9 ο The mobile station shall then enter the analog Initialization Task with
10 an origination indication (see 2.6.1).
12 actions:
20 + If the analog channel type is ‘00’, the mobile station shall perform the
22 ο The mobile station shall store the system identification (SIDs = SIDr),
23 voice mobile station attenuation code (VMACs = VMACr), voice
24 channel number (ANALOG_CHANs = ANALOG_CHANr), SAT color
25 code (SCCs = SCCr), and message encryption mode indicator (MEMs =
26 MEMr).
27 ο The mobile station shall set DTXs to ‘00’.

31 ο The mobile station shall enter the Confirm Initial Voice Channel Task
32 (see 2.6.4.2) with an origination indication.
33 + If the analog channel type is not ‘00’, the mobile station shall perform the
35 ο If the mobile supports narrow analog mode, the mobile station shall
2-152
C.S0005-0-2 v1.0
1 ◊ The mobile station shall store the system identification (SIDs =

2 SIDr), voice mobile station attenuation code (VMACs = VMACr),
3 voice channel number (ANALOG_CHANs = ANALOG_CHANr),
4 message encryption mode indicator (MEMs = MEMr), analog
5 channel type (AN_CHAN_TYPEs = AN_CHAN_TYPEr) and the
6 digital SAT code (DSCCs = DSCC_MSBr × 4 + SCCr).
7 ◊ The mobile station shall set DTXs to ‘00’.
8 ◊ If PACAs is equal to enabled, the mobile station shall set PACAs to

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

38 DEFAULT_CONFIGr as specified in Table 3.7.2.3.2.21-2.
2-153
C.S0005-0-2 v1.0
1 − If the mobile station does not support either of the Radio Configurations
2 (FOR_RC or REV_RC), the mobile station shall send a Mobile Station Reject
3 Order with the ORDQ field set to ‘00000110’ (capability not supported by the
4 mobile station) and remain in the Mobile Station Origination Attempt Substate.
5 − If CH_INDr = ‘01’ and the mobile station does not support the Fundamental
7 ORDQ field set to ‘00000110’ (capability not supported by the mobile
8 station) and remain in the Mobile Station Origination Attempt Substate.
9 − If CH_INDr = ‘10’ and the mobile station does not support the Dedicated
10 Control Channel, the mobile station shall send a Mobile Station Reject Order
11 with the ORDQ field set to ‘00000110’ (capability not supported by the
12 mobile station) and remain in the Mobile Station Origination Attempt Substate.
13 − If CH_INDr = ‘11’ and the mobile station does not support the Dedicated
14 Control Channel and Fundamental Channel concurrently, the mobile station
15 shall send a Mobile Station Reject Order with the ORDQ field set to
18 − If FREQ_INCLr equals ‘1’ and if the band class (BAND_CLASSr) is not
19 supported by the mobile station, the mobile station shall send a Mobile
20 Station Reject Order with ORDQ field set to ‘00000110’ (capability not
21 supported by the mobile station) and remain in the Mobile Station Origination
23 − If the mobile station does not send a Mobile Station Reject Order as specified
24 above, it shall continue to perform the actions specified below.
25 − If FREQ_INCLr equals ‘1’, the mobile station shall set
26 + CDMABANDs = BAND_CLASSr
27 + CDMACHs = CDMA_FREQr
28 − The mobile station shall store the bypass indicator

29 (BYPASS_ALERT_ANSWERs = BYPASS_ALERT_ANSWERr).
30 − The mobile station shall store granted mode (GRANTED_MODEs =

31 GRANTED_MODEr )
32 − The mobile station shall store the default configuration (DEFAULT_CONFIGs

33 = DEFAULT_CONFIGr).
34 − The mobile station shall store the Forward Traffic Channel Radio
35 Configuration (FOR_RCs = FOR_RCr) and the Reverse Traffic Channel Radio
36 Configuration (REV_RCs = REV_RCr).

38 FRAME_OFFSETr).
39 − The mobile station shall store the message encryption mode indicator
40 (ENCRYPT_MODEs = ENCRYPT_MODEr).
2-154
C.S0005-0-2 v1.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

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

20 ADD_PILOT_REC_INCr equals ‘1’, the mobile station shall store the
21 following:
22 ◊ Set the PILOT_REC_TYPE field of PILOT_REC to

23 PILOT_REC_TYPEr.

25 OTD_POWER_LEVEL field of PILOT_REC to
26 OTD_POWER_LEVELr.

31 FPC_DCCH_INIT_SETPTs to FPC_DCCH_INIT_SETPTr,
32 FPC_DCCH_CURR_SETPTs to FPC_ DCCH_INIT_SETPTs,
33 FPC_DCCH_FERs to FPC_DCCH_FERr, FPC_DCCH_MIN_SETPTs to
34 FPC_DCCH_MIN_SETPTr, FPC_DCCH_MAX_SETPTs to
35 FPC_DCCH_MAX_SETPTr, and FPC_PRI_CHANs to ‘1’ if the mobile station
36 supports any Radio Configuration greater than 2. Then for each included
37 member of the Active Set, the mobile station shall store the following:
2-155
C.S0005-0-2 v1.0
1 ο Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC_INCL. If

2 ADD_PILOT_REC_INCL is equal to ‘1’, the mobile station shall store
3 the following:

5 PILOT_REC_TYPEr.

8 OTD_POWER_LEVELr.
12 ο Set the DCCH_INCL field to DCCH_INCLr. If DCCH_INCLr equals ‘1’,

13 the mobile station shall store the following:
14 ◊ Set the CODE_CHAN_DCCH field to CODE_CHAN_DCCHr.
15 ◊ Set the QOF_MASK_ID_DCCH field to QOF_MASK_ID_DCCHr.

17 FPC_FCCH_INIT_SETPTs to FPC_FCH_INIT_SETPTr,
18 FPC_FCH_CURR_SETPTs to FPC_FCH_INIT_SETPTs, FPC_FCH_FERs to
19 FPC_FCH_FERr, FPC_FCH_MIN_SETPTs to FPC_FCH_MIN_SETPTr,
20 FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr,
21 FPC_DCCH_INIT_SETPTs to FPC_DCCH_INIT_SETPTr,
22 FPC_DCCH_CURR_SETPTs to FPC_DCCH_INIT_SETPTs,
23 FPC_DCCH_FERs to FPC_DCCH_FERr, FPC_DCCH_MIN_SETPTs to
24 FPC_DCCH_MIN_SETPTr, FPC_DCCH_MAX_SETPTs to
25 FPC_DCCH_MAX_SETPTr and FPC_PRI_CHANs to FPC_PRI_CHANr.
26 Then for each included member of the Active Set, the mobile station shall
27 store the following:
29 ο Set the ADD_PILOT_REC_INCL field to ADD_PILOT_REC. If

30 ADD_PILOT_REC_INCL is equal to ‘1’, the mobile station shall store
31 the following:

33 PILOT_REC_TYPEr.

37 ο Set the PWR_COMB_IND field to PWR_COMB_INDr
2-156
C.S0005-0-2 v1.0
1 ο Set the CODE_CHAN_DCCH field to CODE_CHAN_DCCHr.
2 ο Set the QOF_MASK_ID_DCCH field to QOF_MASK_ID_DCCHr.
3 − The mobile station shall initialize CODE_CHAN_LIST as described in 2.6.8,

4 and shall set SERV_NEGs to enabled.
5 − If FREQ_INCLr equals ‘1’, the mobile station shall then tune to the new
6 frequency assignment.
7 − The mobile station shall then enter the Traffic Channel Initialization Substate
8 of the Mobile Station Control on the Traffic Channel State.
9 6. Feature Notification Message: If RELEASEr is equal to ‘1’, the mobile station shall
10 enter the Mobile Station Idle State or the System Determination Substate of the Mobile
11 Station Initialization State with a release indication (see 2.6.1.1).
12 7. Intercept Order: The mobile station shall enter the Mobile Station Idle State.
28 11. PACA Message: If P_REV_IN_USEs is less than or equal to four and the mobile
33 • If PACAs is equal to disabled, the mobile station shall perform the following
34 actions:
35 − If the purpose of the message is to respond to an Origination Message
36 (PURPOSEr is equal to ‘0000’), the mobile station shall perform the following
37 actions:
38 + The mobile station shall set PACAs to enabled and shall set PACA_SIDs to
39 SIDs.
2-157
C.S0005-0-2 v1.0
1 + The mobile station shall set the PACA state timer to the duration shown
2 in Table 3.7.2.3.2.20-2 corresponding to the value of PACA_TIMEOUTs.
3 + The mobile station should indicate to the user that the call has been
4 queued as a PACA call, and should indicate the current queue position
5 (Q_POSr) of the call.
6 + The mobile station shall enter the Mobile Station Idle State.
7 − If the purpose of the message is to cancel the PACA call (PURPOSEr is equal
8 to ‘0011’), the mobile station shall perform the following actions:
9 + The mobile station shall set PACAs to disabled and PACA_CANCEL to ‘0’,
10 shall disable the PACA state timer, and should indicate to the user that
11 the PACA call has been canceled.
13 − If the purpose of the message is anything else (PURPOSEr is not equal to
14 ‘0000’ or ‘0011’), the mobile station shall ignore the message. The mobile
15 station shall remain in the Mobile Station Origination Attempt Substate.
16 • If PACAs is equal to enabled, the mobile station shall perform the following
17 actions:
18 − If the purpose of the message is to respond to an Origination Message
19 (PURPOSEr is equal to ‘0000’), the mobile station shall perform the following
20 actions:
21 + The mobile station should indicate to the user that the PACA call is still
22 queued, and should indicate to the user the current queue position
23 (Q_POSr) of the call.
27 − If the purpose of the message is to provide the queue position of the PACA
28 call (PURPOSEr is equal to ‘0001’), the mobile station shall perform the
30 + The mobile station should indicate to the user that the PACA call is still
31 queued, and should indicate the current queue position (Q_POSr) of the
32 call.
36 − If the purpose of the message is to instruct the mobile station to re-originate

37 the PACA call (PURPOSEr is equal to ‘0010’), the mobile station shall remain
38 in the Mobile Station Origination Attempt Substate.
2-158
C.S0005-0-2 v1.0
1 − If the purpose of the message is to cancel the PACA call (PURPOSEr is equal
2 to ‘0011’), the mobile station shall perform the following actions:
3 + The mobile station shall set PACAs to disabled, shall disable the PACA
4 state timer, and should indicate to the user that the PACA call has been
5 canceled.
7 12. Registration Accepted Order: If ORDQr is equal to ‘00000101’, the mobile station
8 shall set ROAM_INDIs to ROAM_INDIr and should display the roaming condition.
19 indication (see 2.6.1.1). If the mobile station enters the Mobile Station Idle State, and
20 if PACAs is equal to enabled, the mobile station shall set PACAs to disabled and
23 15. Reorder Order: If NDSS_ORIGs is equal to enabled, the mobile station shall set
25 has been canceled. If PACAs is equal to enabled, the mobile station shall set PACAs
26 to disabled and PACA_CANCEL to ‘0’, shall disable the PACA state timer, and should
27 indicate to the user that the PACA call has been canceled. The mobile station shall
29 16. Retry Order: The mobile station shall process the order as follows:
32 or ‘011’.
33 • If RETRY_TYPEr is equal to ‘001’, then the mobile station shall perform the
34 following:
37 − If RETRY_DELAYr is not equal to ‘00000000’ the mobile station shall set

38 RETRY_DELAYs as follows:
2-159
C.S0005-0-2 v1.0
1 + If the most significant bit of the RETRY_DELAYr is 0, set


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 follows:

21 mobile station).
22 • If DELETE TMSIr is equal to ‘1’, the mobile station shall set all the bits of
24 • The mobile station shall disable the full-TMSI timer.

26 • If RECORD_TYPEr is ‘00000000’, the mobile station shall set RETURN_IF_FAILs

27 = RETURN_IF_FAILr, and enter the System Determination Substate of the Mobile
28 Station Initialization State with an NDSS off indication (see 2.6.1.1); otherwise:
29 – if REDIRECT_TYPEr is ‘0’, the mobile station shall store the redirection
30 record received in the message as REDIRECT_RECs and shall enter the
31 System Determination Substate of the Mobile Station Initialization State with
32 a redirection indication (see 2.6.1.1).
33 − if REDIRECT_TYPEr is ‘1’, the mobile station shall store the redirection
34 record received in the message as REDIRECT_RECs and shall enable
35 NDSS_ORIGs, and shall record the dialed digits. The mobile station shall
36 enter the System Determination Substate of the Mobile Station Initialization
37 State with a redirection indication (see 2.6.1.1).
39 in 2.3.12.1.5.
2-160
C.S0005-0-2 v1.0
14 message specifies a band class or a band class and an operating mode which are not
25 as follows:
32 TMSI_CODEr.
40 other messages.
41 If the mobile station performs an access probe handoff or access handoff and receives any
42 of the following messages, it shall process the message as specified in 2.6.3.1.3:
2-161
C.S0005-0-2 v1.0
3 3. Neighbor List Message
5 5. Extended Neighbor List Message
9 2.6.3.6 Registration Access Substate

10 In this substate, the mobile station sends a Registration Message. If the base station
11 responds with an authentication request, the mobile station responds in this substate.
12 Upon entering the Registration Access Substate, the mobile station shall send the
13 Registration Message.
19 2.1.1.2.2.1 of TIA/EIA/IS-2000-[4]).
22 TIA/EIA/IS-2000-[4]).
24 to a message received from the base station) other than the Registration Message, Layer 3
25 shall indicate to Layer 2 that the type of the message is a request other than a registration
26 request or a message transmission request (see 2.1.1.2.2.1 of TIA/EIA/IS-2000-[4]).
27 When transmitting an autonomous Registration Message (i.e., it is not sent as a response to
28 a Registration Request Order received from the base station), Layer 3 shall indicate to Layer
29 2 that the type of the message is a request that is a registration (see 2.1.1.2.2.1 of
30 TIA/EIA/IS-2000-[4]).
31 In the Registration Access Substate, the mobile station shall send each message in assured
32 mode requiring confirmation of delivery.
34 station declares a loss of the Paging Channel (see 2.6.2.1.1.43.1.8), the mobile station shall
2-162
C.S0005-0-2 v1.0
4 State.
6 station in this substate, it shall then enter the Mobile Station Idle State unless:
7 • If the registration access was initiated due to a user direction to power down, the
8 mobile station shall update registration variables as specified in 2.6.5.5.3.3 and may
9 power down.
10 • If the message requires a response, the mobile station shall send a response to the
11 message in this substate.
12 If the mobile station receives confirmation of delivery of the Registration Message, the
13 mobile station shall update its registration variables as specified in 2.6.5.5.3.1.
14 If the mobile station is directed by the user to originate a call, the mobile station may
15 process the origination request as follows:

21 • The mobile station shall enter the Mobile Station Origination Attempt Substate with
22 an origination indication.
25 If the mobile station receives a General Page Message, the mobile station may determine if
26 there is a page match (see 2.6.2.3). If a match is declared, the mobile station shall perform
27 the following:

30 • The mobile station shall enter the Page Response Substate.
2-163
C.S0005-0-2 v1.0
4 1. Authentication Challenge Message: If the registration access was initiated due to a

5 user direction to power down, the mobile station shall ignore the message;
6 otherwise, the mobile station shall respond to the message as specified in
7 2.3.12.1.4, regardless of the value of AUTHs.
8 2. Base Station Challenge Confirmation Order: If the registration access was initiated
9 due to a user direction to power down, the mobile station shall ignore the message;
10 otherwise, the mobile station shall respond to the message as specified in
11 2.3.12.1.5.
34 If PACAs is equal to disabled, the mobile station shall send a Mobile Station Reject
35 Order with the ORDQ field set to ‘00000010’ (message not accepted in this state).
37 • If the purpose of the message is to respond to an Origination Message

38 (PURPOSEr is equal to ‘0000’), the mobile station shall send a Mobile Station
39 Reject Order with the ORDQ field set to ‘00000010’ (message not accepted in this
40 state).
2-164
C.S0005-0-2 v1.0
1 • If the purpose of the message is to provide the queue position of the PACA call
2 (PURPOSEr is equal to ‘0001’), the mobile station shall set the PACA state timer
3 to the duration shown in Table 3.7.2.3.2.20-2 corresponding to the value of
4 PACA_TIMEOUTs, should indicate to the user that the PACA call is still queued,
5 and should indicate to the user the current queue position (Q_POSr) of the call.
6 • If the purpose of the message is to instruct the mobile station to re-originate the
7 PACA call (PURPOSEr is equal to ‘0010’), Layer 3 shall send an L2-
8 Supervision.Request primitive to Layer 2 to abort any access attempt in
9 progress, shall set the PACA state timer to the duration shown in Table
10 3.7.2.3.2.20-2 corresponding to the value of PACA_TIMEOUTs, and shall enter
11 the Mobile Station Origination Attempt Substate with a PACA response indication.
12 • If the purpose of the message is to cancel the PACA call (PURPOSEr is equal to
13 ‘0011’), the mobile station shall set PACAs to disabled and PACA_CANCEL to ‘0’,
14 shall disable the PACA state timer, and should indicate to the user that the
28 indication (see 2.6.1.1). If the mobile station enters the Mobile Station Idle State, and
29 if PACAs is equal to enabled, the mobile station shall set PACAs to disabled and
35 or ‘011’.


2-165
C.S0005-0-2 v1.0


10 follows:

14 mobile station).

24 14. SSD Update Message: If the registration access was initiated due to a user direction
25 to power down, the mobile station shall ignore the message. Otherwise, the mobile
26 station shall respond to the message as specified in 2.3.12.1.5.
39 class (BAND_CLASSr) and operating mode (OP_MODEr) in the response.
40 If the message specifies a band class or a band class and an operating mode which
41 are not supported by the mobile station, the mobile station shall send a Mobile
2-166
C.S0005-0-2 v1.0
1 Station Reject Order with ORDQ set to ‘00000110’ (message requires a capability that
2 is not supported by the mobile station). If the response to this message exceeds the
10 as follows:
17 TMSI_CODEr.
25 other messages.
26 2.6.3.7 Mobile Station Message Transmission Substate

27 In this substate, the mobile station sends a Data Burst Message. If the base station
29 Support of this substate is optional.
35 2.1.1.2.2.1 of TIA/EIA/IS-2000-[4]).
38 TIA/EIA/IS-2000-[4]).
2-167
C.S0005-0-2 v1.0
2 to a message received from the base station) other than the Data Burst Message, Layer 3
3 shall indicate to Layer 2 that the message is a request other than a registration request or a
4 message transmission request (see 2.1.1.2.2.1 of TIA/EIA/IS-2000-[4]).
5 When transmitting an autonomous Data Burst Message, Layer 3 shall indicate to Layer 2
6 that the type of the message is a request that is a message transmission (see 2.1.1.2.2.1 of
7 TIA/EIA/IS-2000-[4]).
8 In the Mobile Station Message Transmission Substate, the mobile station shall send each
10 Upon entering the Mobile Station Message Transmission Substate, the mobile station shall
11 transmit the message as follows:
12 • If the mobile station entered this substate with a message transmission indication,
13 the mobile station shall transmit the Data Burst Message to the base station.
15 station declares a loss of the Paging Channel (see 2.6.2.1.1.43.1.8), the mobile station shall
23 State.
24 If the mobile station receives confirmation of any message sent by the mobile station in this
25 substate, it shall send a response in this substate if required and shall then enter the
26 Mobile Station Idle State.
29 If the mobile station receives a General Page Message, the mobile station may determine
30 whether there is a page match (see 2.6.2.3). If a match is declared, the mobile station shall

34 • The mobile station shall enter the Page Response Substate.
35 • If the mobile station entered this substate with a message transmission indication,
36 the mobile station may store the Data Burst Message for later transmission.
2-168
C.S0005-0-2 v1.0
33 If PACAs is equal to disabled, the mobile station shall send a Mobile Station Reject
34 Order with the ORDQ field set to ‘00000010’ (message not accepted in this state).
36 • If the purpose of the message is to respond to an Origination Message

37 (PURPOSEr is equal to ‘0000’), the mobile station shall send a Mobile Station
38 Reject Order with the ORDQ field set to ‘00000010’ (message not accepted in this
39 state).
2-169
C.S0005-0-2 v1.0
1 • If the purpose of the message is to provide the queue position of the PACA call
2 (PURPOSEr is equal to ‘0001’), the mobile station shall set the PACA state timer
3 to the duration shown in Table 3.7.2.3.2.20-2 corresponding to the value of
4 PACA_TIMEOUTs, should indicate to the user that the PACA call is still queued,
5 and should indicate to the user the current queue position (Q_POSr) of the call.
6 • If the purpose of the message is to instruct the mobile station to re-originate the
7 PACA call (PURPOSEr is equal to ‘0010’), Layer 3 shall send an L2-
8 Supervision.Request primitive to Layer 2 to abort any access attempt in
9 progress, shall set the PACA state timer to the duration shown in Table
10 3.7.2.3.2.20-2 corresponding to the value of PACA_TIMEOUTs, and shall enter
11 the Mobile Station Origination Attempt Substate with a PACA response indication.
12 • If the purpose of the message is to cancel the PACA call (PURPOSEr is equal to
13 ‘0011’), the mobile station shall set PACAs to disabled and PACA_CANCEL to ‘0’,
14 shall disable the PACA state timer, and should indicate to the user that the
27 or ‘011’.




2-170
C.S0005-0-2 v1.0
2 follows:

6 mobile station).

17 in 2.3.12.1.5.
30 class (BAND_CLASSr) and operating mode (OP_MODEr) in the response.
32 is not supported by the mobile station, the mobile station shall send a Mobile Station
33 Reject Order with ORDQ set to ‘00000110’ (message requires a capability that is not
42 as follows:
2-171
C.S0005-0-2 v1.0
7 TMSI_CODEr.
8 The mobile station shall set the TMSI expiration time by setting
9 TMSI_EXP_TIMEs-p to TMSI_EXP_TIMEr. The mobile station shall disable the
10 full-TMSI timer. The mobile station shall then respond with a TMSI Assignment
11 Completion Message within T56m seconds.
14 other messages.
15 2.6.3.8 PACA Cancel Substate

16 In this substate, the mobile station sends a PACA Cancel Message. If the base station
20 outstanding (see 2.1.1.2.2.1 of TIA/EIA/IS-2000.[4]).
23 2.1.1.2.2.1 of TIA/EIA/IS-2000.[4]).
26 TIA/EIA/IS-2000.[4]).
30 request (see 2.1.1.2.2.1 of TIA/EIA/IS-2000.[4]).
31 In the PACA Cancel Substate, the mobile station shall send each message in assured mode
32 requiring confirmation of delivery.
33 Upon entering the PACA Cancel Substate, the mobile station shall transmit the PACA Cancel
34 Message.
36 station declares a loss of the Paging Channel (see 2.6.2.1.1.43.1.8), it shall declare an
37 access attempt failure and update its registration variables as specified in 2.6.5.5.3.2,
38 disable its transmitter and enter the Mobile Station Idle State. If the mobile station receives
39 confirmation of any message sent by the mobile station in this substate, it shall send a
40 response in this substate if required and shall then enter the Mobile Station Idle State.
2-172
C.S0005-0-2 v1.0
1 If the mobile station receives a General Page Message, the mobile station may determine if
2 there is a page match (see 2.6.2.3). If a match is declared, Layer 3 shall send an L2-
3 Supervision.Request primitive to Layer 2 to abort any access attempt in progress and shall
4 enter the Page Response Substate.
35 7. PACA Message: The mobile station shall send a Mobile Station Reject Order with the
36 ORDQ field set to ‘00000010’ (message not accepted in this state).
2-173
C.S0005-0-2 v1.0
7 or ‘011’.




22 follows:

26 mobile station).

37 in 2.3.12.1.5.
2-174
C.S0005-0-2 v1.0

11 class (BAND_CLASSr) and operating mode (OP_MODEr) in the Status Response
12 Message.
14 is not supported by the mobile station, the mobile station shall send a Mobile Station
15 Reject Order with ORDQ set to ‘00000110’ (message requires a capability that is not
24 as follows:
31 TMSI_CODEr.
38 other messages.
39 2.6.4 Mobile Station Control on the Traffic Channel State
40 In this state, the mobile station communicates with the base station using the Forward and
41 Reverse Traffic Channels.
2-175
C.S0005-0-2 v1.0
1 As illustrated in Figure 2.6.4-1, the Mobile Station Control on the Traffic Channel State
2 consists of the following substates:
3 • Traffic Channel Initialization Substate - In this substate, the mobile station verifies
4 that it can receive the Forward Traffic Channel and begins transmitting on the
5 Reverse Traffic Channel.
6 • Waiting for Order Substate - In this substate, the mobile station waits for an Alert
7 With Information Message.
8 • Waiting for Mobile Station Answer Substate - In this substate, the mobile station
9 waits for the user to answer the call.
10 • Conversation Substate - In this substate, the mobile station exchanges Traffic
11 Channel frames with the base station in accordance with the current service
12 configuration. The mobile station may perform the gating operation of Reverse Pilot
13 Channel.
14 • Release Substate - In this substate, the mobile station disconnects the call.
15
2-176
C.S0005-0-2 v1.0
(Enter from System Access State)
Traffic
Channel
Initialization
Substate
(2.6.4.2)
Mobile station terminated call and Layer 3 receives a

forward dedicated channel acquired indication from Layer 2
Warning for Mobile station originated call and

Order Substate Layer 3 receives a
(2.6.4.3.1) forward dedicated channel
Receives acquired
Release Order indication from Layer 2
Receives a Maintenance Order or an
Alert With Information Message Mobile station terminated
call, bypass ordered by
the base station, and
Waiting for Layer 3 receives a
Mobile Station forward dedicated
Answer Substate channel acquired
(2.6.4.3.2) indication from Layer 2
Receives
Release Order Receives a
Mobile station user Maintenance
answers call Order or an Alert With
Information Message*
Conversation Receives Alert With

Substate Information Message
(2.6.4.4)
*If SIGNAL_TYPE is
equal
Mobile station user initiates disconnect or to '01' or '10' or if
mobile station receives Release Order the Signal Information
Record is not included
Release
Note: Not all state
Substate
transitions are shown.
(2.6.4.5)
System Determination Substate

of the Mobile Station
Initialization State
1
2
3 Figure 2.6.4-1. Mobile Station Control on the Traffic Channel State
2-177
C.S0005-0-2 v1.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-178
C.S0005-0-2 v1.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-179
C.S0005-0-2 v1.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 and the mobile station supports the Radio Configurations
21 greater than two, the mobile station shall perform the following:
22 • The mobile station shall set FPC_DELTA_SETPTs to (FPC_ FCH_CURR_SETPTs –

23 FPC _DCCH_CURR _SETPTs).
24 • For each received frame, if |FPC _FCH_CURR _SETPTs – FPC_DCCH_CURR

25 _SETPTs – FPC_DELTA_SETPTs| is equal to or greater than its assigned threshold
26 FPC_SETPT_THRESHs, the mobile station shall send the Outer Loop Report Message
27 requiring acknowledgment to the base station, and the mobile station shall then set
28 FPC_DELTA_SETPTs to (FPC _FCH_CURR _SETPTs – FPC _DCCH_CURR _SETPTs).
29 For each of the supplemental channels assigned to the mobile station and FPC_MODEs is
30 set to ‘000’, the mobile station shall perform the following:
31 • The mobile station shall set FPC_DELTA_SCH_SETPTs to

32 (FPC_FCH_CURR_SETPTs – FPC_SCH_CURR_SETPTs) if FPC_PRI_CHANs is equal to
33 ‘0’.
34 • The mobile station shall set FPC_DELTA_SCH_SETPTs to
35 (FPC_DCCH_CURR_SETPTs – FPC_SCH_CURR_SETPTs) if FPC_PRI_CHANs is equal
36 to ‘1’.
2-180
C.S0005-0-2 v1.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’ or ‘010’, for each additional Forward Supplemental Channel other than the Forward
16 Supplemental Channel specified by FPC_SEC_CHANs, the mobile station shall perform the
17 following:
18 • The mobile station shall set FPC_DELTA_SCH_SETPTs to (FPC_SCH_CURR_

19 SETPTs[FPC_SEC_CHANs] – FPC_SCH_CURR_SETPTs) for the Supplemental
20 Channel.
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:
36 • Power control reporting threshold (PWR_REP_THRESHs = PWR_REP_THRESHr)
37 • Power control reporting frame count (PWR_REP_FRAMESs = PWR_REP_FRAMESr)
38 • Threshold report mode indicator

39 (PWR_THRESH_ENABLEs = PWR_THRESH_ENABLEr)
2-181
C.S0005-0-2 v1.0
1 • Periodic report mode indicator

2 (PWR_PERIOD_ENABLEs = PWR_PERIOD_ENABLEr)
3 • Power report delay (PWR_REP_DELAYs = PWR_REP_DELAYr)
4 The mobile station shall set TOT_FRAMESs and BAD_FRAMESs to zero.
5 2.6.4.1.1.3 Processing the Power Control Message

6 The mobile station shall send a Mobile Station Reject Order with the ORDQ field set to
7 ‘00000110’ (message requires a capability that is not supported by the mobile station) if any
8 of the following conditions are detected:
9 • If the mobile station does not support any Radio Configuration greater than 2 and
10 FPC_MODEr is not supported by the mobile station.
11 • If the mobile station does not support Supplemental Channel and FPC_MODEr is set
12 to the ‘001’ or ‘010’.
13 • If PWR_CNTL_STEPr corresponds to a power control step size (see 2.1.2.3.2 of
14 TIA/EIA/IS-2000-[2]) is not supported by the mobile station.
16 ‘00000111’ (message cannot be handled by the current mobile station configuration) if any
18 • FPC_PRI_CHANr is set to ‘1’ and only the Fundamental Channel is assigned.
19 • FPC_PRI_CHANr is set to ‘0’ and only the Dedicated Control Channel is assigned.
20 If none of the above conditions are true, the mobile station shall process the message as
21 follows at the action time (see 2.6.4.1.5) specified in the message:
22 • The mobile station shall store the power control step size (PWR_CNTL_STEPs =
23 PWR_CNTL_STEPr).
24 • If FPC_INCLr is equal to ‘1’, the mobile station shall perform the following:
25 – The mobile station shall set FPC_MODE_NO_SCHs = FPC_MODEr.
26 – The mobile station shall set FPC_MODEs = FPC_MODE_NO_SCHs if there is no

27 forward Supplemental Channel burst in progress (see 2.6.6.2.5.1.1).
28 – The mobile station shall set FPC_PRI_CHANs to FPC_PRI_CHANr
29 – If FPC_OLPC_FCH_INCL is equal to ‘1’, the mobile station shall:

30 + Set FPC_FCH_FERs to FPC_FCH_FERr.
31 + If FPC_FCH_MIN_SETPTr is not equal to ‘11111111’, set

32 FPC_FCH_MIN_SETPTs to FPC_FCH_MIN_SETPTr; otherwise, set
33 FPC_FCH_MIN_SETPTs to FPC_FCH_CURR_SETPTs.
34 + If FPC_FCH_MAX_SETPTr is not equal to ‘11111111’, set

35 FPC_FCH_MAX_SETPTs to FPC_FCH_MAX_SETPTr; otherwise, set
36 FPC_FCH_MAX_SETPTs to FPC_FCH_CURR_SETPTs.
2-182
C.S0005-0-2 v1.0
1 – If FPC_OLPC_DCCH_INCL is equal to ‘1’, the mobile station shall:

2 + Set FPC_ DCCH_FERs to FPC_DCCH_FERr.
3 + If FPC_DCCH_MIN_SETPTr is not equal to ‘11111111’, set

4 FPC_DCCH_MIN_SETPTs to FPC_DCCH_MIN_SETPTr; otherwise, set
5 FPC_DCCH_MIN_SETPTs to FPC_DCCH_CURR_SETPTs.
6 + If FPC_DCCH_MAX_SETPTr is not equal to ‘11111111’, set

7 FPC_DCCH_MAX_SETPTs to FPC_DCCH_MAX_SETPTr; otherwise, set
8 FPC_DCCH_MAX_SETPTs to FPC_DCCH_CURR_SETPTs.
9 – If FPC_INCL is equal to '1' and FPC_MODE is equal to ‘001’ or ‘010, the mobile
10 station shall:
11 + Set FPC_SEC_CHANs to FPC_SEC_CHANr.
12 – If NUM_SUPr is not equal to ‘00’, for each Supplemental Channel included in the
13 message, the mobile station shall:
14 + Set SCH_IDs to SCH_IDr.
15 + Set FPC_SCH_FERs[SCH_IDs] to FPC_SCH_FERr.
16 + If FPC_SCH_MIN_ SETPTr is not equal to ‘11111111’, set

17 FPC_SCH_MIN_SETPTs[SCH_IDs] to FPC_SCH_MIN_SETPTr; otherwise, set
18 FPC_SCH_MIN_SETPTs[SCH_IDs] to FPC_SCH_CURR_SETPTs.
19 + If FPC_SCH_MAX_SETPTr is not equal to ‘11111111’, set

20 FPC_SCH_MAX_SETPTs[SCH_IDs] to FPC_SCH_MAX_SETPTr; otherwise, set
21 FPC_SCH_MAX_SETPTs[SCH_IDs] to FPC_SCH_CURR_SETPTs.
22 – If FPC_THRESH_INCL is equal to ‘1’, the mobile station shall set

23 FPC_SETPT_THRESHs to FPC_SETPT_THRESHr.
24 – If FPC_THRESH_SCH_INCL is equal to ‘1’, the mobile station shall set

25 FPC_SETPT_THRESH_SCHs to FPC_SETPT_THRESH_SCHr
26 • If RPC_INCLr is equal to ‘1’ and the mobile station supports any Radio Configuration
27 greater than 2, the mobile station shall perform the following:
28 – If RPC_ADJ_REC_TYPE is equal to ‘0000’, the mobile station shall update the

29 Reverse Channel Adjustment Gain Table (see 2.1.2.3.3 of TIA/EIA/IS-2000-[2])
30 containing an offset relative to the Reverse Pilot Channel power for each reverse
31 link code channel received in this message.
32 – If RPC_ADJ_REC_TYPE is equal to ‘0001’ or ‘0010’, the mobile station shall

33 update the Reverse Link Attribute Adjustment Gain Table (see 2.1.2.3.3 of
34 TIA/EIA/IS-2000-[2]) containing an offset relative to the Reverse Pilot Channel
35 power for each transmission rate, frame length, coding type received in this
36 message.
2-183
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-[3]). The
13 multiplex options which support Supplemental Code Channel transmission and
14 Supplemental Channel transmission on the Forward and Reverse Traffic Channels
15 are included in TIA/EIA/IS-2000-[3]. Multiplex Options 3 through 16 also indicate
16 the capability for supporting Supplemental Code Channel transmission on the
17 Forward and Reverse Traffic Channels. Invocation of Supplemental Code Channel
18 operation on the Forward or Reverse Traffic Channels occurs by the Supplemental
19 Channel Request Message, the Supplemental Channel Assignment Message, and the
20 General Handoff Direction Message. Invocation of Supplemental Channel operation
21 on the Forward or Reverse Traffic Channels occurs by the Supplemental Channel
22 Request Mini Message, the Extended Supplemental Channel Assignment Message,
23 the Forward Supplemental Channel Assignment Mini Message, Universal Handoff
24 Direction Message, and the Reverse Supplemental Channel Assignment Mini
25 Message. The multiplex option used for the Forward Traffic Channel can be the
26 same as that used for the Reverse 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-184
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-[3]
20 for Multiplex options applicable to Supplemental Code Channels), and by using the
21 appropriate Supplemental Code Channel related messages (i.e., the Supplemental
22 Channel Request Message, the Supplemental Channel Assignment Message, and the
23 General Handoff Direction Message). After Supplemental Code Channels have been
24 assigned by the base station, the connected service option can transmit primary
25 and/or secondary traffic on Supplemental Code Channels. Connected service
26 options can also invoke operation on Supplemental Channels in either one or both
27 of the Forward and Reverse Traffic Channels by negotiating a multiplex option that
28 supports operation on Supplemental Channels (see TIA/EIA/IS-2000-[3] for
29 Multiplex Options applicable to Supplemental Channel) and by using the
30 appropriate Supplemental Channel related messages (i.e., the Supplemental Channel
31 Request Mini Message, the Extended Supplemental Channel Assignment Message, the
32 Forward Supplemental Channel Assignment Mini Message, the Reverse Supplemental
33 Channel Assignment Mini Message, and the Universal Handoff Direction Message).
34 After Supplemental Channels have been assigned by the base station, the connected
35 service option can transmit primary and/or secondary traffic on Supplemental
36 Channels. The associated service option connection reference provides a means for
37 uniquely identifying the service option connection. The reference serves to resolve
38 ambiguity 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-185
C.S0005-0-2 v1.0
1 2. Forward and Reverse Power Control Parameters: These consist of forward power
2 control operation mode, outer loop power control parameters (Ex. 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-186
C.S0005-0-2 v1.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-187
C.S0005-0-2 v1.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: The base station can use this message to propose an initial
21 6.Page Response Message: The mobile station can use this message to accept or to
22 reject the initial service configuration proposed by the base station in a General
23 Page Message, or to propose an alternative initial service configuration.
24 7.Status Request Message: The base station can use this message to request service
25 capability information from the mobile station.
26 8.Status Response Message: The mobile station can use this message to return the
27 service capability information requested by the base station in a Status Request
28 Message.
29 9.Extended Status Response Message: The mobile station can use this message to
30 return the service capability information requested by the base station in a Status
31 Request Message.
32 10. Universal Handoff Direction Message: The base station can use this message to
34 negotiation, is to be used following a CDMA-to-CDMA hard handoff. The base
35 station can use this message to accept a service configuration proposed in a Service
36 Request Message or Service Response Message. The base station can also use this
37 message to instruct the mobile station to begin using the service configuration.
2-188
C.S0005-0-2 v1.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-189
C.S0005-0-2 v1.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, or a Handoff Completion
4 Message accordingly.
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
22
2-190
C.S0005-0-2 v1.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.
Receives
SCM, GHDM, or UHDM Receives
Waiting for SCM, GHDM, or UHDM
Service
Action Time
Subfunction
Receives Service
Request Message
Receives Service
proposing; sends Receives SCM, GHDM, or UHDM Response Message
Service Response
Message accepting. proposing; sends
Service Request
Message accepting.
Waiting for
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.
1
2
3 Figure 2.6.4.1.2.2-1. Mobile Station Service Subfunctions
2-191
C.S0005-0-2 v1.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:
24 If the mobile station accepts the service configuration specified in the message,
25 the mobile station shall activate the Waiting for Service Action Time
26 Subfunction; otherwise, the mobile station shall send a Mobile Station Reject
27 Order (ORDQ = ‘00000111’) within T56m seconds.
28 2. Service Option Control Message: If the service option connection specified by the
29 message is part of the current service configuration, and the service option
30 specified by the message is the same as the service option associated with the
31 service option connection, the mobile station shall interpret the action time of
32 the message as specified in 2.6.4.1.5, and shall process the message in
33 accordance with the requirements for the service option; otherwise, the mobile
34 station shall send a Mobile Station Reject Order (ORDQ = ‘00000111’) within
35 T56m seconds.
36 3. Service Request Message: The mobile station shall process the message as
37 follows:
38 – If the purpose of the message is to reject a proposed service configuration,

39 the mobile station shall send a Mobile Station Reject Order (ORDQ =
40 ‘00000010’) within T56m seconds.
2-192
C.S0005-0-2 v1.0
1 – If the purpose of the message is to propose a service configuration, the

2 mobile station shall process the message as follows:
3 + If the mobile station accepts the proposed service configuration, the

4 mobile station shall send a Service Response Message to accept the
5 proposed service configuration within T59m seconds. The mobile station
6 shall activate the Waiting for Service Connect Message Subfunction.
7 + If the mobile station does not accept the proposed service configuration
8 and does not have an alternative service configuration to propose, the
9 mobile station shall send a Service Response Message to reject the
10 proposed service configuration within T59m seconds.
12 and has an alternative service configuration to propose, the mobile
13 station shall send a Service Response Message to propose the alternative
14 service configuration within T59m seconds. The mobile station shall
15 activate the Waiting for Service Request Message Subfunction.
16 4. Service Response Message: The mobile station shall send a Mobile Station Reject
18 5. General Handoff Direction Message: If the SCR_INCLUDED field is included in

19 this message and is set to ‘1’:
20 If the mobile station has not rejected this message, the mobile station shall
21 activate the Waiting for Service Action Time Subfunction.
22 6. Universal Handoff Direction Message: If the SCR_INCLUDED field is included in

26 • If the mobile station receives one of the following service option negotiation
27 messages, the mobile station shall send a Mobile Station Reject Order (ORDQ =
28 ‘00000010’) within T56m seconds:
29 1. Service Option Request Order
30 2. Service Option Response Order
31 3. Service Option Control Order
32 2.6.4.1.2.2.2 Waiting for Service Request Message Subfunction

33 While this subfunction is active, the mobile station waits to receive a Service Request
34 Message.
35 Upon activation of the Waiting for Service Request Message Subfunction, the mobile station
36 shall set the subfunction timer for T68m seconds.
37 While the Waiting for Service Request Message Subfunction is active, the mobile station shall
2-193
C.S0005-0-2 v1.0
1 • If the subfunction timer expires, the mobile station shall activate the Normal Service
2 Subfunction.
8 configuration.
9 • The mobile station shall not initiate service negotiation for a new service
10 configuration.
14 service option.
21 activate the Waiting for Service Action Time Subfunction; otherwise, the mobile
22 station shall activate the Normal Service Subfunction.
30 T56m seconds.
32 follows:

34 the mobile station shall activate the Normal Service Subfunction.


2-194
C.S0005-0-2 v1.0
5 shall activate the Normal Service Subfunction.
10 reset the subfunction timer for T68m seconds.


29 2.6.4.1.2.2.3 Waiting for Service Response Message Subfunction

30 While this subfunction is active, the mobile station waits to receive a Service Response
31 Message.
32 Upon activation of the Waiting for Service Response Message Subfunction, the mobile station
34 While the Waiting for Service Response Message Subfunction is active, the mobile station
37 Subfunction.
2-195
C.S0005-0-2 v1.0
6 configuration.
8 configuration.
12 service option.
19 the mobile station shall activate the Waiting for Service Action Time Subfunction;
20 otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ =
21 ‘00000111’) within T56m seconds and shall activate the Normal Service
22 Subfunction.
30 T56m seconds.
32 follows:


37 mobile station shall discontinue processing the service configuration
38 requested by the user and shall process the message as follows:
2-196
C.S0005-0-2 v1.0

15 4. Service Response Message: The mobile station shall process the message as
16 follows:
17 – If the service request sequence number (SERV_REQ_SEQr) from the message
18 does not match the sequence number of the Service Request Message for
19 which the mobile station is expecting a response, the mobile station shall not
20 process the other layer 3 fields of the message.
21 – If the purpose of the message is to reject the service configuration proposed

22 in the corresponding Service Request Message, the mobile station shall
23 activate the Normal Service Subfunction. The mobile station may indicate to
24 the user that the requested service configuration has been rejected.


28 mobile station shall send a Service Request Message to accept the
33 mobile station shall send a Service Request Message to reject the
38 station shall send a Service Request Message to propose the alternative
40 reset the subfunction timer for T68m seconds.
2-197
C.S0005-0-2 v1.0

16 2.6.4.1.2.2.4 Waiting for Service Connect Message Subfunction

17 While this subfunction is active, the mobile station waits to receive a Service Connect
18 Message, a General Handoff Direction Message, or a Universal Handoff Direction Message
19 containing a service configuration record.
20 Upon activation of the Waiting for Service Connect Message Subfunction, the mobile station
22 While the Waiting for Service Connect Message Subfunction is active, the mobile station shall
25 Subfunction.
31 configuration.
33 configuration.
37 service option.
2-198
C.S0005-0-2 v1.0
7 the mobile station shall activate the Waiting for Service Action Time Subfunction;
8 otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ =
9 ‘00000111’) within T56m seconds and shall activate the Normal Service
10 Subfunction.
18 T56m seconds.
20 follows:



29 shall reset the subfunction timer for T65m seconds.
2-199
C.S0005-0-2 v1.0


17 2.6.4.1.2.2.5 Waiting for Service Action Time Subfunction
18 While this subfunction is active, the mobile station waits for the action time associated with
19 a new service configuration. If the action time was specified by a Service Connect Message,
20 the mobile station shall send the Service Connect Completion Message at the action time.
21 While the Wait for Service Action Time Subfunction is active, the mobile station shall perform
22 the following:
23 • Prior to the action time associated with the Service Connect Message, General
24 Handoff Direction Message, or Universal Handoff Direction Message containing a
25 service configuration record, the mobile station shall process Forward and Reverse
26 Traffic Channel frames in accordance with the current service configuration. The
27 mobile station shall discard any Forward Traffic Channel frame which has a format
28 that is not supported by the mobile station. The mobile station may discard any
29 type of Forward Traffic Channel traffic that is not signaling traffic and is not part of
30 the current service configuration.
2-200
C.S0005-0-2 v1.0
1 • At the action time associated with the Service Connect Message, General Handoff
2 Direction Message or Universal Handoff Direction Message containing a service
3 configuration record, the mobile station shall process the received Service
4 Configuration Record as specified in 2.6.4.1.14, shall process the received Non-
5 negotiable Service Configuration Record (if included) as specified in 2.6.4.1.15, and
6 shall begin to use the service configuration specified by the Service Connect
7 Message, General Handoff Direction Message or Universal Handoff Direction Message
8 containing a service configuration record as the current service configuration and
9 shall begin to process Forward and Reverse Traffic Channel frames accordingly. If
10 the action time was specified by a Service Connect Message, the mobile station shall
11 send a Service Connect Completion Message within T56m seconds after the action
12 time. The mobile station shall exit this subfunction and activate the Normal Service
13 Subfunction.
15 configuration.
16 • For any service option connection that is part of the current or pending service
17 configuration, the mobile station may send a Service Option Control Message to
18 invoke a service option specific function in accordance with the requirements for the
19 associated service option.
24 1. Service Connect Message: The mobile station shall send a Mobile Station Reject
27 message is part of the current or pending service configuration, and the service
28 option specified by the message is the same as the service option associated with
29 the service option connection, the mobile station shall interpret the action time
30 of the message as specified in 2.6.4.1.5, and shall process the message in
33 T56m seconds.
34 3. Service Request Message: The mobile station shall send a Mobile Station Reject

41 remain in this subfunction until the action time specified in the message, and
2-201
C.S0005-0-2 v1.0
1 shall begin to use the service configuration specified by the General Handoff
2 Direction Message at the action time.

6 remain in this subfunction until the action time specified in the message, and
7 shall begin to use the service configuration specified by the Universal Handoff
8 Direction Message at the action time.
15 2.6.4.1.2.2.6 SO Negotiation Subfunction

16 The SO Negotiation Subfunction is only supported for mobile stations operating in Band
17 Class 0.
18 Upon activation of the SO Negotiation Subfunction, the mobile station shall delete from the
19 current service configuration any service option connection which does not use primary
20 traffic on both the Forward and Reverse Traffic Channels.
21 While the SO Negotiation Subfunction is active, the mobile station shall perform the
22 following:
23 • If the current service configuration includes a service option connection, the mobile
24 station shall process the received primary traffic bits in accordance with the
25 requirements for the service option associated with the service option connection;
26 otherwise, the mobile station shall discard the received primary traffic bits.
28 station shall transmit primary traffic bits in accordance with the requirements for
29 the service option associated with the service option connection; otherwise, the
30 mobile station shall transmit null traffic on the Reverse Fundamental Channel, if
31 the Fundamental Channel is present or transmit power control bits on the Reverse
32 Pilot Channel, if only the Dedicated Control Channel is present.
34 station may send a Service Option Control Order to invoke a service option specific
35 function in accordance with the requirements for the service option associated with
36 the service option connection.
37 • To initiate service option negotiation, the mobile station shall set SO_REQs to the
38 number of the requested service option and shall send a Service Option Request
39 Order containing the requested service option number.
2-202
C.S0005-0-2 v1.0
1 • If SERV_NEGs changes from disabled to enabled (see 2.6.6.2.5.1), the mobile station
2 shall set SO_REQs to NULL and shall activate the Normal Service Subfunction.
3 • If the mobile station receives a Service Option Request Order, it shall process the
4 order as follows:
5 – If the mobile station accepts the requested service option, the mobile station
6 shall set SO_REQs to NULL and shall send a Service Option Response Order
7 accepting the requested service option within T58m seconds. The mobile station
8 shall interpret the message action time of the Service Option Request Order in
9 accordance with the requirements for the requested service option and the
10 mobile station shall begin using the service configuration implied by the
11 requested service option in accordance with those requirements. The implied
12 service configuration shall include the default Forward and Reverse multiplex
13 options and radio configurations associated with the requested service option,
14 and shall include one service option connection for which the service option
15 connection reference is 1, the service option is the requested service option, and
16 the Forward and Reverse Traffic Channel types are both primary traffic.
17 – If the mobile station does not accept the requested service option and has an
18 alternative service option to request, the mobile station shall set SO_REQs to the
19 alternative service option number and shall send a Service Option Request Order
20 requesting the alternative service option within T58m seconds.
21 – If the mobile station does not accept the requested service option and does not
22 have an alternative service option to request, the mobile station shall set
23 SO_REQs to NULL and shall send a Service Option Response Order to reject the
24 request within T58m seconds. The mobile station shall continue to use the
25 current service configuration.
26 • If the mobile station receives a Service Option Response Order, it shall process the
27 order as follows:
28 – If the service option number specified in the order is equal to SO_REQs, the
29 mobile station shall set SO_REQs to NULL. The mobile station shall interpret
30 the message action time of the Service Option Response Order in accordance with
31 the requirements for the specified service option, and the mobile station shall
32 begin using the service configuration implied by the specified service option in
33 accordance with those requirements. The implied service configuration shall
34 include the default Forward and Reverse multiplex options radio configurations
35 associated with the specified service option, and shall include one service option
36 connection for which the service option connection reference is 1, the service
37 option is the specified service option, and the Forward and Reverse Traffic
38 Channel types are both primary traffic.
39 – If the order indicates a service option rejection, the mobile station shall set
40 SO_REQs to NULL. The mobile station shall continue to use the current service
41 configuration.
2-203
C.S0005-0-2 v1.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_REQs, the mobile station shall set
3 SO_REQs to NULL and shall send a Mobile Station Reject Order (ORDQ =
4 ‘00000100’) within T58m seconds. The mobile station shall continue to use the
6 • If the mobile station receives a Service Option Control Order, it shall process the
7 order as follows:
8 – If the current service configuration includes a service option connection, the

9 mobile station shall interpret the message action time of the Service Option
10 Control Order in accordance with the requirements for the service option
11 associated with the service option connection and the mobile station shall
12 process the Service Option Control Order in accordance with those requirements;
13 – otherwise, the mobile station shall send a Mobile Station Reject Order (ORDQ =
16 mobile station shall send a Mobile Station Reject Order (ORDQ = ‘00000010’) within
17 T56m seconds:
18 1. Service Connect Message
19 2. Service Option Control Message
20 3. Service Request Message
21 4. Service Response Message
22 2.6.4.1.3 Ordering of Messages
23 The Layer 2 protocol does not guarantee delivery of messages in any order. If the mobile
24 station requires that the base station receive a set of messages in a certain order, the
25 mobile station shall send each message in assured mode requiring confirmation of delivery
26 and shall wait for the confirmation of delivery of each message before transmitting the next
27 message in the set.
28 2.6.4.1.4 Processing the In-Traffic System Parameters Message

29 The mobile station shall store the following parameters from the In-Traffic System
30 Parameters Message:
33 • Search window size for the Active Set and the Candidate Set
35 • Search window size for the Neighbor Set (SRCH_WIN_Ns = SRCH_WIN_Nr)
36 • Search window size for the Remaining Set (SRCH_WIN_Rs = SRCH_WIN_Rr)
37 • Pilot detection threshold (T_ADDs = T_ADDr)
2-204
C.S0005-0-2 v1.0
1 • Pilot drop threshold (T_DROPs = T_DROPr)
2 • Active Set versus Candidate Set comparison threshold (T_COMPs = T_COMPr)
3 • Drop timer value (T_TDROPs = T_TDROPr)
4 • Maximum age for retention of Neighbor Set members

5 (NGHBR_MAX_AGEs = NGHBR_MAX_AGEr)
6 • Protocol revision level (P_REVs = P_REVr), and protocol revision level currently in
7 use (P_REV_IN_USEs = min (P_REVs, MOB_P_REVp of the current band class) )
8 • Slope of the handoff add/drop criterion (SOFT_SLOPEs = SOFT_SLOPEr)
9 • Intercept of the handoff add criterion (ADD_INTERCEPTs = ADD_INTERCEPTr)
10 • Intercept of the handoff drop criterion (DROP_INTERCEPTs = DROP_INTERCEPTr)
11 • If included, Reverse Supplemental Code Channel or Reverse Supplemental Channel

12 transmission offset threshold (T_MULCHANs = T_MULCHANr)
13 • If included, Reverse Supplemental Code Channel beginning of transmission

14 preamble length (BEGIN_PREAMBLEs = BEGIN_PREAMBLEr)
15 • If included, Reverse Supplemental Code Channel discontinuous transmission

16 resumption preamble length (RESUME_PREAMBLEs = RESUME_PREAMBLEr)
17 • If included, Slotted Timer (T_SLOTTEDs = T_SLOTTEDr)
18 If the mobile station supports packet data service options, the mobile station shall store the
19 packet data services zone identifier (PACKET_ZONE_IDs = PACKET_ZONE_IDr).
20 The mobile station shall determine its roaming status (see 2.6.5.3). The mobile station
21 should indicate to the user whether the mobile station is roaming.
22 2.6.4.1.5 Message Action Times
23 A Forward Traffic Channel message without a USE_TIME field or with a USE_TIME field set
24 to ‘0’ has an implicit action time. A message that has its USE_TIME field set to ‘1’ has an
25 explicit action time that is specified in the ACTION_TIME field of the message.
26 A message with an explicit action time is called a pending message.
27 Unless otherwise specified, a message having an implicit action time shall take effect no
28 later than the first 80 ms boundary (relative to System Time) occurring at least 80 ms after
29 the end of the frame containing the last bit of the message. A message with an explicit
30 action time, except for a Power Up Function Message, shall take effect when System Time (in
31 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME field. A Power Up
32 Function Message shall take effect ACTION_TIME_FRAME frames after the time when
33 System Time (in 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME
34 field. The difference in time between ACTION_TIME and the end of the frame containing the
35 last bit of the message shall be at least 80 ms.
36 The mobile station shall support two pending messages at any given time, not including
37 pending Service Option Control Orders or Service Option Control Messages. The number of
38 pending Service Option Control Orders or Service Option Control Messages that the mobile
2-205
C.S0005-0-2 v1.0
1 station is required to support is specific to the service option (see the relevant service option
2 description). In addition, the mobile station shall support one pending Power Up Function
3 Message.
4 2.6.4.1.6 Long Code Transition Request Processing

5 The mobile station performs these procedures upon receiving a Long Code Transition
6 Request Order.
7 If the Long Code Transition Request Order requests a transition to the private long code, and
8 the mobile station is able to generate the private long code (see 2.3.12.3), and the mobile
9 station accepts the request, the mobile station shall send a Long Code Transition Response
10 Order (ORDQ = ‘00000011’) within T56m seconds. The mobile station shall use the private
11 long code on both the Forward Traffic Channel and the Reverse Traffic Channel. The
12 mobile station shall begin using the private long code using the explicit action time (see
13 2.6.4.1.5) specified in the message. The mobile station should indicate to the user that the
14 voice privacy mode is active. If the Long Code Transition Request Order requests a private
15 long code transition, and the mobile station is not able to generate the private long code or
16 the mobile station does not accept the request, the mobile station shall send a Long Code
17 Transition Response Order (ORDQ = ‘00000010’) within T56m seconds.
18 If the Long Code Transition Request Order requests a transition to the public long code and
19 the mobile station accepts the request, the mobile station shall send a Long Code Transition
20 Response Order (ORDQ = ‘00000010’) within T56m seconds. The mobile station shall use
21 the public long code on both the Forward Traffic Channel and the Reverse Traffic Channel.
22 The mobile station shall begin using the public long code using the explicit action time (see
23 2.6.4.1.5) specified in the message. The mobile station should indicate to the user that the
24 voice privacy mode is inactive. If the Long Code Transition Request Order requests a public
25 long code transition, and the mobile station does not accept the request, the mobile station
26 shall send a Long Code Transition Response Order (ORDQ = ‘00000011’) within T56m
27 seconds.
28 2.6.4.1.7 Power Up Function (PUF)
29 Figure 2.6.4.1.7-1 illustrates the general structure of a PUF attempt. A PUF pulse is the
30 interval during which the mobile station transmits at the specified power level while
31 executing the Power Up Function.
32 A PUF probe is one or more consecutive Traffic Channel frames. A PUF probe consists of
33 three parts: PUF setup, PUF pulse, and PUF recovery. PUF_SETUP_SIZE is the duration of
34 the PUF setup part, in power control groups. PUF_PULSE_SIZE is the duration of the PUF
35 pulse, in power control groups. The PUF recovery period occupies the remainder of the last
36 frame of the PUF probe.
37 A PUF attempt is a sequence of PUF probes sent by the mobile station in response to a
38 Power Up Function Message. A PUF attempt begins at an offset frame boundary within 80
39 ms of the ACTION_TIME specified in the Power Up Function Message. A PUF attempt can be
40 terminated in one of four ways:
41 • The mobile station receives a Power Up Function Completion Message.
2-206
C.S0005-0-2 v1.0
1 • The mobile station has transmitted the maximum number of PUF probes specified in
2 the Power Up Function Message.
3 • The mobile station has transmitted the maximum number of probes allowed at its
4 maximum output power.
5 • The mobile station receives a new Power Up Function Message.
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
7
8 Figure 2.6.4.1.7-1. Structure of PUF Attempt
10 2.6.4.1.7.1 Processing the Power Up Function Message

12 ‘00000110’ (message requires a capability that is not supported by the mobile station) if any
14 • PUF_FREQ_INCLr is set to ‘1’ and PUF_BAND_CLASSr is not supported by the
15 mobile station.
16 • PUF_FREQ_INCLr is set to ‘1’ and the mobile station is unable to re-tune to the PUF
17 Target Frequency during (PUF_SETUP_SIZEr + 1) power control groups.
18 • MOB_P_REVp is not equal to five and the mobile station does not support the Power
19 Up Function.
2-207
C.S0005-0-2 v1.0
2 ‘00001100’ (invalid Frequency Assignment), if the Frequency Assignment specified in the
3 message is the same as the Serving Frequency (PUF_FREQ_INCLr is equal to ‘1’,
4 PUF_BAND_CLASSr is equal to CDMABANDs and PUF_CDMA_FREQr is equal to
5 CDMACHs).
6 If the mobile station is processing a PUF probe, the mobile station shall wait for the PUF
7 probe to complete. It shall then terminate the current PUF attempt. The mobile station
8 shall store the following parameters:
9 • Maximum number of PUF probes transmitted at full power level (MAX_PWR_PUFs =
10 MAX_PWR_PUFr + 1)
11 • Total number of PUF probes (TOTAL_PUF_PROBESs = TOTAL_PUF_PROBESr + 1)
12 • PUF interval (PUF_INTERVALs = PUF_INTERVALr)
13 • Number of PUF setup power control groups (PUF_SETUP_SIZEs =

14 PUF_SETUP_SIZEr + 1)
15 • Number of PUF pulse power control groups (PUF_PULSE_SIZEs = PUF_PULSE_SIZEr

16 +1)
17 • Power increase of initial PUF pulse (PUF_INIT_PWRs = PUF_INIT_PWRr)
18 • Power increase for each successive PUF pulse (PUF_PWR_STEPs = PUF_PWR_STEPr)
19 • Frequency included indicator (PUF_FREQ_INCLs = PUF_FREQ_INCLr)
20 If PUF_FREQ_INCLs equals ‘1’, the mobile station shall store the following:
21 • PUF probe Target Frequency CDMA Channel number (PUF_TF_CDMACHs =

22 PUF_CDMA_FREQr)
23 • PUF probe Target Frequency CDMA band class (PUF_TF_CDMABANDs =

24 PUF_BAND_CLASSr)
25 The mobile station shall set CURRENT_PUF_PROBEs equal to 0.
26 The mobile station shall then begin the PUF attempt at the time specified in 2.6.4.1.7.2.
27 2.6.4.1.7.2 Power Up Function Procedures
28 The mobile station shall process the initial PUF probe beginning at the start of the frame
29 which starts ACTION_TIME_FRAMEr × 20 ms + FRAME_OFFSETs × 1.25 ms after the
30 System Time specified by ACTION_TIMEr. The mobile station shall process additional PUF
31 probes beginning at intervals of PUF_INTERVALs frames from the beginning of the initial
32 PUF probe.
33 The mobile station shall transmit the PUF probes as described in 2.6.4.1.7.2.1 and
34 2.6.4.1.7.2.2.
35 2.6.4.1.7.2.1 PUF Probe On Serving Frequency
36 The mobile station shall process each PUF probe as follows:
2-208
C.S0005-0-2 v1.0
1 • The mobile station shall use closed loop power control procedures as specified in
2 2.1.2.3.2 of TIA/EIA/IS-2000-[2].
3 • The mobile station shall use the gated output procedures specified in 2.1.2.2.2.4
4 and 2.1.3.1.10.3 of TIA/EIA/IS-2000-[2].
5 • The mobile station shall control its mean output power as specified in 2.1.2.3.1 of
6 TIA/EIA/IS-2000-[2].
7 • The mobile station shall monitor its output power during the PUF pulse, and should
8 monitor its output power at least once during each power control group of the PUF
9 pulse. If the mobile station detects that the transmit power level specified in of
10 TIA/EIA/IS-2000-[2] is equal to or greater than the maximum power output of the
11 mobile station at any time during a PUF pulse, the mobile station shall decrement
12 MAX_PWR_PUFs by one for that PUF pulse.
13 • The mobile station shall transmit the traffic channel preamble for the duration of
14 the PUF probe on the Reverse Fundamental Code Channel.
15 After the processing of each PUF probe, the mobile station shall increment
16 CURRENT_PUF_PROBEs by 1. If MAX_PWR_PUFs is equal to 0, the mobile station shall
17 terminate the PUF attempt. If CURRENT_PUF_PROBEs equal to TOTAL_PUF_PROBEs, the
18 mobile station shall terminate the PUF attempt.
19 2.6.4.1.7.2.2 PUF Probe On PUF Target Frequency
20 The mobile station shall process each PUF probe as follows:
21 • The mobile station shall use closed loop power control procedures as specified in
22 2.1.2.3.2 of TIA/EIA/IS-2000-[2].
23 • The mobile station shall use the gated output procedures specified in 2.1.3.1.10.3 of
24 TIA/EIA/IS-2000-[2].
25 • The mobile station shall control its mean output power as specified in 2.1.2.3.1 of
26 TIA/EIA/IS-2000-[2].
27 • The mobile station shall store the following Serving Frequency parameters from its
28 current configuration:
29 – CDMA Band Class (PUF_SF_CDMABANDs = CDMABANDs)
30 – Frequency assignment (PUF_SF_CDMACHs = CDMACHs)
31 • The mobile station shall monitor its output power during the PUF pulse, and should
32 monitor its output power at least once during each power control group of PUF
33 pulse. If the mobile station detects that the transmit power level specified in
34 2.1.2.3.1 of TIA/EIA/IS-2000-[2] is equal to or greater than the maximum power
35 output of the mobile station at any time during a PUF pulse, the mobile station shall
36 decrement the MAX_PWR_PUFs by one for that PUF pulse.
2-209
C.S0005-0-2 v1.0
1 • At the beginning of the PUF probe, the mobile station shall disable its transmitter,
2 stop processing the Forward Supplemental Code Channel (if any), or the Forward
3 Supplemental Channel (if any), disable all corrections to the mobile station time
4 reference (see 2.1.5 of TIA/EIA/IS-2000-[2]), tune to the CDMA channel specified by
5 PUF_TF_CDMACHs, and PUF_TF_CDMABANDs and re-enable its transmitter.
6 • The mobile station shall transmit the traffic channel preamble on the Reverse
7 Fundamental Code Channel during the PUF pulse at PUF_TX_PWRs.
8 • The mobile station should disable its transmitter immediately after the end of the
9 PUF pulse, and shall disable its transmitter before the end of the first power control
10 group after the PUF pulse. It shall then tune to its assigned CDMA channel as given
11 by CDMACHs and CDMABANDs.
12 • If the interval between the time that the mobile station tunes to the PUF Target
13 Frequency and the time that it re-tunes to the Serving Frequency is equal to or
14 greater than (N2m × 0.02) seconds, the mobile station shall wait to receive a period
15 of (N3m × 20) ms with sufficient signal quality (e.g. good frames) on the physical
16 channel corresponding to FPC_PRI_CHANs.
17 • The mobile station shall then re-enable its transmitter and re-enable any
18 adjustments to the mobile station time reference.
19 • If the Forward Supplemental Code Channel assignment has not expired while the
20 mobile station has tuned to the PUF Target Frequency, then the mobile station shall
21 resume processing the Forward Supplemental Code Channels after re-tuning to the
23 • If the Forward Supplemental Channel assignment has not expired while the mobile
24 station has tuned to the PUF Target Frequency, then the mobile station shall
25 resume processing the Forward Supplemental Channels after re-tuning to the
27 • If the Reverse Supplemental Code Channel assignment has not expired while the
28 mobile station has tuned to the PUF Target Frequency, then the mobile station may
29 resume transmitting the Reverse Supplemental Code Channels after re-tuning to the
31 • If the Reverse Supplemental Channel assignment has not expired while the mobile
32 station has tuned to the PUF Target Frequency, then the mobile station may resume
33 transmitting the Reverse Supplemental Code Channels after re-tuning to the Serving
34 Frequency.
35 After the processing of each PUF probe, the mobile station shall increment
36 CURRENT_PUF_PROBEs by one. If MAX_PWR_PUFs is equal to 0, the mobile station shall
37 terminate the PUF attempt. If CURRENT_PUF_PROBEs is equal to TOTAL_PUF_PROBEs,
38 the mobile station shall terminate the PUF attempt.
2-210
C.S0005-0-2 v1.0
1 2.6.4.1.7.3 Processing the Power Up Function Completion Message
2 The mobile station shall terminate any PUF attempt no later than the completion of the
3 current probe in progress and shall discard any pending Power Up Function Message. If
4 LOC_INDr is equal to ‘1’, the mobile station may store the following parameters:
5 • Mobile Station Latitude (MS_LATs = MS_LATr)
6 • Mobile Station Longitude (MS_LONGs = MS_LONGr)
7 • Time stamp (MS_LOC_TSTAMPs = MS_LOC_TSTAMPr)
8 2.6.4.1.8 Forward Traffic Channel Supervision

9 When in the Mobile Station Control on the Traffic Channel State, the mobile station shall
10 continuously monitor the Forward Channel, except:
11 • During a PUF probe in which it transmits on a PUF target frequency (see 2.6.4.1.7),
12 • During a search of pilots on a CDMA Candidate Frequency (see 2.6.6.2.8.3),
13 • During a search of analog frequencies (see 2.6.6.2.10).

14 The mobile station shall monitor the physical channel corresponding to FPC_PRI_CHANs.
15 If the mobile station receives a period of (N2m × 20) ms with insufficient signal quality (e.g.
16 bad frames) on the physical channel corresponding to FPC_PRI_CHANs, it shall disable its
17 transmitter. Thereafter, if the mobile station receives a period of (N3m × 20) ms with
18 sufficient signal quality (e.g. good frames) on the physical channel corresponding to
19 FPC_PRI_CHANs, then the mobile station should re-enable its transmitter.
20 The mobile station shall establish a Forward Traffic Channel fade timer. The timer shall be
21 enabled when the mobile station first enables its transmitter when in the Traffic Channel
22 Initialization Substate of the Mobile Station Control on the Traffic Channel State. The fade
23 timer shall be reset for T5m seconds whenever the mobile station receives a period of (N3m
24 × 20) ms with sufficient signal quality (e.g. good frames) on the physical channel
25 corresponding to FPC_PRI_CHANs. The mobile station shall disable the fade timer when it
26 tunes to a PUF target frequency, and shall re-enable the fade timer at the end of the PUF
27 probe. If the timer expires, the mobile station shall disable its transmitter and declare a
28 loss of the Forward Traffic Channel.
29 The mobile station also enables, disables, and resets the fade timer when it performs a hard
30 handoff or a periodic search, as described in 2.6.6.2.8 and 2.6.6.2.10.
31 2.6.4.1.9 Processing the Extended Release Message and the Extended Release Mini Message
32 • Upon receiving the Extended Release Message or the Extended Release Mini Message,
33 the mobile station shall process the message as follows:
34 − If the mobile station determines that the configuration specified by CH_INDr is not
35 valid, the mobile station shall send a Mobile Station Reject Order with the ORDQ field
36 set to ‘00000111’ (message can not be handled by the current mobile station
37 configuration) and the mobile station shall not perform the remaining procedures in
38 this section.
2-211
C.S0005-0-2 v1.0
1 – If the physical channels indicated by the two least significant bits of CH_INDr
2 includes all the physical channels (FCH, DCCH, or both) currently being processed
3 by the mobile station, the mobile station shall perform the following:
4 + Enter the Release Substate with a base station extended release indication if the
5 message is the Extended Release Message.
6 + Enter the Release Substate with a base station extended release with mini
7 message indication if the message is the Extended Release Mini Message.
8 – Otherwise, the mobile station shall perform the following:

9 + If the received message is the Extended Release Message, the mobile station
10 shall send an Extended Release Response Message to the base station. If the
11 received message is the Extended Release Mini Message, the mobile station shall
12 send an Extended Release Response Mini Message to the base station.
13 + The mobile station shall update CH_INDs as follows: If the least significant bit of
14 CH_INDr equals ‘1’, the mobile station shall set CH_INDs = ‘10’; if the second
15 mostleast significant bit of CH_INDr equals ‘1’, the mobile station shall set
16 CH_INDs = ‘01’.
17 + If CH_INDr is equal to ‘001’ or ‘101’, the mobile station shall set FPC_PRI_CHANs
18 to ‘1’ at the action time of the message.
19 + If CH_INDr is equal to ‘010’, the mobile station shall set FPC_PRI_CHANs to ‘0’ at
20 the action time of the message.
21 + If the least significant bit of CH_INDr equals ‘1’, then the mobile station shall
22 stop transmitting on R-FCH and stop processing F-FCH at the action time
23 specified by the message.
24 + If the second most significant bit of CH_INDr equals ‘1’, then the mobile station
25 shall stop transmitting on R-DCCH and stop processing F-DCCH at the action
26 time specified by the message.
27 + If GATING_RATE_INCLr equals ‘1’, the mobile station shall set
28 PILOT_GATING_RATEs = PILOT_GATING_RATEr at the action time of the
29 message.
30 + If the most significant bit of CH_INDr equals ‘1’, the mobile station shall set
31 PILOT_GATING_USE_RATE to ‘1’. The mobile station shall start the reverse pilot
32 gating at PILOT_GATING_RATEs at the action time of the message. Furthermore,
33 if the least significant bit of CH_INDr equals ‘1’ (that is, the Fundamental
34 Channel is being released), the mobile station shall store the configuration used
35 for the Fundamental Channel. The mobile station shall cancel the forward and
36 reverse supplemental channel assignment, if any.
2-212
C.S0005-0-2 v1.0
1 2.6.4.1.10 Processing the Resource Allocation Message and Resource Allocation Mini
2 Message
3 The mobile station shall process the Resource Allocation Message and the Resource
4 Allocation Mini Message as follows:
5 • The mobile station shall set FPC_PRI_CHANs = FPC_PRI_CHANr at the action time of
6 the message.
7 • If the Fundamental Channel was previously established prior to transitioning to the

8 Control Hold mode, the mobile station shall start processing F-FCH and start
9 transmitting on R-FCH at the action time of the message. The mobile station shall
10 establish the Fundamental Channel with the same configuration as previously used,
11 and shall set CH_INDs to ‘11’.
12 • The mobile station shall set PILOT_GATING_USE_RATE to ‘0’. The mobile station
13 shall start the continuous reverse pilot at the action time of the message.
14 2.6.4.1.11 Reserved
15 2.6.4.1.12 Processing the Service Configuration Record
16 The mobile station shall update the Service Configuration information record currently in
17 use as follows:
18 • The mobile station shall store the forward traffic channel multiplex option
19 [FOR_MUX_OPTIONs = FOR_MUX_OPTIONr].
20 • The mobile station shall store the reverse traffic channel multiplex option
21 [REV_MUX_OPTIONs = REV_MUX_OPTIONr].
22 • The mobile station shall store the transmission rates of the forward Fundamental
23 /Dedicated Control traffic channel [FOR_RATESs = FOR_RATESr].
24 • The mobile station shall store the transmission rates of the reverse Fundamental
25 /Dedicated Control traffic channel [REV_RATESs = REV_RATESr].
26 • The mobile station shall delete all instances of current service option connection
27 records. For each of the NUM_CON_RECr occurrences of the service option
28 connection record (SO_CON_REC[i]), the mobile station shall perform the following:
29 – The mobile station shall store the service option connection reference
30 (SO_CON_RECs[i].CON_REF = CON_REFr).
31 – The mobile station shall store the service option

32 (SO_CON_RECs[i].SERVICE_OPTION = SERVICE_OPTIONr).
33 – The mobile station shall store the forward traffic channel traffic type
34 (SO_CON_RECs[i].FOR_TRAFFIC = FOR_TRAFFICr).
35 – The mobile station shall store the reverse traffic channel traffic type
36 (SO_CON_RECs[i].REV_TRAFFIC = REV_TRAFFICr).
2-213
C.S0005-0-2 v1.0
1 – The mobile station shall store the encryption mode indicator for user information
2 privacy (SO_CON_RECs[i].UI_ENCRYPT_MODE = UI_ENCRYPT_MODEr).
3 – The mobile station shall store the service reference identifier

4 (SO_CON_RECs[i].SR_ID = SR_IDr).
5 – If RLP_INFO_INCLr equals ‘1’, the mobile station shall store the Radio Link
6 Protocol block of bits (SO_CON_RECs[i].RLP_BLOB = RLP_BLOBr).
7 • If FCH_CC_INCLr equals ‘1’, the mobile station shall do the following:
8 - The mobile station shall store the indicator for 5ms frames on Fundamental
9 Channel as follows: if FCH_FRAME_SIZEr equals ‘1’, the mobile station shall set
10 FCH_5MS_FRAMESs = ‘1’; otherwise, it is set to ‘0’.
11 - The mobile station shall store the Forward Fundamental Channel Radio
12 Configuration (FOR_FCH_RCs = FOR_FCH_RCr).
13 - The mobile station shall store the Reverse Fundamental Channel Radio
14 Configuration (REV_FCH_RCs = REV_FCH_RCr).
15 • If DCCH_CC_INCLr equals ‘1’, the mobile station shall do the following:
16 - The mobile station shall store the indicator for 5ms frames on Dedicated Control
17 Channel as follows: If DCCH_FRAME_SIZEr equals ‘10’ or ‘11’, the mobile station
18 shall set DCCH_5MS_FRAMESs = ‘1’; otherwise, it is set to ‘0’.
19 - The mobile station shall store the Forward Dedicated Control Channel Radio
20 Configuration (FOR_DCCH_RCs = FOR_DCCH_RCr).
21 - The mobile station shall store the Reverse Dedicated Control Channel Radio
22 Configuration (REV_DCCH_RCs = REV_DCCH_RCr).
23 • If FOR_SCH_CC_INCLr equals ‘1’, the mobile station shall store the NUM_FOR_SCHr
24 occurrences of the Forward Supplemental Channel channel configuration records
25 as follows:
26 - The mobile station shall store the Forward Supplemental Channel Identification
27 (FOR_SCH_ID[FOR_SCH_IDr]s = FOR_SCH_IDr).
28 - The mobile station shall store the Forward Supplemental Channel Multiplex
29 Option (FOR_SCH_MUX[FOR_SCH_IDr]s = FOR_SCH_MUXr).
30 - The mobile station shall store the Forward Supplemental Channel Radio
31 Configuration (FOR_SCH_RC[FOR_SCH_IDr]s = SCH_RCr).
32 - The mobile station shall store the Forward Supplemental Channel Coding Type
33 (FOR_SCH_CODING[FOR_SCH_IDr]s = CODINGr).
34 - The mobile station shall set the Forward Supplemental Channel frame length
35 FOR_SCH_FRAME_LENGTHs[FOR_SCH_IDr] to ‘00’ (i.e., 20 ms frame length).
2-214
C.S0005-0-2 v1.0
1 • If REV_SCH_CC_INCLr equals ‘1’, the mobile station shall store the NUM_REV_SCHr
2 occurrences of the Reverse Supplemental Channel channel configuration records as
3 follows:
4 - The mobile station shall store the Reverse Supplemental Channel Identification
5 (REV_SCH_ID[REV_SCH_IDr]s = REV_SCH_IDr).
6 - The mobile station shall store the Reverse Supplemental Channel Multiplex
7 Option (REV_SCH_MUX[REV_SCH_IDr]s = REV_SCH_MUXr).
8 - The mobile station shall store the Reverse Supplemental Channel Radio
9 Configuration (REV_SCH_RC[REV_SCH_IDr]s = SCH_RCr).
10 - The mobile station shall store the Reverse Supplemental Channel Coding Type
11 (REV_SCH_CODING[REV_SCH_IDr]s = CODINGr).
12 - The mobile station shall set the Reverse Supplemental Channel frame length
13 REV_SCH_FRAME_LENGTHs[REV_SCH_IDr] to ‘00’ (i.e., 20 ms frame length).
14 2.6.4.1.13 Processing the Non-Negotiable Service Configuration Record
15 The mobile station shall update the Non-Negotiable Service Configuration information
16 record currently in use as follows:
17 • If FPC_INCLr equals ‘1’, the mobile station shall do the following:
18 - The mobile station shall store the Power Control Subchannel indicator
19 (FPC_PRI_CHANs = FPC_PRI_CHANr).
20 - The mobile station shall store the forward power control operation mode
21 (FPC_MODE_NO_SCHs = FPC_MODEr).
22 - The mobile station shall set FPC_MODEs = FPC_MODE_NO_SCHs if there is no

23 forward Supplemental Channel assignment in progress (see 2.6.6.2.5.1.1).
24 - If FPC_OLPC_FCH_INCLr equals ‘1’, the mobile station shall do the following:
25 + The mobile station shall store the Fundamental Channel target Frame Error
26 Rate (FPC_FCH_FERs = FPC_FCH_FERr).
27 + The mobile station shall store the minimum Fundamental Channel Outer
28 Loop Eb/Nt setpoint (FPC_FCH_MIN_SETPTs = FPC_FCH_MIN_SETPTr).
29 + The mobile station shall store the maximum Fundamental Channel Outer
30 Loop Eb/Nt setpoint (FPC_FCH_MAX_SETPTs = FPC_FCH_MAX_SETPTr).
31 - If FPC_OLPC_DCCH_INCLr equals ‘1’, the mobile station shall do the following:
32 + The mobile station shall store the Dedicated Control Channel target Frame
33 Error Rate (FPC_DCCH_FERs = FPC_DCCH_FERr).
34 + The mobile station shall store the minimum Dedicated Control Channel
35 Outer Loop Eb/Nt setpoint (FPC_DCCH_MIN_SETPTs =
36 FPC_DCCH_MIN_SETPTr).
37 + The mobile station shall store the maximum Dedicated Control Channel
2-215
C.S0005-0-2 v1.0
1 Outer Loop Eb/Nt setpoint (FPC_DCCH_MAX_SETPTs =

2 FPC_DCCH_MAX_SETPTr).
3 • If GATING_RATE_INCLr equals ‘1’, the mobile station shall store the Reverse Pilot
4 Channel gating rate (PILOT_GATING_RATEs = PILOT_GATING_RATEr).
5 • The mobile station shall determine the Logical-to-Physical Mapping to be used as

6 follows:
7 - If LPM_INDr equals ‘00’, the mobile station shall reset the Logical-to-Physical
8 Mapping to their default values as follows:
9 + Default number of Logical-to-Physical Mapping entries

10 (NUM_LPM_ENTRIESs = ‘0100’).
11 + Default Table(0) Logical-to-Physical Mapping service reference identifier

12 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].SR_IDs = ‘000’).
13 + Default Table(0) Logical-to-Physical Mapping logical resource identifier

14 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].LOGICAL_RESOURCEs =
15 ‘0001’].
16 + Default Table(0) Logical-to-Physical Mapping physical resource identifier:

17 ο If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall set
18 LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].PHYSICAL_RESOURCEs to
19 ‘0000’.
20 ο If CH_INDs is equal to ‘10’, the mobile station shall set
22 ‘0001’.
23 + Default Table(0) Logical-to-Physical Mapping forward mapping indicator

24 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].FORWARD_FLAGs = ‘1’).
25 + Default Table(0) Logical-to-Physical Mapping reverse mapping indicator

26 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].REVERSE_FLAGs = ‘1’).
27 + Default Table(0) Logical-to-Physical Mapping priority

28 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].PRIORITYs = ‘0000’).


33 ‘0000’).
34 + Default Table(1) Logical-to-Physical Mapping physical resource identifier:

35 ο If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall set
37 ‘0000’.
2-216
C.S0005-0-2 v1.0
1 ο If CH_INDs is equal to ‘10’, the mobile station shall set

3 ‘0001’.





14 ‘0000’].
15 + Default Table(2) Logical-to-Physical Mapping physical resource identifier

16 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[2].PHYSICAL_RESOURCEs =
17 ‘0010’).





28 ‘0000’].
29 + Default Table(3) Logical-to-Physical Mapping physical resource identifier

30 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[3].PHYSICAL_RESOURCEs =
31 ‘0011’).



2-217
C.S0005-0-2 v1.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 =
6 NUM_LPM_ENTRIESr). For each ith 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 2.6.4.2 Traffic Channel Initialization Substate
33 In this substate, the mobile station verifies that it can receive the Forward Traffic Channel
34 and begins transmitting on the Reverse Traffic Channel.
35 Upon entering the Traffic Channel Initialization Substate, the mobile station shall perform
36 the following:
37 • The mobile station shall perform registration initialization as specified in 2.6.5.5.4.1.
38 • Layer 3 shall send an L2-Supervision.Request primitive to Layer 2 to reset the

39 acknowledgment procedures as specified in 2.2.1.1 and 2.2.2.1 of of TIA/EIA/IS-
40 2000-[4].
2-218
C.S0005-0-2 v1.0
1 • The mobile station shall initialize Forward Traffic Channel power control as specified
2 in 2.6.4.1.1.1.
3 • The mobile station shall set the following variables to their initial default values
4 given below:
5 – Default power control step size

6 (PWR_CNTL_STEPs = ‘000’)
7 – Default Reverse Discontinuous Transmission Duration on Reverse Supplemental

8 Code Channel (REV_DTX_DURATIONs = ‘0000’)
9 – Default Reverse Discontinuous Transmission Duration on Reverse Supplemental

10 Channel (REV_SCH_DTX_DURATIONs = ‘0000’)
11 – Default Reverse Supplemental Channel power offset adjustment relative to

12 Reverse Pilot Channel power
13 + RLGAIN_SCH_PILOTs [0]= ‘000000’
14 + RLGAIN_SCH_PILOTs [1]= ‘000000’
15 – Default channel on which the mobile station is to perform the primary inner loop
16 estimation and the base station is to multiplex the Power Control Subchannel:
17 + If CH_INDs is equal to ‘01’, the mobile station shall set FPC_PRI_CHANs to
18 ‘0’.
19 + If CH_INDs is equal to ‘10’, the mobile station shall set FPC_PRI_CHANs to
20 ‘1’.
21 – Default forward power control operation mode used except during the forward
22 Supplemental Channel interval
23 (FPC_MODE_NO_SCHs = ‘000’)
24 – Default forward power control operation mode used during the forward
25 Supplemental Channel interval
26 (FPC_MODE_SCHs = ‘000’).
27 – Default forward power control operation mode

28 (FPC_MODEs = ‘000’).
29 – Slotted timer (T_SLOTTEDs =T74m)
30 – Default Reverse Pilot Channel gating (PILOT_GATING_USE_RATE=‘0’)
31 – Default begin preamble for Reverse Supplemental Code Channels

32 (BEGIN_PREAMBLEs = ‘000’)
33 – Default resume preamble for Reverse Supplemental Code Channels

34 (RESUME_PREAMBLEs = ‘000’)
35 – Default start time for Reverse Supplemental Code Channel assignment

36 (REV_START_TIMEs = NULL)
37 – Default retry delays:

38 – RETRY_DELAYs[010] = 0
2-219
C.S0005-0-2 v1.0
1 – RETRY_DELAYs[011] = 0
2 – Default pilot strength reporting offset

3 (T_MULCHANs = ‘000’)
4 – Default start time for forward Supplemental Code Channel Assignment

5 (FOR_START_TIMEs = NULL)
6 – Default number of Reverse Supplemental Code Channels

7 (NUM_REV_CODESs = ‘000’)
8 – Default reverse use T_ADD abort indicator

9 (USE_T_ADD_ABORTs = ‘0’)
10 – Default Supplemental Channel Request Message sequence number

11 (SCRM_SEQ_NUMs = NULL)
12 – Default indicator to ignore reverse Supplemental Code Channel assignment

13 (IGNORE_SCAMs = ‘0’)
14 – Default indicator to ignore reverse Supplemental Channel assignment

15 (IGNORE_ESCAMs = ‘0’)
16 – Default maximum wait time on the CDMA Candidate Frequency

17 (CF_WAIT_TIMEs = ‘1111’)
18 – Default search period for the candidate search

19 (SEARCH_PERIODs = ‘1111’)
20 – Default search window size for the Candidate Frequency Search Set
21 (CF_SRCH_WIN_Ns = SRCH_WIN_Ns)
22 – Default search window size for the Remaining Set on the CDMA Candidate
23 Frequency (CF_SRCH_WIN_Rs = SRCH_WIN_Rs)
24 – Default pilot PN sequence offset increment for the CDMA Candidate Frequency
25 (CF_PILOT_INCs = PILOT_INCs)
26 – Default Candidate Frequency search priorities included indicator

27 (CF_SEARCH_PRIORITY_INCLs =‘0’)
28 – Default Candidate Frequency search window size included indicator

29 (CF_SRCH_WIN_NGHBR_INCLs = ‘0’)
30 – Default Candidate Frequency search window offset included indicator

31 (CF_SRCH_OFFSET_INCLs = ‘0’)
32 – Default periodic search indicator

33 (PERIODIC_SEARCHs = ‘0’)
34 – Default return-if-handoff-fail indicator

35 (RETURN_IF_HANDOFF_FAILs = ‘0’)
36 – Default total pilot Ec/Io threshold

37 (MIN_TOTAL_PILOT_EC_IOs = ‘00000’)
2-220
C.S0005-0-2 v1.0
1 – Default total pilot Ec threshold

2 (SF_TOTAL_EC_THRESHs = ‘11111’)
3 – Default total pilot Ec/Io threshold

4 (SF_TOTAL_EC_IO_THRESHs = ‘11111’)
5 – Default received power difference threshold

6 (DIFF_RX_PWR_THRESHs = ‘00000’)
7 – Default maximum wait time on the CDMA Target Frequency

8 (TF_WAIT_TIMEs = ‘1111’)
9 – Default Candidate Frequency Search Set

10 (Candidate Frequency Search Set is empty)
11 – Default Analog Frequency Search Set

12 (Analog Frequency Search Set is empty)
13 – Default Candidate Frequency CDMA band

14 (CF_CDMABANDs = NULL)
15 – Default Candidate Frequency CDMA channel

16 (CF_CDMACHs = NULL)
17 – Default indicator for 5ms frames on Fundamental Channel

18 (FCH_5MS_FRAMESs = ‘0’)
19 – Default indicator for 5ms frames on Dedicated Control Channel

20 (DCCH_5MS_FRAMESs = ‘0’)
21 – Default start time unit for Supplemental Channel

22 (START_TIME_UNITs = ‘000’).
23 – Default Forward Supplemental Channel FER report indicator

24 (FOR_SCH_FER_REPs = ‘0’).
25 – Default Forward Supplemental Channel Configuration parameters:
26 + Set the Forward Supplemental Channel frame length

27 FOR_SCH_FRAME_LENGTHs[0] to NULL.
28 + Set the Forward Supplemental Channel Multiplex Option FOR_SCH_MUXs[0]

29 to NULL.
30 + Set the Forward Supplemental Channel Radio Configuration

31 FOR_SCH_RCs[0] to NULL.
32 + Set the Forward Supplemental Channel Coding Type FOR_SCH_CODINGs[0]

33 to NULL.
34 + Set QOF_IDs[0][SCCL_INDEXs][i] to NULL, for all integer values of i from 0 to
35 15.
36 + Set FOR_SCH_CC_INDEXs [0][SCCL_INDEXs][i] to NULL, for all integer
37 values of i from 0 to 15.
2-221
C.S0005-0-2 v1.0
1 + Set the Forward Supplemental Channel frame length

2 FOR_SCH_FRAME_LENGTHs[1] to NULL.
3 + Set the Forward Supplemental Channel Multiplex Option FOR_SCH_MUXs[1]

4 to NULL.
5 + Set the Forward Supplemental Channel Radio Configuration

6 FOR_SCH_RCs[1] to NULL.
7 + Set the Forward Supplemental Channel Coding Type FOR_SCH_CODINGs[1]

8 to NULL.
9 + Set QOF_IDs[1][SCCL_INDEXs][i] to NULL, for all integer values of i from 0 to
10 15.
11 + Set FOR_SCH_CC_INDEXs [1][SCCL_INDEXs][i] to NULL, for all integer
12 values of i from 0 to 15.
13 – Default Reverse Supplemental Channel Configuration parameters:

14 + REV_WALSH_IDs[0][0000] = 1
15 + REV_WALSH_IDs[0][0001] = 1
16 + REV_WALSH_IDs[0][0010] = 1
17 + REV_WALSH_IDs[0][0011] = 1
18 + REV_WALSH_IDs[0][0100] = 0
19 + REV_WALSH_IDs[0][0101] = 0
20 + REV_WALSH_IDs[0][0110] = 0
21 + REV_WALSH_IDs[1][0000] = 1
22 + REV_WALSH_IDs[1][0001] = 1
23 + REV_WALSH_IDs[1][0010] = 1
24 + REV_WALSH_IDs[1][0011] = 0
25 + REV_WALSH_IDs[1][0100] = 0
26 + REV_WALSH_IDs[1][0101] = 0
27 + REV_WALSH_IDs[1][0110] = 0
28 + Set the Reverse Supplemental Channel frame length

29 REV_SCH_FRAME_LENGTHs[0] to NULL.
30 + Set the Reverse Supplemental Channel Multiplex Option REV_SCH_MUXs[0]

31 to NULL.
32 + Set the Reverse Supplemental Channel Radio Configuration

33 REV_SCH_RCs[0] to NULL.
34 + Set the Reverse Supplemental Channel Coding Type REV_SCH_CODINGs[0]

35 to NULL.
2-222
C.S0005-0-2 v1.0
1 + Set the Reverse Supplemental Channel frame length

2 REV_SCH_FRAME_LENGTHs[1] to NULL.
3 + Set the Reverse Supplemental Channel Multiplex Option REV_SCH_MUXs[1]

4 to NULL.
5 + Set the Reverse Supplemental Channel Radio Configuration

6 REV_SCH_RCs[1] to NULL.
7 + Set the Reverse Supplemental Channel Coding Type REV_SCH_CODINGs[1]

8 to NULL.
9 – Default number of Logical-to-Physical Mapping entries

10 (NUM_LPM_ENTRIESs = ‘0100’)
11 – Default Table(0) Logical-to-Physical Mapping service reference identifier

12 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].SR_IDs = ‘000’)
13 – Default Table(0) Logical-to-Physical Mapping logical resource identifier

14 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].LOGICAL_RESOURCEs = ‘0001’)
15 – Default Table(0) Logical-to-Physical Mapping physical resource identifier:

16 + If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall set
18 ‘0000’.
19 + If CH_INDs is equal to ‘10’, the mobile station shall set
21 ‘0001’.
22 – Default Table(0) Logical-to-Physical Mapping forward mapping indcator

23 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].FORWARD_FLAGs = ‘1’)
24 – Default Table(0) Logical-to-Physical Mapping reverse mapping indicator

25 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].REVERSE_FLAGs = ‘1’)
26 – Default Table(0) Logical-to-Physical Mapping priority

27 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[0].PRIORITYs = ‘0000’)


32 – Default Table(1) Logical-to-Physical Mapping physical resource identifier:

33 + If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall set
35 ‘0000’.
36 + If CH_INDs is equal to ‘10’, the mobile station shall set
38 ‘0001’.
2-223
C.S0005-0-2 v1.0
1 – Default Table(1) Logical-to-Physical Mapping forward mapping indicator





10 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[2].LOGICAL_RESOURCEs = ‘0000’).
11 – Default Table(2) Logical-to-Physical Mapping physical resource identifier

12 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[2].PHYSICAL_RESOURCEs = ‘0010’).





23 – Default Table(3) Logical-to-Physical Mapping physical resource identifier

24 (LOGICAL_TO_PHYSICAL_MAPPING_TABLE[3].PHYSICAL_RESOURCEs = ‘0011’)



31 • The mobile station shall disable the TMS_Slotted timer, and set SLOTTEDs to YES.
32 • If the ASSIGN_MODEr field from the Channel Assignment Message equals ‘000’, the
33 mobile station shall set SERV_NEGs to disabled.
34 • If the ASSIGN_MODEr field from the Channel Assignment Message equals ‘100’, the
35 mobile station shall set SERV_NEGs to enabled.
36 • The mobile station shall determine the service configuration as follows:
2-224
C.S0005-0-2 v1.0
1 – If SERV_NEGs equals disabled, the initial service configuration shall include

2 Multiplex Option 1 and Radio Configuration 1 for both the Forward and Reverse
3 Traffic Channels, and shall include no service option connections.
4 – If SERV_NEGs equals enabled, and if GRANTED_MODEs equals ‘00’, the initial
5 service configuration shall include the multiplex option and radio configuration
6 for the Forward and Reverse Traffic Channels as specified by
7 DEFAULT_CONFIGs, and shall include no service option connections.
8 – If SERV_NEGs equals enabled and GRANTED_MODEs equals ‘01’ or ‘10’, the

9 initial service configuration shall include the default Forward and Reverse Traffic
10 Channel multiplex options and transmission rates corresponding to the service
11 option requested by the mobile station in the Origination Message, in the case of
12 a mobile station originated call, or the Page Response Message, in the case of a
13 mobile station terminated call, and shall include no service option connections.
14 – If SERV_NEGs equals disabled, the mobile station shall perform the following:
15 + If the call is mobile station originated and the Origination Message requests a
16 special service option, the mobile station shall set SO_REQs to the special
17 service option number.
18 + If the call is mobile station originated and the Origination Message does not
19 request a special service option, the mobile station shall set SO_REQs to 1
20 (the default service option number).
21 + If the call is mobile station terminated, the mobile station shall set SO_REQs
22 to the service option number requested in the Page Response Message.
23 While in the Traffic Channel Initialization Substate, the mobile station shall perform the
24 following:
25 • The mobile station shall monitor Forward Traffic Channels associated with one or
26 more pilots in the Active Set.
27 • The mobile station shall perform pilot strength measurements as specified in

28 2.6.6.2.2, but shall not send Pilot Strength Measurement Messages.
29 • The mobile station shall perform registration timer maintenance as specified in

30 2.6.5.5.4.2.
37 If the mobile station does not support the assigned CDMA Channel (see 2.1.1 and 3.1.1 of
38 TIA/EIA/IS-2000-[2]) or all of the assigned Forward Traffic code channels (see 2.1.3.1.9 of
39 TIA/EIA/IS-2000-[2]), the mobile station shall enter the System Determination Substate of
40 the Mobile Station Initialization State with an error indication (see 2.6.1.1).
2-225
C.S0005-0-2 v1.0
1 If the mobile station supports the assigned CDMA Channel and the assigned Forward
2 Traffic code channels, the mobile station shall perform the following:
3 • The mobile station shall tune to the assigned CDMA Channel.
4 • The mobile station shall set its code channel for the assigned Forward Traffic code
5 channel.
6 • The mobile station shall set its Forward and Reverse Traffic Channel frame offsets to
7 the assigned frame offset as determined by FRAME_OFFSETs.
8 • The mobile station shall set its Forward and Reverse Traffic Channel long code
9 masks to the public long code mask (see 2.1.3.1.12 of TIA/EIA/IS-2000-[2]).
10 If the mobile station does not receive a period of (N5m × 20) ms with sufficient signal
11 quality (e.g. good frames) on the physical channel corresponding to FPC_PRI_CHANs within
12 T50m seconds after entering this substate, the mobile station shall enter the System
13 Determination Substate of the Mobile Station Initialization State with a system lost indication
14 (see 2.6.1.1).
15 If the mobile station receives a period of (N5m × 20) ms with sufficient signal quality (e.g.
16 good frames) on the physical channel corresponding to FPC_PRI_CHANs within T50m
17 seconds after entering this substate, the mobile station shall perform the following
18 additional functions while it remains in the Traffic Channel Initialization Substate:
19 • The mobile station shall perform Forward Traffic Channel supervision as specified in
20 2.6.4.1.8. If a loss of the Forward Traffic Channel is declared, the mobile station
21 shall enter the System Determination Substate of the Mobile Station Initialization State
23 • The mobile station shall adjust its transmit power as specified in 2.1.2.3 of
24 TIA/EIA/IS-2000-[2].
25 • The mobile station shall transmit the Traffic Channel preamble as specified in
26 2.1.3.6.2.3 and 2.1.3.7.2.3 of TIA/EIA/IS-2000-[2], and Layer 3 shall send an
27 acquiring dedicated channel indication to Layer 2 (see 2.2.2.1.2 of TIA/EIA/IS-2000-
28 [4]).
29 • The mobile station shall process Forward Traffic Channel signaling traffic and shall
30 discard other types of Forward Traffic Channel traffic.
31 • If Layer 3 receives a L2-Condition.Notification primitive from Layer 2 indicating an

32 acknowledgment failure, the mobile station shall disable its transmitter and enter
35 The mobile station should provide diversity combining of the Forward Traffic Channels
36 associated with pilots in the Active Set if the mobile station receives multiple pilots in the
37 Extended Channel Assignment Message.
38 If Layer 3 does not receive a forward dedicated channel acquired indication from Layer 2 (see
39 2.2.2.1.2 of TIA/EIA/IS-2000-[4]) within T51m seconds after the first occurrence of
40 receiving a period of (N5m × 20) ms with sufficient signal quality (e.g. good frames) on the
2-226
C.S0005-0-2 v1.0
1 physical channel corresponding to FPC_PRI_CHANs, the mobile station shall disable its
2 transmitter and enter the System Determination Substate of the Mobile Station Initialization
3 State with a system lost indication (see 2.6.1.1).
4 If Layer 3 receives a forward dedicated channel acquired indication from Layer 2 within
5 T51m seconds after the first occurrence of receiving a period of (N5m × 20) ms with
6 sufficient signal quality (e.g. good frames) on the physical channel corresponding to
7 FPC_PRI_CHANs, the mobile station shall perform the following:
8 • If CH_INDs is equal to ‘01’ or ‘11’, the mobile station shall begin transmitting on the
9 Reverse Fundamental Channel.
10 • If CH_INDs is equal to ‘10’ or ‘11’, the mobile station shall begin transmitting on the
11 Reverse Dedicated Control Channel when the mobile station has user data or
12 signaling traffic to send on the Reverse Dedicated Control Channel.
13 • If SERV_NEGs equals disabled, the mobile station shall activate the SO Negotiation
14 Subfunction.
15 • If SERV_NEGs equals enabled and the GRANTED_MODEs is ‘00’ or ‘01’, the mobile
17 • If SERV_NEGs equals enabled and the GRANTED_MODEs is ‘10’, the mobile station
19 • If the call is mobile station terminated, and BYPASS_ALERT_ANSWERs is ‘1’, the
20 mobile station shall enter the Conversation Substate. If the call is mobile station
21 terminated and BYPASS_ALERT_ANSWERs is ‘0’, the mobile station shall enter the
22 Waiting for Order Substate.
23 • If the call is mobile station originated, the mobile station shall enter the
24 Conversation Substate.
25 2.6.4.3 Alerting
26 2.6.4.3.1 Waiting for Order Substate

27 In this substate, the mobile station waits for an Alert With Information Message.
28 Upon entering the Waiting for Order Substate, the mobile station shall set the substate
29 timer for T52m seconds.
30 While in the Waiting for Order Substate, the mobile station shall perform the following:
31 • If the substate timer expires, the mobile station shall disable its transmitter and
33 a system lost indication (see 2.6.1.1).
34 • The mobile station may send a Pilot Strength Measurement Mini Message to report
35 pilot strength order change information, periodic pilot strength information, or
36 threshold based pilot strength information, as specified in the Mobile Assisted Burst
37 Operation Parameters Message.
2-227
C.S0005-0-2 v1.0
6 TIA/EIA/IS-2000-[2].
7 • The mobile station shall perform Forward Traffic Channel power control as specified
8 in 2.6.4.1.1.
9 • The mobile station shall perform handoff processing as specified in 2.6.6.
11 accordance with requirements for the active service subfunction (see 2.6.4.1.2.2).

13 2.6.5.5.4.2.
14 • If the mobile station is directed by the user to transmit a message, the mobile
15 station shall send a Data Burst Message.
16 • If the mobile station is directed by the user to request a new service configuration,
17 the mobile station shall initiate service negotiation or service option negotiation in
18 accordance with the requirements for the active service subfunction (see
19 2.6.4.1.2.2).
20 • The mobile station may send a Service Option Control Message or Service Option
21 Control Order to invoke a service option specific function in accordance with the
22 requirements for the active service subfunction (see 2.6.4.1.2.2).
23 • If the mobile station is directed by the user to request a private long code transition
24 and has the long code mask (see 2.3.12.3), the mobile station shall send a Long
25 Code Transition Request Order (ORDQ = ‘00000001’) in assured mode.
26 • If the mobile station is directed by the user to request a public long code transition,
27 the mobile station shall send a Long Code Transition Request Order (ORDQ =
28 ‘00000000’) in assured mode.
29 • If the mobile station is directed by the user to operate in analog mode, allowing
30 operation in either wide or narrow analog mode, the mobile station shall send the
31 Request Analog Service Order in assured mode.
32 • If the mobile station is directed by the user to operate in wide analog mode, the
33 mobile station shall send the Request Wide Analog Service Order in assured mode.
34 • If the mobile station is directed by the user to operate in narrow analog mode, the
35 mobile station shall send the Request Narrow Analog Service Order in assured mode.
36 • If the mobile station is directed by the user to power down, the mobile station shall
37 enter the Release Substate with a power-down indication (see 2.6.4.5).
2-228
C.S0005-0-2 v1.0

5 • If the mobile station receives a message which is included in the following list and
6 every message field value is within its permissible range, the mobile station shall
7 process the message as described below and in accordance with the message’s
8 action time (see 2.6.4.1.5).
9 1. Alert With Information Message: If the message contains a Signal information
10 record, the mobile station should alert the user in accordance with the Signal
11 information record; otherwise, the mobile station should use standard alert as
12 defined in 3.7.5.5. The mobile station shall enter the Waiting for Mobile Station
13 Answer Substate (see 2.6.4.3.2).
14 2. Analog Handoff Direction Message: If the analog mode directed by the base
15 station is supported by the mobile station, the mobile station shall process the
16 message as specified in 2.6.6.2.9, and enter the Waiting For Order Task (see of
17 TIA/EIA/IS-2000-[6] for handoff to a wide analog channel and 2.6.5.3.1A of
18 TIA/EIA/IS-91-A[28] for handoff to an 800 MHz narrow analog channel). If the
19 mobile station is directed to an unsupported operation mode or band class, the
20 mobile station shall respond with a Mobile Station Reject Order with ORDQ equal
21 to ‘00000110’ (message requires a capability that is not supported by the mobile
22 station).
23 3. Audit Order
24 4. Authentication Challenge Message: The mobile station shall reset the substate
25 timer for T52m seconds. The mobile station shall then process the message and
26 respond as specified in 2.3.12.1.4 within T32m seconds, regardless of the value
27 of AUTHs.
28 5. Base Station Challenge Confirmation Order: The mobile station shall reset the
29 substate timer for T52m seconds. The mobile station shall then process the
30 message and respond with an SSD Update Confirmation Order or SSD Update
31 Rejection Order as specified in 2.3.12.1.5 within T32m seconds.
32 6. Candidate Frequency Search Control Message: The mobile station shall process
33 the message as specified in 2.6.6.2.5.1.
34 7. Candidate Frequency Search Request Message: The mobile station shall process
37 9. Extended Handoff Direction Message: If the band class is not specified in the
38 message or the specified band class is supported by the mobile station, the
39 mobile station shall process the message as specified in 2.6.6.2.5.1. The mobile
40 station shall reset the substate timer for T52m seconds.
41 10. Extended Neighbor List Update Message: The mobile station shall process the
2-229
C.S0005-0-2 v1.0
1 message as specified in 2.6.6.2.6.3.
2 11. Extended Release Message: The mobile station shall process the message as
3 specified in 2.6.4.1.9.
4 12. Extended Release Mini Message: The mobile station shall process the message
5 as specified in 2.6.4.1.11.
6 13. Extended Supplemental Channel Assignment Message: The mobile station shall
7 process the message as specified in 2.6.6.2.5.1.
8 14. General Handoff Direction Message: If the band class is not specified in the
9 message or the specified band class is supported by the mobile station, the
10 mobile station shall process the message as specified in 2.6.6.2.5.1. The mobile
11 station shall reset the substate timer for T52m seconds. If the message
12 contains a service configuration record, the mobile station shall process the
13 message in accordance with the requirements for the active service subfunction
14 (see 2.6.4.1.2.2).
15 15. In-Traffic System Parameters Message: The mobile station shall process the
18 17. 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 mobile station shall enter the System Determination Substate of
23 the Mobile Station Initialization State with a lock indication (see 2.6.1.1), and
24 shall not enter the System Access State again until after the next mobile station
25 power-up or until it has received an Unlock Order. This requirement shall take
27 System Access State.
28 18. Long Code Transition Request Order: The mobile station shall process the
30 19. Maintenance Order: The mobile station shall enter the Waiting for Mobile Station
31 Answer Substate.
34 (MAINTRSNs-p equals the least significant four bits of ORDQr). The mobile
35 station shall remain in the unlocked condition. The mobile station should
36 notify the user of the maintenance required condition.
37 21. Message Encryption Mode Order: The mobile station shall process the message
38 as specified in 2.3.12.2.
39 22. Mobile Station Registered Message: The mobile station shall process the
2-230
C.S0005-0-2 v1.0
1 23. Mobile Assisted Burst Operation Parameters Message: The mobile station shall
3 24. Neighbor List Update Message: The mobile station shall process the message as
4 specified in 2.6.6.2.6.3.
5 25. Outer Loop Report Request Order: The mobile station shall send the Outer Loop
6 Report Message in assured mode to the base station.
7 26. Parameter Update Order: The mobile station shall reset the substate timer for
8 T52m seconds. The mobile station shall increment COUNTs-p (see 2.3.12.1.3).
9 The mobile station shall send a Parameter Update Confirmation Order within
10 T56m seconds. The mobile station shall set the ORDQ field of the Parameter
11 Update Confirmation Order to the same value as the ORDQ field of the Parameter
12 Update Order.
13 27. Periodic Pilot Measurement Request Order: The mobile station shall process the
14 order as specified in 2.6.6.2.5.1.
15 28. Pilot Measurement Request Order: The mobile station shall process the order as
16 specified in 2.6.6.2.5.1.
17 29. Power Control Message: The mobile station shall process the message as
18 specified in 2.6.4.1.1.3.
19 30. Power Control Parameters Message: The mobile station shall process the
21 31. Power Up Function Message: The mobile station shall process the message as
22 specified in 2.6.4.1.7.1.
23 32. Power Up Function Completion Message: The mobile station shall process the
25 33. Release Order: The mobile station shall enter the Release Substate with a base
26 station release indication (see 2.6.4.5).
27 34. Resource Allocation Message: The mobile station shall process the message as
29 35. Resource Allocation Mini Message: The mobile station shall process the message
31 36. Retrieve Parameters Message: The mobile station shall send, within T56m
32 seconds, a Parameters Response Message.
35 RETRY_DELAYs[RETRY_TYPE] to ‘0’, where RETRY_TYPE is equal to ‘001’,
36 ‘010’, or ‘011’.
38 following:
2-231
C.S0005-0-2 v1.0
1 − If RETRY_DELAYr is equal to ‘00000000’, then the mobile station shall

2 set RETRY_DELAYs [RETRY_TYPEr] to 0.


8 + The mobile station shall set RETRY_DELAY_VALUEs to the seven

9 least significant bits of RETRY_DELAYr.
13 • If RETRY_TYPEr is equal to ‘010’ or ‘011’, the mobile station shall perform

14 the following:
15 – If RETRY_DELAYr[RETRY_TYPEr] is ‘00000000’, then the mobile station
16 shall set RETRY_DELAYs [RETRY_TYPEr] to ‘0’.

18 shall set RETRY_DELAYs[RETRY_TYPEr] to infinity.
19 – If RETRY_DELAYr[RETRY_TYPEr] is not equal to ‘00000000’ or

20 ‘11111111’, the mobile station shall store the next system time 80 ms
21 boundary + RETRY_DELAYr[RETRY_TYPEr] × 320 ms as
23 38. Reverse Supplemental Channel Assignment Mini Message: The mobile station
24 shall process the message as specified in 2.6.6.2.5.1.
25 39. Service Connect Message: The mobile station shall process the message in
27 2.6.4.1.2.2).
28 40. Service Option Control Message: The mobile station shall process the message
29 in accordance with the requirements for the active service subfunction (see
30 2.6.4.1.2.2).
31 41. Service Option Control Order: The mobile station shall process the message in
33 2.6.4.1.2.2).
34 42. Service Option Request Order: The mobile station shall process the message in
36 2.6.4.1.2.2).
37 43. Service Option Response Order: The mobile station shall process the message in
39 2.6.4.1.2.2).
2-232
C.S0005-0-2 v1.0
1 44. Service Request Message: The mobile station shall process the message in
3 2.6.4.1.2.2).
4 45. Service Response Message: The mobile station shall process the message in
6 2.6.4.1.2.2).
7 46. 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 47. SSD Update Message: The mobile station shall reset the substate timer for
12 T52m seconds. The mobile station shall then process the message and respond
13 with a Base Station Challenge Order as specified in 2.3.12.1.5 within T32m
14 seconds.
15 48. Status Request Message: The mobile station shall send, within T56m seconds, a
16 Status Response Message. If the message does not specify any qualification
17 information (QUAL_INFO_TYPEr is equal to ‘00000000’), the mobile station shall
18 include the requested information records in the Status Response Message. If
19 the message specifies a band class (QUAL_INFO_TYPEr is equal to ‘00000001’),
20 the mobile station shall only include the requested information records for the
21 specified band class (BAND_CLASSr) in the Status Response Message. If the
22 message specifies a band class and an operating mode (QUAL_INFO_TYPEr is
25 mode (OP_MODEr) in the Status Response Message. If the message specifies a
26 band class or a band class and an operating mode which is not supported by
28 with ORDQ set to ‘00000110’ (message requires a capability that is not
31 ORDQ set to ‘00001000’ (response message would exceed the allowable length).
32 If the message specifies an information record which is not supported by the
33 mobile station for the specified band class and operating mode, the mobile
34 station shall send a Mobile Station Reject Order with ORDQ set to ‘00001001’
35 (information record is not supported for the specified band class and operating
36 mode).
37 49. Status Request Order: If CDMABANDs is equal to ‘00000’, the mobile station
38 shall send, within T56m seconds, a Status Message. The mobile station shall
39 respond with information corresponding to the current band class and
40 operating mode.
41 50. Supplemental Channel Assignment Message: The mobile station shall process
43 51. TMSI Assignment Message: The mobile station shall store the TMSI zone and
2-233
C.S0005-0-2 v1.0
1 code as follows:
8 TMSI_CODEr.
13 52. Universal Handoff Direction Message: The mobile station process the message
14 specified in 2.6.6.2.5.1. The mobile station shall reset the substate timer for
15 T52m seconds. If the message contains a service configuration record, the
16 mobile station shall process the message in accordance with the requirements
17 for the active service subfunction (se 2.6.4.1.2.2).
18 • If the mobile station receives a message that is not included in the above list, cannot
19 be processed, or requires a capability which is not supported, the mobile station
20 shall discard the message and send a Mobile Station Reject Order (ORDQ set to the
21 applicable reason code as determined from Table 2.7.3-1) within T56m seconds.
28 2.6.4.3.2 Waiting for Mobile Station Answer Substate
29 In this substate, the mobile station waits for the user to answer the mobile station
30 terminated call or to invoke special treatment.
31 Upon entering the Waiting for Mobile Station Answer Substate, the mobile station shall set
32 the substate timer for T53m seconds.
33 While in the Waiting for Mobile Station Answer Substate, the mobile station shall perform the
34 following:
2-234
C.S0005-0-2 v1.0
4 Operation Parameters Request Message.
10 TIA/EIA/IS-2000-[2].
12 in 2.6.4.1.1.

17 2.6.5.5.4.2.
18 • If the mobile station is directed by the user to answer the call, the mobile station
19 shall send a Connect Order in assured mode. The mobile station shall enter the
20 Conversation Substate.
21 • If the mobile station is directed by the user to transmit a message, the mobile
22 station shall send a Data Burst Message.
26 2.6.4.1.2.2).
27 • If the mobile station is directed by the user to forward the incoming call, the mobile
28 station shall send a Flash With Information Message in assured mode with a Keypad
29 Facility information record (see 2.7.4.2) with the CHARi field set to a pre-
30 programmed feature code which indicates User Selective Call Forwarding with a pre-
31 registered number.
32 • If the mobile station is directed by the user to forward the incoming call to a number
33 stored in the mobile station, the mobile station shall send a Flash With Information
34 Message in assured mode with a Keypad Facility information record (see 2.7.4.2)
35 with the CHARi field set to the following:
36 - A pre-programmed feature code which indicates User Selective Call Forwarding

37 to a number stored in the mobile station as the first digits in the field and
38 - The forwarding to number immediately following the pre-programmed feature

39 code.
2-235
C.S0005-0-2 v1.0
1 • If the mobile station is directed by the user to forward the incoming call to network-
2 based voice mail, the mobile station shall send a Flash With Information Message in
3 assured mode with a Keypad Facility information record (see 2.7.4.2) with the
4 CHARi field set to a pre-programmed feature code which indicates User Selective
5 Call Forwarding to voice mail.
6 • If the mobile station is directed by the user to activate answer holding, the mobile
7 station shall send a Flash With Information Message in assured mode requiring
8 confirmation of delivery with a Keypad Facility information record (see 2.7.4.2) with
9 the CHARi field set to a pre-programmed feature code which indicates Answer
10 Holding. After receiving confirmation of delivery of the Flash With Information
11 Message, the mobile station shall send a Connect Order in assured mode. The
12 mobile station shall enter the Conversation Substate.

39 1. Alert With Information Message: The mobile station shall reset the substate
40 timer for T53m seconds. If the Alert With Information Message does not contain
41 a Signal information record, the mobile station should use standard alert as
42 defined in 3.7.5.5.
2-236
C.S0005-0-2 v1.0
3 message as specified in 2.6.6.2.9 and enter the Waiting For Answer Task (see
4 2.6.4.3.2 for handoff to a wide analog channel and 2.6.5.3.2A of TIA/EIA/IS-91-
5 A[28] for handoff to an 800 MHz narrow analog channel). If the mobile station
6 is directed to an unsupported operation mode or band class, the mobile station
7 shall respond with a Mobile Station Reject Order with ORDQ equal to ‘00000110’
8 (message requires a capability that is not supported by the mobile station).
9 3. Audit Order
10 4. Authentication Challenge Message: The mobile station shall process the

11 message and respond as specified in 2.3.12.1.4 within T32m seconds, regardless
12 of the value of AUTHs.
14 message and respond with an SSD Update Confirmation Order or SSD Update
15 Rejection Order as specified in 2.3.12.1.5 within T32m seconds.
22 message or the specified band is supported by the mobile station, the mobile
23 station shall process the message as specified in 2.6.6.2.5.1.
32 14. Forward Supplemental Channel Assignment Mini Message: The mobile station
36 station shall process the message as specified in 2.6.6.2.5.1. If the message
39 (see 2.6.4.1.2.2).
2-237
C.S0005-0-2 v1.0
5 station’s semi-permanent memory (LCKRSN_Ps-p equals the least-significant
15 20. Maintenance Order: The mobile station shall reset the substate timer for T53m
16 seconds.
19 (MAINTRSNs-p equals the least-significant four bits of ORDQr). The mobile
29 specified in 2.6.6.2.6.3.
32 27. Parameter Update Order: The mobile station shall increment COUNTs-p (see
33 2.3.12.1.3). The mobile station shall send a Parameter Update Confirmation
34 Order within T56m seconds. The mobile station shall set the ORDQ field of the
35 Parameter Update Confirmation Order to the same value as the ORDQ field of the
36 Parameter Update Order.
40 specified in 2.6.6.2.5.1.
2-238
C.S0005-0-2 v1.0
17 RETRY_DELAYs[RETRY_TYPE] to 0, where RETRY_TYPE is equal to ‘001’,
18 ‘010’, or ‘011’.
20 following:




34 the following:
36 shall set RETRY_DELAYs [RETRY_TYPEr] to 0.

2-239
C.S0005-0-2 v1.0

11 2.6.4.1.2.2).
14 2.6.4.1.2.2).
17 2.6.4.1.2.2).
20 2.6.4.1.2.2).
23 2.6.4.1.2.2).
26 2.6.4.1.2.2).
29 2.6.4.1.2.2).
34 48. SSD Update Message: The mobile station shall process the message and
35 respond with a Base Station Challenge Order as specified in 2.3.12.1.5 within
36 T32m seconds.
2-240
C.S0005-0-2 v1.0

8 band class or a band class and an operating mode which is not supported by
13 ORDQ set to ‘00001000’ (response message would exceed the allowable length).
18 mode).
20 shall send, within T56m seconds, a Status Message. The mobile station shall
22 operating mode.
26 code as follows:
33 TMSI_CODEr.
38 53. Universal Handoff Direction Message: The mobile station shall process the
39 message as specified in 2.6.6.2.5.1. If the message contains a service
40 configuration record, the mobile station shall process the message in
42 2.6.4.1.2.2)
2-241
C.S0005-0-2 v1.0
11 2.6.4.4 Conversation Substate
12 In this substate, the mobile station exchanges Traffic Channel frames with the base station
13 in accordance with the current service configuration. The mobile station may perform the
14 gating operation of Reverse Pilot Channel.
15 The mobile station can be in the Active Mode or Control Hold Mode while in this substate.
16 The following are the attributes when the mobile station is in the Active Mode of
17 Conversation Substate:
18 • PILOT_GATING_USE_RATE is set to ‘0’ (i.e., the reverse pilot (r-pich) is not gated).
19 • Flow of data traffic is permitted by the Multiplex Sublayer.

20 The following are the attributes when the mobile station is in the Control-Hold Mode of
21 Conversation Substate:
22 • PILOT_GATING_USE_RATE is set to ‘1’.

23 • The reverse pilot (r-pich) may be gated (if PILOT_GATING_RATEs is not equal to ‘00’).
24 • Flow of data traffic is blocked by the Multiplex Sublayer.
25
26 Figure 2.6.4.4-1 shows the valid transitions between the modes of a Conversation Substate
27 and the over-the-air Upper Layer Signaling Messages that trigger transitions between these
28 mode.
29
2-242
C.S0005-0-2 v1.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.4-1. Mobile Station Modes

3 Upon entering the Conversation Substate, the mobile station shall perform the following:
4 • If SERV_NEGs equals enabled, the call is mobile station originated, and
5 GRANTED_MODEs is equal to ‘00’ or ‘01’, the mobile station should initiate service
6 negotiation to request a service configuration in accordance with the requirements
7 for the active service subfunction (see 2.6.4.1.2.2).
8 While in the Conversation Substate, the mobile station shall perform the following:
16 Operation Parameters Message (see 2.6.6.2.5.2).
18 TIA/EIA/IS-2000-[2].
20 in 2.6.4.1.1.
2-243
C.S0005-0-2 v1.0

4 2.6.5.5.4.2.
5 • The mobile station shall send an Origination Continuation Message in assured mode,
6 within T54m seconds after entering the Conversation Substate if any of the following
7 conditions occur:
8 – The mobile station originated the call and did not send all the dialed digits in the
9 Origination Message.
10 – There is more than one calling party number associated with the mobile station.
11 – A calling party subaddress is used in the call.
12 – A called party subaddress is used in the call.
13 If more than one calling party number is associated with the mobile station, the
14 mobile station shall include the calling party number being used in the calling party
15 number information record in the Origination Continuation Message. If only one
16 calling party number is associated with the mobile station, the mobile station shall
17 not include the calling party number information record in the Origination
18 Continuation Message. If a calling party subaddress is used, the mobile station shall
19 include the calling party subaddress information record in the Origination
20 Continuation Message: otherwise, the mobile station shall omit the calling party
21 subaddress information record. If a called party subaddress is used, the mobile
22 station shall include the called party subaddress information record in the
23 Origination Continuation Message: otherwise, the mobile station shall omit the calling
24 party subaddress information record.
25 • If the mobile station is directed to send a Data Burst Message, the mobile station
26 shall send a Data Burst Message. If PILOT_GATING_USE_RATE is set to ‘1’, the
27 mobile station may request to transition to the Active Mode
28 (PILOT_GATING_USE_RATE set to ‘0’) prior to sending the Data Burst Message.
29
33 2.6.4.1.2.2).
2-244
C.S0005-0-2 v1.0
4 • If the mobile station is directed by the user to issue a flash, the mobile station shall
5 build a Flash With Information Message with the collected digits or characters
6 contained in a Keypad Facility information record, if needed, and shall send the
7 message in assured mode.
8 • If the mobile station is directed by the user to forward the incoming call, the mobile
9 station shall send a Flash With Information Message in assured mode with a Keypad
10 Facility information record (see 2.7.4.2) with the CHARi field set to a pre-
11 programmed feature code which indicates User Selective Call Forwarding with a pre-
12 registered number.
13 • If the mobile station is directed by user to forward the incoming call to a number
14 stored in the mobile station, the mobile station shall send a Flash With Information
15 Message in assured mode with a Keypad Facility information record (see 2.7.4.2)
16 with the CHARi field set to the following:
17 - A pre-programmed feature code which indicates User Selective Call Forwarding

18 to a number stored in the mobile station as the first digits in the field and
19 - The forwarding to number immediately following the pre-programmed feature

20 code.
21 • If the mobile station is directed by the user to forward the incoming call to network-
22 based voice mail, the mobile station shall send a Flash With Information Message in
24 CHARi field set to a pre-programmed feature code which indicates User Selective
25 Call Forwarding to voice mail.
26 • If answer holding is activated and the mobile station is directed by the user to
27 deactivate answer holding, or if the mobile station is directed by the user to activate
28 answer holding, the mobile station shall send a Flash With Information Message in
30 CHARi field set to a pre-programmed feature code which indicates Answer Holding.
31 • If the mobile station is directed by the user to send burst DTMF digits, the mobile
32 station shall build the Send Burst DTMF Message with the dialed digits and shall
33 send the message in assured mode requiring confirmation of delivery. The mobile
34 station sending multiple Send Burst DTMF Messages shall preserve relative ordering
35 of these messages (see 1.6 of TIA/EIA/IS-2000-[4]). The mobile station should
36 attempt to preserve the user timing as much as possible, using recommended values
37 of DTMF_ON_LENGTH (see Table 2.7.2.3.2.7-1) and DTMF_OFF_LENGTH (see Table
38 2.7.2.3.2.7-2).
2-245
C.S0005-0-2 v1.0
1 • If the mobile station is directed by the user to send a continuous DTMF digit, the
2 mobile station shall build the Continuous DTMF Tone Order with the dialed digit and
3 shall send the order in assured mode requiring confirmation of delivery. When the
4 mobile station is directed by the user to cease sending the continuous DTMF digit,
5 the mobile station shall send the Continuous DTMF Tone Order (ORDQ = ‘11111111’)
6 in assured mode requiring confirmation of delivery. The mobile station sending
7 multiple Continuous DTMF Tone Orders shall preserve relative ordering of these
8 messages (see TIA/EIA/IS-2000-[2]). The mobile station shall send the Continuous
9 DTMF Tone Order with the ORDQ set to ‘11111111’ indicating the completion of the
10 current continuous DTMF digit before sending the Continuous DTMF Tone Order for
11 another digit or the Send Burst DTMF Message.
19 • If the mobile station is directed by the user to disconnect the call, the mobile station
20 shall enter the Release Substate with a mobile station release indication (see
21 2.6.4.5).

25 acknowledgment failure, the mobile station shall disable its transmitter and shall
28 • The mobile station shall perform the following:

29 − The mobile station may send the Resource Request Message or Resource Request
30 Mini Message in accordance with requirements for the currently connected
31 service option whenever RETRY_DELAYs[RETRY_TYPE] is equal to 0, where,
32 RETRY_TYPE is equal to ‘010’.
33 − The mobile station shall not send the Resource Request Message or Resource
34 Request Mini Message whenever RETRY_DELAYs[RETRY_TYPE] is set to infinity,
35 where, RETRY_TYPE is equal to ‘010’.
36 − If RETRY_DELAYs[RETRY_TYPE] is not 0 or infinity, the mobile station shall not
37 send the Resource Request Message or Resource Request Mini Message until after
38 the system time stored in RETRY_DELAYs[RETRY_TYPE], where, RETRY_TYPE is
39 equal to ‘010’.
2-246
C.S0005-0-2 v1.0
1 − The mobile station may send the Supplemental Channel Request Message or
2 Supplemental Channel Request Mini Message whenever
3 RETRY_DELAYs[RETRY_TYPE] is set to ‘0’, where, RETRY_TYPE is equal to ‘011’.
4 − The mobile station shall not send the Supplemental Channel Request Message or
5 Supplemental Channel Request Mini Message whenever
6 RETRY_DELAYs[RETRY_TYPE] is set to infinity, where, RETRY_TYPE is equal to
7 ‘011’.
8 − If RETRY_DELAYs[RETRY_TYPE] is not 0 or infinity, the mobile station shall not
9 send the Supplemental Channel Request Message or Supplemental Channel
10 Request Mini Message until after the system time stored in
11 RETRY_DELAYs[RETRY_TYPE] , where, RETRY_TYPE is equal to ‘011’.
12 − At the system time stored in RETRY_DELAYs[RETRY_TYPE], the mobile station

13 shall reset RETRY_DELAYs[RETRY_TYPE] to ‘0’, where RETRY_TYPE is equal to
14 ‘001’, ‘010’ or ‘011’.
15 • If the mobile station has user data to send and PILOT_GATING_USE_RATE is equal
16 to ‘1’, then the mobile station may send a Resource Request Message, Resource
17 Request Mini Message, Supplemental Channel Request Message, or Supplemental
18 Channel Request Mini Message to request for continuous reverse pilot transmission
19 and user traffic transmission.
20 • The mobile station may send a Resource Release Request Message or a Resource
21 Release Request Mini Message to request for reverse pilot gating operation to be
22 performed.
23 • The mobile station may enter the Release Substate with a service inactive indication
24 (see 2.6.4.5) if the service corresponding to the packet data service option instance
25 is inactive at the mobile station.
30 1. Alert With Information Message: If the message contains a Signal information
31 record with the SIGNAL_TYPE field set to ‘01’ or ‘10’, or if the message does not
32 contain a Signal information record, the mobile station shall enter the Waiting
33 For Mobile Station Answer Substate. The mobile station should alert the user in
34 accordance with the Signal information record. If the Alert With Information
35 Message does not contain a Signal information record, the mobile station
36 should use standard alert as defined in 3.7.5.5.
39 message as specified in 2.6.6.2.9 and shall enter the Conversation Task (see
40 2.6.4.4 for handoff to a wide analog channel and 2.6.5.4A of TIA/EIA/IS-91-A
41 [28] for handoff to an 800 MHz narrow analog channel). If the mobile station is
42 directed to an unsupported operation mode or band class, the mobile station
2-247
C.S0005-0-2 v1.0
1 shall respond with a Mobile Station Reject Order with ORDQ equal to ‘00000110’
2 (message requires a capability that is not supported by the mobile station).
3 3. Audit Order
4 4. Authentication Challenge Message: The mobile station shall process the

5 message and shall respond as specified in 2.3.12.1.4 within T32m seconds,
6 regardless of the value of AUTHs.
8 message and shall respond with an SSD Update Confirmation Order or SSD
9 Update Rejection Order as specified in 2.3.12.1.5 within T32m seconds.
14 8. Continuous DTMF Tone Order: Support of this order by the mobile station is
15 optional.
18 message, or if the specified band class is supported by the mobile station, the
19 mobile station shall process the message as specified in 2.6.6.2.5.1.
28 15. Flash With Information Message
33 station shall process the message as specified in 2.6.6.2.5.1. If the message
36 (see 2.6.4.1.2.2).
2-248
C.S0005-0-2 v1.0
14 22. Maintenance Order: The mobile station shall enter the Waiting for Mobile Station
15 Answer Substate.
26 specified in 2.6.6.2.6.3.
29 28. Parameter Update Order: The mobile station shall increment COUNTs-p (see
30 2.3.12.1.3). The mobile station shall send a Parameter Update Confirmation
31 Order within T56m seconds. The mobile station shall set the ORDQ field of the
32 Parameter Update Confirmation Order to the same value as the ORDQ field of the
33 Parameter Update Order.
37 specified in 2.6.6.2.5.1.
39 specified in 2.6.4.1.1.3.
2-249
C.S0005-0-2 v1.0
17 ‘010’, or ‘011’.
19 following:




33 the following:
35 shall set RETRY_DELAYs [RETRY_TYPEr] to ‘0’.

2-250
C.S0005-0-2 v1.0

7 41. Send Burst DTMF Message: Support of this order by the mobile station is
8 optional.
11 2.6.4.1.2.2).
14 2.6.4.1.2.2).
17 2.6.4.1.2.2).
20 2.6.4.1.2.2).
23 2.6.4.1.2.2).
25 follows:
26 If RECORD_TYPEr is equal to ‘00000000’, the mobile station shall do the
27 following:
28 – The mobile station shall set RETURN_IF_FAILs = RETURN_IF_FAILr.
29 – If DELETE_TMSIr is equal to ‘1’, the mobile station shall set all the bits of
31 – The mobile station shall disable the full-TMSI timer.
32 – The mobile station shall enter the Release Substate with an NDSS off
33 indication (see2.6.4.5).
34 If RECORD_TYPEr is not equal to ‘00000000’, REDIRECT_TYPEr is ‘1’, and the
35 mobile station supports the band class and operating mode specified in the
36 message, the mobile station shall do the following:
37 – The mobile station shall store the redirection record received in the
38 message as REDIRECT_RECs.
2-251
C.S0005-0-2 v1.0
1 – The mobile station shall enable NDSS_ORGSs and shall record the dialed
2 digits.

7 – The mobile station shall enter the Release Substate with a redirection
8 indication (see2.6.4.5).
9 Otherwise, the mobile station shall discard the message and send a Mobile
10 Station Reject Order (ORDQ set to the applicable reason code as determined from
11 Table 2.7.3-1) within T56m seconds.
14 2.6.4.1.2.2).
17 2.6.4.1.2.2).
22 51. SSD Update Message: The mobile station shall process the message and
23 respond with a Base Station Challenge Order as specified in 2.3.12.1.5 within
24 T32m seconds.
35 mode (OP_MODEr) in the Status Response Message.
36 If the message specifies a band class or a band class and an operating mode
37 which is not supported by the mobile station, the mobile station shall send a
38 Mobile Station Reject Order with ORDQ set to ‘00000110’ (message requires a
39 capability that is not supported by the mobile station).
40 If the response to this message exceeds the allowable length, the mobile station
2-252
C.S0005-0-2 v1.0
1 shall send a Mobile Station Reject Order with ORDQ set to ‘00001000’ (response
2 message would exceed the allowable length).

7 mode).
9 shall send a Status Message within T56m seconds. The mobile station shall
11 operating mode.
15 code as follows:
18 • The mobile station shall store the assigning TMSI zone number by setting
19 the ASSIGNING_TMSI_ZONE_LENs-p least significant octets of
22 TMSI_CODEr.
24 TMSI_EXP_TIMEs-p to TMSI_EXP_TIMEr. The mobile station shall disable
25 the full-TMSI timer. The mobile station shall then respond with a TMSI
26 Assignment Completion Message within T56m seconds.
27 If the bits of TMSI_CODEs-p are not all equal to ‘1’, and if System Time (in 80
28 ms units) exceeds TMSI_EXP_TIMEs-p × 212, the mobile station shall set all
29 the bits of TMSI_CODEs-p to ‘1’ within T66m seconds.
30 If the full-TMSI timer expires or has expired, the mobile station shall set all
31 the bits of TMSI_CODEs-p to ‘1’. The mobile station shall update the
32 registration variables as described in 2.6.5.5.2.5.
37 2.6.4.1.2.2).
2-253
C.S0005-0-2 v1.0
5 2.6.4.5 Release Substate
6 In this substate, the mobile station confirms the call disconnect.

7 Upon entering the Release Substate, the mobile station shall perform the following:
8 • The mobile station shall set the substate timer for T55m seconds.
9 • If the mobile station enters the Release Substate with a power-down indication, the
10 mobile station shall send a Release Order (ORDQ = ‘00000001’), and shall perform
11 power-down registration procedures (see 2.6.5.5.4.4).
12 • If the mobile station enters the Release Substate with a mobile station release
13 indication, the mobile station shall send a Release Order (ORDQ = ‘00000000’), and
14 set RETURN_CAUSEs to ‘0000’.
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 mobile station shall disable its transmitter, set RETURN_CAUSEs to ‘0000’, and
22 with a release indication (see 2.6.1.1).
23 • If the mobile station entered the Release Substate with a base station extended
24 release indication, then the mobile station shall perform the following:
25 – The mobile station shall send an Extended Release Response Message to the
26 base station.
27 – The mobile station shall disable its transmitter, set RETURN_CAUSEs to ‘0000’,
28 and shall enter the System Determination Substate of the Mobile Station
29 Initialization State with a release indication (see 2.6.1.1).
30 • If the mobile station entered the Release Substate with a base station extended
31 release with mini message indication, then the mobile station shall perform the
32 following:
33 – The mobile station shall send an Extended Release Response Mini Message to the
34 base station.
35 – The mobile station shall disable its transmitter, set RETURN_CAUSEs to ‘0000’,
36 and shall enter the System Determination Substate of the Mobile Station
37 Initialization State with a release indication (see 2.6.1.1).
2-254
C.S0005-0-2 v1.0
1 • If the mobile station enters the Release Substate with a redirection indication, the
2 mobile station shall send a Release Order (ORDQ = ‘00000000’) and shall enter the
3 System Determination Substate of the Mobile Station Initialization State with a
5 • If the mobile station enters the Release Substate with an NDSS off indication, the
6 mobile station shall send a Release Order (ORDQ = ‘00000000’), and shall enter the
7 System Determination Substate of the Mobile Station Initialization State with an NDSS
8 off indication (see 2.6.1.1).
9 While in the Release Substate, the mobile station shall perform the following:
18 TIA/EIA/IS-2000-[2].
20 in 2.6.4.1.1.
22 • If the Fundamental Channel is present, the mobile station shall transmit null traffic,
23 except when transmitting signaling traffic, on the Reverse Fundamental Channel.
24 • The mobile station shall process Forward Traffic Channel signaling traffic and shall
25 discard other types of Forward Traffic Channel traffic.

27 2.6.5.5.4.2.

31 release indication (see 2.6.1.1).
32 • If the mobile station receives a message which is included in the following list, and if
35 action time (see 2.6.4.1.5):
36 1. Alert With Information Message: The mobile station shall enter the Waiting for
37 Mobile Station Answer Substate. If the Alert With Information Message does not
38 contain a Signal information record, the mobile station should use standard
39 alert as defined in 3.7.5.5.
2-255
C.S0005-0-2 v1.0
5 5. Extended Handoff Direction Message: The mobile station shall process the
11 8. General Handoff Direction Message: The mobile station shall process the
15 2.6.4.1.2.2).
39 specified in 2.6.6.2.6.3.
2-256
C.S0005-0-2 v1.0
10 21. Release Order: The mobile station shall disable its transmitter. If the mobile
11 station enters the Release Substate with a power-down indication, the mobile
12 station may power down; otherwise, the mobile station shall enter the System
13 Determination Substate of the Mobile Station Initialization State with a release
14 indication (see 2.6.1.1).
20 ‘010’, or ‘011’.
22 following:



37 2.6.4.1.2.2).
2-257
C.S0005-0-2 v1.0
1 2.6.4.1.2.2).
2 26. Service Redirection Message: The mobile station shall disable its transmitter. If
3 the mobile station enters the Release Substate with a power-down indication,
4 the mobile station may power down; otherwise, the mobile station shall process
5 the message as follows:
6 • If RECORD_TYPEr is ‘00000000’, the mobile station shall do the following:

11 – The mobile station shall enter the System Determination Substate of the
12 Mobile Station Initialization State with an NDSS off indication (see2.6.1.1).
13 • If RECORD_TYPE is not equal to ‘00000000’, REDIRECT_TYPEr is ‘1’, and
14 the mobile station supports the band class and operating mode specified in
15 the message, the mobile station shall do the following:
16 – The mobile station shall store the redirection record received in the
17 message as REDIRECT_RECs.

22 – The mobile station shall enter the System Determination Substate of the
23 Mobile Station Initialization State with a redirection indication (see
24 2.6.1.1).
25 • Otherwise, the mobile station shall discard the message and send a Mobile
26 Station Reject Order (ORDQ set to the applicable reason code as determined
27 from Table 2.7.3-1) within T56m seconds.
39 band class or a band class and an operating mode which are not supported by
2-258
C.S0005-0-2 v1.0

3 allowable length, the mobile station shall send a Mobile Station Reject Order
4 with ORDQ set to ‘00001000’ (response message would exceed the allowable
5 length). If the message specifies an information record which is not supported
6 by the mobile station for the specified band class and operating mode, the
7 mobile station shall send a Mobile Station Reject Order with ORDQ set to
8 ‘00001001’ (information record is not supported for the specified band class and
9 operating mode).
11 shall send, a Status Message within T56m seconds. The mobile station shall
13 operating mode.
17 code as follows:
24 TMSI_CODEr.
29 If the bits of TMSI_CODEs-p are not all equal to ‘1’, and if System Time (in 80 ms
30 units) exceeds TMSI_EXP_TIMEs-p × 212, the mobile station shall set all the bits
31 of TMSI_CODEs-p to ‘1’ within T66m seconds.
32 If the full-TMSI timer expires or has expired, the mobile station shall set all the
33 bits of TMSI_CODEs-p to ‘1’. The mobile station shall update the registration
34 variables as described in 6.6.5.5.2.5.
39 2.6.4.1.2.2)
2-259
C.S0005-0-2 v1.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.
5 2.6.5 Registration
6 2.6.5.1 Forms of Registration
7 Registration is the process by which the mobile station notifies the base station of its
8 location, status, identification, slot cycle, and other characteristics. The mobile station
9 informs the base station of its location and status so that the base station can efficiently
10 page the mobile station when establishing a mobile station terminated call. For operation
11 in the slotted mode, the mobile station supplies the SLOT_CYCLE_INDEX parameter so that
12 the base station can determine which slots the mobile station is monitoring. The mobile
13 station supplies the station class mark and the protocol revision number so that the base
14 station knows the capabilities of the mobile station.
15 The CDMA system supports ten different forms of registration:
16 1. Power-up registration. The mobile station registers when it powers on, switches
17 from using a different frequency block, switches from using a different band class,
18 switches from using an alternative operating mode, or switches from using the
19 analog system.
20 2. Power-down registration. The mobile station registers when it powers off if

21 previously registered in the current serving system.
22 3. Timer-based registration. The mobile station registers when a timer expires.
23 4. Distance-based registration. The mobile station registers when the distance

24 between the current base station and the base station in which it last registered
25 exceeds a threshold.
26 5. Zone-based registration. The mobile station registers when it enters a new zone.
27 6. Parameter-change registration. The mobile station registers when certain of its

28 stored parameters change or when it enters a new system.
29 7. Ordered registration. The mobile station registers when the base station requests it.
30 8. Implicit registration. When a mobile station successfully sends an Origination
31 Message or Page Response Message, the base station can infer the mobile station’s
32 location. This is considered an implicit registration.
33 9. Traffic Channel registration. Whenever the base station has registration information
34 for a mobile station that has been assigned to a Traffic Channel, the base station
35 can notify the mobile station that it is registered.
36 10. User Zone Registration. The mobile station registers when it selects an active User
37 Zone (see 2.6.9.1.2).
2-260
C.S0005-0-2 v1.0
1 The first five forms of registration, as a group, are called autonomous registration and are
2 enabled by roaming status (see 2.6.5.3). Parameter-change registration is independent of
3 roaming status. Ordered registration is initiated by the base station through an Order
4 Message. Implicit registration does not involve the exchange of any registration messages
5 between the base station and the mobile station. The base station can obtain registration
6 information by sending the Status Request Message to the mobile station on either the f-
7 csch or the f-dsch. The base station can obtain limited registration information by sending
8 the Status Request Order to the mobile station on the f-dsch. The mobile station can be
9 notified that it is registered through the Mobile Station Registered Message.
10 Any of the various forms of autonomous registration and parameter-change registration can
11 be enabled or disabled. The forms of registration that are enabled and the corresponding
12 registration parameters are communicated in the System Parameters Message.
13 In addition, the mobile station may enable or disable autonomous registration for each type
14 of roaming described in 2.6.5.3.
15 2.6.5.1.1 Power-Up Registration
16 Power-up registration is performed when the mobile station is turned on. To prevent
17 multiple registrations when power is quickly turned on and off, the mobile station delays
18 T57m seconds before registering, after entering the Mobile Station Idle State.
19 The mobile station shall maintain a power-up/initialization timer. While the power-
20 up/initialization timer is active, the mobile station shall not make registration access
21 attempts.
22 2.6.5.1.2 Power-Down Registration
23 Power-down registration is performed when the user directs the mobile station to power off.
24 If power-down registration is performed, the mobile station does not power off until after
25 completing the registration attempt.
26 The mobile station does not perform power-down registration if it has not previously
27 registered in the system that corresponds to the current SIDs and NIDs (see 2.6.5.5.2.4).
28 2.6.5.1.3 Timer-Based Registration
29 Timer-based registration causes the mobile station to register at regular intervals. Its use
30 also allows the system to automatically deregister mobile stations that did not perform a
31 successful power-down registration. Timer-based registration uses a Paging Channel slot
32 counter (equivalent to a timer with time increments of 80 ms). Timer-based registration is
33 performed when the counter reaches a maximum value (REG_COUNT_MAXs) that is
34 controlled by the base station via the REG_PRD field of the System Parameters Message.
35 The base station disables timer-based registration by setting REG_PRD to zero.
36 The mobile station shall maintain a timer-based registration counter (REG_COUNTs). The
37 mobile station shall compute and store the timer expiration count (REG_COUNT_MAXs) as
38 REG_COUNT_MAXs = 2REG_PRD/4.
2-261
C.S0005-0-2 v1.0
1 The mobile station shall maintain an indicator of timer-based registration timer enable
2 status (COUNTER_ENABLEDs).
3 The counter is reset when the mobile station powers on and when the mobile station
4 switches from different band classes, different serving systems, different frequency blocks,
5 and alternate operating modes. The counter is also reset after each successful registration.
6 Whenever the mobile station changes COUNTER_ENABLEDs from NO to YES, it shall set
7 REG_COUNTs to a pseudorandom value between 0 and REG_COUNT_MAXs - 1, using the
8 pseudorandom number generator specified in 2.6.7.2.
9 If the mobile station is operating in the non-slotted mode, it shall increment the timer-
10 based registration counter once per 80 ms whenever COUNTER_ENABLEDs equals YES. If
11 the mobile station is operating in slotted mode, it may increment the timer-based
12 registration counter when it begins to monitor the Paging Channel (see 2.6.2.1.1.3). A
13 mobile station operating in the slotted mode shall increment the counter by the same
14 amount that the counter would have been incremented if the mobile station had been
15 operating in the non-slotted mode.10
16 2.6.5.1.4 Distance-Based Registration

17 Distance-based registration causes a mobile station to register when the distance between
18 the current base station and the base station in which it last registered exceeds a
19 threshold. The mobile station determines that it has moved a certain distance by
20 computing a distance measure based on the difference in latitude and longitude between
21 the current base station and the base station where the mobile station last registered. If
22 this distance measure exceeds the threshold value, the mobile station registers.
23 The mobile station stores the base station latitude (BASE_LAT_REGs-p), the base station
24 longitude (BASE_LONG_REGs-p) and the registration distance (REG_DIST_REGs-p), of the
25 base station to which the first access probe (for a Registration Message, Origination
26 Message, or Page Response Message sent on the r-csch) was transmitted after entering the
27 System Access State. The mobile station shall compute the current base station’s distance
28 from the last registration point (DISTANCE) as:
( ∆lat ) 2 + ( ∆long ) 2
29 DISTANCE =  ,
16
30 where
31 ∆lat = BASE_LATs - BASE_LAT_REGs-p
32 and
33 ∆long = (BASE_LONGs - BASE_LONG_REGs-p) × cos (π/180 × BASE_LAT_REGs-p/14400).
10 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-262
C.S0005-0-2 v1.0
1 The mobile station shall compute DISTANCE with an error of no more than ±5% of its true
2 value when |BASE_LAT_REGs-p/14400| is less than 60 and with an error of no more than
3 ±7% of its true value when |BASE_LAT_REGs-p/14400| is between 60 and 70.11
4 2.6.5.1.5 Zone-Based Registration

5 Registration zones are groups of base stations within a given system and network. A base
6 station’s zone assignment is identified by the REG_ZONE field of the System Parameters
7 Message.
8 Zone-based registration causes a mobile station to register whenever it moves into a new
9 zone, not on its internally stored list of visited registration zones. A zone is added to the list
10 whenever a registration (including implicit registration) occurs, and is deleted upon
11 expiration of a timer. After a system access, timers are enabled for every zone except one
12 that was successfully registered by the access.
13 A mobile station can be registered in more than one zone. Zones are uniquely identified by
14 a zone number (REG_ZONE) plus the SID and NID of the zone.
15 The mobile station shall store a list of the zones in which the mobile station has registered
16 (ZONE_LISTs). Each entry in ZONE_LISTs shall include the zone number (REG_ZONE) and
17 the (SID, NID) pair for the zone. The mobile station shall be capable of storing at least N9m
18 entries in ZONE_LISTs. A base station shall be considered to be in ZONE_LISTs only if the
19 base station’s REG_ZONE, SID and NID are found in an entry in ZONE_LISTs. The mobile
20 station provides storage for one entry of ZONE_LISTs in semi-permanent memory,
21 ZONE_LISTs-p (see 2.3.4).
22 The mobile station shall maintain a zone list entry timer for each entry in ZONE_LISTs.
23 When an entry in ZONE_LISTs is removed from the list, the corresponding zone list entry
24 timer shall be disabled. The timer duration shall be as determined from the stored value of
25 ZONE_TIMERs using Table 3.7.2.3.2.1-1. The mobile station shall provide a means to
26 examine each timer’s value while the timer is active, so that the age of list entries can be
27 compared.
28 If the mobile station supports Band Class 1, Band Class 2, Band Class 4, Band Class 5, or
29 Band Class 7, the mobile station shall maintain an identifier of the frequency block for each
30 entry in ZONE_LISTs (see 2.1.1.1 of TIA/EIA/IS-2000-[2]). When the mobile station adds a
31 zone to ZONE_LISTs, the mobile station shall include the identifier for the frequency
32 block.12
33 If the mobile station supports multiple band classes, the mobile station shall maintain an
34 identifier of the band class for each entry in ZONE_LISTs (see 2.1.1.1 of TIA/EIA/IS-2000-
11 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.
12 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-263
C.S0005-0-2 v1.0
1 [2]). When the mobile station adds a zone to ZONE_LISTs, the mobile station shall include
2 the identifier for the band class.
3 The base station controls the maximum number of zones in which a mobile station may be
4 considered registered, by means of the TOTAL_ZONES field of the System Parameters
5 Message. When an entry is added to the zone list, or if TOTAL_ZONES is decreased, the
6 mobile station removes entries from the zone list if there are more entries than allowed by
7 the setting of TOTAL_ZONES.
8 Whenever ZONE_LISTs contains more than TOTAL_ZONESs entries, the mobile station shall
9 delete the excess entries according to the following rules:
10 • If TOTAL_ZONESs is equal to zero, the mobile station shall delete all entries.
11 • If TOTAL_ZONESs is not equal to zero, the mobile station shall delete those entries
12 having active zone list entry timers, starting with the oldest entry, as determined by
13 the timer values, and continuing in order of decreasing age until no more than
14 TOTAL_ZONESs entries remain.
15 The mobile station shall store a list of the systems/networks in which the mobile station
16 has registered (SID_NID_LISTs). Each entry in SID_NID_LISTs shall include the (SID, NID)
17 pair for the system/network. The mobile station shall be capable of storing N10m entries in
18 SID_NID_LISTs. A base station shall be considered to be in the SID_NID_LISTs only if the
19 base station’s SID and NID are found in an entry in SID_NID_LISTs. The mobile station
20 shall provide storage for one entry of SID_NID_LISTs in semi-permanent memory
21 (SID_NID_LISTs-p).
22 If the mobile station supports Band Class 1, Band Class 2, Band Class 4, Band Class 5, or
23 Band Class 7, the mobile station shall maintain an identifier of the frequency block for each
24 entry in SID_NID_LISTs (see 2.1.1.1 of TIA/EIA/IS-2000-[2]). When the mobile station adds
25 an entry to SID_NID_LISTs, the mobile station shall include the identifier for the frequency
26 block.
27 If the mobile station supports multiple band classes, the mobile station shall maintain an
28 identifier of the band class for each entry in SID_NID_LISTs (see 2.1.1.1 of TIA/EIA/IS-
29 2000-[2]). When the mobile station adds an entry to SID_NID_LISTs, the mobile station
30 shall include the identifier for the band class.
31 The mobile station shall maintain a SID/NID list entry timer for each entry in
32 SID_NID_LISTs. When an entry in SID_NID_LISTs is removed from the list, the
33 corresponding SID/NID list entry timer shall be disabled. The timer duration shall be as
34 determined from the stored value of ZONE_TIMERs using Table 3.7.2.3.2.1-1. The mobile
35 station shall provide a means to examine each timer’s value while the timer is active, so
36 that the age of list entries can be compared.
37 Whenever SID_NID_LISTs contains more than N10m entries, the mobile station shall delete
38 the excess entries according to the following rule:
39 • The mobile station shall delete those entries having active SID/NID list entry timers,
40 starting with the oldest entry, as determined by the timer values, and continuing in
41 order of decreasing age.
2-264
C.S0005-0-2 v1.0
1 Whenever MULT_SIDSs is equal to ‘0’ and SID_NID_LIST contains entries with different
2 SIDs, the mobile station shall delete the excess entries according to the following rules:
3 • If the SID/NID entry timer for any entry is disabled, the mobile station shall delete
4 all entries not having the same SID as the entry whose timer is disabled;
5 • Otherwise, the mobile station shall delete all entries not having the same SID as the
6 newest entry in SID_NID_LIST, as determined by the timer values.
7 Whenever MULT_NIDSs is equal to ‘0’, and SID_NID_LIST contains more than one entry for
8 any SID, the mobile station shall delete the excess entries for each SID according to the
9 following rules:
10 • If the SID/NID entry timer for any entry is disabled, the mobile station shall delete
11 all entries for that SID except the entry whose timer is disabled;
12 • For all other SIDs, the mobile station shall delete all entries for each SID except the
13 newest entry, as determined by the timer values.
14 2.6.5.1.6 Parameter-Change Registration
15 Parameter-change registration is performed when a mobile station modifies any of the

16 following stored parameters:
17 • The preferred slot cycle index (SLOT_CYCLE_INDEXp)
18 • The station class mark (SCMp)
19 • The call termination enabled indicators (MOB_TERM_HOMEp,

20 MOB_TERM_FOR_SIDp, and MOB_TERM_FOR_NIDp)
21 Parameter-change registration is also performed when any of the following capabilities

22 supported by the mobile station changes:
23 • The band classes
24 • The power classes
25 • The radio configurations
26 • The operating modes
27 • Quick Paging Channel
28 Parameter-change registration is performed whenever there is no entry in the mobile

29 station’s SID_NID_LISTs that matches the base station’s SID and NID.
30 Parameter-change registration is independent of the roaming status of the mobile station.13
31 Whenever a parameter changes, the mobile station shall delete all entries from
32 SID_NID_LISTs.
13 The indicator REG_ENABLED does not govern parameter-change registration.
2-265
C.S0005-0-2 v1.0
1 2.6.5.1.7 Ordered Registration
2 The base station can command the mobile station to register by sending a Registration
3 Request Order. Ordered registration is performed in the Mobile Station Order and Message
4 Processing Operation (2.6.2.4). Requirements are specified in 2.6.5.5.2.3.
5 2.6.5.1.8 Implicit Registration

6 Whenever an Origination Message or Page Response Message is sent, the base station can
7 infer the location of the mobile station. This is considered an implicit registration.
8 Requirements are specified in 2.6.5.5.3.
9 2.6.5.1.9 Traffic Channel Registration
10 While a mobile station is assigned a Traffic Channel, the mobile station is notified that it is
11 registered through the Mobile Station Registered Message. Requirements are specified in
12 2.6.5.5.4.3.
13 2.6.5.1.10 User Zone Registration
14 User Zone registration is performed when the mobile station selects an active User Zone
15 (see 2.6.9.2.1).
16 2.6.5.2 Systems and Networks
17 A base station is a member of a cellular or PCS system and a network. A network is a

18 subset of a system.
19 Systems are labeled with an identification called the system identification or SID; networks
20 within a system are given a network identification or NID. A network is uniquely identified
21 by the pair (SID, NID). The SID number 0 is a reserved value. The NID number 0 is a
22 reserved value indicating all base stations that are not included in a specific network. The
23 NID number 65535 (216-1) is a reserved value the mobile station may use for roaming
24 status determination (see 2.6.5.3) to indicate that the mobile station considers the entire
25 SID (regardless of NID) as home (non-roaming).
26 Figure 2.6.5.2-1 shows an example of systems and networks. SID i contains three
27 networks labeled t, u, and v. A base station in system i that is not in one of these three
28 networks is in NID 0.
29
2-266
C.S0005-0-2 v1.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) does not match one of the mobile station’s non-roaming (SID, NID) pairs. Two
7 types of roaming are defined: A mobile station is a foreign NID roamer if the mobile station
8 is roaming and there is some (SID, NID) pair in the mobile station’s (SID, NID) list for which
9 SID is equal to SIDs. A mobile station is a foreign SID roamer if there is no (SID, NID) pair
10 in the mobile station’s (SID, NID) list for which SID is equal to SIDs14. The mobile station
14 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)
pair is in the list. If the base station (SID, NID) pair is (2, 7), then the mobile station is a foreign NID
(footnote continued on next page)
2-267
C.S0005-0-2 v1.0
1 may use the special NID value 65535 to indicate that the mobile station considers all NIDs
2 within a SID to be non-roaming (i.e., that the mobile station is not roaming when operating
3 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 The mobile station shall store a mobile station call termination enabled indicator,
17 MOB_TERMs. The mobile station shall set MOB_TERMs to YES if any of the following
18 conditions is met:
19 • The mobile station is not roaming, and MOB_TERM_HOMEp is equal to ‘1’; or
20 • The mobile station is a foreign NID roamer and MOB_TERM_FOR_NIDp is equal to

21 ‘1’; or
22 • The mobile station is a foreign SID roamer and MOB_TERM_FOR_SIDp is equal to
23 ‘1’; otherwise the mobile station shall set MOB_TERMs to NO.
24 The mobile station shall store a registration status indicator, REG_ENABLEDs. The mobile
25 station shall set the indicator REG_ENABLEDs to YES if any of the following conditions is
26 met for the mobile station:
27 • The mobile station is not roaming, and both HOME_REGs and MOB_TERM_HOMEp
28 are equal to ‘1’; or
29 • The mobile station is a foreign NID roamer and both FOR_NID_REGs and
30 MOB_TERM_FOR_NIDp are equal to ‘1’; or
31 • The mobile station is a foreign SID roamer and both FOR_SID_REGs and
32 MOB_TERM_FOR_SIDp are equal to ‘1’; otherwise the mobile station shall set
33 REG_ENABLEDs to NO.
34 The mobile station performs autonomous registrations if REG_ENABLEDs is YES.
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-268
C.S0005-0-2 v1.0
1 2.6.5.4 Registration Timers and Indicators
2 The mobile station shall provide the following registration timers:
3 • Power-up/initialization timer (see 2.6.5.1.1).
4 • Timer-based registration timer (see 2.6.5.1.3).
5 • Zone list entry timers (see 2.6.5.1.5).
6 • SID/NID list entry timers (see 2.6.5.1.5).
7 The mobile station shall provide a means of enabling and disabling each timer. When a
8 timer is disabled, it shall not be considered expired. A timer that has been enabled is
9 referred to as active.
10 2.6.5.5 Registration Procedures
11 2.6.5.5.1 Actions in the Mobile Station Initialization State
12 2.6.5.5.1.1 Power-Up or Change to a Different Operating Mode, Band Class, Serving

13 System, or Frequency Block
14 Upon power-up, the mobile station shall perform the following actions:
15 • Delete all entries of ZONE_LISTs.
16 • If ZONE_LISTs-p contains an entry, copy the entry to ZONE_LISTs and disable the
17 corresponding entry timer.
18 • Delete all entries of SID_NID_LISTs.
19 • If SID_NID_LISTs-p contains an entry, copy the entry to SID_NID_LISTs and disable

20 the corresponding entry timer.
21 • Set the registered flag (REGISTEREDs) to NO.
22 • Set timer-based registration enable status (COUNTER_ENABLEDs) to NO.
23 • Set autonomous registration enable status (REG_ENABLEDs) to NO.
24 • Set RETURN_CAUSEs to ‘0000’.
25 Upon switching from CDMA in a different band class, from CDMA in a different serving
26 system in a band class that supports multiple serving systems (e.g., Band Class 0), from
27 CDMA in a different frequency block in a band class that supports frequency block
28 allocations (e.g. Band Class 1), or from the 800 MHz analog system, the mobile station shall
30 • Set timer-based registration enable status (COUNTER_ENABLEDs) to NO.
31 • Set autonomous registration enable status (REG_ENABLEDs) to NO.
32 • Set RETURN_CAUSEs to ‘0000’.
2-269
C.S0005-0-2 v1.0
1 2.6.5.5.1.2 Timer Maintenance
2 While in the Mobile Station Initialization State, the mobile station shall update all active
3 registration timers (see 2.6.5.4). If any timer expires while in this state, the mobile station
4 shall preserve the expiration status so that further action can be taken in the Mobile Station
5 Idle State.
6 2.6.5.5.1.3 Entering the Mobile Station Idle State

7 Before entering the Mobile Station Idle State from the Mobile Station Initialization State, the
8 mobile station shall perform the following action:
9 • If REGISTEREDs is equal to NO, enable the power-up/initialization timer with an
10 expiration time of T57m seconds (see 2.6.5.1.1) only when the mobile station is
11 entering this state with a power-up indication.
12 2.6.5.5.2 Actions in the Mobile Station Idle State
13 Requirements in this section and its subsections apply only when the mobile station is in
14 the Mobile Station Idle State.
15 2.6.5.5.2.1 Idle Registration Procedures

16 These procedures are performed whenever the mobile station is in the Mobile Station Idle
17 State (see 2.6.2.1.3).
18 While in the Mobile Station Idle State, the mobile station shall update all active registration
19 timers (see 2.6.5.4).
20 If the power-up/initialization timer has expired or is disabled, the mobile station shall
21 perform the following actions in the order given. If any action necessitates a registration,
22 the mobile station shall enter the Update Overhead Information Substate of the System
23 Access State (see 2.6.3) with a registration indication.
24 1. The timer-based registration timer shall be enabled (COUNTER_ENABLEDs = YES)
25 and the timer count (REG_COUNTs) shall be set to a pseudorandom number as
26 specified in 2.6.5.1.3, if the following conditions are met:
27 a. COUNTER_ENABLEDs is equal to NO; and
28 b. The stored configuration parameters are current (see 2.6.2.2); and

29 c. REG_ENABLEDs is equal to YES; and
30 d. REG_PRDs is not equal to zero.
31 2. If any zone list entry timer (see 2.6.5.1.5) has expired, the mobile station shall delete
32 the corresponding entry from ZONE_LISTs.
33 3. If any SID/NID list entry timer (see 2.6.5.1.5) has expired, the mobile station shall
34 delete the corresponding entry from SID_NID_LISTs.
35 4. The mobile station shall perform power-up registration, as specified in 2.6.5.1.1, if

36 all the following conditions are met:
2-270
C.S0005-0-2 v1.0
1 a. POWER_UP_REGs is equal to ‘1’; and

3 c. REGISTEREDs is equal to NO, and
4 d. REG_ENABLEDs is equal to YES.
5 5. The mobile station shall perform parameter-change registration (see 2.6.5.1.6) if all
6 the following conditions are met:
7 a. PARAMETER_REGs is equal to ‘1’; and

9 c. There is no entry of SID_NID_LISTs whose SID and NID fields match the stored
10 SIDs and NIDs.
11 6. The mobile station shall perform timer-based registration (see 2.6.5.1.3) if all the
12 following conditions are met:
13 a. COUNTER_ENABLEDs is equal to YES; and

16 d. REG_COUNTs is greater than or equal to REG_COUNT_MAXs.
17 7. The mobile station shall perform distance-based registration (see 2.6.5.1.4) if all the
19 a. REG_DISTs is not equal to zero; and

22 d. The current base station’s distance from the base station in which the mobile
23 station last registered (see 2.6.5.1.4) is greater than or equal to
24 REG_DIST_REGs-p.
25 8. The mobile station shall perform zone-based registration (see 2.6.5.1.5) if all the
27 a. TOTAL_ZONESs is not equal to zero; and

30 d. There is no entry of ZONE_LISTs whose SID, NID and REG_ZONE fields match
31 the stored SIDs, NIDs and REG_ZONEs.
32 9. The mobile station shall perform User Zone registration (see 2.6.2.5.1.10) if it selects
33 an active User Zone (see 2.6.9.1.2).
2-271
C.S0005-0-2 v1.0
1 2.6.5.5.2.2 Processing the Registration Fields of the System Parameters Message
2 When the mobile station processes the System Parameters Message, it shall perform the
4 1. If REG_PRDs is equal to zero, the mobile station shall set COUNTER_ENABLEDs to
5 NO.
6 2. If REG_PRDs is not equal to zero, the mobile station shall set REG_COUNT_MAXs as
8 3. The mobile station shall update its roaming status and set REG_ENABLEDs as
9 specified in 2.6.5.3.
10 4. If ZONE_LISTs contains more than TOTAL_ZONESs entries, the mobile station shall
11 delete the excess entries according to the rules specified in 2.6.5.1.5.
12 5. If MULT_SIDSs is equal to ‘0’ and SID_NID_LIST contains entries with different
13 SIDs, delete the excess entries according to the rules specified in 2.6.5.1.5.
14 6. If MULT_NIDSs is equal to ‘0’ and SID_NID_LIST contains more than one entry for
15 any SID, delete the excess entries according to the rules specified in 2.6.5.1.5.
16 2.6.5.5.2.3 Ordered Registration

17 Ordered registration is performed after receiving a Registration Request Order while in the
18 Mobile Station Order and Message Processing Operation (see 2.6.2.4).
19 The mobile station shall enter the Update Overhead Information Substate of the System
20 Access State with a registration indication within T33m seconds after the Registration
21 Request Order is received.
22 2.6.5.5.2.4 Power Off
23 These procedures are performed when the mobile station is directed by the user to power
24 off.
25 The mobile station shall perform the following actions:

26 • If an entry of ZONE_LISTs does not have an active timer, copy that entry to
27 ZONE_LISTs-p; otherwise, delete any entry in ZONE_LISTs-p.
28 • If an entry of SID_NID_LISTs does not have an active timer, copy that entry to
29 SID_NID_LISTs-p; otherwise, delete any entry in SID_NID_LISTs-p.
30 The mobile station shall perform power-down registration (see 2.6.5.1.2) by entering the
31 System Access State with a registration indication within T33m seconds after the user
32 directs the mobile station to power off, if all the following conditions are true:
33 • REG_ENABLEDs equals YES; and
34 • POWER_DOWN_REGs equals ‘1’; and
35 • There is an entry of SID_NID_LISTs for which the SID and NID fields are equal to
36 SIDs and NIDs; and
2-272
C.S0005-0-2 v1.0
1 • The power-up/initialization timer (see 2.6.5.1.1) is disabled or has expired.
2 2.6.5.5.2.5 Full-TMSI Timer Expiration

3 When the mobile station sets all the bits of TMSI_CODEs-p to ‘1’ upon expiration of the full-
4 TMSI timer (see 2.6.2), the mobile station shall delete all entries from SID_NID_LISTs and
5 ZONE_LISTs.
6 2.6.5.5.3 Actions in the System Access State
8 the System Access State.
9 2.6.5.5.3.1 Successful Access, Registration, or Implicit Registration
10 These procedures shall be performed after the mobile station receives confirmation of
11 delivery of a Registration Message, Origination Message, or Page Response Message sent on
12 the r-csch (see 2.6.3.1.2).
13 • Disable the power-up/initialization timer (see 2.6.5.1.1).
14 • If the mobile station supports the 800 MHz analog mode, set the First-Idle ID status
15 to enabled (see 2.6.3.11).
16 • Set DIGITAL_REGs-p to ‘00000001’.
17 • Set REG_COUNTs to zero.
18 • Set REGISTEREDs to YES.
19 • Delete all entries from ZONE_LISTs belonging to a different band class (see 2.1.1.1 of
20 TIA/EIA/IS-2000-[2]) than CDMABANDs.
21 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete all entries from

22 ZONE_LISTs that have a SID from a different serving system than SERVSYSs.
23 • If CDMABANDs = ‘00001’, CDMABANDs = ‘00010’, CDMABANDs = ‘00100’,

24 CDMABANDs = ‘00101’, or CDMABANDs = ‘00111’, delete all entries from
25 ZONE_LISTs belonging to a different frequency block (see 2.1.1.1 of TIA/EIA/IS-
26 2000-[2]) than the frequency block associated with SIDs.
27 • Add REG_ZONEs, SIDs, and NIDs to ZONE_LISTs if not already in the list. If
28 required, include the band class identifier and block identifier for the current band
29 and frequency block as specified in 2.6.5.1.5.
30 • Disable the zone list entry timer for the entry of ZONE_LISTs containing
31 REG_ZONEs, SIDs, and NIDs. For any other entry of ZONE_LISTs whose entry timer
32 is not active, enable the entry timer with the duration specified by ZONE_TIMERs
33 (see 2.6.5.1.5).
34 • If ZONE_LISTs contains more than TOTAL_ZONESs entries, delete the excess entries
35 according to the rules specified in 2.6.5.1.5.
36 • Delete all entries from SID_NID_LISTs belonging to a different band class (see
37 2.1.1.1 of TIA/EIA/IS-2000-[2]) than CDMABANDs
2-273
C.S0005-0-2 v1.0
1 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete all entries from

2 SID_NID_LISTs that have a SID from a different serving system than SERVSYSs.

5 SID_NID_LISTs belonging to a different frequency block (see 2.1.1.1 of TIA/EIA/IS-
7 • Add SIDs and NIDs to SID_NID_LISTs if not already in the list. If required, include
8 the band class identifier and block identifier for the current band and frequency
9 block as specified in 2.6.5.1.5.
10 • Disable the SID/NID list entry timer for the entry of SID_NID_LISTs containing SIDs,
11 and NIDs. For any other entry of SID_NID_LISTs whose entry timer is not active,
12 enable the entry timer with the duration specified in 2.6.5.1.5.
13 • If SID_NID_LISTs contains more than N10m entries, delete the excess entries
15 • If MULT_SIDSs is equal to ‘0’ and SID_NID_LIST contains entries with different
17 • If MULT_NIDSs is equal to ‘0’ and SID_NID_LIST contains more than one entry for
19 • Set the stored location of last registration (BASE_LAT_REGs-p and BASE_LONG-
20 _REGs-p) to the current base station’s location (BASE_LATs and BASE_LONGs). Set
21 the stored registration distance (REG_DIST_REGs-p) to the current base station’s
22 registration distance (REG_DISTs).
23 These procedures shall be performed after the mobile station receives confirmation of
24 delivery of any other message:
30 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete from ZONE_LISTs all

31 entries from ZONE_LISTs that have a SID from a different serving system than
32 SERVSYSs.

37 • For any entry of ZONE_LISTs not matching REG_ZONEs, SIDs, and NIDs and not
38 having an active entry timer, enable the entry timer with the duration specified by
39 ZONE_TIMERs (see 2.6.5.1.5).
2-274
C.S0005-0-2 v1.0
2 2.1.1.1 of TIA/EIA/IS-2000-[2]) than CDMABANDs.
3 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete from SID_NID_LISTs all

4 entries from SID_NID_LISTs that have a SID from a different serving system than
5 SERVSYSs.

10 • For any entry of SID_NID_LISTs not matching SIDs and NIDs and not having an
11 active entry timer, enable the entry timer with the duration specified by
13 2.6.5.5.3.2 Unsuccessful Access
14 These procedures are performed when the mobile station declares an access attempt failure
15 when in the System Access State (see 2.6.3).
22 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete from ZONE_LISTs all

23 entries from ZONE_LISTs that have a SID from a different serving system than
24 SERVSYSs.

29 • For any entry of ZONE_LISTs not matching REG_ZONEs, SIDs, and NIDs and not
30 having an active entry timer, enable the entry timer with the duration specified by
33 2.1.1.1 of TIA/EIA/IS-2000-[2]) than CDMABANDs.
34 • If CDMABANDs = ‘00000’ or CDMABANDs = ‘00011’, delete from SID_NID_LISTs all

35 entries from SID_NID_LISTs that have a SID from a different serving system than
36 SERVSYSs.
2-275
C.S0005-0-2 v1.0

5 • For any entry of SID_NID_LISTs not matching SIDs and NIDs and not having an
6 active entry timer, enable the entry timer with the duration specified by
8 2.6.5.5.3.3 Power Off
10 off.

13 ZONE_LISTs-p; otherwise, delete any entry in ZONE_LISTs-p.
15 SID_NID_LISTs-p; otherwise, delete any entry in SID_NID_LISTs-p.
16 2.6.5.5.4 Actions in the Mobile Station Control on the Traffic Channel State
19 2.6.5.5.4.1 Traffic Channel Initialization

20 Upon entering the Traffic Channel Initialization Substate of the Mobile Station Control on the
21 Traffic Channel State, the mobile station shall set COUNTER_ENABLEDs to NO.
22 2.6.5.5.4.2 Timer Maintenance

23 While in the Mobile Station Control on the Traffic Channel State, the mobile station shall
24 update all active registration timers.
25 If a zone list entry timer expires, the mobile station shall delete the corresponding entry
26 from ZONE_LISTs. If a SID/NID list entry timer expires, the mobile station shall delete the
27 corresponding entry from SID_NID_LISTs.
28 2.6.5.5.4.3 Processing the Mobile Station Registered Message

29 The mobile station receives the Mobile Station Registered Message on the Forward Traffic
30 Channel when the mobile station is considered registered for the base station whose
31 location and other parameters are included in the message.

35 • Registration zone (REG_ZONEs = REG_ZONEr)
2-276
C.S0005-0-2 v1.0
1 • Number of registration zones to be retained (TOTAL_ZONESs = TOTAL_ZONESr)
2 • Zone timer length (ZONE_TIMERs = ZONE_TIMERr)
3 • Multiple SID storage indicator (MULT_SIDSs = MULT_SIDSr)
4 • Multiple NID storage indicator (MULT_NIDSs = MULT_NIDSr)
5 • Base station latitude (BASE_LATs = BASE_LATr)
6 • Base station longitude (BASE_LONGs = BASE_LONGr)
7 • Registration distance (REG_DISTs = REG_DISTr)
10 to enabled (see TIA/EIA/IS-2000-[6]).
12 • Add REG_ZONEs, SIDs, and NIDs to ZONE_LISTs if not already in the list. If
13 required, include the band class identifier and block identifier for the current band
14 and frequency block as specified in 2.6.5.1.5.
17 • Disable the zone list entry timer for the entry of ZONE_LISTs containing
18 REG_ZONEs, SIDs, and NIDs. For any other entry of ZONE_LISTs whose entry timer
19 is not active, enable the entry timer with the duration specified by ZONE_TIMERs
20 (see 2.6.5.1.5).
21 • If ZONE_LISTs contains more than TOTAL_ZONESs entries, delete the excess entries
25 • Add SIDs and NIDs to SID_NID_LISTs if not already in the list. If required, include
26 the band class identifier and block identifier for the current band and PCS frequency
27 block as specified in 2.6.5.1.5.
28 • Disable the SID/NID list entry timer for the entry of SID_NID_LISTs containing SIDs,
29 and NIDs. For any other entry of SID_NID_LISTs whose entry timer is not active,
30 enable the entry timer with the duration specified in 2.6.5.1.5.
31 • If SID_NID_LISTs contains more than N10m entries, delete the excess entries
33 • If MULT_SIDSs is equal to ‘0’ and SID_NID_LIST contains entries with different
35 • If MULT_NIDSs is equal to ‘0’ and SID_NID_LIST contains more than one entry for
2-277
C.S0005-0-2 v1.0
1 • Set the stored location of last registration (BASE_LAT_REGs-p and BASE_LONG-

2 _REGs-p) to the base station’s location (BASE_LATs and BASE_LONGs). Set the
3 stored registration distance (REG_DIST_REGs-p) to the base station’s registration
4 distance (REG_DISTs).
5 • Update its roaming status and set MOB_TERMs as specified in 2.6.5.3. The mobile
6 station should indicate to the user whether the mobile station is roaming.
7 2.6.5.5.4.4 Power Off
9 off.

12 ZONE_LISTs-p; otherwise, delete the entry in ZONE_LISTs-p if ZONE_LISTs-p
13 contains an entry.
15 SID_NID_LISTs-p; otherwise, delete the entry in SID_NID_LISTs-p if SID_NID_LISTs-p
16 contains an entry.
17 2.6.6 Handoff Procedures
18 This section presents an overview and mobile station requirements for handoffs occurring
19 while the mobile station is in the Mobile Station Control on the Traffic Channel State (see
20 2.6.4). Mobile station requirements for handoffs occurring while the mobile station is in the
21 Mobile Station Idle State are specified in 2.6.2.1.4.
22 2.6.6.1 Overview
23 2.6.6.1.1 Types of Handoff

24 The mobile station supports the following three handoff procedures while in the Mobile
25 Station Control on the Traffic Channel State:
26 • Soft Handoff: A handoff in which the mobile station commences communications

27 with a new base station without interrupting communications with the old base
28 station. Soft handoff can only be used between CDMA Channels having identical
29 Frequency Assignments. Soft handoff provides diversity of Forward Traffic Channels
30 and Reverse Traffic Channel paths on the boundaries between base stations.
31 • CDMA-to-CDMA Hard Handoff: A handoff in which the mobile station is transitioned
32 between disjoint sets of base stations, different band classes, different Frequency
33 Assignments, or different frame offsets.
34 • CDMA-to-Analog Handoff: A handoff in which the mobile station is directed from a
35 CDMA traffic channel to an analog voice channel.
36 The mobile station shall support soft handoffs on the same Frequency Assignment (see
37 2.6.6.2.7). The mobile station shall support CDMA-to-CDMA hard handoffs between band
38 classes on which it supports CDMA operation (see 2.6.6.2.8). The mobile station shall
2-278
C.S0005-0-2 v1.0
1 support CDMA-to-Analog handoffs from band classes on which it supports CDMA operation
2 to band classes on which it supports analog operation (see 2.6.6.2.9).
3 2.6.6.1.2 Pilot Sets
4 Within section 2.6.6 the term pilot refers to a Pilot Channel identified by a pilot sequence
5 offset (see 3.1.3.2.1) and a Frequency Assignment (see 3.1.1.1). A pilot is associated with
6 the Forward Traffic Channels in the same Forward CDMA Channel. All pilots in a pilot set
7 have the same CDMA Frequency Assignment.
8 The mobile station searches for pilots on the current CDMA Frequency Assignment to detect
9 the presence of CDMA Channels and to measure their strengths. When the mobile station
10 detects a pilot of sufficient strength that is not associated with any of the Forward Traffic
11 Channels assigned to it, it sends a Pilot Strength Measurement Message to the base station.
12 The base station can then assign a Forward Traffic Channel associated with that pilot to the
13 mobile station and direct the mobile station to perform a handoff.
14 The pilot search parameters and the rules for Pilot Strength Measurement Message
15 transmission are expressed in terms of the following sets of pilots:
16 • Active Set: The pilots associated with the Forward Traffic Channels assigned to the
17 mobile station.
18 • Candidate Set: The pilots that are not currently in the Active Set but have been
19 received by the mobile station with sufficient strength to indicate that the associated
20 Forward Traffic Channels could be successfully demodulated.
21 • Neighbor Set: The pilots that are not currently in the Active Set or the Candidate Set
22 and are likely candidates for handoff.
23 • Remaining Set: The set of all possible pilots in the current system on the current
24 CDMA Frequency Assignment, excluding the pilots in the Neighbor Set, the
25 Candidate Set, and the Active Set. This set of possible pilots consists of pilots
26 whose pilot PN sequence offset indices are integer multiples of PILOT_INCs.
27 The base station may direct the mobile station to search for pilots on a different CDMA
28 frequency to detect the presence of CDMA Channels and to measure their strengths. The
29 mobile station reports the results of the search to the base station using the Candidate
30 Frequency Search Report Message. Depending upon the pilot strength measurements
31 reported in the Candidate Frequency Search Report Message, the base station can direct the
32 mobile station to perform an inter-frequency hard handoff.
33 The pilot search parameters are expressed in terms of the following sets of pilots on the
34 CDMA Candidate Frequency:
35 • Candidate Frequency Neighbor Set: A list of pilots on the CDMA Candidate
36 Frequency.
37 • Candidate Frequency Search Set: A subset of the Candidate Frequency Neighbor Set
38 that the base station may direct the mobile station to search.
2-279
C.S0005-0-2 v1.0
1 2.6.6.2 Requirements
2 2.6.6.2.1 Pilot Search
3 For the pilot sets defined in 2.6.6.1.2, the base station sets the search window (range of PN
4 offsets) in which the mobile station is to search for usable multipath components (i.e.,
5 multipath components that the mobile station can use for demodulation of the associated
6 Forward Traffic Channel) of the pilots in the set.
7 Search performance criteria are defined in TIA/EIA-98-C[14] and ANSI J-STD-018[10].
8 This search shall be governed by the following:

9 • Active Set and Candidate Set: The search procedures for pilots in the Active Set and
10 Candidate Set shall be identical. The search window size15 for each pilot in the
11 Active Set and Candidate Set shall be the number of PN chips specified in Table
12 2.6.6.2.1-1 corresponding to SRCH_WIN_As. The mobile station should center the
13 search window for each pilot of the Active Set and Candidate Set around the earliest
14 arriving usable multipath component of the pilot. If the mobile station receives a
15 value greater than or equal to 13 for SRCH_WIN_Ar, it may store and use the value
16 13 in SRCH_WIN_As.
17 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
18
15 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-280
C.S0005-0-2 v1.0
1 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
2
3 • Neighbor Set: If SRCH_WIN_NGHBR_INCLs is equal to ‘1’, the search window size for
4 each pilot in the Neighbor Set shall be the number of PN chips specified in Table
5 2.6.6.2.1-1, corresponding to SRCH_WIN_NGHBRs associated with the pilot being
6 searched. If SRCH_WIN_NGHBR_INCLs is equal to ‘0’, the search window size for
7 each pilot in the Neighbor Set shall be the number of PN chips specified in Table
8 2.6.6.2.1-1 corresponding to SRCH_WIN_Ns. If SRCH_OFFSET_INCLs is equal to ‘1’,
9 the search window offset for each pilot in the Neighbor Set shall be the number of
10 PN chips specified in Table 2.6.6.2.1-2, corresponding to SRCH_OFFSET_NGHBRs
11 associated with the pilot being searched. If SRCH_OFFSET_INCLs is equal to ‘0’, the
12 search window offset for each pilot in the Neighbor Set shall be zero PN chip. The
13 mobile station should center the search window for each pilot in the Neighbor Set
14 around the pilot’s PN sequence offset plus the corresponding search window offset,
15 using timing defined by the mobile station’s time reference (see TIA/EIA/IS-2000-
16 [2]). If SEARCH_PRIORITY_INCLs is equal to ‘1’, the mobile station should use
17 SEARCH_PRIORITYs for the corresponding pilot to schedule its neighbor search. If
18 the mobile station supports hopping pilot beacons and the TIMING_INCL field of the
19 NGHBR_REC for the corresponding pilot is equal to ‘1’, then the mobile station shall
20 use the information included in the NGHBR_TX_OFFSET, NGHBR_TX_DURATION,
21 and NGHBR_TX_PERIOD fields of the NGHBR_REC for the corresponding pilot to
22 schedule the time for searching the neighbor. If ADD_PILOT_REC_INCL field of the
23 NGHBR_REC for the corresponding pilot is equal to ‘1’, the mobile station shall use
24 the information included in the NGHBR_PILOT_REC field for searching the neighbor.
25 • Remaining Set: The search window size for each pilot in the Remaining Set shall be
26 the number of PN chips specified in Table 2.6.6.2.1-1 corresponding to
27 SRCH_WIN_Rs. The mobile station should center the search window for each pilot
28 in the Remaining Set around the pilot’s PN sequence offset, using timing defined by
29 the mobile station’s time reference (see TIA/EIA/IS-2000-[2]). The mobile station
30 should only search for Remaining Set pilots whose pilot PN sequence offset indices
31 are equal to integer multiples of PILOT_INCs.
2-281
C.S0005-0-2 v1.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 set shall be
3 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 chip. 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 TIA/EIA/IS-
16 2000-[2]). If CF_SEARCH_PRIORITY_INCLs is equal to ‘1’, the mobile station should
17 use SEARCH_PRIORITYs associated with each pilot to schedule a search of its
18 Candidate 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 The mobile station should use the searcher element (see TIA/EIA/IS-2000-[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 TIA/EIA/IS-2000-[2]) supported by
27 the mobile station.
28 2.6.6.2.3 Handoff Drop Timer
29 The mobile station shall maintain a handoff drop timer for each pilot in the Active Set and
30 Candidate Set.
31 If P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to ‘000000’, the
33 • For the Candidate Set, the mobile station shall start the timer whenever the
34 strength of the corresponding pilot becomes less than T_DROPs. The mobile station
35 shall reset and disable the timer if the strength of the corresponding pilot exceeds
36 T_DROPs.
37 • For the Active Set, the mobile station shall start the timer whenever the strength of
38 the corresponding pilot becomes less than T_DROPs. The mobile station shall start
39 the timer even if the timer has previously expired. The mobile station shall reset
40 and disable the timer if the strength of the corresponding pilot exceeds T_DROPs.
2-282
C.S0005-0-2 v1.0
1 If P_REV_IN_USEs is greater than three and SOFT_SLOPEs is not equal to ‘000000’, the
3 • For the Candidate Set, the mobile station shall start the timer whenever the
4 strength of the corresponding pilot becomes less than T_DROPs. The mobile station
5 shall reset and disable the timer if the strength of the corresponding pilot exceeds
6 T_DROPs.
7 • For the Active Set, the mobile station shall sort the NA pilots in the Active Set in
8 order of increasing strengths, i.e., PS1 < PS2 < PS3 < …< PSNA where the strength
9 PS is as defined in 2.6.6.2.2. The mobile station shall start the timer whenever the
10 strength PSi satisfies the following inequality:
SOFT_SLOPEs DROP_INTERCEPTs T_DROPs
10 × log 10PS i < max(
8
×10 × log10 ∑ PS j + 2
,
2
)
11 j> i
i = 1, 2, ..., PSN -1
A
12
13 For the Active Set, the mobile station shall start the timer even if the timer has previously
14 expired. The mobile station shall reset and disable the timer whenever the above inequality
15 is not satisfied for the corresponding pilot.
16 If T_TDROPs equals zero, the mobile station shall consider the timer expired within 100 ms
17 of enabling it. Otherwise, the mobile station shall consider the timer expired within 10% of
18 the timer expiration value shown in Table 2.6.6.2.3-1 corresponding to T_TDROPs. If
19 T_TDROPs changes, the mobile station shall begin using the new value for all handoff drop
20 timers within 100 ms.
21
22 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
23
24 The mobile station shall indicate the status of the handoff drop timer for all pilots in the
25 Active Set and Candidate Set when transmitting a Pilot Strength Measurement Message.
2-283
C.S0005-0-2 v1.0
1 2.6.6.2.4 Pilot PN Phase
2 The mobile station shall measure the arrival time, PILOT_ARRIVAL, for each pilot reported
3 to the base station. The pilot arrival time shall be the time of occurrence, as measured at
4 the mobile station antenna connector, of the earliest arriving usable multipath component
5 of the pilot. The arrival time shall be measured relative to the mobile station’s time
6 reference (see TIA/EIA/IS-2000-[2]) in units of PN chips. The mobile station shall compute
7 the reported pilot PN phase, PILOT_PN_PHASE, as
8 PILOT_PN_PHASE = (PILOT_ARRIVAL + (64 × PILOT_PN)) mod 215,
9 where PILOT_PN is the PN sequence offset index of the pilot (see TIA/EIA/IS-2000-2)[2]).
10 2.6.6.2.5 Handoff Messages
11 2.6.6.2.5.1 Processing of Forward Traffic Channel Handoff Messages
12 If the mobile station receives any of the following messages, then the mobile station shall
13 process the message as described.
14 1. Pilot Measurement Request Order: The mobile station shall send, within T56m
15 seconds, a Pilot Strength Measurement Message.
16 2. Analog Handoff Direction Message: The mobile station shall process the message as
19 specified in 2.6.6.2.6.3 and set SEARCH_PRIORITY_INCLs,
20 SRCH_WIN_NGHBR_INCLs, and SRCH_OFFSET_INCLs to ‘0’, and set TIMING_INCL
21 for each of the neighboring base stations in the Neighbor List Update Message to ‘0’.
22 4. Extended Handoff Direction Message: The mobile station shall process the message as
23 follows:
24 The mobile station shall send a Mobile Station Reject Order with the ORDQ field set
25 to ‘00000110’ (capability not supported), if the mobile station does not support the
26 band class specified in the Extended Handoff Direction Message.
27 If the mobile station does not send a Mobile Station Reject Order in response to the
28 Extended Handoff Direction Message, the mobile station shall perform the following at
29 the action time of the message:
30 • The mobile station shall send a Handoff Completion Message as specified in
31 2.6.6.2.5.2.
32 • Update the Active Set, Candidate Set, and Neighbor Set in accordance with the
33 Extended Handoff Direction Message processing (see 2.6.6.2.6.1, 2.6.6.2.6.2, and
34 2.6.6.2.6.3).
2-284
C.S0005-0-2 v1.0
1 • The mobile station shall delete all pilots that are not listed in the Active Set of the
2 Fundamental Channel from the Active Set of the Supplemental Channel for the
3 Forward Supplemental Channel Assignment (if any). If these deleted pilots include
4 all pilots in the Active Set of the Supplemental Channel, the mobile station shall
5 cancel the Forward Supplemental Channel Assignment.
6 • Discontinue use of all Forward Traffic Channels associated with pilots not listed in
7 the Extended Handoff Direction Message.
8 • The mobile station shall update the Code Channel List, CODE_CHAN_LISTs, as
9 specified in 2.6.8.
10 • If the mobile station is currently processing Forward Supplemental Code Channels,

11 then it shall continue processing the Forward Supplemental Code Channels using
12 the updated Code Channel List, CODE_CHAN_LISTs.
13 • The mobile station shall set IGNORE_SCAMs and IGNORE_ESCAMs to ‘0’.
14 • If HARD_INCLUDED is equal to ‘1’, perform the following actions:

15 – If FRAME_OFFSETr is not equal to FRAME_OFFSETs, change the frame
16 offset on all of the code channels of the Forward Traffic Channel and of the
18 – If RESET_L2r is equal to ‘1’, Layer 3 shall send a L2-Supervision.Request
19 primitive to Layer 2 to reset the acknowledgment procedures as specified in
20 2.2.1.1 and 2.2.2.1 of TIA/EIA/IS-2000-4.[4]. The acknowledgment
21 procedures shall be reset immediately after the action time of the Extended
23 – If RESET_FPCr is equal to ‘1’, initialize the Forward Traffic Channel power
24 control counters as specified in 2.6.4.1.1.1.
25 – If SERV_NEG_TYPEr is equal to ‘1’, set SERV_NEGs to enabled; otherwise set
26 SERV_NEGs to disabled. – Use the long code mask specified by the
27 PRIVATE_LCMr (see 2.3.12.3) and indicate to the user the voice privacy mode
28 status.
29 – Process the ENCRYPT_MODE field as specified in 2.3.12.2.
30 • Store the following parameters from the current configuration:

31 – Serving Frequency Assignment (SF_CDMACHs = CDMACHs)
32 – Serving Frequency band class (SF_BAND_CLASSs = BAND_CLASSs)
33 – Serving Frequency frame offset (SF_FRAME_OFFSETs= FRAME_OFFSETs)
34 • If HARD_INCLUDED is not equal to ‘1’, set NUM_PREAMBLEs = ‘000’.
35 • Store the following parameters from the Extended Handoff Direction Message:
36 – Extended Handoff Direction Message sequence number (HDM_SEQs =
37 HDM_SEQr)
38 – If SEARCH_INCLUDED is equal to ‘1’, then store the following:
2-285
C.S0005-0-2 v1.0
1 + Search window size for the Active Set and Candidate Set
2 (SRCH_WIN_As = SRCH_WIN_Ar )
3 + Pilot detection threshold (T_ADDs = T_ADDr)
4 + Pilot drop threshold (T_DROPs = T_DROPr)
5 + Active Set versus Candidate Set comparison threshold

6 (T_COMPs = T_COMPr)
7 + Drop timer value (T_TDROPs = T_TDROPr)
8 – If HARD_INCLUDED is equal to ‘1’, then store the following:

9 + Frame offset (FRAME_OFFSETs = FRAME_OFFSETr)
10 + Nominal power setting of the target cell (NOM_PWRs = NOM_PWRr)
11 + Hard handoff traffic channel preamble count required before transmitting

12 Handoff Completion Message (NUM_PREAMBLEs = NUM_PREAMBLEr )
13 + CDMA band class (CDMABANDs = BAND_CLASSr)
14 + Frequency assignment (CDMACHs = CDMA_FREQr)
15 + Nominal power setting of the target cell (If CDMABANDs = ‘00000’ or

16 CDMABANDs = ‘00011’, then NOM_PWR_EXTs = ‘0’; otherwise,
17 NOM_PWR_EXTs = NOM_PWR_EXTr)
18 – One occurrence of PILOT_PN and PWR_COMB_IND for each included

19 member of the Active Set.
20 – If ADD_LENGTH is not equal to ‘000’, then store the following:

21 + Protocol revision level (P_REVs = P_REVr)
22 + Protocol revision level currently in use (P_REV_IN_USEs = the minimum

23 value of P_REVs and MOB_P_REVp of the current band class)
24 – Disable return on failure (RETURN_IF_HANDOFF_FAILs = ‘0’)
25 • Perform a soft or hard handoff depending on the following conditions:
26 – If any of the following conditions is true, the mobile station shall perform a
27 hard handoff:
28 + HARD_INCLUDED is set to ‘1’ and either BAND_CLASSr is not equal to
29 SF_CDMABANDs, CDMA_FREQr is not equal to SF_CDMACHs, or
30 FRAME_OFFSETr is not equal to SF_FRAME_OFFSETs, or
31 + The set of pilots specified by the message is disjoint from the Active Set
32 prior to the action time of the message.
33 – If the mobile station performs a hard handoff, it shall do the following:
34 + If a Periodic Serving Frequency Pilot Report Procedure is in progress, abort

35 the procedure (see 2.6.6.2.12).
2-286
C.S0005-0-2 v1.0
1 + If a Candidate Frequency periodic search is in progress, abort the periodic

2 search (see 2.6.6.2.8.3.4 and 2.6.6.2.10.4) and set PERIODIC_SEARCHs to
3 ‘0’.
4 + The mobile station shall cancel the Forward Supplemental Channel

5 assignment or the Reverse Supplemental Channel assignment (if any).
6 + Perform the actions specified in 2.6.6.2.8.1. If the message specifies more

7 than one pilot, the mobile station shall also perform the actions specified in
8 2.6.6.2.7.1 and 2.6.6.2.7.2.
9 – Otherwise, the mobile station shall perform a soft handoff as specified in

10 2.6.6.2.7.
11 5. Candidate Frequency Search Request Message: The mobile station shall process the
14 to ‘00000110’ (capability not supported), if the following conditions is true:
15 • SEARCH_MODEr is not equal to ‘0000’, and the mobile station does not support
16 the capability specified by SEARCH_MODEr
17 If none of the above conditions is true, the mobile station shall perform the actions
18 described in the remainder of this section to process the Candidate Frequency
19 Search Request Message.
20 If SEARCH_MODEr is equal to ‘0000’, the mobile station shall process the Candidate
21 Frequency Search Request Message as follows:
22 • The mobile station shall send a Mobile Station Reject Order with the ORDQ field
23 set to ‘00001100’ (invalid Frequency Assignment), if the Frequency Assignment
24 specified in the message is the same as the Serving Frequency (BAND_CLASSr is
25 equal to CDMABANDs and CDMA_FREQr is equal to CDMACHs).
27 set to ‘00001010’ (search set not specified), if SEARCH_TYPEr is equal to ‘01’ or
28 ‘11’, and one of the following conditions is true:
29 − PILOT_UPDATEr is equal to ‘0’ and the Candidate Frequency Search Set
30 before the action time of the Candidate Frequency Search Request Message is
31 empty, or
32 − PILOT_UPDATEr is equal to ‘1’ and the message specifies an empty search
33 set.
35 set to ‘0001101’ (search period too short), if SEARCH_TYPEr is equal to ‘11’ and
36 search_period is less than (max (fwd_time, rev_time ) + T71m) seconds, where
37 search_period, fwd_time and rev_time are defined below.
2-287
C.S0005-0-2 v1.0
1 (In the following, if PILOT_UPDATEr is equal to ‘1’, rec_search_set is the set of

2 pilots specified in the Candidate Frequency Search Request Message with the
3 corresponding SEARCH_SET field set to ‘1’; otherwise, rec_search_set is the
4 Candidate Frequency Search Set before the action time of the Candidate
5 Frequency Search Request Message.)
6 search_period = time period corresponding to SEARCH_PERIODr shown in
7 Table 2.6.6.2.8.3.2-1
8 fwd_time = the mobile station’s estimate of the total length of time, in
9 seconds, for which the mobile station will need to suspend its
10 current Forward Traffic Channel processing in order to tune to
11 the Candidate Frequency, to search rec_search_set, and to re-
12 tune to the Serving Frequency; if the mobile station searches
13 rec_search_set in multiple visits, fwd_time is the total time for
14 all visits to the Candidate Frequency in a search period (see
15 2.6.6.2.8.3.2)
16 rev_time = the mobile station’s estimate of the total length of time, in
18 current Reverse Traffic Channel processing in order to tune to
19 the Candidate Frequency, to search rec_search_set, and to re-
20 tune to the Serving Frequency; if the mobile station searches
21 rec_search_set in multiple visits, rev_time is the total time for
22 all visits to the Candidate Frequency in a search period
23 • If the mobile station does not send a Mobile Station Reject Order in response to
24 the Candidate Frequency Search Request Message, it shall perform the following:
25 − The mobile station shall send a Candidate Frequency Search Response

26 Message in assured mode, within T56m seconds of receiving the Candidate
27 Frequency Search Request Message. The mobile station shall set the fields of
28 the Candidate Frequency Search Response Message as follows:
29 + The mobile station shall set TOTAL_OFF_TIME_FWD and

30 TOTAL_OFF_TIME_REV to its estimate of the total number of frames or
31 power control groups for which it will need to suspend its current
32 Forward Traffic Channel processing and Reverse Traffic Channel
33 processing, respectively, in order to tune to the Candidate Frequency, to
34 search rec_search_set, and to re-tune to the Serving Frequency (see
35 2.6.6.2.8.3.2). If the mobile station searches rec_search_set in multiple
36 visits to the Candidate Frequency, the mobile station shall report the
37 total number of frames or power control groups in all visits in a search
38 period for which it will need to suspend its current Forward Traffic
39 Channel and the Reverse Traffic Channel processing.
2-288
C.S0005-0-2 v1.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 to tune to the Candidate
6 Frequency, to search a subset of rec_search_set, and to re-tune to the
7 Serving Frequency.16
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 FWD and MAX_OFF_TIME_FWD are expressed in units of power control
11 groups. If these time estimates are expressed in units of frames, the
12 mobile station shall set PCG_OFF_TIMES to ‘0’. The mobile station shall
13 not use power control groups as the unit of delay if P_REV_IN_USEs is
14 less than six.
15 + Ιf 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, if MAX_NUM_VISITS is not equal
21 to 0, the mobile station shall set INTER_VISIT_TIME, in units of frames
22 or power control groups, to its estimate of the time between subsequent
23 visits within the same search period.
24 − When the message takes effect, the mobile station shall perform the following
25 actions:
26 + If any periodic search is in progress, the mobile station shall abort it (see
27 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
28 + Store the following parameters from the Candidate Frequency Search

29 Request Message:
30 ο Candidate Frequency Search Request Message sequence number

31 (CFSRM_SEQs = CFSRM_SEQr)
32 ο Periodic search flag: If SEARCH_TYPEr is equal to ‘11’, the mobile

33 station shall set PERIODIC_SEARCHs to ‘1’; otherwise, the mobile
34 station shall set PERIODIC_SEARCHs to ‘0’.
35 ο Search period on the Candidate Frequency

36 (SEARCH_PERIODs = SEARCH_PERIODr)
16 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-289
C.S0005-0-2 v1.0
1 ο Candidate Frequency search mode

2 (SEARCH_MODEs = SEARCH_MODEr)
3 ο Band class for the Candidate Frequency

4 (CF_CDMABANDs = BAND_CLASSr)
5 ο CDMA Channel number for the CDMA Candidate Frequency

6 (CF_CDMACHs = CDMA_FREQr)
7 ο Serving Frequency total pilot Ec threshold

8 (SF_TOTAL_EC_THRESHs = SF_TOTAL_EC_THRESHr)
9 ο Serving Frequency total pilot Ec/Io threshold

10 (SF_TOTAL_EC_IO_THRESHs = SF_TOTAL_EC_IO_THRESHr)
11 ο Received power difference threshold

12 (DIFF_RX_PWR_THRESHs = DIFF_RX_PWR_THRESHr)
13 ο Candidate Frequency Total pilot Ec/Io threshold

14 (MIN_TOTAL_PILOT_EC_IOs = MIN_TOTAL_PILOT_EC_IOr)
15 ο Pilot detection threshold on the CDMA Candidate Frequency

16 (CF_T_ADDs = CF_T_ADDr)
17 ο Maximum time on the CDMA Target Frequency that the mobile

18 station may wait to receive a period of (N11m × 20) ms with sufficient
19 signal quality (e.g. good frames) on the physical channel
20 corresponding to FPC_PRI_CHANs
21 (TF_WAIT_TIMEs = TF_WAIT_TIMEr)
22 ο Pilot PN sequence offset increment on the CDMA Candidate

23 Frequency (CF_PILOT_INCs = CF_PILOT_INCr)
24 ο Search window for pilots in the Neighbor Set on the CDMA Candidate
25 Frequency (CF_SRCH_WIN_Ns = CF_SRCH_WIN_Nr)
26 ο Search window for pilots in the Remaining Set on the CDMA

27 Candidate Frequency (CF_SRCH_WIN_Rs = CF_SRCH_WIN_Rr)
28 ο If PILOT_UPDATE is equal to ‘1’, the mobile station shall perform the

29 following:
30 ◊ Set CF_SEARCH_PRIORITY_INCLs and
31 CF_SRCH_WIN_NGHBR_INCLs to the values corresponding to
32 CF_NGHBR_SRCH_MODE shown in Table 2.6.6.2.5.1-1,
33 ◊ Set CF_SRCH_OFFSET_INCLs to CF_SRCH_OFFSET_INCLr.
34 ο If PILOT_UPDATE is equal to ‘1’, the mobile station shall replace the

35 Candidate Frequency Neighbor Set with all neighbor pilots specified
36 in the Candidate Frequency Search Request Message.
2-290
C.S0005-0-2 v1.0
1 ο If PILOT_UPDATE is equal to ‘1’ and CF_SEARCH_PRIORITY_INCLs is

2 equal to ‘1’, the mobile station shall store the search priority
3 (SEARCH_PRIORITYs = SEARCH_PRIORITYr) associated with each of
4 the neighboring base stations contained in the Candidate Frequency
5 Neighbor Set.
6 ο If PILOT_UPDATE is equal to ‘1’ and CF_SRCH_WIN_NGHBR_INCLs is
7 equal to ‘1’, the mobile station shall perform the following:
8 ◊ Store the neighbor pilot channel search window size

9 (SRCH_WIN_NGHBRs = SRCH_WIN_NGHBRr) associated with
10 each of the neighboring base stations contained in the Candidate
11 Frequency Neighbor Set,
12 ◊ If CF_SRCH_OFFSET_INCLr equals to ‘1’, store the neighbor pilot
13 channel search window offset (SRCH_OFFSET_NGHBRs =
14 SRCH_OFFSET_NGHBRr) associated with each of the neighboring
15 base stations contained in the Candidate Frequency Neighbor Set.
16 ο If PILOT_UPDATE is equal to ‘1’, the mobile station shall replace the

17 Candidate Frequency Search Set with all flagged pilots (those with the
18 corresponding SEARCH_SET field set to ‘1’) specified in the Candidate
19 Frequency Search Request Message.
20 + If ALIGN_TIMINGr is equal to ‘1’ and the mobile station will align its
21 search as requested by the base station, the mobile station shall set
22 ALIGN_TIMING_USEDs to ‘1’ and SEARCH_OFFSETs to
23 SEARCH_OFFSETr; otherwise, the mobile station shall set
24 ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs to ‘000000’.
25 + If the mobile station sets the PCG_OFF_TIMES field of the Candidate

26 Frequency Search Response Message to ‘1’, it shall set
27 SEARCH_TIME_RESOLUTIONs to 0.00125; otherwise, it shall set
28 SEARCH_TIME_RESOLUTIONs to 0.02.
29 + If SEARCH_TYPEr is equal to ‘01’, the mobile station shall perform a
30 single search of the Candidate Frequency Search Set, as described in
31 2.6.6.2.8.3.1. If SEARCH_TYPEr is equal to ‘11’, the mobile station shall
32 perform the periodic search procedures, as described in 2.6.6.2.8.3.2.
33
2-291
C.S0005-0-2 v1.0
1 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
3 If SEARCH_MODEr is equal to ‘0001’, and if the mobile station supports analog

4 searching, the mobile station shall process the Candidate Frequency Search Request
5 Message as follows:
8 search_period is less than (max (fwd_time, rev_time ) + T71m) seconds where
9 search_period, fwd_time and rev_time are defined below.
10 (In the following, rec_search_set is the set of analog frequencies specified in the
11 Candidate Frequency Search Request Message.)
13 Table 2.6.6.2.8.3.2-1
17 each analog frequency in rec_search_set and measure its
18 strength, and to re-tune to the Serving Frequency; if the mobile
19 station searches rec_search_set in multiple visits, fwd_time is
20 the total time for all visits away from the Serving Frequency in a
21 search period (see 2.6.6.2.10.2)
25 each analog frequency in rec_search_set and measure its
26 strength, and to re-tune to the Serving Frequency; if the mobile
27 station searches rec_search_set in multiple visits, rev_time is the
28 total time for all visits away from the Serving Frequency in a
29 search period
30 • If the mobile station does not send a Mobile Station Reject Order in response to
31 the Candidate Frequency Search Request Message, it shall perform the following:
2-292
C.S0005-0-2 v1.0
1 − The mobile station shall send a Candidate Frequency Search Response

2 Message in assured mode, within T56m seconds of receiving the Candidate
3 Frequency Search Request Message. The mobile station shall set the fields of
4 the Candidate Frequency Search Response Message as follows:
5 + The mobile station shall set TOTAL_OFF_TIME_FWD and

6 TOTAL_OFF_TIME_REV to its estimate of the total number of frames or
7 power control groups for which it will need to suspend its current
9 processing, respectively, in order to tune to each analog frequency in
10 rec_search_set, and to re-tune to the Serving Frequency (see
11 2.6.6.2.8.3.2). If the mobile station searches rec_search_set in multiple
12 visits away from the Serving Frequency, the mobile station shall report
13 the total number of frames or power control groups in all visits in a
14 search period for which it will need to suspend its current Forward
15 Traffic Channel and the Reverse Traffic Channel processing.
16 + The mobile station shall set MAX_OFF_TIME_FWD and

17 MAX_OFF_TIME_REV to its estimate of the maximum number of frames
18 or power control groups for which it will need to suspend its current
20 processing, respectively, during any single visit away from the Serving
21 Frequency, to search a subset of rec_search_set, and to re-tune to the
23 + The mobile station shall set PCG_OFF_TIMES to ‘1’ if

24 TOTAL_OFF_TIME_FWD, MAX_OFF_TIME_FWD, TOTAL_OFF_TIME_-
25 FWD and MAX_OFF_TIME_FWD are expressed in units of power control
26 groups. If these time estimates are expressed in units of frames, the
27 mobile station shall set PCG_OFF_TIMES to ‘0’. The mobile station shall
28 not use power control groups as the unit of delay if P_REV_IN_USEs is
29 less than six.
30 + Ιf ALIGN_TIMINGr is equal to ‘1’, the mobile station shall set
31 ALIGN_TIMING_USED to ‘1’ to indicate if it will align its search as
32 requested by the base station; otherwise, the mobile station shall set
33 ALIGN_TIMING_USED to ‘0’. If ALIGN_TIMING_USED is set to ‘1’, the
34 mobile station shall set MAX_NUM_VISITS to the maximum number of
35 visits per search period minus one and, if MAX_NUM_VISITS is not equal
36 to 0, the mobile station shall set INTER_VISIT_TIME, in units of frames
37 or power control groups, to its estimate of the time between subsequent
38 visits within the same search period.
39 − When the message takes effect, the mobile station shall perform the following
40 actions:
41 + If any periodic search is in progress, the mobile station shall abort it (see
42 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
2-293
C.S0005-0-2 v1.0
1 + Store the following parameters from the Candidate Frequency Search

2 Request Message:
3 ο Candidate Frequency Search Request Message sequence number

4 (CFSRM_SEQs = CFSRM_SEQr)
5 ο Periodic search flag: If SEARCH_TYPEr is equal to ‘11’, the mobile

6 station shall set PERIODIC_SEARCHs to ‘1’; otherwise, the mobile
7 station shall set PERIODIC_SEARCHs to ‘0’.
8 ο Search period for the analog frequencies search

9 (SEARCH_PERIODs = SEARCH_PERIODr)
10 ο Candidate Frequency search mode

11 (SEARCH_MODEs = SEARCH_MODEr)
12 ο Band class for the analog frequencies

13 (CF_CDMABANDs = BAND_CLASSr)
14 ο Serving Frequency total pilot Ec threshold

15 (SF_TOTAL_EC_THRESHs = SF_TOTAL_EC_THRESHr)
16 ο Serving Frequency total pilot Ec/Io threshold

17 (SF_TOTAL_EC_IO_THRESHs = SF_TOTAL_EC_IO_THRESHr)
18 ο Candidate Frequency Analog Search Set: The mobile station shall

19 replace the Candidate Frequency Analog Search Set with the analog
20 frequencies included in the Candidate Frequency Search Request
21 Message.
22 + If ALIGN_TIMINGr is equal to ‘1’ and the mobile station will align its
23 search as requested by the base station, the mobile station shall set
24 ALIGN_TIMING_USEDs to ‘1’ and SEARCH_OFFSETs to
25 SEARCH_OFFSETr; otherwise, the mobile station shall set
27 + If the mobile station sets the PCG_OFF_TIMES field of the Candidate

28 Frequency Search Response Message to ‘1’, it shall set
29 SEARCH_TIME_RESOLUTIONs to 0.00125; otherwise, it shall set
30 SEARCH_TIME_RESOLUTIONs to 0.02.
31 + If SEARCH_TYPEr is equal to ‘01’, the mobile station shall perform a

32 single search of the Candidate Frequency Analog Search Set as described
33 in 2.6.6.2.10.1. If SEARCH_TYPEr is equal to ‘11’, the mobile station
34 shall perform the periodic search procedures described in 2.6.6.2.10.2.
35 6. Candidate Frequency Search Control Message: The mobile station shall process the
37 If SEARCH_MODEs is equal to ‘0000’:
39 set to ‘00001010’ (search set not specified), if SEARCH_TYPEr is not equal to ‘00’
40 and the Candidate Frequency Search Set is empty.
2-294
C.S0005-0-2 v1.0
2 set to ‘00001011’ (invalid search request), if SEARCH_TYPEr is not equal to ‘00’
3 and the Candidate Frequency is the same as the Serving Frequency
4 (CF_CDMABANDs is equal to CDMABANDs and CF_CDMACHs is equal to
5 CDMACHs).

10 Table 2.6.6.2.8.3.2-1,
14 the Candidate Frequency, to search the Candidate Frequency
15 Search Set and to re-tune to the Serving Frequency; if the
16 mobile station searches the Candidate Frequency Search Set in
17 multiple visits, fwd_time is the total time for all visits to the
18 Candidate Frequency in a search period (see 2.6.6.2.8.3.2),
19 and
23 the Candidate Frequency, to search the Candidate Frequency
24 Search Set and to re-tune to the Serving Frequency; if the
25 mobile station searches the Candidate Frequency Search Set in
26 multiple visits, rev_time is the total time for all visits to the
27 Candidate Frequency in a search period.
28 • If the mobile station does not reject the Candidate Frequency Search Control
29 Message, it shall perform the following actions when the message takes effect:
30 − If any periodic search is in progress, the mobile station shall abort it (see
31 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
32 − If ALIGN_TIMINGr is equal to ‘1’ and the mobile station will align its search
33 as requested by the base station, the mobile station shall set
34 ALIGN_TIMING_USEDs to ‘1’; otherwise, the mobile station shall set
35 ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs to ‘000000’.− Ιf
36 SEARCH_TYPEr is equal to ‘00’, the mobile station shall set
37 PERIODIC_SEARCHs to ‘0’.
38 − If SEARCH_TYPEr is equal to ‘01’:
39 + The mobile station shall set PERIODIC_SEARCHs to ‘0’.
40 + The mobile station shall perform a single search of the Candidate

41 Frequency Search Set, as described in 2.6.6.2.8.3.1.
2-295
C.S0005-0-2 v1.0
3 + The mobile station shall perform the periodic search procedures for the
4 Candidate Frequency Search Set, as described in 2.6.6.2.8.3.2.
5 If SEARCH_MODEs is equal to ‘0001’:
7 set to ‘00001010’ (search set not specified), if SEARCH_TYPEr is not equal to ‘00’
8 and the Candidate Frequency Analog Search Set is empty.

13 Table 2.6.6.2.8.3.2-1,
17 each analog frequency in the Candidate Frequency Analog
18 Search Set and measure its strength, and to re-tune to the
19 Serving Frequency; if the mobile station searches the Candidate
20 Frequency Analog Search Set in multiple visits, fwd_time is the
22 search period (see 2.6.6.2.10.2),
23 and
27 each analog frequency in the Candidate Frequency Analog
28 Search Set and measure its strength, and to re-tune to the
29 Serving Frequency; if the mobile station searches the Candidate
30 Frequency Analog Search Set in multiple visits, fwd_time is the
32 search period (see 2.6.6.2.10.2).
33 • If the mobile station does not reject the Candidate Frequency Search Control
34 Message, it shall perform the following actions when the message takes effect:
35 − If any periodic search is in progress, the mobile station shall abort it (see
36 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
37 − If ALIGN_TIMINGr is equal to ‘1’ and the mobile station will align its search
38 as requested by the base station, the mobile station shall set
39 ALIGN_TIMING_USEDs to ‘1’; otherwise, the mobile station shall set
2-296
C.S0005-0-2 v1.0
1 − Ιf SEARCH_TYPEr is equal to ‘00’, the mobile station shall set

6 + The mobile station shall perform a single search of the Candidate

7 Frequency Analog Search Set, as described in 2.6.6.2.10.1.
10 + The mobile station shall perform the periodic search procedures for the
11 Candidate Frequency Analog Search Set, as described in 2.6.6.2.10.2.
12 7. Extended Neighbor List Update Message: The mobile station shall update its
13 neighbor set as specified in 2.6.6.2.6.3 and perform the following:
14 • If NGHBR_SRCH_MODEr is equal to ‘01’ or ‘11’, the mobile station shall store
15 the search priority (SEARCH_PRIORITYs = SEARCH_PRIORITYr) associated with
16 each of the neighboring base stations contained in the Extended Neighbor List
17 Update Message which are in the mobile’s neighbor set.
18 • If NGHBR_SRCH_MODEr is equal to ‘01’ or ‘00’, the mobile station shall set the
19 SRCH_OFFSET_INCLs field ‘0’.
20 • If NGHBR_SRCH_MODEr is equal to ‘10’ or ‘11’, the mobile station shall perform

21 the following:
22 − Store the neighbor pilot channel search window size

23 (SRCH_WIN_NGHBRs = SRCH_WIN_NGHBRr) associated with each of the
24 neighboring base stations contained in the Extended Neighbor List Updated
25 Message which are in the mobile’s neighbor set,
26 − If SRCH_OFFSET_INCLr equals to ‘1’, set the SRCH_OFFSET_NGHBR field of
27 NGHBR_REC[i] to the ith occurrence of SRCH_OFFSET_NGHBRr,
28 − Set SRCH_OFFSET_INCLs to SRCH_OFFSET_INCLr.
29 • The mobile station shall update the default search window size for its Neighbor
30 Set (SRCH_WIN_Ns = SRCH_WIN_Nr).
31 • The mobile station shall set SEARCH_PRIORITY_INCLs and

32 SRCH_WIN_NGHBR_INCLs to the value specified in Table 2.6.6.2.5.1-1
33 corresponding to NGHBR_SRCH_MODEr.
34 • If USE_TIMING is equal to ‘1’, the mobile station shall store the timing included
35 flag (TIMING_INCL) associated with each of the neighboring base stations
36 contained in the Extended Neighbor List Update Message which are in the mobile
37 station neighbor set; otherwise the mobile station shall set the timing included
38 flag (TIMING_INCL) associated with each of the neighboring base stations to ‘0’.
2-297
C.S0005-0-2 v1.0
1 • If USE_TIMING is equal to ‘1’ and TIMING_INCLr is equal to ‘1’, the mobile

2 station shall store the neighbor transmit time offset (NGHBR_TX_OFFSET =
3 NGHBR_TX_OFFSETr) associated with each of the neighboring base stations
4 contained in the Extended Neighbor List Update Message which are in the mobile
5 station neighbor set.
6 • If USE_TIMING is equal to ‘1’ and the TIMING_INCL is equal to ‘1’, then the
8 − If the GLOBAL_TIMING_INCL field is equal to ‘1’, then the mobile station

9 shall store the neighbor transmit time duration (NGHBR_TX_DURATION =
10 GLOBAL_TX_DURATIONr) and the neighbor transmit time duration
11 (NGHBR_TX_PERIOD = GLOBAL_TX_PERIODr) contained in the Extended
12 Neighbor List Update Message.
13 − If the GLOBAL_TIMING_INCL field is equal to ‘0’, then the mobile station

14 shall store the neighbor transmit time duration (NGHBR_TX_DURATION =
15 NGHBR_TX_DURATIONr) and the neighbor transmit time duration
16 (NGHBR_TX_PERIOD = NGHBR_TX_PERIODr) associated with each of the
17 neighboring base stations contained in the Extended Neighbor List Update
18 Message which are in the mobile station neighbor set.
19 • For each of the neighboring base stations contained in the General Neighbor List
20 Message, the mobile station shall set ADD_PILOT_REC_INCL field of
21 NGHBR_REC[i] to the ith occurrence of ADD_PILOT_REC_INCLr. If
22 ADD_PILOT_REC_INCr equals ‘1’, for each pilot, the mobile station shall also
24 − Set the NGHBR_PILOT_REC_TYPE field of NGHBR_PILOT_REC to

25 NGHBR_PILOT_REC_TYPEr.
26 − If NGHBR_PILOT_REC_TYPEr is equal to ‘000’. The mobile station shall set

27 the OTD_POWER_LEVEL field of NGHBR_PILOT_REC to
29 8. Supplemental Channel Assignment Message: The mobile station shall process this
32 to the specified value if any of the following conditions is true, and shall not perform
33 any other action described in this section for processing the Supplemental Channel
34 Assignment Message:
36 set to ‘00000110’ (capability not supported), if the number of forward or reverse
37 Supplemental Code Channels specified in the Supplemental Channel Assignment
38 Message is greater than the maximum number of Supplemental Code Channels
39 supported by the mobile station.
2-298
C.S0005-0-2 v1.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-299
C.S0005-0-2 v1.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-300
C.S0005-0-2 v1.0
1 + If USE_REV_HDM_SEQr is equal to ‘1’, REV_LINKED_HDM_SEQr is equal

2 to HDM_SEQs, then the mobile station shall set the REV_START_TIMEs
3 to the action time of the General Handoff Direction Message that is linked
4 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 may start

16 transmitting on NUM_REV_CODESs Reverse Supplemental Code
17 Channels at the start time specified by REV_START_TIMEs for a duration
18 of time specified by the following rules:
19 ο If USE_REV_DURATIONr is equal to ‘1’, the mobile station shall set
20 REV_DURATIONs to REV_DURATIONr. The mobile station may
21 continue transmitting on the Reverse Supplemental Code Channels
22 for a period of (REV_DURATIONs × 80) ms, or until it receives the
23 action time of a subsequent General Handoff Direction Message or a
24 Supplemental Channel Assignment Message that specifies a different
25 Reverse Supplemental assignment duration or start time.
26 ο If USE_REV_DURATIONr is equal to ‘0’, the mobile station may
27 continue to transmit indefinitely on the Reverse Supplemental Code
28 Channels, or until it receives the action time of a subsequent General
29 Handoff Direction Message or a Supplemental Channel Assignment
30 Message that specifies a different Reverse Supplemental assignment
31 duration or start time.
32 • If FOR_INCLUDED is equal to ‘1’, then the mobile station shall process Forward
33 Supplemental Code Channel assignment information as follows:
34 − The mobile station shall assign a value to FOR_START_TIMEs according to
35 the following rules:
36 + If EXPL_FOR_START_TIME is equal to ‘1’, the mobile station shall set the

37 FOR_START_TIMEs to FOR_START_TIMEr.
38 + If USE_FOR_HDM_SEQr is equal to ‘1’ and FOR_LINKED_HDM_SEQr is

39 not equal to HDM_SEQs, the mobile station shall set the
40 FOR_START_TIMEs to NULL.
2-301
C.S0005-0-2 v1.0
1 + If USE_FOR_HDM_SEQr is equal to ‘1’, FOR_LINKED_HDM_SEQr is equal

2 to HDM_SEQs, then the mobile station shall set the FOR_START_TIMEs
3 to the action time of the General Handoff Direction Message that is linked
4 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 start processing the Forward Supplemental
13 Code Channels in the CODE_CHAN_LISTs at FOR_START_TIMEs for a period
14 of time specified by the following rules:
15 + If USE_FOR_DURATION is equal to ‘1’, the mobile station shall set

16 FOR_DURATIONs to FOR_DURATIONr. The mobile station shall continue
17 processing the Forward Supplemental Code Channels for a period of
18 (FOR_DURATIONs × 80) ms, or until it receives the action time of a
19 subsequent Supplemental Channel Assignment Message or a General
20 Handoff Direction Message that specifies a different Forward
21 Supplemental assignment duration or start time.
22 + If USE_FOR_DURATIONr is equal to ‘0’, the mobile station shall continue
23 processing the Forward Supplemental Code Channels until it receives the
24 action time of a subsequent Supplemental Channel Assignment Message
25 or a General Handoff Direction Message that specifies a different Forward
26 Supplemental assignment duration or start time.
27 − If FOR_SUP_CONFIGr is equal to ‘10’, the mobile station shall perform the
28 following:
29 + The mobile station shall update the CODE_CHAN_LISTs as specified in
30 2.6.8.
31 + If FOR_START_TIMEs is not equal to NULL the mobile station should stop
32 processing Forward Supplemental Code Channels at the time specified by
33 FOR_START_TIMEs.
34 − If FOR_SUP_CONFIGr is equal to ‘11’, the mobile station shall perform the

35 following:
36 + The mobile station shall update the CODE_CHAN_LISTs as specified in
37 2.6.8.
38 + If FOR_START_TIMEs is not equal to NULL, then the mobile station shall
39 start processing the Forward Supplemental Code Channels in the
40 CODE_CHAN_LISTsat the time specified by FOR_START_TIMEs for a
41 period of time specified by the following rules:
2-302
C.S0005-0-2 v1.0
1 ο If USE_FOR_DURATIONr is equal to ‘1’, the mobile station shall set

2 FOR_DURATIONs to FOR_DURATIONr. The mobile station shall
3 continue processing the Forward Supplemental Code Channels for
4 (FOR_DURATIONs × 80) ms, until it receives a subsequent
5 Supplemental Channel Assignment Message or a General Handoff
6 Direction Message that specifies a different Forward Supplemental
7 assignment duration or start time.
8 ο If USE_FOR_DURATIONr is equal to ‘0’, the mobile station shall
9 continue processing the Forward Supplemental Code Channels until
10 it receives a subsequent Supplemental Channel Assignment Message
11 or a General Handoff Direction Message that specifies a different
12 Forward Supplemental assignment duration or start time.
13 9. General Handoff Direction Message: The mobile station shall process the message as
14 follows:
15 In addition to the requirements in this section, if the SCR_INCLUDED field is

16 included in this message and is set to ‘1’ the mobile station shall also process this
17 message in accordance with the requirements for the active service subfunction (see
18 2.6.4.1.2.2).
21 any other action described in this section for processing the General Handoff
22 Direction Message:
24 set to ‘00000110’ (capability not supported), if the mobile station does not
25 support the band class specified in the General Handoff Direction Message.
27 set to ‘00000110’ (capability not supported), if the number of forward or reverse
28 Supplemental Code Channels specified in the General Handoff Direction Message
29 is greater than the maximum number of Supplemental Code Channels
31 • If the SCR_INCLUDED field is included in this message and is set to ‘1’, the
33 - The mobile station shall send a Mobile Station Reject Order with the ORDQ
34 field set to ‘00000111’ (message cannot be handled by the current mobile
35 station configuration), if the mobile station does not support the service
36 configuration specified in the General Handoff Direction Message.
37 - The mobile station shall send a Mobile Station Reject Order (ORDQ =
38 ‘00000111’) within T56m seconds, if the mobile station supports the service
39 configuration specified but does not accept the service configuration specified
40 in the General Handoff Direction Message.
2-303
C.S0005-0-2 v1.0
2 set to ‘00000111’ (message cannot be handled by the current mobile station
3 configuration), if the NNSCR_INCLUDED field is included and set to ‘1’ and the
4 SCR_INCLUDED field is either not included or included but set to ‘0’, and the
5 mobile station does not support the configuration specified in the non-negotiable
6 service configuration information record in the General Handoff Direction
7 Message.
9 set to ‘00001010’ (search set not specified), if the PERIODIC_SEARCH field is
10 included in the General Handoff Direction Message and is set to ‘1’, and the
11 Candidate Frequency Search Set is empty.
13 set to ‘00001101’ (search period too short), if the PERIODIC_SEARCH field is
14 included in the General Handoff Direction Message and is set to ‘1’, and
15 search_period is less than (max (fwd_time, rev_time) + T71m seconds), where
16 search_period = time period corresponding to SEARCH_PERIODs shown in

17 Table 2.6.6.2.8.3.2-1,
18 fwd_time = the mobile station’s estimate of the total length of time, in seconds,
19 for which the mobile station will need to suspend its current
20 Forward Traffic Channel processing in order to tune to the CDMA
21 Candidate Frequency, to search the Candidate Frequency Search
22 Set, and to re-tune to the Serving Frequency; if the mobile station
23 searches the Candidate Frequency Search Set in multiple visits,
24 fwd_time is the total time for all visits to the CDMA Candidate
25 Frequency in a search period (see 2.6.6.2.8.3.2),
26 and
27 rev_time = the mobile station’s estimate of the total length of time, in seconds,
28 for which the mobile station will need to suspend its current Reverse
29 Traffic Channel processing in order to tune to the CDMA Candidate
30 Frequency, to search the Candidate Frequency Search Set, and to
31 re-tune to the Serving Frequency; if the mobile station searches the
32 Candidate Frequency Search Set in multiple visits, rev_time is the
33 total time for all visits to the CDMA Candidate Frequency in a search
34 period.
36 described in the remainder of this section to process the General Handoff Direction
37 Message at the action time of the message.
38 If EXTRA_PARMS is equal to ‘1’, the mobile station shall store the return on failure
39 indicator from the General Handoff Direction Message (RETURN_IF_HANDOFF_FAILs
40 = RETURN_IF_HANDOFF_FAILr); otherwise the mobile station shall set
41 RETURN_IF_HANDOFF_FAILs to ‘0’.
2-304
C.S0005-0-2 v1.0
1 The mobile station shall set RETURN_IF_HANDOFF_FAILs to ‘0’ (disable return on

2 failure) if any of the following conditions is true:
3 • If P_REV_IN_USEs is less than or equal to four and the mobile station does not
4 support hard handoff with return on failure, or
5 • At least one of the pilots specified by the message is also included in the Active
6 Set prior to the action time of the message, and one of the following conditions is
7 true:
8 − EXTRA_PARMS is equal to ‘0’, or
9 − EXTRA_PARMS is equal to ‘1’, the message specifies the same Frequency

10 Assignment as the Serving Frequency (BAND_CLASSr is equal to
11 CDMABANDs and CDMA_FREQr is equal to CDMACHs), and
12 FRAME_OFFSETr is equal to FRAME_OFFSETs.
13 The mobile station shall store the following parameters from its current
14 configuration:
15 • CDMA band class (SF_CDMABANDs = CDMABANDs)
16 • Frequency assignment (SF_CDMACHs = CDMACHs)
17 • Frame Offset (SF_FRAME_OFFSETs = FRAME_OFFSETs)
18 If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, the mobile station shall also store the
19 following parameters from its current configuration:
20 • Protocol revision level

21 (SF_P_REVs = P_REVs)
22 • Protocol revision level in use on the Serving Frequency

23 (SF_P_REV_IN_USEs = P_REV_IN_USEs)
24 • Search window size for the Active Set and Candidate Set
25 (SF_SRCH_WIN_As = SRCH_WIN_As)
26 • Search window size for the Neighbor Set

27 (SF_SRCH_WIN_Ns = SRCH_WIN_Ns)
28 • Search window size for the Remainder Set

29 (SF_SRCH_WIN_Rs = SRCH_WIN_Rs)
30 • Pilot detection threshold

31 (SF_T_ADDs = T_ADDs)
32 • Pilot drop threshold

33 (SF_T_DROPs = T_DROPs)
34 • Active Set versus Candidate Set comparison threshold

35 (SF_T_COMPs = T_COMPs)
36 • Drop timer value

37 (SF_T_TDROPs = T_TDROPs)
2-305
C.S0005-0-2 v1.0
1 • Soft slope for the dynamic add and drop thresholds

2 (SF_SOFT_SLOPEs = SOFT_SLOPEs)
3 • Intercept for the dynamic add threshold

4 (SF_ADD_INTERCEPTs = ADD_INTERCEPTs)
5 • Intercept for the dynamic drop threshold

6 (SF_DROP_INTERCEPTs = DROP_INTERCEPTs)
7 • Private long code mask indicator: If the mobile station is using the private long
8 code mask on the Serving Frequency, it shall set SF_PRIVATE_LCMs to ‘1’;
9 otherwise, it shall set SF_PRIVATE_LCMs to ‘0’.
10 • Service negotiation type

11 (SF_SERV_NEGs = SERV_NEGs)
12 • Service configuration :
13 Store the current service configuration (service configuration record and non-
14 negotiable service configuration record) in SF_SERVICE_CONFIGs
15 • Message encryption mode: If message encryption is on, the mobile station shall
16 set SF_ENCRYPT_MODEs to ‘1’; otherwise, the mobile station shall set
17 SF_ENCRYPT_MODEs to ‘0’.
18 • Extended nominal power setting of the current cell

19 (SF_NOM_PWR_EXTs = NOM_PWR_EXTs)
20 • Nominal power setting of the current cell

21 (SF_NOM_PWRs = NOM_PWRs)
22 • Power control step

23 (SF_PWR_CNTL_STEPs = PWR_CNTL_STEPs)
24 • Serving Frequency Active Set (SF Active Set = (For each pilot in the current
25 Active Set: (PILOT_PN, PWR_COMB_IND) ) )
26 • Serving Frequency Code Channel List

27 (SF_CODE_CHAN_LISTs = CODE_CHAN_LISTs)
28 When the message takes effect, the mobile station shall perform the following
29 actions:
31 2.6.6.2.5.2.
32 • Update the Active Set, Candidate Set, and Neighbor Set in accordance with the
33 General Handoff Direction Message processing (see 2.6.6.2.6.1, 2.6.6.2.6.2, and
34 2.6.6.2.6.3).
35 • The mobile station shall delete all pilots that are not listed in the Active Set of
36 the Fundamental Channel from the Active Set of the Supplemental Channel for
37 the Forward Supplemental Channel Assignment (if any). If these deleted pilots
38 include all pilots in the Active Set of the Supplemental Channel, the mobile
39 station shall cancel the Forward Supplemental Channel Assignment.
2-306
C.S0005-0-2 v1.0
1 • Discontinue use of all Forward Traffic Channels associated with pilots not listed
2 in the General Handoff Direction Message.
3 • If EXTRA_PARMS is equal to ‘1’, perform the following actions:

4 − If FRAME_OFFSETr is not equal to FRAME_OFFSETs, change the frame
5 offset on all of the code channels of the Forward Traffic Channel and of the
7 − If RESET_L2r is equal to ‘1’, and RETURN_IF_HANDOFF_FAILs is equal to ‘0’,
8 Layer 3 shall send a L2-Supervision.Request primitive to Layer 2 to reset the
9 acknowledgment procedures, as specified in 2.2.1.1 and 2.2.2.1 of
10 TIA/EIA/IS-2000-4.[4]. The mobile station shall reset the acknowledgment
11 procedures immediately after the action time of the General Handoff Direction
12 Message.
13 − If RESET_FPCr is equal to ‘1’ and RETURN_IF_HANDOFF_FAILs is equal to
14 ‘0’, initialize the Forward Traffic Channel power control counters, as specified
15 in 2.6.4.1.1.1.
16 − If SERV_NEG_TYPEr is equal to ‘1’, set SERV_NEGs to enabled; otherwise set
17 SERV_NEGs to disabled.− Use the long code mask specified by the
18 PRIVATE_LCMr (see 2.3.12.3) and indicate to the user the voice privacy mode
19 status.
20 − Process the ENCRYPT_MODE field, as specified in 2.3.12.2.
21 • If EXTRA_PARMS is equal to ‘0’, set the following variables to the values

22 indicated:
23 − Hard handoff traffic channel preamble count required before transmitting a

24 Handoff Completion Message (NUM_PREAMBLEs = ‘000’)
25 – Complete search flag (COMPLETE_SEARCHs = ‘1’)
26 − CDMA band class for the Target Frequency

27 (TF_CDMABANDs = SF_CDMABANDs)
28 − Frequency assignment for the Target Frequency

29 (TF_CDMACHs = SF_CDMACHs)
30 • Store the following parameters from the General Handoff Direction Message:
31 − General Handoff Direction Message sequence number

32 (HDM_SEQs = HDM_SEQr)
33 − Forward power control subchannel relative gain (FPC_SUBCHAN_GAINs =

34 FPC_SUBCHAN_GAINr).
35 − If the mobile station uses FPC_SUBCHAN_GAINs, the mobile station shall

37 + If PC_ACTION_TIMEr is received, the mobile station shall apply its usage
38 of the FPC_SUBCHAN_GAINs at the time specified by PC_ACTION_TIMEr.
2-307
C.S0005-0-2 v1.0
1 + If PC_ACTION_TIME is not received and the explicit action time is

2 received, the mobile station shall apply its usage of the
3 FPC_SUBCHAN_GAINs at the action time.
4 + If neither PC_ACTION_TIMEr nor explicit action time is received, the

5 mobile station shall apply its usage of the FPC_SUBCHAN_GAINs at the
6 first 80ms boundary occurring at least 80ms after the end of the frame
7 containing the last bit of the General Handoff Direction Message sent to
9 − Reverse Eighth Gating Mode (REV_FCH_GATING_MODEs =
10 REV_FCH_GATING_MODEr).
11 − Reverse Power Control Delay if REV_PWR_CNTL_DELAY_INCLr is equal to ‘1’

12 (REV_PWR_CNTL_DELAYs = REV_PWR_CNTL_DELAYr).
13 − If SEARCH_INCLUDED is equal to ‘1’, store the following:
16 + Pilot detection threshold

17 (T_ADDs = T_ADDr)
18 + Pilot drop threshold

19 (T_DROPs = T_DROPr)

22 + Drop timer value

23 (T_TDROPs = T_TDROPr)
24 + Soft slope for the dynamic add and drop thresholds

25 (SOFT_SLOPEs = SOFT_SLOPEr)
26 + Intercept for the dynamic add threshold

27 (ADD_INTERCEPTs = ADD_INTERCEPTr)
28 + Intercept for the dynamic drop threshold

29 (DROP_INTERCEPTs = DROP_INTERCEPTr)
30 − If EXTRA_PARMS is equal to ‘1’, store the following:

31 + Protocol revision level (P_REVs = P_REVr), and protocol revision level
32 currently in use (P_REV_IN_USEs = min (P_REVs, MOB_P_REVp of the
33 current band class) )
34 + If the mobile station supports packet data service options, the packet
35 data services zone identifier (PACKET_ZONE_IDs = PACKET_ZONE_IDr)
2-308
C.S0005-0-2 v1.0
1 + Acknowledgment procedures reset indicator

2 (If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, set TF_RESET_L2s to
3 RESET_L2r)
4 + Indicator to initialize the Forward Traffic Channel power control counters

5 (If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, set TF_RESET_FPCs to
6 RESET_FPCr)
8 + Extended nominal power setting of the target cell (If CDMABANDs =

9 ‘00000’ or CDMABANDs = ‘00011’, then NOM_PWR_EXTs = ‘0’; otherwise,
10 NOM_PWR_EXTs = NOM_PWR_EXTr)
11 + Hard handoff traffic channel preamble count required before transmitting

12 a Handoff Completion Message (NUM_PREAMBLEs = NUM_PREAMBLEr )
13 + CDMA band class for the Target Frequency

14 (TF_CDMABANDs = BAND_CLASSr and CDMABANDs = BAND_CLASSr)
15 + Frequency assignment for the Target Frequency

16 (TF_CDMACHs = CDMA_FREQr and CDMACHs = CDMA_FREQr)
17 + Complete search flag (COMPLETE_SEARCHs = COMPLETE_SEARCHr)
18 + Periodic search flag (PERIODIC_SEARCHs = PERIODIC_SEARCHr)
19 + Nominal code channel output power offset relative to the Reverse Pilot
20 Channel power (RLGAIN_TRAFFIC_PILOTs = RLGAIN_TRAFFIC_PILOTr)
21 – If EXTRA_PARMS is equal to ‘1’ and DEFAULT_RLAG is equal to ‘1’, the

22 mobile station shall set each entry of the Reverse Link Attribute Adjustment
23 Gain Table and Reverse Channel Adjustment Gain Table (see 2.1.2.3.3 of
24 TIA/EIA/IS-2000-2)[2]) to 0.
25 − If REV_PARMS_INCLUDED is included and is equal to '1', the mobile station

26 shall store the following:
27 + Reverse Supplemental Code Channel Request Message neighbor channel
28 pilot strength offset (T_MULCHANs = T_MULCHANr)
29 + Reverse Supplemental Code Channel beginning of transmission preamble

30 length (BEGIN_PREAMBLEs = BEGIN_PREAMBLEr)
31 + Reverse Supplemental Code Channel resumption of transmission

32 preamble length (RESUME_PREAMBLEs = RESUME_PREAMBLEr)
33 − For each pilot included in the message, the mobile station shall store the
34 following:
35 + PILOT_PN, the pilot PN sequence offset index
36 + PWR_COMB_IND, the power control symbol combining indicator
2-309
C.S0005-0-2 v1.0
1 − If USE_PWR_CNTL_STEP is equal to ‘1’ and PWR_CNTL_STEPr corresponds

2 to a power control step size supported by the mobile station (see 2.1.2.3.2 of
3 TIA/EIA/IS-2000-2)[2]), then the mobile station shall set PWR_CNTL_STEPs
4 to PWR_CNTL_STEPr.
5 • Set the pilot detection threshold for the Target Frequency and the Candidate
6 Frequency:
7 − Set TF_T_ADDs to T_ADDs.
8 − If the Target Frequency is the same as the Candidate Frequency

9 (TF_CDMABANDs is equal to CF_CDMABANDs and TF_CDMACHs is equal to
10 CF_CDMACHs), set CF_T_ADDs to T_ADDs.
11 • If FOR_INCLUDED is included and is equal to ‘0’, the mobile station shall

13 − The mobile station shall update the Code Channel List, CODE_CHAN_LISTs,
14 as specified in 2.6.8.
15 − If USE_FOR_HDM_SEQs is equal to ‘1’ and FOR_LINKED_HDM_SEQs is
16 equal to HDM_SEQr (this indicates that there is pending Forward
17 Supplemental Code Channel assignment information, received in a
18 Supplemental Channel Assignment Message, linked to this General Handoff
19 Direction Message), then the mobile station shall perform the following
20 actions:
21 + The mobile station shall set USE_FOR_HDM_SEQs to ‘0’.
22 + If SCAM_FOR_ORDERs is equal to ‘0’, the mobile station shall stop

23 processing all Forward Supplemental Code Channels at the action time of
24 the General Handoff Direction Message.
25 + If SCAM_FOR_ORDERs is equal to ‘1’, the mobile station shall start
26 processing the Forward Supplemental Code Channels specified in
27 CODE_CHAN_LISTs at the action time of the General Handoff Direction
28 Message, for a period of time determined by the following rules:
29 ο If SCAM_FOR_DURATION_MODEs is equal to ‘1’, the mobile station
30 shall continue processing the Forward Supplemental Code Channels
31 for a period of (FOR_DURATIONs × 80) ms, until it receives a
32 subsequent General Handoff Direction Message or a Supplemental
33 Channel Assignment Message that specifies a different Forward
34 Supplemental Code Channel assignment.
35 ο If SCAM_FOR_DURATION_MODEs is equal to ‘0’, the mobile station
36 shall continue processing the Forward Supplemental Code Channels
37 until it receives a subsequent Supplemental Channel Assignment
38 Message or a General Handoff Direction Message that specifies a
39 different Forward Supplemental Code Channel assignment.
2-310
C.S0005-0-2 v1.0
1 − If USE_FOR_HDM_SEQs is equal to ‘0’ or FOR_LINKED_HDM_SEQs is not

2 equal to HDM_SEQr, and if the mobile station is currently processing
3 Forward Supplemental Code Channels, it shall continue processing the
4 Forward Supplemental Code Channels using the updated Code Channel List,
5 CODE_CHAN_LISTs.
6 • If NNSCR_INCLUDED field is included and set to ‘1’ and SCR_INCLUDED field is

7 either not included or included but set to ‘0’, the mobile station shall process the
8 received Non-negotiable Service Configuration Record as specified in 2.6.4.1.13
9 at the action time of this message.
10 • If FOR_INCLUDED is included and is equal to ‘1’, then the mobile station shall
11 process the Forward Supplemental Code Channel assignment information as
12 follows:
13 − The mobile station shall set USE_FOR_HDM_SEQs to ‘0’.
14 − If FOR_START_TIMEs specifies a time which is after the action time of the

15 General Handoff Direction Message, the mobile station shall cancel any
16 pending Forward Supplemental Code Channel assignment and shall set
17 FOR_START_TIMEs to NULL.
18 − The mobile station shall update the Code Channel List, CODE_CHAN_LISTs,
19 in accordance with the value of FOR_SUP_CONFIG, as specified in 2.6.8.
20 − If FOR_SUP_CONFIG is equal to ‘00’ or ‘10’, the mobile station should stop

21 processing Forward Supplemental Code Channels, if any, when the message
22 takes effect.
23 − If FOR_SUP_CONFIG is equal to ‘01’ or ‘11’, the mobile station shall start

24 processing the Forward Supplemental Code Channels in the updated Code
25 Channel List, CODE_CHAN_LISTs, at the action time of the message, for a
26 period of time determined by the following rules:
27 + If USE_FOR_DURATION is equal to ‘1’, the mobile station shall set

28 FOR_DURATIONs to FOR_DURATIONr. The mobile station shall continue
29 processing the Forward Supplemental Code Channels for a period of
30 (FOR_DURATIONs × 80) ms, until it receives a subsequent Supplemental
31 Channel Assignment Message or a General Handoff Direction Message
32 that specifies a different Forward Supplemental Code Channel
33 assignment.
34 + If USE_FOR_DURATION is equal to ‘0’, the mobile station shall continue
35 processing the Forward Supplemental Code Channels until it receives a
36 subsequent Supplemental Channel Assignment Message or a General
37 Handoff Direction Message that specifies a different Forward
39 • If REV_INCLUDED is included and is equal to ‘0’, the mobile station shall

2-311
C.S0005-0-2 v1.0
1 − If USE_REV_HDM_SEQs is equal to ‘1’ and REV_LINKED_HDM_SEQs is

2 equal to HDM_SEQr (this indicates that there is pending Reverse
3 Supplemental Code Channel assignment information, received in a
4 Supplemental Channel Assignment Message, linked to this General Handoff
5 Direction Message), the mobile station shall perform the following actions:
6 + If NUM_REV_CODESs is equal to ‘000’, the mobile station shall stop
7 transmitting on all Reverse Supplemental Code Channels at the action
8 time of the message.
9 + If NUM_REV_CODESs is not equal to ‘000’, the mobile station may start

11 Channels at the action time of the message, for a duration of time
12 determined by the following rules:
13 ο If SCAM_REV_DURATION_MODEs is equal to ‘1’, the mobile station
14 may continue transmitting on the Reverse Supplemental Code
15 Channels for a period of (REV_DURATIONs × 80) ms, until it receives
16 a subsequent General Handoff Direction Message or a Supplemental
17 Channel Assignment Message that specifies a different Reverse
19 ο If SCAM_REV_DURATION_MODEs is equal to ‘0’, the mobile station
20 may continue transmitting on the Reverse Supplemental Code
21 Channels until it receives a subsequent General Handoff Direction
22 Message or a Supplemental Channel Assignment Message that
23 specifies a different Reverse Supplemental Code Channel assignment.
24 + The mobile station shall set USE_REV_HDM_SEQs to ‘0’.
25 − If USE_REV_HDM_SEQs is equal to ‘0’ or REV_LINKED_HDM_SEQs is not
26 equal to HDM_SEQr, and if the previous Reverse Supplemental Code
27 Channel assignment is still valid, the mobile station may continue to
28 transmit on the Reverse Supplemental Code Channels according to the
29 previously specified Reverse Supplemental Code Channel assignment.
30 • If REV_INCLUDED is included and is equal to ‘1’, then the mobile station shall
31 process the Reverse Supplemental Code Channel assignment information as
32 follows:
33 − The mobile station shall set REV_DTX_DURATIONs to
34 REV_DTX_DURATIONr.
35 − The mobile station shall set USE_REV_HDM_SEQs to ‘0’.
36 − If REV_START_TIMEs specifies a time which is after the action time of the

37 General Handoff Direction Message, the mobile station shall cancel any
38 pending Reverse Supplemental Code Channel assignment and shall set
39 REV_START_TIMEs to NULL.
2-312
C.S0005-0-2 v1.0
1 − If CLEAR_RETRY_DELAY is equal to ‘1’, the mobile station shall cancel any

2 previously indicated retry delay and shall set RETRY_DELAYs to 0, set
4 ‘010’ or ‘011’; otherwise, the mobile station shall continue to honor any
5 previously active retry delay stored in RETRY_DELAYs and
6 RETRY_DELAYs[RETRY_TYPE], where RETRY_TYPE is equal to ‘001’, ‘010’ or
7 ‘011’.
8 − The mobile station shall set NUM_REV_CODESs to NUM_REV_CODESr, and
10 + If NUM_REV_CODESs is equal to ‘000’, the mobile station shall stop
11 transmitting on all Reverse Supplemental Code Channels at the action
12 time of the message.
13 + If NUM_REV_CODESs is not equal to ‘000’, the mobile station may start

15 Channels at the action time of the message, for a duration of time
16 determined by the following rules:
17 ο If USE_REV_DURATIONr is equal to ‘1’, the mobile station shall set
18 REV_DURATIONs to REV_DURATIONr. The mobile station may
19 continue transmitting on the Reverse Supplemental Code Channels
20 for a period of (REV_DURATIONs × 80) ms, until it receives a
21 subsequent General Handoff Direction Message or a Supplemental
22 Channel Assignment Message that specifies a different Reverse
24 ο If USE_REV_DURATION is equal to ‘0’, the mobile station may

25 continue to transmit on the Reverse Supplemental Code Channels
26 until it receives a subsequent General Handoff Direction Message or a
27 Supplemental Channel Assignment Message that specifies a different
28 Reverse Supplemental Code Channel assignment.
29 − The mobile station shall store USE_T_ADD_ABORTr, the Reverse
30 Supplemental Code Channel assignment T_ADD abort indicator, as
31 USE_T_ADD_ABORTs.
32 • The mobile station shall set IGNORE_SCAMs and IGNORE_ESCAMs to ‘0’.
33 • If PERIODIC_SEARCHs is equal to ‘0’ and a periodic search is in progress, the

34 mobile station shall abort the periodic search (see 2.6.6.2.8.3.4 and
35 2.6.6.2.10.4).
37 − If any of the following conditions is true, the mobile station shall perform a
38 hard handoff:
39 + EXTRA_PARMS is set to ‘1’ and either BAND_CLASSr is not equal to
2-313
C.S0005-0-2 v1.0
1 + The set of pilots specified by the message is disjoint from the Active
2 Set prior to the action time of the message.
3 − If the mobile station performs a hard handoff, it shall do the following:
4 + If a Periodic Serving Frequency Pilot Report Procedure is in progress, the

5 mobile station shall abort the procedure (see 2.6.6.2.12).
6 + If a Candidate Frequency periodic search is in progress, the mobile station

7 shall abort the periodic search (see 2.6.6.2.8.3.4 and 2.6.6.2.10.4).
8 + The mobile station shall cancel the Forward Supplemental Channel

9 assignment or the Reverse Supplemental Channel assignment (if any).
10 + If RETURN_IF_HANDOFF_FAILs is equal to ‘0’, the mobile station shall
11 perform actions specified in 2.6.6.2.8.1. If the message specifies more than
12 one pilot, the mobile station shall also perform actions specified in
13 2.6.6.2.7.1 and 2.6.6.2.7.2.
15 perform actions specified in 2.6.6.2.8.2. If the message specifies more than
16 one pilot, the mobile station shall also perform actions specified in
17 2.6.6.2.7.1 and 2.6.6.2.7.2.
18 − Otherwise, the mobile station shall perform a soft handoff as specified in

19 2.6.6.2.7.
20 10. Periodic Pilot Measurement Request Order: The mobile station shall perform the
21 following:
22 • If the PPSMM timer is enabled, disable it.

23 • If ORDQ is equal to ‘11111111’, the mobile station shall send a Periodic Pilot
24 Strength Measurement Message to the base station within T56m seconds.
25 • If ORDQ is equal to ‘11111111’, the mobile station shall send a Periodic Pilot
26 Strength Measurement Message to the base station within T56m seconds.
27 • If ORDQ is not equal to ‘11111111’, the mobile station shall perform the
28 following:
29 − Set the MIN_PILOT_PWR_THRESHs to MIN_PILOT_PWR_THRESHr
30 received from the Periodic Pilot Strength Measurement Request Order.
31 − Set the MIN_PILOT_EC_IO_THRESHs to MIN_PILOT_EC_IO_THRESHr
32 received from the Periodic Pilot Strength Measurement Request Order.
33 − Set PPSMM_PERIODs equal to the larger value of ORDQ and the total
34 length of time, in units of 80 ms, required by the mobile station to update
35 the pilot strength measurement of each pilot in the Active Set and the
36 Candidate Set.
37 − Perform the Periodic Serving Frequency Pilot Report Procedure as

2-314
C.S0005-0-2 v1.0
1 11. Universal Handoff Direction Message: The mobile station shall process the message
2 as follows:
3 In addition to the requirements in this section, if the SCR_INCLUDED field is

4 included in this message and is set to ‘1’ the mobile station shall also process this
5 message in accordance with the requirements for the active service subfunction (see
6 2.6.4.1.2.2).
9 any other action described in this section for processing the Universal Handoff
10 Direction Message:
12 set to ‘00000110’ (capability not supported), if the mobile station does not
13 support the band class specified in the Universal Handoff Direction Message.
14 • If the SCR_INCLUDED field is included in this message and is set to ‘1’, the
16 - The mobile station shall send a Mobile Station Reject Order with the ORDQ
17 field set to ‘00000111’ (message cannot be handled by the current mobile
18 station configuration), if the mobile station does not support the service
19 configuration specified in the Universal Handoff Direction Message.
20 - The mobile station shall send a Mobile Station Reject Order (ORDQ =
21 ‘00000111’) within T56m seconds, if the mobile station supports the service
22 configuration specified but does not accept the service configuration specified
23 in the Universal Handoff Direction Message.
25 set to ‘00000111’ (message cannot be handled by the current mobile station
26 configuration), if the NNSCR_INCLUDED field is included and set to ‘1’ and the
27 SCR_INCLUDED field is either not included or included but set to ‘0’, and the
28 mobile station does not support the configuration specified in the non-negotiable
29 service configuration information record in the Universal Handoff Direction
30 Message.
32 set to ‘00001010’ (search set not specified), if the PERIODIC_SEARCH field is
33 included in the Universal Handoff Direction Message is set to ‘1’ and the
34 Candidate Frequency Search Set is empty.
36 set to ‘00000011’ (message structure not acceptable), if the message specifies the
37 Forward/Reverse Supplemental Channel assignment and the most significant
38 bit of CH_INDr is set to ‘0’.
2-315
C.S0005-0-2 v1.0
3 configuration), if the message includes a reverse Supplemental Channel
4 assignment, and any mobile station’s reverse supplemental channel
5 configuration parameter for the corresponding Supplemental Channel is NULL.
8 configuration), if the message includes a forward Supplemental Channel
9 assignment and any mobile station’s forward supplemental channel
11 • The mobile station shall send a Mobile Station Reject Order with the ORDQ field set
12 to ‘00001101’ (search period too short), if the PERIODIC_SEARCH field is included
13 in the Universal Handoff Direction Message and is set to ‘1’, and search_period is less
14 than (max (fwd_time, rev_time) + T71m seconds), where
15 search_period = time period corresponding to SEARCH_PERIODs shown in

16 Table 2.6.6.2.8.3.2-1,
17 fwd_time = the mobile station’s estimate of the total length of time, in seconds,
18 for which the mobile station will need to suspend its current Forward Traffic
19 Channel processing in order to tune to the CDMA Candidate Frequency, to search
20 the Candidate Frequency Search Set, and to re-tune to the Serving Frequency; if the
21 mobile station searches the Candidate Frequency Search Set in multiple visits,
22 fwd_time is the total time for all visits to the CDMA Candidate Frequency in a search
23 period (see 2.6.6.2.8.3.2),
24 and
25 rev_time = the mobile station’s estimate of the total length of time, in seconds, for
26 which the mobile station will need to suspend its current Reverse Traffic Channel
27 processing in order to tune to the CDMA Candidate Frequency, to search the
28 Candidate Frequency Search Set, and to re-tune to the Serving Frequency; if the
29 mobile station searches the Candidate Frequency Search Set in multiple visits,
30 rev_time is the total time for all visits to the CDMA Candidate Frequency in a search
31 period.
33 described in the remainder of this section to process the Universal Handoff Direction
34 Message at the action time of the message.
35 If EXTRA_PARMS is equal to '1', the mobile station shall store the return on failure
36 indicator from the Universal Handoff Direction Message
37 (RETURN_IF_HANDOFF_FAILs = RETURN_IF_HANDOFF_FAILr); otherwise the
38 mobile station shall set RETURN_IF_HANDOFF_FAILs to ‘0’.
39 The mobile station shall set RETURN_IF_HANDOFF_FAILs to ‘0’ (disable return on

40 failure) if any of the following conditions is true:
41 • If P_REV_IN_USEs is less than or equal to four and the mobile station does not
2-316
C.S0005-0-2 v1.0
1 support hard handoff with return on failure, or
2 • At least one of the pilots specified by the message is also included in the Active
3 Set prior to the action time of the message, and one of the following conditions is
4 true:
5 − EXTRA_PARMS is equal to ‘0’, or
6 − EXTRA_PARMS is equal to ‘1’, the message specifies the same Frequency

7 Assignment as the Serving Frequency (BAND_CLASSr is equal to
8 CDMABANDs and CDMA_FREQr is equal to CDMACHs), and
9 FRAME_OFFSETr is equal to FRAME_OFFSETs.
10 The mobile station shall store the following parameters from its current
11 configuration:
12 • CDMA band class (SF_CDMABANDs = CDMABANDs)
13 • Frequency assignment (SF_CDMACHs = CDMACHs)
14 • Frame Offset (SF_FRAME_OFFSETs = FRAME_OFFSETs)
15 If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, the mobile station shall also store the
16 following parameters from its current configuration:
17 • Protocol revision level (SF_P_REVs = P_REVs)
18 • Protocol revision level in use on the Serving Frequency (SF_P_REV_IN_USEs
19 = P_REV_IN_USEs)
20 • Search window size for the Active Set and Candidate Set (SF_SRCH_WIN_As
21 = SRCH_WIN_As)
22 • Search window size for the Neighbor Set

23 (SF_SRCH_WIN_Ns = SRCH_WIN_Ns),
24 • Search window size for the Remainder Set

25 (SF_SRCH_WIN_Rs = SRCH_WIN_Rs)
26 • Pilot detection threshold (SF_T_ADDs = T_ADDs)
27 • Pilot drop threshold (SF_T_DROPs = T_DROPs)
28 • Active Set versus Candidate Set comparison threshold

29 (SF_T_COMPs = T_COMPs)
30 • Drop timer value (SF_T_TDROPs = T_TDROPs)
31 • Soft slope for the dynamic add and drop thresholds

32 (SF_SOFT_SLOPEs = SOFT_SLOPEs)
33 • Intercept for the dynamic add threshold

34 (SF_ADD_INTERCEPTs = ADD_INTERCEPTs)
35 • Intercept for the dynamic drop threshold

36 (SF_DROP_INTERCEPTs = DROP_INTERCEPTs)
2-317
C.S0005-0-2 v1.0
1 • Private long code mask indicator: If the mobile station is using the private
2 long code mask on the Serving Frequency, it shall set SF_PRIVATE_LCMs to
3 ‘1’; otherwise, it shall set SF_PRIVATE_LCMs to ‘0’.
4 • Service negotiation type (SF_SERV_NEGs = SERV_NEGs)
5 • Service configuration : Store the current service configuration (service

6 configuration record and non-negotiable service configuration record) in
7 SF_SERVICE_CONFIGs
8 • Message encryption mode: If message encryption is on, the mobile station

9 shall set SF_ENCRYPT_MODEs to ‘1’; otherwise, the mobile station shall set
10 SF_ENCRYPT_MODEs to ‘0’.
11 • If NNSCR_INCLUDED field is included and set to ‘1’ and SCR_INCLUDED

12 field is either not included or included but set to ‘0’, the mobile station shall
13 process the received Non-negotiable Service Configuration Record as
14 specified in 2.6.4.1.13 at the action time of this message.
15 • Extended nominal power setting of the current cell

16 (SF_NOM_PWR_EXTs = NOM_PWR_EXTs)
17 • Nominal power setting of the current cell (SF_NOM_PWRs = NOM_PWRs)
18 • Power control step (SF_PWR_CNTL_STEPs = PWR_CNTL_STEPs)
19 • Serving Frequency Active Set (SF Active Set = (For each pilot in the current
20 Active Set: (PILOT_PN, PWR_COMB_IND) ) )
21 • Serving Frequency Code Channel List

22 (SF_CODE_CHAN_LISTs = CODE_CHAN_LISTs)
23 When the message takes effect, the mobile station shall perform the following
24 actions:
26 2.6.6.2.5.2.
27 • Update the Active Set, Candidate Set, and Neighbor Set in accordance with
28 the Universal Handoff Direction Message processing (see 2.6.6.2.6.1,
29 2.6.6.2.6.2, and 2.6.6.2.6.3).
30 • Discontinue use of all Forward Traffic Channels associated with pilots not in
31 the updated Active Set.
32 • If PARMS_INCL is equal to ‘1’, perform the following actions:

33 – Set protocol revision level (P_REVs = P_REVr), and protocol revision level
34 currently in use (P_REV_IN_USEs = min (P_REVs, MOB_P_REVp of the
35 current band class)).
36 – If SERV_NEG_TYPEr is equal to ‘1’, set SERV_NEGs to enabled; otherwise
37 set SERV_NEGs to disabled.
38 • If EXTRA_PARMS is equal to ‘1’, perform the following actions:
2-318
C.S0005-0-2 v1.0
1 – If FRAME_OFFSETr is not equal to FRAME_OFFSETs, change the frame

2 offset on all of the code channels of the Forward Traffic Channel and of
3 the Reverse Traffic Channel.
4 – If RESET_L2r is equal to ‘1’, and RETURN_IF_HANDOFF_FAILs is equal
5 to ‘0’, Layer 3 shall send a L2-Supervision.Request primitive to Layer 2 to
6 reset the acknowledgment procedures, as specified in 2.2.1.1 and 2.2.2.1
7 of TIA/EIA/IS-2000-4.[4]. The mobile station shall reset the
8 acknowledgment procedures immediately after the action time of the
9 Universal Handoff Direction Message.
10 – If RESET_FPCr is equal to ‘1’ and RETURN_IF_HANDOFF_FAILs is equal
11 to ‘0’, initialize the Forward Traffic Channel power control counters, as
12 specified in 2.6.4.1.1.1.
13 – Use the long code mask specified by the PRIVATE_LCMr (see 2.3.12.3)
14 and indicate to the user the voice privacy mode status.
15 – Process the ENCRYPT_MODE field, as specified in 2.3.12.2.
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 (NUM_PREAMBLEs = ‘000’)
20 – Complete search flag (COMPLETE_SEARCHs = ‘1’)
21 – CDMA band class for the Target Frequency

22 (TF_CDMABANDs = SF_CDMABANDs)
23 – Frequency assignment for the Target Frequency

24 (TF_CDMACHs = SF_CDMACHs)
25 • Store the following parameters from the Universal Handoff Direction Message:
26 – Universal Handoff Direction Message sequence number

27 (HDM_SEQs = HDM_SEQr)
28 – Forward power control subchannel relative gain (FPC_SUBCHAN_GAINs =

29 FPC_SUBCHAN_GAINr).
30 − If the mobile station uses FPC_SUBCHAN_GAINs, the mobile station shall

32 + If PC_ACTION_TIMEr is received, the mobile station shall apply its
33 usage of the FPC_SUBCHAN_GAINs at the time specified by
34 PC_ACTION_TIMEr.
35 + If PC_ACTION_TIME is not received and the explicit action time is

36 received, the mobile station shall apply its usage of the
37 FPC_SUBCHAN_GAINs at the action time.
2-319
C.S0005-0-2 v1.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-320
C.S0005-0-2 v1.0
1 + Hard handoff traffic channel preamble count required before

2 transmitting a Handoff Completion Message (NUM_PREAMBLEs =
3 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 TIA/EIA/IS-2000-2)[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 TIA/EIA/IS-2000-2)[2]), then the mobile station shall set
22 PWR_CNTL_STEPs to 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 RETRY_DELAYs to 0, set
26 ‘010’ or ‘011’; otherwise, the mobile station shall continue to honor any
27 previously active retry delay stored in RETRY_DELAYs and
28 RETRY_DELAYs[RETRY_TYPE], where RETRY_TYPE is equal to ‘001’, ‘010’
29 or ‘011’.
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-321
C.S0005-0-2 v1.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_RATEs[REV_SCH_IDr] = REV_SCH_RATEr
11 – If CH_INDr is equal to ‘101’, the mobile station shall perform the
12 following:
13 + The mobile station shall set CH_INDs = ‘01’.
14 + If SCH_INCLr is equal to ‘1’ and NUM_FOR_SCH is not equal to

15 ‘00000’, for all the NUM_FOR_SCH occurrences, the mobile station
17 ο Set FOR_SCH_RATEs[FOR_SCH_IDr][SCCL_INDEXr] to
18 FOR_SCH_RATEr.
19 + If SCH_INCLr is equal to ‘1’ and NUM_REV_SCH is not equal to

20 ‘00000’, for all the NUM_REV_SCH occurrences, the mobile station
22 ο Set REV_SCH_RATEs[REV_SCH_IDr] to REV_SCH_RATEr.
23 ο Set REV_WALSH_IDs[REV_SCH_IDr][REV_SCH_RATEs] to
24 REV_WALSH_IDr.
25 + For each member of the Active Set included in the message, the
27 ο Set PILOT_PN to PILOT_PNr.
28 ο If SRCH_OFFSET_INCLr equals to ‘1’, set the SRCH_OFFSET field

29 of PILOT_REC to SRCH_OFFSETr; otherwise, set the
30 SRCH_OFFSET field of PILOT_REC to ‘000’.
31 ο Set ADD_PILOT_REC_INCL to ADD_PILOT_REC_INCLr.
32 ο If ADD_PILOT_REC_INCr equals ‘1’, the mobile station shall also


35 PILOT_REC_TYPEr.
2-322
C.S0005-0-2 v1.0
1 ◊ If PILOT_REC_TYPEr is equal to ‘000’, the mobile station shall

2 set the OTD_POWER_LEVEL field of PILOT_REC to
3 OTD_POWER_LEVELr.
4 ο Store PWR_COMB_IND, CODE_CHAN_FCH and

5 QOF_MASK_ID_FCH.
6 ο If SCH_INCLr is equal to ‘1’ and NUM_SCH is equal to ‘00000’, the
7 mobile station shall delete the corresponding pilot from all entries
8 of the corresponding Supplemental Channel.
9 ο If SCH_INCLr is equal to ‘1’ and NUM_SCH is not equal to ‘00000’,
10 for each Supplemental Channel included in this record, the
11 mobile station shall:
12 ◊ If PILOT_INCL is equal to ‘0’, the mobile station shall delete

13 the corresponding pilot from the Active Set of Supplemental
14 Channel for the corresponding SCCL_INDEXr.
15 ◊ If PILOT_INCL is equal to ‘1’, for each Supplemental Channel

16 included in this record, the mobile station shall set PILOT_PNs
17 [FOR_SCH_IDr][SCCL_INDEXr][i] to PILOT_PNr,
18 QOF_IDs[FOR_SCH_IDr][SCCL_INDEXr][i] to
19 QOF_MASK_ID_SCHr, and
20 FOR_SCH_CC_INDEXs[FOR_SCH_IDr][SCCL_INDEXr][i] to
21 CODE_CHAN_SCHr.
22 ◊ The mobile station shall delete all pilots that are not included
23 in the list specified by the NUM_PILOTS field from the Active
24 Set of Supplemental Channel for the corresponding
25 SCCL_INDEXr.
26 + The mobile station shall delete all pilots that are not listed in the
27 NUM_PILOTS field from the Active Set of Fundamental Channel.
29 Active Set of the Fundamental Channel from the Active Set of the
30 Supplemental Channel for the Forward Supplemental Channel
31 Assignment (if any). If these deleted pilots include all pilots in the
32 Active Set of the Supplemental Channel, the mobile station shall
34 – If CH_INDr is equal to ‘010’ or ‘110’, the mobile station shall perform the
35 following:

2-323
C.S0005-0-2 v1.0
2 FOR_SCH_RATEr.

8 REV_WALSH_IDr.
10 mobile station shall perform the followings:



19 PILOT_REC_TYPEr.

23 ο Store PWR_COMB_IND, CODE_CHAN_DCCH and

24 QOF_MASK_ID_DCCH.
29 the mobile station shall:


35 [FOR_SCH_IDr][SCCL_INDEXs][i] to PILOT_PNr,
36 QOF_IDs[FOR_SCH_IDr][SCCL_INDEXs][i] to
37 QOF_MASK_ID_SCHr, and FOR_SCH_CC_INDEXs
38 [FOR_SCH_IDs][SCCL_INDEXs][i] to CODE_CHAN_SCHr.
2-324
C.S0005-0-2 v1.0
4 SCCL_INDEXr.
6 NUM_PILOTS field from the Active Set of Dedicated Control Channel.
8 Active Set of the Dedicated Control Channel from the Active Set of the
9 Supplemental Channel for the Forward Supplemental Channel
10 Assignment (if any). If these deleted pilots include all pilots in the
11 Active Set of the Supplemental Channel, the mobile station shall
13 – If CH_INDr is equal to ‘111’, the mobile station shall perform the
14 following:

20 FOR_SCH_RATEr.

26 REV_WALSH_IDr.
28 mobile station shall perform the followings:



37 PILOT_REC_TYPEr.
2-325
C.S0005-0-2 v1.0

3 OTD_POWER_LEVELr.
4 ο Store PWR_COMB_IND, CODE_CHAN_FCH, QOF_MASK_ID_FCH,

5 CODE_CHAN_DCCH and QOF_MASK_ID_DCCH.
10 the mobile station shall:


16 [FOR_SCH_IDr][SCCL_INDEXr][i] to PILOT_PNr,
17 QOF_IDs[FOR_SCH_IDr][SCCL_INDEXr][i] to
18 QOF_MASK_ID_SCHr, and FOR_SCH_CC_INDEXs
19 [FOR_SCH_IDr][SCCL_INDEXr][i] to CODE_CHAN_SCHr.
23 SCCL_INDEXr.
25 NUM_PILOTS field from the Active Set of Fundamental Channel and
26 Dedicated Control Channel.
28 Active Set of the Fundamental Channel and Dedicated Control
29 Channel from the Active Set of the Supplemental Channel for the
30 Forward Supplemental Channel Assignment (if any). If these deleted
31 pilots include all pilots in the Active Set of the Supplemental
32 Channel, the mobile station shall cancel the Forward Supplemental
33 Channel Assignment.
34 • If the most significant bit of CH_INDr is set to ‘1’ and
35 PILOT_GATING_USE_RATE is equal to ‘1’, the mobile station shall set
36 PILOT_GATING_USE_RATE to ‘0’ and shall start the continuous reverse pilot
37 at the specified action time. If the most significant bit of CH_INDr is set to ‘0’
38 and PILOT_GATING_USE_RATE is equal to ‘0’, the mobile station shall
40 - The mobile station shall set PILOT_GATING_USE_RATE to ‘1’ and shall

41 start the reverse pilot gating at the specified action time.
2-326
C.S0005-0-2 v1.0
1 - If the Fundamental Channel is also being released, the mobile station

2 shall store the configuration used for the Fundamental Channel.
3 - The mobile station shall cancel the forward and reverse supplemental
4 channel assignment, if any
5 • The mobile station shall set IGNORE_ESCAMs and IGNORE_SCAMs to ‘0’.
6 • Set the pilot detection threshold for the Target Frequency and the Candidate
7 Frequency:
8 – Set TF_T_ADDs to T_ADDs.
9 – If the Target Frequency is the same as the Candidate Frequency

10 (TF_CDMABANDs is equal to CF_CDMABANDs and TF_CDMACHs is
11 equal to CF_CDMACHs), set CF_T_ADDs to T_ADDs.
12 • If PERIODIC_SEARCHs is equal to ‘0’ and a periodic search is in progress,

13 the mobile station shall abort the periodic search (see 2.6.6.2.8.3.4 and
14 2.6.6.2.10.4).
16 – If any of the following conditions is true, the mobile station shall perform a
17 hard handoff:
18 + EXTRA_PARMS is set to ‘1’ and either BAND_CLASSr is not equal to
21 + The set of pilots specified by the message is disjoint from the Active Set
22 prior to the action time of the message.
23 – If the mobile station performs a hard handoff, it shall do the following:
24 + If a Periodic Serving Frequency Pilot Report Procedure is in progress,

25 abort the procedure (see 2.6.6.2.12).
26 + If a Candidate Frequency periodic search is in progress, the mobile

27 station shall abort the periodic search (see 2.6.6.2.8.3.4 and
28 2.6.6.2.10.4).
29 + If a Forward Supplemental Channel assignment or a Reverse

30 Supplemental Channel assignment is in progress, the mobile station
31 shall abort it.
32 + The mobile station shall cancel any outstanding Forward Supplemental

33 Channel assignment or Reverse Supplemental Channel assignment that
34 is not specified by this message.
36 perform actions specified in 2.6.6.2.8.1. If the message specifies more
37 than 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-327
C.S0005-0-2 v1.0

2 perform actions specified in 2.6.6.2.8.2. If the message specifies more
3 than 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.
8 process this message as follows:
9 • The mobile station shall set ORDER_FLAGs to ORDER_FLAGr.
10 • If ORDER_FLAGr is equal to ‘1’, the mobile station shall perform the

11 following:
12 – The mobile station shall set PS_MIN_DELTAs to PS_MIN_DELTAr+ 1.
13 – The mobile station shall set ORDER_INTERVALs to ORDER_INTERVALr.
14 • If ORDER_FLAGr is equal to ‘0’, the mobile station shall perform the

15 following:
16 – The mobile station shall set PS_MIN_DELTAs to 0.
17 – The mobile station shall set ORDER_INTERVALs to 0.
18 • The mobile station shall set PERIODIC_FLAGs to PERIODIC_FLAGr.
19 • If PERIODIC_FLAGr is equal to ‘1’, the mobile station shall perform the

20 following:
21 – The mobile station shall set NUM_PILOTSs to NUM_PILOTSr.
22 – The mobile station shall set PERIODIC_INTERVALs to

23 PERIODIC_INTERVALr.
24 • If PERIODIC_FLAGr is equal to ‘0’, the mobile station shall perform the

25 following:
26 – The mobile station shall set NUM_PILOTSs to 0.
27 – The mobile station shall set PERIODIC_INTERVALs to 0.
28 • The mobile station shall set THRESHOLD_FLAGs to THRESHOLD_FLAGr.
29 • If THRESHOLD_FLAGr is equal to ‘1’, the mobile station shall perform the

30 following:
31 – The mobile station shall set PS_FLOOR_LOWs to PS_FLOOR_LOWr.
32 – The mobile station shall set PS_FLOOR_HIGHs to PS_FLOOR_HIGHr.
33 – The mobile station shall set PS_CEILING_LOWs to PS_CEILING_LOWr.
34 – The mobile station shall set PS_CEILING_HIGHs to PS_CEILING_HIGHr.
35 • If THRESHOLD_FLAGr is equal to ‘0’, the mobile station shall perform the

36 following:
2-328
C.S0005-0-2 v1.0
1 – The mobile station shall set PS_FLOOR_LOWs to ‘0’.
2 – The mobile station shall set PS_FLOOR_HIGHs to ‘0’.
3 – The mobile station shall set PS_CEILING_LOWs to ‘0’.
4 – The mobile station shall set PS_CEILING_HIGHs to ‘0’.
6 process this message as follows:
7 The mobile station shall send a Mobile Station Reject Order with the ORDQ field
8 set to the specified value if any of the following conditions is true, and shall not
9 perform any other action described in this section for processing the Extended
10 Supplemental Channel Assignment Message:
11 • The mobile station shall send a Mobile Station Reject Order with the ORDQ
12 field set to ‘00000110’ (capability not supported), if the number of forward or
13 reverse Supplemental Channels specified in the Extended Supplemental
14 Channel Assignment Message is greater than the maximum number of
15 Supplemental Channels supported by the mobile station.
17 field set to ‘00000100’ (message field not in valid range), if PILOT_PN
18 specified in the Extended Supplemental Channel Assignment Message is not
19 in the Active Set.
21 field set to ‘00000111’ (message can not be handled by the current mobile
22 station configuration), if the message includes a reverse Supplemental
23 Channel assignment, and any mobile station’s reverse supplemental channel
24 configuration parameter for the corresponding Supplemental Channel is
25 NULL.
27 field set to ‘00000111’ (message can not be handled by the current mobile
28 station configuration), if the message includes a forward Supplemental
29 Channel assignment and any mobile station’s forward supplemental channel
30 configuration parameter for the corresponding Supplemental Channel is
31 NULL.
32 If none of the above conditions is true, the mobile station shall perform the
33 following:
34 • The mobile station shall store REV_SCH_DTX_DURATIONr, Reverse
35 Supplemental Channel Discontinuous Transmission Duration, as
36 REV_SCH_DTX_DURATIONs.
37 • The mobile station shall store the unit for START_TIME_UNITs =

38 START_TIME_UNITr.
39 • The mobile station shall store USE_T_ADD_ABORTr, Reverse Supplemental

40 Channel assignment T_ADD abort indicator, as USE_T_ADD_ABORTs.
2-329
C.S0005-0-2 v1.0
1 • If IGNORE_ESCAMs is equal to ‘1’ and SCRM_SEQ_NUMr is not present or is

2 present and is not equal to SCRM_SEQ_NUMs, then the mobile station shall
3 not process the remaining Reverse Supplemental Channel assignment
4 information in this message.
5 • If IGNORE_ESCAMs is equal to ‘1’ and SCRM_SEQ_NUMr is present and is
6 equal to SCRM_SEQ_NUMs, then the mobile station shall set
7 IGNORE_ESCAMs to ‘0’.
8 • If ADD_INFO_INCLr is equal to ‘1’ the message includes a Supplemental

9 Channel assignment (that is, NUM_FOR_SCHr is not equal to ‘00’ and/or
10 NUM_REV_SCHr is not equal to ‘00’), and PILOT_GATING_USE_RATE is
11 equal to ‘1’, the mobile station shall process the following information of the
12 Extended Supplemental Channel Assignment Message as follows:
13 – The mobile station shall set FPC_PRI_CHANs = FPC_PRI_CHANr at the
14 action time of the message.
15 • If REV_CFG_INCLUDED is equal to ‘1’, for all the (NUM_REV_CFG_RECS + 1)

16 occurrences of the reverse configuration record, the mobile station shall
17 store the REV_WALSH_ID matrix as follows:
18 – REV_WALSH_IDs[REV_SCH_IDr][REV_SCH_RATEr] = REV_WALSH_IDr
19 • If NUM_REV_SCHr is not equal to ‘00’, then the mobile station shall store the
20 following information for each occurrence of the record and process the
21 Reverse Supplemental Burst as specified in 2.6.6.2.5.1.2:
22 – REV_SCH_START_TIME_INCLs[REV_SCH_IDr] =
23 REV_SCH_START_TIME_INCLr
24 – If REV_SCH_START_TIME_INCLs[REV_SCH_IDr] is set to ‘1’, set

25 REV_SCH_START_TIMEs[REV_SCH_IDr] = REV_SCH_START_TIMEr
26 – REV_SCH_DURATIONs[REV_SCH_IDr] = REV_SCH_DURATIONr
27 – REV_SCH_RATEs[REV_SCH_IDr] = REV_SCH_RATEr
28 • If NUM_FOR_SCHr is not equal to ‘00’, then the mobile station shall store the
29 following information for each occurrence of the record and process the
30 Forward Supplemental Burst as specified in 2.6.6.2.5.1.1:
31 – FOR_SCH_START_TIME_INCLs[FOR_SCH_IDr] =
32 FOR_SCH_START_TIME_INCLr
33 – If FOR_SCH_START_TIME_INCLs[FOR_SCH_IDr] is set to ‘1’, set

34 FOR_SCH_START_TIMEs[FOR_SCH_IDr] = FOR_SCH_START_TIMEr
35 – FOR_SCH_DURATIONs[FOR_SCH_IDr] = FOR_SCH_DURATIONr
36 – SCCL_INDEXs[FOR_SCH_IDr] = SCCL_INDEXr
37 • If FOR_CFG_INCLUDEDs is equal to ‘1’, the mobile station shall perform the

38 following:
2-330
C.S0005-0-2 v1.0
1 – Set FOR_SCH_FER_REPs to FOR_SCH_FER_REPr.
2 – If FOR_SCH_FER_REPr is equal to ‘0’, set SCH_TOT_FRAMESs and

3 SCH_BAD_FRAMESs to 0.
4 – Store NUM_FOR_CFG_RECS occurrences of Forward Supplemental

5 Channel Configuration associated with the identification of Forward
7 • For each record of the Forward Supplemental Channel Code list the mobile
8 station shall store the Forward Supplemental Channel Code list associated
9 with the FOR_SCH_IDr as follows:
10 – FOR_SCH_RATEs[FOR_SCH_IDr][SCCL_INDEXr] = FOR_SCH_RATEr.
11 – NUM_SUP_SHOs[FOR_SCH_IDr][SCCL_INDEXr] = NUM_SUP_SHOr.
12 – For the ith 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

18 ADD_PILOT_REC_INCLr equals ‘1’, the mobile station shall store the
19 following:
20 ο Set the PILOT_REC_TYPE field of PILOT_REC to
21 PILOT_REC_TYPEr.
22 ο If PILOT_REC_TYPEr is equal to ‘000’, the mobile station shall set
23 the OTD_POWER_LEVEL field of PILOT_REC to
25 + QOF_MASK_ID_SCHs[FOR_SCH_IDr][SCCL_INDEXr][i] =
26 QOF_MASK_ID_SCHr,
27 + FOR_SCH_CC_INDEXs[FOR_SCH_IDr][SCCL_INDEXr][i]=
28 FOR_SCH_CC_INDEXr.
29 • The mobile station may soft-combine the Forward Supplemental Channel

30 frames received on the Forward Supplemental Channels in the same Forward
31 Supplemental Channel Active Set.
32 • If the mobile station supports any Radio Configuration greater than 2, the
34 – If FPC_INCLr is equal to ‘1’, the mobile station shall set
35 FPC_MODE_SCHs to FPC_MODE_SCHr
36 – If FPC_INCL is equal to ‘1’ and FPC_MODE is equal to ‘001’or ‘010’’, the

37 mobile station shall set FPC_SEC_CHANs to FPC_SEC_CHANr.
2-331
C.S0005-0-2 v1.0
1 – If NUM_SUPr is included and not equal to ‘00’, for each Supplemental

2 Channel included in the message, the mobile station shall:
3 + Set SCH_IDs to SCH_IDr.
4 + Set FPC_SCH_FERs to FPC_SCH_FER.
5 + Set FPC_SCH_INIT_SETPTs as follows:
6 ο If FPC_SCH_INIT_SETPT_OPr is set to ‘0’, set

7 FPC_SCH_INIT_SETPTs to FPC_SCH_INIT_SETPTr.
8 ο If FPC_SCH_INIT_SETPT_OPr is set to ‘1’:
9 ◊ If FPC_PRI_CHANr is equal to ‘0’, set FPC_SCH_INIT_SETPTs

10 to (FPC_FCH_CURR_SETPTs + FPC_SCH_INIT_SETPTr).
11 ◊ Otherwise, set FPC_SCH_INIT_SETPTs to

12 (FPC_DCCH_CURR_SETPTs + FPC_SCH_INIT_SETPTr).
13 + Set FPC_SCH_MIN_SETPTs to FPC_SCH_MIN_SETPTr.
14 + Set FPC_SCH_MAX_SETPTs to FPC_SCH_MAX_SETPTr.
15 – If FPC_THRESH_SCH_INCL is included and equal to ‘1’, the mobile

16 station shall set FPC_SETPT_THRESH_SCHs to
17 FPC_SETPT_THRESH_SCHr.
18 • If RPC_INCL is equal to ‘1’, the mobile station shall store

19 RLGAIN_SCH_PILOTr, and use it as RLGAIN_SCH_PILOTs at the start time of
20 the reverse Supplemental Channel assignment specified in the message.
21 • If PILOT_GATING_USE_RATE is set to ‘1’ and if NUM_REV_SCHr or
22 NUM_FOR_SCHr is not equal to ‘00’, the mobile station shall perform the
23 following:
24 – The mobile station shall set PILOT_GATING_USE_RATE to ‘0’ and shall

25 start the continuous reverse pilot at the specified action time.
26 – If the Fundamental Channel was previously established prior to

27 transitioning to the Control Hold Mode, the mobile station shall start
28 processing F-FCH and start transmitting on R-FCH at the action time of
29 the message. The mobile station shall establish the Fundamental
30 Channel with the same configuration as previously used.
31
33 shall process this message as follows:
36 configuration), if any mobile station’s forward supplemental channel
38 Otherwise the mobile station shall store the following information and process
2-332
C.S0005-0-2 v1.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:

10 - If the Fundamental Channel was previously established prior to

11 transitioning to the Control Hold mode, the mobile station shall start
16 shall process this message as follows:
19 configuration), if any mobile station’s reverse supplemental channel
21 If IGNORE_ESCAMs is equal to ‘1’, the mobile station shall not process the
22 Reverse Supplemental Channel assignment information in this message.
23 Otherwise, the mobile station shall store the following information and process
24 the Reverse Supplemental Burst as specified in 2.6.6.2.5.1.2:
25 • Set REV_SCH_START_TIME_INCLs [REV_SCH_IDr] to ‘1’
26 • REV_SCH_START_TIMEs[REV_SCH_IDr] = REV_SCH_START_TIMEr
27 • REV_SCH_DURATIONs[REV_SCH_IDr] = REV_SCH_DURATIONr
28 • REV_SCH_RATEs[REV_SCH_IDr] = REV_SCH_RATEr
29 • If PILOT_GATING_USE_RATE is set to ‘1’, the mobile station shall perform

30 the following:

33 - If the Fundamental Channel was previously established prior to

34 transitioning to the Control Hold mode, the mobile station shall start
2-333
C.S0005-0-2 v1.0
1 2.6.6.2.5.1.1 Processing of the Forward Supplemental Burst Assignment
2 A Forward Supplemental Assignment specifies the explicit start time specified by

3 FOR_SCH_START_TIME, or the implicit start time (if FOR_SCH_START_TIME_INCL is set to
4 ‘0’) FOR_SCH_DURATION, and SCCL_INDEX of a forward burst assignment. The time
5 interval of duration is specified by FOR_SCH_DURATION (see Table 3.7.3.3.2.37-3) and
6 starts at the time specified by the explicit start time FOR_SCH_START_TIME or the implicit
7 start time (if FOR_SCH_START_TIME_INCL is set to ‘0’). This time interval for a Forward
8 Supplemental Assignment is called the Forward Supplemental Assignment Interval. A
9 value of FOR_SCH_DURATION equal to '1111' indicates infinite duration. The variable
10 SCCL_INDEXs[FOR_SCH_ID] specifies the rate, QOF index and the Active Set for the
11 Forward Supplemental Channel identified by FOR_SCH_ID for a given Forward
12 Supplemental Assignment. A value of FOR_SCH_DURATION equal to '0000' indicates that
13 the mobile station should stop processing the forward Supplemental Channels at the
14 explicit start time specified by FOR_SCH_START_TIME or the implicit start time (if
15 FOR_SCH_START_TIME_INCL is set to ‘0’). The implicit start time is the time occurring no
16 later than the first 80 ms boundary (relative to System Time) which occurs at least 80 ms
17 after the end of the frame containing the last bit of the message carrying the forward
18 supplemental burst assignment.
19 For each Forward Supplemental Assignment the mobile station shall determine the start
20 time for processing forward supplemental channel as the time for which the following
21 equation holds:
22 (t/(START_TIME_UNITs+1) − FOR_SCH_START_TIMEr) mod 32 = 0,
23 where t is the System Time in units of 20 ms.
24 Figure 2.6.6.2.5.1.1-1 illustrates the scenario in which a second Forward Supplemental

25 Assignment is received while the mobile station is processing the forward supplemental
26 channel according to a previously received assignment. Two cases are displayed in Figure
27 2.6.6.2.5.1.1-1: Case a) where the first assignment extends beyond the start time of the
28 second assignment and Case b) where the first assignment ends before the second one
29 starts.
30
31
2-334
C.S0005-0-2 v1.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-335
C.S0005-0-2 v1.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 rate, QOF index, and the
19 Supplemental Channel Active Set indexed by SCCL_INDEXs[FOR_SCH_ID].
20 – Otherwise, if the mobile station is not currently processing the Forward

21 Supplemental Channel identified by FOR_SCH_ID, then at the time specified by
22 FOR_SCH_START_TIMEs[FOR_SCH_ID], the mobile station should start
23 processing the Forward Supplemental Channel identified by FOR_SCH_ID for a
24 duration of time specified by FOR_SCH_DURATIONs[FOR_SCH_ID] with the rate,
25 QOF index, and the Supplemental Channel Active Set indexed by
26 SCCL_INDEXs[FOR_SCH_ID].
27 • If FOR_SCH_DURATIONs[FOR_SCH_ID] is equal to ‘0000’, the mobile station should

29 – If FOR_SCH_START_TIME INCLs is equal to ‘1’, the mobile station should stop
30 processing the Forward Supplemental Channel identified by FOR_SCH_ID at the
31 time specified by FOR_SCH_START_TIMEs[FOR_SCH_ID].
32 – If FOR_SCH_START_TIME INCLs is equal to ‘0’, the mobile station should stop

33 processing the Forward Supplemental Channel identified by FOR_SCH_ID no
34 later than the first 80 ms boundary (relative to System Time) occurring at least
35 80 ms at the end of the frame containing the last bit of the message.
36 2.6.6.2.5.1.2 Processing of the Reverse Supplemental Burst Assignment
37 A Reverse Supplemental Assignment specifies the explicit start time identified by

38 REV_SCH_START_TIME or the implicit start time (if REV_SCH_START_TIME_INCL is set to
39 ‘0’), REV_SCH_DURATION, and REV_SCH_RATE of a reverse burst assignment. The time
40 interval of duration is specified by REV_SCH_DURATION (see Table 3.7.3.3.2.37-3) and
41 starts at the time specified by the explicit start time REV_SCH_START_TIME or the implicit
2-336
C.S0005-0-2 v1.0
1 start time (if REV_SCH_START_TIME_INCL is set to ‘0’). This time interval for a Reverse
2 Supplemental Assignment is called the reverse supplemental assignment interval. A value
3 of REV_SCH_DURATION equal to '1111' indicates infinite duration. A value of
4 REV_SCH_DURATION equal to '0000' indicates that the mobile station should stop
5 transmitting the reverse Supplemental Channels at the explicit start time specified by
6 REV_SCH_START_TIME or the implicit start time (if REV_SCH_START_TIME_INCL is set to
7 ‘0’). The implicit start time is the time occurring no later than the first 80 ms boundary
8 (relative to System Time) which occurs at least 80 ms after the end of the frame containing
9 the last bit of the message carrying the reverse supplemental burst assignment.
10 For each Reverse Supplemental Assignment the mobile station shall determine the start
11 time for processing reverse supplemental channel as the time for which the following
12 equation holds:
13 (t/(START_TIME_UNITs+1) − REV_SCH_START_TIMEr) mod 32 = 0,
15 Figure 2.6.6.2.5.1.1-1 illustrates the scenario in which a second Reverse Supplemental

16 Assignment is received while the mobile station is transmitting on the reverse supplemental
17 channel according to a previously received assignment. Two cases are displayed in Figure
18 2.6.6.2.5.1.2-1: Case a) where the first assignment extends beyond the start time of the
19 second assignment and Case b) where the first assignment ends before the second one
20 starts.
21 Figure 2.6.6.2.5.1.1-2 shows an example scenario in which the mobile station receives a
22 second Reverse Supplemental Assignment before it starts transmitting on the supplemental
23 channel according to the first assignment. In this case, the second assignment simply
24 replaces the first assignment.
25 For each Reverse Supplemental Channel assignment corresponding to each Reverse

26 Supplemental Channel (identified by REV_SCH_ID), the mobile station shall perform the
27 following:
28 • If REV_SCH_DURATIONs[REV_SCH_ID] is not equal to ‘0000’, then
29 – If the mobile station is currently transmitting on the Reverse Supplemental

30 Channel identified by REV_SCH_ID, then the mobile station may continue
31 transmitting on the Reverse Supplemental Channel identified by REV_SCH_ID
32 with the Walsh cover specified by
33 REV_WALSH_IDs[REV_SCH_ID][REV_SCH_RATE] according to the current
34 Reverse Supplemental Assignment for the Reverse Supplemental Channel
35 identified by REV_SCH_ID up to the time specified by the
36 REV_SCH_START_TIMEs[REV_SCH_ID] (i.e., the mobile station shall stop
37 transmitting on the reverse supplemental channel identified by REV_SCH_ID at
38 either the time specified by REV_SCH_START_TIMEs[REV_SCH_ID], the start
39 time of the new assignment, or at the time the previously received assignment
40 ends, whichever time is earlier).
2-337
C.S0005-0-2 v1.0
1 At the time specified by REV_SCH_START_TIMES[REV_SCH_ID], the mobile

2 station may start transmitting on the Reverse Supplemental Channel identified
3 by REV_SCH_ID with the Walsh cover specified by
4 REV_WALSH_IDs[REV_SCH_ID][REV_SCH_RATEs[REV_SCH_ID]] and the rate
5 specified by REV_SCH_RATEs[REV_SCH_ID].
6 – If the mobile station is not currently transmitting on the Reverse Supplemental

7 Channel identified by REV_SCH_ID, then at the time specified by
8 REV_SCH_START_TIMEs[REV_SCH_ID], the mobile station may start
10 with the Walsh cover specified by
11 REV_WALSH_IDs[REV_SCH_ID][REV_SCH_RATEs[REV_SCH_ID]] and the rate
12 specified by REV_SCH_RATEs[REV_SCH_ID].
13 • If REV_SCH_DURATIONs[REV_SCH_ID] is equal to ‘0000’, the mobile station shall

14 perform the followings:
15 – If REV_START_TIME_INCLs is equal to ‘1’, the mobile station shall stop
16 transmitting on the Reverse Supplemental Channel identified by REV_SCH_ID at
17 the time specified by REV_SCH_START_TIMEs[REV_SCH_ID].
18 – If REV_START_TIME_INCLs is equal to ‘0’, the mobile station shall stop

20 no later than the first 80 ms boundary (relative to System Time) occurring at
21 least 80 ms at the end of the frame containing the last bit of the message.
22 2.6.6.2.5.2 Processing of Reverse Traffic Channel Handoff Messages
23 The mobile station sends the following messages on the Reverse Traffic Channel in support
24 of handoff when its transmitter is enabled, following the receipt of a forward dedicated
25 channel acquired indication from Layer 2 (see 2.2.2.1.2 of TIA/EIA/IS-2000-4)[4]):
26 1. Pilot Strength Measurement Message: The mobile station shall send an autonomous
27 Pilot Strength Measurement Message in assured mode. The mobile station shall send
28 this message containing measurements consistent with the event whenever any of
29 the following events occur:
30 • P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to
31 ‘000000’ and the strength of a Neighbor Set or Remaining Set pilot is found to be
32 above T_ADDs.
33 • P_REV_IN_USEs is greater than three, SOFT_SLOPEs is not equal to ‘000000’,

34 and the strength PS, as specified in 2.6.6.2.2, of any Candidate Set pilot is found
35 to satisfy the following inequality:
∑ PSi +
SOFT_SLOPEs ADD_INTERCEPT s
36 10 × log 10PS > × 10 × log 10
8 2
i∈A
2-338
C.S0005-0-2 v1.0
1 where the summation is performed over all pilots currently in the Active Set and
2 a Pilot Strength Measurement Message carrying this information has not been
3 sent since the last Extended Handoff Direction Message , General Handoff
4 Direction Message or Universal Handoff Direction Message was received.
6 and the strength PS, as specified in 2.6.6.2.2, of any Neighbor Set or Remaining
7 Set pilot is found to satisfy the following inequality:
8
∑ PSi +
SOFT_SLOPEs ADD_INTERCEPT s T_ADD s
9 10 × log 10PS > max( × 10 × log 10 , )
8 2 2
i∈A
10 where the summation is performed over all pilots currently in the Active Set.
11 • P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to
12 ‘000000’, the strength of a Candidate Set pilot exceeds the strength of an Active
13 Set pilot by T_COMPs × 0.5 dB, and a Pilot Strength Measurement Message
14 carrying this information has not been sent since the last Extended Handoff
15 Direction Message, General Handoff Direction Message or Universal Handoff
16 Direction Message was received.
18 and the strength of a Candidate Set pilot exceeds the strength of an Active Set
19 pilot by T_COMPs × 0.5 dB and satisfies the following inequality:
∑ PSi +
SOFT_SLOPEs ADD_INTERCEPTs
20 10 × log 10PS > × 10 × log10
8 2
i∈A
21 where the summation is performed over all pilots currently in the Active Set and
22 a Pilot Strength Measurement Message carrying this information has not been
23 sent since the last Extended Handoff Direction Message ,General Handoff
24 Direction Message or Universal Handoff Direction Message was received.
25 • The handoff drop timer of an Active Set pilot has expired and a Pilot Strength
26 Measurement Message carrying this information has not been sent since the last
27 Extended Handoff Direction Message, General Handoff Direction Message, or
28 Universal handoff Direction Message was received.
29 2. Handoff Completion Message: The mobile station shall send a Handoff Completion
30 Message in assured mode as follows:
31 • If the handoff message (Extended Handoff Direction Message, General Handoff

32 Direction Message or Universal Handoff Direction Message) specifies a soft
33 handoff, the mobile station shall send the Handoff Completion Message within
34 T56m seconds after the action time of the received handoff message.
35 • If the handoff message (Extended Handoff Direction Message, General Handoff

36 Direction Message or Universal Handoff Direction Message) specifies a hard
37 handoff without return on failure (see 2.6.6.2.8.1), the mobile station shall send
38 the Handoff Completion Message within T73m seconds after the action time of
39 the received handoff message.
2-339
C.S0005-0-2 v1.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
4 within T56m seconds after mobile station declares the handoff to be successful
5 (see 2.6.6.2.8.2).
6 3. Candidate Frequency Search Report Message: The mobile station shall send a
7 Candidate Frequency Search Report Message in assured mode, whenever any of the
8 following events occur:
9 • RETURN_IF_HANDOFF_FAILs is equal to ‘1’, and a handoff attempt is
10 unsuccessful (see 2.6.6.2.8.2). In this case, the mobile station shall send a
11 Candidate Frequency Search Report Message within T56m seconds after
12 completing a search of all pilots in the Candidate Frequency Search Set and
13 resuming the use of the Serving Frequency Active Set (see 2.6.6.2.8.2.1).
14 • RETURN_IF_HANDOFF_FAILs is equal to ‘1’, an inter-frequency handoff attempt
15 is unsuccessful (see 2.6.6.2.8.2), and PERIODIC_SEARCHs is equal to ‘1’. In
16 this case, the mobile station shall send a Candidate Frequency Search Report
17 Message in a search period if the conditions specified in 2.6.6.2.8.3.2 are met.
18 • The mobile station receives a Candidate Frequency Search Request Message or a

19 Candidate Frequency Search Control Message with SEARCH_TYPE set to ‘01’. If
20 none of the conditions requiring the mobile station to send a Mobile Station
21 Reject Order is true (see 2.6.6.2.5.1), the mobile station shall send a Candidate
22 Frequency Search Report Message, as described in 2.6.6.2.8.3.1 and
23 2.6.6.2.10.1.
24 • The mobile station receives a Candidate Frequency Search Request Message or
25 Candidate Frequency Search Control Message with SEARCH_TYPE set to ‘11’,
26 SEARCH_MODEs is equal to ‘0000’ and the Candidate Frequency Search Set is
27 not empty. If none of the conditions requiring the mobile station to send a
28 Mobile Station Reject Order is true (see 2.6.6.2.5.1), the mobile station shall send
29 a Candidate Frequency Search Report Message in a search period if the
30 conditions specified in 2.6.6.2.8.3.2 are met.
31 • The mobile station receives a Candidate Frequency Search Request Message or
32 Candidate Frequency Search Control Message with SEARCH_TYPE set to ‘11’,
33 SEARCH_MODEs is equal to ‘0001’ and the Candidate Frequency Analog Search
34 Set is not empty. If none of the conditions requiring the mobile station to send a
35 Mobile Station Reject Order is true (see 2.6.6.2.5.1), the mobile station shall send
36 a Candidate Frequency Search Report Message in a search period if the
37 conditions specified in 2.6.6.2.10.2 are met.
38 4. Periodic Pilot Strength Measurement Message: The mobile station shall send a
39 Periodic Pilot Strength Measurement Message in unassured mode, as specified in
40 2.6.6.2.5.1 and 2.6.6.2.12.
41 5. Pilot Strength Measurement Mini Message: If the mobile station supports the Mobile
42 Assisted Burst operation capability, the mobile station shall send this message while
2-340
C.S0005-0-2 v1.0
1 processing any Supplemental Channel, according to the following:
2 • The mobile station shall transmit a Pilot Strength Measurement Mini Message for
3 a pilot p in the Active Set on the r-dsch logical channel whenever all of the
4 following conditions are true:
5 – ORDER_FLAGs is equal to ‘1’.
6 – The pilot p in the Active Set has a received signal strength that is greater
7 than the signal strength of another pilot in the Active Set by
8 PS_MIN_DELTAs, in units of 0.5 dB, at the current time and has been for
9 ORDER_INTERVALs most recent successive 20 ms frame intervals since this
10 pilot was last reported in a rank order based Pilot Strength Measurement Mini
11 Message.
12 – The rank order of pilot p has changed.

13 • If PERIODIC_FLAGs is equal to ‘1’, the mobile station shall transmit a Pilot
14 Strength Measurement Mini Message within PERIODIC_INTERVALs 20 ms frame
15 intervals on the r-dsch for each of the n pilots in the Active Set with the largest
16 signal strengths, where n = (min (NUM_PILOTS, the number of pilots in the
17 Active Set)), whenever the following condition is true:
18 – The mobile station has not transmitted another Pilot Strength
19 Measurement Mini Message for the corresponding pilot during the last
20 PERIODIC_INTERVALs 20 ms frame intervals.
21 • If THRESHOLD_FLAGs is equal to ‘1’, the mobile station shall transmit a Pilot

22 Strength Measurement Mini Message for pilot p on the r-dsch logical channel
23 whenever all of the following conditions are true:
24 – The mobile station has not transmitted a previous Pilot Strength Measurement
25 Mini Message for pilot p within the most recent THRESHOLD_INTERVALs 20
26 ms frames intervals.
27 – Pilot p is in the Active Set.
28 – The signal strength of pilot p is greater than PS_CEILING_HIGHs and the
29 signal strength of pilot p was less than or equal to PS_CEILING_LOWs at any
30 time since the mobile station last sent a Pilot Strength Measurement Mini
31 Message for pilot p; or the signal strength of pilot p is less than
32 PS_FLOOR_LOWs and the signal strength for pilot p was greater than or
33 equal to PS_FLOOR_HIGHs at any time since the last time that the mobile
34 station sent a Pilot Strength Measurement Mini Message for pilot p.
35 2.6.6.2.6 Set Maintenance
36 2.6.6.2.6.1 Maintenance of the Active Set

37 The mobile station shall support a maximum Active Set size of N6m pilots. The mobile
38 station shall track the pilot strengths of all pilots in the Active Set.
2-341
C.S0005-0-2 v1.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, it shall replace
5 the pilots in the Active Set with the pilots listed in the message.
6 2.6.6.2.6.2 Maintenance of the Candidate Set

7 The mobile station shall support a maximum Candidate Set size of N7m pilots.
8 When the mobile station is first assigned a Forward Traffic Channel, the mobile station
9 shall initialize the Candidate Set to contain no pilots. The mobile station shall adjust the
10 Candidate Set whenever any of the following events occur:
11 • If the mobile station detects that the strength of a Neighbor Set pilot or a Remaining
12 Set pilot exceeds T_ADDs, the mobile station shall add the pilot to the Candidate
13 Set.
14 • If the mobile station processes an Extended Handoff Direction Message, a General
15 Handoff Direction Message or a Universal Handoff Direction Message which does not
16 list a pilot in the current Active Set, and the handoff drop timer corresponding to
17 that pilot has not expired, the mobile station shall add the pilot to the Candidate
18 Set.
19 • If P_REV_IN_USEs is greater than three, and SOFT_SLOPEs is not equal to ‘000000’,
20 the mobile station shall perform the following: If the mobile station processes a
21 General Handoff Direction Message or a Universal Handoff Direction Message which
22 does not list a pilot in the current Active Set, the handoff drop timer corresponding
23 to that pilot has expired, and that pilot is found to be above T_DROPs, the mobile
24 station shall add the pilot to the Candidate Set.
26 Handoff Direction Message or Universal Handoff Direction Message, which lists a
27 pilot in the current Candidate Set, the mobile station shall delete the pilot from the
28 Candidate Set.
29 • If the handoff drop timer corresponding to a Candidate Set pilot expires, the mobile
30 station shall delete the pilot from the Candidate Set.
31 • If the mobile station adds a pilot to the Candidate Set, and the resulting Candidate
32 Set size exceeds N7m, the mobile station shall delete from the Candidate Set the
33 pilot whose handoff drop timer is closest to expiration. If more than one such pilot
34 exists, the mobile station shall delete one such pilot that has the lowest strength. If
35 no pilot in the Candidate Set has an enabled handoff drop timer, the mobile station
36 shall delete from the Candidate Set the pilot that has the lowest strength.
37 2.6.6.2.6.3 Maintenance of the Neighbor Set

38 The mobile station shall support a Neighbor Set size of at least N8m pilots.
39 When the mobile station is first assigned a Forward Traffic Channel, the mobile station
40 shall initialize the Neighbor Set to contain all the pilots specified in the most recently
2-342
C.S0005-0-2 v1.0
1 received Neighbor List Message, Extended Neighbor List Message or General Neighbor List
2 Message.
3 The mobile station shall maintain a counter, AGEs, for each pilot in the Neighbor Set. The
4 mobile station shall initialize this counter to zero when it moves the pilot from the Active
5 Set or the Candidate Set to the Neighbor Set. The mobile station shall initialize this
6 counter to NGHBR_MAX_AGEs when it moves the pilot from the Remaining Set to the
7 Neighbor Set. The mobile station shall increment AGEs for each pilot in the Neighbor Set
8 upon receipt of a Neighbor List Update Message or an Extended Neighbor List Update
9 Message. When the mobile station is first assigned to a Forward Traffic Channel, the
10 mobile station shall set AGEs for each pilot in the Neighbor Set to NGHBR_MAX_AGEs.
11 The mobile station shall adjust the Neighbor Set whenever any of the following events
12 occur:
13 • If the mobile station receives a Neighbor List Update Message or an Extended
14 Neighbor List Update Message, it shall perform the following:
15 – Increment AGEs for each pilot in the Neighbor Set.
16 – Delete from the Neighbor Set all pilots whose AGEs exceeds NGHBR_MAX_AGEs.
17 – Add to the Neighbor Set each pilot named in the message, if it is not already a
18 pilot of the Active Set, Candidate Set, or Neighbor Set. If the mobile station can
19 store in the Neighbor Set only k additional pilots, and more than k new pilots
20 were sent in the Neighbor List Update Message or the Extended Neighbor List
21 Update Message, the mobile station shall store the first k new pilots listed in the
22 message.
23 • If the handoff drop timer of a pilot in the Candidate Set expires, the mobile station
24 shall add the pilot to the Neighbor Set.
25 • If P_REV_IN_USEs is less than or equal to three or SOFT_SLOPEs is equal to
26 ‘000000’, the mobile station shall perform the following: If the mobile station
27 processes an Extended Handoff Direction Message, a General Handoff Direction
28 Message, or a Universal Handoff Direction Message in which a pilot in the Active Set
29 is not listed, and the handoff drop timer corresponding to the pilot has expired, the
30 mobile station shall add the pilot to the Neighbor Set.
31 • If P_REV_IN_USEs is greater than three, and SOFT_SLOPEs is not equal to ‘000000’,
32 the mobile station shall perform the following: If the mobile station processes an
33 Extended Handoff Direction Message, a General Handoff Direction Message, or a
34 Universal Handoff Direction Message which does not list a pilot in the current Active
35 Set, the handoff drop timer corresponding to that pilot has expired, and that pilot is
36 found to be below T_DROPs, the mobile station shall add the pilot to the Neighbor
37 Set.
38 • If the mobile station adds a pilot to the Candidate Set, and the resulting Candidate
39 Set size exceeds the size supported by the mobile station, the mobile station shall
40 add the deleted Candidate Set pilot to the Neighbor Set (see 2.6.6.2.6.2).
2-343
C.S0005-0-2 v1.0
1 • If the mobile station detects that the strength of a Neighbor Set pilot exceeds
2 T_ADDs, the mobile station shall delete the pilot from the Neighbor Set.

4 Handoff Direction Message or a Universal Handoff Direction Message which lists a
5 pilot in the current Neighbor Set, the mobile station shall delete the pilot from the
6 Neighbor Set.
7 • If the mobile station adds a pilot to the Neighbor Set, and the resulting Neighbor Set
8 size exceeds the size supported by the mobile station, the mobile station shall delete
9 from the Neighbor Set the pilot whose AGEs is the largest. If more than one such
10 pilot exists, the mobile station shall delete one such pilot that has the lowest
11 strength.
12 2.6.6.2.7 Soft Handoff
13 2.6.6.2.7.1 Forward Traffic Channel Processing
14 All Forward Traffic Channels associated with pilots in the Active Set of the mobile station
15 carry identical modulation symbols with the exception of the power control subchannel (see
16 TIA/EIA/IS-2000-2)[2]).
17 When the Active Set contains more than one pilot, the mobile station should provide
18 diversity combining of the associated Forward Traffic Channels. The mobile station shall
19 provide for differential propagation delays from zero to at least 150 µs.
20 2.6.6.2.7.2 Reverse Traffic Channel Power Control During Soft Handoff

21 The Extended Handoff Direction Message, a General Handoff Direction Message or a
22 Universal Handoff Direction Message identifies sets of Forward Fundamental Code Channels
23 or Forward Dedicated Control Channels that carry identical closed loop power control
24 subchannels. A set consists of one or more Forward Fundamental Code Channels or
25 Forward Dedicated Control Channels with identical power control information.
26 In each power control group containing valid power control bits (see TIA/EIA/IS-2000-2)[2]),
27 the mobile station should provide diversity combining of the identical closed loop power
28 control subchannels and shall obtain at most one power control bit from each set of
29 identical closed loop power control subchannels. The mobile station should only combine
30 reliable power control bits (see 9.3.8 of TIA/EIA-98-C[14]) as follows:
31 • If the reliable power control bits obtained from all sets are equal to ‘0’, the mobile
32 station shall increase its power as specified in TIA/EIA/IS-2000-2.[2].
33 • If the reliable power control bit obtained from any set is equal to ‘1’, the mobile
34 station shall decrease its power as specified in TIA/EIA/IS-2000-2.[2].
35 2.6.6.2.7.3 Starting Periodic Search following Soft Handoff

36 If the PERIODIC SEARCHs is equal to ‘1’, a periodic search is not already in progress, and
37 the Frequency Assignment after handoff is different from the Candidate Frequency
2-344
C.S0005-0-2 v1.0
1 (CDMABANDs is not equal to CF_CDMABANDs or CDMACHs is not equal to CF_CDMACHs),

2 the mobile station shall do the following:
3 • The mobile station shall set ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs to
4 ‘000000’.• The mobile station shall start a periodic search as described in
5 2.6.6.2.8.3.2.
6 2.6.6.2.8 CDMA-to-CDMA Hard Handoff
7 The base station directs the mobile station to perform a CDMA-to-CDMA hard handoff by
8 sending an Extended Handoff Direction Message, a General Handoff Direction Message or a
9 Universal Handoff Direction Message in which the mobile station is transitioned between
10 disjoint sets of base stations, different Frequency Assignments, or different frame offsets. If
11 RETURN_IF_HANDOFF_FAILs is equal to ‘0’, the mobile station performs the actions
12 described in 2.6.6.2.8.1. If RETURN_IF_HANDOFF_FAILs is equal to ‘1’, the mobile station
13 performs the actions described in 2.6.6.2.8.2.
14 2.6.6.2.8.1 Hard Handoff without Return on Failure

15 At the action time specified of the Extended Handoff Direction Message, the General Handoff
16 Direction Message or Universal Handoff Direction Message the mobile station shall disable
17 its transmitter, reset the fade timer specified in 2.6.4.1.8, suspend incrementing
18 TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs, and DCCH_BAD_FRAMESs if
19 applicable as specified in 2.6.4.1.1, and tune to the assigned Forward Traffic Channel. The
20 mobile station shall perform acquisition of the pilots in the new Active Set.
21 If a periodic Serving Frequency pilot report procedure is in progress, the mobile station
22 shall abort it (see 2.6.6.2.12).
23 The mobile station shall begin monitoring the assigned Forward Traffic Channel within the
24 time specified below:
25 • If the Extended Handoff Direction Message, General Handoff Direction Message or
26 Universal Handoff Direction Message specifies a CDMA Frequency Assignment
27 different from the Serving Frequency and an Active Set containing pilots with pilot
28 PN sequence offsets identical to those of the pilots in the Serving Frequency Active
29 Set, the mobile station shall begin monitoring the assigned Forward Traffic Channel
30 within T60m seconds after the action time.

32 Universal Handoff Direction Message specifies a CDMA Frequency Assignment
33 different from the Serving Frequency and an Active Set containing a pilot with pilot
34 PN sequence offset not equal to that of any pilot in the Serving Frequency Active Set,
35 the mobile station shall begin monitoring the assigned Forward Traffic Channel
36 within T61m seconds after the action time.

38 Universal Handoff Direction Message specifies a CDMA-to-CDMA hard handoff
39 without changing the CDMA Frequency Assignment, the mobile station shall begin
40 monitoring the assigned Forward Traffic Channel within T62m seconds after the
41 action time.
2-345
C.S0005-0-2 v1.0
1 After the action time, upon receiving a period of (N11m × 20) ms with sufficient signal
2 quality (e.g. good frames) on the physical channel corresponding to FPC_PRI_CHANs on the
3 assigned Forward Traffic Channel, the mobile station shall re-enable its transmitter. The
4 mobile station shall transmit the Traffic Channel Preamble, as described in 2.1.3.6.2.3 of
5 TIA/EIA/IS-2000-[2], followed by a Handoff Completion Message.
6 After the action time, upon receiving a period of (N3m × 20) ms with sufficient signal quality
7 (e.g. good frames) on the physical channel corresponding to FPC_PRI_CHANs, the mobile
8 station shall resume incrementing TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs,
9 and DCCH_BAD_FRAMESs if applicable as specified in 2.6.4.1.1.
10 If the PERIODIC SEARCHs is equal to ‘1’, a periodic search is not already in progress, and
11 the Frequency Assignment after handoff is different from the Candidate Frequency
12 (CDMABANDs is not equal to CF_CDMABANDs or CDMACHs is not equal to CF_CDMACHs),
13 the mobile station shall do the following:
14 • The mobile station shall set ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs to
15 ‘000000’.
16 • The mobile station shall start a periodic search as described in 2.6.6.2.8.3.2.
17 2.6.6.2.8.2 Hard Handoff with Return on Failure

18 At the action time specified in the General Handoff Direction Message or Universal Handoff
19 Direction Message, the mobile station shall do the following:
20 • The mobile station shall stop processing the Forward Fundamental Code Channel,
21 the Forward Dedicated Control Channel, the Forward Supplemental Code Channels
22 (if any), and the Forward Supplemental Channels (if any).
23 • The mobile station shall stop transmitting on the Reverse Fundamental Code
24 Channel, on the Reverse Dedicated Control Channel, and on the Reverse
25 Supplemental Code Channels (if any), and on the Reverse Supplemental Channels (if
26 any).
27 • The mobile station shall disable the fade timer (see 2.6.4.1.8) and the handoff drop
28 timers corresponding to the Serving Frequency Active Set and Candidate Set (see
29 2.6.6.2.3), and shall suspend incrementing TOT_FRAMESs, BAD_FRAMESs,
30 DCCH_TOT_FRAMESs, and DCCH_BAD_FRAMESs if applicable (see 2.6.4.1.1).
31 • The mobile station shall lock the accumulation of valid level changes in the closed
32 loop mean output power and shall ignore received power control bits related to the
33 period that the transmitter is disabled (see 2.1.2.3.2 of TIA/EIA/IS-2000-2)[2]).
34 • If the Serving Frequency is different from the Target Frequency (SF_CDMACHs is not
35 equal to TF_CDMACHs or SF_CDMABANDs is not equal to TF_CDMABANDs), the
36 mobile station shall set CDMACHs to TF_CDMACHs and CDMABANDs to
37 TF_CDMABANDs, and shall tune to the Target Frequency.
38 The mobile station shall not change its time reference (see 2.1.5 of TIA/EIA/IS-2000-2)[2])
39 until the handoff is successfully completed (as described later in this section) or the mobile
40 station resumes using the Serving Frequency Active Set (as described in 2.6.6.2.8.2.1).
2-346
C.S0005-0-2 v1.0
1 The mobile station shall maintain a handoff timer. The mobile station shall set the
2 expiration time for the handoff timer to (0.08 × TF_WAIT_TIMEs) seconds and enable the
3 timer at the action time of the General Handoff Direction Message or Universal Handoff
4 Direction Message.

6 • If the Target Frequency is different from the Serving Frequency (TF_CDMABANDs is
7 not equal to SF_CDMABANDs, or TF_CDMACHs is not equal to SF_CDMACHs), the
8 mobile station shall measure the mean input power on the Target Frequency
9 (target_freq_pwr, in dBm / 1.23 MHz) and may use target_freq_pwr along with the
10 measurement of the average input power on the Serving Frequency
11 (avg_serving_freq_pwr, in dBm / 1.23 MHz) in the handoff procedure. The mobile
12 station may declare the handoff attempt to be unsuccessful if all of the following
13 conditions are true:
14 – DIFF_RX_PWR_THRESHs is not equal to ‘00000’,
15 – the mobile station has been measuring the received power on the Serving
16 Frequency for at least the last N12m frames, and
17 – (target_freq_pwr - avg_serving_freq_pwr) is less than (-30 + 2 ×

18 DIFF_RX_PWR_THRESHs) dB.
19 If the mobile station declares the handoff attempt to be unsuccessful, it shall restore
20 the configuration to what it was before the handoff attempt (see 2.6.6.2.5.1) and
21 send a Candidate Frequency Search Report Message as described in 2.6.6.2.8.2.1.
22 • The mobile station shall measure Ec/Io for each pilot in the Active Set using the
23 procedures specified in 2.6.6.2.2, if any of the following conditions is true:
24 – the Target Frequency is the same as the Serving Frequency (TF_CDMABANDs is
25 equal to SF_CDMABANDs, and TF_CDMACHs is equal to SF_CDMACHs),
26 – the mobile station does not use the power measurements in the handoff
27 procedure,
28 – DIFF_RX_PWR_THRESHs is equal to ‘00000’,
29 – the mobile station has not been measuring the received power on the Serving
30 Frequency for at least the last N12m frames, or
31 – (target_freq_pwr - avg_servng_freq_pwr) is not less than (-30 + 2 ×

32 DIFF_RX_PWR_THRESHs) dB.
33 If the mobile station measures Ec/Io for pilots in the Active Set, it shall compare the
34 sum of the measured Ec/Io for all pilots with the minimum total pilot Ec/Io
35 threshold (MIN_TOTAL_PILOT_EC_IOs).
36 – If MIN_TOTAL_PILOT_EC_IOs is not equal to ‘00000’, and (-20 × log10

37 (Ec/Io)total) is less than MIN_TOTAL_PILOT_EC_IOs, where (Ec/Io)total is the
38 sum of the measured Ec/Io for the pilots in the Active Set. The mobile station
39 shall declare the handoff attempt to be unsuccessful, and shall do the following:
2-347
C.S0005-0-2 v1.0
1 + If COMPLETE_SEARCHs is equal to ‘1’, and the Target Frequency is the same

2 as the Candidate Frequency (TF_CDMABANDs is equal to CF_CDMABANDs,
3 and TF_CDMACHs is equal to CF_CDMACHs) and is different from the
4 Serving Frequency (TF_CDMABANDs is not equal to SF_CDMABANDs, or
5 TF_CDMACHs is not equal to SF_CDMACHs), the mobile station shall
6 measure the strength of each pilot in its Candidate Frequency Search Set
7 using the procedures specified in 2.6.6.2.2.
8 + Otherwise, the mobile station shall end the search.
9 – The mobile station shall then restore its configuration to what it was before the
10 handoff attempt (see 2.6.6.2.5.1) and send a Candidate Frequency Search Report
11 Message as described in 2.6.6.2.8.2.1.
12 – If MIN_TOTAL_PILOT_EC_IOs is equal to ‘00000’, or ( - 20 × log10 (Ec/Io)total) is
13 not less than MIN_TOTAL_PILOT_EC_IOs, where (Ec/Io)total is the sum of the
14 measured Ec/Io for the pilots in the Active Set, the mobile station shall attempt
15 to demodulate the Forward Traffic Channel(s). If the Active Set contains more
16 than one pilot, the mobile station shall perform the actions specified in
17 2.6.6.2.7. If the Target Frequency is the same as the Candidate Frequency
18 (TF_CDMABANDs is equal to CF_CDMABANDs, and TF_CDMACHs is equal to
19 CF_CDMACHs), and is different for the Serving Frequency (TF_CDMABANDs is
20 not equal to SF_CDMABANDs, or TF_CDMACHs is not equal to SF_CDMACHs),
21 the mobile station shall measure the strength of each pilot in its Candidate
22 Frequency Search Set using the procedures specified in 2.6.6.2.2, while waiting
23 to receive a period of (N11m × 20) ms with sufficient signal quality (e.g. good
24 frames) on the physical channel corresponding to FPC_PRI_CHANs. The mobile
25 station shall wait for the first of the following events to occur:
26 + The handoff timer expires and the mobile station has not received a period of
27 (N11m × 20) ms with sufficient signal quality (e.g. good frames) on the
28 physical channel corresponding to FPC_PRI_CHANs. In this case, the mobile
29 station shall declare the handoff attempt to be unsuccessful, and do the
30 following:
31 ο If COMPLETE_SEARCHs is equal to ‘1’, and if the Target Frequency is the
32 same as the Candidate Frequency (TF_CDMABANDs is equal to
33 CF_CDMABANDs, and TF_CDMACHs is equal to CF_CDMACHs) and is
34 different from the Serving Frequency (TF_CDMABANDs is not equal to
35 SF_CDMABANDs, or TF_CDMACHs is not equal to SF_CDMACHs), and
36 the mobile station has not completed the search of all pilots in its
37 Candidate Frequency Search Set, then it shall complete the search, i.e.,
38 it shall obtain at least one measurement of the strength of each pilot in
39 its Candidate Frequency Search Set, using the search procedures
40 specified in 2.6.6.2.8.3.
41 ο Otherwise, the mobile station shall end the search.
2-348
C.S0005-0-2 v1.0
1 The mobile station shall then restore its configuration to what it was before
2 the handoff attempt (see 2.6.6.2.5.1) and send a Candidate Frequency Search
3 Report Message as described in 2.6.6.2.8.2.1.
4 + The mobile station receives a period of (N11m × 20) ms with sufficient signal
5 quality (e.g. good frames) on the physical channel corresponding to
6 FPC_PRI_CHANs. In this case, the mobile station shall declare the handoff
7 attempt to be successful, and do the following:
8 ο The mobile station shall disable the handoff timer.

9 ο If TF_RESET_L2s is equal to ‘1’, Layer 3 shall send a L2-
10 Supervision.Request primitive to Layer 2 to reset the acknowledgment
11 procedures as specified in 2.2.1.1 and 2.2.2.1 of TIA/EIA/IS-2000-4.[4].
12 ο If TF_RESET_FPCs is equal to ‘1’, the mobile station shall initialize the
13 Forward Traffic Channel power control counters as specified in
14 2.6.4.1.1.1.
15 ο If the Target Frequency is the same as the Candidate Frequency

16 (TF_CDMABANDs is equal to CF_CDMABANDs, and TF_CDMACHs is
17 equal to CF_CDMACHs) and is different from the Serving Frequency
18 (TF_CDMABANDs is not equal to SF_CDMABANDs, or TF_CDMACHs is
19 not equal to SF_CDMACHs), the mobile station shall do the following:
20 ◊ The mobile station shall replace its Neighbor Set with its Candidate
21 Frequency Neighbor Set, excluding the pilots in its Active Set. When
22 the mobile station adds a pilot from its Candidate Frequency
23 Neighbor Set to its Active Set, it shall maintain SEARCH_PRIORITYs,
24 SRCH_WIN_NGHBRs, and SRCH_OFFSET_NGHBRs associated with
25 the pilot.
26 ◊ The mobile station shall set PILOT_INCs to CF_PILOT_INCs,
27 SRCH_WIN_Ns to CF_SRCH_WIN_Ns, and SRCH_WIN_Rs to
28 CF_SRCH_WIN_Rs.
29 ◊ The mobile station shall set SEARCH_PRIORITY_INCLs to

30 CF_SEARCH_PRIORITY_INCLs, SRCH_OFFSET_INCLs to
31 CF_SRCH_OFFSET_INCLs, and SRCH_WIN_NGHBR_INCLs to
32 CF_SRCH_WIN_NGHBR_INCLs.
33 ο The mobile station shall re-enable its transmitter and shall re-enable the
34 fade timer (see 2.6.4.1.8) and reset it for T5m seconds. Then, the mobile
35 station shall transmit the Traffic Channel Preamble, as described in
36 2.1.3.6.2.3 of TIA/EIA/IS-2000-[2], followed by a Handoff Completion
37 Message.
2-349
C.S0005-0-2 v1.0
1 ο After starting the handoff timer, upon receiving the first period of (N3m ×
2 20) ms with sufficient signal quality (e.g. good frames) on the physical
3 channel corresponding to FPC_PRI_CHANs, the mobile station shall
4 resume incrementing TOT_FRAMESs, BAD_FRAMESs,
5 DCCH_TOT_FRAMESs, and DCCH_BAD_FRAMESs if applicable as
7 ο If the Target Frequency is same as the Candidate Frequency

8 (TF_CDMABANDs is equal to CF_CDMABANDs and TF_CDMACHs is
9 equal to CF_CDMACHs), then the mobile station shall set
11 ο If PERIODIC_SEARCHs is equal to ‘1’, the mobile station shall do the

12 following:
13 ◊ The mobile station shall set ALIGN_TIMING_USEDs to ‘0’ and
14 SEARCH_OFFSETs to ‘000000’.
15 ◊ The mobile station shall start a periodic search as described in

16 2.6.6.2.8.3.2.
17 ο The mobile station shall maintain its pilot sets using the procedures
18 described in 2.6.6.2.6.
19 2.6.6.2.8.2.1 Restoring the Configuration
20 If the mobile station declares a handoff attempt to be unsuccessful (see 2.6.6.2.8.2), it shall
22 • If the handoff timer is enabled, the mobile station shall disable it.
23 • The mobile station shall restore the following parameters:

24 – Message encryption mode: If SF_ENCRYPT_MODEs is equal to ‘0’, the mobile
25 station shall turn off message encryption; otherwise, it shall turn on message
26 encryption.
27 – Service configuration: The mobile station shall use the service configuration
28 stored in SF_SERVICE_CONFIGs to process Forward and Reverse Traffic
29 Channel frames.
30 – Protocol revision level (P_REVs = SF_P_REVs)
31 – Protocol revision level in use on the serving frequency (P_REV_IN_USEs =

32 SF_P_REV_IN_USEs)
33 – Service negotiation type (SERV_NEGs = SF_SERV_NEGs)
34 – Long code mask: If SF_PRIVATE_LCMs is equal to ‘1’, the mobile station shall
35 use the private long code mask; otherwise, it shall use the public long code
36 mask.
37 – Search window size for the Active Set and Candidate Set
38 (SRCH_WIN_As = SF_SRCH_WIN_As)
2-350
C.S0005-0-2 v1.0
1 – Search window size for the Neighbor Set

2 (SRCH_WIN_Ns = SF_SRCH_WIN_Ns)
3 – Search window size for the Remaining Set

4 (SRCH_WIN_Rs = SF_SRCH_WIN_Rs)
5 – Pilot detection threshold (T_ADDs = SF_T_ADDs)
6 – Pilot drop threshold (T_DROPs = SF_T_DROPs)
7 – Soft slope for the dynamic add and drop threshold (SOFT_SLOPEs =
8 SF_SOFT_SLOPEs)
9 – Intercept for the dynamic add threshold (ADD_INTERCEPTs =

10 SF_ADD_INTERCEPTs)
11 – Intercept for the dynamic drop threshold (DROP_INTERCEPTs =

12 SF_DROP_INTERCEPTs)
13 – Active Set versus Candidate Set comparison threshold (T_COMPs =

14 SF_T_COMPs)
15 – Drop timer value (T_TDROPs = SF_T_TDROPs)
16 – Frame offset (FRAME_OFFSETs = SF_FRAME_OFFSETs)
17 – Nominal power setting (NOM_PWRs = SF_NOM_PWRs)
18 – Extended nominal power setting (NOM_PWR_EXTs = SF_NOM_PWR_EXTs)
19 – Power control step (PWR_CNTL_STEPs = SF_PWR_CNTL_STEPs)
20 – CDMA band class (CDMABANDs = SF_CDMABANDs)
21 – Frequency assignment (CDMACHs = SF_CDMACHs)
22 – Active Set (For each pilot in the Serving Frequency Active Set: (PILOT_PN,
23 PWR_COMB_IND) )
24 – Code channel list (CODE_CHAN_LISTs = SF_CODE_CHAN_LISTs)
25 • The mobile station shall tune to the Serving Frequency and resume using the
26 Serving Frequency Active Set as follows:
27 – If the mobile station was processing the Forward Fundamental Channel prior to
28 tuning to the Candidate Frequency, the mobile station shall resume processing
29 the Forward Fundamental Channel. If the mobile station was transmitting on
30 the Reverse Fundamental Channel prior to tuning to the Candidate Frequency,
31 the mobile station shall resume transmitting on the Reverse Fundamental
32 Channel.
33 – If the mobile station was processing the Forward Dedicated Control Channel
34 prior to tuning to the Candidate Frequency, the mobile station shall resume
35 processing the Forward Dedicated Control Channel. If the mobile station was
36 transmitting on the Reverse Dedicated Control Channel prior to tuning to the
37 Candidate Frequency, the mobile station shall resume transmitting on the
38 Reverse Dedicated Control Channel.
2-351
C.S0005-0-2 v1.0
1 – The mobile station shall not resume transmitting on the Reverse Supplemental
2 Code Channels and Reverse Supplemental Channels (if any). The mobile station
3 shall not process on the Forward Supplemental Code Channels and Forward
4 Supplemental Channels (if any).
5 – When the mobile station resumes transmission on the Reverse Traffic Channel,
6 it shall use the following rules to re-enable its transmitter:
7 + If the interval between the time that the mobile station disables its
8 transmitter and the time that it resumes using the Serving Frequency Active
9 Set is equal to or greater than (N2m × 20) ms, then the mobile station shall
10 wait to receive a period of (N3m × 20) ms with sufficient signal quality (e.g.
11 good frames) on the physical channel corresponding to FPC_PRI_CHANs
12 before it re-enables its transmitter.
13 + Otherwise, the mobile station shall re-enable its transmitter no later than
14 N3m × 20 ms after the mobile station tunes to the Serving Frequency. The
15 mobile station should re-enable its transmitter earlier. After the mobile
16 station re-enables its transmitter, the mean output power shall be as
17 specified in 2.1.2.4.1 of TIA/EIA/IS-2000-[2] for a step change in input
18 power. If the mobile station re-enables its transmitter earlier than N3m × 20
19 ms after it tunes to the Serving Frequency, the initial mean output power
20 shall be as specified in 2.1.2.3.1 of TIA/EIA/IS-2000-[2], where the initial
21 mean input power estimate is either:
22 ο within 6 dB of the actual mean input power, or
23 ο equal to the mean input power before the mobile station tuned to the
24 Target Frequency.
25 • The mobile station shall enable the fade timer and the handoff drop timers
26 corresponding to the pilots in its Active Set and Candidate Set. The mobile station
27 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 • The mobile station shall send a Candidate Frequency Search Report Message within
30 T56m seconds of declaring the handoff attempt to be unsuccessful. The mobile
31 station shall report the contents of the Candidate Frequency Search Report Message
32 as follows:
33 – The mobile station shall report the two components of the Target Frequency in
34 the CDMA_FREQ and BAND_CLASS fields.
35 – The mobile station shall report the received power on the Target Frequency and
36 on the Serving Frequency in the CF_TOTAL_RX_PWR and SF_TOTAL_RX_PWR
37 fields, respectively.
38 – For each pilot in the Target Frequency Active Set that measures above
39 TF_T_ADDs, the mobile station shall report its phase and strength in the fields
40 PILOT_PN_PHASE and PILOT_STRENGTH, respectively.
2-352
C.S0005-0-2 v1.0
1 – If the Target Frequency is the same as the Candidate Frequency

2 (TF_CDMABANDs is equal to CF_CDMABANDs, and TF_CDMACHs is equal to
3 CF_CDMACHs), and is different from the Serving Frequency (TF_CDMABANDs is
4 not equal to SF_CDMABANDs or TF_CDMACHs is not equal to SF_CDMACHs),
5 the mobile station shall also report the strength of each pilot in the Candidate
6 Frequency Search Set that measures above CF_T_ADDs.
7 • If the Serving Frequency is the same as the Candidate Frequency (SF_CDMABANDs

8 is equal to CF_CDMABANDs and SF_CDMACHs is equal to CF_CDMACHs), then the
9 mobile station shall set PERIODIC_SEARCHs to ‘0’.
10 • If PERIODIC_SEARCHs is equal to ‘1’ and the Candidate Frequency Search Set is

11 not empty, the mobile station shall do the following:
12
13 – The mobile station shall set ALIGN_TIMING_USEDs to ‘0’ and SEARCH_OFFSETs

14 to ‘000000’.
15 – The mobile station shall carry out the periodic search procedures described in
16 2.6.6.2.8.3.2.
17 2.6.6.2.8.3 Search of Pilots on the CDMA Candidate Frequency

18 If SEARCH_MODEs is equal to ‘0000’, the mobile station shall do the following: If
19 PERIODIC_SEARCHs is equal to ‘0’, the mobile station shall search the Candidate
20 Frequency Search Set once, as described in 2.6.6.2.8.3.1; otherwise, the mobile station
21 shall search the Candidate Frequency Search Set periodically, as described in 2.6.6.2.8.3.2.
22 2.6.6.2.8.3.1 CDMA Candidate Frequency Single Search
23 The mobile station does a single search of the Candidate Frequency Search Set by
24 performing the following actions at the action time of the Candidate Frequency Search
25 Control Message or the Candidate Frequency Search Request Message that started the
26 search.
27 • If ALIGN_TIMING_USEDs is set to ‘0’, the mobile station shall measure the strength
28 of all pilots in the Candidate Frequency Search Set in one or more visits to the
29 Candidate Frequency, as described in 2.6.6.2.8.3.3.
31 of all pilots in the Candidate Frequency Search Set in one or more scheduled visits
32 (see below) to the Candidate Frequency, as described in 2.6.6.2.8.3.3.
33 The mobile station shall schedule visits to the Candidate Frequency only at
34 ((0.00125 × SEARCH_OFFSETs) + k × (SEARCH_TIME_RESOLUTIONs ×
35 inter_visit_time)) seconds after the action time of the Candidate Frequency Search
36 Request Message or the Candidate Frequency Search Control Message that started
37 the search, where
2-353
C.S0005-0-2 v1.0
1 k = an integer between 0 and max_num_visits, inclusive, where

2 max_num_visits is the value of MAX_NUM_VISITS field of the
3 last Candidate Frequency Search Response Message sent by the
4 mobile station,
5 and
6 inter_visit_time = the value of the INTER_VISIT_TIME field of the last Candidate
7 Frequency Search Response Message sent by the mobile station.
9 • The mobile station shall complete the measurements and send a Candidate
10 Frequency Search Report Message within ((0.00125 × SEARCH_OFFSETs) +
11 freshness_interval) seconds after the action time of the Candidate Frequency Search
12 Control Message, or the Candidate Frequency Search Request Message, where
13 freshness_interval is determined as follows:
14 – If the value of the TOTAL_OFF_TIME_FWD field or of the TOTAL_OFF_TIME_REV

15 field of the last Candidate Frequency Search Response Message sent by the
16 mobile station to the base station is greater than or equal to (T70m -
17 T71m)/SEARCH_TIME_RESOLUTIONs, then
18 freshness_interval = (max (fwd_time, rev_time) + T71m seconds),
19 where
20 fwd_time = SEARCH_TIME_RESOLUTIONs × (value of the
21 TOTAL_OFF_TIME_FWD field of
22 the last Candidate Frequency Search Response
23 Message sent by the mobile station),
24 and
25 rev_time = SEARCH_TIME_RESOLUTIONs × (value of the
26 TOTAL_OFF_TIME_REV field of the
27 last Candidate Frequency Search Response
28 Message sent by the mobile station).
29 – Otherwise,
30 freshness_interval = T70m seconds.
31 The mobile station shall set the fields of the Candidate Frequency Search Report
32 Message as follows:
33 – The mobile station shall report the two components of the Candidate Frequency
34 in the CDMA_FREQ and BAND_CLASS fields.
35 – The mobile station shall report the received power on the Candidate Frequency
36 and on the Serving Frequency in the CF_TOTAL_RX_PWR and
37 SF_TOTAL_RX_PWR fields, respectively.
2-354
C.S0005-0-2 v1.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 2.6.6.2.8.3.2 Candidate Frequency Periodic Search
5 When the mobile station performs a periodic search, it periodically searches the Candidate
6 Frequency Search Set and reports the results to the base station in the Candidate
7 Frequency Search Report Message, as described in this section. The mobile station may
8 measure all pilots in the Candidate Frequency Search Set in one visit to the Candidate
9 Frequency, or it may visit the Candidate Frequency several times in a search period, each
10 time measuring all or some of the pilots in the Candidate Frequency Search Set, as
11 described in 2.6.6.2.8.3.3.
12 If SF_TOTAL_EC_THRESHs is not equal to ‘11111’, while tuned to the Serving Frequency
13 (specified by CDMACHs and CDMABANDs), the mobile station shall measure the total
14 received power spectral density, in mW/1.23 MHz, on the Serving Frequency at least once
15 every 20 ms frame and shall maintain the average of the spectral density (spec_density)
16 over the last N12m frames.
17 (In the following, (Ec/Io)total is the total Ec/Io of the pilots in the Active Set, measured as
18 specified in 2.6.6.2.2, and total_ec is defined as (10 × log10 ((Ec/Io)total × spec_density)).)
19 The mobile station shall maintain a periodic search timer as follows:
20 • When the mobile station starts a periodic search, it shall set the periodic search
21 timer to the value in Table 2.6.6.2.8.3.2-1 corresponding to SEARCH_PERIODs and
22 shall enable the timer.
23 − If the periodic search is started by a Candidate Frequency Search Request
24 Message or a Candidate Frequency Search Control Message , then the mobile
25 station shall start the periodic search (0.00125 × SEARCH_OFFSETs) seconds
26 after the action time of the Candidate Frequency Search Request Message or the
27 Candidate Frequency Search Control Message that started the search.
28 – If the periodic search is started following successful or unsuccessful handoff

29 attempt, the mobile station shall start the periodic search:
30 + Upon sending the Handoff Completion Message, in the case that the handoff
31 was successful.
32 + Upon sending the Candidate Frequency Search Report Message, in the case that the
33 handoff was unsuccessful.• When the periodic search timer expires, the mobile
34 station shall reset the periodic search timer to the value in Table 2.6.6.2.8.3.2-1
35 corresponding to SEARCH_PERIODs and shall re-enable the timer.
36 • If ALIGN_TIMING_USEDs is set to ‘0’, SF_TOTAL_EC_THRESHs is not equal to

37 ‘11111’ and SF_TOTAL_EC_IO_THRESHs is equal to ‘11111’, the mobile station shall
38 perform the following actions once per frame:
39 – Disable the periodic search timer if total_ec is not less than
40 (-120 + 2 × SF_TOTAL_EC_THRESHs).
2-355
C.S0005-0-2 v1.0
1 – Reset the expiration time of the periodic search timer to the value in
2 Table 2.6.6.2.8.3.2-1 corresponding to SEARCH_PERIODs, and re-enable the
3 timer if the following conditions are true:
4 + the periodic search timer is disabled, and

5 + total_ec is less than (-120 + 2 × SF_TOTAL_EC_THRESHs).
6 • If ALIGN_TIMING_USEDs is set to ‘0’, SF_TOTAL_EC_THRESHs is equal to ‘11111’

7 and SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’, the mobile station shall
9 – Disable the periodic search timer if (-20 × log10 (Ec/Io)total) is not greater than
10 SF_TOTAL_EC_IO_THRESHs.

15 + (-20 × log10 (Ec/Io)total) is greater than SF_TOTAL_EC_IO_THRESHs.

17 ‘11111’ and SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’, the mobile station
18 shall perform the following actions once per frame:
19 – Disable the periodic search timer if the following conditions are true:
20 + total_ec is not less than (-120 + 2 × SF_TOTAL_EC_THRESHs), and
21 + (-20 × log10 (Ec/Io)total) is not greater than SF_TOTAL_EC_IO_THRESHs.

26 + total_ec is less than (-120 + 2 × SF_TOTAL_EC_THRESHs), or (-20 × log10
27 (Ec/Io)total) is greater than SF_TOTAL_EC_IO_THRESHs.
28 • The mobile station shall maintain the periodic search timer independent of the total
29 Ec and the total Ec/Io of the pilots in the Serving Frequency Active Set, if any of the
31 – ALIGN_TIMING_USEDs is set to ‘1, or
32 – SF_TOTAL_EC_THRESHs is equal to ‘11111’ and SF_TOTAL_EC_IO_THRESHs is

33 equal to ‘11111’.
34
2-356
C.S0005-0-2 v1.0
1 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
3 If the periodic search timer is enabled, the mobile station shall perform the following
4 actions before the timer expires:
6 of all pilots in the Candidate Frequency Search Set at least once in one or more
7 visits to the Candidate Frequency, as described in 2.6.6.2.8.3.3.
9 of all pilots in the Candidate Frequency Search Set in one or more scheduled visits
10 (see below) to the Candidate Frequency, as described in 2.6.6.2.8.3.3.
11 The mobile station shall schedule visits to the Candidate Frequency only at
17 max_num_visits is the value of NUM_VISITS field of the last
18 Candidate Frequency Search Response Message sent by the
19 mobile station,
20 and
23
24 – The mobile station shall abort a scheduled visit to the Candidate Frequency if at
25 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
2-357
C.S0005-0-2 v1.0
1 + SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’ and (-20 × log10

2 (Ec/Io)total) is not greater than SF_TOTAL_EC_IO_THRESHs.
3 – If the mobile station aborts a scheduled visit during a search period, it may
4 abort all remaining scheduled visits in that search period.
5 • The mobile station shall send a Candidate Frequency Search Report Message if
6 MIN_TOTAL_PILOT_EC_IOs is equal to ‘00000’ or if (- 20 × log10 (Ec/Io)total) is not
7 less than MIN_TOTAL_PILOT_EC_IOs, where (Ec/Io)total is the sum of Ec/Io for all
8 those pilots that measure above CF_T_ADDs in the current search period.
9 The mobile station shall report the contents of the Candidate Frequency Search
10 Report Message as follows:
11 – The mobile station shall report the two components of the Candidate Frequency
12 in the CDMA_FREQ and BAND_CLASS fields.
13 – The mobile station shall report the received power on the Candidate Frequency
14 and on the Serving Frequency in the CF_TOTAL_RX_PWR and
15 SF_TOTAL_RX_PWR fields, respectively.
16 – For each pilot in the Candidate Frequency Search Set that measures above
17 CF_T_ADDs, the mobile station shall report its phase and strength in the fields
19 • The mobile station shall ensure that the strength measurement for all pilots in the
20 Candidate Frequency Search Set were obtained within freshness_interval before the
21 Candidate Frequency Search Report Message is sent, where freshness_interval is
22 determined as follows:

25 mobile station to the base station is greater than or equal to
26 (T70m - T71m)/ SEARCH_TIME_RESOLUTIONs , then
27 freshness_interval = (max (fwd_time, rev_time) + T71m) seconds,
28 where
33 and
38 – Otherwise,
2-358
C.S0005-0-2 v1.0
1 2.6.6.2.8.3.3 Candidate Frequency Pilot Measurements
2 The mobile station measures the strength of all pilots in the Candidate Frequency Search
3 Set in one or more visits to the Candidate Frequency. The mobile station shall perform the
4 following actions each time it visits the Candidate Frequency to measure pilot strengths:
5 • If the mobile station is processing the Forward Fundamental Channel, the mobile
6 station shall stop processing the Forward Fundamental Code Channel. If the mobile
7 station is transmitting on the Reverse Fundamental Channel, the mobile station
8 shall stop transmitting on the Reverse Fundamental Channel.
9 • If the mobile station is processing the Forward Dedicated Control Channel, the
10 mobile station shall stop processing the Forward Dedicated Control Channel. If the
11 mobile station is transmitting on the Reverse Dedicated Control Channel, the mobile
12 station shall stop transmitting on the Reverse Dedicated Control Channel.
13 • The mobile station shall stop processing the Forward Supplemental Code Channels
14 and Forward Supplemental Channels (if any). The mobile station shall stop
15 transmitting on the Reverse Supplemental Code Channels and Reverse
18 timers corresponding to its current Active Set and Candidate Set (see 2.6.6.2.3), and
19 shall suspend incrementing TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs,
20 DCCH_BAD_FRAMESs, SCH_TOT_FRAMESs, and SCH_BAD_FRAMESs if applicable
21 (see 2.6.4.1.1).
24 period that the transmitter is disabled (see 2.1.2.3.1 of TIA/EIA/IS-2000-2)[2]).
25 • The mobile station shall store the following parameters from its current
26 configuration:
27 – CDMA band class (SF_CDMABANDs = CDMABANDs)
28 – Frequency assignment (SF_CDMACHs = CDMACHs)
29 – Pilot detection threshold (SF_T_ADDs = T_ADDs)
30 • The mobile station shall set the following parameters:

31 – CDMABANDs = CF_CDMABANDs
32 – CDMACHs = CF_CDMACHs
33 – T_ADDs = CF_T_ADDs
34 The mobile station shall tune to the Candidate Frequency.
35 • The mobile station shall not change its time reference (see 2.1.5 of TIA/EIA/IS-
36 .2000.[2]) until it resumes using the Serving Frequency Active Set, as described
37 below.
2-359
C.S0005-0-2 v1.0
1 • The mobile station shall measure the mean input power on the Candidate Frequency
2 (cand_freq_pwr, in dBm / 1.23 MHz), and may use cand_freq_pwr along with the
3 measurement of the mean input power on the Serving Frequency
4 (avg_serving_freq_pwr, in dBm / 1.23 MHz) in the search procedure as follows:
5 – If DIFF_RX_PWR_THRESHs is not equal to ‘00000’, and (cand_freq_pwr -
6 avg_serving_freq_pwr) is less than (-30 + 2 × DIFF_RX_PWR_THRESHs) dB, the
7 mobile station may terminate the search for pilots in the current visit to the
8 Candidate Frequency.
9 – If DIFF_RX_PWR_THRESHs is equal to ‘00000’, the mobile station does not use
10 the power measurements in the search procedure, or (cand_freq_pwr -
11 avg_serving_freq_pwr) is not less than (-30 + 2 × DIFF_RX_PWR_THRESHs) dB,
12 the mobile station shall measure Ec/Io for all or some of the pilots in its
13 Candidate Frequency Search Set, using the search procedures specified in
14 2.6.6.2.2.
15 • The mobile station shall restore the following parameters:

16 – Pilot detection threshold (T_ADDs = SF_T_ADDs)
17 – CDMA band class (CDMABANDs = SF_CDMABANDs)
18 – Frequency assignment (CDMACHs = SF_CDMACHs)
19 • The mobile station shall tune to the Serving Frequency and shall resume using the
26 Channel.
33 – If the Forward Supplemental Code Channels and Forward Supplemental

34 Channels assignment has not expired, the mobile station shall resume
35 processing the Forward Supplemental Code Channels and Forward
36 Supplemental Channels (if any). If the Reverse Supplemental Code Channel and
37 Reverse Supplemental Channels assignment has not expired, the mobile station
38 may resume transmitting on the Reverse Supplemental Code Channels and
39 Reverse Supplemental Channels (if any).
2-360
C.S0005-0-2 v1.0
11 specified in 2.1.2.4.1 for a step change in input power. If the mobile station
12 re-enables its transmitter earlier than N3m × 20 ms after it tunes to the
13 Serving Frequency, the initial mean output power shall be as specified in
14 2.1.2.3.1 of TIA/EIA/IS-2000-[2], where the initial mean input power
15 estimate is either:
24 2.6.6.2.8.3.4 Aborting CDMA Candidate Frequency Periodic Search
25 When the mobile station aborts a periodic search, it shall do the following:
26 • The mobile station shall cancel any remaining visits to the Candidate Frequency in
27 the current search period, and shall not send a Candidate Frequency Search Report
28 Message for the current search period.
29 • The mobile station shall disable the periodic search timer.
30 2.6.6.2.9 CDMA-to-Analog Handoff
31 The base station directs the mobile station to perform a CDMA-to-Analog handoff by
32 sending an Analog Handoff Direction Message. If the mobile station has narrow analog
33 capability, the base station may direct the handoff to a narrow analog channel.
34 If the mobile station supports analog operation in the requested band class, the mobile
35 station shall set DTXs to ‘00’ and store the following parameters from the Analog Handoff
38 • Voice mobile station attenuation code (VMACs = VMACr)
39 • Analog voice channel number (ANALOG_CHANs = ANALOG_CHANr)
2-361
C.S0005-0-2 v1.0
1 • SAT color code (SCCs = SCCr)
2 • Message encryption mode indicator (MEMs = MEMr)
3 • Analog voice channel type (AN_CHAN_TYPEs = AN_CHAN_TYPEr)
4 • Digital supervisory audio color code (DSCCs = DSCC_MSBr × 4 + SCCr)
5 If the mobile station does not support analog operation in the requested band class, the
6 mobile station shall discard the message and send a Mobile Station Reject Order with the
7 ORDQ field set to ‘00000110’ (capability not supported by the mobile station).
8 At the action time specified by the Analog Handoff Direction Message (see 2.6.4.1.5), the
9 mobile station shall disable its transmitter. The mobile station shall enable its transmitter
10 on the wide analog voice channel or optional narrow analog voice channel within T63m
11 seconds after the action time.
12 2.6.6.2.10 Search of Analog Frequencies

13 If SEARCH_MODEs is equal to ‘0001’, and the mobile station supports analog searching,
14 the mobile station shall do the following: If PERIODIC_SEARCHs is equal to ‘0’, the mobile
15 station shall search the Candidate Analog Frequency Search Set once, as described in
16 2.6.6.2.10.1; otherwise, the mobile station shall search the Candidate Frequency Analog
17 Search Set periodically, as described in 2.6.6.2.10.2.
18 2.6.6.2.10.1 Analog Frequencies Single Search
19 The mobile station does a single search of the Candidate Frequency Analog Search Set by
20 performing the following actions at the action time of the Candidate Frequency Search
21 Control Message or the Candidate Frequency Search Request Message that started the
22 search:
24 of all analog frequencies in the Candidate Frequency Analog Search Set in one or
25 more visits away from the Serving Frequency, as described in 2.6.6.2.10.3.
27 of analog frequencies in the Candidate Frequency Analog Search Set in one or more
28 scheduled visits (see below) away from the Serving Frequency, as described in
29 2.6.6.2.10.3.
30 The mobile station shall schedule visits away from the Serving Frequency only at
38 mobile station,
39 and
2-362
C.S0005-0-2 v1.0

3 • The mobile station shall complete the measurements and send a Candidate
4 Frequency Search Report Message within ((0.00125 × SEARCH_OFFSETs) +
5 freshness_interval) seconds after the action time of the Candidate Frequency Search
6 Control Message or the Candidate Frequency Search Request Message, where
7 freshness_interval is determined as follows:

10 mobile station to the base station is greater than or equal to (T70m - T71m)/
11 SEARCH_TIME_RESOLUTIONs , then
13 where
18 and
23 – Otherwise,
25 2.6.6.2.10.2 Analog Frequencies Periodic Search
26 When the mobile station performs a periodic search, it periodically searches the Candidate
27 Frequency Analog Search Set, and reports the results to the base station in the Candidate
28 Frequency Search Report Message, as described in this section. The mobile station may
29 measure all analog frequencies in the Candidate Frequency Analog Search Set in one visit
30 away from the Serving Frequency, or it may make multiple visits in a search period, each
31 time measuring all or some of the analog frequencies in the Candidate Frequency Analog
32 Search Set, as described in 2.6.6.2.10.3.
33 If SF_TOTAL_EC_THRESHs is not equal to ‘11111’, while tuned to the Serving Frequency
34 (specified by CDMACHs and CDMABANDs), the mobile station shall measure the total
35 received power spectral density, in mW/1.23 MHz, on the Serving Frequency at least once
36 every 20 ms frame and shall maintain the average of the spectral density (spec_density)
37 over the last N12m frames.
38 (In the following, (Ec/Io)total is the total Ec/Io of the pilots in the Active Set, measured as
39 specified in 2.6.6.2.2, and total_ec is defined as (10 × log10 ((Ec/Io)total × spec_density)).)
2-363
C.S0005-0-2 v1.0
1 The mobile station shall maintain a periodic search timer as follows:
2 • When the mobile station starts a periodic search, it shall set the periodic search
3 timer to the value in Table 2.6.6.2.8.3.2-1 corresponding to SEARCH_PERIODs and
4 shall enable the timer.
5 − If the periodic search is started by a Candidate Frequency Search Request
6 Message or a Candidate Frequency Search Control Message, then the mobile
7 station shall start the periodic search (0.00125 × SEARCH_OFFSETs) seconds
8 after the action time of the Candidate Frequency Search Request Message or the
9 Candidate Frequency Search Control Message that started the search.
10 – If the periodic search is started following successful or unsuccessful handoff

11 attempt, the mobile station shall start the periodic search:
12 + Upon sending the Handoff Completion Message, in the case that the handoff
13 was successful.
14 + Upon sending the Candidate Frequency Search Report Message, in the case
15 that the handoff was unsuccessful.
16 • When the periodic search timer expires, the mobile station shall reset the periodic
17 search timer to the value in Table 2.6.6.2.8.3.2-1 corresponding to
18 SEARCH_PERIODs and shall re-enable the timer.

20 ‘11111’ and SF_TOTAL_EC_IO_THRESHs is equal to ‘11111’, the mobile station shall
22 – Disable the periodic search timer if total_ec is not less than
23 (-120 + 2 × SF_TOTAL_EC_THRESHs).

28 + total_ec is less than (-120 + 2 × SF_TOTAL_EC_THRESHs).
29 • If ALIGN_TIMING_USEDs is set to ‘0’, SF_TOTAL_EC_THRESHs is equal to ‘11111’

30 and SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’, the mobile station shall
32 – Disable the periodic search timer if (-20 × log10 (Ec/Io)total) is not greater than
33 SF_TOTAL_EC_IO_THRESHs.

38 + (-20 × log10 (Ec/Io)total) is greater than SF_TOTAL_EC_IO_THRESHs.
2-364
C.S0005-0-2 v1.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
12 (-20 × log10 (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 If the periodic search timer is enabled, the mobile station shall perform the following
20 actions before the timer expires:
22 of all analog frequencies in the Candidate Frequency Analog Search Set at least once
23 in one or more visits away from the Serving Frequency, as described in 2.6.6.2.10.3.
25 of analog frequencies in the Candidate Frequency Analog Search Set in one or more
26 scheduled visits (see below) away from the Serving Frequency, as described in
27 2.6.6.2.10.3.
28 The mobile station shall schedule visits away from the Serving Frequency only at
36 mobile station,
37 and
2-365
C.S0005-0-2 v1.0
1 – The mobile station shall abort a scheduled visit away from the Serving
2 Frequency if at the scheduled time, one or both of the following conditions hold:
3 + SF_TOTAL_EC_THRESHs is not equal to ‘11111’ and total_ec is not less than
4 (-120 + 2 × SF_TOTAL_EC_THRESHs), or
5 + SF_TOTAL_EC_IO_THRESHs is not equal to ‘11111’ and (-20 × log10

6 (Ec/Io)total) is not greater than SF_TOTAL_EC_IO_THRESHs.
7 – If the mobile station aborts a scheduled visit during a search period, it may
8 abort all remaining scheduled visits in that search period.
9 • The mobile station shall set the fields of the Candidate Frequency Search Report
10 Message as follows: The mobile station shall report the received power on the
11 Serving Frequency in the TOTAL_RX_PWR_SF field. For each frequency in the
12 Candidate Frequency Analog Search Set, the mobile station shall report its
13 frequency and strength in the fields ANALOG_FREQ and SIGNAL_STRENGTH,
14 respectively.
15 • The mobile station shall ensure that the strength measurements for all analog
16 frequencies in the Candidate Frequency Analog Search Set were obtained within
17 freshness_interval before the Candidate Frequency Search Report Message is sent,
18 where freshness_interval is determined as follows:

21 mobile station to the base station is greater than or equal to (T70m - T71m)/
22 SEARCH_TIME_RESOLUTIONs ), then
24 where
29 and
34 – Otherwise,
36 2.6.6.2.10.3 Analog Frequency Measurements
37 The mobile station measures the strength of all analog frequencies in the Candidate
38 Frequency Analog Search Set in one or more visits away from the Serving Frequency. The
2-366
C.S0005-0-2 v1.0
1 mobile station shall perform the following actions during each visit away from the Serving
2 Frequency to measure analog frequency signal strengths:
3 • If the mobile station is processing the Forward Fundamental Channel, the mobile
4 station shall stop processing the Forward Fundamental Channel. If the mobile
5 station is transmitting on the Reverse Fundamental Channel, the mobile station
6 shall stop transmitting on Reverse Fundamental Channel.
7 • If the mobile station is processing the Forward Dedicated Control Channel, the
8 mobile station shall stop processing Forward Dedicated Control Channel. If the
9 mobile station is transmitting on the Reverse Dedicated Control Channel, the mobile
10 station shall stop transmitting on Reverse Dedicated Control Channel.
11 • The mobile station shall stop processing the Forward Supplemental Code Channels
12 and Forward Supplemental Channels (if any). The mobile station shall stop
13 transmitting on the Reverse Supplemental Code Channels and Reverse
16 timers corresponding to its current Active Set and Candidate Set (see 2.6.6.2.3), and
17 shall suspend incrementing TOT_FRAMESs, BAD_FRAMESs, DCCH_TOT_FRAMESs,
19 (see 2.6.4.1.1).
22 period that the transmitter is disabled (see TIA/EIA/IS-2000-2)[2]).
23 • The mobile station shall tune to one of the analog frequencies in the Candidate
24 Frequency Analog Search Set, and shall measure the mean input power on the
25 analog frequency.
26 • The mobile station may tune to other frequencies in the Candidate Frequency
27 Analog Search Set and make power measurements during this visit away from the
29 • The mobile station shall not change its time reference (see 2.1.5 of TIA/EIA/IS-
30 2000-2)[2]) until it resumes using the Serving Frequency Active Set, as described
31 below.
32 • The mobile station shall tune to the Serving Frequency and resume using the
39 Channel.
2-367
C.S0005-0-2 v1.0
7 – If the Forward Supplemental Code Channels or Forward Supplemental Channels

8 assignment has not expired, the mobile station shall resume processing the
9 Forward Supplemental Code Channels or Forward Supplemental Channels
10 respectively (if any).
11 – If the Reverse Supplemental Code Channel or Reverse Supplemental Channels

12 assignment has not expired, the mobile station may resume transmitting on the
13 Reverse Supplemental Code Channels or Reverse Supplemental Channels
14 respectively (if any).
27 specified in 2.1.2.4.1 of TIA/EIA/IS-2000-[2] for a step change in input
28 power. If the mobile station re-enables its transmitter earlier than N3m × 20
29 ms after it tunes to the Serving Frequency, the initial mean output power
30 shall be as specified in 2.1.2.3.1 of TIA/EIA/IS-2000-[2], where the initial
31 mean input power estimate is either:
40 2.6.6.2.10.4 Aborting Analog Frequencies Periodic Search
41 When the mobile station aborts a periodic search, it shall do the following:
2-368
C.S0005-0-2 v1.0
1 • The mobile station shall cancel any remaining visits away from the Serving
2 Frequency in the current search period and shall not send a Candidate Frequency
3 Search Report Message for the current search period.
4 • The mobile station shall disable the periodic search timer.
5 2.6.6.2.11 Processing of Reverse Supplemental Code Channels and Reverse Supplemental

6 Channels
7 If USE_T_ADD_ABORTs is set to ‘1’, and the strength of a Neighbor Set or Remaining Set
8 pilot is found to be above T_ADDs, then the mobile station shall terminate any active
9 transmission on Reverse Supplemental Code Channels or Reverse Supplemental Channels
10 at the end of the current 20 ms frame. The mobile station shall do the following:
11 • Any previously active Reverse Supplemental Code Channel or Reverse Supplemental

12 Channel assignment shall be considered implicitly terminated.
13 • If active transmission on Reverse Supplemental Code Channels is terminated, the

14 mobile station shall set NUM_REV_CODESs to ‘000’ and shall set IGNORE_SCAMs
15 to ‘1’.
16 • If active transmission on Reverse Supplemental Channels is terminated, the mobile

17 station shall set IGNORE_ESCAMs to ‘1’.
18 • The mobile station shall set SCRM_SEQ_NUMs to (SCRM_SEQ_NUMs + 1) mod 16.
19 • The mobile station shall transmit a Supplemental Channel Request Message with
20 USE_SCRM_SEQ_NUM set to ‘1’, SCRM_SEQ_NUM set to SCRM_SEQ_NUMs, and
21 SIZE_OF_REQ_BLOB set to ‘0000’.
22 2.6.6.2.12 Periodic Serving Frequency Pilot Report Procedure

23 While the mobile station is tuned to the Serving Frequency (specified by CDMACHs and
24 CDMABANDs), the mobile station shall measure the total received power spectral density, in
25 mW/1.23 MHz, on the Serving Frequency at least once every 20 ms frame. The mobile
26 station shall maintain the average value of the total received power spectral density,
27 spec_density, over the last N12m frames. The mobile station shall maintain the PPSMM
28 timer as follows:
29 • When the mobile station starts a Periodic Serving Frequency Pilot Report Procedure,
30 it shall set the PPSMM timer to PPSMM_PERIODs × 0.08 seconds and shall enable
31 the timer.
32 • When the PPSMM timer expires, the mobile station shall send a Periodic Pilot
33 Strength Measurement Message (2.6.6.2.5.2) to the base station, reset the PPSMM
34 timer to PPSMM_PERIODs × 0.08 seconds and shall re-enable the timer.
35 • When the mobile station receives an Extended Handoff Direction Message , a General
36 Handoff Direction Message or a Universal Handoff Direction Message directing the
37 mobile station to perform a hard handoff (see 2.6.6.2.5.1), it shall abort the Periodic
38 Serving Frequency Pilot Report Procedure and disable the PPSMM timer if it is
39 enabled.
2-369
C.S0005-0-2 v1.0
1 • If MIN_PILOT_PWR_THRESHs is not equal to ‘11111’ and

2 MIN_PILOT_EC_IO_THRESHs is equal to ‘11111’, the mobile station shall perform
3 the following actions once per frame:
4 – Disable the PPSMM timer if the received total energy per PN chip, Ec, of the
5 pilots in the Active Set is not less than (-120 + 2 × MIN_PILOT_PWR_THRESHs),
6 where the value of Ec is computed as 10 × log10 (PS × spec_density) and PS is
7 the total Ec/Io of the pilots in the Active Set measured as specified in 2.6.6.2.2.
8 – Reset the expiration time of the PPSMM timer to PPSMM_PERIODs × 0.08

9 seconds and re-enable the timer if the following conditions are true:
10 ο the PPSMM timer is disabled, and

11 ο the received total energy per PN chip, Ec, of the pilots in the Active Set is less
12 than (-120 + 2 × MIN_PILOT_PWR_THRESHs).
13 • If MIN_PILOT_PWR_THRESHs is equal to ‘11111’ and MIN_PILOT_EC_IO_THRESHs

14 is not equal to ‘11111’, the mobile station shall perform the following actions once
15 per frame:
16 – Disable the PPSMM timer if the total pilot strength of the pilots in the Active Set,
17 PS, satisfies the condition that (-20 × log10(PS)) is not greater than
18 MIN_PILOT_EC_IO_THRESHs.

22 ο the total pilot strength of the pilots in the Active Set, PS, satisfies the
23 condition that (-20 × log10(PS)) is greater than MIN_PILOT_EC_IO_THRESHs.
24 • If MIN_PILOT_PWR_THRESHs is not equal to ‘11111’ and

25 MIN_PILOT_EC_IO_THRESHs is not equal to ‘11111’, the mobile station shall
27 – Disable the PPSMM timer if the following conditions are true:

28 ο the received total energy per PN chip, Ec, of the pilots in the Active Set is not
29 less than (-120 + 2 × MIN_PILOT_PWR_THRESHs), and
30 ο the total pilot strength of the pilots in the Active Set, PS, satisfies the
31 condition that (-20 × log10(PS)) is not greater than
32 MIN_PILOT_EC_IO_THRESHs.


36 ο the received total energy per PN chip, Ec, of the pilots in the Active Set is less
37 than (-120 + 2 × MIN_PILOT_PWR_THRESHs), or the total pilot strength of
38 the pilots in the Active Set, PS, satisfies the condition that (-20 × log10(PS)) is
39 greater than MIN_PILOT_EC_IO_THRESHs.
2-370
C.S0005-0-2 v1.0
1 • If MIN_PILOT_PWR_THRESHs is equal to ‘11111’ and MIN_PILOT_EC_IO_THRESHs

2 is equal to ‘11111’, the mobile station shall maintain the PPSMM timer independent
3 of the received power and the total Ec/Io of the pilots.
4 2.6.6.3 Examples
5 The following examples illustrate typical message exchanges between the mobile station and
6 the base station during handoff. Refer to Annex B for examples of call processing during
7 handoff.
8 Figure 2.6.6.3-1 shows an example of the messages exchanged between the mobile station
9 and the base station during a typical handoff process if P_REV_IN_USEs is less than or
10 equal to three or SOFT_SLOPEs is equal to ‘000000’.
11 Figure 2.6.6.3-2 shows an example of the messages exchanged between the mobile station
12 and the base station during a typical handoff process if P_REV_IN_USEs is greater than
13 three and SOFT_SLOPEs is not equal to ‘000000’.
14 Figure 2.6.6.3-3 illustrates the messaging triggered by a pilot of the Candidate Set as its
15 strength gradually rises above the strength of each pilot of the Active Set if P_REV_IN_USEs
16 is less than or equal to three, or SOFT_SLOPEs is equal to ‘000000’. Note that the mobile
17 station reports that a Candidate Set pilot is stronger than an Active Set pilot only if the
18 difference between their respective strengths is at least T_COMP × 0.5 dB.
19 Figure 2.6.6.3-4 illustrates the messaging triggered by a pilot of the Candidate Set as its
20 strength gradually rises above the strength of each pilot of the Active Set if P_REV_IN_USEs
21 is greater than three and SOFT_SLOPEs is not equal to ‘000000’. Note that the mobile
22 station reports that a Candidate Set pilot is stronger than an Active Set pilot only if the
23 difference between their respective strengths is at least T_COMP × 0.5 dB and Pilot P0
24 strength exceeds [(SOFT_SLOPE/8) × 10 × log10(PS1 + PS2) + ADD_INTERCEPT/2].
25
2-371
C.S0005-0-2 v1.0
Pilot
Strength
T_ADD
T_DROP
Time
(1) (2)(3) (4) (5) (6) (7)
Neighbor Candidate Active Neighbor
Set Set Set Set
1
2
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’
18
2-372
C.S0005-0-2 v1.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’
19
2-373
C.S0005-0-2 v1.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’
10
2-374
C.S0005-0-2 v1.0
Pilot
Strength Pilot P0
10 log 10(PS 1 + 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’
16
2-375
C.S0005-0-2 v1.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, Quick Paging Channel
13 Number, and Paging Slot Number, the hash value is computed as follows:17
14 R = N × ((40503 × (L ⊕ H ⊕ DECORR)) mod 216 ) / 216.
15 For determining a mobile station’s assigned paging indicator bit positions, the hash value is
16 computed as follows:
17 R1 = N × ((40503 × (L ⊕ H ⊕ DECORR1)) mod 216)/216,
18 and
19 R2 = ( (1 - (2 ×R1)/(N+4) ) × (N+4)/2 + (2 ×R1)/(N+4) × ((N+4)/2 – 4)) × ((40503 × (L
20 ⊕ H ⊕ DECORR2)) mod 216)/216 + N + 4 + (2 ×R1)/(N+4) × ((N+4)/2) for Quick
21 Paging Channel indicator rate of 4800 bps, or
22 R2 = ( (1 - (2 ×R1)/(N+8) ) × (N+8)/2 + (2 ×R1)/(N+8) × ((N+8)/2 – 8) ) × ((40503 ×
23
16 16
(L ⊕ H ⊕ DECORR2)) mod 2 )/2  + N + 8 + (2 ×R1)/(N+8) × ((N+8)/2) for Quick
24 Paging Channel indicator rate of 9600bps.
25 The mobile station shall choose the range N and the modifiers DECORR, DECORR1, and
26 DECORR2 according to the application as shown in Table 2.6.7.1-1. In the table,
27 HASH_KEY [0...11] denotes the 12 least significant bits of HASH_KEY.
28
17 This formula is adapted from Knuth, Donald N., The Art of Computer Programming, 2 volumes,
(Reading, MA, Addison-Wesley, 1998).
2-376
C.S0005-0-2 v1.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 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 (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 mod R1 and
Positions bps) 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.
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.18
18 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
W., “Random Number Generators: Good Ones are Hard to Find,” Communications of the ACM, vol. 31,
no. 10, October 1988, pp. 1192-1201.
2-377
C.S0005-0-2 v1.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_LISTsas 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.
33 • When the mobile station processes the General Handoff Direction Message, the
34 mobile station shall update the CODE_CHAN_LISTs to contain the Forward
35 Fundamental Code Channel associated with each pilot included in the General
36 Handoff Direction Message. The first code channel occurrence associated with each
37 pilot included in the General Handoff Direction Message corresponds to the Forward
38 Fundamental Code Channel. The mobile station shall do the following:
39 − If FOR_SUP_CONFIGr is included and FOR_SUP_CONFIGr is equal to ‘10’ or ‘11’,
2-378
C.S0005-0-2 v1.0
1 + For each pilot listed in the General Handoff Direction Message, the mobile
2 station shall set the Forward Supplemental Code Channels (associated with
3 the pilot) in the CODE_CHAN_LISTs to the Forward Supplemental Code
4 Channels specified in the General Handoff Direction Message.
5 + The mobile station shall delete all information in the CODE_CHAN_LISTs
6 associated with a pilot that is not included in the General Handoff Direction
7 Message.
8 − If FOR_SUP_CONFIGr is equal to ‘00’ or ‘01’ or if FOR_SUP_CONFIGr is not
9 included in the General Handoff Direction Message, the mobile station shall not
10 update Supplemental Code Channels associated with the pilots included in the
11 General Handoff Direction Message. The mobile station shall perform the
13 + For each pilot listed in the General Handoff Direction Message which does not
14 have a corresponding code channel in the CODE_CHAN_LISTs, the mobile
15 station shall add the code channel, CODE_CHAN, of that pilot to the
16 CODE_CHAN_LISTs, as the Forward Fundamental Code Channel for the
17 pilot.
18 + The mobile station shall delete all information in the CODE_CHAN_LISTs
19 associated with a pilot that is not included in the General Handoff Direction
20 Message.
21 • When the mobile station processes the Supplemental Channel Assignment Message it
22 shall follow the following rules:
23 − If FOR_SUP_CONFIGr is equal to ‘10’ or ‘11’, the mobile station shall update the
24 Forward Supplemental Code Channels for each pilot in the Active Set.
25 − If the pilot is not listed in the Supplemental Channel Assignment Message, the
26 mobile station shall delete all occurrences of Forward Supplemental Code
27 Channels associated with the pilot from the Code Channel List.
28 − If a pilot is listed in the Supplemental Channel Assignment Message, then the
29 mobile station shall set the Forward Supplemental Code Channels (associated
30 with the pilot) in the CODE_CHAN_LISTs to the Forward Supplemental Code
31 Channels specified in the Supplemental Channel Assignment Message.
32 − If FOR_SUP_CONFIGr is equal to ‘00’ or ‘01’, the mobile station shall not update
33 Supplemental Code Channels associated with the pilots included in the
34 Supplemental Channel Assignment Message.
35 2.6.9 CDMA Tiered Services
36 This section presents an overview and mobile station requirements for the support of CDMA
37 Tiered services while the mobile station is in the Mobile Station Idle State and in the Mobile
2-379
C.S0005-0-2 v1.0
1 2.6.9.1 Overview
2 2.6.9.1.1 Definition
3 The mobile station may support Tiered Services based upon User Zones. Tiered Services
4 provide the user custom services and special features based upon the mobile station
5 location. Tiered Services also provides private network support. Important to the operation
6 of CDMA Tiered Services is the concept of User Zones. It is via User Zones by which the
7 base station offers custom services based upon the mobile station location.
8 User Zones are associated with a set of features and services, plus a geographic area in
9 which the User Zone features/services are made available to the customers that have
10 subscribed to that User Zone. The boundary of the User Zone Geographic area may be
11 established based on the coverage area of a public or private base station or it may be
12 established independent of RF topology.
13 User Zones may be supported by the public system on the same frequency as the serving
14 base station, or they may be supported on a private system operating on a different
15 frequency.
16 2.6.9.1.2 Types of User Zones
17 User Zones may be of two basic types:

18 • Broadcast User Zones: Broadcast User Zones are identified to the mobile station using
19 the Paging Channel. In this case, the base station broadcasts on the Paging Channel
20 messages identifying the User Zones that fall within the coverage area of the
21 particular cell/sector. Mobile stations, as part of their monitoring of the Paging
22 Channel, will identify the presence of a particular User Zone.
23 • Mobile Specific User Zones: Mobile Specific User Zones are not broadcast by the base
24 station. The mobile station may use other overhead message parameters and
25 compare them with internally stored User Zone parameters to identify the presence of
26 a particular User Zone. These parameters may include: SID, NID, BASE_ID,
27 BASE_LAT, and BASE_LONG.
28 Broadcast User Zones allow for permanent as well as temporary subscription. Temporary
29 subscription provides User Zone features and capabilities to users who are not subscribed
30 to the User Zone. In this case, a mobile station, upon entering a new coverage area, may
31 detect the presence of a User Zone that it presently does not subscribe to, but one that
32 supports temporary subscription. The mobile station then queries the network to obtain
33 the User Zone parameters. Once these parameters are received, the mobile station offers to
34 the user via the mobile station user interface, the option of subscribing to the particular
35 User Zone.
36 Some User Zones may require active registration (Active User Zones) upon the mobile
37 station’s entry to immediately trigger a change in a feature(s). For others, the implicit
38 registration at call setup is sufficient (Passive User Zones). Active User Zones are used
39 where inbound features change as a result of being in the User Zone. During the Mobile
40 Station Idle State, a mobile stations needs to register to update the User Zone ID whenever
41 the User Zone that the mobile station is entering and/or leaving is of the Active type.
2-380
C.S0005-0-2 v1.0
1 A mobile station that supports User Zone services may store a list of User Zones, where
2 each User Zone is identified by a User Zone ID (UZID). Associated with each stored User
3 Zone, the mobile station may also store a number of determinant parameters used for
4 identifying User Zones.
6 If the mobile station supports User Zone services, it shall maintain and update UZIDs
7 according the following rule:
8 If the mobile station selects a User Zone supported by the base station, the mobile station
9 shall set UZIDs to the User Zone Identifier associated with the User Zone; otherwise, the
10 mobile station shall set UZIDs to ‘0000000000000000’. The precise process for determining
11 how to select a User Zone that is supported by the base station is left to the mobile station
12 manufacturer.
13 If the mobile station does not support User Zone services, the mobile station shall set
14 UZIDs to ‘0000000000000000’.
15 The mobile station may search pilots of private neighbor base stations on other frequencies
16 and band classes as identified in the Private Neighbor List Message. Search performance
17 criteria are defined in TIA/EIA/IS-98C[14].
18 2.6.9.2.1 User Zone Operation in the Mobile Station Idle State:
19 When a mobile station performs an idle handoff, it selects User Zones based on internally
20 stored parameters and information broadcast on the Paging Channel as described in
21 2.6.9.1.
22 After the mobile station performs idle handoff, if the mobile station determines that a
23 change from one Broadcast User Zone to another Broadcast User Zone is required, the
24 mobile station shall not update UZIDs, UZ_EXIT_IN_USEs and shall not perform User Zone
25 registration until the pilot strength of the currently serving base station exceeds that of the
26 base station corresponding to the old User Zone by the value of UZ_EXIT_IN_USEs.
27 If the mobile station determines that it needs to change User Zone, and if the difference
28 between the pilot strengths exceeds UZ_EXIT_IN_USEs, then the mobile station shall do the
29 following:
30 • Perform User Zone registration.

31 • Update UZIDs.
32 • Set UZ_EXIT_IN_USEs to UZ_EXIT_RCVDs.
33 The mobile station may also implement other means to avoid the premature exiting of a
34 User Zone due to rapid changes in signal strength. The exact implementation of such
35 techniques is left to mobile station implementation.
36 If the mobile station is in the Mobile Station Idle State and it receives a User Zone Reject
37 Message the mobile station shall perform the following:
38 • Set REJECT_ACTION_INDIs to REJECT_ACTION_INDIr.
2-381
C.S0005-0-2 v1.0
1 • If UZID_ASSIGN_INCLr = ‘0’, the mobile station shall set UZIDs to

2 ‘0000000000000000’, otherwise; the mobile station shall set UZIDs to
3 ASSIGN_UZIDr.
4 If the mobile station is in the Mobile Station Idle State and it selects an active User Zone,
5 then the mobile station shall perform User Zone registration (see 2.6.5.1.10) by entering the
6 System Access State with a registration indication.
7 The mobile station should provide the user with a User Zone indication corresponding to
8 the User Zone in service each time UZIDs is updated.
9 2.6.9.2.2 User Zone Operation in the Mobile Station Control on the Traffic Channel State
10 If the mobile station is in the Conversation Substate of the Mobile Station Control on the
11 Traffic Channel State and if it determines that the User Zone has changed, it shall update
12 UZIDs and send a User Zone Update Request Message to the base station.
13 If the mobile station is in the Waiting for Order Substate, Waiting for Mobile Station Answer
14 Substate, Conversation Substate, or Release Substate of the Mobile Station Control on the
15 Traffic Channel State and it receives a User Zone Update Message, then the mobile station
16 shall update UZIDs and set it equal to UZIDr.
17 If the mobile station is in the Waiting for Order Substate, Waiting for Mobile Station Answer
18 Substate, Conversation Substate, or Release Substate of the Mobile Station Control on the
19 Traffic Channel State and it receives a User Zone Reject Message, then the mobile station
21 • Set REJECT_ACTION_INDIs to REJECT_ACTION_ INDIr.
22 • If UZID_ASSIGN_INCLr = 0, the mobile station shall set UZIDs to ‘0’, otherwise; the
23 mobile station shall set UZIDs to ASSIGN_UZIDr.
24 The mobile station should provide the user with a User Zone indication corresponding to
25 the User Zone in service each time UZIDs is updated.
26
2-382
C.S0005-0-2 v1.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 Some bits in the PDUs are marked as RESERVED. These bits allow extension of the PDUs
5 for future features and capabilities. The mobile station sets all reserved bits to ‘0’.
6
2-385
C.S0005-0-2 v1.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
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.
14
2-386
C.S0005-0-2 v1.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
4
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).
11
12 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)
All other REG_TYPE values are reserved.
13
2-387
C.S0005-0-2 v1.0
1 SLOT_CYCLE_INDEX – Slot cycle index.

2 If the mobile station is configured for slotted mode operation,
3 the mobile station shall set this field to the preferred slot cycle
4 index, SLOT_CYCLE_INDEXp (see 2.6.2.1.1). Otherwise, the
5 mobile station shall set this field to ‘000’.
6 MOB_P_REV – Protocol revision of the mobile station.
7 The mobile station shall set this field to ‘00000110’.
8 SCM – Station class mark.
9 The mobile station shall set this field to its station class mark.
10 See 2.3.3.
11 MOB_TERM – Mobile terminated calls accepted indicator.
12 If the mobile station is configured to accept mobile terminated
13 calls while operating with the current roaming status (see
14 2.6.5.3), the mobile station shall set this bit to ‘1’. Otherwise,
15 the mobile station shall set this bit to ‘0’.
16 RETURN_CAUSE – Reason of the mobile station registration or access.
17 The mobile station shall set this field to the RETURN_CAUSE
18 value shown in Table 2.7.1.3.2.1-2 corresponding to the service
19 redirection failure condition (see 2.6.1.1).
20
21 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.
22
23 QPCH_SUPPORTED – Quick Paging Channel supported indicator.

24 If P_REV_IN_USEs is less than six, the mobile station shall omit
25 this field; otherwise, the mobile station shall include this field and
26 set it as follows.
2-388
C.S0005-0-2 v1.0
1 If the mobile station supports the Quick Paging Channel, the

2 mobile station shall set this field to ‘1’; otherwise, the mobile
3 station shall set this field to ‘0’.
4 ENHANCED_RC – Enhanced radio configuration supported indicator.
8 If the mobile station supports any radio configuration in the Radio
9 Configuration Class 2 (see 1.1.1), the mobile station shall set this
10 field to ‘1’; otherwise, the mobile station shall set this field to ‘0’.
11 UZID_INCL – User Zone Identifier included indicator.
15 If the message is to contain the User Zone Identifier, the mobile
16 station shall set this field to ‘1’; otherwise, the mobile station
17 shall set this field to ‘0’.
18 UZID – User Zone Identifier.
19 If the UZID_INCL is included in the message and is set to ‘1’, the
20 mobile station shall include this field and set it to UZIDs;
21 otherwise, the mobile station shall omit this field.
22
2-389
C.S0005-0-2 v1.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
14
2-390
C.S0005-0-2 v1.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 TSB58-A. If the mobile station
11 sets this field equal to ‘111110’, it shall set the first two
12 CHARi 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-391
C.S0005-0-2 v1.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 TSB58-A.
20
Field Length (bits)
EXTENDED_BURST_TYPE 16
(first two CHARi fields)
21
2-392
C.S0005-0-2 v1.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)
4
2-393
C.S0005-0-2 v1.0
DRS 0 or 1
UZID_INCL 0 or 1
UZID 0 or 16
CH_IND 0 or 2
SR_ID 0 or 3
OTD_SUPPORTED 0 or 1
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

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
14 The mobile station shall set this field to ‘ ‘00000110’.
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.
19 The mobile station shall set this field to the value shown in
20 Table 2.7.1.3.2.4-1 corresponding to its current configuration.
21
2-394
C.S0005-0-2 v1.0
1 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
3 SPECIAL_SERVICE – Special service option indicator.

4 To request a special service option, the mobile station shall set
5 this field to ‘1’. To request the default service option (Service
6 Option 1), the mobile station shall set this field to ‘0’.
7 SERVICE_OPTION – Requested service option for this origination.
8 If the SPECIAL_SERVICE field is set to ‘1’, the mobile station
9 shall set this field to the value specified in TSB58-A,
10 corresponding to the requested service option. If the
11 SPECIAL_SERVICE field is set to ‘0’, the mobile station shall
12 omit this field.
13 PM – Privacy mode indicator.
14 To request voice privacy, the mobile station shall set this field
15 to ‘1’; otherwise, the mobile station shall set this field to ‘0’.
16 DIGIT_MODE – Digit mode indicator.
17 This field indicates whether the dialed digits are 4-bit DTMF
18 codes or 8-bit ASCII codes using a specified numbering plan.
19 To originate the call using the binary representation of DTMF
20 digits, the mobile station shall set this field to ‘0’. To originate
21 the call using ASCII characters, the mobile station shall set
22 this field to ‘1’.
23 NUMBER_TYPE – Type of number.
24 If the DIGIT_MODE field is set to ‘1’, the mobile station shall
25 set this field to the NUMBER_TYPE value shown in Table
26 2.7.1.3.2.4-2 corresponding to the type of the number as
27 defined in ANSI T1.607-1990, Section 4.5.9[8]. If the
28 DIGIT_MODE field is set to ‘0’, the mobile station shall omit
29 this field.
30
2-395
C.S0005-0-2 v1.0
1 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
3 NUMBER_PLAN – Numbering plan.

5 set this field to the NUMBER_PLAN value shown in Table
6 2.7.1.3.2.4-3 corresponding to the requested numbering plan
7 as defined in ANSI T1.607-1990, Section 4.5.9[8]. If the
8 DIGIT_MODE field is set to ‘0’, the mobile station shall omit
9 this field.
10
11 Table 2.7.1.3.2.4-3. Numbering Plan Identification
NUMBER_PLAN
Description
(binary)
Unknown 0000
ISDN/Telephony numbering plan 0001
(CCITT E.164 and CCITT E.163)
Data numbering plan (CCITT X.121) 0011
Telex numbering plan (CCITT F.69) 0100
Private numbering plan 1001
Reserved for extension 1111
All other NUMBER_PLAN codes are reserved.
12
13 MORE_FIELDS – More dialed digits indicator.

14 This field indicates whether additional dialed digits will be
15 sent in a later Origination Continuation Message.
16 If all dialed digits will fit into this message, the mobile station
17 shall set this field to ‘0’. If not, the mobile station shall set
2-396
C.S0005-0-2 v1.0
1 NUM_FIELDS – Number of dialed digits in this message.

2 The mobile station shall set this field to the number of dialed
3 digits included in this message.
4 CHARi – A dialed digit or character.
6 this field. If the DIGIT_MODE field is set to ‘0’, the mobile
7 station shall set each occurrence of this field to the code value
8 shown in Table 2.7.1.3.2.4-4 corresponding to the dialed digit.
10 set each occurrence of this field to the ASCII representation
11 corresponding to the dialed digit, as specified in ANSI
12 X3.4[12], with the most significant bit set to ‘0’.
13
14 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.
15
16 NAR_AN_CAP – Narrow analog capability.

17 If the mobile station is capable of narrow analog operation, the
18 mobile station shall set this bit to ‘1’; otherwise, the mobile
19 station shall set this bit to ‘0’.
20 PACA_REORIG – PACA re-origination.
21 If this is a user directed origination, the mobile station shall
22 set this field to ‘0’. If this is a PACA re-origination, the mobile
24 RETURN_CAUSE – Reason for the mobile station registration or access.
25 The mobile station shall set this field to the RETURN_CAUSE
26 value shown in Table 2.7.1.3.2.1-2 corresponding to the
27 service redirection failure condition (see 2.6.1.1).
28 MORE_RECORDS – More records indicator.
29 This field indicates whether information records will be sent in
30 a later Origination Continuation Message. If information
31 records will be sent, the mobile station shall set this field to
32 ‘1’; otherwise, the mobile station shall set this field to ‘0’.
2-397
C.S0005-0-2 v1.0
1 ENCRYPTION- – Encryption algorithms supported by the mobile station.

2 _SUPPORTED If AUTH_MODE is equal to ‘00’, the mobile station shall omit
3 the ENCRYPTION_SUPPORTED field; otherwise, the mobile
4 station shall set this field as specified in Table 2.7.1.3.2.4-5.
6 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
8 PACA_SUPPORTED – CDMA PACA support indication.

9 This field identifies the mobile station’s support for PACA in
10 CDMA mode. The mobile station shall set this field to ‘1’.
11
12 NUM_ALT_SO – Number of alternative service options.

14 alternative service options it supports other than the one
15 specified in the SERVICE_OPTION field. The mobile station
16 shall set this field to a value less than or equal to
17 MAX_NUM_ALT_SOs.
18 ALT_SO – Alternative service option.
19 The mobile station shall include NUM_ALT_SO occurrences of
20 this field. The mobile station shall set this field to the value
21 specified in TSB58-A, corresponding to the alternative service
22 option supported by the mobile station.
23 DRS – Data Ready to Send.
24 If P_REV_IN_USEs is less than six, the mobile station shall
25 omit this field; otherwise, the mobile station shall include this
26 field and set it as follows.
27 If there is data to send, the mobile station shall set this field
33 If the message is to contain the User Zone Identifier, the
2-398
C.S0005-0-2 v1.0

2 If the UZID_INCL field is included in the message and is set to
3 ‘1’, the mobile station shall include this field and set it to
4 UZIDs; otherwise, the mobile station shall omit this field.
5 CH_IND – Channel indicator.

8 field and set it, as shown in Table 2.7.1.3.2.4-6, to request
9 physical resources.
10 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
11
12 SR_ID – Service reference identifier.

15 field and set it as follows:
16 If the service instance provides a service reference identifier,
17 the mobile station shall set this field to the service reference
18 identifier specified by the service instance. If the service
19 instance does not provide a service reference identifier, the
20 mobile station shall set this field to the smallest unused
21 service reference identifier value between 1 and 6 (inclusive).
22 OTD_SUPPORTED – Orthogonal Transmit Diversity supported indicator.
26 If the mobile station supports orthogonal transmit diversity, it
27 shall set this field to ‘1’; otherwise, the mobile station shall set
30 If P_REV_IN_USE is less than six, the mobile station shall omit
2-399
C.S0005-0-2 v1.0

11 FOR_RC_PREF – Forward Radio Configuration preference.
14 field and set this field as follows.
15 The mobile station shall set this field to its preferred Radio
16 Configuration for the Forward Traffic Channel.
17 REV_RC_PREF – Reverse FCH Radio Configuration Preference.
22 Configuration for the Reverse Traffic Channel.
23 FCH_SUPPORTED – Fundamental Channel supported indicator.
27 The mobile station shall set this field to ‘1’ if the mobile
28 station supports Fundamental Channel; otherwise, the mobile
30 FCH Capability
31 Type-specific fields – Fundamental Channel capability information.
32 If the FCH_SUPPORTED field is set to ‘1’, the mobile station
33 shall include this field and set it as defined in 2.7.4.27.1;
35 DCCH_SUPPORTED – Dedicated Control Channel supported indicator.
37 omit this field; otherwise the mobile station shall include this
40 station supports Dedicated Control Channel; otherwise, the
42 DCCH Capability
43 Type specific fields – Dedicated Control Channel capability information.
2-400
C.S0005-0-2 v1.0
1 If the DCCH_SUPPORTED field is set to ‘1’, the mobile station

2 shall include this field and set it as defined in 2.7.4.27.2;
4 RESERVED – The reserved bit.
7 set it to ‘0’.
8 REV_FCH-
9 _GATING_REQ – Reverse Fundamental gating mode request indicator.
10 If P_REV_IN_USE is less than six, the mobile station shall
13 If the mobile station requests to turn on the reverse
14 Fundamental Traffic Channel gating mode in Radio
15 Configurations 3, 4, 5, and 6, the mobile station shall set this
16 field to ‘1’; otherwise, the mobile station shall set this field to
17 ‘0’.
18
19
2-401
C.S0005-0-2 v1.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
NUM_ALT_SO occurrences of the following field:
ALT_SO 16
UZID_INCL 0 or 1
UZID 0 or 16
CH_IND 0 or 2
OTD_SUPPORTED 0 or 1
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
2-402
C.S0005-0-2 v1.0

3 2.6.5.3), the mobile station shall set this bit to ‘1’. Otherwise,
8 index, SLOT_CYCLE_INDEXp (see 2.6.2.1.1). Otherwise, the
11 The mobile station shall set this field to ‘‘00000110’.
13 The mobile station shall set this field to the station class mark
14 of the mobile station. See 2.3.3.
15 REQUEST_MODE – Requested mode code. The mobile station shall set this field
16 to the value shown in Table 2.7.1.3.2.4-1 corresponding to its
17 current configuration.
18 SERVICE_OPTION – Service option.
19 If the mobile station accepts the service option specified by the
20 page record of the General Page Message, it shall set this field
21 as follows:
22 • If the page record to which the mobile station is
23 responding contained a SERVICE OPTION field, the mobile
24 station shall set this field to the service option number
25 specified in the SERVICE OPTION field of the page record
26 to which the mobile station is responding.
27 • If the page record to which the mobile station is
28 responding did not contain a SERVICE OPTION field, the
29 mobile station shall set this field to the default option
30 number ‘0000000000000001’.
31 If the mobile station does not accept the service option
32 specified by the page record of the General Page Message to
33 which the mobile station is responding and the mobile station
34 has an alternative service option to request, the mobile station
35 shall set this field to the service option code specified in
36 TSB58-A corresponding to the alternative service option.
37 If the mobile station does not accept the service option
38 specified by the page record of the General Page Message to
39 which the mobile station is responding and the mobile station
40 does not have an alternative service option to request, the
41 mobile station shall set this field to ‘0000000000000000’ to
42 reject the service option specified by the page record of the
43 General Page Message to which the mobile station is
44 responding.
45 PM – Privacy mode indicator.
2-403
C.S0005-0-2 v1.0
1 To request voice privacy, the mobile station shall set this field
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
7 ENCRYPTION- – Encryption algorithms supported by the mobile station.
8 _SUPPORTED If AUTH_MODE is equal to ‘00’, the mobile station shall omit
9 this field; otherwise, the mobile station shall set this field as
10 specified in table 2.7.1.3.2.4-5.
11 NUM_ALT_SO – Number of alternative service options.
13 alternative service options it supports other than the one
14 specified in the SERVICE_OPTION field. The mobile station
15 shall set this field to a value less than or equal to
16 MAX_NUM_ALT_SOs.
17 ALT_SO – Alternative service option.
18 The mobile station shall include NUM_ALT_SO occurrences of
19 this field. The mobile station shall set this field to the value
20 specified in TSB58-A, corresponding to the alternative service
21 option supported by the mobile station.
26 If the message is to contain the User Zone Identifier, the
30 If the UZID_INCL field is included in the message and is set to
31 ‘1’, the mobile station shall include this field and set it to
32 UZIDs; otherwise, the mobile station shall omit this field.
33 CH_IND – Channel Indicator.
36 field and set it, as shown in Table 2.7.1.3.2.5-1, to request
37 physical resources.
2-404
C.S0005-0-2 v1.0
1 Table 2.7.1.3.2.5-1. Channel indicator
CH_IND Channel(s) Requested

(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
8 shall set this field to ‘1’; otherwise, the mobile station shall set
24 FOR_RC_PREF – Forward Radio Configuration preference.
29 Configuration for the Forward Traffic Channel.
30 REV_RC_PREF – Reverse Radio Configuration preference.
2-405
C.S0005-0-2 v1.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.
13 shall include this field and set it as described in 2.7.4.27.1;
20 station supports Dedicated Control Channel; otherwise, the
22 DCCH Capability Type-
23 specific fields – Dedicated Control Channel capability information.
24 If DCCH_SUPPORTED is set to ‘1’, the mobile station shall
25 include this field and set it as defined in 2.7.4.27.2; otherwise,
26 the mobile station shall omit this field.
27 REV_FCH-
28 _GATING_REQ – Reverse eighth gating mode request indicator.
29 If P_REV_IN_USE is less than six, the mobile station shall
32 If the mobile station requests to turn on the reverse
33 Fundamental Traffic Channel gating mode in Radio
34 Configurations 3, 4, 5, and 6, the mobile station shall set this
36 ‘0’.
37
2-406
C.S0005-0-2 v1.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.
7
2-407
C.S0005-0-2 v1.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.
28
2-408
C.S0005-0-2 v1.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-409
C.S0005-0-2 v1.0
1 2.7.1.3.2.9 PACA Cancel Message
2 MSG_TAG: PACNM
2-410
C.S0005-0-2 v1.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-411
C.S0005-0-2 v1.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.
6
2-412
C.S0005-0-2 v1.0
1 2.7.1.3.2.11 Reserved
2
2-413
C.S0005-0-2 v1.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-414
C.S0005-0-2 v1.0
1 Table 2.7.2.3-1. Messages on r-dsch
Message Name MSG_TAG Section

Number

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-415
C.S0005-0-2 v1.0
1 2.7.2.3.1 Reserved
2 2.7.2.3.2 Message Body Contents

3
2-416
C.S0005-0-2 v1.0
2 MSG_TAG: ORDM
Field Length (bits)
ORDER 6
ADD_RECORD_LEN 3
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
2-417
C.S0005-0-2 v1.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.
8
2-418
C.S0005-0-2 v1.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:
8 The mobile station shall set this field to the record type code
9 shown in Table 2.7.4-1 corresponding to the type of this
10 information record.
13 in the type-specific fields of this record.
15 The mobile station shall set these fields as specified in 2.7.4
16 for this type of information record.
17
2-419
C.S0005-0-2 v1.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 TSB58-A. If the mobile station
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-420
C.S0005-0-2 v1.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)
23
2-421
C.S0005-0-2 v1.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.1.5 of TIA/EIA/IS-
15 2000.[2]), measured as specified in 2.6.6.2.2. If this value (-2
16 × 10 log10 PS) is less than 0, the mobile station shall set this
17 field to ‘000000’. If this value is greater than ‘111111’, the
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 TIA/EIA/IS-2000-[2]) has expired, the mobile
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-422
C.S0005-0-2 v1.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:
∑ PSi +
SOFT_SLOPEs ADD_INTERCEPTs
7 10 × log 10PS > × 10 × log10
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’.
25 KEEP – Keep pilot indicator.
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’;
28 otherwise, the mobile station shall set this field to ‘1’.
29
2-423
C.S0005-0-2 v1.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-424
C.S0005-0-2 v1.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
40 greater than ‘111111’, the mobile station shall set this field to
41 ‘111111’.
42 DCCH_PWR_MEAS_INCL - Forward Dedicated Control Channel power measurement
43 included.
2-425
C.S0005-0-2 v1.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
15 shall omit this field; otherwise, the mobile station shall set
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-426
C.S0005-0-2 v1.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’.
10
2-427
C.S0005-0-2 v1.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
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
15 DTMF_OFF_LENGTH – DTMF inter-digit interval code.

16 The mobile station shall set this field to the
17 DTMF_OFF_LENGTH value shown in Table 2.7.2.3.2.7-2
18 corresponding to the requested minimum interval between
19 DTMF pulses to be generated by the base station.
20
2-428
C.S0005-0-2 v1.0
1 Table 2.7.2.3.2.7-2. Recommended Minimum Inter-digit

2 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.
3
4 DIGITi – DTMF digit.

6 for each DTMF digit to be generated by the base station. The
7 mobile station shall set each occurrence of this field to the
8 code value shown in Table 2.7.1.3.2.4-4 corresponding to the
9 dialed digit.
10
2-429
C.S0005-0-2 v1.0
1 2.7.2.3.2.8 Status Message
2 MSG_TAG: STM
Field Length (bits)
RECORD_TYPE 8
RECORD_LEN 8

7 shown in Table 2.7.4-1 corresponding to the type of this
14 for this type of record.
15
2-430
C.S0005-0-2 v1.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
5 DIGIT_MODE – Digit mode indicator.

6 The mobile station shall set this field to the DIGIT_MODE
7 value from the Access Channel Origination Message for which
8 this message is a continuation.
9 NUM_FIELDS – Number of dialed digits in this message.
10 The mobile station shall set this field to the number of dialed
12 CHARi – A dialed digit or character.
14 this field. The mobile station shall include occurrences of this
15 field for all dialed digits after those sent in the Access Channel
16 Origination Message of which this message is a continuation.
18 set each occurrence of this field to the code value shown in
19 Table 2.7.1.3.2.4-4 corresponding to the dialed digit. If the
20 DIGIT_MODE field is set to ‘1’, the mobile station shall set
21 each occurrence of this field to the ASCII representation
22 corresponding to the dialed digit, as specified in ANSI
24 If the MORE_RECORDS field in the last Access Channel Origination Message, of which this
25 message is a continuation, is set to ‘1’, the mobile station shall include one or more
26 occurrences of the following three-field record; otherwise, the mobile station shall not
27 include the following record.
30 shown in Table 2.7.4-1.
2-431
C.S0005-0-2 v1.0

3 in the type-specific fields included in this record.
5 The mobile station shall include type-specific fields as
7
2-432
C.S0005-0-2 v1.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

6 Direction Message, or Universal Handoff Direction Message
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
11 Direction Message that determined the current Active Set.
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.
22
2-433
C.S0005-0-2 v1.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.
25
2-434
C.S0005-0-2 v1.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-435
C.S0005-0-2 v1.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
10 2.7.4.18 for the Service Configuration information record.
11
2-436
C.S0005-0-2 v1.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-437
C.S0005-0-2 v1.0

10 The mobile station shall set these fields as specified in
11 2.7.4.18 for the Service Configuration information record.
12
2-438
C.S0005-0-2 v1.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.
11
2-439
C.S0005-0-2 v1.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.
20
2-440
C.S0005-0-2 v1.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.
29
2-441
C.S0005-0-2 v1.0
1 2.7.2.3.2.17 TMSI Assignment Completion Message
2 MSG_TAG: TACM

4
2-442
C.S0005-0-2 v1.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
5 SIZE_OF_REQ_BLOB – Size of the request information block of octets (REQ_BLOB).

7 in the Reverse Supplemental Code Channel or the Reverse
8 Supplemental Channel request block of octets (REQ_BLOB).
9 REQ_BLOB – Reverse Supplemental Code Channel or the Reverse
10 Supplemental Channel request block of octets.
11 The mobile station shall include information in this field
12 containing the parameters that specify the characteristics of
13 the Reverse Supplemental Code Channels or the Reverse
14 Supplemental Channel request. The mobile station shall set
15 this field in accordance with the connected Service Option.
16 USE_SCRM_SEQ_NUM – Use Supplemental Channel Request Message sequence number
17 indicator.
2-443
C.S0005-0-2 v1.0
1 The mobile station shall set this field to '1' if the Supplemental
2 Channel Request Message sequence number is included in
3 this message; otherwise, the mobile station shall set this field
4 to '0'.
5 SCRM_SEQ_NUM – Supplemental Channel Request Message sequence number.
6 If USE_SCRM_SEQ_NUM is set to '1', the mobile station shall
7 set this field to the Supplemental Channel Request Message
8 sequence number that the base station is to include in a
9 Supplemental Channel Assignment Message or Extended
10 Supplemental Channel Assignment Message which is in
11 response to this message; otherwise, the mobile station shall
12 omit this field.
13 REF_PN – Time reference PN sequence offset.
14 If SIZE_OF_REQ_BLOB is set to ‘0000’ and
15 USE_SCRM_SEQ_NUM is set to ‘0’, the mobile station shall
17 to the PN sequence offset of the pilot used by the mobile
18 station to derive its time reference, relative to the zero offset
19 pilot PN sequence in units of 64 PN chips.
20 PILOT_STRENGTH – Reference pilot strength.
24 to
25 - 2 × 10 × log10 PS,
27 station to derive its time reference (see 2.1.5 of TIA/EIA/IS-
28 2000-[2]), measured as specified in 2.6.6.2.2. If this value (-2
29 × 10 log10 PS) is less than 0, the mobile station shall set this
30 field to ‘000000’. If this value is greater than ‘111111’, the
32 NUM_ACT_PN – Number of reported pilots in the Active Set.
36 to the number of reported pilots in the Active Set other than
37 the pilot identified by the REF_PN field.
38 If SIZE_OF_REQ_BLOB is set to ‘0000’ and USE_SCRM_SEQ_NUM is set to ‘0’, the mobile
39 station shall not include any occurrence of the following record; otherwise, the mobile
40 station shall include one occurrence of the following two-field record for each pilot in the
41 Active Set other than the pilot identified by the REF_PN field:
42 ACT_PN_PHASE – Active pilot measured phase.
43 The mobile station shall set this field to the phase of this pilot
44 PN sequence relative to the zero offset pilot PN sequence, in
45 units of one PN chip, as specified in 2.6.6.2.4.
46 ACT_PILOT_STRENGTH – Active pilot strength.
2-444
C.S0005-0-2 v1.0

2 - 2 × 10 × log10 PS,
7 ‘111111’.
8 NUM_NGHBR_PN – Number of reported neighbor pilots in the Candidate Set and
9 the Neighbor Set.
13 as follows:
15 reported pilots which are not in the Active Set and have
16 measurable strength that exceeds (T_ADDs - T_MULCHANs).
17 (NUM_ACT_PN + NUM_NGHBR_PN) shall not exceed 8. If
18 there are more than (8 - NUM_ACT_PN) pilots not in the Active
19 Set with strength exceeding (T_ADDs - T_MULCHANs),
20 the mobile station shall set NUM_NGHBR_PN to
21 (8 - NUM_ACT_PN) and report the NUM_NGHBR_PN strongest
22 pilots not in the Active Set.
23 If SIZE_OF_REQ_BLOB is set to ‘0000’ and USE_SCRM_SEQ_NUM is set to ‘0’, the mobile
24 station shall not include any occurrence of the following record; otherwise, the mobile
25 station shall include one occurrence of the following two-field record for each of the
26 NUM_NGHBR_PN reported pilots.
27 NGHBR_PN_PHASE – Neighbor pilot measured phase.
28 The mobile station shall set this field to the phase of this pilot
29 PN sequence relative to the zero offset pilot PN sequence, in
30 units of one PN chip, as specified in 2.6.6.2.4.
31 NGHBR_PILOT-
32 _STRENGTH – Neighbor pilot strength.
34 - 2 × 10 × log10 PS,
39 ‘111111’.
40
2-445
C.S0005-0-2 v1.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 (if PCG_OFF_TIME is
14 set to ‘0’) or power control groups (if PCG_OFF_TIME is set to
15 ‘1’) for which the mobile station will need to suspend its
17 the Candidate Frequency, to perform the requested search,
18 and to re-tune to the Serving Frequency. If the mobile station
19 requires multiple visits to the Candidate Frequency to
20 complete the requested search, the mobile station shall set
21 this field to the total number of frames (if PCG_OFF_TIME is
23 ‘1’) for all visits to the Candidate Frequency in a search
24 period.
25 MAX_OFF_TIME_FWD – Maximum time the mobile station is away from the Forward
26 Traffic Channel.
2-446
C.S0005-0-2 v1.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 (if PCG_OFF_TIME is
14 ‘1’) 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 or power control
21 groups for all visits to the Candidate Frequency in a search
22 period.
23 MAX_OFF_TIME_REV – Maximum time the mobile station is away from the Reverse
24 Traffic Channel.
26 estimate of the maximum number of frames or power control
27 groups for which the mobile station will need to suspend its
28 current Reverse Traffic Channel processing during a visit to
29 the Candidate Frequency, to perform a part of the requested
30 search, and to re-tune to the Serving Frequency.
31 PCG_OFF_TIMES – Indicator if off times are expressed in units of power control
32 groups.
33 If P_REV_IN_USEs is less than six, the mobile station shall set
34 this field to ‘0’; otherwise, the mobile station shall set this field
35 as follows:
36 The mobile station shall set this field to ‘1’ if it expresses
37 TOTAL_OFF_TIME_FWD, MAX_OFF_TIME_FWD,
38 TOTAL_OFF_TIME_REV, and MAX_OFF_TIME_REV in units of
39 power control groups; otherwise, the mobile station shall set
40 this field to ‘0’ so that TOTAL_OFF_TIME_FWD,
41 MAX_OFF_TIME_FWD, TOTAL_OFF_TIME_REV, and
42 MAX_OFF_TIME_REV are expressed in units of frames.
43 ALIGN_TIMING_USED – Alignment timing used indicator.
44 The mobile station shall set this field to ‘1’ if it will align the
45 times of its visits away from the Serving Frequency, as
46 requested by the base station; otherwise, the mobile station
48 MAX_NUM_VISITS – Maximum number of visits per search period.
2-447
C.S0005-0-2 v1.0
1 If the ALIGN_TIMING_USED field is set to ‘0’, the mobile

2 station shall omit this field; otherwise, the mobile station shall
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
9 station shall omit this field.
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.
20
2-448
C.S0005-0-2 v1.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-449
C.S0005-0-2 v1.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
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 TSB58-A.
11 If 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
15 TSB58-A.
16 CDMA_FREQ – Frequency assignment.
18 handoff attempt, the mobile station shall set this field to the
19 CDMA Channel number, in the specified CDMA band class,
20 corresponding to the CDMA Frequency Assignment for the
21 Target Frequency, as specified in 3.1.1.1 of TIA/EIA/IS-2000-
22 [2]. If this message is being sent to report measurements on a
23 Candidate Frequency, the mobile station shall set this field to
24 the CDMA Channel number, in the specified CDMA band
25 class, corresponding to the CDMA Frequency Assignment for
26 the Candidate Frequency, as specified in 3.1.1.1 of
27 TIA/EIA/IS-2000-[2].
28 SF_TOTAL_RX_PWR – Total received power on the Serving Frequency.
30 min (31,  (10 × log10(total_received_power) + 110) / 2 
31 )
2-450
C.S0005-0-2 v1.0
1 where total_received_power is the mean input power received

2 by the mobile station on the Serving Frequency, in mW/1.23
3 MHz.
4 CF_TOTAL_RX_PWR – Indicates the total received power on the Target Frequency or
5 the Candidate Frequency.
7 handoff attempt, the mobile station shall include the total
8 received power on the Target Frequency; if this message is
9 being sent to report measurements on a Candidate Frequency,
10 the mobile station shall include the total received power on
13 min (31,  (10 × log10(total_received_power) + 110) / 2 
14 )
16 by the mobile station on the Target Frequency or the
17 Candidate Frequency, in mW/1.23 MHz.
18 NUM_PILOTS - Number of pilots.
19 The mobile station shall set this field to the number of pilots
20 included in this message. The mobile station shall set this
21 field to a value from 0 to N8m, inclusive.
22
23 The mobile station shall include NUM_PILOTS occurrences of the following three-field
24 record:
25 PILOT_PN_PHASE – Pilot measured phase.
31 - 2 × 10 × log10 PS,
36 ‘111111’.
37 RESERVED_1 – Reserved bits.
39 If SEARCH_MODE is equal to ‘0001’, the mobile station shall include the following fields:
40
2-451
C.S0005-0-2 v1.0
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
RESERVED_3 0 - 7 (as needed)

4 The mobile station shall set this field to the CDMA band class
5 corresponding to the analog frequencies that are being
6 reported in this message, as specified in TSB58-A.
7 SF_TOTAL_RX_PWR - Indicates the total received power on the Serving Frequency.
9 min (31,  (10 × log10(total_received_power) + 110) / 2  )

11 by the mobile station on the Serving Frequency, in mW/1.23
12 MHz.
13 NUM_ANALOG_FREQS - Number of analog frequencies.
14 The base station shall set this field to the number of analog
15 frequencies included in this message.
16 RESERVED_2 - Reserved bits.
18
19 The message will include NUM_ANALOG_FREQS occurrences of the following three-field

20 record, one for each neighbor on the candidate frequency.
21 ANALOG_FREQ - Analog frequency channel number.
22 The base station shall set this field analog frequency channel
23 number to search.
24 SIGNAL_STRENGTH - Signal strength.
26 - 0.5 × SS,
2-452
C.S0005-0-2 v1.0
1 where SS is the strength of this signal, measured in dBm as

2 specified in 2.6.6.2.10.3. If this value (- 0.5 × SS) is less
3 than 0, the mobile station shall set this field to ‘000000’. If
4 this value is greater than 63, the mobile station shall set this
5 field to ‘111111’.
7 RESERVED_3 - The mobile station shall add reserved bits as needed in order
8 to make the length of the entire message equal to an integer
9 number of octets. The mobile station shall set each of these
10 bits to ‘0’.
11
2-453
C.S0005-0-2 v1.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
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.
12 - 2 × 10 × log10PS ,
14 station to derive its time reference (see TIA/EIA/IS-2000-[2]),
15 measured as specified in 2.6.6.2.2. If this value is less than
16 0, the mobile station shall set this field to ‘000000’. If this
17 value is greater than ‘111111’, the mobile station shall set this
18 field to ‘111111’.
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 TIA/EIA/IS-2000-[2]) has expired, the mobile station shall
23 set this field to ‘0’; otherwise, the mobile station shall set this
24 field to ‘1’.
25 SF_RX_PWR - The received power spectral density of the Serving Frequency.
27 min (31,  (10 × log10(spec_density) + 120) / 2  )
2-454
C.S0005-0-2 v1.0
1 where spec_density is the mobile station received power

2 spectral density of the Serving Frequency, in mW/1.23MHz.
3 If this value is less than 0, the mobile station shall set this
4 field to ‘00000’.
5 NUM_PILOT - Number of Pilots.
6 The mobile station shall set this field to the number of other
7 reported pilots of the Active Set and the Candidate Set.
9 The mobile station shall include NUM_PILOT occurrences of the following three-field record,
10 one for each pilot in the Active Set and one for each pilot in the Candidate Set, other than
11 the pilot identified by the REF_PN field.
12 PILOT_PN_PHASE - Pilot measured phase.
16 PILOT_STRENGTH - Pilot strength.
18  - 2 × 10 × log10PS ,
20 2.6.6.2.2. If this value is less than 0, the mobile station shall
21 set this field to ‘000000’. If this value is greater than
22 ‘111111’, the mobile station shall set this field to ‘111111’.
23 KEEP - Keep pilot indicator.
24 If the handoff drop timer (see 2.6.6.2.3) corresponding to this
25 pilot has expired, the mobile station shall set this field to ‘0’;
27
2-455
C.S0005-0-2 v1.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.

6 The mobile station shall set this field to ‘1’ if
7 CURR_FCH_SETPT is included; otherwise the mobile station
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 field is included; otherwise the mobile
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-456
C.S0005-0-2 v1.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.
6 The mobile station shall set this field to the Supplemental
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
15
2-457
C.S0005-0-2 v1.0
1 2.7.2.3.2.23 Resource Request Message
2 MSG_TAG: RRM
2-458
C.S0005-0-2 v1.0
1 2.7.2.3.2.24 Resource Request Mini Message
2 MSG_TAG: RRMM
2-459
C.S0005-0-2 v1.0
1 2.7.2.3.2.25 Extended Release Response Message
2 MSG_TAG: ERRM
2-460
C.S0005-0-2 v1.0
1 2.7.2.3.2.26 Extended Release Response Mini Message
2 MSG_TAG: ERRMM
2-461
C.S0005-0-2 v1.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), of the Active-
9 Set pilot whose strength is being reported. The mobile station
10 shall use a value of 0 to report the pilot represented by the
11 REF_PN field in the last sent Pilot Strength Measurement
12 Message. The mobile station shall use a value of n, where n is
13 an integer greater than 0, to report the pilot represented by
14 the nth occurrence of the PILOT_PN_PHASE field in the last
15 sent Pilot Strength Measurement Message.
18 -2 × 10 × log10 PS,
19 where PS is the strength of this Active-Set pilot, measured as
20 specified in TIA/EIA/IS-2000-[2]. If this value is less than 0,
21 the mobile station shall set this field to ‘000000’. If this value
22 is greater than ‘111111’, the mobile station shall set this field
23 to ‘111111’.
24 RANK – Rank order.
25 The mobile station shall set this field to the rank order of the
26 pilot whose strength is being reported, relative to all other
27 pilots in the current Active Set. The mobile station shall use a
28 value of 0 to report the strongest pilot in the current Active
29 Set.
30
2-462
C.S0005-0-2 v1.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 octets.

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.
11
2-463
C.S0005-0-2 v1.0
1 2.7.2.3.2.29 Resource Release Request Message
2 MSG_TAG: RRRM
2-464
C.S0005-0-2 v1.0
1 2.7.2.3.2.30 Resource Release Request Mini Message
2 MSG_TAG: RRRMM
2-465
C.S0005-0-2 v1.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.
7 2.7.3 Orders
8 Order Messages are sent by the mobile station on the r-csch and on the r-dsch. The
9 general PDU format used on the r-csch is defined in 2.7.1.3.2.2, and the general PDU
10 format used on the r-dsch is defined in 2.7.2.3.2.1. There are many specific types of Order
11 Messages, as shown in Table 2.7.3-1.
12 The mobile station may send on the r-csch any type of order shown in Table 2.7.3-1 with a
13 ‘Y’ in the first column, but shall not send on the r-csch any type of order with an ‘N’ in the
14 first column. The mobile station may send on the r-dsch any type of order shown in
15 Table 2.7.3-1 with a ‘Y’ in the second column, but shall not send on the r-dsch any type of
16 order with an ‘N’ in the second column. The mobile station shall be capable of sending all
17 types of orders shown in Table 2.7.3-1 with a ‘Y’ in the sixth column.
18 An order consists of a 6-bit order code and zero or more order-specific fields. The mobile
19 station shall set the ORDER field in the Order Message to the order code shown in Table
20 2.7.3-1 corresponding to the type of order being sent.
21 If the order qualification code in the fourth column of Table 2.7.3-1 is ‘00000000’ and there
22 are no other additional fields as shown by an ‘N’ in the fifth column, the mobile station
23 shall include no order qualification code or other order-specific fields in the Order Message.
24 The order qualification code of such a message is implicitly ‘00000000’.
25 If the order qualification code is not ‘00000000’ and there are no other additional fields as
26 shown in Table 2.7.3-1 by an ‘N’ in the fifth column, the mobile station shall include the
27 order qualification code as the only order-specific field in the Order Message.
28 If there are other additional fields as shown in Table 2.7.3-1 by a ‘Y’ in the fifth column, the
29 mobile station shall include order-specific fields as specified in the corresponding
30 subsection of this section.
31
2-466
C.S0005-0-2 v1.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
TIA/EIA/IS-2000-[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)
3
2-467
C.S0005-0-2 v1.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)
3
2-468
C.S0005-0-2 v1.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)
3
2-469
C.S0005-0-2 v1.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 N 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)
3
2-470
C.S0005-0-2 v1.0
1 2.7.3.1 Base Station Challenge Order
Order-Specific Field Length (bits)
ORDQ 8
RANDBS 32
4 ORDQ – Order qualification code.

6 RANDBS – Random challenge data.
8 2.3.12.1.5.
9
2-471
C.S0005-0-2 v1.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 TSB58-A, corresponding to the requested or
9 alternative service option.
10
2-472
C.S0005-0-2 v1.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 TSB58-A, corresponding to the accepted
9 service option, or to ‘0000000000000000’ to reject the
10 proposed service option. See 2.6.4.1.2.2.1.
11
2-473
C.S0005-0-2 v1.0
1 2.7.3.4 Mobile Station Reject Order
ORDQ 8
REJECTED_TYPE 8
If the order is sent on the 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:
REJECTED_ORDER 8
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 and
or if the order is sent on the Reverse Traffic Channel and
REJECTED_TYPE is ‘00000011’ or
the order-specific fields also include the following field:
REJECTED_RECORD 8
REJECTED_PDU_TYPE 0 or 2

6 The mobile station shall set this field to the ORDQ value
7 shown in Table 2.7.3-1 corresponding to the reason for
8 rejecting the message.
9 REJECTED_TYPE – Message type of rejected message.
11 MSG_TYPE field of the message being rejected.
12 If the MSG_TYPE field is not 8 bits, the mobile station shall
13 set the least significant bits of this field to the value of the
14 MSG_TYPE field and set all the remaining bits to ‘0’.
2-474
C.S0005-0-2 v1.0
1 REJECTED_ORDER – Order type of rejected message.

2 If the rejected message was an Order Message, the mobile
3 station shall set this field to the value of the ORDER field in
4 the rejected message.
5 Otherwise, the mobile station shall omit this field.
6 REJECTED_ORDQ – Order qualification code of rejected message.
7 If the rejected message was an Order Message including an
8 ORDQ field, the mobile station shall set this field to the value
9 of the ORDQ field in the rejected message. If the rejected
10 message was an Order Message not including an ORDQ field,
11 the mobile station shall set this field to ‘00000000’.
13 REJECTED_PARAM_ID – Parameter identification of the rejected parameter.
14 If the rejected message was a Set Parameters Message, the
15 mobile station shall set this field to the PARAMETER_ID of the
16 first parameter for which the requested operation could not be
17 completed.
19 REJECTED_RECORD – Record type of the rejected information record.
20 If the rejected message was a Feature Notification Message, an
21 Alert With Information Message or a Flash With Information
22 Message, the mobile station shall set this field to the
23 RECORD_TYPE field of the first information record that could
24 not be accepted.
26 REJECTED_PDU_TYPE – PDU type of the rejected message.
29 to the REJECTED_PDU_TYPE code shown in Table 2.7.3.5-1
30 corresponding to the PDU type of the message being rejected.
31
32 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
33
34
35
2-475
C.S0005-0-2 v1.0
1 2.7.4 Information Records

2 On the r-csch, information records may be included in the Status Response Message and
3 the Extended Status Response Message. On the r-dsch, information records may be
4 included in the Origination Continuation Message, the Flash With Information Message, the
5 Service Request Message, the Service Response Message, the Status Message, and the Status
6 Response Message. Table 2.7.4-1 lists the information record type values that may be used
7 with each message type. The following sections describe the contents of each of the record
8 types in detail.
9
10 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
11
2-476
C.S0005-0-2 v1.0
Record SDU_TAG r-csch r-dsch

Information Record Type
(binary)
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
Geo-location Information 00011110 Status [2] Y Y
Band Subclass Information 00011111 Status [2] Y Y
Extended Record Type — 11111110 Country-Specific
International
All other record type values are reserved.
[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
2-477
C.S0005-0-2 v1.0
1 2.7.4.1 Reserved
2-478
C.S0005-0-2 v1.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 ANSI
12
2-479
C.S0005-0-2 v1.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

5 The mobile station shall set this field to the NUMBER_TYPE
7 of the called number, as defined in ANSI T1.607-1990, Section
8 4.5.9[8].
10 The mobile station shall set this field to the NUMBER_PLAN
12 numbering plan used for the called number, as defined in
13 ANSI T1.607-1990, Section 4.5.9[8].
15 The mobile stations shall include one occurrence of this field
16 for each character in the called number. The mobile station
17 shall set each occurrence of this field to the ASCII
18 representation corresponding to the character, as specified in
19 ANSI X3.4[12], with the most significant bit set to ‘0’.
20 RESERVED – Reserved bit.
22
2-480
C.S0005-0-2 v1.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 ANSI T1.607-1990,
9 Section 4.5.9[8].
13 numbering plan used for the calling number, as defined in
14 ANSI T1.607-1990, Section 4.5.9[8].
15 PI – Presentation indicator.
16 This field indicates whether or not the calling number should
17 be displayed.
18 The mobile station shall set this field to the PI value shown in
19 Table 2.7.4.4-1 corresponding to the presentation indicator,
20 as defined in ANSI T1.607-1990, Section 4.5.9[8].
21
22 Table 2.7.4.4-1. Presentation Indicators
Description PI (binary)
Presentation allowed 00
Presentation restricted 01
Number not available 10
Reserved 11
23
2-481
C.S0005-0-2 v1.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 ANSI T1.607-1990, Section 4.5.9[8].
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
17
2-482
C.S0005-0-2 v1.0
1 2.7.4.5 Reserved
2-483
C.S0005-0-2 v1.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.
ORIG_MODE 1
PRI_SERVICE 16
SEC_SERVICE 16
RESERVED 7
5 ORIG_MODE – Origination mode indicator.

6 If the current call is a mobile-originated call, the mobile
7 station shall set this field to ‘0’. If the current call is a mobile-
8 terminated call, the mobile station shall set this field to ‘1’.
9 PRI_SERVICE – Primary service option.
10 The mobile station shall set this field to the value specified in
11 TSB58-A, corresponding to the current primary service option.
12 If no primary service option is active, the mobile station shall
13 set this field to ‘0000000000000000’.
14 SEC_SERVICE – Secondary service option.
16 TSB58-A, corresponding to the current secondary service
17 option. If no secondary service option is active, the mobile
21
2-484
C.S0005-0-2 v1.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 ‘00000110’; 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-485
C.S0005-0-2 v1.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 2.6.1.2.2.
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 TSB58-A);
18 otherwise, the mobile station shall include one occurrence of
19 this field with the value set to ‘0000000000000000’.
22
2-486
C.S0005-0-2 v1.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
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-487
C.S0005-0-2 v1.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.
10 The mobile station shall add reserved bits as needed in order
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’.
14
2-488
C.S0005-0-2 v1.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.
12 The mobile station shall set this field to the value shown in
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,
22
2-489
C.S0005-0-2 v1.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 in ANSI T1.607-1990,
8 Section 4.5.9[8].
12 numbering plan used for the connected number, as defined,
13 in ANSI T1.607-1990, Section 4.5.9[8].
14 PI – Presentation indicator.
15 This field indicates whether or not the connected number
16 should be displayed. The mobile station shall set this field to
17 the PI value shown in Table 2.7.4.4-1 corresponding to the
18 presentation indicator, as defined in ANSI T1.607-1990,
19 Section 4.5.9[8].
20 SI – Screening indicator.
21 This field indicates how the connected number was screened.
22 The mobile station shall set this field to the SI value shown in
27 for each character in the connected number. The mobile
28 station shall set each occurrence of this field to the ASCII
33
2-490
C.S0005-0-2 v1.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.)
21
2-491
C.S0005-0-2 v1.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).
8
2-492
C.S0005-0-2 v1.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
Subfield (bits) Subfield Description
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
RESERVED 6
11
12 The mobile station shall set each subfield to ‘1’ if the

13 corresponding band class is supported by the mobile station;
14 otherwise, the mobile station shall set the subfield to ‘0’.
15 If the mobile station does not support any band class that is
16 listed in the second octet, the mobile station need not include
17 the second octet.
2-493
C.S0005-0-2 v1.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.
9
2-494
C.S0005-0-2 v1.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
5 MAX_EIRP – Maximum effective isotropic radiated power (EIRP).

6 The mobile station shall set this field to the minimum EIRP at
7 maximum output (in dBW) for the mobile station plus 60 (see
8 TIA/EIA-98-C[14]). When the mobile station output power is
9 expressed in ERP, it may be converted to EIRP by adding 2 dB
10 to the ERP value.1
11
1 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-495
C.S0005-0-2 v1.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 TIA/EIA/IS-2000.6 analog mode [6]
OP_MODE3 1 TIA/EIA/IS-91 wide analog mode [28]
OP_MODE4 1 TIA/EIA/IS-91 narrow analog mode [28]
RESERVED 3 –
19
2-496
C.S0005-0-2 v1.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

OP_MODE1 1 CDMA mode2
OP_MODE2 1 Analog mode TIA/EIA/IS-2000.[6]
OP_MODE3 1 Wide analog mode TIA/EIA/IS-91 [28]
OP_MODE4 1 Narrow analog mode TIA/EIA/IS-91 [28]
RESERVED 3 – –
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’.
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.
18
2 The mobile station shall set OP_MODE1 as same as OP_MODE0.
2-497
C.S0005-0-2 v1.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 TSB58-A for the service option supported.
21
22
2-498
C.S0005-0-2 v1.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_RATES set to ‘00000000’. If this instance is included, the mobile station shall
15 set MULTIPLEX_OPTION to the highest numbered multiplex option from the set {3,
16 5, 7, 9, 11, 13, 15} which the mobile station supports for reverse operation, and the
17 mobile station shall support all multiplex options less than or equal to
18 MULTIPLEX_OPTION from that set for reverse operation.
21 FOR_RATES set to ‘00000000’. If this instance is included, the mobile station shall
23 6, 8, 10, 12, 14, 16} which the mobile station supports for reverse operation, and the
25 MULTIPLEX_OPTION from that set for reverse operation.
28 REV_RATES set to ‘00000000’. If this instance is included, the mobile station shall
30 5, 7, 9, 11, 13, 15} which the mobile station supports for forward operation, and the
32 MULTIPLEX_OPTION from that set for forward operation.
35 REV_RATES set to ‘00000000’. If this instance is included, the mobile station shall
37 6, 8, 10, 12, 14, 16} which the mobile station supports for forward operation, and
38 the mobile station shall support all multiplex options less than or equal to
39 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_RATES is set to a value other than ‘00000000’.
2-499
C.S0005-0-2 v1.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_RATES 8
REV_RATES 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 (e.g., 1 corresponds to Multiplex
10 Option 1).
11 FOR_RATES – Forward Traffic Channel transmission rates.
12 If FOR_RATES = ‘00000000’, then the specified multiplex
13 option in this record shall indicate the supported multiplex
14 option for the Reverse Traffic Channel only. In this case, no
15 further interpretation of the FOR_RATES field shall be made.
16 The mobile station shall not set both FOR_RATES and
17 REV_RATES equal to ‘00000000’ in the same information
18 record.
19 If MULTIPLEX_OPTION is equal to 1, 3, 5, 7, 9, 11, 13, or 15,
20 this field consists of the subfields specified in Table 2.7.4.17-1
21 which are included in the information record in the order
22 shown in the table. The subfields in Table 2.7.4.17-1 refer to
23 the rates supported on the Fundamental Code Channel of the
25
2-500
C.S0005-0-2 v1.0
1 Table 2.7.4.17-1. Forward Fundamental Traffic Channel

2 Transmission Rates for Forward Multiplex Option 1
Length
RS1_9600_FOR 1 Forward Traffic Channel,

9600 bps
4800 bps
2400 bps
1200 bps
RESERVED 4
3

8 the rates supported on the Fundamental Channel of the
10
11 Table 2.7.4.17-2. Forward Fundamental Traffic Channel

12 Transmission Rates for Forward Multiplex Option 2
Length

14400 bps
7200 bps
3600 bps
1800 bps
RESERVED 4
13
14 The mobile station shall set the subfields specified in Tables

15 2.7.4.17-1 and 2.7.4.17-2, corresponding to the Forward
16 Traffic Channel transmission rates supported by the mobile
17 station for this multiplex option to ‘1’, and shall set the
18 remaining subfields to ‘0’. The mobile station shall set
19 RESERVED to ‘0000’.
2-501
C.S0005-0-2 v1.0
1 REV_RATES – Reverse Traffic Channel transmission rates.

2 If REV_RATES is equal to ‘00000000’, then the specified
3 multiplex option in this record indicate the supported
4 multiplex option for the Forward Traffic Channel only. In this
5 case, no further interpretation of the REV_RATES field shall
6 be made. The mobile station shall not set both FOR_RATES
7 and REV_RATES equal to ‘00000000’ in the same information
8 record.
15
16 Table 2.7.4.17-3. Reverse Fundamental Traffic Channel

17 Transmission Rates for Reverse Multiplex Option 1
Length
RS1_9600_REV 1 Reverse Traffic Channel,

9600 bps
RS1_4800_REV 1 Reverse Traffic Channel ,
4800 bps
2400 bps
1200 bps
RESERVED 4
18

25
2-502
C.S0005-0-2 v1.0
1 Table 2.7.4.17-4. Reverse Fundamental Traffic Channel

2 Transmission Rates for Reverse Multiplex Option 2
Length
RS2_14400_REV 1 Reverse Traffic Channel ,

14400 bps
7200 bps
3600 bps
1800 bps
RESERVED 4
3
4 The mobile station shall set the subfields specified in Table

5 2.7.4.17-3 and Table 2.7.4.17-4 corresponding to the Reverse
6 Traffic Channel transmission rates supported by the mobile
7 station for this multiplex option to ‘1’, and shall set the
8 remaining subfields to ‘0’. The mobile station shall set
10
2-503
C.S0005-0-2 v1.0
1 2.7.4.18 Service Configuration

2 This record is included in a Status Response Message to return the current service
3 configuration, and in a Service Request Message and a Service Response Message to
4 propose a service configuration.
2-504
C.S0005-0-2 v1.0
FOR_MUX_OPTION 16
REV_MUX_OPTION 16
FOR RATES 8
REV_RATES 8
NUM_CON_REC 8
NUM_CON_REC occurrences of the following variable-length
record
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)
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
1
2-505
C.S0005-0-2 v1.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 fields 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 fields Variable (see 3.7.5.7.1)

2
3 FOR_MUX_OPTION – Forward Traffic Channel multiplex option.

4 For a Status Response Message, the mobile station shall set
5 this field to the number of the Forward Traffic Channel
6 multiplex option for the current service configuration (e.g., 1
7 corresponds to Multiplex Option 1).
8 For a Service Request Message and a Service Response
9 Message, the mobile station shall set this field to the number
10 of the Forward Traffic Channel multiplex option for the
11 proposed service configuration.
12 REV_MUX_OPTION – Reverse Traffic Channel multiplex option.
14 this field to the number of the Reverse Traffic Channel
15 multiplex option for the current service configuration (e.g., 1
16 corresponds to Multiplex Option 1).
18 Message, the mobile station shall set this field to the number
19 of the Reverse Traffic Channel multiplex option for the
20 proposed service configuration.
2-506
C.S0005-0-2 v1.0
1 FOR_RATES – Transmission rates of the Fundamental Channel of the

3 The mobile station shall use the Forward Fundamental
4 Channel transmission rates specified in 2.7.4.17 for the
5 specified Forward Traffic Channel multiplex option.
7 the subfields corresponding to the Forward Traffic Channel
8 transmission rates of the current service configuration to ‘1’,
9 and shall set the remaining subfields to ‘0’. The mobile
10 station shall set RESERVED to ‘0000’.
12 Message, the mobile station shall set the subfields
13 corresponding to the Forward Traffic Channel transmission
14 rates of the proposed service configuration to ‘1’, and shall set
15 the remaining subfields to ‘0’. The mobile station shall set
17 REV_RATES – Transmission rates of the Fundamental Channel of the
19 The mobile station shall use the Reverse Fundamental
20 Channel transmission rates specified in 2.7.4.17 for the
21 specified Reverse Traffic Channel multiplex option.
23 the subfields corresponding to the Reverse Traffic Channel
24 transmission rates of the current service configuration to ‘1’,
25 and shall set the remaining subfields to ‘0’. The mobile
26 station shall set RESERVED to ‘0000’.
28 Message, the mobile station shall set the subfields
29 corresponding to the Reverse Traffic Channel transmission
30 rates of the proposed service configuration to ‘1’, and shall set
31 the remaining subfields to ‘0’. The mobile station shall set
33 NUM_CON_REC – Number of service option connection records.
34 The mobile station shall set this field to the number of service
35 option connection records included in the message.
36 For a Status Response Message, the mobile station shall include one occurrence of the
37 following variable-length record for each service option connection of the current service
38 configuration.
39 For a Service Request Message and a Service Response Message, the mobile station shall
40 include one occurrence of the following variable-length record for each service option
41 connection of the proposed service configuration.
42 RECORD_LEN – Service option connection record length.
44 included in this service option connection record including
45 this field.
2-507
C.S0005-0-2 v1.0
1 CON_REF – Service option connection reference.

3 this field to the service option connection reference.
5 Message, if the service option connection is part of the current
6 service configuration, the mobile station shall set this field to
7 the service option connection reference; otherwise, the mobile
11 this field to the service option in use with the service option
12 connection.
14 Message, the mobile station shall set this field to the service
15 option to be used with the service option connection.
16 FOR_TRAFFIC – Forward Traffic Channel traffic type.
18 this field to the FOR_TRAFFIC code shown in Table 2.7.4.18-1
19 corresponding to the Forward Traffic Channel traffic type in
23 FOR_TRAFFIC code shown in Table 2.7.4.18-1 corresponding
24 to the Forward Traffic Channel traffic type to be used with the
25 service option connection.
26
27 Table 2.7.4.18-1. FOR_TRAFFIC Codes
FOR_TRAFFIC
(binary) Description
The service option connection does not

0000 use Forward Traffic Channel traffic.
The service option connection uses
0001 primary traffic on the Forward Traffic
Channel.
The service option connection uses
0010 secondary traffic on the Forward Traffic
Channel.
All other FOR_TRAFFIC codes are reserved
28
29 REV_TRAFFIC – Reverse Traffic Channel traffic type.

31 this field to the REV_TRAFFIC code shown in Table 2.7.4.18-2
32 corresponding to the Reverse Traffic Channel traffic type in
2-508
C.S0005-0-2 v1.0

3 REV_TRAFFIC code shown in Table 2.7.4.18-2 corresponding
4 to the Reverse Traffic Channel traffic type to be used with the
7 Table 2.7.4.18-2. REV_TRAFFIC Codes
REV_TRAFFIC
0000 The service option connection does not

use Reverse Traffic Channel traffic.
0001 The service option connection uses
primary traffic on the Reverse Traffic
Channel.
secondary traffic on the Reverse Traffic
Channel.
All other REV_TRAFFIC codes are reserved
9 UI_ENCRYPT_MODE – Encryption mode indicator for user information privacy.

11 this field to indicate the current user information encryption
12 mode as shown in Table 2.7.4.18-3.
14 Message, the mobile station shall set this field to indicate the
15 proposed user information encryption mode as shown in Table
16 2.7.4.18-3.
17 Table 2.7.4.18-3. User information Encryption Modes
UI_ENCRYPT_MODE
Encryption Mode
Field
(binary)
000 User Information Encryption

disabled
001 User Information encryption
with ORYX algorithm enabled
(see “Common Cryptograph
Algorithms”)
010-111 Reserved
18
2-509
C.S0005-0-2 v1.0

3 this field to the service reference identifier in use.
5 Message, the mobile station shall set this field as follows:
6 If the service option connection is a part of the current service
7 configuration, the mobile station shall set this field to the
8 service reference identifier in use.
9 If the service option connection is not a part of the current
10 service configuration, the mobile station shall perform the
11 following:
12 - If this service option connection request is initiated by the
13 base station, the mobile station shall set this field to the
14 value sent by the base station.
16 mobile station, the mobile station shall perform the
17 following: if the service instance provides a service
18 reference identifier, the mobile station shall set this field
19 to the service reference identifier specified by the service
20 instance; otherwise, the mobile station shall set this field
21 to the smallest unused service reference identifier value
22 between 1 and 6 (inclusive).
23
24 RLP_INFO_INCL - RLP information included indicator.
25 The mobile station shall set this field to ‘1’ if the RLP_BLOB
26 field is included in this record; otherwise, it shall set this field
27 to ‘0’.
28 RLP_BLOB_LEN - RLP information block of bits length.
29 If the RLP_INFO_INCL field is set to ‘0’, the mobile station

30 shall omit this field; otherwise, it shall include this field and
31 set it as follows:
32 The mobile station shall set this field to the size of the
33 RLP_BLOB field in integer number of octets.
34 RLP_BLOB - Radio Link Protocol block of bits.
35 If the RLP_INFO_INCL field is set to ‘0’, the mobile station

36 shall omit this field; otherwise, the mobile station shall
37 include this field and set it as follows:
2-510
C.S0005-0-2 v1.0

2 this field to the Radio Link Protocol block of bits for this
3 service option connection, and shall add ‘0’ bits to the end of
4 the field as needed in order to make the length of this field
5 equal to an integer number of octets.
6 For a Service Request Message or Service Response Message,

7 the mobile station shall set this field to the proposed Radio
8 Link Protocol block of bits for this service option connection,
9 and shall add ‘0’ bits to the end of the field as needed in order
10 to make the length of this field equal to an integer number of
11 octets.
12 RESERVED - Reserved bits.

14 to make the length of this record equal to an integer number
15 of octets. The mobile station shall set these bits to ‘0’.
16 FCH_CC_INCL – Fundamental Channel Configuration included indicator.

17 The mobile station shall set this field to ‘1’, if Fundamental
18 Channel Configuration information is included in the record;
20 FCH_FRAME_SIZE – Fundamental Channel Frame Size.
21 If FCH_CC_INCL field is set to ‘1’, the mobile station shall

22 include this field and set it as described below; otherwise, the

25 this field to ‘1’, if the 5ms frame size is used in the Forward
26 and Reverse Fundamental Channel, in addition to 20ms
27 frame, for the current service configuration; otherwise, the
29 For a Service Request Message or a Service Response Message,

30 the mobile station shall set this field to ‘1’ to propose that the
31 5 ms frame size in addition to the 20 ms frame size is used for
32 the proposed service configuration; otherwise the mobile
33 station shall set this field to ‘0’
34 FOR_FCH_RC – Forward Fundamental Channel Radio Configuration.

2-511
C.S0005-0-2 v1.0

2 this field to the Forward Fundamental Channel Radio
3 Configuration for the current service configuration.
4 For a Service Request Message or Service Response Message,
5 the mobile station shall set this field to the Forward
6 Fundamental Channel Radio Configuration for the proposed
8 (see TIA/EIA/IS-2000-[2] Table 3.1.3.1-1)
9 REV_FCH_RC – Reverse Fundamental Channel Radio Configuration.
14 field to the Reverse Fundamental Channel Radio
17 the mobile station shall set this field to the Reverse
18 Fundamental Channel Radio Configuration for the proposed
20 (see TIA/EIA/IS-2000-[2] Table 2.1.3.1-1)
21 DCCH_CC_INCL – DCCH Channel Configuration included indicator.
22 The mobile station shall set this field to ‘1’, if DCCH channel
23 configuration information is included in this record;
25 DCCH_FRAME_SIZE – Dedicated Control Channel Frame Size.
26 If DCCH_CC_INCL field is set to ‘1’, the mobile station shall


30 this field to the frame size, as defined in Table 3.7.5.7-3, for

33 the mobile station shall set this field to the frame size, as
34 defined in Table 3.7.5.7-1, for the proposed service
35 configuration.
36 FOR_DCCH_RC – Forward Dedicated Control Channel Radio Configuration.

2-512
C.S0005-0-2 v1.0

2 this field to the Forward Dedicated Control Channel Radio
5 the mobile station shall set this field to the forward Dedicated
6 Control Channel Radio Configuration (see TIA/EIA/IS-2000-
7 [2] Table 3.1.3.1-1) for the proposed service configuration.
8 REV_DCCH_RC – Reverse Dedicated Control Channel Radio Configuration.
13 this field to the Reverse Dedicated Control Channel Radio
14 Configuration (see Table 2.1.3.1-1 of TIA/EIA/IS-2000-[2]) for
17 the mobile station shall set this field to the Reverse Dedicated
18 Control Channel Radio Configuration for the proposed service
19 configuration.
20 FOR_SCH_CC_INCL – Forward SCH Channel Configuration included indicator.
21 The mobile station shall set this field to ‘1’, if the Forward
22 Supplemental Channel Configuration information is included;
24 NUM_FOR_SCH – Number of Forward Supplemental Channels.
25 If FOR_SCH_CC_INCL field is set to ‘1’, the mobile station
26 shall include this field and set it as describe below; otherwise,
27 the mobile station shall omit this field.
29 this field to the number of Forward Supplemental Channels
30 for the current service configuration and include one
31 occurrence of the following three-field SCH record for each
32 Supplemental Channel Configuration.
34 the mobile station shall set this field to the number of
35 Forward Supplemental Channels for the proposed service
36 configuration and include one occurrence of the following
37 three-field SCH record for each Supplemental Channel
38 Configuration.
39 FOR_SCH_ID – Forward Supplemental Channel identification.
40 The mobile station shall set this field to the identification of
41 the Supplemental Channel included in this Forward
42 Supplemental Channel Configuration record.
44 Channel identifier, shown in Table 2.7.3.18-4.
2-513
C.S0005-0-2 v1.0
1 Table 2.7.3.18-4. SCH Identifier
FOR_SCH_ID
Description
REV_SCH_ID
(binary)
00 Supplemental Channel 0
01 Supplemental Channel 1
10-11 Reserved
3 FOR_SCH_MUX – Forward Supplemental Channel Multiplex Option.

4 The mobile station shall set this field to the Multiplex Option
5 of the Supplemental (see 2.2.4.4.1.5 of TIA/EIA/IS-2000.[3])
6 for this service configuration.
7 SCH_CC Type
8 -specific field - Forward Supplemental Channel Configuration Record.
9 The mobile station shall set this field to the subfields of the
10 Channel Configuration record defined in 3.7.5.7.1, for this
11 Supplemental Channel included in the service configuration.
12 REV_SCH_CC_INCL – Reverse SCH Channel Configuration included indicator.
13 The mobile station shall set this field to ‘1’, if the Reverse
14 Supplemental Channel Configuration information is included;
16 NUM_REV_SCH – Number of Reverse Supplemental Channels.
17 If REV_SCH_CC_INCL field is set to ‘1’, the mobile station
18 shall include this field and set it as described below;
21 this field to the number of Reverse Supplemental Channels for
22 the current service configuration and include one occurrence
23 of the following three-field record for each reverse
24 Supplemental Channel Configuration.
26 the mobile station shall set this field to the number of Reverse
27 Supplemental Channels for the proposed service configuration
28 and include one occurrence of the following three-field record
29 for each reverse Supplemental Channel Configuration.
30 REV_SCH_ID – Reverse Supplemental Channel identification.
31 The mobile station shall set this field to the identifier of the
32 Supplemental Channel included in this Reverse Supplemental
33 Channel Configuration record.
35 Channel identifier, shown in Table 2.7.3.18-4
36 REV_SCH_MUX – Reverse Supplemental Channel Multiplex Option.
2-514
C.S0005-0-2 v1.0
1 The mobile station shall set this field to the Multiplex Option
2 associated with the maximum data rate for this Reverse
3 Supplemental Channel (see TIA/EIA/IS-2000.[3]).
4 SCH_CC Type-
5 specific fields – Reverse Supplemental Channel Configuration record.
6 The mobile station shall set this field to the subfields of the
7 Channel Configuration record defined in 3.7.5.7.1, for this
8 Reverse Supplemental Channel included in the service
9 configuration.
14 bits to ‘0’.
15
16
2-515
C.S0005-0-2 v1.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
10 ANSI T1.607-1990, Section 4.5.8[8].
11
12 Table 2.7.4.19-1. Subaddress Types
SUBADDRESS
TYPE
Description (binary)
NSAP (CCITT Recommendation 000

X.213/ISO 8348 AD2)
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 ANSI T1.607-1990, Section 4.5.8[8]. This field is only used
19 when the type of subaddress is “User specified” and the coding
20 is BCD.
21
2-516
C.S0005-0-2 v1.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.
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.
18
2-517
C.S0005-0-2 v1.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 ANSI T1.607-1990, Section 4.5.10[8].
15 ANSI T1.607-1990, Section 4.5.10[8]. It is only used when the
16 type of subaddress is “User specified” and the coding is BCD.
21 for each character in the calling party subaddress.
25 8348 AD2.
26 When the SUBADDRESS_TYPE field is set to ‘010’, user-
31
2-518
C.S0005-0-2 v1.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 ANSI T1.607-1990, Section 4.5.14[8].
22 for each character in the connected subaddress.
26 8348 AD2.
32
2-519
C.S0005-0-2 v1.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.
13
2-520
C.S0005-0-2 v1.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.
24
2-521
C.S0005-0-2 v1.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.
24
2-522
C.S0005-0-2 v1.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 1
SDB 1
RLP_CAP_BLOB_LEN 3
RLP_CAP_BLOB 8X
RLP_CAP_BLOB_LEN
6 ACCESS_ENTRY_HO – Access Entry Handoff Support.

7 This field identifies the mobile station’s support for access
8 entry handoff (see 2.6.2.3). The mobile station shall set this
9 field to ‘1’ if access entry handoff is supported; otherwise, the
11 ACCESS_PROBE_HO – Access Probe Handoff Support.
2-523
C.S0005-0-2 v1.0
1 This field identifies the mobile station’s support for access

2 probe handoff (see 2.6.3.1.3.3). The mobile station shall set
3 this field to ‘1’ if access probe handoff is supported; otherwise,
5 ANALOG_SEARCH – Analog Search Support.
6 This field identifies the mobile station’s support for analog
7 searching (see 2.6.6.2.10). The mobile station shall set this
8 field to ‘1’ if analog searching is supported; otherwise, the
10 HOPPING_BEACON – Hopping Beacon Support.
11 This field identifies the mobile station’s support for hopping pilot
12 beacons. The mobile station shall set this field to ‘1’ if hopping
13 pilot beacons are supported; otherwise, this field shall be set to
14 ‘0’.
15 MAHHO – Mobile Assisted Hard Handoff Support.
16 This field identifies the mobile station’s support for mobile
17 assisted hard handoff. The mobile station shall set this field to
18 ‘1’.
19 PUF – Location Power Up Function Support.
20 This field identifies the mobile station’s support for location
21 power up function (see 2.6.4.1.7).
22 If MOB_P_REVp is equal to ‘00000101’, the mobile station shall
23 set this field to ‘1’; otherwise the mobile station shall set this
24 field as follows:
25 If the mobile station supports location power up function, the
26 mobile station shall set this field to ‘1’, otherwise, the mobile
28 ANALOG_553A – Analog TIA/EIA-553A Support.
29 This field identifies the mobile station’s compatibility with
30 TIA/EIA-553A[15]. The mobile station shall set this field to ‘1’.
31 QPCH – Quick Paging Channel Support.
32 This field identifies the mobile station’s support for the Quick
33 Paging Channel. The mobile station shall set this field to ‘1’ if
34 the Quick Paging Channel is supported; otherwise, the mobile
36 SLOTTED_TIMER – Slotted Timer Support.
37 This field identifies the mobile station’s support for the Slotted
38 Timer. The mobile station shall set this field to ‘1’ if the Slotted
39 Timer is supported; otherwise, the mobile station shall set this
41 CHS_SUPPORTED – Control Hold Mode supported indicator.
42 The mobile station shall set this field to ‘1’ to indicate that the
43 mobile station supports the Control Hold Mode; otherwise, the
2-524
C.S0005-0-2 v1.0
2 GATING_RATE_SET – Set of supported Reverse Pilot gating rates.

3 If CHS_SUPPORTED is set to ‘1’, the mobile station shall set
4 this field to value shown in Table 2.7.4.25-1 corresponding to
5 the set of supported reverse pilot gating rates; otherwise the
7
8 Table 2.7.4.25-1. Set of supported Reverse Pilot Gating

9 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
10
11 EXT_CAP_INCLUDED – Extended Capabilities Included indicator.

12 The mobile station shall set this field to ‘1’ to indicate that
13 extended capability indicators are included in this record;
15 MABO – Mobile Assisted Burst Operation capability indicator.
16 If EXT_CAP_INCLUDED is set to ‘1’, the mobile station shall set
17 this field to ‘1’ to indicate that it supports the Mobile Assisted
18 Burst Operation capability; otherwise, the mobile station shall
19 set this field to ‘0’.
20 SDB – Short Data Burst supported indicator.
21 If EXT_CAP_INCLUDED is set to ‘1’, the mobile station shall
22 set this field to ’1’ to indicate that it supports Short Data
23 Burst capability; otherwise, the mobile station shall set this
25 RLP_CAP_BLOB_LEN - RLP capability information length.
27 station does not support Radio Link Protocol; otherwise, it
28 shall set this field to the size of the RLP_CAP_BLOB field in
29 integer number of octets.
30 RLP_CAP_BLOB - Radio Link Protocol capability information block of bits.
31 If the RLP_CAP_BLOB_LEN field is set to ‘000’, the mobile
32 station shall omit this field; otherwise, the mobile station shall
33 set this field to the Radio Link Protocol capability information
34 block of bits, as shown in Table 2.7.4.25-2.
35
2-525
C.S0005-0-2 v1.0
1 Table 2.7.4.25-2. RLP Capability Information Block
Subfields Length
MAX_MS_NAK_ROUNDS_FWD 3
MAX_MS_NAK_ROUNDS_REV 3
RESERVED 2
2 MAX_MS_NAK-
3 ROUNDS_FWD - Maximum number of RLP NAK rounds supported by the
4 mobile station on the forward traffic channel.
5 The mobile station shall set this field to the maximum number
6 of NAK round(s) it supports on the forward traffic channel (BS
7 RLP transmitting function) (see TIA/EIA/IS-707-A-1[39]).
8 MAX_MS_NAK-
9 ROUNDS_REV - Maximum number of RLP NAK rounds supported by the
10 mobile station on the reverse traffic channel.
11 The mobile station shall include this field and set it to the
12 maximum number of NAK round(s) it supports on the reverse
13 traffic channel (MS RLP transmitting function) (see
14 TIA/EIA/IS-707-A-1[39]).
21 bits to ‘0’.
22
2-526
C.S0005-0-2 v1.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-527
C.S0005-0-2 v1.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
RESERVED_1 0 or 2
RESERVED 0 – 7 (as needed)
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.
18 otherwise the mobile station shall omit this field.
21 station supports the Dedicated Control Channel; otherwise,
23 DCCH Type-
24 specific fields – Fundamental Channel configuration capability information.
2-528
C.S0005-0-2 v1.0
1 If the DCCH_SUPPORTED field is set to ‘1’, the mobile station

3 otherwise the mobile station shall omit this field.
4 FOR_SCH_SUPPORTED – Forward Supplemental Channel supported indicator.
6 station supports the Forward Supplemental Channel;
8 FOR_SCH Type-
9 specific fields – Forward Supplemental Channel Configuration Capability
10 Information.
11 If the FOR_SCH_SUPPORTED field is set to ‘1’, the mobile
12 station shall include this field and set it as described in
13 2.7.4.27.3; otherwise the mobile station shall omit this field.
14 REV_SCH_SUPPORTED – Reverse Supplemental Channel supported indicator.
16 station supports the Reverse Supplemental Channel;
18 REV_SCH Type-
19 specific fields – Reverse Supplemental Channel Configuration capability
20 information.
21 If the REV_SCH_SUPPORTED field is set to ‘1’, the mobile
22 station shall include this field and set it as described in
23 2.7.4.27.4; otherwise the mobile station shall omit this field.
24 RESERVED_1 – Reserved bits.
25 If both the FOR_SCH_SUPPORTED and
26 REV_SCH_SUPPORTED fields are set to ‘0’, the mobile station
27 shall omit this field. Otherwise, the mobile station shall set

33 bits to ‘0’.
34 2.7.4.27.1 FCH Type-specific Fields
35 The Fundamental Channel configuration capability information included in the FCH Type-
36 specific fields contains the following subfields:
37
2-529
C.S0005-0-2 v1.0
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
2 FCH_FRAME_SIZE – Fundamental Channel Frame Size capability indicator.

3 If in addition to the 20 ms frame size the mobile station also
4 supports the 5 ms frame size on the Fundamental Channel,
5 the mobile station shall set this field to ‘1’; otherwise, the
7 FOR_FCH_LEN – Forward Fundamental Channel Configuration information
8 length.
9 The mobile station shall set this field to the number of 3 bit
10 units required to specify the length, in bits, of the
11 FOR_FCH_RC_MAP field.
12 FOR_FCH_RC_MAP – Forward Fundamental Radio Configuration information.
13 The mobile station shall set this field as described below to
14 indicate which Radio Configurations (see TIA/EIA/IS-2000-[2]
15 Table 3.1.3.1-1) are supported by the mobile station on the
16 Forward Fundamental Channel.
17 This field consists of the sequence of 1-bit indicators, each
18 indicating the mobile station support for specific Radio
19 Configuration. Bit positions of these indicators in the field
20 and corresponding Radio Configurations are specified in Table
21 2.7.4.27.1-1.
22 The mobile station shall set each indicator to ‘1’ if the
23 corresponding Radio Configuration on the Forward
24 Fundamental Channel is supported by the mobile station;
25 otherwise, the mobile station shall set the indicator to ‘0’. The
26 mobile station shall set any unused bits in the field to ‘0’.
2-530
C.S0005-0-2 v1.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.
12 Reverse Fundamental Channel.
17 2.7.4.27.1-2.
19 corresponding Radio Configuration on the Reverse
20 Fundamental Channel is supported by the mobile station;
23
2-531
C.S0005-0-2 v1.0
1 Table 2.7.4.27.1-2. Reverse Channel Radio Configurations Supported
Subfield Length (bits) Subfield Description

2-532
C.S0005-0-2 v1.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
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 TIA/EIA/IS-
20 2000-[2] Table 3.1.3.1-1) are supported by the mobile station
21 on the Forward Dedicated Control Channel.
26 2.7.4.27.1-1.
2-533
C.S0005-0-2 v1.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.
21 2.7.4.27.1-2.
23 corresponding Radio Configuration on the Reverse Dedicated
24 Control Channel is supported by the mobile station;
27
2-534
C.S0005-0-2 v1.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
RESERVED 6
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.
17 Forward Supplemental Channel.
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.
30 Forward Supplemental Channels supported by the mobile
31 station.
2-535
C.S0005-0-2 v1.0
1 If the FOR_SCH_NUM field is greater than zero, the mobile

2 station shall include one occurrence of the following 8 fields
3 for each Forward 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 FOR_TURBO-
8 _SUPPORTED – Forward Turbo Coding supported indicator.
9 If the mobile station supports Turbo Coding on this Forward
10 Supplemental Channel, it shall set this field to ‘1’; otherwise,
12 FOR_MAX_TURBO-
13 _BLOCK_SIZE – Forward maximum Turbo Coding block size.
14 If the field FOR_TURBO_SUPPORTED is set to ‘0’, the mobile
15 station shall omit this field; otherwise the mobile station shall
16 include this field and set it to the maximum block size allowed
17 for Turbo coding (see Table 2.7.4.27.3-1).
18 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, and 5, 8 and 9
7
0000 172 267
0001 360 552
0010 744 1128
0011 1512 2280
0100 3048 4584
0101 6120 9192
0110 12264 20712
2-536
C.S0005-0-2 v1.0
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)
14 The mobile station shall set this field to ‘000000’
15
2-537
C.S0005-0-2 v1.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
RESERVED 6
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 TIA/EIA/IS-2000-[2]
17 Reverse Supplemental Channel.
22 2.7.4.27.1-1.
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-538
C.S0005-0-2 v1.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
10 Supplemental Channel, it shall set this field to ‘1’; otherwise,
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).
29 The mobile station shall set this field to ‘000000’
30
2-539
C.S0005-0-2 v1.0
1 2.7.4.28 Extended Multiplex Option Information

3 Status Response Message to return multiplex option information about the mobile station.
2-540
C.S0005-0-2 v1.0
NUM_MO_FOR_FCH 4
NUM_MO_FOR_FCH occurrences of the following two-field
record:
MO_FOR_FCH 16
FOR_RATES_FCH 8
NUM_MO_REV_FCH 4
NUM_MO_REV_FCH occurrences of the following two-field
record:
MO_REV_FCH 16
REV_RATES_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-541
C.S0005-0-2 v1.0
RESERVED 0 - 7 (as needed)
3 NUM_MO_FOR_FCH – Number of Forward Fundamental Channel Multiplex Options.

5 Forward Fundamental Channel Multiplex Options supported
6 by the mobile station.
7 If NUM_MO_FOR_FCH is not equal to ‘0000’, the mobile

8 station shall include NUM_MO_FOR_FCH occurrences of the
9 following two fields for each supported Forward Fundamental
10 Channel multiplex option:
11 MO_FOR_FCH – Forward Fundamental Channel multiplex option.
12 The mobile station shall set this field to the Forward
13 Fundamental Channel multiplex option.
14 FOR_RATES_FCH – Forward Fundamental Channel transmission rates.
16 indicate which transmission rates are supported by the mobile
17 station on the Forward Fundamental Channel.
19 indicating the mobile station support for specific transmission
20 rate. Bit positions of these indicators in the field and
21 corresponding transmission rates are specified in Table
22 2.7.4.28-1 if MO_FOR_FCH is equal to 1, and Table 2.7.4.28-2
23 if MO_FOR_FCH is equal to 2.
25 corresponding transmission rate on the Forward Fundamental
26 Channel is supported by the mobile station; otherwise, the
27 mobile station shall set the indicator to ‘0’.
28
2-542
C.S0005-0-2 v1.0
1 Table 2.7.4.28-1. Forward Fundamental Channel

2 Transmission Rates for MO_FOR_FCH equal to 1
Length

9600 bps
4800 bps
2400 bps
1200 bps
RESERVED 4
4 Table 2.7.4.28-2. Forward Fundamental Channel

5 Transmission Rates for MO_FOR_FCH equal to 2
Length

14400 bps
7200 bps
3600 bps
1800 bps
RESERVED 4
7 NUM_MO_REV_FCH – Number of Reverse Fundamental Channel Multiplex Options.

9 Reverse Fundamental Channel Multiplex Options supported
11 If NUM_MO_REV_FCH is not equal to ‘0000’, the mobile

12 station shall include NUM_MO_REV_FCH occurrences of the
13 following two fields for each supported Reverse Fundamental
14 Channel multiplex option:
15 MO_REV_FCH – Reverse Fundamental Channel multiplex option.
16 The mobile station shall set this field to the Reverse
17 Fundamental Channel multiplex option.
2-543
C.S0005-0-2 v1.0
1 REV_RATES_FCH – Reverse Fundamental Channel transmission rates.

3 indicate which transmission rates are supported by the mobile
4 station on the Reverse Fundamental Channel.
6 indicating the mobile station support for specific transmission
7 rate. Bit positions of these indicators in the field and
8 corresponding transmission rates are specified in Table
9 2.7.4.28-3 if MO_REV_FCH is equal to 1, and Table 2.7.4.28-4
10 if MO_REV_FCH is equal to 2.
12 corresponding transmission rate on the Reverse Fundamental
13 Channel is supported by the mobile station; otherwise, the
14 mobile station shall set the indicator to ‘0’.
15
16 Table 2.7.4.28-3. Reverse Fundamental Channel

17 Transmission Rates for MO_REV_FCH equal to 1
Length

9600 bps
4800 bps
2400 bps
1200 bps
RESERVED 4
18
2-544
C.S0005-0-2 v1.0
1 Table 2.7.4.28-4. Reverse Fundamental Channel

2 Transmission Rates for MO_REV_FCH equal to 2
Length

14400 bps
7200 bps
3600 bps
1800 bps
RESERVED 4
4 NUM_MO_FOR_DCCH – Number of Forward Dedicated Control Channel Multiplex

5 Options.
7 Forward Dedicated Control Channel Multiplex Options
9 If NUM_MO_FOR_DCCH is not equal to ‘0000’, the mobile

10 station shall include NUM_MO_FOR_DCCH occurrence of the
11 following one field for each supported Forward Dedicated
12 Control Channel multiplex option:
13 MO_FOR_DCCH – Forward Dedicated Control Channel multiplex option.
15 Dedicated Control Channel multiplex option.
16 NUM_MO_REV_DCCH – Number of Reverse Dedicated Control Channel Multiplex
17 Options.
19 Reverse Dedicated Control Channel Multiplex Options
21 If NUM_MO_REV_DCCH is not equal to ‘0000’, the mobile

22 station shall include NUM_MO_REV_DCCH occurrence of the
23 following one field for each supported Reverse Dedicated
24 Control Channel multiplex option:
25 MO_REV_DCCH – Reverse Dedicated Control Channel multiplex option.
26 The mobile station shall set this field to the Reverse Dedicated
27 Control Channel multiplex option.
28
29 NUM_MO_FER_SCH – Number of Forward Supplemental Channel Multiplex Options.
2-545
C.S0005-0-2 v1.0
2 Reverse Supplemental Channel Multiplex Options supported
4 If NUM_MO_FER_SCH is not equal to ‘0000’, the mobile

5 station shall include NUM_MO_FER_SCH occurrence of the
6 following two fields:
7 FOR_SCH_ID – Forward Supplemental Channel identifier.
8 The mobile station shall set this field to specify the Forward
9 Supplemental Channel to which the Forward Supplemental
10 multiplex option supported by the mobile station corresponds.
11 MO_FOR_SCH – Forward Supplemental Channel multiplex option.
13 Supplemental Channel multiplex option associated with the
14 maximum data rate (see 2.2.2.2.1 of TIA/EIA/IS-2000.[3]) that
15 the mobile station supports1.
16 NUM_MO_REV_SCH – Number of Reverse Supplemental Channel Multiplex Options.
18 Reverse Supplemental Channel Multiplex Options supported
20 If NUM_MO_REV_SCH is not equal to ‘0000’, the mobile

21 station shall include NUM_MO_REV_SCH occurrence of the
22 following two fields:
23 REV_SCH_ID – Reverse Supplemental Channel identifier.
24 The mobile station shall set this field to specify the Reverse
25 Supplemental Channel to which the Reverse Supplemental
26 multiplex option supported by the mobile station corresponds.
27 MO_REV_SCH – Reverse Supplemental Channel multiplex option.
28 The mobile station shall set this field to the Reverse
29 Supplemental Channel multiplex option associated with the
30 maximum data rate (see 2.2.2.2.1 of TIA/EIA/IS-2000.[3]) that
31 the mobile station supports1.
36 bits to ‘0’.
37
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 TIA/EIA/IS-2000.[3].
2-546
C.S0005-0-2 v1.0
2 2.7.4.29 Geo-Location Information
3 This information record identifies the geo-location capabilities of the mobile station. The
4 mobile station shall use the following fixed-length format for the type-specific fields:
GEO_LOC 3
RESERVED 5
7 GEO_LOC – Geo-location.
8 The mobile station shall set this field to the value shown in Table
9 2.7.4.34-1.
10 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
001 IS-801 capable (Advanced Forward Link
Triangulation only)
010 IS-801 capable (Advanced Forward Link
Triangulation and Global Positioning
Systems)
011 Global Positioning Systems only
All other GEO_LOC_TYPE values are reserved.

13
2-547
C.S0005-0-2 v1.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 ‘00010’ (TACS 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

RESERVED 5
14
15 If BAND_CLASS specified in the Status Request Message is

16 equal to ‘00101’ (450 MHz NMT Band), this field consists of
17 the following subfields which are included in the information
18 record in the order shown:
19
2-548
C.S0005-0-2 v1.0
Length

2 The mobile station shall set each subfield to ‘1’ if the

3 corresponding sub-band class is supported by the mobile
4 station; otherwise, the mobile station shall set the subfield to
5 ‘0’.
7 The mobile station shall set all reserved bits to ‘0’.
8 When more band classes are defined, the reserved bits will be
9 used for the new corresponding subfields. Sufficient octets
10 will be added to this field to accommodate the new subfields.
11 All the undefined bits in an additional octet will be reserved
12 bits.
16
17
2-549
C.S0005-0-2 v1.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
17 TIA/EIA/IS-2000-[6]).
18 3.3.2 Encryption
19 If the base station supports mobile station authentication (see 3.3.1), it may also support
20 message encryption by providing the capability to send encryption control messages and
21 the ability to perform the operations of encryption and decryption as specified in 2.3.12.2.
22 3.3.3 Voice Privacy
23 If the base station supports mobile station authentication (see 3.3.1), it may also support
24 voice privacy using the private long code mask, as specified in 2.3.12.3.
25 3.4 Supervision
26 3.4.1 Access Channel
27 The base station shall continually monitor each active Access Channel. The base station
28 should provide control in cases of overload by using the Access Parameters Message.
29 3.4.2 Reverse Traffic Channel
30 The base station shall continually monitor each active Reverse Traffic Channel to determine
31 if the call is active. If the base station detects that the call is no longer active, the base
32 station shall declare loss of Reverse Traffic Channel continuity (see 3.6.4).
3-1
C.S0005-0-2 v1.0
1 3.5 Reserved
2 3.6 Call Processing
3 This section describes base station call processing. It contains frequent references to the
4 messages that flow between the base station and the mobile station. While reading this
5 section, it may be helpful to refer to the message formats (see 2.7 and 3.7), and to the call
6 flow examples (see Annex B). The values for the time and numeric constants used in this
7 section (e.g., T1b and N4m) are specified in Annex D.
8 Base station call processing consists of the following types of processing:

9 • Pilot and Sync Channel Processing - During Pilot and Sync Channel Processing, the
10 base station transmits the Pilot Channel and Sync Channel which the mobile station
11 uses to acquire and synchronize to the CDMA system while the mobile station is in
12 the Mobile Station Initialization State.
13 • Paging Channel Processing - During Paging Channel Processing, the base station
14 transmits the Paging Channel which the mobile station monitors to receive
15 messages while the mobile station is in the Mobile Station Idle State and the System
16 Access State.
17 • Access Channel Processing - During Access Channel Processing, the base station
18 monitors the Access Channel to receive messages which the mobile station sends
19 while the mobile station is in the System Access State.
20 • Traffic Channel Processing - During Traffic Channel Processing, the base station uses
21 the Forward and Reverse Traffic Channels to communicate with the mobile station
22 while the mobile station is in the Mobile Station Control on the Traffic Channel State.
23 3.6.1 Pilot and Sync Channel Processing

24 During Pilot and Sync Channel Processing, the base station transmits the Pilot and Sync
25 Channels which the mobile station uses to acquire and synchronize to the CDMA system
26 while the mobile station is in the Mobile Station Initialization State.
27 3.6.1.1 Preferred Set of CDMA Channels
28 The preferred set of frequency assignments are the CDMA Channels on which the mobile
29 station attempts to acquire the CDMA system (see TIA/EIA/IS-2000-[2]).
30 The base station shall support at least one member of the preferred set of frequency
31 assignments. The base station may support additional CDMA Channels.
32 3.6.1.2 Pilot Channel Operation
33 The Pilot Channel (see TIA/EIA/IS-2000-[2]) is a reference channel which the mobile station
34 uses for acquisition, timing, and as a phase reference for coherent demodulation.
35 The base station shall continually transmit a Pilot Channel for every CDMA Channel
36 supported by the base station, unless the base station is classified as a hopping pilot
37 beacon.
3-2
C.S0005-0-2 v1.0
1 3.6.1.3 Sync Channel Operation
2 The Sync Channel (see TIA/EIA/IS-2000-[2)[2]) provides the mobile station with system
3 configuration and timing information.
4 The base station shall transmit at most one Sync Channel for each supported CDMA
5 Channel. The base station shall support a Sync Channel on at least one member of the
6 preferred set of frequency assignments that it supports. The base station should support a
7 Sync Channel on every member of the preferred set of frequency assignments that it
8 supports.
9 If the base station operates in Band Class 0 or Band Class 3 and supports the Primary
10 CDMA Channel, then the base station shall transmit a Sync Channel on the Primary CDMA
11 Channel.
12 The base station shall continually send the Sync Channel Message on each Sync Channel
13 that the base station transmits.
14 3.6.2 Paging Channel and Quick Paging Channel Processing
15 3.6.2.1 Paging Channel Procedures

16 During Paging Channel Processing, the base station transmits the Paging Channel (see
17 TIA/EIA/IS-2000-[2)[2]) which the mobile station monitors to receive messages while the
18 mobile station is in the Mobile Station Idle State and the System Access State.
19 The base station may transmit up to seven Paging Channels on each supported CDMA
20 Channel.
21 For each Paging Channel that the base station transmits, the base station shall continually
22 send valid Paging Channel messages (see 3.7.2), which may include the Null Message (see
23 TIA/EIA/IS-2000-[4)[4]).
24 The base station shall not send any message which is not completely contained within two
25 consecutive Paging Channel slots, unless the processing requirements for the message
26 explicitly specify a different size limitation.1
27 3.6.2.1.1 CDMA Channel Determination
28 To determine the mobile station’s assigned CDMA Channel, the base station shall use the
29 hash function specified in 2.6.7.1 with the following inputs:
30 • IMSI_S based on the IMSI with which the mobile station registered (see 2.3.1)
31 • Number of CDMA Channels on which the base station transmits Paging Channels.
1See, for example, TIA/EIA-637-A which specifies processing requirements for the Data Burst
Message.
3-3
C.S0005-0-2 v1.0
1 3.6.2.1.2 Paging Channel Determination
2 To determine the mobile station’s assigned Paging Channel, the base station shall use the
3 hash function specified in 2.6.7.1 with the following inputs:
5 • Number of Paging Channels which the base station transmits on the mobile station’s
6 assigned CDMA Channel.
7 3.6.2.1.3 Paging Slot Determination
8 To determine the assigned Paging Channel slots for a mobile station with a given slot cycle
9 index, the base station shall select a number PGSLOT using the hash function specified in
10 2.6.7.1 with the following inputs:
12 • Maximum number of Paging Channel slots (2048).
13 The assigned Paging Channel slots for the mobile station are those slots for which
14 (t/4  − PGSLOT) mod (16 × T) = 0,
15 where t is the System Time in frames, and T is the slot cycle length in units of 1.28 seconds
16 given by
17 T = 2i,
18 where i is the slot cycle index.
19 When the base station is able to determine that the mobile station is operating in the
20 slotted mode and is able to determine the mobile station’s preferred slot cycle index, the
21 base station uses for the mobile station’s slot cycle index the smaller of the mobile station’s
22 preferred slot cycle index and the maximum slot cycle index.
23 When the base station is not able to determine whether the mobile station is operating in
24 the slotted mode, or the base station is not able to determine the mobile station’s preferred
25 slot cycle index, the base station uses for the mobile station’s slot cycle index the smaller of
26 the maximum slot cycle index and 1.
27 3.6.2.1.4 Message Transmission and Acknowledgment Procedures
28 The Paging Channel acknowledgment procedures facilitate the reliable exchange of

29 messages between the base station and the mobile station on the f-csch and r-csch. The
30 acknowledgment procedures and requirements are described in 3.1.1.2 and 3.1.2.1 of
31 TIA/EIA/IS-2000-4.[4].
32 3.6.2.2 Overhead Information
33 The base station sends overhead messages to provide the mobile station with the
34 information that it needs to operate with the base station.
35 The base station shall maintain a configuration sequence number (CONFIG_SEQ), and shall
36 increment CONFIG_SEQ modulo 64 whenever the base station modifies the following
3-4
C.S0005-0-2 v1.0
1 messages:
3 2. Neighbor List Message (Band Class 0 only)
4 3. CDMA Channel List Message
6 5. Extended Neighbor List Message (band classes other than Band Class 0)
9 8. User Zone Identification Message
10 9. Private Neighbor List Message
12 11. Extended CDMA Channel List Message
13 The base station shall maintain an access configuration sequence number

14 (ACC_CONFIG_SEQ), and shall increment ACC_CONFIG_SEQ modulo 64 whenever the base
15 station modifies the Access Parameters Message.
16 On each of the Paging Channels the base station transmits, the base station shall send
17 each of the following system overhead messages at least once per T1b seconds:
19 2. CDMA Channel List Message
22 If the base station operates in Band Class 1, Band Class 3, or Band Class 4, and
23 MIN_P_REV is less than six, the base station shall send the Extended Neighbor List Message
24 and may also send the General Neighbor List Message. If BAND_CLASS is equal to ‘00000’,
25 the base station shall send the Neighbor List Message, and may also send the General
26 Neighbor List Message. If the base station is sending the Neighbor List Message, it shall
27 send it at least once per T1b seconds. If the base station is sending the Extended Neighbor
28 List Message, it shall send it at least once per T1b seconds. If the base station is sending
29 the General Neighbor List Message, it shall send it at least once per T1b seconds.
30 If the base station uses addressing modes requiring use of only the IMSI_M_S, independent
31 of values of the IMSI_M_11_12 and MCC_M, the base station shall set IMSI_T_SUPPORTED
32 to ‘0’, MCC to ‘1111111111’, and IMSI_11_12 to ‘1111111’ in the Extended System
33 Parameters Message.
34 If the base station sets IMSI_T_SUPPORTED to ‘1’, the base station shall not set
35 PREF_MSID_TYPE to ‘00’ in the Extended System Parameters Message.
3-5
C.S0005-0-2 v1.0
1 The base station may send a Global Service Redirection Message on any given Paging
2 Channel. If the message is sent, the base station shall send it at least once per T1b
3 seconds.
4 If P_REV is greater than or equal to six, the base station may send an Extended Global
5 Service Redirection Message on any given Paging Channel. If the message is sent, the base
6 station shall send it at least once per T1b seconds. The base station may send this message
7 to redirect only those mobile stations with MOB_P_REV equal to or greater than six.
8 When both the Global Service Redirection Message and the Extended Global Service
9 Redirection Message are sent, the base station shall use the Global Service Redirection
10 Message for mobile stations with MOB_P_REV less than six, and shall use the Extended
11 Global Service Redirection Message for mobile stations with MOB_P_REV equal to or greater
12 than six. When only the Global Service Redirection Message is sent and this message is for
13 mobile station with MOB_P_REV less then six, the base station shall set EXCL_P_REV_MS
14 to ‘1’.
15 If only the Global Service Redirection Message is sent and this message is for redirecting all
16 mobile stations, the base station shall set EXCL_P_REV_MS to ‘0’.
17 The base station may send a User Zone Identification Message on any given Paging Channel.
18 If the message is sent, the base station shall send it at least once per T1b seconds.
19 The base station may send a Private Neighbor List Message on any given Paging Channel. If
20 the message is sent, the base station shall send it at least once per T1b seconds.
21 The base station may send an Extended CDMA Channel List Message on any given Paging
22 Channel. If the message is sent, the base station shall send it at least once per T1b
23 seconds.
24 3.6.2.3 Mobile Station Directed Messages
25 The base station shall use the following rules for selecting the Paging Channel slot in which
26 to send a message to a mobile station:
27 • If the base station is able to determine that the mobile station is operating in the
28 non-slotted mode, the base station may send the message to the mobile station in
29 any Paging Channel slot.
30 • If the base station is able to determine that the mobile station is operating in the
31 slotted mode and is able to determine the mobile station’s slot cycle index (see
32 2.6.2.1.1.3), the base station shall send the message at least once in an assigned
33 Paging Channel slot for the mobile station (see 3.6.2.1.3), with the position within
34 the slot subject to the following limitations:
35 – If the mobile station has registered with a class 0 IMSI, the base station shall
36 not send the message in the assigned Paging Channel slot after sending a
37 General Page Message with CLASS_0_DONE set to ‘1’ in that slot.
3-6
C.S0005-0-2 v1.0
1 – If the mobile station has been assigned a TMSI, the base station shall not send
2 the message in the assigned Paging Channel slot after sending a General Page
3 Message with TMSI_DONE set to ‘1’ in that slot.
4 • If the base station is not able to determine whether the mobile station is operating in
5 the non-slotted mode, or the base station is not able to determine the mobile
6 station’s slot cycle index, the base station shall assume that the mobile station is
7 operating in the slotted mode with a slot cycle index which is the smaller of
8 MAX_SLOT_CYCLE_INDEX and 1. The base station shall send the message at least
9 once in an assigned Paging Channel slot for the mobile station (see 3.6.2.1.3), with
10 the position within the slot subject to the following limitations:
17 – If the mobile station has been assigned a TMSI, the base station shall not send
18 the message in the assigned Paging Channel slot after sending a General Page
19 Message with TMSI_DONE set to ‘1’ in that slot.
20 The base station should send at least one General Page Message in each Paging Channel
21 slot. The base station shall not omit a General Page Message in two adjacent slots. The
22 base station should send messages directed to mobile stations operating in the slotted mode
23 as the first messages in the slot.
24 If the base station sends a General Page Message with ORDERED_TMSIS set to ‘1’ in a slot,
25 the base station shall order page records with PAGE_CLASS equal to ‘10’ in ascending order
26 such that if a particular TMSI_CODE value for one page record is greater than the
27 TMSI_CODE value for another page record, the page record with the greater TMSI_CODE
28 value is sent later in the slot.
29 The base station may send the following messages directed to a mobile station on the f-
30 csch. If the base station sends a message, the base station shall comply with the specified
31 requirements for sending the message, if any:
32 1. Abbreviated Alert Order
33 2. Audit Order
34 3. Authentication Challenge Message
35 4. Base Station Challenge Confirmation Order
36 5. Channel Assignment Message
38 7. Extended Channel Assignment Message
3-7
C.S0005-0-2 v1.0
1 9. General Page Message
2 10. Intercept Order
4 12. Lock Until Power-Cycled Order: The base station should send this order in an
5 unassured mode.
6 13. Maintenance Required Order
7 14. PACA Message
8 15. Registration Accepted Order
9 16. Registration Rejected Order
10 17. Registration Request Order
11 18. Release Order
12 19. Reorder Order
13 20. Retry Order
14 21. Service Redirection Message
15 22. Slotted Mode Order
16 23. SSD Update Message
17 24. Status Request Message
18 25. TMSI Assignment Message
19 26. Unlock Order: The base station should send this order in unassured mode.
20 27. User Zone Reject Message.
21 3.6.2.4 Broadcast Messages

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 for selecting the Paging Channel slot in which to send a
28 broadcast Data Burst Message.
29 3.6.2.4.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’.
3-8
C.S0005-0-2 v1.0
1 3.6.2.4.1.1 General Overview
2 The base station may transmit Data Burst Messages directed to broadcast addresses. Since
3 mobile stations operating in slotted mode do not constantly monitor a Paging Channel, it is
4 necessary to use special procedures to ensure that mobile stations operating in the slotted
5 mode are able to receive the message. The base station may either send a broadcast
6 message in many slots, or may send a broadcast message in a predetermined paging slot.
7 This single transmission of the pending broadcast message may be announced by a
8 preceding “broadcast page”. A broadcast page is a General Page Message record with the
9 PAGE_CLASS field set to ‘11’.
10 If pending transmission of the broadcast message is announced by the broadcast page,

11 mobile stations use the BC_ADDR and the BURST_TYPE fields of the broadcast page record
12 to determine whether or not to receive the announced broadcast message. The base station
13 sets the value of the BC_ADDR according to the requirements of the standards related to
14 the BURST_TYPE. There is a predetermined timing relationship between the sending of the
15 broadcast page and the sending of the related broadcast message. This timing relationship
16 allows mobile stations to determine which slot to monitor in order to receive the broadcast
17 message.
18 To reduce the overhead for sending broadcast pages or broadcast messages, a base station
19 may use periodic broadcast paging (see 3.6.2.4.1.2.1.2). When periodic broadcast paging is
20 enabled, broadcast pages or broadcast messages are sent only once during a broadcast
21 paging cycle. Mobile stations that are operating in the slotted mode and are configured to
22 receive broadcast messages monitor the paging channel during the slot in which the
23 broadcast pages or broadcast messages are sent. For the purpose of periodic broadcast
24 paging, system time is divided into broadcast paging cycles, each having a duration of (B +
25 3) Paging Channel slots, where B is a power of two. In each broadcast paging cycle, the
26 first paging slot may contain broadcast pages or broadcast messages.
27 3.6.2.4.1.2 Requirements for Sending Broadcast Messages
28 3.6.2.4.1.2.1 Broadcast Delivery Options
29 When transmitting broadcast messages that are to be received by mobile stations operating
30 in the slotted mode, the base station shall use one of the two following procedures to
31 transmit a broadcast message.
32 3.6.2.4.1.2.1.1 Method 1: Multi-Slot Broadcast Message Transmission
33 The base station may send a broadcast message using this method without regard to
34 whether periodic broadcast paging is enabled or disabled (see 3.6.2.4.1.2.3).
35 When using this method, the base station shall send the broadcast message in a sufficient
36 number of paging slots such that it may be received by any mobile station that is operating
37 in the slotted mode. For example, the base station may send the broadcast message in M
38 successive paging slots where M is the number of slots in a maximum paging cycle as
39 defined in 2.6.2.1.1.3.3.
3-9
C.S0005-0-2 v1.0
1 3.6.2.4.1.2.1.2 Method 2: Periodic Broadcast Paging
2 If the base station sends a broadcast message using this method, then the base station
3 shall enable periodic broadcast paging (see 3.6.2.4.1.2.3).
4 To deliver a broadcast message using this method, the base station should perform the
5 following:
6 • If the number and size of the broadcast messages waiting to be sent are such that
7 the messages can be sent in a single slot, the base station should send the
8 broadcast messages in the first slot of the next broadcast paging cycle (see
9 2.6.2.1.1.3.3).
10 • If there is a single broadcast message waiting to be sent, the base station should
11 send the broadcast message beginning in the first slot of the next broadcast paging
12 cycle (see 2.6.2.1.1.3.3).
13 • Otherwise, the base station should first include a broadcast page for each broadcast
14 message to be sent, in a General Page Message that is sent in the first slot of the
15 next broadcast paging cycle (see 2.6.2.1.1.3.3). The base station should then send
16 the related broadcast messages in the paging slots specified in 3.6.2.4.1.2.4.
17 3.6.2.4.1.2.2 Duplicate Broadcast Message Transmission
18 If the base station sends a broadcast message or a broadcast page and an associated
19 broadcast message more than once when periodic broadcast paging is enabled (see
20 3.6.2.4.1.2.3), then all repetitions of the broadcast message or the broadcast page and the
21 associated broadcast message should be sent within 4 × (B + 3) paging slots of the paging
22 slot in which the broadcast message or broadcast page was first sent. (B + 3 is the duration
23 of the broadcast paging cycle as defined in 2.6.2.1.1.3.3).
24 When a base station sends a broadcast message or a broadcast page when periodic
25 broadcast paging is enabled (see 3.6.2.4.1.2.3), and the base station has a second, different
26 broadcast message to send which contains identical BURST_TYPE and BC_ADDR fields,
27 then the base station shall wait 4 × (B + 3) paging slots after the first slot of the broadcast
28 paging cycle containing the final sending of the first broadcast message or broadcast page
29 before sending the second, different broadcast message or related broadcast page.
30 3.6.2.4.1.2.3 Periodic Broadcast Paging

31 The base station uses the BCAST_INDEX field of the Extended System Parameters Message
32 to specify the current state of periodic broadcast paging to all mobile stations.
33 To enable periodic broadcast paging, the base station shall set the BCAST_INDEX field of
34 the Extended System Parameters Message to an unsigned 3-bit number in the range 1-7,
35 equal to the broadcast slot cycle index as defined in 2.6.2.1.1.3.3. The value of the
36 BCAST_INDEX field may exceed the value of the MAX_SLOT_CYCLE_INDEX field sent in the
37 System Parameters Message.
38 To indicate that periodic broadcast paging is either disabled or is not supported by the base
39 station, the base station shall set the BCAST_INDEX field to ‘000’.
3-10
C.S0005-0-2 v1.0
1 3.6.2.4.1.2.4 Broadcast Message Slot Determination
2 When a base station uses broadcast paging, it shall determine the slot in which to send the
3 corresponding broadcast message using the following procedures:
4 • The base station shall consider a broadcast page to have been sent in the paging
5 slot in which the General Page Message containing the broadcast page began.
6 • The reference slot is defined as the paging slot in which the broadcast page was
7 sent.
8 • Let n represent the ordinal number of the broadcast page relative to other broadcast
9 pages that are contained in the same General Page Message (n = 1, 2, 3,...). The
10 base station shall send the broadcast message announced by broadcast page n in
11 the paging slot that occurs n × 3 paging slots after the reference slot.
12 3.6.2.5 Quick Paging Channel Processing
13 The base station may support a Quick Paging Channel. The base station may transmit up
14 to three Quick Paging Channels on each supported CDMA Channel.
15 When a Quick Paging Channel is supported, the base station shall transmit paging
16 indicators to the mobile station in the assigned positions in the assigned Quick Paging
17 Channel slot. The base station shall set the paging indicators to “ON” if the mobile station
18 is operating in the slotted mode and is to receive the Paging Channel in the assigned Paging
19 Channel slot following its assigned Quick Paging Channel slot.
20 When the base station changes CONFIG_MSG_SEQ, the base station should set the paging
21 indicators for all mobile stations to “ON” for each Quick Paging Channel slot for a time
22 interval T (in units of 1.28 seconds), such that
23 T = N × 2MAX_SLOT_CYCLE_INDEX,
24 where N is an integer greater than or equal to one.
25 If the base station supports configuration change indicators on the Quick Paging Channel,
26 when the base station changes CONFIG_MSG_SEQ, the base station shall set all
27 configuration change indicators to “ON” for each Quick Paging Channel slot for a time
28 interval of T31m seconds. At all other times, the base station shall set all configuration
29 change indicators to “OFF”.
30 If the base station does not support configuration change indicators on the Quick Paging
31 Channel, then the base station shall set all configuration change indicators to “OFF”.
32 When the base station sends a broadcast message using Multi-Slot Broadcast Message
33 Transmission (see 3.6.2.4.1.2.1.1), the base station should set all paging indicators to “ON”
34 for the Quick Paging Channel slot which begins 100 ms prior to the beginning of the Paging
35 Channel slot in which the broadcast message begins.
36 The base station shall set all reserved indicators to “OFF”.
37 3.6.2.5.1 Quick Paging Channel Determination
38 To determine the mobile station’s assigned Quick Paging Channel, the base station shall
3-11
C.S0005-0-2 v1.0
1 use the hash function specified in 2.6.7.1 with the following inputs:
3 • Number of Quick Paging Channels which the base station transmits on the mobile
4 station’s assigned CDMA Channel.
5 3.6.2.5.2 Quick Paging Channel Slot Determination
6 The mobile station’s assigned Quick Paging Channel slots are those slots for which
7 ((t+5)/4 − PGSLOT) mod (16 × T) = 0,
8 where t is the System Time in frames, PGSLOT is selected in the range 0 to 2047 by using
9 the hash function specified in 2.6.7.1, and T is the slot cycle length in units of 1.28 seconds
10 such that
11 T = 2i,
12 and i is the slot cycle index.
13 3.6.2.5.3 Paging Indicator Position Determination
14 To determine the mobile station’s assigned paging indicators, the base station shall use the
15 same formula as used by the mobile station (see 2.6.2.1.2.2).
16 3.6.2.5.4 Configuration Change Indicator Position Determination
17 Configuration change indicators are transmitted on the first Quick Paging Channel.
19 positions of the first pair of configuration change indicators in a Quick Paging Channel slot
20 shall be the last two bits in the first 40 ms half of the Quick Paging Channel slot. The bit
21 positions of the second pair of configuration change indicators in a Quick Paging Channel
22 slot shall be the last two bits in the Quick Paging Channel slot.
24 positions of the first four configuration change indicators in a Quick Paging Channel slot
25 shall be the last four bits in the first 40 ms half of the Quick Paging Channel slot. The bit
26 position of the second four configuration change indicators in a Quick Paging Channel slot
27 shall be the last four bits in the Quick Paging Channel slot.
28 3.6.2.5.5 Reserved Indicator Positions
29 On the first Quick Paging Channel, if the Quick Paging Channel data rate is 2400 bps
30 (indicator rate is 4800 bps), the reserved indicator positions are described as follows:
31 • The two Quick Paging Channel bit positions prior to the last two bits in the first 40
32 ms half of a Quick Paging Channel slot are reserved. The two Quick Paging Channel
33 bit positions prior to the last two bits in a Quick Paging Channel slot are also
34 reserved.
35 On the first Quick Paging Channel, if the Quick Paging Channel data rate is 4800 bps
36 (indicator rate is 9600 bps), the reserved indicator positions are described as follows:
3-12
C.S0005-0-2 v1.0
1 • The four Quick Paging Channel bit positions prior to the last four bits in the first
2 40 ms half of a Quick Paging Channel slot are reserved. The four Quick Paging
3 Channel bit positions prior to the last four bits in a Quick Paging Channel slot are
4 also reserved.
5 On Quick Paging Channels other than the first Quick Paging Channel, if the Quick Paging
6 Channel data rate is 2400 bps (indicator rate is 4800 bps), the reserved indicator positions
7 are described as follows:
8 • The last four Quick Paging Channel bit positions in the first 40 ms half of a Quick
9 Paging Channel slot are reserved. The last four Quick Paging Channel bit positions
10 in a Quick Paging Channel slot are also reserved.
11 On Quick Paging Channels other than the first Quick Paging Channel, if the Quick Paging
12 Channel data rate is 4800 bps (indicator rate is 9600 bps), the reserved indicator positions
13 are described as follows:
14 • The last eight Quick Paging Channel bit positions in the first 40 ms half of a Quick
15 Paging Channel slot are reserved. The last eight Quick Paging Channel bit positions
16 in a Quick Paging Channel slot are also reserved.
17 3.6.3 Access Channel Processing

18 During Access Channel Processing, the base station monitors the Access Channel to receive
19 messages which the mobile station sends while the mobile station is in the System Access
20 State.
21 Each Access Channel is associated with a Paging Channel. Up to 32 Access Channels can
22 be associated with a Paging Channel. The number of Access Channels associated with a
23 particular Paging Channel is specified in the Access Parameters Message sent on that
24 Paging Channel.
25 The base station shall continually monitor all Access Channels associated with each Paging
26 Channel that the base station transmits.
27 3.6.3.1 Reserved
28 3.6.3.2 Reserved
29 3.6.3.3 Response to Page Response Message

30 If the base station receives a Page Response Message, the base station should send a
31 Channel Assignment Message, an Extended Channel Assignment Message, or a Release
32 Order. The base station may also start authentication procedures (see 2.3.12), start TMSI
33 assignment procedures (see 2.3.15), send a Data Burst Message, or request status
34 information records with the Status Request Message. If the base station is operating with
35 the mobile station in Band Class 0, the base station may also request the status
36 information records with the Status Request Order.
37 If the base station sends the Extended Channel Assignment Message, the base station may
38 include more than one pilot to be in the Active Set.
3-13
C.S0005-0-2 v1.0
1 If the base station sends a Channel Assignment Message or an Extended Channel

2 Assignment Message, the base station shall perform the following:
3 • If the message directs the mobile station to a CDMA Traffic Channel, the base
4 station shall begin Traffic Channel Processing (see 3.6.4) for the mobile station.
5 • If the message directs the mobile station to an 800 MHz wide analog voice channel,
6 the base station shall follow the procedure described in TIA/EIA/IS-2000-6.[6].
7 • If the message directs the mobile station to an 800 MHz narrow analog voice
8 channel, the base station shall follow the procedure described in 3.6.5A of
9 TIA/EIA/IS-91-A[28].
10 • Layer 3 shall send a mobile station inactive on common channel indication to Layer 2
11 (see 3.1.1.2.2 of TIA/EIA/IS-2000-[4)[4]).
12 3.6.3.4 Response to Orders
13 No requirements.
14 3.6.3.5 Response to Origination Message

15 If the base station receives an Origination Message, the base station should send a Channel
16 Assignment Message, an Extended Channel Assignment Message, an Intercept Order, a
17 Reorder Order, a Release Order, a PACA Message, a Service Redirection Message, or a Retry
18 Order. The base station may also commence authentication procedures (see 2.3.12) or
19 TMSI assignment procedures (see 2.3.15). The base station may also request status
20 information records with the Status Request Message. If the base station is operating with
21 the mobile station in Band Class 0, the base station may also request status information
22 records with the Status Request Order.
23 If the base station sends the Extended Channel Assignment Message, the base station may
24 include more than one pilot to be in the Active Set.
25 If the base station sends a Channel Assignment Message or an Extended Channel
26 Assignment Message, the base station shall perform the following:
27 • If the message directs the mobile station to a CDMA Traffic Channel, the base
28 station shall begin Traffic Channel Processing (see 3.6.4) for the mobile station.
29 • If the message directs the mobile station to an 800 MHz wide analog voice channel,
30 the base station shall follow the procedure described in TIA/EIA/IS-2000-2.[2].
31 • If the message directs the mobile station to an 800 MHz narrow analog voice
32 channel, the base station shall follow the procedure described in 3.6.5A of
33 TIA/EIA/IS-91-A[28].
34 • The base station shall raise a mobile station inactive on common channel indication
35 for the mobile station.
36 If the base station sends a Channel Assignment Message, the base station shall not set
37 RESPOND equal to ‘0’ when ASSIGN_MODE = ‘001’, ASSIGN_MODE = ‘010’, or
38 ASSIGN_MODE = ‘101’. If the base station sends an Extended Channel Assignment
3-14
C.S0005-0-2 v1.0
1 Message, the base station shall not set RESPOND equal to ‘0’ when ASSIGN_MODE = ‘001’
2 or ASSIGN_MODE = ‘010’
3 3.6.3.6 Response to Registration Message

4 If the base station receives a Registration Message, the base station may send a Registration
5 Accepted Order, a Registration Rejected Order, or a Service Redirection Message. The base
6 station may also start authentication procedures (see 2.3.12), start TMSI assignment
7 procedures (see 2.3.15), or request status information records with the Status Request
8 Message. If the base station is operating with the mobile station in Band Class 0, the base
9 station may also request the status information records with a Status Request Order.
10 If the Registration Message specifies a power-down registration, Layer 3 shall send a mobile
11 station inactive on common channel indication to Layer 2 (see 3.1.1.2.2 of TIA/EIA/IS-2000-
12 [4)[4]).
13 3.6.3.7 Response to Data Burst Message
14 No requirements.
15 3.6.3.8 Reserved
16 3.6.3.9 Reserved
17 3.6.3.10 Service Redirection

18 If the base station sends a Service Redirection Message or a Global Service Redirection
19 Message to the mobile station, Layer 3 shall send a mobile station inactive on common
20 channel indication to Layer 2 (see 3.1.1.2.2 of TIA/EIA/IS-2000-[4)[4]).
21 3.6.4 Traffic Channel Processing

22 During Traffic Channel Processing, the base station uses the Forward and Reverse Traffic
23 Channels to communicate with the mobile station while the mobile station is in the Mobile
25 Traffic Channel processing consists of the following substates:

26 • Traffic Channel Initialization Substate - In this substate, the base station begins
27 transmitting on the Forward Traffic Channel and receiving on the Reverse Traffic
28 Channel.
29 • Waiting for Order Substate - In this substate, the base station sends the Alert With
30 Information Message to the mobile station.
31 • Waiting for Answer Substate - In this substate, the base station waits for the Connect
32 Order from the mobile station.
33 • Conversation Substate - In this substate, the base station exchanges Traffic Channel
34 frames with the mobile station in accordance with the current service configuration.
35 • Release Substate - In this substate, the base station disconnects the call.
3-15
C.S0005-0-2 v1.0
1 3.6.4.1 Special Functions and Actions
2 The base station performs the following special functions and actions in one or more of the
3 Traffic Channel processing substates:
4 3.6.4.1.1 Forward Traffic Channel Power Control
5 When the base station enables Forward Traffic Channel power control, the mobile station
6 reports frame error rate statistics to the base station using the Power Measurement Report
7 Message.
8 The base station may enable Forward Traffic Channel power control using the System
9 Parameters Message sent on the Paging Channel and the Power Control Parameters Message
10 sent on the Forward Traffic Channel. The base station may enable periodic reporting which
11 causes the mobile station to report frame error rate statistics at specified intervals. The
12 base station may also enable threshold reporting which causes the mobile station to report
13 frame error rate statistics when the frame error rate reaches a specified threshold.2
14 The base station may use the reported frame error rate statistics to adjust the transmit
15 power of the Forward Traffic Channel.
16 3.6.4.1.2 Service Configuration and Negotiation
17 During Traffic Channel operation, the mobile station and base station communicate
18 through the exchange of Forward and Reverse Traffic Channel Configurations. The mobile
19 station and base station use a common set of attributes for building and interpreting Traffic
20 Channel frames. This set of attributes, referred to as a service configuration, consists of
21 both negotiable and non-negotiable parameters.
22 The set of negotiable service configuration parameters consists of the following:
23 1. Forward and Reverse Multiplex Options: These control the way in which the
24 information bits of the Forward and Reverse Traffic Channel frames, respectively,
25 are divided into various types of traffic, such as signaling traffic, primary traffic
26 and secondary traffic. A multiplex option together with a radio configuration
27 specifies the frame structures and transmission rates (see, for example,
28 2.2.4.4.1.3 of TIA/EIA/IS-2000- [3]). The Multiplex Options which support
29 Supplemental Code Channel transmission and Supplemental Channel
30 transmission on the Forward and Reverse Traffic Channels are included in
31 TIA/EIA/IS-2000-[3]. Invocation of Supplemental Code Channel operation on the
32 Forward or Reverse Traffic Channels occurs by transmission of the Supplemental
33 Channel Request Message, the Supplemental Channel Assignment Message, and
34 the General Handoff Direction Message. The Multiplex Options which support
35 Supplemental Code Channel transmission and Supplemental Channel
36 transmission on the Forward and Reverse Traffic Channels are included in
37 TIA/EIA/IS-2000-[3]. The multiplex option used for the Forward Traffic Channel
2In this section the term base station may imply multiple cells or sectors.
3-16
C.S0005-0-2 v1.0
1 can be the same as that used for the Reverse Traffic Channel, or it can be
2 different.
3 2. Forward and Reverse Traffic Channel Configurations: These include the radio
4 configurations and other necessary attributes for the Forward and Reverse Traffic
5 Channels. The Traffic Channel Configuration used can be different for the
6 Forward and Reverse Traffic Channels or it can be the same.
7 3. Forward and Reverse Traffic Channel Transmission Rates: These are the
8 transmission rates actually used for the Forward and Reverse Traffic Channels,
9 respectively. The transmission rates for the Forward Traffic Channel can include
10 all of the transmission rates supported by the radio configuration associated with
11 the Forward Traffic Channel multiplex option, or a subset of the supported rates.
12 Similarly, the transmission rates used for the Reverse Traffic Channel can include
13 all rates supported by the radio configuration associated with the Reverse Traffic
14 Channel multiplex option, or a subset of the supported rates. The transmission
15 rates used for the Forward Traffic Channel can be the same as those used for the
16 Reverse Traffic Channel, or they can be different.
17 4. Service Option Connections: These are the services in use on the Traffic Channel.
18 There can be multiple service option connections. It is also possible that there is
19 no service option connection, in which case the base station uses the Forward
20 Traffic Channel as follows:
21 • Sends signaling traffic and null traffic on the Forward Fundamental

22 Channel.
23 • Sends signaling traffic on the Forward Dedicated Control Channel.
24 • Sends power control bits on the Forward Fundamental Channel if

25 FPC_PRI_CHAN is set to ‘0’; sends power control bits on the Forward
26 Dedicated Control Channel if FPC_PRI_CHAN is set to ‘1’.
27 Associated with each service option connection are a service option, a Forward
28 Traffic Channel traffic type, a Reverse Traffic Channel traffic type, and a service
29 option connection reference. The associated service option formally defines the
30 way in which traffic bits are processed by the mobile station and base station. The
31 associated Forward and Reverse Traffic Channel traffic types specify the types of
32 traffic used to support the service option. A service option can require the use of a
33 particular type of traffic, such as primary or secondary, or it can accept more than
34 one traffic type. A service option can be one-way, in which case it can be
35 supported on the Forward Traffic Channel only or the Reverse Traffic Channel
36 only. Alternatively, a service option can be two-way, in which case it can be
37 supported on the Forward and Reverse Traffic Channels simultaneously.
38 Connected service options can also invoke operation on Supplemental Code
39 Channels in either one or both of the Forward and Reverse Traffic Channels by
40 negotiating a multiplex option that supports operation on Supplemental Code
41 Channels (see TIA/EIA/IS-2000-[3] for Multiplex Options applicable to
42 Supplemental Code Channels), and by using the appropriate Supplemental Code
43 Channel related messages (i.e., the Supplemental Channel Request Message, the
3-17
C.S0005-0-2 v1.0
1 Supplemental Channel Assignment Message, and the General Handoff Direction

2 Message). After Supplemental Code Channels have been assigned by the base
3 station, the connected service option can transmit primary and/or secondary
4 traffic on Supplemental Code Channels. Connected service options can also invoke
5 operation on Supplemental Channels in either one or both of the Forward and
6 Reverse Traffic Channels by negotiating a multiplex option that supports operation
7 on Supplemental Channels (see TIA/EIA/IS-2000-[3] for Multiplex Options
8 applicable to Supplemental Channels) and by using the appropriate Supplemental
9 Channel related messages (i.e., the Supplemental Channel Request Message, the
10 Universal Handoff Direction Message, the Supplemental Channel Request Mini
11 Message, the Extended Supplemental Channel Assignment Message, the Forward
12 Supplemental Channel Assignment Mini Message, and the Reverse Supplemental
13 Channel Assignment Mini Message). After Supplemental Channels have been
14 assigned by the base station, the connected service option can transmit primary
15 and/or secondary traffic on Supplemental Channels. The associated service option
16 connection reference provides a means for uniquely identifying the service option
17 connection. The reference serves to resolve ambiguity when there are multiple
18 service option connections in use.
19 The non-negotiable service configuration parameters are sent from the base station to the
20 mobile stations only, and consists of the following:
21 1. Reverse Pilot Gating Rate: This controls the way in which the reverse pilot is gated
22 on the Reverse Pilot Channel. The base station specifies the reverse pilot gating rate
23 to be used in the Service Connect Message, the General Handoff Direction Message,
24 and the Universal Handoff Direction Message.
25 2. Forward and Reverse Power Control Parameters: These consist of forward power
26 control operation mode, outer loop power control parameters (Ex. target frame error
27 rate, minimum Eb/Nt setpoint, and maximum Eb/Nt setpoint) for the Forward
28 Fundamental Channel and Forward Dedicated Control Channel, and Power Control
29 Subchannel indicator which indicates where the mobile station is to perform the
30 primary inner loop estimation and the base station is to multiplex the Power Control
31 Subchannel.
32 3. Logical to Physical Mapping: This is a table of logical to physical mapping entries,
33 consisting of service reference identifier, logical resource, physical resource, forward
34 flag, reverse flag, and priority.
35 The mobile station can request a default service configuration associated with a service
36 option at call origination, and can request new service configurations during Traffic
37 Channel operation. A requested service configuration can differ greatly from its predecessor
38 or it can be very similar. For example, the mobile station can request a service
39 configuration in which all of the service option connections are different from those of the
40 existing configuration; or the mobile station can request a service configuration in which
41 the existing service option connections are maintained with only minor changes, such as a
42 different set of transmission rates or a different mapping of service option connections to
43 Forward and Reverse Traffic Channel traffic types.
3-18
C.S0005-0-2 v1.0
1 If the mobile station requests a service configuration that is acceptable to the base station,
2 they both begin using the new service configuration. If the mobile station requests a
3 service configuration that is not acceptable to the base station, the base station can reject
4 the requested service configuration or propose an alternative service configuration. If the
5 base station proposes an alternative service configuration, the mobile station can accept or
6 reject the base station’s proposed service configuration, or propose yet another service
7 configuration. This process, called service negotiation, ends when the mobile station and
8 base station find a mutually acceptable service configuration, or when either the mobile
9 station or base station rejects a service configuration proposed by the other.
10 It is also possible for the base station to request a default service configuration, associated
11 with a service option, when paging the mobile station and to request new service
12 configurations during Traffic Channel operation. The service negotiation proceeds as
13 described above, but with the roles of the mobile station and base station reversed.
14 For CDMA mode operation in Band Class 0, the mobile station and base station can also
15 use an alternative method for negotiating a service configuration known as service option
16 negotiation. Service option negotiation is similar to service negotiation, but offers less
17 flexibility for specifying the attributes of the service configuration. During service option
18 negotiation, the base station or mobile station specifies only which service option is to be
19 used. There is no facility for explicitly specifying the multiplex options, traffic types or
20 transmission rates to be used on the Forward and Reverse Traffic Channels in conjunction
21 with the service option. Instead, implicit service configuration attributes are assumed. In
22 particular, the Forward and Reverse Multiplex Options and transmission rates are assumed
23 to be the default multiplex options and transmission rates associated with the requested
24 service option, and the traffic type for both the Forward and Reverse Traffic Channels is
25 assumed to be primary traffic. Furthermore, a service configuration established using
26 service option negotiation is restricted to having only a single service option connection.
27 At mobile station origination and termination, the type of negotiation to use, either service
28 negotiation or service option negotiation, is indicated in the Channel Assignment Message.
29 Service negotiation is always used with the Extended Channel Assignment Message. If a
30 CDMA-to-CDMA hard handoff occurs during the call, the type of negotiation to use
31 following the handoff is indicated in the Extended Handoff Direction Message, General
32 Handoff Direction Message, or Universal Handoff Direction Message.
33 For CDMA mode operation in band classes other than Band Class 0, only service
34 negotiation is to be used.
35 The following messages are used to support service negotiation:

36 1. Service Request Message: The mobile station can use this message to propose a
37 service configuration, or to accept or reject a service configuration proposed in a
38 Service Response Message. The base station can use this message to propose a
39 service configuration, or to reject a service configuration proposed in a Service
41 2. Service Response Message: The mobile station can use this message to accept or
43 an alternative service configuration. The base station can use this message to
3-19
C.S0005-0-2 v1.0

2 an alternative service configuration.
3 3. Service Connect Message: The base station can use this message to accept a service
4 configuration proposed in a Service Request Message or Service Response Message,
5 and instruct the mobile station to begin using the service configuration.
6 4. Service Connect Completion Message: The mobile station can use this message to
7 acknowledge the transition to a new service configuration.
8 5. Service Option Control Message: The mobile station and base station can use this
10 6. Extended Channel Assignment Message: The base station can use this message to
11 accept or reject the initial service configuration proposed by the mobile station in
12 an Origination Message or a Page Response Message.
13 The following messages are used to support service option negotiation:

14 1. Service Option Request Order: The mobile station and base station can use this
15 message either to request a service option or suggest an alternative service option.
16 2. Service Option Response Order: The mobile station and base station can use this
17 message to accept or reject a service option request.
18 3. Service Option Control Order: The mobile station and base station can use this
20 The following messages are used to support both service negotiation and service option
21 negotiation:
22 1. Origination Message: The mobile station can use this message to propose an initial
24 2. Channel Assignment Message: The base station can use this message to accept or
25 reject the initial service configuration proposed by the mobile station in an
26 Origination Message or a Page Response Message, and to indicate which type of
27 negotiation, either service negotiation or service option negotiation, is to be used
28 during the call.
29 3. Extended Handoff Direction Message: The base station can use this message to
31 negotiation, is to be used following a CDMA-to-CDMA hard handoff.
32 4. General Handoff Direction Message: The base station can use this message to
38 5. General Page Message: The base station can use this message to propose an initial
3-20
C.S0005-0-2 v1.0
1 6. Page Response Message: The mobile station can use this message to accept or reject
2 the initial service configuration proposed by the base station in a General Page
3 Message, or to propose an alternative initial service configuration.
4 7. Status Request Message: The base station can use this message to request service
5 capability information from the mobile station.
6 8. Status Response Message: The mobile station can use this message to return the
7 service capability information requested by the base station in a Status Request
8 Message.
9 9. Extended Status Response Message: The mobile station can use this message to
10 return the service capability information requested by the base station in a Status
11 Request Message.
12 10. Universal Handoff Direction Message: The base station can use this message to
18 3.6.4.1.2.1 Use of Variables
19 3.6.4.1.2.1.1 Maintaining the Service Request Sequence Number
20 The base station shall maintain a service request sequence number variable,
21 SERV_REQ_NUM, for use with service negotiation. Upon beginning Traffic Channel
22 processing, the base station shall set SERV_REQ_NUM to 0. Each time the base station
23 sends a new Service Request Message, it shall set the SERV_REQ_SEQ field of the message
24 to the current value of SERV_REQ_NUM, and shall then set SERV_REQ_NUM equal to
25 (SERV_REQ_NUM + 1) modulo 8.
26 3.6.4.1.2.1.2 Maintaining the Service Connect Sequence Number
27 The base station shall maintain a service connect sequence number variable,
28 SERV_CON_NUM, for use with service negotiation. Upon beginning Traffic Channel
29 processing, the base station shall set SERV_CON_NUM to 0. Each time the base station
30 sends a new Service Connect Message, a General Handoff Direction Message, or a Universal
31 Handoff Direction Message containing a service configuration record, it shall set the
32 SERV_CON_SEQ field of the message to the current value of SERV_CON_NUM, and shall
33 then set SERV_CON_NUM equal to (SERV_CON_NUM + 1) modulo 8.
34 3.6.4.1.2.1.3 Assigning Service Option Connection References
35 When the base station assigns a service option connection reference for use in identifying a
36 new service option connection during service negotiation, the base station shall use the
37 following criteria:
38 1. The base station shall not assign a reference equal to ‘00000000’; and
3-21
C.S0005-0-2 v1.0
1 2. The base station shall not assign a reference that is associated with a service option
2 connection of the current service configuration; and
3 3. If there was a previous service configuration, the base station shall not assign a
4 reference that was associated with a service option connection of the previous
6 3.6.4.1.2.1.4 Maintaining the Service Negotiation Indicator Variable
7 The base station shall maintain a service negotiation indicator variable, SERV_NEG, to
8 indicate which type of negotiation to use, either service negotiation or service option
9 negotiation. The base station shall set SERV_NEG to enabled whenever service negotiation
10 is to be used, and shall set SERV_NEG to disabled whenever service option negotiation is to
11 be used. The precise rules for setting SERV_NEG are specified in 3.6.4.2 and 3.6.6.2.2.2.
12 For CDMA operation in band classes other than Band Class 0, the base station shall set
13 SERV_NEG to enabled.
14 3.6.4.1.2.1.5 Maintaining the Service Option Request Number
15 The base station shall maintain a service option request number variable, SO_REQ, for use
16 with service option negotiation. The base station shall set SO_REQ to a special value,
17 NULL, if the base station does not have an outstanding service option request. If the base
18 station has an outstanding service option request, the base station shall set SO_REQ to the
19 number of the service option associated with the outstanding request.
20 3.6.4.1.2.2 Service Subfunctions
21 As illustrated in Figure 3.6.4.1.2.2-1, the base station supports service configuration and
22 negotiation by performing the following set of service subfunctions.
23 • Normal Service Subfunction - While this subfunction is active, the base station
24 processes service configuration requests from the mobile station and sends service
25 configuration requests to the mobile station.
26 • Waiting for Service Request Message Subfunction - While this subfunction is active,
27 the base station waits to receive a Service Request Message.
28 • Waiting for Service Response Message Subfunction - While this subfunction is active,
29 the base station waits to receive a Service Response Message.
30 • Waiting for Service Action Time Subfunction - While this subfunction is active, the
31 base station waits for the action time associated with a new service configuration.
32 • Waiting for Service Connect Completion Message Subfunction - While this subfunction
33 is active, the base station waits to receive a Service Connect Completion Message or a
34 Handoff Completion Message.
35 • SO Negotiation Subfunction - While this subfunction is active and the base station is
36 operating in Band Class 0, the base station supports service option negotiation with
3-22
C.S0005-0-2 v1.0
1 The SO Negotiation Subfunction supports service option negotiation. All of the other service
2 subfunctions support service negotiation.
3 At any given time during Traffic Channel processing, only one of the service subfunctions is
4 active. For example, when the base station first begins Traffic Channel processing, either
5 the Normal Service Subfunction or the SO Negotiation Subfunction is active. Each of the
6 other service subfunctions may become active in response to various events which occur
7 during the Traffic Channel substates. Typically, the base station processes events
8 pertaining to service configuration and negotiation in accordance with the requirements for
9 the active service subfunction. However, some Traffic Channel substates do not allow for
10 the processing of certain events pertaining to service configuration and negotiation, or
11 specify requirements for processing such events which supersede the requirements of the
12 active service subfunction.
13
3-23
C.S0005-0-2 v1.0
For service
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
SCM, GHDM,
Receives Service Connect or UHDM
Completion Message or Handoff
Completion Message.
Waiting for
Service
Connect
Completion
Message
Subfunction
Receives Service
Request Message
Action time passes; uses new service Receives Service
either accepting or
configuration. Response Message
proposing; sends
either accepting
SCM, GHDM, or UHDM.
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
3-24
C.S0005-0-2 v1.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-25
C.S0005-0-2 v1.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 send a Service Response Message to propose the alternative service
13 configuration. The base station shall activate the Waiting for Service
14 Request Message Subfunction.
16 • If the base station receives one of the following service option negotiation messages,
17 the base station shall process the message according to the specified requirements,
18 if any:
22 3.6.4.1.2.2.2 Waiting for Service Request Message Subfunction

23 While this subfunction is active, the base station waits to receive a Service Request
24 Message.
25 While the Waiting for Service Request Message Subfunction is active, the base station shall
27 • If the base station does not receive a Service Request Message, the base station shall
28 activate the Normal Service Subfunction.
34 configuration.
38 service option.
3-26
C.S0005-0-2 v1.0

5 any:
12 3. Service Request Message: The base station shall process the message as follows:
13 • If the purpose of the message is to accept a proposed service configuration,

14 the base station shall perform one of the following actions:
15 – The base station shall send a Service Connect Message, General Handoff
16 Direction Message, or Universal Handoff Direction Message and shall
18 – The base station shall send a Service Request Message to propose an

19 alternative service configuration and shall activate the Waiting for Service
20 Response Message Subfunction.
21 • If the purpose of the message is to reject a proposed service configuration,

22 the base station shall activate the Normal Service Subfunction.

25 – If the base station accepts the proposed service configuration, the base
29 Subfunction.
32 station shall send a Service Response Message to reject the proposed
33 service configuration. The base station shall activate the Normal Service
34 Subfunction.
37 send a Service Response Message to propose the alternative service
38 configuration.
3-27
C.S0005-0-2 v1.0
3 if any:
7 3.6.4.1.2.2.3 Waiting for Service Response Message Subfunction

8 While this subfunction is active, the base station waits to receive a Service Response
9 Message.
10 While the Waiting for Service Response Message Subfunction is active, the base station shall
12 • If the base station does not receive a Service Response Message, the base station
19 configuration.
23 service option.

28 any:
35 3. Service Request Message: The base station should not process the layer 3 fields
36 of the message.
37 4. Service Response Message: The base station shall process the message as
38 follows:
3-28
C.S0005-0-2 v1.0
1 • If the service request sequence number (SERV_REQ_SEQ) from the message

2 does not match the sequence number of the Service Request Message for
3 which the base station is expecting a response, the base station shall not
4 process the layer 3 fields of the message.
5 • If the purpose of the message is to accept a proposed service configuration,

6 the base station shall perform one of the following actions:
7 – The base station shall send a Service Connect Message, a General
8 Handoff Direction Message, or a Universal Handoff Direction Message
9 containing a service configuration record and shall activate the Waiting
10 for Service Action Time Subfunction. Or
11 – The base station shall send a Service Request Message to propose an

12 alternative service configuration.
13 • If the purpose of the message is to reject a proposed service configuration,

14 the base station shall activate the Normal Service Subfunction.

17 – If the base station accepts the proposed service configuration, the base
21 Subfunction.
24 station shall send a Service Request Message to reject the proposed
25 service configuration. The base station shall activate the Normal Service
26 Subfunction.
29 send a Service Request Message to propose the alternative service
30 configuration.
33 if any:
37 3.6.4.1.2.2.4 Waiting for Service Action Time Subfunction
38 While this subfunction is active, the base station waits for the action time associated with a
39 new service configuration.
3-29
C.S0005-0-2 v1.0
1 While the Waiting for Service Action Time Subfunction is active, the base station shall
3 • Prior to the action time associated with the Service Connect Message, a General
4 Handoff Direction Message, or Universal Handoff Direction Message containing a
5 service configuration record, the base station shall process Forward and Reverse
6 Traffic Channel frames in accordance with the current service configuration. The
7 base station shall discard any Reverse Traffic Channel frame which has a format
8 that is not supported by the base station. The base station may discard any type of
9 Reverse Traffic Channel traffic that is not signaling traffic and is not part of the
11 • At the action time associated with the Service Connect Message, General Handoff
12 Direction Message, or Universal Handoff Direction Message containing a service
13 configuration record, the base station shall begin to use the service configuration
14 specified by the Service Connect Message, the General Handoff Direction Message, or
15 the Universal Handoff Direction Message containing a service configuration record,
16 as the current service configuration and shall begin to process Forward and Reverse
17 Traffic Channel frames accordingly. The base station shall activate the Waiting for
18 Service Connect Completion Message Subfunction.

23 any:
26 message is part of the current or pending service configuration, and the service
27 option specified by the message is the same as the service option associated with
28 the service option connection, the base station shall process the message in
34 if any:
3-30
C.S0005-0-2 v1.0
1 3.6.4.1.2.2.5 Waiting for Service Connect Completion Message Subfunction
2 While this subfunction is active, the base station waits to receive a Service Connect
3 Completion Message, or a Handoff Completion Message.
4 While the Waiting for Service Connect Completion Message Subfunction is active, the base
6 • If the base station has sent a Service Connect Message and does not receive a Service
7 Connect Completion Message, or if the base station has sent a General Handoff
8 Direction Message or a Universal Handoff Direction Message containing a Service
9 Configuration record and does not receive a Handoff Completion Message, the base
16 configuration.
17 • The base station shall not initiate service negotiation for a new service configuration.

22 any:
23 1. Service Connect Completion Message, or Handoff Completion Message: The base
34 if any:
3-31
C.S0005-0-2 v1.0
1 3.6.4.1.2.2.6 SO Negotiation Subfunction
2 While this subfunction is active, the base station supports service option negotiation with
4 Upon activating the SO Negotiation Subfunction, the base station shall set SO_REQ to NULL.
5 The base station shall delete from the current service configuration any service option
6 connection which does not use primary traffic on both the Forward and Reverse Traffic
7 Channels.
8 While the SO Negotiation Subfunction is active, the base station shall perform the following:
9 • If the current service configuration includes a service option connection, the base
10 station shall process the received primary traffic bits in accordance with the
11 requirements for the service option associated with the service option connection;
12 otherwise, the base station shall discard the received primary traffic bits.
14 station shall transmit primary traffic bits in accordance with the requirements for
15 the service option associated with the service option connection; otherwise, the base
16 station shall transmit null traffic and power control bits on the Forward
17 Fundamental Channel, if the Fundamental channel is present to transmit power
18 control bits on the Forward Dedicated Control Channel, if only the Dedicated
19 Control Channel is present.
21 station may send a Service Option Control Order to invoke a service option specific
22 function in accordance with the requirements for the service option associated with
23 the service option connection.
24 • To initiate service option negotiation, the base station shall set SO_REQ to the
25 number of the requested service option and shall send a Service Option Request
26 Order containing the requested service option number.
27 • If SERV_NEG changes from disabled to enabled (see 3.6.6.2.2.2, 3.6.6.2.2.10, and

28 3.6.6.2.2.11), the base station shall activate the Normal Service Subfunction.
29 • The base station shall process a service option request received in an Origination
30 Message, a Page Response Message, or a Service Option Request Order as follows:
31 – If the base station accepts the requested service option, the base station shall
32 set SO_REQ to NULL and shall send a Service Option Response Order accepting
33 the requested service option within T4b seconds. The base station shall begin
34 using the service configuration implied by the requested service option in
35 accordance with the requirements for the requested service option. The implied
36 service configuration shall include the default Forward and Reverse Multiplex
37 Options and transmission radio configurations associated with the requested
38 service option. This implied service configuration shall include one service
39 option connection for which the service option connection reference is 1, for
40 which the service option is the requested service option, and for which the
41 Forward and Reverse Traffic Channel types are both primary traffic.
3-32
C.S0005-0-2 v1.0
1 – If the base station does not accept the requested service option and has an
2 alternative service option to request, the base station shall set SO_REQ to the
3 alternative service option number and shall send a Service Option Request Order
4 requesting the alternative service option within T4b seconds.
5 – If the base station does not accept the requested service option and does not
6 have an alternative service option to request, the base station shall set SO_REQ
7 to NULL and shall send a Service Option Response Order to reject the request
8 within T4b seconds. The base station shall continue to use the current service
9 configuration.
10 • If the base station receives a Service Option Response Order, it shall process the
11 order as follows:
12 – If the service option number specified in the order is equal to SO_REQ, the base
13 station shall set SO_REQ to NULL and shall begin using the service
14 configuration implied by the specified service option in accordance with the
15 requirements for the service option. The implied service configuration shall
16 include the default Forward and Reverse Multiplex Options and transmission
17 radio configurations associated with the requested service option. This implied
18 service configuration shall include one service option connection for which the
19 service option connection reference is 1, for which the service option is the
20 requested service option, and for which the Forward and Reverse Traffic Channel
21 types are both primary traffic.
22 – If the order indicates a service option rejection, the base station shall set
23 SO_REQ to NULL. The base station shall continue to use the current service
24 configuration.
25 – If the order does not indicate a service option rejection and the service option
26 specified in the order is not equal to SO_REQ, the base station shall set SO_REQ
27 to NULL, should send a Release Order (ORDQ = ‘00000010’), and should enter
28 the Release Substate.
29 • If the base station receives a Service Option Control Order, the base station shall
30 process the order as follows:
31 – If the current service configuration includes a service option connection, the

32 base station shall process the received Service Option Control Order in
33 accordance with the requirements for the service option associated with the
37 any:
39 2. Service Option Control Message
3-33
C.S0005-0-2 v1.0
1 3.6.4.1.3 Ordering of Messages
2 The Layer 2 protocol does not guarantee delivery of messages in any order. If the base
3 station requires that the mobile station receive a set of messages in a certain order, the
4 base station shall send each message in assured mode requiring confirmation of delivery
5 and shall wait for the confirmation of delivery of each message before transmitting the next
6 message in the set.
7 3.6.4.1.4 Message Action Times
8 A Forward Traffic Channel message without a USE_TIME field or with a USE_TIME field set
9 to ‘0’ has an implicit action time. A message that has its USE_TIME field set to ‘1’ has an
10 explicit action time that is specified in the ACTION_TIME field of the message.
11 A message with an explicit action time is called a pending message.
12 Unless otherwise specified, a message having an implicit action time shall take effect no
13 later than the first 80 ms boundary (relative to System Time) occurring at least 80 ms after
14 the end of the frame containing the last bit of the message. A message with an explicit
15 action time, except for a Power Up Function Message, shall take effect when System Time (in
16 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME field. A Power Up
17 Function Message shall take effect ACTION_TIME_FRAME frames after the time when
18 System Time (in 80 ms units) modulo 64 becomes equal to the message’s ACTION_TIME
19 field. The difference in time between ACTION_TIME and the end of the frame containing the
20 last bit of the message shall be at least 80 ms.
21 The base station shall support two pending messages at any given time, not including
22 pending Service Option Control Orders, Service Option Control Messages, or Power Up
23 Function Messages. The number of pending Service Option Control Orders or Service Option
24 Control Messages that the base station is required to support is specific to the service
25 option (see the relevant service option descriptions). In addition, the base station shall
26 support one pending Power Up Function Message.
27 3.6.4.1.5 Long Code Transition Request Processing

28 If a request for voice privacy is specified in the Origination Message or Page Response
29 Message, the base station may send a Long Code Transition Request Order (ORDQ =
30 ‘00000001’) requesting a transition to the private long code.
31 The base station shall process the Long Code Transition Request Order as follows:
32 • If the Long Code Transition Request Order requests a transition to the private long
33 code and the base station accepts the request, the base station shall send a Long
34 Code Transition Request Order (ORDQ = ‘00000001’). If the base station does not
35 accept the private long code transition request, the base station shall send a Long
36 Code Transition Request Order (ORDQ = ‘00000000’).
3-34
C.S0005-0-2 v1.0
1 • If the Long Code Transition Request Order requests a transition to the public long
2 code and the base station accepts the request, the base station shall send a Long
3 Code Transition Request Order (ORDQ = ‘00000000’). If the base station does not
4 accept the public long code transition request, the base station shall send a Long
5 Code Transition Request Order (ORDQ = ‘00000001’).
6 The base station shall process the Long Code Transition Response Order as follows:
7 • If the Long Code Transition Response Order indicates that the mobile station accepts
8 the long code transition requested in the Long Code Transition Request Order sent by
9 the base station, the base station shall use the requested long code mask on both
10 the Forward Traffic Channel and the Reverse Traffic Channel. The base station
11 shall specify an explicit action time in the Long Code Transition Request Order. The
12 base station shall begin using the requested long code mask using the explicit action
13 time (see 3.6.4.1.4).
14 3.6.4.1.6 Processing Resource Request Messages

15 The base station shall process Resource Request Message and Resource Request Mini
16 Message, as follows:
17 • The base station may send one of the messages that assign appropriate resources
18 (e.g., Extended Supplemental Channel Assignment Message, Resource Allocation
19 Message, Resource Allocation Mini Message, Forward Supplemental Channel
20 Assignment Mini Message, Reverse Supplemental Channel Assignment Mini Message,
21 Universal Handoff Direction Message) to the mobile station. If the base station sends
22 one of these messages, the base station shall set PILOT_GATING_USE_RATE to ‘0’
23 and start transmitting the Forward Power Control Subchannel with the maximum
24 rate at the action time of the message.
25 • The base station may send a Retry Order to the mobile station.
26 3.6.4.1.7 Reserved
27 3.6.4.1.8 Processing Resource Release Request Message and Resource Release Request Mini
28 Message
29 The base station may perform the following in response to receiving a Resource Release
30 Request Message or Resource Release Request Mini Message:
31 • The base station may send a Extended Release Message, Extended Release Mini
32 Message, or a Universal Handoff Direction Message to instruct the mobile station to
33 commence the reverse pilot gating operation.
34 3.6.4.2 Traffic Channel Initialization Substate
35 In this substate, the base station begins transmitting on the Forward Traffic Channel and
36 acquires the Reverse Traffic Channel.
37 Upon entering the Traffic Channel Initialization Substate, the base station shall perform the
38 following:
3-35
C.S0005-0-2 v1.0
1 • Layer 3 shall send an L2-Supervision.Request primitive to Layer 2 to reset the

2 message acknowledgment procedures as specified in 3.2.1.1 and 3.2.2.1 of
3 TIA/EIA/IS-2000-[4].
4 • The base station shall set its Forward and Reverse Traffic Channel long code masks
5 to the public long code mask (see TIA/EIA/IS-2000-[2)[2]).
6 • The base station shall set its Forward and Reverse Traffic Channel frame offsets (see
7 TIA/EIA/IS-2000-[2)[2]) to the frame offset assigned to the mobile station.
8 • If the base station set the ASSIGN_MODE field of the Channel Assignment Message
9 to ‘000’, the base station shall set SERV_NEG to disabled. If the base station set the
10 ASSIGN_MODE field of the Channel Assignment Message to ‘100’, the base station
11 shall set SERV_NEG to enabled. For operation in band classes other than Band
12 Class 0, SERV_NEG is always equal to enabled.
13 • If the base station uses the Extended Channel Assignment Message, the base station
14 shall set the SERV_NEG to enabled.
15 • The base station shall determine the initial service configuration as follows:
16 – If SERV_NEG is equal to 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_NEG is equal to enabled and the base station set the GRANTED_MODE
20 field of the Channel Assignment Message or the Extended Channel Assignment
21 Message to ‘00’, the initial service configuration shall include the multiplex
22 option and Radio Configuration for the Forward and Reverse Traffic Channels as
23 specified by the DEFAULT_CONFIG field, and shall include no service option
24 connections.
25 – If SERV_NEG is equal to enabled and the base station set the GRANTED_MODE
26 field of the Channel Assignment Message or the Extended Channel Assignment
27 Message to ‘01’ or ‘10’, the initial service configuration shall include the default
28 Forward and Reverse Traffic Channel multiplex options and transmission rates
29 corresponding to the service option requested by the mobile station in the
30 Origination Message, in the case of a mobile-station-originated call, or the Page
31 Response Message, in the case of a mobile station terminated call, and shall
32 include no service option connections.
33 • If SERV_NEG is equal to disabled, the base station shall activate the SO Negotiation
34 Subfunction (see 3.6.4.1.2.2.6); otherwise, the base station shall activate the Normal
35 Service Subfunction (see 3.6.4.1.2.2.1).
36 • The base station shall set PILOT_GATING_USE_RATE to ‘0’.

37 While in the Traffic Channel Initialization Substate, the base station shall perform the
38 following:
39 • If the Forward Fundamental Channel is assigned, the base station shall transmit
40 null Traffic Channel data on the Forward Fundamental Channel, except when
41 transmitting signaling traffic.
3-36
C.S0005-0-2 v1.0
1 • If FPC_PRI_CHAN is set to ‘0’, the base station shall transmit power control bits on
2 the Forward Fundamental Channel. If FPC_PRI_CHAN is set to ‘1’, the base station
3 shall transmit power control bits on the Forward Dedicated Control Channel.
4 • If the base station acquires the Reverse Traffic Channel, Layer 3 shall send a reverse
5 dedicated channel acquired indication to Layer 2 (see 2.2.2.1.2 of TIA/EIA/IS-2000-
6 [4)[4]). If the call is a mobile station terminated call and the base station set
7 BYPASS_ALERT_ANSWER to ‘1’, the base station shall enter the Conversation
8 Substate (see 3.6.4.4). If the call is a mobile station terminated call and the base
9 station set BYPASS_ALERT_ANSWER to ‘0’, the base station shall enter the Waiting
10 for Order Substate (see 3.6.4.3.1). If the call is a mobile-station-originated call, the
11 base station shall enter the Conversation Substate (see 3.6.4.4).
12 • If the base station fails to acquire the Reverse Traffic Channel, the base station shall
13 either retransmit the Channel Assignment Message or the Extended Channel
14 Assignment Message on the Paging Channel and remain in the Traffic Channel
15 Initialization Substate, or the base station should disable transmission on the
16 Forward Traffic Channel and discontinue the Traffic Channel Processing for the
17 mobile station.
18 3.6.4.3 Alerting
19 3.6.4.3.1 Waiting for Order Substate

20 In this substate, the base station sends an Alert With Information Message to the mobile
21 station.
22 Upon entering the Waiting for Order Substate, the base station shall perform the following:
23 • If SERV_NEG is equal to disabled, the base station shall process the service option
24 request specified in the Page Response Message in accordance with the
26 • If SERV_NEG is equal to enabled and the base station set the GRANTED_MODE field
27 of the Channel Assignment Message or the Extended Channel Assignment Message to
28 ‘00’ or ‘01’, the base station should initiate service negotiation to request a service
29 configuration in accordance with the requirements for the active service subfunction
30 (see 3.6.4.1.2.2).
31 • If SERV_NEG is equal to enabled and the base station set the GRANTED_MODE field
32 of the Channel Assignment Message or the Extended Channel Assignment Message to
33 ‘10’, the base station should send a Service Connect Message in accordance with the
35 While in the Waiting for Order Substate, the base station shall perform the following:
36 • The base station shall transmit the power control subchannel as specified in
37 TIA/EIA/IS-2000-[2].
40 3.6.4.1.2.2).
3-37
C.S0005-0-2 v1.0
1 • If the base station declares a loss of Reverse Traffic Channel continuity (see 3.4), the
2 base station should send a Release Order to the mobile station. If the base station
3 sends a Release Order, the base station shall enter the Release Substate.
4 • The base station may perform Forward Traffic Channel power control as specified in
5 3.6.4.1.1.
6 • The base station may request a new service configuration by initiating service
7 negotiation or service option negotiation in accordance with the requirements for the
8 active service subfunction (see 3.6.4.1.2.2).
9 • The base station may send a Service Option Control Message or Service Option
12 • The base station may request a long code transition, as specified in 3.6.4.1.5, either
13 autonomously or in response to a request for voice privacy specified in the
14 Origination Message or Page Response Message.
15 • The base station may perform authentication procedures as specified in 3.3.1.
16 • The base station may perform TMSI assignment procedures (see 2.3.15).
17 • The base station may send the following messages. If the base station sends a
18 message, the base station shall comply with the specified requirements for sending
19 the message, if any.
20 1. Alert With Information Message: The base station shall enter the Waiting for
21 Answer Substate.
22 2. Analog Handoff Direction Message: The base station shall enter the Waiting for
23 Order Task (see 3.6.4.3.1 for handoff to a wide analog channel and 3.6.5.3.1A of
24 TIA/EIA/IS-91[28] for handoff to a narrow analog channel).
25 3. Audit Order
28 6. Candidate Frequency Search Request Message
29 7. Candidate Frequency Search Control Message
31 9. Extended Handoff Direction Message
32 10. Extended Release Message: If the physical channels indicated in CH_IND field of
33 this message includes all the physical channels currently being processed by the
34 mobile station, the base station shall enter the Release Substate.
35 11. Extended Release Mini Message: If the physical channels indicated in CH_IND
36 field of this message includes all the physical channels currently being
37 processed by the mobile station, the base station shall enter the Release
38 Substate.
3-38
C.S0005-0-2 v1.0
1 12. General Handoff Direction Message
2 13. Extended Neighbor List Update Message
3 14. In-Traffic System Parameters Message
5 16. Lock Until Power-Cycled Order: The base station should send this order in
6 unassured mode.
7 17. Long Code Transition Request Order
9 19. User Zone Update Message
10 20. Maintenance Order: The base station shall enter the Waiting for Answer
11 Substate.
13 22. Message Encryption Mode Order
14 23. Mobile Station Registered Message
15 24. Neighbor List Update Message
16 25. Parameter Update Order (see 2.3.12.1.3).
17 26. Periodic Pilot Measurement Request Order
18 27. Pilot Measurement Request Order
19 28. Power Control Message
20 29. Power Control Parameters Message
21 30. Power Up Function Message
22 31. Power Up Function Completion Message
23 32. Release Order: The base station shall enter the Release Substate.
24 33. Resource Allocation Message
25 34. Resource Allocation Mini Message
26 35. Retrieve Parameters Message
27 36. Service Connect Message: The base station shall send the message in
29 3.6.4.1.2.2).
30 37. Service Option Control Message: The base station shall send the message in
32 3.6.4.1.2.2).
3-39
C.S0005-0-2 v1.0
2 41. Service Request Message: The base station shall send the message in
4 3.6.4.1.2.2).
5 42. Service Response Message: The base station shall send the message in
7 3.6.4.1.2.2).
8 43. Set Parameters Message

11 46. Status Request Order
12 47. Supplemental Channel Assignment Message
14 49. Universal Handoff Direction Message
15 • If the base station receives one of the following messages from the mobile station,
17 if any:
18 1. Base Station Challenge Order: The base station shall process the message as
20 2. Candidate Frequency Search Report Message: The base station shall process the
21 message as described in 2.6.6.2.2.6.
22 3. Candidate Frequency Search Response Message: The base station shall process
23 the message as described in 2.6.6.2.2.4.
25 5. Extended Release Response Message
26 6. Extended Release Response Mini Message
27 7. Handoff Completion Message
28 8. Local Control Response Order
29 9. Long Code Transition Request Order: The base station shall process the message
30 as described in 3.6.4.1.5.
31 10. Long Code Transition Response Order
32 11. Mobile Station Reject Order
33 12. Outer Loop Report Message
34 13. Parameters Response Message
35 14. Parameter Update Confirmation Order
3-40
C.S0005-0-2 v1.0
1 15. Periodic Pilot Strength Measurement Message
2 16. Pilot Strength Measurement Mini Messsage
3 17. Pilot Strength Measurement Message: The base station shall process the message
5 18. Power Measurement Report Message: The base station may process the message
7 19. Release Order: The base station shall send the mobile station a Release Order
8 within T2b seconds and enter the Release Substate; otherwise, the base station
9 shall send an Alert with Information Message, within T2b seconds, and enter the
10 Waiting for Answer Substate.
11 20. Request Analog Service Order: The base station may respond with an Analog
13 21. Request Narrow Analog Service Order: The base station may respond with an
14 Analog Handoff Direction Message.
15 22. Request Wide Analog Service Order: The base station may respond with an
17 23. Resource Request Message: The base station shall process the message as
19 24. Resource Request Mini Message: The base station shall process the message as
21 25. Service Connect Completion Message: The base station shall process the message
23 3.6.4.1.2.2).
24 26. Service Option Control Message: The base station shall process the message in
26 3.6.4.1.2.2).
27 27. Service Option Control Order: The base station shall process the message in
29 3.6.4.1.2.2).
30 28. Service Option Request Order: The base station shall process the message in
32 3.6.4.1.2.2).
33 29. Service Option Response Order: The base station shall process the message in
35 3.6.4.1.2.2).
36 30. Service Request Message: The base station shall process the message in
38 3.6.4.1.2.2).
3-41
C.S0005-0-2 v1.0
1 31. Service Response Message: The base station shall process the message in
3 3.6.4.1.2.2).
4 32. SSD Update Confirmation Order
5 33. SSD Update Rejection Order
6 34. Status Response Message
7 35. Status Message
8 36. TMSI Assignment Completion Message
9 37. User Zone Update Request Message: The base station shall process this message
11 3.6.4.3.2 Waiting for Answer Substate

12 In this substate, the base station waits for a Connect Order from the mobile station.
13 While in the Waiting for Answer Substate, the base station shall perform the following:
14 • The base station shall transmit the power control subchannel (see TIA/EIA/IS-
15 2000-[2)[2]).
18 TIA/EIA/IS-2000-[2)[2]).
23 3.6.4.1.1.
3-42
C.S0005-0-2 v1.0
1 1. Alert With Information Message
2 2. Analog Handoff Direction Message: The base station shall enter the Waiting for
3 Answer Task (see 3.6.4.3.2 for handoff to a wide analog channel and 3.6.5.3.2 of
4 TIA/EIA/IS-91[28] for handoff to a narrow analog channel).
5 3. Audit Order
19 Substate.
20 13. Extended Supplemental Channel Assignment Message
21 14. Forward Supplemental Channel Assignment Mini Message
26 unassured mode.
28 20. Maintenance Order
31 23. Mobile Assisted Burst Operation Parameters Message
3-43
C.S0005-0-2 v1.0
10 37. Reverse Supplemental Channel Assignment Mini Message
13 3.6.4.1.2.2).
16 3.6.4.1.2.2).
22 3.6.4.1.2.2).
25 3.6.4.1.2.2).
3-44
C.S0005-0-2 v1.0
3 if any:
10 4. Connect Order: The base station shall enter the Conversation Substate.
14 8. Flash With Information Message: If the message contains a Keypad Facility

15 record with feature codes indicating User Selective Call Forwarding with a pre-
16 registered number, a stored number, or voice mail, the base station may send
17 the mobile station a Release Order and enter the Release Substate.
18 9. Handoff Completion Message: The base station shall process the message as
19 described in 3.6.6.2.2.7.
25 14. Origination Continuation Message
32 20. Pilot Strength Measurement Mini Messsage
3-45
C.S0005-0-2 v1.0
13 28. Service Connect Completion Message: The base station shall process the message
15 3.6.4.1.2.2).
18 3.6.4.1.2.2).
21 3.6.4.1.2.2).
24 3.6.4.1.2.2).
27 3.6.4.1.2.2).
30 3.6.4.1.2.2).
33 3.6.4.1.2.2).
3-46
C.S0005-0-2 v1.0
3 3.6.4.4 Conversation Substate
4 In this substate, the base station exchanges Traffic Channel frames with the mobile station
5 in accordance with the current service configuration.
6 Upon entering the Conversation Substate, the base station shall perform the following:
7 • If SERV_NEG equals enabled, the call is mobile-station-originated and the base

8 station sets the GRANTED_MODE field of the Channel Assignment Message or the
9 Extended Channel Assignment Message to ‘10’, the base station should send a
10 Service Connect Message in accordance with the requirements for the active service
11 subfunction (see 3.6.4.1.2.2).
12 • If SERV_NEG equals disabled and the call is mobile-station-originated, the base

13 station shall process the service option request specified in the Origination Message
15 3.6.4.1.2.2).
16 While in the Conversation Substate, the base station shall perform the following:
18 TIA/EIA/IS-2000-[2].
21 3.6.4.1.2.2).
22 • When PILOT_GATING_USE_RATE is equal to ‘0’ and the base station is to establish

23 a Fundamental Channel or a Dedicated Control Channel, the base station shall send
24 a Universal Handoff Direction Message to the mobile station.
25 "# When PILOT_GATING_USE_RATE is equal to ‘1’ and the base station has data to
26 send, the base station may send a Resource Allocation Message, Resource Allocation
27 Mini Message, Extended Supplemental Channel Assignment Message, Forward
28 Supplemental Channel Assignment Mini Message, Reverse Supplemental Channel
29 Assignment Mini Message, or Universal Handoff Direction Message to start
30 transmitting the Forward Power Control Subchannel with the maximum rate and
31 start exchange of user information.
32 • If both the Fundamental Channel and the Dedicated Control Channel are currently
33 established, and the base station is to release one of these two channels, the base
34 station shall send a Universal Handoff Direction Message, Extended Release
35 Message, or an Extended Release Mini Message to the mobile station.
3-47
C.S0005-0-2 v1.0
1 • When PILOT_GATING_USE_RATE is equal to ‘0’ and the base station does not have
2 any data to send and the base station has determined that the mobile station does
3 not have any data to send (see the RLP out-of-data indication in TIA/EIA/IS-707-
4 A[39]), then the base station may send an Extended Release Message, Extended
5 Release Mini Message or Universal Handoff Direction Message to start transmitting
6 the Forward Power Control Subchannel with the specified rate and stop the
7 exchange of user information.
12 3.6.4.1.1.
24 • If the call is mobile-station-originated and the PACA_REORIG field of the Origination
25 Message is equal to ‘1’, the base station should send either an Alert With Information
26 Message which contains a signal information record with the SIGNAL_TYPE field set
27 to ‘01’ or ‘10’, or an Alert With Information Message which does not contain a signal
29 • The base station may control operation of the Forward or Reverse Supplemental
30 Code Channels by including Supplemental Code Channel assignment information in
31 the Supplemental Channel Assignment Message, or the General Handoff Direction
32 Message.
33 • The base station may control operation of the Forward or Reverse Supplemental
34 Channels by including Supplemental Channel assignment information in the
35 Extended Supplemental Channel Assignment Message, the Forward Supplemental
36 Channel Assignment Mini Message, or the Reverse Supplemental Channel Assignment
37 Mini Message.
40 the message, if any:
3-48
C.S0005-0-2 v1.0
1 1. Alert With Information Message: If the message contains a signal information

3 contain a signal information record, the base station shall enter the Waiting for
4 Answer Substate.
5 2. Analog Handoff Direction Message: The base station shall enter the Conversation
6 Task (see TIA/EIA/IS-2000-[6] for handoff to a wide analog channel and 3.6.5.4A
7 of TIA/EIA/IS-91[28] for handoff to an 800 MHz narrow analog channel).
8 3. Audit Order
13 8. Continuous DTMF Tone Order
23 Substate.
31 unassured mode.
34 Substate.
3-49
C.S0005-0-2 v1.0
15 39. Retry Order
17 41. Send Burst DTMF Message
20 3.6.4.1.2.2).
23 3.6.4.1.2.2).
27 47. Service Redirection Message: The base station shall enter the Release Substate.
30 3.6.4.1.2.2).
33 3.6.4.1.2.2).
3-50
C.S0005-0-2 v1.0
10 if any:
23 described in 3.6.6.2.2.7.
3-51
C.S0005-0-2 v1.0
1 20. Pilot Strength Measurement Mini Message
8 23. Resource Release Request Message: The base station shall process the message
10 24. Resource Release Request Mini Message: The base station shall process the
11 message as described in 3.6.4.1.8.
23 31. Service Connect Completion Message: The base station shall process the
25 (see 3.6.4.1.2.2).
28 3.6.4.1.2.2).
31 3.6.4.1.2.2).
34 3.6.4.1.2.2).
37 3.6.4.1.2.2).
3-52
C.S0005-0-2 v1.0
3 3.6.4.1.2.2).
6 3.6.4.1.2.2).
11 42. Supplemental Channel Request Message: The base station may respond with a
12 Supplemental Channel Assignment Message, an Extended Supplemental Channel
13 Assignment Message, or a Retry Order.
14 43. Supplemental Channel Request Mini Message: The base station may respond
15 with a Forward Supplemental Channel Assignment Mini Message or a Reverse
16 Supplemental Channel Assignment Mini Message, or both. The base station may
17 also respond with a Retry Order.
21 3.6.4.5 Release Substate
22 In this substate, the base station disconnects the call.

23 While in the Release Substate, the base station shall perform the following:
25 TIA/EIA/IS-2000-[2].
26 • The base station shall transmit on the Forward Traffic Channel for at least T3b
27 seconds. The base station shall transmit null traffic and power control bits on the
28 Forward Fundamental Channel, except when transmitting signaling traffic, if the
29 Fundamental Channel is present or transmit power control bits on the Forward
30 Dedicated Control Channel, if only the dedicated Control Channel is present. After
31 T3b seconds, the base station should stop transmitting on the Forward Traffic
32 Channel.
33 • The base station shall process Reverse Traffic Channel signaling traffic and may
34 discard other types of Reverse Traffic Channel traffic.
37 3.6.4.1.1.
3-53
C.S0005-0-2 v1.0
1 • The base station may send a Service Option Control Message to invoke a service
2 option specific function in accordance with the requirements for the active service
3 subfunction (see 3.6.4.1.2.2).
7 1. Alert With Information Message: If the message contains a signal information
9 contain a signal information record, the base station shall enter the Waiting for
10 Answer Substate.
11 2. Audit Order
17 8. Extended Release Message
18 9. Extended Release Mini Message
25 unassured mode.
27 Substate.
32 21. Parameter Update Order (see 2.3.12.1.3 or 3.7.4).
3-54
C.S0005-0-2 v1.0
2 26. Release Order
9 3.6.4.1.2.2).
18 40. User Zone Update message
21 if any:
28 4. Connect Order
31 7. Extended Release Response Message:
34 described in 3.6.6.2.2.7.
3-55
C.S0005-0-2 v1.0
7 17. Periodic Pilot Strength Measurement Message: The base station shall process the
8 message as described in 3.6.6.2.2.1
9 18. Pilot Strength Measurement Message
10 19. Power Measurement Report Message
11 20. Release Order
12 21. Request Analog Service Order
13 22. Request Narrow Analog Service Order
14 23. Request Wide Analog Service Order
15 24. Resource Release Request Message
16 25. Resource Release Request Mini Message
17 26. Resource Request Message
18 27. Resource Request Mini Message
23 3.6.4.1.2.2).
28 35. Service Response Message:
3-56
C.S0005-0-2 v1.0
3 3.6.5 Registration
4 Registration is the process by which a mobile station notifies the base station of its location,
5 status, identification, slot cycle, and other characteristics. The base station can make use
6 of location information to efficiently page the mobile station when establishing a mobile
7 station terminated call. Registration also provides the mobile station’s
8 SLOT_CYCLE_INDEX parameter so that the base station can determine which Paging
9 Channel slots a mobile station operating in the slotted mode is monitoring. Registration
10 also provides the protocol revision number so that the base station knows the capabilities of
12 The CDMA system supports ten different forms of registration:
13 1. Power-up registration. The mobile station registers when it powers on, or switches
14 from using the analog system.
15 2. Power-down registration. The mobile station registers when it powers off if

16 previously registered in the current serving system.
17 3. Timer-based registration. The mobile station registers when a timer expires.
18 4. Distance-based registration. The mobile station registers when the distance

19 between the current base station and the base station in which it last registered
20 exceeds a threshold.
21 5. Zone-based registration. The mobile station registers when it enters a new zone.
22 6. Parameter-change registration. The mobile station registers when certain of its

23 stored parameters change or when it enters a new system.
24 7. Ordered registration. The mobile station registers when the base station requests
25 it.
26 8. Implicit registration. When a mobile station successfully sends an Origination
27 Message or Page Response Message, the base station can infer the mobile station’s
28 location. This is considered an implicit registration.
29 9. Traffic Channel registration. Whenever the base station has registration

30 information for a mobile station that has been assigned to a Traffic Channel, the
31 base station can notify the mobile station that it is registered.
32 10. User Zone Registration. The mobile station registers when it selects an active User
33 Zone (see 2.6.9.1.2).
34 The first five forms of registration, as a group, are called autonomous registration and are
35 conditioned, in part, by roaming status and by indicators contained in the System
36 Parameters Message (see 2.6.5.3). The base station may initiate ordered registration
37 through the Registration Request Order.
38 The base station can obtain registration information by sending the Status Request Message
39 to the mobile station on either the Paging Channel or the Forward Traffic Channel. If the
3-57
C.S0005-0-2 v1.0
1 base station is operating with the mobile station in Band Class 0, the base station can also
2 obtain registration information by sending the Status Request Order to the mobile station on
3 the Forward Traffic Channel. The base station may notify the mobile station that it is
4 registered through the Mobile Station Registered Message.
5 3.6.5.1 Registration on the Paging and Access Channels
6 The base station shall specify the forms of registration that are enabled, the corresponding
7 registration parameters, and the roaming status conditions for which registration is enabled
8 in the System Parameters Message. If any of the autonomous registration forms are
9 enabled, the base station should also enable parameter-change registration.
10 The base station should process an Origination Message or Page Response Message sent on
11 the Access Channel as an implicit registration of the mobile station sending the message.
12 The base station can obtain complete registration information about the mobile station at
13 any time by sending a Registration Request Order to the mobile station.
14 3.6.5.2 Registration on the Traffic Channels
15 The base station can obtain registration information from a mobile station on the Traffic
16 Channel by means of the Status Request Message or the Status Request Order. When the
17 base station has registration information for a mobile station, the base station may send a
18 Mobile Station Registered Message to the mobile station, specifying the base station’s
19 registration system, zone, and location information.
20 3.6.6 Handoff Procedures
21 3.6.6.1 Overview
22 3.6.6.1.1 Types of Handoff
23 The base station supports the following three handoff procedures:

24 • Soft Handoff: A handoff in which a new base station commences communications
25 with the mobile station without interrupting the communications with the old base
26 station. The base station3 can direct the mobile station to perform a soft handoff
27 only when all Forward Traffic Channels assigned to the mobile station have identical
28 band classes, frequency assignments and frame offsets. Soft handoff provides
29 diversity of Forward Traffic Channels and Reverse Traffic Channel paths on the
30 boundaries between base stations.
31 • CDMA-to-CDMA Hard Handoff: A handoff in which the base station directs the
32 mobile station to transition between disjoint sets of base stations, different band
33 classes, different frequency assignments, different radio configuration, or different
34 frame offsets.
3In this section the term base station may imply multiple cells or sectors.
3-58
C.S0005-0-2 v1.0
1 • CDMA-to-Analog Handoff: A handoff in which the base station directs the mobile
2 station from a Forward Traffic Channel to an analog voice channel.
3 Base station support of CDMA-to-CDMA hard handoff between different band classes and
4 support of CDMA-to-analog handoff is optional.
5 Section 2.6.6 describes the mobile station requirements during handoff.
6 3.6.6.1.2 Active Set
7 The Active Set contains the pilots (see 2.6.6.1.2) associated with the Forward Traffic
8 Channels assigned to the mobile station. Initially the base station informs the mobile
9 station of the contents of the Active Set using the Channel Assignment Message or the
10 Extended Channel Assignment Message; subsequent changes to the contents of the Active
11 Set are provided using the Extended Handoff Direction Message, General Handoff Direction
12 Message, or Universal Handoff Direction Message.
14 3.6.6.2.1 Overhead Information
15 The base station sends the following messages governing the pilot search procedures
16 performed by the mobile station:
18 • In-Traffic System Parameters Message
21 • Neighbor List Update Message
22 • Extended Neighbor List Update Message
24 • General Handoff Direction Message
25 • Extended Handoff Direction Message
26 • Candidate Frequency Search Request Message
27 • Candidate Frequency Search Control Message
28 • Universal Handoff Direction Message
29 3.6.6.2.1.1 System Parameters

30 The base station sends handoff related parameters on the Paging Channel in the System
31 Parameters Message and the Extended System Parameters Message.
32 The base station may revise handoff related parameters for a mobile station operating on
33 the Traffic Channel by sending the In-Traffic System Parameters Message.
3-59
C.S0005-0-2 v1.0
1 The base station may modify the values of the parameters SRCH_WIN_A, T_ADD, T_DROP,
2 T_COMP, and T_TDROP through the Extended Handoff Direction Message, the General
3 Handoff Direction Message, or the Universal Handoff Direction Message. In addition, the
4 base station may also modify the values of the parameters SRCH_WIN_N, SRCH_WIN_R,
5 SOFT_SLOPE, ADD_INTERCEPT, and DROP_INTERCEPT through the General Handoff
6 Direction Message or the Universal Handoff Direction Message.
7 3.6.6.2.1.2 Neighbor List

8 The base station sends a Neighbor List on the Paging Channel in the Neighbor List Message,
9 the Extended Neighbor List Message, or the General Neighbor List Message. The base station
10 should list the pilots in the Neighbor List Message in descending priority order (see
11 2.6.6.2.6.3).
12 The base station may revise the Neighbor List for a mobile station operating on the Traffic
13 Channel by sending a Neighbor List Update Message or an Extended Neighbor List Update
14 Message.
15 The base station shall not include a pilot that is a member of the mobile station’s Active Set
16 in a Neighbor List Update Message or an Extended Neighbor List Update Message. The base
17 station shall not specify more than N8m pilots in the Neighbor List Message, Extended
18 Neighbor List Message, General Neighbor List Message, or in the Extended Neighbor List
19 Update Message. The base station shall not specify more than 20 pilots in the Neighbor List
20 Update Message. The base station should list the pilots in the Neighbor List Update
21 Message in descending priority order (see 2.6.6.2.6.3).
22 The base station may also indicate the availability of neighboring analog systems in the
23 General Neighbor List Message to assist the mobile station in performing system reselection
24 (see 2.6.2.1.6).
25 3.6.6.2.1.3 Candidate Frequency Neighbor List
26 The base station sends a Candidate Frequency Neighbor List and inter-frequency hard
27 handoff related parameters in the Candidate Frequency Search Request Message. The base
28 station shall not specify more than N8m pilots in the Candidate Frequency Search Request
29 Message.
30 3.6.6.2.1.4 Candidate Frequency Search List
31 The base station designates a subset of the Candidate Frequency Neighbor List included in
32 the Candidate Frequency Search Request Message as the Candidate Frequency Search List.
33 For each pilot belonging to the Candidate Frequency Search List, the base station shall set
34 the corresponding SEARCH_SET field of the Candidate Frequency Search Request Message
35 to ‘1’.
3-60
C.S0005-0-2 v1.0
1 3.6.6.2.2 Call Processing During Handoff
2 3.6.6.2.2.1 Processing the Pilot Strength Measurement Message

3 The base station should use the pilot strength measurements in the Pilot Strength
4 Measurement Message to determine a new Active Set.
5 The base station may also use the PN phase measurements in the Pilot Strength
6 Measurement Message to estimate the propagation delay to the mobile station. This
7 estimate can be used to reduce Reverse Traffic Channel acquisition time.
8 The base station may respond to a Pilot Strength Measurement Message received from the
9 mobile station by sending the Extended Handoff Direction Message, the General Handoff
10 Direction Message, or the Universal Handoff Direction Message.
11 3.6.6.2.2.2 Processing the Extended Handoff Direction Message
12 The base station shall maintain a handoff message sequence number. If the base station
13 specifies that the mobile station is to use service negotiation, the base station shall set the
14 SERV_NEG variable (see 3.6.4.1.2.1.4) to be enabled at the action time of the message. The
15 sequence number shall be initialized to zero prior to the transmission of the first Extended
16 Handoff Direction Message, General Handoff Direction Message (see 3.6.6.2.2.10), or the
17 Universal Handoff Direction Message to the mobile station. The base station shall increment
18 the sequence number modulo 4 each time the base station modifies the pilot list (including
19 the order in which pilots are specified within the list) or the code channels (including a
20 change in the ordering such that the first code channel occurrence for any pilot is changed)
21 sent to the mobile station in an Extended Handoff Direction Message, a General Handoff
22 Direction Message, or a Universal Handoff Direction Message.
23 Following a hard handoff, the base station should set the handoff message sequence
24 number to the value of the LAST_HDM_SEQ field of the Handoff Completion Message and
25 should use the pilot order contained in the Handoff Completion Message to interpret the
26 contents of subsequent Power Measurement Report Messages.
27 The base station shall set the contents of an Extended Handoff Direction Message according
28 to the following rules:
29 • An Extended Handoff Direction Message shall list no more than N6m pilots in the
30 new Active Set.
31 • An Extended Handoff Direction Message shall identify the identical power control
32 subchannels (i.e., those carrying identical power control bits).
33 • An Extended Handoff Direction Message may change the code channel associated
34 with an Active Set pilot that remains in the new Active Set.
3-61
C.S0005-0-2 v1.0
1 • The base station specifies the long code mask to be used on the new Forward Traffic
2 Channel by using the PRIVATE_LCM field of the Extended Handoff Direction
3 Message. The base station may change the long code mask to be used on the new
4 Forward Traffic Channel via the PRIVATE_LCM field of the Extended Handoff
5 Direction Message only for CDMA-to-CDMA hard handoffs. If a change of long code
6 mask is specified and the base station does not specify an explicit action time in the
7 Extended Handoff Direction Message, the base station shall begin using the new long
8 code mask on the first 80 ms boundary (relative to System Time) occurring at least
9 80 ms after the end of the frame containing the last bit of the message.
10 • For CDMA-to-CDMA handoffs, the base station may require the mobile station to
11 perform a reset of the acknowledgment procedures by using the RESET_L2 field of
12 the Extended Handoff Direction Message. If the base station requires the mobile
13 station to reset the acknowledgment procedures, Layer 3 shall send an indication to
14 Layer 2 to reset the acknowledgment procedures (see 3.2.1.1 and 3.2.2.1 of
15 TIA/EIA/IS-2000-[4)[4]). The acknowledgment procedures shall be reset
16 immediately after the action time of the Extended Handoff Direction Message.
17 • For CDMA-to-CDMA hard handoffs, the base station may alter the frame offset by
18 setting the FRAME_OFFSET field to a new value. If the base station specifies a new
19 frame offset and does not specify an explicit action time, the base station shall
20 change its Forward and Reverse Traffic Channel frame offsets at the second 80 ms
21 boundary (relative to System Time) after the end of transmission of the Extended
22 Handoff Direction Message, unless the end of transmission of the message coincides
23 with an 80 ms boundary, in which case the change in frame offsets shall occur 80
24 ms after the end of transmission.
25 • For CDMA-to-CDMA hard handoffs to Band Class 0 or Band Class 3, the base
26 station may alter the nominal transmit power offset after handoff by setting the
27 NOM_PWR field to the new nominal transmit power offset. For CDMA-to-CDMA
28 hard handoffs to band classes other than Band Class 0 and Band Class 3, the base
29 station may alter the nominal transmit power offset after handoff by setting both the
30 NOM_PWR and NOM_PWR_EXT fields to the new nominal transmit power offset.
31 • The base station may specify a different band class by setting the BAND_CLASS and
32 CDMA_FREQ fields to the band class and CDMA frequency assignment respectively.
33 The base station shall not specify a band class not supported by the mobile station.
34 • If the base station sends the Extended Handoff Direction Message in assured mode,
35 the base station should set the action time of the message such that there is
36 sufficient time for the mobile station to transmit a message containing the
37 acknowledgment prior to the action time.
3-62
C.S0005-0-2 v1.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-63
C.S0005-0-2 v1.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 from the mobile station or
16 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.
20 For Forward Multiplex Options 3 through 16, the base station should discontinue
21 transmission of Forward Supplemental Code Channels removed from the Code Channel List
22 according to the following rules:
23 • If a General Handoff Direction Message is used to remove one or more Forward
24 Supplemental Code Channels, the base station should discontinue transmission on
25 those code channels no later than the action time of the General Handoff Direction
26 Message.
27 • If a Supplemental Channel Assignment Message is used to remove one or more

28 Forward Supplemental Code Channels, the base station should discontinue
29 transmission on those Forward Supplemental Code Channels no later than the
30 implicit action time of the Supplemental Channel Assignment Message.
31 3.6.6.2.2.8 Ordering Pilot Measurements From the Mobile Station

32 The base station may direct the mobile station to send a Pilot Strength Measurement
33 Message by sending a Pilot Measurement Request Order.
34 The base station may send a Periodic Pilot Measurement Request Order to direct the mobile
35 station to periodically send pilot strength measurements. In response to the order, the
36 mobile station reports the pilot strength measurements using the Periodic Pilot Strength
37 Measurement Message.
3-64
C.S0005-0-2 v1.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-65
C.S0005-0-2 v1.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 USE_SCRM_SEQ_NUM to the
34 sequence number corresponding to the SCRM_SEQ_NUM field in a Supplemental
35 Channel Request Message to which the mobile station is to match this message.
36 Otherwise, the base station shall set USE_SCRM_SEQ_NUM to ‘0’ and omit
37 SCRM_SEQ_NUM.
38 • A Supplemental Channel Assignment Message may specify Forward Supplemental
39 Code Channel assignments. If Forward Supplemental Code Channel assignment
40 information is included, the base station shall set FOR_INCLUDED to ‘1’ and include
41 the appropriate Forward Supplemental Code Channel assignment information.
42 Otherwise, the base station shall set FOR_INCLUDED to ‘0’.
3-66
C.S0005-0-2 v1.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-67
C.S0005-0-2 v1.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.
18 The base station shall set the contents of a General Handoff Direction Message according to
19 the following rules:
20 • A General Handoff Direction Message shall list no more than N6m pilots in the new
21 Active Set.
22 • The base station may include a Service Configuration Information Record in the
23 General Handoff Direction Message to accept a service configuration proposed in a
24 Service Request Message or Service Response Message, and instruct the mobile
25 station to begin using the service configuration.
26 • A General Handoff Direction Message shall identify the identical power control
28 • A General Handoff Direction Message shall identify the transmit power level of the
29 power control subchannels to the transmit power level of 20 ms frames at a 9600
30 bps or 14400 bps rate on their respective associated channels (Forward
31 Fundamental Channel or Forward Dedicated Control Channel).
32 • For CDMA-to-CDMA handoffs, the base station may specify Power Control
33 Subchannel Gain action time (PC_ACTION_TIME]. If PC_ACTION_TIME is included
34 in this message, the base station shall apply the new FPC_SUBCHAN_GAIN at the
35 time specified by PC_ACTION_TIME. If the PC_ACTION_TIME is not included in this
36 message but the explicit action time is included, the base station shall apply the
37 new FPC_SUBCHAN_GAIN at the action time of the General Handoff Direction
38 Message. If the implicit action time is used, the base station should gradually apply
39 any change in FPC_SUBCHAN_GAIN.
40 • A General Handoff Direction Message may change the code channel associated with
41 an Active Set pilot that remains in the new Active Set.
3-68
C.S0005-0-2 v1.0
2 Channel by using the PRIVATE_LCM field of the General Handoff Direction Message.
3 The base station may change the long code mask to be used on the new Forward
4 Traffic Channel via the PRIVATE_LCM field of the General Handoff Direction Message
5 only for CDMA-to-CDMA hard handoffs. If a change of long code mask is specified
6 and the base station does not specify an explicit action time in the General Handoff
7 Direction Message, the base station shall begin using the new long code mask on the
8 first 80 ms boundary (relative to System Time) occurring at least 80 ms after the end
9 of the frame containing the last bit of the message.
12 the General Handoff Direction Message. If the base station requires the mobile
15 TIA/EIA/IS-2000-[4)[4]). The acknowledgment procedures of the base station that
16 the mobile station is to handoff to shall be reset immediately after the action time of
22 boundary (relative to System Time) after the end of transmission of the General
35 • If the base station sends the General Handoff Direction Message in assured mode,
3-69
C.S0005-0-2 v1.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-70
C.S0005-0-2 v1.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-71
C.S0005-0-2 v1.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-72
C.S0005-0-2 v1.0
3 The base station shall set the contents of a Universal Handoff Direction Message according
4 to the following rules:
5 • A Universal Handoff Direction Message shall list no more than N6m pilots in the new
6 Active Set.
7 • The base station may include a Service Configuration Information Record in the
8 Universal Handoff Direction Message to accept a service configuration proposed in a
9 Service Request Message or Service Response Message, and instruct the mobile
10 station to begin using the service configuration.
11 • A Universal Handoff Direction Message shall identify the identical power control
13 • A Universal Handoff Direction Message shall identify the transmit power level of the
14 power control subchannels to the transmit power level of 20 ms frames at a 9600
15 bps or 14400 bps rate on their respective associated channels (Forward
16 Fundamental Channel or Forward Dedicated Control Channel).
17 • For CDMA-to-CDMA handoffs, the base station may specify Power Control
18 Subchannel Gain action time (PC_ACTION_TIME]. If PC_ACTION_TIME is included
19 in this message, the base station shall apply the new FPC_SUBCHAN_GAIN at the
20 time specified by PC_ACTION_TIME. If the PC_ACTION_TIME is not included in this
21 message but the explicit action time is included, the base station shall apply the
22 new FPC_SUBCHAN_GAIN at the action time of the Universal Handoff Direction
23 Message. If the implicit action time is used, the base station should gradually apply
24 any change in FPC_SUBCHAN_GAIN.
25 • A Universal Handoff Direction Message may change the code channel associated with
27 • A Universal Handoff Direction Message may delete the code channel associated with
29 • A Universal Handoff Direction Message may add the code channel associated with an
30 Active Set pilot that remains in the new Active Set.
32 Channel by using the PRIVATE_LCM field of the Universal Handoff Direction
33 Message. The base station may change the contents of this field only for CDMA-to-
34 CDMA hard handoffs. If a change of long code mask is specified and the base
35 station does not specify an explicit action time in the Universal Handoff Direction
36 Message, the base station shall begin using the new long code mask on the first 80
37 ms boundary (relative to System Time) occurring at least 80 ms after the end of the
38 frame containing the last bit of the message.
3-73
C.S0005-0-2 v1.0
3 the Universal Handoff Direction Message. If the base station requires the mobile
6 TIA/EIA/IS-2000-[4)[4]). The acknowledgment procedures of the base station that
7 the mobile station is to handoff to shall be reset immediately after the action time of
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-74
C.S0005-0-2 v1.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 data transfer rate associated with this Reverse Supplemental Channel
3-75
C.S0005-0-2 v1.0
1 assignment.
2 This message may specify the mapping between a particular SCCL_INDEX and a set of
3 fields that specifies the data transfer rate, QOF index, Forward Supplemental Channel
4 Walsh code for each PILOT_PN, and the active set for the Forward Supplemental Channel
5 associated with FOR_SCH_ID.
6 This message may also include REV_WALSH_ID field which specifies the Reverse
7 Supplemental Walsh cover.
8 This message also includes START_TIME_UNIT for this message, Forward Supplemental
9 Channel Assignment Mini Messages, or Reverse Supplemental Channel Assignment Mini
10 Messages, or Universal Handoff Direction Message.
11 The base station shall set the contents of an Extended Supplemental Channel Assignment
12 Message according to the following rules:
13 • An Extended Supplemental Channel Assignment Message may specify a Reverse

14 Supplemental Channel assignment. The base station shall set NUM_REV_SCH to
15 the number of Reverse Supplemental Channels to be assigned.
16 • An Extended Supplemental Channel Assignment Message may specify a Forward
17 Supplemental Channel assignment. The base station shall set NUM_FOR_SCH to
18 the number of Forward Supplemental Channels to be assigned..
19 • The base station shall set the START_TIME_UNIT field to indicate the unit of the
20 FOR_SCH_START_TIME included in this message and the Forward Supplemental
21 Channel Assignment Mini Messages and REV_SCH_START_TIME included in this
22 message and the Reverse Supplemental Channel Assignment Mini Messages. The
23 base station shall set this field to one less than the number of 20 ms intervals that
24 is to be used by the mobile station for calculating the start time included in Forward
25 Supplemental Channel assignments or Reverse Supplemental Channel assignments.
26 • An Extended Supplemental Channel Assignment Message may specify Forward
27 Supplemental Channel configuration information. The base station shall set
28 NUM_FOR_SCH_CFG to the number of Forward Supplemental Channel to be
29 configured.
30 • The base station shall set the NUM_REC field to the number of instances of the
31 following record minus one included in this message. The base station shall set the
32 fields within each record as follows:
33 – The base station shall set the SCCL_INDEX field to the index of the
34 Supplemental Channel Code Information Record in the Supplemental
35 Channel Code List Table.
36 – The base station shall set the FOR_SCH_RATE field to the appropriate data
37 rate in the Forward Supplemental Channel specification record indexed by
38 SCCL_INDEX.
3-76
C.S0005-0-2 v1.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 FOR_SCH_CC_INDEX field to the Forward
12 Supplemental Channel code index corresponding to the PILOT_PN.
13 • REV_SCH_DTX_DURATION: The base station shall set REV_SCH_DTX_DURATION

14 to the maximum duration of time in units of 20 ms that the mobile station is
15 allowed 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 the transmission
39 rate, code channel index, and the identifier of the Quasi Orthogonal Function corresponding
40 to the assignment.
41 The base station shall set the content of a Forward Supplemental Channel Assignment Mini
3-77
C.S0005-0-2 v1.0
2 • The base station shall set the FOR_SCH_ID to Forward Supplemental Channel
3 identifier of the burst assignment that this message carries.
4 • The base station shall set the FOR_SCH_DURATION field to '0000' to indicate that
5 the mobile station should stop processing the Forward Supplemental Channel
6 starting at the explicit start time of the message specified by
7 FOR_SCH_START_TIME. The base station shall set the FOR_ SCH_DURATION field
8 to ‘1111’ to indicate that the mobile station should process the Forward
9 Supplemental Channel, starting at the explicit start time of the message specified by
10 FOR_ SCH_START_TIME, until a subsequent Forward Supplemental Channel
11 Assignment Mini Message or an Extended Supplemental Channel Assignment
12 Message with the same FOR_SCH_ID field is received. The base station shall set the
13 FOR_ SCH_DURATION field to the duration in units of 20ms (see Table 3.7.3.3.2.37-
14 3), starting at the explicit start time of the message specified by
15 FOR_SCH_START_TIME, during which the mobile station is to process the Forward
17 • The base station shall set the FOR_SCH_START_TIME field to the System Time, in
18 units of time specified by START_TIME_UNIT, (modulo 32) at which the mobile
19 station is to start processing the Forward Supplemental Channel specified in this
20 message. The explicit start time for processing Forward Supplemental Channels is
21 the time for which:
22 (t/(START_TIME_UNIT+1) − FOR_SCH_START_TIME) mod 32 = 0,
24 • The base station shall set the SCCL_INDEX field to the index of the record in the
25 Forward Supplemental Channel Code list corresponding to the FOR_SCH_ID.
26 • If PILOT_GATING_USE_RATE is equal to ‘1’, the base station shall set

27 PILOT_GATING_USE_RATE to ‘0’ and start transmitting the Forward Power Control
28 Subchannel with the maximum rate at the action time of the message.
29 3.6.6.2.2.14 Processing of Reverse Supplemental Channel Assignment Mini Message
30 The base station may use this message to specify Reverse Supplemental Channel
31 assignment parameters for the mobile station Reverse Supplemental Channel. This
32 information includes the reverse supplemental channel identifier (REV_SCH_ID), the
33 duration of transmission on the Reverse Supplemental Channel, the start time for the burst
34 assignment, and the rate at which the mobile station may transmit.
35 The base station shall set the content of the Reverse Supplemental Channel Assignment Mini
3-78
C.S0005-0-2 v1.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 RATE (see Table 3.7.3.3.2.37-1) to indicate the Reverse
19 Supplemental Channel rate, which is assigned to the mobile station.
20 • If PILOT_GATING_USE_RATE is 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 the
39 mobile station in order for the mobile station to send a Pilot Strength
40 Measurement Mini Message.
3-79
C.S0005-0-2 v1.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-80
C.S0005-0-2 v1.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.
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-81
C.S0005-0-2 v1.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. In this case, the base station broadcasts messages on
13 the Paging Channel identifying the User Zones that fall within the coverage area of
14 the particular cell/sector. A mobile station, as part of its monitoring of the Paging
15 Channel, will identify the presence of a particular User Zone.
16 • Mobile Specific User Zones: Mobile Specific User Zones are not broadcast by the base
17 station. A mobile station may use other overhead message parameters and compare
18 them with internally stored User Zone parameters to identify the presence of a
19 particular User Zone. These parameters may include: SID, NID, BASE_ID,
20 BASE_LAT, and BASE_LONG.
22 If the base station supports CDMA Tiered Services, the base station sends the following
23 messages to assist the mobile station in identifying the presence of User Zones and to
24 validate the User Zone requested by a mobile station:
27 • User Zone Update Message
28 • User Zone Reject Message
29 3.6.7.2.1 User Zone Identification Message
30 The base station identifies Broadcast User Zones supported by the base station by sending
31 the User Zone Identification Message on the Paging Channel. The base station should list
32 the UZID of each Broadcast User Zone supported by the base station.
33 3.6.7.2.2 Private Neighbor List Message
34 The base station sends a Private Neighbor List and identifies the User Zones supported by
35 its private neighbor base stations by sending the Private Neighbor List Message on the
36 Paging Channel. The Private Neighbor List Message shall list no more than N8m private
37 neighbors.
3-82
C.S0005-0-2 v1.0
1 3.6.7.2.3 User Zone Update Message and User Zone Reject Message on f-dsch
2 For a mobile station operating in the Waiting for Order Substate, Waiting for Mobile Station
3 Answer Substate, Conversation Substate, or Release Substate of the Mobile Station Control on
4 the Traffic Channel State, the base station may update the User Zone associated with the
5 mobile station by sending a User Zone Update Message. The base station may also send a
6 User Zone Reject Message to reject the User Zone requested by the mobile station in the
7 Origination Message, Page Response Message, or User Zone Update Request Message. The
8 base station may include the ASSIGN_UZID field in the User Zone Reject Message to assign
9 a User Zone to the mobile station to replace the rejected User Zone.
10 3.6.7.2.4 User Zone Reject Message on f-csch

11 The base station may send the User Zone Reject Message on the Paging Channel to reject
12 the User Zone requested by the mobile station in the Registration Message, Origination
13 Message, or Page Response Message. The base station may include the ASSIGN_UZID field
14 in the User Zone Reject Message to assign a User Zone to the mobile station to replace the
15 rejected User Zone.
16
3-83
C.S0005-0-2 v1.0
1 3.7 PDU Formats for Messages
2 The following sections specify the requirements on the PDU formats transmitted on the
3 f_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
12
3-84
C.S0005-0-2 v1.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-85
C.S0005-0-2 v1.0
1 Table 3.7.2.3-1. f-csch Messages
MSG_TAG Section
Message Name Number
System Parameters Message SPM 3.7.2.3.2.1

Access Parameters Message APM 3.7.2.3.2.2
Neighbor List Message (Band Class 0 only) NLM 3.7.2.3.2.3
CDMA Channel List Message CCLM 3.7.2.3.2.4
Channel Assignment Message CAM 3.7.2.3.2.8
Authentication Challenge Message AUCM 3.7.2.3.2.10
SSD Update Message SSDUM 3.7.2.3.2.11
Feature Notification Message FNM 3.7.2.3.2.12
Extended System Parameters Message ESPM 3.7.2.3.2.13
Extended Neighbor List Message (band classes other ENLM 3.7.2.3.2.14
than Band Class 0)
Status Request Message STRQM 3.7.2.3.2.15
Service Redirection Message SRDM 3.7.2.3.2.16
General Page Message GPM 3.7.2.3.2.17
Global Service Redirection Message GSRDM 3.7.2.3.2.18
TMSI Assignment Message TASM 3.7.2.3.2.19
PACA Message PACAM 3.7.2.3.2.20
Extended Channel Assignment Message ECAM 3.7.2.3.2.21
General Neighbor List Message GNLM 3.7.2.3.2.22
User Zone Identification Message UZIM 3.7.2.3.2.23
Private Neighbor List Message PNLM 3.7.2.3.2.24
Reserved -- 3.7.2.3.2.25
Sync Channel Message SCHM 3.7.2.3.2.26
Extended Global Service Redirection Message EGSRM 3.7.2.3.2.27
Extended CDMA Channel List Message ECCLM 3.7.2.3.2.28
User Zone Reject Message UZRM 3.7.2.3.2.29

2
3-86
C.S0005-0-2 v1.0
3 The following sections specify the contents of message body for each message that may be
4 sent on the f-csch.
5
3-87
C.S0005-0-2 v1.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)

4
3-88
C.S0005-0-2 v1.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
3 PILOT_PN - Pilot PN sequence offset index.

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-89
C.S0005-0-2 v1.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-90
C.S0005-0-2 v1.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.
7
8 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.

9
10 PAGE_CHAN - Number of Paging Channels.

11 The base station shall set this field to the number of Paging
12 Channels on this CDMA Channel. The base station shall not
14 MAX_SLOT_CYCLE- - Maximum slot cycle index.
15 _INDEX The base station shall set this field to the
16 SLOT_CYCLE_INDEX value corresponding to the maximum
17 slot cycle length permitted (see 2.6.2.1.1).
18 HOME_REG - Home registration indicator.
19 If mobile stations that are not roaming (see 2.6.5.3) and have
20 MOB_TERM_HOME equal to ‘1’ are to be enabled for
21 autonomous registrations, the base station shall set this field
22 to ‘1’. If such mobile stations are not to be enabled for
23 autonomous registration, the base station shall set this field
24 to ’0’.
25 FOR_SID_REG - SID roamer registration indicator.
26 If mobile stations that are foreign SID roamers (see 2.6.5.3)
27 and have MOB_TERM_FOR_SID equal to ‘1’ are to be enabled
28 for autonomous registration, the base station shall set this
29 field to ‘1’. If such mobile stations are not to be enabled for
31 to ’0’.
32 FOR_NID_REG - NID roamer registration indicator.
33 If mobile stations that are foreign NID roamers (see 2.6.5.3)
34 and have MOB_TERM_FOR_NID equal to ‘1’ are to be enabled
35 for autonomous registration, the base station shall set this
36 field to ‘1’. If such mobile stations are not to be enabled for
38 to ‘0’.
3-91
C.S0005-0-2 v1.0
1 POWER_UP_REG - Power-up registration indicator.

2 If mobile stations enabled for autonomous registration are to
3 register immediately after powering on and receiving the
4 system overhead messages, the base station shall set this field
5 to ‘1’; otherwise, the base station shall set this field to ‘0’.
6 POWER_DOWN_REG - Power-down registration indicator.
7 If mobile stations enabled for autonomous registration are to
8 register immediately before powering down, the base station
9 shall set this field to ‘1’; otherwise, the base station shall set
11 PARAMETER_REG - Parameter-change registration indicator.
12 If mobile stations are to register on parameter change events
13 as specified in 2.6.5.1.6, the base station shall set this field to
14 ‘1’. If not, the base station shall set this field to ‘0’.
15 REG_PRD - Registration period.
16 If mobile stations are not to perform timer-based registration,
17 the base station shall set this field to ‘0000000’. If mobile
18 stations are to perform timer-based registration, the base
19 station shall set this field to the value in the range 29 to 85
20 inclusive, such that the desired timer value is
21 2REG_PRD/4 × 0.08 seconds.

22 BASE_LAT - Base station latitude.
23 The base station shall set this field to its latitude in units of
24 0.25 second, expressed as a two’s complement signed number
25 with positive numbers signifying North latitudes. The base
26 station shall set this field to a value in the range -1296000 to
27 1296000 inclusive (corresponding to a range of -90° to +90°).
28 BASE_LONG - Base station longitude.
29 The base station shall set this field to its longitude in units of
31 with positive numbers signifying East longitude. The base
32 station shall set this field to a value in the range -2592000 to
33 2592000 inclusive (corresponding to a range of -180° to
34 +180°).
35 REG_DIST - Registration distance.
36 If mobile stations are to perform distance-based registration,
37 the base station shall set this field to the non-zero “distance”
38 beyond which the mobile station is to re-register (see
39 2.6.5.1.4). If mobile stations are not to perform distance-
40 based registration, the base station shall set this field to 0.
41 SRCH_WIN_A - Search window size for the Active Set and Candidate Set.
43 Table 2.6.6.2.1-1 corresponding to the search window size to
44 be used by mobile stations for the Active Set and Candidate
45 Set.
3-92
C.S0005-0-2 v1.0
1 SRCH_WIN_N - Search window size for the Neighbor Set.

4 be used by mobile stations for the Neighbor Set.
5 SRCH_WIN_R - Search window size for the Remaining Set.
8 be used by mobile stations for the Remaining Set.
9 NGHBR_MAX_AGE - Neighbor Set maximum AGE.
10 The base station shall set this field to the maximum AGE
11 value beyond which mobile stations are to drop members from
12 the Neighbor Set (see 2.6.6.2.6.3).
13 PWR_REP_THRESH - Power control reporting threshold.
14 The base station shall set this field to the number of bad
15 frames (see TIA/EIA/IS-2000-[2)[2]) to be received in a
16 measurement period on the channel which carries the Power
17 Control Subchannel before mobile stations are to generate a
18 Power Measurement Report Message (see 2.6.4.1.1). If the
19 base station sets PWR_THRESH_ENABLE to ‘1’, it shall not set
21 PWR_REP_FRAMES - Power control reporting frame count.
22 The base station shall set this field to the value such that the
23 number given by
24 2(PWR_REP_FRAMES/2) × 5 frames
25 is the number of frames over which mobile stations are to
26 count frame errors.
27 PWR_THRESH- - Threshold report mode indicator.
28 _ENABLE If mobile stations are to generate threshold Power
29 Measurement Report Messages, the base station shall set this
30 field to ‘1’. If mobile stations are not to generate threshold
31 Power Measurement Report Messages, the base station shall
33 PWR_PERIOD- - Periodic report mode indicator.
34 _ENABLE If mobile stations are to generate periodic Power Measurement
35 Report Messages, the base station shall set this field to ‘1’. If
36 mobile stations are not to generate periodic Power
39 PWR_REP_DELAY - Power report delay.
40 The period that mobile stations wait following a Power
41 Measurement Report Message before restarting frame counting
42 for power control purposes.
43 The base station shall set this field to the power report delay
44 value, in units of 4 frames (see 2.6.4.1.1).
3-93
C.S0005-0-2 v1.0
1 RESCAN - Rescan indicator.

2 If mobile stations are to re-initialize and re-acquire the system
3 upon receiving this message, the base station shall set this
4 field to ‘1’; otherwise, the base station shall set this field to ’0’.
5 T_ADD - Pilot detection threshold.
6 This value is used by the mobile station to trigger the transfer
7 of a pilot from the Neighbor Set or Remaining Set to the
8 Candidate Set (see 2.6.6.2.6) and to trigger the sending of the
9 Pilot Strength Measurement Message initiating the handoff
10 process (see 2.6.6.2.5.2).
11 The base station shall set this field to the pilot detection
12 threshold, expressed as an unsigned binary number equal to
13 - 2 × 10 × log10 Ec/Io .
14 T_DROP - Pilot drop threshold.
15 This value is used by mobile stations to start a handoff drop
16 timer for pilots in the Active Set and the Candidate Set (see
17 2.6.6.2.3).
18 The base station shall set this field to the pilot drop threshold,
19 expressed as an unsigned binary number equal to
20 - 2 × 10 × log10 Ec/Io .
21 T_COMP - Active Set versus Candidate Set comparison threshold.

22 Mobile stations transmit a Pilot Strength Measurement
23 Message when the strength of a pilot in the Candidate Set
24 exceeds that of a pilot in the Active Set by this margin (see
25 2.6.6.2.5.2).
26 The base station shall set this field to the threshold Candidate
27 Set pilot to Active Set pilot ratio, in units of 0.5 dB.
28 T_TDROP - Drop timer value.
29 Timer value after which an action is taken by mobile stations
30 for a pilot that is a member of the Active Set or Candidate Set,
31 and whose strength has not become greater than T_DROP. If
32 the pilot is a member of the Active Set, a Pilot Strength
33 Measurement Message is issued. If the pilot is a member of
34 the Candidate Set, it will be moved to the Neighbor Set.
35 The base station shall set this field to the T_TDROP value
36 shown in Table 2.6.6.2.3-1 corresponding to the drop timer
37 value to be used by mobile stations.
38 EXT_SYS_PARAMETER - Extended System Parameters Message indicator.
39 The base station shall set this field to ‘1’.
40 EXT_NGHBR_LIST - Extended Neighbor List Message indicator.
41 The base station sets this field to ‘1’ when it sends the
42 Extended Neighbor List Message on the Paging Channel;
43 otherwise the base station sets this field to ‘0’.
3-94
C.S0005-0-2 v1.0
1 If the base station is operating in Band Class 1, Band Class 3,

2 or Band Class 4 with MIN_P_REV less than six, it shall set
3 this field to ‘1’. If the base station is operating in Band Class
4 0, it shall set this field to ‘0’.
5 GEN_NGHBR_LIST - General Neighbor List Message indicator.
6 If the base station is sending the General Neighbor List
7 Message on the Paging Channel, it shall set this field to ‘1’;
8 otherwise, it shall set this field to ‘0’.
10 or Band Class 4 with MIN_P_REV greater than or equal to six,
11 and if EXT_NGHBR_LIST is set to ‘0’, the base station shall set
14 Band Class 6, or Band Class 7, Band Class 8, or Band Class
15 9, and if EXT_NGHBR_LIST is set to ‘0’, the base station shall
17
18 GLOBAL_REDIRECT - Global Service Redirection Message indicator.

19 If the base station is sending the Global Service Redirection
22 PRI_NGHBR_LIST - Private Neighbor List Message indicator.
23 If the base station is sending the Private Neighbor List Message
24 on the Paging Channel, it shall set this field to ‘1’; otherwise,
25 it shall set this field to ‘0’.
26 USER_ZONE_ID - User Zone Identification Message indicator.
27 If the base station is sending the User Zone Identification
30 EXT_GLOBAL-
31 _REDIRECT - Extended Global Service Redirection Message indicator.
32 If the base station is sending the Extended Global Service
33 Redirection Message on the Paging Channel, it shall set this
34 field to ‘1’; otherwise, the base station shall set this field to ‘0’.
35 EXT_CHAN_LIST - Extended CDMA Channel List Message indicator.
36 The base station shall set this field to ‘1’, if the Extended
37 Channel List Message is sent on the Paging Channel,
39
3-95
C.S0005-0-2 v1.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

5
3-96
C.S0005-0-2 v1.0
Field Length (bits)
MAX_REQ_SEQ 4
MAX_RSP_SEQ 4
AUTH 2
RAND 0 or 32
NOM_PWR_EXT 1

6 ACC_MSG_SEQ - Access parameters message sequence number.
7 The base station shall set this field to ACC_CONFIG_SEQ
8 (see 3.6.2.2).
9 ACC_CHAN - Number of Access Channels.
10 The base station shall set this field to one less than the
11 number of Access Channels associated with this Paging
12 Channel.
13 NOM_PWR - Nominal transmit power offset.
14 The base station shall set this field to the correction factor to
15 be used by mobile stations in the open loop power estimate,
16 expressed as a two’s complement value in units of 1 dB
17 (see TIA/EIA/IS-2000-[2)[2]).
18 INIT_PWR - Initial power offset for access.
20 be used by mobile stations in the open loop power estimate for
21 the initial transmission on an Access Channel, expressed as a
22 two’s complement value in units of 1 dB (see TIA/EIA/IS-
23 2000-[2)[2]).
24 PWR_STEP - Power increment.
25 The base station shall set this field to the value by which
26 mobile stations are to increase their transmit power between
27 successive access probes in an access probe sequence, in
28 units of 1 dB.
29 NUM_STEP - Number of access probes.
31 maximum number of access probes mobile stations are to
32 transmit in a single access probe sequence.
3-97
C.S0005-0-2 v1.0
1 MAX_CAP_SZ - Maximum Access Channel message capsule size.

2 The base station shall set this field to the value in the range 0
3 to 7, three less than the maximum number of Access Channel
4 frames in an Access Channel message capsule.
5 PAM_SZ - Access Channel preamble length.
7 number of Access Channel frames that mobile stations are to
8 transmit in each Access Channel preamble.
9 PSIST(0-9) - Persistence value for access overload classes 0 through 9.
10 If mobile stations in access overload classes 0 through 9 are
11 permitted to transmit requests on the Access Channel, the
12 base station shall set this field to the persistence value to be
13 used. If such mobile stations are not permitted to transmit
14 requests on the Access Channel, the base station shall set
16 PSIST(10) - Persistence value for access overload class 10 (test mobile
17 stations).
18 If mobile stations in access overload class 10 are permitted to
19 transmit requests on the Access Channel, the base station
20 shall set this field to the persistence value to be used. If such
21 mobile stations are not permitted to transmit requests on the
22 Access Channel, the base station shall set this field to ‘111’.
23 PSIST(11) - Persistence value for access overload class 11 (emergency
24 mobile stations).
30 PSIST(12) - Persistence value for access overload class 12.
3-98
C.S0005-0-2 v1.0

13 MSG_PSIST - Persistence modifier for Access Channel attempts for message
14 transmissions.
15 A mobile station multiplies its transmission probability by
16 2-MSG_PSIST for such attempts.
17 The base station shall set this field to the persistence modifier
18 for Access Channel attempts for message transmissions.
19 REG_PSIST - Persistence modifier for Access Channel attempts for
20 registrations which are not responses to the Registration
21 Request Order.
22 A mobile station multiplies its transmission probability by
23 2-REG_PSIST for such attempts.
24 The base station shall set this field to the persistence modifier
25 for Access Channel attempts for registrations which are not
26 responses to the Registration Request Order.
27 PROBE_PN_RAN - Time randomization for Access Channel probes.
28 A mobile station delays its transmission from System Time by
29 RN PN chips, where RN is a number determined by hashing
30 between 0 and 2PROBE_PN_RAN - 1 PN chips.
31 The base station shall set this field to the value in the range 0
32 to 9 inclusive such that the time randomization range is
33 2PROBE_PN_RAN - 1 PN chips.
34 ACC_TMO - Acknowledgment timeout.
35 The base station shall set this field to two less than the length
36 of time mobile stations are to wait after the end of an Access
37 Channel transmission before determining that the base
38 station did not receive the transmission, in units of 80 ms.
39 PROBE_BKOFF - Access Channel probe backoff range.
41 maximum number of slots mobile stations are to delay due to
42 random backoff between consecutive access probes.
3-99
C.S0005-0-2 v1.0
1 BKOFF - Access Channel probe sequence backoff range.

3 maximum number of slots mobile stations are to delay due to
4 random backoff between successive access probe sequences
5 and before the first access probe sequence of a response
6 access.
7 MAX_REQ_SEQ - Maximum number of access probe sequences for an Access
8 Channel request.
9 The base station shall set this field to the maximum number
10 of access probe sequences mobile stations are to transmit for
11 an Access Channel request. The base station shall set this
12 field to a value greater than 0.
13 MAX_RSP_SEQ - Maximum number of access probe sequences for an Access
14 Channel response.
16 of access probe sequences mobile stations are to transmit for
17 an Access Channel response. The base station shall set this
18 field to a value greater than 0.
19 AUTH - Authentication mode.
20 If mobile stations are to include standard authentication data
21 in Access Channel messages, the base station shall set this
22 field to ‘01’. If mobile stations are not to include
23 authentication data in Access Channel messages, the base
24 station shall set this field to ‘00’. All other values are
25 reserved.
26 RAND - Random challenge value.
27 If the AUTH field is set to ‘01’, the base station shall set this
28 field to the random challenge value to be used by mobile
29 stations for authentication. If the AUTH field is set to any
30 other value, the base station shall omit this field.
31 NOM_PWR_EXT - Extended nominal transmit power.
32 If the base station is operating in Band Class 0 or Band Class
33 3, it shall set this field to ‘0’.
34 If the base station is operating in a band class other than
35 Band Class 0 or Band Class 3, then it shall set this field as
36 follows:
37 If the correction factor to be used by mobile stations in the
38 open loop power estimate is between -24 dB and -9 dB
39 inclusive, the base station shall set this field to ‘1’; otherwise
40 (the correction factor is in the range -8 dB to 7 dB inclusive),
41 the base station shall set this field to ‘0’.
42
3-100
C.S0005-0-2 v1.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-101
C.S0005-0-2 v1.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.
001 The neighbor base station has the same number of frequencies having
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.

station.
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-102
C.S0005-0-2 v1.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 the
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.
5
3-103
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-[2)[2]), the base station
20 shall include their 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 TIA/EIA/IS-2000-
24 [2)[2]).
25
3-104
C.S0005-0-2 v1.0
1 3.7.2.3.2.5 Reserved
2 No text.
3
3-105
C.S0005-0-2 v1.0
1 3.7.2.3.2.6 Reserved
2 No text.
3
3-106
C.S0005-0-2 v1.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.
13
3-107
C.S0005-0-2 v1.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
RESPOND 1
FREQ_INCL 1
CDMA_FREQ 0 or 11
PILOT_PN 9
11
3-108
C.S0005-0-2 v1.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-109
C.S0005-0-2 v1.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
RESPOND 1
FREQ_INCL 1
BAND_CLASS 0 or 5
CDMA_FREQ 0 or 11
PILOT_PN 9
8 ASSIGN_MODE - Assignment mode.

10 Table 3.7.2.3.2.8-1 corresponding to the assignment mode for
11 this assignment.
12
3-110
C.S0005-0-2 v1.0
1 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

5 the additional record fields included in this assignment
6 record.
7 Additional record fields - Additional record fields.
8 The additional record fields are determined by the value of
9 ASSIGN_MODE, as described below.
10
11 If the ASSIGN_MODE field is set to ‘000’, the base station shall include the following fields:
12 FREQ_INCL - Frequency included indicator.
13 If the CDMA_FREQ field is included in this assignment record,
14 the base station shall set this bit to ‘1’. If the CDMA_FREQ
15 field is not included in this assignment record, the base
17 CODE_CHAN - Code channel.
18 The base station shall set this field to the code channel index
19 (see TIA/EIA/IS-2000-[2)[2]) in the range 1 to 63 inclusive
20 that the mobile station is to use on the Fundamental Channel
21 of the Forward Traffic Channel.
22 CDMA_FREQ - Frequency assignment.
23 If the FREQ_INCL bit is set to ‘1’, the base station shall set
24 this field to the CDMA Channel number corresponding to the
25 CDMA frequency assignment for the CDMA Channel
26 containing the Forward Traffic Channel the mobile station is
27 to use. If the FREQ_INCL bit is set to ‘0’, the base station
28 shall omit this field.
3-111
C.S0005-0-2 v1.0
1 FRAME_OFFSET - Frame offset.

2 The Forward and Reverse Traffic Channel frames are delayed
3 FRAME_OFFSET × 1.25 ms relative to system timing (see
4 TIA/EIA/IS-2000-[2)[2]).
5 The base station shall set this field to the Forward and
6 Reverse Traffic Channel frame offset.
7 ENCRYPT_MODE - Message encryption mode.
8 The base station shall set this field to the ENCRYPT_MODE
10 encrypting mode that is to be used for messages sent on the
11 Forward and Reverse Traffic Channels, as specified
12 in 2.3.12.2.
13
14 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 Reserved
15

17 The base station shall add reserved bits as needed in order to
18 make the total length of the fields after the preceding
19 ADD_RECORD_LEN field through this RESERVED field equal
20 to an integer number of octets. The base station shall set
22
24 RESPOND - Respond on new Access Channel indicator.
25 If the mobile station is to retransmit an Origination Message or
26 Page Response Message after processing this channel
27 assignment, the base station shall set this field to ‘1’. The
28 base station may set this field to ‘0’ only in response to a Page
3-112
C.S0005-0-2 v1.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
33 TIA/EIA/IS-2000-6)[6]) after processing this channel
37 ANALOG_SYS - System indicator.
38 If USE_ANALOG_SYS is equal to ‘0’, the base station shall set
39 this field to ‘0’. Otherwise, the base station shall set this field
40 to ‘0’ if the mobile station is to use analog system A, or to ‘1’ if
41 the mobile station is to use analog system B.
42 USE_ANALOG_SYS - Use analog system indicator.
43 The base station shall set this field to ‘1’ to direct the mobile
44 station to the analog system specified by ANALOG_SYS;
45 otherwise, the base station shall set this field to ‘0’.
3-113
C.S0005-0-2 v1.0

2 The base station shall set this field according to values defined
3 in TSB58-A.
4
6 SID - System identification of the analog system.
8 of the analog system supporting the assigned voice channel
9 for this assignment (see TIA/EIA/IS-2000-[6)[6]).
10 VMAC - Voice mobile station attenuation code.
11 The base station shall set this field to the mobile station
12 power level associated with the assigned voice channel for this
13 assignment (see TIA/EIA/IS-2000-[6)[6]).
14 ANALOG_CHAN - Voice channel number.
15 The base station shall set this field to the voice channel
16 number for this assignment (see TIA/EIA/IS-2000-[6)[6]).
17 SCC - SAT color code.
18 The base station shall set this field to the supervisory audio
19 tone color code associated with the assigned voice channel. If
20 the assignment is to a narrow analog channel, the base
21 station shall set this field to the two least significant bits of
22 the DSCC.
23 MEM - Message encryption mode indicator.
24 If analog control message encryption is to be enabled on the
25 assigned forward and reverse analog voice channels, the base
26 station shall set this bit to ‘1’; otherwise, the base station
27 shall set this bit to ‘0’.
28 AN_CHAN_TYPE - Analog voice channel type.
29 The base station shall set this field to the analog channel type
30 as specified in Table 3.7.3.3.2.6-1. If the mobile station does
31 not have narrow analog capability, the base station shall set
33 DSCC_MSB - Digital supervisory audio tone color code most significant bit.
34 The base station shall set this field to ‘0’ when directing
35 handoff to a wide analog channel. The base station shall set
36 this field to the most significant bit of the DSCC when
37 directing handoff to a narrow analog channel.

40 in TSB58-A.
41
3-114
C.S0005-0-2 v1.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
13 this field to ‘0’; otherwise, the base station shall set this field
14 as follows.
15 If the base station has received a Page Response Message that
16 specifies a packet data service option or other non-voice
17 service option, and the mobile station is to bypass the Waiting
18 for Order Substate and the Waiting for Mobile Station Answer
19 Substate, the base station shall set this field to ‘1’; otherwise,
21 DEFAULT_CONFIG - Default Configuration.
22 If the GRANTED_MODE field is set to ‘00’, the base station
23 shall set this field as specified in Table 3.7.2.3.2.8-3 to
24 indicate an initial multiplex option and Radio Configuration
25 for the Forward and Reverse Traffic Channels.
3-115
C.S0005-0-2 v1.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-116
C.S0005-0-2 v1.0
7 not to take place before the base station sends the first Service
8 Connect Message.
9 CODE_CHAN - Code channel.
11 (see TIA/EIA/IS-2000-[2)[2]) in the range 1 to 63 inclusive
13 of the Forward Traffic Channel.
17 TIA/EIA/IS-2000-[2)[2]).
25 in 2.3.12.2.
28 this field to the CDMA band class, as specified in TSB58-A,
29 corresponding to the CDMA frequency assignment for the
30 CDMA Channel containing the Forward Traffic Channel the
31 mobile station is to use. If the FREQ_INCL bit is set to ‘0’, the
32 base station shall omit this field.
35 this field to the CDMA Channel number, in the specified
36 CDMA band class, corresponding to the CDMA frequency
37 assignment for the CDMA Channel containing the Forward
38 Traffic Channel the mobile station is to use. If the
39 FREQ_INCL bit is set to ‘0’, the base station shall omit this
40 field.
3-117
C.S0005-0-2 v1.0
7 Response Message.
18 CDMA Channel containing the Paging Channel the mobile
19 station is to use. If the FREQ_INCL bit is set to ‘0’, the base
25 assignment for the CDMA Channel containing the Paging
26 Channel the mobile station is to use. If the FREQ_INCL bit is
27 set to ‘0’, the base station shall omit this field.
36 base station.
43
3-118
C.S0005-0-2 v1.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 TSB58-A. If the mobile station
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-119
C.S0005-0-2 v1.0

9 remaining six bits of the EXTENDED_BURST_TYPE_INTER-
10 NATIONAL field shall specify the COUNTRY_BURST_TYPE.
11 The mobile 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)
23
3-120
C.S0005-0-2 v1.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).
7
3-121
C.S0005-0-2 v1.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.
6
3-122
C.S0005-0-2 v1.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.
12 RECORD_TYPE - Information record type.
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.
17 Type-specific fields - Type-specific fields.
18 The base station shall include type-specific fields as specified
19 in 3.7.5.
20
3-123
C.S0005-0-2 v1.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
3-124
C.S0005-0-2 v1.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

8 (see 3.6.2.2).
9 DELETE_FOR_TMSI - Delete foreign TMSI.
3-125
C.S0005-0-2 v1.0
1 The base station shall set this field to ‘1’ to cause the mobile
2 station to delete its TMSI if the TMSI was assigned in a
3 different TMSI zone from that specified by the TMSI_ZONE
4 field of this message; otherwise, the base station shall set this
5 field to ‘0’.
6 USE_TMSI - Use TMSI indicator.
8 Table 3.7.2.3.2.13-1 corresponding to the type of MSID that
9 the mobile station is to use on the Access Channel.
10 PREF_MSID_TYPE - Preferred Access Channel Mobile Station Identifier Type.
12 Table 3.7.2.3.2.13-1 corresponding to the type of MSID that
13 the mobile station is to use on the Access Channel.
14
15 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)
1 11 TMSI (valid TMSI is
assigned);
IMSI and ESN (TMSI not
assigned)
16
17 MCC - Mobile Country Code.

18 The base station shall set this field to the MCC (see 2.3.1)
19 IMSI_11_12 - 11th and 12th digits of the IMSI.
20 The base station shall set this field to the IMSI_11_12 (see
21 2.3.1).
22 TMSI_ZONE_LEN - TMSI zone length.
23 The base station shall set this field to the number of octets
24 included in the TMSI_ZONE. The base station shall set this
25 field to a value in the range 1 to 8 inclusive.
26 TMSI_ZONE - TMSI zone.
27 The base station shall set this field to the TMSI zone number
28 as specified in TIA/EIA/IS-735[33].
3-126
C.S0005-0-2 v1.0
1 BCAST_INDEX - Broadcast slot cycle index.

2 To enable periodic broadcast paging, the base station shall set
3 this field to an unsigned 3-bit number in the range 1-7, equal
4 to the broadcast slot cycle index as defined in 2.6.2.1.1.3.3.
5 To disable periodic broadcast paging, the base station shall
7 IMSI_T_SUPPORTED - IMSI_T support indicator.
8 The base station shall set this field to ‘1’ to indicate support
9 for a 15-digit IMSI_T addressing according to the CCITT
10 recommendation E.212.
11 P_REV - Protocol revision level.
13 MIN_P_REV - Minimum protocol revision level.
14 The base station sets this field to prevent mobile stations
15 which cannot be supported by the base station from accessing
16 the system.
17 The base station shall set this field to the minimum protocol
18 revision level that it supports. For Band Class 0 operation,
19 the base station should set this field to a value of ‘00000010’
20 or greater. For Band Class 1 or Band Class 4 operation, the
21 base station should set this field to a value of ‘00000001’ or
22 greater. For Band Class 3 operation, the base station should
23 set this field to a value of ‘00000011’ or greater. For Band
24 Class 2 or Band Class 5 operation, the base station should set
25 this field to a value of ‘00000101’ or greater. For Band Class
26 6 or, Band Class 7, Band Class 8, or Band Class 9 operation,
27 the base station should set this field to ‘00000110’.
28 SOFT_SLOPE - The slope in the inequality criterion for adding a pilot to the
29 Active Set, or dropping a pilot from the Active Set (see
30 2.6.6.2.3 and 2.6.6.2.5.2).
31 The base station shall set this field as an unsigned binary
32 number.
33 ADD_INTERCEPT - The intercept in the inequality criterion for adding a pilot to
34 the Active Set (see 2.6.6.2.5.2).
35 The base station shall set this field as a two’s complement
36 signed binary number, in units of dB.
37 DROP_INTERCEPT - The intercept in the inequality criterion for dropping a pilot
38 from the Active Set (see 2.6.6.2.3).
41 PACKET_ZONE_ID - Packet data services zone identifier.
42 If the base station supports a packet data service zone, the
43 base station shall set this field to its non-zero packet data
44 services zone identifier.
45 If the base station does not support a packet data service
46 zone, the base station shall set this field to ‘00000000’.
3-127
C.S0005-0-2 v1.0
1 MAX_NUM_ALT_SO - Maximum number of alternative service options.

3 of alternative service option numbers that the mobile station
4 is allowed to include in the Origination Message or the Page
5 Response Message.
6 RESELECT_INCLUDED - System reselection parameters included.
7 If the base station is including system reselection parameters,
8 the base station shall set this field to ‘1’; otherwise, the base
10 EC_THRESH - Pilot power threshold.
11 If RESELECT_INCLUDED is set to ‘1’, the base station shall
12 include the field EC_THRESH and set this field to:
13  (pilot_power_threshold + 115) 
14 where pilot_power_threshold is the pilot power, Ec, in
15 dBm/1.23 MHz, below which the mobile station is to perform
16 system reselection; otherwise, the base station shall omit this
17 field.
18 EC_IO_THRESH - Pilot Ec/ Io threshold.
19 If RESELECT_INCLUDED is set to ‘1’, the base station shall
20 include the field EC_IO_THRESH and set this field to:
21  - 20 × log10 (pilot_threshold ) 
22 where pilot_threshold is the pilot Ec/Io below which the mobile
23 station is to perform system reselection; otherwise, the base
25 PILOT_REPORT - Pilot reporting indicator.
26 The base station shall set this field to ‘1’ if the mobile station
27 is to report the additional pilots which have pilot strengths
28 exceeding T_ADD in all Access Channel messages. The base
29 station shall set this field to ‘0’ if the mobile station is to
30 report the additional pilots which have pilot strengths
31 exceeding T_ADD only in the Origination Message and the
32 Page Response Message.
33 NGHBR_SET-
34 _ENTRY_INFO - Neighbor Set access entry handoff information included
35 indicator.
36 If the base station is including information on the Neighbor
37 Set access entry handoff, the base station shall set this field
39 ACC_ENT_HO_ORDER - Access entry handoff permitted indicator.
40 If NGHBR_SET_ENTRY_INFO is set to ‘1’, the base station
42 otherwise, the base station shall omit this field.
3-128
C.S0005-0-2 v1.0
2 is permitted to perform an access entry handoff after receiving
3 a message while performing the Mobile Station Order and
4 Message Processing Operation in the Mobile Station Idle State
5 (see 2.6.2.4); otherwise, the base station shall set this field to
6 ‘0’.
7 NGHBR_SET-
8 _ACCESS_INFO - Neighbor Set access handoff included indicator.
9 If the base station is including information on the Neighbor
10 Set access handoff or access probe handoff, the base station
11 shall set this field to ‘1’, otherwise, the base station shall set
13 ACCESS_HO - Access handoff permitted indicator.
14 If NGHBR_SET_ACCESS_INFO is set to ‘1’, the base station
18 is permitted to perform an access handoff (see 2.6.3.1.3.2);
20 ACCESS_HO_MSG_RSP - Access handoff permitted for message response indicator.
21 If ACCESS_HO is set to ‘1’, the base station shall include this
22 field and set it as described below; otherwise, the base station
25 is permitted to perform an access handoff after receiving a
26 message and before responding to that message in the System
27 Access State; otherwise, the base station shall set this field to
28 ‘0’.
29 ACCESS_PROBE_HO - Access probe handoff permitted indicator.
30 If NGHBR_SET_ACCESS_INFO is set to ‘1’, the base station
34 is permitted to perform an access probe handoff (see
35 2.6.3.1.3.3); otherwise, the base station shall set this field to
36 ‘0’.
37 ACC_HO_LIST_UPD - Access handoff list update permitted indicator.
38 If ACCESS_PROBE_HO is included and is set to ‘1’, the base
39 station shall include this field and set it as described below;
42 is permitted to update the access handoff list during an
43 access attempt (see 2.6.3.1.7.2); otherwise, the base station
45 ACC_PROBE_HO-
3-129
C.S0005-0-2 v1.0
1 _OTHER_MSG - Access probe handoff permitted for messages other than the
2 Origination Message and the Page Response Message.
3 If ACCESS_PROBE_HO is set to ‘1’, the base station shall
7 is permitted to perform an access probe handoff for messages
8 other than the Origination Message and the Page Response
9 Message. The base station shall set this field to ‘0’ if the
10 mobile station is permitted to perform an access probe
11 handoff only for the Origination Message and the Page
12 Response Message. See 2.6.3.1.3.3.
13 MAX_NUM_PROBE_HO - Maximum number of times that the mobile station is
14 permitted to perform an access probe handoff.
15 If ACCESS_PROBE_HO is set to ‘1’, the base station shall
19 of times the mobile station is allowed to perform an access
20 probe handoff within an access attempt minus one.
21 NGHBR_SET_SIZE - Size of the Neighbor Set.
22 If NGHBR_SET_ENTRY_INFO or NGHBR_SET_ACCESS_INFO
23 is equal to ‘1’, the base station shall set this field to the
24 number of pilots included in the Neighbor List Message,
25 Extended Neighbor List Message, or General Neighbor List
26 Message; otherwise, the base station shall omit this field.
27 If NGHBR_SET_ENTRY_INFO is equal to ‘1’, the base station shall include
28 NGHBR_SET_SIZE occurrences of the following field:
29 ACCESS_ENTRY_HO - Access entry handoff permitted when entering the System
30 Access State.
32 is permitted to perform an access entry handoff to the base
33 station associated with the corresponding pilot between the
34 time it receives a message on the Paging Channel when in the
35 Mobile Station Idle State and it enters the System Access State
36 to respond to the message; otherwise, the base station shall
37 set this field to ‘0’. The base station shall use the same order
38 for the ACCESS_ENTRY_HO fields in this message as is used
39 for pilots which are listed in the Neighbor List Message,
41 Message. Specifically, the ith occurrence of the
42 ACCESS_ENTRY_HO field shall correspond the ith pilot in the
43 Neighbor List Message, Extended Neighbor List Message, or
44 General Neighbor List Message.
45 If NGHBR_SET_ACCESS_INFO is equal to ‘1’, the base station shall include
46 NGHBR_SET_SIZE occurrences of the following field:
3-130
C.S0005-0-2 v1.0
1 ACCESS_HO_ALLOWED - Access handoff and access probe handoff permitted for the
2 corresponding pilot while in the System Access State.
4 is permitted to perform an access handoff or access probe
5 handoff to the base station associated with the corresponding
6 pilot when the mobile station is in the System Access State
7 (see 2.6.3.1.8 and 2.6.3.1.9); otherwise, the base station shall
8 set this field to ‘0’. The base station shall use the same order
9 for the ACCESS_HO_ALLOWED fields in this message as is
10 used for pilots which are listed in the Neighbor List Message,
12 Message. Specifically, the ith occurrence of the
13 ACCESS_HO_ALLOWED field shall correspond the ith pilot in
14 the Neighbor List Message, Extended Neighbor List Message, or
15 General Neighbor List Message.
16 BROADCAST_GPS_ASST - Broadcast GPS Assist Indicator.
17 The base station shall set this field to ‘1’ if it supports
18 Broadcast GPS Assist capability; otherwise, the base station
20 QPCH_SUPPORTED - Quick Paging Channel Supported Indication.
21 If the base station supports Quick Paging Channel operation,
22 the base station shall set this field to ‘1’; otherwise the base
24 NUM_QPCH - Number of Quick Paging Channels.
25 If the base station sets QPCH_SUPPORTED to ‘1’, the base
28 The base station shall set this field to the number of Quick
29 Paging Channels on this CDMA Channel. The base station
30 shall not set this field to ‘00’.
31 QPCH_RATE - Quick Paging Channel indicator rate.
35 The base station shall set this field to the QPCH_RATE field
37 indicator rate used by the Quick Paging Channel in the
38 system.
3-131
C.S0005-0-2 v1.0
1 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
2 QPCH_POWER-
3 _LEVEL_PAGE - Quick Paging Channel paging indicator transmit power level.
7 The base station shall set this field to the Quick Paging
8 Channel paging indicator transmit power level relative to that
9 of the Pilot Channel as specified in Table 3.7.2.3.2.13-3.
10 Table 3.7.2.3.2.13-3 Quick Paging Channel Transmit

11 Power Level
12 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-132
C.S0005-0-2 v1.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.
15 The base station shall set this field to the Quick Paging
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 TIA/EIA/IS-2000-[2)[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_INCL is set to ‘0’, the base station shall
37 omit this field; otherwise, the base station shall include this
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 TIA/EIA/IS-2000.[2]), in units of
45 1.25 ms.
46
3-133
C.S0005-0-2 v1.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-134
C.S0005-0-2 v1.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.
5 Table 3.7.2.3.2.14-1 corresponding to the configuration of this
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.

station.
3-135
C.S0005-0-2 v1.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-136
C.S0005-0-2 v1.0
station has a Pilot Channel on the following frequency:
• If FREQ_INCL equals ‘0’ for this record, this 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.

4 offset for this neighbor, in units of 64 PN chips.
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-137
C.S0005-0-2 v1.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.
8
3-138
C.S0005-0-2 v1.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

6 QUAL_INFO_TYPE - Qualification information type.
8 Table 3.7.2.3.2.15-1 to show the inclusion of qualification
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-139
C.S0005-0-2 v1.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
Extended Multiplex Option 00011100 00000000
Information
Geo-location Information 00011110 00000000
Band Subclass Information 00011111 00000001
3 QUAL_INFO_LEN - Qualification information length.

5 included in the type-specific fields of the qualification
6 information.
8 The base station shall set these fields to the qualification
9 information according to the QUAL_INFO_TYPE field.
3-140
C.S0005-0-2 v1.0
1 If QUAL_INFO_TYPE is equal to ‘00000000’, the type-specific

2 fields are omitted.
3 If QUAL_INFO_TYPE is equal to ‘00000001’, the base station
4 shall use the following fixed-length format for the type-specific
5 fields:
6
Type-specific Field Length (bits)
BAND_CLASS 5
RESERVED 3

10 fields:
11
BAND_CLASS 5
OP_MODE 8
RESERVED 3
12

14 The base station shall set this field as defined in TSB58-A to
15 specify the band class qualification information.
16 OP_MODE - Operating mode.
17 The base station shall set this field as shown in
18 Table 3.7.2.3.2.15-3 to specify the operating mode
19 qualification information if MOB_P_REV of the current band
20 class is less than or equal to three. The base station shall set
21 this field as shown in Table 3.7.2.3.2.15-4 to specify the
22 operating mode qualification information if MOB_P_REV of the
23 current band class is greater than three.
24
3-141
C.S0005-0-2 v1.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 and Band 00000000

Class 4
CDMA mode in Band Class 0 and Band 00000001
Class 3
TIA/EIA/IS-2000.6 analog mode[6] 00000010
TIA/EIA/IS-91 wide analog mode[28] 00000011
TIA/EIA/IS-91 narrow analog mode[28] 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 00000000 or

00000001
Analog mode TIA/EIA/IS- 00000010
2000.[6]
Wide analog mode TIA/EIA/IS- 00000011
91[28]
Narrow analog mode TIA/EIA/IS- 00000100
91[28]
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
15 shown in Table 3.7.2.3.2.15-2 corresponding to the
16 information record requested.
17
3-142
C.S0005-0-2 v1.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-143
C.S0005-0-2 v1.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 EIA/TIA-553[15],
EIA/TIA/IS-54[25], TIA/EIA/IS-91[28],
TIA/EIA/IS-136[31], TIA/EIA-95[30], and
TIA/EIA/IS-2000-[6]
Redirection to a CDMA system as defined 00000010
in TIA/EIA-95[30] and TIA/EIA/IS-2000-
[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.
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
6 set this field to the number of octets in the type-specific fields
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
3-144
C.S0005-0-2 v1.0
Field Length (bits)
EXPECTED_SID 15
IGNORE_CDMA 1
SYS_ORDERING 3
RESERVED 5
2 EXPECTED_SID - Expected SID.

3 If the base station is redirecting the mobile station to a
4 specific system, the base station shall set this field to the SID
5 of that system; otherwise, the base station shall set this field
6 to 0.
7 IGNORE_CDMA - Ignore CDMA Available indicator.
9 mobile station is to ignore the CDMA Capability Message on
10 the analog system to which it is being redirected. The base
11 station shall set this field to ‘0’ to indicate that the mobile
12 station may discontinue service on the system to which it is
13 being redirected if the mobile station receives a CDMA
14 Capability Message with CDMA_AVAIL equal to ‘1’, and the
15 preferred mode of the mobile station is CDMA.
16 SYS_ORDERING - System ordering.
17 The base station shall set this field to the SYS_ORDERING
19 order in which the mobile station is to attempt to obtain
20 service on an analog system.
21
3-145
C.S0005-0-2 v1.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

6
3-146
C.S0005-0-2 v1.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

4 The base station shall set this field to the CDMA band class,
5 as specified in TSB58-A.
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’.
30
3-147
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-[4)[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
3-148
C.S0005-0-2 v1.0

2 (see 3.6.2.2).
3 ACC_MSG_SEQ - Access parameters message sequence number.
4 The base station shall set this field to ACC_CONFIG_SEQ
5 (see 3.6.2.2).
6 CLASS_0_DONE - Class 0 pages are done.
7 If all messages and records directed to mobile stations
8 operating in the slotted mode, active in this slot, and having
9 an assigned class 0 IMSI have been sent by the end of this
10 General Page Message, the base station shall set this field to
11 ‘1’; otherwise, the base station shall set this field to ‘0’.
12 CLASS_1_DONE - Class 1 pages are done.
13 If all messages and records directed to mobile stations
14 operating in the slotted mode, active in this slot, and having
15 an assigned class 1 IMSI have been sent by the end of this
16 General Page Message, the base station shall set this field to
18 TMSI_DONE - TMSI pages are done.
19 If all the page records having PAGE_CLASS equal to ‘10’ or
20 other directed messages for mobile stations operating in the
21 slotted mode, active in this slot, and having an assigned TMSI
22 have been sent by the end of this General Page Message, the
23 base station shall set this field to ‘1’; otherwise, the base
25 ORDERED_TMSIS - TMSIs sent in numerical order.
26 If all the page records of PAGE_CLASS equal to ‘10’ are sent
27 such that the TMSI code values of the TMSI_CODE_ADDR
28 fields for the mobile stations operating in the slotted mode are
29 in ascending numerical order in all the General Page
30 Messages sent within this slot, the base station shall set this
32 BROADCAST_DONE - Broadcast pages are done.
33 If all broadcast page records (PAGE_CLASS equal to ‘11’) have
34 been sent by the end of this General Page Message, the base
35 station shall set this field to ‘1’; otherwise, the base station
39 ADD_LENGTH - Number of octets in the page message specific fields.
40 If there are no additional page message specific fields, the
41 base station shall set this field to ‘000’.
42 ADD_PFIELD - Additional page message specific fields.
43 The base station shall not include any additional page
44 message specific fields, if ADD_LENGTH is ‘000’.
3-149
C.S0005-0-2 v1.0
1 SERVICE_OPTION - Service option.

2 If base station requests a special service option in the page
3 type-specific fields (i.e., the SDU_INCLUDED field, see
4 TIA/EIA/IS-2000.[4], is set to ‘1’), the base station shall set
5 this field to the service option code shown in TSB58-A,
6 corresponding to the requested service option; otherwise, the
8
3-150
C.S0005-0-2 v1.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).
10
3-151
C.S0005-0-2 v1.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-152
C.S0005-0-2 v1.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-153
C.S0005-0-2 v1.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-154
C.S0005-0-2 v1.0

10 make the length of the record equal to an integer number of
12
3-155
C.S0005-0-2 v1.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

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.
20
3-156
C.S0005-0-2 v1.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.
0100 – 1111 Reserved
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-157
C.S0005-0-2 v1.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

Value (binary) (Minutes)
000 1
001 2
010 5
011 10
100 20
101 30
110 45
111 60
7
3-158
C.S0005-0-2 v1.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-159
C.S0005-0-2 v1.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
3-160
C.S0005-0-2 v1.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-161
C.S0005-0-2 v1.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
3-162
C.S0005-0-2 v1.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
PILOT_REC_TYPE 0 or 3
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
3-163
C.S0005-0-2 v1.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
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)
3-164
C.S0005-0-2 v1.0
PWR_COMB_IND 1
CODE_CHAN_FCH 11
QOF_MASK_ID_FCH 2
CODE_CHAN_DCCH 11
QOF_MASK_ID_DCCH 2
2 ASSIGN_MODE - Assignment mode.

4 Table 3.7.2.3.2.21-1 corresponding to the assignment mode
5 for this assignment.
6
7 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

11 Additional record fields - Additional record fields.
12 The additional record fields are determined by the value of
13 ASSIGN_MODE, as described below.
3-165
C.S0005-0-2 v1.0

5 If MOB_P_REV is less than six, the base station shall not set
7 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.
9 BYPASS_ALERT-
3-166
C.S0005-0-2 v1.0

7 RESERVED - Reserved bit.
9 NUM_PILOTS - Number of pilots in the Active Set.
10 The base station shall set this field to number of pilots that
11 are to be in the mobile station’s Active Set on the Traffic
12 Channel minus one. The base station shall set this field to
13 the value in the range 0 to N6m-1 inclusive.
19 Reverse Traffic Channels, and to indicate that service
20 negotiation may take place before the base station sends the
27 Response Message, and to indicate that service negotiation
28 may take place before the base station sends the first Service
29 Connect Message.
37 Connect Message.
41 TIA/EIA/IS-2000-[2)[2]).
3-167
C.S0005-0-2 v1.0

5 in 2.3.12.2.
10 CDMA Channel containing the Forward Traffic Channel the
17 assignment for the CDMA Channel containing the Forward
18 Traffic Channel the mobile station is to use. If the
19 FREQ_INCL bit is set to ‘0’, the base station shall omit this
20 field.
21 The base station shall include NUM_PILOTS plus one occurrence of the following three-field
22 record, one for each member of the mobile station’s Active Set on the Traffic Channel.
26 PWR_COMB_IND - Power control symbol combining indicator.
27 If the Forward Traffic Channel associated with this pilot will
28 carry the same closed-loop power control subchannel bits as
29 that of the previous pilot in this message, the base station
31 this field to ‘0’. For the first occurrence of this record in the
32 message, the base station shall set this field to ‘0’.
33 CODE_CHAN - Code channel index.
35 (see 2.1.3.1.9 and 3.1.3.1.13 of TIA/EIA/IS-2000-[2)[2]) that
36 the mobile station is to use on the Forward Traffic Channel
37 associated with this pilot. If Radio Configuration 1, 2, 3, or 5
38 (see 3.1.3.1.2 of TIA/EIA/IS-2000-[2)[2]) is used, the base
39 station shall set this field in the range 1 to 63 inclusive. If
40 Radio Configuration 4, 6 or 8 is used, the base station shall
41 set this field in the range 1 to 127 inclusive. If Radio
42 Configuration 7 or 9 is used, the base station shall set this
43 field in the range 1 to 255 inclusive.
44 FOR_FCH_RC - Forward Fundamental Channel radio configuration
3-168
C.S0005-0-2 v1.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-169
C.S0005-0-2 v1.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
10 transmission power. The base station shall set this field as a
11 two’s complement signed binary number, in units of 1 dB.
12 FPC_FCH_FER - Fundamental Channel target Frame Error Rate.
13 The base station shall set this field to the target Frame Error
14 Rate on the Forward Fundamental Channel, as specified in
15 Table 3.7.3.3.2.25-2.
16 FPC_ FCH_MIN_SETPT - Minimum Fundamental Channel Outer Loop Eb/Nt setpoint.
17 The base station shall set this field to minimum Fundamental
18 Channel Outer Loop Eb/Nt setpoint, in units of 0.125 dB.
19 FPC_ FCH_MAX_SETPT - Maximum Fundamental Channel Outer Loop Eb/Nt setpoint.
20 The base station shall set this field to maximum Fundamental
22
23 REV_FCH-
24 _GATING_MODE - Reverse eighth gating mode indicator.
26 is allowed to perform the reverse eighth gating mode where
27 the 1/8th rate frames on the Reverse Fundamental Channel
28 are gated off for 10 ms per frame (see 2.1.3.7.8 of TIA/EIA/IS-
29 2000.[2]); otherwise, the base station shall set this field to ‘0’.
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
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_INCL field in the Extended
43 System Parameters Message is set to ‘0’, the base station shall
3-170
C.S0005-0-2 v1.0
1 REV_PWR-
3 If REV_PWR_CNTL_DELAY_INCL is set to ‘0’, the base station
4 shall omit this field; otherwise, the base station shall include
5 this field and set it as follows:
11 Subchannel, see 2.1.2.3.2 of TIA/EIA/IS-2000.[2]) used by the
12 mobile station, in units of 1.25 ms.
37 station is to use. If the FREQ_INCL bit is set to ‘0’, the base
44 Channel the mobile station is to use. If the FREQ_INCL bit is
45 set to ‘0’, the base station shall omit this field.
3-171
C.S0005-0-2 v1.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
28 TIA/EIA/IS-2000-[6)[6]) after processing this channel
32 ANALOG_SYS - System indicator.
33 If USE_ANALOG_SYS is equal to ‘0’, the base station shall set
35 to ‘0’ if the mobile station is to use analog system A, or to ‘1’ if
36 the mobile station is to use analog system B.
37 USE_ANALOG_SYS - Use analog system indicator.
38 The base station shall set this field to ‘1’ to direct the mobile
39 station to the analog system specified by ANALOG_SYS;

43 in TSB58-A.
44
3-172
C.S0005-0-2 v1.0
4 of the analog system supporting the assigned voice channel
5 for this assignment (see TIA/EIA/IS-2000-[6)[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 TIA/EIA/IS-2000-[6)[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 TIA/EIA/IS-2000-[6)[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
22 station shall set this bit to ‘1’; otherwise, the base station
36 in TSB58-A.
3-173
C.S0005-0-2 v1.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
10 this field; otherwise, the base station shall set this field as
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.
18 BYPASS_ALERT-
31 Reverse Traffic channels, and to indicate that service
32 negotiation may take place before the base station sends the
39 Response Message, and to indicate that service negotiation
40 may take place before the base station sends the first Service
41 Connect Message.
3-174
C.S0005-0-2 v1.0
8 Connect Message.
14 FOR_RC - Forward Traffic Channel radio configuration.
17 the Forward Traffic (Fundamental and Dedicated Control)
18 Channel before the first Service Connect Message is sent to the
19 mobile station.
23 3.7.2.3.2.21-3).
24 REV_RC - Reverse Traffic Channel radio configuration.
27 the Reverse Traffic (Fundamental and Dedicated Control)
28 Channel before the first Service Connect Message is sent to the
29 mobile station.
33 3.7.2.3.21-3).
37 TIA/EIA/IS-2000-[2)[2]).
45 in 2.3.12.2.
46 FPC_SUBCHAN_GAIN - Forward Power Control Subchannel relative gain.
3-175
C.S0005-0-2 v1.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
11 transmission power. The base station shall set this field as a
12 two’s complement signed binary number, in units of 1 dB.
13 NUM_PILOTS - Number of pilots in the Active Set.
14 The base station shall set this field to number of pilots that
15 are to be in the mobile station’s Active Set on the Traffic
16 Channel minus one. The base station shall set this field to
17 the value in the range 0 to N6m-1 inclusive.
18 CH_IND - Channel indicator.
19 The base station shall set this field as shown in Table
20 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
22
23 CH_RECORD_LEN - Channel record length.

25 the CH_RECORD_FIELDS included in this channel record.
26 CH_RECORD_FIELDS - Channel record fields.
27 The channel record fields are determined by the value of
28 CH_IND, as described below.
29 REV_FCH-
32 is allowed to perform the reverse eighth gating mode where
33 the 1/8th rate frames on the Reverse Fundamental Channel
34 are gated off for 10 ms per frame (see 2.1.3.7.8 of TIA/EIA/IS-
35 2000.[2]); otherwise, the base station shall set this field to ‘0’.
3-176
C.S0005-0-2 v1.0
1 The base station shall not set this field to ‘1’ if

2 REV_FCH_GATING_REQ included in the Origination Message
3 or Page Response Message is set to ‘0’.
4 REV_PWR-
12 If the REV_FCH_GATING_MODE field in this message is set to
13 ‘1’ and the REV_PWR_CNTL_INCL field in the Extended
14 System Parameters Message is set to ‘0’, the base station shall
16 REV_PWR-
27 mobile station, in units of 1.25 ms.
29 The base station shall set all the bits of this field to ‘0’ to make
30 the entire record octet-aligned.
31
32 If the CH_IND field is set to ‘01’, the base station shall include the following fields:
36 FPC_FCH_FER - Fundamental channel target Frame Error Rate.
38 Rate on the Forward Fundamental Channel, as specified in
39 Table 3.7.3.3.2.25-2.
3-177
C.S0005-0-2 v1.0

4 The base station shall include NUM_PILOTS plus one occurrence of the following record,
5 one for each member of the mobile station’s Active Set on the Traffic Channel.
9 ADD_PILOT_REC_INCL - Additional pilot information included indicator.
10 The base station shall set this field to ‘1’ if additional pilot
11 information listed in PILOT_REC_TYPE and RECORD_LEN
12 fields are included. The base station shall set this field to ‘0’ if
13 the corresponding pilot is the common pilot and there is no
14 additional pilot information included.
15 PILOT_REC_TYPE - Pilot record type.
16 If ADD_PILOT_REC_INCL is set to ‘1’, the base station shall
17 set this field to the PILOT_REC_TYPE value shown in Table
18 3.7.2.3.2.21-5 corresponding to the type of Pilot Record
19 specified by this record.
21 omit this field.
22
23 Table 3.7.2.3.2.21-5. Pilot Record Types
PILOT_REC_TYPE
Transmit Diversity Pilot 000

All other PILOT_REC_TYPE values are reserved
24
25 RECORD_LEN - Pilot record length.

28 of this pilot record.
30 omit this field.
31 Type-specific fields - Pilot record type-specific fields.
33 include type-specific fields based on the PILOT_REC_TYPE of
34 this pilot record.
36 omit this field.
3-178
C.S0005-0-2 v1.0
2 If PILOT_REC_TYPE is equal to ‘000’, the base station shall include the following fields:
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6
5 OTD_POWER_LEVEL - OTD transmit power level.

6 The base station shall set this field to the OTD transmit power
7 level relative to that of the Forward Pilot Channel, as specified
8 in Table 3.7.2.3.2.21-6.
9
10 Table 3.7.2.3.2.21-6. OTD Transmit Power Level
OTD_POWER_LEVEL Transmit Power Level
00 9 dB below the Forward Pilot

Channel transmit power
11 Same as the Forward Pilot
11

14

16 If the Forward Fundamental Traffic Channel associated with
17 this pilot will carry the same closed-loop power control
18 subchannel bits as that of the previous pilot in this message,
20 station shall set this field to ‘0’. For the first occurrence of
21 this record in the message, the base station shall set this field
22 to ‘0’.
23 CODE_CHAN_FCH - Code channel index for the Fundamental Channel.
3-179
C.S0005-0-2 v1.0

2 Spreading Rate 1, the base station shall set this field to the
3 code channel index (see 2.1.3.1.9 and 3.1.3.1.13 of
4 TIA/EIA/IS-2000-[2)[2]) that the mobile station is to use on
5 the Forward Fundamental Channel associated with this pilot.
6 If Radio Configuration 1, 2, 3, or 5 (see 3.1.3.1.2 of
7 TIA/EIA/IS-2000-[2)[2]) is used, the base station shall set this
8 field in the range 1 to 63 inclusive. If Radio Configuration 4, 6
9 or 8 is used, the base station shall set this field in the range 1
10 to 127 inclusive. If Radio Configuration 7 or 9 is used, the
11 base station shall set this field in the range 1 to 255 inclusive.
12 QOF_MASK_ID_FCH - Quasi-Orthogonal Function Mask Identifier for the
16 quasi-orthogonal function mask identifier (see Table
17 3.1.3.1.13-2 of TIA/EIA/IS-2000-[2)[2]) that the mobile station
18 is to use on the Forward Fundamental Channel associated
19 with this pilot.
23 CH_RECORD_LEN field through this RESERVED field equal to
24 an integer number of octets. The base station shall set these
25 bits to ‘0’.
27 FPC_DCCH_INIT_SETPT - Initial Dedicated Control Channel outer loop Eb/Nt setpoint.
28 The base station shall set this field to initial Dedicated Control
30 FPC_DCCH_FER - Dedicated Control Channel target Frame Error Rate.
32 Rate on the Dedicated Control Channel, as specified in Table
33 3.7.3.3.2.25-2.
34 FPC_ DCCH_MIN_SETPT - Minimum Dedicated Control Channel Outer Loop Eb/Nt
35 setpoint.
36 The base station shall set this field to minimum Dedicated
37 Control Channel Outer Loop Eb/Nt setpoint, in units of 0.125
38 dB.
39 FPC_ DCCH_MAX_SETPT - Maximum Dedicated Control Channel Outer Loop Eb/Nt
40 setpoint.
41 The base station shall set this field to maximum Dedicated
43 dB.
3-180
C.S0005-0-2 v1.0
2 record for each member of the mobile station’s Active Set on the Traffic Channel.
18 omit this field.
24 omit this field.
30 omit this field.
31
33
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6
34
35 OTD_POWER_LEVEL - OTD transmit power level.

37 level relative to that of the Forward Pilot Channel as specified
38 in Table 3.7.2.3.2.21-6.
3-181
C.S0005-0-2 v1.0

3

5 If the Forward Dedicated Control Traffic Channel associated
6 with this pilot will carry the same closed-loop power control
11 to ‘0’.
12 CODE_CHAN_DCCH - Code channel index for the Dedicated Control Channel.
17 the Forward Dedicated Control Channel associated with this
18 pilot. If Radio Configuration 1, 2, 3, or 5 (see 3.1.3.1.2 of
19 TIA/EIA/IS-2000-[2)[2]) is used, the base station shall set this
20 field in the range 1 to 63 inclusive. If Radio Configuration 4, 6
21 or 8 is used, the base station shall set this field in the range 1
22 to 127 inclusive. If Radio Configuration 7 or 9 is used, the
24 QOF_MASK_ID_DCCH - Quasi-Orthogonal Function Mask Identifier for the Dedicated
25 Control Channel.
30 is to use on the Forward Dedicated Control Channel
31 associated with this pilot.
37 bits to ‘0’.
38
43 FPC_DCCH_INIT_SETPT - Initial Dedicated Control Channel outer loop Eb/Nt setpoint.
44 The base station shall set this field to initial Dedicated Control Channel outer loop Eb/Nt
45 setpoint, in units of 0.125 dB.
3-182
C.S0005-0-2 v1.0
1 FPC_PRI_CHAN - Power Control Subchannel indicator.

3 is to perform the primary inner loop estimation on the
4 received Forward Fundamental Channel and the base station
5 is to multiplex the Power Control Subchannel on the Forward
6 Fundamental Channel. The base station shall set this field to
7 ‘1’ if the mobile station is to perform the primary inner loop
8 estimation on the received Forward Dedicated Control
9 Channel and the base station is to multiplex the Power
10 Control Subchannel on the Forward Dedicated Control
11 Channel.
14 Rate on the Forward Fundamental Channel.
23 Rate on the Dedicated Control Channel.
24 FPC_ DCCH_MIN_SETPT - Minimum Dedicated Control Channel Outer Loop Eb/Nt
25 setpoint.
26 The base station shall set this field to minimum Dedicated
28 dB.
29 FPC_ DCCH_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-183
C.S0005-0-2 v1.0
12 omit this field.
18 omit this field.
24 omit this field.
25
27
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6
28
29 OTD_POWER_LEVEL - OTD Transmit Power Level.

32 in Table 3.7.2.3.2.21-6.
3-184
C.S0005-0-2 v1.0
1 If the Forward Fundamental Traffic Channel associated with

2 this pilot will carry the same closed-loop power control
7 to ‘0’.
8 CODE_CHAN_FCH - Code channel index for the Fundamental Channel.
13 the Forward Channel associated with this pilot. If Radio
14 Configuration 1, 2, 3, or 5 (see 3.1.3.1.2 of TIA/EIA/IS-2000-
15 [2)[2]) is used, the base station shall set this field in the range
16 1 to 63 inclusive. If Radio Configuration 4, 6 or 8 is used, the
18 If Radio Configuration 7 or 9 is used, the base station shall
19 set this field in the range 1 to 255 inclusive.
20 QOF_MASK_ID_FCH - Quasi-Orthogonal Function Mask Identifier for the
26 is to use on the Forward Fundamental Channel associated
27 with this pilot.
28 CODE_CHAN_DCCH - Code channel index for the Dedicated Control channel.
32 TIA/EIA/IS-2000-[2)[2]), in the range of 1 to 255 inclusive,
33 that the mobile station is to use on the Dedicated Control
34 Channel associated with this pilot. If Radio Configuration 1,
35 2, 3, or 5 (see 3.1.3.1.2 of TIA/EIA/IS-2000-[2)[2]) is used, the
37 If Radio Configuration 4, 6 or 8 is used, the base station shall
41 QOF_MASK_ID_DCCH - Quasi-Orthogonal Function Mask Identifier for the Dedicated
42 Control Channel.
47 is to use on the Forward Dedicated Control Channel
48 associated with this pilot.
3-185
C.S0005-0-2 v1.0

5 bits to ‘0’.
6
3-186
C.S0005-0-2 v1.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
3-187
C.S0005-0-2 v1.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
Type-specific fields 0 or 8 × RECORD_LEN
SRCH_OFFSET_NGHBR 0 or 3

8 (see 3.6.2.2).
19 15 inclusive.
20 NGHBR_SRCH_MODE - Search mode.
22 Table 3.7.2.3.2.22-1 corresponding to the search mode.
23
3-188
C.S0005-0-2 v1.0
1 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
3 NGHBR_CONFIG-
4 _PN_INCL - Neighbor configuration and PN offset included.
5 If neighbor configuration and PN offset fields are included in
6 this message, the base station shall set this field to ‘1’;
8 FREQ_FIELDS_INCL - Frequency fields included.
9 If frequency fields are included in this message, the base
12 USE_TIMING - Use timing indicator.
13 If base station timing information is included for neighbor
14 base stations, the base station shall set this field to ‘1’;
16 GLOBAL_TIMING-
17 _INCL - Global timing included.
18 If USE_TIMING is set to ‘1’, the base station shall include the
19 field GLOBAL_TIMING_INCL and set this field as described
20 below; otherwise, the base station shall omit this field.
21 If base station timing information is included globally for all
22 neighbor base stations with TIMING_INCL equal to ‘1’, the
25 GLOBAL_TX-
26 _DURATION - Global neighbor transmit time duration.
27 If GLOBAL_TIMING_INCL is included and is set to ‘1’, the base
28 station shall include the field GLOBAL_TX_DURATION and
29 shall set this field as described below; otherwise, the base
31 The base station shall set this field to the duration of the base
32 station transmit window, during each period, in units of 80
33 ms. The base station should set this field to a value of 3 or
34 greater.
3-189
C.S0005-0-2 v1.0
1 GLOBAL_TX-
2 _PERIOD - Global neighbor transmit time period.
4 station shall include the field GLOBAL_TX_PERIOD and shall
5 set this field as described below; otherwise, the base station
7 The base station shall set this field to duration of the period,
8 in units of 80 ms.
9 NUM_NGHBR - Number of neighbor pilot PN sequences.
11 neighbors included in the message.
12
14 mobile station is to place in its Neighbor Set. The base station shall use the same order for
15 the following record in this message as is used for pilots which are listed in the Neighbor
16 List Message or Extended Neighbor List Message. Specifically, the ith occurrence of the
17 following record shall correspond the ith pilot in the Neighbor List Message or in the
18 Extended Neighbor List Message.
19

21 If NGHBR_CONFIG_PN_INCL = ‘1’, the base station shall set
22 this field to the value shown in Table 3.7.2.3.2.22-2
23 corresponding to the configuration of this neighbor; otherwise,
24 the base station shall omit this field.
25
3-190
C.S0005-0-2 v1.0
Value
(binary) Neighbor Configuration

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-191
C.S0005-0-2 v1.0
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:
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.
station has a Pilot Channel on the following frequency:
• If FREQ_INCL equals ‘0’ for this record, thisthe 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.

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
11 station shall set the search priority as shown in Table
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-192
C.S0005-0-2 v1.0
1 Table 3.7.2.3.2.22-3. Search Priority Field
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
11 this field; otherwise, the base station shall set this field as
12 follows:
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 in this assignment record, the base station shall
17 set this bit to ‘0’.
18 NGHBR_BAND - Neighbor band class.
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 TSB58-A, 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 included and is set to ‘1’, the base
27 station shall set this field to the CDMA Channel number, in
28 the specified CDMA band class, corresponding to the CDMA
29 frequency assignment for the CDMA Channel containing the
30 Paging Channel the mobile station is to search. If the
31 FREQ_INCL bit is omitted or is set to ‘0’, the base station shall
32 omit this field.
33 TIMING_INCL - Timing included indicator.
35 field TIMING_INCL and set this field as described below;
3-193
C.S0005-0-2 v1.0
1 If base station timing information is included for this neighbor

2 base station, the base station shall set this field to ‘1’;
4 NGHBR_TX_OFFSET - Neighbor transmit time offset.
5 If TIMING_INCL is included and is set to ‘1’, the base station
6 shall include the field NGHBR_TX_OFFSET and set this field
7 as described below; otherwise, the base station shall omit this
8 field.
9 The base station shall set this field to the time offset, in units
10 of 80 ms, from the beginning of the neighbor timing period to
11 the beginning of the first base station transmit window within
12 the period. The beginning of the neighbor timing period
13 occurs when t/4 mod (16384)= 0.
14 NGHBR_TX_DURATION - Neighbor transmit time duration.
15 If TIMING_INCL is included and is set to ‘1’ and
16 GLOBAL_TIMING_INCL is set to ‘0’, the base station shall
17 include the field NGHBR_TX_DURATION and set this field as
18 described below; otherwise, the base station shall omit this
19 field.
20 The base station shall set this field to duration of the base
21 station transmit window, during each period, in units of
22 80 ms. The base station should set this field to a value of 3 or
23 greater.
24 NGHBR_TX_PERIOD - Neighbor transmit time period.
27 include the field NGHBR_TX_PERIOD and set this field as
29 field.
32 NUM_ANALOG_NGHBR - Number of neighboring analog systems.
34 neighboring analog systems included in the message.
35
36 The base station shall include one occurrence of the following record for each neighboring
37 analog system included in the message:
38

42 SYS_A_B - System A/B.
3-194
C.S0005-0-2 v1.0
1 If BAND_CLASS is set to ‘00000’ or to ‘00011’, the base station

2 shall set this field to the value shown in Table 3.7.2.3.2.22-4
3 corresponding to the availability of neighboring analog
4 systems; otherwise, the base station shall set this field to ‘00’.
5 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
7 SRCH_OFFSET_INCL - Neighbor pilot channel search window offset included.

8 If the SRCH_OFFSET_NGHBR field is included in the following
9 records, the base station shall set this bit to ‘1’; otherwise, the
10 base station shall set this bit to ‘0’.
13 the following record in this message as is used for pilots which are listed in the Neighbor
14 List Message or Extended Neighbor List Message. Specifically, the ith occurrence of the
15 following record shall correspond the ith pilot in the Neighbor List Message or in the
16 Extended Neighbor List Message.
19 information listed in the NGHBR_PILOT_REC_TYPE and
20 RECORD_LEN fields are included. The base station shall set
21 this field to ‘0’ if the corresponding pilot is the common pilot
22 and there is no additional pilot information included.
23 NGHBR_PILOT_REC_TYPE - Neighbor Pilot record type
25 set this field to the NGHBR_PILOT_REC_TYPE value shown in
26 Table 3.7.2.3.2.22-5 corresponding to the type of Pilot Record
28
29 Table 3.7.2.3.2.22-5. Neighbor Pilot Record Types
NGHBR_PILOT_REC_TYPE
Common Pilot with Transmit 000

Diversity
All other NGHBR_PILOT_REC_TYPE values are reserved
30
3-195
C.S0005-0-2 v1.0

2 omit this field.
8 omit this field.
11 include type-specific fields based on the
12 NGHBR_PILOT_REC_TYPE of this pilot record.
14 omit this field.
15
16 If NGHBR_PILOT_REC_TYPE is equal to ‘000’, the base station shall include the following
17 fields:
18
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6
19

23 in Table 3.7.2.3.2.21-6.
26 SRCH_OFFSET_NGHBR - Neighbor pilot channel search window size offset.
27 If NGHBR_SRCH_MODE = ‘10’ or ‘11’ and
28 SRCH_OFFSET_INCL equals to ‘1’, then the base station shall
29 set this field to the value shown in Table 2.6.6.2.1-2
30 corresponding to the search window offset to be used by
31 mobile stations for this neighbor. If NGHBR_SRCH_MODE is
32 set to any other value or if SRCH_OFFSET_INCL equals to ‘0’,
34
3-196
C.S0005-0-2 v1.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’;
28
3-197
C.S0005-0-2 v1.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 8×
fields RADIO_INTERFACE_L
EN

9 (see 3.6.2.2).
10 NUM_RADIO_INTERFACE - Number of interface types.
11 The base station shall set this field to the number of radio
12 interface types for which private neighbors are included in
13 this message.
14 The base station shall include NUM_RADIO_INTERFACE occurrences of the following
15 record, one occurrence for each radio interface for which private neighbors are included in
16 this message.
17 RADIO_INTERFACE_TYPE - The radio interface type.
18 The base station shall set this field to the radio interface type
19 of this record as specified in Table 3.7.2.3.2.24-1.
3-198
C.S0005-0-2 v1.0
1 Table 3.7.2.3.2.24-1. Radio Interface Type
RADIO_INTERAFCE_TYPE Descriptions
(binary)
0000 MC system
0001-1111 Reserved
2 RADIO_INTERFACE_LEN - The length of the Radio Interface Type-specific fields.

4 the Radio Interface Type-specific fields of this record.
5 If RADIO_INTERFACE_TYPE is equal to ‘0000’, the base station shall include the following
6 fields:
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-199
C.S0005-0-2 v1.0
1 COMMON_INCL - Common configuration included indicator.

2 If all private neighbor base stations included in this message
3 are on the same CDMA band class and CDMA Channel
4 number as specified in the COMMON_BAND_CLASS and
5 COMMON_NGHBR_FREQ fields, the base station shall set this
7 COMMON_BAND_CLASS - Neighbor band class.
8 If COMMON_INCL is set to ‘1’, the base station shall set this
9 field to the CDMA band class as specified in TSB58
11 CDMA Channel containing the Paging Channel for all private
12 neighbors; otherwise, the base station shall omit this field.
13 COMMON_NGHBR_FREQ - Neighbor frequency assignment.
14 If the COMMON_INCL bit is set to ‘1’, the base station shall
15 set this field to the CDMA Channel number, in the specified
18 Channel for all private neighbor base station; otherwise, the
20 SRCH_WIN_N - Search window size for the Private Neighbor Set.
23 be used by mobile stations for the Private Neighbor Set.
24 NUM_PRI_NGHBR - Number of private neighbor pilot PN sequences.
25 The base station shall set this field to the number of private
27
28 The base station shall include NUM_PRI_NGHBR occurrences of the following record.
29 SID - System Identification.
31 number for this private neighbor system (see 2.6.5.2).
32 NID - Network Identification.
36 number for this private neighbor network (see 2.6.5.2).
37 PRI_NGHBR_PN - Private neighbor pilot PN sequence offset index.
39 offset for this private neighbor, in units of 64 PN chips.
3-200
C.S0005-0-2 v1.0
2 information listed in the NGHBR_PILOT_REC_TYPE and
6 NGHBR_PILOT_REC_TYPE - Neighbor Pilot record type
12 omit this field.
18 omit this field.
24 omit this field.
26 fields:
27
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6
28

32 in Table 3.7.2.3.2.21-6.
35 BAND_CLASS - Neighbor band class.
3-201
C.S0005-0-2 v1.0
1 If COMMON_INCL is set to ‘0’, the base station shall set this

2 field to the CDMA band class as specified in TSB58
4 CDMA Channel containing the Paging Channel for the private
5 neighbor; otherwise, the base station shall omit this field.
7 If the COMMON_INCL bit is set to ‘0’, the base station shall
8 set this field to the CDMA Channel number, in the specified
11 Channel for the private neighbor base station; otherwise, the
13 UZID_INCL - User Zone identifier included indicator.
14 If the UZID information is included, the base station shall set
16 to ‘0’.
17 NUM_UZID - Number of User Zone identifiers.
18 If UZID_INCL is set to ‘1’, the base station shall set this field
19 to the number of occurrences of UZID supported by the
20 private neighbor base station; otherwise, the base station
22 If UZID_INCL is set to ‘1’, the base station shall include NUM_UZID occurrences of the
23 following three-field subrecord; otherwise, the base station shall omit this subrecord.
24 UZID - User Zone identifiers.
26 supported by the private neighbor base station.
27 UZ_REV - User Zone update revision number.
28 The base station shall set this field to the User Zone update
29 revision number.
30 TEMP_SUB - Temporary subscription flag.
31 If the corresponding User Zone allows for temporary
32 subscription, the base station shall set this field to ‘1’;
34
3-202
C.S0005-0-2 v1.0
1 3.7.2.3.2.25 Reserved
2
3-203
C.S0005-0-2 v1.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

7 MIN_P_REV - Minimum protocol revision level.
8 The base station sets this field to prevent mobile stations
9 which cannot be supported by the base station from accessing
10 the system.
12 revision level that it supports. For Band Class 0 operation,
13 the base station should set this field to a value of ‘00000010’
14 or greater. For Band Class 1 or Band Class 4 operation, the
15 base station should set this field to a value of ‘00000001’ or
16 greater. For Band Class 3 operation, the base station should
17 set this field to a value of ‘00000011’ or greater. For Band
18 Class 2 or Band Class 5 operation, the base station should set
19 this field to a value of ‘00000101’ or greater. For Band Class
20 6 or, Band Class 7 , Band Class 8, or Band Class 9 operation,
21 the base station should set this field to ‘00000110’.
24 number for this system (see 2.6.5.2).
3-204
C.S0005-0-2 v1.0

9 LC_STATE - Long code state.
10 The base station shall set this field to the long code state at
11 the time given by the SYS_TIME field of this message.
12 SYS_TIME - System time.
13 The base station shall set this field to the System Time as of
14 four Sync Channel superframes (320 ms) after the end of the
15 last superframe containing any part of this Sync Channel
16 Message, minus the pilot PN sequence offset, in units of 80
17 ms (see 1.3 of TIA/EIA/IS-2000-[2)[2]).
18 LP_SEC - The number of leap seconds that have occurred since the start
19 of System Time.
20 The base station shall set this field to the number of leap
21 seconds that have occurred since the start of System Time, as
22 of the time given by the SYS_TIME field of this message.
23 LTM_OFF - Offset of local time from System Time.
24 The base station shall set this field to the two’s complement
25 offset of local time from System Time, in units of 30 minutes.
26 The local time of day, in units of 80 ms, as of four Sync
27 Channel superframes (320 ms) after the end of the last
28 superframe containing any part of this Sync Channel Message,
29 minus the pilot PN sequence offset, is equal to SYS_TIME -
30 (LP_SEC × 12.5) + (LTM_OFF × 22500).
31 DAYLT - Daylight savings time indicator.
32 If daylight savings time is in effect, the base station shall set
34 to ‘0’.
35 PRAT - Paging Channel data rate.
36 The base station shall set this field to the PRAT field value
37 shown in Table 3.7.2.3.2.26-1 corresponding to the data rate
38 used by the Paging Channels in the system.
3-205
C.S0005-0-2 v1.0
1 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

4 The base station shall set this field to the CDMA Channel
5 number corresponding to the CDMA frequency assignment for
6 the CDMA Channel containing a Primary Paging Channel.4
7 EXT_CDMA_FREQ - Extended frequency assignment.
8 The base station shall set this field to the CDMA Channel
9 number corresponding to the CDMA frequency assignment for
10 the CDMA Channel containing a Primary Paging Channel that
11 a mobile station capable of Radio Configurations greater than
12 2 or capable of supporting Quick Paging Channel will use.
13
4 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-206
C.S0005-0-2 v1.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-207
C.S0005-0-2 v1.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 are excluded from
23 this Global Service Redirection, the base station shall set this
24 field to ‘1’. Otherwise, if the mobile stations with MOB_P_REV
25 in the protocol revision range specified in DIRECT_P_MIN and
26 DIRECT_P_MAX are subjected to the redirection, the base
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-208
C.S0005-0-2 v1.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-209
C.S0005-0-2 v1.0
1 The base station shall set this field to the maximum delay
2 time, in units of 8 second increments, to be used by mobile
3 stations in the event of a global redirection to analog mode.
4 This operation can be invoked to avoid overloading an
5 underlying 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’
33
3-210
C.S0005-0-2 v1.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

10 (see 3.6.2.2).
11 NUM_FREQ - Number of CDMA Frequencies
13 supported CDMA frequencies included in this message.
14 CDMA_FREQ - CDMA Channel frequency assignment.
16 each CDMA Channel, containing a Paging Channel.
17 The base station shall set each occurrence of this field to the
18 CDMA channel number corresponding to the CDMA frequency
19 assignment for that CDMA Channel (see TIA/EIA/IS-2000-
20 [2)[2]).
21 RC_QPCH_SEL_INCL - RC and QPCH Selection included indicator
22 The base station shall set this field to ‘1’, if NUM_FREQ
23 occurrences of RC_QPCH_HASH_IND are included; otherwise,
24 it shall set this field to ‘0’.
25 If the base station sets RC_QPCH_SEL_INCL to ‘1’, the base station shall set the
26 RC_QPCH_HASH_IND field to ‘1’ in at least one of the following one-field records:
27 RC_QPCH_HASH_IND- RC_QPCH channel hashing indicator.
3-211
C.S0005-0-2 v1.0
1 If RC_QPCH_SEL_INCL is set to ‘1’, the base station shall

2 include this field and set this field as follow; otherwise, the
4 If the associated CDMA_FREQ is to be selected for CDMA
5 channel hashing by mobile stations capable of RC greater
6 than two or capable of supporting Quick Paging Channel, the
7 base station shall set the field to ‘1’; otherwise, the base
8 station shall set this field to ‘0 ’.
9
10 3.7.2.3.2.29 User Zone Reject Message
11 MSG_TAG: UZRM
Field Length (bits)
REJECT_UZID 16
REJECT_ACTION_INDI 3
UZID_ASSIGN_INCL 1
ASSIGN_UZID 0 or 16
12 REJECT_UZID - Rejected User Zone identifier.
14 of the User Zone rejected by the base station.
15 REJECT_ACTION_INDI - Rejection action indicator.
17 Table 3.7.2.3.2.29-1 corresponding to the User Zone rejection
18 action field to identify the mobile station action.
3-212
C.S0005-0-2 v1.0
1 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
3 UZID_ASSIGN_INCL - User Zone identifier assignment included indicator.
4 If assigned UZID information is included, the base station

7 ASSIGN_UZID - Assigned User Zone identifiers.
9 of the User Zone assigned to the mobile station.
10
11
3-213
C.S0005-0-2 v1.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
6
3-214
C.S0005-0-2 v1.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-215
C.S0005-0-2 v1.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
4 The following sections specify the contents of the message body for each message that may
5 be sent on the f-dsch.
6
3-216
C.S0005-0-2 v1.0
2 MSG_TAG: ORDRM
Field Length (bits)
USE_TIME 1
ACTION_TIME 6
ORDER 6
ADD_RECORD_LEN 3
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.
25
3-217
C.S0005-0-2 v1.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.

7
3-218
C.S0005-0-2 v1.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.
15
3-219
C.S0005-0-2 v1.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 TSB58-A. If the base station sets
11 this field equal to ‘111110’, it shall set the first two CHARi
12 fields of 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.
25 The base station shall include NUM_FIELDS occurrences of
26 this field. The base station shall set these fields to the
3-220
C.S0005-0-2 v1.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
22 TSB58-A.
23
Field Length (bits)
Remaining CHARi fields 8 x (NUM_FIELDS – 2)
24
3-221
C.S0005-0-2 v1.0
1 3.7.3.3.2.5 Reserved
2 No text.
3
3-222
C.S0005-0-2 v1.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

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 TIA/EIA/IS-2000-[6)[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 TIA/EIA-553-A[15] corresponding to the nominal
24 power for this mobile station.
25 ANALOG_CHAN - Analog voice channel number.
3-223
C.S0005-0-2 v1.0
1 The base station shall set this field to the channel number of
2 the analog voice channel, as specified in Table 2.1.1-1 of
3 TIA/EIA-553-A[15].
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 TIA/EIA-553-A and 2.4.1 of TIA/EIA-553-
9 A[15].
10 If the assignment is to a narrow analog channel, the base station
11 shall set this field to the two least significant bits of the DSCC.
13 To enable analog control message encryption on the assigned
14 forward and reverse analog voice channels, the base station
15 shall set this bit to ‘1’. To disable analog control message
16 encryption, the base station shall set this bit to ‘0’.
22
23 Table 3.7.3.3.2.6-1. Analog Channel Type
Analog
Description Ch AN_CHAN_TYPE
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
24
32 in TSB58-A.
33
3-224
C.S0005-0-2 v1.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

7 number for this cellular system (see 2.6.5.2).
3-225
C.S0005-0-2 v1.0
2 The base station shall set this field to the window size
3 parameter shown in Table 2.6.6.2.1-1 corresponding to the
4 number of PN chips that the mobile station is to search for
5 pilots in the Active Set and Candidate Set.
10 pilots in the Neighbor Set.
15 pilots in the Remaining Set.
21 process (see 2.6.6.2.5.2).
24 -2 × 10 × log10 Ec/Io .
26 This value is used by the mobile station to start a handoff
27 drop timer for pilots in the Active Set and the Candidate Set
28 (see 2.6.6.2.3).
29 The base station shall set this field to the pilot drop threshold,
30 expressed as an unsigned binary number equal to
31 -2 × 10 × log10 Ec/Io .

33 The mobile station transmits a Pilot Strength Measurement
36 2.6.6.2.5.2).
37 The base station shall set this field to the threshold Candidate
38 Set pilot to Active Set pilot ratio, in units of 0.5 dB.
3-226
C.S0005-0-2 v1.0
1 Timer value after which an action is taken by the mobile

2 station for a pilot that is a member of the Active Set or
3 Candidate Set, and whose strength has not become greater
4 than T_DROP. If the pilot is a member of the Active Set, a
5 Pilot Strength Measurement Message is issued. If the pilot is a
6 member of the Candidate Set, it will be moved to the Neighbor
7 Set.
8 The base station shall set this field to the T_TDROP value
9 shown in Table 2.6.6.2.3-1 corresponding to the drop timer
10 value to be used by the mobile station.
11 NGHBR_MAX_AGE - Maximum age for retention of Neighbor Set members.
12 The mobile station drops neighbor set members whose AGE
13 count exceeds this field.
14 The base station shall set this field to the Neighbor Set
15 maximum age retention value (see 2.6.6.2.6.3).
17 The base station shall set this field to the base station
18 protocol revision level.
21 2.6.6.2.3 and 2.6.6.2.5.2).
23 number.
34 base station shall set this field to its non-zero packet data
35 services zone identifier.
38 EXTENSION - Indicator that extension fields are present.
39 If Reverse Supplemental Code Channel or Reverse Supple-
40 mental Channel system parameters are included in this
41 message, the base station shall set this field to ‘1’; otherwise,
43 T_MULCHAN - Supplemental Channel Request Message pilot strength
44 reporting offset.
3-227
C.S0005-0-2 v1.0
1 If EXTENSION is set to ‘1’, the base station shall include this

2 field and set this field to the threshold offset that the mobile
3 station is to use when reporting neighbor pilot strength
4 measurements in a Supplemental Channel Request Message.
5 The mobile station is to interpret this field as an offset to
6 T_ADD ranging from 0.5 dB (corresponding to T_MULCHAN =
7 ‘000’) to 4.0 dB (corresponding to T_MULCHAN = ‘111’) in 0.5
8 dB increments.
9 BEGIN_PREAMBLE - Number of preamble frames on Reverse Supplemental Code
10 Channels at the beginning of transmission on Reverse
11 Supplemental Code Channel.
13 field and set this field to the number of Reverse Supplemental
14 Code Channel preamble frames that the mobile station is to
15 send when beginning transmission on Reverse Supplemental
16 Code Channels.
17 RESUME_PREAMBLE - Number of preamble frames on Reverse Supplemental Code
18 Channels at the resumption of transmission.
20 field and set this field to the number of Reverse Supplemental
21 Code Channel preamble frames that the mobile station is to
22 send when resuming transmission on a Reverse Supplemental
23 Code Channel following an autonomous suspension of
24 transmission on an allocated Supplemental Code Channel.
25 T_SLOTTED_INCL - Slotted timer value included indicator.
26 The base station shall set this field to ‘1’ if the slotted timer
27 value is included; otherwise, the base station shall set this
29 T_SLOTTED - Slotted timer value
30 If T_SLOTTED_INCL is set to ‘1’, the base station shall include

31 this field and set this field to the value of the TMS_Slotted
32 timer to be used by the mobile station in units of 80 ms.
33
3-228
C.S0005-0-2 v1.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.
21
3-229
C.S0005-0-2 v1.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
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.
14 The base station shall set this field to the
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.
24
3-230
C.S0005-0-2 v1.0
1 3.7.3.3.2.10 Power Control Parameters Message
2 MSG_TAG: PCPM
Field Length (bits)
PWR_REP_THRESH 5
PWR_REP_FRAMES 4
PWR_THRESH_ENABLE 1
PWR_PERIOD_ENABLE 1
PWR_REP_DELAY 5
5 PWR_REP_THRESH - Power control reporting threshold.

6 The base station shall set this field to the number of bad
7 frames (see TIA/EIA/IS-2000-[2)[2]) to be received in a
8 measurement period on the channel which carries the Power
9 Control Subchannel before the mobile station is to generate a
10 Power Measurement Report Message (see 2.6.4.1.1). If the
11 base station sets PWR_THRESH_ENABLE to ‘1’, it shall not set
13 PWR_REP_FRAMES - Power control reporting frame count.
14 The base station shall set this field to the value such that the
15 number given by
16 2(PWR_REP_FRAMES/2) × 5 frames
17 is the number of frames over which the mobile station is to
18 count frame errors.
19 PWR_THRESH- - Threshold report mode indicator.
20 _ENABLE If the mobile station is to generate threshold Power
22 field to ‘1’. If the mobile station is not to generate threshold
25 PWR_PERIOD- - Periodic report mode indicator.
26 _ENABLE If the mobile station is to generate periodic Power
28 field to ‘1’. If the mobile station is not to generate periodic
31 PWR_REP_DELAY - Power report delay.
32 The period that the mobile station waits following a Power
33 Measurement Report Message before restarting frame counting
34 for power control purposes.
3-231
C.S0005-0-2 v1.0
1 The base station shall set this field to the power report delay
2 value, in units of 4 frames (see 2.6.4.1.1).
3
3-232
C.S0005-0-2 v1.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.
12
3-233
C.S0005-0-2 v1.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.
16
3-234
C.S0005-0-2 v1.0
1 3.7.3.3.2.13 SSD Update Message
2 MSG_TAG: SSDUM
Field Length (bits)
RANDSSD 56
5 RANDSSD - Random data.

7
3-235
C.S0005-0-2 v1.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.
15
3-236
C.S0005-0-2 v1.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.
14 REG_ZONE - Registration zone.
15 The base station shall set this field to its registration zone
16 number (see 2.6.5.1.5).
17 TOTAL_ZONES - Number of registration zones to be retained.
19 registration zones the mobile station is to retain for purposes
20 of zone-based registration (see 2.6.5.1.5).
21 If zone-based registration is to be disabled, the base station
23 ZONE_TIMER - Zone timer length.
24 The base station shall set this field to the ZONE_TIMER value
25 shown in Table 3.7.2.3.2.1-1 corresponding to the length of
26 the zone registration timer to be used by mobile stations.
3-237
C.S0005-0-2 v1.0
1 MULT_SIDS - Multiple SID storage indicator.

2 If mobile stations may store entries of SID_NID_LIST
3 containing different SIDs, the base station shall set this field
4 to ‘1’; otherwise the base station shall set this field to ‘0’.
5 MULT_NIDS - Multiple NID storage indicator.
6 If mobile stations may store multiple entries of SID_NID_LIST
7 having the same SID (with different NIDs), the base station
8 shall set this field to ‘1’; otherwise the base station shall set
10 BASE_LAT - Base station latitude.
11 The base station shall set this field to its latitude in units of
13 with positive numbers signifying North latitudes. The base
14 station shall set this field to a value in the range –1296000 to
15 1296000 inclusive (corresponding to a range of –90° to +90°).
16 BASE_LONG - Base station longitude.
17 The base station shall set this field to its longitude in units of
19 with positive numbers signifying East longitude. The base
20 station shall set this field to a value in the range –2592000 to
21 2592000 inclusive (corresponding to a range of –180° to
22 +180°).
23 REG_DIST - Registration distance.
24 If mobile stations are to perform distance-based registration,
25 the base station shall set this field to the non-zero “distance”
26 beyond which the mobile station is to re-register (see
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.
29
3-238
C.S0005-0-2 v1.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
5 QUAL_INFO_TYPE - Qualification information type.

7 Table 3.7.2.3.2.15-1 to show the inclusion of qualification
8 information in the type-specific fields.
9 QUAL_INFO_LEN - Qualification information length.
11 included in the type-specific fields of the qualification
12 information.
14 The base station shall set these fields to the qualification
15 information according to the QUAL_INFO_TYPE field.
16 If QUAL_INFO_TYPE is equal to ‘00000000’, the type-specific
17 fields are omitted.
20 fields:
BAND_CLASS 5
RESERVED 3
21

24 fields:
3-239
C.S0005-0-2 v1.0
BAND_CLASS 5
OP_MODE 8
RESERVED 3

5 OP_MODE - Operating mode.
6 The base 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_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:
19 shown in Table 3.7.2.3.2.15-2 corresponding to the
20 information record requested.
21
3-240
C.S0005-0-2 v1.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

5
3-241
C.S0005-0-2 v1.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-242
C.S0005-0-2 v1.0

5 process (see 2.6.6.2.5.2).
7 include the field T_ADD and set this field to the pilot detection
9 -2 × 10 × log10 Ec/Io ; otherwise, the base station shall omit
10 this field.
14 2.6.6.2.3).
16 include the field T_DROP and set this field to the pilot drop
19 this field.
24 2.6.6.2.5.2).
26 include the field T_COMP and set this field to the threshold
27 Candidate Set pilot to Active Set pilot ratio, in units of 0.5 dB;
36 Set.
38 include the field T_TDROP and set this field to the T_TDROP
39 value shown in Table 2.6.6.2.3-1 corresponding to the drop
40 timer value to be used by the mobile station; otherwise, the
42 HARD_INCLUDED - Hard handoff parameters included.
3-243
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-[2)[2]).
13 If HARD_INCLUDED is set to ‘1’, the base station shall include
14 the field FRAME_OFFSET and set it to the Forward and
15 Reverse Traffic Channel frame offset; otherwise, the base
17 PRIVATE_LCM - Private long code mask indicator.
18 This field is used to change the long code mask after a hard
19 handoff.
21 the field PRIVATE_LCM and set it as described below;
23 If the private long code mask is to be used after the handoff,
24 the base station shall set this field to ’1’; otherwise, the base
26 RESET_L2 - Reset acknowledgment procedures command.
27 This field is used to reset acknowledgment processing in the
28 mobile station.
30 the field RESET_L2 and set it as described below; otherwise,
32 If the field is included and the mobile station is to reset its
33 acknowledgment procedures, the base station shall set this
35 RESET_FPC - Reset Forward Traffic Channel power control.
36 This field is used to reset the Forward Traffic Channel power
37 control counters.
39 the field RESET_FPC and set it as described below; otherwise,
41 The base station shall set this field to ‘0’ if the Forward Traffic
42 Channel power control counters are to be maintained after
43 completion of the handoff. If the counters are to be initialized
44 as specified in 2.6.4.1.1.1, then the base station shall set this
3-244
C.S0005-0-2 v1.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
15 in 2.3.12.2; otherwise, the base station shall omit this field.
18 this field and set it as described below; otherwise, the base
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, then the base station shall set this field to ‘0’.
24 off to a base station operating in a band class other than
25 Band Class 0 or Band Class 3, then the base station shall set
26 this 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,
35 expressed as a two’s complement value in units of 1 dB
36 (see TIA/EIA/IS-2000-[2)[2]); otherwise, the base station shall
37 omit this field.
38 NUM_PREAMBLE - Traffic Channel preamble length.
39 If HARD_INCLUDED is set to ‘0’, the base station shall omit
40 the NUM_PREAMBLE field; otherwise, the base station shall
41 include this field and set it to the length of Traffic Channel
42 preamble that the mobile station is to send when performing a
43 handoff; as follows:
3-245
C.S0005-0-2 v1.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 TSB58-A; otherwise, the base
18 the field CDMA_FREQ and set it to the CDMA Channel
19 number, in the specified CDMA band class, corresponding to
20 the CDMA frequency assignment for the CDMA Channel as
21 specified in TIA/EIA/IS-2000-[2]; otherwise, the base station
23 ADD_LENGTH - Number of octets in the additional fields.
25 included in the Additional fields. If Additional fields are not
26 included in this message, the base station shall set this field
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-246
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-[2)[2]) that the
22 mobile station is to use as the Forward Fundamental Channel
23 associated with this pilot. If Radio Configuration 1, 2, 3, or 5 (see
24 3.1.3.1.2 of TIA/EIA/IS-2000-[2)[2]) is used, the base station shall
25 set this field in the range 1 to 63 inclusive. If Radio Configuration
26 4, 6 or 8 is used, the base station shall set this field in the range
27 1 to 127 inclusive. If Radio Configuration 7 or 9 is used, the base
28 station shall set this field in the range 1 to 255 inclusive.
29
3-247
C.S0005-0-2 v1.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-248
C.S0005-0-2 v1.0
9 The base station shall set these fields as specified in 3.7.5.7
10 for the Service Configuration information record.
11
3-249
C.S0005-0-2 v1.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-250
C.S0005-0-2 v1.0
11
3-251
C.S0005-0-2 v1.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 5
One occurrence of the following three-field record:
RECORD_TYPE 8
RECORD_LEN 8
One occurrence of the following three-field record:
RECORD_TYPE 8
RECORD_LEN 8

7 in this message.
14 at which the specified service configuration is to take effect. If
15 the USE_TIME field is set to ‘0’ the base station shall set this
16 field to ‘000000’.
17 SERV_CON_SEQ - Connect sequence number.
18 The base station shall set this field to the connect sequence
19 number pertaining to this connect message as specified in
20 3.6.4.1.2.1.2.
3-252
C.S0005-0-2 v1.0
1 The base station shall include one occurrence of the following three-field record to specify
2 the service configuration.
14
15 The base station shall include one occurrence of the following three-field record to specify
16 the non-negotiable service configuration parameters.
19 shown in Table 3.7.5-1 corresponding to the Non-Negotiable
20 Service Configuration information record.
23 included in the type-specific fields of the Non-Negotiable
24 Service Configuration information record.
27 for the Non-Negotiable Service Configuration information
28 record.
29
3-253
C.S0005-0-2 v1.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.
31
3-254
C.S0005-0-2 v1.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
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.
20
3-255
C.S0005-0-2 v1.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-256
C.S0005-0-2 v1.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-257
C.S0005-0-2 v1.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 TSB58-A.
9 to 0.
14 field to 65535.
27 make the length of the entire record equal to an integer
28 number of octets. The base station shall set these bits to ‘0’.
29
3-258
C.S0005-0-2 v1.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

5
3-259
C.S0005-0-2 v1.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-260
C.S0005-0-2 v1.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-261
C.S0005-0-2 v1.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
16 included, this field indicates the allocated duration, in units of
17 80 ms, during which the mobile station may transmit on
18 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-262
C.S0005-0-2 v1.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;
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-263
C.S0005-0-2 v1.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-264
C.S0005-0-2 v1.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 included,
18 this field indicates allocated duration, in units of 80 ms,
19 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-265
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-[2)[2]) in the range 1 to 63 inclusive of
33 the Supplemental 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 TIA/EIA/IS-2000-2)[2]) in the range of 1 to (63 –
39 NUM_FOR_SUP + 1), inclusive, that the mobile station is to
40 use as the first Forward Supplemental Code Channel
41 associated with this pilot. The mobile station is to use
42 NUM_FOR_SUP successive code channels beginning with
43 index BASE_CODE_CHAN (i.e., BASE_CODE_CHAN through
44 BASE_CODE_CHAN + NUM_FOR_SUP – 1) for the Forward
45 Supplemental Code Channels associated with this pilot.
3-266
C.S0005-0-2 v1.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.
4
3-267
C.S0005-0-2 v1.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

5
3-268
C.S0005-0-2 v1.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-269
C.S0005-0-2 v1.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;
7 otherwise, the base station shall set this field as follows:
8 The base station shall set the value to the forward power
9 control operation mode as specified in Table 2.1.3.1.11-1 of
10 TIA/EIA/IS-2000-2.[2].
23 Channel.
24 If only the Fundamental Channel is assigned, the base station
25 shall set this field to ‘0’. If only the Dedicated Control
26 Channel is assigned, the base station shall set this field to ‘1’.
27 FPC_OLPC_FCH_INCL - Fundamental Channel Outer Loop Power Control parameter
31 If the forward link fundamental channel outer loop power
32 control parameters are included in this message, the base
36 If FPC_OLPC_FCH_INCL is included and set to ‘1’, the base
37 station shall set this field to the target Frame Error Rate on
38 the Forward Fundamental Channel, as specified in Table
39 3.7.3.3.2.25-2; otherwise, the base station shall omit this
40 field.
3-270
C.S0005-0-2 v1.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-271
C.S0005-0-2 v1.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’ or ‘010’,
19 the base station shall set this field to the master
20 Supplemental Channel index; otherwise, the base station shall
21 omit this field.
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-272
C.S0005-0-2 v1.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 station shall set this field to
9 FPC_SETPT_THRESH - Setpoint Report Threshold.
10 If FPC_THRESH_INCL is set to ‘1’, the base station shall set
11 the value to FPC_SETPT_THRESH (in units of 0.125 dB) above
12 which the outer loop report message will be sent by the mobile
13 station; otherwise, the base station shall omit this field.
14 FPC_THRESH_SCH_INCL - SCH Setpoint Report Threshold included indicator.
17 If FPC_SETPT_THRESH_SCH is included in this message, the
20 FPC_SETPT-
21 _THRESH_SCH - SCH Setpoint Report Threshold.
22 If FPC_THRESH_SCH_INCL is set to ‘1’, the base station shall
23 set the value to FPC_SETPT_THRESH_SCH (in units of 0.125
24 dB) above which the outer loop report message will be sent by
25 the mobile station; otherwise, the base station shall omit this
26 field.
27 RPC_INCL - Reverse Link Power Control parameter included indicator.
28 If the reverse power control related information is included in
31 RPC_NUM_REC - Number of records for Reverse Link Power Control.
32 If RPC_INCL is set to ‘0’, the base station shall omit this field;
33 otherwise, the base station shall set this field to the number of
34 records included in this message.
35 If RPC_NUM_REC is included in this message, the base station shall include
36 RPC_NUM_REC occurrences of the following record:
37 RPC_ADJ_REC_TYPE - Reverse Link Power Control adjustment record type.
39 Table 3.7.2.3.2.25-3 corresponding to the type of adjustment
40 that is to be used.
3-273
C.S0005-0-2 v1.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_TYP RPC_ADJ_REC_LE

E N
(binary)
Reverse Channel 0000 2-5
Adjustment Gain
Reverse Link Attribute 0001 2-10
Adjustment Gain for
Basic Rates
Reverse Link Attribute 0010 2-13
Adjustment 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.
13 If RPC_ADJ_REC_TYPE is equal to ‘0000’, the base station shall set type-specific fields as
3-274
C.S0005-0-2 v1.0
1 Table 3.7.2.3.2.25-4. Type Specific Fields for

2 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)
5 FCH_INCL - FCH channel adjustment gain included indicator.

6 If FCH_CHAN_ADJ_GAIN is included in this message, the base
9 FCH_CHAN_ADJ_GAIN - Channel adjustment gain for Reverse Fundamental Channel.
10 If FCH_INCL is set to ‘0’, the base station shall omit this field;
11 otherwise, the base station shall set each field to the value of
12 the gain adjustment that the mobile station is to make for the
13 Reverse Fundamental Channel. The base station shall set
14 this field to the correction factor expressed as a two’s
15 complement value in units of 0.125 dB. The base station
16 shall set the value in the range from –48 to 48.
17 DCCH_INCL - DCCH channel adjustment gain included indicator.
18 If DCCH_CHAN_ADJ_GAIN is included in this message, the
21 DCCH_CHAN_ADJ_GAIN - Channel adjustment gain for the Reverse Dedicated Control
22 Channel.
23 If DCCH_INCL is set to ‘0’, the base station shall omit this
24 field; otherwise, the base station shall set each field to the
25 value of the gain adjustment that the mobile station is to
26 make for the Reverse Dedicated Control Channel. The base
27 station shall set this field to the correction factor expressed as
28 a two’s complement value in units of 0.125 dB. The base
29 station shall set the value in the range from –48 to 48.
30 SCH0_INCL - SCH0 channel adjustment gain included indicator.
3-275
C.S0005-0-2 v1.0
1 If SCH0_CHAN_ADJ_GAIN is included in this message, the

4 SCH0_CHAN_ADJ_GAIN - Channel adjustment gain for Reverse Supplemental Channel
5 0.
6 If SCH0_INCL is set to ‘0’, the base station shall omit this
9 make for the Reverse Supplemental Channel 0. The base
10 station shall set this field to the correction factor expressed as
11 a two’s complement value in units of 0.125 dB. The base
13 SCH1_INCL - SCH1 channel adjustment gain included indicator.
14 If SCH1_CHAN_ADJ_GAIN is included in this message, the
17 SCH1_CHAN_ADJ_GAIN - Channel adjustment gain for Reverse Supplemental Channel
18 1.
19 If SCH1_INCL is set to ‘0’, the base station shall omit this
22 make for the Supplemental Channel 1. The base station shall
23 set this field to the correction factor expressed as a two’s
24 complement value in units of 0.125 dB. The base station
25 shall set the value in the range from –48 to 48.
3-276
C.S0005-0-2 v1.0

Length (Bits)
Fields
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
NORM_ATT_GAIN_9600_5MS 0 or 8
5 RL_ATT_ADJ-
6 _GAIN_TYPE - Reverse Link Attribute Adjustment Gain value type indicator.
7 If the following corresponding gain adjustment fields are set to
8 the value of the nominal attribute gain adjustment that the
9 mobile station is to make for the corresponding transmission
10 attributes (relative to Nominal_Attribute_Gain specified in
11 Table 2.1.2.3.3-1 of TIA/EIA/IS-2000-2)[2]), the base station
12 shall set this field to ‘0’. If the following corresponding gain
13 adjustment fields are set to the value of the pilot reference
14 level adjustment that the mobile station is to use for the
15 corresponding transmission attributes (relative to
16 Pilot_Reference_Level specified in Table 2.1.2.3.3-1 of
17 TIA/EIA/IS-2000-2)[2]), the base station shall set this field to
18 ‘1’.
19 RC3_RC5_20MS_INCL - Reverse Link Attribute Adjustment Gain for Radio
20 Configuration 3 or 5 of 20ms frame included indicator.
3-277
C.S0005-0-2 v1.0
1 If Reverse Link Attribute adjustment Gain for Radio

2 Configuration 3 or 5 of 20ms frame is included in this
5 RL_ATT_ADJ_GAIN_1500 - Reverse Link Attribute Adjustment Gain for the transmission
6 rate 1500bits/s.
7 If RC3_RC5_20MS_INCL is set to ‘0’, the base station shall
8 omit this field.
9 If RC3_RC5_20MS_INCL is set to ‘1’ and
10 RL_ATT_ADJ_GAIN_TYPE is set to ‘0’, the base station shall
11 set this field to the value of the nominal attribute gain
12 adjustment that the mobile station is to make for the
13 transmission attributes with transmission rate 1500bits/s,
14 convolutional code and 20ms frame. The base station shall
15 set the value in the range from –48 to 48.
18 set this field to the value of the pilot reference level
22 set the value in the range from 0 to 63.
23 The base station shall set this field to the correction factor
24 expressed as a two’s complement value in units of 0.125 dB.
26 rate 2700bits/s.
28 omit this field.
36 If RC3_RC5__20MS_INCL is set to ‘1’ and
45 RL_ATT_ADJ_GAIN_4800 - Reverse Link Attribute Gain Adjustment for the transmission
46 rate 4800bits/s.
47 If RC3_RC5__20MS_INCL is set to ‘0’, the base station shall
48 omit this field.
3-278
C.S0005-0-2 v1.0

18 rate 9600bits/s.
20 omit this field.
38 Configuration 4 and 20ms frame included indicator.
39 If Reverse Link Attribute Adjustment Gain for Radio
40 Configuration 4 and 20ms frame is included in this message,
44 rate 1800bits/s.
46 omit this field.
3-279
C.S0005-0-2 v1.0

18 rate 3600bits/s.
20 omit this field.
38 rate 7200bits/s.
40 omit this field.
3-280
C.S0005-0-2 v1.0

2 NORM_ATT_GAIN_TYPE is set to ‘1’, the base station shall set
3 this field to the value of the pilot reference level adjustment
4 that the mobile station is to make for the transmission
5 attributes with transmission rate 7200bits/s, convolutional
6 code and 20ms frame. The base station shall set the value in
7 the range from 0 to 63.
10 RL_ATT_ADJ_GAIN_14400- Reverse Link Attribute Adjustment Gain for the transmission
11 rate 14400bits/s.
13 omit this field.
16 set this field to the value of the nominal gain adjustment that
17 the mobile station is to make for the transmission attributes
18 with transmission rate 14400bits/s, convolutional code and
19 20ms frame. The base station shall set the value in the range
20 from –48 to 48.
30 5MS_INCL - 5ms frame Reverse Link Attribute Adjustment Gain included
31 indicator.
32 If Reverse Link Attribute Adjustment Gain for 5ms frame is
33 included in this message, the base station shall set this field
35 RL_ATT_ADJ_GAIN-
36 _9600_5MS - Reverse Link Attribute Adjustment Gain for the transmission
37 rate 9600bits/s with 5ms frame.
38 If 5MS_INCL is set to ‘0’, the base station shall omit this field.
39 If 5MS_INCL is set to ‘1’ and RL_ATT_ADJ_GAIN_TYPE is set
40 to ‘0’, the base station shall set this field to the value of the
41 nominal attribute gain adjustment that the mobile station is
42 to make for the transmission attributes with transmission rate
43 9600bits/s, convolutional code and 5ms frame. The base
3-281
C.S0005-0-2 v1.0
1 If 5MS_INCL is set to ‘1’ and RL_ATT_ADJ_GAIN_TYPE is set

2 to ‘1’, the base station shall set this field to the value of the
3 pilot reference level adjustment that the mobile station is to
4 make for the transmission attributes with transmission rate
5 9600bits/s, convolutional code and 5ms frame. The base
6 station shall set the value in the range from 0 to 63.
12 number of octets. The base station shall set these bits to ’0’.

Length (Bits)
Fields
CODE_TYPE 1
RL_ATT_ADJ_GAIN_TYPE 1
RC3_RC5_20MS_INCL 1
RC4_RC6_20MS_INCL 1
17
18 CODE_TYPE - Coding type indicator.
3-282
C.S0005-0-2 v1.0
1 If the following corresponding gain adjustment fields apply for

2 the convolutonal code, the base station shall set this field to
3 ‘0’. If the following corresponding gain adjustment fields apply
4 for the Turbo code, the base station shall set this field to ‘1’.
5 RL_ATT_ADJ-
6 _GAIN_TYPE - Reverse Link Attribute adjustment Gain value type indicator.
7 If the following corresponding gain adjustment fields are set to
8 the value of the nominal attribute gain adjustment that the
9 mobile station is to make for the corresponding transmission
10 attributes (relative to Nominal_Attribute_Gain specified in
11 Table 2.1.2.3.3-1 of TIA/EIA/IS-2000-2)[2]), the base station
12 shall set this field to ‘0’. If the following corresponding gain
13 adjustment fields are set to the value of the pilot reference
14 level adjustment that the mobile station is to use for the
15 corresponding transmission attributes (relative to
16 Pilot_Reference_Level specified in Table 2.1.2.3.3-1 of
17 TIA/EIA/IS-2000-2)[2]), the base station shall set this field to
18 ‘1’.
20 Conguration 3 and 5 of 20ms frame included indicator.
22 Configuration 3 and 5 of 20ms frame is included in this
25 RL_ATT_ADJ_GAIN-
26 _19200 - Reverse Link Attribute Adjustment Gain for the transmission
29 omit this field.
35 and 20ms frame. The base station shall set the value in the
36 range from –48 to 48.
41 transmission attributes with transmission rate 19200bits/s
43 range from 0 to 63.
46 RL_ATT_ADJ_GAIN-
3-283
C.S0005-0-2 v1.0

2 rate 38400bits/s.
4 omit this field.
16 attributes with transmission rate 38400bits/s and 20ms
17 frame. The base station shall set the value in the range from
18 0 to 63.
21 RL_ATT_ADJ_GAIN-
25 omit this field.
42 RL_ATT_ADJ_GAIN-
46 omit this field.
3-284
C.S0005-0-2 v1.0

3 this field to the value of the nominal attribute gain adjustment
5 attributes with transmission rate 153600bits/s, and 20ms
7 –48 to 48.
14 0 to 63.
17 RL_ATT_ADJ_GAIN-
21 omit this field.
38 RL_ATT_ADJ_GAIN-
42 omit this field.
3-285
C.S0005-0-2 v1.0

18 Configuration 4 and 6 of 20ms frame included indicator.
20 Configuration 4 and 6 of 20ms frame is included in this
23 RL_ATT_ADJ_GAIN-
27 omit this field.
41 0 to 63.
44 RL_ATT_ADJ_GAIN-
3-286
C.S0005-0-2 v1.0

2 omit this field.
5 this field to the value of the nominal attribute gain adjustment
7 attributes with transmission rate 57600bits/s, and 20ms
9 –48 to 48.
16 0 to 63.
19 RL_ATT_ADJ_GAIN-
23 omit this field.
40 RL_ATT_ADJ_GAIN-
44 omit this field.
3-287
C.S0005-0-2 v1.0

17 RL_ATT_ADJ_GAIN-
21 omit this field.
38 RL_ATT_ADJ_GAIN-
42 omit this field.
3-288
C.S0005-0-2 v1.0

5 transmission attributes with transmission rate
6 1036800bits/s, and 20ms frame. The base station shall set
7 the value in the range from –48 to 48.
21
3-289
C.S0005-0-2 v1.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
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 field:
NGHBR_PN 9
TIMING_INCL 0 or 1
NGHBR_TX_OFFSET 0 or 7
NGHBR_TX_DURATION 0 or 4
NGHBR_TX_PERIOD 0 or 7
SRCH_OFFSET_INCL 1

RECORD_LEN 0 or 3

3-290
C.S0005-0-2 v1.0
8 15 inclusive.
9 NGHBR_SRCH_MODE - Search mode.
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
00 No search priorities or search windows

01 Search priorities
10 Search windows
11 Search windows and search priorities
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’).
23 USE_TIMING - Use timing indicator.
24 If base station timing information is included for neighbor
25 base stations, the base station shall set this field to ‘1’;
27 GLOBAL_TIMING-
28 _INCL - Global timing included.
30 field GLOBAL_TIMING_INCL and set this field as described
32 If base station timing information is included globally for all
33 neighbor base stations with TIMING_INCL equal to ‘1’, the
36 GLOBAL_TX-
3-291
C.S0005-0-2 v1.0
1 _DURATION - Global neighbor transmit time duration.

3 station shall include the field GLOBAL_TX_DURATION and
4 shall set this field as described below; otherwise, the base
6 The base station shall set this field to the duration of the base
7 station transmit window, during each period, in units of 80
8 ms. The base station should set this field to a value of 3 or
9 greater.
10 GLOBAL_TX-
11 _PERIOD - Global neighbor transmit time period.
13 station shall include the field GLOBAL_TX_PERIOD and shall
14 set this field as described below; otherwise, the base station
18 NUM_NGHBR - Number of neighbor pilot PN sequences.
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-292
C.S0005-0-2 v1.0
1 Table 3.7.3.3.2.26-2. SEARCH_PRIORITY Field
Value Search Priority

(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
10 TIMING_INCL - Timing included indicator.
12 field TIMING_INCL and set this field as described below;
14 If base station timing information is included for this neighbor
15 base station, the base station shall set this field to ‘1’;
17 NGHBR_TX_OFFSET - Neighbor transmit time offset.
18 If TIMING_INCL is included and is set to ‘1’, the base station
19 shall include the field NGHBR_TX_OFFSET and set this field
20 as described below; otherwise, the base station shall omit this
21 field.
22 The base station shall set this field to the time offset, in units
23 of 80 ms, from the beginning of the neighbor timing period to
24 the beginning of the first base station transmit window within
25 the period. The beginning of the neighbor timing period
26 occurs when t/4 mod (16384)= 0.
27 NGHBR_TX_DURATION - Neighbor transmit time duration.
30 include the field NGHBR_TX_DURATION and set this field as
32 field.
33 The base station shall set this field to duration of the base
34 station transmit window, during each period, in units of
35 80 ms. The base station should set this field to a value of 3 or
36 greater.
37 NGHBR_TX_PERIOD - Neighbor transmit time period.
3-293
C.S0005-0-2 v1.0

3 include the field NGHBR_TX_PERIOD and set this field as
5 field.
8 SRCH_OFFSET_INCL - Neighbor pilot channel search window offset included.
9 If NGHBR_SRCH_MODE = ‘10’ or ‘11’ and if the
10 SRCH_OFFSET_NGHBR field is included in the following
11 records, the base station shall set this bit to ‘1’; otherwise, the
12 base station shall set this bit to ‘0’.
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-294
C.S0005-0-2 v1.0
2 fields:
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6

8 in Table 3.7.2.3.2.21-6.
11 SRCH_OFFSET_NGHBR - Neighbor pilot channel search window offset.
12 If NGHBR_SRCH_MODE = ‘10’ or ‘11’ and
13 SRCH_OFFSET_INCL equals to ‘1’, then the base station shall
14 set this field to the value shown in Table 2.6.6.2.1-2
15 corresponding to the search window offset to be used by the
16 mobile station for this neighbor. If NGHBR_SRCH_MODE is
17 set to any other value or if SRCH_OFFSET_INCL equals to ‘0’,
19
3-295
C.S0005-0-2 v1.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.
14

22 CFSRM_SEQ - Candidate Frequency Search Request Message sequence
23 number.
3-296
C.S0005-0-2 v1.0
1 The base station shall set this field to the Candidate

2 Frequency Search Request Message sequence number, as
4 SEARCH_TYPE - Search command.
6 SEARCH_TYPE code from Table 3.7.3.3.2.27-1 to indicate the
8
9 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.
10
11 SEARCH_PERIOD - Time between successive searches on the Candidate

12 Frequency.
13 The base station shall set this field to the SEARCH_PERIOD
14 value shown in Table 2.6.6.2.8.3.2-1 corresponding to the
15 search period to be used by the mobile station, i.e., the time
16 between successive searches on the Candidate Frequency.
17 SEARCH_MODE - Search mode.
18 The base station shall set this field to the SEARCH_MODE
19 value specified in Table 3.7.3.3.2.27-2 corresponding to the
20 type of search specified by this message.
21
22 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-1111 Reserved
23
3-297
C.S0005-0-2 v1.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:
3-298
C.S0005-0-2 v1.0
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

2
3-299
C.S0005-0-2 v1.0
Field Length (bits)

RECORD_LEN 0 or 3
RESERVED_3 0 - 7 (as needed)

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-300
C.S0005-0-2 v1.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 the mobile station is to search for pilots on the CDMA
9 Candidate Frequency irrespective of the received power on the
10 Candidate Frequency, the base station shall set this field to
11 ‘00000’; otherwise, the base station shall set this field to
12  (minimum_power_diff + 30) / 2 
13 where minimum_power_diff is determined by the following
14 rule: The mobile station is not to search for pilots on the
15 CDMA Candidate Frequency if (cand_freq_pwr -
16 serving_freq_pwr) is less than minimum_power_diff (in dB),
17 where cand_freq_pwr is the received power on the CDMA
18 Candidate Frequency, in dBm / 1.23 MHz, and
19 serving_freq_pwr is the received power on the Serving
20 Frequency, in dBm / 1.23 MHz.
21 MIN_TOTAL_PILOT-
22 _EC_IO - Minimum total pilot Ec/ Io.
23 If the mobile station is to attempt to demodulate the Forward
24 Traffic Channels irrespective of the strength of pilots in the
25 Active Set, the base station shall set this field to ‘00000’;
26 otherwise, the base station shall set this field to
27  - 20 × log10 total_pilot_threshold 
28 where total_pilot_threshold is defined by the following rule: The

29 mobile station is not to attempt to demodulate the Forward
30 Traffic Channels if the sum of Ec/Io of all pilots in the mobile
31 station’s Active Set is less than total_pilot_threshold.
32 CF_T_ADD - Pilot detection threshold for the CDMA Candidate Frequency.
33 This value is used by the mobile station to trigger the sending
34 of the Candidate Frequency Search Report Message during a
35 periodic search of the CDMA Candidate Frequency (see
36 2.6.6.2.8.3.2).
39 -2 × 10 × log10 Ec/Io .
40 TF_WAIT_TIME - The total maximum wait time on the CDMA Target Frequency.
41 The base station shall set this field to the maximum wait time,
42 in units of 80 ms, that the mobile station is to spend waiting
43 for a period of (N11m × 20) ms with sufficient signal quality
44 (e.g. good frames) on the CDMA Target Frequency.
3-301
C.S0005-0-2 v1.0
1 CF_PILOT_INC - Pilot PN sequence offset index increment to be used on the

2 CDMA Candidate Frequency after handoff.
4 increment, in units of 64 PN chips, that the mobile station is
5 to use for searching the Remaining Set, after a handoff to the
6 CDMA Candidate Frequency is successfully completed. The
7 base station should set this field to the largest increment such
8 that the pilot PN sequence offsets of all its neighbor base
9 stations are integer multiples of that increment.
10 CF_SRCH_WIN_N - Default search window size for the Candidate Frequency
11 Search Set.
13 Table 2.6.6.2.1-1 corresponding to the default search window
14 size to be used by the mobile station for its Candidate
15 Frequency Neighbor Set. The mobile station uses the default
16 search window size for all pilots in its Candidate Frequency
17 Neighbor Set when the search window has not been specified
18 for each pilot individually.
19 CF_SRCH_WIN_R - Search window size for the Remaining Set on the CDMA
24 pilots in the Remaining Set on the CDMA Candidate
25 Frequency after a handoff is successfully completed.
28 PILOT_UPDATE - Pilot search parameter update indicator.
32 NUM_PILOTS - Number of pilots included in the message.
33 The base station shall set this field to the number of the
34 CDMA Candidate Frequency pilots included in this message.
35 The base station shall set this field to a value from 0 to N8m,
36 inclusive.
37 CF_NGHBR_SRCH-
38 _MODE - Search mode for Candidate Frequency Search Set.
41
3-302
C.S0005-0-2 v1.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 bases station shall omit this
28 field; otherwise, the base station shall include this field and
30 If SRCH_OFFSET_NGHBR is included in the message, the
31 base station shall set this bit to ‘1’; otherwise, the base station
33 If PILOT_UPDATE is set to ‘1’, the base station shall include NUM_PILOTS occurrences of
34 the following four-field record, one for each included CDMA Candidate Frequency Pilot.
3-303
C.S0005-0-2 v1.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)
OTD_POWER_LEVEL 2
RESERVED 6
29

33 in Table 3.7.2.3.2.21-6.
35 The base station shall set these bits to ‘0’.
3-304
C.S0005-0-2 v1.0
1 SRCH_OFFSET_NGHBR - Neighbor pilot channel search window offset.

2 If CF_NGHBR_SRCH_MODE is set to ‘10’ or ‘11’ and
3 CF_SRCH_OFFSET_INCL equals to ‘1’, then the base station
4 shall set this field to the value specified in Table 2.6.6.2.1-2
6 mobile station for this neighbor. If CF_NGHBR_SRCH_MODE
7 is set to any other value or if CF_SRCH_OFFSET_INCL equals
8 to ‘0’, the base station shall omit this field.
11 make the length of the Mode-specific fields equal to an integer
13 If SEARCH_MODE is equal to ‘0001’, the base station shall include the following fields:
14
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
15

17 The base station shall set this field to the CDMA band class
18 associated with the analog frequencies included in this
19 message.
20 SF_TOTAL_EC-
21 _THRESH - Serving Frequency total pilot Ec threshold.
22 If the mobile station is not to use the measurement of total Ec
23 of the pilots in the Serving Frequency Active Set in the Analog
24 Frequencies periodic search procedure, the base station shall
25 set this field to ‘11111’; otherwise, the base station shall set
26 this field to
27  (10 × log10 (total_ec_thresh) + 120) / 2 
3-305
C.S0005-0-2 v1.0
1 where total_ec_thresh is defined by the following rule: The

2 mobile station is not to visit any analog frequency if the total
3 Ec of the pilots in the Serving Frequency Active Set is greater
4 than total_ec_thresh.
5 SF_TOTAL_EC-
6 _IO_THRESH - Serving Frequency total pilot Ec/Io threshold.
7 If the mobile station is not to use the measurement of total
8 Ec/Io of the pilots in the Serving Frequency Active Set in the
9 Analog Frequencies periodic search procedure, the base
12  - 20 × log10 (total_ec_io_thresh) 
13 where total_ec_io_thresh is defined by the following rule: The

14 mobile station is not to visit any analog frequency if the total
15 Ec/Io of the pilots in the Serving Frequency Active Set is
16 greater than total_ec_io_thresh.
19 NUM_ANALOG_FREQS - Number of analog frequencies.
21 neighbors on the candidate frequency. The base station shall
22 set this field to a value from 1 to 7, inclusive.
23
24 The message will include NUM_ANALOG_FREQS occurrences of the following one-field

25 record, one for each neighbor on the candidate frequency.
26 ANALOG_FREQ - Analog frequency channel number.
27 The base station shall set this field to the analog frequency
28 channel number to search.
31 make the length of the Mode-specific fields equal to an integer
33 ALIGN_TIMING - Align timing indicator.
34 If the base station requests that the mobile station offset the
35 start of the first search from the action time of this message
36 (or of a subsequent Candidate Frequency Search Control
37 Message that starts a search) by a delay specified by the
38 SEARCH_OFFSET field, the base station shall set this field to
40 SEARCH_OFFSET - Search offset.
41 If the ALIGN_TIMING field is set to ‘0’, the base station shall
43 field and set it to
3-306
C.S0005-0-2 v1.0
1 min ( 63, search_offset_time / 0.00125  )

2 where search_offset_time is the time offset, in seconds, of the
4 (or of a subsequent Candidate Frequency Search Control
5 Message that starts a search).
6
3-307
C.S0005-0-2 v1.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-308
C.S0005-0-2 v1.0
3-309
C.S0005-0-2 v1.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-310
C.S0005-0-2 v1.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
34 specified in TSB58-A; otherwise, the base station shall omit
35 this 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 TIA/EIA/IS-
41 2000-[2]; otherwise, the base station shall omit this field.
42
3-311
C.S0005-0-2 v1.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

6 The base station shall set these bits to ‘000000’.
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-312
C.S0005-0-2 v1.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.
17
3-313
C.S0005-0-2 v1.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

5
3-314
C.S0005-0-2 v1.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
3-315
C.S0005-0-2 v1.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
RLGAIN_TRAFFIC_PILOT 0 or 6
DEFAULT_RLAG 0 or 1
NNSCR_INCLUDED 0 or 1
RECORD_TYPE 0 or 8
RECORD_LEN 0 or 8

5 in this message.
3-316
C.S0005-0-2 v1.0
4 set to ‘0’ the base station shall omit this field.
5 HDM_SEQ - General Handoff Direction Message sequence number.
9 The base station shall set this field to the handoff message
10 sequence number, as specified in 3.6.6.2.2.10.
20 pilots in the Active Set and the Candidate Set; otherwise, the
24 include the field SRCH_WIN_N and set this field to the window
26 the search window size to by used by mobile stations for the
27 Neighbor Set after completion of the handoff; otherwise, the
31 include the field SRCH_WIN_R and set this field to the window
34 Remaining Set after completion of the handoff; otherwise, the
41 process (see 2.6.6.2.5.2).
46 this field.
3-317
C.S0005-0-2 v1.0

4 2.6.6.2.3).
9 this field.
14 2.6.6.2.5.2).
26 Set.
33 active set, or dropping a pilot from the active set (see 2.6.6.2.3
34 and 2.6.6.2.5.2).
36 include the field SOFT_SLOPE in the additional fields and set
37 this field as an unsigned binary number; otherwise, the base
40 the active set (see 2.6.6.2.5.2).
42 include the field ADD_INTERCEPT in the additional fields and
43 set this field as a two's complement signed binary number;
46 from the active set (see 2.6.6.2.3).
3-318
C.S0005-0-2 v1.0

2 include the field DROP_INTERCEPT in the additional fields
3 and set this field as a two' complement signed binary number;
5 EXTRA_PARMS - Extra parameters included.
6 If the mobile station is to change FRAME_OFFSET,
7 PRIVATE_LCM, ENCRYPT_MODE, NOM_PWR, BAND_CLASS,
8 or CDMA_FREQ, or the mobile station is to perform a reset of
9 the acknowledgment procedures, or the mobile station is to
10 reset Forward Traffic Channel power control counters, the
14 If EXTRA_PARMS is set to ‘1’, the base station shall set this
15 field to the base station protocol revision level that the mobile
16 station is to use after completion of the handoff; otherwise,
19 If EXTRA_PARMS is set to ‘1’, the base station shall include
20 the field PACKET_ZONE_ID and set this field as described
23 base station shall set this field to the non-zero packet data
24 services zone identifier that the mobile station is to use after
25 completion of the handoff.
30 FRAME_OFFSET × 1.25 ms relative to system timing (see of
31 TIA/EIA/IS-20000.[2]).
33 the field FRAME_OFFSET and set this field to the Forward
34 and Reverse Traffic Channel frame offset; otherwise, the base
38 handoff.
40 the field PRIVATE_LCM and set this field as described below;
3-319
C.S0005-0-2 v1.0

2 mobile station.
4 the field RESET_L2 and set this field as described below;
13 the field RESET_FPC and set this field as described below;
22 the field SERV_NEG_TYPE and set this field as described
27 to ‘0’.
30 the field ENCRYPT_MODE and set this field to the
31 ENCRYPT_MODE value shown in Table 3.7.2.3.2.8-2
32 corresponding to the encryption mode that is to be used for
33 messages sent on the Forward and Reverse Traffic Channels,
34 as specified in 2.3.12.2; otherwise, the base station shall omit
35 this field.
38 this field and set this field as described below; otherwise, the
3-320
C.S0005-0-2 v1.0

5 station in the open loop power estimate is between -24 dB and
6 -9 dB inclusive; otherwise (the correction factor is in the range
7 -8 dB to 7 dB inclusive), the base station shall set this field to
8 ‘0’.
11 the field NOM_PWR and set this field to the correction factor
12 to be used by the mobile station in the open loop power
13 estimate, expressed as a two’s complement value in units of 1
14 dB (see TIA/EIA/IS-2000-2)[2]); otherwise, the base station
16 NUM_PREAMBLE - Traffic Channel preamble length.
17 If EXTRA_PARMS is set to ‘0’, the base station shall omit the
18 NUM_PREAMBLE field; otherwise, the base station shall
28 ms units.
31 the field BAND_CLASS and set this field to the CDMA band
32 class corresponding to the CDMA frequency assignment for
33 the CDMA Channel as specified in TSB58-A; otherwise, the
37 the field CDMA_FREQ and set this field to the CDMA Channel
38 number, in the specified CDMA band class, corresponding to
40 specified in TIA/EIA/IS-2000-[2]; otherwise, the base station
42 RETURN_IF_HANDOFF- - Return on failure flag.
43 _FAIL If EXTRA_PARMS is set to ‘1’, the base station shall include
44 the field RETURN_IF_HANDOFF_FAIL and set this field as
46 field.
3-321
C.S0005-0-2 v1.0
1 If the base station includes this field, it shall set this field to
2 ‘1’ if the mobile station is to resume the use of the Active Set
3 on the Serving Frequency following an unsuccessful hard
4 handoff attempt, as specified in 2.6.6.2.8.2; otherwise, the
6 COMPLETE_SEARCH - Flag to complete search.
7 If RETURN_IF_HANDOFF_FAIL is included and is set to ‘1’,
8 the base station shall include the field COMPLETE_SEARCH
9 and set this field as described below; otherwise, the base
12 ‘1’ if the mobile station is to complete the search of the
13 Candidate Frequency Search Set before resuming the use of
14 the Active Set on the Serving Frequency when an inter-
15 frequency handoff attempt is unsuccessful, as specified in
16 2.6.6.2.8.2; otherwise, the base station shall set this field to
17 ‘0’.
18 PERIODIC_SEARCH - Flag to search the Candidate Frequency periodically.
20 the field PERIODIC_SEARCH and set this field as described
23 ‘1’ if the mobile station is to periodically search the Candidate
24 Frequency, as specified in 2.6.6.2.8.3; otherwise, the base
26 SCR_INCLUDED - Service Configuration Record included indicator.
28 the field SCR_INCLUDED and shall set this field as described
30 The base station shall set this field to ‘1’ if it includes the
31 Service Configuration Record in the message; otherwise, the
34 If SCR_INCLUDED is included and is set to ‘1’, the base
35 station shall include the field SERV_CON_SEQ and shall set
36 this field to the connect sequence number pertaining to this
37 service configuration as specified in 3.6.4.1.2.1.2.
38 If SCR_INCLUDED is included and is set to ‘1’, the base station shall include one
39 occurrence of the following three-field record to specify the service configuration.
42 station shall include the field RECORD_TYPE and shall set
43 this field to the record type value shown in Table 3.7.5-1
44 corresponding to the Service Configuration information
45 record.
3-322
C.S0005-0-2 v1.0

2 station shall include the field RECORD_LEN and shall set this
3 field to the number of octets included in the type-specific
4 fields of the Service Configuration information record.
7 station shall include the type specific fields and shall set these
8 fields as specified in 3.7.5.7 for the Service Configuration
10 SUP_CHAN_PARAMS- - Supplemental channel parameters included indicator.
11 _INCLUDED The base station shall set this field to ‘1’ if the base station
12 includes the FOR_INCLUDED, REV_INCLUDED, and
13 REV_PARAMS_INCLUDED fields in the message; otherwise,
15 FOR_INCLUDED - Forward assignment information included indicator.
16 If SUP_CHAN_PARMS_INCLUDED is set to ‘1’, the base station
17 shall include the field FOR_INCLUDED and set this field as
19 field.
21 ‘1’ if Forward Supplemental Code Channel assignment
22 information is included in the message; otherwise, the base
24 FOR_SUP_CONFIG - Forward Supplemental Code Channel configuration indicator.
25 If FOR_INCLUDED is included and is set to ‘1’, the base
26 station shall include the field FOR_SUP_CONFIG and set this
27 field according to the following rules:
28 The base station shall set this field to ‘00’ if Forward
29 Supplemental Code Channels are not specified in the
30 message, and the mobile station is to stop processing all
31 Forward Supplemental Code Channels.
32 The base station shall set this field to ‘01’ if Forward
33 Supplemental Code Channels are not specified in the
34 message, and the mobile station is to start processing the
35 Forward Supplemental Code Channels previously stored in its
36 Code Channel List, CODE_CHAN_LISTs.
38 Supplemental Code Channels are specified in the message,
39 and the mobile station is to stop processing all Forward
40 Supplemental Code Channels in CODE_CHAN_LISTs, and to
41 update the CODE_CHAN_LISTs, according to the information
42 contained in the message.
3-323
C.S0005-0-2 v1.0
2 Supplemental Code Channels are specified in the message,
3 and the mobile station is to update its Code Channel List,
4 CODE_CHAN_LISTs, according to the information contained in
5 the message and to start processing the Forward
7
8 NUM_FOR_SUP - Number of Forward Supplemental Code Channels.

10 base station shall include the field NUM_FOR_SUP and set it
11 to the number of Forward Supplemental Code Channels
12 assigned to the mobile station; otherwise, the base station
13 shall omit this field. NUM_FOR_SUP shall not exceed the
14 maximum number of Forward Supplemental Code Channels
15 for the negotiated multiplex option.
16 USE_FOR_DURATION - Use forward duration indicator.
17 If FOR_SUP_CONFIG is included and is set to ‘01’ or ‘11’ the
18 base station shall include the field USE_FOR_DURATION and
19 set this field as described below; otherwise the base station
22 FOR_DURATION field is included in the message and the
23 mobile station is to process the Forward Supplemental Code
24 Channels for a time duration indicated by FOR_DURATION.
26 is to process the Forward Supplemental Code Channels for an
27 indefinite duration (i.e., the mobile station is to continue
28 processing Forward Supplemental Code Channels until it
29 receives a subsequent Supplemental Channel Assignment
30 Message or a General Handoff Direction Message that specifies
31 a different Forward Supplemental Code Channel assignment.
32 FOR_DURATION - Duration of Forward Supplemental Code Channel assignment.
33 If USE_FOR_DURATION is included and is set to ‘1’ the base
34 station shall include the field FOR_DURATION and set this
35 field to the allocated duration, in units of 80 ms, for which the
36 mobile station is to process the Forward Supplemental Code
37 Channels; otherwise, the base station shall omit this field.
38 REV_INCLUDED - Reverse assignment information included indicator.
40 shall include the field REV_INCLUDED and set this field as
42 field.
44 ‘1’ if Reverse Supplemental Code Channel assignment
45 information is included in the message; otherwise, the base
47 REV_DTX_DURATION - Reverse Discontinuous Transmission Duration.
3-324
C.S0005-0-2 v1.0
1 If REV_INCLUDED is included and is set to ‘1’, the base

2 station shall include the field REV_DTX_DURATION; otherwise
5 the maximum duration of time in units of 20 ms that the
6 mobile station is allowed to stop transmission on a Reverse
7 Supplemental Code Channel within the reverse assignment
8 duration. The base station shall set this field to ‘0000’ if the
9 mobile station is to stop using a Reverse Supplemental Code
10 Channel once it has stopped transmitting on that Reverse
11 Supplemental Code Channel. The base station shall set this
12 field to ‘1111’ if the mobile station is allowed to resume
13 transmission on a Reverse Supplemental Code Channel at any
14 time within the reverse assignment duration.
15 CLEAR_RETRY_DELAY - Clear retry delay indicator.
17 station shall include the field CLEAR_RETRY_DELAY and set
18 this field as described below; otherwise the base station shall
19 omit this field.
21 mobile station is to clear any existing retry delay which it has
22 stored (see 2.6.6.2.5.1); otherwise, the base station shall set
24 USE_REV_DURATION - Use reverse duration indicator.
26 station shall include the field USE_REV_DURATION and set
28 omit this field.
30 REV_DURATION field is included in the message and the
31 mobile station is allowed to transmit on the Reverse
32 Supplemental Code Channels for a time duration indicated by
33 REV_DURATION.
35 is allowed to transmit on the Reverse Supplemental Code
36 Channels for an indefinite duration (i.e., the mobile station
37 may continue to transmit on the Reverse Supplemental Code
38 Channels until it receives a subsequent Supplemental Channel
40 that specifies a different Reverse Supplemental Code Channel
41 assignment.
42 REV_DURATION - Duration of Reverse Supplemental Code Channel Assignment.
43 If USE_REV_DURATION is included and is set to ‘1’, the base
44 station shall include the field REV_DURATION and set this
45 field to the allocated duration, in units of 80 ms, for which the
46 mobile station may transmit on Reverse Supplemental Code
47 Channels; otherwise the base station shall omit this field.
48 NUM_REV_CODES - Number of Reverse Supplemental Code Channels.
3-325
C.S0005-0-2 v1.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
19 field as described below; otherwise, the base station shall omit
20 this field.
22 ‘1’ if the following three fields are included in the message;
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-326
C.S0005-0-2 v1.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.
21
22 The base station shall include one occurrence of the following four-part record for each of
23 the NUM_PILOTS pilots included in the message:
32 this field to ‘0’. The base station shall set this field to ‘0’ in
33 the first record in the pilot list.
34 FOR_FUND_CODE- - Forward Fundamental Channel.
35 _CHAN The base station shall set this field to the code channel index
36 to be used for the Forward Fundamental Channel associated
37 with this pilot.
38 FOR_SUP_INCLUDED - Forward Supplemental Code Channel included.
39 The base station shall include this field if FOR_SUP_CONFIG
40 is included and is set to ‘10’ or ‘11’. If included, the base
41 station shall set this field to ‘1’ if there are Supplemental Code
42 Channels associated with this pilot.
43
44 FOR_SUP_CHAN_REC - Forward Supplemental Code Channel record
3-327
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-2)[2]) in the range of 1 to (63 -
35 NUM_FOR_SUP + 1), inclusive, that the mobile station is to
36 use as the first Forward Supplemental Code Channel
37 associated with this pilot. The mobile station is to use code
38 channel index (BASE_CODE_CHAN + i - 1), where i ranges
39 from 1 to NUM_FOR_SUP, for the ith Forward Supplemental
40 Code Channel associated with this pilot.
41 FOR_SUP_CODE_CHAN - Forward Supplemental Code Channel.
3-328
C.S0005-0-2 v1.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;
4 otherwise the base station shall omit this field.
5 The base station shall set the ith occurrence of this field to the
6 code channel index (see TIA/EIA/IS-2000-2)[2]), in the range 1
7 to 63 inclusive, that the mobile station is to use for the ith
8 Forward Code 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 TIA/EIA/IS-2000-2)[2]); otherwise, the base
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-329
C.S0005-0-2 v1.0
1 If the mobile station is to use the default values for the reverse
2 link attribute gain, as specified in Table 2.1.2.3.3-1 of
3 TIA/EIA/IS-2000-[2] after completion of handoff, the base
6 NNSCR_INCLUDED - Non Negotiable Service Configuration Record included
7 indicator.
8 The base station shall omit this field, if EXTRA_PARMS is set
9 to ‘0’; otherwise, the base station shall include this field and
10 set this field as described below:
11 The base station shall set this field to ‘1’, if the Non Negotiable
12 Service Configuration record is included in this message;
14 If NNSCR_INCLUDED is included and is set to ‘1’, the base station shall include one
15 occurrence of the following three-field record to specify the non-negotiable service
16 configuration parameters.
18 If NNSCR_INCLUDED is included and is set to ‘1’, the base
21 corresponding to the Non-Negotiable Service Configuration
27 fields of the Non-Negotiable Service Configuration information
28 record.
32 fields as specified in 3.7.5.20 for the Non-Negotiable Service
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-330
C.S0005-0-2 v1.0

4 REV_PWR-
15 mobile station after handoff, in units of 1.25 ms. To disable
16 the gating on the reverse Fundamental Channel, the base
18
3-331
C.S0005-0-2 v1.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.
27
3-332
C.S0005-0-2 v1.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.
16
18 The base station shall set this field to ‘0’ if the mobile station is to perform the
19 primary inner loop estimation on the received Forward Fundamental Channel and the base
20 station is to multiplex the Power Control Subchannel on the Forward Fundamental
21 Channel. The base station shall set this field to ‘1’ if the mobile station is to perform the
22 primary inner loop estimation on the received Forward Dedicated Control Channel and the
23 base station is to multiplex the Power Control Subchannel on the Forward Dedicated
24 Control Channel.
3-333
C.S0005-0-2 v1.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-334
C.S0005-0-2 v1.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 GATING_RATE_INCL - Reverse pilot gating rate included flag.
4 PILOT_GATING_RATE field is included, otherwise it shall set
6 PILOT_GATING_RATE - Actual Reverse Pilot gating Rate.
7 If the GATING_RATE_INCL field is set to ‘1’ then the base
8 station shall set this field to the PILOT_GATING_RATE field
9 shown in Table 3.7.3.3.2.34-2 corresponding to the actual
10 gating rate on the Reverse Pilot Channel; otherwise, the base
12
13 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
14
3-335
C.S0005-0-2 v1.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
29
3-336
C.S0005-0-2 v1.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

5
3-337
C.S0005-0-2 v1.0
Field Length (bits)
ENCRYPT_MODE 0 or 2
NOM_PWR_EXT 0 or 1
NOM_PWR 0 or 4
RLGAIN_TRAFFIC_PILOT 0 or 6
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
3-338
C.S0005-0-2 v1.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_RATE 4
FPC_SUBCHAN_GAIN 5
USE_PC_TIME 1
PC_ACTION_TIME 0 or 6
3-339
C.S0005-0-2 v1.0
CH_IND 3
ACTIVE_SET_REC_LEN 8
ACTIVE_SET_REC_FIELDS 8x
ACTIVE_SET_REC_LEN
2 If CH_IND = ‘101’, the ACTIVE_SET_REC_FIELDS shall be:

3
NUM_FOR_SCH 0 or 5
NUM_FOR_SCH occurrences of the following three fields:
FOR_SCH_ID 1
SCCL_INDEX 4
FOR_SCH_RATE 4
NUM_REV_SCH 0 or 5
NUM_REV_SCH occurrences of the following three fields:
REV_SCH_ID 1
REV_WALSH_ID 1
REV_SCH_RATE 4
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
3-340
C.S0005-0-2 v1.0
NUM_SCH 0 or 5
NUM_SCH occurrences of the following record
FOR_SCH_ID 1
SCCL_INDEX 4
PILOT_INCL 1
CODE_CHAN_SCH 0 or 11
QOF_MASK_ID_SCH 0 or 2
3 If CH_IND = ‘010’ or ‘110’, the ACTIVE_SET_REC_FIELDS shall be:

4
NUM_FOR_SCH 0 or 5
FOR_SCH_ID 1
SCCL_INDEX 4
FOR_SCH_RATE 4
NUM_REV_SCH 0 or 5
REV_SCH_ID 1
REV_WALSH_ID 1
REV_SCH_RATE 4
NUM_PILOTS 3
SRCH_OFFSET_INCL 1
PILOT_PN 9
SRCH_OFFSET 0 or 3
RECORD_LEN 0 or 3
3-341
C.S0005-0-2 v1.0
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 If CH_IND = ‘111’, the ACTIVE_SET_REC_FIELDS shall be:

4
NUM_FOR_SCH 0 or 5
FOR_SCH_ID 1
SCCL_INDEX 4
FOR_SCH_RATE 4
NUM_REV_SCH 0 or 5
REV_SCH_ID 1
REV_WALSH_ID 1
REV_SCH_RATE 4
NUM_PILOTS 3
SRCH_OFFSET_INCL 1
PILOT_PN 9
SRCH_OFFSET 0 or 3
3-342
C.S0005-0-2 v1.0
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 record
FOR_SCH_ID 1
SCCL_INDEX 4
PILOT_INCL 1

5 in this message.
13 set to ‘0’ the base station shall omit this field.
14 HDM_SEQ - Universal Handoff Direction Message sequence number.
18 The base station shall set this field to the handoff message
19 sequence number, as specified in 2.6.6.2.2.10.
20 PARMS_INCL - Parameters included indicator.
21 The base station shall set this field to ‘1’, if P_REV and
22 SERV_NEG_TYPE are included; otherwise, the base station
23 shall set this field ‘0’.
3-343
C.S0005-0-2 v1.0

2 If PARMS_INCL is set to ‘1’, the base station shall set this field
3 to the base station protocol revision level that the mobile
4 station is to use after completion of the handoff; otherwise,
7 If PARMS_INCL is set to ‘1’, the base station shall include the
8 field SERV_NEG_TYPE and set this field as described below;
13 to ‘0’.
23 pilots in the Active Set and the Candidate Set; otherwise, the
27 include the field SRCH_WIN_N and set this field to the window
30 Neighbor Set after completion of the handoff; otherwise, the
34 include the field SRCH_WIN_R and set this field to the window
37 Remaining Set after completion of the handoff; otherwise, the
44 process (see 2.6.6.2.5.2).
3-344
C.S0005-0-2 v1.0

5 this field.
9 2.6.6.2.3).
14 this field.
19 2.6.6.2.5.2).
31 Set.
39 2.6.6.2.3 and 2.6.6.2.5.2).
41 include the field SOFT_SLOPE in the additional fields and set
42 this field as an unsigned binary number; otherwise, the base
3-345
C.S0005-0-2 v1.0

2 include the field ADD_INTERCEPT in the additional fields and
3 set this field as a two's complement signed binary number;
8 include the field DROP_INTERCEPT in the additional fields
9 and set this field as a two's complement signed binary
10 number; otherwise, the base station shall omit this field.
11 EXTRA_PARMS - Extra parameters included.
12 If the base station includes the fields PACKET_ZONE_ID,
13 FRAME_OFFSET, PRIVATE_LCM, RESET_L2, RESET_FPC,
14 SERV_NEG_TYPE, ENCRYPT_MODE, NOM_PWR_EXT,
15 NOM_PWR, RLGAIN_TRAFFIC_PILOT, DEFAULT_RLAG,
16 NUM_PREAMBLE, BAND_CLASS, PERIODIC_SEARCH, or
17 CDMA_FREQ in this message, the base station shall set this
21 the field PACKET_ZONE_ID and set this field as described
24 base station shall set this field to the non-zero packet data
25 services zone identifier that the mobile station is to use after
26 completion of the handoff.
32 TIA/EIA/IS-2000-2)[2]).
34 the field FRAME_OFFSET and set this field to the Forward
35 and Reverse Traffic Channel frame offset; otherwise, the base
39 handoff.
41 the field PRIVATE_LCM and set this field as described below;
3-346
C.S0005-0-2 v1.0

3 mobile station.
5 the field RESET_L2 and set this field as described below;
14 the field RESET_FPC and set this field as described below;
23 the field ENCRYPT_MODE and set this field to the
24 ENCRYPT_MODE value shown in Table 3.7.2.3.2.8-2
25 corresponding to the encryption mode that is to be used for
26 messages sent on the Forward and Reverse Traffic Channels,
27 as specified in 2.3.12.2; otherwise, the base station shall omit
28 this field.
31 this field and set this field as described below; otherwise, the
40 station in the open loop power estimate is between -24 dB and
41 -9 dB inclusive; otherwise (the correction factor is in the range
42 -8 dB to 7 dB inclusive), the base station shall set this field to
43 ‘0’.
3-347
C.S0005-0-2 v1.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 TIA/EIA/IS-2000-2)[2]); otherwise, the base station
7 RLGAIN_TRAFFIC_PILOT - Gain adjustment of the Reverse Traffic Channel relative to the
8 Reverse Pilot Channel power for Radio configurations greater
9 than 2.
11 this field and set it to the correction factor to be used by
12 mobile stations in setting the power of a reverse traffic
13 channel, expressed as a two’s complement value in units of
14 0.125 dB (see 2.1.2.3.3 of TIA/EIA/IS-2000-[2]; otherwise, the
16 DEFAULT_RLAG - Default reverse link attribute gain used indicator.
17 If EXTRA_PARAMS is set to ‘0’, the base station shall omit this
18 field; otherwise, the base station set this field as follows:
19 If the mobile station is to use the default values for the reverse
20 link attribute gain, as specified in Table 2.1.2.3.3-1 of
21 TIA/EIA/IS-2000-[2] after completion of handoff, the base
24 NUM_PREAMBLE - Number of Traffic Channel preamble.
25 If EXTRA_PARMS is set to ‘0’, the base station shall omit the
26 NUM_PREAMBLE field; otherwise, the base station shall
36 ms units.
39 the field BAND_CLASS and set this field to the CDMA band
40 class corresponding to the CDMA frequency assignment for
41 the CDMA Channel as specified in TSB58-A; otherwise, the
44 If EXTRA_PARMS is set to ‘0’, the base station shall omit this
45 field; otherwise, the base station shall set this field as follows:
3-348
C.S0005-0-2 v1.0
1 If a Radio Configuration associated with Spreading Rate 1 is

2 used, the base station shall set this field to the CDMA
3 Channel number, in the specified CDMA band class,
5 CDMA Channel as specified in TIA/EIA/IS-2000-2.[2].
6 RETURN_IF-
7 _HANDOFF_FAIL - Return on failure flag.
9 the field RETURN_IF_HANDOFF_FAIL and set this field as
11 field.
13 ‘1’ if the mobile station is to resume the use of the Active Set
14 on the Serving Frequency following an unsuccessful hard
15 handoff attempt, as specified in 2.6.6.2.8.2; otherwise, the
17 COMPLETE_SEARCH - Flag to complete search.
18 If RETURN_IF_HANDOFF_FAIL is included and is set to ‘1’,
19 the base station shall include the field COMPLETE_SEARCH
20 and set this field as described below; otherwise, the base
23 ‘1’ if the mobile station is to complete the search of the
24 Candidate Frequency Search Set before resuming the use of
25 the Active Set on the Serving Frequency when an inter-
26 frequency handoff attempt is unsuccessful, as specified in
27 2.6.6.2.8.2; otherwise, the base station shall set this field to
28 ‘0’.
29 PERIODIC_SEARCH - Flag to search the Candidate Frequency periodically.
31 the field PERIODIC_SEARCH and set this field as described
34 ‘1’ if the mobile station is to periodically search the Candidate
35 Frequency, as specified in 2.6.6.2.8.3; otherwise, the base
37 SCR_INCLUDED - Service Configuration Record included.
39 the field SCR_INCLUDED and shall set this field as described
41 The base station shall set this field to ‘1’ if it includes the
42 Service Configuration Record in the message; otherwise, the
3-349
C.S0005-0-2 v1.0

2 station shall include the field SERV_CON_SEQ and shall set
3 this field to the connect sequence number pertaining to this
4 service configuration as specified in 3.6.4.1.2.1.2.
5 If SCR_INCLUDED is included and is set to ‘1’, the base station shall include one
6 occurrence of the following three-field record to specify the service configuration.
11 corresponding to the Service Configuration information
12 record.
17 fields of the Service Configuration information record.
21 fields as specified in 3.7.5.7 for the Service Configuration
23 NNSCR_INCLUDED - Non Negotiable Service Configuration Record Included
24 indicator
25 The base station shall omit this field, if EXTRA_PARMS is set
26 to ‘0’; otherwise, the base station shall include this field and
27 set this field as described below:
28 This base station shall set this field to ‘1’, if the Non
29 Negotiable Service Configuration record is included in this
30 message; otherwise, the base station shall set this field to ‘0’.
31 If NNSCR_INCLUDED is included and is set to ‘1’, the base station shall include one
32 occurrence of the following three-field record to specify the non-negotiable service
33 configuration.
38 corresponding to the Non-Negotiable Service Configuration
44 fields of the Non-Negotiable Service Configuration information
45 record.
3-350
C.S0005-0-2 v1.0

4 fields as specified in 3.7.5.20 for the Non-Negotiable Service
6 USE_PWR_CNTL_STEP - Power control step size indicator.
7 The base station shall set this field to ‘1’ if the field
8 PWR_CNTL_STEP is included in the message.
9 PWR_CNTL_STEP - Power control step size.
10 If USE_PWR_CNTL_STEP is set to ‘1’, then the base station
11 shall include the field PWR_CNTL_STEP and set this field to
12 the step size that the mobile station is to use for closed loop
13 power control, according to Table 3.7.3.3.2.25-1; otherwise,
15 CLEAR_RETRY_DELAY - Clear retry delay indicator.
17 is to clear any existing retry delay which it has stored (see
18 2.6.6.2.5.1); otherwise, the base station shall set this field to
19 ‘0’.
20 SCH_INCL - SCH related parameters included indicator.
21 The base station shall set this field to '1' if this message
22 include the NUM_FOR_ASSIGN, NUM_REV_ASSIGN, NUM_
23 FOR_SCH, NUM_ REV_SCH, and NUM_SCH fields. Otherwise,
24 the base station shall set this field to '0'.
25 NUM_FOR-
26 _ASSIGN - Number of Forward Supplemental Channel assigned.
27 If SCH_INCL is set to ‘0’, the base station shall omit this field;
29 Forward Supplemental Channel assigned.
30 The base station shall include NUM_FOR_ASSIGN occurrences of the following five fields
31 (FOR_SCH_ID, FOR_SCH_DURATION, FOR_SCH_START_TIME_INCL,
32 FOR_SCH_START_TIME, and SCCL_INDEX).
33
34 FOR_SCH_ID - Forward Supplemental Channel identifier.

35 The base station shall set this field to the Identifier of the
37 FOR_SCH_DURATION - Duration of Forward Supplemental Channel assignment.

38 The base station shall set this field to the duration (see Table
39 3.7.3.3.2.37-3), starting at the start time of the message
40 specified by FOR_START_TIME, during which the mobile
41 station is to process the Forward Supplemental Channel.
3-351
C.S0005-0-2 v1.0
1 The base station shall set this field to ‘0000’ to indicate that
2 the mobile station should stop processing the Forward
3 Supplemental Channel starting at the explicit start time of the
4 message specified by FOR_SCH_START_TIME or at the
5 implicit start time if FOR_SCH_START_TIME_INCL is set to ‘0’.
7 the mobile station should process the Forward Supplemental
8 Channel, starting at the start time of the message specified by
9 FOR_SCH_START_TIME, until the start time specified by a
10 subsequent Forward Supplemental Channel assignment
11 corresponding to the same Supplemental Channel (see
12 2.6.6.2.5.1.1).
13 FOR_SCH_
14 START_TIME_INCL - Start time included indicator.
15 If FOR_SCH_DURATION is not equal to ‘0000’, the base

16 station shall set this field to ‘1’. If FOR_SCH_DURATION is
17 equal to ‘0000’, the base station shall set this field as follows:
19 FOR_SCH_START_TIME is included in this message;
21 FOR_SCH_START_TIME - Start time for Forward Supplemental Channel Assignment.

22 If FOR_SCH_START_TIME INCL is set to ‘0’, the base station
23 shall omit this field; otherwise, the base station shall set this
24 field to the System Time, in units of time specified by
25 START_TIME_UNIT, (modulo 32) at which the mobile station is
26 to start processing the Forward Supplemental Channel
27 specified in this message. The explicit start time for
28 processing Forward Supplemental Channels is the time for
29 which
30 (t/(START_TIME_UNIT+1) − FOR_SCH_START_TIME) mod 32

31 = 0,
33 SCCL_INDEX - Supplemental Channel Code list index.
34 The base station shall set this field to the index of the record
35 in the Forward Supplemental Channel Code list corresponding
36 to the FOR_SCH_ID. The base station shall include an
37 SCCL_INDEX whose SCH Active Set is a subset of the Active
38 Set of the Fundamental Channel, Dedicated Control Channel,
39 or both.
40 NUM_REV-
41 _ASSIGN - Number of Reverse Supplemental Channel assigned.
3-352
C.S0005-0-2 v1.0
3 Reverse Supplemental Channel assigned.
4 The base station shall include NUM_REV_ASSIGN occurrences of the following five fields
5 (REV_SCH_ID, REV_SCH_DURATION, REV_SCH_START_TIME_INCL,
6 REV_SCH_START_TIME, and REV_SCH_RATE).
7 REV_SCH_ID - Reverse Supplemental Channel Identifier.

8 The base station shall set this field to the identifier of the
10 REV_SCH_DURATION - Duration of Reverse Supplemental Channel assignment.

11 The base station shall set this field to '0000' to indicate that
12 the mobile station is to stop transmitting on the Reverse
13 Supplemental Channel specified by REV_SCH_ID at the
14 explicit start time specified by REV_SCH_START_TIME or at
15 the implicit start time if REV_SCH_START_TIME_INCL is set
16 to ‘0’. The base station shall set this field to '1111' to indicate
17 that the mobile station may transmit on the Reverse
18 Supplemental Channel specified by REV_SCH_ID, starting at
19 the explicit start time specified by REV_SCH_START_TIME in
20 this message, until the start time specified by a subsequent
21 Reverse Supplemental Channel assignment corresponding to
22 the same Supplemental Channel (see 2.6.6.2.5.1.1). The base
23 station shall set this field to the duration according to Table
24 3.7.3.3.2.37-3, starting at the explicit start time specified by
25 REV_SCH_START_TIME, during which the mobile station may
26 transmit on the Reverse Supplemental Channel specified by
27 REV_SCH_ID.
28 REV_SCH-
29 _START_TIME_INCL - Start time included indicator.

30 If REV_SCH_DURATION is not equal to ‘0000’, the base
31 station shall set this field to ‘1’. If REV_SCH_DURATION is

34 REV_SCH_START_TIME is included in this message;
3-353
C.S0005-0-2 v1.0
1 REV_SCH_START_TIME - Start time for Reverse Supplemental Channel Assignment.
2 If REV_SCH_START_TIME_INCL is set to ‘0’, the base station

5 START_TIME_UNIT, (modulo 32) at which the mobile station
6 may start transmitting on the Reverse Supplemental Channel
8 transmitting on the Reverse Supplemental Channel is the time
9 for which
10 (t/(START_TIME_UNITs+1) − REV_SCH_START_TIME) mod

11 32 = 0,
13 REV_SCH_RATE - Reverse Supplemental Channel rate granted by the base

14 station.
15 The base station shall set this field (see Table 3.7.3.3.2.37-1)
16 to indicate the Reverse Supplemental Channel rate that is
21 relative to that of 20 ms frames at a 9600 bps or 14400 bps
22 rate on the Forward Fundamental Channel or the Forward
23 Dedicated Control Channel that the Forward Power Control
24 Subchannel is punctured on. The base station shall set the
25 value in units of 0.25 dB.
26 USE_PC_TIME - Use power control action time indicator.
27 This field indicates whether an explicit time
28 [PC_ACTION_TIME] at which a new value for power control
29 sub-channel to traffic ratio (FPC_SUBCHAN_GAIN] takes effect
30 is specified in the message.
34 PC_ACTION_TIME - Power Control Subchannel gain action time.
35 If the USE_PC_TIME field is set to ‘1’, the base station shall
36 set this field to the System Time, in units of 80 ms (modulo
37 64), at which FPC_SUBCHAN_GAIN specified in this message
38 is to take effect. If the USE_PC_TIME field is set to ‘0’ the
42 3.7.3.3.2.36-1.
3-354
C.S0005-0-2 v1.0
CH_IND Physical Resource(s) Allocated

(Binary)
000 Reserved.
001 Reserved
011 Reserved
100 Reserved
101 For Radio Configurations 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
3 ACTIVE_SET_REC_LEN - Active Set record length.

5 the ACTIVE_SET_REC_FIELDS included in this message.
6 ACTIVE_SET-
7 _REC_FIELDS - Active Set record fields.
8 The Active Set record fields are determined by the value of
9 CH_IND, as described below.
10 REV_FCH-
13 is allowed to perform the reverse eighth gating mode after
14 handoff; otherwise, the base station shall set this field to ‘0’.
15 REV_PWR-
3-355
C.S0005-0-2 v1.0
1 REV_PWR-
12 mobile station after handoff, in units of 1.25 ms.
14 NUM_FOR_SCH - Number of Forward Supplemental Channel records.
18 Forward Supplemental Channel records need to be updated.
19 If NUM_FOR_SCH is included and not equal to ‘00000’, the base station shall include
20 NUM_FOR_SCH occurrence of the following three fields:
26 in the Supplemental Channel Code list.
27 FOR_SCH_RATE - Forward Supplemental Channel Rate.
28 The base station shall set this field to the data rate (see Table
29 3.7.3.3.2.37-1) corresponding to SCCL_INDEX.
30 NUM_REV_SCH - Number of Reverse Supplemental Channel records.
34 Reverse Supplemental Channels need to be updated.
35 If NUM_REV_SCH is included and not equal to ‘00000’, the base station shall include
36 NUM_REV_SCH occurrence of the following three fields:
37 REV_SCH_ID - Reverse Supplemental Channel identifier.
40 REV_WALSH_ID - Reverse Supplemental Channel Walsh cover Identifier.
3-356
C.S0005-0-2 v1.0
1 The base station shall set this field according to Table

2 3.7.3.3.2.37-2 to indicate the Walsh cover ID that the mobile
3 station is to use when transmitting at the rate specified by
4 REV_SCH_RATE on the Reverse Supplemental Channel
5 specified by REV_SCH_ID. If only one reverse supplemental
6 channel is assigned, the base station should set this field to
7 the default value for the REV_WALSH_ID as specified in
8 2.6.4.2.
9 REV_SCH_RATE - Reverse Supplemental Channel Rate.

11 3.7.3.3.2.37-1 to indicate the rate corresponding to the
12 REV_WALSH_ID field.

15 included in the message. The base station shall set this field
16 to an integer that is equal to or greater than 1.
17 SRCH_OFFSET_INCL - Target pilot channel search window offset included.
18 If the SRCH_OFFSET field is included in the following records,
21 The base station shall include one occurrence of the following record for each of the
22 NUM_PILOTS pilots included in the message:
26 SRCH_OFFSET - Target pilot channel search window offset.
27 If SRCH_OFFSET_INCL equals to ‘1’, then the base station
30 mobile station for this target pilot. Otherwise, the base
44 omit this field.
3-357
C.S0005-0-2 v1.0

6 omit this field.
12 omit this field.
13
15
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6
16

20 in Table 3.7.2.3.2.21-6.
3-358
C.S0005-0-2 v1.0
1 CODE_CHAN_FCH - Code channel on the Fundamental Channel.

3 used, the base station shall set this field to the code channel
4 index (see 2.1.3.1.9 and 3.1.3.1.13 of TIA/EIA/IS-2000-2)[2])
6 of the Forward Traffic Channel. If Radio Configuration 1, 2, 3,
7 or 5 (see 3.1.3.1.2 of TIA/EIA/IS-2000-2)[2]) is used, the base
13 QOF_MASK_ID_FCH - Quasi-orthogonal function index on the Fundamental
14 Channel.
16 used, the base station shall set this field to the index of the
17 Quasi-orthogonal function (see Table 3.1.3.1.13-2 of
18 TIA/EIA/IS-2000-2)[2]).
19 NUM_SCH - Number of Supplemental Channel records.
23 Supplemental Channel records need to be updated.
24 If NUM_SCH is included and not equal to ‘00000’, the base station shall include NUM_SCH
25 occurrence of the following five fields:
27 The base station shall set this field the identifier of the
28 Forward Supplemental Channel pertaining to this record.
32 PILOT_INCL - The corresponding pilot included in Supplemental Channel
33 Active Set indicator.
34 The base station shall set this field to ‘1’ if the corresponding
35 pilot is included in the Active Set of Supplemental Channel;
37 CODE_CHAN_SCH - Code channel on the Supplemental Channel.
38 If PILOT_INCL is included and set to ‘1’, the base station shall
39 set this field as follows; otherwise, the base station shall omit
40 this field.
42 (see 2.1.3.1.9 and 3.1.3.1.13 of TIA/EIA/IS-2000-2)[2]) that
43 the mobile station is to use on the Supplemental Channel of
44 the Forward Traffic Channel indexed by SCCL_INDEX.
3-359
C.S0005-0-2 v1.0
1 QOF_MASK_ID_SCH - Quasi-orthogonal function index on the Supplemental

2 Channel.
3 If PILOT_INCL is included and set to ‘1’, the base station shall
4 set this field as follows; otherwise, the base station shall omit
5 this field.
6 The base station shall set this field to the index of the Quasi-
7 orthogonal function (see Table 3.1.3.1.13-2 of TIA/EIA/IS-
8 2000-2)[2]).
10 If the CH_IND field is set to ‘010’ or ‘110’, the base station shall include the following fields:
19 The base station shall set this field to identifier of the Forward
31 Forward Supplemental Channels need to be updated.
3-360
C.S0005-0-2 v1.0

8 2.6.4.2.


44 omit this field.
3-361
C.S0005-0-2 v1.0

6 omit this field.
12 omit this field.
13
15
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6
16

20 in Table 3.7.2.3.2.21-6.
3-362
C.S0005-0-2 v1.0
1 CODE_CHAN_DCCH - Code channel on the Dedicated Control Channel.

6 Channel of the Forward Traffic Channel. If Radio
8 2)[2]) is used, the base station shall set this field in the range
13 QOF_MASK_ID_DCCH - Quasi-orthogonal function index on the Dedicated Control
14 Channel.
18 TIA/EIA/IS-2000-2)[2]).
24 If NUM_SCH is included and not equal to ‘00000’, the mobile station shall include
25 NUM_SCH occurrence of the following five fields:
26 FOR_SCH_ID - Forward Supplemental Channel identifier
37 CODE_CHAN_SCH - Code channel on the Supplemental Channel.
43 Channel.
3-363
C.S0005-0-2 v1.0
3 2000-2)[2]).
26 Forward Supplemental Channels need to be updated.
40 2.6.4.2.
3-364
C.S0005-0-2 v1.0


35 omit this field.
41 omit this field.
3-365
C.S0005-0-2 v1.0

5 omit this field.
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6

13 in Table 3.7.2.3.2.21-6.
23 CODE_CHAN_FCH - Code Channel on the Fundamental Channel.
28 of the Forward Traffic Channel. If Radio Configuration 1, 2, 3,
29 or 5 (see 3.1.3.1.2 of TIA/EIA/IS-2000-2)[2]) is used, the base
35 QOF_MASK_ID_FCH - Quasi-orthogonal function index on the Fundamental
36 Channel.
40 TIA/EIA/IS-2000-2)[2]).
3-366
C.S0005-0-2 v1.0
1 CODE_CHAN_DCCH - Code channel on the DCCH.

6 Channel of the Forward Traffic Channel. If Radio
8 2)[2]) is used, the base station shall set this field in the range
13 QOF_MASK_ID_DCCH - Quasi-orthogonal function index on the DCCH.
17 TIA/EIA/IS-2000-2)[2]).
21 If NUM_SCH is included and not equal to ‘00000’, the mobile station shall include
22 NUM_SCH occurrence of the following fields:
28 in the Supplemental Channel Code List Table.
34 CODE_CHAN_SCH - Code Channel on the Supplemental Channel.
42 Channel.
3-367
C.S0005-0-2 v1.0
3 2000-2)[2]).
4
3-368
C.S0005-0-2 v1.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 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
REV_SCH_RATE 4
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
REV_SCH_RATE 4

5
3-369
C.S0005-0-2 v1.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 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
FOR_SCH_RATE 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
FOR_SCH_CC_INDEX 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-370
C.S0005-0-2 v1.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
1
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.
3-371
C.S0005-0-2 v1.0
1 The base station shall set this field to the maximum duration
2 of time in units of 20 ms that the mobile station is allowed to
3 stop transmission on a Reverse Supplemental Channel within
4 the reverse assignment duration. The base station shall set
5 this field to ‘0000’ if the mobile station is to stop using a
6 Reverse Supplemental Channel once it has stopped
7 transmitting on that Reverse Supplemental Channel. The base
8 shall set this field to ‘1111’ if the mobile station is allowed to
9 resume transmission on a Reverse Supplemental Channel at
10 any time within the reverse assignment duration.
13 mobile station is to utilize the T_ADD Reverse Supplemental
14 Channel abort feature for this reverse assignment; otherwise,
16 USE_SCRM_SEQ_NUM - Use Supplemental Channel Request Message sequence

19 SCRM_SEQ_NUM field is included in this message; otherwise,
21 SCRM_SEQ_NUM - Supplemental Channel Request Message sequence number.
22 If USE_SCRM_SEQ_NUM is set to ‘1’, the base station shall set

23 this field to the sequence number corresponding to the
24 SCRM_SEQ_NUM field in a Supplemental Channel Request
25 Message to which the mobile station is to match this message;
27 ADD_INFO_INCL - Additional information included indicator.

28 If the message is to contain the FPC_PRI_CHAN field, the base
31 The base station shall set this field to ‘0’ if any of the following
32 conditions hold:
33 – The message does not contain any Supplemental Channel
34 assignment.
35 – The mobile station is currently in Active Mode.
36 FPC_PRI_CHAN - Power Control Subchannel Indicator.
37 If the ADD_INFO_INCL field is set to ’0’, the base station shall
38 omit this field; otherwise, the base station shall set this field
39 as follows:
3-372
C.S0005-0-2 v1.0
10 Channel.
11 REV_CFG_INCLUDED - Reverse Supplemental Channel configuration included.
13 contains a Reverse Supplemental Channel configuration.
14 Otherwise, the base station shall set this field to '0'.
15 NUM_REV_CFG_RECS - Number of the Reverse Supplemental Channel configuration
16 Records.
17 If REV_CFG_INCLUDED is set to ‘1’, the base station shall set
18 this field to one less than the number of reverse supplemental
19 channel configuration records consisting of the following three
20 fields that are included in this message; otherwise, the base
22 The base station shall include NUM_REV_CFG_RECS+1 occurrences of the following three
23 fields only if the REV_CFG_INCLUDED field is set to ‘1’.
35 2.6.4.2.
36 Table 3.7.3.3.2.37-2. REV_WALSH_ID Field
Walsh Cover
REV_WALSH_ID
(binary) SCH_ID = '0' SCH_ID = '1'
0 +- ++--
1 ++-- ++----++
37
3-373
C.S0005-0-2 v1.0

4 Table 3.7.3.3.2.37-1. SCH Data Rate
REV_SCH_RATE Rate Granted by the

Base Station (kbps)
FOR_SCH_RATE
(binary)
R-RC 3, 5 R-RC 4, 6
F-RC 3, 4, F-RC5, 8, 9
6, 7
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
5
6 NUM_REV_SCH - Number of Reverse Supplemental Channels assigned.

7 The base station shall set this field to the number of Reverse
8 Supplemental Channel assigned. The base station shall set
9 this field to ‘00’ if the assignment of Supplemental Channel is
10 not included.
11 The base station shall include NUM_REV_SCH occurrences of the following five fields
12 (REV_SCH_ID, REV_SCH_DURATION, REV_SCH_START_TIME_INCL,
13 REV_SCH_START_TIME, and REV_SCH_RATE).

17 REV_SCH_DURATION - Duration of Reverse Supplemental Channel assignment
3-374
C.S0005-0-2 v1.0
3 Supplemental Channel specified by REV_SCH_ID at the
4 explicit start 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 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 Table 3.7.3.3.2.37-3. FOR_SCH_DURATION and

19 REV_SCH_DURATION Fields
FOR_SCH_DURATION Duration in 20 ms
REV_SCH_DURITION
(binary)
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 Infinite
3-375
C.S0005-0-2 v1.0
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_START_TIME - Start time for Reverse Supplemental Channel assignment.
10 If REV_SCH_START_TIME_INCL is set to ‘0’, the base station

13 START_TIME_UNIT, (modulo 32) at which the mobile station
14 may start transmitting on the Reverse Supplemental Channel
16 transmitting on the Reverse Supplemental Channel is the time
17 for which
18 (t/(START_TIME_UNITs+1) − REV_SCH_START_TIME) mod
19 32 = 0,
22 station.
24 to indicate the Reverse Supplemental Channel rate that is
26 FOR_CFG_INCLUDED - Forward Supplemental Channel configuration included.
28 contains a Forward Supplemental Channel configuration.
29 Otherwise, the base station shall set this field to '0'.
30 FOR_SCH_FER_REP - Forward Supplemental Channel FER report indicator.
31 If FOR_CFG_INCLUDED is set to ‘0’, the base station shall
32 omit this field, otherwise, the base station shall include this
35 is to report the Supplemental Channel frame counts (see
36 2.6.4.1.1); otherwise, the base station shall set this field to ‘0’.
37 NUM_FOR_CFG_RECS - Number of the Forward Supplemental Channel configuration
38 Records.
39 If FOR_CFG_INCLUDED is set to ‘1’, the base station shall set
40 this field to one less than the number of forward supplemental
41 channel configuration records consisting of the following three
42 fields that are included in this message; otherwise, the base
44 The base station shall include NUM_FOR_CFG_RECS+1 occurrences of the following fields
3-376
C.S0005-0-2 v1.0
1 only if the FOR_CFG_INCLUDED field is set to ‘1’.

2 FOR_SCH_ID - Forward Supplemental Channel identifier
8 FOR_SCH_RATE - Forward Supplemental Channel rate
10 to indicate the data rate corresponding to SCCL_INDEX.
11 NUM_SUP_SHO - Number of Forward Supplemental Channels in Soft Handoff

12 The base station shall set this field to the size of the Forward
13 Supplemental Channel Active Set minus one.
14 The base station shall include NUM_SUP_SHO+1 occurrences of the following fields for each
15 Forward Supplemental channel corresponding to the FOR_SCH_ID and the SCCL_INDEX
16 whose frames may be soft-combined by the mobile station:
17

23 information listed in ACTIVE_PILOT_REC_TYPE and
27 PILOT_REC_TYPE - Pilot record type
33 omit this field.
39 omit this field.
3-377
C.S0005-0-2 v1.0

3 ACTIVE_PILOT_REC_TYPE of this pilot record.
5 omit this field.
6 If PILOT_REC_TYPE is equal to ‘000’, the base station shall

7 include the following fields:
Field Length (bits)
OTD_POWER_LEVEL 2
RESERVED 6

13 in Table 3.7.2.3.2.21-6.
14 FOR_SCH_CC_INDEX - Forward Supplemental Channel code channel index.
15 The base station shall set this field to the Forward
16 Supplemental Channel code channel corresponding to
17 PILOT_PN.
19 Channel.
21 orthogonal function (see 3.1.3.1.13 of TIA/EIA/IS-2000-2)[2]).
22
23 NUM_FOR_SCH - Number of Forward Supplemental Channels assigned.

24 The base station shall set this field to the number of forward
25 Supplemental Channel assigned. The base station shall set
26 this field to ‘00’ if the assignment of Supplemental Channel is
27 not included.
28 The base station shall include NUM_FOR_SCH occurrences of the following five fields
29 (FOR_SCH_ID, FOR_SCH_DURATION, FOR_SCH_START_TIME_INCL,
30 FOR_SCH_START_TIME, and SCCL_INDEX).
31

3-378
C.S0005-0-2 v1.0
3 specified by FOR_SCH_START_TIME, during which the mobile
7 Supplemental Channel starting at the explicit start time of the
8 message specified by FOR_SCH_START_TIME or at the
9 implicit start time if FOR_SCH_START_TIME_INCL is set to ‘0’.
12 Channel, starting at the start time of the message specified by
13 FOR_SCH_START_TIME, until the start time specified by a
14 subsequent Forward Supplemental Channel assignment
15 corresponding to the same Supplemental Channel (see
16 2.6.6.2.5.1.1).
17 FOR_SCH-
19 If FOR_SCH_DURATION is not equal to ‘0000’, the base

20 station shall set this field to ‘1’. If FOR_SCH_DURATION is
23 FOR_SCH_START_TIME is included in this message;
25 FOR_SCH-
26 _START_TIME - Start time for Forward Supplemental Channel assignment.
27 If FOR_SCH_START_TIME_INCL is set to ‘0’, the base station
30 START_TIME_UNIT, (modulo 32) at which the mobile station is
31 to start processing the Forward Supplemental Channel
32 specified in this message. The start time for processing
33 Forward Supplemental Channels is the time for which
35 = 0,
43 or both.
44 FPC_INCL - Forward Link Power Control parameter included indicator.
3-379
C.S0005-0-2 v1.0
1 If the forward power control related information is included in

4 FPC_MODE_SCH - Forward Power Control operational mode indicator used
5 during forward Supplemental Channel assignment interval.
6 If FPC_INCL is set to ‘1’, the base station shall set the value to
7 the forward power control operation mode as specified in
8 Table 2.1.3.1.11-1 of TIA/EIA/IS-2000-[2]; otherwise, the base
10 FPC_SCH_INIT_SETPT_OP - Initial Supplemental Channel Outer Loop Eb/Nt setpoint
11 option.
15 FPC_SCH_INIT_SETPT contains the absolute value of the
16 initial F-SCH Eb/Nt setpoint. The base station shall set this
17 field to ‘1’ to indicate that FPC_SCH_INIT_SETPT contains the
18 offset value of the initial F-SCH Eb/Nt setpoint relative to the
19 current value used in the mobile station for the channel
20 carrying the Forward Power Control Subchannel.
21 FPC_SEC_CHAN - Master Supplemental channel index.
22 If FPC_INCL is set to '1' and FPC_MODE_SCH is set to '001' or
23 '010', the base station shall set this field to the master
24 Supplemental Channel index; otherwise, the base station shall
25 omit this field.
26 NUM_SUP - Number of Supplemental Channels.
28 otherwise, the base station shall set this field to the total
29 number of the Supplemental Channels.
30 The base station shall include NUM_SUP occurrences of the following record:
33 Channel index.
34 FPC_SCH_FER - Supplemental channel target Frame Error Rate.
36 Rate on the Supplemental Channel, as specified in Table
37 3.7.3.3.2.25-2.
38 FPC_SCH_INIT_SETPT - Initial Supplemental Channel Output Loop Eb/Nt setpoint
39 The base station shall set this field to initial Supplemental
40 Channel Outer Loop Eb/Nt setpoint (absolute value or offset
41 value as indicated by FPC_SCH_INIT_SETPT_OP) as follows:.
42 • If FPC_SCH_INIT_SETPT_OP is set to '0', the unit is 0.125

43 dB;
3-380
C.S0005-0-2 v1.0
1 • If FPC_SCH_INIT_SETPT_OP is set to '1', the unit is 0.125

2 dB and the offset is expressed as two's complement signed
3 number.
4 FPC_SCH_MIN_SETPT - Minimum Supplemental Channel outer loop Eb/Nt setpoint.
5 The base station shall set this field to minimum Supplemental
7 FPC_SCH_MAX_SETPT - Maximum Supplemental Channel outer loop Eb/Nt setpoint.
8 The base station shall set this field to maximum Supplemental
10 FPC_THRESH_SCH_INCL - SCH Setpoint Report Threshold Included Indicator.
12 otherwise, the base station shall include this field and set it as
13 follows:
14 If SCH setpoint report threshold is included in this message,
17 FPC_SETPT_THRESH_SCH - SCH Setpoint Report Threshold.
18 If FPC_THRESH_SCH_INCL is set to ‘1’, the base station shall
19 set this field to the value of the Supplemental Channel
20 setpoint threshold (in units of 0.125 dB) above which the
21 outer loop report message will be sent by the mobile station;
23 RPC_INCL - Reverse Power Control parameter included indicator.
24 The base station shall set this field to ‘1’ if RPC_NUM_SUP is
25 included in this message; otherwise the base station shall set
27 RPC_NUM_SUP - Number of Supplemental Channels.
28 If RPC_INCL is set to ‘1’, the base station shall set this field to
29 the total number of the Supplemental Channels minus one;
31 The base station shall include NUM_SUP +1 occurrences of the following two fields record:
34 Channel index.
35 RLGAIN_SCH_PILOT - Supplemental channel power offset adjustment relative to
36 Reverse Pilot Channel power for radio configurations greater
37 than 2.
39 be used by mobile stations setting the power of a
40 supplemental channel, expressed as a two’s complement value
41 in units of 0.125 dB.
42
43
3-381
C.S0005-0-2 v1.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-382
C.S0005-0-2 v1.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
18 specified by a subsequent Forward Supplemental Channel
19 assignment corresponding to the same 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.
39
3-383
C.S0005-0-2 v1.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
REV_SCH_RATE 4
3-384
C.S0005-0-2 v1.0
4 REV_SCH_DURATION - Duration of Reverse Supplemental Channel assignment.
7 Supplemental Channel specified by REV_SCH_ID at the start
8 time specified by START_TIME. The base station shall set this
9 field to '1111' to indicate that the mobile station may transmit
10 on the Reverse Supplemental Channel specified by
11 REV_SCH_ID, starting at the start time specified by
12 REV_SCH_START_TIME in this message, until the start time
13 specified by a subsequent Reverse Supplemental Channel
14 assignment corresponding to the same Supplemental Channel
15 (see 2.6.6.2.5.1.1). The base station shall set this field to the
16 duration according to Table 3.7.3.3.2.37-3, starting at the
17 explicit start time specified by REV_SCH_START_TIME, during
18 which the mobile station may transmit on the Reverse
19 Supplemental Channel specified by REV_SCH_ID.
20 REV_SCH-
21 _START_TIME - Start time for Reverse Supplemental Channel Assignment Mini

22 Message.
24 units of time specified by START_TIME_UNIT, (modulo 32) at
25 which the mobile station may start transmitting on the
26 Reverse Supplemental Channel specified in this message. The
27 explicit start time for transmitting on the Reverse
28 Supplemental Channel is the time for which
29 (t/(START_TIME_UNIT+1) − REV_SCH_START_TIME) mod 32

30 = 0,

33 station.

35 3.7.3.3.2.37-1 to indicate the Reverse Supplemental Channel
36 rate, that is assigned to the mobile station.
37
3-385
C.S0005-0-2 v1.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-386
C.S0005-0-2 v1.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 0.5
18 dB, must be measured for ORDER_INTERVAL successive 20
19 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-387
C.S0005-0-2 v1.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-388
C.S0005-0-2 v1.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 corresponding to the User Zone rejection
9 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.
17
3-389
C.S0005-0-2 v1.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.
7
3-390
C.S0005-0-2 v1.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.
24
3-391
C.S0005-0-2 v1.0
1 Table 3.7.4-1. Order and Order Qualification Codes Used on the f-csch and the f-dsch
2 (Part 1 of 3)
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 TIA/EIA/IS-
2000.[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
00001010 (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)
3-392
C.S0005-0-2 v1.0
Y N 010010 11111111 N N Unlock Order

1
3-393
C.S0005-0-2 v1.0
2 (Part 2 of 3)
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
3-394
C.S0005-0-2 v1.0
2 (Part 3 of 3)
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; see 3.7.4.5)
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)
Y N 011111 00000000 N N Slotted Mode Order

(transition to the slotted
mode operation.)
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)

3
3-395
C.S0005-0-2 v1.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.
12
3-396
C.S0005-0-2 v1.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

8 The base station shall set this field to the service option code
9 shown in TSB58-A, corresponding to the requested or
10 alternative service option.
11
3-397
C.S0005-0-2 v1.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

8 The base station shall set this field to the service option code
9 shown in TSB58-A, corresponding to the accepted service
10 option, or to ‘0000000000000000’ to reject the last service
11 option requested by the mobile station.
12
3-398
C.S0005-0-2 v1.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
11 shown in Table 3.7.4.4-1.
12
13 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.
14
3-399
C.S0005-0-2 v1.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

6 If ROAM_INDI is included in the order, the base station shall set
7 this field to ‘00000101’; otherwise, the base station shall set this
8 field to ‘00000000’.
9 ROAM_INDI - Roaming display indication.
10 If ORDQ is set to ‘00000000’, the base station shall omit this field.
11 If ORDQ is set to ‘00000101’, the base station shall include this
12 field and shall set it to the appropriate ROAM_INDI code
13 corresponding to the MS roaming condition. These values are
14 defined in TSB58-A.
15
3-400
C.S0005-0-2 v1.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
RESERVED 6

6 The base station shall set this field to a report period, in units
7 of 0.08 seconds, in the range of ‘00001010’ to ‘1111110’
8 inclusive. The base station shall set this field to ‘11111111’ to
9 request a one time Periodic Pilot Strength Measurement
10 Message.
11 MIN_PILOT_PWR-
12 _THRESH - The threshold of the total received Ec of the pilots in the
13 Active Set.
14 If the mobile station is to report pilot strength measurements
15 periodically to the base station irrespective of the pilot power
16 of the Active Set, the base station shall set this field to
17 ‘11111’; otherwise, the base station shall set this field to the
18 total Ec threshold, expressed as an unsigned binary number
19 equal to:
20  (10 × log10(pilot_ec_thresh) + 120) / 2 
21 where pilot_ec_thresh is the threshold of the mobile station

22 received total Ec (in mW) of the pilots in the Active Set below
23 which the mobile station is to send the pilot strength
24 measurements periodically to the base station.
25 MIN_PILOT_EC-
26 _IO_THRESH - Pilot Strength Threshold of Serving Frequency.
27 If the mobile station is to ignore this threshold, the base
29 station shall set this field to the total Ec/Io threshold,
30 expressed as an unsigned binary number equal to:
31 - 20 × log10 pilot_streng_thresh ,
3-401
C.S0005-0-2 v1.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.
7 3.7.4.7 Retry Order

8 The Retry Order can be sent on either the f-csch or on the f-dsch to indicate the requested
9 service is rejected and specify the retry delay.
10
ORDQ 8
RETRY_TYPE 3
RETRY_DELAY 0 or 8
RESERVED 5

13 RETRY_TYPE - Retry delay type.
14 The base station shall set this field specified as in Table
15 3.7.4.7-1.
16 Table 3.7.4.7-1 Retry Delay Type
Value Retry Type Usage

(binary)
3-402
C.S0005-0-2 v1.0
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
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
2 RETRY_DELAY - Retry delay.

3 If RETRY_TYPE is set to ‘000’ the base station shall omit this
4 field. Otherwise the base station shall include this field and
6 If RETRY_TYPE is set to ‘001’, the base station shall set this
7 field to the duration of the delay interval, as shown in Table
8 3.7.4.7-2, during which the mobile station is not permitted to
9 send an Origination Message with the same Packet Data
10 Service Option. The base station shall set this field to
11 ‘00000000’ to indicate that there is no retry delay or to clear a
12 previously set retry delay.
13 Table 3.7.4.7-1 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
14
3-403
C.S0005-0-2 v1.0
1 If RETRY_TYPE is set to ‘010’ or ‘011’, the base station shall

2 set this field to the duration of the delay interval in units of
3 320 ms during which the mobile station is not permitted to
4 send another Supplemental Channel Request (Mini) Message or
5 Resource Request (Mini) Message. The base station shall set
6 RETRY_DELAY to ‘00000000’ to indicate that there is no retry
7 delay or to clear a previously set retry delay. The base station
8 shall set RETRY_DELAY to ‘11111111’ to indicate that the
9 mobile station is to refrain from sending the request
10 indefinitely.
13
3-404
C.S0005-0-2 v1.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 and
4 the Flash with Information Message. Table 3.7.5-1 lists the information record type values
5 that may be used with each message type. The following sections describe the contents of
6 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
3-405
C.S0005-0-2 v1.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
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-406
C.S0005-0-2 v1.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-407
C.S0005-0-2 v1.0
Record
Type
Non-Negotiable Service 00010011 SCM N Y

Configuration
GHDM N Y
UHDM N Y
Extended Record Type - 11111110 Country-Specific

International

2
3-408
C.S0005-0-2 v1.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
9 each occurrence of this field to the ASCII representation
10 corresponding to the character entered, as specified in ANSI
12
3-409
C.S0005-0-2 v1.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 ANSI T1.607-1990, Section
9 4.5.9[8].
10 NUMBER_PLAN - Numbering plan.
11 The base station shall set this field to the NUMBER_PLAN
13 numbering plan used for the called number, as defined in
14 ANSI T1.607-1990, Section 4.5.9[8].
17 each character in the called number. The base station shall
19 corresponding to the character, as specified in ANSI X3.4[12],
20 with the most significant bit set to ‘0’.
23
3-410
C.S0005-0-2 v1.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 ANSI T1.607-1990,
9 Section 4.5.9[8].
13 numbering plan used for the calling number, as defined in
14 ANSI T1.607-1990, Section 4.5.9[8].
15 PI - Presentation indicator.
16 This field indicates whether or not the calling number should
17 be displayed.
18 The base station shall set this field to the PI value shown in
21 SI - Screening indicator.
22 This field indicates how the calling number was screened.
23 The base station shall set this field to the SI value shown in
3-411
C.S0005-0-2 v1.0
2 The base stations shall include one occurrence of this field for
3 each character in the calling number. The base station shall
5 corresponding to the character, as specified in ANSI X3.4[12],
6 with the most significant bit set to ‘0’.
9
3-412
C.S0005-0-2 v1.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 ANSI T1.607-1990,
9 Section 4.5.9[8].
13 numbering plan used for the connected number, as defined in
14 ANSI T1.607-1990, Section 4.5.9[8].
16 This field indicates whether or not the connected number
17 should be displayed.
18 The base station shall set this field to the PI value shown in
22 This field indicates how the connected number was screened.
23 The base station shall set this field to the SI value shown in
3-413
C.S0005-0-2 v1.0
3 each character in the connected number. The base station
9
3-414
C.S0005-0-2 v1.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
10 shown in Table 3.7.5.5-1.
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-415
C.S0005-0-2 v1.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-416
C.S0005-0-2 v1.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-417
C.S0005-0-2 v1.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-418
C.S0005-0-2 v1.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.

5
3-419
C.S0005-0-2 v1.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.
8
3-420
C.S0005-0-2 v1.0
1 3.7.5.7 Service Configuration

2 This record is included in a Service Request Message and a Service Response Message to
3 propose a service configuration. It is included in a Service Connect Message to specify an
4 actual service configuration to be used. It can be included in a General Handoff Direction
5 Message and Universal Handoff Direction Message to specify an actual service configuration
6 to be used.
FOR_MUX_OPTION 16
REV_MUX_OPTION 16
FOR_RATES 8
REV_RATES 8
NUM_CON_REC 8
NUM_CON_REC occurrences of the following variable-length

record:
3-421
C.S0005-0-2 v1.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)
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-422
C.S0005-0-2 v1.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 Traffic Channel multiplex option.

5 Message, the base station shall set this field to the number of
6 the Forward Traffic Channel multiplex option in the proposed
8 For a Service Connect Message, General Handoff Direction
9 Message, and a Universal Handoff Direction Message, the base
10 station shall set this field to the number of the Forward Traffic
11 Channel multiplex option of the actual service configuration to
12 be used.
13 REV_MUX_OPTION - Reverse Traffic Channel multiplex option.
15 Message, the base station shall set this field to the number of
16 the Reverse Traffic Channel multiplex option in the proposed
3-423
C.S0005-0-2 v1.0

3 station shall set this field to the number of the Reverse Traffic
4 Channel multiplex option of the actual service configuration to
5 be used.
6 FOR_RATES - Transmission rates of the Forward Fundamental Channel.
7 The base station shall set this field to the Forward
8 Fundamental Channel transmission rates specified in 2.7.4.17
9 for the specified Forward Traffic Channel multiplex option.
11 the base station shall set the subfields corresponding to the
12 Forward Fundamental Channel transmission rates of the
13 proposed service configuration to ‘1’, and shall set the
14 remaining subfields to ‘0’. The base station shall set
18 station shall set the subfields corresponding to the Forward
19 Fundamental Channel transmission rates of the actual service
20 configuration to be used to ‘1’, and shall set the remaining
21 subfields to ‘0’. The base station shall set RESERVED to
22 ‘0000’.
23 REV_RATES - Transmission rates of the Reverse Fundamental Channel.
24 The base station shall set this field to the Reverse
25 Fundamental Channel transmission rates specified in 2.7.4.17
26 for the specified Reverse Traffic Channel multiplex option.
28 the base station shall set the subfields corresponding to the
29 Reverse Fundamental Channel transmission rates of the
30 proposed service configuration to ‘1’, and shall set the
31 remaining subfields to ‘0’. The base station shall set
35 station shall set the subfields corresponding to the Reverse
36 Fundamental Channel transmission rates of the actual service
37 configuration to be used to ‘1’, and shall set the remaining
38 subfields to ‘0’. The base station shall set RESERVED to
39 ‘0000’.
40 NUM_CON_REC - Number of service option connection records.
41 The base station shall set this field to the number of service
42 option connection records included in the message.
43 For a Service Request Message or a Service Response Message, the base station shall
44 include one occurrence of the following variable-length record for each service option
45 connection of the proposed service configuration.
3-424
C.S0005-0-2 v1.0
1 For a Service Connect Message, a General Handoff Direction Message, or a Universal Handoff
2 Direction Message, the base station shall include one occurrence of the following variable-
3 length record for each service option connection of the actual service configuration to be
4 used.
5 RECORD_LEN - Service option connection record length.
7 included in this service option connection record including
8 this field.
9 CON_REF - Service option connection reference.
10 For a Service Request Message or a Service Response Message:
11 if the service option connection is part of the current service
12 configuration, the base station shall set this field to the
13 service option connection reference; otherwise, the base
17 station shall set this field to the service option connection
18 reference assigned to the service option connection.
20 The base station shall set this field to the service option to be
21 used with the service option connection.
22 FOR_TRAFFIC - Forward Traffic Channel traffic type.
23 The base station shall set this field to the FOR_TRAFFIC code
24 shown in Table 3.7.5.7-1 corresponding to the Forward Traffic
25 Channel traffic type to be used with the service option
26 connection.
27
28 Table 3.7.5.7-1. FOR_TRAFFIC Codes
FOR_TRAFFIC

use Forward Traffic Channel traffic.
primary traffic on the Forward Traffic
Channel.
secondary traffic on the Forward Traffic
Channel.
All other FOR_TRAFFIC codes are reserved.
29
30 REV_TRAFFIC - Reverse Traffic Channel traffic type.
3-425
C.S0005-0-2 v1.0
1 The base station shall set this field to the REV_TRAFFIC code
2 shown in Table 3.7.5.7-2 corresponding to the Reverse Traffic
3 Channel traffic type to be used with the service option
4 connection.
5
6 Table 3.7.5.7-2. REV_TRAFFIC Codes
REV_TRAFFIC

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.

7
8 UI_ENCRYPT_MODE - Encryption mode indicator for user information privacy.

9 For a Service Request Message or a Service Response Message:
10 the base station shall set this field to the proposed user
11 information encryption mode, as shown in Table 2.7.4.18-3.
14 station shall set this field to the assigned user information
15 encryption mode, as shown in Table 2.7.4.18-3.
17 For a Service Request Message, a Service Response Message, a
18 Service Connect Message, a General Handoff Direction
19 Message, or a Universal Handoff Direction Message, the base
20 station shall set this field as follows:
21 If the service option connection is a part of the current service
22 configuration, the base station shall set this field to the
23 service reference identifier in use.
24 If the service option connection is not a part of the current
25 service configuration, the base station shall perform the
26 following:
28 mobile station, the base station shall set this field to the
29 value sent by the mobile station.
3-426
C.S0005-0-2 v1.0

2 base station, the base station shall perform the following:
3 if the service instance provides a service reference
4 identifier, the base station shall set this field to the service
5 reference identifier specified by the service instance;
6 otherwise, the base station shall set this field to the
7 highest unused service reference identifier value between
8 1 and 6 (inclusive).
9
10 RLP_INFO_INCL - RLP information included indicator.
11 The base station shall set this field to ‘1’ if the RLP_BLOB field
12 is included in this record; otherwise, it shall set this field to
13 ‘0’.
14 RLP_BLOB_LEN - RLP information block of bits length.
15 If the RLP_INFO_INCL field is set to ‘0’, the base station shall

16 omit this field; otherwise, it shall include this field and set it
17 as follows:
18 The base station shall set this field to the size of the
19 RLP_BLOB field in integer number of octets.
20 RLP_BLOB - Radio Link Protocol block of bits.
21 If the RLP_INFO_INCL field is set to ‘0’, the base station shall

24 The base station shall set this field to the Radio Link Protocol
25 block of bits for this service option connection, and shall add
26 ‘0’ bits to the end of the field as needed in order to make the
27 length of this field equal to an integer number of octets.

30 make the length of this record equal to an integer number of
32 FCH_CC_INCL - Channel configuration for the Fundamental Channel included

33 indicator.
34 The base station shall set this field to ‘1’, if the channel
35 configuration information for the Fundamental Channel is
36 included in this Service Configuration Record; otherwise, the
38 FCH_FRAME_SIZE - Fundamental Channel frame size supported indicator.
3-427
C.S0005-0-2 v1.0
1 If the FCH_CC_INCL field is set to ‘0’, the base station shall

4 The base station shall set this field to ‘1’ if the service
5 configuration includes the use of 5 ms frame size in addition
6 to 20ms frame size for the Forward and Reverse Fundamental
7 Channel; otherwise, the base station shall set this field to ‘0’.
8 FOR_FCH_RC - Forward Fundamental Channel Radio Configuration.
13 the base station shall set this field to the Forward
14 Fundamental Channel Radio Configuration (see Table 3.1.3.1-
15 1 of TIA/EIA/IS-2000-[2]) in the proposed service
16 configuration.
17 For a Service Connect Message, a General Handoff Direction
19 station shall set this field to the actual Forward Fundamental
20 Channel Radio Configuration to be used.
21 REV_FCH_RC - Reverse Fundamental Channel Radio Configuration.
26 the base station shall set this field to the Reverse
27 Fundamental Channel Radio Configuration (see Table 2.1.3.1-
28 1 of TIA/EIA/IS-2000-[2]) in the proposed service
29 configuration.
32 station shall set this field to the actual Reverse Fundamental
33 Channel Radio Configuration to be used.
34 DCCH_CC_INCL - Channel configuration for the Dedicated Control Channel
36 The base station shall set this field to ‘1’, if channel
37 configuration information for the Dedicated Control Channel
38 is included in this Service Configuration Record; otherwise,
40 DCCH_FRAME_SIZE - Dedicated Control Channel frame size.
41 If the DCCH_CC_INCL field is set to ‘0’, the base station shall
43 field and set it according to the Table 3.7.5.7-3 as follows:
3-428
C.S0005-0-2 v1.0

3 station shall set this field to the actual Dedicated Control
4 Channel frame size(s) to be used in the service configuration.
6 the base station shall set this field to the Dedicated Control
7 Channel frame size for the proposed service configuration
8 message.
9
10 Table 3.7.5.7-3. DCCH Frame Size
DCCH_FRAME_SIZE
00 Reserved
11 Both 5 ms and 20 ms frame sizes
11
12 FOR_DCCH_RC - Forward Dedicated Control Channel Radio Configuration.

18 station shall set this field to the actual Forward Dedicated
19 Control Channel Radio Configuration to be used (see Table
20 3.1.3.1-1 of TIA/EIA/IS-2000-[2]).
22 the base station shall set this field to the Forward Dedicated
24 configuration.
25 REV_DCCH_RC - Reverse Dedicated Control Channel Radio Configuration.
31 station shall set this field to the actual Reverse Dedicated
32 Control Channel Radio Configuration to be used (see Table
33 2.1.3.1-1 of TIA/EIA-IS-2000-[2]).
35 the base station shall set this field to the reverse Dedicated
37 configuration.
3-429
C.S0005-0-2 v1.0
1 FOR_SCH-
2 _CC_INCL - Channel configuration for the Forward Suppemental
3 Channelincluded indicator.
4 The base station shall set this field to ‘1’, if the channel
5 configuration information for the forward Supplemental
6 Channel is included in this Service Configuration Record;
8 NUM_FOR_SCH - Number of Forward Supplemental Channels.
9 If the FOR_SCH_CC_INCL field is set to ‘0’, the base station
11 field to the number of Forward Supplemental Channels
12 associated with this service configuration.
13 If the NUM_FOR_SCH field is present and is set to any value other than ‘00’, the base
14 station shall include one occurrence of the following three field record for each Forward
15 Supplemental Channel included in this record:
16 FOR_SCH_ID - Forward Supplemental Channel Identification
21 FOR_SCH_MUX - Forward Supplemental Channel Multiplex Option.
22 The base station shall set this field to the Multiplex Option
23 associated with the maximum data rate for this Forward
24 Supplemental Channel (see 2.2.4.4.1.5 of TIA/EIA/IS-2000-
25 3)[3]).
26 SCH_CC_Type-specific field - Supplemental Channel Configuration Information.
27 The base station shall set this field as defined in 3.7.5.7.1 for
28 this Forward Supplemental Channel.
29 REV_SCH_CC_INCL - Channel configuration for the Reverse Supplemental Channel
31 The base station shall set this field to ‘1’ if the channel
32 configuration information for the reverse Supplemental
33 Channel is included in this service configuration record;
35 NUM_REV_SCH - Number of Reverse Supplemental Channels.
36 If the REV_SCH_CC_INCL field is set to ‘0’, the base station
38 field to the number of Reverse Supplemental Channels
39 associated with this service configuration.
40 If the NUM_REV_SCH field is present and is set to any value other than ‘00’, the base
41 station shall include one occurrence of the following three field record for each Reverse
42 Supplemental Channel included in this record:
43 REV_SCH_ID - Reverse Supplemental Channel Identification
3-430
C.S0005-0-2 v1.0
2 Reverse Supplemental Channel pertaining to this record.
5 REV_SCH_MUX - Reverse Supplemental Channel Multiplex Option
6 The base station shall set this field to the Multiplex Option
7 associated with the maximum data rate for this Reverse
8 Supplemental Channel (see 2.2.4.4.1.5 of TIA/EIA/IS-2000-
9 3)[3]).
10 SCH_CC_Type-specific field - Supplemental Channel Configuration Information.
11 The base station shall set this field as defined in 3.7.5.7.1 for
12 this Reverse Supplemental Channel.
15 make the length of the entire message equal to an integer
17
3-431
C.S0005-0-2 v1.0
1 3.7.5.7.1 Channel Configuration for the Supplemental Channel Type-specific Field
2 The channel configuration information for the Supplemental Channel Type-specific field
3 consists of the following subfields:
Subfields Length (bits)
SCH_REC_LEN 4
SCH_RC 5
CODING 1
RESERVED 6
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 in Table 3.1.3.1-1 of TIA/EIA/IS-
15 2000-[2] for the Forward Supplemental Channel and Table
16 2.1.3.1-1 of TIA/EIA/IS-2000-2 for the Reverse Supplemental
17 Channel.
18 CODING - Coding type.
19 The mobile station or base station shall set this field to ‘1’ if
20 the mobile station or the base station is to use Convolutional
21 Coding when the number of channel bits per frame is less
22 than 360 and Turbo Coding when the number of channel bits
23 per frame is equal to or greater than 360. The mobile station
24 or base station shall set this field to ‘0’ if the mobile station or
25 the base station uses Convolutional Coding for all block sizes.

28
29
3-432
C.S0005-0-2 v1.0
1 3.7.5.8 Called Party Subadddress
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 ANSI T1.607-1990, Section 4.5.8[8].
12 ODD/EVEN_INDICATOR - The indicator of odd/even bits.
22 each character in the called party subaddress.
26 8348 AD2.
32
3-433
C.S0005-0-2 v1.0
1 3.7.5.9 Calling Party Subadddress
2 This information record identifies the calling party subaddress.
EXTENSION_BIT 1
SUBADDRESS_TYPE 3
RESERVED 3
CHARi 8

11 ANSI T1.607-1990, Section 4.5.10[8].
12 ODD/EVEN INDICATOR - The indicator of odd/even bits.
22 each character in the calling party subaddress.
26 8348 AD2.
32
3-434
C.S0005-0-2 v1.0
1 3.7.5.10 Connected Subadddress
EXTENSION_BIT 1
SUBADDRESS_TYPE 3
RESERVED 3
CHARi 8

11 ANSI T1.607-1990, Section 4.5.14[8].
12 ODD/EVEN INDICATOR - The indicator of odd/even bits.
22 each character in the connected subaddress.
26 8348 AD2.
32
3-435
C.S0005-0-2 v1.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.
16 numbering plan used for the redirecting number, as defined in
17 ANSI T1.625 §6.1.3.7.
19 If the EXTENSION_BIT_1 is set to ‘0’ and
20 REDIRECTION_REASON is included in this record, the base
21 station shall set this field to ‘0’. If the EXTENSION_BIT_1 is
22 set to ‘0’ and REDIRECTION_REASON is not included in this
23 record, the base station shall set this field to ‘1’. If the
24 EXTENSION_BIT_1 is set to ‘1’, the base station shall omit
25 this field.
3-436
C.S0005-0-2 v1.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; otherwise, the base station shall omit
8 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; otherwise, the base station shall omit
19 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; otherwise, the base station
34
3-437
C.S0005-0-2 v1.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
9
3-438
C.S0005-0-2 v1.0
1 3.7.5.12 Redirecting Subadddress
EXTENSION_BIT 1
SUBADDRESS_TYPE 3
RESERVED 3
CHARi 8

11 ANSI T1.625 §6.1.3.8.
12 ODD/EVEN INDICATOR - The indicator of odd /even bits.
16 ANSI T1.625 §6.1.3.8. It is only used when the type of
17 subaddress is “User specified” and the coding is BCD.
22 each character in the redirecting subaddress.
26 8348 AD2.
32
3-439
C.S0005-0-2 v1.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.
23
3-440
C.S0005-0-2 v1.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
RESERVED 4
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-441
C.S0005-0-2 v1.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

20
3-442
C.S0005-0-2 v1.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.
28
3-443
C.S0005-0-2 v1.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 ANSI T1.610 Annex D[9].
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 ANSI T1.610 Annex D[9].
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 ANSI T1.610 Annex D[9].
23
24
3-444
C.S0005-0-2 v1.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
3-445
C.S0005-0-2 v1.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 ANSI T1.610 Annex D[9].
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 ANSI X3.4[12], with the
10 most significant bit set to ‘0’.
11
3-446
C.S0005-0-2 v1.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.
7
3-447
C.S0005-0-2 v1.0
1 3.7.5.18 Reserved
2
3-448
C.S0005-0-2 v1.0
1 3.7.5.19 Reserved
2
3-449
C.S0005-0-2 v1.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.
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
RESERVED 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
3-450
C.S0005-0-2 v1.0
2 FPC_INCL - Forward power control information included indicator.

3 The base station shall set this field to ‘1’ if the forward power
4 control information parameters are included in this record;
7 If the FPC_INCL field is set to ‘0’, the base station shall omit
8 this field; otherwise, the base station shall include this field
9 and set it as follows:
13 is to multiplex the Power Control Subchannel on Forward
14 Fundamental Channel; the base station shall set this field to
18 Control Subchannel on Forward Dedicated Control Channel.
19 If only Fundamental Channel is assigned, the base station
20 shall set this field to ‘0’. If only the Dedicated Control
21 Channel is assigned, the base station shall set this field to ‘1’.
22 FPC_MODE - Forward Power Control operation mode indicator.
26 The base station shall set this field to the value of the forward
27 power control operation mode as specified in Table 2.1.3.1.11-
28 1 of TIA/EIA/IS-2000-[2].
29 FPC_OLPC_FCH_INCL - Fundamental Channel Outer Loop Power Control parameter
34 If the forward link Fundamental Channel outer loop power
35 control parameters are included in this record, the base
38 FPC_FCH_FER - Fundamental Channel target Frame Error Rate.
41 the Forward Fundamental Channel, as specified in Table
43 field.
3-451
C.S0005-0-2 v1.0

2 station shall set this field to minimum Fundamental Channel
3 Outer Loop Eb/Nt setpoint, in units of 0.125dB; otherwise,
6 If FPC_OLPC_FCH_INCL is set to ‘1’, the base station shall set
7 this field to maximum Fundamental Channel Outer Loop
8 Eb/Nt setpoint, in units of 0.125dB; otherwise, the base
10 FPC_OLPC_DCCH_INCL - Dedicated Control Channel Outer Loop Power Control
11 parameter included indicator.
15 If the forward link Dedicated Control Channel outer loop
16 power control parameters are included in this message, the
22 the Forward Dedicated Control Channel, as specified in Table
24 field.
25 FPC_DCCH_MIN_SETPT - Minimum Dedicated Control Channel Outer Loop Eb/Nt
26 setpoint.
28 station shall set this field to minimum Dedicated Control
29 Channel Outer Loop Eb/Nt setpoint, in units of 0.125dB;
31 FPC_DCCH_MAX_SETPT - Maximum Dedicated Control Channel Outer Loop Eb/Nt
32 setpoint.
34 station shall set this field to maximum Dedicated Control
35 Channel Outer Loop Eb/Nt setpoint, in units of 0.125dB;
37 GATING_RATE_INCL- Reverse Pilot Channel Gating rate included flag.
39 PILOT_GATING_RATE field is included; otherwise, it shall set
41 PILOT_GATING_RATE - Reverse Pilot Channel Gating rate.
42 If the GATING_RATE_INCL field is set to ‘0’, the base station
44 field as follows: The base station shall set this field to the
45 PILOT_GATING_RATE field shown in Table 3.7.5.20-1
46 corresponding to the gating rate on the Reverse Pilot Channel.
3-452
C.S0005-0-2 v1.0
1 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

5 LPM_IND - Logical to Physical Mapping indicator.
6 The base station shall set this field to the LPM_IND field value
7 shown in Table 3.7.5.20-2 corresponding to the Logical to
8 Physical Mapping indicator.
9 Table 3.7.5.20-2. Logical to Physical Mapping indicator
LPM_IND Field (binary) Logical to Physical 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
10 NUM_LPM_ENTRIES - Number of Logical-to-Physical Mapping entries.

11 If the LPM_IND field is set to ‘01’, the base station shall
12 include this field and set is as follows; otherwise, the base
14 The base station shall set this field to the number of Logical-
15 to-Physical Mapping entries that are included in this record.
16 If the NUM_LPM_ENTRIES field is included and is not equal to ‘0000’, the base station shall
17 include NUM_LPM_ENTRIES occurrences of the following six-field record for each Logical-
18 to-Physical Mapping entry:
19 SR_ID - Service reference identifier.
21 service reference to which this Logical to Physical Mapping
22 entry applies.
3-453
C.S0005-0-2 v1.0
1 LOGICAL_RESOURCE - Logical resource identifier.

2 The base station shall set this field to the logical resource
3 identifier shown in Table 3.7.5.20-3 which is to be mapped by
4 this Logical to Physical Mapping entry.
5 Table 3.7.5.20-3. Logical Resource Identifier.
LOGICAL_RESOURCE Logical Resource

(binary)
0000 dtch
0001 dsch
6 PHYSICAL_RESOURCE - Physical resource identifier.

7 The base station shall set this field to the physical resource
8 identifier shown in Table 3.7.5.20-4 to which the logical
9 channel specified in this Logical to Physical Mapping entry is
10 to be mapped.
11 Table 3.7.5.20-4. Physical Resource Identifier.
PHYSICAL_RESOURCE Physical Resource
(binary)
0000 FCH
0001 DCCH
0010 SCH0
0011 SCH1

12
13 FORWARD_FLAG - Forward mapping indicator.

14 The base station shall set this field to ‘1’ if the logical to
15 physical channel mapping specified in this record applies to
16 forward logical channels; otherwise, the base station shall set
18 REVERSE_FLAG - Reverse mapping indicator.
19 The base station shall set this field to ‘1’ if the logical to
20 physical channel mapping specified in this record applies to
21 reverse logical channels; otherwise, the base station shall set
23 PRIORITY - Multiplexing priority.
3-454
C.S0005-0-2 v1.0

3-455
C.S0005-0-2 v1.0
1 ANNEX A RESERVED
2
A-1
C.S0005-0-2 v1.0
2 No text.
A-2
C.S0005-0-2 v1.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-27, the following message acronyms will apply:
10 ERRM: Extended Release Response Message
11 ERRMM: Extended Release Response Mini Message
12 RRM: Resource Request Message
13 RRMM: Resource Request Mini Message
14 RRRM: Resource Release Request Message
15 RRRMM: Resource Release Request Mini Message
16 SCRM: Supplemental Channel Request Message
17 SCRMM: Supplemental Channel Request Mini Message
18 ERM: Extended Release Message
19 ERMM: Extended Release Mini Message
20 RAM: Resource Allocation Message
21 RAMM: Resource Allocation Mini Message
22 UHDM: Universal Handoff Direction Message
23 ESCAM: Extended Supplemental Channel Assignment Message
24 FSCAMM: Forward Supplemental Channel Assignment Mini Message
25 RSCAMM: Reverse Supplemental Channel Assignment Mini Message
26 HCM: Handoff Complete Message
27
B-1
C.S0005-0-2 v1.0
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)
1 Figure B-1A. Simple Call Flow, Mobile Station Origination Example Using
2 Service Option Negotiation with Service Option 1
3
B-2
C.S0005-0-2 v1.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
C.S0005-0-2 v1.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
4
B-4
C.S0005-0-2 v1.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
4
B-5
C.S0005-0-2 v1.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
9
B-6
C.S0005-0-2 v1.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

3
B-7
C.S0005-0-2 v1.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
11
B-8
C.S0005-0-2 v1.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

3
B-9
C.S0005-0-2 v1.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)

3
B-10
C.S0005-0-2 v1.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)

3
B-11
C.S0005-0-2 v1.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)

3
B-12
C.S0005-0-2 v1.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
17
B-13
C.S0005-0-2 v1.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
3
B-14
C.S0005-0-2 v1.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
4
B-15
C.S0005-0-2 v1.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)
4
B-16
C.S0005-0-2 v1.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)
4
B-17
C.S0005-0-2 v1.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.
4
B-18
C.S0005-0-2 v1.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)
4
B-19
C.S0005-0-2 v1.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)
4
B-20
C.S0005-0-2 v1.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)
4
B-21
C.S0005-0-2 v1.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.
4
B-22
C.S0005-0-2 v1.0


on F1)

on F2) on F2)
4
B-23
C.S0005-0-2 v1.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.
2 Figure B-15. Call Flow for Inter-Frequency Handoff (Periodic Search Using General
3 Handoff Direction Message) (Part 1 of 4)
4
B-24
C.S0005-0-2 v1.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.
4
B-25
C.S0005-0-2 v1.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.
4
B-26
C.S0005-0-2 v1.0


on F1)

on F2) on F2)
4
B-27
C.S0005-0-2 v1.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)
4
B-28
C.S0005-0-2 v1.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
4
B-29
C.S0005-0-2 v1.0


Active Set. (Discontinues use of Active Set
on F3)

on F1) on F1)
.
.
on F2)
.
.
(Continues communication
on F1)
4
B-30
C.S0005-0-2 v1.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)
4
B-31
C.S0005-0-2 v1.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)
4
B-32
C.S0005-0-2 v1.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
2 Figure B-18. Simple Call Flow Mobile Station Origination Example with Transmission
3 on Forward Supplemental Code Channels (Part 1 of 2)
4
B-33
C.S0005-0-2 v1.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)
4
B-34
C.S0005-0-2 v1.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)
4
B-35
C.S0005-0-2 v1.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)
4
B-36
C.S0005-0-2 v1.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)
4
B-37
C.S0005-0-2 v1.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
4
B-38
C.S0005-0-2 v1.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.
4
B-39
C.S0005-0-2 v1.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)
4
B-40
C.S0005-0-2 v1.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
4
B-41
C.S0005-0-2 v1.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
4
B-42
C.S0005-0-2 v1.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
2
3
4 Figure B-22. Active/Control Hold to Idle State Transition (BS Initiated)
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
6
7
8 Figure B-23. Active/Control Hold to Idle State Transition (MS Initiated)
10
B-43
C.S0005-0-2 v1.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 Mode Transition (BS Initiated)
MS L3 BS L3
Active Active
RRRM /
RRRMM
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
6 Figure B-25. Active to Control Hold Mode Transition (MS Initiated)

7
B-44
C.S0005-0-2 v1.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
4 Figure B-26. Control Hold to Active Mode Transition (BS Initiated)

5
B-45
C.S0005-0-2 v1.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
3 Figure B-27. Control Hold to Active Mode Transition (MS Initiated)
B-46
C.S0005-0-2 v1.0
1 ANNEX C RESERVED
2
C-1
C.S0005-0-2 v1.0
2 No text.
3
C-2
C.S0005-0-2 v1.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 4)
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 3s 2.6.2.1.1.1
message
T31m Maximum time for which configuration parameters 600 s 2.6.2.2

are considered valid
11
12
D-1
C.S0005-0-2 v1.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 Maximum time to enter the Update Overhead 3s 2.6.3.3
Information Substate or the Mobile Station Idle State
after receiving a Channel Assignment Message with
ASSIGN_MODEr equal to ‘001’ or ‘101’
T40m Maximum time to receive a valid Paging Channel 3s 2.6.3.1.8
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
T42m Maximum time to receive a delayed layer 3 response 12 s 2.6.3.1.1.2
following the receipt of an acknowledgment for an 2.6.3.3
access probe 2.6.3.5
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
T52m Maximum time to receive a message in the Waiting 5s 2.6.4.3.1
for Order Substate of the Mobile Station Control on
the Traffic Channel State that transits the mobile
station to a different substate or state
D-2
C.S0005-0-2 v1.0
Time
Limit
T53m Maximum time to receive a message in the Waiting 65 s 2.6.4.3.2
for Mobile Station Answer Substate of the Mobile
Station Control on the Traffic Channel State that
transits the mobile station to a different substate or
state
T54m Maximum time for the mobile station to send an 0.2 s 2.6.4.4
Origination Continuation Message upon entering the
Conversation Substate of the Mobile Station Control
on the Traffic Channel State
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
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
D-3
C.S0005-0-2 v1.0
Time
Limit
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 1s 2.6.3.1.8
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.3 s 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.0 s 2.6.4.2
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-4
C.S0005-0-2 v1.0
1 Table D-2. Other Constants
Con-
stant Description Value References
N2m Number of received consecutive bad Forward Traffic 12 2.6.4.1.8

Channel frames before a mobile station must
disable its transmitter
N3m Number of received consecutive good Forward 2
Traffic Channel frames before a mobile station is 2.6.4.1.8
allowed to re-enable its transmitter after disabling
its transmitter
N4m Reserved
N5m Number of received consecutive good Forward 2 2.6.4.2
Traffic Channel frames 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
frames), in units of 20 ms, received on the Forward
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
2
D-5
C.S0005-0-2 v1.0
1 No text.
D-6
C.S0005-0-2 v1.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.
8
E-1
C.S0005-0-2 v1.0
Table E-1. Retrievable and Settable Parameters (Part 1 of 10)
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 IS-2000-3
MUX1_REV_FCH_2 2 24 Y Y IS-2000-3
MUX1_REV_FCH_3 3 24 Y Y IS-2000-3
MUX1_REV_FCH_4 4 24 Y Y IS-2000-3
MUX1_REV_FCH_5 5 24 Y Y IS-2000-3
MUX1_REV_FCH_6 6 24 Y Y IS-2000-3
MUX1_REV_FCH_7 7 24 Y Y IS-2000-3
MUX1_REV_FCH_8 8 24 Y Y IS-2000-3
MUX1_REV_FCH_9 9 N/A N/A N/A IS-2000-3
MUX1_REV_FCH_11 11 24 N Y IS-2000-3
MUX1_REV_FCH_12 12 24 N Y IS-2000-3
MUX1_REV_FCH_13 13 24 N Y IS-2000-3
MUX1_REV_FCH_14 14 24 N Y IS-2000-3
MUX1_FOR_FCH_1 15 24 Y Y IS-2000-3
MUX1_FOR_FCH_2 16 24 Y Y IS-2000-3
MUX1_FOR_FCH_3 17 24 Y Y IS-2000-3
MUX1_FOR_FCH_4 18 24 Y Y IS-2000-3
MUX1_FOR_FCH_5 19 24 Y Y IS-2000-3
MUX1_FOR_FCH_6 20 24 Y Y IS-2000-3
MUX1_FOR_FCH_7 21 24 Y Y IS-2000-3
MUX1_FOR_FCH_8 22 24 Y Y IS-2000-3
2
E-2
C.S0005-0-2 v1.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 IS-2000-3
MUX1_FOR_FCH_10 24 24 Y Y IS-2000-3
MUX1_FOR_FCH_11 25 24 N Y IS-2000-3
MUX1_FOR_FCH_12 26 24 N Y IS-2000-3
MUX1_FOR_FCH_13 27 24 N Y IS-2000-3
MUX1_FOR_FCH_14 28 24 N Y IS-2000-3
PAG_1 29 24 Y Y IS-2000-4
PAG_2 30 24 Y Y IS-2000-4
PAG_3 31 16 Y Y IS-2000-4
PAG_4 32 24 Y Y IS-2000-4
PAG_5 33 24 Y Y IS-2000-4
PAG_6 34 16 Y Y IS-2000-4
PAG_7 35 16 Y Y IS-2000-4
ACC_1 36 16 Y Y IS-2000-4
ACC_2 37 16 Y Y IS-2000-4
ACC_3 38 16 Y Y IS-2000-4
ACC_4 39 16 Y Y IS-2000-4
ACC_5 40 16 Y Y IS-2000-4
ACC_6 41 16 Y Y IS-2000-4
ACC_7 42 16 Y Y IS-2000-4
ACC_8 43 16 Y Y IS-2000-4
LAYER2_RTC1 44 16 Y Y IS-2000-4
LAYER2_RTC2 45 16 Y Y IS-2000-4
LAYER2_RTC3 46 16 Y Y IS-2000-4
LAYER2_RTC4 47 16 Y Y IS-2000-4
LAYER2_RTC5 48 16 Y Y IS-2000-4
OTHER_SYS_TIME 49 36 Y N 2.4
E-3
C.S0005-0-2 v1.0

Reference
Section
MUX2_REV_FCH_1 50 24 Y Y IS-2000-3
MUX2_REV_FCH_2 51 24 Y Y IS-2000-3
MUX2_REV_FCH_3 52 24 Y Y IS-2000-3
MUX2_REV_FCH_4 53 24 Y Y IS-2000-3
MUX2_REV_FCH_5 54 24 Y Y IS-2000-3
MUX2_REV_FCH_6 55 24 Y Y IS-2000-3
MUX2_REV_FCH_7 56 24 Y Y IS-2000-3
MUX2_REV_FCH_8 57 24 Y Y IS-2000-3
MUX2_REV_FCH_9 58 24 Y Y IS-2000-3
MUX2_REV_FCH_10 59 24 Y Y IS-2000-3
MUX2_REV_FCH_11 60 24 Y Y IS-2000-3
MUX2_REV_FCH_12 61 24 Y Y IS-2000-3
MUX2_REV_FCH_13 62 24 Y Y IS-2000-3
MUX2_REV_FCH_14 63 24 Y Y IS-2000-3
MUX2_REV_FCH_15 64 24 Y Y IS-2000-3
MUX2_REV_FCH_16 65 24 Y Y IS-2000-3
MUX2_REV_FCH_17 66 24 Y Y IS-2000-3
MUX2_REV_FCH_18 67 24 Y Y IS-2000-3
MUX2_REV_FCH_19 68 24 Y Y IS-2000-3
MUX2_REV_FCH_20 69 24 Y Y IS-2000-3
MUX2_REV_FCH_21 70 24 Y Y IS-2000-3
MUX2_REV_FCH_22 71 24 Y Y IS-2000-3
MUX2_REV_FCH_23 72 24 Y Y IS-2000-3
MUX2_REV_FCH_24 73 24 Y Y IS-2000-3
MUX2_REV_FCH_25 74 24 Y Y IS-2000-3
E-4
C.S0005-0-2 v1.0

Reference
Section
MUX2_FOR_FCH_1 76 24 Y Y IS-2000-3
MUX2_FOR_FCH_2 77 24 Y Y IS-2000-3
MUX2_FOR_FCH_3 78 24 Y Y IS-2000-3
MUX2_FOR_FCH_4 79 24 Y Y IS-2000-3
MUX2_FOR_FCH_5 80 24 Y Y IS-2000-3
MUX2_FOR_FCH_6 81 24 Y Y IS-2000-3
MUX2_FOR_FCH_7 82 24 Y Y IS-2000-3
MUX2_FOR_FCH_8 83 24 Y Y IS-2000-3
MUX2_FOR_FCH_9 84 24 Y Y IS-2000-3
MUX2_FOR_FCH_10 85 24 Y Y IS-2000-3
MUX2_FOR_FCH_11 86 24 Y Y IS-2000-3
MUX2_FOR_FCH_12 87 24 Y Y IS-2000-3
MUX2_FOR_FCH_13 88 24 Y Y IS-2000-3
MUX2_FOR_FCH_14 89 24 Y Y IS-2000-3
MUX2_FOR_FCH_15 90 24 Y Y IS-2000-3
MUX2_FOR_FCH_16 91 24 Y Y IS-2000-3
MUX2_FOR_FCH_17 92 24 Y Y IS-2000-3
MUX2_FOR_FCH_18 93 24 Y Y IS-2000-3
MUX2_FOR_FCH_19 94 24 Y Y IS-2000-3
MUX2_FOR_FCH_20 95 24 Y Y IS-2000-3
MUX2_FOR_FCH_21 96 24 Y Y IS-2000-3
MUX2_FOR_FCH_22 97 24 Y Y IS-2000-3
MUX2_FOR_FCH_23 98 24 Y Y IS-2000-3
MUX2_FOR_FCH_24 99 24 Y Y IS-2000-3
MUX2_FOR_FCH_25 100 24 Y Y IS-2000-3
MUX2_FOR_FCH_26 101 24 Y Y IS-2000-3
E-5
C.S0005-0-2 v1.0

Reference
Section
SCCH1_REV_S 102 24 Y Y IS-2000-3

SCCH1_REV_P 103 24 Y Y IS-2000-3
SCCH2_REV_S 104 24 Y Y IS-2000-3
SCCH2_REV_P 105 24 Y Y IS-2000-3
SCCH3_REV_S 106 24 Y Y IS-2000-3
SCCH3_REV_P 107 24 Y Y IS-2000-3
SCCH4_REV_S 108 24 Y Y IS-2000-3
SCCH4_REV_P 109 24 Y Y IS-2000-3
SCCH5_REV_S 110 24 Y Y IS-2000-3
SCCH5_REV_P 111 24 Y Y IS-2000-3
SCCH6_REV_S 112 24 Y Y IS-2000-3
SCCH6_REV_P 113 24 Y Y IS-2000-3
SCCH7_REV_S 114 24 Y Y IS-2000-3
SCCH7_REV_P 115 24 Y Y IS-2000-3
SCCH1_FOR_S 116 24 Y Y IS-2000-3
SCCH1_FOR_P 117 24 Y Y IS-2000-3
SCCH2_FOR_S 118 24 Y Y IS-2000-3
SCCH2_FOR_P 119 24 Y Y IS-2000-3
SCCH3_FOR_S 120 24 Y Y IS-2000-3
SCCH3_FOR_P 121 24 Y Y IS-2000-3
SCCH4_FOR_S 122 24 Y Y IS-2000-3
SCCH4_FOR_P 123 24 Y Y IS-2000-3
SCCH5_FOR_S 124 24 Y Y IS-2000-3
SCCH5_FOR_P 125 24 Y Y IS-2000-3
SCCH6_FOR_S 126 24 Y Y IS-2000-3
SCCH6_FOR_P 127 24 Y Y IS-2000-3
SCCH7_FOR_S 128 24 Y Y IS-2000-3
SCCH7_FOR_P 129 24 Y Y IS-2000-3
E-6
C.S0005-0-2 v1.0

Reference
Section
MM_RTC1 130 16 Y Y IS-2000-4

2.2.1.1.4
MM_RTC2 131 16 Y Y IS-2000-4
2.2.1.1.4
MM_RTC3 132 16 Y Y IS-2000-4
2.2.1.1.4
MM_RTC4 133 16 Y Y IS-2000-4
2.2.1.1.4
MM_RTC5 134 16 Y Y IS-2000-4
2.2.1.1.4
MUX1_REV_FCH_5_ms 136 24 N Y IS-2000-3
MUX1_FOR_FCH_15 137 N/A N/A N/A IS-2000-3
MUX1_FOR_FCH_5_ms 138 24 N Y IS-2000-3
MUX2_REV_FCH_5_ms 140 24 N Y IS-2000-3
MUX2_FOR_FCH_27 141 N/A N/A N/A IS-2000-3
MUX2_FOR_FCH_5_ms 142 24 N Y IS-2000-3
MUX1_REV_DCCH_1 143 24 Y Y IS-2000-3
MUX1_REV_DCCH_2 144 24 Y Y IS-2000-3
MUX1_REV_DCCH_3 145 24 Y Y IS-2000-3
MUX1_REV_DCCH_4 146 24 Y Y IS-2000-3
MUX1_REV_DCCH_5 147 24 Y Y IS-2000-3
MUX1_REV_DCCH_6 148 N/A N/A N/A IS-2000-3
MUX1_REV_DCCH_11 153 24 N Y IS-2000-3
MUX1_REV_DCCH_12 154 24 N Y IS-2000-3
1
E-7
C.S0005-0-2 v1.0

Reference
Section
MUX1_REV_DCCH_13 155 24 N Y IS-2000-3

MUX1_REV_DCCH_14 156 24 N Y IS-2000-3
MUX1_REV_DCCH_15 157 24 Y Y IS-2000-3
MUX1_REV_DCCH_5_ms 158 24 N Y IS-2000-3
MUX1_FOR_DCCH_1 159 24 Y Y IS-2000-3
MUX1_FOR_DCCH_2 160 24 Y Y IS-2000-3
MUX1_FOR_DCCH_3 161 24 Y Y IS-2000-3
MUX1_FOR_DCCH_4 162 24 Y Y IS-2000-3
MUX1_FOR_DCCH_5 163 24 Y Y IS-2000-3
MUX1_FOR_DCCH_6 164 N/A N/A N/A IS-2000-3
MUX1_FOR_DCCH_10 168 24 Y Y IS-2000-3
MUX1_FOR_DCCH_11 169 24 N Y IS-2000-3
MUX1_FOR_DCCH_12 170 24 N Y IS-2000-3
MUX1_FOR_DCCH_13 171 24 N Y IS-2000-3
MUX1_FOR_DCCH_14 172 24 N Y IS-2000-3
MUX1_FOR_DCCH_15 173 24 Y Y IS-2000-3
MUX1_FOR_DCCH_5_ms 174 24 N Y IS-2000-3
MUX2_REV_DCCH_1 175 24 Y Y IS-2000-3
MUX2_REV_DCCH_2 176 24 Y Y IS-2000-3
MUX2_REV_DCCH_3 177 24 Y Y IS-2000-3
MUX2_REV_DCCH_4 178 24 Y Y IS-2000-3
MUX2_REV_DCCH_5 179 24 Y Y IS-2000-3
MUX2_REV_DCCH_6 180 24 Y Y IS-2000-3
MUX2_REV_DCCH_7 181 24 Y Y IS-2000-3
E-8
C.S0005-0-2 v1.0

Reference
Section
MUX2_REV_DCCH_8 182 24 Y Y IS-2000-3

MUX2_REV_DCCH_9 183 24 Y Y IS-2000-3
MUX2_REV_DCCH_10 184 24 Y Y IS-2000-3
MUX2_REV_DCCH_27 201 24 Y Y IS-2000-3
MUX2_REV_DCCH_5_ms 202 24 N Y IS-2000-3
MUX2_FOR_DCCH_1 203 24 Y Y IS-2000-3
MUX2_FOR_DCCH_2 204 24 Y Y IS-2000-3
MUX2_FOR_DCCH_3 205 24 Y Y IS-2000-3
MUX2_FOR_DCCH_4 206 24 Y Y IS-2000-3
MUX2_FOR_DCCH_5 207 24 Y Y IS-2000-3
MUX2_FOR_DCCH_6 208 24 Y Y IS-2000-3
MUX2_FOR_DCCH_7 209 24 Y Y IS-2000-3
MUX2_FOR_DCCH_8 210 24 Y Y IS-2000-3
MUX2_FOR_DCCH_9 211 24 Y Y IS-2000-3
E-9
C.S0005-0-2 v1.0

Reference
Section
MUX2_FOR_DCCH_10 212 24 Y Y IS-2000-3

MUX2_FOR_DCCH_26 228 24 Y Y IS-2000-3
MUX2_FOR_DCCH_27 229 24 Y Y IS-2000-3
MUX2_FOR_DCCH_5_ms 230 24 N Y IS-2000-3
SCH0_REV_1X 231 24 Y Y IS-2000-3
SCH0_REV_2X 232 24 Y Y IS-2000-3
SCH0_REV_4X 233 24 Y Y IS-2000-3
SCH0_REV_8X 234 24 Y Y IS-2000-3
SCH0_REV_16X 235 24 Y Y IS-2000-3
SCH0_REV_LTU 236 24 Y Y IS-2000-3
SCH0_REV_LTUOK 237 N/A N/A N/A IS-2000-3
SCH1_REV_1X 238 24 Y Y IS-2000-3
SCH1_REV_2X 239 24 Y Y IS-2000-3
2
E-10
C.S0005-0-2 v1.0

Reference
Section
SCH1_REV_4X 240 24 Y Y IS-2000-3

SCH1_REV_8X 241 24 Y Y IS-2000-3
SCH1_REV_16X 242 24 Y Y IS-2000-3
SCH1_REV_LTU 243 24 Y Y IS-2000-3
SCH1_REV_LTUOK 244 N/A N/A N/A IS-2000-3
SCH0_FOR_1X 245 24 Y Y IS-2000-3
SCH0_FOR_2X 246 24 Y Y IS-2000-3
SCH0_FOR_4X 247 24 Y Y IS-2000-3
SCH0_FOR_8X 248 24 Y Y IS-2000-3
SCH0_FOR_16X 249 24 Y Y IS-2000-3
SCH0_FOR_LTU 250 24 Y Y IS-2000-3
SCH0_FOR_LTUOK 251 24 Y Y IS-2000-3
SCH1_FOR_1X 252 24 Y Y IS-2000-3
SCH1_FOR_2X 253 24 Y Y IS-2000-3
SCH1_FOR_4X 254 24 Y Y IS-2000-3
SCH1_FOR_8X 255 24 Y Y IS-2000-3
SCH1_FOR_16X 256 24 Y Y IS-2000-3
SCH1_FOR_LTU 257 24 Y Y IS-2000-3
SCH1_FOR_LTUOK 258 24 Y Y IS-2000-3
E-11
C.S0005-0-2 v1.0
1 No text.
E-12
C.S0005-0-2 v1.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.
15
F-1
C.S0005-0-2 v1.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
10
F-2
C.S0005-0-2 v1.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
C.S0005-0-2 v1.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
6
F-4
C.S0005-0-2 v1.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
C.S0005-0-2 v1.0
1 No text
F-6

C.S0005 0 2

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

C.S0005 0 2

Hochgeladen von

Copyright:

Verfügbare Formate

3GPP2 C.

Date: April 24, 2001

2 Upper Layer (Layer 3) Signaling Standard for

1 1. GENERAL ............................................................................................................. 1-1

2 1.1 Terms and Numeric Information ........................................................................... 1-1

3 1.1.1 Terms ............................................................................................................. 1-1

4 1.1.2 Numeric Information ..................................................................................... 1-21

5 1.1.2.1 Reserved ................................................................................................. 1-22

6 1.1.2.2 CDMA Numeric Information..................................................................... 1-22

7 1.2 Signaling Architecture ........................................................................................ 1-40

8 1.3 Signaling and Functionality ................................................................................ 1-40

9 1.3.1 Control Plane and Data Plane ........................................................................ 1-40

10 1.3.2 Interface to Layer 2 ....................................................................................... 1-41

11 1.3.2.1 Message Control and Status Block (MCSB)............................................... 1-41

12 1.3.2.2 Interface Primitives.................................................................................. 1-42

13 1.3.3. Reserved ..................................................................................................... 1-44

14 1.3.4. Functional Description ................................................................................ 1-44

15 1.3.5. PDU Transmission and Reception ................................................................ 1-44

16 2. REQUIREMENTS FOR MOBILE STATION CDMA OPERATION ................................ 2-1

17 2.1 Reserved .............................................................................................................. 2-1

18 2.2 Reserved .............................................................................................................. 2-1

19 2.3 Security and Identification .................................................................................... 2-1

20 2.3.1 Mobile Station Identification Number............................................................... 2-1

21 2.3.1.1 Encoding of IMSI_M_S and IMSI_T_S ......................................................... 2-3

22 2.3.1.2 Encoding of IMSI_M_11_12 and IMSI_T_11_12 ........................................... 2-5

23 2.3.1.3 Encoding of the MCC_M and MCC_T .......................................................... 2-5

24 2.3.1.4 Mobile Directory Number ........................................................................... 2-5

25 2.3.2 Electronic Serial Number................................................................................. 2-5

26 2.3.3 Station Class Mark.......................................................................................... 2-6

27 2.3.4 Registration Memory ....................................................................................... 2-6

28 2.3.5 Access Overload Class ..................................................................................... 2-7

29 2.3.6 Reserved ......................................................................................................... 2-8

30 2.3.7 Reserved ......................................................................................................... 2-8

31 2.3.8 Home System and Network Identification......................................................... 2-8

1 2.3.9 Local Control Option........................................................................................ 2-9

2 2.3.10 Preferred Operation Selection......................................................................... 2-9

3 2.3.10.1 Preferred System...................................................................................... 2-9

4 2.3.10.2 Preferred CDMA or Analog........................................................................ 2-9

5 2.3.11 Discontinuous Reception ............................................................................... 2-9

6 2.3.12 Authentication, Encryption of Signaling Information/User Data and Voice

8 2.3.12.1 Authentication ......................................................................................... 2-9

9 2.3.12.1.1 Shared Secret Data (SSD) ................................................................. 2-10

10 2.3.12.1.2 Random Challenge Memory (RAND) .................................................. 2-10

12 2.3.12.1.4 Unique Challenge-Response Procedure ............................................. 2-10

13 2.3.12.1.5 Updating the Shared Secret Data (SSD) ............................................ 2-11

14 2.3.12.2 Signaling Message Encryption ................................................................ 2-15

15 2.3.12.2.1 Encrypted Messages on the f-dsch .................................................... 2-16

16 2.3.12.2.2 Encrypted Messages on the r-dsch.................................................... 2-18

17 2.3.12.3 Voice Privacy ......................................................................................... 2-21

18 2.3.13 Lock and Maintenance Required Orders ....................................................... 2-21

19 2.3.14 Mobile Station Revision Identification........................................................... 2-22

20 2.3.15 Temporary Mobile Station Identity................................................................ 2-22

21 2.3.15.1 Overview................................................................................................ 2-22

22 2.3.15.2 TMSI Assignment Memory...................................................................... 2-23

23 2.4 Accumulated Statistics........................................................................................ 2-24

24 2.4.1 Monitored Quantities and Statistics.................................................................. 2-24

25 2.4.2 Accumulated Paging Channel Statistics.......................................................... 2-24

26 2.5 Reserved ............................................................................................................. 2-25

27 2.6 Call Processing.................................................................................................... 2-27

28 2.6.1 Mobile Station Initialization State .................................................................. 2-29

29 2.6.1.1 System Determination Substate ............................................................... 2-31

30 2.6.1.1.1 Custom System Selection Process ....................................................... 2-36