C.S0024-B v2.0 070624

3GPP2 C.
S0024-B
Version 2.0
Date: March 2007
cdma2000 High Rate Packet Data Air Interface

Specification
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.
NOTE: This is a replacement version of C.S0024-B Version 2.0. This version fixes a
problem in Table 12.4.1.3.2.3.5.4-1, 64-QAM Modulation Table, where the top 16 rows and
column headings were missing. The corresponding figure, Figure 12.4.1.3.2.3.5.4-1, Signal
Constellation for 64-QAM Modulation, correctly showed the signal constellation. While
fixing this table a few minor formatting issues were also corrected in the document.
No text.
3GPP2 C.S0024-B v2.0
CONTENTS
1 FOREWORD................................................................................................................... ciii
2 NOTES ............................................................................................................................civ
3 REFERENCES .................................................................................................................civ
4 1 Overview .....................................................................................................................1-1
5 1.1 Scope of This Document ........................................................................................1-1
6 1.2 Requirements Language ........................................................................................1-1
7 1.3 Architecture Reference Model ................................................................................1-1
8 1.4 Protocol Architecture .............................................................................................1-2
9 1.4.1 Layers..............................................................................................................1-2
10 1.5 Physical Layer Channels........................................................................................1-3
11 1.6 Protocols ...............................................................................................................1-4
12 1.6.1 Interfaces ........................................................................................................1-4
13 1.6.2 States ..............................................................................................................1-5
14 1.6.3 InUse and InConfiguration Protocol/Application Instances ..............................1-6
15 1.6.3.1 InConfiguration Instantiation.....................................................................1-6
16 1.6.3.1.1 Protocol Instantiation...........................................................................1-6
17 1.6.3.1.2 Application Instantiation......................................................................1-6
18 1.6.3.2 Protocol Initialization .................................................................................1-6
19 1.6.3.3 Procedures and Messages ..........................................................................1-7
20 1.6.3.3.1 Commit Procedures..............................................................................1-7
21 1.6.4 Common Commands .......................................................................................1-7
22 1.6.5 Protocol Negotiation.........................................................................................1-7
23 1.6.6 Protocol Overview ............................................................................................1-8
24 1.7 Default Applications ............................................................................................1-12
25 1.8 Streams...............................................................................................................1-13
26 1.9 Sessions and Connections ...................................................................................1-13
27 1.10 Security.............................................................................................................1-13
28 1.11 Terms ................................................................................................................1-13
29 1.12 Notation ............................................................................................................1-17
30 1.13 Malfunction Detection .......................................................................................1-19
31 1.14 CDMA System Time ...........................................................................................1-19
32 1.15 Revision Number ...............................................................................................1-21
i
3GPP2 C.S0024-B v2.0
CONTENTS
1 2 Default Signaling Application ...................................................................................... 2-1

2 2.1 Introduction .......................................................................................................... 2-1
3 2.1.1 General Overview ............................................................................................ 2-1
4 2.1.2 Public Data ..................................................................................................... 2-1
5 2.1.3 Data Encapsulation for the InUse Instance of the Signaling Application .......... 2-1
6 2.2 Protocol Initialization ............................................................................................ 2-3
7 2.2.1 Protocol Initialization for the InConfiguration Application Instance.................. 2-3
8 2.2.2 Protocol Initialization for the InUse Application Instance ................................. 2-3
9 2.3 General Signaling Requirements ........................................................................... 2-3
10 2.3.1 General Requirements ..................................................................................... 2-3
11 2.3.2 Message Information ....................................................................................... 2-4
12 2.4 Procedures and Messages for the InConfiguration Instance of the Signaling
13 Application ............................................................................................................ 2-5
14 2.4.1 Procedures ...................................................................................................... 2-5
15 2.4.2 Commit Procedures ......................................................................................... 2-5
16 2.4.3 Message Formats ............................................................................................ 2-6
17 2.4.3.1 ConfigurationRequest ................................................................................ 2-6
18 2.4.3.2 ConfigurationResponse.............................................................................. 2-6
19 2.5 Signaling Network Protocol.................................................................................... 2-7
20 2.5.1 Overview ......................................................................................................... 2-7
21 2.5.2 Primitives and Public Data .............................................................................. 2-7
22 2.5.2.1 Commands ................................................................................................ 2-7
23 2.5.2.2 Return Indications..................................................................................... 2-7
24 2.5.3 Protocol Data Unit ........................................................................................... 2-7
25 2.5.4 Procedures and Messages for the InUse Instance of the Protocol ..................... 2-8
26 2.5.4.1 Procedures ................................................................................................ 2-8
27 2.5.4.2 Type Definitions......................................................................................... 2-8
28 2.5.4.3 Messages ................................................................................................... 2-9
29 2.5.4.4 SNP Header ............................................................................................. 2-10
30 2.5.4.5 Interface to Other Protocols ..................................................................... 2-10
31 2.5.4.5.1 Commands ........................................................................................ 2-10
32 2.5.4.5.2 Indications......................................................................................... 2-10
ii
3GPP2 C.S0024-B v2.0
CONTENTS
1 2.6 Signaling Link Protocol ........................................................................................2-12

2 2.6.1 Overview........................................................................................................2-12
3 2.6.2 Primitives and Public Data.............................................................................2-12
4 2.6.2.1 Commands ..............................................................................................2-12
5 2.6.2.2 Return Indications ...................................................................................2-12
6 2.6.3 Protocol Data Unit .........................................................................................2-12
7 2.6.4 Procedures ....................................................................................................2-12
8 2.6.4.1 Reset .......................................................................................................2-12
9 2.6.4.2 Delivery Layer Procedures........................................................................2-13
10 2.6.4.2.1 General Procedures............................................................................2-13
11 2.6.4.2.1.1 Transmitter Requirements............................................................2-13
12 2.6.4.2.1.2 Receiver Requirements .................................................................2-13
13 2.6.4.2.2 Best Effort Delivery Procedures ..........................................................2-13
14 2.6.4.2.2.1 Transmitter Requirements............................................................2-13
15 2.6.4.2.2.2 Receiver Requirements .................................................................2-13
16 2.6.4.2.3 Reliable Delivery Procedures ..............................................................2-13
17 2.6.4.2.3.1 Overview ......................................................................................2-13
18 2.6.4.2.3.2 Initialization .................................................................................2-14
19 2.6.4.2.3.3 Data Transfer ...............................................................................2-14
20 2.6.4.2.3.3.1 Transmit Procedures ..............................................................2-14
21 2.6.4.2.3.3.2 Receive Procedures.................................................................2-15
22 2.6.4.3 Fragmentation Layer Procedures..............................................................2-16
23 2.6.4.3.1 Overview ............................................................................................2-16
24 2.6.4.3.2 Initialization.......................................................................................2-16
25 2.6.4.3.3 Data Transfer.....................................................................................2-17
26 2.6.4.3.4 Sender Requirements .........................................................................2-17
27 2.6.4.3.5 Receiver Requirements.......................................................................2-17
28 2.6.5 Header Formats .............................................................................................2-18
29 2.6.5.1 SLP-F Header...........................................................................................2-18
30 2.6.5.2 SLP-D Header ..........................................................................................2-19
31 2.6.6 Message Formats ...........................................................................................2-20
32 2.6.6.1 Reset .......................................................................................................2-20
iii
3GPP2 C.S0024-B v2.0
CONTENTS
1 2.6.6.2 ResetAck ................................................................................................. 2-20

2 2.6.6.3 Protocol Numeric Constants .................................................................... 2-21
3 2.6.7 Interface to Other Protocols ........................................................................... 2-21
4 2.6.7.1 Commands .............................................................................................. 2-21
5 2.6.7.2 Indications .............................................................................................. 2-21
6 2.7 Configuration Attributes for the Default Signaling Application ............................ 2-21
7 2.8 Session State Information ................................................................................... 2-22
8 3 Default Packet Application .......................................................................................... 3-1
9 3.1 Introduction .......................................................................................................... 3-1
11 3.1.2 Public Data ..................................................................................................... 3-1
12 3.1.3 Data Encapsulation for the InUse Instance of the Application ......................... 3-1
13 3.2 Protocol Initialization ............................................................................................ 3-2
14 3.2.1 Protocol Initialization for the InConfiguration Application Instance.................. 3-2
15 3.3 Procedures and Messages for the InConfiguration Instance of the Packet
16 Application ............................................................................................................ 3-2
17 3.3.1 Procedures ...................................................................................................... 3-2
18 3.3.2 Commit Procedures ......................................................................................... 3-3
19 3.3.3 Message Formats ............................................................................................ 3-3
20 3.3.3.1 ConfigurationRequest ................................................................................ 3-3
21 3.3.3.2 ConfigurationResponse.............................................................................. 3-4
22 3.4 Radio Link Protocol ............................................................................................... 3-5
23 3.4.1 Overview ......................................................................................................... 3-5
25 3.4.2.1 Commands ................................................................................................ 3-5
29 3.4.4.1 Procedures ................................................................................................ 3-5
30 3.4.4.1.1 Initialization and Reset ........................................................................ 3-5
31 3.4.4.1.1.1 Initialization Procedure .................................................................. 3-6
32 3.4.4.1.1.2 Reset Procedure ............................................................................. 3-6
iv
3GPP2 C.S0024-B v2.0
CONTENTS
1 3.4.4.1.1.2.1 Reset Procedure for the Initiating Side ......................................3-6

2 3.4.4.1.1.2.2 Reset Procedure for the Responding Side..................................3-6
3 3.4.4.1.2 Data Transfer.......................................................................................3-7
4 3.4.4.1.2.1 RLP Transmit Procedures ...............................................................3-7
5 3.4.4.1.2.2 RLP Receive Procedures .................................................................3-8
6 3.4.4.2 RLP Packet Header ....................................................................................3-9
7 3.4.4.3 Message Formats .......................................................................................3-9
8 3.4.4.3.1 Reset....................................................................................................3-9
9 3.4.4.3.2 ResetAck ..............................................................................................3-9
10 3.4.4.3.3 Nak ....................................................................................................3-10
11 3.4.4.4 Interface to Other Protocols .....................................................................3-11
12 3.4.4.4.1 Commands.........................................................................................3-11
13 3.4.4.4.2 Indications .........................................................................................3-11
14 3.4.4.5 RLP Packet Priorities................................................................................3-11
15 3.4.5 Protocol Numeric Constants ..........................................................................3-11
16 3.5 Location Update Protocol .....................................................................................3-12
17 3.5.1 Overview........................................................................................................3-12
19 3.5.2.1 Commands ..............................................................................................3-12
22 3.5.4 Procedures and Messages for the InUse Instance of the Protocol....................3-12
23 3.5.4.1 Procedures...............................................................................................3-12
24 3.5.4.1.1 Access Network Requirements............................................................3-12
25 3.5.4.1.2 Access Terminal Requirements...........................................................3-12
26 3.5.4.2 Message Formats .....................................................................................3-13
27 3.5.4.2.1 LocationRequest.................................................................................3-13
28 3.5.4.2.2 LocationNotification ...........................................................................3-13
29 3.5.4.2.3 LocationAssignment ...........................................................................3-14
30 3.5.4.2.4 LocationComplete ..............................................................................3-15
32 3.5.4.3.1 Commands.........................................................................................3-15
v
3GPP2 C.S0024-B v2.0
CONTENTS
1 3.5.4.3.2 Indications......................................................................................... 3-15

2 3.6 Flow Control Protocol .......................................................................................... 3-16
3 3.6.1 Overview ....................................................................................................... 3-16
4 3.6.2 Primitives and Public Data ............................................................................ 3-16
5 3.6.2.1 Commands .............................................................................................. 3-16
6 3.6.2.2 Return Indications................................................................................... 3-17
7 3.6.3 Protocol Data Unit ......................................................................................... 3-17
8 3.6.4 Procedures and Messages for the InUse Instance of the Protocol ................... 3-17
9 3.6.4.1 Procedures .............................................................................................. 3-17
10 3.6.4.1.1 Transmission and Processing of DataReady Message ......................... 3-17
11 3.6.4.1.2 Close State ........................................................................................ 3-17
12 3.6.4.1.2.1 Access Terminal Requirements .................................................... 3-17
13 3.6.4.1.2.2 Access Network Requirements ..................................................... 3-17
14 3.6.4.1.3 Open State......................................................................................... 3-17
17 3.6.4.2 Message Formats..................................................................................... 3-18
18 3.6.4.2.1 XonRequest ....................................................................................... 3-18
19 3.6.4.2.2 XonResponse ..................................................................................... 3-18
20 3.6.4.2.3 XoffRequest ....................................................................................... 3-19
21 3.6.4.2.4 XoffResponse ..................................................................................... 3-19
22 3.6.4.2.5 DataReady ......................................................................................... 3-19
23 3.6.4.2.6 DataReadyAck ................................................................................... 3-20
24 3.6.5 Interface to Other Protocols ........................................................................... 3-20
25 3.6.5.1 Commands .............................................................................................. 3-20
26 3.6.5.2 Indications .............................................................................................. 3-20
27 3.6.6 Protocol Numeric Constants .......................................................................... 3-20
28 3.7 Configuration Attributes for the Default Packet Application ................................ 3-22
29 3.8 Session State Information ................................................................................... 3-22
30 3.8.1 Location Parameter ....................................................................................... 3-22
31 3.8.2 FlowControlState Parameter .......................................................................... 3-23
32 4 Multi-Flow Packet Application..................................................................................... 4-1
vi
3GPP2 C.S0024-B v2.0
CONTENTS
1 4.1 Introduction ..........................................................................................................4-1

2 4.1.1 General Overview.............................................................................................4-1
3 4.1.2 Public Data......................................................................................................4-1
4 4.1.3 Data Encapsulation for the InUse Instance of the Application..........................4-1
5 4.2 Protocol Initialization.............................................................................................4-2
6 4.2.1 Protocol Initialization for the InConfiguration Application Instance ..................4-2
8 Application ............................................................................................................4-2
9 4.3.1 Procedures ......................................................................................................4-2
10 4.3.2 Commit Procedures .........................................................................................4-3
11 4.3.3 Message Formats .............................................................................................4-4
12 4.3.3.1 ConfigurationRequest ................................................................................4-4
13 4.3.3.2 ConfigurationResponse ..............................................................................4-5
14 4.4 Radio Link Protocol ...............................................................................................4-6
15 4.4.1 Overview..........................................................................................................4-6
16 4.4.2 Primitives and Public Data...............................................................................4-6
17 4.4.2.1 Commands ................................................................................................4-6
18 4.4.2.2 Return Indications .....................................................................................4-6
19 4.4.3 Protocol Data Unit ...........................................................................................4-6
20 4.4.4 Procedures and Messages for the InUse Instance of the Protocol......................4-6
21 4.4.4.1 Procedures.................................................................................................4-6
22 4.4.4.1.1 Initialization and Reset.........................................................................4-8
23 4.4.4.1.1.1 Initialization Procedure ..................................................................4-8
24 4.4.4.1.1.1.1 Initialization Procedure for the RLP Transmitter .......................4-8
25 4.4.4.1.1.1.2 Initialization Procedure for the RLP Receiver.............................4-8
26 4.4.4.1.1.2 Reset Procedure .............................................................................4-8
27 4.4.4.1.1.2.1 Reset Procedure for the Initiating Side when it is an RLP
28 Transmitter .............................................................................................4-8
29 4.4.4.1.1.2.2 Reset Procedure for Initiating Side when it is an RLP
30 Receiver...................................................................................................4-9
31 4.4.4.1.1.2.3 Reset Procedure for the Responding Side when it is an RLP
32 Receiver...................................................................................................4-9
33 4.4.4.1.1.2.4 Reset Procedure for the Responding Side when it is a RLP
34 transmitter ............................................................................................4-10
vii
3GPP2 C.S0024-B v2.0
CONTENTS
1 4.4.4.1.1.2.5 RLP Reset Message Flows....................................................... 4-10

2 4.4.4.2 Data Transfer .......................................................................................... 4-10
3 4.4.4.2.1 RLP Transmit Procedures .................................................................. 4-11
4 4.4.4.2.1.1 Reservation State Maintenance .................................................... 4-12
5 4.4.4.2.1.1.1 State-independent Requirements ........................................... 4-13
6 4.4.4.2.1.1.1.1 Access Terminal Requirements ......................................... 4-13
7 4.4.4.2.1.1.1.2 Access Network Requirements.......................................... 4-14
8 4.4.4.2.1.1.2 Close State ............................................................................. 4-15
11 4.4.4.2.1.1.3 Open State ............................................................................. 4-16
14 4.4.4.2.2 RLP Receive Procedures ..................................................................... 4-17
15 4.4.4.3 RLP Packet Header .................................................................................. 4-19
16 4.4.4.4 Message Formats..................................................................................... 4-20
17 4.4.4.4.1 ResetTxIndication .............................................................................. 4-20
18 4.4.4.4.2 ResetRxIndication.............................................................................. 4-20
19 4.4.4.4.3 ResetTxIndicationAck ........................................................................ 4-21
20 4.4.4.4.4 ResetTxComplete ............................................................................... 4-21
21 4.4.4.4.5 ResetRxComplete............................................................................... 4-22
22 4.4.4.4.6 Nak.................................................................................................... 4-22
23 4.4.4.4.7 ReservationOnRequest....................................................................... 4-23
24 4.4.4.4.8 ReservationOffRequest....................................................................... 4-25
25 4.4.4.4.9 ReservationAccept ............................................................................. 4-26
26 4.4.4.4.10 ReservationReject ............................................................................ 4-26
27 4.4.4.4.11 RevReservationOn............................................................................ 4-28
28 4.4.4.4.12 RevReservationOff............................................................................ 4-28
29 4.4.4.4.13 FwdReservationOff........................................................................... 4-29
30 4.4.4.4.14 FwdReservationOn........................................................................... 4-30
31 4.4.4.4.15 FwdReservationAck.......................................................................... 4-30
32 4.4.4.4.16 AttributeUpdateRequest................................................................... 4-31
viii
3GPP2 C.S0024-B v2.0
CONTENTS
1 4.4.4.4.17 AttributeUpdateAccept .....................................................................4-31

2 4.4.4.4.18 AttributeUpdateReject ......................................................................4-32
4 4.4.4.5.1 Commands.........................................................................................4-32
5 4.4.4.5.2 Indications .........................................................................................4-32
6 4.4.4.6 RLP Packet Priorities................................................................................4-33
8 4.5 Data Over Signaling Protocol ...............................................................................4-34
9 4.5.1 Overview........................................................................................................4-34
11 4.5.2.1 Commands ..............................................................................................4-34
15 4.5.4.1 Procedures...............................................................................................4-34
16 4.5.4.2 Message Formats .....................................................................................4-35
17 4.5.4.2.1 DataOverSignaling .............................................................................4-35
18 4.5.4.2.2 DataOverSignalingAck .......................................................................4-36
20 4.5.4.3.1 Commands.........................................................................................4-36
21 4.5.4.3.2 Indications .........................................................................................4-36
22 4.6 Location Update Protocol .....................................................................................4-37
23 4.6.1 Overview........................................................................................................4-37
25 4.6.2.1 Commands ..............................................................................................4-37
29 4.6.4.1 Procedures...............................................................................................4-37
32 4.6.4.2 Message Formats .....................................................................................4-38
ix
3GPP2 C.S0024-B v2.0
CONTENTS
1 4.6.4.2.1 LocationRequest ................................................................................ 4-38

2 4.6.4.2.2 LocationNotification ........................................................................... 4-38
3 4.6.4.2.3 LocationAssignment........................................................................... 4-39
4 4.6.4.2.4 LocationComplete .............................................................................. 4-40
5 4.6.4.2.5 StorageBLOBRequest......................................................................... 4-41
6 4.6.4.2.6 StorageBLOBNotification ................................................................... 4-41
7 4.6.4.2.7 StorageBLOBAssignment ................................................................... 4-42
8 4.6.4.2.8 StorageBLOBComplete....................................................................... 4-42
10 4.6.4.3.1 Commands ........................................................................................ 4-43
11 4.6.4.3.2 Indications......................................................................................... 4-43
12 4.7 Flow Control Protocol .......................................................................................... 4-44
13 4.7.1 Overview ....................................................................................................... 4-44
15 4.7.2.1 Commands .............................................................................................. 4-44
19 4.7.4.1 Procedures .............................................................................................. 4-45
20 4.7.4.1.1 Transmission and Processing of DataReady Message ......................... 4-45
21 4.7.4.1.2 Close State ........................................................................................ 4-45
24 4.7.4.1.3 Open State......................................................................................... 4-46
27 4.7.4.2 Message Formats..................................................................................... 4-46
28 4.7.4.2.1 XonRequest ....................................................................................... 4-46
29 4.7.4.2.2 XonResponse ..................................................................................... 4-47
30 4.7.4.2.3 XoffRequest ....................................................................................... 4-47
31 4.7.4.2.4 XoffResponse ..................................................................................... 4-47
32 4.7.4.2.5 DataReady ......................................................................................... 4-48
x
3GPP2 C.S0024-B v2.0
CONTENTS
1 4.7.4.2.6 DataReadyAck....................................................................................4-48
2 4.7.5 Interface to Other Protocols ...........................................................................4-49
3 4.7.5.1 Commands ..............................................................................................4-49
4 4.7.5.2 Indications...............................................................................................4-49
6 4.8 Configuration Attributes for the Multi-Flow Packet Application............................4-50
7 4.8.1 Simple Attributes...........................................................................................4-51
8 4.8.2 Complex Attributes........................................................................................4-55
9 4.8.2.1 FlowNNIdentificationFwd Attribute...........................................................4-55
10 4.8.2.2 FlowNNIdentificationRev Attribute ...........................................................4-57
11 4.8.2.3 FlowNNTimersFwd Attribute ....................................................................4-59
12 4.8.2.4 FlowNNTimersRev Attribute .....................................................................4-60
13 4.8.2.5 FlowNNReservationFwd Attribute .............................................................4-60
14 4.8.2.6 FlowNNReservationRev Attribute..............................................................4-61
15 4.8.2.7 SupportedHigherLayerProtocols Attribute ................................................4-62
16 4.8.2.8 ATSupportedQoSProfiles Attribute ...........................................................4-63
17 4.8.2.9 ANSupportedQoSProfiles Attribute...........................................................4-64
18 4.8.2.10 MaxRLPFlows Attribute..........................................................................4-64
19 4.8.2.11 ReservationKKQoSRequestFwd Attribute ...............................................4-65
20 4.8.2.12 ReservationKKQoSRequestRev Attribute ................................................4-66
21 4.8.2.13 ReservationKKQoSResponseFwd Attribute .............................................4-67
22 4.8.2.14 ReservationKKQoSResponseRev Attribute ..............................................4-68
23 4.8.2.15 MaxReservations Attribute .....................................................................4-69
24 4.9 Session State Information....................................................................................4-71
25 4.9.1 Location Parameter........................................................................................4-71
26 4.9.2 FlowControlState Parameter ..........................................................................4-71
27 4.9.3 DataOverSignalingMessageSequence Parameter ............................................4-72
28 4.9.4 StorageBLOB Parameter ................................................................................4-73
29 4.9.5 ReservationState Parameter...........................................................................4-74
30 5 Stream Layer...............................................................................................................5-1
31 5.1 Introduction ..........................................................................................................5-1
xi
3GPP2 C.S0024-B v2.0
CONTENTS
1 5.1.2 Data Encapsulation for the InUse Protocol Instance ........................................ 5-1
2 5.2 Default Stream Protocol ........................................................................................ 5-3
3 5.2.1 Overview ......................................................................................................... 5-3
5 5.2.2.1 Commands ................................................................................................ 5-3
7 5.2.2.3 Public Data................................................................................................ 5-3
9 5.2.4 Protocol Initialization....................................................................................... 5-3
10 5.2.4.1 Protocol Initialization for the InConfiguration Protocol Instance................. 5-3
11 5.2.4.2 Protocol Initialization for the InUse Protocol Instance ................................ 5-4
12 5.2.5 Procedures and Messages for the InConfiguration Instance of the Protocol...... 5-4
13 5.2.5.1 Procedures ................................................................................................ 5-4
14 5.2.5.2 Commit Procedures ................................................................................... 5-4
15 5.2.5.3 Message Formats....................................................................................... 5-5
16 5.2.5.3.1 ConfigurationRequest .......................................................................... 5-5
17 5.2.5.3.2 ConfigurationResponse ........................................................................ 5-5
19 5.2.6.1 Procedures ................................................................................................ 5-6
20 5.2.6.2 Stream Header .......................................................................................... 5-6
21 5.2.6.3 Interface to Other Protocols ....................................................................... 5-6
22 5.2.6.3.1 Commands .......................................................................................... 5-6
23 5.2.6.3.2 Indications........................................................................................... 5-6
24 5.2.7 Configuration Attributes.................................................................................. 5-7
25 5.2.7.1 StreamConfiguration Attribute .................................................................. 5-7
26 5.2.8 Protocol Numeric Constants ............................................................................ 5-7
27 5.2.9 Session State Information ............................................................................... 5-8
28 5.3 Generic Virtual Stream Protocol ............................................................................ 5-9
29 5.3.1 Overview ......................................................................................................... 5-9
31 5.3.2.1 Commands ................................................................................................ 5-9
xii
3GPP2 C.S0024-B v2.0
CONTENTS
1 5.3.2.3 Public Data ................................................................................................5-9

3 5.3.4 Protocol Initialization .......................................................................................5-9
4 5.3.4.1 Protocol Initialization for the InConfiguration Protocol Instance .................5-9
5 5.3.5 Procedures and Messages for the InConfiguration Instance of the Protocol ....5-10
6 5.3.5.1 Procedures...............................................................................................5-10
7 5.3.5.2 Commit Procedures .................................................................................5-10
8 5.3.5.3 Message Formats .....................................................................................5-10
9 5.3.5.3.1 ConfigurationRequest.........................................................................5-10
10 5.3.5.3.2 ConfigurationResponse ......................................................................5-11
12 5.3.6.1 Procedures...............................................................................................5-12
13 5.3.6.2 Message Formats .....................................................................................5-12
14 5.3.6.2.1 ApplicationData .................................................................................5-12
16 5.3.6.3.1 Commands.........................................................................................5-13
17 5.3.6.3.2 Indications .........................................................................................5-13
18 5.3.7 Configuration Attributes ................................................................................5-13
19 5.3.7.1 Simple Attributes .....................................................................................5-13
21 5.3.9 Session State Information..............................................................................5-14
22 6 Session Layer ..............................................................................................................6-1
23 6.1 Introduction ..........................................................................................................6-1
25 6.1.2 Data Encapsulation for the InUse Protocol Instance ........................................6-2
26 6.2 Default Session Management Protocol ...................................................................6-3
27 6.2.1 Overview..........................................................................................................6-3
29 6.2.2.1 Commands ................................................................................................6-4
31 6.2.2.3 Public Data ................................................................................................6-4
xiii
3GPP2 C.S0024-B v2.0
CONTENTS

5 6.2.5.1 Procedures ................................................................................................ 6-5
7 6.2.5.3 Message Formats....................................................................................... 6-6
11 6.2.6.1 Procedures ................................................................................................ 6-7
12 6.2.6.1.1 Command Processing .......................................................................... 6-7
13 6.2.6.1.1.1 Activate.......................................................................................... 6-7
14 6.2.6.1.1.2 Deactivate ...................................................................................... 6-7
15 6.2.6.1.2 Processing the SessionClose Message .................................................. 6-8
16 6.2.6.1.3 Processing Failed Indications............................................................... 6-8
17 6.2.6.1.4 Inactive State....................................................................................... 6-9
18 6.2.6.1.5 AMP Setup State.................................................................................. 6-9
19 6.2.6.1.5.1 Access Terminal Requirements ...................................................... 6-9
21 6.2.6.1.6 Open State......................................................................................... 6-10
22 6.2.6.1.6.1 Keep Alive Functions.................................................................... 6-10
23 6.2.6.1.7 Close State ........................................................................................ 6-11
24 6.2.6.2 Message Formats..................................................................................... 6-11
25 6.2.6.2.1 SessionClose...................................................................................... 6-11
26 6.2.6.2.1.1 Definition of MoreInfo record when the CloseReason is 0x03........ 6-12
27 6.2.6.2.1.2 Definition of MoreInfo record when the CloseReason is 0x04........ 6-13
28 6.2.6.2.2 KeepAliveRequest .............................................................................. 6-14
29 6.2.6.2.3 KeepAliveResponse ............................................................................ 6-15
31 6.2.6.3.1 Commands Sent ................................................................................ 6-15
32 6.2.6.3.2 Indications......................................................................................... 6-15
xiv
3GPP2 C.S0024-B v2.0
CONTENTS

4 6.3 Default Address Management Protocol ................................................................6-17
5 6.3.1 Overview........................................................................................................6-17
7 6.3.2.1 Commands ..............................................................................................6-18
9 6.3.2.3 Public Data ..............................................................................................6-18
10 6.3.3 Connection Endpoints ...................................................................................6-19
12 6.3.5 Protocol Initialization .....................................................................................6-19
13 6.3.5.1 Protocol Initialization for the InConfiguration Protocol Instance ...............6-19
14 6.3.5.2 Protocol Initialization for the InUse Protocol Instance...............................6-19
16 6.3.6.1 Procedures...............................................................................................6-19
18 6.3.6.3 Message Formats .....................................................................................6-20
22 6.3.7.1 Procedures...............................................................................................6-21
23 6.3.7.1.1 Command Processing.........................................................................6-21
24 6.3.7.1.1.1 Activate ........................................................................................6-21
25 6.3.7.1.1.2 Deactivate ....................................................................................6-22
26 6.3.7.1.1.3 UpdateUATI..................................................................................6-22
27 6.3.7.1.2 UATIAssignment Message Validation..................................................6-22
28 6.3.7.1.3 Processing HardwareIDRequest message............................................6-22
29 6.3.7.1.4 Inactive State .....................................................................................6-22
30 6.3.7.1.4.1 Access Terminal Requirements.....................................................6-22
31 6.3.7.1.4.2 Access Network Requirements......................................................6-23
32 6.3.7.1.5 Setup State ........................................................................................6-23
xv
3GPP2 C.S0024-B v2.0
CONTENTS

3 6.3.7.1.6 Open State......................................................................................... 6-25
6 6.3.7.2 Message Formats..................................................................................... 6-29
7 6.3.7.2.1 UATIRequest...................................................................................... 6-29
8 6.3.7.2.2 UATIAssignment ................................................................................ 6-30
9 6.3.7.2.3 UATIComplete.................................................................................... 6-31
10 6.3.7.2.4 HardwareIDRequest........................................................................... 6-32
11 6.3.7.2.5 HardwareIDResponse ........................................................................ 6-32
12 6.3.7.2.6 AttributeUpdateRequest .................................................................... 6-33
13 6.3.7.2.7 AttributeUpdateAccept....................................................................... 6-34
14 6.3.7.2.8 AttributeUpdateReject........................................................................ 6-34
16 6.3.7.3.1 Commands ........................................................................................ 6-35
17 6.3.7.3.2 Indications......................................................................................... 6-35
18 6.3.8 Configuration Attributes................................................................................ 6-35
20 6.3.10 Session State Information............................................................................ 6-37
21 6.3.10.1 SessionSeed Parameter.......................................................................... 6-37
22 6.3.10.2 MessageSequence Parameter ................................................................. 6-38
23 6.3.10.3 HardwareID Parameter .......................................................................... 6-38
24 6.4 Default Session Configuration Protocol ............................................................... 6-40
25 6.4.1 Overview ....................................................................................................... 6-40
27 6.4.2.1 Commands .............................................................................................. 6-41
29 6.4.2.3 Public Data.............................................................................................. 6-42
31 6.4.4 Protocol Initialization..................................................................................... 6-42
32 6.4.4.1 Protocol Initialization for the InConfiguration Protocol Instance............... 6-42
xvi
3GPP2 C.S0024-B v2.0
CONTENTS

3 6.4.5.1 Procedures...............................................................................................6-43
5 6.4.5.3 Message Formats .....................................................................................6-43
7 6.4.6.1 Procedures...............................................................................................6-43
8 6.4.6.1.1 Processing the Activate Command......................................................6-45
9 6.4.6.1.2 Processing the Deactivate Command..................................................6-45
10 6.4.6.1.3 Maintaining the ConnectionState Parameter ......................................6-45
11 6.4.6.1.4 Maintaining the ConfigurationLock parameter ...................................6-45
12 6.4.6.1.5 Inactive State .....................................................................................6-46
13 6.4.6.1.6 AT Initiated State ...............................................................................6-46
16 6.4.6.1.7 AN Initiated State...............................................................................6-49
19 6.4.6.1.8 Open State .........................................................................................6-54
22 6.4.6.2 Message Formats .....................................................................................6-56
23 6.4.6.2.1 ConfigurationComplete ......................................................................6-56
24 6.4.6.2.2 ConfigurationStart .............................................................................6-57
27 6.4.6.2.5 SoftConfigurationComplete ................................................................6-59
28 6.4.6.2.6 LockConfiguration..............................................................................6-60
29 6.4.6.2.7 LockConfigurationAck ........................................................................6-60
30 6.4.6.2.8 UnLockConfiguration .........................................................................6-61
31 6.4.6.2.9 UnLockConfigurationAck ...................................................................6-61
32 6.4.6.2.10 DeletePersonality .............................................................................6-62
xvii
3GPP2 C.S0024-B v2.0
CONTENTS
1 6.4.6.2.11 DeletePersonalityAck ....................................................................... 6-62

3 6.4.6.2.13 AttributeUpdateAccept..................................................................... 6-63
4 6.4.6.2.14 AttributeUpdateReject...................................................................... 6-64
6 6.4.6.3.1 Commands ........................................................................................ 6-64
7 6.4.6.3.2 Indications......................................................................................... 6-64
9 6.4.7.1 Simple Attributes..................................................................................... 6-65
10 6.4.7.2 Complex Attributes.................................................................................. 6-67
11 6.4.7.2.1 PriorSession Attribute........................................................................ 6-67
12 6.4.7.2.2 ATSupportedApplicationSubtypes Attribute ....................................... 6-69
14 6.4.9 Message Flows .............................................................................................. 6-70
16 6.4.10.1 ConfigurationLock Parameter ................................................................ 6-73
17 6.4.10.2 ATSupportedNonDefaultProtocolSubTypes Parameter............................ 6-74
18 6.4.10.3 CurrentPersonalityIndex Parameter ....................................................... 6-75
19 6.5 Generic Multimode Capability Discovery Protocol................................................ 6-76
20 6.5.1 General Overview .......................................................................................... 6-76
22 6.5.2.1 Commands .............................................................................................. 6-76
24 6.5.2.3 Public Data.............................................................................................. 6-76
28 6.5.5 Procedures and Messages for the InConfiguration Instance of the Protocol.... 6-76
29 6.5.5.1 Procedures .............................................................................................. 6-76
30 6.5.5.1.1 Access Network Procedures ............................................................... 6-77
31 6.5.5.1.2 Commit Procedures ........................................................................... 6-77
32 6.5.5.2 Message Formats..................................................................................... 6-77
xviii
3GPP2 C.S0024-B v2.0
CONTENTS
4 6.5.6.1 Procedures...............................................................................................6-78
5 6.5.6.2 Message Formats .....................................................................................6-78
7 6.5.7.1 Commands ..............................................................................................6-78
8 6.5.7.2 Indications...............................................................................................6-79
10 6.5.9 Configuration Attributes for the Multimode Capability Discovery Protocol .....6-79
11 6.6 Session State Information....................................................................................6-95
12 7 Connection Layer ........................................................................................................7-1
13 7.1 Introduction ..........................................................................................................7-1
15 7.1.2 Data Encapsulation for the InUse Protocol Instance ........................................7-3
16 7.2 Default Air-Link Management Protocol ..................................................................7-5
17 7.2.1 Overview..........................................................................................................7-5
19 7.2.2.1 Commands ................................................................................................7-7
21 7.2.2.3 Public Data ................................................................................................7-7
23 7.2.4 Protocol Initialization .......................................................................................7-8
25 7.2.4.2 Protocol Initialization for the InUse Protocol Instance.................................7-8
26 7.2.5 Procedures and Messages for the InConfiguration Instance of the Protocol ......7-8
27 7.2.5.1 Procedures.................................................................................................7-8
28 7.2.5.2 Commit Procedures ...................................................................................7-8
29 7.2.5.3 Message Formats .......................................................................................7-9
30 7.2.5.3.1 ConfigurationRequest...........................................................................7-9
xix
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.2.6.1 Procedures .............................................................................................. 7-10

2 7.2.6.1.1 Command Processing ........................................................................ 7-10
3 7.2.6.1.1.1 OpenConnection .......................................................................... 7-10
4 7.2.6.1.1.2 CloseConnection .......................................................................... 7-11
5 7.2.6.1.2 Initialization State.............................................................................. 7-11
7 7.2.6.1.3 Idle State ........................................................................................... 7-11
9 7.2.6.1.3.1.1 General Requirements............................................................ 7-11
10 7.2.6.1.3.1.2 Idle State Cleanup Procedures ............................................... 7-12
13 7.2.6.1.3.2.2 Idle State Cleanup Procedures ............................................... 7-13
14 7.2.6.1.4 Connected State ................................................................................ 7-13
19 7.2.6.1.4.2.2 Connected State Cleanup Procedures..................................... 7-15
20 7.2.6.2 Message Formats..................................................................................... 7-15
21 7.2.6.2.1 Redirect ............................................................................................. 7-15
22 7.2.6.2.2 ConnectionFailureReport ................................................................... 7-15
23 7.2.6.2.3 ConnectionFailureReportAck ............................................................. 7-18
25 7.2.6.3.1 Commands Sent ................................................................................ 7-18
26 7.2.6.3.2 Indications......................................................................................... 7-19
29 7.2.9 Session State Information ............................................................................. 7-20
30 7.3 Default Initialization State Protocol ..................................................................... 7-21
31 7.3.1 Overview ....................................................................................................... 7-21
xx
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.3.2.1 Commands ..............................................................................................7-21

3 7.3.2.3 Public Data ..............................................................................................7-22
9 7.3.5.1 Procedures...............................................................................................7-23
11 7.3.5.3 Message Formats .....................................................................................7-23
15 7.3.6.1 Procedures...............................................................................................7-25
17 7.3.6.1.1.1 Activate ........................................................................................7-25
18 7.3.6.1.1.2 Deactivate ....................................................................................7-25
19 7.3.6.1.2 Inactive State .....................................................................................7-25
20 7.3.6.1.3 Network Determination State .............................................................7-25
21 7.3.6.1.4 Pilot Acquisition State ........................................................................7-26
22 7.3.6.1.5 Synchronization State ........................................................................7-26
23 7.3.6.2 Message Formats .....................................................................................7-26
24 7.3.6.2.1 Sync...................................................................................................7-26
26 7.3.6.3.1 Commands Sent.................................................................................7-27
27 7.3.6.3.2 Indications .........................................................................................7-27
31 7.4 Default Idle State Protocol ...................................................................................7-29
32 7.4.1 Overview........................................................................................................7-29
xxi
3GPP2 C.S0024-B v2.0
CONTENTS

2 7.4.2.1 Commands .............................................................................................. 7-31
4 7.4.2.3 Public Data.............................................................................................. 7-31
8 7.4.4.2 Protocol Initialization for the InUse Protocol Instance .............................. 7-32
10 7.4.5.1 Procedures .............................................................................................. 7-32
11 7.4.5.2 Commit Procedures ................................................................................. 7-32
12 7.4.5.3 Message Formats..................................................................................... 7-33
13 7.4.5.3.1 ConfigurationRequest ........................................................................ 7-33
14 7.4.5.3.2 ConfigurationResponse ...................................................................... 7-33
16 7.4.6.1 Procedures .............................................................................................. 7-34
18 7.4.6.1.1.1 Activate........................................................................................ 7-34
19 7.4.6.1.1.2 Deactivate .................................................................................... 7-34
20 7.4.6.1.1.3 OpenConnection .......................................................................... 7-35
21 7.4.6.1.1.4 Close............................................................................................ 7-35
22 7.4.6.1.2 Access Terminal Procedures for Sending a ConnectionRequest
23 Message ...................................................................................................... 7-35
24 7.4.6.1.3 Inactive State..................................................................................... 7-35
25 7.4.6.1.4 Sleep State ........................................................................................ 7-36
26 7.4.6.1.5 Monitor State..................................................................................... 7-36
28 7.4.6.1.5.1.1 CDMA Channel Selection ....................................................... 7-37
29 7.4.6.1.5.1.2 Transition to Sleep State ........................................................ 7-37
32 7.4.6.1.6 Connection Setup State ..................................................................... 7-38
xxii
3GPP2 C.S0024-B v2.0
CONTENTS

3 7.4.6.2 Message Formats .....................................................................................7-40
4 7.4.6.2.1 Page ...................................................................................................7-40
5 7.4.6.2.2 ConnectionRequest ............................................................................7-41
6 7.4.6.2.3 ConnectionDeny.................................................................................7-41
8 7.4.6.3.1 Commands Sent.................................................................................7-42
9 7.4.6.3.2 Indications .........................................................................................7-42
11 7.4.7.1 PreferredControlChannelCycle Attribute ..................................................7-43
14 7.5 Enhanced Idle State Protocol ...............................................................................7-45
15 7.5.1 Overview........................................................................................................7-45
17 7.5.2.1 Commands ..............................................................................................7-47
19 7.5.2.3 Public Data ..............................................................................................7-47
25 7.5.5.1 Procedures...............................................................................................7-48
27 7.5.5.3 Message Formats .....................................................................................7-49
31 7.5.6.1 Procedures...............................................................................................7-50
xxiii
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.5.6.1.1.1 Activate........................................................................................ 7-50

2 7.5.6.1.1.2 Deactivate .................................................................................... 7-50
3 7.5.6.1.1.3 OpenConnection .......................................................................... 7-51
4 7.5.6.1.1.4 Close............................................................................................ 7-51
6 Message ...................................................................................................... 7-51
7 7.5.6.1.3 T12 and T23 Computation.................................................................... 7-52
8 7.5.6.1.4 Inactive State..................................................................................... 7-52
9 7.5.6.1.5 Sleep State ........................................................................................ 7-52
10 7.5.6.1.6 Monitor State..................................................................................... 7-53
19 7.5.6.2 Message Formats..................................................................................... 7-60
20 7.5.6.2.1 Page................................................................................................... 7-60
21 7.5.6.2.2 ConnectionRequest............................................................................ 7-61
22 7.5.6.2.3 ConnectionDeny ................................................................................ 7-62
27 7.5.6.3.1 Commands Sent ................................................................................ 7-64
28 7.5.6.3.2 Indications......................................................................................... 7-65
32 7.5.7.2.1 PreferredControlChannelCycle Attribute ............................................ 7-66
xxiv
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.5.7.2.2 SlottedMode Attribute ........................................................................7-67

2 7.5.7.3 PagingMask Attribute...............................................................................7-68
5 7.6 Quick Idle State Protocol .....................................................................................7-71
6 7.6.1 Overview........................................................................................................7-71
8 7.6.2.1 Commands ..............................................................................................7-73
10 7.6.2.3 Public Data ..............................................................................................7-73
16 7.6.5.1 Procedures...............................................................................................7-74
18 7.6.5.3 Message Formats .....................................................................................7-75
22 7.6.6.1 Procedures...............................................................................................7-76
24 7.6.6.1.1.1 Activate ........................................................................................7-76
25 7.6.6.1.1.2 Deactivate ....................................................................................7-76
26 7.6.6.1.1.3 OpenConnection...........................................................................7-77
27 7.6.6.1.1.4 Close ............................................................................................7-77
29 Message ......................................................................................................7-77
30 7.6.6.1.3 T12 and T23 Computation ....................................................................7-78
31 7.6.6.1.4 Inactive State .....................................................................................7-78
32 7.6.6.1.5 Sleep State .........................................................................................7-78
33 7.6.6.1.6 Monitor State .....................................................................................7-80
xxv
3GPP2 C.S0024-B v2.0
CONTENTS

8 7.6.6.2 Message Formats..................................................................................... 7-88
9 7.6.6.2.1 Page................................................................................................... 7-88
10 7.6.6.2.2 ConnectionRequest............................................................................ 7-89
11 7.6.6.2.3 ConnectionDeny ................................................................................ 7-90
12 7.6.6.2.4 QuickPage ......................................................................................... 7-91
17 7.6.6.3.1 Commands Sent ................................................................................ 7-94
18 7.6.6.3.2 Indications......................................................................................... 7-94
22 7.6.7.2.1 PreferredControlChannelCycle Attribute ............................................ 7-96
23 7.6.7.2.2 SlottedMode Attribute ........................................................................ 7-97
24 7.6.7.3 PagingMask Attribute .............................................................................. 7-98
25 7.6.7.4 QuickPaging Attribute ........................................................................... 7-100
26 7.6.8 Protocol Numeric Constants ........................................................................ 7-100
27 7.6.9 Session State Information ........................................................................... 7-101
28 7.7 Default Connected State Protocol ...................................................................... 7-102
29 7.7.1 Overview ..................................................................................................... 7-102
30 7.7.2 Primitives and Public Data .......................................................................... 7-103
31 7.7.2.1 Commands ............................................................................................ 7-103
32 7.7.2.2 Return Indications................................................................................. 7-103
xxvi
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.7.2.3 Public Data ............................................................................................7-103

2 7.7.3 Protocol Data Unit .......................................................................................7-103
3 7.7.4 Protocol Initialization ...................................................................................7-104
4 7.7.4.1 Protocol Initialization for the InConfiguration Protocol Instance .............7-104
5 7.7.4.2 Protocol Initialization for the InUse Protocol Instance.............................7-104
6 7.7.5 Procedures and Messages for the InConfiguration Instance of the Protocol ..7-104
7 7.7.5.1 Procedures.............................................................................................7-104
8 7.7.5.2 Commit Procedures ...............................................................................7-104
9 7.7.5.3 Message Formats ...................................................................................7-105
10 7.7.5.3.1 ConfigurationRequest.......................................................................7-105
11 7.7.5.3.2 ConfigurationResponse ....................................................................7-105
12 7.7.6 Procedures and Messages for the InUse Instance of the Protocol..................7-106
13 7.7.6.1 Procedures.............................................................................................7-106
14 7.7.6.1.1 Command Processing.......................................................................7-106
15 7.7.6.1.1.1 Activate ......................................................................................7-106
16 7.7.6.1.1.2 Deactivate ..................................................................................7-106
17 7.7.6.1.1.3 CloseConnection ........................................................................7-107
18 7.7.6.1.2 Open State .......................................................................................7-107
19 7.7.6.1.2.1 Access Terminal Requirements...................................................7-107
20 7.7.6.1.2.1.1 General Requirements ..........................................................7-107
21 7.7.6.1.2.1.2 Cleanup Procedures .............................................................7-108
22 7.7.6.1.2.2 Access Network Requirements....................................................7-108
23 7.7.6.1.2.2.1 General Requirements ..........................................................7-108
24 7.7.6.1.2.2.2 Cleanup Procedures .............................................................7-108
25 7.7.6.1.3 Close State.......................................................................................7-108
26 7.7.6.2 Message Formats ...................................................................................7-108
27 7.7.6.2.1 ConnectionClose ..............................................................................7-108
28 7.7.6.3 Interface to Other Protocols ...................................................................7-110
29 7.7.6.3.1 Commands Sent...............................................................................7-110
30 7.7.6.3.2 Indications .......................................................................................7-110
31 7.7.7 Configuration Attributes ..............................................................................7-110
32 7.7.8 Protocol Numeric Constants ........................................................................7-110
xxvii
3GPP2 C.S0024-B v2.0
CONTENTS

2 7.8 Default Route Update Protocol .......................................................................... 7-111
3 7.8.1 Overview ..................................................................................................... 7-111
5 7.8.2.1 Commands ............................................................................................ 7-112
7 7.8.2.3 Public Data............................................................................................ 7-113
8 7.8.3 Protocol Data Unit ....................................................................................... 7-113
9 7.8.4 Protocol Initialization................................................................................... 7-113
10 7.8.4.1 Protocol Initialization for the InConfiguration Protocol Instance............. 7-113
11 7.8.4.2 Protocol Initialization for the InUse Protocol Instance ............................ 7-113
12 7.8.5 Procedures and Messages for the InConfiguration Instance of the Protocol.. 7-114
13 7.8.5.1 Procedures ............................................................................................ 7-114
14 7.8.5.2 Commit Procedures ............................................................................... 7-114
15 7.8.5.3 Message Formats................................................................................... 7-115
16 7.8.5.3.1 ConfigurationRequest ...................................................................... 7-115
17 7.8.5.3.2 ConfigurationResponse .................................................................... 7-116
18 7.8.6 Procedures and Messages for the InUse Instance of the Protocol ................. 7-116
19 7.8.6.1 Procedures ............................................................................................ 7-116
20 7.8.6.1.1 Command Processing ...................................................................... 7-116
21 7.8.6.1.1.1 Activate...................................................................................... 7-116
22 7.8.6.1.1.2 Deactivate .................................................................................. 7-116
23 7.8.6.1.1.3 Open.......................................................................................... 7-117
24 7.8.6.1.1.4 Close.......................................................................................... 7-117
25 7.8.6.1.2 Pilots and Pilot Sets ......................................................................... 7-118
26 7.8.6.1.2.1 Neighbor Set Search Window Parameters Update....................... 7-118
27 7.8.6.1.2.2 Pilot Search ............................................................................... 7-119
28 7.8.6.1.2.3 Pilot Strength Measurement....................................................... 7-120
29 7.8.6.1.2.4 Pilot Drop Timer Maintenance.................................................... 7-120
30 7.8.6.1.2.5 Active Set Management .............................................................. 7-121
31 7.8.6.1.2.6 Candidate Set Management ....................................................... 7-121
32 7.8.6.1.2.7 Neighbor Set Management ......................................................... 7-121
xxviii
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.8.6.1.2.8 Remaining Set Management .......................................................7-123

2 7.8.6.1.2.9 Pilot PN Phase Measurement ......................................................7-124
3 7.8.6.1.3 Message Sequence Numbers ............................................................7-124
4 7.8.6.1.3.1 RouteUpdate Message Validation ...............................................7-124
5 7.8.6.1.3.2 TrafficChannelAssignment Message Validation...........................7-124
6 7.8.6.1.3.3 AttributeOverride Message Validation.........................................7-125
7 7.8.6.1.4 Inactive State ...................................................................................7-125
8 7.8.6.1.5 Idle State .........................................................................................7-126
9 7.8.6.1.5.1 Active Set Maintenance ..............................................................7-126
10 7.8.6.1.5.2 Pilot Channel Supervision in the Idle State.................................7-126
11 7.8.6.1.5.3 Processing the TrafficChannelAssignment Message in the Idle
12 State ......................................................................................................7-127
13 7.8.6.1.5.4 Route Update Report Rules ........................................................7-128
14 7.8.6.1.6 Connected State...............................................................................7-130
15 7.8.6.1.6.1 Access Terminal Requirements...................................................7-130
16 7.8.6.1.6.2 Access Network Requirements....................................................7-130
18 7.8.6.1.6.3.1 Access Network ....................................................................7-130
19 7.8.6.1.6.3.2 Access Terminal ...................................................................7-131
20 7.8.6.1.6.4 ResetReport Message..................................................................7-131
21 7.8.6.1.6.5 Route Update Report Rules ........................................................7-132
22 7.8.6.1.6.6 Processing the TrafficChannelAssignment Message in the
23 Connected State .....................................................................................7-133
24 7.8.6.1.6.7 Processing the TrafficChannelComplete Message........................7-134
25 7.8.6.1.6.8 Transmission and Processing of the NeighborList Message .........7-135
26 7.8.6.1.6.9 Transmission and Processing of the AttributeOverride Message .7-135
27 7.8.6.1.6.10 Processing of OverheadMessages.Updated Indication ...............7-136
28 7.8.6.1.6.11 OverheadMessagesNeighborList Initialization ...........................7-136
29 7.8.6.2 Message Formats ...................................................................................7-136
30 7.8.6.2.1 RouteUpdate ....................................................................................7-136
31 7.8.6.2.2 TrafficChannelAssignment ...............................................................7-138
32 7.8.6.2.3 TrafficChannelComplete ...................................................................7-144
33 7.8.6.2.4 ResetReport .....................................................................................7-144
xxix
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.8.6.2.5 NeighborList .................................................................................... 7-144

2 7.8.6.2.6 AttributeOverride............................................................................. 7-149
3 7.8.6.2.7 AttributeOverrideResponse .............................................................. 7-149
4 7.8.6.2.8 RouteUpdateRequest ....................................................................... 7-150
5 7.8.6.2.9 AttributeUpdateRequest .................................................................. 7-153
6 7.8.6.2.10 AttributeUpdateAccept................................................................... 7-154
7 7.8.6.2.11 AttributeUpdateReject.................................................................... 7-154
8 7.8.6.3 Interface to Other Protocols ................................................................... 7-154
9 7.8.6.3.1 Commands Sent .............................................................................. 7-154
10 7.8.6.3.2 Indications....................................................................................... 7-155
11 7.8.7 Configuration Attributes.............................................................................. 7-155
12 7.8.7.1 Simple Attributes................................................................................... 7-155
13 7.8.7.2 Complex Attributes................................................................................ 7-157
14 7.8.7.2.1 SearchParameters Attribute............................................................. 7-157
15 7.8.7.2.2 SetManagementSameChannelParameters Attribute ......................... 7-159
16 7.8.7.2.3 SetManagementDifferentChannelParameters Attribute .................... 7-162
17 7.8.7.2.4 SupportedCDMAChannels Attribute ................................................ 7-164
20 7.8.9.1 RouteUpdate Parameter......................................................................... 7-165
21 7.8.9.2 ExtendedRouteUpdate Parameter .......................................................... 7-168
22 7.8.9.3 AttributeOverrideMessageSequence Parameter ...................................... 7-170
23 7.9 Multicarrier Route Update Protocol ................................................................... 7-172
24 7.9.1 Overview ..................................................................................................... 7-172
26 7.9.2.1 Commands ............................................................................................ 7-173
28 7.9.2.3 Public Data............................................................................................ 7-174
32 7.9.5 Procedures and Messages for the InConfiguration Instance of the Protocol.. 7-175
xxx
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.9.5.1 Procedures.............................................................................................7-175
3 7.9.5.3 Message Formats ...................................................................................7-177
7 7.9.6.1 Procedures.............................................................................................7-178
9 7.9.6.1.1.1 Activate ......................................................................................7-178
10 7.9.6.1.1.2 Deactivate ..................................................................................7-178
11 7.9.6.1.1.3 Open ..........................................................................................7-178
12 7.9.6.1.1.4 Close ..........................................................................................7-179
13 7.9.6.1.2 Pilots and Pilot Sets .........................................................................7-180
14 7.9.6.1.2.1 Neighbor Set Search Window Parameters Update .......................7-180
15 7.9.6.1.2.2 Pilot Search................................................................................7-181
16 7.9.6.1.2.3 Pilot Strength Measurement .......................................................7-182
17 7.9.6.1.2.4 Pilot Drop Timer Maintenance ....................................................7-182
18 7.9.6.1.2.5 Sub-Active Sets ..........................................................................7-182
19 7.9.6.1.2.6 Pilot Groups ...............................................................................7-183
20 7.9.6.1.2.7 Scheduler Groups ......................................................................7-183
21 7.9.6.1.2.8 Active Set Management ..............................................................7-184
22 7.9.6.1.2.9 Candidate Set Management........................................................7-184
23 7.9.6.1.2.10 Neighbor Set Management........................................................7-185
24 7.9.6.1.2.11 Remaining Set Management .....................................................7-187
25 7.9.6.1.2.12 Pilot PN Phase Measurement ....................................................7-187
26 7.9.6.1.3 Message Sequence Numbers ............................................................7-187
27 7.9.6.1.3.1 RouteUpdate Message Validation ...............................................7-188
28 7.9.6.1.3.2 TrafficChannelAssignment Message Validation...........................7-188
29 7.9.6.1.4 Inactive State ...................................................................................7-188
30 7.9.6.1.5 Idle State .........................................................................................7-189
32 7.9.6.1.5.2 Pilot Channel Supervision in the Idle State.................................7-189
xxxi
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.9.6.1.5.3 Processing the TrafficChannelAssignment Message in the Idle

2 State ...................................................................................................... 7-190
3 7.9.6.1.5.4 Route Update Report Rules ........................................................ 7-191
4 7.9.6.1.6 Connected State .............................................................................. 7-192
5 7.9.6.1.6.1 Access Terminal Requirements .................................................. 7-192
6 7.9.6.1.6.2 Access Network Requirements ................................................... 7-193
7 7.9.6.1.6.3 Active Set Maintenance .............................................................. 7-193
8 7.9.6.1.6.3.1 Access Network .................................................................... 7-193
9 7.9.6.1.6.3.2 Access Terminal ................................................................... 7-194
10 7.9.6.1.6.4 ResetReport Message ................................................................. 7-195
11 7.9.6.1.6.5 Route Update Report Rules ........................................................ 7-195
12 7.9.6.1.6.6 Processing the TrafficChannelAssignment Message in the
13 Connected State..................................................................................... 7-197
14 7.9.6.1.6.7 Processing the TrafficChannelComplete Message ....................... 7-198
15 7.9.6.1.6.8 Transmission and Processing of the NeighborList Message......... 7-198
16 7.9.6.1.6.9 Processing of OverheadMessages.Updated Indication................. 7-199
17 7.9.6.1.6.10 OverheadMessagesNeighborList Initialization........................... 7-199
18 7.9.6.2 Message Formats................................................................................... 7-199
19 7.9.6.2.1 RouteUpdate.................................................................................... 7-199
20 7.9.6.2.2 TrafficChannelAssignment ............................................................... 7-202
21 7.9.6.2.3 TrafficChannelComplete................................................................... 7-213
22 7.9.6.2.4 ResetReport ..................................................................................... 7-214
23 7.9.6.2.5 NeighborList .................................................................................... 7-214
24 7.9.6.2.6 RouteUpdateRequest ....................................................................... 7-219
29 7.9.6.3.1 Commands Sent .............................................................................. 7-224
30 7.9.6.3.2 Indications....................................................................................... 7-225
xxxii
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.9.7.2 Complex Attributes ................................................................................7-229

2 7.9.7.2.1 SearchParameters Attribute .............................................................7-230
3 7.9.7.3 SetManagementParameters Attribute.....................................................7-231
4 7.9.7.3.1 SupportedCDMAChannels Attribute.................................................7-234
5 7.9.7.3.2 SupportedDRXPatterns Attribute .....................................................7-236
7 7.9.9 Session State Information............................................................................7-238
8 7.9.9.1 RouteUpdate Parameter .........................................................................7-239
9 7.10 Default Packet Consolidation Protocol .............................................................7-243
10 7.10.1 Overview....................................................................................................7-243
11 7.10.2 Primitives and Public Data.........................................................................7-243
12 7.10.2.1 Commands ..........................................................................................7-243
13 7.10.2.2 Return Indications ...............................................................................7-243
14 7.10.2.3 Public Data ..........................................................................................7-243
15 7.10.3 Protocol Data Unit .....................................................................................7-243
16 7.10.4 Protocol Initialization .................................................................................7-244
17 7.10.4.1 Protocol Initialization for the InConfiguration Protocol Instance ...........7-244
18 7.10.4.2 Protocol Initialization for the InUse Protocol Instance...........................7-244
19 7.10.5 Procedures and Messages for the InConfiguration Instance of the Protocol 7-244
20 7.10.5.1 Procedures...........................................................................................7-244
21 7.10.5.2 Commit Procedures..............................................................................7-245
22 7.10.5.3 Message Formats .................................................................................7-245
23 7.10.5.3.1 ConfigurationRequest.....................................................................7-245
24 7.10.5.3.2 ConfigurationResponse ..................................................................7-246
25 7.10.6 Procedures and Messages for the InUse Instance of the Protocol................7-246
26 7.10.6.1 Procedures...........................................................................................7-246
27 7.10.6.1.1 Destination Channels.....................................................................7-246
28 7.10.6.1.2 Priority Order .................................................................................7-247
29 7.10.6.1.3 Forced Single Encapsulation ..........................................................7-247
30 7.10.6.1.4 Access Terminal Procedures...........................................................7-247
31 7.10.6.1.4.1 Format A Packets .....................................................................7-247
32 7.10.6.1.4.2 Format B Packets .....................................................................7-247
xxxiii
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.10.6.1.5 Access Network Procedures ........................................................... 7-248

2 7.10.6.1.5.1 Control Channel....................................................................... 7-248
3 7.10.6.1.5.1.1 Control Channel Connection Layer Packets ........................ 7-248
4 7.10.6.1.5.1.2 Synchronous Capsule Priority Rules .................................. 7-249
5 7.10.6.1.5.1.3 Sub-synchronous Capsule Priority Rules ........................... 7-249
6 7.10.6.1.5.1.4 Asynchronous Capsule Priority Rules................................. 7-250
7 7.10.6.1.5.2 Forward Traffic Channel .......................................................... 7-250
8 7.10.6.1.5.2.1 Format A Packets ............................................................... 7-250
9 7.10.6.1.5.2.2 Format B Packets............................................................... 7-250
10 7.10.6.2 Message Formats................................................................................. 7-251
11 7.10.6.3 Header Format .................................................................................... 7-251
12 7.10.6.3.1 Pad ................................................................................................ 7-251
13 7.10.6.3.2 Connection Layer Header............................................................... 7-251
14 7.10.6.4 Interface to Other Protocols ................................................................. 7-251
15 7.10.6.4.1 Commands Sent ............................................................................ 7-251
16 7.10.6.4.2 Indications..................................................................................... 7-251
17 7.10.7 Configuration Attributes............................................................................ 7-251
18 7.10.8 Protocol Numeric Constants ...................................................................... 7-251
19 7.10.9 Session State Information.......................................................................... 7-251
20 7.11 Overhead Messages Protocol ........................................................................... 7-252
21 7.11.1 Overview ................................................................................................... 7-252
22 7.11.2 Primitives and Public Data ........................................................................ 7-252
23 7.11.2.1 Commands .......................................................................................... 7-252
24 7.11.2.2 Return Indications............................................................................... 7-252
25 7.11.2.3 Public Data.......................................................................................... 7-253
26 7.11.3 Protocol Data Unit ..................................................................................... 7-253
27 7.11.4 Protocol Initialization................................................................................. 7-253
28 7.11.4.1 Protocol Initialization for the InConfiguration Protocol Instance........... 7-253
29 7.11.4.2 Protocol Initialization for the InUse Protocol Instance .......................... 7-253
31 7.11.5.1 Procedures .......................................................................................... 7-254
32 7.11.5.2 Commit Procedures ............................................................................. 7-254
xxxiv
3GPP2 C.S0024-B v2.0
CONTENTS
1 7.11.5.3 Message Formats .................................................................................7-254

5 7.11.6.1 Procedures...........................................................................................7-256
6 7.11.6.1.1 Extensibility Requirements ............................................................7-256
7 7.11.6.1.2 Command Processing.....................................................................7-256
8 7.11.6.1.2.1 Activate ....................................................................................7-256
9 7.11.6.1.2.2 Deactivate ................................................................................7-256
10 7.11.6.1.3 Inactive State .................................................................................7-256
11 7.11.6.1.4 Active State ....................................................................................7-257
12 7.11.6.1.5 Access Network Requirements........................................................7-257
13 7.11.6.1.6 Access Terminal Requirements.......................................................7-257
14 7.11.6.1.6.1 Supervision Procedures ............................................................7-259
15 7.11.6.1.6.1.1 Supervision of QuickConfig Message ..................................7-259
16 7.11.6.1.6.1.2 Supervision of SectorParameters Message ..........................7-259
17 7.11.6.2 Message Formats .................................................................................7-260
18 7.11.6.2.1 QuickConfig ...................................................................................7-260
19 7.11.6.2.2 SectorParameters ...........................................................................7-263
20 7.11.6.3 Interface to Other Protocols..................................................................7-276
21 7.11.6.3.1 Commands Sent.............................................................................7-276
22 7.11.6.3.2 Indications .....................................................................................7-276
23 7.11.7 Configuration Attributes ............................................................................7-277
24 7.11.8 Protocol Numeric Constants ......................................................................7-277
25 7.11.9 Session State Information ..........................................................................7-277
26 8 Security Layer .............................................................................................................8-1
27 8.1 Introduction ..........................................................................................................8-1
29 8.2 Data Encapsulation for the InUse Protocol Instances ............................................8-1
30 8.3 Default Security Protocol .......................................................................................8-3
31 8.3.1 Overview..........................................................................................................8-3
xxxv
3GPP2 C.S0024-B v2.0
CONTENTS
1 8.3.2.1 Commands ................................................................................................ 8-3

3 8.3.2.3 Public Data................................................................................................ 8-3
9 8.3.5.1 Procedures ................................................................................................ 8-4
11 8.3.5.3 Message Formats....................................................................................... 8-4
15 8.3.6.1 Procedures ................................................................................................ 8-5
16 8.3.6.2 Message Formats....................................................................................... 8-6
17 8.3.6.3 Default Security Protocol Header ............................................................... 8-6
18 8.3.6.4 Default Security Protocol Trailer ................................................................ 8-6
19 8.3.6.5 Interface to Other Protocols ....................................................................... 8-6
20 8.3.6.5.1 Commands .......................................................................................... 8-6
21 8.3.6.5.2 Indications........................................................................................... 8-6
22 8.3.7 Configuration Attributes.................................................................................. 8-6
23 8.3.8 Protocol Numeric Constants ............................................................................ 8-6
24 8.3.9 Session State Information ............................................................................... 8-6
25 8.4 Generic Security Protocol ...................................................................................... 8-7
26 8.4.1 Overview ......................................................................................................... 8-7
28 8.4.2.1 Commands ................................................................................................ 8-7
30 8.4.2.3 Public Data................................................................................................ 8-7
xxxvi
3GPP2 C.S0024-B v2.0
CONTENTS

2 8.4.5 Procedures and Messages for the InConfiguration Instance of the Protocol ......8-8
3 8.4.5.1 Procedures.................................................................................................8-8
4 8.4.5.2 Commit Procedures ...................................................................................8-8
5 8.4.5.3 Message Formats .......................................................................................8-8
6 8.4.5.3.1 ConfigurationRequest...........................................................................8-8
7 8.4.5.3.2 ConfigurationResponse ........................................................................8-9
8 8.4.6 Procedures and Messages for the InUse Instance of the Protocol......................8-9
9 8.4.6.1 Procedures.................................................................................................8-9
10 8.4.6.2 Message Formats .....................................................................................8-10
11 8.4.6.3 Generic Security Protocol Header.............................................................8-11
12 8.4.6.4 Generic Security Protocol Trailer..............................................................8-11
14 8.4.6.5.1 Commands.........................................................................................8-11
15 8.4.6.5.2 Indications .........................................................................................8-11
19 8.5 Default Key Exchange Protocol ............................................................................8-12
20 8.5.1 Overview........................................................................................................8-12
22 8.5.2.1 Commands ..............................................................................................8-12
24 8.5.2.3 Public Data ..............................................................................................8-12
30 8.5.5.1 Procedures...............................................................................................8-13
32 8.5.5.3 Message Formats .....................................................................................8-13
xxxvii
3GPP2 C.S0024-B v2.0
CONTENTS

4 8.5.6.1 Procedures .............................................................................................. 8-14
5 8.5.6.2 Message Formats..................................................................................... 8-14
7 8.5.6.3.1 Commands ........................................................................................ 8-15
8 8.5.6.3.2 Indications......................................................................................... 8-15
12 8.6 DH Key Exchange Protocol .................................................................................. 8-16
13 8.6.1 Overview ....................................................................................................... 8-16
15 8.6.2.1 Commands .............................................................................................. 8-16
17 8.6.2.3 Public Data.............................................................................................. 8-16
19 8.6.2.4.1 Commands ........................................................................................ 8-17
20 8.6.2.4.2 Indications......................................................................................... 8-17
25 8.6.5.1 Procedures .............................................................................................. 8-18
26 8.6.5.1.1 Access Terminal Requirements .......................................................... 8-18
27 8.6.5.1.2 Access Network Requirements ........................................................... 8-20
28 8.6.5.1.3 Authentication Key and Encryption Key Generation........................... 8-21
30 8.6.5.3 Message Formats..................................................................................... 8-24
31 8.6.5.3.1 KeyRequest........................................................................................ 8-24
32 8.6.5.3.2 KeyResponse ..................................................................................... 8-24
xxxviii
3GPP2 C.S0024-B v2.0
CONTENTS
1 8.6.5.3.3 ANKeyComplete .................................................................................8-25

2 8.6.5.3.4 ATKeyComplete ..................................................................................8-26
6 8.6.6.1 Procedures...............................................................................................8-27
7 8.6.6.2 Message Formats .....................................................................................8-27
9 8.6.6.3.1 Commands.........................................................................................8-28
10 8.6.6.3.2 Indications .........................................................................................8-28
13 8.6.9 Message Flows...............................................................................................8-29
14 8.6.10 Session State Information ............................................................................8-31
15 8.6.10.1 SKey Parameter .....................................................................................8-31
16 8.6.10.2 FACAuthKey Parameter .........................................................................8-32
17 8.6.10.3 RACAuthKey Parameter .........................................................................8-32
18 8.6.10.4 FACEncKey Parameter ...........................................................................8-33
19 8.6.10.5 RACEncKey Parameter...........................................................................8-33
20 8.6.10.6 FPCAuthKey Parameter..........................................................................8-33
21 8.6.10.7 RPCAuthKey Parameter .........................................................................8-34
22 8.6.10.8 FPCEncKey Parameter ...........................................................................8-34
23 8.6.10.9 RPCEncKey Parameter ...........................................................................8-35
24 8.7 Default Authentication Protocol ...........................................................................8-36
25 8.7.1 Overview........................................................................................................8-36
27 8.7.2.1 Commands ..............................................................................................8-36
29 8.7.2.3 Public Data ..............................................................................................8-36
xxxix
3GPP2 C.S0024-B v2.0
CONTENTS
3 8.7.5.1 Procedures .............................................................................................. 8-37
5 8.7.5.3 Message Formats..................................................................................... 8-37
9 8.7.6.1 Procedures .............................................................................................. 8-38
10 8.7.6.2 Default Authentication Protocol Header ................................................... 8-39
11 8.7.6.3 Default Authentication Protocol Trailer .................................................... 8-39
12 8.7.6.4 Message Formats..................................................................................... 8-39
14 8.7.6.5.1 Commands ........................................................................................ 8-39
15 8.7.6.5.2 Indications......................................................................................... 8-39
19 8.8 SHA-1 Authentication Protocol............................................................................ 8-40
20 8.8.1 Overview ....................................................................................................... 8-40
22 8.8.2.1 Commands .............................................................................................. 8-40
24 8.8.2.3 Public Data.............................................................................................. 8-40
29 8.8.5.1 Procedures .............................................................................................. 8-41
31 8.8.5.3 Message Formats..................................................................................... 8-41
xl
3GPP2 C.S0024-B v2.0
CONTENTS

3 8.8.6.1 Procedures...............................................................................................8-42
6 8.8.6.2 SHA-1 Authentication Protocol Header Format ........................................8-45
7 8.8.6.3 SHA-1 Authentication Protocol Trailer......................................................8-45
9 8.8.7.1 Commands ..............................................................................................8-45
10 8.8.7.2 Indications...............................................................................................8-45
14 8.9 Default Encryption Protocol.................................................................................8-47
16 8.9.1.1 Commands ..............................................................................................8-47
18 8.9.1.3 Public Data ..............................................................................................8-47
24 8.9.4.1 Procedures...............................................................................................8-48
26 8.9.4.3 Message Formats .....................................................................................8-48
30 8.9.5.1 Procedures...............................................................................................8-49
31 8.9.5.2 Message Formats .....................................................................................8-49
32 8.9.5.3 Default Encryption Protocol Header .........................................................8-50
xli
3GPP2 C.S0024-B v2.0
CONTENTS
1 8.9.5.4 Default Encryption Protocol Trailer.......................................................... 8-50

3 8.9.5.5.1 Commands ........................................................................................ 8-50
4 8.9.5.5.2 Indications......................................................................................... 8-50
8 9 MAC Layer .................................................................................................................. 9-1
9 9.1 Introduction .......................................................................................................... 9-1
11 9.1.2 Data Encapsulation for the InUse Instances of the MAC Protocols................... 9-1
12 9.2 Default Control Channel MAC Protocol.................................................................. 9-4
13 9.2.1 Overview ......................................................................................................... 9-4
15 9.2.2.1 Commands ................................................................................................ 9-4
17 9.2.2.3 Public Data................................................................................................ 9-5
23 9.2.5.1 Procedures ................................................................................................ 9-5
25 9.2.5.3 Message Formats....................................................................................... 9-6
29 9.2.6.1 Procedures ................................................................................................ 9-7
30 9.2.6.1.1 Command Processing .......................................................................... 9-8
31 9.2.6.1.1.1 Activate.......................................................................................... 9-8
32 9.2.6.1.1.2 Deactivate ...................................................................................... 9-9
xlii
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.2.6.1.2 Control Channel Cycle .........................................................................9-9

2 9.2.6.1.3 Inactive State .......................................................................................9-9
3 9.2.6.1.4 Active State ..........................................................................................9-9
4 9.2.6.1.4.1 Access Network Requirements........................................................9-9
5 9.2.6.1.4.1.1 General Requirements ..............................................................9-9
6 9.2.6.1.4.1.2 Transmission of Synchronous Capsules .................................9-10
7 9.2.6.1.4.1.3 Transmission of Asynchronous Capsules................................9-11
8 9.2.6.1.4.1.4 Transmission of Sub-synchronous Capsules ..........................9-11
10 9.2.6.1.4.2.1 Initial Acquisition ...................................................................9-12
11 9.2.6.1.4.2.2 Normal Operation ...................................................................9-12
12 9.2.6.1.4.2.3 Control Channel Supervision..................................................9-12
13 9.2.6.1.4.2.4 Address Matching...................................................................9-13
14 9.2.6.2 Header and Trailer Formats .....................................................................9-13
15 9.2.6.2.1 MAC Layer Header .............................................................................9-13
16 9.2.6.2.2 Control Channel Header.....................................................................9-14
17 9.2.6.2.3 Pad ....................................................................................................9-15
18 9.2.6.2.4 Reserved ............................................................................................9-15
20 9.2.6.3.1 Commands.........................................................................................9-15
21 9.2.6.3.2 Indications .........................................................................................9-15
25 9.3 Enhanced Control Channel MAC Protocol............................................................9-16
26 9.3.1 Overview........................................................................................................9-16
28 9.3.2.1 Commands ..............................................................................................9-16
30 9.3.2.3 Public Data ..............................................................................................9-17
xliii
3GPP2 C.S0024-B v2.0
CONTENTS

2 9.3.5 Protocol Initialization for the InUse Protocol Instance .................................... 9-17
3 9.3.5.1 Procedures .............................................................................................. 9-17
6 9.3.6.1 Procedures .............................................................................................. 9-18
8 9.3.6.3 Message Formats..................................................................................... 9-19
12 9.3.7.1 Procedures .............................................................................................. 9-20
14 9.3.7.1.1.1 Activate........................................................................................ 9-21
15 9.3.7.1.1.2 Deactivate .................................................................................... 9-21
16 9.3.7.1.2 Control Channel Cycle ....................................................................... 9-21
17 9.3.7.1.3 Inactive State..................................................................................... 9-21
18 9.3.7.1.4 Active State........................................................................................ 9-21
21 9.3.7.1.4.1.2 Transmission of Synchronous Capsules ................................. 9-23
22 9.3.7.1.4.1.3 Transmission of Asynchronous Capsules ............................... 9-24
23 9.3.7.1.4.1.4 Transmission of Sub-synchronous Capsules .......................... 9-24
24 9.3.7.1.4.1.5 Transmission of Quick Synchronous Capsules....................... 9-25
26 9.3.7.1.4.2.1 Initial Acquisition ................................................................... 9-25
27 9.3.7.1.4.2.2 Normal Operation................................................................... 9-26
28 9.3.7.1.4.2.3 Control Channel Supervision ................................................. 9-26
29 9.3.7.1.4.2.4 Address Matching .................................................................. 9-26
30 9.3.7.2 Header and Trailer Formats..................................................................... 9-27
31 9.3.7.2.1 MAC Layer Header ............................................................................. 9-27
32 9.3.7.2.2 Control Channel Header .................................................................... 9-28
xliv
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.3.7.2.3 Pad ....................................................................................................9-29

2 9.3.7.2.4 Reserved ............................................................................................9-29
4 9.3.7.3.1 Commands.........................................................................................9-29
5 9.3.7.3.2 Indications .........................................................................................9-29
9 9.4 Default Access Channel MAC Protocol .................................................................9-31
10 9.4.1 Overview........................................................................................................9-31
12 9.4.2.1 Commands ..............................................................................................9-31
14 9.4.2.3 Public Data ..............................................................................................9-32
20 9.4.5.1 Procedures...............................................................................................9-33
22 9.4.5.3 Message Formats .....................................................................................9-34
26 9.4.6.1 Procedures...............................................................................................9-35
28 9.4.6.1.1.1 Activate ........................................................................................9-36
29 9.4.6.1.1.2 Deactivate ....................................................................................9-36
30 9.4.6.1.2 Access Channel Structure ..................................................................9-36
31 9.4.6.1.3 Inactive State .....................................................................................9-37
32 9.4.6.1.4 Active State ........................................................................................9-38
xlv
3GPP2 C.S0024-B v2.0
CONTENTS

2 9.4.6.1.4.1.1 Reverse Link Silence Interval.................................................. 9-38
3 9.4.6.1.4.1.2 Probe Transmission................................................................ 9-39
4 9.4.6.1.4.1.3 Access Channel Long Code Mask ........................................... 9-40
5 9.4.6.1.4.1.4 Probe Sequence Transmission ................................................ 9-41
7 9.4.6.2 Header and Message Formats.................................................................. 9-43
8 9.4.6.2.1 MAC Layer Header ............................................................................. 9-43
9 9.4.6.2.2 FCS ................................................................................................... 9-44
10 9.4.6.2.3 Padding Bits ...................................................................................... 9-45
11 9.4.6.2.4 Reserved Bits..................................................................................... 9-45
12 9.4.6.2.5 ACAck ............................................................................................... 9-45
13 9.4.6.2.6 AccessParameters .............................................................................. 9-46
15 9.4.6.3.1 Commands ........................................................................................ 9-47
16 9.4.6.3.2 Indications......................................................................................... 9-47
18 9.4.7.1 InitialConfiguration Attribute................................................................... 9-48
19 9.4.7.2 PowerParameters Attribute ...................................................................... 9-49
22 9.5 Enhanced Access Channel MAC Protocol ............................................................ 9-51
23 9.5.1 Overview ....................................................................................................... 9-51
25 9.5.2.1 Commands .............................................................................................. 9-51
27 9.5.2.3 Public Data.............................................................................................. 9-52
32 9.5.5.1 Procedures .............................................................................................. 9-53
xlvi
3GPP2 C.S0024-B v2.0
CONTENTS

2 9.5.5.3 Message Formats .....................................................................................9-54
6 9.5.6.1 Procedures...............................................................................................9-55
8 9.5.6.1.1.1 Activate ........................................................................................9-56
9 9.5.6.1.1.2 Deactivate ....................................................................................9-56
10 9.5.6.1.2 Access Channel Structure ..................................................................9-56
11 9.5.6.1.3 Inactive State .....................................................................................9-58
12 9.5.6.1.4 Active State ........................................................................................9-58
14 9.5.6.1.4.1.1 Reverse Link Silence Interval ..................................................9-58
15 9.5.6.1.4.1.2 Probe Transmission ................................................................9-59
16 9.5.6.1.4.1.3 Access Channel Long Code Mask............................................9-62
17 9.5.6.1.4.1.4 Probe Sequence Transmission ................................................9-63
19 9.5.6.2 Header and Message Formats ..................................................................9-66
20 9.5.6.2.1 MAC Layer Header .............................................................................9-66
21 9.5.6.2.2 FCS....................................................................................................9-67
22 9.5.6.2.3 Padding Bits.......................................................................................9-68
23 9.5.6.2.4 Reserved Bits .....................................................................................9-68
24 9.5.6.2.5 ACAck ................................................................................................9-68
25 9.5.6.2.6 AccessParameters ..............................................................................9-69
26 9.5.6.2.7 AttributeUpdateRequest.....................................................................9-77
27 9.5.6.2.8 AttributeUpdateAccept .......................................................................9-78
28 9.5.6.2.9 AttributeUpdateReject ........................................................................9-78
30 9.5.6.3.1 Commands.........................................................................................9-79
31 9.5.6.3.2 Indications .........................................................................................9-79
xlvii
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.5.7.1 InitialConfiguration Attribute................................................................... 9-82

4 9.6 Default Forward Traffic Channel MAC Protocol ................................................... 9-85
5 9.6.1 Overview ....................................................................................................... 9-85
7 9.6.2.1 Commands .............................................................................................. 9-86
9 9.6.2.3 Public Data.............................................................................................. 9-86
15 9.6.5.1 Procedures .............................................................................................. 9-87
17 9.6.5.3 Message Formats..................................................................................... 9-88
21 9.6.6.1 Procedures .............................................................................................. 9-89
23 9.6.6.1.1.1 Activate........................................................................................ 9-89
24 9.6.6.1.1.2 Deactivate .................................................................................... 9-89
25 9.6.6.1.2 Forward Traffic Channel Addressing .................................................. 9-90
26 9.6.6.1.3 Inactive State..................................................................................... 9-90
27 9.6.6.1.4 Variable Rate State ............................................................................ 9-90
28 9.6.6.1.4.1 DRC and Packet Transmission Requirements .............................. 9-90
29 9.6.6.1.4.1.1 Access Terminal Requirements............................................... 9-90
30 9.6.6.1.4.1.2 Access Network Requirements................................................ 9-92
31 9.6.6.1.4.2 Transitions from the Variable Rate State ...................................... 9-93
32 9.6.6.1.5 Fixed Rate State ................................................................................ 9-93
xlviii
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.6.6.1.5.1 DRC Requirements.......................................................................9-94

2 9.6.6.1.5.2 Packet Transmission ....................................................................9-94
3 9.6.6.1.5.3 Transitions from the Fixed Rate State...........................................9-94
4 9.6.6.1.6 Supervision Procedures......................................................................9-95
5 9.6.6.1.6.1 DRC Supervision ..........................................................................9-95
6 9.6.6.1.6.2 ForwardTrafficValid Monitoring ....................................................9-95
7 9.6.6.2 Trailer and Message Formats ...................................................................9-96
8 9.6.6.2.1 MAC Layer Trailer ..............................................................................9-96
9 9.6.6.2.2 FixedModeEnable...............................................................................9-96
10 9.6.6.2.3 FixedModeXoff ...................................................................................9-97
12 9.6.6.3.1 Commands Sent.................................................................................9-97
13 9.6.6.3.2 Indications .........................................................................................9-97
15 9.6.7.1 Simple Attributes .....................................................................................9-98
16 9.6.7.2 Complex Attributes ..................................................................................9-98
17 9.6.7.2.1 DRCLock Attribute .............................................................................9-98
18 9.6.7.2.2 HandoffDelays Attribute...................................................................9-100
21 9.7 Enhanced Forward Traffic Channel MAC Protocol..............................................9-102
22 9.7.1 Overview......................................................................................................9-102
23 9.7.2 Primitives and Public Data...........................................................................9-103
24 9.7.2.1 Commands ............................................................................................9-103
25 9.7.2.2 Return Indications .................................................................................9-103
26 9.7.2.3 Public Data ............................................................................................9-103
31 9.7.5.1 Procedures.............................................................................................9-104
xlix
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.7.5.3 Message Formats................................................................................... 9-105

5 9.7.6.1 Procedures ............................................................................................ 9-106
6 9.7.6.1.1 MAC Layer Packet............................................................................ 9-106
7 9.7.6.1.1.1 Description of MAC Layer packet types ...................................... 9-107
8 9.7.6.1.1.2 Construction of MAC Layer packets ........................................... 9-108
9 9.7.6.1.2 Preamble MAC Index ....................................................................... 9-112
10 9.7.6.1.3 Forward Traffic Channel Addressing ................................................ 9-113
11 9.7.6.1.4 Transmission Format of the Forward Traffic Channel....................... 9-113
12 9.7.6.1.5 Data Rate Control and Data Source Control Channels ..................... 9-114
14 9.7.6.1.6.1 Activate...................................................................................... 9-120
15 9.7.6.1.6.2 Deactivate .................................................................................. 9-120
16 9.7.6.1.7 Inactive State................................................................................... 9-121
17 9.7.6.1.8 Variable Rate State .......................................................................... 9-121
18 9.7.6.1.8.1 Packet Transmission and DRC Requirements ............................ 9-121
19 9.7.6.1.8.1.1 Access Terminal Requirements............................................. 9-121
20 9.7.6.1.8.1.2 Access Network Requirements.............................................. 9-121
21 9.7.6.1.8.2 Transitions from the Variable Rate State .................................... 9-122
22 9.7.6.1.9 Fixed DRC State .............................................................................. 9-122
23 9.7.6.1.9.1 Packet Transmission Requirements ........................................... 9-123
26 9.7.6.1.9.2 Transitions from the Fixed DRC State ........................................ 9-123
27 9.7.6.1.10 Supervision Procedures ................................................................. 9-124
28 9.7.6.1.10.1 DRC Supervision...................................................................... 9-124
29 9.7.6.1.10.2 ForwardTrafficValid Monitoring ................................................ 9-124
30 9.7.6.2 Message Formats................................................................................... 9-124
31 9.7.6.2.1 FixedModeEnable ............................................................................ 9-124
32 9.7.6.2.2 FixedModeXoff ................................................................................. 9-125
l
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.7.6.2.3 AttributeUpdateRequest...................................................................9-126
2 9.7.6.2.4 AttributeUpdateAccept .....................................................................9-126
3 9.7.6.2.5 AttributeUpdateReject ......................................................................9-127
4 9.7.6.3 Interface to Other Protocols ...................................................................9-127
5 9.7.6.3.1 Commands Sent...............................................................................9-127
6 9.7.6.3.2 Indications .......................................................................................9-127
7 9.7.7 Configuration Attributes ..............................................................................9-127
8 9.7.7.1 Simple Attributes ...................................................................................9-128
11 9.7.7.2.2 DRCTranslationOffset Attribute........................................................9-131
14 9.8 Multicarrier Forward Traffic Channel MAC Protocol...........................................9-135
15 9.8.1 Overview......................................................................................................9-135
17 9.8.2.1 Commands ............................................................................................9-136
19 9.8.2.3 Public Data ............................................................................................9-136
24 9.8.5.1 Procedures.............................................................................................9-137
26 9.8.5.3 Message Formats ...................................................................................9-138
30 9.8.6.1 Procedures.............................................................................................9-139
31 9.8.6.1.1 MAC Layer Packet ............................................................................9-139
32 9.8.6.1.1.1 Description of MAC Layer packet types.......................................9-140
li
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.8.6.1.1.2 Construction of MAC Layer packets ........................................... 9-141

2 9.8.6.1.2 Preamble MAC Index ....................................................................... 9-146
3 9.8.6.1.3 Forward Traffic Channel Addressing ................................................ 9-146
4 9.8.6.1.4 Transmission Format of the Forward Traffic Channel....................... 9-147
5 9.8.6.1.5 Data Rate Control and Data Source Control Channels ..................... 9-148
7 9.8.6.1.6.1 Activate...................................................................................... 9-158
8 9.8.6.1.6.2 Deactivate .................................................................................. 9-158
9 9.8.6.1.7 Inactive State................................................................................... 9-158
10 9.8.6.1.8 Variable Rate State .......................................................................... 9-159
11 9.8.6.1.8.1 Packet Transmission and DRC Requirements ............................ 9-159
14 9.8.6.1.8.2 Transitions from the Variable Rate State .................................... 9-159
15 9.8.6.1.9 Fixed DRC State .............................................................................. 9-160
16 9.8.6.1.9.1 Packet Transmission Requirements ........................................... 9-160
19 9.8.6.1.9.2 Transitions from the Fixed DRC State ........................................ 9-161
20 9.8.6.1.10 Supervision Procedures ................................................................. 9-162
21 9.8.6.1.10.1 DRC Supervision...................................................................... 9-162
22 9.8.6.1.10.2 ForwardTrafficValid Monitoring ................................................ 9-163
23 9.8.6.2 Message Formats................................................................................... 9-163
24 9.8.6.2.1 FixedModeEnable ............................................................................ 9-163
25 9.8.6.2.2 FixedModeXoff ................................................................................. 9-165
30 9.8.6.3.1 Commands Sent .............................................................................. 9-167
31 9.8.6.3.2 Indications....................................................................................... 9-167
lii
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.8.7.1 Simple Attributes ...................................................................................9-168

4 9.8.7.2.2 TentativeDRCtoTxDRCMap Attribute................................................9-173
5 9.8.7.2.3 ATSupportedPacketFormats Attribute ..............................................9-183
6 9.8.7.2.4 ExtendedSpans Attribute .................................................................9-185
9 9.9 Default Reverse Traffic Channel MAC Protocol...................................................9-187
10 9.9.1 Overview......................................................................................................9-187
12 9.9.2.1 Commands ............................................................................................9-188
14 9.9.2.3 Public Data ............................................................................................9-188
18 9.9.4.2 Protocol Initialization for the InUse Protocol Instance.............................9-189
20 9.9.5.1 Procedures.............................................................................................9-189
22 9.9.5.3 Message Formats ...................................................................................9-190
26 9.9.6.1 Procedures.............................................................................................9-191
28 9.9.6.1.1.1 Activate ......................................................................................9-192
29 9.9.6.1.1.2 Deactivate ..................................................................................9-192
30 9.9.6.1.2 Reverse Traffic Channel Long Code Mask .........................................9-193
31 9.9.6.1.3 Inactive State ...................................................................................9-193
32 9.9.6.1.4 Setup State ......................................................................................9-193
liii
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.9.6.1.4.1 Access Terminal Requirements .................................................. 9-193

2 9.9.6.1.4.2 Access Network Requirements ................................................... 9-194
3 9.9.6.1.5 Open State....................................................................................... 9-194
4 9.9.6.1.5.1 Frame Offset Delay .................................................................... 9-194
5 9.9.6.1.5.2 Rate Control............................................................................... 9-194
6 9.9.6.1.5.3 Power Control ............................................................................ 9-196
7 9.9.6.2 Reverse Link Silence Interval ................................................................. 9-196
8 9.9.6.3 Trailer and Message Formats................................................................. 9-196
9 9.9.6.3.1 MAC Layer Trailer............................................................................ 9-196
10 9.9.6.3.2 RTCAck ........................................................................................... 9-197
11 9.9.6.3.3 BroadcastReverseRateLimit ............................................................. 9-197
12 9.9.6.3.4 UnicastReverseRateLimit ................................................................. 9-198
14 9.9.6.4.1 Commands Sent .............................................................................. 9-199
15 9.9.6.4.2 Indications....................................................................................... 9-199
17 9.9.7.1 PowerParameters Attribute .................................................................... 9-199
18 9.9.7.2 RateParameters Attribute ...................................................................... 9-201
21 9.9.9.1 LongCodeMask Parameter ..................................................................... 9-204
22 9.10 Subtype 1 Reverse Traffic Channel MAC Protocol ............................................ 9-205
23 9.10.1 Overview ................................................................................................... 9-205
25 9.10.2.1 Commands .......................................................................................... 9-206
27 9.10.2.3 Public Data.......................................................................................... 9-206
32 9.10.5.1 Procedures .......................................................................................... 9-207
liv
3GPP2 C.S0024-B v2.0
CONTENTS

2 9.10.5.3 Message Formats .................................................................................9-208
6 9.10.6.1 Procedures...........................................................................................9-209
8 9.10.6.1.1.1 Activate ....................................................................................9-210
9 9.10.6.1.1.2 Deactivate ................................................................................9-210
10 9.10.6.1.2 Reverse Traffic Channel Long Code Mask .......................................9-210
11 9.10.6.1.3 Inactive State .................................................................................9-211
12 9.10.6.1.4 Setup State ....................................................................................9-211
13 9.10.6.1.4.1 Access Terminal Requirements.................................................9-211
14 9.10.6.1.4.2 Access Network Requirements..................................................9-212
15 9.10.6.1.5 Open State .....................................................................................9-212
16 9.10.6.1.5.1 Frame Offset Delay...................................................................9-212
17 9.10.6.1.5.2 Rate Control .............................................................................9-212
18 9.10.6.1.5.3 Power Control...........................................................................9-213
19 9.10.6.2 Reverse Link Silence Interval ...............................................................9-213
20 9.10.6.3 Trailer and Message Formats ...............................................................9-214
21 9.10.6.3.1 MAC Layer Trailer ..........................................................................9-214
22 9.10.6.3.2 RTCAck ..........................................................................................9-214
23 9.10.6.3.3 BroadcastReverseRateLimit............................................................9-215
24 9.10.6.3.4 UnicastReverseRateLimit................................................................9-216
25 9.10.6.3.5 AttributeUpdateRequest .................................................................9-217
26 9.10.6.3.6 AttributeUpdateAccept ...................................................................9-218
27 9.10.6.3.7 AttributeUpdateReject ....................................................................9-218
29 9.10.6.4.1 Commands Sent.............................................................................9-218
30 9.10.6.4.2 Indications .....................................................................................9-219
32 9.10.7.1 PowerParameters Attribute ..................................................................9-219
lv
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.10.7.2 RateParameters Attribute .................................................................... 9-221

4 9.10.9.1 LongCodeMask Parameter ................................................................... 9-223
8 9.12.1 Overview ................................................................................................... 9-279
10 9.12.2.1 Commands .......................................................................................... 9-280
12 9.12.2.3 Public Data.......................................................................................... 9-281
17 9.12.5.1 Procedures .......................................................................................... 9-282
18 9.12.5.2 Commit Procedures ............................................................................. 9-282
19 9.12.5.3 Message Formats................................................................................. 9-283
20 9.12.5.3.1 ConfigurationRequest .................................................................... 9-283
21 9.12.5.3.2 ConfigurationResponse .................................................................. 9-283
22 9.12.6 Procedures and Messages for the InUse Instance of the Protocol ............... 9-284
23 9.12.6.1 Procedures .......................................................................................... 9-284
24 9.12.6.1.1 MAC Layer Packet.......................................................................... 9-284
25 9.12.6.1.2 Command Processing .................................................................... 9-284
26 9.12.6.1.2.1 Activate.................................................................................... 9-284
27 9.12.6.1.2.2 Deactivate ................................................................................ 9-285
28 9.12.6.1.3 Reverse Traffic Channel Long Code Mask....................................... 9-285
29 9.12.6.1.4 Inactive State................................................................................. 9-285
30 9.12.6.1.5 Setup State.................................................................................... 9-286
31 9.12.6.1.5.1 Access Terminal Requirements ................................................ 9-286
32 9.12.6.1.5.2 Access Network Requirements ................................................. 9-286
lvi
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.12.6.1.6 Open State .....................................................................................9-286

3 9.12.6.1.6.1.1 Packet size and Transmission Mode Selection
4 Requirements ......................................................................................9-300
5 9.12.6.1.6.1.1.1 Procedures....................................................................9-300
6 9.12.6.1.6.1.1.2 Requirements ...............................................................9-302
7 9.12.6.1.6.1.2 Request message ................................................................9-303
8 9.12.6.1.6.1.3 Grant message ...................................................................9-303
9 9.12.6.1.6.1.4 Power Control .....................................................................9-304
10 9.12.6.1.6.1.5 Reverse Link Silence Interval ..............................................9-304
12 9.12.6.1.6.2.1 Grant Message ...................................................................9-305
14 9.12.6.2.1 MAC Layer Trailer ..........................................................................9-305
15 9.12.6.2.2 RTCAck ..........................................................................................9-306
16 9.12.6.2.3 Request..........................................................................................9-306
17 9.12.6.2.4 Grant .............................................................................................9-307
18 9.12.6.2.5 AttributeUpdateRequest .................................................................9-309
19 9.12.6.2.6 AttributeUpdateAccept ...................................................................9-309
20 9.12.6.2.7 AttributeUpdateReject ....................................................................9-310
22 9.12.6.3.1 Commands Sent.............................................................................9-310
23 9.12.6.3.2 Indications .....................................................................................9-310
25 9.12.7.1 Simple Attributes .................................................................................9-312
26 9.12.7.2 Complex Attributes ..............................................................................9-320
27 9.12.7.2.1 AssociatedFlowsNN Attribute..........................................................9-320
28 9.12.7.2.2 AuxiliaryPilotChannelParameters Attribute ....................................9-322
29 9.12.7.2.3 BucketFactorNN Attribute ..............................................................9-323
30 9.12.7.2.4 CommonPowerParameters Attribute...............................................9-327
31 9.12.7.2.5 MaxNumSubPackets Attribute .......................................................9-328
32 9.12.7.2.6 PermittedPayload Attribute ............................................................9-330
33 9.12.7.2.7 PilotStrength Attribute ...................................................................9-340
lvii
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.12.7.2.8 PowerParameters128 Attribute ...................................................... 9-342

2 9.12.7.2.9 PowerParameters256 Attribute ...................................................... 9-344
3 9.12.7.2.10 PowerParameters512 Attribute .................................................... 9-346
5 9.12.7.2.12 PowerParameters1024 Attribute .................................................. 9-351
12 9.12.7.2.19 PowerParameters12288 Attribute ................................................ 9-366
13 9.12.7.2.20 RequestParameters Attribute ....................................................... 9-368
14 9.12.7.2.21 RRIChannelPowerParameters Attribute........................................ 9-369
15 9.12.7.2.22 T2PInflowRangeNN Attribute........................................................ 9-370
16 9.12.7.2.23 T2PTransitionFunctionNN Attribute ............................................. 9-371
17 9.12.7.2.24 TxT2Pmax Attribute ..................................................................... 9-377
18 9.12.7.2.25 MaxMACFlows Attribute .............................................................. 9-378
21 9.12.9.1 LongCodeMask Parameter ................................................................... 9-380
22 9.13 Multicarrier Reverse Traffic Channel MAC Protocol ......................................... 9-382
23 9.13.1 Overview ................................................................................................... 9-382
25 9.13.2.1 Commands .......................................................................................... 9-383
27 9.13.2.3 Public Data.......................................................................................... 9-384
32 9.13.5.1 Procedures .......................................................................................... 9-385
lviii
3GPP2 C.S0024-B v2.0
CONTENTS

2 9.13.5.3 Message Formats .................................................................................9-386
6 9.13.6.1 Procedures...........................................................................................9-387
7 9.13.6.1.1 MAC Layer Packet ..........................................................................9-387
9 9.13.6.1.2.1 Activate ....................................................................................9-387
10 9.13.6.1.2.2 Deactivate ................................................................................9-388
11 9.13.6.1.3 Reverse Traffic Channel Long Code Mask .......................................9-388
12 9.13.6.1.4 Inactive State .................................................................................9-389
13 9.13.6.1.5 Setup State ....................................................................................9-389
16 9.13.6.1.6 Open State .....................................................................................9-390
18 9.13.6.1.6.1.1 Packet size and Transmission Mode Selection
19 Requirements ......................................................................................9-407
20 9.13.6.1.6.1.1.1 Procedures for Reverse CDMA Channel r ......................9-408
21 9.13.6.1.6.1.1.2 Requirements for Reverse CDMA Channel r ..................9-410
22 9.13.6.1.6.1.2 Messages ............................................................................9-412
23 9.13.6.1.6.1.2.1 Request message ..........................................................9-412
24 9.13.6.1.6.1.3 Grant message ...................................................................9-412
25 9.13.6.1.6.1.3.1 CarrierRequest message ...............................................9-412
26 9.13.6.1.6.1.3.2 Reverse CDMA Channel Dropping.................................9-412
27 9.13.6.1.6.1.4 Reverse Logical Channels ...................................................9-413
28 9.13.6.1.6.1.5 Power Control .....................................................................9-413
29 9.13.6.1.6.1.6 Reverse Link Silence Interval ..............................................9-413
31 9.13.6.1.6.2.1 ReverseCDMAChannelDropped message ............................9-414
32 9.13.6.1.6.2.2 Grant Message ...................................................................9-414
lix
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.13.6.2.1 MAC Layer Trailer .......................................................................... 9-415

2 9.13.6.2.2 RTCAck ......................................................................................... 9-415
3 9.13.6.2.3 CarrierRequest .............................................................................. 9-416
4 9.13.6.2.4 ReverseCDMAChannelDropped...................................................... 9-417
5 9.13.6.2.5 ReverseCDMAChannelDroppedAck ................................................ 9-418
6 9.13.6.2.6 Request ......................................................................................... 9-419
7 9.13.6.2.7 Grant............................................................................................. 9-420
8 9.13.6.2.8 AttributeUpdateRequest................................................................. 9-422
9 9.13.6.2.9 AttributeUpdateAccept................................................................... 9-423
10 9.13.6.2.10 AttributeUpdateReject.................................................................. 9-423
11 9.13.6.3 Interface to Other Protocols ................................................................. 9-424
12 9.13.6.3.1 Commands Sent ............................................................................ 9-424
13 9.13.6.3.2 Indications..................................................................................... 9-424
14 9.13.7 Configuration Attributes............................................................................ 9-424
15 9.13.7.1 Simple Attributes................................................................................. 9-425
16 9.13.7.2 Complex Attributes.............................................................................. 9-434
17 9.13.7.2.1 AssociatedFlowsNN Attribute ......................................................... 9-434
18 9.13.7.2.2 AssociatedFlowConfigurationsNC Attribute .................................... 9-435
19 9.13.7.2.3 AssociatedATConfigurationsCC Attribute ....................................... 9-436
20 9.13.7.2.4 AuxiliaryPilotChannelParameters Attribute .................................... 9-437
21 9.13.7.2.5 BucketFactorNN Attribute.............................................................. 9-438
22 9.13.7.2.6 CommonPowerParameters Attribute .............................................. 9-442
23 9.13.7.2.7 DataTokenBucketNN Attribute....................................................... 9-443
24 9.13.7.2.8 MaxNumSubPacketsCC Attribute .................................................. 9-444
25 9.13.7.2.9 PermittedPayload Attribute ............................................................ 9-446
26 9.13.7.2.10 PilotStrengthConfigXX Attribute................................................... 9-455
lx
3GPP2 C.S0024-B v2.0
CONTENTS
1 9.13.7.2.17 PowerParameters2048 Attribute...................................................9-471

6 9.13.7.2.22 PowerParameters12288 Attribute .................................................9-482
7 9.13.7.2.23 RequestParameters Attribute .......................................................9-484
8 9.13.7.2.24 RRIChannelPowerParameters Attribute ........................................9-485
9 9.13.7.2.25 T2PInflowRangeConfigXX Attribute ..............................................9-486
10 9.13.7.2.26 T2PTransitionFunctionConfigXX Attribute....................................9-487
11 9.13.7.2.27 TxT2PmaxConfigXX Attribute .......................................................9-493
12 9.13.7.2.28 MaxMACFlows Attribute...............................................................9-495
15 9.13.9.1 LongCodeMask Parameter....................................................................9-496
16 10 Default (Subtype 0) and Subtype 1 Physical Layer Protocol .....................................10-1
17 10.1 Default (Subtype 0) and Subtype 1 Physical Layer Protocol Instance .................10-1
18 10.1.1 Overview......................................................................................................10-1
20 10.1.2.1 Commands ............................................................................................10-1
22 10.1.2.3 Public Data ............................................................................................10-1
26 10.1.4.2 Protocol Initialization for the InUse Protocol Instance of the Subtype 1
27 Physical Layer Protocol ..................................................................................10-2
29 10.1.5.1 Procedures.............................................................................................10-2
30 10.1.5.2 Commit Procedures................................................................................10-2
31 10.1.5.3 Message Formats ...................................................................................10-3
lxi
3GPP2 C.S0024-B v2.0
CONTENTS
2 10.1.6.1 Procedures ............................................................................................ 10-4
3 10.1.6.2 Message Formats................................................................................... 10-4
5 10.1.6.3.1 Commands ...................................................................................... 10-4
6 10.1.6.3.2 Indications....................................................................................... 10-4
9 10.1.8.1 Protocol Numeric Constants for the Default (Subtype 0) Physical
10 Layer Protocol ................................................................................................ 10-4
11 10.1.8.2 Protocol Numeric Constants for the Subtype 1 Physical Layer Protocol .. 10-4
13 10.2 Physical Layer Packets ...................................................................................... 10-6
14 10.2.1 Overview ..................................................................................................... 10-6
15 10.2.2 Physical Layer Packet Formats .................................................................... 10-6
16 10.2.2.1 Control Channel Physical Layer Packet Format...................................... 10-6
17 10.2.2.2 Access Channel Physical Layer Packet Format....................................... 10-6
18 10.2.2.3 Forward Traffic Channel Physical Layer Packet Format ......................... 10-8
19 10.2.2.4 Reverse Traffic Channel Physical Layer Packet Format .......................... 10-9
20 10.2.3 Bit Transmission Order ............................................................................. 10-10
21 10.2.4 Computation of the FCS Bits ..................................................................... 10-10
22 10.3 Access Terminal Requirements........................................................................ 10-12
23 10.3.1 Transmitter ............................................................................................... 10-12
24 10.3.1.1 Frequency Parameters ......................................................................... 10-12
25 10.3.1.1.1 Frequency Tolerance...................................................................... 10-12
26 10.3.1.2 Power Output Characteristics .............................................................. 10-12
27 10.3.1.2.1 Output Power Requirements of Reverse Channels.......................... 10-12
28 10.3.1.2.1.1 Access Channel Output Power ................................................. 10-12
29 10.3.1.2.1.2 Reverse Traffic Channel Output Power ..................................... 10-12
30 10.3.1.2.2 Maximum Output Power ................................................................ 10-12
31 10.3.1.2.3 Output Power Limits...................................................................... 10-13
32 10.3.1.2.3.1 Minimum Controlled Output Power.......................................... 10-13
lxii
3GPP2 C.S0024-B v2.0
CONTENTS
1 10.3.1.2.3.2 Standby Output Power .............................................................10-13

2 10.3.1.2.4 Controlled Output Power................................................................10-13
3 10.3.1.2.4.1 Estimated Open-Loop Output Power ........................................10-13
4 10.3.1.2.4.2 Closed-Loop Output Power .......................................................10-15
5 10.3.1.2.5 Power Transition Characteristics....................................................10-15
6 10.3.1.2.5.1 Open-Loop Estimation..............................................................10-15
7 10.3.1.2.5.2 Closed-Loop Correction ............................................................10-16
8 10.3.1.3 Modulation Characteristics ..................................................................10-16
9 10.3.1.3.1 Reverse Channel Structure ............................................................10-16
10 10.3.1.3.1.1 Modulation Parameters ............................................................10-22
11 10.3.1.3.1.2 Data Rates ...............................................................................10-23
12 10.3.1.3.2 Access Channel..............................................................................10-23
13 10.3.1.3.3 Reverse Traffic Channel .................................................................10-26
14 10.3.1.3.3.1 Pilot Channel............................................................................10-26
15 10.3.1.3.3.2 Data Channel ...........................................................................10-26
16 10.3.1.3.3.3 Pilot Channel............................................................................10-27
17 10.3.1.3.3.4 Reverse Rate Indicator Channel................................................10-27
18 10.3.1.3.3.5 Data Rate Control Channel.......................................................10-28
19 10.3.1.3.3.6 ACK Channel............................................................................10-31
20 10.3.1.3.3.7 Data Channel ...........................................................................10-31
21 10.3.1.3.4 Encoding........................................................................................10-32
22 10.3.1.3.4.1 Reverse Link Encoder Structure and Parameters......................10-32
23 10.3.1.3.4.2 Turbo Encoding........................................................................10-32
24 10.3.1.3.4.2.1 Turbo Encoders ..................................................................10-33
25 10.3.1.3.4.2.2 Turbo Code Termination .....................................................10-33
26 10.3.1.3.4.2.3 Turbo Interleavers ..............................................................10-35
27 10.3.1.3.5 Channel Interleaving ......................................................................10-39
28 10.3.1.3.6 Sequence Repetition.......................................................................10-39
29 10.3.1.3.7 Orthogonal Covers .........................................................................10-40
30 10.3.1.3.8 Quadrature Spreading ...................................................................10-40
31 10.3.1.3.8.1 Access Terminal Common Short-Code PN Sequences ...............10-41
32 10.3.1.3.8.2 Long Codes...............................................................................10-42
lxiii
3GPP2 C.S0024-B v2.0
CONTENTS
1 10.3.1.3.8.3 Baseband Filtering ................................................................... 10-44

2 10.3.1.4 Closed-Loop Power-Control Operation ................................................. 10-45
3 10.3.1.5 Reception of the DRCLock Channel ..................................................... 10-46
4 10.3.1.6 Reception of the Reverse Activity Channel ........................................... 10-46
5 10.3.1.7 Synchronization and Timing ................................................................ 10-46
6 10.4 Access Network Requirements......................................................................... 10-48
7 10.4.1 Transmitter ............................................................................................... 10-48
11 10.4.1.3 Modulation Characteristics.................................................................. 10-48
12 10.4.1.3.1 Forward Channel Structure ........................................................... 10-48
13 10.4.1.3.1.1 Modulation Parameters ............................................................ 10-53
14 10.4.1.3.1.2 Data Rates ............................................................................... 10-56
15 10.4.1.3.2 Forward Link Channels ................................................................. 10-56
16 10.4.1.3.2.1 Pilot Channel ........................................................................... 10-56
17 10.4.1.3.2.1.1 Modulation......................................................................... 10-56
18 10.4.1.3.2.1.2 Orthogonal Spreading ........................................................ 10-56
19 10.4.1.3.2.1.3 Quadrature Spreading........................................................ 10-56
20 10.4.1.3.2.2 Forward MAC Channel............................................................. 10-57
21 10.4.1.3.2.2.1 Reverse Power Control Channel.......................................... 10-58
22 10.4.1.3.2.2.2 DRCLock Channel.............................................................. 10-58
23 10.4.1.3.2.2.3 Reverse Activity Channel .................................................... 10-59
24 10.4.1.3.2.3 Forward Traffic Channel .......................................................... 10-59
25 10.4.1.3.2.3.1 Forward Traffic Channel Preamble ..................................... 10-59
26 10.4.1.3.2.3.2 Encoding............................................................................ 10-60
27 10.4.1.3.2.3.2.1 Turbo Encoder ............................................................. 10-61
28 10.4.1.3.2.3.2.2 Turbo Interleaver.......................................................... 10-64
29 10.4.1.3.2.3.3 Scrambling......................................................................... 10-68
30 10.4.1.3.2.3.4 Channel Interleaving .......................................................... 10-69
31 10.4.1.3.2.3.4.1 Symbol Reordering ....................................................... 10-69
32 10.4.1.3.2.3.4.2 Symbol Permuting ........................................................ 10-70
lxiv
3GPP2 C.S0024-B v2.0
CONTENTS
1 10.4.1.3.2.3.5 Modulation .........................................................................10-71

2 10.4.1.3.2.3.5.1 QPSK Modulation .........................................................10-71
3 10.4.1.3.2.3.5.2 8-PSK Modulation.........................................................10-72
4 10.4.1.3.2.3.5.3 16-QAM Modulation .....................................................10-73
5 10.4.1.3.2.3.6 Sequence Repetition and Symbol Puncturing......................10-75
6 10.4.1.3.2.3.7 Symbol Demultiplexing.......................................................10-76
7 10.4.1.3.2.3.8 Walsh Channel Assignment ................................................10-77
8 10.4.1.3.2.3.9 Walsh Channel Scaling.......................................................10-77
9 10.4.1.3.2.3.10 Walsh Chip Level Summing ..............................................10-77
10 10.4.1.3.2.4 Control Channel .......................................................................10-77
11 10.4.1.3.3 Time-Division Multiplexing.............................................................10-77
12 10.4.1.3.4 Quadrature Spreading ...................................................................10-80
13 10.4.1.3.5 Filtering .........................................................................................10-81
14 10.4.1.3.5.1 Baseband Filtering ...................................................................10-81
15 10.4.1.3.5.2 Phase Characteristics ...............................................................10-83
16 10.4.1.3.6 Synchronization and Timing...........................................................10-84
17 10.4.1.3.6.1 Timing Reference Source ..........................................................10-84
18 10.4.1.3.6.2 Sector Transmission Time ........................................................10-84
19 11 Subtype 2 Physical Layer ........................................................................................11-1
20 11.1 Subtype 2 Physical Layer Protocol Instance .......................................................11-1
21 11.1.1 Overview......................................................................................................11-1
23 11.1.2.1 Commands ............................................................................................11-1
25 11.1.2.3 Public Data ............................................................................................11-1
30 11.1.5.1 Procedures.............................................................................................11-2
31 11.1.5.2 Commit Procedures................................................................................11-2
32 11.1.5.3 Message Formats ...................................................................................11-3
lxv
3GPP2 C.S0024-B v2.0
CONTENTS

4 11.1.6.1 Procedures ............................................................................................ 11-4
5 11.1.6.2 Message Formats................................................................................... 11-4
7 11.1.6.3.1 Commands ...................................................................................... 11-4
8 11.1.6.3.2 Indications....................................................................................... 11-4
12 11.2 Physical Layer Packets ...................................................................................... 11-5
13 11.2.1 Overview ..................................................................................................... 11-5
14 11.2.2 Physical Layer Packet Formats .................................................................... 11-5
15 11.2.2.1 Control Channel Physical Layer Packet Format...................................... 11-5
16 11.2.2.2 Access Channel Physical Layer Packet Format....................................... 11-6
17 11.2.2.3 Forward Traffic Channel Physical Layer Packet Format ......................... 11-6
18 11.2.2.4 Reverse Traffic Channel Physical Layer Packet Format .......................... 11-7
19 11.2.3 Bit Transmission Order ............................................................................... 11-8
20 11.2.4 Computation of the FCS Bits ....................................................................... 11-8
21 11.3 Access Terminal Requirements........................................................................ 11-10
22 11.3.1 Transmitter ............................................................................................... 11-10
26 11.3.1.2.1 Output Power Requirements of Reverse Channels.......................... 11-10
27 11.3.1.2.1.1 Access Channel Output Power ................................................. 11-10
28 11.3.1.2.1.2 Reverse Traffic Channel Output Power ..................................... 11-10
29 11.3.1.2.2 Maximum Output Power ................................................................ 11-10
30 11.3.1.2.3 Output Power Limits...................................................................... 11-11
31 11.3.1.2.3.1 Minimum Controlled Output Power.......................................... 11-11
32 11.3.1.2.3.2 Standby Output Power............................................................. 11-11
lxvi
3GPP2 C.S0024-B v2.0
CONTENTS

4 11.3.1.2.5 Power Transition Characteristics....................................................11-14
9 11.3.1.3.1.1 Modulation Parameters ............................................................11-25
10 11.3.1.3.1.2 Data Rates ...............................................................................11-26
11 11.3.1.3.2 Access Channel..............................................................................11-27
12 11.3.1.3.2.1 Pilot Channel............................................................................11-28
13 11.3.1.3.2.2 Data Channel ...........................................................................11-28
14 11.3.1.3.3 Reverse Traffic Channel .................................................................11-28
15 11.3.1.3.3.1 Pilot Channel............................................................................11-29
16 11.3.1.3.3.2 Reverse Rate Indicator Channel................................................11-29
17 11.3.1.3.3.3 Data Source Control Channel...................................................11-30
18 11.3.1.3.3.4 Data Rate Control Channel.......................................................11-32
19 11.3.1.3.3.5 ACK Channel............................................................................11-35
20 11.3.1.3.3.6 Data Channel ...........................................................................11-36
21 11.3.1.3.3.7 Auxiliary Pilot Channel.............................................................11-36
22 11.3.1.3.4 Encoding........................................................................................11-37
23 11.3.1.3.4.1 Reverse Link Encoder Structure and Parameters......................11-37
24 11.3.1.3.4.2 Turbo Encoding........................................................................11-38
25 11.3.1.3.4.2.1 Turbo Encoders ..................................................................11-39
26 11.3.1.3.4.2.2 Turbo Code Termination .....................................................11-39
27 11.3.1.3.4.2.3 Turbo Interleavers ..............................................................11-42
28 11.3.1.3.5 Scrambling for Reverse Traffic Channel Physical Layer Packets......11-46
29 11.3.1.3.6 Channel Interleaving for Access Channel Physical Layer Packets ...11-47
30 11.3.1.3.7 Channel Interleaving for Reverse Traffic Channel Physical Layer
31 Packets .....................................................................................................11-48
32 11.3.1.3.7.1 Symbol Reordering ...................................................................11-48
33 11.3.1.3.7.2 Matrix Interleaving ...................................................................11-49
lxvii
3GPP2 C.S0024-B v2.0
CONTENTS
1 11.3.1.3.8 Orthogonal Covers ......................................................................... 11-50

2 11.3.1.3.9 Modulation .................................................................................... 11-51
3 11.3.1.3.9.1 B4 Modulation ......................................................................... 11-51
4 11.3.1.3.9.2 Q4 Modulation ......................................................................... 11-52
5 11.3.1.3.9.3 Q2 Modulation ......................................................................... 11-52
6 11.3.1.3.9.4 Q4Q2 Modulation .................................................................... 11-53
7 11.3.1.3.9.5 E4E2 Modulation ..................................................................... 11-53
8 11.3.1.3.10 Sequence Repetition for Access Channel Physical Layer Packets.. 11-57
9 11.3.1.3.11 Sequence Repetition and Symbol Selection for Reverse Traffic
10 Channel Physical Layer Packets................................................................ 11-57
11 11.3.1.3.12 Quadrature Spreading ................................................................. 11-57
12 11.3.1.3.12.1 Access Terminal Common Short-Code PN Sequences ............. 11-58
13 11.3.1.3.12.2 Long Codes ............................................................................ 11-59
14 11.3.1.3.12.3 Baseband Filtering ................................................................. 11-61
15 11.3.2 Receiver..................................................................................................... 11-62
16 11.3.2.1 Closed-Loop Power-Control Operation ................................................. 11-62
17 11.3.2.2 Reception of the DRCLock Channel ..................................................... 11-63
18 11.3.2.3 Reception of the Reverse Activity Channel ........................................... 11-63
19 11.3.2.4 Reception of ARQ Channel................................................................... 11-64
20 11.3.3 Synchronization and Timing ...................................................................... 11-68
21 11.4 Access Network Requirements......................................................................... 11-70
22 11.4.1 Transmitter ............................................................................................... 11-70
26 11.4.1.3 Modulation Characteristics.................................................................. 11-70
27 11.4.1.3.1 Forward Channel Structure ........................................................... 11-70
29 11.4.1.3.1.2 Data Rates ............................................................................... 11-76
30 11.4.1.3.2 Forward Link Channels ................................................................. 11-77
31 11.4.1.3.2.1 Pilot Channel ........................................................................... 11-77
32 11.4.1.3.2.1.1 Modulation......................................................................... 11-77
lxviii
3GPP2 C.S0024-B v2.0
CONTENTS
1 11.4.1.3.2.1.2 Orthogonal Spreading.........................................................11-77

2 11.4.1.3.2.1.3 Quadrature Spreading ........................................................11-77
3 11.4.1.3.2.2 Forward MAC Channel .............................................................11-77
4 11.4.1.3.2.2.1 Reverse Power Control Channel ..........................................11-81
5 11.4.1.3.2.2.2 DRCLock Channel ..............................................................11-81
6 11.4.1.3.2.2.3 Reverse Activity Channel ....................................................11-82
7 11.4.1.3.2.2.4 ARQ Channel......................................................................11-82
8 11.4.1.3.2.3 Forward Traffic Channel...........................................................11-84
9 11.4.1.3.2.3.1 Forward Traffic Channel Preamble......................................11-84
10 11.4.1.3.2.3.2 Encoding ............................................................................11-86
11 11.4.1.3.2.3.2.1 Turbo Encoder..............................................................11-88
12 11.4.1.3.2.3.2.2 Turbo Interleaver ..........................................................11-91
13 11.4.1.3.2.3.3 Scrambling .........................................................................11-95
14 11.4.1.3.2.3.4 Channel Interleaving ..........................................................11-97
15 11.4.1.3.2.3.4.1 Symbol Reordering........................................................11-98
16 11.4.1.3.2.3.4.2 Matrix Interleaving........................................................11-98
17 11.4.1.3.2.3.4.3 Short Sequence Repetition ............................................11-99
18 11.4.1.3.2.3.5 Modulation .......................................................................11-101
19 11.4.1.3.2.3.5.1 QPSK Modulation .......................................................11-101
20 11.4.1.3.2.3.5.2 8-PSK Modulation.......................................................11-102
21 11.4.1.3.2.3.5.3 16-QAM Modulation ...................................................11-103
22 11.4.1.3.2.3.6 Sequence Repetition and Symbol Puncturing....................11-105
23 11.4.1.3.2.3.7 Symbol Demultiplexing.....................................................11-107
24 11.4.1.3.2.3.8 Walsh Channel Assignment ..............................................11-108
25 11.4.1.3.2.3.9 Walsh Channel Scaling.....................................................11-108
26 11.4.1.3.2.3.10 Walsh Chip Level Summing ............................................11-108
27 11.4.1.3.2.4 Control Channel .....................................................................11-108
28 11.4.1.3.3 Time-Division Multiplexing...........................................................11-108
29 11.4.1.3.4 Quadrature Spreading .................................................................11-115
30 11.4.1.3.5 Filtering .......................................................................................11-116
31 11.4.1.3.5.1 Baseband Filtering .................................................................11-116
32 11.4.1.3.5.2 Phase Characteristics .............................................................11-118
lxix
3GPP2 C.S0024-B v2.0
CONTENTS
1 11.4.1.3.6 Synchronization and Timing ........................................................ 11-119

2 11.4.1.3.6.1 Timing Reference Source........................................................ 11-119
3 11.4.1.3.6.2 Sector Transmission Time ...................................................... 11-119
4 12 SUBTYPE 3 Physical Layer...................................................................................... 12-1
5 12.1 Subtype 3 Physical Layer Protocol Instance....................................................... 12-1
6 12.1.1 Overview ..................................................................................................... 12-1
8 12.1.2.1 Commands ............................................................................................ 12-1
10 12.1.2.3 Public Data............................................................................................ 12-1
14 12.1.5 Procedures and Messages for the InConfiguration Instance of the Protocol .. 12-2
15 12.1.5.1 Procedures ............................................................................................ 12-2
16 12.1.5.2 Commit Procedures ............................................................................... 12-2
17 12.1.5.3 Message Formats................................................................................... 12-3
21 12.1.6.1 Procedures ............................................................................................ 12-4
22 12.1.6.2 Message Formats................................................................................... 12-4
27 12.1.6.3.1 Commands ...................................................................................... 12-5
28 12.1.6.3.2 Indications....................................................................................... 12-5
31 12.1.7.2 Complex Attributes................................................................................ 12-8
32 12.1.7.2.1 AdditionalCarriersInitTxPower Attribute .......................................... 12-8
lxx
3GPP2 C.S0024-B v2.0
CONTENTS
1 12.1.7.2.2 ReversePilotTransmitSlots Attribute ...............................................12-10

4 12.2 Physical Layer Packets ....................................................................................12-13
5 12.2.1 Overview....................................................................................................12-13
6 12.2.2 Physical Layer Packet Formats ..................................................................12-13
7 12.2.2.1 Control Channel Physical Layer Packet Format ....................................12-13
8 12.2.2.2 Access Channel Physical Layer Packet Format .....................................12-14
9 12.2.2.3 Forward Traffic Channel Physical Layer Packet Format........................12-14
10 12.2.2.4 Reverse Traffic Channel Physical Layer Packet Format.........................12-15
11 12.2.3 Bit Transmission Order .............................................................................12-16
12 12.2.4 Computation of the FCS Bits .....................................................................12-16
13 12.3 Access Terminal Requirements ........................................................................12-18
14 12.3.1 Transmitter................................................................................................12-18
15 12.3.1.1 Frequency Parameters .........................................................................12-18
16 12.3.1.1.1 Frequency Tolerance ......................................................................12-18
17 12.3.1.2 Power Output Characteristics ..............................................................12-18
18 12.3.1.2.1 Output Power Requirements of Reverse Channels ..........................12-18
19 12.3.1.2.1.1 Access Channel Output Power..................................................12-18
20 12.3.1.2.1.2 Reverse Traffic Channel Output Power .....................................12-18
21 12.3.1.2.2 Maximum Output Power ................................................................12-18
22 12.3.1.2.3 Output Power Limits ......................................................................12-19
23 12.3.1.2.3.1 Minimum Controlled Output Power ..........................................12-19
24 12.3.1.2.3.2 Standby Output Power .............................................................12-19
28 12.3.1.2.4.3 Power Transition Characteristics ..............................................12-25
lxxi
3GPP2 C.S0024-B v2.0
CONTENTS

2 12.3.1.3.1.2 Data Rates ............................................................................... 12-47
3 12.3.1.3.2 Access Channel ............................................................................. 12-48
4 12.3.1.3.2.1 Pilot Channel ........................................................................... 12-49
5 12.3.1.3.2.2 Data Channel........................................................................... 12-49
6 12.3.1.3.3 Reverse Traffic Channel ................................................................. 12-49
7 12.3.1.3.3.1 Pilot Channel ........................................................................... 12-50
8 12.3.1.3.3.2 Reverse Rate Indicator Channel ............................................... 12-50
9 12.3.1.3.3.3 Data Source Control Channel .................................................. 12-52
10 12.3.1.3.3.4 Data Rate Control Channel ...................................................... 12-56
11 12.3.1.3.3.5 ACK Channel ........................................................................... 12-61
12 12.3.1.3.3.6 Data Channel........................................................................... 12-64
13 12.3.1.3.3.7 Auxiliary Pilot Channel ............................................................ 12-65
14 12.3.1.3.4 Encoding ....................................................................................... 12-65
15 12.3.1.3.4.1 Reverse Link Encoder Structure and Parameters ..................... 12-65
16 12.3.1.3.4.2 Turbo Encoding ....................................................................... 12-67
17 12.3.1.3.4.2.1 Turbo Encoders.................................................................. 12-67
18 12.3.1.3.4.2.2 Turbo Code Termination..................................................... 12-68
19 12.3.1.3.4.2.3 Turbo Interleavers .............................................................. 12-70
20 12.3.1.3.5 Scrambling for Reverse Traffic Channel Physical Layer Packets ..... 12-74
21 12.3.1.3.6 Channel Interleaving for Access Channel Physical Layer Packets ... 12-75
22 12.3.1.3.7 Channel Interleaving for Reverse Traffic Channel Physical Layer
23 Packets ..................................................................................................... 12-76
24 12.3.1.3.7.1 Symbol Reordering................................................................... 12-76
25 12.3.1.3.7.2 Matrix Interleaving................................................................... 12-77
26 12.3.1.3.8 Orthogonal Covers ......................................................................... 12-78
27 12.3.1.3.9 Modulation .................................................................................... 12-79
28 12.3.1.3.9.1 B4 Modulation ......................................................................... 12-79
29 12.3.1.3.9.2 Q4 Modulation ......................................................................... 12-80
30 12.3.1.3.9.3 Q2 Modulation ......................................................................... 12-80
31 12.3.1.3.9.4 Q4Q2 Modulation .................................................................... 12-81
32 12.3.1.3.9.5 E4E2 Modulation ..................................................................... 12-81
lxxii
3GPP2 C.S0024-B v2.0
CONTENTS
1 12.3.1.3.10 Sequence Repetition for Access Channel Physical Layer Packets ..12-85
2 12.3.1.3.11 Sequence Repetition and Symbol Selection for Reverse Traffic
3 Channel Physical Layer Packets ................................................................12-85
4 12.3.1.3.12 Quadrature Spreading..................................................................12-85
5 12.3.1.3.12.1 Access Terminal Common Short-Code PN Sequences .............12-86
6 12.3.1.3.12.2 Long Codes.............................................................................12-87
7 12.3.1.3.12.3 Baseband Filtering .................................................................12-89
8 12.3.1.4 Discontinuous Transmission................................................................12-91
9 12.3.2 Receiver .....................................................................................................12-93
10 12.3.2.1 Closed-Loop Power-Control Operation..................................................12-93
11 12.3.2.2 Reception of the DRCLock Channel......................................................12-94
12 12.3.2.3 Reception of the Reverse Activity Channel............................................12-94
13 12.3.2.4 Reception of ARQ Channel ...................................................................12-94
14 12.3.3 Synchronization and Timing ....................................................................12-100
15 12.4 Access Network Requirements .......................................................................12-102
16 12.4.1 Transmitter..............................................................................................12-102
17 12.4.1.1 Frequency Parameters .......................................................................12-102
18 12.4.1.1.1 Frequency Tolerance ....................................................................12-102
19 12.4.1.2 Power Output Characteristics ............................................................12-102
20 12.4.1.3 Modulation Characteristics ................................................................12-102
21 12.4.1.3.1 Forward Channel Structure..........................................................12-102
22 12.4.1.3.1.1 Modulation Parameters ..........................................................12-107
23 12.4.1.3.1.2 Data Rates .............................................................................12-111
24 12.4.1.3.2 Forward Link Channels................................................................12-111
25 12.4.1.3.2.1 Pilot Channel..........................................................................12-111
26 12.4.1.3.2.1.1 Modulation .......................................................................12-112
27 12.4.1.3.2.1.2 Orthogonal Spreading.......................................................12-112
28 12.4.1.3.2.1.3 Quadrature Spreading ......................................................12-112
29 12.4.1.3.2.2 Forward MAC Channel ...........................................................12-112
30 12.4.1.3.2.2.1 Reverse Power Control Channel ........................................12-118
31 12.4.1.3.2.2.2 DRCLock Channel ............................................................12-119
32 12.4.1.3.2.2.3 Reverse Activity Channel ..................................................12-119
33 12.4.1.3.2.2.4 ARQ Channel....................................................................12-120
lxxiii
3GPP2 C.S0024-B v2.0
CONTENTS
1 12.4.1.3.2.3 Forward Traffic Channel ........................................................ 12-121

2 12.4.1.3.2.3.1 Forward Traffic Channel Preamble ................................... 12-121
3 12.4.1.3.2.3.2 Encoding.......................................................................... 12-126
4 12.4.1.3.2.3.2.1 Turbo Encoder ........................................................... 12-128
5 12.4.1.3.2.3.2.2 Turbo Interleaver........................................................ 12-131
6 12.4.1.3.2.3.3 Scrambling....................................................................... 12-135
7 12.4.1.3.2.3.4 Channel Interleaving ........................................................ 12-138
8 12.4.1.3.2.3.4.1 Symbol Reordering ..................................................... 12-138
9 12.4.1.3.2.3.4.2 Matrix Interleaving ..................................................... 12-139
10 12.4.1.3.2.3.4.3 Short Sequence Repetition ......................................... 12-140
11 12.4.1.3.2.3.5 Modulation....................................................................... 12-142
12 12.4.1.3.2.3.5.1 QPSK Modulation ....................................................... 12-142
13 12.4.1.3.2.3.5.2 8-PSK Modulation ...................................................... 12-143
14 12.4.1.3.2.3.5.3 16-QAM Modulation ................................................... 12-144
15 12.4.1.3.2.3.5.4 64-QAM Modulation ................................................... 12-146
16 12.4.1.3.2.3.6 Sequence Repetition and Symbol Puncturing ................... 12-149
17 12.4.1.3.2.3.7 Symbol Demultiplexing .................................................... 12-153
18 12.4.1.3.2.3.8 Walsh Channel Assignment.............................................. 12-153
19 12.4.1.3.2.3.9 Walsh Channel Scaling .................................................... 12-153
20 12.4.1.3.2.3.10 Walsh Chip Level Summing............................................ 12-154
21 12.4.1.3.2.4 Control Channel..................................................................... 12-154
22 12.4.1.3.3 Time-Division Multiplexing .......................................................... 12-154
23 12.4.1.3.4 Quadrature Spreading ................................................................. 12-162
24 12.4.1.3.5 Filtering ....................................................................................... 12-163
25 12.4.1.3.5.1 Baseband Filtering ................................................................. 12-163
26 12.4.1.3.5.2 Phase Characteristics ............................................................ 12-165
27 12.4.1.3.6 Synchronization and Timing ........................................................ 12-166
28 12.4.1.3.6.1 Timing Reference Source........................................................ 12-166
29 12.4.1.3.6.2 Sector Transmission Time ...................................................... 12-166
30 13 Common Algorithms and Data Structures............................................................... 13-1
31 13.1 Channel Record ................................................................................................ 13-1
32 13.2 Access Terminal Identifier Record ..................................................................... 13-3
lxxiv
3GPP2 C.S0024-B v2.0
CONTENTS
1 13.3 Attribute Record ................................................................................................13-3

2 13.4 Hash Function...................................................................................................13-5
3 13.5 Pseudorandom Number Generator ....................................................................13-5
4 13.5.1 General Procedures .....................................................................................13-5
5 13.5.2 Initialization ................................................................................................13-6
6 13.6 Sequence Number Validation.............................................................................13-6
7 13.7 Generic Configuration Protocol ..........................................................................13-6
8 13.7.1 Introduction ................................................................................................13-6
9 13.7.2 Procedures ..................................................................................................13-7
10 13.7.2.1 Configuration Negotiation ......................................................................13-7
11 13.7.3 Message Formats .........................................................................................13-8
12 13.7.3.1 ConfigurationRequest ............................................................................13-8
13 13.7.3.2 ConfigurationResponse ..........................................................................13-8
14 13.8 Session State Information Record ......................................................................13-9
15 13.9 SectorID Provisioning ......................................................................................13-11
16 13.9.1 Overview of Relevant Formats ....................................................................13-11
17 13.9.1.1 Global Unicast IPv6 Address Format ....................................................13-11
18 13.9.1.2 Site-Local Unicast IPv6 Address Format...............................................13-11
19 13.9.1.3 Link-Local Unicast IPv6 Address Format..............................................13-11
20 13.9.1.4 Reserved IPv6 Address Format.............................................................13-12
21 13.9.1.5 Modified EUI-64 Format.......................................................................13-12
22 13.9.2 SectorID Construction ...............................................................................13-13
23 13.9.2.1 Construction of Globally Unique SectorID ............................................13-13
24 13.9.2.1.1 SectorID Based On an IPv6 Unique Identifier .................................13-13
25 13.9.2.1.2 SectorID Not Based On an IPv6 Unique Identifier ...........................13-14
26 13.9.2.1.2.1 ANSI-41 Method .......................................................................13-15
27 13.9.2.1.2.2 GSM/UMTS Method .................................................................13-15
28 13.9.2.1.2.3 IPv4 Unique Identifier...............................................................13-16
29 13.9.2.2 Construction of Locally Unique SectorID..............................................13-16
30 13.10 Generic Attribute Update Protocol .................................................................13-17
31 13.10.1 Introduction ............................................................................................13-17
32 13.10.2 Procedures...............................................................................................13-17
lxxv
3GPP2 C.S0024-B v2.0
CONTENTS
1 13.10.2.1 Initiator Requirements....................................................................... 13-17

2 13.10.2.2 Responder Requirements................................................................... 13-18
3 13.10.3 Message Formats..................................................................................... 13-18
4 13.10.3.1 AttributeUpdateRequest .................................................................... 13-18
5 13.10.3.2 AttributeUpdateAccept ...................................................................... 13-19
6 13.10.3.3 AttributeUpdateReject ....................................................................... 13-19
7 13.10.4 Protocol Numeric Constants .................................................................... 13-19
8 13.11 Linear Interpolation....................................................................................... 13-20
9 13.12 Bi-linear Interpolation ................................................................................... 13-21
10 13.13 IIR filter implementation ............................................................................... 13-22
11 14 Assigned Names And Numbers ............................................................................... 14-1
12 14.1 Protocols ........................................................................................................... 14-1
lxxvi
3GPP2 C.S0024-B v2.0
FIGURES
1 Figure 1.3-1. Architecture Reference Model ....................................................................1-2

2 Figure 1.4.1-1. Air Interface Layering Architecture .........................................................1-2
3 Figure 1.5-1. Forward Channel Structure.......................................................................1-3
4 Figure 1.5-2. Reverse Channel Structure .......................................................................1-4
5 Figure 1.6.6-1. Default Protocols ....................................................................................1-8
6 Figure 1.6.6-2. Non-Default Protocols ..........................................................................1-10
7 Figure 1.14-1. CDMA System Time Line .......................................................................1-20
8 Figure 2.1.1-1. Default Signaling Layer Protocols ...........................................................2-1
9 Figure 2.1.3-1. Message Encapsulation (Non-fragmented) ..............................................2-2
10 Figure 2.1.3-2. Message Encapsulation (Fragmented).....................................................2-2
11 Figure 2.3.2-1. Sample Message Information..................................................................2-4
12 Figure 2.5.3-1. SNP Packet Structure .............................................................................2-8
13 Figure 2.6.4.2.3.3.1-1. SLP-D Transmit Sequence Number Variable.............................2-15
14 Figure 2.6.4.2.3.3.2-1. SLP Receive Sequence Number Variables .................................2-16
15 Figure 3.1.1-1. Default Packet Application Protocols ......................................................3-1
16 Figure 3.1.3-1. Default Packet Application Encapsulation ..............................................3-2
17 Figure 3.4.4.1.2-1. RLP Transmit Sequence Number Variable ........................................3-7
18 Figure 3.4.4.1.2-2. RLP Receive Sequence Number Variables .........................................3-8
19 Figure 3.6.1-1. Flow Control Protocol State Diagram (Access Terminal) ........................3-16
20 Figure 3.6.1-2. Flow Control Protocol State Diagram (Access Network) .........................3-16
21 Figure 4.1.1-1. Multi-Flow Packet Application Protocols .................................................4-1
22 Figure 4.1.3-1. Multi-Flow Packet Application Encapsulation.........................................4-2
23 Figure 4.4.4.1.1.2.5-1. RLP Reset Procedure Initiated by RLP Transmitter ...................4-10
24 Figure 4.4.4.1.1.2.5-2. RLP Reset Procedure Initiated by RLP Receiver.........................4-10
25 Figure 4.4.4.2.1-1. RLP Transmit Sequence Number Variable ......................................4-11
26 Figure 4.4.4.2.1-2. Reverse Reservation State Diagram (Access Terminal) ....................4-13
27 Figure 4.4.4.2.1-3. Forward Reservation State Diagram (Access Network) ....................4-13
28 Figure 4.4.4.2.2-1. RLP Receive Sequence Number Variables .......................................4-18
29 Figure 4.7.1-1. Flow Control Protocol State Diagram (Access Terminal) ........................4-44
30 Figure 4.7.1-2. Flow Control Protocol State Diagram (Access Network) .........................4-44
31 Figure 5.1.2-1. Stream Layer Encapsulation ..................................................................5-2
lxxvii
3GPP2 C.S0024-B v2.0
FIGURES
1 Figure 5.2.6-1. Stream Layer Packet Structure .............................................................. 5-6

2 Figure 6.1.1-1. Session Layer Protocols.......................................................................... 6-2
3 Figure 6.1.2-1. Session Layer Encapsulation ................................................................. 6-2
4 Figure 6.2.1-1. Default Session Management Protocol State Diagram (Access
5 Terminal).................................................................................................................. 6-3
7 Network)................................................................................................................... 6-4
8 Figure 6.3.1-1. Default Address Management Protocol State Diagram (Access
9 Terminal)................................................................................................................ 6-17
11 Network)................................................................................................................. 6-18
12 Figure 6.4.1-1. Default Session Configuration Protocol State Diagram (Access
13 Terminal)................................................................................................................ 6-41
15 Network)................................................................................................................. 6-41
16 Figure 6.4.9-1. Default Session Configuration Protocol: Extensive Negotiation
17 Procedure............................................................................................................... 6-70
18 Figure 6.4.9-2. Default Session Configuration Protocol: Minimal Negotiation
19 Procedure with Key Exchange ................................................................................ 6-71
20 Figure 6.4.9-3. Default Session Configuration Protocol: Negotiation of Multiple
21 Personalities........................................................................................................... 6-72
22 Figure 6.4.9-4. Default Session Configuration Protocol: Personality Change During
23 Connection............................................................................................................. 6-73
24 Figure 7.1.1-1. Connection Layer Protocols .................................................................... 7-3
25 Figure 7.1.2-1. Connection Layer Encapsulation (Format A) .......................................... 7-4
26 Figure 7.1.2-2. Connection Layer Encapsulation (Format B) .......................................... 7-4
27 Figure 7.2.1-1. Default Air Link Management Protocol State Diagram (Access
28 Terminal).................................................................................................................. 7-6
30 Network)................................................................................................................... 7-6
31 Figure 7.3.1-1. Default Initialization State Protocol State Diagram ............................... 7-21
32 Figure 7.4.1-1. Default Idle State Protocol State Diagram (Access Terminal) ................ 7-29
33 Figure 7.4.6.1.6-1. Connection Setup Exchange .......................................................... 7-39
34 Figure 7.5.1-1. Enhanced Idle State Protocol State Diagram (Access Terminal) ............ 7-45
35 Figure 7.5.6.1.7-1. Connection Setup Exchange .......................................................... 7-58
lxxviii
3GPP2 C.S0024-B v2.0
FIGURES
1 Figure 7.6.1-1. Quick Idle State Protocol State Diagram (Access Terminal) ...................7-71
2 Figure 7.6.6.1.7-1. Connection Setup Exchange...........................................................7-86
3 Figure 7.7.1-1. Default Connected State Protocol State Diagram (Access Terminal) ....7-102
4 Figure 7.7.1-2. Default Connected State Protocol State Diagram (Access Network) .....7-103
5 Figure 7.8.1-1. Default Route Update Protocol State Diagram ....................................7-111
6 Figure 7.9.1-1. Multicarrier Route Update Protocol State Diagram .............................7-172
7 Figure 7.10.3-1. Connection Layer Packet Structure (Format A) .................................7-244
8 Figure 7.10.3-2. Connection Layer Packet Structure (Format B) .................................7-244
9 Figure 7.11.1-1. Overhead Messages Protocol State Diagram .....................................7-252
10 Figure 8.1.1-1. Security Layer Protocols .........................................................................8-1
11 Figure 8.2-1. Security Layer Encapsulation....................................................................8-2
12 Figure 8.6.5.1-1. Message Bits for Generation of Authentication and Encryption
13 Keys .......................................................................................................................8-22
14 Figure 8.6.9-1. Example Call Flow: Timer TKEPSigCompAN Expires But TKEPKeyCompAT Does
15 Not Expire ..............................................................................................................8-30
16 Figure 8.6.9-2. Example Call Flow: Timer TKEPSigCompAN Does Not Expire But
17 TKEPKeyCompAT Expires................................................................................................8-31
18 Figure 9.1.2-1. Control Channel MAC Layer Packet Encapsulation ................................9-2
19 Figure 9.1.2-2. Access Channel MAC Layer Packet Encapsulation .................................9-2
20 Figure 9.1.2-3. Forward Traffic Channel MAC Layer Packet Encapsulation ....................9-3
21 Figure 9.1.2-4. Reverse Traffic Channel MAC Layer Packet Encapsulation .....................9-3
22 Figure 9.2.1-1. Default (Subtype 0) Control Channel MAC Protocol State Diagram .........9-4
23 Figure 9.2.6-1. Control Channel MAC Packet Structure .................................................9-8
24 Figure 9.2.6.1.4.1-1. Location of Control Channel Capsules .........................................9-10
25 Figure 9.3.1-1. Enhanced Control Channel MAC Protocol State Diagram .....................9-16
26 Figure 9.3.7-1. Enhanced Control Channel MAC Packet Structure...............................9-21
27 Figure 9.3.7.1.4.1-1. Location of Control Channel Capsules .........................................9-23
28 Figure 9.4.1-1. Default Access Channel MAC Protocol State Diagram...........................9-31
29 Figure 9.4.6.1-1. Access Channel MAC Packet Structure .............................................9-35
30 Figure 9.4.6.1.2-1. Access Probe Structure ..................................................................9-37
31 Figure 9.4.6.1.2-2. Access Probe Sequences.................................................................9-37
32 Figure 9.4.6.2-1. Access Channel MAC Layer Capsule FCS ..........................................9-45
lxxix
3GPP2 C.S0024-B v2.0
FIGURES
1 Figure 9.5.1-1. Enhanced Access Channel MAC Protocol State Diagram ...................... 9-51
2 Figure 9.5.6.1-1. Enhanced Access Channel MAC Packet Structure............................. 9-55
3 Figure 9.5.6.1.2-1. Access Probe Structure .................................................................. 9-57
4 Figure 9.5.6.1.2-2. Access Probe Sequences ................................................................ 9-57
5 Figure 9.5.6.2-1. Access Channel MAC Layer Capsule FCS.......................................... 9-68
6 Figure 9.6.1-1. Default Forward Traffic Channel MAC Protocol State Diagram ............. 9-85
7 Figure 9.6.6-1. Forward Traffic Channel MAC Layer Packet Structure ......................... 9-89
8 Figure 9.7.1-1. Enhanced Forward Traffic Channel MAC Protocol State Diagram ....... 9-102
9 Figure 9.7.6.1.1-1. Enhanced Forward Traffic Channel MAC Layer Packet Structure . 9-107
10 Figure 9.7.6.1.1.2-1 Format of Forward Traffic Channel Single User Simplex MAC
11 Layer Packet......................................................................................................... 9-109
12 Figure 9.7.6.1.1.2-2 Format of Forward Traffic Channel Multiuser MAC Layer
13 Packet .................................................................................................................. 9-109
14 Figure 9.8.1-1. Multicarrier Forward Traffic Channel MAC Protocol State Diagram .... 9-135
15 Figure 9.8.6.1.1-1. Multicarrier Forward Traffic Channel MAC Layer Packet
16 Structure ............................................................................................................. 9-140
17 Figure 9.8.6.1.1.2-1 Format of Forward Traffic Channel Single User MAC Layer
18 Packet .................................................................................................................. 9-141
19 Figure 9.8.6.1.1.2-2 Format of Forward Traffic Channel Multi-User MAC Layer
20 Packet .................................................................................................................. 9-142
21 Figure 9.8.6-3. Example of the RPC and DRC Mapping Related to DRC supervision .. 9-162
22 Figure 9.9.1-1. Default (Subtype 0) Reverse Traffic Channel MAC Protocol State
23 Diagram ............................................................................................................... 9-187
24 Figure 9.9.6-1. Reverse Traffic Channel MAC Layer Packet Structure ........................ 9-191
25 Figure 9.10.1-1. Subtype 1 Reverse Traffic Channel MAC Protocol State Diagram...... 9-205
26 Figure 9.10.6-1. Reverse Traffic Channel MAC Layer Packet Structure ...................... 9-209
27 Figure 9.12.1-1. Subtype 3 Reverse Traffic Channel MAC Protocol State Diagram...... 9-280
28 Figure 9.12.6.1.1-1.Reverse Traffic Channel MAC Layer Packet Structure ................. 9-284
29 Figure 9.13.1-1. Multicarrier Reverse Traffic Channel MAC Protocol State Diagram
30 (for each supported Reverse CDMA Channel) ....................................................... 9-383
31 Figure 9.13.6.1.1-1.Reverse Traffic Channel MAC Layer Packet Structure ................. 9-387
32 Figure 10.2.2.1-1. Physical Layer Packet Format for the Control Channel .................... 10-6
33 Figure 10.2.2.2-1. Default (Subtype 0) Physical Layer Protocol Packet Format for the
34 Access Channel ...................................................................................................... 10-7
lxxx
3GPP2 C.S0024-B v2.0
FIGURES
1 Figure 10.2.2.2-2. Subtype 1 Physical Layer Protocol Packet Format for the Access
2 Channel..................................................................................................................10-7
3 Figure 10.2.2.3-1. Physical Layer Packet Format for the Forward Traffic Channel ........10-9
4 Figure 10.2.2.4-1. Physical Layer Packet Format for the Reverse Traffic Channel .......10-10
5 Figure 10.2.4-1. FCS Computation for the Physical Layer Packet ...............................10-11
6 Figure 10.3.1.3.1-1. Default (Subtype 0) Physical Layer Protocol Reverse Channel
7 Structure for the Access Channel .........................................................................10-18
8 Figure 10.3.1.3.1-2. Subtype 1 Physical Layer Protocol Reverse Channel Structure
9 for the Access Channel .........................................................................................10-19
10 Figure 10.3.1.3.1-3. Reverse Channel Structure for the Reverse Traffic Channel
11 (Part 1 of 2)...........................................................................................................10-20
13 (Part 2 of 2)...........................................................................................................10-21
14 Figure 10.3.1.3.1-5. Pilot Channel and RRI Channel TDM Allocations for the
15 Reverse Traffic Channel ........................................................................................10-21
16 Figure 10.3.1.3.1-6. Multislot Physical Layer Packet with Normal Termination...........10-22
17 Figure 10.3.1.3.1-7. Multislot Physical Layer Packet with Early Termination..............10-22
18 Figure 10.3.1.3.2-1. Example of an Access Probe Transmitted at 9.6 kbps (Subtype
19 0 Physical Layer Protocol) .....................................................................................10-25
20 Figure 10.3.1.3.2-2. Example of an Access Probe Transmitted at 9.6 kbps (Subtype
21 1 Physical Layer Protocol) .....................................................................................10-25
22 Figure 10.3.1.3.2-3. Example of an Access Probe Transmitted at a Data Rate of 19.2
23 or 38.4 kbps .........................................................................................................10-26
24 Figure 10.3.1.3.3.5-1. DRC Timing for Nongated Transmission ..................................10-30
25 Figure 10.3.1.3.3.5-2. DRC Timing for Gated Transmission........................................10-31
26 Figure 10.3.1.3.4.2.2-1. Turbo Encoder .....................................................................10-34
27 Figure 10.3.1.3.4.2.3-1. Turbo Interleaver Output Address Calculation Procedure .....10-36
28 Figure 10.3.1.3.5-1. Channel Interleaver Address Generation ....................................10-39
29 Figure 10.3.1.3.8.2-1. Long Code Generators .............................................................10-43
30 Figure 10.3.1.3.8.3-1. Baseband Filter Frequency Response Limits............................10-44
31 Figure 10.4.1.3.1-1. Forward Channel Structure........................................................10-51
32 Figure 10.4.1.3.1-2. Forward Link Slot Structure .......................................................10-52
33 Figure 10.4.1.3.1-3. Multislot Physical Layer Packet with Normal Termination...........10-52
34 Figure 10.4.1.3.1-4. Multislot Physical Layer Packet with Early Termination..............10-53
lxxxi
3GPP2 C.S0024-B v2.0
FIGURES
1 Figure 10.4.1.3.2.2.2-1. DRCLock Puncturing Example ............................................. 10-59

2 Figure 10.4.1.3.2.3.2-1. Forward Link Encoder.......................................................... 10-61
3 Figure 10.4.1.3.2.3.2.1-1. Turbo Encoder .................................................................. 10-63
4 Figure 10.4.1.3.2.3.2.2-1. Turbo Interleaver Output Address Calculation Procedure.. 10-65
5 Figure 10.4.1.3.2.3.3-1. Symbol Scrambler ................................................................ 10-69
6 Figure 10.4.1.3.2.3.5.1-1. Signal Constellation for QPSK Modulation......................... 10-72
7 Figure 10.4.1.3.2.3.5.2-1. Signal Constellation for 8-PSK Modulation ........................ 10-73
8 Figure 10.4.1.3.2.3.5.3-1. Signal Constellation for 16-QAM Modulation..................... 10-75
9 Figure 10.4.1.3.3-1. Preamble, Pilot, MAC, and Data Multiplexing for the Multiple-
10 Slot Cases with Data Rates of 153.6, 307.2, 614.4, 921.6, and 1228.8 kbps ........ 10-78
11 Figure 10.4.1.3.3-2. Preamble, Pilot, MAC, and Data Multiplexing with Data Rates
12 of 38.4 and 76.8 kbps .......................................................................................... 10-78
13 Figure 10.4.1.3.3-3. Preamble, Pilot, MAC, and Data Multiplexing for the 1-Slot
14 Cases with Data Rates of 1.2288, 1.8432, and 2.4576 Mbps ................................ 10-79
16 Case with a Data Rate of 614.4 kbps.................................................................... 10-79
17 Figure 10.4.1.3.5.1-1. Baseband Filter Frequency Response Limits ........................... 10-82
18 Figure 11.2.2.1-1. Physical Layer Packet Formats for the Control Channel .................. 11-6
19 Figure 11.2.2.2-1. Physical Layer Packet Format for the Access Channel ..................... 11-6
20 Figure 11.2.2.3-1. Physical Layer Packet Format for the Forward Traffic Channel........ 11-7
21 Figure 11.2.4-1. 16-bit FCS Computation for the Physical Layer Packet....................... 11-9
22 Figure 11.2.4-2. 24-bit FCS Computation for the Physical Layer Packet....................... 11-9
23 Figure 11.3.1.3.1-1. Reverse Channel Structure for the Access Channel .................... 11-18
25 for the Reverse Traffic Channel (Part 1 of 5).......................................................... 11-19
34 Figure 11.3.1.3.1-9. Reverse Traffic Channel Sub-frame Structure ............................ 11-25
lxxxii
3GPP2 C.S0024-B v2.0
FIGURES

2 kbps .....................................................................................................................11-27
4 or 38.4 kbps .........................................................................................................11-28
5 Figure 11.3.1.3.3-1. DSC Channel Timeline ...............................................................11-32
9 Figure 11.3.1.3.5-1. Symbol Scrambler ......................................................................11-47
11 Figure 11.3.1.3.12.2-1. Long-Code Generators ...........................................................11-60
12 Figure 11.3.1.3.12.3-1. Baseband Filter Frequency Response Limits..........................11-61
13 Figure 11.3.2.4-1. Reverse Traffic Channel Physical Layer Packet with Maximum
14 Transmit Duration................................................................................................11-66
15 Figure 11.3.2.4-2. Reverse Traffic Channel Packet Transmission with Early
16 Termination..........................................................................................................11-67
17 Figure 11.3.2.4-3. Reverse Traffic Channel Packet Transmission Failure....................11-68
18 Figure 11.4.1.3.1-1. Forward Channel Structure........................................................11-73
19 Figure 11.4.1.3.1-2. Forward Link Slot Structure .......................................................11-74
20 Figure 11.4.1.3.2.3.2-1. Forward Link Encoder ..........................................................11-86
21 Figure 11.4.1.3.2.3.2.1-1. Turbo Encoder...................................................................11-90
22 Figure 11.4.1.3.2.3.3-1. Symbol Scrambler ................................................................11-97
23 Figure 11.4.1.3.2.3.5.1-1. Signal Constellation for QPSK Modulation .......................11-102
24 Figure 11.4.1.3.2.3.5.2-1. Signal Constellation for 8-PSK Modulation ......................11-103
25 Figure 11.4.1.3.2.3.5.3-1. Signal Constellation for 16-QAM Modulation ...................11-105
27 Slot Cases with Transmission Formats in Table 11.4.1.3.3-1 ..............................11-110
28 Figure 11.4.1.3.3-2. Preamble, Pilot, MAC, and Data Multiplexing with
29 Transmission Formats in Table 12.4.1.3.3-2.......................................................11-111
31 Case with Transmission Formats in Table 11.4.1.3.3-4. .....................................11-112
33 Slot Cases with Transmission Formats in Table 11.4.1.3.3-5 ..............................11-113
lxxxiii
3GPP2 C.S0024-B v2.0
FIGURES
1 Figure 12.2.2.1-1. Physical Layer Packet Formats for the Control Channel ................ 12-14
2 Figure 12.2.2.2-1. Physical Layer Packet Format for the Access Channel ................... 12-14
3 Figure 12.2.2.3-1. Physical Layer Packet Format for the Forward Traffic Channel...... 12-15
4 Figure 12.2.4-1. 16-bit FCS Computation for the Physical Layer Packet..................... 12-17
5 Figure 12.2.4-2. 24-bit FCS Computation for the Physical Layer Packet..................... 12-17
6 Figure 12.3.1.3.1-1. Reverse Channel Structure for the Access Channel .................... 12-32
7 Figure 12.3.1.3.1-2. Subtype 3 Physical Layer Protocol NoFeedbackMultiplexing
8 mode Reverse Channel Structure for the Reverse Traffic Channel for single
9 carrier operation (Part 1 of 5) ............................................................................... 12-33
17 mode Reverse Channel Structure for the Reverse Traffic Channel for single
18 carrier operation (Part 5 of 5) ............................................................................... 12-37
20 mode Reverse Channel Structure for the Reverse Traffic Channel for Multicarrier
21 operation.............................................................................................................. 12-38
22 Figure 12.3.1.3.1-8. BasicFeedbackMultiplexing Mode Transmission (N forward
23 CDMA channels with 1 Reverse CDMA channel)................................................... 12-39
24 Figure 12.3.1.3.1-9. EnhancedFeedbackMultiplexing Mode DRC Channel
25 Transmission (2 Forward CDMA channels with 1 Reverse CDMA channel) ........... 12-39
26 Figure 12.3.1.3.1-10. EnhancedFeedbackMultiplexing Multicarrier Mode DRC
27 Channel Transmission (4 Forward CDMA channels with 1 Reverse CDMA
28 channel) ............................................................................................................... 12-40
29 Figure 12.3.1.3.1-11. EnhancedFeedbackMultiplexing Mode ACK Channel
33 Figure 12.3.1.3.1-13. EnhancedFeedbackMultiplexing Mode DSC Channel
34 Transmission (2 independent DSC Channel Transmissions with 1 Reverse
35 CDMA channel) .................................................................................................... 12-41
lxxxiv
3GPP2 C.S0024-B v2.0
FIGURES

2 Transmission (4 independent DSC Channel Transmissions with 1 Reverse
3 CDMA channel) ....................................................................................................12-42
4 Figure 12.3.1.3.1-15. EnancedFeedbackMultiplexing Mode Transmission (16
5 forward CDMA channels with 1 Reverse CDMA channel) ......................................12-42
6 Figure 12.3.1.3.1-16. Multislot Forward Traffic Channel Physical Layer Packet with
7 Normal Termination..............................................................................................12-43
9 early Termination on one carrier and normal termination on another carrier for
10 EnhancedFeedbackMultiplexing mode with single DSC transmission and offset
11 ACK transmission.................................................................................................12-44
12 Figure 12.3.1.3.1-19. NoFeedbackMultiplexing mode Reverse Traffic Channel Sub-
13 frame Structure with single carrier .......................................................................12-44
15 kbps .....................................................................................................................12-48
17 or 38.4 kbps .........................................................................................................12-49
18 Figure 12.3.1.3.3-1. DSC Channel Timeline (NoFeedbackMultiplexing Mode and
19 BasicFeedbackMultiplexing Mode) ........................................................................12-55
20 Figure 12.3.1.3.3-2. DSC Channel Timeline (EnhancedFeedbackMultiplexing mode
21 with time division multiplexing of two DSC Channel transmissions) ....................12-56
25 Figure 12.3.1.3.5-1. Symbol Scrambler ......................................................................12-75
27 Figure 12.3.1.3.12.2-1. Long-Code Generators ...........................................................12-88
29 Figure 12.3.1.4-1. Discontinuous Transmission with DTXMode equal to ‘1’ and
30 DTXRRIMode equal to ’0’ ......................................................................................12-92
32 DTXRRIMode equal to ’1’ ......................................................................................12-93
34 Transmit Duration................................................................................................12-98
36 Termination..........................................................................................................12-99
lxxxv
3GPP2 C.S0024-B v2.0
FIGURES
1 Figure 12.3.2.4-3. Reverse Traffic Channel Packet Transmission Failure ................. 12-100
2 Figure 12.4.1.3.1-2. Forward Link Slot Structure..................................................... 12-107
3 Figure 12.4.1.3.2.3.2-1. Forward Link Encoder........................................................ 12-126
4 Figure 12.4.1.3.2.3.2.1-1. Turbo Encoder ................................................................ 12-130
5 Figure 12.4.1.3.2.3.3-1. Symbol Scrambler .............................................................. 12-138
6 Figure 12.4.1.3.2.3.5.1-1. Signal Constellation for QPSK Modulation....................... 12-143
7 Figure 12.4.1.3.2.3.5.2-1. Signal Constellation for 8-PSK Modulation ...................... 12-144
8 Figure 12.4.1.3.2.3.5.3-1. Signal Constellation for 16-QAM Modulation................... 12-146
9 Figure 12.4.1.3.2.3.5.4-1. Signal Constellation for 64-QAM Modulation................... 12-149
10 Figure 12.4.1.3.3-2. Preamble, Pilot, MAC, and Data Multiplexing with
11 Transmission Formats in Table 12.4.1.3.3-2 ...................................................... 12-157
13 Case with Transmission Formats in Table 12.4.1.3.3-4. ..................................... 12-159
15 Slot Cases with Transmission Formats in Table 12.4.1.3.3-5 ............................. 12-160
16 Figure 12.4.1.3.5.1-1. Baseband Filter Frequency Response Limits ......................... 12-164
17 Figure 13.9.1.1-1. Global Unicast IPv6 Address Format ............................................. 13-11
18 Figure 13.9.1.2-1. Site-Local Unicast IPv6 Address Format........................................ 13-11
19 Figure 13.9.1.3-1. Link-Local Unicast IPv6 Address Format....................................... 13-12
20 Figure 13.9.1.4-1. Format of the Reserved IPv6 Addresses ......................................... 13-12
21 Figure 13.9.1.4-2. IPv6 Values That Are to be Avoided ............................................... 13-12
22 Figure 13.9.1.5-1. Universally Unique Modified EUI-64.............................................. 13-13
23 Figure 13.9.1.5-2. Locally Unique Modified EUI-64 .................................................... 13-13
24 Figure 13.9.2.1.2-1. “S” bits in the Site-Local Unicast IPv6 Address Format............... 13-14
25 Figure 13.9.2.1.2-2. “S” bits in the Link-Local Unicast IPv6 Address Format.............. 13-14
26 Figure 13.9.2.1.2-3. “S” bits in the Reserved IPv6 Address Format............................. 13-14
27 Figure 13.9.2.1.2-4. sub-fields of the “S” bits............................................................. 13-15
28 Figure 13.9.2.1.2.1-1. Assignment of the “T” Bits, the “N” Bits, and the “X” Bits for
29 the ANSI-41 Method ............................................................................................. 13-15
31 the GSM/UMTS Method ....................................................................................... 13-16
33 the IPv4 Method ................................................................................................... 13-16
lxxxvi
3GPP2 C.S0024-B v2.0
FIGURES
1 Figure 13.9.2.2-1. Format of the Locally Unique SectorID ..........................................13-16

2
lxxxvii
3GPP2 C.S0024-B v2.0
FIGURES
1 No text
lxxxviii
3GPP2 C.S0024-B v2.0
TABLES
1 Table 2.5.4-1. Default Protocol Stack Type Values..........................................................2-9

2 Table 3.5.4.2-1. LocationType Encoding .......................................................................3-14
3 Table 3.5.4.2-2. Subfields of LocationValue when LocationType = 0x01........................3-15
4 Table 3.7-1. Configurable Values..................................................................................3-22
5 Table 3.8.1-1. The Format of the Parameter Record for the Location Parameter............3-22
6 Table 3.8.2-1. The Format of the Parameter Record for the FlowControlState
7 Parameter...............................................................................................................3-23
8 Table 4.6.4.2-1. LocationType Encoding .......................................................................4-40
9 Table 4.6.4.2-2. Subfields of LocationValue when LocationType = 0x01........................4-40
10 Table 4.8-1. Configurable Values..................................................................................4-52
11 Table 4.8.2.1-1. Default Values of SequenceLength, RLPIDLength, and RLPID in the
12 FlowNNIdentificationFwd attribute..........................................................................4-57
14 FlowNNIdentificationRev attribute ..........................................................................4-59
15 Table 4.9.1-1. The Format of the Parameter Record for the Location Parameter............4-71
17 Parameter...............................................................................................................4-71
18 Table 4.9.3-1. The Format of the Parameter Record for the
19 DataOverSignalingMessageSequence Parameter .....................................................4-72
20 Table 4.9.4-1. The Format of the Parameter Record for the StorageBLOB Parameter ....4-73
21 Table 4.9.5-1. The Format of the Parameter Record for the ReservationState
22 Parameter...............................................................................................................4-74
23 Table 5.1-1. Application Subtypes for Applications Defined in this Specification ............5-1
24 Table 5.3.7-1. Configurable Values...............................................................................5-13
25 Table 6.2.6.2.1-1. Encoding of CloseReason Field.........................................................6-12
26 Table 6.2.7-1. Configurable Attributes..........................................................................6-16
27 Table 6.3.7.2-1. HardwareIDType encoding ..................................................................6-33
29 Table 6.3.10.1-1. The Format of the Parameter Record for the SessionSeed
30 Parameter...............................................................................................................6-37
31 Table 6.3.10.2-1. The Format of the Parameter Record for the MessageSequence
32 Parameter...............................................................................................................6-38
33 Table 6.3.10.3-1. The Format of the Parameter Record for the HardwareID
34 Parameter...............................................................................................................6-38
lxxxix
3GPP2 C.S0024-B v2.0
TABLES
1 Table 6.4.7.1-1. Simple Configurable Attributes........................................................... 6-66

2 Table 6.4.10.1-1. The Format of the Parameter Record for the ConfigurationLock
3 Parameter .............................................................................................................. 6-73
4 Table 6.4.10.2-1. The Format of the Parameter Record for the
5 ATSupportedNonDefaultProtocolSubTypes Parameter ............................................ 6-74
6 The Format of the Parameter Record for the C Parameter............................................. 6-75
7 Table 6.5.9-1. Configurable Values .............................................................................. 6-80
8 Table 7.2.1-1. Active Protocols Per Air Link Management Protocol State......................... 7-7
9 Table 7.2.6.2.2-1. ConnectionFailureReason Encoding ................................................ 7-17
10 Table 7.2.7-1 Configurable Simple Attributes............................................................... 7-19
11 Table 7.4.6.2-1. Encoding of the RequestReason Field ................................................. 7-41
12 Table 7.4.6.2-2. Encoding of the DenyReason Field...................................................... 7-42
13 Table 7.5.6.1.5-1. Computation of Periodi from SlotCyclei............................................ 7-53
16 Table 7.5.7.1-1Configurable Simple Attributes............................................................. 7-66
17 Table 7.5.7.2.2-1. Definition of MaskPurpose Field of a Paging Mask ........................... 7-69
18 Table 7.6.6.1.5-1. Computation of PagePeriodi from SlotCyclei..................................... 7-80
21 Table 7.6.7.1-1. Configurable Simple Attributes........................................................... 7-95
22 Table 7.6.7.2.2-1. Definition of MaskPurpose Field of a Paging Mask ........................... 7-99
23 Table 7.7.6.2-1. Encoding of the CloseReason Field ................................................... 7-109
24 Table 7.8.1-1. Route Update Protocol Parameters that are Public Data of the
25 Overhead Messages Protocol ................................................................................ 7-112
26 Table 7.8.6.2-1. DRCLength Encoding ....................................................................... 7-140
27 Table 7.8.6.2-2. Encoding of the RABLength Field ..................................................... 7-141
28 Table 7.8.6.2-3. Reverse Activity Channel Gain Encoding .......................................... 7-142
29 Table 7.8.6.2-4. Search Window Sizes........................................................................ 7-147
30 Table 7.8.6.2-5. Search Window Offset....................................................................... 7-148
31 Table 7.8.6.2.8-1. Search Window Sizes..................................................................... 7-152
32 Table 7.8.6.2.8-2. Search Window Offset.................................................................... 7-153
xc
3GPP2 C.S0024-B v2.0
TABLES
1 Table 7.8.7.1-1. Configurable Values..........................................................................7-156

2 Table 7.8.7.2.2-1. Pilot Drop Timer Values .................................................................7-161
3 Table 7.8.9.1-1. The Format of the Parameter Record for the RouteUpdate
4 Parameter.............................................................................................................7-166
5 Table 7.8.9.2-1. The Format of the Parameter Record for the ExtendedRouteUpdate
6 Parameter.............................................................................................................7-169
8 AttributeOverrideMessageSequence Parameter .....................................................7-170
10 Overhead Messages Protocol.................................................................................7-173
11 Table 7.9.6.2-1. Reverse Activity Channel Encoding ...................................................7-206
12 Table 7.9.6.2-2. DRCLength Encoding........................................................................7-208
13 Table 7.9.6.1.6.10-3. ReverseChannelConfiguration Encoding ...................................7-210
14 Table 7.9.6.2-4. Search Window Sizes ........................................................................7-217
15 Table 7.9.6.2-5. Search Window Offset .......................................................................7-218
16 Table 7.9.6.2.6-1. Search Window Sizes .....................................................................7-222
17 Table 7.9.6.2.6-2. Search Window Offset ....................................................................7-223
19 Table 7.9.7.2.1-1. Pilot Drop Timer Values .................................................................7-233
20 Table 7.9.7.3.2-1. Encoding of the SupportedDRXPattern Field..................................7-238
21 Table 7.9.9.1-1. The Format of the Parameter Record for the RouteUpdate
22 Parameter.............................................................................................................7-240
23 Table 7.11.6.2-1. Search Window Sizes ......................................................................7-269
24 Table 7.11.6.2-2. Search Window Offset .....................................................................7-270
25 Table 7.11.7-1 Configurable Simple Attributes ...........................................................7-277
26 Table 8.6.5.1-1. Message Bits.......................................................................................8-19
27 Table 8.6.5.1-2. Message Bits.......................................................................................8-21
28 Table 8.6.5.1-3. Subfields of SKey ................................................................................8-22
30 Table 8.6.6.3-1. Common Primitive Base and Common Prime Modulus for
31 KeyLength equal to 768 ..........................................................................................8-29
32 Table 8.6.6.3-2. Common Primitive Base and Common Prime Modulus for
33 KeyLength equal to 1024 ........................................................................................8-29
34 Table 8.6.10.1-1. The Format of the Parameter Record for the SKey Parameter ............8-31
xci
3GPP2 C.S0024-B v2.0
TABLES
1 Table 8.6.10.2-1. The Format of the Parameter Record for the FACAuthKey
2 Parameter .............................................................................................................. 8-32
3 Table 8.6.10.3-1. The Format of the Parameter Record for the RACAuthKey
4 Parameter .............................................................................................................. 8-32
5 Table 8.6.10.4-1. The Format of the Parameter Record for the FACEncKey
6 Parameter .............................................................................................................. 8-33
7 Table 8.6.10.5-1. The Format of the Parameter Record for the RACEncKey
8 Parameter .............................................................................................................. 8-33
9 Table 8.6.10.6-1. The Format of the Parameter Record for the FPCAuthKey
10 Parameter .............................................................................................................. 8-33
11 Table 8.6.10.7-1. The Format of the Parameter Record for the RPCAuthKey
12 Parameter .............................................................................................................. 8-34
13 Table 8.6.10.8-1. The Format of the Parameter Record for the FPCEncKey
14 Parameter .............................................................................................................. 8-34
15 Table 8.6.10.9-1. The Format of the Parameter Record for the RPCEncKey
16 Parameter .............................................................................................................. 8-35
17 Table 8.8.6.1-1. Message Bits for ACPAC Computation ................................................ 8-44
18 Table 8.8.6.1-2. Message Bits for ACPAC Computation ................................................ 8-45
21 Table 9.4.6.1.4.1.3-1. Access Channel Long Code Masks ............................................. 9-40
22 Table 9.5.6.1.4.1.2-1. Access Channel Rates and Payload............................................ 9-60
23 Table 9.5.6.1.4.1.3-1. Access Channel Long Code Masks ............................................. 9-62
24 Table 9.5.6.2.1-1. ProbeNumber Encoding ................................................................... 9-67
25 Table 9.5.6.2.6-1. PreambleLengthSlots Encoding........................................................ 9-72
26 Table 9.5.6.2.6-2. AccessOffset Encoding..................................................................... 9-73
27 Table 9.5.6.2.6-3. SectorAccessMaxRate Encoding....................................................... 9-73
28 Table 9.5.6.2.6-4. ProbeTimeOutAdjust Encoding ........................................................ 9-74
29 Table 9.5.6.2.6-5. PilotStrengthNominal Encoding ....................................................... 9-74
30 Table 9.5.6.2.6-6. PilotStrengthCorrectionMin Encoding .............................................. 9-75
31 Table 9.5.6.2.6-7. PilotStrengthCorrectionMax Encoding ............................................. 9-75
33 Table 9.6.6.1.4.1-1. DRC Value Specification ............................................................... 9-92
34 Table 9.6.7.1-1. Configurable Values ........................................................................... 9-98
xcii
3GPP2 C.S0024-B v2.0
TABLES
1 Table 9.6.7.2.1-1. DRCLockPeriod Encoding. ...............................................................9-99

2 Table 9.6.7.2.1-2. DRCLockLength Encoding .............................................................9-100
3 Table 9.7.6.1.2-1 Preamble MAC Index of Multi-User MAC packets ............................9-113
4 Table 9.7.6.1.4-1 List of all Transmission Formats Consistent with each MAC Layer
5 Packet Size ...........................................................................................................9-114
6 Table 9.7.6.1-2 Rate Metric, Span and Lists of Associated Transmission Formats ......9-116
8 Table 9.8.6.1.2-1 Preamble MAC Index of Multi-User MAC packets ............................9-146
10 Packet Size ...........................................................................................................9-148
11 Table 9.8.6.1-2 Rate Metric, Termination Target, Maximum Span, and Lists of
12 Associated Transmission Formats ........................................................................9-150
14 Table 9.8.7.2.3-1. Values for MaxOptionalDataRate ...................................................9-184
15 Table 9.8.7.2.3-2. Values for MaxOptionalPayloadSize ...............................................9-184
16 Table 9.8.7.2.3-3. Values for ShortPacketsEnabledThresh .........................................9-185
17 Table 9.9.6-1. Reverse Traffic Channel Rates and Payload..........................................9-192
18 Table 9.9.6.1.2-1. Reverse Traffic Channel Long Code Masks .....................................9-193
19 Table 9.9.6.1.5-1. Determination of MaxRate .............................................................9-195
20 Table 9.9.6.3-1. Encoding of the RateLimit Field ........................................................9-198
21 Table 9.9.6.3-2. Encoding of the RateLimit Field ........................................................9-199
22 Table 9.9.7.1-1. Encoding of the RPCStep Field..........................................................9-201
23 Table 9.9.9.1-1. The Format of the Parameter Record for the LongCodeMask
24 Parameter.............................................................................................................9-204
25 Table 9.10.6-1. Reverse Traffic Channel Rates and Payload........................................9-210
26 Table 9.10.6.1.2-1. Reverse Traffic Channel Long Code Masks ...................................9-211
27 Table 9.10.6.1.5-1. Determination of MaxRate ...........................................................9-213
28 Table 9.10.6.3-1. Encoding of the RateLimit Field ......................................................9-216
29 Table 9.10.6.3-2. Encoding of the RateLimit Field ......................................................9-217
30 Table 9.10.7.1-1. Encoding of the RPCStep Field........................................................9-221
32 Parameter.............................................................................................................9-223
33 Table 9.12.6.1.3-1.Reverse Traffic Channel Long Code Masks ....................................9-285
xciii
3GPP2 C.S0024-B v2.0
TABLES
1 Table 9.12.6.1.6.1-1.Reverse Traffic Channel Rates and Payload................................ 9-287

2 Table 9.12.6.1.6.1-2. Traffic Channel to Pilot Channel power ratios ........................... 9-288
3 Table 9.12.6.2.3-1.Encoding of QueueLength Field .................................................... 9-307
4 Table 9.12.7.1-1.Configurable Simple Attributes........................................................ 9-313
5 Table 9.12.7.2.2-1.Encoding of AuxiliaryPilotChannelMinPayload Field ..................... 9-323
6 Table 9.12.7.2.3-1. T2PAxis Default Values ............................................................... 9-326
7 Table 9.12.7.2.3-2. FRABAxis Default Values............................................................. 9-326
8 Table 9.12.7.2.3-3. BucketFactor Default Values ....................................................... 9-326
9 Table 9.12.7.2.3-4. T2PAxis Default Values ............................................................... 9-326
10 Table 9.12.7.2.3-5. FRABAxis Default Values............................................................. 9-326
11 Table 9.12.7.2.3-6. BucketFactor Default Values ....................................................... 9-327
12 Table 9.12.7.2.4-1.Encoding of the RPCStep Field ..................................................... 9-328
13 Table 9.12.7.2.6-1. Packet size encoding.................................................................... 9-339
14 Table 9.12.7.2.7-1. PilotStrengthAxis Default Values ................................................. 9-341
15 Table 9.12.7.2.7-2. PilotStrengthPilotStrengthAxis Default Values ............................. 9-341
16 Table 9.12.7.2.23-1. T2PAxis Default Values ............................................................. 9-374
17 Table 9.12.7.2.23-2. FRABAxis Default Values........................................................... 9-374
18 Table 9.12.7.2.23-3. T2PUpT2PAxisTTFRABAxisF Default Values .............................. 9-375
19 Table 9.12.7.2.23-4. T2PDnT2PAxisTTFRABAxisF Default Values .............................. 9-376
20 Table 9.12.7.2.23-5. T2PAxis Default Values ............................................................. 9-376
21 Table 9.12.7.2.23-6. FRABAxis Default Values........................................................... 9-376
22 Table 9.12.7.2.23-7. T2PUpT2PAxisFRABAxis Default Values .................................... 9-377
23 Table 9.12.7.2.23-8. T2PDnT2PAxisFRABAxis Default Values.................................... 9-377
24 Table 9.12.7.2.24-1. PilotStrengthAxis Default Values ............................................... 9-378
25 Table 9.12.7.2.24-2. TxT2PmaxPilotStrengthAxis Default Values ............................... 9-378
26 Table 9.12.9.1-1.The Format of the Parameter Record for the LongCodeMask
27 Parameter ............................................................................................................ 9-380
28 Table 9.13.6.1.3-1.Reverse Traffic Channel Long Code Masks.................................... 9-388
29 Table 9.13.6.1.6.1-1.Reverse Traffic Channel Rates and Payload................................ 9-391
30 Table 9.13.6.1.6.1-2. Traffic Channel to Pilot Channel power ratios ........................... 9-392
31 Table 9.13.6.2.4-1. Reason Codes .............................................................................. 9-418
32 Table 9.13.6.2.6-1.Encoding of QueueLength Field .................................................... 9-420
xciv
3GPP2 C.S0024-B v2.0
TABLES
1 Table 9.13.7.1-1.Configurable Simple Attributes ........................................................9-426

2 Table 9.13.7.2.4-1.Encoding of AuxiliaryPilotChannelMinPayload Field......................9-438
3 Table 9.13.7.2.5-1. T2PAxis Default Values................................................................9-441
4 Table 9.13.7.2.5-2. FRABAxis Default Values .............................................................9-441
5 Table 9.13.7.2.5-3. BucketFactor Default Values .......................................................9-441
6 Table 9.13.7.2.5-4. T2PAxis Default Values................................................................9-441
7 Table 9.13.7.2.5-5. FRABAxis Default Values .............................................................9-441
8 Table 9.13.7.2.5-6. BucketFactor Default Values .......................................................9-442
9 Table 9.13.7.2.6-1.Encoding of the RPCStep Field......................................................9-443
10 Table 9.13.7.2.7-1.Encoding of the DataTokenInflow Field .........................................9-444
11 Table 9.13.7.2.7-2.Encoding of the DataBucketLevelMax Field...................................9-444
12 Table 9.13.7.2.9-1. Packet size encoding ....................................................................9-455
13 Table 9.13.7.2.10-1. PilotStrengthAxis Default Values................................................9-457
14 Table 9.13.7.2.10-2. PilotStrengthPilotStrengthAxis Default Values ...........................9-457
15 Table 9.13.7.2.26-1. T2PAxis Default Values ..............................................................9-490
16 Table 9.13.7.2.26-2. FRABAxis Default Values ...........................................................9-490
17 Table 9.13.7.2.26-3. T2PUpT2PAxisTTFRABAxisF Default Values ..............................9-491
18 Table 9.13.7.2.26-4. T2PDnT2PAxisTTFRABAxisF Default Values ..............................9-492
19 Table 9.13.7.2.26-5. T2PAxis Default Values ..............................................................9-492
20 Table 9.13.7.2.26-6. FRABAxis Default Values ...........................................................9-492
21 Table 9.13.7.2.26-7. T2PUpT2PAxisFRABAxis Default Values ....................................9-493
22 Table 9.13.7.2.26-8. T2PDnT2PAxisFRABAxis Default Values ....................................9-493
23 Table 9.13.7.2.27-1. PilotStrengthAxis Default Values................................................9-495
24 Table 9.13.7.2.27-2. TxT2PmaxPilotStrengthAxis Default Values ...............................9-495
26 Parameter.............................................................................................................9-496
27 Table 10.3.1.2.4.1-1. Relative Power Levels vs. Data Rate...........................................10-14
28 Table 10.3.1.3.1.1-1. Modulation Parameters for the Access Channel and the
29 Reverse Traffic Channel ........................................................................................10-23
30 Table 10.3.1.3.3.4-1. RRI Symbol and Simplex Encoder Assignments ........................10-27
31 Table 10.3.1.3.3.5-1. DRC Bi-Orthogonal Encoding....................................................10-29
32 Table 10.3.1.3.3.5-2. 8-ary Walsh Functions..............................................................10-29
xcv
3GPP2 C.S0024-B v2.0
TABLES
1 Table 10.3.1.3.4.1-1. Parameters for the Reverse Link Encoder ................................. 10-32
2 Table 10.3.1.3.4.2.2-1. Puncturing Patterns for the Data Bit Periods ......................... 10-35
3 Table 10.3.1.3.4.2.2-2. Puncturing Patterns for the Tail Bit Periods ........................... 10-35
4 Table 10.3.1.3.4.2.3-1. Turbo Interleaver Parameter .................................................. 10-37
5 Table 10.3.1.3.4.2.3-2. Turbo Interleaver Lookup Table Definition ............................. 10-38
6 Table 10.3.1.3.8.3-1. Baseband Filter Coefficients ..................................................... 10-45
7 Table 10.4.1.3.1.1-1. Modulation Parameters for the Forward Traffic Channel and
8 the Control Channel (Part 1 of 2) .......................................................................... 10-54
10 the Control Channel (Part 2 of 2) .......................................................................... 10-55
11 Table 10.4.1.3.1.1-3. Modulation Parameters for the MAC Channel ........................... 10-56
12 Table 10.4.1.3.2.1.3-1. MAC Channel and Preamble Use Versus MACIndex............... 10-57
13 Table 10.4.1.3.2.3.1-1. Preamble Repetition............................................................... 10-60
14 Table 10.4.1.3.2.3.2-1. Parameters of the Forward Link Encoder ............................... 10-61
15 Table 10.4.1.3.2.3.2.1-1. Puncturing Patterns for the Data Bit Periods ...................... 10-64
16 Table 10.4.1.3.2.3.2.1-2. Puncturing Patterns for the Tail Bit Periods ........................ 10-64
17 Table 10.4.1.3.2.3.2.2-1. Turbo Interleaver Parameter ............................................... 10-66
18 Table 10.4.1.3.2.3.2.2-2. Turbo Interleaver Lookup Table Definition .......................... 10-67
19 Table 10.4.1.3.2.3.3-1. Parameters Controlling the Scrambler Initial State ................ 10-68
20 Table 10.4.1.3.2.3.4.1-1. Scrambled Turbo Encoder Output and Symbol Reordering
21 Demultiplexer Symbol Sequences......................................................................... 10-70
22 Table 10.4.1.3.2.3.4.2-1. Channel Interleaver Parameters.......................................... 10-71
23 Table 10.4.1.3.2.3.5.1-1. QPSK Modulation Table ...................................................... 10-72
24 Table 10.4.1.3.2.3.5.2-1. 8-PSK Modulation Table ..................................................... 10-73
25 Table 10.4.1.3.2.3.5.3-1. 16-QAM Modulation Table .................................................. 10-74
26 Table 10.4.1.3.2.3.6-1. Sequence Repetition and Symbol Puncturing Parameters ...... 10-76
27 Table 10.4.1.3.3-1. Preamble, Pilot, MAC, and Data Multiplexing Parameters ............ 10-80
28 Table 10.4.1.3.5.1-1. Baseband Filter Coefficients ..................................................... 10-83
29 Table 11.3.1.2.4.1-1. Relative Power Levels vs. Data Rate for Access Channel
30 Transmissions...................................................................................................... 11-12
31 Table 11.3.1.3.1-1. Walsh Channel Assignments for Physical Layer Reverse Traffic
32 Channel ............................................................................................................... 11-17
33 Table 11.3.1.3.1.1-1. Modulation Parameters for the Access Channel ........................ 11-25
xcvi
3GPP2 C.S0024-B v2.0
TABLES
1 Table 11.3.1.3.1.1-2. Modulation Parameters for the Reverse Traffic Channel ............11-26
2 Payload Size to Payload Index Mapping ......................................................................11-30
3 Table 11.3.1.3.3.2-2. Sub-packet Identifier to Sub-packet Index Mapping..................11-30
4 Table 11.3.1.3.3.3-1. DSC Encoding...........................................................................11-31
7 Table 11.3.1.3.3.6-1. Data Channel Modulation Formats ...........................................11-36
8 Table 11.3.1.3.4-1. Parameters for the Reverse Link Encoder for the Access Channel 11-37
9 Table 11.3.1.3.4-2. Parameters for the Reverse Link Encoder for the Reverse Traffic
10 Channel – Part 1 of 2 ............................................................................................11-38
12 Channel – Part 2 of 2 ............................................................................................11-38
13 Table 11.3.1.3.4.2.2-1. Puncturing Patterns for the Data Bit Periods..........................11-42
14 Table 11.3.1.3.4.2.2-2. Puncturing Patterns for the Tail Bit Periods ...........................11-42
15 Table 11.3.1.3.4.2.3-1. Turbo Interleaver Parameter ..................................................11-44
16 Table 11.3.1.3.4.2.3-2. Turbo Interleaver Lookup Table Definition .............................11-45
17 Table 11.3.1.3.5-1. Parameters Controlling the Scrambler Initial State – Part 1 of 2 ...11-46
19 Table 11.3.1.3.7.2-1. Channel Interleaver Parameters ................................................11-50
20 Table 11.3.1.3.9.1-1. B4 Modulation Table.................................................................11-52
21 Table 11.3.1.3.9.2-1. Q4 Modulation Table.................................................................11-52
23 Table 11.3.1.3.9.5-1. E4 Modulation Table .................................................................11-54
25 Table 11.3.1.3.12.3-1. Baseband Filter Coefficients....................................................11-62
26 Table 11.3.2.4-1. H-ARQ Transmission Rules.............................................................11-64
28 the Control Channel .............................................................................................11-75
29 Table 11.4.1.3.1.1-2. Modulation Parameters for the MAC Channel ...........................11-76
30 Table 11.4.1.3.2.2-1. Forward Link MAC Channel Assignment...................................11-77
31 Table 11.4.1.3.2.2-2. MAC Channel and Preamble Use Versus MACIndex ..................11-80
32 Table 11.4.1.3.2.3.1-1. Preamble Repetition ...............................................................11-85
xcvii
3GPP2 C.S0024-B v2.0
TABLES
1 Table 11.4.1.3.2.3.2-1. Parameters of the Forward Link Encoder ............................... 11-87

2 Table 11.4.1.3.2.3.2.1-1. Puncturing Patterns for the Data Bit Periods ...................... 11-91
3 Table 11.4.1.3.2.3.2.1-2. Puncturing Patterns for the Tail Bit Periods ........................ 11-91
4 Table 11.4.1.3.2.3.2.2-1. Turbo Interleaver Parameter ............................................... 11-93
5 Table 11.4.1.3.2.3.2.2-2. Turbo Interleaver Lookup Table Definition .......................... 11-94
6 Table 11.4.1.3.2.3.3-1. Parameters Controlling the Scrambler Initial State ................ 11-96
7 Table 11.4.1.3.2.3.4.3-1. Channel Interleaver Parameters........................................ 11-100
8 Table 11.4.1.3.2.3.5.1-1. QPSK Modulation Table .................................................... 11-101
9 Table 11.4.1.3.2.3.5.2-1. 8-PSK Modulation Table ................................................... 11-103
10 Table 11.4.1.3.2.3.5.3-1. 16-QAM Modulation Table ................................................ 11-104
11 Table 11.4.1.3.2.3.6-1. Sequence Repetition and Symbol Puncturing Parameters .... 11-106
12 Table 11.4.1.3.3-1. Transmission Formats Corresponding to Timing Diagram in
13 Figure 11.4.1.3.3-1 ............................................................................................ 11-109
15 Figure 11.4.1.3.3-2 ............................................................................................ 11-110
17 Figure 11.4.1.3.3-3 ............................................................................................ 11-111
19 Figure 11.4.1.3.3-4 ............................................................................................ 11-112
21 Figure 11.4.1.3.3-5 ............................................................................................ 11-113
22 Table 11.4.1.3.3-6. Preamble, Pilot, MAC, and Data Multiplexing Parameters .......... 11-114
23 Table 11.4.1.3.5.1-1. Baseband Filter Coefficients ................................................... 11-118
24 Table 12.1.7.1-1. Configurable Values ......................................................................... 12-7
25 Table 12.1.7.2.2-1.Encoding of ReversePilotTransmitSlotsDuration Field................... 12-11
26 Table 12.1.7.2.2-2.Encoding of ReversePilotTransmitSlotsPeriod Field ....................... 12-12
28 Transmissions...................................................................................................... 12-21
29 Table 12.3.1.3.1-1. FeedbackMultiplexingIndex composition ..................................... 12-26
31 Channel ............................................................................................................... 12-30
32 Table 12.3.1.3.1.1-1. Modulation Parameters for the Access Channel ........................ 12-46
33 Table 12.3.1.3.1.1-2. Modulation Parameters for the Reverse Traffic Channel ............ 12-47
34 Payload Size to Payload Index Mapping...................................................................... 12-51
xcviii
3GPP2 C.S0024-B v2.0
TABLES
1 Table 12.3.1.3.3.2-2. Sub-packet Identifier to Sub-packet Index Mapping..................12-51

2 Table 12.3.1.3.3.3-1. DSC Channel Data Rate............................................................12-52
3 Table 12.3.1.3.3.3-2. DSC Channel transmission and FeedbackMultiplexingMethod..12-53
4 Table 12.3.1.3.3.3-3. DSC Encoding...........................................................................12-54
5 Table 12.3.1.3.3.4-1. DRC Channel transmission and FeedbackMultiplexingMethod .12-58
9 Table 12.3.1.3.3.5-1. ACK Channel transmission and FeedbackMultiplexingMethod
10 if DSC Channel is transmitted using that FeedbackMultiplexingMethod...............12-63
11 Table 12.3.1.3.3.5-2. ACK Channel transmission and FeedbackMultiplexingMethod
12 if DSC Channel is not transmitted using that FeedbackMultiplexingMethod.........12-64
14 Table 12.3.1.3.3.6-1. Data Channel Modulation Formats ...........................................12-65
15 Table 12.3.1.3.4-1. Parameters for the Reverse Link Encoder for the Access Channel 12-66
17 Channel – Part 1 of 2 ............................................................................................12-66
19 Channel – Part 2 of 2 ............................................................................................12-67
20 Table 12.3.1.3.4.2.2-1. Puncturing Patterns for the Data Bit Periods..........................12-70
21 Table 12.3.1.3.4.2.2-2. Puncturing Patterns for the Tail Bit Periods ...........................12-70
22 Table 12.3.1.3.4.2.3-1. Turbo Interleaver Parameter ..................................................12-72
23 Table 12.3.1.3.4.2.3-2. Turbo Interleaver Lookup Table Definition .............................12-73
26 Table 12.3.1.3.7.2-1. Channel Interleaver Parameters ................................................12-78
27 Table 12.3.1.3.9.1-1. B4 Modulation Table.................................................................12-80
32 Table 12.3.1.3.12.2-1. Additional Long Code Masks for Reverse Traffic Channel in
33 BasicFeedbackMultiplexing mode and EnhancedFeedbackMultiplexing mode ......12-89
xcix
3GPP2 C.S0024-B v2.0
TABLES
1 Table 12.3.1.3.12.3-1. Baseband Filter Coefficients ................................................... 12-91

2 Table 12.3.2.4-1. H-ARQ Transmission Rules ............................................................ 12-95
4 the Control Channel........................................................................................... 12-109
5 Table 12.4.1.3.1.1-2. Modulation Parameters for the Optional Packet Formats on
6 the Forward Traffic Channel............................................................................... 12-110
7 Table 12.4.1.3.1.1-3. Modulation Parameters for the MAC Channel ......................... 12-111
8 Table 12.4.1.3.2.2-1. Forward Link MAC Channel Assignment ................................ 12-112
9 Table 12.4.1.3.2.2-2. MAC Channel Versus MACIndex............................................. 12-116
10 Table 12.4.1.3.2.2-3. Preamble Use Versus MACIndex ............................................. 12-117
11 Table 12.4.1.3.2.3.1-1. Preamble Repetition............................................................. 12-123
12 Table 12.4.1.3.2.3.1-2. Extended Span and Extension Preamble Transmit Slot and
13 Repetition........................................................................................................... 12-125
14 Table 12.4.1.3.2.3.2-1. Parameters of the Forward Link Encoder ............................. 12-127
15 Table 12.4.1.3.2.3.2.1-1. Puncturing Patterns for the Data Bit Periods .................... 12-131
16 Table 12.4.1.3.2.3.2.1-2. Puncturing Patterns for the Tail Bit Periods ...................... 12-131
17 Table 12.4.1.3.2.3.2.2-1. Turbo Interleaver Parameter ............................................. 12-133
18 Table 12.4.1.3.2.3.2.2-2. Turbo Interleaver Lookup Table Definition ........................ 12-134
19 Table 12.4.1.3.2.3.3-1. Parameters Controlling the Scrambler Initial State .............. 12-136
20 Table 12.4.1.3.2.3.4.3-1. Channel Interleaver Parameters........................................ 12-141
21 Table 12.4.1.3.2.3.5.1-1. QPSK Modulation Table .................................................... 12-143
22 Table 12.4.1.3.2.3.5.2-1. 8-PSK Modulation Table ................................................... 12-144
25 Table 12.4.1.3.2.3.6-1. Sequence Repetition and Symbol Puncturing Parameters .... 12-151
27 Figure 12.4.1.3.3-1 ............................................................................................ 12-155
29 Figure 12.4.1.3.3-2 ............................................................................................ 12-156
31 Figure 12.4.1.3.3-3 ............................................................................................ 12-157
33 Figure 12.4.1.3.3-4 ............................................................................................ 12-159
c
3GPP2 C.S0024-B v2.0
TABLES

2 Figure 12.4.1.3.3-5.............................................................................................12-159
3 Table 12.4.1.3.3-6. Preamble, Pilot, MAC, and Data Multiplexing Parameters ..........12-161
4 Table 12.4.1.3.5.1-1. Baseband Filter Coefficients....................................................12-165
5 Table 13.1-1. SystemType Encoding .............................................................................13-1
6 Table 13.2-1. ATIType Field Encoding ..........................................................................13-3
7 Table 13.8-1. The Format of the Session State Information Record...............................13-9
8 Table 13.8-2. Encoding of the ParameterType Field ....................................................13-10
9 Table 14.1-1. Protocol Type and Subtypes ....................................................................14-2
10
ci
3GPP2 C.S0024-B v2.0
TABLES
1 No text
cii
3GPP2 C.S0024-B v2.0
FOREWORD
1 (This foreword is not part of this Standard)

2 This standard was prepared by Technical Specification Group C of the Third Generation
3 Partnership Project 2 (3GPP2). This standard is evolved from and is a companion to the
4 cdma2000®1 standards. This air interface standard provides high rate packet data services.
5
1 “cdma2000® is the trademark for the technical nomenclature for certain specifications and standards
of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication),
cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the
United States.”
ciii
3GPP2 C.S0024-B v2.0
REFERENCES
1 The following documents contain provisions, which, through reference in this text,
2 constitute provisions of this document. References are either specific (identified by date of
3 publication, edition number, version number, etc.) or non-specific. For a specific reference,
4 subsequent revisions do not apply. For a non-specific reference, the latest version applies.
5 In the case of a reference to a 3GPP2 document, a non-specific reference implicitly refers to
6 the latest version of that document in the same Release as the present document.
7
8 [1] P.S0001, Wireless IP Network Standard.
9 [2] C.S0002, Physical Layer Standard for cdma2000 Spread Spectrum Systems.
10 [3] C.S0005, Upper Layer (Layer 3) Signaling Specification for cdma2000 Spread
11 Spectrum Systems.
12 [4] C.S0032, Recommended Minimum Performance Standards for cdma2000 High

13 Rate Packet Data Access Network.
14 [5] C.S0033, Recommended Minimum Performance Standards for cdma2000 High

15 Rate Packet Data Access Terminal.
16 [6] FIPS PUB 180-1, Federal Information Processing Standards Publication 180-1.
17 [7] Internet Engineering Task Force (IETF) RFC 2409, The Internet Key Exchange
18 (IKE).
19 [8] A.S0009, Interoperability Specification (IOS) for High Rate Packet Data (HRPD)
20 Access Network Interfaces.
21 [9] A.S0008, Interoperability Specification (IOS) for High Rate Packet Data (HRPD)
22 Access Network Interfaces.
23 [10] C.R1001, Administration of Parameter Value Assignments for cdma2000 Spread

24 Spectrum Standards. (Informative)
25 [11] IETF RFC 2373, IP Version 6 Addressing Architecture.
26 [12] ITU-T Recommendation E.212, Identification Plan for Land Mobile Stations, 1988.
27 [13] IETF RFC 3056, Connection of IPv6 Domains via IPv4 Clouds, February 2001.
28 [14] C.S0054, cdma2000 High Rate Broadcast-Multicast Packet Data Air Interface
29 Specification.
30 [15] C.S0057, Band Class Specification for cdma2000 Spread Spectrum Systems.
31 [16] C.S0004, Signaling Link Access Control (LAC) standard for cdma2000 Spread
32 Spectrum Systems.
33 [17] IETF RFC 1662, PPP in HDLC-like Framing.
34 [18] X.S0011, cdma2000 Wireless IP Network Standard.
civ
3GPP2 C.S0024-B v2.0
REFERENCES
1 [19] C.S0072, Mobile Station Equipment Identifier (MEID) Support for cdma2000
2 Spread Spectrum Systems.
3 [20] C.S0063, cdma2000 High Rate Packet Data Supplemental Services.
cv
3GPP2 C.S0024-B v2.0
REFERENCES
1 No text
cvi
Overview 3GPP2 C.S0024-B v2.0
1 1 OVERVIEW
2 1.1 Scope of This Document

3 These technical requirements form a compatibility standard for cdma2000 high rate packet
4 data systems. These requirements ensure that a compliant access terminal can obtain
5 service through any access network conforming to this standard. These requirements do
6 not address the quality or reliability of that service, nor do they cover equipment
7 performance or measurement procedures.
8 This specification is primarily oriented toward requirements necessary for the design and
9 implementation of access terminals. As a result, detailed procedures are specified for
10 access terminals to ensure a uniform response to all access networks. Access network
11 procedures, however, are specified only to the extent necessary for compatibility with those
12 specified for the access terminal.
13 This specification includes provisions for future service additions and expansion of system
14 capabilities. The architecture defined by this specification permits such expansion without
15 the loss of backward compatibility to older access terminals.
16 This compatibility standard is based upon spectrum allocations that have been defined by
17 various governmental administrations. Those wishing to deploy systems compliant with
18 this standard should also take notice of the requirement to be compliant with the
19 applicable rules and regulations of local administrations. Those wishing to deploy systems
20 compliant with this standard should also take notice of the electromagnetic exposure
21 criteria for the general public and for radio frequency carriers with low frequency amplitude
22 modulation.
23 1.2 Requirements Language

24 Compatibility, as used in connection with this standard, is understood to mean: Any access
25 terminal can obtain service through any access network conforming to this standard.
26 Conversely, all access networks conforming to this standard can service access terminals.
27 “Shall” and “shall not” identify requirements to be followed strictly to conform to the
28 standard and from which no deviation is permitted. “Should” and “should not” indicate that
29 one of several possibilities is recommended as particularly suitable, without mentioning or
30 excluding others, that a certain course of action is preferred but not necessarily required,
31 or that (in the negative form) a certain possibility or course of action is discouraged but not
32 prohibited. “May” and “need not” indicate a course of action permissible within the limits of
33 the standard. “Can” and “cannot” are used for statements of possibility and capability,
34 whether material, physical, or causal.
35 1.3 Architecture Reference Model

36 The architecture reference model is presented in Figure 1.3-1. The reference model consists
37 of the following functional units:
1-1
3GPP2 C.S0024-B v2.0 Overview
Air Interface
Sector
Access Terminal Access Network

1
2 Figure 1.3-1. Architecture Reference Model
3 The access terminal, the access network, and the sector are formally defined in 1.11.
4 The reference model includes the air interface between the access terminal and the access
5 network. The protocols used over the air interface are defined in this document.
6 1.4 Protocol Architecture

7 The air interface has been layered, with interfaces defined for each layer (and for each
8 protocol within each layer). This allows future modifications to a layer or to a protocol to be
9 isolated.
10 1.4.1 Layers
11 Figure 1.4.1-1 describes the layering architecture for the air interface. Each layer consists
12 of one or more protocols that perform the layer’s functionality. Each of these protocols can
13 be individually negotiated.
Application Layer
Stream Layer
Session Layer
Connection Layer
Security Layer
MAC Layer
Physical Layer
14
15 Figure 1.4.1-1. Air Interface Layering Architecture
16 The protocols and layers specified in Figure 1.4.1-1 are:

17 Application Layer: The Application Layer provides multiple applications. It provides the
18 Default Signaling Application for transporting air interface protocol messages. The
19 Default Signaling Application is defined in Chapter 2. It also provides the Default
20 Packet Application for transporting user data. The Default Packet Application is
21 defined in Chapter 3.
1-2
1 Stream Layer: The Stream Layer provides multiplexing of distinct application streams.
2 The Default Stream Protocol provides four streams. Stream 0 is dedicated to
3 signaling and defaults to the Default Signaling Application (see Chapter 2). Stream
4 1, Stream 2, and Stream 3 are not used by default. The Stream Layer is defined in
5 Chapter 4 Chapter 65. The Generic Virtual Stream Protocol provides 255 virtual
6 streams to which applications may be bound.
7 Session Layer: The Session Layer provides address management, protocol negotiation,
8 protocol configuration and state maintenance services. The Session Layer is defined
9 in Chapter 6.
10 Connection Layer: The Connection Layer provides air link connection establishment
11 and maintenance services. The Connection Layer is defined in Chapter 7.
12 Security Layer: The Security Layer provides authentication and encryption services. The
13 Security Layer is defined in Chapter 8.
14 MAC Layer: The Medium Access Control (MAC) Layer defines the procedures used to
15 receive and to transmit over the Physical Layer. The MAC Layer is defined in
16 Chapter 9.
17 Physical Layer: The Physical Layer provides the channel structure, frequency, power
18 output, modulation, and encoding specifications for the Forward and Reverse
19 Channels. The Physical Layer is defined in Chapters 10, 11, and 12.
20 Each layer may contain one or more protocols. Protocols use signaling messages or headers
21 to convey information to their peer protocols at the other side of the air-link. When
22 protocols and applications send messages, they use the Signaling Network Protocol (SNP) to
23 transmit these messages.
24 1.5 Physical Layer Channels

25 The Physical Layer defines the Physical Layer Channels and the Forward and Reverse
26 Channel hierarchies shown in Figure 1.5-1 and Figure 1.5-2. Channel x is part of Channel
27 y if y is an ancestor of x. The specific channels are defined in 1.11. When the context is
28 clear, the complete qualified name is usually omitted (e.g., Pilot Channel as opposed to
29 Forward Pilot Channel or Data Channel as opposed to Reverse Traffic Data Channel).
Forward
Medium
Pilot Access Control Traffic
Control
Reverse
Reverse
DRCLock Power ARQ
Activity
Control
30
31 Figure 1.5-1. Forward Channel Structure
1-3
4 Figure 1.5-2. Reverse Channel Structure
5 1.6 Protocols
6 1.6.1 Interfaces
7 This standard defines a set of interfaces for communications between protocols in the same
8 entity and between a protocol executing in one entity and the same protocol executing in
9 the other entity.
10 In the following the generic term “entity” is used to refer to the access terminal and the
11 access network.
12 Protocols in this specification have four types of interfaces:
13 • Headers and messages are used for communications between a protocol executing in
14 one entity and the same protocol executing in the other entity.
15 • Commands are used by a protocol to obtain a service from another protocol within the
16 same access network or access terminal. For example, AccessChannelMAC.Abort causes
17 the Access Channel MAC Protocol to abort any access attempt currently in progress.
1-4
1 • Indications are used by a protocol to convey information regarding the occurrence of an

2 event to another protocol within the same access network or access terminal. Any
3 protocol can register to receive these indications. For example, the access terminal
4 Reverse Traffic Channel MAC Protocol returns a “Reverse Link Acquired” indication
5 when it gets a message from its peer protocol at the access network that it has acquired
6 the Reverse Traffic Channel. This notification is then used by Connection Layer
7 protocols to continue with the handshake leading to the establishment of the
8 connection.
9 • Public Data is used to share information in a controlled way between
10 protocols/applications. Public data is shared between protocols/applications in the
11 same layer, as well as between protocols/applications in different layers. The public
12 data of the InUse protocol/application is created when an InUse instance (see 1.6.3) of
13 a protocol/application is created. An example of this is the MinimumProtocolRevision
14 made public by the Connection Layer Initialization State Protocol after the protocol
15 receives it in the Sync message. All configurable attributes of the InConfiguration
16 instance of a protocol or application are also public data of that protocol or application.
17 Commands and indications are written in the form of Protocol.Command and
18 Protocol.Indication. For example, AccessChannelMAC.Activate is a command activating the
19 Access Channel MAC, and IdleState.ConnectionOpened is an indication provided by the
20 Connection Layer Idle State Protocol that the connection is now open. When the context is
21 clear, the Protocol part is dropped (e.g., within the Idle State Protocol, Activate refers to
22 IdleState.Activate).
23 Commands are always written in the imperative form, since they direct an action.
24 Indications are always written in the past tense since they notify of events that happened
25 (e.g., OpenConnection for a command and ConnectionOpened for an indication).
26 Headers and messages are binding on all implementations. Commands, indications, and
27 public data are used as a device for a clear and precise specification. Access terminals and
28 access networks can be compliant with this specification while choosing a different
29 implementation that exhibits identical behavior.
30 1.6.2 States
31 When protocols exhibit different behavior as a function of the environment (e.g., if a
32 connection is opened or not, if a session is opened or not, etc.), this behavior is captured in
33 a set of states and the events leading to a transition between states.
34 Unless otherwise specifically mentioned, the state of the access network refers to the state
35 of a protocol engine in the access network as it applies to a particular access terminal.
36 Since the access network communicates with multiple access terminals, multiple
37 independent instantiations of a protocol will exist in the access network, each with its own
38 independent state machine.
39 Unless otherwise specifically shown, the state transitions due to failure are not shown in
40 the figures.
1-5
1 Typical events leading to a transition from one state to another are the receipt of a
2 message, a command from a higher layer protocol, an indication from a lower layer
3 protocol, or the expiration of a timer.
4 When a protocol is not functional at a particular time (e.g., the Access Channel MAC
5 protocol at the access terminal when the access terminal has an open connection) the
6 protocol is placed in a state called the Inactive state. This state is common for most
7 protocols.
8 Other common states are Open, indicating that the session or connection (as applicable to
9 the protocol) is open and Close, indicating that the session or connection is closed.
10 If a protocol has a single state other than the Inactive state, that state is always called the
11 Active state. If a protocol has more than one state other than the Inactive state, all of these
12 states are considered active, and are given individual names (e.g., the Forward Traffic
13 Channel MAC protocol has three states: Inactive, Variable Rate, and Fixed Rate).
14 1.6.3 InUse and InConfiguration Protocol/Application Instances

15 A protocol/application instance can be either an InUse instance or an InConfiguration
16 instance.
17 1.6.3.1 InConfiguration Instantiation

18 An InConfiguration instance of each protocol is created by the Session Configuration
19 Protocol once the session configuration is initiated (e.g., in the Default Session
20 Configuration Protocol this occurs once entering the AT Initiated state).
21 1.6.3.1.1 Protocol Instantiation

22 InConfiguration protocol instances can be changed by the Session Configuration Protocol.
23 Once the access terminal and access network agree upon using a new protocol subtype for
24 a certain protocol Type, an InConfiguration protocol instance associated with the newly
25 negotiated protocol (specified by its protocol subtype) is created and the existing
26 InConfiguration protocol instance for that protocol Type is replaced by the newly negotiated
27 one.
28 1.6.3.1.2 Application Instantiation

29 InConfiguration application instances are created by the Stream Layer protocol. Once the
30 access terminal and access network agree upon using a new application subtype for a
31 certain stream, an InConfiguration application instance associated with the newly
32 negotiated application (specified by its application subtype) is created, and the existing
33 InConfiguration application instance for that stream is replaced by the newly negotiated
34 one.
35 1.6.3.2 Protocol Initialization

36 The initialization procedures for an InUse protocol/application instance are invoked upon
37 creation of the InUse protocol/application instance.
1-6
1 The initialization procedures for an InConfiguration protocol/application instance are

2 invoked upon creation of the InConfiguration protocol/application instance.
3 1.6.3.3 Procedures and Messages

4 Each protocol/application specifies procedures and messages corresponding to the InUse
5 and InConfiguration protocol/application instances. In general, the InConfiguration
6 protocol/application instances process messages that are related to parameter
7 configuration for each protocol/application, while non-configuration procedures and
8 messages are processed by the InUse protocol/application instances. Each
9 protocol/application specifies procedures and messages corresponding to the InUse and
10 InConfiguration protocol/application instances.
11 1.6.3.3.1 Commit Procedures

12 Each InConfiguration protocol/application defines a set of Commit procedures. The
13 Commit procedures for a protocol/application are invoked by the InUse instance of the
14 Session Configuration Protocol.
15 If the Commit procedures for an InConfiguration protocol instance set the state of the
16 protocol instance to a particular initial state and the InConfiguration protocol instance
17 becomes the InUse protocol instance, the procedures associated with entering the initial
18 state are to be executed at that time
19 If the Commit procedures for an InConfiguration protocol instance set the state of the
20 InUse protocol instance to a particular initial state, the procedures associated with entering
21 the initial state are executed upon entering the initial state.
22 1.6.4 Common Commands

23 Most protocols support the following two commands:
24 • Activate, which commands the protocol to transition from the Inactive state to some
25 other state.
26 • Deactivate, which commands the protocol to transition to the Inactive state. Some
27 protocols do not transition immediately to the Inactive state, due to requirements on
28 orderly cleanup procedures.
29 Other common commands are Open and Close, which command protocols to perform
30 session open / close or connection open / close related functions.
31 1.6.5 Protocol Negotiation

32 Most protocols can be negotiated and can be configured when the session is set-up (see 1.9
33 for a discussion of sessions). Protocols are associated with a Type that denotes the type of
34 the protocol (e.g., Access Channel MAC Protocol) and with a Subtype that denotes a specific
35 instance of a protocol (e.g., the Default Access Channel MAC Protocol).
36 The negotiation and configuration processes are part of the Session Layer.
1-7
1 1.6.6 Protocol Overview

2 Figure 1.6.6-1 presents the default protocols defined for each one of the layers shown in
3 Figure 1.4.1-1. The following is a brief description of each protocol. A more complete
4 description is provided in the Introduction section of each layer. Figure 1.6.6-2 presents
5 the non-default protocols defined in this specification for each one of the layers shown in
6 Figure 1.4.1-1.
Default Signaling Default Packet

Application Application
Flow
Signaling Control
Network Protocol Application
Protocol
Layer
Signaling
Radio Link Location Update
Link
Protocol Protocol
Protocol
Stream Stream
Protocol Layer
Session Address Session

Session
Management Management Configuration
Protocol Protocol Protocol Layer
Air Link
Initialization State Idle State Connected State
Management
Protocol Protocol Protocol
Protocol
Connection
Layer
Packet Overhead
Route Update
Consolidation Messages
Protocol
Protocol Protocol
Key Security
Security Authentication Encryption
Exchange
Protocol
Forward Traffic Reverse Traffic

Control Channel Access Channel MAC
Channel MAC Channel MAC
MAC Protocol MAC Protocol Layer
Protocol Protocol
Subtype 0 Physical
Physical Layer
Protocol Layer
9 Figure 1.6.6-1. Default Protocols
1-8
Multi-flow Packet CDMA2000 Circuit

Application Services Notification
Flow Data Over Application
Control Signaling
Protocol Protocol CDMA2000 Application
Circuit Services
Notification Layer
Protocol
Protocol Protocol
Generic Virtual Stream

Stream Protocol Layer
Generic
Multimode
Session
Capability
Discovery Layer
Protocol
Enhanced Idle MultiCarrier

Quick Idle State Connection
State Route Update
Protocol Layer
Protocol Protocol
DH Key SHA-1 Security

Generic Security
Exchange Authentication
Protocol Layer
Protocol Protocol
Enhanced Multicarrier
Enhanced Control Enhanced Access
Forward Traffic Forward Traffic
Protocol Protocol
Protocol Protocol
MAC
Subtype 1 Subtype 2 Subtype 3 Multicarrier Layer
Reverse Traffic Reverse Traffic Reverse Traffic Reverse Traffic
Channel MAC Channel MAC Channel MAC Channel MAC
Protocol Protocol Protocol Protocol
Subtype 1 Subtype 2 Subtype 3

Physical
Physical Layer Physical Layer Physical Layer
1-9
Multi-flow Packet
Application
Flow Data Over
Control Signaling
Protocol Protocol Application
Layer
Protocol Protocol
Generic Virtual Stream

Stream Protocol Layer
Generic
Multimode
Session
Capability
Discovery Layer
Protocol
Enhanced Idle MultiCarrier

Quick Idle State Connection
State Route Update
Protocol Layer
Protocol Protocol
DH Key SHA-1 Security

Generic Security
Exchange Authentication
Protocol
Protocol Protocol Layer
Enhanced Multicarrier
Enhanced Control Enhanced Access
Forward Traffic Forward Traffic
Protocol Protocol
Protocol Protocol
MAC
Subtype 1 Subtype 2 Subtype 3 Multicarrier Layer
Reverse Traffic Reverse Traffic Reverse Traffic Reverse Traffic
Channel MAC Channel MAC Channel MAC Channel MAC
Subtype 1 Subtype 2 Subtype 3

Physical
Physical Layer Physical Layer Physical Layer
2 Figure 1.6.6-2. Non-Default Protocols
3 • Application Layer:
4 − Default Signaling Application:
5 + Signaling Network Protocol: The Signaling Network Protocol (SNP) provides
6 message transmission services for signaling messages.
7 + Signaling Link Protocol: The Signaling Link Protocol (SLP) provides
8 fragmentation mechanisms, along with reliable and best-effort delivery
9 mechanisms for signaling messages. When used in the context of the Default
10 Signaling Application, SLP carries SNP packets.
1-10
1 − Default Packet Application:

2 + Radio Link Protocol: The Radio Link Protocol (RLP) provides retransmission and
3 duplicate detection for an octet data stream.
4 + Location Update Protocol: The Location Update Protocol defines location update
5 procedures and messages in support of mobility management for the Default
6 Packet Application.
7 + Flow Control Protocol: The Flow Control Protocol defines flow control
8 procedures to enable and disable the Default Packet Application data flow.
9 • Stream Layer:
10 − Stream Protocol: Adds the stream header to application packets prior to
11 transmission; and, after reception, removes the stream header and forwards
12 application packets to the correct application.
13 • Session Layer:
14 − Session Management Protocol: provides means to control the activation and
15 the deactivation of the Address Management Protocol and the Session
16 Configuration Protocol. It also provides a session keep alive mechanism.
17 − Address Management Protocol: Provides access terminal identifier (ATI)
18 management.
19 − Session Configuration Protocol: Provides negotiation and configuration of the
20 protocols used in the session.
21 • Connection Layer:
22 − Air Link Management Protocol: Provides the overall state machine
23 management that an access terminal and an access network follow during a
24 connection.
25 − Initialization State Protocol: Provides the procedures that an access terminal
26 follows to acquire a network and that an access network follows to support
27 network acquisition.
28 − Idle State Protocol: Provides the procedures that an access terminal and an
29 access network follow when a connection is not open.
30 − Connected State Protocol: Provides the procedures that an access terminal and
31 an access network follow when a connection is open.
32 − Route Update Protocol: Provides the means to maintain the route between the
33 access terminal and the access network.
34 − Overhead Messages Protocol: Provides broadcast messages containing
35 information that is mostly used by Connection Layer protocols.
36 − Packet Consolidation Protocol: Provides transmit prioritization and packet
37 encapsulation for the Connection Layer.
38 • Security Layer:
1-11
1 − Key Exchange Protocol: Provides the procedures followed by the access

2 network and the access terminal to exchange security keys for authentication
3 and encryption.
4 − Authentication Protocol: Provides the procedures followed by the access
5 network and the access terminal for authenticating traffic.
6 − Encryption Protocol: Provides the procedures followed by the access network
7 and the access terminal for encrypting traffic.
8 − Security Protocol: Provides procedures for generation of a cryptosync that can
9 be used by the Authentication Protocol and Encryption Protocol.
10 • MAC Layer:
11 − Control Channel MAC Protocol: Provides the procedures followed by the access
12 network to transmit, and by the access terminal to receive the Control
13 Channel.
14 − Access Channel MAC Protocol: Provides the procedures followed by the access
15 terminal to transmit, and by the access network to receive the Access Channel.
16 − Forward Traffic Channel MAC Protocol: Provides the procedures followed by
17 the access network to transmit, and by the access terminal to receive the
18 Forward Traffic Channel.
19 − Reverse Traffic Channel MAC Protocol: Provides the procedures followed by the
20 access terminal to transmit, and by the access network to receive the Reverse
21 Traffic Channel.
22 • Physical Layer:
23 − Physical Layer Protocol: Provides channel structure, frequency, power output
24 and modulation specifications for the forward and reverse links.
25 1.7 Default Applications

26 This document defines two default applications that all compliant access terminals and
27 access networks support:
28 • Default Signaling Application, which provides the means to carry messages between a
29 protocol in one entity and the same protocol in the other entity. The Default Signaling
30 Application consists of a messaging protocol (Signaling Network Protocol) and a link
31 layer protocol that provides message fragmentation, retransmission and duplicate
32 detection (Signaling Link Protocol).
33 • Default Packet Application. The Default Packet Application consists of a link layer
34 protocol that provides octet retransmission and duplicate detection (Radio Link
35 Protocol), a location update protocol that provides mobility between data service
36 networks and a flow control protocol that provides flow control of data traffic.
37 The applications used and the streams upon which they operate are negotiated as part of
38 session negotiation.
1-12
1 1.8 Streams
2 The air interface can support up to four parallel application streams. The first stream
3 (Stream 0) always carries Signaling, and the other three can be used to carry applications
4 with different Quality of Service (QoS) requirements or other applications.
5 1.9 Sessions and Connections

6 A session refers to a shared state between the access terminal and the access network.
7 This shared state stores the protocols and protocol configurations that were negotiated and
8 are used for communications between the access terminal and the access network.
9 Other than to open a session, an access terminal cannot communicate with an access
10 network without having an open session.
11 A connection is a particular state of the air-link in which the access terminal is assigned a
12 Forward Traffic Channel, a Reverse Traffic Channel and associated MAC Channels.
13 During a single session the access terminal and the access network can open and can close
14 a connection multiple times.
15 1.10 Security
16 The air interface supports a security layer, which can be used for authentication and
17 encryption of access terminal traffic transported by the Control Channel, the Access
18 Channel, the Forward Traffic Channel and the Reverse Traffic Channel.
19 1.11 Terms
20 Access Network (AN). The network equipment providing data connectivity between a
21 packet switched data network (typically the Internet) and the access terminals. An access
22 network is equivalent to a base station in [2].
23 Access Terminal (AT). A device providing data connectivity to a user. An access terminal
24 may be connected to a computing device such as a laptop personal computer or it may be a
25 self-contained data device such as a personal digital assistant. An access terminal is
26 equivalent to a mobile station in [2].
27 ATI. Access Terminal Identifier.
28 Auxiliary Pilot. An unmodulated, direct-sequence spread spectrum signal transmitted by
29 an access terminal in conjunction with certain transmissions on the Reverse Traffic Data
30 Channel. This channel provides an additional phase reference for the Reverse Traffic Data
31 Channel for coherent demodulation and may provide means for improved signal strength
32 measurement.
33 BasicFeedbackMultiplexing mode. At least one of the reverse CDMA channel carries
34 feedback for forward CDMA channels corresponding to more than one sub-Active Set using
35 unique long codes for the feedback channels associated with forward CDMA channels
36 corresponding to each sub-Active Set.
37 BATI. Broadcast Access Terminal Identifier.
38 BPSK. Binary Phase Shift Keying
1-13
1 Cell. A physical grouping of one or more sectors that transmit the same power control
2 command to an access terminal.
3 CDMA System Time in Slots. An integer value s such that: s = ⎣t × 600⎦, where t
4 represents CDMA System Time in seconds. Whenever the document refers to the CDMA
5 System Time in slots, it is referring to the value s.
6 CDMA System Time. The time reference used by the system. CDMA System Time is
7 synchronous to UTC time except for leap seconds and uses the same time origin as GPS
8 time. Access terminals use the same CDMA System Time, offset by the propagation delay
9 from the access network to the access terminal.
10 Channel. The set of channels transmitted between the access network and the access
11 terminals within a given frequency assignment. A Channel consists of a Forward Link and
12 a Reverse Link.
13 Connection Layer. The Connection Layer provides air link connection establishment and
14 maintenance services. The Connection Layer is defined in Chapter 7.
15 Dedicated Resource. An access network resource required to provide any data service to
16 the access terminal, e.g, Wireless IP Service (see [1]) that is granted to the access terminal
17 only after access terminal authentication has completed successfully. Power control and
18 rate control are not considered dedicated resources.
19 DRCLock Channel. The portion of the Forward MAC Channel that indicates to the access
20 terminal whether or not the access network can receive the DRC Channel and Reverse Link
21 Channel sent by the access terminal.
22 Effective Isotropically Radiated Power (EIRP). The product of the power supplied to the
23 antenna and the antenna gain in a direction relative to an isotropic antenna.
24 Effective Radiated Power (ERP). The product of the power supplied to the antenna and its
25 gain relative to a half-wave dipole in a given direction.
26 EnhancedFeedbackMultiplexing mode. At least one of the reverse CDMA channels
27 carries feedback for forward CDMA channels corresponding to up to four sub-Active Sets
28 using one long code.
29 FDD-Paired. A forward CDMA channel and reverse CDMA channel pair where the [15]
30 specification specifies the association between the forward CDMA channel and reverse
31 CDMA channel.
32 Forward Channel. The portion of the Channel consisting of those Physical Layer Channels
33 transmitted from the access network to the access terminal.
34 Forward Control Channel. The channel that carries data to be received by all access
35 terminals monitoring the Forward Channel.
36 Forward MAC Channel. The portion of the Forward Channel dedicated to Medium Access
37 Control activities. The Forward MAC Channel consists of the RPC, DRCLock, and RA
38 Channels.
39 Forward MAC Reverse Activity (RA) Channel. The portion of the Forward MAC Channel
40 that indicates activity level on the Reverse Channel.
1-14
1 Forward MAC Reverse Power Control (RPC) Channel. The portion of the Forward MAC
2 Channel that controls the power of the Reverse Channel for one particular access terminal.
3 Forward Pilot Channel. The portion of the Forward Channel that carries the pilot.
4 Forward Traffic Channel. The portion of the Forward Channel that carries information for
5 a specific access terminal. The Forward Traffic Channel can be used as either a Dedicated
6 Resource or a non-Dedicated Resource. Prior to successful access terminal authentication,
7 the Forward Traffic Channel serves as a non-Dedicated Resource. Only after successful
8 access terminal authentication can the Forward Traffic Channel be used as a Dedicated
9 Resource for the specific access terminal.
10 Frame. The duration of time specified by 16 slots or 26.66… ms.
11 FCS. Frame Check Sequence.
12 Global Positioning System (GPS). A US government satellite system that provides location
13 and time information to users. See Navstar GPS Space Segment/Navigation User Interfaces
14 ICD-GPS-200 for specifications.
15 H-ARQ Bit. Hybrid-ARQ bit. The bit sent on ARQ channel in response to the 1st, 2nd, and
16 3rd sub-packet of a reverse-link physical packet to support physical layer ARQ.
17 L-ARQ Bit. Last ARQ bit. The bit sent on ARQ channel in response to the last sub-packet
18 of a reverse-link physical packet to support MAC layer ARQ.
19 MAC Layer. The MAC Layer defines the procedures used to receive and to transmit over
20 the Physical Layer. The MAC Layer is defined in Chapter 9.
21 MATI. Multicast Access Terminal Identifier.
22 Multi-User packet. A single physical layer packet composed of zero or more security layer
23 packets addressed to one or more access terminals.
24 NULL. A value which is not in the specified range of the field.
25 NoFeedbackMultiplexing mode. In NoFeedbackMultiplexing mode each reverse CDMA
26 channel carries the feedback channels for the forward CDMA channels corresponding to at
27 most one sub-Active Set.
28 Physical Layer Protocol. The Physical Layer Protocol provides the channel structure,
29 frequency, power output, modulation, and encoding specifications for the forward and
30 reverse links. The Subtype 0 and Subtype 1 Physical Layer is defined in 10 and the
31 Subtype 2 Physical Layer is defined in 11 and Subtype 3 Physical Layer is defined in 12.
32 P-ARQ. Packet-ARQ bit. The bit sent on the ARQ channel in response to a reverse-link
33 physical layer packet to support MAC layer ARQ.
34 QPSK. Quadrature Phase Shift Keying
35 QAM. Quadrature Amplitude Modulation
36 RATI. Random Access Terminal Identifier.
37 Reservation. Air interface resources set up by the access network to carry a higher layer
38 flow. A Reservation is identified by its ReservationLabel. ReservationLabels are bound to
1-15
1 RLP Flows that carry higher layer flows. A Reservation can be either in the Open or Close
2 state.
3 Reverse Access Channel. The portion of the Reverse Channel that is used by access
4 terminals to communicate with the access network when they do not have a traffic channel
5 assigned. There is a separate Reverse Access Channel for each sector of the access
6 network.
7 Reverse Access Data Channel. The portion of the Access Channel that carries data.
8 Reverse Access Pilot Channel. The portion of the Access Channel that carries the pilot.
9 Reverse Channel. The portion of the Channel consisting of those Physical Layer Channels
10 transmitted from the access terminal to the access network.
11 Reverse Traffic Ack Channel. The portion of the Reverse Traffic Channel that indicates
12 the success or failure of the Forward Traffic Channel reception.
13 Reverse Traffic Channel. The portion of the Reverse Channel that carries information
14 from a specific access terminal to the access network. The Reverse Traffic Channel can be
15 used as either a Dedicated Resource or a non-Dedicated Resource. Prior to successful
16 access terminal authentication, the Reverse Traffic Channel serves as a non-Dedicated
17 Resource. Only after successful access terminal authentication can the Reverse Traffic
18 Channel be used as a Dedicated Resource for the specific access terminal.
19 Reverse Traffic Data Channel. The portion of the Reverse Traffic Channel that carries
20 user data.
21 Reverse Traffic MAC Channel. The portion of the Reverse Traffic Channel dedicated to
22 Medium Access Control activities. The Reverse Traffic MAC Channel consists of the RRI and
23 DRC Channels.
24 Reverse Traffic MAC Data Rate Control (DRC) Channel. The portion of the Reverse
25 Traffic Channel that indicates the rate at which the access terminal can receive the
26 Forward Traffic Channel and the sector from which the access terminal wishes to receive
27 the Forward Traffic Channel.
28 Reverse Traffic MAC Data Source Control (DSC) Channel. The portion of the Reverse
29 Traffic Channel that indicates the data source from which the access terminal wishes to
30 receive the Forward Traffic Channel.
31 Reverse Traffic MAC Reverse Rate Indicator (RRI) Channel. The portion of the Reverse
32 Traffic Channel that indicates the rate of the Reverse Traffic Data Channel.
33 Reverse Traffic Pilot Channel. The portion of the Reverse Traffic Channel that carries the
34 pilot.
35 Reverse Traffic Auxiliary Pilot Channel. The portion of the Reverse Traffic Channel that
36 carries the auxiliary pilot.
37 RLP. Radio Link Protocol provides retransmission and duplicate detection for an octet-
38 aligned data stream.
39 Rx. Receive.
1-16
1 Sector. The part of the access network that is identified by (SectorID, CDMA Channel).
2 Security Layer. The Security Layer provides authentication and encryption services. The
3 Security Layer is defined in Chapter 87.
4 Session Layer. The Session Layer provides protocol negotiation, protocol configuration,
5 and state maintenance services. The Session Layer is defined in Chapter 6.
6 Single User packet. A single physical layer packet consisting of one or more security layer
7 packets addressed to one access terminal.
8 Slot. A duration of time specified by 1.66… ms.
9 SLP. Signaling Link Protocol provides best-effort and reliable-delivery mechanisms for
10 signaling messages. SLP is defined in 2.6.
11 SNP. Signaling Network Protocol provides message transmission services for signaling
12 messages. The protocols that control each layer use SNP to deliver their messages to their
13 peer protocols.
14 Stream Layer. The Stream Layer provides multiplexing of distinct streams. Stream 0 is
15 dedicated to signaling and defaults to the default signaling stream (SNP / SLP). Stream 1,
16 Stream 2, and Stream 3 are not used by default. The Stream Layer is defined in Chapter
17 45.
18 Sub-Frame. A sub-frame is a group of four contiguous slots. The start of a sub-frame is
19 specified by (T ─ FrameOffset) mod 4 = 0, where T is the CDMA System Time in slots.
20 Sub-packet. A sub-packet is the smallest unit of a Reverse Traffic Channel transmission
21 that can be acknowledged at the physical layer by the access network. A sub-packet is
22 transmitted over four contiguous slots.
23 Subnet Mask (of length n). A 128-bit value whose binary representation consists of n
24 consecutive ‘1’s followed by 128-n consecutive ‘0’s.
25 Tx. Transmit.
26 TxT2P. Transmitted Traffic Channel to Pilot Channel transmit power ratio.
27 T2P. Traffic Channel to Pilot Channel transmit power ratio.
28 UATI. Unicast Access Terminal Identifier.
29 Universal Coordinated Time (UTC). An internationally agreed-upon time scale maintained
30 by the Bureau International de l’Heure (BIH) used as the time reference by nearly all
31 commonly available time and frequency distribution systems.
32 UTC. Universal Temps Coordine. See Universal Coordinated Time.
33 1.12 Notation
34 A[i] The ith element of array A. The first element of the array is A[0].
35 <e1, e2, …, en> A structure with elements ‘e1’, ‘e2’, …, ‘en’.

36 Two structures E = <e1, e2, …, en> and F = <f1, f2, …, fm> are equal if
1-17
1 and only if ‘m’ is equal to ‘n’ and ei is equal to fi for i=1, …n.
2 Given E = <e1, e2, …, en> and F = <f1, f2, …, fm>, the assignment “E =
3 F” denotes the following set of assignments: ei = fi, for i=1, …n.
4 S.e The member of the structure ‘S’ that is identified by ‘e’.
5 M[i:j] Bits ith through jth inclusive (i ≥ j) of the binary representation of

6 variable M. M[0:0] denotes the least significant bit of M.
7 | Concatenation operator. (A | B) denotes variable A concatenated with

8 variable B.
9 × Indicates multiplication.
10 ⎣x⎦ Indicates the largest integer less than or equal to x: ⎣1.1⎦ = 1, ⎣1.0⎦ =
11 1.
12 ⎡x⎤ Indicates the smallest integer greater or equal to x: ⎡1.1⎤ = 2, ⎡2.0⎤ =

13 2.
14 |x| Indicates the absolute value of x: |–17|=17, |17|=17.
15 ⊕ Indicates exclusive OR (modulo-2 addition).
16 ⊗ Indicates bitwise logical AND operator.
17 min (x, y) Indicates the minimum of x and y.
18 max (x, y) Indicates the maximum of x and y.
19 x mod y Indicates the remainder after dividing x by y: x mod y = x – (y ×

20 ⎣x/y⎦).
21 x^y Indicates the result of x raised to the power y, also denoted as xy.
22 xy Indicates the result of x raised to the power y, also denoted as x^y.

23 Unless otherwise specified, the format of field values is unsigned binary.
24 Unless indicated otherwise, this standard presents numbers in decimal form. Binary
25 numbers are distinguished in the text by the use of single quotation marks. Hexadecimal
26 numbers are distinguished by the prefix ‘0x’.
27 Unless specified otherwise, each field of a packet shall be transmitted in sequence such
28 that the most significant bit (MSB) is transmitted first and the least significant bit (LSB) is
29 transmitted last. The MSB is the left-most bit in the figures in this document. If there are
30 multiple rows in a table, the top-most row is transmitted first. If a table is used to show the
31 sub-fields of a particular field or variable, the top-most row consists of the MSBs of the
32 field. Within a row in a table, the left-most bit is transmitted first. Notations of the form
1-18
1 “repetition factor of N” or “repeated N times” mean that a total of N versions of the item are
2 used.
3 1.13 Malfunction Detection

4 The access terminal shall have a malfunction timer that is separate from and independent
5 of all other functions and that runs continuously whenever power is applied to the
6 transmitter of the access terminal. The timer shall expire if the access terminal detects a
7 malfunction. If the timer expires, the access terminal shall be inhibited from transmitting.
8 The maximum time allowed for expiration of the timer is two seconds.
9 1.14 CDMA System Time

10 All sector air interface transmissions are referenced to a common system-wide timing
11 reference that uses the Global Positioning System (GPS) time, which is traceable to and
12 synchronous with Universal Coordinated Time (UTC). GPS and UTC differ by an integer
13 number of seconds, specifically the number of leap second corrections added to UTC since
14 January 6, 1980. The start of CDMA System Time is January 6, 1980 00:00:00 UTC, which
15 coincides with the start of GPS time.
16 CDMA System Time keeps track of leap second corrections to UTC but does not use these
17 corrections for physical adjustments to the CDMA System Time clocks.
18 Figure 1.14-1 shows the relation of CDMA System Time at various points in the system.
19 The access network zero offset pilot PN sequences (as defined in 10.3.1.3.8) and the access
20 terminal common short code PN sequences (as defined in 10.3.1.3.8.1) for the I and Q
21 branches are shown in their initial states at the start of CDMA System Time. The initial
22 state of the access network zero offset pilot PN sequences, both I and Q, is that state in
23 which the next 15 outputs of the pilot PN sequence generator are ‘0’. The initial state of the
24 access terminal common short code PN sequences, both I and Q, is that state in which the
25 output of the short code PN sequence generator is the ‘1’ following 15 consecutive ‘0’
26 outputs.
27 From Figure 1.14-1, note that the CDMA System Time at various points in the
28 transmission and the reception processes is the absolute time referenced at the access
29 network antenna offset by the one-way or round-trip delay of the transmission, as
30 appropriate. Time measurements are referenced to the transmit and receive antennas of
31 the access network and the RF connector of the Access Terminal. The precise zero instant
32 of CDMA System Time is the midpoint between the ‘1’ prior to the 15 consecutive ‘0’
33 outputs and the immediate succeeding ‘0’ of the access network zero offset pilot PN
34 sequences.
1-19
00:00:00 UTC
Jan 6, 1980
Access Network Zero Offset
'...1' '0(15)1...'
Sector I Pilot PN Sequence
Tx Access Network Zero Offset
'...1' '0(15)1...'
Q Pilot PN Sequence
00:00:00 UTC
Jan 6, 1980
Access Network Zero Offset
Access '...1' '0(15)1...'
I Pilot PN Sequence
Terminal
Rx Access Network Zero Offset
'...1' '0(15)1...'
Q Pilot PN Sequence
Access Terminal Common

Access '...10(15)' '1...'
I Short Code PN Sequence
Terminal
Tx Access Terminal Common
'...10(15)' '1...'
Q Short Code PN Sequence
00:00:00 UTC
Jan 6, 1980
Access Terminal Common

'...10(15)' '1...'
Sector I Short Code PN Sequence
Rx Access Terminal Common
'...10(15)' '1...'
Q Short Code PN Sequence
One-Way Delay One-Way Delay
~ 3 μs/km
~ 5 μs/mi
Notes: (1) Time measurements are made at the antennas of Sectors and the RF connectors of the
Access Terminals.
(2) 0(n) denotes a sequence of n consecutive zeroes.
1
2 Figure 1.14-1. CDMA System Time Line
1-20
1 1.15 Revision Number

2 Access terminals and access networks complying with the requirements of this
3 specification shall set their revision number to 0x01.
1-21
1 No text.
1-22
Default Signaling Application 3GPP2 C.S0024-B v2.0
1 2 DEFAULT SIGNALING APPLICATION
2 2.1 Introduction
3 2.1.1 General Overview

4 The Default Signaling Application encompasses the Signaling Network Protocol (SNP) and
5 the Signaling Link Protocol (SLP). Protocols in each layer use SNP to exchange messages.
6 SNP is also used by application specific control messages.
7 SNP provides a one or two octet header that defines the Type of the protocol and the
8 protocol instance (i.e., InConfiguration or InUse) with which the message is associated. The
9 SNP uses the header to route the message to the appropriate protocol instance.
10 SLP provides message fragmentation, reliable and best-effort message delivery and
11 duplicate detection for messages that are delivered reliably.
12 The relationship between SNP and SLP is illustrated in Figure 2.1.1-1.
Signaling Network Protocol (SNP)
Signaling SLP-D
Link
Protocol
(SLP)
SLP-F
13
14 Figure 2.1.1-1. Default Signaling Layer Protocols
15 The Signaling Link Protocol consists of two sub-layers, the delivery layer, SLP-D, and the
16 fragmentation layer, SLP-F.
17 2.1.2 Public Data

18 This application shall make the following data public:
19 • Subtype for this application
20 2.1.3 Data Encapsulation for the InUse Instance of the Signaling Application
21 Figure 2.1.3-1 and Figure 2.1.3-2 illustrate the relationship between a message, SNP
22 packets, SLP packets, and Stream Layer payloads. Figure 2.1.3-1 shows a case where SLP
23 does not fragment the SNP packet. Figure 2.1.3-2 shows a case where the SLP fragments
24 the SNP packet into more than one SLP-F payload.
2-1
3GPP2 C.S0024-B v2.0 Default Signaling Application
message
SNP SNP SNP

packet header payload
SLP-D SLP-D SLP-D

SLP-F SLP-F SLP-F

Stream
Layer
payload
1
2 Figure 2.1.3-1. Message Encapsulation (Non-fragmented)
message
SNP SNP SNP

SLP-D SLP-D SLP-D

SLP-F SLP-F SLP-F SLP-F SLP-F

...
packets header payload header payload
Stream Stream
Layer ... Layer
payload payload
3
4 Figure 2.1.3-2. Message Encapsulation (Fragmented)
2-2
1 2.2 Protocol Initialization
2 2.2.1 Protocol Initialization for the InConfiguration Application Instance

3 Upon creation, the InConfiguration instance of this application in the access terminal and
4 the access network shall perform the following in the order specified:
5 • The fall-back values of the attributes for this application instance shall be set to the
6 default values specified for each attribute.
7 • If the InUse instance of this application has the same application subtype as this
8 InConfiguration application instance, then the fall-back values of the attributes defined
9 by the InConfiguration application instance shall be set to the corresponding attribute
10 values for the InUse application instance.
11 • The value for each attribute for this protocol instance shall be set to the fall-back value
12 for that attribute.
13 2.2.2 Protocol Initialization for the InUse Application Instance

14 Upon creation, the InUse instance of the Signaling Application in the access terminal and
15 access network shall set the value of the attributes for this application protocol to the
17 2.3 General Signaling Requirements
18 2.3.1 General Requirements

19 The following requirements are common to all protocols that carry messages using SNP and
20 that provide for message extensibility. The access terminal and the access network shall
21 abide by the following rules when generating and processing any signaling message carried
22 by SNP.
23 • Messages are always an integer number of octets in length; and, if necessary, include a
24 Reserved field at the end of the message to make them so. The receiver shall ignore the
25 value of the Reserved fields.
26 • The first field of the message shall be transmitted first. Within each field, the most
27 significant bit of the field shall be transmitted first.
28 • Message identifiers shall be unambiguous for each protocol Type and for each Subtype
29 for all protocols compatible with the Air Interface, defined by MinimumRevision and
30 above.
31 • For future revisions, the transmitter shall add new fields only at the end of a message
32 (excluding any trailing Reserved field). The transmitter shall not add fields if their
33 addition makes the parsing of previous fields ambiguous for receivers whose protocol
34 revision is equal to or greater than MinimumRevision.
35 • The receiver shall discard all unrecognized messages.
36 • The receiver shall discard all unrecognized fields.
2-3
1 • The receiver shall discard a message if any of the fields in the message is set to a value
2 outside of the defined field range, unless the receiver is specifically directed to ignore
3 this field. A field value is outside of the allowed range if a range was specified with the
4 field and the value is not in this range, or the field is set to a value that is defined as
5 invalid. Values that are designated as reserved are considered to be outside of the
6 allowed range.
7 2.3.2 Message Information

8 Each message definition contains information regarding channels on which the message
9 can be transmitted, whether the message requires SLP reliable or best-effort delivery, the
10 addressing modes applicable to the message, and the message priority. This information is
11 provided in the form of a table, an example of which is given in Figure 2.3.2-1.
12
Channels CCsyn SLP Best Effort
Addressing broadcast Priority 30
13 Figure 2.3.2-1. Sample Message Information
14 The following values are defined:

15 • Channels: This information field indicates the Physical Layer Channels on which this
16 message can be transmitted. The sender of the message shall send the message only on
17 the Physical Layer channel(s) indicated by this information field. Values are:
18 − FTC for Forward Traffic Channel or Control Channel given that the Route
19 Update Protocol is in the Connected State,
20 − CC for Control Channel (synchronous, sub-synchronous, or asynchronous
21 capsule),
22 − CCsyn for Control Channel synchronous capsule (including the Control
23 Channel synchronous Sleep State capsule),
24 − CCsubsyn for Control Channel sub-synchronous capsule (including the
25 Control Channel synchronous capsule)
26 − CCsynSS for Control Channel Synchronous Sleep State capsule,
27 − CCsynQ for Control Channel quick synchronous capsule,
28 − AC for Access Channel,
29 − RTC for Reverse Traffic Channel,
30 − BC for Broadcast Channel as defined in [14]
31 • SLP: Signaling Link Protocol requirements. The sender of the message shall send the
32 message only using the SLP in the mode(s) indicated by this information field. Values
33 are:
34 − Best Effort: the message is sent once and is subject to erasure, and
2-4
1 − Reliable: erasures are detected and the message is retransmitted one or more
2 times, if necessary.
3 • Addressing: Addressing modes for the message. The sender of the message shall send
4 the message only with an address type(s) indicated by this information field. Values are:
5 − Broadcast if a broadcast address can be used with this message,
6 − Multicast if a multicast address can be used with this message, and
7 − Unicast if a unicast address can be used with this message.
8 • Priority: A number between 0 and 255 where lower numbers indicate higher priorities.
9 The priority is used by the Connection Layer (specifically, the Packet Consolidation
10 Protocol) in prioritizing the messages for transmission.
11 2.4 Procedures and Messages for the InConfiguration Instance of the Signaling
12 Application
13 2.4.1 Procedures
14 This protocol uses the Generic Configuration Protocol (see 13.7) to define the processing of
15 the configuration messages.
16 2.4.2 Commit Procedures

17 The access terminal and the access network shall perform the procedures specified in this
18 section, in the order specified, when directed by the InUse instance of the Session
19 Configuration Protocol to execute the Commit procedures:
20 • All the public data that are defined by this application, but are not defined by the InUse
21 application instance shall be added to the public data of the InUse application.
22 • If the InUse instance of this application (corresponding to the stream to which this
23 application is bound) has the same subtype as this application instance, then
24 − The access terminal and the access network shall set the attribute values
25 associated with the InUse instance of this application to the attribute values
26 associated with the InConfiguration instance of this application, and
27 − The access terminal and the access network shall purge the InConfiguration
28 instance of the application.
30 application is bound) does not have the same subtype as this application instance, then
31 the access terminal and the access network shall perform the following:
32 − The InConfiguration instance of the Signaling Application at the access
33 terminal and access network shall become the InUse instance for the Signaling
34 Application (corresponding to the stream to which this application is bound).
35 • All the public data not defined by this application shall be removed from the public data
36 of the InUse application.
2-5
1 2.4.3 Message Formats
2 2.4.3.1 ConfigurationRequest
3 The ConfigurationRequest message format is as follows:
4
Field Length (bits)
MessageID 8
TransactionID 8
Zero or more instances of the following record
AttributeRecord Attribute dependent
5 MessageID The sender shall set this field to 0x50.
6 TransactionID The sender shall increment this value for each new
7 ConfigurationRequest message sent.
8 AttributeRecord The format of this record is specified in 13.3.
Channels FTC RTC SLP Reliable
Addressing unicast Priority 40
10 2.4.3.2 ConfigurationResponse
11 The ConfigurationResponse message format is as follows:
12
Field Length (bits)
MessageID 8
TransactionID 8
14 TransactionID The sender shall set this value to the TransactionID field of the
15 corresponding ConfigurationRequest message.
16 AttributeRecord An attribute record containing a single attribute value. If this

17 message selects a complex attribute, only the ValueID field of the
18 complex attribute shall be included in the message. The format of the
19 AttributeRecord is given in 13.3. The sender shall not include more
20 than one attribute record with the same attribute identifier.
2-6

2
3 2.5 Signaling Network Protocol
4 2.5.1 Overview
5 The Signaling Network Protocol (SNP) is a message-routing protocol, and routes messages
6 to protocols specified by the <InConfigurationProtocol, Type> pair of fields provided in the
7 SNP header.
8 The InConfigurationProtocol field in the SNP header determines whether the encapsulated
9 message corresponds to the InUse protocol instance or the InConfiguration protocol
10 instance.
11 The actual protocol indicated by the Type is negotiated during session set-up. For example,
12 Type 0x01 is associated with the Control Channel MAC Protocol. The specific Control
13 Channel MAC Protocol used (and, therefore, the Control Channel MAC protocol generating
14 and processing the messages delivered by SNP) is negotiated when the session is setup.
15 The remainder of the message following the Type field (SNP header) is processed by the
16 protocol specified by the Type.
17 SNP is a protocol associated with the Default Signaling Application. The application
18 subtype for this application is defined in [10].
19 2.5.2 Primitives and Public Data
20 2.5.2.1 Commands
21 This protocol does not define any commands.
22 2.5.2.2 Return Indications

23 This protocol does not return any indications.
24 2.5.3 Protocol Data Unit

25 The protocol data unit for this protocol is an SNP packet. Each SNP packet consists of one
26 message sent by a protocol using SNP.
27 The protocol constructs an SNP packet by adding the SNP header (see 2.5.4.4) in front of
28 the payload. The structure of the SNP packet is shown in Figure 2.5.3-1.
2-7
SNP packet
SNP
message
header
1
2 Figure 2.5.3-1. SNP Packet Structure
3 2.5.4 Procedures and Messages for the InUse Instance of the Protocol
4 2.5.4.1 Procedures
5 SNP receives messages for transmission from multiple protocols. SNP shall add the SNP
6 header to each message and forward it for transmission to SLP.
7 SNP receives messages from SLP. SNP shall route these messages to their associated
8 protocols according to the value of the InConfigurationProtocol and Type field in the SNP
9 header. If InConfigurationProtocol field in the SNP header is set to ‘1’, the SNP shall route
10 the message to the InConfiguration instance of the protocol identified by the Type field,
11 otherwise the SNP shall route the message to the InUse instance of the protocol identified
12 by the Type field.
13 If an SNP message is to be transmitted on the Forward Traffic Channel or on the Reverse
14 Traffic Channel, and if a connection is not open, SNP shall issue an
15 AirLinkManagement.OpenConnection command. SNP should queue all messages requiring
16 transmission in the Forward Traffic Channel or in the Reverse Traffic Channel until the
17 protocol receives an IdleState.ConnectionOpened indication.
18 When SNP receives an SLP.Reset indication, it shall refrain from passing messages from
19 protocols other than SLP for transmission to SLP until it receives an SLP.ResetAcked
20 indication.
21 2.5.4.2 Type Definitions

22 Type definitions associated with the default protocol stack are presented in Table 2.5.4-1.
23 The constant name and protocol layer are provided for informational purposes.
2-8
1 Table 2.5.4-1. Default Protocol Stack Type Values
Type Protocol Constant Layer

Name
0x14 Stream 0 Application NAPP0Type Application
0x13 Stream Protocol NSTRType Stream
0x19 Virtual Stream NVSPType Stream
0x10 Session Management Protocol NSMPType Session
0x11 Address Management Protocol NADMPType Session
Session Configuration
0x12 NSCPType Session
Protocol
Multimode Capability
0x1b NMCDType Session
Discovery
0x0a Air Link Management Protocol NALMPType Connection
0x0b Initialization State Protocol NISPType Connection
0x0c Idle State Protocol NIDPType Connection
0x0d Connected State Protocol NCSPType Connection
0x0e Route Update Protocol NRUPType Connection
0x0f Overhead Messages Protocol NOMPType Connection
0x09 Packet Consolidation Protocol NPCPType Connection
0x08 Security Protocol NSPType Security
0x05 Key Exchange Protocol NKEPType Security
0x06 Authentication Protocol NAPType Security
0x07 Encryption Protocol NEPType Security
Control Channel MAC
0x01 NCCMPType MAC
Protocol
0x02 Access Channel MAC Protocol NACMPType MAC
Forward Traffic Channel MAC
0x03 NFTCMPType MAC
Protocol
Reverse Traffic Channel MAC
0x04 NRTCMPType MAC
Protocol
0x00 Physical Layer Protocol NPHYPType Physical
2 2.5.4.3 Messages
3 No messages are defined for the InUse instance of the protocol.
2-9
1 2.5.4.4 SNP Header

2 The SNP shall place the following header in front of every message that it sends:
3
Field Length (bits)

InConfigurationProtocol 1
Type 7 or 15
4 InConfigurationProtocol
5 InConfiguration or InUse protocol instance flag. The sender shall set
6 this flag to ‘1’ to indicate that the encapsulated message is destined
7 for the InConfiguration instance of the protocol that is identified by
8 the Type field. The sender shall set this flag to ‘0’ to indicate that the
9 encapsulated message is destined for the InUse instance of the
10 protocol that is identified by the Type field.
11 Type Protocol Type. This field has the following format:

12
Sub-Field Length (bits)

Type1 7
Type2 0 or 8
13 Type1 This sub-field shall be set to the seven most significant bits of the
14 Type value for the protocol (as defined in [10]) associated with the
15 encapsulated message.
16 Type2 If the length of the Type value for the protocol associated with the
17 encapsulated message is 7 bits, then this sub-field shall be omitted.
18 Otherwise, this field shall be set to the 8 least significant bits of the
19 Type value for the protocol associated with the encapsulated
20 message.2
21 2.5.4.5 Interface to Other Protocols
22 2.5.4.5.1 Commands
23 This protocol issues the following command:
24 • AirLinkManagement.OpenConnection
25 2.5.4.5.2 Indications
26 This protocol registers to receive the following indications:
27 • IdleState.ConnectionOpened
2 For example, if Type1 is ‘0011010’, then Type2 shall be 8 bits long.
2-10
1 • SLP.Reset
2 • SLP.ResetAcked
2-11
1 2.6 Signaling Link Protocol
2 2.6.1 Overview
3 The Signaling Link Protocol (SLP) has two layers: The delivery layer and the fragmentation
4 layer.
5 The purpose of the SLP delivery layer (SLP-D) is to provide best effort and reliable delivery
6 for SNP packets. SLP-D provides duplicate detection and retransmission for messages
7 using reliable delivery. SLP-D does not ensure in-order delivery of SNP packets.
8 The purpose of the SLP fragmentation layer (SLP-F) is to provide fragmentation for SLP-D
9 packets.
10 SLP is a protocol associated with the default signaling application. The application subtype
11 for this application is defined in [10].
13 2.6.2.1 Commands

16 This protocol returns the following indications:
17 • Reset
18 • ResetAcked

20 The protocol data units of this protocol are an SLP-D packet and an SLP-F packet.
21 2.6.4 Procedures
22 Unless explicitly specified, SLP requirements for the access terminal and the access
23 network are identical; and are, therefore, presented in terms of sender and receiver.
24 2.6.4.1 Reset
25 SLP can only be reset at the initiative of the access network. To reset SLP, the access
26 network shall perform the following:
27 • The access network shall initialize its data structures as described in 2.6.4.3.2 and
28 2.6.4.2.3.2,
29 • The access network shall return a Reset indication, and
30 • The access network shall send a Reset message.
31 Upon receiving a Reset message, the access terminal shall validate the message sequence
32 number as defined in 13.6. If the message is valid, the access terminal shall respond with a
33 ResetAck message and shall initialize its data structures as described in 2.6.4.3.2 and
2-12
1 2.6.4.2.3.2. If the message sequence number of the Reset message is not valid, the access
2 terminal shall discard the message.
3 The SLP in the access network shall return a ResetAcked indication when it receives a
4 ResetAck message with a MessageSequence field equal to the MessageSequence sent in the
5 Reset message. The access network shall set the MessageSequence sent in the first Reset
6 message after reception of a RouteUpdate.ConnectionInitiated indication to one. The access
7 network shall increment the sequence number for every subsequent Reset message it
8 sends.
9 The access terminal shall initialize the reset receive pointer used to validate Reset
10 messages (see 13.6) to 0 when the protocol receives a RouteUpdate.ConnectionInitiated
11 indication.
12 2.6.4.2 Delivery Layer Procedures
13 2.6.4.2.1 General Procedures

14 These procedures apply to both the best effort and reliable delivery modes.
15 2.6.4.2.1.1 Transmitter Requirements

16 The transmitter shall take the packet from the upper layer and add the SLP-D header.
17 The transmitter shall forward the resulting SLP-D packet to the SLP fragmentation layer.
18 2.6.4.2.1.2 Receiver Requirements

19 The receiver shall forward the AckSequenceNumber field of the SLP-D header to the co-
20 located transmitter (see 2.6.4.2.3.3.1).
21 2.6.4.2.2 Best Effort Delivery Procedures
22 2.6.4.2.2.1 Transmitter Requirements

23 The transmitter shall set the SequenceValid field of a best-effort SLP-D packet to ‘0’, if the
24 SequenceValid field is included in the SLP-D packet.
25 2.6.4.2.2.2 Receiver Requirements

26 The receiver shall forward the SLP-D payload to the upper layer.
27 2.6.4.2.3 Reliable Delivery Procedures
28 2.6.4.2.3.1 Overview
29 SLP-D is an Ack-based protocol with a sequence space of S=3 bits.
30 SLP-D maintains the following variables for reliable delivery SLP-D packet payloads:
31 • V(S) The sequence number of the next SLP-D packet to be sent.
32 • V(N) The sequence number of the next expected SLP-D packet.
33 • Rx A 2S bit vector. Rx[i] = ‘1’ if the SLP-D packet with sequence number i was received.
2-13
1 2.6.4.2.3.2 Initialization
2 When SLP-D is initialized or reset it shall perform the following:
3 • Set the send state variable V(S) to zero in the transmitter.
4 • Set the receive state variable V(N) to zero in the receiver.
5 • Set Rx[i] to ‘0’ for i = 0...2S-1.
6 • Clear the retransmission and resequencing buffers.
7 • Discard any SLP-D packets queued for retransmission.
8 When SLP-D is initialized or is reset, the sender shall begin sending SLP-D packets with an
9 initial SequenceNumber of 0.
10 The access terminal and the access network shall perform the initialization procedure if the
11 protocol receives a RouteUpdate.ConnectionInitiated indication.
12 2.6.4.2.3.3 Data Transfer

13 All operations and comparisons performed on SLP-D packet sequence numbers shall be
14 carried out in unsigned modulo 2S arithmetic. For any SLP-D packet sequence number N,
15 the sequence numbers in the range [N+1, N+2S-1-1] shall be considered greater than N and
16 the numbers in the range [N-2S-1, N-1] shall be considered smaller than N.
17 2.6.4.2.3.3.1 Transmit Procedures

18 The transmitter shall set the SequenceValid field of a reliable-delivery SLP-D packet to ‘1’.
19 The transmitter shall acknowledge each reliable-delivery SLP-D packet that its co-located
20 receiver received. The transmitter shall send an acknowledgment within the time specified
21 by TSLPAck of the receiver receiving a reliable-delivery SLP-D packet. The transmitter
22 acknowledges the received SLP-D packet by setting the AckSequenceNumber field of a
23 transmitted SLP-D packet to the SequenceNumber field of the SLP-D packet being
24 acknowledged, and by setting the AckSequenceValid field to ‘1’. The transmitter may use
25 the AckSequenceNumber field of an SLP-D it is transmitting; or, if none is available within
26 the required acknowledgment time, it shall transmit an SLP-D header-only SLP-D packet
27 carrying the acknowledgment. The SLP-D header-only SLP-D packet shall be sent as a
28 best-effort SLP-D packet.
29 Acknowledging an SLP-D packet with sequence number N does not imply an
30 acknowledgment for an SLP-D packet with a sequence number smaller than N.
2-14
V(S) = sequence number of

↓ the next SLP-D packet to be sent
••• •••
SLP-D packets sent and acknowledged
SLP-D packets sent and outstanding
SLP-D packets awaiting transmission
1 Figure 2.6.4.2.3.3.1-1. SLP-D Transmit Sequence Number Variable
2 The transmitter shall maintain an S-bit variable V(S). The sequence number field
3 (SequenceNumber) in each new reliable-delivery SLP-D packet transmitted shall be set to
4 V(S). After transmitting the reliable-delivery SLP-D packet, V(S) shall be incremented.
5 If SLP-D has already transmitted 2S-1 SLP-D packets, SLP-D shall transmit an SLP-D
6 packet with sequence number n, only after receiving acknowledgments for the SLP-D
7 packets transmitted with sequence number n - 2S-1 and below, or after determining that
8 these SLP-D packets could not be delivered.
9 If the transmitter does not receive from its co-located receiver an AckSequenceNumber
10 equal to the SequenceNumber of an outstanding reliable-delivery SLP-D packet within the
11 time interval specified by TSLPWaitAck, the transmitter shall retransmit the SLP-D packet. The
12 transmitter shall attempt to transmit a reliable-delivery SLP-D packet for a maximum of
13 NSLPAttempt.
14 The transmitter shall provide a retransmission buffer for 2S-1 SLP-D packets. Reliable-
15 delivery SLP-D packets shall be stored in the buffer when they are first transmitted and
16 may be deleted from the buffer, when they are acknowledged or when SLP-D determines
17 that they could not be delivered.
18 2.6.4.2.3.3.2 Receive Procedures

19 The SLP-D reliable-delivery receiver shall maintain an S-bit variable V(N). V(N) contains the
20 sequence number of the next expected SLP-D packet.
21 The receiver shall maintain a vector Rx with 2S one-bit elements. Rx[k] is set to ‘1’ if the
22 SLP-D packet with sequence number k has been received.
23
2-15
V(N) = sequence number of

the next expected SLP-D packet ↓
••• •••
SLP-D packets received in sequence
SLP-D packets received out of sequence
Buffer space for new or missed SLP-D packets
1 Figure 2.6.4.2.3.3.2-1. SLP Receive Sequence Number Variables
2 For each received SLP-D packet, the receiver shall perform the following actions:
3 • If a received SLP-D packet has a sequence number k that is smaller than V(N) and Rx[k]
4 = ‘1’, SLP-D shall discard it as a duplicate.
5 • If a received SLP-D packet has a sequence number k that is smaller than V(N) and Rx[k]
6 = ‘0’, SLP-D shall set Rx[k] to ‘1’ and pass the SLP-D payload to the upper layer.
7 • If a received SLP-D packet has sequence number k that is greater than or equal to V(N),
8 SLP-D shall set Rx[k] to ‘1’ and Rx[(k+v) mod 2S] to ‘0’ for v = 1, 2, 3 …, 2S-1. SLP-D shall
9 set V(N) to k+1 and pass the SLP-D payload to the upper layer.
10 2.6.4.3 Fragmentation Layer Procedures
11 2.6.4.3.1 Overview
12 SLP-F is a self-synchronizing loss detection protocol with a sequence space of S = 6 bits.
13 SLP-F maintains the following variables for SLP-F packets:
14 • V(S) The sequence number of the next SLP-F packet to be sent.
15 • Sync The SLP-F synchronized status flag.
16 2.6.4.3.2 Initialization
17 When SLP-F is initialized or reset it shall perform the following:
18 • Set the send state variable V(S) to zero in the transmitter.
19 • Set Sync to zero.
20 • Clear the re-assembly buffers.
21 When SLP-F is initialized or reset, the sender shall begin sending SLP-F packets with an
22 initial SequenceNumber of 0.
23 The access terminal and the access network shall perform the initialization procedure if the
24 protocol receives a ReverseTrafficChannelMAC.LinkAcquired indication.
2-16
1 2.6.4.3.3 Data Transfer

2 All operations and comparisons performed on SLP-F packet sequence numbers shall be
3 carried out in unsigned modulo 2S arithmetic.
4 2.6.4.3.4 Sender Requirements

5 The sender shall construct the SLP-F packet(s) by adding the SLP-F header, defined in
6 2.6.5.1, in front of each SLP-F payload. The size of each SLP-F packet shall not exceed the
7 current maximum SLP-F packet size.
8 The sender shall construct the SLP-F payload(s) from an SLP-D packet. If the SLP-D packet
9 exceeds the current maximum SLP-F payload size, then the sender shall fragment the SLP-
10 D packet. If the sender does not fragment the SLP-D packet, then the SLP-D packet is the
11 SLP-F payload. If the sender does fragment the SLP-D packet, then each SLP-D packet
12 fragment is an SLP-F payload.
13 If the SLP-F payload contains the beginning of an SLP-D packet, then the sender shall set
14 the SLP-F header Begin field to ‘1’; otherwise, the sender shall set the SLP-F header Begin
15 field to ‘0’.
16 If the SLP-F payload contains the end of an SLP-D packet, then the sender shall set the
17 SLP-F header End field to ‘1’; otherwise, the sender shall set the SLP-F header End field to
18 ‘0’
19 The sender shall set the SLP-F SequenceNumber field to V(S).
20 If the SLP-F payload contains a complete SLP-D packet, then the sender shall not include
21 the SLP-F header Begin, End and SequenceNumber fields; otherwise, the sender shall
22 include the SLP-F header Begin, End and SequenceNumber fields.
23 The sender shall increment the V(S) each time it sends a new SLP-F packet.
24 If an SLP-D packet is fragmented, a later fragment shall be transmitted at a time later than
25 the time at which any previous fragment was transmitted. The transmitter shall ensure
26 that no more than one SLP-F re-assembly buffer is needed for the Traffic Channel at the
27 same time.
28 2.6.4.3.5 Receiver Requirements

29 The receiver shall maintain an independent re-assembly buffer for each Connection
30 Endpoint as defined by the Address Management Protocol. The receiver writes the SLP-F
31 payloads to the corresponding re-assembly buffer when the Sync variable of the
32 corresponding re-assembly buffer is equal to 1. The receiver shall perform the following in
33 the order specified:
34 • If the SLP-F header Fragmented field is ‘0’, then the receiver shall assume the SLP-F
35 header Begin field is ‘1’, the SLP-F header End field is ‘1’ and the SLP-F header
36 SequenceNumber is ‘0’.
2-17
1 • If the SequenceNumber of the current SLP-F packet is not one greater than
2 SequenceNumber of the last SLP-F packet whose payload was written to the re-
3 assembly buffer, then the receiver shall discard the contents of the re-assembly buffer
4 and shall set the Sync flag to ‘0’.
5 • If the Begin field is ‘1’, then the receiver shall discard the contents of the re-assembly
6 buffer and set the Sync flag to ‘1’.
7 • If the Sync flag is ‘1’, then the receiver shall write the SLP-F payload to the re-assembly
8 buffer, otherwise the receiver shall discard the SLP-F payload.
9 • If the End field is ‘1’, then the receiver shall pass the contents of the re-assembly buffer
10 to the upper layer and set the Sync flag to ‘0’.
11 Upon receiving a ControlChannelMAC.Interrupted indication, the access terminal shall
12 discard the contents of the re-assembly buffers for the SLP Connection Endpoint
13 associated with <BATI, Control Channel> (see 8.3.3), and set the corresponding Sync flag to
14 ‘0’.
15 2.6.5 Header Formats

16 The combined SLP-D and SLP-F header length, x, is such that
17 x modulo 8 = 6.
18 2.6.5.1 SLP-F Header

19 The SLP-F header length, x, is such that
20 x modulo 8 = 5; if the SLP-F payload contains an SLP-D packet with SLP-D
21 header,
22 x modulo 8 = 6; if the SLP-F payload contains an SLP-D packet without SLP-D

23 header,
24 The SLP-F header has the following format:

25
Field Length(bits)
Reserved 4
Fragmented 1
Begin 0 or 1
End 0 or 1
SequenceNumber 0 or 6
OctetAlignmentPad 0 or 1
26 Reserved The sender shall set this field to zero. The receiver shall ignore this
27 field.
28 Fragmented SLP-F header fragmentation indicator. If the rest of the SLP-F header
29 is included, then the sender shall set this field to ‘1’; otherwise, the
2-18
1 sender shall set this field to ‘0’. If the SLP-F payload contains a
2 complete SLP-D packet, the sender shall not include the rest of the
3 SLP-F header; otherwise, the sender shall include the rest of the SLP-
4 F header.
5 Begin Start of SLP-D packet flag. The sender shall only include this field if
6 the Fragmented field is set to ‘1’. If this SLP-F payload contains the
7 beginning of an SLP-D packet, then the sender shall set this field to
8 ‘1’; otherwise, the sender shall set this field to ‘0’.
9 End End of SLP-D packet flag. The sender shall only include this field if
10 the Fragmented field is set to ‘1’. If this SLP-F payload contains the
11 end of an SLP-D packet, the sender shall set this field to ‘1’;
12 otherwise, the sender shall set this field to ‘0’.
13 SequenceNumber SLP-F packet sequence number. The sender shall only include this
14 field if the Fragmented field is set to ‘1’. The sender shall increment
15 this field for each new SLP-F packet sent.
16 OctetAlignmentPad Octet alignment padding. The sender shall include this field and set
17 it to ‘0’ if the Fragmented field is set to ‘1’ and Begin field is set to ‘0’.
18 Otherwise, the sender shall omit this field.
19 2.6.5.2 SLP-D Header

20 The SLP-D header length, x, is such that
21 x modulo 8 = 1.
22 The SLP-D header has the following format:
23
Field Length(bits)
FullHeaderIncluded 1
AckSequenceValid 0 or 1
AckSequenceNumber 0 or 3
SequenceValid 0 or 1
SequenceNumber 0 or 3
24 FullHeaderIncluded SLP-D header included flag. If the rest of SLP-D header is included,
25 then the sender shall set this field to ‘1’; otherwise, the sender shall
26 set this field to ‘0’. If the sender is either sending or acknowledging a
27 reliable-delivery SLP-D payload, then the sender shall include the
28 rest of the SLP-D header; otherwise, the sender shall not include the
29 rest of the SLP-D header.
2-19
1 AckSequenceValid The sender shall only include this field if the FullHeaderIncluded
2 field is set to ‘1’. If the AckSequenceNumber field contains a valid
3 value, then the sender shall set this field to ‘1’; otherwise, the sender
4 shall set this field to ‘0’.
5 AckSequenceNumber
6 The sender shall only include this field if the FullHeaderIncluded
7 field is set to ‘1’. If the AckSequenceValid field is set to ‘1’, then the
8 sender shall set this field to the sequence number of the first reliable-
9 delivery SLP-D payload that has not been acknowledged; otherwise,
10 the sender shall set this field to zero. If the AckSequenceValid field is
11 set to ‘0’, then the receiver shall ignore this field.
12 SequenceValid The sender shall only include this field if the FullHeaderIncluded
13 field is set to ‘1’. If the SequenceNumber field contains a valid value,
14 then the sender shall set this field to ‘1’; otherwise, the sender shall
15 set this field to ‘0’.
16 SequenceNumber The sender shall only include this field if the FullHeaderIncluded
17 field is set to ‘1’. If the SequenceValid field is set to ‘1’, then the
18 sender shall set this field to the sequence number of the reliable SLP-
19 D payload; otherwise, the sender shall set this field to zero. If the
20 SequenceValid field is set to ‘0’, then the receiver shall ignore this
21 field.
23 2.6.6.1 Reset
24 The Reset message is used by the access network to reset SLP.
25
Field Length (bits)
MessageID 8
MessageSequence 8
26 MessageID The access network shall set this field to 0x00.
27 MessageSequence The access network shall increment this field for every new Reset
28 message it sends.
29
Channels FTC SLP Best Effort
30 2.6.6.2 ResetAck
31 The ResetAck message is used by the access terminal to complete an SLP reset.
2-20
Field Length (bits)
MessageID 8
MessageSequence 8
2 MessageID The access terminal shall set this field to 0x01.
3 MessageSequence The access terminal shall set this field to the sequence number of the
4 associated Reset message.
5
Channels RTC SLP Best Effort
6 2.6.6.3 Protocol Numeric Constants

7
Constant Meaning Value

Time for receiver to acknowledge
TSLPAck an arriving reliable-delivery SLP-D 200 ms
packet
Maximum Number of attempts for
NSLPAttempt sending a reliable-delivery SLP-D 3
packet
Retransmission timer for a
TSLPWaitAck 400 ms
reliable-delivery SLP-D packet
8 2.6.7 Interface to Other Protocols
9 2.6.7.1 Commands
10 This protocol does not issue any commands.
11 2.6.7.2 Indications
13 • RouteUpdate.ConnectionInitiated
14 • ReverseTrafficChannelMAC.LinkAcquired
15 • ControlChannelMAC.Interrupted
16 2.7 Configuration Attributes for the Default Signaling Application

17 No configuration attributes are defined for this protocol.
2-21
1 2.8 Session State Information

2 This protocol does not define any parameter record to be included in a Session State
3 Information record (see 13.8).
4
2-22
Default Packet Application 3GPP2 C.S0024-B v2.0
1 3 DEFAULT PACKET APPLICATION
2 3.1 Introduction

4 The Default Packet Application provides an octet stream that can be used to carry packets
5 between the access terminal and the access network.
6 The Default Packet Application provides:
7 • The functionality defined in [1].
8 • The Radio Link Protocol (RLP), which provides retransmission, and duplicate detection,
9 thus, reducing the radio link error rate as seen by the higher layer protocols.
10 • Packet Location Update Protocol, which defines location update procedures and
11 messages in support of mobility management for the Packet Application.
12 • Flow Control Protocol, which provides flow control for the Default Packet Application.
13 The relationship between the Default Packet Application protocols is illustrated in Figure
14 3.1.1-1.
Radio Link Protocol (RLP) Location Update Protocol
Flow Control Protocol
15
16 Figure 3.1.1-1. Default Packet Application Protocols

20 3.1.3 Data Encapsulation for the InUse Instance of the Application

21 Figure 3.1.3-1 illustrates the relationship between the octet stream from the upper layer,
22 an RLP packet, and a Stream Layer payload. This application uses the Signaling
23 Application to transmit and receive messages.
3-1
3GPP2 C.S0024-B v2.0 Default Packet Application
octet stream
RLP RLP RLP

Stream
Layer
payload
1
2 Figure 3.1.3-1. Default Packet Application Encapsulation

9 • If the InUse instance of this application (i.e., corresponding to the stream to which this
10 application is bound) has the same application subtype as this InConfiguration
11 application instance, then the fall-back values of the attributes defined by the
12 InConfiguration application instance shall be set to the corresponding attribute values
13 for the InUse application instance.
14 • The value for each attribute for this application instance shall be set to the fall-back
15 value for that attribute.
16 • The value of the InConfiguration application instance public data shall be set to the
17 value of the corresponding InUse application instance public data.
18 • The value of the application subtype associated with the InConfiguration application
19 instance shall be set to the application subtype that identifies this application.
21 Application
22 3.3.1 Procedures
25 The Default Packet Application shall not be bound to a virtual stream.
3-2

16 the access terminal and the access network shall perform the following in the order
17 specified:
18 − The initial state of the Flow Control Protocol associated with the
19 InConfiguration instance of the Packet Application at the access terminal and
20 access network shall be set to the Close State.
21 − The InConfiguration instance of the Packet Application at the access terminal
22 and access network shall become the InUse instance for the Packet Application
23 (corresponding to the stream to which this application is bound).
29
Field Length (bits)
MessageID 8
TransactionID 8
3-3
7
Field Length (bits)
MessageID 8
TransactionID 8

16
3-4
1 3.4 Radio Link Protocol
2 3.4.1 Overview
3 The Radio Link Protocol (RLP) provides an octet stream service with an acceptably low
4 erasure rate for efficient operation of higher layer protocols (e.g., TCP). When used as part
5 of the Default Packet Application, the protocol carries an octet stream from the upper layer.
6 RLP uses Nak-based retransmissions.
7 RLP is a protocol associated with the default packet applicationDefault Packet Application.
8 The application subtype for this application is defined in [10].
10 3.4.2.1 Commands


15 The transmission unit of this protocol is an RLP packet.
16 RLP is unaware of higher layer framing; it operates on a featureless octet stream.
19 RLP receives octets for transmission from the higher layer and forms an RLP packet by
20 concatenating the RLP packet header defined in 3.4.4.2 with a number of received
21 contiguous octets. The policy RLP follows in determining the number of octets to send in an
22 RLP packet is beyond the scope of this specification. It is subject to the requirement that
23 an RLP packet shall not exceed the maximum payload length that can be carried by a
24 Stream Layer packet given the target channel and current transmission rate on that
25 channel.
26 RLP makes use of the Reset, ResetAck, and Nak messages to perform control related
27 operations.
28 3.4.4.1.1 Initialization and Reset

29 The RLP initialization procedure initializes the RLP variables and data structures in one
30 end of the link. The RLP reset procedure guarantees that RLP state variables on both sides
31 are synchronized. The reset procedure includes initialization.
32 The access terminal and the access network shall perform the Initialization Procedure
33 defined in 3.4.4.1.1.1 if the protocol receives an IdleState.ConnectionOpened indication.
3-5
1 3.4.4.1.1.1 Initialization Procedure

2 When RLP performs the initialization procedure it shall:
3 • Reset the send state variable V(S) to zero,
4 • reset the receive state variables V(R) and V(N) to zero,
5 • clear the resequencing buffer, and
6 • clear the retransmission queues.
7 3.4.4.1.1.2 Reset Procedure
8 3.4.4.1.1.2.1 Reset Procedure for the Initiating Side

9 The side initiating a reset procedure sends a Reset message and enters the RLP Reset
10 State.
11 Upon entering the RLP Reset state RLP shall:
12 • Perform the initialization procedure defined in 3.4.4.1.1.1.
13 • Ignore all RLP data octets received while in the RLP Reset state.
14 • If a Nak message is received for the RLP flow being reset while in the RLP Reset state,
15 the message shall be ignored.
16 • If RLP receives a ResetAck message while in the RLP Reset state, it shall send a
17 ResetAck message back and leave the RLP Reset state.
18 • If RLP receives an IdleState.ConnectionOpened indication while in the RLP Reset state, it
19 shall leave the RLP Reset state.
20 If a ResetAck message is received while RLP is not in the RLP Reset state, the message
21 shall be ignored.
22 3.4.4.1.1.2.2 Reset Procedure for the Responding Side

23 When RLP receives a Reset message, it shall respond with a ResetAck message. After
24 sending the message it shall enter the RLP Reset state, if it was not already in the RLP reset
25 state. Upon entering the RLP Reset state RLP shall:
26 • Perform the initialization procedure defined in 3.4.4.1.1.1.
27 • Ignore all RLP data octets received while in the RLP Reset state.
30 • When RLP receives a ResetAck message, it shall leave the RLP reset state.
33 If a ResetAck is received while RLP is not in the RLP Reset state, the message shall be
34 ignored.
3-6
1 3.4.4.1.2 Data Transfer

2 RLP is a Nak-based protocol with a sequence space of S bits, where S = 22.
3 All operations and comparisons performed on RLP packet sequence numbers shall be
4 carried out in unsigned modulo 2S arithmetic. For any RLP octet sequence number N, the
5 sequence numbers in the range [N+1, N+2S-1-1] shall be considered greater than N and the
6 sequence numbers in the range [N-2S-1, N-1] shall be considered smaller than N.
7 3.4.4.1.2.1 RLP Transmit Procedures

8 The RLP transmitter shall maintain an S-bit variable V(S) for all transmitted RLP data
9 octets (see Figure 3.4.4.1.2-1). V(S) is the sequence number of the next RLP data octet to be
10 sent. The sequence number field (SEQ) in each new RLP packet transmitted shall be set to
11 V(S), corresponding to the sequence number of the first octet in the packet. The sequence
12 number of the ith octet in the packet (with the first octet being octet 0) is implicitly given by
13 SEQ+i. V(S) shall be incremented for each octet contained in the packet.
14 After transmitting a packet, the RLP transmitter shall start an RLP flush timer for time
15 TRLPFlush. If the RLP transmitter sends another packet before the RLP flush timer expires,
16 the RLP transmitter shall reset and restart the timer. If the timer expires, the RLP
17 transmitter shall disable the flush timer and the RLP transmitter should send an RLP
18 packet that contains at least the octet with sequence number V(S)-1. The RLP transmitter
19 should allow sufficient time before deleting a packet transmitted for the first time.
20 Upon receiving a Nak message, RLP shall insert a copy of the requested octet(s) into its
21 output stream if those octets are available. If the Nak record includes any sequence
22 number greater than or equal to V(S), RLP shall perform the reset procedures specified in
23 3.4.4.1.1.2. If the Nak record does not include any sequence number greater than or equal
24 to V(S) but the requested octets are not available for retransmissions, RLP shall ignore the
25 Nak.
26
V(S) = sequence number

of the first octet of the next RLP
↓ packet to be sent.
••• •••
Octets sent
Octets awaiting transmission
27 Figure 3.4.4.1.2-1. RLP Transmit Sequence Number Variable
28 RLP shall assign the following priorities to RLP packets:

29 • Packet containing re-transmitted octets: 60
30 • Packet containing octets transmitted for the first time: 70
3-7
1 3.4.4.1.2.2 RLP Receive Procedures

2 The RLP receiver shall maintain two S-bit variables for receiving, V(R) and V(N) (see Figure
3 3.4.4.1.2-2). V(R) contains the sequence number of the next new octet expected to arrive.
4 V(N) contains the sequence number of the first missing octet, as described below.
5 In addition, the RLP receiver shall keep track of the status of each octet in its resequencing
6 buffer indicating whether the octet was received or not. Use of this status is implied in the
7 following procedures.
8
V(N) = next octet needed V(R) = next new

for sequential delivery ↓ ↓ octet expected
••• •••
Octets received in sequence
Octets received out of sequence
Buffer space for new or missed octets
9 Figure 3.4.4.1.2-2. RLP Receive Sequence Number Variables
10 In the following, X denotes the sequence number of a received octet. For each received
11 octet, RLP shall perform the following procedures:
12 • If X < V(N), the octet shall be discarded as a duplicate.
13 • If V(N) ≤ X < V(R), and the octet is not already stored in the resequencing buffer, then:
14 − RLP shall store the received octet in the resequencing buffer.
15 − If X = V(N), RLP shall pass all contiguous octets in the resequencing buffer,
16 from V(N) upward, to the higher layer, and may remove the passed octets from
17 the resequencing buffer. RLP shall then set V(N) to (LAST+1) where LAST is the
18 sequence number of the last contiguous octet (i.e., the octet with the highest
19 sequence number) passed to the higher layer from the resequencing buffer.
20 • If V(N) < X < V(R), and the octet has already been stored in the resequencing buffer,
21 then the octet shall be discarded as a duplicate.
22 • If X = V(R), then:
23 − If V(R) = V(N), RLP shall increment V(N) and V(R) and shall pass the octet to the
24 higher layer.
25 − If V(R) ≠ V(N), RLP shall increment V(R) and shall store the octet in the
26 resequencing buffer.
27 • If X > V(R), then:
3-8
1 − RLP shall store the octet in the resequencing buffer.

2 − RLP shall send a Nak message requesting the retransmission of all missing
3 RLP octets from V(R) to X-1, inclusive.
4 − RLP shall set V(R) to X+1.
5 RLP shall set a Nak abort timer for each data octet requested in a Nak record for a period of
6 TRLPAbort. If a requested octet has not arrived when its Nak abort timer expires, RLP shall
7 pass all octets in the resequencing buffer up to the missing octet, in order of sequence
8 number, to the higher layer. RLP shall skip any missing octets. RLP shall set V(N) to the
9 sequence number of the next missing octet, or to V(R) if there are no remaining missing
10 octets. Further recovery is the responsibility of the upper layer protocols.
11 3.4.4.2 RLP Packet Header

12 The RLP packet header, which precedes the RLP payload, has the following format:
13
Field Length (bits)

SEQ 22
14 SEQ The RLP sequence number of the first octet in the RLP payload.
15 3.4.4.3 Message Formats

16 The messages described in this section control the function of the RLP. These messages are
17 exchanged between the access terminal and the access network using the SNP.
18 3.4.4.3.1 Reset
19 The access terminal and the access network send the Reset message to reset RLP.
20
Field Length (bits)
MessageID 8

22
23 3.4.4.3.2 ResetAck
24 The access terminal and the access network send the ResetAck message to complete the
25 RLP reset procedure.
26
3-9
Field Length (bits)

MessageID 8

2
3 3.4.4.3.3 Nak
4 The access terminal and the access network send the Nak message to request the
5 retransmission of one or more octets.
6
Field Length (bits)
MessageID 8
NakRequests 8
NakRequests occurrences of the following three

fields:
Reserved 2
FirstErased 22
WindowLen 16
8 NakRequests The sender shall set this field to the number of Nak requests
9 included in this message. The sender shall include NakRequests
10 occurrences of the following three fields with the message.
11 Reserved The sender shall set this field to zero. The receiver shall ignore this
12 field.
13 FirstErased The sender shall set this field to the sequence number of the first
14 RLP octet erased in a sequence of erased octets whose
15 retransmission is requested.
16 WindowLen The sender shall set this field to the length of the erased window. The
17 receiver shall retransmit all the octets in the range FirstErased to
18 FirstErased+WindowLen-1, inclusive.
19
3-10
Channels FTC RTC SLP Best Effort
2 3.4.4.4.1 Commands
7 3.4.4.5 RLP Packet Priorities

8
Type of RLP Packet Channel Addressing Priority

Packet containing only First
FTC, RTC unicast 70
Time Transmissions
Packet containing re-
transmitted application FTC, RTC unicast 60
traffic
9 3.4.5 Protocol Numeric Constants

10

Time to wait for a retransmission of an
TRLPAbort 500 ms
octet requested in a Nak message
Time to wait before retransmitting the last
TRLPFlush 300 ms
transmitted octet
3-11
1 3.5 Location Update Protocol
2 3.5.1 Overview
3 The Location Update Protocol defines location update procedures and messages for mobility
4 management for the Default Packet Application.
5 The Location Update Protocol is a protocol associated with the default packet
6 applicationDefault Packet Application. The application subtype for this application is
7 defined in [10].
9 3.5.2.1 Commands


14 The transmission unit of this protocol is a message. This is a control protocol; and,
15 therefore, it does not carry payload on behalf of other layers or protocols.
18 3.5.4.1.1 Access Network Requirements

19 If the protocol receives an AddressManagement.SubnetChanged indication, the access
20 network:
21 • May send a LocationRequest message to query the Location information.
22 • May send a LocationAssignment message to update the Location information.
23 3.5.4.1.2 Access Terminal Requirements

24 If the access terminal receives a LocationRequest message, it shall send a
25 LocationNotification message. If the access terminal has a stored value for the
26 LocationValue parameter, the access terminal shall set the LocationType, LocationLength,
27 and LocationValue fields in this message to its stored values of these fields. If the access
28 terminal does not have a stored value for the LocationValue parameter, the access terminal
29 shall omit the LocationLength and LocationValue fields in this message.
30 • If the access terminal receives a LocationAssignment message, it shall send a
31 LocationComplete message and the access terminal shall store the value of the
32 LocationType, LocationLength, and LocationValue fields of the LocationAssignment
33 message in LocationType, LocationLength, and LocationValue variables, respectively.
3-12
2 3.5.4.2.1 LocationRequest
3 The access network uses this message to query the access terminal of its Location
4 information.
5
Field Length (bits)
MessageID 8

7
Channels CC FTC SLP Best Effort
8 3.5.4.2.2 LocationNotification
9 The access terminal sends the LocationNotification message either in response to the
10 LocationRequest message or in an unsolicited manner as specified in [89][9] if the
11 configured value of the RANHandoff attribute is 0x01.
12
Field Length (bits)
MessageID 8
LocationType 8
LocationLength 0 or 8
LocationValue 0 or 8 × LocationLength
14 LocationType The access terminal shall set this field to zero if the value of its stored
15 LocationValue is NULL; otherwise, the access terminal shall set this
16 field to the stored value of LocationType.
17 LocationLength The access terminal shall not include this field if the value of its
18 stored LocationValue is NULL; otherwise, the access terminal shall
19 set this field to the stored value of LocationLength.
20 LocationValue The access terminal shall not include this field if the value of its
22 set this field to the stored value of LocationValue.
23
3-13
Channels AC RTC SLP Reliable3 Best Effort
1 3.5.4.2.3 LocationAssignment
2 The access network uses this message to update the Location information of the access
3 terminal.
Field Length (bits)
MessageID 8
TransactionID 8
LocationType 8
LocationLength 8
LocationValue 8 × LocationLength
5 TransactionID The access network shall increment this value for each new
6 LocationAssignment message sent.
7 LocationType The access network shall set this field to the type of the location as
8 specified in Table 3.5.4.2-1.
9 Table 3.5.4.2-1. LocationType Encoding
LocationType LocationLength Meaning
0x00 N/A No location is stored

0x01 0x05 Location compatible with [3]
(see Table 3.5.4.2-2)
All other values N/A Reserved
10 LocationLength The access network shall set this field to the length of the
11 LocationValue field in octets as specified in Table 3.5.4.2-1.
12 LocationValue The access network shall set this field to the Location of type
13 specified by LocationType. If LocationType is set to 0x01, the access
14 network shall set this field as shown in Table 3.5.4.2-2, where SID,
15 NID, and PACKET_ZONE_ID correspond to the current access
16 network.
3 This message is sent reliably when it is sent over the Reverse Traffic Channel.
3-14
1 Table 3.5.4.2-2. Subfields of LocationValue when LocationType = 0x01
Sub-fields of
# of bits
LocationValue
SID 15
Reserved 1
NID 16
PACKET_ZONE_ID 8
3 3.5.4.2.4 LocationComplete
4 The access terminal sends this message in response to the LocationAssignment message.
5
Field Length (bits)
MessageID 8
TransactionID 8
7 TransactionID The access terminal shall set this field to the TransactionID field of
8 the corresponding LocationAssignment message.
9
11 3.5.4.3.1 Commands
15 • AddressManagement.SubnetChanged (access network only)
3-15
1 3.6 Flow Control Protocol
2 3.6.1 Overview
3 The Flow Control Protocol provides procedures and messages used by the access terminal
4 and the access network to perform flow control for the Default Packet Application.
5 This protocol can be in one of the following states:
6 • Close State: in this state the Default Packet Application does not send or receive any
7 RLP packets.
8 • Open State: in this state the Default Packet Application can send and receive RLP
9 packets.
10 Figure 3.6.1-1 and Figure 3.6.1-2 show the state transition diagram at the access terminal
11 and the access network.
12
Tx XonRequest
Initial State or Tx an RLP packet
Close State Open State
13
Rx XoffResponse
14 Figure 3.6.1-1. Flow Control Protocol State Diagram (Access Terminal)
Rx XonRequest
Initial State or Rx an RLP packet
15
Tx XoffResponse
16 Figure 3.6.1-2. Flow Control Protocol State Diagram (Access Network)
17 The flow control protocol is a protocol associated with the default packet applicationDefault
18 Packet Application. The application subtype for this application is defined in [10].
20 3.6.2.1 Commands
3-16


4 The transmission unit of this protocol is a message. This is a control protocol and,
8 3.6.4.1.1 Transmission and Processing of DataReady Message

9 The access network may send a DataReady message to indicate that there is data
10 corresponding to this packet application awaiting to be transmitted.
11 The access terminal shall send a DataReadyAck within the time period specified by
12 TFCResponse after reception of the DataReady message to acknowledge reception of the
13 message.
14 3.6.4.1.2 Close State
15 3.6.4.1.2.1 Access Terminal Requirements

16 The access terminal shall send an XonRequest message or an RLP packet (corresponding to
17 this instance of the Default Packet Application) when it is ready to exchange RLP packets
18 with the access network. The access terminal should send an XonRequest message or an
19 RLP packet (corresponding to this instance of the Default Packet Application) when it
20 receives a DataReady from the access network.
21 The access terminal shall transition to the Open State when it sends an XonRequest
22 message or when it sends an RLP packet (corresponding to this instance of the Default
23 Packet Application).
24 3.6.4.1.2.2 Access Network Requirements

25 The access network shall not send any RLP packets in this state.
26 If the access network receives an XonRequest message, it shall
27 • Send an XonResponse message within the time period specified by TFCResponse after
28 reception of the XonRequest message to acknowledge reception of the message.
29 • Transition to the Open State.
30 The access network shall also transition to the Open State if it receives an RLP packet
31 (corresponding to this instance of the Default Packet Application).
32 3.6.4.1.3 Open State

33 In this state, the access terminal and the access network may send or receive any RLP
34 packets.
3-17

2 The access terminal may re-send an XonRequest message if it does not receive an
3 XonResponse message or an RLP packet (corresponding to this instance of the Default
4 Packet Application) within the time period specified by TFCResponse after sending the
5 XonRequest message.
6 The access terminal should send an XonRequest message if it receives a DataReady
7 message.
8 The access terminal may send an XoffRequest message to request the access network to
9 stop sending RLP packets. The access terminal shall transition to the Close state when it
10 receives an XoffResponse message.
11 The access terminal may re-send an XoffRequest message if it does not receive an
12 XoffResponse message within the time period specified by TFCResponse after sending the
13 XoffRequest message.

15 If the access network receives an XoffRequest message, it shall
16 • Send an XoffResponse message within the time period specified by TFCResponse after
17 reception of XoffRequest message to acknowledge reception of the message.
18 • Transition to the Close State.
19 If the access network receives an XonRequest message, it shall send an XonResponse
20 message within the time period specified by TFCResponse after reception of the XonRequest
21 message to acknowledge reception of the message.
23 3.6.4.2.1 XonRequest
24 The access terminal sends this message to request transition to the Open State.
25
Field Length (bits)
MessageID 8
27
Channels AC RTC SLP Best Effort
28 3.6.4.2.2 XonResponse
29 The access network sends this message to acknowledge reception of the XonRequest
30 message.
3-18
Field Length (bits)
MessageID 8

3
4 3.6.4.2.3 XoffRequest
5 The access terminal sends this message to request transition to the Close State.
6
Field Length (bits)
MessageID 8
9 3.6.4.2.4 XoffResponse
10 The access network sends this message to acknowledge reception of the XoffRequest
11 message.
12
Field Length (bits)
MessageID 8
13 MessageID The access network shall set this field to 0x0a.

14
15 3.6.4.2.5 DataReady
16 The access network sends this message to indicate that there is data corresponding to this
17 packet application awaiting to be transmitted.
18
3-19
Field Length (bits)
MessageID 8
TransactionID 8
1 MessageID The access network shall set this field to 0x0b.
3 DataReady message sent.
4
5 3.6.4.2.6 DataReadyAck
6 The access terminal sends this message to acknowledge reception of a DataReady message.
7
Field Length (bits)
MessageID 8
TransactionID 8
8 MessageID The access terminal shall set this field to 0x0c.
9 TransactionID The access terminal shall set this value to the value of the
10 TransactionID field of the corresponding DataReady message.
11
13 3.6.5.1 Commands
16 This protocol does not register to receive any indications.

18
3-20

Time period within which the access
TFCResponse terminal and access network are to 1 second
respond to flow control messages.
3-21
1 3.7 Configuration Attributes for the Default Packet Application

2 The negotiable simple attribute for this protocol is listed in Table 3.7-1. The access
3 terminal and the access network shall use as defaults the values in Table 3.7-1 typed in
4 bold italics.
5 Table 3.7-1. Configurable Values
Attribute ID Attribute Values Meaning

0x00 The access terminal shall not send an
unsolicited LocationNotification message. The
access network does not switch between the
radio access technologies (e.g. specified in [3])
in a manner that preserves the state of all
protocol layers at or above the data link layer
(PPP).
0xff RANHandoff 0x01 The access terminal shall send an unsolicited
LocationNotification message. The access
network switches between the radio access
technologies (e.g. specified in [3]) in a manner
that preserves the state of all protocol layers
at or above the data link layer (PPP).
All other Reserved
values

7 The Session State Information record (see 13.8) consists of parameter records.
8 This application defines the following parameter records in addition to the configuration
9 attributes for this application.
10 3.8.1 Location Parameter
11 Table 3.8.1-1. The Format of the Parameter Record for the Location Parameter
Field Length (bits)
ParameterType 8
Length 8
LocationType 8
LocationValue 8 × (Length – 2)
12 ParameterType This field shall be set to 0x01 for this parameter record.
13 Length This field shall be set to the length of this parameter record in units
14 of octets excluding the Length field.
3-22
1 LocationType This field shall be set to the value of LocationType associated with
2 the access terminal’s session.
3 LocationValue This field shall be set to the stored value of LocationValue associated
4 with the access terminal’s session.
5 3.8.2 FlowControlState Parameter
7 Parameter
Field Length (bits)
ParameterType 8
Length 8
FlowControlState 8
11 FlowControlState This field shall be set to 0x00 if the state of the Flow Control Protocol
12 associated with the access terminal’s session is Close. Otherwise,
13 this field shall be set to 0x01. All the other values for this field are
14 reserved.
3-23
1 No text.
3-24
Multi-Flow Packet Application 3GPP2 C.S0024-B v2.0
1 4 MULTI-FLOW PACKET APPLICATION
2 4.1 Introduction

4 The Multi-Flow Packet Application provides multiple octet streams that can be used to
5 carry octets between the access terminal and the access network.
6 The Multi-Flow Packet Application provides:
7 • the functionality defined in [1],
8 • the Radio Link Protocol (RLP), which provides retransmission and duplicate detection,
9 • the Data Over Signaling Protocol, which provides transmission and duplicate detection
10 of higher layer data packets using signaling messages,
11 • the Location Update Protocol, which defines location update procedures and messages
12 in support of mobility management for the Packet Application, and
13 • the Flow Control Protocol, which provides flow control for the Multi-Flow Packet
14 Application.
15 The relationship between the Multi-Flow Packet Application protocols is illustrated in
16 Figure 4.1.1-1.
Location Update Radio Link Protocol Data Over Signaling

Protocol (RLP) Protocol
Flow Control Protocol
17
18 Figure 4.1.1-1. Multi-Flow Packet Application Protocols

22 4.1.3 Data Encapsulation for the InUse Instance of the Application

23 Figure 4.1.3-1 illustrates the relationship between octets from the higher layer, RLP
24 packets, and Stream Layer payload. This application uses the Signaling Application to
25 transmit and receive messages.
4-1
3GPP2 C.S0024-B v2.0 Multi-Flow Packet Application
Upper Layer Octets
RLP RLP RLP RLP RLP RLP RLP

packets header payload header payload header payload
Stream Layer Stream Layer Stream Layer

payload payload payload
1
2 Figure 4.1.3-1. Multi-Flow Packet Application Encapsulation

9 • If the InUse instance of this application (i.e., corresponding to the stream to which this
10 application is bound) has the same application subtype as this InConfiguration
11 application instance, then the fall-back values of the attributes defined by the
12 InConfiguration application instance shall be set to the corresponding attribute values
13 for the InUse application instance.
14 • The value for each attribute for this application instance shall be set to the fall-back
15 value for that attribute.
16 • The value of the InConfiguration application instance public data shall be set to the
17 value of the corresponding InUse application instance public data.
18 • The value of the application subtype associated with the InConfiguration application
21 Application
22 4.3.1 Procedures
25 The Multi-Flow Packet Application shall not be bound to a virtual stream.
26 The access terminal shall not send a ConfigurationRequest message containing the
27 ReservationKKQoSResponseFwd attribute. The access network shall not send a
28 ConfigurationRequest message containing the ReservationKKQoSRequestFwd attribute.
29 The access terminal shall not send a ConfigurationRequest message containing the
30 ReservationKKQoSResponseRev attribute. The access network shall not send a
31 ConfigurationRequest message containing the ReservationKKQoSRequestRev attribute.
4-2
1 The access terminal shall not initiate negotiation of the ANSupportedQoSProfiles attribute.
2 The access network shall not initiate negotiation of the ATSupportedQoSProfiles attribute.
3 The access terminal should include supported values of ProfileValue with ProfileType equal
4 to 0x04 in the ATSupportedQoSProfiles attribute during the AT Initiated state of the
5 Session Configuration Protocol. The access network shall include all supported values of
6 ProfileValue with ProfileType equal to 0x04 in the ANSupportedQoSProfiles attribute during
7 the AN Initiated state of the Session Configuration Protocol. The access terminal shall use
8 the ProfileType 0x00, 0x01, or 0x02 in the ReservationKKQoSRequestFwd or the
9 ReservationKKQoSRequestRev attributes. The access network shall use ProfileType 0x00 or
10 0x03 in the ReservationKKQoSResponseFwd or the ReservationKKQoSResponseRev
11 attributes.
12 The access network shall not initiate negotiation of the MaxRLPFlows attribute.
13 The access network and access terminal shall not propose value of MaxAbortTimer that is
14 less than any of the AbortTimer values in FlowNNTimersFwd and FlowNNTimersRev
15 Attributes.

30 application is bound) does not have the same subtype as this application instance,
31 then:
32 − The access terminal and the access network shall initialize a receive pointer for
33 DataOverSignaling message validation, V(R), to 63.
34 − The access terminal and the access network shall initialize a transmit pointer
35 for DataOverSignaling message validation, V(S), to zero.
36 − The access terminal and the access network shall set the StorageBLOB
37 parameter of the Location Update Protocol to NULL.
38 − The initial state of the Flow Control Protocol associated with the
39 InConfiguration instance of the Packet Application at the access terminal and
40 access network shall be set to the Close State.
4-3
1 − The access network shall set the Forward Reservation with ReservationLabel
2 0xff to the Open state.5
3 − The access terminal shall set the Reverse Reservation with ReservationLabel
4 0xff to the Open state.
5 − The access network shall set the Forward Reservations with ReservationLabel
6 not equal to 0xff to the Close state.
7 − The access terminal shall set the Reverse Reservations with ReservationLabel
8 not equal to 0xff to the Close state.
9 − The InConfiguration instance of the Packet Application at the access terminal
10 and access network shall become the InUse instance for the Packet Application
11 (corresponding to the stream to which this application is bound).
17
Field Length (bits)
MessageID 8
TransactionID 8
22
5 Forward and reverse link Reservations 0xff are initialized in the Open state so that data can be sent
without having to perform a state transition.
4-4
3
Field Length (bits)
MessageID 8
TransactionID 8

12
4-5
1 4.4 Radio Link Protocol
2 4.4.1 Overview
3 The Radio Link Protocol (RLP) provides one or more octet streams with an acceptably low
4 erasure rate for efficient operation of higher layer protocols (e.g., TCP). When used as part
5 of the Multi-Flow Packet Application, the protocol carries one or more octet streams from
6 the higher layer. Each octet stream is carried by an RLP flow. RLP uses Nak-based
7 retransmissions. RLP is a protocol associated with the Multi-Flow Packet Application. The
8 application subtype for this application is defined in [10].
10 4.4.2.1 Commands


15 The transmission unit of this protocol is an RLP packet.
17 An RLP flow on the forward link is defined to be activated if the Active parameter of the
18 FlowNNIdentificationFwd attribute is set to 0x01, where NN is the hexadecimal RLP flow
19 number in the range 0x00 to MaxNumRLPFlowsFwd - 1 inclusive. The number of activated
20 RLP flows on the forward link shall not exceed the value of the MaxActivatedRLPFlowsFwd
21 attribute.
22 An RLP flow on the reverse link is defined to be activated if the Active parameter of the
23 FlowNNIdentificationRev attribute is set to 0x01, where NN is the hexadecimal RLP flow
24 number in the range 0x00 to MaxNumRLPFlowsRev - 1 inclusive. The number of activated
25 RLP flows on the reverse link shall not exceed the value of the MaxActivatedRLPFlowsRev
26 attribute.
27 An RLP flow is defined to be deactivated if it is not activated.
28 This section defines the procedures and messages for the in-use instance of each forward
29 or reverse RLP flow.
31 • An RLP flow receives octets for transmission from the higher layer and forms an RLP
32 packet by prepending the RLP packet header defined in 4.4.4.3 with a number of
33 received contiguous octets.
4-6
1 • The policy RLP follows in determining the number of octets to send in an RLP packet is
2 beyond the scope of this specification. It is subject to the requirement that an RLP
3 packet shall not exceed the maximum payload length that can be carried by a Stream
4 Layer packet given the target channel and current transmission rate on that channel.
5 For the purpose of binding RLP flows to lower layer flows, each RLP flow shall be treated as
6 a substream with the substream number set to the RLP flow number.
7 RLP makes use of the ResetTxIndication, ResetRxIndication, ResetTxIndicationAck,
8 ResetTxComplete, ResetRxComplete, and Nak messages to perform control related
9 operations.
10 The access network shall not initiate modification of the ReservationKKQoSRequestFwd or
11 the ReservationKKQoSRequestRev attributes. If the access network receives an
12 AttributeUpdateRequest message requesting to set the ReservationKKQoSRequestFwd or
13 the ReservationKKQoSRequestRev attribute to its default value, then the access network
14 shall respond with an AttributeUpdateAccept message. The access terminal shall not
15 initiate modification of the ReservationKKQoSResponseFwd or the
16 ReservationKKQoSResponseRev attributes. The access terminal shall use the ProfileType
17 0x00, 0x01, or 0x02 in the ReservationKKQoSRequestFwd or the
18 ReservationKKQoSRequestRev attributes. The access network shall use ProfileType 0x00 or
19 0x03 in the ReservationKKQoSResponseFwd or the ReservationKKQoSResponseRev
20 attributes.
21 When forward RLP flow NN is activated, the access network and the access terminal shall
22 not update any parameters of the FlowNNIdentificationFwd attribute other than to
23 deactivate forward RLP flow NN. The access terminal shall not initiate activation of a
24 deactivated forward RLP flow NN unless the access terminal initiated deactivation of
25 forward RLP flow NN since the last time the flow was activated, and the deactivation was
26 successful. The access network shall not initiate activation of a deactivated forward RLP
27 flow NN unless the access network initiated deactivation of forward RLP flow NN since the
28 last time the flow was activated, and the deactivation was successful.
29 When reverse RLP flow NN is activated, the access network and the access terminal shall
30 not update any parameters of the FlowNNIdentificationRev attribute other than to
31 deactivate reverse RLP flow NN. The access terminal shall not initiate activation of a
32 deactivated reverse RLP flow NN unless the access terminal initiated deactivation of reverse
33 RLP flow NN since the last time the flow was activated, and the deactivation was successful.
34 The access network shall not initiate activation of a deactivated reverse RLP flow NN unless
35 the access network initiated deactivation of reverse RLP flow NN since the last time the flow
36 was activated, and the deactivation was successful.
37 When forward RLP flow NN is activated, the access network and the access terminal shall
38 not update the FlowNNHigherLayerProtocolFwd attribute. The
39 FlowNNHigherLayerProtocolFwd attribute shall not be set to a value that is not included as
40 ProtocolIdentifier in the SupportedHigherLayerProtocols attribute. When reverse RLP flow
41 NN is activated, the access network and the access terminal shall not update the
42 FlowNNHigherLayerProtocolRev attribute. The FlowNNHigherLayerProtocolRev attribute
4-7
1 shall not be set to a value that is not included as ProtocolIdentifier in the

2 SupportedHigherLayerProtocols attribute.
3 4.4.4.1.1 Initialization and Reset

4 The RLP initialization procedure initializes the RLP variables and data structures in one
5 end of the link. The RLP reset procedure guarantees that RLP state variables on both sides
6 are synchronized. The reset procedure includes initialization.
7 The access terminal and the access network shall perform the initialization procedures
8 defined in 4.4.4.1.1.1.1 and 4.4.4.1.1.1.2 for all activated RLP flows if the protocol receives
9 an IdleState.ConnectionOpened indication. The access network shall perform the
10 initialization procedure defined in 4.4.4.1.1.1.1 for forward RLP flow NN when forward RLP
11 flow NN is activated. The access terminal shall perform the initialization procedure defined
12 in 4.4.4.1.1.1.2 for forward RLP flow NN when forward RLP flow NN is activated. The access
13 terminal shall perform the initialization procedure defined in 4.4.4.1.1.1.1 for reverse RLP
14 flow NN when reverse RLP flow NN is activated. The access network shall perform the
15 initialization procedure defined in 4.4.4.1.1.1.2 for reverse RLP flow NN when reverse RLP
16 flow NN is activated.
17 4.4.4.1.1.1 Initialization Procedure
18 4.4.4.1.1.1.1 Initialization Procedure for the RLP Transmitter

19 When RLP transmitter performs the initialization procedure it shall:
20 • Reset the send state variable V(S)NN to zero, and
21 • clear the retransmission queues.
22 4.4.4.1.1.1.2 Initialization Procedure for the RLP Receiver

23 When RLP receiver performs the initialization procedure it shall:
24 • Reset the receive state variables V(R) NN and V(N) NN to zero, and
25 • clear the resequencing buffer.
26 4.4.4.1.1.2 Reset Procedure
27 4.4.4.1.1.2.1 Reset Procedure for the Initiating Side when it is an RLP Transmitter
28 If the side initiating a reset procedure is an RLP transmitter for the RLP flow (or all flows)
29 being reset, then it shall send a ResetTxIndication message and enter the RLP Reset State.
30 Upon entering the RLP Reset state RLP shall:
31 • Perform the RLP transmitter initialization procedure defined in 4.4.4.1.1.1.1 for the RLP
32 flow being reset.
4-8
1 • If the RLP transmitter that initiated the reset procedure is an access terminal, and if a
2 PhysicalLayer.ReverseTrafficPacketsMissed indication is received for the RLP flow being
3 reset while RLP is in the Reset state, then the indication shall be ignored.
4 • The RLP transmitter should not transmit RLP packets while in the RLP Reset state.
5 • If RLP receives a ResetTxIndicationAck message for the RLP flow being reset while in
6 the RLP Reset state, it shall send a ResetTxComplete message back and leave the RLP
7 Reset state.
10 If a ResetTxIndicationAck message is received for an RLP flow while the RLP flow is not in
11 the RLP Reset state, the message shall be ignored.
12 4.4.4.1.1.2.2 Reset Procedure for Initiating Side when it is an RLP Receiver

13 If the side initiating a reset procedure is an RLP receiver for the RLP flow being reset, then
14 it shall send a ResetRxIndication message and enter the RLP Reset State. Upon entering
15 the RLP Reset state, RLP shall:
16 • Perform the RLP receiver initialization procedure defined in 4.4.4.1.1.1.2 for the RLP
18 • Ignore all RLP data octets received for the RLP flow being reset while in the RLP Reset
19 state.
20 • When RLP receives a ResetRxComplete message for the RLP flow being reset, it shall
21 leave the RLP reset state.
24 If a ResetRxComplete is received for an RLP flow while the RLP flow is not in the RLP Reset
25 state, the message shall be ignored.
26 4.4.4.1.1.2.3 Reset Procedure for the Responding Side when it is an RLP Receiver
27 If the side responding to a reset procedure is an RLP receiver for the RLP flow being reset,
28 then it shall respond with a ResetTxIndicationAck message upon receiving a
29 ResetTxIndication message. After sending the message it shall enter the RLP Reset state for
30 the RLP flow being reset, if it was not already in the RLP reset state. Upon entering the RLP
31 Reset state RLP shall:
32 • Perform the RLP receiver initialization procedure defined in 4.4.4.1.1.1.2 for the RLP
34 • Ignore all RLP data octets received for the RLP flow being reset while in the RLP Reset
35 state.
36 • When RLP receives a ResetTxComplete message for the RLP flow being reset, it shall
37 leave the RLP reset state.
4-9

3 If a ResetTxComplete message is received for an RLP flow while the RLP flow is not in the
4 RLP Reset state, the message shall be ignored.
5 4.4.4.1.1.2.4 Reset Procedure for the Responding Side when it is a RLP transmitter
6 If the side responding to a reset procedure is an RLP transmitter for the RLP flow being
7 reset, then it shall respond with a ResetRxComplete message upon receiving a
8 ResetRxIndication message. After sending the message, it shall perform the RLP
9 transmitter initialization procedure defined in 4.4.4.1.1.1.1 for the RLP flow being reset.
10 4.4.4.1.1.2.5 RLP Reset Message Flows
RLP Transmitter RLP Receiver

Enter RLP Reset
State and
Initialize RLP
Ignore Nak
Messages
Transmitter ResetTxIndication Enter RLP Reset

State and
Initialize RLP
Data Octets
Ignore RLP
ResetTxIndicationAck Receiver
Leave RLP Reset

State
ResetTxComplete
Leave RLP Reset
State
11
12 Figure 4.4.4.1.1.2.5-1. RLP Reset Procedure Initiated by RLP Transmitter
RLP Transmitter RLP Receiver

Enter RLP Reset
State and
Initialize RLP
Data Octets
Ignore RLP
ResetRxIndication Receiver
Initialize RLP
Transmitter
ResetRxComplete
Leave RLP Reset
State
13
14 Figure 4.4.4.1.1.2.5-2. RLP Reset Procedure Initiated by RLP Receiver
15 4.4.4.2 Data Transfer

16 RLP is a Nak-based protocol with a sequence space of SequenceLength bits, where
17 SequenceLength is a parameter associated with forward or reverse RLP Flow NN.
4-10
1 All operations and comparisons performed on RLP packet sequence numbers shall be
2 carried out in unsigned modulo 2S arithmetic, where S represents the value of
3 SequenceLength. For any RLP octet sequence number N, the sequence numbers in the
4 range [N+1, N+2S-1-1] shall be considered greater than N and the sequence numbers in the
5 range [N-2S-1, N-1] shall be considered smaller than N.
6 4.4.4.2.1 RLP Transmit Procedures

7 The RLP transmitter shall maintain a SequenceLength-bit variable V(S)NN for all transmitted
8 RLP data octets (see Figure 4.4.4.2.1-1), where NN is the two-digit hexadecimal RLP flow
9 number in the range 0x00 to M - 1 inclusive, where M is MaxNumRLPFlowsFwd or
10 MaxNumRLPFlowsRev for an RLP flow on the forward link or reverse link respectively.
11 V(S)NN is the sequence number of the next RLP data octet to be sent. The sequence number
12 field (SEQ) in each new RLP packet transmitted shall be set to V(S)NN, corresponding to the
13 sequence number of the first octet in the packet. The sequence number of the ith octet in
14 the packet (with the first octet being octet 0) is implicitly given by SEQ+i. V(S)NN shall be
15 incremented for each octet contained in the packet.
16 The RLP transmitter should allow sufficient time before deleting a packet transmitted for
17 the first time. Upon receiving a Nak message, RLP shall transmit the requested octet(s) if
18 those octets are available. If the RLP transmitter is the access network, and the Nak record
19 includes any sequence number greater than or equal to V(S)NN, RLP shall perform the reset
20 procedures specified in 4.4.4.1.1.2.1 for forward RLP flow NN. If the RLP transmitter is the
21 access terminal, and the Nak record includes any sequence number greater than or equal
22 to V(S)NN, RLP shall perform the reset procedures specified in 4.4.4.1.1.2.1 for reverse RLP
23 flow NN. If the Nak record does not include any sequence number greater than or equal to
24 V(S)NN but the requested octets are not available for retransmissions, RLP shall ignore the
25 Nak for octets that are not available.
26
V(S)NN = sequence number

of the first octet of the next RLP
↓ packet to be sent.
••• •••
Octets sent
Octets awaiting transmission
27 Figure 4.4.4.2.1-1. RLP Transmit Sequence Number Variable
28 Upon receiving a PhysicalLayer.ReverseTrafficPacketsMissed indication for reverse RLP flow

29 NN, the RLP transmitter in the access terminal shall transmit the requested octet(s) if and
30 only if all of the following conditions are satisfied:
31 • FlowNNPhysicalLayerNakEnableRev attribute is set to 0x01,
32 • the requested octets have not been retransmitted before, and
4-11
1 • the requested octets are available.

2 Upon receiving a PhysicalLayer.ReverseTrafficPacketsMissed indication for reverse RLP flow
3 NN, the RLP transmitter in the access terminal shall not transmit the requested octet(s) if
4 the octets have been retransmitted before.
5 If FlowNNNakEnableFwd is 0x01, then the flow NN RLP transmitter at the access network
6 shall meet the following requirements:
7 • After transmitting a packet, the RLP transmitter shall start an RLP flush timer for time
8 FlushTimer, where FlushTimer is a parameter of the FlowNNTimersFwd attribute.
9 • If the RLP transmitter sends another packet before the RLP flush timer expires, the RLP
10 transmitter shall reset and restart the timer.
11 • If the timer expires, the RLP transmitter shall disable the flush timer and the RLP
12 transmitter should send an RLP packet that contains at least the octet with sequence
13 number V(S)NN-1.
14 If FlowNNNakEnableRev is 0x01, then the flow NN RLP transmitter at the access terminal
15 shall meet the following requirements:
16 • After transmitting a packet, the RLP transmitter shall start an RLP flush timer for time
17 FlushTimer, where FlushTimer is a parameter of the FlowNNTimersRev attribute.
18 • If the RLP transmitter sends another packet before the RLP flush timer expires, the RLP
19 transmitter shall reset and restart the timer.
20 • If the timer expires, the RLP transmitter shall disable the flush timer and the RLP
21 transmitter should send an RLP packet that contains at least the octet with sequence
22 number V(S)NN-1.
23 The RLP transmitter should not transmit more than 2SequenceLength-1 first-time octets in any
24 AbortTimer interval, where SequenceLength is the length of the SEQ field in the RLP header
25 for the corresponding RLP flow.
26 4.4.4.2.1.1 Reservation State Maintenance

27 The ReservationLabel parameter of the FlowNNNNReservationFwd or
28 FlowNNNNReservationRev attribute indicates the higher layer flows associated with RLP
29 flow NNNN. Each ReservationLabel shall be associated with no more than one forward RLP
30 flow. Each ReservationLabel shall be associated with no more than one reverse RLP flow.
31 Each Reservation can be in one of the following two states:
32 • Close State
33 • Open State
34 The transmitter should transmit a higher layer payload using the RLP flow associated with
35 the higher layer flow if the associated RLP flow is activated and if the Reservation is in the
36 Open state. The transmitter should transmit a higher layer payload belonging to a higher
37 layer flow that is not associated with any RLP flow using the RLP flow with
38 ReservationLabel 0xff. The transmitter may transmit a higher layer payload belonging to a
39 higher layer flow identified by a Reservation that is in the Close state using the RLP flow
4-12
1 with ReservationLabel 0xff. The transmitter may transmit a higher layer payload belonging
2 to a higher layer flow identified by a Reservation that is bound to a de-activated RLP flow
3 using the RLP flow with ReservationLabel 0xff.Figure 4.4.4.2.1-2 and Figure 4.4.4.2.1-3
4 show the state transition diagram at the access terminal and the access network
5 respectively. State transitions that may be caused by the IdleState.ConnectionOpened,
6 ConnectedState.ConnectionClosed and RouteUpdate.ConnectionLost indications are not
7 shown.
Initial State
of Reservations Initial State
other than 0xff of Reservation 0xff
Rx ReservationAccept for a ReservationOnRequest
or Rx RevReservationOn
Close State O pen State
Rx ReservationAccept for a ReservationOffRequest

8
or Rx RevReservationO ff
9 Figure 4.4.4.2.1-2. Reverse Reservation State Diagram (Access Terminal)
Initial State
Initial State
of Reservations
of Reservation 0xff
other than 0xff
Tx ReservationAccept for a ReservationOnRequest
or Tx FwdReservationOn
Tx ReservationAccept for a ReservationOffRequest

10
11 Figure 4.4.4.2.1-3. Forward Reservation State Diagram (Access Network)
12 The access terminal and the access network shall not perform any actions that will result
13 in the number of Reverse Link Reservations in the Open state to exceed the value specified
14 by MaxNumOpenReservationsRev. The access terminal and the access network shall not
15 perform any actions that will result in the number of Forward Link Reservations in the
16 Open state to exceed the value specified by MaxNumOpenReservationsFwd.
17 4.4.4.2.1.1.1 State-independent Requirements
18 4.4.4.2.1.1.1.1 Access Terminal Requirements

19 Upon receiving a RevReservationOn message, the access terminal shall
20 • Respond with a ReservationAccept message within the time period specified by
21 TRLPResponse of receiving the RevReservationOn message.
22 • Set the TransactionID field of the ReservationAccept message to that of the
23 RevReservationOn message.
24 Upon receiving a RevReservationOff message, the access terminal shall
4-13
1 • Respond with a ReservationAccept message within the time period specified by

2 TRLPResponse of receiving the RevReservationOff message.
3 • Set the TransactionID field of the ReservationAccept message to that of the
4 RevReservationOff message.
5 Upon receiving a FwdReservationOn message, the access terminal shall
6 • Respond with a FwdReservationAck message within the time period specified by
7 TRLPResponse of reception of the FwdReservationOn message.
8 • Set the TransactionID field of the FwdReservationAck message to that of the
9 FwdReservationOn message.
10 Upon receiving a FwdReservationOff message, the access terminal shall
11 • Respond with a FwdReservationAck message within the time period specified by
12 TRLPResponse of receiving the FwdReservationOff message.
13 • Set the TransactionID field of the FwdReservationAck message to that of the
14 FwdReservationOff message.
15 4.4.4.2.1.1.1.2 Access Network Requirements

16 The access network may re-send a FwdReservationOn message if it does not receive a
17 FwdReservationAck message containing the same TransactionID within the time period
18 specified by TRLPResponse of sending the FwdReservationOn message.
19 The access network may re-send a FwdReservationOff message if it does not receive a
20 FwdReservationAck message containing the same TransactionID within the time period
21 specified by TRLPResponse of sending the FwdReservationOff message.
22 The access network may send a RevReservationOn message to transition the state of the
23 reverse link Reservation of the access terminal to the Open state. The access network may
24 re-send a RevReservationOn message if it does not receive a ReservationAccept message
25 containing the same TransactionID within the time period specified by TRLPResponse of
26 sending the RevReservationOn message.
27 The access network may send a RevReservationOff message to transition the state of the
28 reverse link Reservation of the access terminal to the Close state. The access network may
29 re-send a RevReservationOff message if it does not receive a ReservationAccept message
30 containing the same TransactionID within the time period specified by TRLPResponse of
31 sending the RevReservationOff message.
32 If the access network receives a ReservationOnRequest message, it shall
33 • Send either a ReservationAccept message or a ReservationReject message within the
34 time period specified by TRLPResponse of reception of the ReservationOnRequest message.
35 • Set the TransactionID field of the ReservationAccept or ReservationReject message to
36 that of the ReservationOnRequest message.
37 If the access network receives a ReservationOffRequest message, it shall
4-14
1 • Send a ReservationAccept or a ReservationReject message within the time period

2 specified by TRLPResponse of reception of the ReservationOffRequest message.
3 • Set the TransactionID field of the ReservationAccept or ReservationReject message to
4 that of the ReservationOffRequest message.
5 4.4.4.2.1.1.2 Close State

7 The access terminal shall not transmit SDUs from higher layer flows belonging to this
8 Reservation using any RLP flow other than the RLP flow associated with ReservationLabel
9 0xff. The access terminal may send a ReservationOnRequest message to request transition
10 of the Reservation to the Open state6. The access terminal may re-send a
11 ReservationOnRequest message if it does not receive a corresponding ReservationAccept or
12 ReservationReject message within the time period specified by TRLPResponse of sending the
13 ReservationOnRequest message. If the ReservationOnRequest message contains a reverse
14 Reservation, then the Reservation shall transition to the Open state when the access
15 terminal receives the corresponding ReservationAccept message.
16 Upon receiving a RevReservationOn message, the access terminal shall transition the
17 Reservation to the Open state. Upon receiving an IdleState.ConnectionOpened indication,
18 the access terminal shall transition the Reservations to the Open State whose
19 corresponding ReservationKKIdleStateRev attribute is 0x02, where KK is the two-digit
20 hexadecimal ReservationLabel in the range 0x00 to 0xff inclusive.

22 If the Reservation entered this state as a result of any condition other than the following
23 conditions, then the access network shall send a FwdReservationOff message upon
24 entering this state:
25 • the access network transmitted a ReservationAccept message in response to a
26 ReservationOffRequest message requesting to transition the Reservation to the Close
27 state, or
28 • ReservationKKIdleStateFwd attribute of the Reservation is 0x01 or 0x02, and the
29 Reservation transitioned to the Close state because the Connection was closed or lost.
30 Upon sending a ReservationAccept message for a forward Reservation in response to a
31 ReservationOnRequest message, the access network shall transition the Reservation to the
32 Open state.
33 Upon sending a FwdReservationOn message, the access network shall transition the
34 Reservation to the Open State. Upon receiving an IdleState.ConnectionOpened indication,
6 Note that the ReservationOnRequest message supports requests for multiple Reservations on both
the forward and reverse links. This arrangement allows requests for groups of Reservations (e.g., for
bidirectional higher layer application flows) to be combined in the same ReservationOnRequest
message.
4-15
1 the access network shall transition the Reservations to the Open State whose
2 corresponding ReservationKKIdleStateFwd attribute is 0x02, where KK is the two-digit
3 hexadecimal ReservationLabel in the range 0x00 to 0xff inclusive.
4 The access network may transmit SDUs from higher layer flows belonging to this
5 Reservation using the Link Flow to which the Reservation is bound. Upon doing so, the
6 access network shall transition the Reservation to the Open State.
7 4.4.4.2.1.1.3 Open State

9 The access terminal may transmit SDUs from higher layer flows belonging to this
10 Reservation using the RLP flow to which the Reservation is bound.
11 The access terminal may send a ReservationOffRequest message to request the transition
12 of a Reservation to the Close state. The access terminal may re-send a
13 ReservationOffRequest message if it does not receive a ReservationAccept or
14 ReservationReject message within the time period specified by TRLPResponse of sending the
15 ReservationOffRequest message. If the ReservationOffRequest message contains a reverse
16 Reservation, then the access terminal shall transition the Reservation to the Close state
17 when the access terminal receives a ReservationAccept message.
18 Upon receiving a RevReservationOff message, the access terminal shall transition the
19 Reservation to the Close state. Upon receiving a ConnectedState.ConnectionClosed
20 indication, the access terminal shall transition to the Close state Reservations whose
21 corresponding ReservationKKIdleStateRev attribute is 0x01 or 0x02 unless an access
22 network initiated Connection is being opened at the same time7, where KK is the two-digit
23 hexadecimal ReservationLabel. Upon receiving an IdleState.ConnectionFailed indication, the
24 access terminal shall transition to the Close state Reservations whose corresponding
25 ReservationKKIdleStateRev attribute is 0x01 or 0x02, where KK is the two-digit
26 hexadecimal ReservationLabel.

28 The access network may transmit SDUs from higher layer flows belonging to this
29 Reservation using the RLP flow to which the Reservation is bound.
30 Upon sending a ReservationAccept message for a forward Reservation in response to a
31 ReservationOffRequest message, the access network shall transition the Reservation to the
32 Close State.
33 Upon receiving a ConnectedState.ConnectionClosed or RouteUpdate.ConnectionLost
34 indication, the access network shall transition to the Close state Reservations whose
35 corresponding ReservationKKIdleStateFwd attribute is 0x01 or 0x02 unless an access
36 network initiated Connection is being opened at the same time, where KK is the two-digit
7 An access network can send ConnectionClose message of Connected State Protocol and
TrafficChannelAssignment message of Route Update Protocol in the same security layer packet.
4-16
1 hexadecimal ReservationLabel. Upon receiving a RouteUpdate.ConnectionLost or

2 IdleState.ConnectionFailed indication, the access network shall transition to the Close state
3 Reservations whose corresponding ReservationKKIdleStateFwd attribute is 0x01 or 0x02,
4 where KK is the two-digit hexadecimal ReservationLabel.
5 If, for any KK, all of the following conditions are true, the access network shall take action
6 within TTurnaround, where TTurnaround is equal to 2 seconds, such that at least one of the
7 following conditions would no longer be true (e.g., by modifying the value of
8 ReservationKKQoSResponseFwd or by transitioning forward Reservation KK to the Close
9 state):
10 • ReservationKKQoSRequestFwd is set to a non-default value.
11 • Forward Reservation KK is in the Open state.
12 • ReservationKKQoSResponseFwd is set to the default value or the
13 QoS_ATTRIBUTE_SET_ID field in ReservationKKQoSResponseFwd is not equal to the
14 value of any QoS_ATTRIBUTE_SET_ID field in the corresponding
15 ReservationKKQoSRequestFwd attribute (see [18]).
16 If, for any KK, all of the following conditions are true, the access network shall take action
17 within TTurnaround, where TTurnaround is equal to 2 seconds, such that at least one of the
18 following conditions would no longer be true (e.g., by modifying the value of
19 ReservationKKQoSResponseRev or by transitioning reverse Reservation KK to the Close
20 state):
21 • ReservationKKQoSRequestRev is set to a non-default value.
22 • Reverse Reservation KK is in the Open state.
23 • ReservationKKQoSResponseRev is set to the default value or the
24 QoS_ATTRIBUTE_SET_ID field in ReservationKKQoSResponseRev is not equal to the
25 value of any QoS_ATTRIBUTE_SET_ID field in the corresponding
26 ReservationKKQoSRequestRev attribute (see [18]).
27 4.4.4.2.2 RLP Receive Procedures

28 The RLP receiver shall maintain two SequenceLength-bit variables for receiving, V(R)NN and
29 V(N)NN (see Figure 4.4.4.2.2-1), where NN is the two-digit hexadecimal RLP flow number in
30 the range 0x00 to M - 1 inclusive, where M is MaxNumRLPFlowsFwd or
31 MaxNumRLPFlowsRev for an RLP flow on the forward link or reverse link respectively.
32 V(R)NN contains the sequence number of the next new octet expected to arrive. V(N)NN
33 contains the sequence number of the first missing octet, as described below.
34 In addition, the RLP receiver shall keep track of the status of each octet in its resequencing
35 buffer indicating whether the octet was received or not. Use of this status is implied in the
37
4-17
V(N)NN = next octet needed V(R)NN = next new

for sequential delivery ↓ ↓ octet expected
••• •••
Octets received in sequence
Octets received out of sequence
Buffer space for new or missed octets
1 Figure 4.4.4.2.2-1. RLP Receive Sequence Number Variables
2 In the following, X denotes the sequence number of a received octet. For each received
3 octet, RLP shall perform the following procedures:
4 • If X < V(N)NN, the octet shall be discarded as a duplicate.
5 • If V(N)NN ≤ X < V(R)NN, and the octet is not already stored in the resequencing buffer,
6 then:
7 − RLP shall store the received octet in the resequencing buffer.
8 − If X = V(N)NN, RLP shall pass all contiguous octets in the resequencing buffer,
9 from V(N)NN upward, to the higher layer8, and may remove the passed octets
10 from the resequencing buffer. RLP shall then set V(N)NN to (LAST+1) where
11 LAST is the sequence number of the last contiguous octet (i.e., the octet with
12 the highest sequence number) passed to the higher layer from the
14 • If V(N)NN < X < V(R)NN, and the octet has already been stored in the resequencing buffer,
15 then the octet shall be discarded as a duplicate.
16 • If X = V(R)NN, then:
17 − If V(R)NN = V(N)NN, RLP shall increment V(N)NN and V(R)NN and shall pass the
18 octet to the higher layer.
19 − If V(R)NN ≠ V(N)NN, RLP shall increment V(R)NN and shall store the octet in the
21 • If X > V(R)NN, then:
22 − RLP shall store the octet in the resequencing buffer.
8 If the RLP receiver is an access terminal, then the higher layer is indicated by the
FlowNNHigherLayerProtocolFwd attribute. If the RLP receiver is an access network, then the higher
layer is indicated by the FlowNNHigherLayerProtocolRev attribute.
4-18
1 − If the RLP receiver is an access network, then RLP shall set a RLP abort timer
2 to the AbortTimer parameter associated with reverse RLP flow NN for each
3 missing RLP octet from V(R)NN to X-1, inclusive. If the RLP receiver is an access
4 terminal, then RLP shall set a RLP abort timer to the AbortTimer parameter
5 associated with forward RLP flow NN for each missing RLP octet from V(R)NN to
6 X-1, inclusive.
7 − If the RLP receiver is an access terminal, and if the FlowNNNakEnableFwd
8 attribute is set to 0x01, RLP shall send a Nak message requesting the
9 retransmission of all missing RLP octets in the range of V(R)NN to X-1, inclusive
10 after the delay specified by the FlowNNNAKDelayTimeFwd attribute. The
11 access terminal shall not send a Nak message if there are no missing octets in
12 the range of V(R)NN to X-1 at the end of the delay specified by the
13 FlowNNNAKDelayTimeFwd attribute. V(R)NN and X in the above are the values
14 of the V(R)NN and X at the time the RLP receiver detected the missing octets.
15 − RLP shall set V(R)NN to X+1.
16 If a missing octet has not arrived when its RLP abort timer expires, RLP shall pass all
17 octets in the resequencing buffer up to the missing octet, in order of sequence number, to
18 the higher layer. RLP shall skip any missing octets. RLP shall set V(N)NN to the sequence
19 number of the next missing octet, or to V(R)NN if there are no remaining missing octets.
20 Further recovery is the responsibility of the higher layer protocols.
21 4.4.4.3 RLP Packet Header

22 The RLP packet header, which precedes the RLP payload, has the following format:
23
Field Length (bits)

RLPID RLPIDLength9
SEQ SequenceLength10
24 RLPID The identifier for this RLP flow.
25 SEQ The RLP sequence number of the first octet in the RLP payload.
9 If this RLP packet is being sent on the forward link, the length of this field is specified by the
RLPIDLength field in the FlowNNIdentificationFwd attribute corresponding to this flow. If this RLP
packet is being sent on the reverse link, the length of this field is specified by the RLPIDLength field
in the FlowNNIdentificationRev attribute corresponding to this flow.
10 If this RLP packet is being sent on the forward link, the length of this field is specified by the
SequenceLength field in the FlowNNIdentificationFwd attribute corresponding to this flow. If this RLP
packet is being sent on the reverse link, the length of this field is specified by the SequenceLength
field in the FlowNNIdentificationRev attribute corresponding to this flow.
4-19

2 The messages described in this section control the function of the RLP. These messages are
3 exchanged between the access terminal and the access network using the SNP.
4 4.4.4.4.1 ResetTxIndication
5 The RLP transmitter in the access terminal or the access network sends the
6 ResetTxIndication message to reset its peer RLP receiver.
7
Field Length (bits)
MessageID 8
RLPFlow 5
Reserved 3
9 RLPFlow The sender shall set this field to the RLP flow that is reset. The
10 sender shall set this field to ‘11111’ to reset all RLP flows.
11 Reserved The sender shall set this field to ‘000’. The receiver shall ignore this
12 field.
13
Addressing Unicast Priority 50
14 4.4.4.4.2 ResetRxIndication
15 The RLP receiver in the access terminal or the access network sends the ResetRxIndication
16 message to reset its peer RLP transmitter.
17
Field Length (bits)
MessageID 8
RLPFlow 5
Reserved 3
19 RLPFlow The sender shall set this field to the RLP flow that is reset. The
20 sender shall set this field to ‘11111’ to reset all RLP flows.
22 field.
23
4-20
1 4.4.4.4.3 ResetTxIndicationAck
2 The RLP receiver in the access terminal or the access network sends the
3 ResetTxIndicationAck message in response a to ResetTxIndication message.
4
Field Length (bits)
MessageID 8
RLPFlow 5
Reserved 3
5
6 MessageID The sender shall set this field to 0x0d.
7 RLPFlow The sender shall set this field to the RLP flow that is reset. If this
8 message is being sent in response to a ResetTxIndication message
9 that required reset of all RLP flows, then the sender shall set this
10 field to ‘11111’.
12 field.
13
14 4.4.4.4.4 ResetTxComplete
16 ResetTxComplete message to complete the RLP reset procedure.
17
Field Length (bits)
MessageID 8
RLPFlow 5
Reserved 3
18
19 MessageID The sender shall set this field to 0x0e.
20 RLPFlow The sender shall set this field to the RLP flow that is reset. If all RLP
21 flows were reset, then the sender shall set this field to ‘11111’.
4-21
2 field.
3
4 4.4.4.4.5 ResetRxComplete
6 ResetRxComplete message to complete the RLP reset procedure.
7
Field Length (bits)
MessageID 8
RLPFlow 5
Reserved 3
8
9 MessageID The sender shall set this field to 0x0f.
10 RLPFlow The sender shall set this field to the RLP flow that is reset. If all RLP
11 flows were reset, then the sender shall set this field to ‘11111’.
13 field.
14
15 4.4.4.4.6 Nak
16 The access terminal and the access network send the Nak message to request the
17 retransmission of one or more octets.
18
Field Length (bits)
MessageID 8
RLPFlow 5
Reserved1 3
SequenceLength 8
NakRequests 8
NakRequests occurrences of the following three fields:
4-22
Field Length (bits)
FirstErased SequenceLength
WindowLen 16
Reserved2 0-7 (as needed)
2 RLPFlow The sender shall set this field to the RLP flow for which this Nak is
3 being sent.
4 Reserved1 The sender shall set this field to ‘000’. The receiver shall ignore this
5 field.
6 SequenceLength The sender shall set this field to the size of the sequence space in
7 units of bits for this RLP flow.
8 NakRequests The sender shall set this field to the number of Nak requests
9 included in this message. The sender shall include NakRequests
10 occurrences of the following three fields with the message.
11 FirstErased The sender shall set this field to the sequence number of the first
12 RLP octet erased in a sequence of erased octets whose
13 retransmission is requested.
14 WindowLen The sender shall set this field to the length of the erased window.
15 Reserved2 The sender shall add reserved bits to make the length of the entire
16 record an integer number of octets. The sender shall set these bits to
17 ‘0’. The receiver shall ignore these bits.
18
19 4.4.4.4.7 ReservationOnRequest
20 The access terminal sends this message to request transition of one or more Reservations
21 to the Open State.
22
4-23
Field Length (bits)
MessageID 8
TransactionID 8
ReservationCount 8
ReservationCount occurrences of the following two
fields:
Link 1
ReservationLabel 8
EmergencyIndication 0 or 1
Reserved 0 – 7 (as needed)
2 TransactionID The access terminal shall set this field to one more (modulo 256)
3 than the TransactionID field of the last ReservationOnRequest or
4 ReservationOffRequest message sent by the access terminal. If this is
5 the first ReservationOnRequest or ReservationOffRequest message
6 sent by the access terminal, then the access terminal shall set this
7 field to zero.
8 ReservationCount The access terminal shall set this field to the number of
9 ReservationLabel fields in this message.
10 Link If this request is for a forward Reservation, then the access terminal
11 shall set this field to ‘1’. If this request is for a reverse Reservation,
12 then the access terminal shall set this field to ‘0’.
13 ReservationLabel The access terminal shall set this field to the ReservationLabel for
14 which this request is generated.
15 EmergencyIndication
16 If included, the access terminal shall set this field as follows:

17 If this is an emergency ReservationOnRequest, then the access
18 terminal shall set this field to ‘1’. Otherwise, the access terminal shall
20 Reserved The access terminal shall add reserved bits to make the length of the
21 entire message an integer number of octets. The access terminal
22 shall set these bits to ‘0’. The access network shall ignore this field.
23
4-24
1 4.4.4.4.8 ReservationOffRequest
2 The access terminal sends this message to request transition of one or more Reservations
3 to the Close State.
4
Field Length (bits)
MessageID 8
TransactionID 8
ReservationCount 8
fields:
Link 1
ReservationLabel 8
7 than the TransactionID field of the last ReservationOnRequest or
8 ReservationOffRequest message sent by the access terminal. If this is
9 the first ReservationOnRequest or ReservationOffRequest message
10 sent by the access terminal, then the access terminal shall set this
11 field to zero.
12 ReservationCount The access terminal shall set this field to the number of
14 Link If this request is for a forward Reservation, then the access terminal
15 shall set this field to ‘1’. If this request is for a reverse Reservation,
16 then the access terminal shall set this field to ‘0’.
17 ReservationLabel The access terminal shall set this field to the Reservation for which
18 this request is generated.
22
4-25
1 4.4.4.4.9 ReservationAccept
2 The access network sends this message to acknowledge reception of and allow the state
3 transition requested by a ReservationOnRequest or ReservationOffRequest message. The
4 access terminal sends this message to acknowledge reception of and accept the state
5 transition requested by a RevReservationOn or RevReservationOff message.
6
Field Length (bits)
MessageID 8
TransactionID 8
8 TransactionID The access network shall set this field to the TransactionID field of
9 the ReservationOnRequest or ReservationOffRequest message to
10 which the access network is responding. The access terminal shall
11 set this field to the TransactionID field of the RevReservationOn or
12 RevReservationOff message to which the access terminal is
13 responding.
14
Channels CC FTC RTC AC SLP Best Effort
15 4.4.4.4.10 ReservationReject
16 The access network sends this message to acknowledge reception of and deny the state
17 transition requested by a ReservationOnRequest or ReservationOffRequest message.
18
4-26
Field Length (bits)
MessageID 8
TransactionID 8
ReservationCount 8
fields:
AllowableLink 1
AllowableReservationLabel 8
2 TransactionID The access network shall set this field to the TransactionID field of
3 the ReservationOnRequest or ReservationOffRequest message to
4 which the access network is responding.
5 ReservationCount The access network shall set this field to the number of
6 AllowableReservationLabel fields in this message.
7 AllowableLink If the Reservation for which the access network would have allowed
8 the state transition requested in the ReservationOnRequest or
9 ReservationOffRequest message is a forward Reservation, then the
10 access network shall set this field to ‘1’. If the Reservation for which
11 the access network would have allowed the state transition requested
12 in the ReservationOnRequest or ReservationOffRequest message is a
13 reverse Reservation, then the access network shall set this field to ‘0’.
14 AllowableReservationLabel
15 The access network shall set this field to the ReservationLabel for
16 which the access network would have allowed the state transition
17 requested in the ReservationOnRequest or ReservationOffRequest
18 message.
19 Reserved The access network shall add reserved bits to make the length of the
20 entire message an integer number of octets. The access network shall
21 set these bits to ‘0’. The access terminal shall ignore this field.
22
4-27
1 4.4.4.4.11 RevReservationOn
2 The access network sends this message to transition a reverse Reservation to the Open
3 state.
4
Field Length (bits)
MessageID 8
TransactionID 8
ReservationCount 8
ReservationCount occurrences of the following field:
ReservationLabel 8
6 TransactionID The access network shall set this field to one more (modulo 256) than
7 the TransactionID field of the last RevReservationOn or
8 RevReservationOff message sent by the access network. If this is the
9 first RevReservationOn or RevReservationOff message sent by the
10 access network, then the access network shall set this field to zero.
13 ReservationLabel The access network shall set this field to the Reservation which is to
14 be transitioned to the Open state.
15
16 4.4.4.4.12 RevReservationOff
17 The access network sends this message to transition a reverse Reservation to the Close
18 state.
19
4-28
Field Length (bits)
MessageID 8
TransactionID 8
ReservationCount 8
ReservationLabel 8
3 the TransactionID field of the last RevReservationOn or
4 RevReservationOff message sent by the access network. If this is the
5 first RevReservationOn or RevReservationOff message sent by the
9 ReservationLabel The access network shall set this field to the Reservation that is to be
10 transitioned to the Close state.
11
12 4.4.4.4.13 FwdReservationOff
13 The access network sends this message to inform the access terminal when a forward
14 Reservation transitions to the Close state.
15
Field Length (bits)

MessageID 8
TransactionID 8
ReservationCount 8
ReservationLabel 8
18 the TransactionID field of the last FwdReservationOn or
19 FwdReservationOff message sent by the access network. If this is the
20 first FwdReservationOn or FwdReservationOff message sent by the
4-29
3 ReservationLabel The access network shall set this field to the Reservation transitioned
4 to the Close state.
5
6 4.4.4.4.14 FwdReservationOn
7 The access network sends this message to inform the access terminal when a forward
8 Reservation transitions to the Open state.
9
Field Length (bits)
MessageID 8
TransactionID 8
ReservationCount 8
ReservationLabel 8
12 the TransactionID field of the last FwdReservationOn or
13 FwdReservationOff message sent by the access network. If this is the
14 first FwdReservationOn or FwdReservationOff message sent by the
18 ReservationLabel The access network shall set this field to the Reservation that
19 transitioned to the Open state.
20
21 4.4.4.4.15 FwdReservationAck
22 The access terminal sends this message to acknowledge reception of the FwdReservationOn
23 or the FwdReservationOff message and to accept the related state transition.
24
4-30
Field Length (bits)
MessageID 8
TransactionID 8
3 the FwdReservationOn or FwdReservationOff message to which the
4 access terminal is responding.
5
6 4.4.4.4.16 AttributeUpdateRequest
7 The sender sends an AttributeUpdateRequest message to offer an attribute value for a
8 given attribute.
9
Field Length (bits)
MessageID 8
TransactionID 8
One or more instances of the following record
12 AttributeUpdateRequest message sent.

14
15 4.4.4.4.17 AttributeUpdateAccept
16 The sender sends an AttributeUpdateAccept message in response to an
17 AttributeUpdateRequest message to accept the offered attribute values.
18
4-31
Field Length (bits)
MessageID 8
TransactionID 8
3 corresponding AttributeUpdateRequest message.
4
5 4.4.4.4.18 AttributeUpdateReject
6 The access network sends an AttributeUpdateReject message in response to an
7 AttributeUpdateRequest message to reject the offered attribute values.
8
Field Length (bits)
MessageID 8
TransactionID 8
12
Channels FTC SLP Reliable
14 4.4.4.5.1 Commands
19 • IdleState.ConnectionFailed
20 • PhysicalLayer.ReverseTrafficPacketsMissed along with parameters indicating the RLP
21 flow number and missing octets.
4-32
1 • ConnectedState.ConnectionClosed
2 • RouteUpdate.ConnectionLost
3 4.4.4.6 RLP Packet Priorities

4 The sender shall assign priority between 60 and 70 inclusive to RLP packets. For a given
5 RLP flow, the sender shall assign higher priority (lower number) to packets containing
6 retransmitted application traffic than packets containing only first time transmissions. If
7 FlowNNTransmitAbortTimerRev is not set to 0x00, then the access terminal should
8 transmit a higher layer octet within FlowNNTransmitAbortTimerRev time of the higher layer
9 octet being received by the Multi-flow Packet Application. The access terminal may use the
10 FlowNNTransmitAbortTimerRev attribute to determine the priority of reverse RLP packets.
11
Type of RLP Packet Channel Addressing Priority

Packet containing only First Between 60 and 70
FTC, RTC unicast
Time Transmissions inclusive
Packet containing re-
Between 60 and 70
transmitted application FTC, RTC unicast
inclusive
traffic

13

network is to respond to
TRLPRespons 1 second
ReservationOnRequest and
e
ReservationOffRequest messages.
4-33
1 4.5 Data Over Signaling Protocol
2 4.5.1 Overview
3 The Data Over Signaling Protocol provides transmission and duplicate detection of higher
4 layer packets using signaling messages. A higher layer packet is carried in a
5 DataOverSignaling message. The Data Over Signaling Protocol uses message sequence
6 numbers in the DataOverSignaling message to provide duplicate detection. Data Over
7 Signaling Protocol is associated with the Multi-Flow Packet Application. The application
8 subtype for this application is defined in [10].
10 4.5.2.1 Commands


15 The transmission unit of this protocol is a DataOverSignaling message. The
16 DataOverSignaling message carries payload on behalf the higher layer. This protocol uses
17 the Signaling Application to transmit and receive messages.
20 If FlowNNDataOverSignalingAllowedRev is set to 0x00, the access terminal shall not send a
21 DataOverSignaling message for RLP flow NN. The sender shall set the MessageSequence
22 field of a DataOverSignaling message to V(S). Each time the sender sends a new
23 DataOverSignaling message, it shall increment the value of V(S). If the sender does not
24 receive a DataOverSignalingAck message within an implementation specific time interval in
25 response to a DataOverSignaling message requiring an acknowledgment, then the sender
26 may retransmit the DataOverSignaling message containing the same higher layer packet
27 and the same MessageSequence an implementation specific number of times.
28 The access terminal or the access network shall not send a DataOverSignaling message if
29 the associated RLP flow for which the DataOverSignaling message is carrying payload is
30 deactivated, or if the associated Reservation is in the Close state.
31 Upon receiving a DataOverSignaling message, the receiver shall perform the following:
32 • If Reset is set to ‘1’ and the receiver is the access terminal, the receiver shall set V(R) to
33 (MessageSequence – 1) mod 64.
4-34
1 • The receiver shall validate the message using the procedure defined in 13.6 by setting
2 the variable V(R) defined in 13.6 to the V(R) value maintained by the receiver, and by
3 setting S = 6.
4 • The receiver shall discard the DataOverSignaling message if it is invalid. If the
5 DataOverSignaling message is valid, then the receiver shall pass the HigherLayerPacket
6 field of the DataOverSignaling message to the higher layer. If the receiver is an access
7 terminal, then the higher layer is indicated by the FlowNNHigherLayerProtocolFwd
8 attribute, where NN is the RLP Flow with which the DataOverSignaling message is
9 associated. If the receiver is an access network, then the higher layer is indicated by the
10 FlowNNHigherLayerProtocolRev attribute, where NN is the RLP Flow with which the
11 DataOverSignaling message is associated.
12 • If the AckRequired field of the DataOverSignaling message is ‘1’, then the receiver shall
13 respond with a DataOverSignalingAck message with AckSequence field set to the
14 MessageSequence field of the DataOverSignaling message.

16 The messages described in this section are exchanged between the access terminal and the
17 access network using the Signaling Application.
18 4.5.4.2.1 DataOverSignaling
19 The access network or the access terminal sends the DataOverSignaling message to
20 transmit a higher layer packet.
21
Field Length (bits)
MessageID 8
AckRequired 1
Reset 1
MessageSequence 6
HigherLayerPacket Variable Length
23 AckRequired The sender shall set this field to ‘1’ if the receiver is required to
24 acknowledge the receipt of this message. Otherwise, the sender shall
26 Reset The access terminal shall set this field to ‘0’. The access network may
27 set this field to ‘1’ to indicate that the access terminal is to reset its
28 V(R). The access network may set this field to ‘0’ to indicate that the
29 access terminal is not required to reset its V(R).
4-35
1 MessageSequence The sender shall set this field to 1 higher than the MessageSequence
2 field of the last DataOverSignaling message (modulo 64) that it has
3 sent.
4 HigherLayerPacket The sender shall set this field to an entire higher layer packet11. The
5 length of the higher layer packet shall be an integer number of octets.
6
Channels CC AC FTC SLP Best Effort
20 to 50
Addressing unicast Priority
(inclusive)
7 The sender shall assign message priority in the range 20 to 50, inclusive, depending on the
8 priority of the higher layer packet carried as payload in this message.
9 4.5.4.2.2 DataOverSignalingAck
10 The access network or the access terminal sends a DataOverSignalingAck message to
11 acknowledge receipt of a DataOverSignaling message.
12
Field Length (bits)
MessageID 8
Reserved 2
AckSequence 6
15 field.
16 AckSequence The sender shall set this field to the MessageSequence field of the
17 DataOverSignaling message whose receipt is being acknowledged.
Channels CC AC FTC RTC SLP Best Effort
19 4.5.4.3.1 Commands
11 For example, if the higher layer packet is an HDLC frame, then the entire HDLC frame is included.
4-36
1 4.6 Location Update Protocol
2 4.6.1 Overview
3 The Location Update Protocol defines location update procedures and messages for mobility
4 management for the Multi-Flow Packet Application.
5 The Location Update Protocol is a protocol associated with the Multi-Flow Packet
6 Application. The application subtype for this application is defined in [10].
8 4.6.2.1 Commands


17 4.6.4.1.1 Access Network Requirements

18 If the protocol receives an AddressManagement.SubnetChanged indication, the access
19 network:
20 • May send a LocationRequest message to query the Location information.
21 • May send a LocationAssignment message to update the Location information.
22 • May send a StorageBLOBRequest message to query the stored BLOB.
23 • May send a StorageBLOBAssignment message to update the stored BLOB.
24 4.6.4.1.2 Access Terminal Requirements

25 If the access terminal receives a LocationRequest message, it shall send a
26 LocationNotification message. If the access terminal has a stored value for the
27 LocationValue parameter, the access terminal shall set the LocationType, LocationLength,
28 and LocationValue fields in this message to its stored values of these fields. If the access
29 terminal does not have a stored value for the LocationValue parameter, the access terminal
30 shall omit the LocationLength and LocationValue fields in this message.
31 If the access terminal receives a LocationAssignment message, it shall send a
32 LocationComplete message and the access terminal shall store the value of the
4-37
1 LocationType, LocationLength, and LocationValue fields of the LocationAssignment

2 message in LocationType, LocationLength, and LocationValue variables, respectively.
3 If the access terminal receives a StorageBLOBRequest message, it shall send a
4 StorageBLOBNotification message. If the access terminal has a stored value for the
5 StorageBLOB parameter, the access terminal shall set the StorageBLOBLength and
6 StorageBLOB fields in this message to its stored values of these fields. If the access
7 terminal does not have a stored value for the StorageBLOB parameter, the access terminal
8 shall set the StorageBLOBLength field to zero and shall omit the StorageBLOB fields in this
9 message.
10 If the access terminal receives a StorageBLOBAssignment message, it shall send a
11 StorageBLOBComplete message and the access terminal shall store the value of the
12 StorageBLOBLength and StorageBLOB fields of the StorageBLOBAssignment message in
13 StorageBLOBLength and StorageBLOB variables, respectively.
15 4.6.4.2.1 LocationRequest
16 The access network uses this message to query the access terminal of its Location
17 information.
18
Field Length (bits)
MessageID 8

20
21 4.6.4.2.2 LocationNotification
22 The access terminal sends the LocationNotification message either in response to the
23 LocationRequest message or in an unsolicited manner as specified in [98][9] if the
24 configured value of the RANHandoff attribute is 0x01.
25
Field Length (bits)
MessageID 8
LocationType 8
LocationLength 0 or 8
LocationValue 0 or 8 × LocationLength
4-38
1 LocationType The access terminal shall set this field to zero if the value of its stored
2 LocationValue is NULL; otherwise, the access terminal shall set this
3 field to the stored value of LocationType.
4 LocationLength The access terminal shall not include this field if the value of its
6 set this field to the stored value of LocationLength.
7 LocationValue The access terminal shall not include this field if the value of its
9 set this field to the stored value of LocationValue.
10
11 4.6.4.2.3 LocationAssignment
12 The access network uses this message to update the Location information of the access
13 terminal.
Field Length (bits)
MessageID 8
TransactionID 8
LocationType 8
LocationLength 8
LocationValue 8 × LocationLength
16 LocationAssignment message sent.
17 LocationType The access network shall set this field to the type of the location as
18 specified in Table 4.6.4.2-1.
4-39
1 Table 4.6.4.2-1. LocationType Encoding
LocationType LocationLength Meaning
0x00 N/A No location is stored

0x01 0x05 Location compatible with [3]
(see Table 4.6.4.2-2)
All other values N/A Reserved
2 LocationLength The access network shall set this field to the length of the
3 LocationValue field in octets as specified in Table 4.6.4.2-1.
4 LocationValue The access network shall set this field to the Location of type
5 specified by LocationType. If LocationType is set to 0x01, the access
6 network shall set this field as shown in Table 4.6.4.2-2, where SID,
7 NID, and PACKET_ZONE_ID correspond to the current access
8 network.
9 Table 4.6.4.2-2. Subfields of LocationValue when LocationType = 0x01
Sub-fields of
# of bits
LocationValue
SID 15
Reserved 1
NID 16
PACKET_ZONE_ID 8
10
11 4.6.4.2.4 LocationComplete
12 The access terminal sends this message in response to the LocationAssignment message.
13
Field Length (bits)
MessageID 8
TransactionID 8
16 the corresponding LocationAssignment message.
17
4-40
1 4.6.4.2.5 StorageBLOBRequest
2 The access network uses this message to query the access terminal of its StorageBLOB
3 information.
4
Field Length (bits)
MessageID 8

6
7 4.6.4.2.6 StorageBLOBNotification
8 The access terminal sends the StorageBLOBNotification message in response to the
9 StorageBLOBRequest message.
10
Field Length (bits)
MessageID 8
StorageBLOBType 16
StorageBLOBLength 8
StorageBLOB 0 or 8 ×
StorageBLOBLength
12 StorageBLOBType
13 The access terminal shall set this field to zero if the value of its stored
14 StorageBLOB is NULL; otherwise, the access terminal shall set this
15 field to the stored value of StorageBLOBType.
16 StorageBLOBLength
17 The access terminal shall set this field if the value of its stored
18 StorageBLOB is NULL; otherwise, the access terminal shall set this
19 field to the stored value of StorageBLOBLength.
20 StorageBLOB The access terminal shall not include this field if the value of its
21 stored StorageBLOB is NULL; otherwise, the access terminal shall set
22 this field to the stored value of StorageBLOB.
23
4-41
1 4.6.4.2.7 StorageBLOBAssignment
2 The access network uses this message to update the StorageBLOB information of the
3 access terminal.
4
Field Length (bits)
MessageID 8
TransactionID 8
StorageBLOBType 16
StorageBLOBLength 8
StorageBLOB 8 × StorageBLOBLength
7 StorageBLOBAssignment message sent.
8 StorageBLOBType The access network shall set this field to the StorageBLOBType. The
9 access network shall set this field to zero if StorageBLOB is NULL.
10 Otherwise, the access network shall set this field as defined in [10].
11 StorageBLOBLength
12 The access network shall set this field to the length of the
13 StorageBLOB field in octets. The access network shall set this field to
14 zero if StorageBLOB is NULL.
15 StorageBLOB The access network shall not include this field if the StorageBLOB is
16 NULL. Otherwise, the access network shall set this field to the
17 StorageBLOB.
18
19 4.6.4.2.8 StorageBLOBComplete
20 The access terminal sends this message in response to the StorageBLOBAssignment
21 message.
22
4-42
Field Length (bits)
MessageID 8
TransactionID 8
3 the corresponding StorageBLOBAssignment message.
4
6 4.6.4.3.1 Commands
10 • AddressManagement.SubnetChanged (access network only)
4-43
1 4.7 Flow Control Protocol
2 4.7.1 Overview
3 The Flow Control Protocol provides procedures and messages used by the access terminal
4 and the access network to perform flow control for the Multi-Flow Packet Application.
5 This protocol can be in one of the following states:
6 • Close State: in this state the Multi-Flow Packet Application does not send or receive any
7 RLP packets or DataOverSignaling messages.
8 • Open State: in this state the Multi-Flow Packet Application can send and receive RLP
9 packets and DataOverSignaling messages.
10 Figure 4.7.1-1 and Figure 4.7.1-2 show the state transition diagram at the access terminal
Tx XonRequest
or Tx an RLP packet
Initial State
or Tx a DataOverSignaling message
12
Rx XoffResponse
13 Figure 4.7.1-1. Flow Control Protocol State Diagram (Access Terminal)
Rx XonRequest
or Rx an RLP packet
Initial State
or Rx a DataOverSignaling message
14
Tx XoffResponse
15 Figure 4.7.1-2. Flow Control Protocol State Diagram (Access Network)
16 The flow control protocol is a protocol associated with the Multi-Flow Packet Application.
17 The application subtype for this application is defined in [10].
19 4.7.2.1 Commands
4-44


8 4.7.4.1.1 Transmission and Processing of DataReady Message

9 The access network may send a DataReady message to indicate that there is data
10 corresponding to this packet application waiting to be transmitted.
11 The access terminal shall send a DataReadyAck within the time period specified by
12 TFCResponse after reception of the DataReady message to acknowledge reception of the
13 message.
14 4.7.4.1.2 Close State

16 The access terminal shall send an XonRequest message or an RLP packet (corresponding to
17 this instance of the Multi-Flow Packet Application) or a DataOverSignaling message
18 (corresponding to this instance of the Multi-Flow Packet Application) when it is ready to
19 exchange RLP packets or DataOverSignaling messages with the access network. The access
20 terminal should send an XonRequest message or an RLP packet (corresponding to this
21 instance of the Multi-Flow Packet Application) or a DataOverSignaling message
22 (corresponding to this instance of the Multi-Flow Packet Application) when it receives a
23 DataReady from the access network.
24 The access terminal shall transition to the Open State when it sends an XonRequest
25 message or when it sends an RLP packet (corresponding to this instance of the Multi-Flow
26 Packet Application) or when it sends a DataOverSignaling message (corresponding to this
27 instance of the Multi-Flow Packet Application).

29 The access network shall not send any RLP packets or DataOverSignaling messages in this
30 state.
31 If the access network receives an XonRequest message, it shall:
32 • Send an XonResponse message within the time period specified by TFCResponse after
33 reception of the XonRequest message to acknowledge reception of the message.
4-45
1 The access network shall also transition to the Open State if it receives an RLP packet
2 (corresponding to this instance of the Multi-Flow Packet Application) or a
3 DataOverSignaling message (corresponding to this instance of the Multi-Flow Packet
4 Application).
5 4.7.4.1.3 Open State

6 In this state, the access terminal and the access network may send or receive any RLP
7 packets or DataOverSignaling messages.

9 The access terminal may re-send an XonRequest message if it does not receive an
10 XonResponse message or an RLP packet (corresponding to this instance of the Multi-Flow
11 Packet Application) or a DataOverSignaling message (corresponding to this instance of the
12 Multi-Flow Packet Application) within the time period specified by TFCResponse after sending
13 the XonRequest message.
14 The access terminal should send an XonRequest message if it receives a DataReady
15 message.
16 The access terminal may send an XoffRequest message to request the access network to
17 stop sending RLP packets and DataOverSignaling messages. The access terminal shall
18 transition to the Close state when it receives an XoffResponse message.
19 The access terminal may re-send an XoffRequest message if it does not receive an
20 XoffResponse message within the time period specified by TFCResponse after sending the
21 XoffRequest message.

23 If the access network receives an XoffRequest message, it shall
24 • Send an XoffResponse message within the time period specified by TFCResponse after
25 reception of XoffRequest message to acknowledge reception of the message.
27 If the access network receives an XonRequest message, it shall send an XonResponse
28 message within the time period specified by TFCResponse after reception of the XonRequest
29 message to acknowledge reception of the message.
31 4.7.4.2.1 XonRequest
32 The access terminal sends this message to request transition to the Open State.
33
4-46
Field Length (bits)
MessageID 8
3 4.7.4.2.2 XonResponse
4 The access network sends this message to acknowledge reception of the XonRequest
5 message.
6
Field Length (bits)
MessageID 8

8
9 4.7.4.2.3 XoffRequest
10 The access terminal sends this message to request transition to the Close State.
11
Field Length (bits)
MessageID 8
13
14 4.7.4.2.4 XoffResponse
15 The access network sends this message to acknowledge reception of the XoffRequest
16 message.
17
4-47
Field Length (bits)
MessageID 8

2
3 4.7.4.2.5 DataReady
4 The access network sends this message to indicate that there is data corresponding to this
5 packet application awaiting to be transmitted.
6
Field Length (bits)
MessageID 8
TransactionID 8
9 DataReady message sent.
10
11 4.7.4.2.6 DataReadyAck
12 The access terminal sends this message to acknowledge reception of a DataReady message.
13
Field Length (bits)
MessageID 8
TransactionID 8
14 MessageID The access terminal shall set this field to 0x0c.
15 TransactionID The access terminal shall set this value to the value of the
16 TransactionID field of the corresponding DataReady message.
17
4-48
2 4.7.5.1 Commands

7

TFCResponse terminal and access network are to 1 second
respond to flow control messages.
4-49
1 4.8 Configuration Attributes for the Multi-Flow Packet Application

2 The access terminal shall support default values of all attributes.
3 Unless specified otherwise, the access terminal and the access network shall not use the
4 Generic Attribute Update Protocol to update configurable attributes belonging to the Multi-
5 Flow Packet Application. The access terminal and the access network shall support the use
6 of the Generic Attribute Update Protocol to update values of the following configurable
7 attributes belonging to the Multi-Flow Packet Application:
8 • FlowNNTimersFwd,
9 • FlowNNTimersRev,
10 • FlowNNNakEnableFwd,
11 • FlowNNNakEnableRev,
12 • FlowNNPhysicalLayerNakEnableRev,
13 • FlowNNHigherLayerProtocolFwd,
14 • FlowNNHigherLayerProtocolRev,
15 • FlowNNIdentificationFwd,
16 • FlowNNIdentificationRev,
17 • FlowNNReservationFwd,
18 • FlowNNReservationRev,
19 • FlowNNTransmitAbortTimerRev,
20 • FlowNNDataOverSignalingAllowedRev,
21 • ReservationKKIdleStateFwd,
22 • ReservationKKIdleStateRev,
23 • ReservationKKQoSRequestFwd,
24 • ReservationKKQoSRequestRev,
25 • ReservationKKQoSResponseFwd,
26 • ReservationKKQoSResponseRev, and
27 • ANSupportedQoSProfiles
28 If the value of the ATNAKDelaySupported attribute is 0x01, then the access terminal and
29 the access network shall support the use of the Generic Attribute Update Protocol to
30 update values of the following attribute:
31 • FlowNNNakDelayTimeFwd
32 where NN is hexadecimal RLP flow number in the range 0x00 to M - 1 inclusive, where M is
33 MaxNumRLPFlowsFwd or MaxNumRLPFlowsRev for an RLP flow on the forward link or
34 reverse link respectively and KK is the two-digit hexadecimal ReservationLabel.
4-50
1 The updated values of the attributes shall be consistent with the value of the
2 MaxActivatedRLPFlowsFwd and MaxActivatedRLPFlowsRev attributes.
3 The access terminal shall not send an AttributeUpdateRequest message proposing to
4 update the value of the ANSupportedQoSProfiles attribute.
5 The number of Forward Link Reservations that satisfy at least one of the following
6 conditions shall not exceed the value of the
7 MaxNumReservationFwdMaxNumReservationsFwd attribute:
8 • The Reservation is in Open state.
9 • The Reservation is bound to a link flow.
10 • The ReservationKKQoSRequestFwd corresponding to the Reservation is set to a non-
11 default value.
12 The number of Reverse Link Reservations that satisfy at least one of the following
13 conditions shall not exceed the value of the MaxNumReservationsRev attribute:
14 • The Reservation is in Open state.

15 • The Reservation is bound to a link flow.
16 • The ReservationKKQoSRequestRev corresponding to the Reservation is set to a non-
17 default value.
18 4.8.1 Simple Attributes

19 The negotiable simple attribute for this protocol is listed in Table 4.8-1. The access
20 terminal and the access network shall use as defaults the values in Table 4.8-1 typed in
21 bold italics.
22
4-51
1 Table 4.8-1. Configurable Values

0x00 The access terminal shall not send an
unsolicited LocationNotification
message. The access network does not
switch between the radio access
technologies (e.g. specified in [3]) in a
manner that preserves the state of all
protocol layers at or above the data
link layer.
0x01 The access terminal shall send an
0xffff RANHandoff unsolicited LocationNotification
message (e.g. specified in [3]). The
access network switches between the
radio access technologies specified in
[3] in a manner that preserves the
state of all protocol layers at or above
the data link layer.
All Reserved
other
values
0x05 Maximum abort timer is 500 ms.
0x00 Maximum abort timer in units of 100

0x06 to ms.
0xfffc MaxAbortTimer 0x64
All Reserved
other
values
0xfeNN 0x00 Forward link Nak disabled.
FlowNNNakEnableFwd
NN is the two- 0x01 Forward link Nak enabled.
digit NN is the two-digit
hexadecimal hexadecimal RLP flow All Reserved.
RLP flow number in the range other
number of the 0x00 to values
forward RLP MaxNumRLPFlowsFwd -
flow in the 1 inclusive, where
range 0x00 to hexadecimal digits A
MaxNumRLPF through F are specified
lowsFwd -1 in upper case letters.
inclusive.
0xfdNN FlowNNNakEnableRev 0x00 Reverse link Nak disabled.
NN is the two- NN is the two-digit 0x01 Reverse link Nak enabled.
digit hexadecimal RLP flow
4-52

hexadecimal number in the range All Reserved.
RLP flow 0x00 to other
number of the MaxNumRLPFlowsRev -1 values
reverse RLP inclusive, where
flow in the hexadecimal digits A
range 0x00 to through F are specified
MaxNumRLPF in upper case letters.
lowsRev -1
inclusive.
FlowNNHigherLayerProto 0x01 The higher layer protocol is octet-
0xfcNN
colFwd based HDLC-like framing [17].
NN is the two-
NN is the two-digit All Defined in [10]
digit
hexadecimal RLP flow other
hexadecimal
number in the range values
RLP flow
0x00 to
number in the
MaxNumRLPFlowsFwd -
range 0x00 to
1 inclusive, where
MaxNumRLPF
hexadecimal digits A
lowsFwd -1
through F are specified
inclusive.
in upper case letters.
0xfbNN 0x01 The higher layer protocol is octet-
FlowNNHigherLayerProto
based HDLC-like framing [17].
NN is the two- colRev
digit All Defined in [10]
NN is the two-digit
hexadecimal other
hexadecimal RLP flow
RLP flow values
number in the range
number of the
0x00 to
reverse RLP
MaxNumRLPFlowsRev -1
flow in the
inclusive, where
range 0x00 to
MaxNumRLPF
lowsRev -1
inclusive.
0xfaNN 0x01 RLP is to retransmit octets when a
FlowNNPhysicalLayerNak
PhysicalLayer.ReverseTrafficPacketsMi
NN is the two- EnableRev
ssed indication is received.
digit
NN is the two-digit
hexadecimal 0x00 RLP is to ignore
hexadecimal RLP flow
RLP flow PhysicalLayer.ReverseTrafficPacketsMi
number in the range
number of the ssed indication.
0x00 to
reverse RLP
MaxNumRLPFlowsRev -1 All Reserved
flow in the
inclusive, where other
range 0x00 to
hexadecimal digits A values
MaxNumRLPF
lowsRev -1
inclusive.
0xf9KK 0x00 Reservation does not change states

ReservationKKIdleStateF
when a Connection is opened or
KK is the two- wd
closed.
4-53

digit KK is the two-digit 0x01 Reservation transitions to the Close
hexadecimal hexadecimal state when a Connection is closed
ReservationLa ReservationLabel in the unless an access network initiated
bel of the range 0x00 to 0xff Connection is being opened at the
forward inclusive, where same time.
Reservation in hexadecimal digits A
the range through F are specified 0x02 Reservation transitions to the Open
0x00 to 0xff in upper case letters. state when a Connection is opened
inclusive. and transitions to the Close state
when a Connection is closed unless an
access network initiated Connection is
being opened at the same time.
All Reserved
other
values
0x00 Reservation does not change states
when a Connection is opened or
closed.
0xf8KK 0x01 Reservation transitions to the Close
ReservationKKIdleStateR
state when a Connection is closed
KK is the two- ev
unless an access network initiated
digit
KK is the two-digit Connection is being opened at the
hexadecimal
hexadecimal same time.
ReservationLa
ReservationLabel in the
bel of the 0x02 Reservation transitions to the Open
range 0x00 to 0xff
reverse state when a Connection is opened
inclusive, where
Reservation in and transitions to the Close state
the range when a Connection is closed unless an
0x00 to 0xff access network initiated Connection is
inclusive. being opened at the same time.
All Reserved
other
values
0xf7NN 0x000 Maximum delay for transmission of a
FlowNNTransmitAbortTi 0 higher layer octet for RLP flow NN is
NN is the two- merRev not specified.
digit NN is the two-digit
hexadecimal hexadecimal RLP flow 0x0001 Maximum delay for transmission of a
RLP flow number in the range – higher layer octet for RLP flow NN in
number of the 0x00 to 0x03e8 units of 5 ms.
reverse RLP MaxNumRLPFlowsRev -1 All Reserved
flow in the inclusive, where other
range 0x00 to hexadecimal digits A values
MaxNumRLPF through F are specified
lowsRev -1 in upper case letters.
inclusive.
0xf6NN FlowNNDataOverSignalin 0x00 Access terminal is not allowed to send
NN is the two- gAllowedRev DataOverSignaling messages for this
digit NN is the two-digit RLP flow.
4-54

hexadecimal hexadecimal RLP flow 0x01 Access terminal is allowed to send
RLP flow number in the range DataOverSignaling messages for this
number of the 0x00 to RLP flow.
reverse RLP MaxNumRLPFlowsRev -1
flow in the inclusive, where All Reserved
range 0x00 to hexadecimal digits A other
MaxNumRLPF through F are specified values
lowsRev -1 in upper case letters.
inclusive.
0xe7NN 0x00 The values of the NAK Delay Time for
flow NN is zero.
NN is the two-
digit 0x01 – The values of the NAK Delay Time for
hexadecimal 0xff flow NN is specified by the value of
RLP flow this attribute in units of 10 ms.
number of the FlowNNNakDelayTimeFw
reverse RLP d
flow in the
range 0x00 to
MaxNumRLPF
lowsRevFwd -
1 inclusive.
0x00 The access terminal does not support
a non-zero value for the
FlowNNNakDelayTimeFwd.
0x01 The access terminal does support
0xfff9 ATNAKDelaySupported non-zero values for the
FlowNNNakDelayTimeFwd.
All Reserved
other
values
1 4.8.2 Complex Attributes

2 The following complex attributes and default values are defined (see 13.3 for attribute
3 record definition).
4 4.8.2.1 FlowNNIdentificationFwd Attribute

5 NN is the two-digit hexadecimal RLP flow number of the forward RLP flow in the range 0x00
6 to MaxNumRLPFlowsFwd -1 inclusive, where hexadecimal digits A through F are specified
7 in upper case letters.
8
4-55
Field Length (bits) Default
Length 8 N/A
AttributeID 16 N/A
One or more of the following attribute value record:
{
ValueID 8 N/A
See Table
Active 8
4.8.2.1-1.
Zero or one occurrence of the following four fields:
See Table
SequenceLength 8
4.8.2.1-1.
See Table
RLPIDLength 8
4.8.2.1-1.
See Table
RLPID RLPIDLength
4.8.2.1-1.
Reserved 0-7 (as needed) N/A
}
1 Length Length of the complex attribute in octets. The sender shall set this
2 field to the length of the complex attribute excluding the Length field.
3 AttributeID The sender shall set this field to 0x01NN, where NN is the two-digit
4 hexadecimal RLP flow number in the range 0x00 to
5 MaxNumRLPFlowsFwd -1 inclusive.
6 ValueID The sender shall set this field to an identifier assigned to this
7 complex value.
8 Active The sender shall set this field to 0x01 to activate RLP flow number
9 NN. The sender shall set this field to 0x00 de-activate RLP flow
10 number NN.
11 SequenceLength If Active is set to 0x01, the sender shall set this field to the size of the
12 sequence space in units of bits for this RLP flow. Otherwise, the
13 sender shall omit this field.
14 RLPIDLength If Active is set to 0x00, the sender shall omit this field. Otherwise, the
15 sender shall set this field to the length of the RLPID, in units of bits,
16 for this RLP flow.
17 If SequenceLength and RLPIDLength fields are included, then the sum of SequenceLength
18 and RLPIDLength shall be 22 or 14.
4-56
1 RLPID If Active is set to 0x00, the sender shall omit this field. Otherwise, the
2 sender shall set this field to an identifier for this RLP flow such that
3 the RLPIDs assigned to all activated forward RLP flows in the Multi-
4 Flow Packet Application are prefix-free.
5 Reserved The sender shall add reserved bits to make the length of the record
6 an integer number of octets. The sender shall set these bits to ‘0’. The
7 receiver shall ignore these bits.
8 Table 4.8.2.1-1 shows the default values of SequenceLength, RLPIDLength, and RLPID. The
9 access network or access terminal shall return a Failed indication if the attribute
10 negotiation fails for RLP flows RLP0x01 through RLP MaxNumRLPFlowsFwd -1.

12 FlowNNIdentificationFwd attribute
Default Default Default

RLP flow Default
Sequenc RLPIDLength
0xNN Active RLPID
eLength
0x00 0x01 21 1 ‘0’
0x01 through 0x00 N/A N/A
MaxNumRLP N/A
FlowsFwd -1
13 4.8.2.2 FlowNNIdentificationRev Attribute

14 NN is the two-digit hexadecimal RLP flow number of the reverse RLP flow in the range 0x00
15 to MaxNumRLPFlowsRev -1 inclusive, where hexadecimal digits A through F are specified
17
4-57
Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
Active 8 See Table 4.8.2.2-1.
Zero or one occurrence of the following four fields:
SequenceLength 8 See Table 4.8.2.2-1.
RLPIDLength 8 See Table 4.8.2.2-1.
RLPID RLPIDLength See Table 4.8.2.2-1.
}
5 MaxNumRLPFlowsRev -1 inclusive.
7 complex value.
8 Active The sender shall set this field to 0x01 to activate RLP flow number
9 NN. The sender shall set this field to 0x00 de-activate RLP flow
10 number NN.
11 SequenceLength If Active is set to 0x00, the sender shall omit this field. Otherwise,
12 Active the sender shall set this field to the size of the sequence space
13 in units of bits for this RLP flow.
14 RLPIDLength If Active is set to 0x00, the sender shall omit this field. Otherwise, the
15 sender shall set this field to the length of the RLPID, in units of bits,
16 for this RLP flow.
17 If SequenceLength and RLPIDLength fields are included, then the sum of SequenceLength
18 and RLPIDLength shall be 22 or 14.
19 RLPID If Active is set to 0x00, the sender shall omit this field. Otherwise, the
20 sender shall set this field to an identifier for this RLP flow such that
21 the RLPIDs assigned to all activated reverse RLP flows in the Multi-
22 Flow Packet Application are prefix-free.
4-58
1 Reserved The sender shall add reserved bits to make the length of the record
2 an integer number of octets. The sender shall set these bits to ‘0’. The
3 receiver shall ignore these bits.
4 Table 4.8.2.2-1 shows the default values of SequenceLength, RLPIDLength, and RLPID. The
5 access network or access terminal shall return a Failed indication if the attribute
6 negotiation fails for RLP flows RLP0x01 through RLP MaxNumRLPFlowsRev -1.

8 FlowNNIdentificationRev attribute
Default Default Default

RLP flow Default
Sequenc RLPIDLength
0xNN Active RLPID
eLength
0x00 0x01 21 1 ‘0’
0x01 through 0x00 N/A N/A
MaxNumRLP N/A
FlowsRev -1
9 4.8.2.3 FlowNNTimersFwd Attribute

13
Length 8 N/A
AttributeID 16 N/A
One or more of the following record:
ValueID 8 N/A
AbortTimer 16 0x01f4
FlushTimer 16 0x012c
20 complex value.
21 AbortTimer The sender shall set this field to the value of the RLP abort timer for
22 this forward RLP flow in units of ms. The sender shall not set this
23 field to a value greater than MaxAbortTimer.
4-59
1 FlushTimer The sender shall set this field to the value of the RLP flush timer for
2 this forward RLP flow in units of ms. The value of the RLP flush timer
3 shall be less than or equal to that of the corresponding abort timer.
4 4.8.2.4 FlowNNTimersRev Attribute

8
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
AbortTimer 16 0x01f4
FlushTimer 16 0x012c
15 complex value.
16 AbortTimer The sender shall set this field to the value of the RLP abort timer for
17 this reverse RLP flow in units of ms. The sender shall not set this
18 field to a value greater than MaxAbortTimer.
19 FlushTimer The sender shall set this field to the value of the RLP flush timer for
20 this reverse RLP flow in units of ms. The value of the RLP flush timer
21 shall be less than or equal to that of the corresponding abort timer.
22 4.8.2.5 FlowNNReservationFwd Attribute

26
4-60
Field Length (bits) Default for Default for

NN = 0x00 NN > 0x00
Length 8 N/A N/A

AttributeID 16 N/A N/A
ValueID 8 N/A N/A
ReservationCount 8 0x01 0x00
ReservationCount occurrence of the following field:
ReservationLabel 8 0xff N/A
7 complex value.
8 ReservationCount The sender shall set this field to the number of reservations
9 associated with this RLP flow.
10 ReservationLabel The sender shall set this field to the ReservationLabel of the
11 reservation associated with this RLP flow.
12 4.8.2.6 FlowNNReservationRev Attribute

16
4-61
Field Length (bits) Default for Default for

NN = 0x00 NN >= 0x00
Length 8 N/A N/A

ValueID 8 N/A N/A
ReservationCount 8 0x01 0x00
ReservationCount occurrence of the following field:
ReservationLabel 8 0xff N/A
7 complex value.
8 ReservationCount The sender shall set this field to the number of reservations
9 associated with this RLP flow.
10 ReservationLabel The sender shall set this field to the ReservationLabel of the
11 reservation associated with this RLP flow.
12 4.8.2.7 SupportedHigherLayerProtocols Attribute

13
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
ProtocolCount 8 0x01
ProtocolCount occurrence of the following field:
ProtocolIdentifier 8 0x01
16 AttributeID The sender shall set this field to 0x0000.
4-62
2 complex value.
3 ProtocolCount The sender shall set this field to the number of occurrences of the
4 ProtocolIdentifier field in this record.
5 ProtocolIdentifier The sender shall set this field to an identifier for the supported higher
6 layer protocol as defined in [10].
7 4.8.2.8 ATSupportedQoSProfiles Attribute

8
Length 8 N/A
AttributeID 16 N/A
One occurrence of the following record:
ValueID 8 N/A
QoSProfileCount 8 0
QoSProfileCount of the following record:
ProfileType 8 N/A
ProfileLength 8 N/A
ProfileValue ProfileLength × 8 N/A
13 complex value.
14 QoSProfileCount The sender shall set this field to the number of QoS Profiles that are
15 included in this message.
16 ProfileType The sender shall set this field to indicate the profile type. The sender
17 shall set this field according to [10].
18 ProfileLength The sender shall set this field to length of the ProfileValue field in
19 units of octets.
20 ProfileValue The sender shall set this field to the profile according to [10].
4-63
1 4.8.2.9 ANSupportedQoSProfiles Attribute

2
Length 8 N/A
AttributeID 16 N/A
One occurrence of the following record:
ValueID 8 N/A
QoSProfileCount 8 0
QoSProfileCount of the following record:
ProfileType 8 N/A
ProfileLength 8 N/A
7 complex value.
8 QoSProfileCount The sender shall set this field to the number of QoS Profiles that are
11 shall set this field according to [10].
13 units of octets.
14 ProfileValue The sender shall set this field to the profile according to [10].
15 4.8.2.10 MaxRLPFlows Attribute

16
4-64
Length 8 N/A
AttributeID 16 N/A
One or more occurrences of the following record:
ValueID 8 N/A
MaxNumRLPFlowsFwd 8 0x06
MaxNumRLPFlowsRev 8 0x06
MaxActivatedRLPFlowsFwd 8 0x03
MaxActivatedRLPFlowsRev 8 0x03
5 complex value.
6 MaxNumRLPFlowsFwd
7 The sender shall set this field to indicate the maximum total number
8 of activated and deactivated forward link RLP flows supported. The
9 value shall be in the range of 0x06 to 0x1f, inclusive
10 MaxNumRLPFlowsRev
11 The sender shall set this field to indicate the maximum total number
12 of activated and deactivated reverse link RLP flows supported. The
13 value shall be in the range of 0x06 to 0x1f, inclusive.
14 MaxActivatedRLPFlowsFwd
15 The sender shall set this field to indicate the maximum number of
16 simultaneous activated forward link RLP Flows supported. The value
17 shall be in the range of 0x03 to MaxNumRLPFlowsFwd, inclusive.
18 MaxActivatedRLPFlowsRev
20 simultaneous activated reverse link RLP Flows supported. The value
21 shall be in the range of 0x03 to MaxNumRLPFlowsRev, inclusive.
22 4.8.2.11 ReservationKKQoSRequestFwd Attribute

23 KK is the two-digit hexadecimal ReservationLabel, where hexadecimal digits A through F
24 are specified in upper case letters.
25
4-65
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
ProfileType 8 0x00
ProfileLength 16 0x0000
3 AttributeID The sender shall set this field to 0x07KK, where KK is the two-digit
6 complex value.
8 shall set this field as defined in [10].
10 units of octets. If ProfileType is equal to 0x00, then the sender shall
11 set this field to 0x0000.
12 ProfileValue The sender shall set this field to the Profile Value corresponding to
13 the Profile Type according to [10]. If ProfileType is equal to 0x00, then
14 the sender shall omit this field. If ProfileType is equal to 0x01, if the
15 ANSupportedQoSProfiles attribute does not have a default value, and
16 if this attribute is included in an AttributeUpdateRequest then the
17 requested Flow Profile IDs shall be a subset of the Flow Profile IDs in
18 the ProfileValue fields of ANSupportedQoSProfiles attribute.
19 4.8.2.12 ReservationKKQoSRequestRev Attribute

22
4-66
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
ProfileType 8 0x00
6 complex value.
14 the sender shall omit this field. If ProfileType is equal to 0x01, if the
15 ANSupportedQoSProfiles attribute does not have a default value, and
16 if this attribute is included in an AttributeUpdateRequest then the
17 requested Flow Profile IDs shall be a subset of the Flow Profile IDs in
18 the ProfileValue fields of ANSupportedQoSProfiles attribute.
19 4.8.2.13 ReservationKKQoSResponseFwd Attribute

22
4-67
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
ProfileType 8 0x00
6 complex value.
14 the sender shall omit this field.
15 4.8.2.14 ReservationKKQoSResponseRev Attribute

18
4-68
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
ProfileType 8 0x00
3 AttributeID The sender shall set this field to 0x0aKK, where KK is the two-digit
6 complex value.
14 the sender shall omit this field.
15 4.8.2.15 MaxReservations Attribute

16
4-69
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
MaxNumReservationsFwd 8 0xff
MaxNumReservationsRev 8 0xff
MaxNumOpenReservationsFwd 8 0x0f
MaxNumOpenReservationsRev 8 0x0f
5 complex value.
6 MaxNumReservationsFwd
7 The sender shall set this field to indicate one less than the maximum
8 total number of Forward Link Reservations supported that satisfy at
9 least one of the following conditions:
10 a. The Reservation is in Open state.
11 b. The Reservation is bound to a link flow.
12 c. The ReservationKKQoSRequestFwd corresponding to the
13 Reservation is set to a non-default value.
14 The value shall be in the range of 0x00 to 0xff, inclusive
15 MaxNumReservationsRev
17 total number of Reverse Link Reservations supported that satisfy at
18 least one of the following conditions:
19 a. The Reservation is in Open state.
20 b. The Reservation is bound to a link flow.
21 c. The ReservationKKQoSRequestRev corresponding to the
22 Reservation is set to a non-default value.
23 The value shall be in the range of 0x00 to 0xff, inclusive.
24 MaxNumOpenReservationsFwd
26 number of simultaneous Open Forward Link Reservations supported.
27 The value shall be in the range of 0x00 to MaxNumReservationsFwd,
28 inclusive.
4-70
1 MaxNumOpenReservationsRev
3 number of simultaneous Open Reverse Link Reservations supported.
4 The value shall be in the range of 0x00 to MaxNumReservationsRev,
5 inclusive.

8 This application defines the following parameter records in addition to the configuration
10 4.9.1 Location Parameter
11 Table 4.9.1-1. The Format of the Parameter Record for the Location Parameter
Field Length (bits)
ParameterType 8
Length 8
LocationType 8
LocationValue 8 × (Length – 2)
15 LocationType This field shall be set to the value of LocationType associated with
17 LocationValue This field shall be set to the stored value of LocationValue associated
18 with the access terminal’s session.
19 4.9.2 FlowControlState Parameter
21 Parameter
Field Length (bits)
ParameterType 8
Length 8
FlowControlState 8
4-71
3 FlowControlState This field shall be set to 0x00 if the state of the Flow Control Protocol
4 associated with the access terminal’s session is Close. Otherwise,
5 this field shall be set to 0x01. All the other values for this field are
6 reserved.
7 4.9.3 DataOverSignalingMessageSequence Parameter
8 Table 4.9.3-1. The Format of the Parameter Record for the

9 DataOverSignalingMessageSequence Parameter
Field Length (bits)
ParameterType 8
Length 8
Reserved1 2
ReceivePointer 6
Reserved2 2
TransmitPointer 6
14 field.
15 ReceivePointer This field shall be set to the value of the receive pointer for
16 DataOverSignaling message validation, V(R).
18 field.
19 TransmitPointer This field shall be set to the value of the transmit pointer for
20 DataOverSignaling message validation, V(S).
4-72
1 4.9.4 StorageBLOB Parameter
2 Table 4.9.4-1. The Format of the Parameter Record for the StorageBLOB Parameter
Field Length (bits)
ParameterType 8
Length 8
StorageBLOBLength 8
StorageBLOB 0 or 8 × StorageBLOBLength
6 StorageBLOBType This field shall be set to zero if the value of its stored StorageBLOB is
7 NULL; otherwise, this field shall be set to the stored value of
8 StorageBLOBType.
9 StorageBLOBLength
10 This field shall be set to zero if the value of its stored StorageBLOB is
12 StorageBLOBLength.
13 StorageBLOB This field shall be omitted if the value of the stored StorageBLOB is
15 StorageBLOB.
4-73
1 4.9.5 ReservationState Parameter
2 Table 4.9.5-1. The Format of the Parameter Record for the ReservationState
3 Parameter
Field Length (bits)
ParameterType 8
Length 8
OpenReservationCount 8
OpenReservationCount occurrences of the following record:
Link 1
ReservationLabel 8
7 OpenReservationCount
8 This field shall be set to the number of Reservations that are in the
9 Open state.
10 Link This field shall be set to ‘1’ for a forward Reservation, and to ‘0’ for a
11 reverse Reservation.
12 ReservationLabel This field shall be set to the ReservationLabel of the Open

13 Reservation.
14 Reserved The sender shall add reserved bits to make the length of the entire
15 parameter an integer number of octets. The sender shall set these
16 bits to zero. The receiver shall ignore this field.
4-74
3GPP2 C.S0024-B v2.0
1 53G1X CIRCUIT SERVICES NOTIFICATION APPLICATION
2 5.1Introduction
3 5.1.1General Overview
4 The 3G1X Circuit Services Notification Application provides the 3G1X Circuit Services
5 Notification Protocol to send notifications for cdma2000 1x circuit-switched services to the
6 access terminal through the cdma2000 high rate packet data air interface while the access
7 terminal is tuned to the cdma2000 high rate packet data channel. The access terminal and
8 the access network can use the 3G1X Circuit Services Notification Protocol to configure a
9 filtering mechanism that allows notifications associated with only certain circuit switched
10 services to be sent through the high rate packet data air interface. The 3G1X Circuit
11 Services Notification Protocol also ensures that the access terminal stays registered in the
12 cdma2000 1x core circuit network even when it is monitoring the high rate packet data
13 CDMA channel.
14 5.1.2Public Data
16 •Subtype for this application
17 5.2Data Encapsulation for the InUse Instance of the Application

18 The 3G1X Circuit Services Notification Protocol sends a cdma2000 1x LAC encapsulated
19 PDU as payload in a 3G1XServices message.
20 The 3G1X Circuit Services Notification Application uses the Signaling Application to
21 transmit and receive messages.
22 5.3Protocol Initialization
23 5.3.1Protocol Initialization for the InConfiguration Application Instance

26 •The fall-back values of the attributes for this application instance shall be set to the
28 •If the InUse instance of this application (i.e., corresponding to the stream or virtual stream
29 to which this application is bound) has the same protocol subtype as this
30 InConfiguration application instance, then the fall-back values of the attributes defined
31 by the InConfiguration application instance shall be set to the values of the
32 corresponding attributes values for the InUse application instance.
33 •The value for each attribute for this application instance shall be set to the fall-back value
35 •The value of the InConfiguration application instance public data shall be set to the value
36 of the corresponding InUse application instance public data.
4-1
3GPP2 C.S0024-B v2.0
1 •The value of the application subtype associated with the InConfiguration application
3 5.4Procedures and Messages for the InConfiguration Instance of the 3G1X Circuit
4 Services Notification Application
5 5.4.1Procedures
6 This application uses the Generic Configuration Protocol (see 14.7) to define the processing
7 of the configuration messages.
8 5.4.2Commit Procedures
12 •All the public data that are defined by this application, but are not defined by the InUse
14 •If the InUse instance of this application (corresponding to the virtual stream to which this
16 −the access terminal and the access network shall set the attribute values
19 −the access terminal and the access network shall purge the InConfiguration
21 •If the InUse instance of this application (corresponding to the virtual stream to which this
23 the access terminal and the access network shall perform the following:
24 −The initial state of the InConfiguration instance of the 3G1X Circuit Services
25 Notification Application at the access network shall be set to the Inactive State.
26 −The access network shall set OtherActiveHRPDServicesCount to zero.
27 −The InConfiguration instance of the 3G1X Circuit Services Notification Application
28 at the access terminal and the access network shall become the InUse
29 instance for the 3G1X Circuit Services Notification Application (corresponding
30 to the stream or virtual stream to which this application is bound).
31 •All the public data that are not defined by this application shall be removed from the list of
32 public data for the InUse application instance.
33 5.4.3Message Formats
34 5.4.3.1ConfigurationRequest
36
4-2
3GPP2 C.S0024-B v2.0
Field Length (bits)
MessageID 8
TransactionID 8
6 5.4.3.2ConfigurationResponse
8
Field Length (bits)
MessageID 8
TransactionID 8

17
4-3
3GPP2 C.S0024-B v2.0
1 5.53G1X Circuit Services Notification Protocol
2 5.5.1Overview
3 The 3G1X Circuit Services Notification Protocol is used to send notifications for cdma2000
4 1x circuit-switched services to the access terminal through the cdma2000 high rate packet
5 data air interface while the access terminal is tuned to the cdma2000 high rate packet data
6 channel. Using the 3G1X Circuit Services Notification Protocol, the access terminal and the
7 access network can configure a filtering mechanism that allows notifications associated
8 with only certain circuit switched services to be sent through the high rate packet data air
9 interface. The 3G1X Circuit Services Notification Protocol also ensures that the access
10 terminal stays registered in the cdma2000 1x core circuit network even when it is
11 monitoring the high rate packet data CDMA channel.
12 5.5.2Primitives
13 5.5.2.1Commands
14 This protocol defines the following commands:
15 •IncrementOtherServiceCount
16 •DecrementOtherServiceCount
17 5.5.2.2Return Indications
19 •3G1XParametersReceived
20 •3G1XParametersResetReceived
21 5.5.3Protocol Data Unit

22 The 3G1X Circuit Services Notification Protocol sends a cdma2000 1x Link Access Control
23 (LAC) encapsulated Protocol Data Unit (PDU) containing a cdma2000 1x Layer 3 message
24 as payload in a 3G1XServices message.
25 5.5.4Procedures and Messages for the InUse Instance of the Protocol
26 5.5.4.1Procedures
27 5.5.4.1.1General Requirements
28 The 3G1X Circuit Services Notification Protocol receives a cdma2000 1x LAC encapsulated
29 PDU containing a cdma2000 1x Layer 3 message for transmission from the higher layer
30 [16], and forms a 3G1XServices message. As defined in [16], a LAC encapsulated PDU is a
4-4
3GPP2 C.S0024-B v2.0
1 LAC PDU together with the associated length and the Cyclic Redundancy Check (CRC)
2 fields added by the Segmentation and Reassembly (SAR) sublayer of the cdma2000 1x LAC.
3 The higher layer shall set the ACK_REQ field of the encapsulated PDU to ‘0’. The higher
4 layer shall set the VALID_ACK field of the encapsulated PDU to ‘0’. If the payload from the
5 cdma2000 1x LAC layer is to be delivered reliably, then the sender shall set AckRequired
6 field of the 3G1XServices message to ‘1’. Otherwise, the sender shall set the AckRequired
7 field of the 3G1XServices message to ‘0’. Upon receiving a 3G1XServices message with
8 AckRequired field set to ‘1’, the receiver shall respond with a 3G1XServicesAck message. If
9 the sender does not receive a 3G1XServicesAck message within an implementation specific
10 time interval in response to the corresponding 3G1XServices message requiring an
11 acknowledgment, then the sender should retransmit the 3G1XServices message an
12 implementation specific number of times.
13 A 3G1XServices message shall have priority in the range 20 to 50, inclusive.
14 5.5.4.1.2Access Terminal Requirements

15 Unless specified otherwise, requirements for the transmission and processing of cdma2000
16 1x messages shall be as specified in [16], [3], [19].
17 5.5.4.1.2.1Transmission and Reception of LAC Encapsulated PDUs

18 The higher layer shall construct the LAC Encapsulated PDU as if for transmission on the
19 r-csch or the r-dsch logical channel as defined in [16]. The higher layer shall omit the Radio
20 Environment Report Fields (See [16] ) of the Utility Sublayer from the LAC Encapsulated
21 PDU sent to the Stream Layer. The LAC Encapsulated PDU shall contain only messages
22 with MessageIDs listed in the AllowedReverseLinkMessages attribute. If the LAC
23 Encapsulated PDU contains an Order message, then the Order message shall contain only
24 orders with (order codes, order qualification code) pairs listed in the OrderCodeReverse
25 attribute. If an order qualification code is not included along with an order code in the
26 OrderCodeReverse attribute, then the Order message may contain an order with any order
27 qualification code for that order code.
28 If the access terminal includes in a message AUTHR whose generation requires a random
29 challenge then the access terminal shall use the value of the RAND attribute as the 32-bit
30 random challenge used for AUTHR computation (See [16]).
31 If the access terminal performs cdma2000 1x distance-based registration while monitoring
32 the high rate packet data channel, then it shall use the Latitude and Longitude public data
33 of the Overhead Messages Protocol in place of BASE_LAT and BASE_LONG respectively.
34 The access terminal shall process received LAC Encapsulated PDUs as follows:
35 •If the LAC Encapsulated PDU contains a message with MessageID not listed in the
36 AllowedForwardLinkMessages attribute, then the access terminal shall silently discard
37 the LAC Encapsulated PDU.
4-5
3GPP2 C.S0024-B v2.0
1 •Otherwise if the LAC Encapsulated PDU contains an Order message with the (order code,
2 order qualification code) pair not listed in the OrderCodeForward attribute, then the
3 access terminal shall silently discard the LAC Encapsulated PDU. The absence of an
4 order qualification code along with an order code in the OrderCodeForward attribute
5 shall be interpreted as all possible (order code, order qualification code) pairs for that
6 order code have been listed in the OrderCodeForward attribute.
7 •Otherwise the access terminal shall pass the LAC Encapsulated PDU to the higher layer
8 [16].
9 5.5.4.1.2.2Processing a 3G1XParameters Message

10 Upon receiving a 3G1XParameters message, the access terminal shall send a
11 3G1XParametersAck message. If the 3G1XParametersSignature field of a received
12 3G1XParameters message is set to zero or is the same as the RouteUpdateTriggerCode
13 public data of the Overhead Messages Protocol, then the access terminal shall issue a
14 3G1XParametersReceived indication. Otherwise, the access terminal shall generate a
15 RouteUpdate.SendRouteUpdate command.
16 5.5.4.1.2.3Processing a 3G1XParametersReset Message

17 Upon reception of a 3G1XParametersReset message, the access terminal shall issue a
18 3G1XParametersResetReceived13 indication and shall respond with a
19 3G1XParametersResetAck message.
20 5.5.4.1.3Access Network Requirements

21 The 3G1X Circuit Services Notification Protocol at the access network can be in one of
22 three states:
23 •Inactive State
24 •Idle Tunnel State
25 •Connected State
26 In the Idle Tunnel State, the access network does not have a connection with the access
27 terminal and the access network is ready to send notifications for cdma2000 1x circuit-
28 switched services to the access terminal through the cdma2000 high rate packet data air
29 interface. In the Inactive State, the access network is not ready to send notifications for
30 cdma2000 1x circuit-switched services to the access terminal through the cdma2000 high
31 rate packet data air interface. In the Connected State, the access network has a connection
32 with the access terminal and the access network is ready to send notifications for
33 cdma2000 1x circuit-switched services to the access terminal through the cdma2000 high
34 rate packet data air interface.
35 Figure 5.5.4.1.3-1 provides an overview of the access network states and state transitions.
13 The access terminal can use this indication to clear all stored values of 3G1X circuit service fields
of the 3G1XParameters message.
4-6
3GPP2 C.S0024-B v2.0
Inactive State
IdleTunnelTime
Timer Expired IdleState.ConnectionOpened
OtherActiveHRPDServicesCount
changes from zero to one
Idle Tunnel Connected

IdleState.ConnectionOpened
State State
ConnectedState.ConnectionClosed or
ConnectedState.ConnectionLost
Initial State
1
2 Figure 5.5.4.1.3-1. 3G1X Circuit Services Notification Protocol State Diagram (Access
3 Network)
4 5.5.4.1.3.1State Independent Requirements

5 The access network shall maintain a count of other active HRPD services, called
6 OtherActiveHRPDServicesCount. If the 3G1X Circuit Services Notification Protocol receives
7 an IncrementOtherServiceCount command, the access network shall increment
8 OtherActiveHRPDServicesCount by one. If the 3G1X Circuit Services Notification Protocol
9 receives a DecrementOtherServiceCount command, the access network shall decrement
10 OtherActiveHRPDServicesCount by one.
11 The access network may send a 3G1XParameters message when the access network
12 determines that the access terminal’s cdma2000 1x circuit service parameters need to be
13 updated. The access network may re-send the 3G1XParameters message if it has not
14 received the corresponding 3G1XParametersAck message from the access terminal within
15 an implementation defined time interval after sending the 3G1XParameters message.
16 The access network may send a 3G1XParametersReset message14. The access network may
17 re-send the 3G1XParametersReset message if it has not received the corresponding
18 3G1XParametersResetAck message from the access terminal within an implementation
19 defined time interval after sending the 3G1XParametersReset message.
20 Unless specified otherwise, requirements for the transmission and processing of cdma2000
21 1x messages shall be as specified in [16], [3], [19].
22 The access network shall construct a LAC Encapsulated PDU as if for transmission on the
23 f-csch or the f-dsch logical channel as defined in [16]. The LAC Encapsulated PDU shall
24 contain only messages with MessageIDs listed in the AllowedForwardLinkMessages
25 attribute. If the LAC Encapsulated PDU contains an Order message, then the Order
14 The access network can use this message to indicate that the access terminal is to clear all stored
values of 3G1X circuit service fields of the 3G1XParameters message.
4-7
3GPP2 C.S0024-B v2.0
1 message shall contain only orders with (order codes, order qualification code) pairs listed in
2 the OrderCodeForward attribute. If an order qualification code is not included along with
3 an order code in the OrderCodeForward attribute, then the Order message may contain an
4 order with any order qualification code for that order code.
5 If the higher layer sends a LAC Encapsulated PDU containing an Order Message, then the
6 Order Message shall contain orders for one mobile station.
7 If the higher layer sends a LAC Encapsulated PDU containing a General Page Message, the
8 General Page Message shall contain one mobile-station-addressed page. The General Page
9 Message shall not contain a broadcast page or an enhanced broadcast page. The higher
10 layer shall set the CLASS_0_DONE field of the General Page Message to ‘1’. The higher layer
11 shall set the CLASS_1_DONE field of the General Page Message to ‘1’. The higher layer shall
12 set the TMSI_DONE field of the General Page Message to ‘1’. The higher layer shall set the
13 ORDERED_TMSIS field of the General Page Message to ‘1’. The higher layer shall set the
14 BROADCAST_DONE field of the General Page Message to ‘1’.
15 The access network shall process received LAC Encapsulated PDUs as follows:
16 •If the LAC Encapsulated PDU contains a message with MessageID not listed in the
17 AllowedReverseLinkMessages attribute, then the access network shall silently discard
18 the LAC Encapsulated PDU.
19 •Otherwise if the LAC Encapsulated PDU contains an Order message with the (order code,
20 order qualification code) pair not listed in the OrderCodeReverse attribute, then the
21 access network shall silently discard the LAC Encapsulated PDU. The absence of an
22 order qualification code along with an order code in the OrderCodeReverseattribute
23 shall be interpreted as all possible (order code, order qualification code) pairs for that
24 order code have been listed in the OrderCodeReverse attribute.
25 •Otherwise the access network shall pass the LAC Encapsulated PDU to the higher layer
26 [16].
27 5.5.4.1.3.2Inactive State Requirements

28 If the 3G1X Circuit Services Notification Protocol receives an IdleState.ConnectionOpened
29 indication, the access network shall transition to the Connected State.
30 The 3G1X Circuit Services Notification Protocol shall transition to the Idle Tunnel State
31 when the value of OtherActiveHRPDServicesCount changes from zero to one.
32 The access network shall not send cdma2000 1x LAC Encapsulated PDUs to the access
33 terminal over the high rate packet data air interface.
34 5.5.4.1.3.3Idle Tunnel State Requirements

35 If the 3G1X Circuit Services Notification Protocol receives an IdleState.ConnectionOpened
36 indication, the access network shall transition to the Connected State.
37 The access network shall maintain a count-down timer, IdleTunnelTime, whenever the
38 3G1X Circuit Services Notification Protocol is in the Idle Tunnel state. The access network
39 shall reset the count-down timer to MaxIdleTunnelTime when the protocol enters the Idle
4-8
3GPP2 C.S0024-B v2.0
1 Tunnel state. The access network shall stop the IdleTunnelTime count-down timer
2 whenever OtherActiveHRPDServicesCount is greater than zero. The access network shall
3 start the IdleTunnelTime count-down timer whenever the value of
4 OtherActiveHRPDServicesCount changes from one to zero. The access network shall
5 consider the IdleTunnelTime timer to be expired when the timer reaches zero.
6 The access network shall transition to the Inactive state when the IdleTunnelTime timer
7 expires.
8 The access network shall not transmit a LAC Encapsulated PDU containing a General Page
9 Message unless all of the following conditions are met:
10 •MessageID of the General Page Message is listed in the AllowedForwardLinkMessages
11 attribute, and
12 •the service option of the page is included in the ServiceOptionIdle complex attribute.
13 The access network shall not transmit a LAC Encapsulated PDU containing a Data Burst
14 Message (See [3]) unless all of the following conditions are met:
15 •Message ID of the Data Burst Message is listed in the AllowedForwardLinkMessages
16 attribute, and
17 •one of the following conditions is met:
18 −the Data Burst Message is addressed to the access terminal, and the burst type of
19 the Data Burst Message is included in the BurstTypeIdle complex attribute, or
20 −the Data Burst Message is addressed to a broadcast address, and the (burst type,
21 broadcast address) pair of the Data Burst Message is included in the
22 BurstTypeIdle complex attribute.
23 5.5.4.1.3.4Connected State Requirements

24 If the 3G1X Circuit Services Notification Protocol receives a RouteUpdate.ConnectionLost or
25 a ConnectedState.ConnectionClosed indication, then the access network shall transition to
26 the Idle Tunnel State.
27 The access network shall not transmit a LAC Encapsulated PDU containing a General Page
28 Message unless all of the following conditions are met:
29 •MessageID of the General Page Message is listed in the AllowedForwardLinkMessages
30 attribute, and
31 •the service option of the page is included in the ServiceOptionConnected complex
32 attribute.
33 The access network shall not transmit a LAC Encapsulated PDU containing a Data Burst
34 Message (See [3]) unless all of the following conditions are met:
35 •Message ID of the Data Burst Message is listed in the AllowedForwardLinkMessages
36 attribute, and
37 •one of the following conditions is met:
4-9
3GPP2 C.S0024-B v2.0
1 −the Data Burst Message is addressed to the access terminal, and the burst type of
2 the Data Burst Message is included in the BurstTypeConnected complex
3 attribute, or
4 −the Data Burst Message is addressed to a broadcast address, and the (burst type,
5 broadcast address) pair of the Data Burst Message is included in the
6 BurstTypeConnected complex attribute.
7 5.5.4.1.3.4.1Processing of a 1x Service Redirection Message

8 If the access terminal receives a 1x Service Redirection Message via this protocol, the access
9 terminal shall use the most recently received cdma2000 1x overhead parameter values
10 (whether received from a 3G1XParameters message or from cdma2000 1x overhead
11 channels) and the RAND attribute value to create a 1x LAC Encapsulated PDU per section
12 5.5.4.1.1 containing a cdma2000 1x Origination Message formatted according to [3], and
13 shall send the LAC Encapsulated PDU if cdma2000 1x Origination Message is configured as
14 one of the messages permitted to be sent by this protocol as specified by the
15 AllowedReverseLinkMessages attribute.
16 5.5.4.1.3.4.2Processing of a 1x (MEID) Universal Handoff Direction Message

17 If the AT receives a 1x Universal Handoff Direction Message or 1x MEID Universal Handoff
18 Direction Message via this protocol, the access terminal shall follow the procedures of [3]
19 with the following exceptions:
20 •If the access terminal is incapable of supporting the service option specified in the 1x
21 (MEID) Universal Handoff Direction Message and if the Release Order is configured
22 as one of the messages permitted to be sent by this protocol as specified by the
23 AllowedReverseLinkMessages attribute, then the AT shall create a 1x LAC
24 Encapsulated PDU per section 5.5.4.1.1 containing a 1x Release Order formatted
25 according to [3], and shall send the LAC PDU to the access network per the
26 procedures of this protocol. The access terminal shall cease further processing of
27 the 1x [MEID] Universal Handoff Direction Message.
28 •The access terminal shall set the initial transmission power on the 1x radio network
29 according to the procedures specified in section 2.1.2.3.1.4 of [2]15 with the
30 following parameters:
31 −ACC_CORRECTIONS set to NOM_PWRs – 16 × NOM_PWR_EXTs.
32 −RLGAIN_ADJs set to zero
33 5.5.4.1.3.4.3Transmission of a 1x Service Redirection Message

34 If the access network sends a 1x LAC Encapsulated PDU containing a 1x Service
35 Redirection Message, then the access network shall set the fields of the 1x Service
36 Redirection Message as indicated below:
15 This procedure for setting the initial transmission power on the 1x radio network is to be used
regardless of the 1x traffic channel Radio Configuration (i.e. RC) value assigned in the (M)UHDM.
4-10
3GPP2 C.S0024-B v2.0
1 •RETURN_IF_FAIL field shall be set to ‘0’.

2 •DELETE_TMSI field shall be set to ‘0’.
3 •REDIRECT_TYPE field shall be set to ‘0’.
4 •RECORD_TYPE field shall be set to ‘0000 0010’. (Redirect to CDMA.)
5 •NUM_CHANS field in the Type specific fields to ‘0000’.
6 5.5.4.1.3.4.4Transmission of a 1x (MEID) Universal Handoff Direction Message

7 If the access network sends a 1x LAC Encapsulated PDU containing a 1x (MEID) Universal
8 Handoff Direction Message, then the access network shall set the fields of the 1x (MEID)
9 Universal Handoff Direction Message as indicated below:
10 •RETURN_IF_HANDOFF_FAIL field shall be set to ‘0’.
11 •The SCR_INCLUDED field shall be included and set to ‘1’.
12 •The NNSCR_INCLUDED field shall be included and set to ‘1’.
13 5.5.4.2Message Formats
14 5.5.4.2.13G1XServices
15 The access terminal or the access network sends a 3G1XServices message to send a
16 cdma2000 1x LAC Encacpsulated PDU.
Field Length (bits)
MessageID 8
AckRequired 1
MessageSequence 6
3G1XLogicalChannel 1
ProtocolRevision 8
PDULength 16
PDU PDULength × 8
18 AckRequired The sender shall set this field to ‘1’ if the receiver is required to
19 acknowledge the receipt of this message. Otherwise, the sender shall
21 MessageSequence If AckRequired is ‘1’, then the sender shall set this field to one more
22 (modulo 64) than the MessageSequence field of the last 3G1XServices
23 message requiring acknowledgement sent by the sender. Otherwise,
24 the sender shall set this field to zero.
4-11
3GPP2 C.S0024-B v2.0
1 3G1XLogicalChannel If the PDU field of this message is constructed as if for transmission

2 on the f-csch or the r-csch logical channel, then the sender shall set
3 this field to ‘0’. If the PDU field of this message is constructed as if for
4 transmission on the f-dsch or the r-dsch logical channel, then the
5 sender shall set this field to ‘1’.
6 ProtocolRevision The access terminal shall set this field to P_REV_IN_USE as defined
7 in [3]. If 3G1XLogicalChannel is set to ‘0’, then the access network
8 shall set this field to P_REV of the cdma2000 1x base station as
9 defined in [3]. Otherwise, the access network shall set this field to
10 P_REV_IN_USE as defined in [3].
11 PDULength The sender shall set this field to the length, in units of octets, of the
12 cdma2000 1x LAC encapsulated PDU carried in this 3G1XServices
13 message.
14 PDU The sender shall set this field to the cdma2000 1x LAC Encapsulated
15 PDU.
16
Channels FTC CC RTC AC SLP Best Effort
17 5.5.4.2.23G1XServicesAck
18 The access terminal or the access network sends a 3G1XServicesAck message to
19 acknowledge the receipt of a 3G1XServices message.
20
Field Length (bits)

MessageID 8
AckSequence 6
Reserved 2
22 AckSequence The sender shall set this field to the MessageSequence field of the
23 3G1XServices message whose receipt is being acknowledged.
25 field.
26
4-12
3GPP2 C.S0024-B v2.0
1 5.5.4.2.33G1XParameters
2 The access network sends a 3G1XParameters message to provide values of parameters
3 associated with the cdma2000 1x circuit service to the access terminal. cdma2000 1x
4 circuit service parameters of the message are marked with a “†” sign in the last column.
5
4-13
3GPP2 C.S0024-B v2.0
Field Length (bits) cdma2000 1x

circuit service
field
MessageID 8
TransactionID 8
3G1XParametersSignature 12
SIDIncluded 1
SID 0 or 15 †
NIDIncluded 1
NID 0 or 16 †
REG_ZONEIncluded 1
REG_ZONE 0 or 12 †
TOTAL_ZONESIncluded 1
TOTAL_ZONES 0 or 3 †
ZONE_TIMERIncluded 1
ZONE_TIMER 0 or 3 †
PACKET_ZONE_IDIncluded 1
PACKET_ZONE_ID 0 or 8 †
PZIDHystParametersIncluded 1
PZ_HYST_ENABLED 0 or 1 †
PZ_HYST_INFO_INCL 0 or 1 †
PZ_HYST_LIST_LEN 0 or 1 †
PZ_HYST_ACT_TIMER 0 or 8 †
PZ_HYST_TIMER_MUL 0 or 3 †
PZ_HYST_TIMER_EXP 0 or 5 †
P_REVIncluded 1
P_REV 0 or 8 †
NEG_SLOT_CYCLE_INDEX_SUPInclu
1
ded
NEG_SLOT_CYCLE_INDEX_SUP 0 or 1 †
ENCRYPT_MODEIncluded 1
ENCRYPT_MODE 0 or 2 †
ENC_SUPPORTEDIncluded 1
ENC_SUPPORTED 0 or 1 †
SIG_ENCRYPT_SUPIncluded 1
SIG_ENCRYPT_SUP 0 or 8 †
4-14
3GPP2 C.S0024-B v2.0

circuit service
field
MSG_INTEGRITY_SUPIncluded 1
MSG_INTEGRITY_SUP 0 or 1 †
SIG_INTEGRITY_SUP_INCLIncluded 1
SIG_INTEGRITY_SUP_INCL 0 or 1 †
SIG_INTEGRITY_SUPIncluded 1
SIG_INTEGRITY_SUP 0 or 8 †
AUTHIncluded 1
AUTH 0 or 2 †
MAX_NUM_ALT_SOIncluded 1
MAX_NUM_ALT_SO 0 or 3 †
USE_SYNC_IDIncluded 1
USE_SYNC_ID 0 or 1 †
MS_INIT_POS_LOC_SUP_INDInclude
1
d
MS_INIT_POS_LOC_SUP_IND 0 or 1 †
MOB_QOSIncluded 1
MOB_QOS 0 or 1 †
BAND_CLASS_INFO_REQIncluded 1
BAND_CLASS_INFO_REQ 0 or 1 †
ALT_BAND_CLASSIncluded 1
ALT_BAND_CLASS 0 or 5 †
MAX_ADD_SERV_INSTANCEIncluded 1
MAX_ADD_SERV_INSTANCE 0 or 3 †
HOME_REGIncluded 1
HOME_REG 0 or 1 †
FOR_SID_REGIncluded 1
FOR_SID_REG 0 or 1 †
FOR_NID_REGIncluded 1
FOR_NID_REG 0 or 1 †
POWER_UP_REGIncluded 1
POWER_UP_REG 0 or 1 †
POWER_DOWN_REGIncluded 1
POWER_DOWN_REG 0 or 1 †
4-15
3GPP2 C.S0024-B v2.0

circuit service
field
PARAMETER_REGIncluded 1
PARAMETER_REG 0 or 1 †
REG_PRDIncluded 1
REG_PRD 0 or 7 †
REG_DISTIncluded 1
REG_DIST 0 or 11 †
PREF_MSID_TYPEIncluded 1
PREF_MSID_TYPE 0 or 2 †
EXT_PREF_MSID_TYPEIncluded 1
EXT_PREF_MSID_TYPE 0 or 2 †
MEID_REQDIncluded 1
MEID_REQD 0 or 1 †
MCCIncluded 1
MCC 0 or 10 †
IMSI_11_12Included 1
IMSI_11_12 0 or 7 †
IMSI_T_SUPPORTEDIncluded 1
IMSI_T_SUPPORTED 0 or 1 †
RECONNECT_MSG_INDIncluded 1
RECONNECT_MSG_IND 0 or 1 †
RER_MODE_SUPPORTEDIncluded 1
RER_MODE_SUPPORTED 0 or 1 †
TKZ_MODE_SUPPORTEDIncluded 1
TKZ_MODE_SUPPORTED 0 or 1 †
TKZ_IDIncluded 1
TKZ_ID 0 or 11 †
PILOT_REPORTIncluded 1
PILOT_REPORT 0 or 1 †
SDB_SUPPORTEDIncluded 1
SDB_SUPPORTED 0 or 1 †
AUTO_FCSO_ALLOWEDIncluded 1
AUTO_FCSO_ALLOWED 0 or 1 †
4-16
3GPP2 C.S0024-B v2.0

circuit service
field
SDB_IN_RCNM_INDIncluded 1
SDB_IN_RCNM_IND 0 or 1 †
FPC_FCH_Included 1
FPC_FCH_INIT_SETPT 0 or 8 †
T_ADD_Included 1
T_ADD 0 or 6 †
Reserved 0-7 (as needed)
2 TransactionID The access network shall increment this value modulo 256 for each
3 new 3G1XParameters message sent. If this is the first
4 3G1XParameters message sent by the access network, then the
5 access network shall set this field to zero.
6 3G1XParametersSignature
7 The access network shall set this field to the
8 RouteUpdateTriggerCode public data of the Overhead Messages
9 Protocol or to zero. If the Overhead Message Protocol does not provide
10 RouteUpdateTriggerCode public data, then the access network shall
11 set this field to zero.
12 SIDIncluded If SID is included in this message, then the access network shall set
13 this field to ‘1’. Otherwise, the access network shall set this field to
14 ‘0’.
15 SID If SIDIncluded is ‘0’, then the access network shall omit this field.
16 Otherwise, the access network shall set this field according to the
17 definition of the SID field as defined in [3].
18 NIDIncluded If NID is included in this message, then the access network shall set
20 ‘0’.
21 NID If NIDIncluded is ‘0’, then the access network shall omit this field.
23 definition of the NID field as defined in [3].
24 REG_ZONEIncluded
25 If REG_ZONE is included in this message, then the access network
26 shall set this field to ‘1’. Otherwise, the access network shall set this
4-17
3GPP2 C.S0024-B v2.0
1 REG_ZONE If REG_ZONEIncluded is ‘0’, the access network shall omit this field.
3 definition of the REG_ZONE field as defined in [3].
4 TOTAL_ZONESIncluded
5 If TOTAL_ZONES is included in this message, then the access
6 network shall set this field to ‘1’. Otherwise, the access network shall
8 TOTAL_ZONES If TOTAL_ZONESIncluded is ‘0’, then the access network shall omit

9 this field. Otherwise, the access network shall set this field according
10 to the definition of the TOTAL_ZONES field as defined in [3].
11 ZONE_TIMERIncluded
12 If ZONE_TIMER is included in this message, then the access network
15 ZONE_TIMER If ZONE_TIMERIncluded is ‘0’, then the access network shall omit

17 to the definition of the ZONE_TIMER field as defined in [3].
18 PACKET_ZONE_IDIncluded
19 If PACKET_ZONE_ID is included in this message, then the access
22 PACKET_ZONE_ID If PACKET_ZONE_IDIncluded is ‘0’, then the access network shall

23 omit this field. Otherwise, the access network shall set this field
24 according to the definition of the PACKET_ZONE_ID field of Extended
25 System Parameters Message [3].
26 PZIDHystParametersIncluded
27 If packet zone hysteresis parameters are included in this message,
28 then the access network shall set this field to ‘1’. Otherwise, the
29 access network shall set this field to ‘0’.
30 PZ_HYST_ENABLED If PZIDHystParametersIncluded is ‘0’, or if PACKET_ZONE_ID is

31 ‘00000000’, then the access network shall omit this field. Otherwise,
32 the access network shall set this field according to the definition of
33 the PZ_HYST_ENABLED field as defined in [3].
34 PZ_HYST_INFO_INCL
35 The access network shall set this field according to the definition of
36 the PZ_HYST_INFO_INCL field as defined in [3].
4-18
3GPP2 C.S0024-B v2.0
1 PZ_HYST_LIST_LEN The access network shall set this field according to the definition of
2 the PZ_HYST_LIST_LEN field as defined in [3].
3 PZ_HYST_ACT_TIMER
5 the PZ_HYST_ACT_TIMER field as defined in [3].
6 PZ_HYST_TIMER_MUL
8 the PZ_HYST_TIMER_MUL field as defined in [3].
9 PZ_HYST_TIMER_EXP
11 the PZ_HYST_TIMER_EXP field as defined in [3].
12 PREVIncluded If PREV is included in this message, then the access network shall
13 set this field to ‘1’. Otherwise, the access network shall set this field
14 to ‘0’.
15 PREV If PREVIncluded is ‘0’, the access network shall omit this field.
17 definition of the PREV field as defined in [3].
18 NEG_SLOT_CYCLI_INDEX_SUPIncluded
19 If NEG_SLOT_CYCLI_INDEX_SUP is included in this message, then
20 the access network shall set this field to ‘1’. Otherwise, the access
21 network shall set this field to ‘0’.
22 NEG_SLOT_CYCLI_INDEX_SUP
23 If NEG_SLOT_CYCLI_INDEX_SUPIncluded is ‘0’, the access network
24 shall omit this field. Otherwise, the access network shall set this field
25 according to the definition of the NEG_SLOT_CYCLI_INDEX_SUP field
26 as defined in [3].
27 ENCRYPT_MODEIncluded
28 If ENCRYPT_MODE is included in this message, then the access
31 ENCRYPT_MODE If ENCRYPT_MODEIncluded is ‘0’, the access network shall omit this

32 field. Otherwise, the access network shall set this field according to
33 the definition of the ENCRYPT_MODE field as defined in [3].
34 ENC_SUPPORTEDIncluded
35 If ENC_SUPPORTED is included in this message, then the access
4-19
3GPP2 C.S0024-B v2.0
1 ENC_SUPPORTED If ENC_SUPPORTEDIncluded is ‘0’, the access network shall omit

3 to the definition of the ENC_SUPPORTED field as defined in [3].
4 SIG_ENCRYPT_SUPIncluded
5 If SIG_ENCRYPT_SUP is included in this message, then the access
8 SIG_ENCRYPT_SUP If SIG_ENCRYPT_SUPIncluded is ‘0’, the access network shall omit

10 to the definition of the SIG_ENCRYPT_SUP field as defined in [3].
11 MSG_INTEGRITY_SUPIncluded
12 If MSG_INTEGRITY_SUP is included in this message, then the access
15 MSG_INTEGRITY_SUP
16 If MSG_INTEGRITY_SUPIncluded is ‘0’, the access network shall
18 according to the definition of the MSG_INTEGRITY_SUP field as
19 defined in [3].
20 SIG_INTEGRITY_SUP_INCLIncluded
21 If SIG_INTEGRITY_SUP_INCL is included in this message, then the
22 access network shall set this field to ‘1’. Otherwise, the access
24 SIG_INTEGRITY_SUP_INCL
25 If SIG_INTEGRITY_SUP_INCLIncluded is ‘0’, the access network
27 according to the definition of the SIG_INTEGRITY_SUP_INCL field as
28 defined in [3].
29 SIG_INTEGRITY_SUPIncluded
30 If SIG_INTEGRITY_SUP is included in this message, then the access
33 SIG_INTEGRITY_SUP
34 If SIG_INTEGRITY_SUPIncluded is ‘0’, the access network shall omit
36 to the definition of the SIG_INTEGRITY_SUP field as defined in [3].
4-20
3GPP2 C.S0024-B v2.0
1 AUTHIncluded If AUTH is included in this message, then the access network shall
3 to ‘0’.
4 AUTH If AUTHIncluded is ‘0’, the access network shall omit this field.
6 definition of the AUTH field as defined in [3].
7 MAX_NUM_ALT_SOIncluded
8 If MAX_NUM_ALT_SO is included in this message, then the access
11 MAX_NUM_ALT_SO If MAX_NUM_ALT_SOIncluded is ‘0’, the access network shall omit

13 to the definition of the MAX_NUM_ALT_SO field as defined in [3].
14 USE_SYNC_IDIncluded
15 If USE_SYNC_ID is included in this message, then the access
18 USE_SYNC_ID If USE_SYNC_IDIncluded is ‘0’, the access network shall omit this

20 the definition of the USE_SYNC_ID field as defined in [3].
21 MS_INIT_POS_LOC_SUP_INDIncluded
22 If MS_INIT_POS_LOC_SUP_IND is included in this message, then the
25 MS_INIT_POS_LOC_SUP_IND
26 If MS_INIT_POS_LOC_SUP_INDIncluded is ‘0’, the access network
28 according to the definition of the MS_INIT_POS_LOC_SUP_IND field
30 MOB_QOSIncluded If MOB_QOS is included in this message, then the access network

33 MOB_QOS If MOB_QOSIncluded is ‘0’, the access network shall omit this field.
35 definition of the MOB_QOS field as defined in [3].
36 BAND_CLASS_INFO_REQIncluded
37 If BAND_CLASS_INFO_REQ is included in this message, then the
4-21
3GPP2 C.S0024-B v2.0
3 BAND_CLASS_INFO_REQ
4 If BAND_CLASS_INFO_REQIncluded is ‘0’, the access network shall
6 according to the definition of the BAND_CLASS_INFO_REQ field as
7 defined in [3].
8 ALT_BAND_CLASSIncluded
9 If ALT_BAND_CLASS is included in this message, then the access
12 ALT_BAND_CLASS If ALT_BAND_CLASSIncluded is ‘0’, the access network shall omit

14 to the definition of the ALT_BAND_CLASS field as defined in [3].
15 MAX_ADD_SERV_INSTANCEIncluded
16 If MAX_ADD_SERV_INSTANCE is included in this message, then the
19 MAX_ADD_SERV_INSTANCE
20 If MAX_ADD_SERV_INSTANCEIncluded is ‘0’, the access network
22 according to the definition of the MAX_ADD_SERV_INSTANCE field
24 HOME_REGIncluded If HOME_REG is included in this message, then the access network

27 HOME_REG If HOME_REGIncluded is ‘0’, the access network shall omit this field.
29 definition of the HOME_REG field as defined in [3].
30 FOR_SID_REGIncluded
31 If FOR_SID_REG is included in this message, then the access
34 FOR_SID_REG If FOR_SID_REGIncluded is ‘0’, the access network shall omit this

36 the definition of the FOR_SID_REG field as defined in [3].
4-22
3GPP2 C.S0024-B v2.0
1 FOR_NID_REGIncluded
2 If FOR_NID_REG is included in this message, then the access
5 FOR_NID_REG If FOR_NID_REGIncluded is ‘0’, the access network shall omit this

7 the definition of the FOR_NID_REG field as defined in [3].
8 POWER_UP_REGIncluded
9 If POWER_UP_REG is included in this message, then the access
12 POWER_UP_REG If POWER_UP_REGIncluded is ‘0’, the access network shall omit this

14 the definition of the POWER_UP_REG field as defined in [3].
15 POWER_DOWN_REGIncluded
16 If POWER_DOWN_REG is included in this message, then the access
19 POWER_DOWN_REG
20 If POWER_DOWN_REGIncluded is ‘0’, the access network shall omit
22 to the definition of the POWER_DOWN_REG field as defined in [3].
23 PARAMETER_REGIncluded
24 If PARAMETER_REG is included in this message, then the access
27 PARAMETER_REG If PARAMETER_REGIncluded is ‘0’, the access network shall omit

29 to the definition of the PARAMETER_REG field as defined in [3].
30 REG_PRDIncluded If REG_PRD is included in this message, then the access network

33 REG_PRD If REG_PRDIncluded is ‘0’, the access network shall omit this field.
35 definition of the REG_PRD field as defined in [3].
4-23
3GPP2 C.S0024-B v2.0
1 REG_DISTIncluded If REG_DIST is included in this message, then the access network

3 field to ‘0’.
4 REG_DIST If REG_DISTIncluded is ‘0’, the access network shall omit this field.
6 definition of the REG_DIST field as defined in [3].
7 PREF_MSID_TYPEIncluded
8 If PREF_MSID_TYPE is included in this message, then the access
11 PREF_MSID_TYPE If PREF_MSID_TYPEIncluded is ‘0’, the access network shall omit

13 to the definition of the PREF_MSID_TYPE field as defined in [3].
14 EXT_PREF_MSID_TYPEIncluded
15 If EXT_PREF_MSID_TYPE is included in this message, then the
18 EXT_PREF_MSID_TYPE
19 If EXT_PREF_MSID_TYPEIncluded is ‘0’, the access network shall
21 according to the definition of the EXT_PREF_MSID_TYPE field as
22 defined in [3].
23 MEID_REQDIncluded
24 If MEID_REQD is included in this message, then the access network
27 MEID_REQD If MEID_REQDIncluded is ‘0’, the access network shall omit this

29 the definition of the MEID_REQD field as defined in [3].
30 MCCIncluded If MCC is included in this message, then the access network shall set
32 ‘0’.
33 MCC If MCCIncluded is ‘0’, the access network shall omit this field.
35 definition of the MCC field as defined in [3].
4-24
3GPP2 C.S0024-B v2.0
1 IMSI_11_12Included If IMSI_11_12 is included in this message, then the access network

3 field to ‘0’.
4 IMSI_11_12 If IMSI_11_12Included is ‘0’, the access network shall omit this field.
6 definition of the IMSI_11_12 field as defined in [3].
7 IMSI_T_SUPPORTEDIncluded
8 If IMSI_T_SUPPORTED is included in this message, then the access
11 IMSI_T_SUPPORTED If IMSI_T_SUPPORTEDIncluded is ‘0’, the access network shall omit

13 to the definition of the IMSI_T_SUPPORTED field as defined in [3].
14 RECONNECT_MSG_INDIncluded
15 If RECONNECT_MSG_IND is included in this message, then the
18 RECONNECT_MSG_IND
19 If RECONNECT_MSG_INDIncluded is ‘0’, the access network shall
21 according to the definition of the RECONNECT_MSG_IND field as
22 defined in [3].
23 RER_MODE_SUPPORTEDIncluded
24 If RER_MODE_SUPPORTED is included in this message, then the
27 RER_MODE_SUPPORTED
28 If RER_MODE_SUPPORTEDIncluded is ‘0’, the access network shall
30 according to the definition of the RER_MODE_SUPPORTED field as
31 defined in [3].
32 TKZ_MODE_SUPPORTEDIncluded
33 If TKZ_MODE_SUPPORTED is included in this message, then the
36 TKZ_MODE_SUPPORTED
37 If TKZ_MODE_SUPPORTEDIncluded is ‘0’, the access network shall
4-25
3GPP2 C.S0024-B v2.0
1 according to the definition of the TKZ_MODE_SUPPORTED field as

2 defined in [3].
3 TKZ_IDIncluded If TKZ_ID is included in this message, then the access network shall
5 to ‘0’.
6 TKZ_ID If TKZ_IDIncluded is ‘0’, the access network shall omit this field.
8 definition of the TKZ_ID field as defined in [3].
9 PILOT_REPORTIncluded
10 If PILOT_REPORT is included in this message, then the access
13 PILOT_REPORT If PILOT_REPORTIncluded is ‘0’, the access network shall omit this

15 the definition of the PILOT_REPORT field as defined in [3].
16 SDB_SUPPORTEDIncluded
17 If SDB_SUPPORTED is included in this message, then the access
20 SDB_SUPPORTED If SDB_SUPPORTEDIncluded is ‘0’, the access network shall omit

22 to the definition of the SDB_SUPPORTED field as defined in [3].
23 AUTO_FCSO_ALLOWEDIncluded
24 If AUTO_FCSO_ALLOWED is included in this message, then the
27 AUTO_FCSO_ALLOWED
28 If AUTO_FCSO_ALLOWEDIncluded is ‘0’, the access network shall
30 according to the definition of the AUTO_FCSO_ALLOWED field as
31 defined in [3].
32 SDB_IN_RCNM_INDIncluded
33 If SDB_IN_RCNM_IND is included in this message, then the access
4-26
3GPP2 C.S0024-B v2.0
1 SDB_IN_RCNM_IND If SDB_IN_RCNM_INDIncluded is ‘0’, the access network shall omit

3 to the definition of the SDB_IN_RCNM_IND field as defined in [3].
4 FPC_FCH_Included
5 If FPC_FCH_INIT_SETPT is included in this message, then the access
6 network shall set this field to ‘1’. Otherwise, the access network set
7 this field to ‘0’.
8 FPC_FCH_INIT_SETPT
9 If FPC_FCH_INIT_SETPT_Included is ‘0’, the access network shall
10 omit this field. Otherwise, the access network shall include this field
11 and set it according to the definition of the FPC_FCH_INIT_SETPT
12 field as defined in [3].
13 T_ADD_Included If T_ADD is included in this message, then the access network shall
14 set this field to ‘1’. Otherwise, the access network set this field to ‘0’.
15 T_ADD If T_ADD_Included is ‘0’, the access network shall omit this field.
16 Otherwise, the access network shall include this field and set it
17 according to the definition of the T_ADD field as defined in [3].16
20 set these bits to zero. The access terminal shall ignore these bits.
21
22 5.5.4.2.43G1XParametersResetAck
23 The access terminal sends a 3G1XParametersAck message to acknowledge the receipt of a
24 3G1XParameters message.
25
Field Length (bits)
MessageID 8
TransactionID 8
16 The AT can use the T_ADD parameter (if it is included in the 3G1XParameters message) for the
purpose of determining what 1X pilots are to be included in RouteUpdate messages and how to set
the 1X pilot KEEP field.
4-27
3GPP2 C.S0024-B v2.0
2 the 3G1XParameters message whose receipt is being acknowledged.
3
4 5.5.4.2.53G1XParametersReset
5 The access network can use this message to indicate that the access terminal is to clear all
6 stored values of 3G1X circuit service fields of the 3G1XParameters message.
Field Length (bits)
MessageID 8
TransactionID 8
8 TransactionID The access network shall increment this value modulo 256 for each
9 new 3G1XParametersReset message sent. If this is the first
10 3G1XParametersReset message sent by the access network, then the
12
13 5.5.4.2.63G1XParametersResetAck
14 The access terminal sends a 3G1XParametersResetAck message to acknowledge the receipt
15 of a 3G1XParametersReset message.
16
Field Length (bits)
MessageID 8
TransactionID 8
19 the 3G1XParametersReset message whose receipt is being
20 acknowledged.
21
4-28
3GPP2 C.S0024-B v2.0
1 5.5.4.2.7AttributeUpdateRequest
3 given attribute.
4
Field Length (bits)
MessageID 8
TransactionID 8

9
10 5.5.4.2.8AttributeUpdateAccept
13
Field Length (bits)
MessageID 8
TransactionID 8
17
4-29
3GPP2 C.S0024-B v2.0
1 5.5.4.2.9AttributeUpdateReject
4
Field Length (bits)
MessageID 8
TransactionID 8
8
9 5.5.5Interface to Other Protocols
10 5.5.5.1Commands
12 •RouteUpdate.SendRouteUpdate
13 5.5.5.2Indications
15 •IdleState.ConnectionOpened (access network only)
16 •RouteUpdate.ConnectionLost (access network only)
17 •ConnectedState.ConnectionClosed (access network only)
18 5.6Configuration Attributes of the 3G1X Circuit Services Notification Application

20 Generic Attribute Update Protocol to update configurable attributes belonging to the 3G1X
21 Circuit Services Notification Application. The access terminal and the access network shall
22 support the use of the Generic Attribute Update Protocol to update values of the following
23 configurable attributes belonging to the 3G1X Circuit Services Notification Application:
24 •AllowedReverseLinkMessages
25 •AllowedForwardLinkMessages
26 •OrderCodeReverse
4-30
3GPP2 C.S0024-B v2.0
1 •OrderCodeForward
2 •RAND
3 The access terminal shall not send an AttributeUpdateRequest message containing any of
4 the following attributes:
5 •AllowedReverseLinkMessages
6 •OrderCodeReverse
7 The access network shall not send an AttributeUpdateRequest message containing any of
8 the following attributes:
9 •AllowedForwardLinkMessages
10 •OrderCodeForward
11 5.6.1Simple Attributes
12 The configurable simple attributes for this application are listed in Table 5.6.1-1. The
13 access terminal and the access network shall use as defaults the values in Table 5.6.1-1
14 typed in bold italics.
15 Table 5.6.1-1. Configurable Values

0x0000 MaxIdleTunnelTime is zero by
default.
0x0001 MaxIdleTunnelTime
to 0x00fe =2IdleTunnelExponent×1.28 sec.
0xff IdleTunnelExponent
0xffff MaxIdleTunnelTime is infinity.
All other Reserved

values
0x0000 Authentication challenge for
0000 computation of AUTHR is zero
by default
0xfe RAND
0x00000 Authentication challenge for
001 to computation of AUTHR
0xffffffff
16 5.6.2Complex Attributes
17 The following configurable complex attributes and default values are defined.
18 5.6.2.1AllowedReverseLinkMessages Attribute
19
4-31
3GPP2 C.S0024-B v2.0
Field Length (bits) Default Value
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
r-cschMessageIDCount 8 0x00
r-cschMessageIDCount occurrences of the following two fields:
Reserved 2 N/A
r-cschMessageID 6 N/A
r-dschMessageIDCount 8 0x00
r-dschMessageIDCount occurrences of the following two fields:
r-dschMessageID 8 N/A
}
5 complex attribute. The sender shall change this field for each set of
6 values for this complex attribute.
7 r-cschMessageIDCount The sender shall set this field to the number of occurrences of the
8 MessageID field following this field in this record.
10 field.
11 r-cschMessageID The sender shall set this field to the message identifier of the
12 cdma2000 1x r-csch Layer 3 message as defined in [16], [19].
13 r-dschMessageIDCount
14 The sender shall set this field to the number of occurrences of the r-
15 dschMessageID field following this field in this record.
16 r-dschMessageID The sender shall set this field to the message identifier of the
17 cdma2000 1x r-dsch Layer 3 message as defined in [16], [19].
4-32
3GPP2 C.S0024-B v2.0
1 5.6.2.2AllowedForwardLinkMessages Attribute
2
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
f-cschMessageIDCount 8 0x00
f-cschMessageIDCount occurrences of the following two fields:
Reserved 2 N/A
f-cschMessageID 6 N/A
f-dschMessageIDCount 8 0x00
f-dschMessageIDCount occurrences of the following field:
f-dschMessageID 8 N/A
}
9 f-cschMessageIDCount
10 The sender shall set this field to the number of occurrences of the f-
11 cschMessageID field following this field in this record.
13 field.
14 f-cschMessageID The sender shall set this field to the message identifier of the
15 cdma2000 1x f-csch Layer 3 message as defined in [16], [19].
16 f-dschMessageIDCount
17 The sender shall set this field to the number of occurrences of the f-
18 dschMessageID field following this field in this record.
4-33
3GPP2 C.S0024-B v2.0
1 f-dschMessageID The sender shall set this field to the message identifier of the
2 cdma2000 1x f-dsch Layer 3 message as defined in [16], [19].
3 5.6.2.3ServiceOptionIdle attribute
4
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
ServiceOptionCount 8 0
ServiceOptionCount occurrences of the following field:
ServiceOption 16 N/A
11 ServiceOptionCount The sender shall set this field to the number of occurrences of the
12 ServiceOption field following this field in this record.
13 ServiceOption The sender shall set this field to the service option code as defined in
14 [10] corresponding to the service option of pages that the access
15 terminal should be notified of when the 3G1X Circuit Services
16 Notification Protocol is in the Idle Tunnel state.
4-34
3GPP2 C.S0024-B v2.0
1 5.6.2.4ServiceOptionConnected Attribute
2
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
ServiceOptionCount 8 0
ServiceOptionCount occurrences of the following field:
ServiceOption 16 N/A
9 ServiceOptionCount The sender shall set this field to the number of occurrences of the
11 ServiceOption The sender shall set this field to the service option code as defined in
12 [10] corresponding to the service option of pages that the access
13 terminal should be notified of when the 3G1X Circuit Services
14 Notification Protocol is in the Connected state.
4-35
3GPP2 C.S0024-B v2.0
1 5.6.2.5BurstTypeIdle Attribute
2
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
BurstTypeCount 8 0
BurstTypeCount occurrences of the following record:
{
BurstType 6 N/A
BroadcastAddressCount 2 0
BroadcastAddressCount occurrences of the following two fields:
AddressLength 4 N/A
BroadcastAddress 8×AddressLength N/A
}
}
9 BurstTypeCount The sender shall set this field to the number of occurrences of the
11 BurstType The sender shall set this field to the Data Burst Type as defined in
12 [10] corresponding to the type of the data burst for which Data Burst
13 Messages are to be tunneled when the 3G1X Circuit Services
15 BroadcastAddressCount
16 The sender shall set this field to the number of broadcast addresses
17 corresponding to the above burst type.
4-36
3GPP2 C.S0024-B v2.0
1 AddressLength The sender shall set this field to the number of octets in the
2 BroadcastAddress field following this field.
3 BroadcastAddress The sender shall set this field to the broadcast address corresponding
4 to the above burst type for which Data Burst Messages are to be
5 tunneled to the access terminal when the 3G1X Circuit Services
7 Reserved The sender shall add reserved bits to make the length of each
8 attribute value record an integer number of octets. The sender shall
9 set these bits to zeros. The receiver shall ignore this field.
10 5.6.2.6BurstTypeConnected Attribute
11
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
BurstTypeCount 8 0
BurstTypeCount occurrences of the following record:
{
BurstType 6 N/A
BroadcastAddressCount 2 0
BroadcastAddressCount occurrences of the following two fields:
AddressLength 4 N/A
BroadcastAddress 8× N/A
AddressLength
}
}
4-37
3GPP2 C.S0024-B v2.0
1 BurstTypeCount The sender shall set this field to the number of occurrences of the
3 BurstType The sender shall set this field to the Data Burst Type as defined in
4 [10] corresponding to the type of the data burst for which Data Burst
5 Messages are to be tunneled when the 3G1X Circuit Services
7 BroadcastAddressCount
8 The sender shall set this field to the number of broadcast addresses
9 corresponding to the above burst type.
10 AddressLength The sender shall set this field to the number of octets in the
11 BroadcastAddress field following this field.
12 BroadcastAddress The sender shall set this field to the broadcast address corresponding
13 to the above burst type for which Data Burst Messages are to be
14 tunneled to the access terminal when the 3G1X Circuit Services
16 Reserved The sender shall add reserved bits to make the length each attribute
17 value record an integer number of octets. The sender shall set these
18 bits to zeros. The receiver shall ignore this field.
19 5.6.2.7OrderCodeReverse Attribute
20
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
OrderCodeCount 8 0x00
OrderCodeCount occurrences of the following record:
Reserved 1 N/A
OrderCode 6 N/A
OrderQualificationCodeIncluded 1 N/A
OrderQualificationCode 0 or 8 N/A
4-38
3GPP2 C.S0024-B v2.0
4 OrderCodeCount The sender shall set this field to the number of occurrences of the
5 OrderCode field following this field in this record. If none of the
6 MessageID fields in this record is ‘000010’ (Order Message), then the
7 sender shall set this field to 0x00.
9 field.
10 OrderCode The sender shall set this field to the order code of the cdma2000 1x
11 r-csch order as defined in [3].
12 OrderQualificationCodeIncluded
13 If an order qualification code is included associated with this order
14 code, then the sender shall set this field to ‘1’. Otherwise, the sender
16 OrderQualificationCode
17 If OrderQualificationCodeIncluded is ‘0’, then the sender shall omit
18 this field. Otherwise, the sender shall set this field to the r-csch order
19 qualification code as defined in [3].
20 5.6.2.8OrderCodeForward Attribute
21
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
OrderCodeCount 8 0x00
OrderCodeCount occurrences of the following two fields:
Reserved 1 N/A
OrderCode 6 N/A
OrderQualificationCodeIncluded 1 N/A
OrderQualificationCode 0 or 8 N/A
4-39
3GPP2 C.S0024-B v2.0
4 OrderCodeCount The sender shall set this field to the number of occurrences of the
5 OrderCode field following this field in this record. If none of the
6 MessageID fields in this record is ‘000111’ (Order Message), then the
7 sender shall set this field to 0x00.
9 field.
10 OrderCode The sender shall set this field to the order code of the cdma2000 1x f-
11 csch order as defined in [3].
12 OrderQualificationCodeIncluded
13 If an order qualification code is included associated with this order
14 code, then the sender shall set this field to ‘1’. Otherwise, the sender
16 OrderQualificationCode
17 If OrderQualificationCodeIncluded is ‘0’, then the sender shall omit
18 this field. Otherwise, the sender shall set this field to the f-csch order
19 qualification code as defined in [3].
20 5.7Session State Information

22 This application defines the following parameter record in addition to the configuration
24 5.7.13G1XParameters
25 Table 5.7.1-1. The Format of the Parameter Record for the 3G1XParameters
26 Parameter
Field Length (bits)
ParameterType 8
Length 8
Current3G1XParameters 8 × (Length – 1)
4-40
3GPP2 C.S0024-B v2.0
1 Current3G1XParameters
2 This field shall include all fields (except MessageID) that were
3 included in any 3G1XParameters message sent to the access
4 terminal since the last 3G1XParametersReset message was sent (if
5 any). The most recent value sent to the access terminal for each field
6 shall be included. Fields of the 3G1XParameters message that were
7 not sent to the access terminal in any 3G1XParameters message
8 since the last 3G1XParametersReset message was sent shall not be
9 included. If no cdma2000 1x parameters were sent to the access
10 terminal in a 3G1XParameters message, then this field may be
11 omitted. If included, this field shall have the format of the
12 3G1XParameters message defined in 5.5.4.2.3 with the MessageID
13 field omitted.
14 5.7.2ProtocolState Parameter
15 Table 5.7.2-1. The Format of the Parameter Record for the ProtocolState Parameter
Field Length (bits)
ParameterType 8
Length 8
State 2
OtherActiveHRPDServices 8
IdleTunnelTime 0 or 32
Reserved 6
19 State If the 3G1X Circuit Services Notification Protocol is in the Inactive

20 State, then this field shall be set to ‘00’. If the 3G1X Circuit Services
21 Notification Protocol is in the Connected State, then this field shall be
22 set to ‘01’. If the 3G1X Circuit Services Notification Protocol is in the
23 IdleTunnel State, then this field shall be set to ‘10’. This field shall
24 not be set to ‘11’.
25 OtherActiveHRPDServices
26 This field shall be set to the value of the
27 OtherActiveHRPDServicesCount parameter. If the value of the
28 OtherActiveHRPDServicesCount is greater than 255, then this field
29 shall be set to 255.
4-41
3GPP2 C.S0024-B v2.0
1 IdleTunnelTime If the State field is not set to ‘10’, then this field shall be omitted.
2 Otherwise, this field shall be set to the CDMA System Time, in units
3 of 320 ms, when the IdleTunnelTime timer is to expire.
4 Reserved This field shall be set to ‘000000’. The receiver shall ignore this field.
4-42
Stream Layer 3GPP2 C.S0024-B v2.0
1 65 STREAM LAYER
2 6.15.1 Introduction
3 6.1.15.1.1 General Overview

4 The Stream Layer provides the following functions:
5 • Multiplexing of application streams for one access terminal. Stream 0 is always
6 assigned to the Signaling Application. The other streams can be assigned to
7 applications with different QoS (Quality of Service) requirements, or other applications.
8 • Provision of configuration messages that map applications to streams.
9 The Stream Layer uses the Stream Layer Protocol to provide these functions.
10 Application Subtypes are specified in [10]. Table 5.1-1 specifies the values of Application
11 Subtype for Applications defined in this specification.
12 Table 5.1-1. Application Subtypes for Applications Defined in this Specification
Value Meaning
0x0001 Default Packet Application bound to the radio
network.
0x0002 Default Packet Application bound to the
service network.
0x0004 Multi-Flow Packet Application bound to the
radio network.
0x0005 Multi-Flow Packet Application bound to the
service network.
0x0006 3G1X Circuit Services Notification
Application
13 6.1.25.1.2 Data Encapsulation for the InUse Protocol Instance

14 Figure 5.1.2-1 illustrates the relationship between an Application Layer packet, a Stream
15 Layer packet and a Session Layer payload.
5-1
3GPP2 C.S0024-B v2.0 Stream Layer
Application
Layer
packet
Stream Stream Stream

Layer Layer Layer
Session
Layer
payload
1
2 Figure 5.1.2-1. Stream Layer Encapsulation
5-2
1 6.25.2 Default Stream Protocol
2 6.2.15.2.1 Overview
3 The Default Stream Protocol provides the Stream Layer functionality. This protocol provides
4 the ability to multiplex up to 4 application streams. Stream 0 is always reserved for a
5 Signaling Application, and, by default, is assigned to the Default Signaling Application.
6 This protocol uses the Generic Configuration Protocol (see 13.7) to define the format and
7 processing of the configuration messages that map applications to streams.
8 The header added by this protocol is 2 bits in length. If x bits is the length of the payload
9 presented to the Stream Layer, x shall satisfy
10 x modulo 8 = 6.
11 6.2.25.2.2 Primitives and Public Data
12 6.2.2.15.2.2.1 Commands
14 6.2.2.25.2.2.2 Return Indications

16 6.2.2.35.2.2.3 Public Data

17 This protocol shall make the following data public:
18 • Subtype for this protocol
19 6.2.35.2.3 Protocol Data Unit

20 The protocol data unit for this protocol is a Stream Layer Packet.
21 6.2.45.2.4 Protocol Initialization
22 6.2.4.15.2.4.1 Protocol Initialization for the InConfiguration Protocol Instance

23 Upon creation, the InConfiguration instance of this protocol in the access terminal and the
24 access network shall perform the following in the order specified:
25 • The fall-back values of the attributes for this protocol instance shall be set to the
27 • If the InUse instance of this protocol has the same protocol subtype as this
28 InConfiguration protocol instance, then the fall-back values of the attributes defined by
29 the InConfiguration protocol instance shall be set to the values of the corresponding
30 attributes associated with the InUse protocol instance.
5-3
1 6.2.4.25.2.4.2 Protocol Initialization for the InUse Protocol Instance

2 Upon creation, the value of the attributes for the InUse instance of this protocol in the
3 access terminal and access network shall be set to the default values specified for each
4 attribute.
5 6.2.55.2.5 Procedures and Messages for the InConfiguration Instance of the Protocol
6 6.2.5.15.2.5.1 Procedures
7 The access terminal and the access network may use the ConfigurationRequest and
8 ConfigurationResponse messages to select the applications carried by each stream. When
9 the access terminal and the access network use these messages, they shall process them
10 according to the requirements presented in the Generic Configuration Protocol (see 13.7).
11 Once the access terminal and the access network agree upon the mapping of a new
12 application layer protocol to a stream (per the Generic Configuration Protocol), the access
13 terminal and access network shall create an InConfiguration instance of the agreed upon
14 application and replace the InConfiguration instance of the application for that stream (if
15 any) with the agreed upon application instance.
16 6.2.5.25.2.5.2 Commit Procedures

20 • All the public data that are defined by this protocol, but are not defined by the InUse
21 protocol instance shall be added to the public data of the InUse protocol.
22 • If the InUse instance of this protocol has the same subtype as this protocol instance,
23 then
25 associated with the InUse instance of this protocol to the attribute values
26 associated with the InConfiguration instance of this protocol, and
28 instance of the protocol.
29 • If the InUse instance of this protocol does not have the same subtype as this protocol
30 instance, then the access terminal and the access network shall perform the following:
31 − The InConfiguration protocol instance shall become the InUse protocol
32 instance for the Stream Protocol.
33 • All the public data not defined by this protocol shall be removed from the public data of
34 the InUse protocol.
5-4
1 6.2.5.35.2.5.3 Message Formats
2 6.2.5.3.15.2.5.3.1 ConfigurationRequest
4
Field Length (bits)
MessageID 8
TransactionID 8
10 6.2.5.3.25.2.5.3.2 ConfigurationResponse
12
Field Length (bits)
MessageID 8
TransactionID 8

5-5
2 6.2.65.2.6 Procedures and Messages for the InUse Instance of the Protocol
3 6.2.6.15.2.6.1 Procedures
4 This protocol receives application packets for transmission from up to four different
5 applications. The protocol adds the Stream header defined in 5.2.6.2 in front of each
6 application packet and forwards it for transmission to the Session Layer.
7 All Stream Layer packets forwarded to the Session Layer shall be octet aligned.
8 The protocol receives Stream Layer packets from the Session Layer and removes the
9 Stream Layer header. The application packet obtained in this manner is forwarded to the
10 application indicated by the Stream field of the Stream Layer header.
11 The structure of the Stream Layer packet is shown in Figure 5.2.6-1
Stream Layer packet
Stream Application
Layer Layer
header packet
12
13 Figure 5.2.6-1. Stream Layer Packet Structure
14 6.2.6.25.2.6.2 Stream Header

15 The sender adds the following header in front of every Stream Layer payload (application
16 packet):
Field Length(bits)
Stream 2
17 Stream The sender shall set this field to the stream number associated with
18 the application sending the application packet following the header.
19 6.2.6.35.2.6.3 Interface to Other Protocols
20 6.2.6.3.15.2.6.3.1 Commands
22 6.2.6.3.25.2.6.3.2 Indications
5-6
1 6.2.75.2.7 Configuration Attributes

2 The following complex attribute and default values are defined (see 13.3 for attribute record
3 definition).
4 6.2.7.15.2.7.1 StreamConfiguration Attribute

5
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
Stream0Application 16 0x0000
Stream1Application 16 0xffff
10 complex value.
11 Stream0Application The sender shall set this field to the subtype of the application used
12 over Stream 0.
14 over Stream 1.
16 over Stream 2.
18 over Stream 3.
19 Sender shall set the last four fields to 0xffff or to one of the non-reserved values for the
20 Application Subtype as specified in [10].
21 6.2.85.2.8 Protocol Numeric Constants

22
5-7

NSTRType Type field for this protocol. Table 2.5.4-1
NSTRDefault Subtype field for this protocol 0x0000
1 6.2.95.2.9 Session State Information

3 The parameter records for this protocol consist of only the configuration attributes of this
4 protocol.
5-8
1 6.35.3 Generic Virtual Stream Protocol
2 6.3.15.3.1 Overview
3 The Generic Virtual Stream Protocol provides Stream Layer functionality. This protocol
4 provides the ability to multiplex up to 255 application streams.
5 This protocol uses the Generic Configuration Protocol (see 13.7) to define the format and
6 processing of the configuration messages that map applications to virtual streams.
8 6.3.2.15.3.2.1 Commands

12 6.3.2.35.3.2.3 Public Data


16 This protocol carries data from the higher layer in an ApplicationData message. Hence, the
17 protocol data unit for this protocol is an ApplicationData message. This protocol uses the
18 Signaling Application to transmit and receive messages.

5-9
2 6.3.5.15.3.5.1 Procedures
3 The access terminal and the access network may use the ConfigurationRequest and
4 ConfigurationResponse messages to select the applications carried by each virtual stream.
5 When the access terminal and the access network use these messages, they shall process
6 them according to the requirements presented in the Generic Configuration Protocol (see
7 13.7).
8 Once the access terminal and the access network agree upon the mapping of a new
9 application layer protocol to a virtual stream (per the Generic Configuration Protocol), the
10 access terminal and access network shall create an InConfiguration instance of the agreed
11 upon application and replace the InConfiguration instance of the application for that
12 virtual stream (if any) with the agreed upon application instance.

20 then
28 − The values of the public data of the InConfiguration protocol instance shall be
29 copied to the corresponding public data of the InUse protocol.
31 instance for the Session Configuration Protocol at the access terminal and the
32 access network.
33 • All the public data that are not defined by this protocol shall be removed from the list of
34 public data for the InUse protocol instance.
5-10
Field Length (bits)
MessageIndicator 8
MessageID 8
TransactionID 8
2 MessageIndicator The sender shall set this field to 0x00 to indicate that this message
3 does not carry application payload.
11
Field Length (bits)
MessageIndicator 8
MessageID 8
TransactionID 8
12 MessageIndicator The sender shall set this field to 0x00 to indicate that this message
13 does not carry application payload.
5-11

6
8 6.3.6.15.3.6.1 Procedures
9 This protocol receives application packets for transmission from up to 255 different
10 applications. This protocol carries payload for the higher layer using virtual streams. This
11 protocol provides 255 virtual streams. A virtual stream is identified by its virtual stream
12 number in the range 0x01 to 0xff inclusive. Data from an application bound to one of the
13 virtual streams is carried using ApplicationData messages.
14 If x bits is the length of the data payload presented to the Stream Layer by an application, x
15 shall satisfy
16 x modulo 8 = 6.
17 The protocol shall generate an ApplicationData message (5.3.6.2.1) to send a data payload
18 belonging to an application bound to a virtual stream.
20 6.3.6.2.15.3.6.2.1 ApplicationData
21 The access terminal or the access network sends an ApplicationData message to send a
22 payload belonging to an application bound to a virtual stream.
23
Field Length (bits)

VirtualStream 8
Reserved 2
StreamLayerPayload (8 × n) + 6, where n is a
non-negative integer.
24 VirtualStream The sender shall set this field to the 8-bit virtual stream number
25 associated with the application sending the application payload
26 carried in this message in the range 0x01 to 0xff, inclusive.
28 field.
5-12
1 StreamLayerPayload The sender shall set this field to payload from the application bound
2 to the virtual stream.
3
Priority of this
message shall be set
to the priority of the
Addressing unicast Priority payload carried in
this message.
5 6.3.6.3.15.3.6.3.1 Commands
7 6.3.6.3.25.3.6.3.2 Indications
10 6.3.7.15.3.7.1 Simple Attributes

11 The configurable simple attribute for this protocol is listed in Table 5.3.7-1. The access
12 terminal and the access network shall use as defaults the values in Table 5.3.7-1 typed in
13 bold italics.

VirtualStreamNNApplic 0xffff Virtual stream not used.
0xffNN
ation
NN is the 0x0000 Application subtype as specified in
NN is the two-digit to 0xfffe [10] for the application bound to
two-digit
hexadecimal virtual
hexadecimal virtual stream NN.
stream number in the
virtual
range 0x01 to 0xFF,
stream
inclusive where
number in
the range
through F are
0x01 to 0xff,
represented by capital
inclusive.
letters.

16
5-13

NVSPType Type field for this protocol Table 2.5.4-1
NVSP Subtype field for this protocol 0x0001

4 protocol.
5-14
Session Layer 3GPP2 C.S0024-B v2.0
1 76 SESSION LAYER

4 The Session Layer contains protocols used to negotiate a session between the access
5 terminal and the access network.
6 A session is a shared state maintained between the access terminal and the access
7 network, including information such as:
8 • A unicast address (UATI) assigned to the access terminal,
9 • the set of protocols used by the access terminal and the access network to
10 communicate over the air-link,
11 • configuration settings for these protocols (e.g., authentication keys, parameters for
12 Connection Layer and MAC Layer protocols, etc.), and
13 • an estimate of the current access terminal location.
14 During a single session the access terminal and the access network can open and close a
15 connection multiple times; therefore, sessions will be closed rarely, and only on occasions
16 such as the access terminal leaving the coverage area or such as prolonged periods in
17 which the access terminal is unavailable.
18 The Session Layer contains the following protocols:
19 • Session Management Protocol: This protocol provides the means to control the
20 activation of other Session Layer protocols. In addition, this protocol ensures the
21 session is still valid and manages closing of the session.
22 • Address Management Protocol: This protocol specifies procedures for the initial UATI
23 assignment and maintains the access terminal addresses.
24 • Session Configuration Protocol: This protocol provides the means to negotiate and
25 provision the protocols used during the session, and negotiates the configuration
26 parameters for these protocols. This protocol uses the procedures and attribute value
27 formats defined by the Generic Configuration Protocol (see 13.7) for protocol
28 negotiation.
29 • Multimode Capability Discovery Protocol: This protocol allows the access network to
30 discover the multimode capabilities of the access terminal.
31 The relationship between the Session Layer protocols is illustrated in
32 Figure 6.1.1-1.
6-1
3GPP2 C.S0024-B v2.0 Session Layer
Session
Management
Protocol
Multimode
Address Session Capability
Management Configuration Discovery
Protocol Protocol Protocol
1
2 Figure 6.1.1-1. Session Layer Protocols

4 The Session Layer does not modify transmitted or received packets.
5 Figure 6.1.2-1 illustrates the relationship between Stream Layer packets, Session Layer
6 packets, and Connection Layer payload.
Stream
Layer
packet
Session Session
Layer Layer
packet payload
Connection
Layer
payload
7
8 Figure 6.1.2-1. Session Layer Encapsulation
6-2
1 7.26.2 Default Session Management Protocol
2 7.2.16.2.1 Overview
3 The Default Session Management protocol provides the means to control the activation of
4 the Address Management Protocol and then the Session Configuration Protocol, in that
5 order, before a session is established. This protocol also periodically ensures that the
6 session is still valid and manages closing the session.
7 The actual behavior and message exchange in each state of this protocol are mainly
8 governed by protocols that are activated by the Default Session Management Protocol.
9 These protocols return indications, which trigger the state transitions of this protocol.
10 This protocol can be in one of four states:
11 • Inactive State: This state applies only to the access terminal. In this state there are no
12 communications between the access terminal and the access network.
13 • AMP Setup State: In this state the access terminal and access network perform
14 exchanges governed by the Address Management Protocol and the access network
15 assigns a UATI to the access terminal.
16 • Open State: In this state a session is open.
17 • Close State: This state applies only to the access network. In this state the access
18 network waits for the close procedure to complete.
19 Figure 6.2.1-1 provides an overview of the access terminal states and state transitions.
Failure transitions are not shown
Initial State
Rx Activate Rx AddressManagement.Opened
AMP
Inactive Open
Setup
State State
State
Tx SessionClose
Tx SessionClose
20

22 Terminal)
6-3

Initial State
AMP
Setup
State
Tx SessionClose Rx AddressManagement.Opened
Rx SessionClose or
Close State
Rx SessionClose
timer expired
Close Open
State State
Tx SessionClose
1
2 Figure 6.2.1-2. Default Session Management Protocol State Diagram (Access Network)
4 7.2.2.16.2.2.1 Commands
6 • Activate
7 • Deactivate

10 • SessionOpened
11 • SessionClosed
12 7.2.2.36.2.2.3 Public Data

6-4

4 This protocol uses the Signaling Application to transmit and receive messages.


18 Upon creation, the InUse instance of this protocol in the access terminal and access
20 • The value of the attributes for this protocol instance shall be set to the default values
21 specified for each attribute.
22 • The protocol at the access network shall enter the AMP Setup State.
23 • The protocol at the access terminal shall enter the Inactive State.
25 7.2.5.16.2.5.1 Procedures

35 then
6-5
7 instance, then the access terminal and the access network shall perform the following
8 in the order specified:
9 − Set the initial state of the InConfiguration protocol instance to the Open State.
11 instance for the Session Management Protocol.
17
Field Length (bits)
MessageID 8
TransactionID 8
22
25
6-6
Field Length (bits)
MessageID 8
TransactionID 8

9
11 7.2.6.16.2.6.1 Procedures
12 7.2.6.1.16.2.6.1.1 Command Processing

13 The list of events that causes an Activate or Deactivate command to be sent to this protocol
14 is outside the scope of this specification.
15 7.2.6.1.1.16.2.6.1.1.1 Activate
16 If the access terminal receives the Activate command in the Inactive State, it shall
17 transition to the AMP Setup State.
18 If the access terminal receives the Activate command in any state other than the Inactive
19 State, the command shall be ignored.
20 The access network shall ignore the command.
21 7.2.6.1.1.26.2.6.1.1.2 Deactivate
22 If the access terminal receives a Deactivate command in the Inactive State, the command
24 If the access terminal receives a Deactivate command in any state other than the Inactive
25 State, the access terminal shall perform the following:
26 • Send a SessionClose message to the access network.
6-7
1 • Issue an AirLinkManagement.CloseConnection command.

2 • Issue an AddressManagement.Deactivate command.
3 • Issue a SessionConfiguration.Deactivate command.
4 • Return a SessionClosed indication.
5 • Transition to the Inactive State.
6 If the access network receives a Deactivate command in the Close State, the command shall
7 be ignored.
8 If the access network receives a Deactivate command in any state other than the Close
9 State, the access network shall send a SessionClose message and transition to the Close
10 State.
11 7.2.6.1.26.2.6.1.2 Processing the SessionClose Message

12 If the access terminal receives a SessionClose message in the Inactive State, the message
14 If the access terminal receives a SessionClose message in any state other than the Inactive
15 State, the access terminal shall perform the following:
22 If the access network receives a SessionClose message in the Close State, the access
23 network shall process it as specified in 6.2.6.1.7.
24 If the access network receives a SessionClose message in any state other than the Close
25 State, the access network shall:
30 • Transition to the AMP Setup State.
31 7.2.6.1.36.2.6.1.3 Processing Failed Indications

32 The access terminal shall ignore an AddressManagement.Failed, or a
33 SessionConfiguration.Failed indication, if the access terminal receives the indication in the
34 Inactive State.
6-8
1 If the access terminal receives a SessionConfiguration.Failed indication while in any state

2 other than the Inactive State, then the access terminal shall perform the following:
8 • The access terminal shall transition to the Inactive State.
9 If the access terminal receives an AddressManagement.Failed indication while in any state
10 other than the Inactive State, then the access terminal shall perform the following:
16 If the access network receives an AddressManagement.Failed, or a
17 SessionConfiguration.Failed indication, the access network shall perform the following:
18 • Send a SessionClose message to the access terminal.
20 7.2.6.1.46.2.6.1.4 Inactive State

21 This state only applies to the access terminal. In this state there are no communications
22 between the access terminal and the access network. The access terminal does not
23 maintain any session-related state and the access network may be unaware of the access
24 terminal’s existence within its coverage area when the access terminal’s Session
25 Management Protocol is in this state.
26 7.2.6.1.56.2.6.1.5 AMP Setup State

27 In this state the Session Management Protocol in the access terminal sends an
28 AddressManagement.Activate command to the Address Management Protocol and waits for
29 the Address Management Protocol to respond.
30 7.2.6.1.5.16.2.6.1.5.1 Access Terminal Requirements

31 Upon entering the AMP Setup State, the access terminal shall send an
32 AddressManagement.Activate command to the Address Management Protocol.
33 If the access terminal receives an AddressManagement.Opened indication, it shall perform
34 the following:
35 • Issue a SessionConfiguration.Activate command.
6-9
1 • Return a SessionOpened indication.

3 7.2.6.1.5.26.2.6.1.5.2 Access Network Requirements

4 If the access network receives an AddressManagement.Opened indication, it shall perform
5 the following:
6 • Issue a SessionConfiguration.Activate command.
7 • Return a SessionOpened indication.
9 7.2.6.1.66.2.6.1.6 Open State

10 In the Open State the access terminal has an assigned UATI and the access terminal and
11 the access network have a session.
12 The access terminal and the access network shall support the keep-alive mechanism
13 defined in 6.2.6.1.6.1.
14 7.2.6.1.6.16.2.6.1.6.1 Keep Alive Functions

15 The access terminal and the access network shall monitor the traffic flowing on the
16 Forward Channel and Reverse Channel, respectively, directed to or from the access
17 terminal. If either the access terminal or the access network detects a period of inactivity of
18 at least TSMPClose/NSMPKeepAlive minutes, it may send a KeepAliveRequest message. The
19 recipient of the message shall respond by sending the KeepAliveResponse message. When a
20 KeepAliveResponse message is received, the access terminal shall not send another
21 KeepAliveRequest message for at least TSMPClose/NSMPKeepAlive minutes.
22 If the access terminal does not detect any traffic from the access network directed to it for a
23 period of at least TSMPClose minutes, it shall perform the following:
29 If the access network does not detect any traffic from the access terminal directed to it for a
30 period of at least TSMPClose minutes, it should perform the following:
6-10
1 If the value of TSMPClose is set to zero, the access terminal and the access network shall not
2 send or expect keep-alive messages, and shall disable the transitions occurring as a
3 consequence of not receiving these messages.
4 7.2.6.1.76.2.6.1.7 Close State

5 The Close State is associated only with the protocol in the access network. In this state the
6 protocol in the access network waits for a SessionClose message from the access terminal
7 or an expiration of a timer.
8 The access network shall set the Close State timer upon entering this state. The value of
9 this timer shall be set to TSMPClose or TSMPMinClose, whichever is larger.
10 When the access network receives a SessionClose message or when the Close State timer
11 expires the protocol shall:
17 While in this state, if the access network receives any packet from the access terminal
18 which is addressed by the UATI assigned during this session and contains anything but a
19 SessionClose message, it shall stay in the Close State and perform the following:
20 • Discard the packet.
21 • Respond with a SessionClose message.
23 7.2.6.2.16.2.6.2.1 SessionClose
24 The sender sends the SessionClose message to terminate the session.
25
Field Length (bits)
MessageID 8
CloseReason 8
MoreInfoLen 8
MoreInfo 8 × MoreInfoLen
27 CloseReason The sender shall set this field to the close reason as shown in Table
28 6.2.6.2.1-1
6-11
1 Table 6.2.6.2.1-1. Encoding of CloseReason Field
Field Meaning MoreInfoLen MoreInfo

Value
0x00 Normal Close 0 N/A
0x01 Close Reply 0 N/A
0x02 Protocol Error 0 N/A
0x03 Protocol Configuration 3 or 4 See 6.2.6.2.1.1.
Failure
0x04 Protocol Negotiation variable See 6.2.6.2.1.2.
Error
0x05 Session Configuration 0 N/A
Failure
0x06 Session Lost 0 N/A
0x07 Session Unreachable 0 N/A
0x08 All session resources 0 N/A
busy
All other values are reserved
2 MoreInfoLen Length in octets of the MoreInfo field.
3 MoreInfo Additional information pertaining to the closure. The format of this

4 field is determined by the particular close reason.
5
6 7.2.6.2.1.16.2.6.2.1.1 Definition of MoreInfo record when the CloseReason is 0x03

7
Field Length (bits)

TypeLength 1
Type 7 or 15
SubType 16
8 TypeLength The sender shall set this field to ‘0’ if the Type field is 7 bits long.
9 Otherwise, the sender shall set this field to ‘1’.
10 Type This field has the following format:

11
6-12

Type1 7
Type2 0 or 8
2 Type value for the protocol (as defined in [10]) for which configuration
3 failed.
4 Type2 If the length of the Type value for the protocol for which configuration
5 failed is 7 bits, then this field shall be omitted. Otherwise, this field
6 shall be set to the 8 least significant bits of the Type value for the
7 protocol for which configuration failed17.
8 SubType The sender shall set this field to the subtype value for the protocol
9 subtype (as defined in [10]) for which configuration failed.
10 7.2.6.2.1.26.2.6.2.1.2 Definition of MoreInfo record when the CloseReason is 0x04

11
Field Length (bits)

TypeLength 1
Type 7 or 15
SubType 16
NumAttributeRecords 8
NumAttributeRecords occurrences of the following field:
OffendingAttributeRecord Variable Length
Reserved Variable
14 Type ProtocolType. This field has the following format:

15
6-13

Type1 7
Type2 0 or 8
2 Type value for the protocol (as defined in [10]) for which there was a
3 negotiation error.
4 Type2 If the length of the Type value for the protocol for which there was a
5 negotiation error is 7 bits, then this sub-field shall be omitted.
6 Otherwise, this field shall be set to the 8 least significant bits of the
7 Type value for the protocol for which there was a negotiation error18.
8 NumAttributeRecords
9 This field shall be set to the number of occurrences of the
10 OffendingAttributeRecord field following this field in this record.
11 OffendingAttributeRecord
12 This field shall be set to the offending attribute record. The format of
13 the attribute record is specified in 15.3.
14 SubType The sender shall set this field to the subtype value for the protocol
15 subtype (as defined in [10]) for which configuration failed.
16 Reserved The sender shall add reserved bits to make the length of the entire
17 record an integer number of octets. The sender shall set these bits to
18 ‘0’. The receiver shall ignore this field.
19 7.2.6.2.26.2.6.2.2 KeepAliveRequest
20 The sender sends the KeepAliveRequest to verify that the peer is still alive.
21
Field Length (bits)
MessageID 8
TransactionID 8
23 TransactionID The sender shall increment this value for each new KeepAliveRequest
24 message sent.
25
6-14
1 7.2.6.2.36.2.6.2.3 KeepAliveResponse
2 The sender sends the KeepAliveResponse message as an answer to the KeepAliveRequest
3 message.
Field Length (bits)
MessageID 8
TransactionID 8
5 TransactionID The sender shall set this value to the value of the TransactionID field
6 of the corresponding KeepAliveRequest message.
7
9 7.2.6.3.16.2.6.3.1 Commands Sent

10 This protocol issues the following commands:
11 • AddressManagement.Activate
12 • SessionConfiguration.Activate
13 • AddressManagement.Deactivate
14 • SessionConfiguration.Deactivate
15 • AirLinkManagement.CloseConnection
16 7.2.6.3.26.2.6.3.2 Indications
18 • AddressManagement.Failed
19 • SessionConfiguration.Failed
20 • AddressManagement.Opened

22 The negotiable attributes for this protocol are listed in Table 6.2.7-1. The access terminal
23 shall use as defaults the values in Table 6.2.7-1 typed in bold italics.
6-15
1 Table 6.2.7-1. Configurable Attributes
Attribute Attribute Values Meaning

ID
0x0CA8 Default is 54 hours.
0xff TSMPClose 0x0000 to 0x0000 means disable keep

0xffff alive messages; all other values
are in minutes.
2

NSMPType Type field for this protocol Table 2.5.4-1
NSMPDefault Subtype field for this protocol 0x0000
NSMPKeepAlive Maximum number of keep alive transactions 3
within TSMPClose.
TSMPMinClose Minimum recommended timer setting for Close 300 seconds
State

7 protocol.
6-16
1 7.36.3 Default Address Management Protocol
2 7.3.16.3.1 Overview
3 The Default Address Management Protocol provides the following functions:
4 • Initial UATI assignment
5 • Maintaining the access terminal unicast address as the access terminal moves between
6 subnets.
7 This protocol operates in one of three states:
8 • Inactive State: In this state there are no communications between the access terminal
10 • Setup State: In this state the access terminal and the access network perform a
11 UATIRequest/UATIAssignment/UATIComplete exchange to assign the access terminal a
12 UATI.
13 • Open State: In this state the access terminal has been assigned a UATI. The access
14 terminal and access network may also perform a UATIRequest/UATIAssignment
15 /UATIComplete or a UATIAssignment/UATIComplete exchange so that the access
16 terminal obtains a new UATI.
17 The protocol states and the messages and events causing the transition between the states
18 are shown in Figure 6.3.1-1 and Figure 6.3.1-2.

Initial State
Tx UATIComplete
Rx Activate
Inactive Setup Open

State State State
Rx Deactivate
Rx Deactivate
19

21 Terminal)
6-17

Initial State
Rx UATIComplete
Rx UATIRequest
Inactive Setup Open

State State State
Rx Deactivate
Rx Deactivate
1
2 Figure 6.3.1-2. Default Address Management Protocol State Diagram (Access Network)
4 7.3.2.16.3.2.1 Commands
5 This protocol defines the following command:
6 • Activate
7 • Deactivate
8 • UpdateUATI

11 • Opened
12 • UATIReleased
13 • UATIAssigned
14 • Failed
15 • SubnetChanged
16 7.3.2.36.3.2.3 Public Data

19 • ReceiveATIList
20 • TransmitATI
21 • SessionSeed
6-18
1 7.3.36.3.3 Connection Endpoints

2 The following Connection Endpoints are defined (to be used by the SLP):
3 • The addresses specified by entries in the ReceiveATIList list whose ATIType is equal to
4 ‘11’ (i.e., RATI) or ‘10’ (i.e., UATI) all define the same connection endpoint.
5 • Each unique <ATI, Physical Layer Channel> where ATI is an entry in the ReceiveATIList
6 with ATIType equal to ‘00’ (i.e., BATI), defines a separate Connection Endpoint.



28 • The protocol at the access terminal and the access network shall enter the Inactive
29 State.
31 7.3.6.16.3.6.1 Procedures
6-19

8 then
17 − Set the initial state of the InConfiguration protocol instance to the Open State.
18 − Set the receive pointer for UATIAssignment message validation, V(R), to 255.
20 instance for the Address Management Protocol.
26
Field Length (bits)
MessageID 8
TransactionID 8
6-20
4
Field Length (bits)
MessageID 8
TransactionID 8

13
15 7.3.7.16.3.7.1 Procedures
17 7.3.7.1.1.16.3.7.1.1.1 Activate
18 If the protocol receives the Activate command in the Inactive State:
19 • The access terminal shall transition to the Setup State.
20 • The access network shall ignore the command.
21 If the protocol receives the Activate command in any state other than the Inactive State, the
22 command shall be ignored.
6-21
1 7.3.7.1.1.26.3.7.1.1.2 Deactivate
2 If the protocol receives the Deactivate command in the Inactive State, the command shall be
3 ignored.
4 If the protocol receives the Deactivate command in any state other than the Inactive State,
5 the protocol shall transition to the Inactive State and return a UATIReleased indication.
6 7.3.7.1.1.36.3.7.1.1.3 UpdateUATI
7 The access network and the access terminal shall ignore the UpdateUATI command when it
8 is received in any state other than the Open State.
9 If the access terminal receives an UpdateUATI command in the Open State, it shall set
10 OldUATI to UATI and shall send a UATIRequest message.
11 If the access network receives an UpdateUATI command in the Open State, it may send a
12 UATIAssignment message.
13 A comprehensive list of events causing the UpdateUATI command is beyond the scope of
14 this specification.
15 7.3.7.1.26.3.7.1.2 UATIAssignment Message Validation

16 Each time that the access network sends a new UATIAssignment message, it shall
17 increment the value of the MessageSequence field.
18 The access terminal shall initialize a receive pointer for the UATIAssignment message
19 validation, V(R), to 255 when it sends a UATIRequest message and there exist an entry in
20 the ReceiveATIList list whose ATIType field is equal to ‘11’ (i.e., RATI).
21 When the access terminal receives a UATIAssignment message, it shall validate the
22 message, using the procedure defined in 13.6 (S is equal to 8). The access terminal shall
23 discard the message if it is invalid.
24 7.3.7.1.36.3.7.1.3 Processing HardwareIDRequest message

25 Upon reception of a HardwareIDRequest message, the access terminal shall respond with a
26 HardwareIDResponse message. The access terminal shall set the HardwareID record of the
27 HardwareIDResponse message to the unique ID that has been assigned to the terminal by
28 the manufacturer.
29 7.3.7.1.46.3.7.1.4 Inactive State

30 In this state, there are no communications between the access terminal and the access
31 network. The access terminal does not have an assigned UATI, the access network does not
32 maintain a UATI for the access terminal, and may be unaware of the access terminal’s
33 existence within its coverage area.

35 Upon entering the Inactive State, the access terminal shall perform the following:
36 • Set OldUATI to NULL.
6-22
1 • Clear the ReceiveATIList

2 • Add the following entry to the ReceiveATIList:
3 <ATIType = ‘00’, ATI = NULL>.
4 • Set TransmitATI to
5 <ATIType = NULL, ATI = NULL>.
6 • Set UATI to NULL.
7 • Set UATIColorCode to NULL.
8 • Set UATISubnetMask to NULL.
9 • Set SessionSeed to the 32-bit pseudo-random number generated using output of the
10 pseudo random number generator specified in 13.5.
11 • Disable the Address timers.
12 • Set (xo, yo) to (NULL, NULL).
13 If the access terminal receives an Activate command, it shall transition to the Setup State.

15 Upon entering the Inactive State, the access network shall perform the following:
16 • Set the value of the access terminal’s UATI to NULL.
17 • Set the value of the access terminal’s UATISubnetMask to NULL.
18 • Set the value of the access terminal’s UATIColorCode to NULL.
19 The access network shall transition to the Setup State if it receives a UATIRequest
20 message.
21 7.3.7.1.56.3.7.1.5 Setup State

22 In this state, the access terminal sends a request to the access network asking for a UATI
23 and waits for the access network’s response.

25 Upon entering the Setup State the access terminal shall perform the following:
26 • Set the TransmitATI to
27 <ATIType = ‘11’, ATI = SessionSeed>,
28 • Add the following entry to the ReceiveATIList list
29 <ATIType = ‘11’, ATI = SessionSeed>.
30 • Shall send a UATIRequest message.
31 A valid (see 6.3.7.1.2) UATIAssignment message that satisfies either of the following
32 conditions is called a “fresh” UATIAssignment message:
6-23
1 • OverheadParametersUpToDate, provided as the public data of the Overhead Messages

2 Protocol, is equal to 1 and the UATIColorCode field in the message matches the
3 ColorCode, given as public data of the Overhead Messages Protocol, or
4 • the SubnetIncluded field of the message is equal to ‘1’,
5 The access terminal shall discard a UATIAssignment message that is not “fresh”.
6 If the access terminal does not receive a “fresh” UATIAssignment message within
7 TADMPATResponse seconds after receiving an AccessChannelMAC.TxEnded indication, it shall
8 return a Failed indication and transition to the Inactive State.
9 If the access terminal receives a “fresh” UATIAssignment message then the access terminal
10 shall perform the following:
11 • Set the UATIColorCode to the UATIColorCode given in the message.
12 • Set its UATI and UATISubnetMask as follows:
13 − If the message includes the UATI104 field and UATISubnetMask field, the
14 access terminal shall set its UATI to UATI104 | UATI024 and UATISubnetMask
15 to UATISubnetMask field included in the message.
16 − Otherwise, the access terminal shall set its UATI to (SectorID[127:24] |
17 UATI024) and UATISubnetMask to SubnetMask where SectorID and
18 SubnetMask are provided as public data of Overhead Messages Protocol.
19 • Delete any entry in the ReceiveATIList list whose ATIType is equal to ‘11’ (i.e., RATI).
21 <ATIType=‘10’, ATI = (UATIColorCode | UATI[23:0])>.
24 • Return an Opened indication.
25 • Return a UATIAssigned indication.
26 • Send a UATIComplete message.

29 When the access network sends a UATIAssignment message, it shall perform the following:
30 • Access network shall assign a Unicast Access Terminal Identifier (UATI) to the access
31 terminal for the session as follows:
32 − Access network may include both UATI104 and UATISubnetMask fields in the
33 UATIAssignment message.
6-24
1 − Access network may omit the UATI104 and UATISubnetMask fields from the
2 message. In this case, the UATI[127:24] is implicitly assigned to be equal to
3 SectorID[127:24] and UATISubnetMask is implicitly assigned to be
4 SubnetMask, where SectorID and SubnetMask correspond to the sector that
5 has received the UATIRequest message.
6 When the access network receives the corresponding UATIComplete message with the
7 MessageSequence field of the UATIAssignment message sent, it shall perform the following:
8 • Return Opened indication.
9 • Return UATIAssigned indication.
10 • Transition to Open State.
11 If the access network does not receive the corresponding UATIComplete message in
12 response to the UATIAssignment message, it may re-transmit the UATIAssignment
13 message. If the access network does not receive the UATIComplete message after an
14 implementation specific number of re-transmissions of the UATIAssignment message, it
15 shall return a Failed indication and transition to the Inactive State.
16 7.3.7.1.66.3.7.1.6 Open State

17 In this state the access terminal has been assigned a UATI.

19 The subnet associated with the UATI and the current subnet are defined to be different if
20 either of the following two conditions are satisfied:
21 • The UATISubnetMask is not equal to the SubnetMask of the sector in the active set, or
22 • the result of bitwise logical AND of the UATI and its subnet mask specified by
23 UATISubnetMask is different from the result of bitwise logical AND of SectorID and its
24 subnet mask specified by SubnetMask (where SectorID and SubnetMask correspond to
25 the sector in the active set).
26 If the access terminal receives a RouteUpdate.IdleHO indication or a
27 ConnectedState.ConnectionClosed, and then it receives an OverheadMessages.Updated
28 indication, and if both of the following two conditions are true, then the access terminal
29 shall set OldUATI to UATI and shall send a UATIRequest message:
30 • The subnet associated with UATI and the current subnet are different, and
31 • SupportSecondaryColorCodes is set to 0x00 or UATIColorCode is different from all of
32 the SecondaryColorCode values provided as public data by the Overhead Messages
33 Protocol1.
1 The advertisement of SecondaryColorCode values might require the access network to deliver pages
across subnet boundaries into areas in other subnets with the same ColorCode value that is
advertised in the SecondaryColorCode values. The means by which the access network accomplishes
this are beyond the scope of this specification.
6-25
1 If the access terminal receives an UpdateUATI command, it shall process the command as
2 specified in 6.3.7.1.1.3.
3 A valid (see 6.3.7.1.2) UATIAssignment message that satisfies either of the following
4 conditions is called a “fresh” UATIAssignment message:
5 • OverheadParametersUpToDate, provided as the public data of the Overhead Messages
6 Protocol, is equal to 1 and the UATIColorCode field in the message matches the
7 ColorCode, given as public data of the Overhead Messages Protocol, or
8 • The SubnetIncluded field of the message equal to ‘1’.
9 The access terminal shall discard a UATIAssignment message that is not “fresh”.
10 Upon sending a UATIRequest message, the access terminal shall start a UATIResponse
11 timer with a timeout value of TADMPATResponse seconds after receiving an
12 AccessChannelMAC.TxEnded indication. The access terminal shall disable this timer if
13 either of the following conditions is true:
14 • The UATISubnetMask is equal to the SubnetMask of the sector in the active set, and
15 the result of bitwise logical AND of the UATI and its subnet mask specified by
16 UATISubnetMask is the same as the result of bitwise logical AND of SectorID and its
17 subnet mask specified by SubnetMask (where SectorID and SubnetMask correspond to
18 the sector in the active set), or
19 • The access terminal receives a “fresh” UATIAssignment message.
20 If the UATIResponse timer expires, the access terminal shall return a Failed indication and
21 transition to the Inactive State.
22 If the access terminal receives a “fresh” UATIAssignment message then the access terminal
24 • Set the UATIColorCode to the UATIColorCode given in the message.
25 • Set its UATI and UATISubnetMask as follows:
26 − If the message includes the UATI104 field and UATISubnetMask field, the
27 access terminal shall set its UATI to UATI104 | UATI024 and UATISubnetMask
28 to UATISubnetMask field included in the message.
29 − Otherwise, the access terminal shall set its UATI to (SectorID[127:24] |
30 UATI024) and UATISubnetMask to SubnetMask where SectorID and
31 SubnetMask are provided as public data of Overhead Messages Protocol.
33 <ATIType = ‘10’, ATI = (UATIColorCode | UATI[23:0])>.
36 • Return a UATIAssigned indication.
37 • Send a UATIComplete message.
6-26
1 • Reset and start an Address timer with a timeout value of TADMPAddress for the added entry
2 to the ReceiveATIList.
3 The access terminal shall perform the following when an Address timer corresponding to an
4 entry in the ReceiveATIList expires:
5 • Disable the Address timer for that entry.
6 • Delete all the entries in the ReceiveATIList that are older than the entry whose Address
7 timer has expired. An entry X in the list is considered older than another entry Y, if the
8 entry X has been added to the list prior to the entry Y.
9 If the access terminal receives an InitializationState.NetworkAcquired indication followed by
10 an OverheadMessages.Updated indication, then the access terminal shall perform the
11 following:
12 • The access terminal shall create a ReducedSubnetMask by appending (128 -
13 UATISubnetMask + ReducedSubnetMaskOffset) ‘0’s to (UATISubnetMask –
14 ReducedSubnetMaskOffset) ‘1’s.
15 • If any of the following conditions is true, then the access terminal shall return a Failed
16 indication and transition to the Inactive State:
17 − The UATISubnetMask is not equal to the SubnetMask of the sector in the
18 active set, or
19 − The result of bitwise logical AND of the UATI and ReducedSubnetMask is
20 different from the result of bitwise logical AND of SectorID and
21 ReducedSubnetMask (where SectorID and SubnetMask correspond to the
22 sector in the active set).
23 Upon receiving an OverheadMessages.Updated indication, the access terminal shall
24 perform the following if MaxNoMonitorDistance is not zero:
25 • If (xo, yo) is (NULL, NULL), then the access terminal shall set (xo, yo) to (Longitude,
26 Latitude), where Longitude and Latitude are public data of the Overhead Messages
27 Protocol.
28 • If (xo, yo) is not (NULL, NULL), then the access terminal shall perform the following:
29 − The access terminal shall set (xn, yn) to (Longitude, Latitude), where Longitude
30 and Latitude are public data of the Overhead Messages Protocol.
31 − The access terminal shall compute NoMonitorDistance with an error of no
32 more than ±5% of its true value when |yo/14400| is less than 60 and with an
33 error of no more than ±7% of its true value when |yo/14400| is between 60
34 and 7019 using the expression
19xo and yo are given in units of 1/4 seconds. xo/14400 and yo/14400 are in units of degrees.
6-27
⎢ ⎡ ⎤
2 ⎥
⎛ π y ⎞
⎢ ⎢(xn − xo )× cos⎜ ⎟ ⎥ + [ y n − yo ] ⎥
2
× o
⎢ ⎣ ⎝ 180 14400 ⎠⎦ ⎥ 20
1 NoMonitorDistance = ⎢ ⎥
⎢ 16 ⎥
⎢ ⎥
⎣ ⎦
2 − The access terminal shall set (xo, yo) to (Longitude, Latitude), where Longitude
3 and Latitude are public data of the Overhead Messages Protocol.
4 − The access terminal shall return a Failed indication and transition to the
5 Inactive State if both of the following conditions are true:
6 + the computed value of NoMonitorDistance is greater than
7 MaxNoMonitorDistance, and
8 + one of the following conditions is true:
9 − the UATISubnetMask is not equal to the SubnetMask of the sector in the
10 active set, or
11 − the result of bitwise logical AND of the UATI and its subnet mask specified
12 by UATISubnetMask is different from the result of bitwise logical AND of
13 SectorID and its subnet mask specified by SubnetMask (where SectorID and
14 SubnetMask correspond to the sector in the active set).

16 The access network may send a UATIAssignment message at any time in this state. The
17 following are some of the possible triggers for sending a UATIAssignment message:
18 • Receiving RouteUpdate.ActiveSetUpdated indication,
19 • Receiving an UpdateUATI command,
20 • Receiving a UATIRequest message.
20 This equation is applicable if the access terminal does not cross longitude = 180 degree. Modified
equation that applies in all cases is as follows:
⎢ ⎡ ⎤
2 ⎥
⎛ π y ⎞
⎢ ⎢D longitude × cos⎜ ⎟⎥ + [y n − y o ] ⎥
2
× o
⎢ ⎣ ⎝ 180 14400 ⎠⎦ ⎥
NoMonitorDistance = ⎢ ⎥
⎢ 16 ⎥
⎢ ⎥
⎣ ⎦
x − xo
D longitude = x n − x o if n < 180
14400
xn − xo
D longitude = 360 × 14400 − x n − x o if ≥ 180
14400
6-28
1 The access network may return a SubnetChanged indication and send a UATIAssignment
2 message after reception of a RouteUpdate.ActiveSetUpdated indication. The triggers for
3 returning a SubnetChanged indication after reception of a RouteUpdate.ActiveSetUpdated
4 indication are outside the scope of this specification.
5 When the access network sends a UATIAssignment message, it shall perform the following:
6 • Assign a Unicast Access Terminal Identifier (UATI) to the access terminal for the session
7 and include it in a UATIAssignment message.
8 − If the UATIAssignment message is sent in response to a UATIRequest message,
9 the access network may include both UATI104 and UATISubnetMask. If the
10 access network does not include the UATI104 and UATISubnetMask fields in
11 the message, the UATI[127:24] is implicitly assigned to be equal to
12 SectorID[127:24], where SectorID corresponds to the sector that has received
13 the UATIRequest message.
14 − Otherwise, the access network shall include both UATI104 and
15 UATISubnetMask fields in the UATIAssignment message.
16 When the access network receives a UATIComplete message with the MessageSequence
17 field that is equal to the MessageSequence field of the UATIAssignment message that it has
18 sent, it shall return a UATIAssigned indication.
19 If the access network does not receive the UATIComplete message in response to the
20 corresponding UATIAssignment message within a certain time interval that is specified by
21 the access network21, it should re-transmit the UATIAssignment message. If the access
22 network does not receive the UATIComplete message after an implementation specific
23 number of re-transmissions of the UATIAssignment message, it shall return a Failed
24 indication and transition to the Inactive State.
26 7.3.7.2.16.3.7.2.1 UATIRequest
27 The access terminal sends the UATIRequest message to request that a UATI be assigned or
28 re-assigned to it by the access network.
29
Field Length (bits)
MessageID 8
TransactionID 8
31 TransactionID The access terminal shall increment this value modulo 256 for each
32 new UATIRequest message sent.
21 The value of this timeout is determined by the access network and specification of the timeout
value is outside the scope of this document.
6-29
Channels AC SLP Best Effort
2 7.3.7.2.26.3.7.2.2 UATIAssignment
3 The access network sends the UATIAssignment message to assign or re-assign a UATI to
4 the access terminal.
5
Field Length (bits)
MessageID 8
MessageSequence 8
Reserved1 7
SubnetIncluded 1
UATISubnetMask 0 or 8
UATI104 0 or 104
UATIColorCode 8
UATI024 24
UpperOldUATILength 4
Reserved2 4
7 MessageSequence The access network shall set this to 1 higher than the
8 MessageSequence field of the last UATIAssignment message (modulo
9 256) that it has sent to this access terminal.
10 Reserved1 The access network shall set this field to zero. The access terminal
11 shall ignore this field.
12 SubnetIncluded The access network shall set this field to ‘1’ if the UATI104 field and
13 UATISubnetMask fields are included in this message; otherwise, the
15 UATISubnetMask The access network shall omit this field if SubnetIncluded is set to
16 ‘0’. If included, the access network shall set this field to the number
17 of consecutive 1's in the subnet mask of the subnet to which the
18 assigned UATI belongs.
19 UATI104 The access network shall omit this field if SubnetIncluded is set to
20 ‘0’. If included, the access network shall set this field to UATI[127:24]
21 of the UATI that it is assigning to the access terminal.
6-30
1 UATIColorCode UATI Color Code. The access network shall set this field to the Color
2 Code associated with the subnet to which the UATI belongs.
3 UATI024 The access network shall set this field to UATI[23:0] of the UATI that
4 it is assigning to the access terminal.
5 UpperOldUATILength The access network shall set this field to the number of least
6 significant octets of OldUATI[127:24] that the access terminal is to
7 send in the UATIComplete message, in the range from 0 to 13,
8 inclusive.
9 Reserved2 The access network shall set this field to zero. The access terminal
11
12 7.3.7.2.36.3.7.2.3 UATIComplete
13 The access terminal sends this message to notify the access network that it has received
14 the UATIAssignment message.
15
Field Length (bits)
MessageID 8
MessageSequence 8
Reserved 4
UpperOldUATILength 4
UpperOldUATI 8 × UpperOldUATILength
17 MessageSequence The access terminal shall set this field to the MessageSequence field
18 of the UATIAssignment message whose receipt this message is
19 acknowledging.
20 Reserved The access terminal shall set this field to zero. The access network
22 UpperOldUATILength The access terminal shall set this field to the length of the
23 UpperOldUATI field in octets.
24 UpperOldUATI If UpperOldUATILength in the UATIAssignment message whose

25 receipt this message is acknowledging is not zero and OldUATI is not
26 NULL, the access terminal shall set this field to
6-31
1 OldUATI[23+UpperOldUATILength×8:24]. Otherwise, the access

2 terminal shall omit this field.
3
Channels AC RTC SLP Reliable Best Effort

22
4 7.3.7.2.46.3.7.2.4 HardwareIDRequest
5 The access network uses this message to query the access terminal of its Hardware ID
6 information.
Field Length (bits)
MessageID 8
TransactionID 8
9 HardwareIDRequest message sent.
10
11 7.3.7.2.56.3.7.2.5 HardwareIDResponse
12 The access terminal sends this message in response to the HardwareIDRequest message.
13
Field Length (bits)
MessageID 8
TransactionID 8
HardwareIDType 24
HardwareIDLength 8
HardwareIDValue 8×HardwareIDLength
16 the corresponding HardwareIDRequest message.
17 HardwareIDType The access terminal shall set this field according to Table 6.3.7.2-1.
6-32
1 Table 6.3.7.2-1. HardwareIDType encoding
HardwareIDType field
value Meaning
0x010000 Electronic Serial Number (ESN) ; see [3]
0x00ffff Mobile Equipment Identifier (MEID); see [3].23
0x00NNNN, where See [10]
NNNN is in the range
0x0000 to 0xfffe,
inclusive.
0xffffff Null
All other values Invalid
2 HardwareIDLength If HardwareIDType is not set to 0xFFFFFF, the access terminal shall

3 set this field to the length in octets of the HardwareIDValue field;
4 otherwise the access terminal shall set this field to 0x00.
5 HardwareIDValue The access terminal shall set this field to the unique ID (specified by
6 HardwareIDType) that has been assigned to the terminal by the
7 manufacturer.
8
Best
Channels AC RTC SLP Reliable24
Effort
9 7.3.7.2.66.3.7.2.6 AttributeUpdateRequest
10 The sender sends an AttributeUpdateRequest message to offer a set of attribute values for a
11 given attribute.
12
Field Length (bits)
MessageID 8
TransactionID 8
23 If an access terminal has an MEID, it uses this format. See [3].
6-33

4
5 7.3.7.2.76.3.7.2.7 AttributeUpdateAccept
8
Field Length (bits)
MessageID 8
TransactionID 8
12
13 7.3.7.2.86.3.7.2.8 AttributeUpdateReject
16
Field Length (bits)
MessageID 8
TransactionID 8
18 TransactionID The access network shall set this value to the TransactionID field of
19 the corresponding AttributeUpdateRequest message.
20
6-34
2 7.3.7.3.16.3.7.3.1 Commands
4 7.3.7.3.26.3.7.3.2 Indications
6 • RouteUpdate.IdleHO
7 • RouteUpdate.ActiveSetUpdated
8 • InitializationState.NetworkAcquired
9 • OverheadMessages.Updated
11 • AccessChannelMAC.TxEnded

14 Generic Attribute Update Protocol to update configurable attributes belonging to the
15 Default Address Management Protocol. If the value of the
16 SupportGAUPMaxNoMonitorDistance attribute is 0x01, then the access terminal and the
17 access network shall support the use of the Generic Attribute Update Protocol to update
18 values of the following attributes belonging to the Default Address Management Protocol:
19 • MaxNoMonitorDistance
20 If the value of the SupportGAUPMaxNoMonitorDistance attribute is not 0x01, the access
21 network shall not include the MaxNoMonitorDistance attribute in an
22 AttributeUpdateRequest message.
23 The access terminal shall not send an AttributeUpdateRequest message containing the
24 MaxNoMonitorDistance attribute.
25 The configurable simple attributes for this protocol are listed in Table 6.3.8-1. The access
26 terminal and access network shall use as defaults the values in Table 6.3.8-1 that are
6-35

ID
0x0000 The access terminal will not
transition to the Inactive state
based on distance.
0xff MaxNoMonitorDistance 0x0001 Maximum allowed distance

to 0xffff traveled without monitoring
overhead, beyond which the
access terminal will transition to
the Inactive state.
0x00 The session cannot be extricated
from the hardware that is
identified by the HardwareID.
0x01 The session can be extricated
0xfe HardwareSeparableFromSession from the hardware that is
identified by the HardwareID.
All Reserved
other
values
0x00 Use of Generic Attribute Update
Protocol to update
MaxNoMonitorDistance is not
supported.
SupportGAUPMaxNoMonitorDist
0xfd Protocol to update
ance
MaxNoMonitorDistance is
supported.
All Reserved
other
values
0x00 ReducedSubnetMaskOffset is
zero.
0x01 – Difference between the number
0x10 of consecutive ‘1’s in the subnet
0xfc ReducedSubnetMaskOffset mask and that in the reduced
subnet mask.
All Reserved
other
values
0x00 Use of secondary color codes is
0xfb SupportSecondaryColorCodes
not supported.
0x01 Use of secondary color codes is
supported.
6-36

ID
All Reserved
other
values
1

3

NADMPType Type field for this protocol. Table
2.5.4-1
NADMPDefault Subtype field for this protocol 0x0000
TADMPATResponse Time to receive UATIAssignment after sending 120
UATIRequest seconds
TADMPAddress The duration of time that the access terminal 180
declares an address match if it receives a seconds
message that is addressed using either the old or
the new UATI

6 This protocol defines the following parameter records in addition to the configuration
7 attributes for this protocol:
8 7.3.10.16.3.10.1 SessionSeed Parameter
9 Table 6.3.10.1-1. The Format of the Parameter Record for the SessionSeed Parameter
Field Length (bits)
ParameterType 8
Length 8
SessionSeed 32
13 SessionSeed This field shall be set to the value of the SessionSeed associated with
6-37
1 7.3.10.26.3.10.2 MessageSequence Parameter
2 Table 6.3.10.2-1. The Format of the Parameter Record for the MessageSequence
3 Parameter
Field Length (bits)
ParameterType 8
Length 8
MessageSequence 8
7 MessageSequence This field shall be set to the MessageSequence field of the last
8 UATIAssignment message that was sent by the source access
9 network.
10 7.3.10.36.3.10.3 HardwareID Parameter

11 The access network may include the HardwareID parameter Session State Information
12 Record to indicate the HardwareID received from the access terminal in a
13 HardwareIDResponse message (if available). If the value of the
14 HardwareSeparableFromSession attribute is not equal to 0x00 or the HardwareID from the
15 access terminal is not available (e.g., if the access network has not requested this
16 information from the access terminal), the access network shall omit this Session State
17 Information Record.
18 Table 6.3.10.3-1. The Format of the Parameter Record for the HardwareID Parameter
Field Length (bits)
ParameterType 8
Length 8
HardwareIDType 24
HardwareIDLength 8
HardwareIDValue 8×HardwareIDLength
6-38
1 HardwareIDType The access network shall set this field to the value of the
2 HardwareIDType field in the most recent HardwareIDResponse
3 message received from the access terminal.
4 HardwareIDLength The access network shall set this field to the value of the
5 HardwareIDLength field in the most recent HardwareIDResponse
7 HardwareIDValue The access network shall set this field to the value of the
8 HardwareIDValue field in the most recent HardwareIDResponse
6-39
1 7.46.4 Default Session Configuration Protocol
2 7.4.16.4.1 Overview
3 The Default Session Configuration Protocol provides for the negotiation and configuration
4 of the set of protocols used during a session.
5 This protocol supports two phases of negotiation:
6 • Access terminal initiated negotiation: In this phase negotiation exchanges are initiated
7 by the access terminal. This phase is used to negotiate the protocols that will be used
8 in the session and negotiate some of the protocols’ parameters (e.g., authentication key
9 lengths).
10 • Access network initiated negotiation: In this phase negotiation exchanges are initiated
11 by the access network. This phase is typically used to override default values used by
12 the negotiated protocols.
13 This protocol uses the Generic Configuration Protocol (see 13.7) procedures and messages
14 when performing the negotiation in each phase. Even if the access terminal requires the
15 use of a Session Configuration Protocol other than the Default Session Configuration
16 Protocol, it shall use the Default Session Configuration Protocol to negotiate the other
18 Example message flow diagrams for an extensive negotiation initiated by the access
19 terminal and a minimal negotiation initiated by the access network are shown in 6.4.9.
20 Additional protocols may be negotiated without further modifications to the Default Session
21 Configuration Protocol.
22 This protocol operates in one of four states:
23 • Inactive State: In this state, the protocol waits for an Activate command.
24 • AT Initiated State: In this state, negotiation is performed at the initiative of the access
25 terminal.
26 • AN Initiated State: In this state, negotiation is performed at the initiative of the access
27 network.
28 • Open State: In this state, the access terminal may initiate the session configuration
29 procedure at any time and the access network may request the access terminal to
30 initiate the session configuration at any time.
6-40
failure transitions not shown

Initial State
AT Initiated
Inactive State Rx Deactivate
State
Rx ConfigurationStart or Rx SoftConfigurationComplete
Rx Deactivate with Continue = ‘1’
Tx ConfigurationRequest or
Rx Deactivate Tx any InConfiguration msg.
Rx Activate Tx ConfigurationComplete
AN Initiated
Open State
State
Rx ConfigurationComplete
1
or Rx SoftconfigurationComplete with Continue = ‘0’

3 Terminal)
failure transitions not shown

Initial State
Rx Deactivate AT Initiated
Inactive State
State
Tx ConfigurationStart or
Rx ConfigurationRequest or
Rx Deactivate Rx any InConfiguration msg.
Rx Deactivate Tx SoftConfigurationComplete
with Continue = ‘1’
Rx Activate
Rx ConfigurationComplete
AN Initiated
Open State
State
Tx ConfigurationComplete
Tx SoftConfigurationComplete with Continue = ‘0’
4

6 Network)
8 7.4.2.16.4.2.1 Commands
6-41
1 • Activate
2 • Deactivate

5 • Reconfigured
6 • Failed
7 7.4.2.36.4.2.3 Public Data

10 • SessionConfigurationToken
11 • ConfigurationLock


18 Upon creation, the access terminal and the access network shall set the
19 SessionConfigurationToken to 0x0000.

23 • The value of the Protocol Type Attributes for this protocol instance shall be set to the
26 State.
27 • The access network and the access terminal shall set the ConfigurationLock to
28 UnLocked.
29 • The access terminal and the access network shall set the ConnectionState parameter to
30 Closed.
6-42
2 7.4.5.16.4.5.1 Procedures
3 This protocol does not have any procedures associated with the InConfiguration instance of
4 the protocol.

12 then the access terminal and the access network shall purge the InConfiguration
16 − The access terminal and the access network shall set the initial state of the
17 InConfiguration protocol instance to the Open State.
18 − The access terminal and the access network shall set the ConnectionState
19 parameter to Closed.
20 − The values of the public data of the InConfiguration protocol instance shall be
21 copied to the corresponding public data of the InUse protocol.
23 instance for the Session Configuration Protocol at the access terminal and the
24 access network.

28 This protocol does not define any messages corresponding to the InConfiguration instance
29 of the protocol.
31 7.4.6.16.4.6.1 Procedures
32 The Default Session Configuration Protocol uses the Generic Configuration Protocol (see
33 13.7) for configuration. All configuration messages sent by this protocol shall have their
34 Type field set to NSCPType.
35 If ConnectionState is Closed, and if PersonalityCount is greater than one, then the four
36 most significant bits of the SessionConfigurationToken field indicate the index of the
6-43
1 personality that is in use. If ConnectionState is Connected, and if PersonalityCount is

2 greater than one, then the four most significant bits of the SessionConfigurationToken field
3 indicate the index of the personality that will be in use after ConnectionState changes to
4 Closed. The rules for setting the twelve least significant bits of the
5 SessionConfigurationToken field are outside the scope of this specification.
6 The Default Session Configuration Protocol allows for the negotiation and storage of up to
7 PersonalityCount personalities. A personality is defined as a complete set of negotiated
8 protocol subtypes, application subtypes, attribute values, and public data that can be used
9 as the InUse instance of the protocols and applications. Only one personality is in use at a
10 time. The total number of personalities shall not exceed PersonalityCount. Each personality
11 is identified by its PersonalityIndex. Valid values of PersonalityIndex are from zero to
12 PersonalityCount – 1, inclusive. Personality with index zero is defined as the Main
13 Personality.
14 If the access terminal supports the Enhanced Forward Traffic Channel MAC Protocol or the
15 Subtype 2 Reverse Traffic Channel MAC Protocol, the access terminal shall support values
16 for the PersonalityCount attribute less than or equal to 0x0004. If the access terminal
17 supports a value for the PersonalityCount attribute greater than 0x0001, then access
18 terminal shall support all values for the SupportGAUPSessionConfigurationToken attribute
19 less than or equal to 0x0001. If the access terminal supports a value for the
20 PersonalityCount attribute greater than 0x0001, the access terminal shall support all
21 values for the SupportConfigurationLock attribute less than or equal to 0x0001.
22 If HardLink subtype is negotiated for a protocol Type, then the protocol subtype, all Session
23 State Information Records (including all attributes), and public data (except as noted) of
24 this protocol Type in the personality under consideration shall be the same as the
25 corresponding protocol subtype, Session State Information Records, and public data of the
26 corresponding protocol Type in the Main Personality and vice versa.
27 When performing the procedures for a protocol with HardLink subtype, the access terminal
28 and the access network shall perform the corresponding procedures for the corresponding
29 protocol subtype in the Main Personality25. When comparing whether two protocols have
30 the same subtype, a HardLink protocol shall be treated as having the same subtype as the
31 corresponding protocol subtype in the Main Personality.
32 The protocol subtype for the Session Configuration Protocol shall be set to HardLink
33 subtype in all personalities with PersonalityIndex greater than zero. The protocol subtype
34 for the Address Management Protocol shall be set to HardLink subtype in all personalities
35 with PersonalityIndex greater than zero. Even if the protocol subtype of the Session
36 Configuration Protocol is HardLink, the values of the Protocol Type attributes in the
37 personality under consideration and the main personality may be different. If HardLink
38 subtype is negotiated for a protocol in the Stream Layer, then the protocol subtype, Session
39 State Information Records, and public data of the protocol as well as Session State
40 Information Records and public data of applications bound to its streams shall be the same
25 i.e. the HardLink subtype protocol shall behave as if it were the same subtype as the
corresponding protocol in the Main Personality.
6-44
1 as the corresponding protocol subtype, Session State Information Records, and public data
2 in the Main Personality and vice versa. The access terminal and the access network shall
3 not negotiate HardLink subtype for protocols in the main personality.
4 7.4.6.1.16.4.6.1.1 Processing the Activate Command

5 If the protocol receives the Activate command in the Inactive State, it shall transition to the
6 Open State.
7 If this command is received in any other state it shall be ignored.
8 7.4.6.1.26.4.6.1.2 Processing the Deactivate Command

9 If the protocol receives the Deactivate command in the Inactive State it shall be ignored.
10 If the protocol receives this command in the AT Initiated State, AN Initiated State, or Open
11 State, it shall transition to the Inactive State.
12 7.4.6.1.36.4.6.1.3 Maintaining the ConnectionState Parameter

13 Upon receiving an IdleState.ConnectionOpened indication, the access terminal and the
14 access network shall set ConnectionState to Connected. Upon receiving a
15 ConnectedState.ConnectionClosed or RouteUpdate.ConnectionLost indication, the access
16 network shall set ConnectionState to Closed. Upon receiving a
17 ConnectedState.ConnectionClosed indication, the access terminal shall set ConnectionState
18 to Closed.
19 7.4.6.1.46.4.6.1.4 Maintaining the ConfigurationLock parameter

20 The access terminal and the access network shall maintain a parameter called
21 ConfigurationLock. If the value of the SupportConfigurationLock attribute is 0x0001, then
22 the access terminal and the access network shall support the processing of the
23 LockConfiguration, LockConfigurationAck, UnLockConfiguration, and
24 UnLockConfigurationAck messages. If the value of the SupportConfigurationLock attribute
25 is not 0x0001, then the access network shall not transmit a LockConfiguration or
26 UnLockConfiguration message.
27 If the access network sends a LockConfiguration message, it shall set ConfigurationLock to
28 Locked. If the access network sends an UnLockConfiguration message, it shall set
29 ConfigurationLock to UnLocked.
30 If the access terminal receives a LockConfiguration message, then the access terminal shall
31 respond with a LockConfigurationAck message and shall set ConfigurationLock to Locked.
32 If the access terminal receives an UnLockConfiguration message, then the access terminal
33 shall respond with an UnLockConfigurationAck message and shall set ConfigurationLock to
34 UnLocked.
35 Upon receiving a ConnectedState.ConnectionClosed or RouteUpdate.ConnectionLost
36 indication, the access network shall set ConfigurationLock to UnLocked. Upon receiving a
37 ConnectedState.ConnectionClosed indication, the access terminal shall set
38 ConfigurationLock to UnLocked.
6-45
1 7.4.6.1.56.4.6.1.5 Inactive State

2 Upon entering this state, the protocol shall set the SessionConfigurationToken to 0x0000.
3 In this state the protocol waits for the Activate command. See 6.4.6.1.1 for processing of the
4 Activate command in this state.
5 7.4.6.1.66.4.6.1.6 AT Initiated State

6 During the AT Initiated State of the Default Session Configuration Protocol the access
7 terminal and the access network use the Generic Configuration Protocol (see 13.7) with the
8 access terminal being the initiator of each exchange. The access terminal and the access
9 network use the ConfigurationRequest/ConfigurationResponse exchange defined in 13.7 to
10 select the protocols and configure their associated parameters that will be used for the
11 session.
12 Also, the access terminal may request restoring a previously established session in this
13 state.
14 The protocol in the access terminal or the access network shall return a Failed indication
15 and transition to the Inactive state, if any of the negotiated protocols declares a failure.

17 Upon entering this state, the access terminal shall
18 • Create an InConfiguration protocol instance with the same protocol subtype as that of
19 the InUse protocol instance for each of the protocols,
20 • For each stream that is bound to an application, create an InConfiguration application
21 instance with the same application subtype as that of the InUse application instance
22 corresponding to that stream,
23 • For each virtual stream that is bound to an application, create an InConfiguration
24 application instance with the same application subtype as that of the InUse application
25 instance corresponding to that virtual stream, and
26 • For each protocol Type, set the fall-back value as well as the current value of the InUse
27 Session Configuration protocol’s Protocol Type Attributes (see Table 6.4.7.1-1) to the
28 subtype values given as public data by the corresponding InConfiguration instance of
29 each protocol.
30 If the access terminal chooses to request restoring a prior session, it shall perform the
31 following in the order specified:
32 • The access terminal shall construct a 32-bit pseudo random number, Nonce.
33 • The access terminal shall temporarily configure the protocols within the Security Layer
34 with the parameters (i.e., the session key and all the negotiated protocols and attributes
35 in the security layer) associated with the prior session.
6-46
1 • The access terminal shall supply the Nonce, to the security layer of the prior session as
2 if the Nonce is the payload to be transmitted on the Access Channel. The access
3 terminal shall set all the unspecified parameters needed by the protocols in the
4 Security Layer to zero for the purpose of generating this Security Layer Packet.
5 • The access terminal shall restore the Security Layer to its previous configuration.
6 • The access terminal shall set the SecurityPacket variable to the Security Layer Packet
7 constructed in the previous step.
8 • The access terminal shall send the UATI corresponding to the prior session and the
9 SecurityPacket variables as a complex attribute (see 6.4.7.2) in a ConfigurationRequest
10 message.
11 The access terminal may send the access network ConfigurationRequest messages,
12 requesting the use of specific protocols per the Generic Configuration Protocol.
13 The access terminal shall include in the ConfigurationRequest messages all supported non-
14 default subtypes of all protocols Types. If the access terminal includes in a
15 ConfigurationRequest message a non-default subtype or HardLink subtype of a protocol,
16 then the access terminal should also include in that ConfigurationRequest message the
17 default subtype of the protocol.26 The access terminal need not include the HardLink
18 subtype in the ConfigurationRequest messages. If the access terminal supports a value of
19 PersonalityCount greater than 0x0001, then the access terminal shall send a
20 ConfigurationRequest messages containing the ATSupportedApplicationSubtypes attribute.
21 If the access terminal sends a ConfigurationRequest message containing the
22 ATSupportedApplicationSubtypes attribute, then the access terminal shall include in this
23 attribute all the Application Subtypes supported by the access terminal.
24 The access terminal shall process the ConfigurationResponse messages it receives per the
25 Generic Configuration Protocol.
26 Following the receipt of a ConfigurationResponse message, the access terminal may:
27 • Send another ConfigurationRequest message attempting to negotiate a different
28 protocol subtype for the protocol Type specified in the ConfigurationResponse message.
29 • Use the protocol configuration procedures defined by the protocol to perform access
30 terminal-initiated parameter configuration.
31 Once the access terminal and the access network agree upon a new protocol subtype for a
32 protocol Type (per the Generic Configuration Protocol), the access terminal shall purge the
33 existing InConfiguration protocol instance corresponding to the protocol type and subtype
34 and create an InConfiguration protocol instance corresponding to the agreed upon protocol
35 subtype.
26 If the access terminal does not propose the default protocol subtype and the fall-back value of the
protocol subtype is non-default, then the access terminal and the access network would not be able
to negotiate the default protocol subtype during the AT Initiated State of the Default Session
Configuration Protocol.
6-47
1 If after performing access terminal-initiated parameter configuration, the access terminal

2 requires the use of a different protocol subtype for this protocol Type, the access terminal
3 may send the access network a new ConfigurationRequest message.
4 If the protocol in access terminal requires no further negotiation of protocols or
5 configuration of negotiated protocols, it shall send a ConfigurationComplete message to the
6 access network and transition to the AN Initiated State.
7 If the access terminal receives an AttributeUpdateRequest message requesting to update
8 the value of the Session Configuration Token in this state, then the access terminal shall
9 ignore the message.

11 Upon entering this state, the access network shall
12 • Create an InConfiguration protocol instance with the same protocol subtype as that of
13 the InUse protocol instance for each of the protocols,
14 • For each stream that is bound to an application, create an InConfiguration application
15 instance with the same application subtype as that of the InUse application instance
16 corresponding to that stream,
17 • For each virtual stream that is bound to an application, create an InConfiguration
18 application instance with the same application subtype as that of the InUse application
19 instance corresponding to that virtual stream, and
20 • For each protocol Type, set the fall-back value as well as the current value of the InUse
21 Session Configuration protocol’s Protocol Type Attributes (see Table 6.4.7.1-1) to the
22 subtype values given as public data by the corresponding InConfiguration instance of
23 each protocol.
24 The access network should re-send the ConfigurationStart message if it has not received
25 either a ConfigurationRequest message or a ConfigurationComplete message from the
26 access terminal within an implementation defined time interval after sending the
27 ConfigurationStart message.
28 If the access network receives a ConfigurationRequest message from the access terminal, it
29 shall process it and shall respond with a ConfigurationResponse message per the Generic
31 Once the access network sends a ConfigurationResponse message for a particular protocol,
32 it shall be ready to execute the access terminal-initiated configuration procedures that are
33 particular to that protocol.
35 protocol Type (per the Generic Configuration Protocol), the access network shall purge the
38 subtype.
39 If the protocol in the access network receives a ConfigurationComplete message, it shall
40 transition to the AN Initiated State.
6-48
1 The access network shall not send an AttributeUpdateRequest message requesting to

2 update the value of the Session Configuration Token in this state.27
3 7.4.6.1.76.4.6.1.7 AN Initiated State

4 During the AN Initiated State of the protocol, the access network and the access terminal
5 execute the access network-initiated configuration procedures specified by each negotiated
6 protocol. These procedures typically allow the access network to override default values
7 otherwise used by the access terminal.
8 The protocol in the access terminal or the access network shall return a Failed indication
9 and transition to the Inactive state, if any of the negotiated protocols declares a failure.

11 In this protocol state the access terminal shall be ready to execute the access network-
12 initiated configuration procedures particular to each protocol used during the session.
13 If the access terminal receives a ConfigurationRequest message from the access network, it
14 shall process it and shall respond with a ConfigurationResponse message according to the
15 Generic Configuration Protocol.
17 protocol Type (per the Generic Configuration Protocol), the access terminal shall purge the
20 subtype.
21 If the access terminal receives an AttributeUpdateRequest message requesting to update
22 the value of the Session Configuration Token in this state, then the access terminal shall
23 ignore the message.
24 If the access terminal receives a SoftConfigurationComplete message, it shall perform the
25 following:
26 • The Session Configuration Protocol shall store the InConfiguration protocol and
27 application instances as a personality that is identified by the PersonalityIndexStore
28 field of the SoftConfigurationComplete message.
29 • If the Continue field of the SoftConfigurationComplete message is set to ‘1’, then the
30 access terminal shall transition to the AT Initiated State.
31 • Otherwise, the access terminal shall perform the following:
32 {
33 If the Commit field of the SoftConfigurationComplete message is set to ‘1’, then the
34 access terminal shall perform the following:
27 If the access network wants to switch personalities, the access network can close the Connection
and then send an AttributeUpdateRequest message requesting to update the value of the Session
Configuration Token.
6-49
1 {
2 Issue an AirLinkManagement.CloseConnection command.
3 Return a Reconfigured indication.
4 When ConnectionState is Closed:
5 {
6 If as a result of ConfigurationRequest/ConfigurationResponse exchange a
7 PriorSession attribute with a non-zero Restore field is agreed upon, then all the
8 session state information (except the SessionConfigurationToken which is set to the
9 value specified in the SoftConfigurationComplete message) corresponding to the
10 session specified by the PriorSession attribute shall take effect.
11 Otherwise,
12 {
13 The Session Configuration Protocol shall set the protocols and attributes of
14 the InConfiguration protocol instances to the corresponding protocols and
15 attribute values of the stored personality with index equal to the value of the
16 four most significant bits of the SessionConfigurationToken.
17 The Session Configuration Protocol shall direct all the InConfiguration
18 protocol instances to execute their Commit procedures.
19 }
20 }
21 }
22 The protocol shall set the SessionConfigurationToken public data to the value specified
23 in the SoftConfigurationComplete message.
24 Transition to the Open State.
25 }
26 If the access terminal receives a ConfigurationComplete message it shall perform the
27 following:
29 • Return a Reconfigured indication.
31 • When ConnectionState is Closed:
32 − The protocol shall set the SessionConfigurationToken public data to the value
33 specified in the ConfigurationComplete message,
34 − If as a result of ConfigurationRequest/ConfigurationResponse exchange a
35 PriorSession attribute with a non-zero Restore field is agreed upon, then
6-50
1 + all the session state information (except the SessionConfigurationToken which

2 is set to the value specified in the ConfigurationComplete message)
3 corresponding to the session specified by the PriorSession attribute shall take
4 effect.
5 − Otherwise,
6 + The Session Configuration Protocol shall direct all the InConfiguration protocol
7 instances to execute their Commit procedures.

9 In this protocol state, the access network may execute the access network-initiated
10 configuration procedures that are particular to each protocol used during the session.
11 The access network shall not send an AttributeUpdateRequest requesting to update the
12 value of the Session Configuration Token message in this state.28 The access network shall
13 not send the ATSupportedApplicationSubtypes attribute in the ConfigurationRequest
14 message.
15 If the access network chooses to negotiate a different Session Configuration Protocol, it
16 shall initiate the Session Configuration Protocol selection (i.e., sending a
17 ConfigurationRequest message specifying protocol Type of NSCPType) prior to selection of any
18 other protocol.
19 The access network may set the SessionConfigurationToken field of the
20 ConfigurationComplete or SoftConfigurationComplete message to reflect the selected
21 protocols and the negotiation parameters associated with the negotiated protocols. If
22 PersonalityCount is greater than one, then the four most significant bits of the
23 SessionConfigurationToken field shall be set to the index of the personality that is to take
24 effect when the protocol transitions to the Open State. If PersonalityCount is greater than
25 one, and if a PriorSession attribute with Restore field set to ‘1’ is negotiated, then the
26 access network shall set the four most significant bits of the Session Configuration Token
27 to the corresponding bits of the Session Configuration Token associated with the prior
28 session. The rules for setting the twelve least significant bits of the Session Configuration
29 Token are outside the scope of this specification.
31 protocol Type (per the Generic Configuration Protocol), the access network shall purge the
33 and create an InConfiguration protocol instance corresponding to the agreed upon protocol.
34 The access network shall not send a SoftConfigurationComplete message if
35 PersonalityCount is one. The access network shall not send a ConfigurationComplete
36 message if PersonalityCount is greater than one.
28 If the access network wants to switch personalities, the access network can close the connection
and then send an AttributeUpdateRequest message requesting to update the value of the
SessionConfigurationToken.
6-51
1 The access network shall send a SoftConfigurationComplete message with Continue field
2 set to ‘1’ if all of the following conditions are satisfied:
3 • PersonalityCount is greater than one.
4 • The protocol in the access network requires no further negotiation of protocols or
5 configuration of negotiated protocols for this personality.
6 • The access network wants to create and store more personalities.
7 The access network shall send a SoftConfigurationComplete message with Continue field
8 set to ‘0’ if all of the following conditions are satisfied:
9 • PersonalityCount is greater than one.
10 • The protocol in the access network requires no further negotiation of protocols or
11 configuration of negotiated protocols for this personality.
12 • The protocol in the access network requires no further creation and storing of
13 personalities.
14 The access network shall not set the PersonalityIndexStore field of the
15 SoftConfigurationComplete message to zero if HardLink protocol subtype has been
16 negotiated for one or more of the InConfiguration protocol instances. The access network
17 shall set the PersonalityIndexStore field of the SoftConfigurationComplete message to zero
18 if a Personality with index zero is not already stored.
19 The access network shall set Commit field of the SoftConfigurationComplete message to ‘1’
20 if any of the following conditions is true:
21 • The session configuration has resulted in any change to the personality that is
22 currently in use.
23 • The four most significant bits of the SessionConfigurationToken field of the
24 SoftConfigurationComplete message are different from those of the previous Session
25 Configuration Token.
26 • A PriorSession attribute with a non-zero Restore field is agreed upon during the session
27 configuration.
28 Upon sending a SoftConfigurationComplete message, the access network shall perform the
29 following:
30 • The Session Configuration Protocol shall store the InConfiguration protocol and
31 application instances as a personality that is identified by the PersonalityIndexStore
32 field of the SoftConfigurationComplete message.
33 • If the Continue field of the SoftConfigurationComplete message is set to ‘1’, then the
34 access network shall transition to the AT Initiated State.
35 • Otherwise, the access network shall perform the following:
36 {
37 If the Commit field of the SoftConfigurationComplete message is set to ‘1’, then the
38 access network shall perform the following:
6-52
1 {
2 Issue an AirLinkManagement.CloseConnection command.
3 Return a Reconfigured indication.
4 When ConnectionState is Closed:
5 {
6 If as a result of ConfigurationRequest/ConfigurationResponse exchange a
8 session state information (except the SessionConfigurationToken which is set to the
9 value specified in the SoftConfigurationComplete message) corresponding to the
10 session specified by the PriorSession attribute shall take effect.
11 Otherwise,
12 {
13 The Session Configuration Protocol shall set the protocols and attributes of
14 the InConfiguration protocol instances to the corresponding protocols and
15 attribute values of the stored personality with index equal to the value of the
16 four most significant bits of the SessionConfigurationToken.
17 The Session Configuration Protocol shall direct all the InConfiguration
18 protocol instances to execute their Commit procedures.
19 }
20 }
21 }
22 The protocol shall set the SessionConfigurationToken public data to the value specified
23 in the SoftConfigurationComplete message.
24 Transition to the Open State.
25 }
26 If the protocol in the access network requires no further negotiation of protocols or
27 configuration of negotiated protocols and if PersonalityCount is one, then the access
29 • Send a ConfigurationComplete message to the access terminal.
33 • When ConnectionState is Closed:
34 − The protocol shall set the SessionConfigurationToken public data to the value
35 specified in the ConfigurationComplete message, and
6-53
1 − If as a result of ConfigurationRequest/ConfigurationResponse exchange a

3 session state information (except the SessionConfigurationToken which is set
4 to the value specified in the ConfigurationComplete message) corresponding to
5 the session specified by the PriorSession attribute shall take effect.
6 − Otherwise,
7 + The protocol shall set the SessionConfigurationToken public data to the value
8 specified in the ConfigurationComplete message, and
9 + The Session Configuration Protocol shall direct all the InConfiguration protocol
11 7.4.6.1.86.4.6.1.8 Open State

12 In this protocol state the access terminal and the access network use the negotiated
13 protocols to exchange data and signaling in accordance with the requirements of each
14 protocol.

16 While in this state, the access terminal may send a ConfigurationRequest message to start
17 the negotiation process (e.g., the access terminal may send this message to negotiate a new
18 stream) if the value of the ConfigurationLock parameter is UnLocked. The access terminal
19 shall not start a negotiation process if the value of the ConfigurationLock parameter is
20 Locked. Starting the configuration process is defined as sending a ConfigurationRequest
21 message, or AttributeUpdateRequest message defined by any protocol, or sending any other
22 message that will initiate a process to change attribute values.
23 The access terminal shall ignore a ConfigurationComplete or SoftConfigurationComplete
24 message received in this state.
25 The protocol in the access terminal shall transition to the AT Initiated State when any of
26 the following occurs:
27 • The protocol in the access terminal receives a ConfigurationStart message,
28 • The protocol in the access terminal sends a ConfigurationRequest message, or
29 • The access terminal sends a message associated with the InConfiguration instance of
30 any other protocol.
31 If PersonalityCount is greater than one, and if the four most significant bits of this Session
32 Configuration Token are different from the index of the current Personality, and if
33 ConnectionState is Closed, then the access terminal shall perform the following:
35 • The Session Configuration Protocol shall set the protocol subtypes, application
36 subtypes, and attributes of the stored copy of the personality that is currently in use to
37 the corresponding protocol subtypes, application subtypes, and attribute values of the
38 InUse instances of all protocols and applications.
6-54
2 subtypes, and attributes of the InConfiguration instances of all protocols and
3 applications to the corresponding protocol subtypes, application subtypes, and
4 attribute values of the stored personality with index equal to the four most significant
5 bits of the SessionConfigurationToken.
6 • The Session Configuration Protocol shall direct all the InConfiguration protocol
8 If the access terminal receives an AttributeUpdateAccept message in response to an
9 AttributeUpdateRequest message proposing a value of the PriorSession attribute with non-
10 zero Restore field, then the access terminal shall perform the following:
11 − If ConnectionState is Opened, then issue an
12 AirLinkManagement.CloseConnection command.
13 − Return a Reconfigured indication.
14 − When ConnectionState is Closed, all the Session State Information
15 corresponding to the session specified by the PriorSession attribute proposed
16 in the AttributeUpdateRequest message shall take effect.
17 If the access terminal receives a DeletePersonality message, then the access terminal shall
18 perform the following:
19 • Delete stored personalities corresponding to the PersonalityIndex fields of the
20 DeletePersonality message.
21 • Send a DeletePersonalityAck message.

23 While in this state, the access network may send a ConfigurationStart message to start the
24 negotiation process (e.g., the access network may send this message to negotiate a new
25 stream) if the value of the ConfigurationLock parameter is UnLocked. The access network
26 shall not start a negotiation process if the value of the ConfigurationLock parameter is
27 Locked. Starting the configuration process is defined as sending a ConfigurationRequest
28 message, or AttributeUpdateRequest message defined by any protocol, or sending any other
29 message that will initiate a process to change attribute values.
30 The protocol in the access network shall transition to the AT Initiated State when any of the
31 following occurs:
32 • The protocol in the access network sends a ConfigurationStart message,
33 • The protocol in the access network receives a ConfigurationRequest message, or
34 • The access network receives a message associated with the InConfiguration instance of
35 any other protocol.
36 If PersonalityCount is greater than one and if the four most significant bits of this Session
37 Configuration Token are different from the index of the current Personality, and if
38 ConnectionState is Closed, then the access network shall perform the following:
6-55
2 subtypes, and attributes of the stored copy of the personality that is currently in use to
3 the corresponding protocol subtypes, application subtypes, and attribute values of the
4 InUse instances of all protocols and applications.
6 subtypes, and attributes of the InConfiguration instances of all protocols and
7 applications to the corresponding protocol subtypes, application subtypes, and
8 attribute values of the stored personality with index equal to the four most significant
9 bits of the Session Configuration Token.
10 • The Session Configuration Protocol shall direct all the InConfiguration protocol
12 If the access network sends an AttributeUpdateAccept message in response to an
13 AttributeUpdateRequest message proposing a value of the PriorSession attribute with non-
14 zero Restore field, then the access network shall perform the following:
15 − If ConnectionState is Opened, then issue an
16 AirLinkManagement.CloseConnection command.
17 − Return a Reconfigured indication.
18 − When ConnectionState is Closed, all the Session State Information
19 corresponding to the session specified by the PriorSession attribute proposed
20 in the AttributeUpdateRequest message shall take effect.
21 While in this state, the access network may send a DeletePersonality message instructing
22 the access terminal to delete stored personalities. Upon receiving a DeletePersonalityAck
23 message in response to the DeletePersonality message, the access network shall delete
24 stored personalities corresponding to the PersonalityIndex fields of the DeletePersonality
25 message.
26 The access network shall not send the DeletePersonality message if PersonalityCount is
27 equal to 0x0001. The PersonalityIndex field of the DeletePersonality message shall not be
28 set to the index of the personality that is currently in use. The PersonalityIndex field of the
29 DeletePersonality message shall not be set to the zero.
31 7.4.6.2.16.4.6.2.1 ConfigurationComplete
32 The sender sends the ConfigurationComplete message to indicate that it has completed the
33 negotiation procedures performed at its initiative.
34
6-56
Field Length (bits)

MessageID 8
TransactionID 8
SessionConfigurationToken 0 or 16
2 TransactionID The access terminal shall increment this value for each new
3 ConfigurationComplete message sent. The access network shall set
4 this field to the value of TransactionID included in the last
5 ConfigurationComplete message received from the access terminal.
6 SessionConfigurationToken
7 Session Configuration Token. The access terminal shall omit this
8 field. The access network shall include this field. The access network
9 may set this field to a 16-bit value that reflects the selected protocols
10 and the negotiation parameters associated with the negotiated
11 protocols.
12
13 7.4.6.2.26.4.6.2.2 ConfigurationStart
14 The access network sends this message to start a session configuration process.
15
Field Length (bits)
MessageID 8

17
20
6-57
Field Length (bits)
MessageID 8
TransactionID 8
8
Field Length (bits)
MessageID 8
TransactionID 8

17
6-58
1 7.4.6.2.56.4.6.2.5 SoftConfigurationComplete
2 The access network sends the SoftConfigurationComplete message to indicate that it has
3 completed the negotiation procedures for this personality.
4
Field Length (bits)

MessageID 8
TransactionID 8
PersonalityIndexStore 4
Continue 1
Commit 0 or 1
SessionConfigurationToken 0 or 16
6 TransactionID The access network shall set this field to the value of TransactionID
7 included in the last ConfigurationComplete message received from
9 PersonalityIndexStore
10 The access network shall set this field to the index of the personality
11 in which the InConfiguration instances of protocols and applications
12 are to be stored, in the range from zero to PersonalityCount – 1,
13 inclusive.
14 Continue If the access network wants to configure more Personalities, then the
17 Commit If the Continue field is equal to ‘1’, then the access network shall
18 omit this field. Otherwise, the access network shall set this field as
19 follows:
20 If the Commit procedure is required, then the access network shall
22 to ‘0’.
24 Session Configuration Token. If the Continue field is equal to ‘1’, then
6-59
1 the access network shall omit this field. Otherwise, the access
2 network shall include this field.
3 If the Commit field is set to ‘1’, then the four most significant bits of
4 this field shall be set to the index of the Personality that is to be
5 committed, in the range from zero to PersonalityCount – 1, inclusive.
6 Otherwise, the four most significant bits of this field shall be set to
7 the index of the Personality that is currently in use, in the range from
8 zero to PersonalityCount – 1, inclusive.
9 The access network may set the 12 least significant bits of this field
10 to a value that reflects the selected protocols and the negotiation
11 parameters associated with the negotiated protocols.
13 entire message equal to an integer number of octets. The access
14 network shall set these bits to ‘0’. The access terminal shall ignore
15 this field.
16
17 7.4.6.2.66.4.6.2.6 LockConfiguration
18 The access network sends the LockConfiguration message to set the ConfigurationLock
19 parameter in the access terminal to Locked.
20
Field Length (bits)

MessageID 8
TransactionID 8
23 the TransactionID field of the last LockConfiguration message sent by
24 the access network. If this is the first LockConfiguration message
25 sent by the access network, then the access network shall set this
26 field to zero.
27
28 7.4.6.2.76.4.6.2.7 LockConfigurationAck
29 The access terminal sends the LockConfigurationAck message to acknowledge the receipt
30 of a LockConfiguration message.
6-60
Field Length (bits)

MessageID 8
TransactionID 8
4 the LockConfiguration message that is being acknowledged.
5
6 7.4.6.2.86.4.6.2.8 UnLockConfiguration
7 The access network sends the UnLockConfiguration message to set the ConfigurationLock
8 parameter in the access terminal to UnLocked.
9
Field Length (bits)

MessageID 8
TransactionID 8
12 the TransactionID field of the last UnLockConfiguration message sent
13 by the access network. If this is the first UnLockConfiguration
14 message sent by the access network, then the access network shall
15 set this field to zero.
16
17 7.4.6.2.96.4.6.2.9 UnLockConfigurationAck
18 The access terminal sends the UnLockConfigurationAck message to acknowledge the
19 receipt of an UnLockConfiguration message.
20
Field Length (bits)

MessageID 8
TransactionID 8
6-61
2 the UnLockConfiguration message that is being acknowledged.
3
4 7.4.6.2.106.4.6.2.10 DeletePersonality
5 The access network sends a DeletePersonality message to delete a stored personalities
6 corresponding to the PersonalityIndex fields in this message.
7
Field Length (bits)
MessageID 8
TransactionID 8
PersonalityCount 4
PersonalityCount instances of the following record
PersonalityIndex 4
Reserved 0 or 4 (as needed)
10 DeletePersonality message sent.
11 PersonalityCount The access network shall set this field to the number of
12 PersonalityIndex fields in this message.
13 PersonalityIndex The access network shall set this field to the personality which the
14 access network intends to delete.
15 Reserved The access network shall set these bits to ‘0’. The access terminal
17
Reliable on FTC
Channels FTC CC SLP
Best Effort on CC
18 7.4.6.2.116.4.6.2.11 DeletePersonalityAck
19 The access terminal sends a DeletePersonalityAck message to acknowledge reception of the
20 DeletePersonality message.
21
6-62
Field Length (bits)
MessageID 8
TransactionID 8
3 the corresponding DeletePersonality message.
4
Reliable on RTC
Channels AC RTC SLP
Best Effort on AC
7 given attribute.
8
Field Length (bits)
MessageID 8
TransactionID 8

13
Reliable on FTC and RTC

Channels CC AC FTC RTC SLP
Best Effort on CC and AC
17
6-63
Field Length (bits)
MessageID 8
TransactionID 8
4
Reliable on FTC and RTC

Channels CC AC FTC RTC SLP
Best Effort on CC and AC
8
Field Length (bits)
MessageID 8
TransactionID 8
12
Reliable on FTC
Channels FTC CC SLP
Best Effort on CC
14 7.4.6.3.16.4.6.3.1 Commands
16 • AirLinkManagement.CloseConnection
17 7.4.6.3.26.4.6.3.2 Indications
18 This protocol registers to receive the following indication:
6-64

7 If the value of the SupportGAUPSessionConfigurationToken attribute is 0x0001, then the
8 access terminal and the access network shall support the use of the Generic Attribute
9 Update Protocol to configure values of the SessionConfigurationToken attribute. The access
10 network may include the SessionContributionTokenSessionConfigurationToken attribute in
11 an AttributeUpdateRequest message sent on the Control Channel.
12 If the value of the SupportGAUPSessionConfigurationToken attribute is not 0x0001, then
13 the access network and the access terminal shall not use the Generic Attribute Update
14 Protocol to configure the value of the SessionConfigurationToken attribute.
15 The access terminal shall not include the SessionConfigurationToken in an
17 The access network shall not include the PriorSession attribute in an
19 If the Overhead Messages Protocol does not advertise PriorSessionGAUP public data, or if
20 the PriorSessionGAUP public data of the Overhead Messages Protocol is set to ‘0’, then the
21 access terminal shall not include the PriorSession attribute in an AttributeUpdateRequest
22 message. If the PriorSessionGAUP public data of the Overhead Messages Protocol is set to
23 ‘1’, then the access terminal may include the PriorSession attribute in an
24 AttributeUpdateRequest message. The access terminal may include the PriorSession
25 attribute in an AttributeUpdateRequest message sent on the Access Channel.

27 The following attribute-value pairs are defined (see 13.3 for attribute record format). All
28 attribute fields for the Default Session Configuration Protocol are two octets in length.
29 Simple Attributes
30 The simple configurable attributes are listed in Table 6.4.7.1-1. All these attributes are
31 simple. The Attribute ID fields for all these attributes are two octets in length and the value
32 fields for these attributes are two octets in length.
6-65
1 Table 6.4.7.1-1. Simple Configurable Attributes

ID
0x00NN Protocol Type, where NN is the 0x0000 Default Protocol
hexadecimal Protocol Type value Subtype.
excluding values 0x14, 0x15, 0x16,
0xfffe HardLink Protocol
and 0x17.29
Subtype
0x0000 – 0xfffd, Protocol Subtype.
0xffff
0x0100 SessionConfigurationToken 0x000030 Default Session
Configuration
Token.
0x0001 – 0xffff Session
Configuration
Token
0x0101 SupportGAUPSessionConfiguration 0x0000 Use of Generic
Token Attribute Update
Protocol to update
the Session
Configuration
Token is not
supported by
default.
0x0001 Use of Generic
Attribute Update
Protocol to update
the Session
Configuration
Token is
supported.
All other values Reserved
0x0110 PersonalityCount 0x0001 Maximum of one
personality is
supported
0x0002 – 0x0010 Maximum
number of
personalities
supported
29 Protocol subtypes for protocol types 0x14 – 0x17 are configured by the Stream Layer Protocol.
30 This value will always be overwritten by the ConfigurationComplete or SoftConfigurationComplete
message.
6-66

ID
0x0102 SupportConfigurationLock 0x0000 Processing of
LockConfiguration
,
LockConfiguration
Ack,
UnLockConfigurat
ion, and
UnLockConfigurat
ionAck messages
is not supported.
0x0001 Processing of
LockConfiguration
,
LockConfiguration
Ack,
UnLockConfigurat
ion, and
UnLockConfigurat
ionAck messages
is supported.
1 7.4.7.26.4.7.2 Complex Attributes

3 definition).
4 7.4.7.2.16.4.7.2.1 PriorSession Attribute

5
6-67
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
Restore 1 ‘0’
‘0000000
Reserved 7
’
UATI 0 or 128 N/A
SecurityPacketLength 0 or 8 N/A
SecurityPacket 0 or SecurityPacketLength × 8 N/A
1 Length Length of the complex attribute in octets. The access terminal shall
2 set this field to the length of the complex attribute excluding the
3 Length field.
4 AttributeID The access terminal shall set this field to 0x1000.
5 ValueID The access terminal shall set this field to an identifier assigned to
6 this complex value.
7 Restore The access terminal shall set this field to ‘1’ if it is requesting to
8 restore a prior session. The access terminal shall set this field to ‘0’ if
9 it is requesting to proceed with the current session configuration and
10 not restore any prior sessions.
11 Reserved The access terminal shall set this field zero. The access network shall
12 ignore this field.
13 UATI The access terminal shall include this field only if the Restore field is
14 set to ‘1’. If included, the access terminal shall set this field to the
15 UATI associated with the prior session.
16 SecurityPacketLength
17 The access terminal shall include this field only if the Restore field is
19 length of the SecurityPacket field in octets.
20 SecurityPacket The access terminal shall include this field only if the Restore field is
22 SecurityPacket variable which is constructed as specified in
23 6.4.6.1.6.1.
6-68
1 7.4.7.2.26.4.7.2.2 ATSupportedApplicationSubtypes Attribute

2
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
NumAppSubtypes 8 0
NumAppSubtypes occurrences of the following field:
ApplicationSubtype 16 N/A
5 Length field.
7 ValueID The access terminal shall set this field to an identifier assigned to
8 this complex value.
9 NumAppSubtypes This field shall be set to the number of occurrences of the

10 ApplicationSubtype field following this field in this record.
11 ApplicationSubtype This field shall be set to the Application Subtype that the access
12 terminal supports.
6-69

2

NSCPType Type field for this protocol Table 2.5.4-1
NSCPDefault Subtype field for this protocol 0x0000
3 7.4.96.4.9 Message Flows
UATIRequest
UATIAssignment Address Management

Protocol
UATIComplete
Session is opened with the default attributes
Connection Establishment
Session negotiation starts
ConfigurationRequest Session Configuration

Protocol Negotiation
ConfigurationResponse (AT initiated)
ConfigurationRequest
ConfigurationResponse Protocol Negotiation
ConfigurationRequest (AT initiated)
ConfigurationResponse
Type X ConfigurationRequest
Type X and Type Y
messages refer to Type X ConfigurationResponse Protocol Configuration
messages
Type Y ConfigurationRequest (AT initiated)
belonging to
protocol X or Y.
Type Y ConfigurationResponse
ConfigurationComplete
Key Exchange
Protocol Configuration
(AN initiated)
ConfigurationRequest
ConfigurationResponse
Type X ConfigurationRequest
Type X ConfigurationResponse
Session Reconfigured
4
5 Figure 6.4.9-1. Default Session Configuration Protocol: Extensive Negotiation

6 Procedure
6-70
UATIRequest
Address
UATIAssignment
Management
UATIComplete Protocol

ConfigurationStart
Key Exchange Protocol Negotiation

and Configuration
2
3 Figure 6.4.9-2. Default Session Configuration Protocol: Minimal Negotiation

4 Procedure with Key Exchange
6-71
UATIRequest
UATIAssignment Address Management

Protocol
UATIComplete
AT Initiated Protocol Negotiation and Configuration

using ConfigurationRequest and
Protocol
ConfigurationResponse messages
AN Initiated Protocol Configuration using

ConfigurationRequest and ConfigurationResponse
Protocol
messages
Key
Key Exchange Exchange
Protocol
SoftConfigurationComplete
(PersonalityIndexStore=0x0, Continue=‘1’)
InConfiguration instance is stored into Main

Personality and Default Session Configuration
Protocol enters AT Initiated State
AT Initiated Protocol Negotiation and Configuration

using ConfigurationRequest and
Protocol
ConfigurationResponse messages
AN Initiated Protocol Configuration using

ConfigurationRequest and ConfigurationResponse
Protocol
messages
SoftConfigurationComplete
(PersonalityIndexStore=0x1, Continue=‘0’)
1
2 Figure 6.4.9-3. Default Session Configuration Protocol: Negotiation of Multiple

3 Personalities
6-72

Access terminal is Connected
Personality 0x2 is currently in use
AttributeUpdateRequest Session
(SessionConfigurationToken=0x3yyy) Configuration
AttributeUpdateAccept Protocol
ConnectionClose, TrafficChannelAssignment Connected State

Protocol and Route
ConnectionClose Update Protocol
Personality 0x3 is in use
1
2 Figure 6.4.9-4. Default Session Configuration Protocol: Personality Change During

3 Connection

6 This protocol defines the following parameter records in addition to the configuration
7 attributes for this protocol.
8 7.4.10.16.4.10.1 ConfigurationLock Parameter

9 The following parameter shall be included in the Session State Information Record if the
10 SupportConfigurationLock attribute is 0x0001.
11 Table 6.4.10.1-1. The Format of the Parameter Record for the ConfigurationLock
12 Parameter
13
Field Length (bits)
ParameterType 8
Length 8
ConfigurationLock 8
17 ConfigurationLock This field shall be set to 0x00 is the value of the ConfigurationLock is
18 UnLocked. Otherwise, the field shall be set to 0x01.
6-73
1 7.4.10.26.4.10.2 ATSupportedNonDefaultProtocolSubTypes Parameter

2 The following parameter shall be included in the Session State Information Record only if
3 the access network supports Extended Session State Information Record as defined in
4 [8][9].

6 ATSupportedNonDefaultProtocolSubTypes Parameter
Field Length (bits)
ParameterType 8
Length 8
TypeLength 1
ProtocolType 7 or 15
NumProtocolSubtypes 8
NumProtocolSubtypes occurrences of the following
field:
ProtocolSubtype 16
12 ProtocolType This field has the following format:

13

Type1 7
Type2 0 or 8
15 Type value for the protocol to which the associated ProtocolSubtypes
16 belong.
18 encapsulated parameter is 7 bits, then this sub-field shall be
19 omitted. Otherwise, this field shall be set to the 8 least significant
20 bits of the Type value for the protocol to which the associated
21 ProtocolSubtypes belong.
6-74
1 NumProtocolSubtypes
2 This field shall be set to the number of occurrences of the
3 ProtocolSubtype field following this field in this record.
4 ProtocolSubtype This field shall be set to the non-default subtype of the protocol Type
5 encapsulated in this record. This field shall not be set to the
6 HardLink subtype. The ProtocolSubtypes for a protocol Type shall be
7 in the same order that the access terminal has sent in the
8 ConfigurationRequest messages.
9 6.4.10.3 CurrentPersonalityIndex Parameter

11 the access network supports Extended Session State Information Record as defined in
12 [8][9] and the Session State Information is being transferred while the connection is open.
13
14 Table 6.4.10.3-1. The Format of the Parameter Record for the C Parameter
Field Length (bits)
ParameterType 8
Length 8
CurrentPersonality 4
Reserved 4
18 CurrentPersonality The sender shall set this field to the index of the Personality that is in
19 use.
20 Reserved The sender shall set this field to ‘0000’.
6-75
1 7.56.5 Generic Multimode Capability Discovery Protocol

3 The Generic Multimode Capability Discovery Protocol allows the access network to discover
4 the multimode capabilities of the access terminal.
6 7.5.2.16.5.2.1 Commands

10 7.5.2.36.5.2.3 Public Data


15 therefore, it does not carry payload on behalf of other layers or protocols. This protocol
16 uses the Signaling Application to transmit and receive messages.

21 • The fall-back values of the attributes for this protocol shall be set to the default values
30 7.5.5.16.5.5.1 Procedures
31 This protocol uses the Generic Configuration Protocol (see 13.7) to define processing of the
32 configuration messages.
6-76
1 7.5.5.1.16.5.5.1.1 Access Network Procedures

2 The access network shall not propose new values for the attributes in Table 6.5.9-1 in a
3 ConfigurationRequest message or a ConfigurationResponse message.
4 7.5.5.1.26.5.5.1.2 Commit Procedures

11 then
19 − The InConfiguration protocol instance at the access terminal and the access
20 network shall become the InUse protocol instance.
26
Field Length (bits)
MessageID 8
TransactionID 8
6-77
4
Field Length (bits)
MessageID 8
TransactionID 8

13
15 7.5.6.16.5.6.1 Procedures
16 The in-use instance of this protocol does not define any procedures.

18 The in-use instance of this protocol does not define any messages.
19 7.5.76.5.7 Interface to Other Protocols
20 7.5.7.16.5.7.1 Commands
6-78
1 7.5.7.26.5.7.2 Indications

4

NMCDType Type field for this protocol. Table 2.5.4-1
NMCDGeneric Subtype field for this protocol 0x0001
5 7.5.96.5.9 Configuration Attributes for the Multimode Capability Discovery Protocol

7 terminal and the access network shall use as defaults the values in Table 6.5.9-1 typed in
8 bold italics.
6-79

0x00 The access terminal does not
support multiple
independently tuneable
SimultaneousCommon transmitters that can be used
0xff
ChannelTransmit simultaneously on the
cdma2000 high rate packet
data and the cdma2000 1x
common channels.
0x01 The access terminal supports
multiple independently
tuneable transmitters that can
be used simultaneously on the
common channels. The
transmitters can be tuned to
adjacent channel numbers in
the same band class. The
transmitters cannot be tuned
to non-adjacent channel
numbers in the same band
class, or to channels in
different band classes.
separate channel numbers in
to channel in different band
classes.
6-80

separate channel numbers,
with a maximum separation of
5MHz, in the same band class.
The transmitters cannot be
tuned to channel in different
band classes.
10MHz, in the same band
class. The transmitters cannot
be tuned to channel in
6-81

5MHz.
10MHz.
15MHz.
6-82

0x0A The access terminal supports
20MHz.
0x0B The access terminal supports
separate CDMA channels.
All other Reserved
values
support multiple
SimultaneousDedicate transmitters that can be used
0xfe
dChannelTransmit simultaneously on the
dedicated channels.
dedicated channels. The
adjacent channel numbers in
to non-adjacent channel
numbers in the same band
class, or to channels in
6-83

separate channel numbers in
to channel in different band
classes.
5MHz, in the same band class.
The transmitters cannot be
tuned to channel in different
band classes.
6-84

5MHz.
10MHz.
6-85

15MHz.
0xA The access terminal supports
20MHz.
0x0B The access terminal supports
separate CDMA channels.
All other Reserved
values
support multiple
SimultaneousCommon receivers that can be used
0xfd
ChannelReceive simultaneously on the
common channels.
6-86

tuneable receivers that can be
used to simultaneously receive
the cdma2000 high rate
packet data Control Channel
and one or more common
channels defined by the
cdma2000 1x air interface.
The access terminal is defined
to have independently
tuneable receivers if each
receiver can be tuned to a
separate CDMA channel.
packet data Traffic Channel
and one or more dedicated
cdma2000 1x air interface,
which are not separated by
more than 5MHz, and are in
receivers cannot be tuned to
channel in different band
classes. The access terminal is
defined to have independently
6-87

6-88

more than 5MHz.The access
terminal is defined to have
receivers if each receiver can
be tuned to a separate CDMA
channel.
6-89

channel.
channel.
channel.
All other Reserved
values
6-90

support multiple
SimultaneousDedicate receivers that can be used
0xfc
dChannelReceive simultaneously on the
dedicated channels.
cdma2000 1x air interface.
The access terminal is defined
to have independently
classes.The access terminal is
6-91

6-92

channel.
6-93

channel.
channel.
channel.
All other Reserved
values
6-94

support hybrid operation with
cdma2000 1x (see [3]).
0xfb HybridMSAT 0x01 The access terminal supports

hybrid operation with
cdma2000 1x (see [3]).
All other Reserved
values
support receiver diversity.
0xfa ReceiverDiversity
receiver diversity.
All other Reserved
values
1 7.66.6 Session State Information

3 The parameter records for this protocol consist of only the configuration attributes for this
4 protocol.
5
6-95
1 No text
6-96
Connection Layer 3GPP2 C.S0024-B v2.0
1 87 CONNECTION LAYER

4 The Connection Layer controls the state of the air-link, and it prioritizes the traffic that is
5 sent over it.
6 This section presents the default protocols for the Connection Layer. With the exception of
7 the Overhead Messages Protocol, each of these protocols can be independently negotiated
8 at the beginning of the session.
9 The access terminal and the access network maintain a connection whose state dictates
10 the form in which communications between these entities can take place. The connection
11 can be either closed or open:
12 • Closed Connection: When a connection is closed, the access terminal is not assigned
13 any dedicated air-link resources. Communications between the access terminal and the
14 access network are conducted over the Access Channel and the Control Channel.
15 • Open Connection: When a connection is open, the access terminal can be assigned the
16 Forward Traffic Channel, and is assigned a Reverse Power Control Channel and a
17 Reverse Traffic Channel. Communications between the access terminal and the access
18 network are conducted over these assigned channels, as well as over the Control
19 Channel.
20 The Connection Layer provides the following connection-related functions:
21 • Manages initial acquisition of the network.
22 • Manages opening and closing of connections.
23 • Manages communications when connection is closed and when a connection is open.
24 • Maintains approximate access terminal’s location in either connection states.
25 • Manages radio link between the access terminal and the access network when a
26 connection is open.
27 • Performs supervision both when the connection is open and when it is closed.
28 • Prioritizes and encapsulates transmitted data received from the Session Layer and
29 forwards it to the Security Layer.
30 • De-capsulates data received from the Security Layer and forwards it to the Session
31 Layer.
32 The Connection Layer performs these functions through the following protocols:
7-1
3GPP2 C.S0024-B v2.0 Connection Layer
1 • Air Link Management Protocol: This protocol maintains the overall connection state in
2 the access terminal and the access network. The protocol can be in one of three states,
3 corresponding to whether the access terminal has yet to acquire the network
4 (Initialization State), has acquired the network but the connection is closed (Idle State),
5 or has an open connection with the access network (Connected State). This protocol
6 activates one of the following three protocols as a function of its current state.
7 • Initialization State Protocol: This protocol performs the actions associated with
8 acquiring an access network.
9 • Idle State Protocol: This protocol performs the actions associated with an access
10 terminal that has acquired the network, but does not have an open connection. Mainly,
11 these are keeping track of the access terminal’s approximate location in support of
12 efficient Paging (using the Route Update Protocol), the procedures leading to the
13 opening of a connection, and support of access terminal power conservation.
14 • Connected State Protocol: This protocol performs the actions associated with an access
15 terminal that has an open connection. Mainly, these are managing the radio link
16 between the access terminal and the access network (handoffs, handled via the Route
17 Update Protocol), and the procedures leading to the close of the connection.
18 In addition to the above protocols, which deal with the state of the connection, the
19 Connection Layer also contains the following protocols:
20 • Route Update Protocol: This protocol performs the actions associated with keeping
21 track of an access terminal’s location and maintaining the radio link between the
22 access terminal and the access network. This protocol performs supervision on the
23 pilots.
24 • Overhead Messages Protocol: This protocol broadcasts essential parameters over the
25 Control Channel. These parameters are shared by protocols in the Connection Layer as
26 well as protocols in other layers. This protocol also performs supervision on the
27 messages necessary to keep the Connection Layer functioning.
28 • Packet Consolidation Protocol: This protocol consolidates and prioritizes packets for
29 transmission as a function of their assigned priority and the target transmission
30 channel.
31 Figure 7.1.1-1 illustrates the relationship between all the Connection Layer protocols. An
32 arrow between two protocols implies that the source sends commands to the target.
7-2
Air Link Packet

Initialization
Management Consolidation
State Protocol
Protocol Protocol
Connected Route Update Idle State

State Protocol Protocol Protocol
Overhead
Messages
Protocol
2 Figure 7.1.1-1. Connection Layer Protocols
3 The Air Link Management Protocol, its descendants and the Overhead Messages Protocol
4 are control protocols. The Packet Consolidation Protocol operates on transmitted and
5 received data.

7 In the transmit direction, the Connection Layer receives Session Layer packets, adds
8 Connection Layer header(s), concatenates them in the order to be processed on the receive
9 side, adds padding, where applicable, and forwards the resulting packet for transmission to
10 the Security Layer.
11 In the receive direction, the Connection Layer receives Security Layer packets from the
12 Security Layer, and forwards the Session Layer packets to the Session Layer in the order
13 received after removing the Connection Layer headers and padding.
14 Figure 7.1.2-1 and Figure 7.1.2-2 illustrate the relationship between Session Layer
15 packets, Connection Layer packets and Security Layer payloads for Format A (maximum
16 size) and Format B Connection Layer packets.
7-3
Session
Layer
packet
Connection Connection
Layer Layer
packet payload
Security
Layer
payload
1
2 Figure 7.1.2-1. Connection Layer Encapsulation (Format A)
Session
Session
Layer
Layer
packet
packet
Connection Connection Connection Connection Connection

Layer Layer Layer Layer Layer pad
packet header payload header payload
Security
Layer
payload
3
4 Figure 7.1.2-2. Connection Layer Encapsulation (Format B)
7-4
1 8.27.2 Default Air-Link Management Protocol
2 8.2.17.2.1 Overview
3 The Default Air-Link Management Protocol provides the following functions:
4 • General state machine and state-transition rules to be followed by an access terminal
5 and an access network for the Connection Layer.
6 • Activation and deactivation of Connection Layer protocols applicable to each protocol
7 state.
8 • Mechanism through which access network can redirect access terminal to another
9 network.
10 The actual behavior and message exchange in each state is mainly governed by protocols
11 that are activated by the Default Air-Link Management Protocol. These protocols return
12 indications which trigger the state transitions of this protocol. These protocols also share
13 data with each other in a controlled fashion, by making that data public.
14 This protocol can be in one of three states:
15 • Initialization State: In this state the access terminal acquires an access network. The
16 protocol activates the Initialization State Protocol to execute the procedures relevant to
17 this state. The access network maintains a single instance of this state and
18 consequently, executes a single instance of the Initialization State Protocol.
19 • Idle State: In this state the connection is closed. The protocol activates the Idle State
20 Protocol to execute the procedures relevant to this state.
21 • Connected State: In this state the connection is open. The protocol activates the
22 Connected State Protocol to execute the procedures relevant to this state.
23 Figure 7.2.1-1 provides an overview of the access terminal states and state transitions. All
24 transitions are caused by indications returned from protocols activated by the Default Air-
25 Link Management Protocol.
7-5
Initial State
NetworkAcquired IdleState.ConnectionOpened
Initialization Connected
Idle State
State State
NetworkRedirected or ConnectionClosed or
NetworkLost or Supervision Failed Supervision Failed
NetworkRedirected
1
3 Terminal)
4 Figure 7.2.1-2 provides an overview of the access network states and state transitions.
Initial State
IdleState.ConnectionOpened
Initialization Connected
Idle State
State State
ConnectionClosed or
(one for all access terminals)
ConnectionLost
5
7 Network)
8 Table 7.2.1-1 provides a summary of the Connection Layer and MAC Layer protocols that
9 are active in each state.
7-6
1 Table 7.2.1-1. Active Protocols Per Air Link Management Protocol State
Initialization State Idle State Connected State

Overhead Messages Protocol Overhead Messages Protocol Overhead Messages Protocol
Initialization State Protocol Idle State Protocol Connected State Protocol
Control Channel MAC
Route Update Protocol Route Update Protocol
Protocol31
Control Channel MAC
Control Channel MAC Protocol
Protocol
Forward Traffic Channel MAC
Access Channel MAC Protocol
Protocol
Forward Traffic Channel MAC Reverse Traffic Channel MAC
Protocol32 Protocol
Reverse Traffic Channel MAC
Protocol33
3 8.2.2.17.2.2.1 Commands
5 • OpenConnection
6 • CloseConnection

9 8.2.2.37.2.2.3 Public Data


31 Activated by the Initialization State Protocol
32 Only during connection setup
33 Only during connection setup
7-7


14 Upon creation, the InUse instance of this protocol in the access terminal shall perform the
15 following:
18 • The protocol shall enter the Initialization State.
19 The access network shall have a single InUse instance of this protocol for each access
20 terminal with which the access network is currently maintaining a session. Upon creation,
21 the InUse instance of this protocol in the access network shall perform the following:
24 • The protocol shall enter the Idle State.
25 Upon creation of the InUse instance of this protocol, the access network shall have a single
26 InUse instance of this protocol operating in the Initialization State at the access network,
27 serving all access terminals.
29 8.2.5.17.2.5.1 Procedures

7-8
3 • If the InUse instance of any of the Connection Layer protocols does not have the same
4 subtype as the corresponding InConfiguration protocol instance, then
5 − the access terminal shall set the initial state of the InConfiguration and InUse
6 protocol instances of the Air-Link Management protocol to the Initialization
7 State.
8 − the access network shall set the initial state of the InConfiguration and InUse
9 protocol instances of the Air-Link Management protocol to the Idle State.
11 then
20 instance for the Air-Link Management Protocol at the access terminal and the
21 access network.
27
Field Length (bits)
MessageID 8
TransactionID 8
7-9
5
Field Length (bits)
MessageID 8
TransactionID 8

14
16 8.2.6.17.2.6.1 Procedures
18 8.2.6.1.1.17.2.6.1.1.1 OpenConnection
19 If the protocol receives the OpenConnection command in the Initialization State, the access
20 terminal shall queue the command and execute it when the access terminal enters the Idle
21 State.
22 The access network shall ignore the command in the Initialization State.
23 If the protocol receives this command in the Idle State:
7-10
1 • Access terminal shall issue an IdleState.OpenConnection command.

2 • Access network shall issue an IdleState.OpenConnection command.
3 If the protocol receives this command in the Connected State the command shall be
4 ignored.
5 8.2.6.1.1.27.2.6.1.1.2 CloseConnection
6 If the protocol receives the CloseConnection command in the Connected State:
7 • Access terminal shall issue a ConnectedState.CloseConnection command.
8 • Access network shall issue a ConnectedState.CloseConnection command.
9 If the protocol receives this command in any other state it shall be ignored.
10 8.2.6.1.27.2.6.1.2 Initialization State

11 In the Initialization State the access terminal has no information about the serving access
12 network. In this state the access terminal selects a serving access network and obtains
13 time synchronization from the access network.

15 The access terminal shall enter the Initialization State when the Default Air-Link
16 Management Protocol is instantiated. This may happen on events such as network
17 redirection and initial power-on. A comprehensive list of events causing the Default Air-
18 Link Management Protocol to enter the Initialization State is beyond the scope of this
19 specification.
20 The access terminal shall issue an InitializationState.Activate command upon entering this
21 state. If the access terminal entered this state because the protocol received a Redirect
22 message and a Channel Record was received with the message, the access terminal shall
23 provide the Channel Record with the command.
24 If the protocol receives an InitializationState.NetworkAcquired indication the access terminal
25 shall issue an InitializationState.Deactivate command34 and transition to the Idle State.
26 8.2.6.1.37.2.6.1.3 Idle State

27 In this state the access terminal has acquired the access network but does not have an
28 open connection with the access network.
30 8.2.6.1.3.1.17.2.6.1.3.1.1 General Requirements

31 The access terminal shall issue the following commands upon entering this state:
34 Some of the Deactivate commands issued by this protocol are superfluous (because the
commanded protocol already put itself in the Inactive State) but are specified here for completeness.
7-11
1 • IdleState.Activate
2 • RouteUpdate.Activate
3 If the access terminal had a queued OpenConnection command, it shall issue an
4 IdleState.OpenConnection command.
5 If the protocol receives an IdleState.ConnectionOpened indication, the access terminal shall
6 perform the cleanup procedures defined in 7.2.6.1.3.1.2 and transition to the Connected
7 State.
8 If the protocol receives an IdleState.ConnectionFailed, a
9 ForwardTrafficChannelMAC.SupervisionFailed, or a
10 ReverseTrafficChannelMAC.SupervisionFailed indication, the access terminal shall:
11 • Issue an IdleState.Close command,
12 • Issue a RouteUpdate.Close command,
13 If the protocol receives a Redirect message, a RouteUpdate.NetworkLost, an
14 OverheadMessages.SupervisionFailed, an OverheadMessages.ANRedirected, a
15 ControlChannelMAC.SupervisionFailed, or an AccessChannelMAC.SupervisionFailed
16 indication, the access terminal shall:
17 • Issue a RouteUpdate.Deactivate command,
18 • Issue an OverheadMessages.Deactivate command,
19 • Issue a ControlChannelMAC.Deactivate command,
20 • Perform the cleanup procedures defined in 7.2.6.1.3.1.2, and
21 • Transition to the Initialization State.
22 8.2.6.1.3.1.27.2.6.1.3.1.2 Idle State Cleanup Procedures

23 The access terminal shall issue the following commands when it exits this state:
24 • IdleState.Deactivate

27 The access network shall issue the following commands upon entering this state:
30 If the protocol receives an IdleState.ConnectionFailed indication, or a
31 ReverseTrafficChannelMAC.SupervisionFailed indication, the access network shall:
32 • Issue an IdleState.Close command,
33 • Issue a RouteUpdate.Close command.
7-12
1 If the protocol receives an IdleState.ConnectionOpened indication, the access network shall

2 perform the cleanup procedures defined in 7.2.6.1.3.2.2 and transition to the Connected
3 State.
4 The access network may send the access terminal a Redirect message to redirect it from
5 the current serving network and optionally, provide it with information directing it to
6 another network. If the access network sends a Redirect message it shall
8 • Perform the cleanup procedures defined in 7.2.6.1.3.2.2.
9 8.2.6.1.3.2.27.2.6.1.3.2.2 Idle State Cleanup Procedures

10 The access network shall issue the following command when it exits this state:
12 8.2.6.1.47.2.6.1.4 Connected State

13 In the Connected State, the access terminal and the access network have an open
14 connection.

17 The access terminal shall issue the following command upon entering this state:
18 • ConnectedState.Activate
19 If the access terminal has stored ConnectionFailure records and if the value of the
20 ConnectionFailureReportingEnabled attribute is 0x01, then the access terminal shall send
21 a ConnectionFailureReport message upon entering this state. Upon receiving the
22 corresponding ConnectionFailureReportAck message, the access terminal shall delete the
23 reported ConnectionFailure records.
24 If the access terminal does not receive a ConnectionFailureReportAck message in response
25 to a ConnectionFailureReport message, then the access terminal may re-transmit the
26 ConnectionFailureReport message an implementation specific number of times.
27 If the protocol receives a ConnectedState.ConnectionClosed, an
28 OverheadMessages.SupervisionFailed, a ControlChannelMAC.SupervisionFailed, a
29 RouteUpdate.AssignmentRejected, or a ForwardTrafficChannelMAC.SupervisionFailed
30 indication, the access terminal shall perform the following:
7-13
1 • If this procedure is invoked due to reception of a OverheadMessages.SupervisionFailed,

2 a ControlChannelMAC.SupervisionFailed, or a
3 ForwardTrafficChannelMAC.SupervisionFailed indication and if the value of the
4 ConnectionFailureReportingEnabled attribute is 0x01, then the access terminal shall
5 generate and store a ConnectionFailure record that contains the reason for connection
6 failure, the CDMA System Time when the Connection failure occurred, the SectorID
7 public data of the Overhead Messages Protocol when the Connection failure occurred,
8 the CDMA Channel on which the Connection failure occurred, and, if available, the
9 Latitude, and Longitude of the location where the Connection Failure occurred. The
10 access terminal shall store at least four Connection failure records corresponding to the
11 last four Connection failures.
15 • Issue a ConnectedState.Deactivate command,
16 • Transition to the Idle State.
17 If the protocol receives a Redirect message or an OverheadMessages.ANRedirected
18 indication, the access terminal shall:
19 • Issue a ConnectedState.CloseConnection command,
23 • Transition to the Initialization State.

26 The access network shall issue the following command upon entering this state:
28 If the protocol receives a ConnectedState.ConnectionClosed, or RouteUpdate.ConnectionLost
29 indication, the access network shall:
31 • Perform the cleanup procedures defined in 7.2.6.1.4.2.2,
33 If the value of the ConnectionFailureReportingEnabled attribute is 0x01, then the access
34 network shall send a ConnectionFailureReportAck message upon receiving a
35 ConnectionFailureReport message.
7-14
1 The access network may send the access terminal a Redirect message to redirect it from
2 the current serving network and optionally, provide it with information directing it to
3 another network. If the access network sends a Redirect message it shall:
5 • Perform the cleanup procedures defined in 7.2.6.1.4.2.2,
7 8.2.6.1.4.2.27.2.6.1.4.2.2 Connected State Cleanup Procedures

8 The access network shall issue the following command when it exits this state:
9 • ConnectedState.Deactivate
11 8.2.6.2.17.2.6.2.1 Redirect
12 The access network sends the Redirect message to redirect the access terminal(s) away
13 from the current network; and, optionally, the access network provides it with information
14 directing it to one of a set of different networks.
15
Field Length (bits)

MessageID 8
NumChannel 8
NumChannel instances of the following field
Channel 24
17 NumChannel The access network shall set this field to the number of Channel
18 records it is including in this message.
19 Channel This field shall be set to the channel that the access terminal should
20 reacquire. The channel shall be specified using the standard Channel
21 Record definition, see 13.1.
22
Addressing broadcast unicast Priority 40
23 8.2.6.2.27.2.6.2.2 ConnectionFailureReport
24 The ConnectionFailureReport message format is as follows:
25
7-15
Field Length (bits)
MessageID 8
TransactionID 8
NumRecords 4
NumRecords occurrences of the following record:
ConnectionFailureReason 4
TimeStamp 32
SectorID 128
ChannelRecord 24
LatLongIncluded 1
Latitude 0 or 22
Longitude 0 or 23
3 than the TransactionID field of the last ConnectionFailureReport
4 message. If this is the first ConnectionFailureReport message sent by
5 the access terminal, then the access terminal shall set this field to
6 zero.
7 NumRecords The access terminal shall set this field to the number of Connection
8 failures reported in this message.
9 ConnectionFailureReason
10 This field indicates the reason for the connection failure. The access
11 terminal shall set this field according to Table 7.2.6.2.2-1.
7-16
1 Table 7.2.6.2.2-1. ConnectionFailureReason Encoding
ConnectionFailureReason
field value Meaning
0x0 General Connection Failure (excluding
failure due to tune away to another air
interface)
0x1 Connection failure due to tune away to
cdma2000 1x air-interface
0x2 Connection failure due to position
determination tune away
All other values See [10].
2 TimeStamp The access terminal shall set this field to the CDMA system time at
3 which this Connection failure occurred in units of 1.28 seconds.
4 SectorID The access terminal shall set this field to the SectorID field of the
5 SectorParameters message transmitted by the access network where
6 the Connection failure occurred. SectorID is public data of the
7 Overhead Messages Protocol.
8 ChannelRecord The access terminal shall set this field to the Channel Record for the
9 CDMA Channel on which the Connection failure occurred. See 13.1
10 for the Channel record format.
11 LatLongIncluded The access terminal shall set this field to ‘1’ if the Latitude and
12 Longitude fields are included in this message. Otherwise, the access
13 terminal shall set this field to ‘0’.
14 Latitude If LatLongIncluded is set to ‘0’, then the access terminal shall omit
15 this field. Otherwise, the access terminal shall set this field to the
16 Latitude of the location where the Connection failure occurred.
17 Longitude If LatLongIncluded is set to ‘0’, then the access terminal shall omit
18 this field. Otherwise, the access terminal shall set this field to the
19 Longitude of the location where the Connection failure occurred.
20 Reserved The access terminal shall add Reserved bits to make the length of the
23
7-17
Best
Channels RTC SLP
Effort
1 8.2.6.2.37.2.6.2.3 ConnectionFailureReportAck
2 The ConnectionFailureReportAck message format is as follows:
3
Field Length (bits)
MessageID 8
TransactionID 8
6 corresponding ConnectionFailureReport message.
7
Best
Channels FTC SLP
Effort
9 8.2.6.3.17.2.6.3.1 Commands Sent

11 • InitializationState.Activate
12 • InitializationState.Deactivate
15 • IdleState.Close
16 • IdleState.OpenConnection
18 • ConnectedState.Deactivate
19 • ConnectedState.CloseConnection
21 • RouteUpdate.Deactivate
22 • RouteUpdate.Close
23 • OverheadMessages.Deactivate
7-18
1 • ControlChannelMAC.Deactivate
2 8.2.6.3.27.2.6.3.2 Indications
4 • InitializationState.NetworkAcquired
6 • IdleState.ConnectionFailed
9 • RouteUpdate.NetworkLost
10 • RouteUpdate.AssignmentRejected
11 • OverheadMessages.ANRedirected
12 • OverheadMessages.SupervisionFailed
13 • ControlChannelMAC.SupervisionFailed
14 • AccessChannelMAC.SupervisionFailed
15 • ReverseTrafficChannelMAC.SupervisionFailed
16 • ForwardTrafficChannelMAC.SupervisionFailed

18 The simple configurable attributes are listed in Table 7.2.7-1. The access network and the
19 access terminal shall use the default values that are typed in bold italics.
20 Table 7.2.7-1 Configurable Simple Attributes

ID
0xff ConnectionFailureRepor 0x00 Access terminal does not send
tingEnabled ConnectionFailureReport messages.
0x01 Access terminal sends
ConnectionFailureReport messages.
All other Reserved
values

22
7-19

NALMPType Type field for this protocol Table 2.5.4-1
NALMPDefault Subtype field for this protocol 0x0000

7-20
1 8.37.3 Default Initialization State Protocol
2 8.3.17.3.1 Overview
3 The Default Initialization State Protocol provides the procedures and messages required for
4 an access terminal to acquire a serving network.
5 At the access terminal, this protocol operates in one of the following four states:
6 • Inactive State: In this state the protocol waits for an Activate command.
7 • Network Determination State: In this state the access terminal chooses an access
8 network on which to operate.
9 • Pilot Acquisition State: In this state the access terminal acquires a Forward Pilot
10 Channel.
11 • Synchronization State: In this state the access terminal synchronizes to the Control
12 Channel cycle, receives the Sync message, and synchronizes to CDMA System Time.
13 Protocol states and events causing transition between states are shown in Figure 7.3.1-1.
Initial State Deactivate triggered transitions not shown
Activate
Network
Inactive State Determination
or e State
e d ng
i r ra
exp t of
er ou pilot timer
Sync message OK tim ion network selected
v is expired
re
Synchronization Pilot Acquisition

State State
14
pilot acquired
15 Figure 7.3.1-1. Default Initialization State Protocol State Diagram
17 8.3.2.17.3.2.1 Commands
19 • Activate (an optional Channel Record can be specified with the command)
20 • Deactivate
7-21

3 • NetworkAcquired
4 8.3.2.37.3.2.3 Public Data

5 This protocol makes the following data public:
7 • Selected CDMA Channel
8 • CDMA System Time
9 • The following fields of the Sync message:
10 − MaximumRevision
11 − MinimumRevision
12 − PilotPN



30 Upon creation, the InUse instance of this protocol in the access terminal shall perform the
31 following:
7-22
1 • The protocol shall enter the Inactive State.
3 8.3.5.17.3.5.1 Procedures

7 The access terminal shall perform the procedures specified in this section, in the order
8 specified, when directed by the InUse instance of the Session Configuration Protocol to
9 execute the Commit procedures:
13 subtype as the corresponding InConfiguration protocol instance, then the access
14 terminal shall set the initial state of the InConfiguration and InUse protocol instances
15 of the Initialization State protocol to the Network Determination State.
17 then
18 − The access terminal shall set the attribute values associated with the InUse
19 instance of this protocol to the attribute values associated with the
20 InConfiguration instance of this protocol, and
21 − The access terminal shall purge the InConfiguration instance of the protocol.
23 instance, then the access terminal shall perform the following in the order specified:
25 instance for the Initialization State Protocol at the access terminal.
31
7-23
Field Length (bits)
MessageID 8
TransactionID 8
8
Field Length (bits)
MessageID 8
TransactionID 8

17
7-24
2 8.3.6.17.3.6.1 Procedures
3 The access network shall broadcast the Sync message periodically in a synchronous
4 Control Channel capsule. This period should not exceed TISPSync seconds.
5 The access network need not keep state for this protocol.

7 The access network shall ignore all commands.
8 8.3.6.1.1.17.3.6.1.1.1 Activate
9 If the protocol receives an Activate command in the Inactive State, the access terminal shall
10 transition to the Network Determination State.
11 If the protocol receives this command in any other state, the access terminal shall ignore it.
12 8.3.6.1.1.27.3.6.1.1.2 Deactivate
13 If the protocol receives a Deactivate command in the Inactive State, the access terminal
14 shall ignore it.
15 If the protocol receives this command in any other state, the access terminal shall
17 8.3.6.1.27.3.6.1.2 Inactive State

18 In the Inactive State the access terminal waits for the protocol to receive an Activate
19 command.
20 8.3.6.1.37.3.6.1.3 Network Determination State

21 In the Network Determination State the access terminal selects a CDMA Channel (see 13.1)
22 and attempts acquire the access network on that CDMA Channel.
23 If a Channel Record was provided with the Activate command, the access terminal should
24 select the system and channel specified by the record.
25 The specific mechanisms to provision the access terminal with a list of preferred networks
26 and with the actual algorithm used for network selection are beyond the scope of this
27 specification.
28 Upon selecting a CDMA Channel the access terminal shall enter the Pilot Acquisition State.
7-25
1 8.3.6.1.47.3.6.1.4 Pilot Acquisition State

2 In the Pilot Acquisition State the access terminal acquires the Forward Pilot Channel of the
3 selected CDMA Channel.
4 Upon entering the Pilot Acquisition State, the access terminal shall tune to the selected
5 CDMA Channel and shall search for the pilot. If the access terminal acquires the pilot, it
6 shall enter the Synchronization State.35 If the access terminal fails to acquire the pilot
7 within TISPPilotAcq seconds of entering the Pilot Acquisition State, it shall enter the Network
8 Determination State.
9 8.3.6.1.57.3.6.1.5 Synchronization State

10 In the Synchronization State the access terminal completes timing synchronization.
11 Upon entering this state, the access terminal shall issue the ControlChannelMAC.Activate
12 command.
13 If the access terminal fails to receive a Sync message within TISPSyncAcq seconds of entering
14 the Synchronization State, the access terminal shall issue a ControlChannelMAC.Deactivate
15 command and shall enter the Network Determination State. While attempting to receive the
16 Sync message, the access terminal shall discard any other messages received on the
17 Control Channel.
18 When the access terminal receives a Sync message:
19 • If the access terminal’s revision number is not in the range defined by the
20 MinimumRevision and MaximumRevision fields (inclusive) specified in the message, the
21 access terminal shall issue a ControlChannelMAC.Deactivate command and enter the
22 Network Determination State.
23 • Otherwise, the access terminal shall:
24 − Set the access terminal time to the time specified in the message; The time
25 specified in the message is the time applicable 160 ms following the beginning
26 of the Control Channel Cycle in which the Sync message was received,
27 − Return a NetworkAcquired indication,
28 − Enter the Inactive State.
30 8.3.6.2.17.3.6.2.1 Sync
31 The access network broadcasts the Sync message to convey basic network and timing
32 information.
33
35 The Access Terminal Minimum Performance Requirements contains specifications regarding pilot
acquisition performance.
7-26
Field Length (bits)

MessageID 2
MaximumRevision 8
MinimumRevision 8
PilotPN 9
SystemTime 37
1 MessageID The access network shall set this field to ‘00’.
2 MaximumRevision Maximum Air-Interface protocol revision supported by the access

3 network. The access network shall set this field to the value specified
4 in 1.15. This value shall be in the range [0x00, 0xff].
5 MinimumRevision Minimum Air-Interface protocol revision supported by the access

6 network. The access network shall set this field to the value specified
7 in 1.15. This value shall be in the range [0x00, MaximumRevision].
8 PilotPN Pilot PN Offset. The access network shall set this field to the pilot PN
9 sequence offset for this sector in units of 64 PN Chips.
10 SystemTime The access network shall set this field to the CDMA System Time 160
11 ms after the start of the Control Channel Cycle in which this Sync
12 message is being sent. The CDMA System Time is specified in units
13 of 26.66... ms.
14
16 8.3.6.3.17.3.6.3.1 Commands Sent

18 • ControlChannelMAC.Activate
20 8.3.6.3.27.3.6.3.2 Indications

7-27

2
Constant Meaning Value Comments

Table
NISPType Type field for this protocol
2.5.4-1
NISPDefault Subtype field for this protocol 0x0000
1.28 3 × Control
TISPSync Sync message transmission period
seconds Channel Cycle
60
TISPPilotAcq Time to acquire pilot in access terminal
seconds
Time to acquire Sync message in access 5
TISPSyncAcq
terminal seconds

7-28
1 8.47.4 Default Idle State Protocol
2 8.4.17.4.1 Overview
3 The Default Idle State Protocol provides the procedures and messages used by the access
4 terminal and the access network when the access terminal has acquired a network and a
5 connection is not open.
6 This protocol operates in one of the following four states:
8 • Sleep State: In this state the access terminal may shut down part of its subsystems to
9 conserve power. The access terminal does not monitor the Forward Channel, and the
10 access network is not allowed to transmit unicast packets to it.
11 • Monitor State: In this state the access terminal monitors the Control Channel, listens
12 for Page messages and if necessary, updates the parameters received from the
13 Overhead Messages Protocol. The access network may transmit unicast packets to the
14 access terminal in this state.
15 • Connection Setup State: In this state the access terminal and the access network set-
16 up a connection.
17 Protocol states and events causing the transition between the states are shown in Figure
18 7.4.1-1 and Figure 7.4.1-2.
19
Deactivate triggered transitions are not shown
Initial State
Rx Activate
Inactive State Monitor State

os e
x Cl
ny or R
n De
ectio
onn esfu
l
Rx C ucc
s s ionS or see text
i t
nsm eques ted
Rx RouteUpdate.ConnectionOpened Tr a R
l MAC. ection nInitia periodic
e n io
nn on ect
Cha ding C .Conn
ess e
x Acc on sen Updat
R up oute
Rx
R
Connection Setup
Sleep State
State
20
21 Figure 7.4.1-1. Default Idle State Protocol State Diagram (Access Terminal)
7-29
Deactivate triggered transitions not shown

Initial State Activate
Inactive State se Sleep State

x Clo
rT
o
ny
nDe
RouteUpdate.ConnectionOpened ct io st
ne ue see text see text
o n eq
xC nR
T tio
ec
nn
x Co
Connection R
Monitor State
Setup State
Rx OpenConnection, or
Rx RouteUpdate.ConnectionInitiated, or
2
Rx ConnectionRequest
3 Figure 7.4.1-2. Default Idle State Protocol State Diagram (Access Network)
4 This protocol supports periodic network monitoring by the access terminal, allowing for
5 significant power savings. The following access terminal operation modes are supported:
6 • Continuous operation, in which the access terminal continuously monitors the Control
7 Channel.
8 • Suspended mode operation, in which the access terminal monitors the Control Channel
9 continuously for a period of time and then proceeds to operate in the slotted mode.
10 Suspended mode follows operation in the Air-Link Management Protocol Connected
11 State and allows for quick network-initiated reconnection.
12 • Slotted mode operation, in which the access terminal monitors only selected slots.
13 This protocol supports two types of connection set-ups:
14 • Normal setup: this procedure is always performed at the initiative of the access
15 terminal.36 It consists of the access terminal sending a ConnectionRequest message
16 which in turn causes the lower layers to open the connection. The Connection Setup
17 State contains the requirements for normal setup.
36 The access network may transmit a Page message to the access terminal directing it to initiate the
procedure.
7-30
1 • Fast Connect: this procedure is always performed at the initiative of the access network
2 and consists of the access network opening the connection directly via a
3 RouteUpdate.Open command.37 Fast Connect eliminates the need for the Page /
4 ConnectionRequest exchange when the access network has pending data to transmit to
5 an access terminal, and is especially useful when the access terminal is in suspended
6 mode. Support for Fast Connect at the access network is optional. Support for Fast
7 Connect at the access terminal is mandatory. The Monitor State contains the
8 requirements for Fast Connect.
10 8.4.2.17.4.2.1 Commands
12 • Activate
13 • Deactivate
15 • Close

18 • ConnectionOpened
19 • ConnectionFailed
20 8.4.2.37.4.2.3 Public Data



37 This command triggers a transmission of a TrafficChannelAssignment message based on the last
RouteUpdate message received from the access terminal.
7-31

16 8.4.5.17.4.5.1 Procedures

28 protocol instances of the Idle State protocol to the Inactive State.
30 protocol instances of the Idle State protocol to the Sleep State.
32 then
7-32
6 instance for the Idle State Protocol at the access terminal and the access
7 network.
13
Field Length (bits)
MessageID 8
TransactionID 8
18
21
7-33
Field Length (bits)
MessageID 8
TransactionID 8

9
11 8.4.6.17.4.6.1 Procedures
13 8.4.6.1.1.17.4.6.1.1.1 Activate
14 When the protocol receives an Activate command in the Inactive State:
15 • The access terminal shall transition to the Monitor State.
16 • The access network shall transition to the Sleep State.38
18 8.4.6.1.1.27.4.6.1.1.2 Deactivate
19 When the protocol receives a Deactivate command in the Inactive State it shall be ignored.
20 When the protocol receives this command in any other state:
38 Since the transitions happen asynchronously, this requirement guarantees that the access
network will not transmit unicast packets to the access terminal over the Control Channel when the
access terminal is not monitoring the channel.
7-34
1 • The access network shall transition to the Inactive State.
2 8.4.6.1.1.37.4.6.1.1.3 OpenConnection
3 When the protocol receives an OpenConnection command in the Inactive State or the
4 Connection Setup State, the command shall be ignored.
5 When the protocol receives this command in the Sleep State:
6 • The access terminal shall transition to the Monitor state and perform the procedures in
7 7.4.6.1.2 for sending a ConnectionRequest message.
8 • The access network shall queue the command and execute it when it is in the Monitor
9 State.
10 When the protocol receives this command in the Monitor State:
11 • The access terminal shall perform the procedures in 7.4.6.1.2 for sending a
12 ConnectionRequest message.
13 • The access network shall send a Page message to the access terminal and transition to
14 the Connection Setup State.
15 8.4.6.1.1.47.4.6.1.1.4 Close
16 When the protocol receives a Close command in the Inactive State it shall be ignored.
17 When the protocol receives a Close command in any other state:
19 • The access network shall transition to the Sleep State.
20 8.4.6.1.27.4.6.1.2 Access Terminal Procedures for Sending a ConnectionRequest Message

21 When procedures in this section are invoked, the access terminal shall perform the
22 following:
23 • Send a ConnectionRequest message,
24 • If an AccessChannelMAC.TransmissionSuccessful indication is received, it shall
25 transition to the Connection Setup State,
26 • If an AccessChannelMAC.TransmissionFailed indication is received, it shall return a
27 ConnectionFailed indication.
28 8.4.6.1.37.4.6.1.3 Inactive State

29 When the protocol is in the Inactive State it waits for an Activate command.
30 If the access terminal receives an OverheadMessages.Updated indication in this state, then
31 the access terminal shall queue the latest OverheadMessages.Updated indication for
32 processing in the Monitor state.
7-35
1 8.4.6.1.47.4.6.1.4 Sleep State

2 When the access terminal is in the Sleep State it may stop monitoring the Control Channel
3 by issuing the following commands:
6 The access terminal may shut down processing resources to reduce power consumption.
7 In order to transmit on the Access Channel in this state, the access terminal shall first
8 transition from the Sleep State to the Monitor State. If the access terminal requires opening
9 a connection, it shall transition to the Monitor state and perform the procedures in
10 7.4.6.1.2 for sending a ConnectionRequest message. When the access network is in the
11 Sleep State, it is prohibited from sending unicast packets to the access terminal.
12 If the access network receives a ConnectionRequest message, it shall transition to the
13 Connection Setup State.
14 If the access terminal advertised a suspend period that is current, the access network may
15 transition to the Monitor State.
16 The access network and the access terminal shall transition from the Sleep State to the
17 Monitor State in time to send and receive, respectively, the synchronous capsule sent in
18 each Control Channel cycle C satisfying
19 (C + R) mod NIDPSleep = 0
20 where C is the number of Control Channel cycles since the beginning of CDMA System
21 Time and R is obtained as follows:
22 • If PreferredControlChannelCycleEnabled is equal to ‘0’, then R is the result of applying
23 the hash function (see 13.4) using the following parameters:
24 − Key = SessionSeed
25 − Decorrelate = 6 × SessionSeed[11:0]
26 − N = NIDPSleep
27 − where SessionSeed is given as public data of the Address Management
28 Protocol.
29 • If PreferredControlChannelCycleEnabled is equal to ‘1’, then R is set to
30 PreferredControlChannelCycle.
31 8.4.6.1.57.4.6.1.5 Monitor State

32 When the access terminal is in the Monitor State, it continuously monitors the Control
33 Channel.
34 When the access network is in the Monitor State, it may send unicast packets to the access
35 terminal.
7-36

2 Upon entering the Monitor State, the access terminal shall issue the following commands:
3 • OverheadMessages.Activate
5 The access terminal shall comply with the following requirements when in the Monitor
6 State:
7 • If the access terminal has queued an OverheadMessages.Updated indication or upon
8 receiving an OverheadMessages.Updated indication, the access terminal shall tune to
9 the CDMA Channel selected as specified in 7.4.6.1.5.1.1.
10 • The access terminal shall monitor the overhead messages as specified in the Overhead
11 Messages Protocol (see 7.11.6.1.6).
12 • If the access terminal receives a Page message, it shall perform the procedures in
14 • If the access terminal requires opening a connection, it shall perform the procedures in
16 • If the access terminal receives a RouteUpdate.ConnectionInitiated indication it shall
17 transition to the Connection Setup State.39
18 • Access terminal may transition to the Sleep State if the requirements specified in
19 7.4.6.1.5.1.2 are satisfied.
20 8.4.6.1.5.1.17.4.6.1.5.1.1 CDMA Channel Selection

21 The access terminal shall select a CDMA Channel from the list of channels in the
22 SectorParameters message. If no channels are listed, the access terminal shall use the
23 channel it is currently monitoring. If one or more channels are available, the access
24 terminal shall use the hash function (see 13.4) to compute an index into the channel list
25 provided in the message. The access terminal shall use the following hash function
26 parameters to obtain this index:
27 • Key = SessionSeed
28 • Decorrelate = 0
29 • N = ChannelCount field of the SectorParameters message
30 Where SessionSeed is provided as public data by the Address Management Protocol.
31 8.4.6.1.5.1.27.4.6.1.5.1.2 Transition to Sleep State

32 The access terminal may transition to the Sleep State if all of the following requirements
33 are met:
39 This requirement provides Fast Connect on the access terminal side.
7-37
1 • Access terminal has received a Control Channel synchronous Sleep State capsule in the
2 current Control Channel Cycle and has determined that the SectorParameters message
3 is up to date (see 7.11.6.1.6). The current Control Channel Cycle is defined to be the
4 Control Channel Cycle that started at slot ⎣T/256⎦, where T is the current CDMA
5 System Time in slots.
6 • Access terminal received an AccessChannelMAC.TxEnded indication for every
7 AccessChannelMAC.TxStarted indication it received since entering the Monitor State.40
8 • Access terminal has not advertised a suspend period that is current (see 7.7.6.1.2.1.1).
9 The suspend period is current if the time advertised in the associated ConnectionClose
10 message is greater than the current CDMA System Time.41

13 • Access network shall select the CDMA Channel following the same specifications as the
14 access terminal, see 7.4.6.1.5.1.1.
15 • If the access network receives a ConnectionRequest message, it shall transition to the
17 • If the access network requires opening a connection with the access terminal and does
18 not use an accelerated procedure to set-up a connection, the access network shall send
19 a Page message to the access terminal over the Control Channel.
20 • The access network may use an accelerated procedure to set-up a connection with the
21 access terminal by bypassing the paging process. The access network should only use
22 this procedure if it has a reasonable estimate of the access terminal’s current location.
23 To set-up a connection in an accelerated fashion (Fast Connect) the access network
24 shall:
25 − Issue a RouteUpdate.Open command.
26 − Transition to the Connection Setup State, when the protocol receives a
27 RouteUpdate.ConnectionInitiated indication.
28 • The access network shall transition to the Sleep State if the access terminal did not
29 advertise a suspend period that is current.
30 8.4.6.1.67.4.6.1.6 Connection Setup State

31 The access terminal and the access network use the Connection Setup State to perform a
32 normal connection set-up.
40 This pairing ensures that the access terminal does not have any outstanding messages waiting for
an answer.
41 The access terminal monitors the Control Channel continuously during a suspend period thus
avoiding the delay in opening access network initiated connections due to the sleep period.
7-38
1 Figure 7.4.6.1.6-1 illustrates the process of opening a connection between the access
2 terminal and the access network when this protocol is used along with the default Route
3 Update and the default Reverse Traffic Channel MAC protocols.42
the ConnectionRequest and the RouteUpdate

are bundled in the same Access Channel MAC
Layer packet
ConnectionRequest
RouteUpdate
ACMAC
ACMAC
ACAck
Route Update Protocol

Idle State Protocol
Idle State Protocol

TrafficChannelAssignment
Pilot + DRC
RTCMAC
RTCMAC
RTCAck
TrafficChannelComplete
access terminal access network

4
5 Figure 7.4.6.1.6-1. Connection Setup Exchange

7 Upon entering the Connection Setup State the access terminal shall:
8 • Issue an OverheadMessages.Activate command,
9 • Issue a ControlChannelMAC.Activate command,
10 • Set a state timer for TIDPATSetup seconds,
11 If the access terminal receives a ConnectionDeny message, the access terminal shall return
12 a ConnectionFailed indication,
13 If the state timer expires, the access terminal shall return a ConnectionFailed indication,
42 The Fast Connect message exchange is identical except for not having the Idle State Protocol
ConnectionRequest message and the Route Update Protocol RouteUpdate message.
7-39
1 If the access terminal receives a RouteUpdate.ConnectionOpened indication, it shall return a

2 ConnectionOpened indication and transition to the Inactive State.

4 If the access network entered this state due to receiving a RouteUpdate.ConnectionInitiated
5 indication, it shall perform the following:
6 • Set state timer for TIDPANSetup seconds.
7 • If the protocol receives a RouteUpdate.ConnectionOpened indication, the access
8 network shall return a ConnectionOpened indication and transition to the Inactive
9 State.
10 • If the state timer expires, the access network shall return a ConnectionFailed
11 indication and shall transition to the Sleep State.
12 Otherwise, the access network shall perform the following:
13 Upon reception of a ConnectionRequest message while in this state or if the access network
14 entered this state due to reception of a ConnectionRequest message, Upon reception of a
15 ConnectionRequest message the access network shall perform the following:
16 • If the access network denies the connection request, it should send the access terminal
17 a ConnectionDeny message, shall return a ConnectionFailed indication, and shall
18 transition to the Sleep State.
20 − Set state timer for TIDPANSetup seconds.
22 − If the protocol receives a RouteUpdate.ConnectionOpened indication, the access
23 network shall return a ConnectionOpened indication and transition to the
24 Inactive State.
25 − If the state timer expires, the access network shall return a ConnectionFailed
27 • If the access network did not enter this state as a result of receiving a
28 ConnectionRequest message, and if the access network does not receive a
29 ConnectionRequest message within an implementation dependent time interval, then
30 the access network shall return a ConnectionFailed indication, and shall transition to
31 the Sleep State.
33 8.4.6.2.17.4.6.2.1 Page
34 The access network sends the Page message to direct the access terminal to request a
35 connection.
36
7-40
Field Length (bits)

MessageID 8

2
Channels CCsynSS SLP Best Effort
3 8.4.6.2.27.4.6.2.2 ConnectionRequest
4 The access terminal sends the ConnectionRequest message to request a connection.
5
Field Length (bits)
MessageID 8
TransactionID 8
RequestReason 4
Reserved 4
8 ConnectionRequest message sent.
9 RequestReason The access terminal shall set this field to one of the request reasons
10 as shown in Table 7.4.6.2-1.
11 Table 7.4.6.2-1. Encoding of the RequestReason Field
Field value Description

0x0 Access Terminal Initiated
0x1 Access Network Initiated
All other values are invalid
14
15 8.4.6.2.37.4.6.2.3 ConnectionDeny
16 The access network sends the ConnectionDeny message to deny a connection.
17
7-41
Field Length (bits)

MessageID 8
TransactionID 8
DenyReason 4
Reserved 4
3 the corresponding ConnectionRequest message.
4 DenyReason The access network shall set this field to indicate the reason it is
5 denying the connection, as shown in Table 7.4.6.2-2.
6 Table 7.4.6.2-2. Encoding of the DenyReason Field

0x0 General
0x1 Network Busy
0x2 Authentication or billing failure
7 Reserved The access network shall set this field to zero. The access terminal
9
Channels CC SLP Best Effort
11 8.4.6.3.17.4.6.3.1 Commands Sent

13 • RouteUpdate.Open (access network only)
18 8.4.6.3.27.4.6.3.2 Indications
7-42
1 • RouteUpdate.ConnectionOpened
3 • AccessChannelMAC.TxStarted
5 • AccessChannelMAC.TransmissionSuccessful
6 • AccessChannelMAC.TransmissionFailed

10 definition).
11 8.4.7.17.4.7.1 PreferredControlChannelCycle Attribute

12
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
PreferredControlChannelCycleEnabled 1 ‘0’
PreferredControlChannelCycle 0 or 15 N/A
Reserved 7 or 0 N/A
}
17 complex value.
18 PreferredControlChannelCycleEnabled
19 The sender shall set this field to ‘1’ if PreferredControlChannelCycle
20 field is included in this attribute; otherwise, the sender shall set this
22 PreferredControlChannelCycle
23 If PreferredControlChannelCycleEnabled is set to ‘1’, the sender shall
24 include this field and set it to specify the Control Channel Cycle in
7-43
1 which the access terminal transitions out of the Sleep State (see 0) in
2 order to monitor the Control Channel. The sender shall omit this field
3 if PreferredControlChannelCycleEnabled is set to ‘0’.
4 Reserved The length of this field shall be such that the attribute value record is
5 octet-aligned. The sender shall set this field to zero. The receiver shall

8

NIDPType Type field for this protocol Table 2.5.4-1
NIDPDefault Subtype field for this protocol 0x0000
NIDPSleep Number of control channel cycles 0x0c 5.12 seconds
constituting a sleep period
TIDPATSetup Maximum access terminal time in the 2.5 seconds
Connection Setup State
TIDPANSetup Maximum access network time in the 1 second

12 protocol.
7-44
1 8.57.5 Enhanced Idle State Protocol
2 8.5.17.5.1 Overview
3 The Enhanced Idle State Protocol provides the procedures and messages used by the
4 access terminal and the access network when the access terminal has acquired a network
5 and a connection is not open.
16 up a connection.
18 7.5.1-1 and Figure 7.5.1-2.
Initial State
Rx Activate

lose
or Rx C
ny
nDe
ectio
onn ce s
ful
Rx C Suc
i on see text
ss or
smi quest d
ra n
C.T ctionR Initiate
Rx RouteUpdate.ConnectionOpened e periodic
MA n
nel nne tio
han ing Co onnec
ssC C
A cce n send pdate.
Rx upo outeU
Rx
R
Connection Setup
Sleep State
State
19
20 Figure 7.5.1-1. Enhanced Idle State Protocol State Diagram (Access Terminal)
7-45

Inactive State se Sleep State

x Clo
rT
o
ny
nDe
RouteUpdate.ConnectionOpened ct io st
ne ue see text see text
o n eq
xC nR
T tio
ec
nn
x Co
Connection R
Monitor State
Setup State
2
3 Figure 7.5.1-2. Enhanced Idle State Protocol State Diagram (Access Network)
7 Channel.
procedure.
7-46
10 8.5.2.17.5.2.1 Commands
12 • Activate
13 • Deactivate
15 • Close

20 8.5.2.37.5.2.3 Public Data

23 • PageResponseAPersistence

7-47

13 7.5.4.2 Protocol Initialization for the InUse Protocol Instance

20 8.5.5.17.5.5.1 Procedures

36 then
7-48
10 network.
16
Field Length (bits)
MessageID 8
TransactionID 8

21
24
7-49
Field Length (bits)
MessageID 8
TransactionID 8

9
11 8.5.6.17.5.6.1 Procedures
13 8.5.6.1.1.17.5.6.1.1.1 Activate
18 8.5.6.1.1.27.5.6.1.1.2 Deactivate
7-50
2 8.5.6.1.1.37.5.6.1.1.3 OpenConnection
9 State.
15 8.5.6.1.1.47.5.6.1.1.4 Close

22 following:
23 • If the access terminal invokes these procedures in response to an access terminal-
24 initiated event and the ConnectionDenyBackoff attribute is set to a value in the range
25 0x00 to 0x78, then the access terminal should perform the following:
26 − If the access terminal determines that the number of control channel cycles
27 that have passed since receiving a ConnectionDeny message with DenyReason
28 set to 0x01 is less than the value of the ConnectionDenyBackoff attribute, then
29 the access terminal shall postpone sending the ConnectionRequest message
30 until the number of control channel cycles since receiving the ConnectionDeny
31 message is greater than or equal to the value specified by the
32 ConnectionDenyBackoff attribute.
7-51

3 8.5.6.1.37.5.6.1.3 T12 and T23 Computation

4 The access terminal shall compute T12 and T23 when an
5 AccessChannelMAC.TransmissionSuccessful indication or a
6 ConnectedState.ConnectionClosed indication is received. The access network shall compute
7 T12 and T23 when an AccessChannelMAC.MACLayerCapsuleReceived indication, a
8 ConnectedState.ConnectionClosed, or a RouteUpdate.ConnectionLost indication is received.
9 The access terminal and the access network shall compute T12 and T23 as follows:
T12 = Tc + Period1 − [(Tc + 256 × R ) mod Period1] + Period1 × [24 × (WakeCount1 + 1) − 1]

,
T23 = T12 + Period 2 − [(T12 + 256 × R ) mod Period 2] + Period 2 × [24 × (WakeCount 2 + 1) − 1]
10
11 where Period1 and Period2 are specified in units of slots, Tc is the current CDMA system
12 time.
13 8.5.6.1.47.5.6.1.4 Inactive State

15 If at the access terminal receives an OverheadMessages.Updated indication in this state,
16 then the access terminal shall queue the latest OverheadMessages.Updated indication for
18 8.5.6.1.57.5.6.1.5 Sleep State

28 When the access network is in the Sleep State, it is prohibited from sending unicast
29 packets to the access terminal.
34 The access network and the access terminal shall transition from the Sleep State to the
35 Monitor State in time to send and receive, respectively, the sub-synchronous capsule or the
36 synchronous capsule sent at time T satisfying the following condition:
7-52
1 [T+256×R] mod Period = Offset,

2 where T is the CDMA System Time in slots, and Offset is public data of the Control
3 Channel MAC protocol.
4 R shall be obtained as follows:
9 − N = Max(Period3/256, 1)
11 Protocol.
14 Period shall be computed as follows:
⎧Period1, CDMA System Time in slots < T12

⎪
15 Period = ⎨Period2, T12 ≤ CDMA System Time in slots < T23 .
⎪Period3, Otherwise
⎩
16 The access network and the access terminal shall compute Periodi according to Table
17 7.5.6.1.5-1.
18 Table 7.5.6.1.5-1. Computation of Periodi from SlotCyclei
SlotCyclei Periodi
0x00 to 0x06 2SlotCyclei × 4 slots
0x07 to 0x1c 2(SlotCyclei – 0x7) × 768 slots
19 8.5.6.1.67.5.6.1.6 Monitor State

20 A paging mask is defined as a periodic interval with period and duty cycle defined by three
21 associated fields PreMaskDuration, MaskDuration, and PostMaskDuration in the
22 PagingMask attribute (see 7.5.7.3).
23 When the access terminal is in the Monitor State, it shall continuously monitor the Control
24 Channel if MaskCount is equal to 0x00 or one of the following conditions is true for all
25 MaskCount paging masks specified by the PagingMask attribute:
26 T mod [(PreMaskDuration + MaskDuration + PostMaskDuration) × 4] <
27 PreMaskDuration × 4, or
28 T mod [(PreMaskDuration + MaskDuration + PostMaskDuration) × 4] ≥
29 (PreMaskDuration + MaskDuration) × 4,
7-53
1 where T is the CDMA System Time in slots, and PreMaskDuration, MaskDuration, and
2 PostMaskDuration are parameters of the PagingMask complex attribute.
4 terminal. When the access network is in the Monitor State, it should not send unicast
5 packets to the access terminal unless one of the following conditions is true for all
10 (PreMaskDuration + MaskDuration) × 4.

18 State:
22 • If the access terminal entered Monitor State to receive the synchronous capsule, it shall
23 monitor the overhead messages as specified in the Overhead Messages Protocol (see
24 7.11.6.1.6).
31 • Access terminal may transition to the Sleep State if the requirements specified in
32 7.5.6.1.6.1.2 are satisfied.

34 The access terminal shall select a CDMA Channel from the list of channels or extended
35 channels in the SectorParameters message. If no channels or extended channels are listed,
7-54
1 the access terminal shall use the channel it is currently monitoring. If one or more
2 channels are available, the access terminal shall use a hash function (see 13.4) to compute
3 an index into the subset of a subset of advertised CDMA Channels according to the
5 The access terminal shall create a combined channel list as follows:
6 • If the extended channel list is included in the SectorParameters message, the access
7 terminal shall create a combined channel list by appending each CDMA Channel in the
8 extended channel list (in order) to the set of CDMA Channels in the channel list (in
9 order). Otherwise, the access terminal shall set the combined channel list to the set of
10 CDMA Channels in the channel list.
11 • If the SupportedCDMAChannels public data of the Route Update Protocol lists any
12 channels, then the access terminal shall remove from the combined channel list the
13 following CDMA Channels:
14 − All forward CDMA Channels that are not supported by the access terminal as
15 indicated by the SupportedCDMAChannels public data of the Route Update
16 Protocol.
17 − All the forward CDMA Channels whose associated reverse CDMA Channel is
18 not supported by the access terminal as indicated by the
19 SupportedCDMAChannels public data of the Route Update Protocol.
20 The set, S, of CDMA Channels is determined as follows:
21 • If the AccessHashingChannelMaskIncluded field in the SectorParameters message is
22 not included or is included and set to ‘0’, the access terminal shall set S to the subset
23 of CDMA Channels in the combined channel list.
25 included and is set to ‘1’, the access terminal shall set S to the subset of CDMA
26 Channels in the combined channel list for which:
27 − Ni is equal to Nmax, where i is the index of the CDMA Channel in the
28 combined channel list,
29 where Nj = bitcount(AccessHashingClassMask
30 [AccessHashingMaskLength:0] ⊗ Mj), where Mj is the
31 AccessHashingChannelMask field in the SectorParameters message
32 corresponding to the jth CDMA Channel in the combined channel list;
33 Nmax is the maximum value of Nk for all k , where k is the index of the
34 CDMA Channel in the combined channel list; and
35 bitcount(x) is the number of ‘1’ bits in the binary representation of x.
36 The CDMA Channels supported by the access terminal are public data of the Route Update
37 Protocol. The access terminal shall use the following hash function parameters to obtain
38 the index into set S:
7-55
2 • N = Number of CDMA Channels in set S
3 where SessionSeed is provided as public data by the Address Management Protocol.
4 If the SystemType field of the channel record which is the result of the above hash function
5 computation is set to 0x00, then both the forward and reverse CDMA channels are
6 specified by that channel record. If the SystemType field of the channel record which is the
7 result of the hash function is set to 0x02, then the reverse CDMA channel which the access
8 terminal shall use in order to access the system is specified by the ReverseBandclass and
9 ReverseChannelNumber fields of SectorParameters message associated with the forward
10 CDMA channel as specified in the field description of ReverseChannelNumber field in the
11 SectorParameters message.

14 are met:
15 • One of the following requirements is met:
16 − The access terminal entered the Monitor State to receive the synchronous
17 capsule and has received a Control Channel synchronous Sleep State capsule
18 in the current Control Channel Cycle and has determined that the
19 SectorParameters message is up to date (see 7.11.6.1.6). The current Control
20 Channel Cycle is defined to be the Control Channel Cycle that started at slot
21 ⎣T/256⎦, where T is the current CDMA System Time in slots.
22 − The access terminal entered the Monitor State to receive a sub-synchronous
23 capsule, and has received the sub-synchronous capsule, or did not receive the
24 sub-synchronous capsule in the expected slots.

32 • Access network shall select the CDMA Channel following the same specifications as the
47This pairing ensures that the access terminal does not have any outstanding messages waiting for
an answer.
7-56
1 • If the access network receives a ConnectionRequest message, it shall transition to the

3 • If the access network requires opening a connection with the access terminal and does
4 not use an accelerated procedure to set-up a connection, the access network shall send
5 a Page message to the access terminal over the Control Channel.
6 • Access network may use an accelerated procedure to set-up a connection with the
7 access terminal by bypassing the paging process. The access network should only use
8 this procedure if it has a reasonable estimate of the access terminal’s current location.
9 To set-up a connection in an accelerated fashion (Fast Connect) the access network
10 shall:
12 − Transition to the Connection Setup State, when the protocol receives a
14 • Access network shall transition to the Sleep State if the access terminal did not
15 advertise a suspend period that is current.
16

7-57

Layer packet
ConnectionRequest
RouteUpdate
ACMAC
ACMAC
ACAck

Idle State Protocol
Idle State Protocol

Pilot + DRC
RTCMAC
RTCMAC
RTCAck

1

4 The access terminal shall comply with the following requirements.
5 • Upon entering the Connection Setup State the access terminal shall:
6 − Issue an OverheadMessages.Activate command,
7 − Issue a ControlChannelMAC.Activate command,
8 − Set a state timer for TIDPATSetup seconds,
9 • If the access terminal receives a ConnectionDeny message, the access terminal shall
10 return a ConnectionFailed indication,
11 • If the state timer expires, the access terminal shall return a ConnectionFailed
12 indication,
13 • If the access terminal receives a RouteUpdate.ConnectionOpened indication, it shall
14 return a ConnectionOpened indication and transition to the Inactive State.
7-58

2 If the ConnectionRequest message contains one or more preferred CDMA channels, then
3 the access network should assign a Traffic Channel on one of the preferred CDMA
4 channels.
5 The access network should deny the connection request if all of the following conditions are
6 true:
7 • the ConnectionRequest message from the access terminal contains one or more
8 preferred CDMA channels, and
9 • none of the preferred CDMA channels in the ConnectionRequest message can be used
10 to assign a Traffic Channel.
16 State.
31 Inactive State.
38 the Sleep State.
7-59
2 8.5.6.2.17.5.6.2.1 Page
4 connection.
5
Field Length (bits)

MessageID 8
PageResponseAPersistenceIncluded 0 or 1
PageResponseAPersistence 0 or 6
7 PageResponseAPersistenceIncluded
8 The access network shall include this field if any of the non-reserved
9 fields that follow this field are included in the message. If included,
10 the access network shall set this field as follows:
11 The access network shall set this field to ‘0’ if the
12 PageResponseAPersistenceSupported attribute is set to 0x00.
13 Otherwise, the access network shall set this field as follows:
15 PageResponseAPersistence field is included in this message.
16 Otherwise, the access network shall set this field to ‘0’.
17 PageResponseAPersistence
18 The access network shall omit this field if the
19 PageResponseAPersistenceIncluded is not included, or if the
20 PageResponseAPersistenceIncluded field is included and set to ‘0’.
21 Otherwise, the access network shall include this field and set it as
22 follows:
-n/4
23 The access network shall set this field n such that 2 is the access
24 persistence probability that the access terminal is to use when
25 responding to this Page message. The access network shall not set
26 this field to 0x3f.
27 Reserved The access network shall include Reserved bits to make the length of
28 the entire message equal to an integer number of octets. The access
29 network shall set these bits to ‘0’.
30
7-60
Channels CCsynSS CCsubsyn SLP Best Effort
3
Field Length (bits)
MessageID 8
TransactionID 8
RequestReason 4
PreferredChannelCount 5
PreferredChannelCount occurrences of the following
field:
PreferredChannel 24
Reserved 0-7 (as

needed)

10 PreferredChannelCount
11 The access terminal shall set this field to the number of occurrences
12 of the PreferredChannel field in this message.
7-61
1 PreferredChannel The access terminal shall set this field to the Channel record
2 specification for the CDMA channel on which the access terminal
3 prefers to be assigned a Traffic Channel (see 13.1).
4 EmergencyIndication50
5 If included, the access terminal shall set this field as follows: If this is
6 an emergency ConnectionRequest, then the access terminal shall set
7 this field to ‘1’. Otherwise, the access terminal shall set this field to
8 ‘0’.
11 shall set these bits to ‘0’. The access terminal shall set this field to
12 zero. The access network shall ignore this field.
13
14 8.5.6.2.37.5.6.2.3 ConnectionDeny
16
Field Length (bits)

MessageID 8
TransactionID 8
DenyReason 4
Reserved 4
50 EmergencyIndicator field is also supported in ReservationOnRequest message of Route Update
Protocol of Multi-flow Packet Application.
7-62

0x0 General
0x1 Network Busy
0x3 Preferred channel not available
4
7 given attribute.
8
Field Length (bits)
MessageID Protocol dependent

TransactionID 8

13
17
7-63
Field Length (bits)

TransactionID 8
4
8
Field Length (bits)

TransactionID 8
12
14 8.5.6.3.17.5.6.3.1 Commands Sent

7-64
1 8.5.6.3.27.5.6.3.2 Indications
8 • AccessChannelMAC.MACLayerCapsuleReceived

16 Enhanced Idle State Protocol. The access terminal and the access network shall support
17 the use of the Generic Attribute Update Protocol to update values of the following attributes
18 belonging to the Enhanced Idle State Protocol:
19 • PreferredControlChannelCycle
20 • SlottedMode
21 • PagingMask
22 • AccessHashingClassMask
23 The access terminal shall not include the AccessHashingClassMask in an
25 The access network shall not send an AttributeUpdateRequest message containing the
26 PreferredControlChannelCycle or the PagingMask attribute.
27 If the SmallSlotCycleAllowed attribute is set to 0x00, then the access network and the
28 access terminal shall not send an AttributeUpdateRequest message proposing a value of
29 the SlotCycle1 field of the SlottedMode attribute that is less than 0x06.

31 The simple configurable attributes are listed in Table 7.5.7.1-1. The access network and
32 the access terminal shall use the default values that are typed in bold italics.
7-65
1 Table 7.5.7.1-1Configurable Simple Attributes

ID
0xff SmallSlotCycleAllowed 0x00 Access terminal and access network will
not propose a value of SlotCycle1 that is
less than 0x06.
0x01 Access terminal and access network can
propose a value of SlotCycle1 that is less
than 0x06.
0x02 Reserved
to
0xff
0x0000 Access terminal and access network will
hash to channels with any access
hashing class.
AccessHashingClassMa
0xfe
sk 0x0001 Access terminal and access network will
to 0xffff hash to channels with designated access
hashing classes (see 7.5.6.1.6.1.1).
0x00- Access terminal is to observe a back off
0x78 period specified by this attribute (in units
of control channel cycles) after receiving a
ConnectionDeny message with
DenyReason field set to 0x01 before
sending an access terminal-initiated
ConnectionRequest message
0xfd ConnectionDenyBackoff 0x79- Reserved

0xfe
0xff Access terminal is to observe an
implementation-specific back off period
after receiving a ConnectionDeny
message with DenyReason field set to
0x01 before sending an access terminal-
initiated ConnectionRequest message
0x00 Access terminal does not support
PageResponseAPersistence.
PageResponseAPersiste 0x01 Access terminal supports

0xfc PageResponseAPersistence.
nceSupported
All other Reserved
values
3 8.5.7.2.17.5.7.2.1 PreferredControlChannelCycle Attribute

4
7-66
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
Reserved 7 or 0 N/A
}
5 complex value.
9 field to ‘0’.
19 8.5.7.2.27.5.7.2.2 SlottedMode Attribute

20
7-67
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
SlotCycle1 5 0x9
SlotCycle2 5 0x9
SlotCycle3 5 0x9
WakeCount1 4 0x0
WakeCount2 4 0x0
Reserved 1 N/A
}
5 complex value.
6 SlotCycle1 The sender shall set this field to SlotCycle1. The sender shall not set
7 this field to more than 0x1c.
8 SlotCycle2 The sender shall set this field to SlotCycle2. SlotCycle2 shall be
9 greater than or equal to SlotCycle1. The sender shall not set this field
10 to more than 0x1c.
14 WakeCount1 The sender shall set this field to WakeCount1.
15 WakeCount2 The sender shall set this field to WakeCount2. WakeCount2 shall be
16 greater or equal to than WakeCount1.
18 field.
19 8.5.7.37.5.7.3 PagingMask Attribute

20
7-68
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
MaskCount 8 0x00
MaskCount occurrences of the following four fields:
MaskPurpose 8 N/A
PreMaskDuration 16 N/A
MaskDuration 16 N/A
PostMaskDuration 16 N/A
5 complex value.
6 MaskCount The sender shall set this field to the number of paging masks
7 specified in this complex attribute.
8 MaskPurpose The sender shall set this field to indicate the purpose of the mask
9 according to Table 7.5.7.2.2-1.
10 Table 7.5.7.2.2-1. Definition of MaskPurpose Field of a Paging Mask
MaskPurpose Value Meaning

0x00 Unspecified purpose.
0x01 The paging mask is associated with monitoring the
cdma2000 1x system (see [3]).
0x02-0xff Specified by [10].
11 PreMaskDuration The sender shall set this field to the length of the pre-mask duration
12 in units of four slots.
13 MaskDuration The sender shall set this field to the length of the masked duration in
14 units of four slots.
15 PostMaskDuration The sender shall set this field to the length of the post-mask duration
7-69

2

NIDPEnhanced Subtype field for this protocol 0x0001

6 protocol.
7-70
1 8.67.6 Quick Idle State Protocol
2 8.6.17.6.1 Overview
3 The Quick Idle State Protocol provides the procedures and messages used by the access
4 terminal and the access network when the access terminal has acquired a network and a
5 connection is not open.
16 up a connection.
18 7.6.1-1 and Figure 8.6.1-2.
Initial State
Rx Activate

lose
or Rx C
ny
nDe
ectio
onn ce s
ful
Rx C Suc
i on see text
ss or
smi quest d
ra n
C.T ctionR Initiate
Rx RouteUpdate.ConnectionOpened e periodic
MA n
nel nne tio
han ing Co onnec
ssC C
A cce n send pdate.
Rx upo outeU
Rx
R
Connection Setup
Sleep State
State
19
20 Figure 7.6.1-1. Quick Idle State Protocol State Diagram (Access Terminal)
7-71

Inactive State e Sleep State

Clos
x
o rT
ny
nDe
RouteUpdate.ConnectionOpened tio es
t
ec u see text see text
o nn eq
xC nR
T tio
n ec
n
Co
Connection Rx
Monitor State
Setup State
1
2 Figure 7.6.1-2. Quick Idle State Protocol State Diagram (Access Network)
6 Channel.
procedure.
7-72
10 8.6.2.17.6.2.1 Commands
12 • Activate
13 • Deactivate
15 • Close

20 8.6.2.37.6.2.3 Public Data

23 • QuickPaging
24 • PageResponseAPersistence

7-73

13 7.6.4.2 Protocol Initialization for the InUse Protocol Instance

20 8.6.5.17.6.5.1 Procedures

29 • The value of the following public data of the InUse protocol shall be set to the
30 corresponding attribute value of the InConfiguration protocol instance:
31 − QuickPaging
7-74
4 then
14 network.
20
Field Length (bits)
MessageID 8
TransactionID 8

25
7-75
Field Length (bits)
MessageID 8
TransactionID 8

10
12 8.6.6.17.6.6.1 Procedures
14 8.6.6.1.1.17.6.6.1.1.1 Activate
19 8.6.6.1.1.27.6.6.1.1.2 Deactivate
7-76

3 8.6.6.1.1.37.6.6.1.1.3 OpenConnection
10 State.
16 8.6.6.1.1.47.6.6.1.1.4 Close

23 following:
24 • If the access terminal invokes these procedures in response to an access terminal-
25 initiated event and the ConnectionDenyBackoff attribute is set to a value in the range
26 0x00 to 0x78, then the access terminal should perform the following:
27 − If the access terminal determines that the number of control channel cycles
28 that have passed since receiving a ConnectionDeny message with DenyReason
29 set to 0x01 is less than the value of the ConnectionDenyBackoff attribute, then
30 the access terminal shall postpone sending the ConnectionRequest message
31 until the number of control channel cycles since receiving the ConnectionDeny
32 message is greater than or equal to the value specified by the
33 ConnectionDenyBackoff attribute.
7-77

3 8.6.6.1.37.6.6.1.3 T12 and T23 Computation

4 The access terminal shall compute T12 and T23 when an
5 AccessChannelMAC.TransmissionSuccessful indication or a
6 ConnectedState.ConnectionClosed indication is received. The access network shall compute
7 T12 and T23 when an AccessChannelMAC.MACLayerCapsuleReceived indication, a
8 ConnectedState.ConnectionClosed, or a RouteUpdate.ConnectionLost indication is received.
9 The access terminal and the access network shall compute T12 and T23 as follows:
T12 = Tc + PagePeriod1 − [(Tc + 256 × R ) mod PagePeriod1] + PagePeriod1× [24 × (WakeCount1 + 1) − 1]
10 ,
T23 = T12 + PagePeriod 2 − [(T12 + 256 × R ) mod PagePeriod 2] + PagePeriod 2 × [24 × (WakeCount2 + 1) − 1]
11 where PagePeriod1 and PagePeriod2 are specified in units of slots, Tc is the current CDMA
12 system time.
13 8.6.6.1.47.6.6.1.4 Inactive State

15 If at the access terminal receives an OverheadMessages.Updated indication in this state,
16 then the access terminal shall queue the latest OverheadMessages.Updated indication for
18 8.6.6.1.57.6.6.1.5 Sleep State

28 When the access network is in the Sleep State, it is prohibited from sending unicast
29 packets to the access terminal.
34 If QuickPagingEnabled is ‘0’, then the access network and the access terminal shall
35 transition from the Sleep State to the Monitor State in time to send and receive,
7-78
1 respectively, the sub-synchronous capsule or the synchronous capsule sent at time T

2 satisfying the following condition:
3 [T+256×R] mod PagePeriod = Offset,
6 If QuickPagingEnabled is ‘1’ and SubSyncQuickPaging is ‘1’, then the access network shall
7 transition from the Sleep State to the Monitor State in time to send the quick synchronous
8 capsule sent at time T satisfying the following condition:
9 [T+1+256×R] mod PagePeriod = Offset,
12 If QuickPagingEnabled is ‘1’ and SubSyncQuickPaging is ‘0’, then the access network shall
13 transition from the Sleep State to the Monitor State in time to send the quick synchronous
14 capsule sent at time T satisfying the following condition:
15 [T+1+256×R] mod (max[PagePeriod, 256]) = Offset,
18 If QuickPagingEnabled is ‘1’, then the access network shall transition from the Sleep State
19 to the Monitor State (if it is not already in the Monitor State) in time to send the sub-
20 synchronous capsule or the synchronous capsule sent at time T satisfying the following
21 condition:
22 [T+256×R] mod PagePeriod = Offset,
25 If QuickPagingEnabled is ‘1’ and SubSyncQuickPaging is ‘1’, then the access terminal
26 should transition from the Sleep State to the Monitor State in time to receive the quick
31 If QuickPagingEnabled is ‘1’ and SubSyncQuickPaging is ‘0’, then the access terminal
32 should transition from the Sleep State to the Monitor State in time to receive the quick
34 [T+1+256×R] mod (max[PagePeriod, 256]) = Offset
35 [T+1+256×R] mod [ma(PagePeriod, 256)] = Offset,
7-79
1 If QuickPagingEnabled is ‘1’ and the access terminal did not transition from the Sleep State
2 to the Monitor State to receive a quick synchronous capsule sent at time T satisfying
3 [T+1+256×R] mod PagePeriod = Offset, then the access terminal shall transition from the
4 Sleep State to the Monitor State to receive the sub-synchronous or synchronous capsule
5 sent at time T+1, where T is the CDMA System Time in slots, and Offset is public data of
6 the Control Channel MAC protocol.
7 R shall be obtained as follows:
12 − N = Max(PagePeriod3/256, 1)
14 Protocol.
17 PagePeriod shall be computed as follows:
⎧PagePeriod1, CDMA System Time in slots < T12

⎪
18 PagePeriod = ⎨PagePeriod2, T12 ≤ CDMA System Time in slots < T23 .
⎪PagePeriod3, Otherwise
⎩
19 The access network and the access terminal shall compute PagePeriodi according to Table
20 7.6.6.1.5-1.
21 Table 7.6.6.1.5-1. Computation of PagePeriodi from SlotCyclei
SlotCyclei PagePeriodi
0x00 to 0x06 2SlotCyclei × 4 slots
0x07 to 0x1c 2(SlotCyclei – 0x7) × 768 slots
22 8.6.6.1.67.6.6.1.6 Monitor State

23 A paging mask is defined as a periodic interval with period and duty cycle defined by three
24 associated fields PreMaskDuration, MaskDuration, and PostMaskDuration in the
25 PagingMask attribute (see 7.6.7.3).

7-80
2 State:
3 • If a QuickPage message is received, then the access terminal shall generate a
4 ControlChannelMAC.ResetSupervisionTimer command.
8 • If the access terminal entered Monitor State (or stayed in the Monitor State) to receive
9 the synchronous capsule, it shall monitor the overhead messages as specified in the
10 Overhead Messages Protocol (see 7.11.6.1.6).
17 • If the access terminal receives a QuickPage message with ConfigurationChange field set
18 to ‘11’, then the access terminal shall generate an OverheadMessages.ANRedirect
19 command.
20 • If the access terminal receives a QuickPage message with ConfigurationChange field not
21 set to ‘11’, then the access terminal shall generate an
22 OverheadMessages.CheckConfiguration command, along with the following arguments:
23 − (PN Offset, CDMA Channel) associated with the sector on which the QuickPage
24 message was received.
25 − ConfigurationChange field of the QuickPage message.
26 • The access terminal may transition to the Sleep State if the requirements specified in
27 7.6.6.1.6.1.2 are satisfied.
28 When the access terminal is in the Monitor State, it shall continuously monitor the Control
29 Channel if MaskCount is equal to 0x00 or one of the following conditions is true for all
34 (PreMaskDuration + MaskDuration) × 4,
7-81

2 The access terminal shall select a CDMA Channel from the list of channels or extended
3 channels in the SectorParameters message. If no channels or extended channels are listed,
4 the access terminal shall use the channel it is currently monitoring. If one or more
5 channels are available, the access terminal shall use a hash function (see 13.4) to compute
6 an index into the subset of a subset of advertised CDMA Channels according to the
8 The access terminal shall create a combined channel list as follows:
9 • If the extended channel list is included in the SectorParameters message, the access
10 terminal shall create a combined channel list by appending each CDMA Channel in the
11 extended channel list (in order) to the set of CDMA Channels in the channel list (in
12 order). Otherwise, the access terminal shall set the combined channel list to the set of
13 CDMA Channels in the channel list.
14 • If the SupportedCDMAChannels public data of the Route Update Protocol lists any
15 channels, then the access terminal shall remove from the combined channel list the
16 following CDMA Channels:
17 − All forward CDMA Channels that are not supported by the access terminal as
18 indicated by the SupportedCDMAChannels public data of the Route Update
19 Protocol.
20 − All the forward CDMA Channels whose associated reverse CDMA Channel is
21 not supported by the access terminal as indicated by the
22 SupportedCDMAChannels public data of the Route Update Protocol.
23 The set, S, of CDMA Channels is determined as follows:
25 not included or is included and set to ‘0’, the access terminal shall set S to the subset
26 of CDMA Channels in the combined channel list.
28 included and is set to ‘1’, the access terminal shall set S to the subset of CDMA
29 Channels in the combined channel list for which:
30 − Ni is equal to Nmax, where i is the index of the CDMA Channel in the
31 combined channel list,
32 where Nj = bitcount(AccessHashingClassMask
33 [AccessHashingMaskLength:0] ⊗ Mj), where Mj is the
34 AccessHashingChannelMask field in the SectorParameters message
35 corresponding to the jth CDMA Channel in the combined channel list;
36 Nmax is the maximum value of Nk for all k , where k is the index of the
37 CDMA Channel in the combined channel list; and
38 bitcount(x) is the number of ‘1’ bits in the binary representation of x.
7-82
1 The CDMA Channels supported by the access terminal are public data of the Route Update
2 Protocol. The access terminal shall use the following hash function parameters to obtain
3 the index into set S:
6 • N = Number of CDMA Channels in set S
7 where SessionSeed is provided as public data by the Address Management Protocol.
8 If the SystemType field of the channel record which is the result of the above hash function
9 computation is set to 0x00, then both the forward and reverse CDMA channels are
10 specified by that channel record. If the SystemType field of the channel record which is the
11 result of the hash function is set to 0x02, then the reverse CDMA channel which the access
12 terminal shall use in order to access the system is specified by the ReverseBandclass and
13 ReverseChannelNumber fields of SectorParameters message associated with the forward
14 CDMA channel as specified in the field description of ReverseChannelNumber field in the

18 are met:
19 • One of the following requirements is met:
20 − The access terminal entered the Monitor State to receive a quick synchronous
21 capsule and received a QuickPage message with the Wth, Xth, Yth , or Zth
22 QuickPageIndicator field set to ‘0’ and the ConfigutationChange
23 ConfigurationChange field is not set to ‘11’, and has determined that the
24 SectorParameters message is up to date (see 8.10.6.1.6). The access terminal
25 shall set W, X, Y, and Z equal to the sum of the output of the hash function
26 (see 13.414.4) and the product of (1 + QuickPIPerGroupCountMinusOne) and
27 0, 1, 2, and 3, respectively. When applying the hash function in order to
28 calculate W, X, Y, and Z, the access terminal shall use Decorrelate values of 2 ×
29 SessionSeed[11:0], 6 × SessionSeed[11:0], 14 × SessionSeed[11:0], and 30 ×
30 SessionSeed[11:0], respectively.X is the result of applying the hash function
31 (see 14.4) using the following parameters The access terminal shall use Key
32 and N values as follows:
33 + Key = SessionSeed, which is provided as public data of the Address
34 Management Protocol,
35 + N = 1 + QuickPIPerGroupCountMinusOne QuickPageIndicatorCountMinusOne
36 field of the QuickPage message, and
37 +Decorrelate = 0xa241.
7-83
1 − The access terminal entered the Monitor State or stayed in the Monitor State to
2 receive the synchronous capsule and has received a Control Channel
3 synchronous Sleep State capsule in the current Control Channel Cycle and
4 has determined that the SectorParameters message is up to date (see
5 8.10.6.1.6). The current Control Channel Cycle is defined to be the Control
6 Channel Cycle that started at slot ⎣T/256⎦, where T is the current CDMA
7 System Time in slots.
8 − The access terminal entered the Monitor State or stayed in the Monitor State to
9 receive a sub-synchronous capsule, and has received the sub-synchronous
10 capsule, or did not receive the sub-synchronous capsule in the expected slots.

18 terminal. When the access network is in the Monitor State, it should not send unicast
19 packets to the access terminal unless one of the following conditions is true for all
24 (PreMaskDuration + MaskDuration) × 4.
27 When the access network is in the Monitor State and if QuickPagingEnabled is ‘1’, then the
28 access network shall not send unicast packets to the access terminal at time T satisfying
29 the following condition:
32 Channel MAC protocol, and R is computed as defined in 7.6.6.1.5.
33 If QuickPagingEnabled is ‘1’, then the access network should send a QuickPage message in
34 the quick synchronous capsule that occurs at time T satisfying the following condition:
55This pairing ensures that the access terminal does not have any outstanding messages waiting for
an answer.
7-84

3 Channel MAC protocol, and R is computed as defined in 7.6.6.1.5.
4 Access network shall select the CDMA Channel following the same specifications as the
8 If the access network requires opening a connection with the access terminal and does not
9 use an accelerated procedure to set-up a connection, the access network shall send a Page
10 message to the access terminal over the Control Channel.
11 Access network may use an accelerated procedure to set-up a connection with the access
12 terminal by bypassing the paging process. The access network should only use this
13 procedure if it has a reasonable estimate of the access terminal’s current location. To set-
14 up a connection in an accelerated fashion (Fast Connect) the access network shall:
15 • Issue a RouteUpdate.Open command.
16 • Transition to the Connection Setup State, when the protocol receives a
18 Access network shall transition to the Sleep State if the access terminal did not advertise a
19 suspend period that is current.

7-85

Layer packet
ConnectionRequest
RouteUpdate
ACMAC
ACMAC
ACAck

Idle State Protocol
Idle State Protocol

Pilot + DRC
RTCMAC
RTCMAC
RTCAck

1

4 The access terminal shall comply with the following requirements.
5 • Upon entering the Connection Setup State the access terminal shall:
6 − Issue an OverheadMessages.Activate command,
7 − Issue a ControlChannelMAC.Activate command,
8 − Set a state timer for TIDPATSetup seconds,
9 • If the access terminal receives a ConnectionDeny message, the access terminal shall
10 return a ConnectionFailed indication,
11 • If the state timer expires, the access terminal shall return a ConnectionFailed
12 indication,
13 • If the access terminal receives a RouteUpdate.ConnectionOpened indication, it shall
14 return a ConnectionOpened indication and transition to the Inactive State.
7-86

2 If the ConnectionRequest message contains one or more preferred CDMA channels, then
3 the access network should assign a Traffic Channel on one of the preferred CDMA
4 channels.
5 The access network should deny the connection request if all of the following conditions are
6 true:
7 • the ConnectionRequest message from the access terminal contains one or more
8 preferred CDMA channels, and
9 • none of the preferred CDMA channels in the ConnectionRequest message can be used
10 to assign a Traffic Channel.
16 State.
31 Inactive State.
38 the Sleep State.
7-87
1 • .
3 8.6.6.2.17.6.6.2.1 Page
5 connection.
6
Field Length (bits)

MessageID 8
PageResponseAPersistenceIncluded 0 or 1
PageResponseAPersistence 0 or 6
8 PageResponseAPersistenceIncluded
10 fields that follow this field are included in the message. If included,
11 the access network shall set this field as follows:
13 PageResponseAPersistenceSupported attribute is set to 0x00.
14 Otherwise, the access network shall set this field as follows:
16 PageResponseAPersistence field is included in this message.
18 PageResponseAPersistence
20 PageResponseAPersistenceIncluded is not included, or if the
21 PageResponseAPersistenceIncluded field is included and set to ‘0’.
22 Otherwise, the access network shall include this field and set it as
23 follows:
-n/4
24 The access network shall set this field n such that 2 is the access
25 persistence probability that the access terminal is to use when
26 responding to this Page message. The access network shall not set
27 this field to 0x3f.
28 Reserved The access network shall include Reserved bits to make the length of
29 the entire message equal to an integer number of octets. The access
30 network shall set these bits to ‘0’.
31
7-88
Channels CCsynSS CCsubsyn SLP Best Effort
3
Field Length (bits)
MessageID 8
TransactionID 8
RequestReason 4
PreferredChannelCount 5
PreferredChannelCount occurrences of the following
field:
PreferredChannel 24
Reserved 0-7 (as
needed)

10 PreferredChannelCount
12 of the PreferredChannel field in this message.
13 PreferredChannel The access terminal shall set this field to the Channel record
14 specification for the CDMA channel on which the access terminal
15 prefers to be assigned a Traffic Channel (see 13.1).
7-89
1 EmergencyIndication58
2 If included, the access terminal shall set this field as follows: If this is
3 an emergency ConnectionRequest, then the access terminal shall set
4 this field to ‘1’. Otherwise, the access terminal shall set this field to
5 ‘0’.
11
12 8.6.6.2.37.6.6.2.3 ConnectionDeny
14
Field Length (bits)

MessageID 8
TransactionID 8
DenyReason 4
Reserved 4
58 EmergencyIndicator field is also supported in ReservationOnRequest message of Route Update
Protocol of Multi-flow Packet Application.
7-90

0x0 General
0x1 Network Busy
0x3 Preferred channel not available
4
5 8.6.6.2.47.6.6.2.4 QuickPage
6 The access network sends the QuickPage message to inform the access terminal of the
7 likelihood of a Page message directed to the access terminal.
8
Field Length (bits)

MessageID 8
ConfigurationChange 2
QuickPIPerGroupCountMinusOneQui 86
ckPageIndicatorCountMinusOne
4 × (QuickPIPerGroupCountMinusOne + 1)
QuickPageIndicatorCountMinusOne + 1 occurrences of the
following field:
QuickPageIndicator 1
10 ConfigurationChange
11 If the Redirect public data of the Overhead Message Protocol is ‘1’,
13 access network shall set this field as follows:
14 Every time an OverheadMessages.ConfigurationChanged indication is
15 received, the access network shall set this field in subsequent
16 QuickPage messages to one more (modulo ‘11’) than the last value of
7-91
1 this field before the indication was received and when the Redirect
2 public data of the Overhead Message Protocol was ‘0’.
3 QuickPIPerGroupCountMinusOne
4 The access network shall set this field to one less than the number of
5 paging indicators contained in each of the four hashing groups
6 within the QuickPageIndicator fields in this message.
7 QuickPageIndicatorCountMinusOne
9 occurrences of the QuickPageIndicator field in this message.
10 QuickPageIndicator
11 The access network shall set the Wth, Xth, Yth, and Zth occurrences
12 of this field to ‘1’ if the synchronous or sub-synchronous capsule that
13 follows the quick synchronous capsule in which this message is sent
14 carries a unicast message directed to the access terminal. The access
15 network shall set W, X, Y, and Z equal to the sum of the output of the
16 hash function (see 13.414.4) and the product of (1 +
17 QuickPIPerGroupCountMinusOne) and 0, 1, 2, and 3, respectively.
18 When applying the hash function in order to calculate W, X, Y, and Z,
19 the access network shall use Decorrelate values of 2 ×
20 SessionSeed[11:0], 6 × SessionSeed[11:0], 14 × SessionSeed[11:0],
21 and 30 × SessionSeed[11:0], respectively. The access network shall
22 use Key and N values as follows:
23 Key = SessionSeed, which is provided as public data of the Address
24 Management Protocol, and
25 N = 1 + QuickPIPerGroupCountMinusOne.
26 QuickPageIndicator The access network shall set the Xth occurrence of this field to ‘1’ if
27 the synchronous or sub-synchronous capsule that follows the quick
28 synchronous capsule in which this message is sent carries a unicast
29 message directed to the access terminal. X is the result of applying
31 Key = SessionSeed, which is provided as public data of the Address
32 Management Protocol,
33 N = 1 + QuickPageIndicatorCountMinusOne, and
34 Decorrelate = 0xa241.
37 network shall set this field to zero. The access terminal shall ignore
38 this field.
39
7-92
Channels CCsynQ SLP Best Effort
3 given attribute.
4
Field Length (bits)

TransactionID 8

9
13
Field Length (bits)

TransactionID 8
17
7-93
4
Field Length (bits)

TransactionID 8
8
10 8.6.6.3.17.6.6.3.1 Commands Sent

17 • ControlChannelMAC.ResetSupervisionTimer (access terminal only)
18 • OverheadMessages.ANRedirect
19 • OverheadMessages.CheckConfiguration
20 8.6.6.3.27.6.6.3.2 Indications
7-94
3 • AccessChannelMAC.MACLayerCapsuleReceived
8 • OverheadMessages.ConfigurationChanged

11 Generic Attribute Update Protocol to update configurable attributes belonging to the Quick
12 Idle State Protocol. The access terminal and the access network shall support the use of
13 the Generic Attribute Update Protocol to update values of the following attributes belonging
14 to the Quick Idle State Protocol:
15 • PreferredControlChannelCycle
16 • SlottedMode
17 • PagingMask
18 • AccessHashingClassMask
19 • QuickPaging
20 The access terminal shall not include the AccessHashingClassMask in an
22 The access network shall not send an AttributeUpdateRequest message containing the
23 PreferredControlChannelCycle or the PagingMask attribute.
24 If the SmallSlotCycleAllowed attribute is set to 0x00, then the access network and the
25 access terminal shall not send an AttributeUpdateRequest message proposing a value of
26 the SlotCycle1 field of the SlottedMode attribute that is less than 0x06.

30 Table 7.6.7.1-1. Configurable Simple Attributes

ID
0xff
SmallSlotCycleAllowed not propose a value of SlotCycle1 that is
less than 0x06.
7-95

ID
0x01 Access terminal and access network can
propose a value of SlotCycle1 that is less
than 0x06.
0x02 Reserved
to
0xff
hash to channels with any access
hashing class.
AccessHashingClassMa
0xfe
sk 0x0001 Access terminal and access network will
to 0xffff hash to channels with designated access
hashing classes (see 7.6.6.1.6.1.1).
0x00- Access terminal is to observe a back off
0x78 period specified by this attribute (in units
of control channel cycles) after receiving a
ConnectionDeny message with
DenyReason field set to 0x01 before
sending an access terminal-initiated
ConnectionRequest message.
0xfd ConnectionDenyBackoff 0x79- Reserved

0xfe
0xff Access terminal is to observe an
implementation-specific back off period
after receiving a ConnectionDeny
message with DenyReason field set to
0x01 before sending an access terminal-
initiated ConnectionRequest message.
0x00 Access terminal does not support
PageResponseAPersistence.
PageResponseAPersiste 0x01 Access terminal supports

0xfc PageResponseAPersistence.
nceSupported
All other Reserved
values
2 8.6.7.2.17.6.7.2.1 PreferredControlChannelCycle Attribute

3
7-96
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
Reserved 7 or 0 N/A
}
5 complex value.
9 field to ‘0’.
19 8.6.7.2.27.6.7.2.2 SlottedMode Attribute

20
7-97
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
SlotCycle1 5 0x9
SlotCycle2 5 0x9
SlotCycle3 5 0x9
WakeCount1 4 0x0
WakeCount2 4 0x0
Reserved 1 N/A
}
5 complex value.
6 SlotCycle1 The sender shall set this field to SlotCycle1. The sender shall not set
7 this field to more than 0x1c.
14 WakeCount1 The sender shall set this field to WakeCount1.
15 WakeCount2 The sender shall set this field to WakeCount2. WakeCount2 shall be
16 greater or equal to than WakeCount1.
18 field.
19 8.6.7.37.6.7.3 PagingMask Attribute

20
7-98
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
MaskCount 8 0x00
MaskCount occurrences of the following four fields:
MaskPurpose 8 N/A
PreMaskDuration 16 N/A
MaskDuration 16 N/A
PostMaskDuration 16 N/A
5 complex value.
6 MaskCount The sender shall set this field to the number of paging masks
7 specified in this complex attribute.
8 MaskPurpose The sender shall set this field to indicate the purpose of the mask
9 according to Table 7.6.7.2.2-1.
10 Table 7.6.7.2.2-1. Definition of MaskPurpose Field of a Paging Mask
MaskPurpose Value Meaning

0x00 Unspecified purpose.
0x01 The paging mask is associated with monitoring the
cdma2000 1x system (see [3]).
0x02-0xff Specified by [10].
11 PreMaskDuration The sender shall set this field to the length of the pre-mask duration
13 MaskDuration The sender shall set this field to the length of the masked duration in
14 units of four slots.
15 PostMaskDuration The sender shall set this field to the length of the post-mask duration
7-99
1 8.6.7.47.6.7.4 QuickPaging Attribute

2
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
QuickPagingEnabled 1 0x00
SubSyncQuickPaging 1 N/A
Reserved 6 N/A
7 complex value.
8 QuickPagingEnabled The sender shall set this field to ‘1’ if the access network is to
9 transmit QuickPage messages. Otherwise, the sender shall set this
11 SubSyncQuickPaging
12 If QuickPagingEnabled is set to ‘0’, then the sender shall set this field
13 to ‘0’. Otherwise, the sender shall set this field as follows:
14 The sender shall set this field to ‘1’ if the access network is to send
15 QuickPage messages in quick synchronous capsules that
16 immediately precede sub-synchronous capsules. Otherwise, the
17 sender shall set this field to ‘0’.
18 Reserved The sender shall set this field to ‘000000’. The receiver shall ignore
19 this field.

21
7-100

NIDPEnhanced Subtype field for this protocol 0x0002

4 protocol.
7-101
1 8.77.7 Default Connected State Protocol
2 8.7.17.7.1 Overview
3 The Default Connected State Protocol provides procedures and messages used by the
4 access terminal and the access network while a connection is open.
7 • Open State: In this state the access terminal can use the Reverse Traffic Channel and
8 the access network can use the Forward Traffic Channel and Control Channel to send
9 application traffic to each other.
10 • Close State: This state is associated only with the access network. In this state the
11 access network waits for connection resources to be safely released.
12 Figure 7.7.1-1 and
13 Figure 7.7.1-2 show the state transition diagrams at the access terminal and the access
14 network respectively.
Rx Activate
Initial State
Inactive
Open State
State
Rx Deactivate, or
15
Tx ConnectionClose
16 Figure 7.7.1-1. Default Connected State Protocol State Diagram (Access Terminal)
7-102
Rx Activate
Initial State
Inactive State Open State
Rx ConnectionClose or
Rx DeActivate
Rx ConnectionClose
Tx ConnectionClose
or timer expires
Close State
3 Figure 7.7.1-2. Default Connected State Protocol State Diagram (Access Network)
5 8.7.2.17.7.2.1 Commands
7 • Activate
8 • Deactivate
9 • CloseConnection

12 • ConnectionClosed
13 8.7.2.37.7.2.3 Public Data

16 • SuspendTime advertised by the access terminal

7-103


20 8.7.5.17.7.5.1 Procedures

30 then
7-104
3 − The access terminal and the access network shall set the initial state of the
4 InConfiguration protocol instance to the Inactive State.
6 instance for the Connected State Protocol at the access terminal and the
7 access network.
13
Field Length (bits)
MessageID 8
TransactionID 8
18
21
7-105
Field Length (bits)
MessageID 8
TransactionID 8

9
11 8.7.6.17.7.6.1 Procedures
13 8.7.6.1.1.17.7.6.1.1.1 Activate
15 • The access terminal shall transition to the Open State.
16 • The access network shall transition to the Open State.
17 When the protocol receives this command in any other state it shall be ignored.
18 8.7.6.1.1.27.7.6.1.1.2 Deactivate
19 When the protocol receives a Deactivate command in the Close State or in the Inactive
20 state, the command shall be ignored.
21 When the protocol receives this command in the Open State:
22 • The access terminal shall perform the cleanup procedures defined in 7.7.6.1.2.1.2.
23 • The access network shall perform the cleanup procedures defined in 7.7.6.1.2.2.2, and
7-106
1 8.7.6.1.1.37.7.6.1.1.3 CloseConnection
2 When the protocol receives a CloseConnection command in the Close State or in the
3 Inactive state, the command shall be ignored.
4 When the protocol receives this command in the Open State:
5 • The access terminal shall send a ConnectionClose message to the access network and
6 perform the cleanup procedures defined in 7.7.6.1.2.1.2.
7 • The access network shall send a ConnectionClose message to the access terminal and
8 transition to the Close State.
9 8.7.6.1.27.7.6.1.2 Open State

10 In the Open State, the access terminal and the access network maintain a connection and
11 can use it to exchange application traffic on the Reverse Traffic Channel, Forward Traffic
12 Channel, and Control Channel.

15 Upon entering the Open State, the access terminal shall issue the following commands:
18 The access terminal shall comply with the following requirements when in the Open State:
19 • The access terminal shall receive the Control Channel and the Forward Traffic Channel.
20 • The access terminal shall not transmit on the Access Channel.
21 • The access terminal shall monitor the overhead messages as specified in the Overhead
22 Messages Protocol (see 7.11.6.1.6).
23 • If the access terminal receives a ConnectionClose message, it shall send a
24 ConnectionClose message with CloseReason set to “Close Reply” and execute the
25 cleanup procedures defined in 7.7.6.1.2.1.2. If the access terminal sends a
26 ConnectionClose message, it may advertise, as part of the ConnectionClose message,
27 that it shall be monitoring the Control Channel continuously, until a certain time
28 following the closure of the connection. This period is called a suspend period, and can
29 be used by the access network to accelerate the process of sending a unicast packet
30 (and specifically, a Page message or TrafficChannelAssignment message) to the access
31 terminal.
32 • If the access terminal sends a ConnectionClose message in response to a
33 ConnectionClose message with CloseReason field set to ‘100’, then the access terminal
34 should advertise a non-zero suspend period in the ConnectionClose message. The
35 access terminal shall not set the CloseReason field in a ConnectionClose message to
36 ‘100’ or ‘101’.
7-107
1 8.7.6.1.2.1.27.7.6.1.2.1.2 Cleanup Procedures

2 If the access terminal executes cleanup procedures it shall:
3 • Issue RouteUpdate.Close command.
4 • Return a ConnectionClosed indication.

8 The access network shall comply with the following requirements when in the Open State:
9 • Access network shall receive the Reverse Traffic Channel and may transmit on the
10 Forward Traffic Channel.
11 • If access network receives a ConnectionClose message, it shall consider the connection
12 closed, and it should execute the cleanup procedures defined in 7.7.6.1.2.2.2 and
14 • If access network requires closing the connection, it shall transmit a ConnectionClose
15 message, and transition to the Close State.
16 8.7.6.1.2.2.27.7.6.1.2.2.2 Cleanup Procedures

17 When the access network performs cleanup procedures it shall:
18 • Issue RouteUpdate.Close command,
19 • Return a ConnectionClosed indication.
20 8.7.6.1.37.7.6.1.3 Close State

21 The Close State is associated only with the access network. In this state the access network
22 waits for a replying ConnectionClose message from the access terminal or for the expiration
23 of the “CSP Close Timer” defined below.
24 Upon entering this state, the access network shall set a “CSP Close Timer” for TCSPClose
25 seconds. If the access network receives a ConnectionClose message in this state, or if the
26 timer expires, it shall execute the cleanup procedures defined in 7.7.6.1.2.2.2, it may close
27 all connection-related resources assigned to the access terminal, and it should transition to
28 the Inactive State.
30 8.7.6.2.17.7.6.2.1 ConnectionClose
31 The access terminal and the access network send the ConnectionClose message to close
32 the connection.
33
7-108
Field Length (bits)

MessageID 8
CloseReason 3
SuspendEnable 1
SuspendTime 0 or 36
Reserved variable
2 CloseReason The sender shall set this field to reflect the close reason, as shown in
3 Table 7.7.6.2-1.
4 Table 7.7.6.2-1. Encoding of the CloseReason Field

‘000’ Normal Close; Reason
Unspecified
‘001’ Close Reply
‘010’ Connection Error
‘011’ Normal Close; Connection
closed because of transition
from the high rate packet data
system to a cdma2000 1x
system (see [2])
‘100’ Normal Close with request for
non-zero suspend time
‘101’ Normal Close with request for
zero suspend time
5 SuspendEnable The access terminal shall set this field to ‘1’ if it will enable a
6 suspend period following the close of the connection. The access
8 SuspendTime Suspend period end time. This field is included only if the
9 SuspendEnable field is set to ‘1’. The access terminal shall set this
10 field to the absolute CDMA System Time of the end of its suspend
11 period in units of 80 ms.
12 Reserved The length of this field shall be such that the entire message is octet-
13 aligned. The sender shall set this field to zero. The receiver shall
15
7-109
2 8.7.6.3.17.7.6.3.1 Commands Sent

3 This protocol sends the following commands:
4 • RouteUpdate.Close
7 8.7.6.3.27.7.6.3.2 Indications


NCSPType Type field for this protocol Table
2.5.4-1
NCSPDefault Subtype field for this protocol 0x0000
TCSPClose Access network timer waiting for a responding 1.5
ConnectionClose message seconds

7-110
1 8.87.8 Default Route Update Protocol
2 8.8.17.8.1 Overview
3 The Default Route Update Protocol provides the procedures and messages used by the
4 access terminal and the access network to keep track of the access terminal’s approximate
5 location and to maintain the radio link as the access terminal moves between the coverage
6 areas of different sectors.
9 • Idle State: This state corresponds to the Air-Link Management Protocol Idle State. In
10 this state, the access terminal autonomously maintains the Active Set. Route update
11 messages from the access terminal to the access network are based on the distance
12 between the access terminal’s current serving sector and the serving sector at the time
13 the access terminal last sent an update.
14 • Connected State: In this state the access network dictates the access terminal’s Active
15 Set. Route update messages from the access terminal to the access network are based
16 on changing radio link conditions.
17 Transitions between states are driven by commands received from Connection Layer
18 protocols and the transmission and reception of the TrafficChannelAssignment message.
19 The protocol states, messages and commands causing the transition between the states are
20 shown in Figure 7.8.1-1.
Tx / Rx
Initial State TrafficChannelAssignment
Rx Activate
Inactive Connected
Idle State
State State
Rx Deactivate Rx Close
21
Rx Deactivate
22 Figure 7.8.1-1. Default Route Update Protocol State Diagram
23 This protocol uses parameters that are provided, as public data by the Overhead Messages
24 Protocol, configured attributes, or protocol constants.
25 Table 7.8.1-1 lists all of the protocol parameters obtained from the public data of the
7-111
2 Overhead Messages Protocol
RU Parameter Comment
Latitude Latitude of sector in units of 0.25 second
Longitude Longitude of sector in units of 0.25 second
Distance (unless modified by the
RouteUpdateRadiusMultiply and/or
RouteUpdateRadiusOverh RouteUpdateRadiusAdd attributes) between the serving
ead sector and the sector in which location was last reported
which triggers a new report. If this field is set to zero, then
distance triggered reporting is disabled
NumNeighbors Number of neighbors specified in the message
NeighborPN PN Offset of each neighbor in units of 64 PN chips
NeighborChannelIncluded Set to ‘1’ if a Channel Record is included for the neighbor
Neighbor Channel Record specifying network type and
NeighborChannel
frequency
4 8.8.2.17.8.2.1 Commands
6 • Activate
7 • Deactivate
8 • Open
9 • Close
10 • SendRouteUpdate

13 • ConnectionLost (access network only)
14 • NetworkLost
15 • IdleHO
16 • ActiveSetUpdated
17 • AssignmentRejected
18 • ConnectionInitiated
7-112
1 8.8.2.37.8.2.3 Public Data

4 • Active Set
5 • Pilot PN for every pilot in the Active Set
6 • Information provided by the SofterHandoff field in the TrafficChannelAssignment
7 message for every pilot in the Active Set
8 • MACIndex for every pilot in the Active Set
9 • Channel record specified in the TrafficChannelAssignment message
10 • FrameOffset specified in the TrafficChannelAssignment message
11 • Current RouteUpdate message
12 • Information listed in SupportedCDMAChannels attribute
13 • Pilot strength of all pilots in the Active Set
14 • DeltaT2P for all pilots in the Active Set



32 Upon creation, the InUse instance of this protocol in the access terminal and the access
7-113
5 8.8.5.17.8.5.1 Procedures
7 the configuration messages. The access terminal should send a ConfigurationRequest
8 message containing the SupportedCDMAChannels attribute. If the access terminal sends a
9 ConfigurationRequest message containing the SupportedCDMAChannels attribute, then
10 the access terminal shall include in the attribute all Band Classes and Band Sub-classes
11 supported by the access terminal.

18 • The value of the following public data of the InUse instance of the protocol shall be set
19 to the corresponding attribute value of the InConfiguration protocol instance:
20 − SupportedCDMAChannels
21 • If the InUse instance of the Route Update Protocol has the same subtype as this
22 protocol instance, but the InUse instance of any other protocol in the Connection Layer
23 does not have the same subtype as the corresponding InConfiguration protocol
24 instance, then
28 − The access terminal shall set the initial state of the InConfiguration and InUse
29 protocol instances of the Route Update protocol to the Inactive State.
30 − The access network shall set the initial state of the InConfiguration and InUse
31 protocol instances of the Route Update protocol to the Idle State.
34 • If the InUse instance of all protocols in the Connection Layer have the same subtype as
35 the corresponding InConfiguration protocol instance, then
7-114
1 − The InUse protocol instance at the access terminal shall perform the
2 procedures specified in 7.8.6.1.2.1.
5 • If the InUse instance of the Route Update Protocol does not have the same subtype as
6 this protocol instance, then the access terminal and the access network shall perform
7 the following:
13 instance for the Route Update Protocol at the access terminal and the access
14 network.
20
Field Length (bits)
MessageID 8
TransactionID 8
25
7-115
3
Field Length (bits)
MessageID 8
TransactionID 8

12
14 8.8.6.17.8.6.1 Procedures
16 8.8.6.1.1.17.8.6.1.1.1 Activate
17 If the protocol receives an Activate command in the Inactive State, the access terminal and
18 the access network shall perform the following:
19 • Issue an AccessChannelMAC.Activate command,
21 If this command is received in any other state, it shall be ignored.
22 8.8.6.1.1.27.8.6.1.1.2 Deactivate
23 If the protocol receives a Deactivate command in the Inactive State, it shall be ignored.
7-116
1 If the protocol receives this command in any other state, the access terminal and the
2 access network shall:
3 • Issue a ReverseTrafficChannelMAC.Deactivate command,
4 • Issue a ForwardTrafficChannelMAC.Deactivate command,
5 • Issue an AccessChannelMAC.Deactivate command,
7 8.8.6.1.1.37.8.6.1.1.3 Open
8 If the protocol receives an Open command in the Idle State,
9 • The access terminal shall ignore it.
10 • The access network shall:
11 − Transmit a TrafficChannelAssignment message as follows:
12 + The access network should base the TrafficChannelAssignment message on the
13 last RouteUpdate message it received from the access terminal.
14 + If the SupportedCDMAChannels attribute contains one or more band classes,
15 then the access network shall assign a Traffic Channel on a CDMA Channel
16 supported by the access terminal as indicated by the value of the
17 SupportedCDMAChannels attribute.
18 − Return a ConnectionInitiated indication,
19 − Issue a ReverseTrafficChannelMAC.Activate command,
20 − Issue a ForwardTrafficChannelMAC.Activate command,
21 − Issue an AccessChannelMAC.Deactivate command,
22 − Transition to the Connected State.
24 8.8.6.1.1.47.8.6.1.1.4 Close
25 If the protocol receives a Close command in the Connected State the access terminal and
26 the access network shall:
7-117
1 8.8.6.1.27.8.6.1.2 Pilots and Pilot Sets

2 The access terminal estimates the strength of the Forward Channel transmitted by each
3 sector in its neighborhood. This estimate is based on measuring the strength of the
4 Forward Pilot Channel (specified by the pilot’s PN offset and the pilot’s CDMA Channel),
5 henceforth referred to as the pilot.
6 When this protocol is in the Connected State, the access terminal uses pilot strengths to
7 decide when to generate RouteUpdate messages.
8 When this protocol is in the Idle State, the access terminal uses pilot strengths to decide
9 which sector’s Control Channel it monitors.
10 The following pilot sets are defined to support the Route Update process:59
11 • Active Set: The set of pilots (specified by the pilot’s PN offset and the pilot’s CDMA
12 Channel) associated with the sectors currently serving the access terminal. When a
13 connection is open, a sector is considered to be serving an access terminal when there
14 is a Forward Traffic Channel, Reverse Traffic Channel and Reverse Power Control
15 Channel assigned to the access terminal. When a connection is not open, a sector is
16 considered to be serving the access terminal when the access terminal is monitoring
17 that sector’s control channel.
18 • Candidate Set: The pilots (specified by the pilot’s PN offset and the pilot’s CDMA
19 Channel) that are not in the Active Set, but are received by the access terminal with
20 sufficient strength to indicate that the sectors transmitting them are good candidates
21 for inclusion in the Active Set.
22 • Neighbor Set: The set of pilots (specified by the pilot’s PN offset and the pilot’s CDMA
23 Channel) that are not in either one of the two previous sets, but are likely candidates
24 for inclusion in the Active Set.
25 • Remaining Set: The set of all possible pilots (specified by the pilot’s PN offset and the
26 pilot’s CDMA Channel) on the current channel assignment, excluding the pilots that are
27 in any of the three previous sets.
28 At any given instant a pilot in the current CDMA Channel is a member of exactly one set.
29 The access terminal maintains all four sets. The access network maintains only the Active
30 Set.
31 The access terminal complies with the following rules when searching for pilots, estimating
32 the strength of a given pilot, and moving pilots between sets.
33 8.8.6.1.2.17.8.6.1.2.1 Neighbor Set Search Window Parameters Update

34 The access terminal shall maintain RouteUpdateNeighborList which is a list of structures of
35 type Neighbor (defined below). For each pilot (specified by the pilot’s PN offset and the
36 pilot’s CDMA Channel) in the Neighbor Set, the access terminal shall maintain a structure
37 in the RouteUpdateNeighborList.
59 In this context, a pilot identifies a sector.
7-118
1 A Neighbor structure consists of four fields: PilotPN, Channel, SearchWindowSize, and

2 SearchWindowOffset.
3 The RouteUpdateNeighborList is used by the access terminal to perform pilot search on a
4 pilot in the Neighbor Set.
5 When this set of procedures is invoked, the access terminal shall perform the following
6 steps in the order specified:
7 • For each pilot (specified by its pilot PN and its channel) in the Neighbor Set, the access
8 terminal shall first initialize the corresponding Neighbor structure in
9 RouteUpdateNeighborList as follows:
10 − Set the structure’s PilotPN field to the neighbor pilot’s PN.
11 − Set the structure’s Channel field to the neighbor pilot’s channel record.
12 − Set the structure’s SearchWindowSize field to the configurable attribute
13 SearchWindowNeighbor.
14 − Set the structure’s SearchWindowOffset to zero.
15 • For each pilot (specified by the pilot’s PN offset and the pilot’s CDMA Channel) listed in
16 the OverheadMessagesNeighborList, the access terminal shall set the non-NULL fields
17 of the corresponding Neighbor structure in the RouteUpdateNeighborList to the fields of
18 the Neighbor structure in the OverheadMessagesNeighborList for this pilot.
19 • For each pilot (specified by the pilot’s PN offset and the pilot’s CDMA Channel) listed in
20 the NeighborListMessageNeighborList, the access terminal shall set the non-NULL fields
21 of the corresponding Neighbor structure in the RouteUpdateNeighborList to the fields of
22 the Neighbor structure in the NeighborListMessageNeighborList for this pilot.
23 8.8.6.1.2.27.8.6.1.2.2 Pilot Search

24 The access terminal shall continually search for pilots in the Connected State and
25 whenever it is monitoring the Control Channel in the Idle State. The access terminal shall
26 search for pilots in all pilot sets. This search shall be governed by the following rules:
27 Search Priority: The access terminal should use the same search priority for pilots in
28 the Active Set and Candidate Set. In descending order of search rate, the access
29 terminal shall search, most often, the pilots in the Active Set and Candidate Set,
30 then shall search the pilots in the Neighbor Set, and lastly shall search the pilots in
31 the Remaining Set.
32 Search Window Size: The access terminal shall use the search window size specified by
33 the configurable attribute SearchWindowActive for pilots in the Active Set and
34 Candidate Set. For each pilot in the Neighbor Set, the access terminal shall use the
35 search window size specified by Table 7.8.6.2-4 and SearchWindowSize field of the
36 corresponding Neighbor structure in the RouteUpdateNeighborList. The access
37 terminal shall use search window size specified by configurable attribute
38 SearchWindowRemaining for pilots in the Remaining Set.
7-119
1 Search Window Center: The access terminal should center the search window around
2 the earliest usable multipath component for pilots in the Active Set. The access
3 terminal should center the search window for each pilot in the Neighbor Set around
4 the pilot’s PN sequence offset plus the search window offset specified by Table
5 7.8.6.2-5 and SearchWindowOffset field of the corresponding Neighbor structure in
6 the RouteUpdateNeighborList using timing defined by the access terminal’s time
7 reference (see 10.4.1.3.6). The access terminal should center the search window
8 around the pilot’s PN sequence offset using timing defined by the access terminal’s
9 time reference (see 10.4.1.3.6) for the Remaining Set.
10 8.8.6.1.2.37.8.6.1.2.3 Pilot Strength Measurement

11 The access terminal shall measure the strength of every pilot it searches. The strength
12 estimate formed by the access terminal shall be computed as the sum of the ratios of
13 received pilot energy per chip, Ec, to total received spectral density, I0 (signal and noise) for
14 at most k multipath components, where k is the maximum number of multipath
15 components that can be demodulated simultaneously by the access terminal.
16 8.8.6.1.2.47.8.6.1.2.4 Pilot Drop Timer Maintenance

17 For each pilot, the access terminal shall maintain a pilot drop timer.
18 If DynamicThresholds is equal to ‘0’, the access terminal shall perform the following:
19 • The access terminal shall start a pilot drop timer for each pilot in the Candidate Set or
20 the Active Set whenever the strength becomes less than the value specified by
21 PilotDrop. The access terminal shall consider the timer to be expired after the time
22 specified by PilotDropTimer.
23 • The access terminal shall reset and disable the timer whenever the strength of the pilot
24 becomes greater than the value specified by PilotDrop.
26 • The access terminal shall start a pilot drop timer for each pilot in the Candidate Set
27 whenever the strength of the pilot becomes less than the value specified by PilotDrop.
28 The access terminal shall consider the timer value to be expired after the time specified
29 by PilotDropTimer. The access terminal shall reset and disable the timer if the strength
30 of the pilot becomes greater than the value specified by PilotDrop.
31 • For each pilot in the Active Set, the access terminal shall sort pilots in the Active Set in
32 order of increasing strengths, i.e., PS1 < PS 2 < PS 3 < ... < PS N , where NA is the number
A
33 of the pilots in the Active Set. The access terminal shall start the Pilot drop timer for
34 each pilot PSi in the Active Set whenever the strength PSi satisfies the following
35 inequality:
⎛ SoftSlope DropIntercept PilotDrop ⎞
36 10 × log10PSi < max⎜⎜ ×10 × log10 ∑ PS j + ,- ⎟
⎟
⎝ 8 j> i 2 2 ⎠
i = 1, 2, ..., NA − 1
7-120
1 The access terminal shall reset and disable the timer whenever the above inequality
2 is not satisfied for the corresponding pilot.
3 Sections 7.8.6.1.2.6 and 7.8.6.1.6.5 specify the actions the access terminal takes when the
4 pilot drop timer expires.
5 8.8.6.1.2.57.8.6.1.2.5 Active Set Management

6 The access terminal shall support a maximum Active Set size of NRUPActive pilots.
7 Rules for maintaining the Active Set are specific to each protocol state (see 7.8.6.1.5.1 and
8 7.8.6.1.6.1).
9 8.8.6.1.2.67.8.6.1.2.6 Candidate Set Management

10 The access terminal shall support a maximum Candidate Set size of NRUPCandidate pilots.
11 The access terminal shall add a pilot to the Candidate Set if one of the following conditions
12 is met:
13 • Pilot is not already in the Active Set or Candidate Set and the strength of the pilot
14 exceeds the value specified by PilotAdd.
15 • Pilot is deleted from the Active Set, its pilot drop timer has expired, DynamicThresholds
16 is equal to ‘1’, and the pilot strength is above the threshold specified by PilotDrop.
17 • Pilot is deleted from the Active Set but its pilot drop timer has not expired.
18 The access terminal shall delete a pilot from the Candidate Set if one of the following
19 conditions is met:
20 • Pilot is added to the Active Set.
21 • Pilot’s drop timer has expired.
22 • Pilot is added to the Candidate Set; and, as a consequence, the size of the Candidate
23 Set exceeds NRUPCandidate. In this case, the access terminal shall delete the weakest pilot
24 in the set. Pilot A is considered weaker than pilot B:
25 − If pilot A has an active drop timer but pilot B does not,
26 − If both pilots have an active drop timer and pilot A’s drop timer is closer to
27 expiration than pilot B’s, or
28 − If neither of the pilots has an active drop timer and pilot A’s strength is less
29 than pilot B’s.
30 8.8.6.1.2.77.8.6.1.2.7 Neighbor Set Management

31 The access terminal shall support a minimum Neighbor Set size of NRUPNeighbor pilots.
32 • The access terminal shall maintain a counter, AGE, for each pilot in the Neighbor Set
33 as follows.
34 The access terminal shall perform the following in the order specified:
7-121
1 • If a pilot is added to the Active Set or Candidate Set, it shall be deleted from the
2 Neighbor Set.
3 • If a pilot is deleted from the Active Set, but not added to the Candidate Set, then it shall
4 be added to the Neighbor Set with the AGE of 0.
5 • If a pilot is deleted from the Candidate Set, but not added to the Active Set, then it shall
6 be added to the Neighbor Set with the AGE of 0.
7 • If the size of the Neighbor Set is greater than the maximum Neighbor Set supported by
8 the access terminal, the access terminal shall delete enough pilots from the Neighbor
9 Set such that the size of the Neighbor Set is the maximum size supported by the access
10 terminal and pilots with higher AGE are deleted first60.
11 • If the access terminal receives an OverheadMessages.Updated indication, then:
12 − The access terminal shall increment the AGE for every pilot in the Neighbor
13 Set.
14 − For each pilot in the neighbor list given as public data by the Overhead
15 Messages Protocol that is a member of the Neighbor Set, the access terminal
17 + The access terminal shall set the AGE of this neighbor list pilot to the minimum
18 of its current AGE and NeighborMaxAge.
20 Messages Protocol (in the order specified in the neighbor list) that is a member
21 of the Remaining Set, the access terminal shall perform the following:
22 + If the addition of this neighbor list pilot to the Neighbor Set would not cause
23 the size of the Neighbor Set size to increase beyond the maximum Neighbor
24 Set size supported by the access terminal, then the access terminal shall add
25 this neighbor list pilot to the Neighbor Set with its AGE set to
26 NeighborMaxAge.
27 + If the addition of this neighbor list pilot would cause the size of the Neighbor
28 Set to increase beyond the maximum Neighbor Set size supported by the
29 access terminal and the Neighbor Set contains at least one pilot with AGE
30 greater than NeighborMaxAge associated with the pilot’s channel, then the
31 access terminal shall delete the pilot in the Neighbor Set for which the
32 difference between its AGE and the NeighborMaxAge associated with that
33 pilot's channel (i.e., AGE - NeighborMaxAge) is the greatest and shall add this
34 neighbor list pilot to the Neighbor Set with its AGE set to NeighborMaxAge
35 associated with the pilot’s channel.
60 The order in which pilots of the same AGE are deleted does not matter in this case.
7-122
3 access terminal and the Neighbor Set does not contain a pilot with AGE
4 greater than NeighborMaxAge associated with the pilot’s channel, the access
5 terminal shall not add this neighbor list pilot to the Neighbor Set.
6 • If the access terminal receives a NeighborList message, then:
8 Set.
9 − For each pilot in the neighbor list given in the NeighborList message that is a
10 member of the Neighbor Set, the access terminal shall perform the following:
13 − For each pilot in the neighbor list given in the NeighborList message (in the
14 order specified in the message) that is a member of the Remaining Set, the
17 the size of the Neighbor Set size to increase beyond the maximum Neighbor
18 Set size supported by the access terminal, then the access terminal shall add
19 this neighbor list pilot to the Neighbor Set with its AGE set to
20 NeighborMaxAge.
35 The access terminal shall perform the procedures specified in 7.8.6.1.2.1 if a pilot
36 (specified by the pilot’s PN offset and the pilot’s CDMA Channel) is added to or deleted from
37 the Neighbor Set.
38 8.8.6.1.2.87.8.6.1.2.8 Remaining Set Management

39 The access terminal shall initialize the Remaining Set to contain all the pilots whose PN
40 offset index is an integer multiple of PilotIncrement and are not already members of any
41 other set.
7-123
1 The access terminal shall add a pilot to the Remaining Set if it deletes the pilot from the
2 Neighbor Set and if the pilot was not added to the Active Set or Candidate Set.
3 The access terminal shall delete the pilot from the Remaining Set if it adds it to another set.
4 8.8.6.1.2.97.8.6.1.2.9 Pilot PN Phase Measurement

5 The access terminal shall measure the arrival time, PILOT_ARRIVAL, for each pilot reported
6 to the access network. The pilot arrival time shall be the time of occurrence, as measured
7 at the access terminal antenna connector, of the earliest arriving usable multipath
8 component of the pilot. The arrival time shall be measured relative to the access terminal’s
9 time reference in units of PN chips. The access terminal shall compute the reported pilot
10 PN phase, PILOT_PN_PHASE, as:
11 PILOT_PN_PHASE = (PILOT_ARRIVAL + (64 × PILOT_PN)) mod 215,
12 where PILOT_PN is the PN sequence offset index of the pilot.
13 8.8.6.1.37.8.6.1.3 Message Sequence Numbers

14 The access network shall validate all received RouteUpdate messages as specified in
15 7.8.6.1.3.1.
16 The access terminal shall validate all received TrafficChannelAssignment messages as
17 specified in 7.8.6.1.3.2.
18 The RouteUpdate message and the TrafficChannelAssignment message carry a
19 MessageSequence field that serves to flag duplicate or stale messages.
20 The MessageSequence field of the RouteUpdate message is independent of the
21 MessageSequence field of the TrafficChannelAssignment message.
22 8.8.6.1.3.17.8.6.1.3.1 RouteUpdate Message Validation

23 When the access terminal first sends a RouteUpdate message, it shall set the
24 MessageSequence field of the message to zero. Subsequently, the access terminal shall
25 increment this field each time it sends a RouteUpdate message.
26 The access network shall consider all RouteUpdate messages it receives in the Idle State as
27 valid.
28 The access network shall initialize the receive pointer, V(R) to the MessageSequence field of
29 the first RouteUpdate message it received in the Idle State, and the access network shall
30 subsequently set it to the MessageSequence field of each received RouteUpdate message.
31 When the access network receives a RouteUpdate message in the Connected State, it shall
32 validate the message using the procedure defined in 13.6. The access network shall discard
33 the message if it is invalid.
34 8.8.6.1.3.27.8.6.1.3.2 TrafficChannelAssignment Message Validation

35 The access network shall set the MessageSequence field of the TrafficChannelAssignment
36 message it sends in the Idle State to zero. Subsequently, each time the access network
37 sends a new TrafficChannelAssignment message in the Connected State, it shall increment
7-124
1 this field. If the access network is sending the same message multiple times, it shall not
2 change the value of this field between transmissions.61
3 The access terminal shall initialize the receive pointer, V(R), to the MessageSequence field
4 of the TrafficChannelAssignment message that it receives in the Idle State.
5 When the access terminal receives a TrafficChannelAssignment message in the Connected
6 State, it shall validate the message using the procedure defined in 13.6. The access
7 terminal shall discard the message if it is invalid.
8 8.8.6.1.3.37.8.6.1.3.3 AttributeOverride Message Validation

9 The access network shall set the MessageSequence field of the first AttributeOverride
10 message that it sends after the Route Update protocol enters the Connected State to zero.
11 Subsequently, each time the access network sends a new AttributeOverride message in the
12 Connected State, it shall increment this field. If the access network is sending the same
13 message multiple times, it shall not change the value of this field between transmissions.62
15 of the first AttributeOverride message that it receives in the Connected State.
16 When the access terminal receives a subsequent AttributeOverride message, it shall
17 validate the message using the procedure defined in 13.6. The access terminal shall
18 discard the message if it is invalid.
19 8.8.6.1.47.8.6.1.4 Inactive State

20 Upon entering this state, the access terminal shall perform the following:
21 • The access terminal shall set the Active Set, the Candidate Set, and the Neighbor Set to
22 NULL.
23 • The access terminal shall initialize the Remaining Set to contain all the pilots whose PN
25 other set.
26 • The access terminal shall perform the following in the order specified:
27 − Remove all Neighbor structures from OverheadMessagesNeighborList.
28 − Remove all Neighbor structures from NeighborListMessageNeighborList.
29 − Perform the procedures specified in 7.8.6.1.2.1.
30 • The access terminal shall set (xL,yL), the longitude and latitude of the sector in whose
31 coverage area the access terminal last sent a RouteUpdate message, to (NULL, NULL).
61 The access network may send a message multiple times to increase its delivery probability.
7-125
1 8.8.6.1.57.8.6.1.5 Idle State

2 In this state, RouteUpdate messages from the access terminal are based on the distance
3 between the sector where the access terminal last sent a RouteUpdate message and the
4 sector currently in its active set.
5 The access network sends the TrafficChannelAssignment message to open a connection in
6 this state.
8 • Remove all Neighbor structures from NeighborListMessageNeighborList and perform the
10 • Stop using the parameters specified in the AttributeOverride message in the set
11 management procedures and start using values specified by the
12 SetManagementSameChannelParameters and the
13 SetManagementDifferentChannelParameters attributes whichever applicable, in the set
14 management procedures.
15 8.8.6.1.5.17.8.6.1.5.1 Active Set Maintenance

16 The access network shall not initially maintain an Active Set for the access terminal in this
17 state.
18 If the access network receives an Open command, prior to send a
19 TrafficChannelAssignment message, the access network shall initialize the Active Set to the
20 set of pilots in the TrafficChannelAssignment message that it sends in response to
21 command (see 7.8.6.1.1.3).
22 The access terminal shall initially keep an Active Set of size one when it is in the Idle State.
23 The Active Set pilot shall be the pilot associated with the Control Channel the access
24 terminal is currently monitoring. The access terminal shall return an IdleHO indication
25 when the Active Set changes in the Idle State.
26 The access terminal shall not change its Active Set pilot at a time that causes it to miss a
27 synchronous Control Channel capsule. Other rules governing when to replace this Active
28 Set pilot are beyond the scope of this specification.
29 If the access terminal receives a TrafficChannelAssignment message, it shall set its Active
30 Set to the list of pilots specified in the message if the TrafficChannelAssignment message
31 does not contain a Channel Record, or if the TrafficChannelAssignment message contains a
32 Channel Record and the access terminal supports the CDMA Channel specified by the
33 Channel Record.
34 8.8.6.1.5.27.8.6.1.5.2 Pilot Channel Supervision in the Idle State

35 The access terminal shall perform pilot channel supervision in the Idle State as follows:
36 • Access terminal shall monitor the pilot strength of the pilot in its active set, all the
37 pilots in the candidate set and all the pilots in the neighbor set that are on the same
38 frequency.
7-126
1 • If the strength of all the pilots that the access terminal is monitoring goes below the
2 value specified by PilotDrop, the access terminal shall start a pilot supervision timer.
3 The access terminal shall consider the timer to be expired after the time specified by
4 PilotDropTimer.
5 • If the strength of at least one of the pilots goes above the value specified by PilotDrop
6 while the pilot supervision timer is counting down, the access terminal shall reset and
7 disable the timer.
8 • If the pilot supervision timer expires, the access terminal shall return a NetworkLost
9 indication.
10 8.8.6.1.5.37.8.6.1.5.3 Processing the TrafficChannelAssignment Message in the Idle State

11 If the access terminal receives a TrafficChannelAssignment message in this state, it shall
12 perform the following if the TrafficChannelAssignment message does not contain a Channel
13 Record, or if the TrafficChannelAssignment message contains a Channel Record and the
14 access terminal supports the CDMA Channel specified by the Channel Record:
15 • Update its Active Set as described in 7.8.6.1.5.1
16 • Set the following public data of the Forward Traffic Channel MAC Protocol to the
17 corresponding fields of the TrafficChannelAssignment message:
18 − DRCLength
19 − ACKChannelGain
20 − DRCCover for every pilot in the Active Set
21 − DSC for every cell in the Active Set
22 • If the Forward Traffic Channel MAC protocol defines the DRCChannelGainBase as a
23 public data, then set that public data to the DRCChannelGainBase field of the
24 TrafficChannelAssignment message. Otherwise, set the DRCChannelGain public data
25 of the Forward Traffic Channel MAC protocol to the DRCChannelGainBase field of the
26 TrafficChannelAssignment message.
27 • If the Forward Traffic Channel MAC protocol defines the DSCChannelGainBase as a
28 public data, then set that public data to the DSCChannelGainBase field of the
30 • Set the following public data of the Reverse Traffic Channel MAC Protocol to the
32 − RAChannelGain for every pilot in the Active Set
33 − RABLength for every pilot in the Active Set
34 − RABOffset for every pilot in the Active Set
7-127
1 • If MACIndexMSB fields are included in the TrafficChannelAssignment message, then

2 the access terminal shall determine the 7-bit MACIndex for each pilot in the Active Set
3 by prepending the corresponding MACIndexMSB field of the TrafficChannelAssignment
4 message to the corresponding MACIndexLSBs field of the TrafficChannelAssignment
5 message. Otherwise the access terminal shall set the MACIndex to the corresponding
6 MACIndexLSBs field.
7 • Return a ConnectionInitiated Indication.
8 • If the Channel Record is included in the message, then the access terminal shall tune
9 to the CDMA Channel specified by the Channel Record.
10 • Issue the following commands:
11 − ReverseTrafficChannelMAC.Activate
12 − ForwardTrafficChannelMAC.Activate
13 − AccessChannelMAC.Deactivate
14 • Transition to the Connected State.
15 8.8.6.1.5.47.8.6.1.5.4 Route Update Report Rules

16 The access terminal shall send RouteUpdate messages to update its location with the
17 access network.
18 The access terminal shall not send a RouteUpdate message if the state timer of the
19 Connection Setup State in the Idle State Protocol is active.
20 The access terminal shall comply with the following rules regarding RouteUpdate
21 messages:
22 • The Default Route Update Protocol shall send a RouteUpdate message upon receiving a
23 SendRouteUpdate command.
24 • If the value of the SupportRouteUpdateEnhancements attribute is not 0x00, then the
25 access terminal shall send a RouteUpdate message whenever it receives a
26 RouteUpdateRequest message.
27 • The access terminal shall send a RouteUpdate message with every access channel
28 capsule transmitted by the access terminal.
29 • The access terminal shall include in the RouteUpdate message the pilot PN phase, pilot
30 strength, and drop timer status for every pilot in the Active Set and Candidate Set.
31 • The access terminal shall send a RouteUpdate message if all of the following conditions
32 are true:
33 − the RouteUpdateRadiusOverhead field of the SectorParameters message is not
34 set to zero, and
35 − the value of the RouteUpdateRadiusMultiply attribute is not 0x00, and
7-128
1 − the computed value r is greater than max ( 0, rm × ro + ra ), where ro is the

2 value provided in the RouteUpdateRadiusOverhead field of the
3 SectorParameters message transmitted by the sector in which the access
4 terminal last sent a RouteUpdate message, rm is the value of the
5 RouteUpdateRadiusMultiply attribute, and ra is the value of the
6 RouteUpdateRadiusAdd attribute.
7 If (xL,yL) are the longitude and latitude of the sector to which the access terminal last sent a
8 RouteUpdate, and (xC,yC) are the longitude and latitude of the sector currently providing
9 coverage to the access terminal, then r is given by63
⎢ ⎡ 2 ⎥
⎢ ⎢( xC − xL ) × cos⎛⎜ π × y L ⎞⎟⎤⎥ + [ yC − y L ]2 ⎥
⎢ ⎣ ⎝ 180 14400 ⎠⎦ ⎥ 64
10 r=⎢ ⎥
⎢ 16 ⎥
⎢ ⎥
⎣ ⎦
11 The access terminal shall compute r with an error of no more than ±5% of its true value
12 when |yL/14400| is less than 60 and with an error of no more than ±7% of its true value
13 when |yL/14400| is between 60 and 70.65
14 If the value of the SupportRouteUpdateEnhancements attribute is 0x00, then the access
15 network shall not send a RouteUpdateRequest message. If the value of the
16 SupportRouteUpdateEnhancements attribute is not 0x00, then the access network may
17 send a RouteUpdateRequest message.
63 The x’s denote longitude and the y’s denote latitude.
64 This equation applies if the access terminal does not cross longitude = 180. Modified equation that
is applicable in all cases is:
⎢ ⎡ ⎤
2 ⎥
⎛ π y ⎞
⎢ ⎢D longitude × cos⎜ ⎟⎥ + [y C − y L ] ⎥
2
× L
⎢ ⎣ ⎝ 180 14400 ⎠⎦ ⎥
r=⎢ ⎥
⎢ 16 ⎥
⎢ ⎥
⎣ ⎦
x − xL
D longitude = x C − x L if C < 180
14400
xC − xL
D longitude = 360 ×14400 − x C − x L if ≥ 180
14400
65xL and yL are given in units of 1/4 seconds. xL/14400 and yL/14400 are in units of degrees.
7-129
1 8.8.6.1.67.8.6.1.6 Connected State

2 In this state, RouteUpdate messages from the access terminal are based on changes in the
3 radio link between the access terminal and the access network, obtained through pilot
4 strength measurements at the access terminal.
5 The access network determines the contents of the Active Set through
6 TrafficChannelAssignment messages.

8 In the Connected State, the access terminal shall perform the following:
9 • If the protocol receives a ReverseTrafficChannelMAC.LinkAcquired indication the access
10 terminal shall:
11 − Send a TrafficChannelComplete message with the MessageSequence field of
12 the message set to the MessageSequence field of the TrafficChannelAssignment
13 message,
14 − Return a ConnectionOpened indication.

16 In the Connected State, the access network shall perform the following:
18 network shall return a ConnectionOpened indication.
20 8.8.6.1.6.3.17.8.6.1.6.3.1 Access Network

21 Whenever the access network sends a TrafficChannelAssignment message to the access
22 terminal, it shall add to the Active Set any pilots listed in the message that are not
23 currently in the Active Set. Upon sending a TrafficChannelAssignment message, the access
24 network shall set the following public data of the Forward Traffic Channel MAC Protocol to
25 the corresponding fields of the TrafficChannelAssignment message:
26 • DRCLength
27 • ACKChannelGain
28 • DRCCover for every pilot in the Active Set
29 • DSC for every cell in the Active Set
7-130

4 Upon sending a TrafficChannelAssignment message, the access network shall set the
5 following public data of the Reverse Traffic Channel MAC Protocol to the corresponding
6 fields of the TrafficChannelAssignment message:
7 • RAChannelGain for every pilot in the Active Set
8 • RABLength for every pilot in the Active Set
9 • RABOffset for every pilot in the Active Set
10 The access network shall delete a pilot from the Active Set if the pilot was not listed in a
11 TrafficChannelAssignment message and if the access network received the
12 TrafficChannelComplete message, acknowledging that TrafficChannelAssignment message.
13 The access network should send a TrafficChannelAssignment message to the access
14 terminal in response to changing radio link conditions, as reported in the access terminal’s
15 RouteUpdate messages.
16 The access network should only specify a pilot in the TrafficChannelAssignment message if
17 it has allocated the required resources in the associated sector. This means that the sector
18 specified by the pilot is ready to receive data from the access terminal and is ready to
19 transmit queued data to the access terminal should the access terminal point its DRC at
20 that sector.
21 If the SupportedCDMAChannels attribute contains one or more band classes, then the
22 access network shall assign a Traffic Channel on a CDMA Channel supported by the access
23 terminal as indicated by the value of the SupportedCDMAChannels attribute.
24 If the access network adds or deletes a pilot in the Active Set, it shall send an
25 ActiveSetUpdated indication.
26 If the access network adds a pilot specified in a RouteUpdate message to the Active Set, the
27 access network may use the PilotPNPhase field provided in the message to obtain a round
28 trip delay estimate from the access terminal to the sector associated with this pilot. The
29 access network may use this estimate to accelerate the acquisition of the access terminal’s
30 Reverse Traffic Channel in that sector.
31 8.8.6.1.6.3.27.8.6.1.6.3.2 Access Terminal

32 If the access terminal receives a valid TrafficChannelAssignment message (see 7.8.6.1.3.2),
33 it shall replace the contents of its current Active Set with the pilots specified in the
34 message. The access terminal shall process the message as defined in 7.8.6.1.6.6.
35 8.8.6.1.6.47.8.6.1.6.4 ResetReport Message

36 The access network may send a ResetReport message to reset the conditions under which
37 RouteUpdate messages are sent from the access terminal. Access terminal usage of the
38 ResetReport message is specified in the following section.
7-131

2 The access terminal sends a RouteUpdate message to the access network in this state to
3 request addition or deletion of pilots from its Active Set. If the access terminal is sending
4 the RouteUpdate message in response to a RouteUpdateRequest message that contains a
5 Channel record, the access terminal shall include in a RouteUpdate message the pilot PN
6 phase, pilot strength, and drop status for pilots whose strength is above the value specified
7 by PilotAdd and subject to the following conditions:
8 • If the RouteUpdateRequest message contains one or more SectorPilotPN fields, the
9 access terminal shall include pilots in the CDMA channel indicated by the Channel
10 record and that are indicated by the SectorPilotPN fields. Otherwise, the access
11 terminal shall include pilots which are in the CDMA channel indicated by the Channel
12 record.
13 If the access terminal is not sending the RouteUpdate message in response to a
14 RouteUpdateRequest message that contains a Channel record, the access terminal shall
15 determine which pilots to include in the RouteUpdate message as follows:
16 • If DynamicThresholds is equal to ‘0’, the access terminal shall include in the
17 RouteUpdate message the pilot PN phase, pilot strength, and drop timer status for
18 every pilot in the Active Set and Candidate Set. If DynamicThresholds is equal to ‘1’,
19 then the access terminal shall include in the RouteUpdate message the pilot PN phase,
20 pilot strength, and drop timer status for every pilot in the Active Set, for each pilot in
21 the Candidate Set whose strength is above the values specified by PilotAdd, and for
22 each pilot in the Candidate Set whose strength, PS, satisfies the following inequality:
SoftSlope AddIntercept ,
23 10 × log10 PS > ×10 × log10 ∑ PS i +
8 i∈A 2
24 where the summation is performed over all pilots currently in the Active Set.
25 The access terminal shall send a RouteUpdate message if any one of the following occurs:
26 • The value of the SupportRouteUpdateEnhancements attribute is not 0x00 and the
27 access terminal receives a RouteUpdateRequest message.
28 • The Default Route Update Protocol receives a SendRouteUpdate command.
29 • If DynamicThresholds is equal to ‘0’ and the strength of a Neighbor Set or Remaining
30 Set pilot is greater than the value specified by PilotAdd.
32 Set pilot, PS, satisfies the following inequality:
⎛ SoftSlope AddInterce pt PilotAdd ⎞
33 10 × log10 PS > max ⎜ ×10 × log10 ∑ PSi + ,- ⎟
⎝ 8 i∈A 2 2 ⎠
34 where the summation is performed over all pilots currently in the Active Set.
35 • If DynamicThresholds is equal to ‘0’ and the strength of a Candidate Set pilot is greater
36 than the value specified by PilotCompare above an Active Set pilot, and a RouteUpdate
37 message carrying this information has not been sent since the last ResetReport
7-132
1 • If DynamicThresholds is equal to ‘0’ and the strength of a Candidate Set pilot is above
2 PilotAdd, and a RouteUpdate message carrying this information has not been sent since
3 the last ResetReport message was received.
4 • If DynamicThresholds is equal to ‘1’ and
5 − the strength of a Candidate Set pilot, PS, satisfies the following inequality:
SoftSlope AddIntercept
6 10 × log 10 PS > ×10 × log 10 ∑ PS i +
8 i∈A 2
7 where the summation is performed over all pilots currently in the Active Set,
8 and
9 − a RouteUpdate message carrying this information has not been sent since the
10 last ResetReport message was received.
12 − the strength of a Candidate Set pilot is greater than the value specified by
13 PilotCompare above an Active Set pilot, and
14 − the strength of a Candidate Set pilot, PS, satisfies the following inequality:
SoftSlope AddInterce pt
15 10 × log10PS > ×10 × log10 ∑ PSi +
8 i∈A 2
16 where the summation is performed over all pilots currently in the Active Set,
17 and
20 • The pilot drop timer of an Active Set pilot has expired, and a RouteUpdate message
21 carrying this information has not been sent since the last ResetReport message was
22 received.
27 8.8.6.1.6.67.8.6.1.6.6 Processing the TrafficChannelAssignment Message in the Connected

28 State
29 If valid TrafficChannelAssignment (see 7.8.6.1.3.2) message does not contain a Channel
30 Record, or if a valid TrafficChannelAssignment message contains a Channel Record and the
31 access terminal supports the CDMA Channel specified by the Channel Record, then the
32 access terminal shall process the message as follows:
33 • The access terminal shall set the following public data of the Forward Traffic Channel
34 MAC Protocol to the corresponding fields of the TrafficChannelAssignment message:
35 − DRCLength
36 − ACKChannelGain
7-133

11 • The access terminal shall set the following public data of the Reverse Traffic Channel
14 − RABLength for every pilot in the Active Set
15 − RABOffset for every pilot in the Active Set
16 • If the TrafficChannelAssignment message contains a value for the FrameOffset that is
17 different from the value of the FrameOffset received in the last
18 TrafficChannelAssignment message that was received in the Idle state, then the access
19 terminal shall return a RouteUpdate.AssignmentRejected indication and shall discard
20 the message.
21 • The access terminal shall update its Active Set as defined in 7.8.6.1.6.3.2.
22 • The access terminal shall tune to the CDMA Channel defined by the Channel Record, if
23 this record is included in the message.
24 • If MACIndexMSB fields are included in the TrafficChannelAssignment message, then
25 the access terminal shall determine the 7-bit MACIndex for each pilot in the Active Set
26 by prepending the corresponding MACIndexMSB field of the TrafficChannelAssignment
27 message to the corresponding MACIndexLSBs field of the TrafficChannelAssignment
28 message. Otherwise the access terminal shall set the MACIndex to the corresponding
29 MACIndexLSBs field.
30 • The access terminal shall start monitoring and responding to the Power Control
31 Channels defined by the MACIndex fields provided in the message. The access terminal
32 should use the SofterHandoff fields to identify the Power Control Channels that are
33 carrying identical information and can therefore be soft-combined.
34 • The access terminal shall send the access network a TrafficChannelComplete message
35 specifying the MessageSequence value received in the TrafficChannelAssignment
36 message.
37 8.8.6.1.6.77.8.6.1.6.7 Processing the TrafficChannelComplete Message

38 The access network should set a transaction timer when it sends a
39 TrafficChannelAssignment message. If the access network sets a transaction timer, it shall
7-134
1 reset the timer when it receives a TrafficChannelComplete message containing a

2 MessageSequence field equal to the one sent in the TrafficChannelAssignment message.
3 If the timer expires, the access network should return a ConnectionLost indication.
4 8.8.6.1.6.87.8.6.1.6.8 Transmission and Processing of the NeighborList Message

5 The access network may send the NeighborList message to the access terminal when the
6 protocol is in the Connected State to override the search window size and/or search
7 window offset corresponding to a pilot in the Neighbor Set.
8 Upon receiving a NeighborList message, the access terminal shall perform the following in
10 • The access terminal shall remove all Neighbor structures from
11 NeighborListMessageNeighborList.
12 • For each pilot (specified by its pilot PN and its channel) listed in the received
13 NeighborList message, the access terminal shall add a Neighbor structure to
14 NeighborListMessageNeighborList and populate it as follows:
15 − Set the structure’s PilotPN field to the message’s corresponding PilotPN field.
16 − If the message’s ChannelIncluded field is set to ‘1’, set the structure’s Channel
17 field to the message’s corresponding Channel field. Otherwise, set the
18 structure’s Channel field to the current channel.
19 − If the message’s SearchWindowSizeIncluded field is set to ‘1’, then set the
20 structure’s SearchWindowSize field to the message’s corresponding
21 SearchWindowSize field. Otherwise, set the structure’s SearchWindowSize field
22 to NULL.
23 − If the SearchWindowOffsetIncluded field is set to ‘1’, then set the structure’s
24 SearchWindowOffset field to the message’s corresponding SearchWindowOffset
25 field. Otherwise, set the structure’s SearchWindowOffset field to NULL.
26 • Perform the procedures specified in 7.8.6.1.2.1.
27 8.8.6.1.6.97.8.6.1.6.9 Transmission and Processing of the AttributeOverride Message

28 The access network may send the AttributeOverride message to the access terminal to
29 override the parameters specified in the SetManagementSameChannelParameters and
30 SetManagementDifferentChannelParameters configuration attributes.
31 If the value of the SetManagementOverrideAllowed attribute is 0x01, then upon receiving a
32 valid (see 7.8.6.1.3.3) AttributeOverride message, the access terminal shall start using the
33 values specified in the message.
34 The access terminal shall discard the values of the
35 SetManagementSameChannelParameters and SetManagementDifferentChannelParameters
36 in the AttributeOverride message if the SetManagementOverrideAllowed attribute is set to
37 0x00.
7-135
1 When the access terminal receives a valid (see 7.8.6.1.3.3) AttributeOverride message, it
2 shall send the access network an AttributeOverrideResponse message specifying the
3 MessageSequence value received in the AttributeOverride message.
4 8.8.6.1.6.107.8.6.1.6.10 Processing of OverheadMessages.Updated Indication

5 Upon receiving OverheadMessages.Updated indication, the access terminal shall perform
6 the OverheadMessagesNeighborList Initialization procedures as specified in 7.8.6.1.6.11
7 and then perform the procedures specified in 7.8.6.1.2.1.
8 8.8.6.1.6.117.8.6.1.6.11 OverheadMessagesNeighborList Initialization

9 When the OverheadMessagesNeighborList initialization procedures are invoked by the
10 access terminal, it shall perform the following:
11 • The access terminal shall remove all Neighbor structures from the
12 OverheadMessagesNeighborList list.
13 • For each pilot (specified by its pilot PN and its channel) in the neighbor list given as
14 public data of Overhead Messages Protocol, the access terminal shall add a Neighbor
15 structure to the OverheadMessagesNeighborList list and populate it as follows:
16 − Set the structure’s PilotPN field to the corresponding NeighborPilotPN field
17 given as public data of the Overhead Messages Protocol.
18 − If the Overhead Messages Protocol’s NeighborChannelIncluded field is set to
19 ‘1’, set the structure’s Channel field to the Overhead Messages Protocol’s
20 corresponding NeighborChannel. Otherwise, set the structure’s Channel field
21 to the current channel.
22 − If the Overhead Messages Protocol’s SearchWindowSizeIncluded field is set to
23 ‘1’, then set the structure’s SearchWindowSize field to the Overhead Messages
24 Protocol’s corresponding SearchWindowSize field. Otherwise, set the
25 structure’s SearchWindowSize field to NULL.
26 − If the Overhead Messages Protocol’s SearchWindowOffsetIncluded field is set to
27 ‘1’, then set the structure’s SearchWindowOffset field to the Overhead
28 Messages Protocol’s corresponding SearchWindowOffset field. Otherwise, set
29 the structure’s SearchWindowOffset field to NULL.
31 8.8.6.2.17.8.6.2.1 RouteUpdate
32 The access terminal sends the RouteUpdate message to notify the access network of its
33 current location and provide it with an estimate of its surrounding radio link conditions.
34
7-136
Field Length (bits)

MessageID 8
MessageSequence 8
ReferencePilotPN 9
ReferencePilotStrength 6
ReferenceKeep 1
NumPilots 4
NumPilots occurrences of the following fields:
PilotPNPhase 15
ChannelIncluded 1
Channel 0 or 24
PilotStrength 6
Keep 1
Reserved Variable
2 MessageSequence The access terminal shall set this field to the sequence number of
3 this message. The sequence number of this message is 1 more than
8
4 the sequence number of the last RouteUpdate message (modulo 2 )
5 sent by this access terminal. If this is the first RouteUpdate message
6 sent by the access terminal, it shall set this field to 0x00.
7 ReferencePilotPN The access terminal shall set this field to the access terminal’s time
8 reference (the reference pilot), relative to the zero offset pilot PN
9 sequence in units of 64 PN chips.
10 ReferencePilotStrength
11 The access terminal shall set this field to ⎣− 2 × 10 × log10PS ⎦, where
12 PS is the strength of the reference pilot, measured as specified in
13 7.8.6.1.2.3. If this value is less than 0, the access terminal shall set
14 this field to ‘000000’. If this value is greater than ‘111111’, the access
16 ReferenceKeep If the pilot drop timer corresponding to the reference pilot has
17 expired, the access terminal shall set this field to ‘0’; otherwise, the
18 access terminal shall set this field to ‘1’.
19 NumPilots The access terminal shall set this field to the number of pilots that
20 follow this field in the message.
7-137
1 PilotPNPhase The PN offset in resolution of 1 chip of a pilot in the Active Set or

2 Candidate Set of the access terminal that is not the reference pilot.
3 ChannelIncluded The access terminal shall set this field to ‘1’ if the channel for this
4 pilot offset is not the same as the current channel. Otherwise, the
6 Channel The access terminal shall include this field if the ChannelIncluded
7 field is set to ‘1’. The access terminal shall set this to the channel
8 record corresponding to this pilot (see 13.1). Otherwise, the access
9 terminal shall omit this field for this pilot offset.
10 PilotStrength The access terminal shall set this field to ⎣− 2 × 10 × log10PS ⎦, where
11 PS is the strength of the pilot in the above field, measured as
12 specified in 7.8.6.1.2.3. If this value is less than 0, the access
13 terminal shall set this field to ‘000000’. If this value is greater than
14 ‘111111’, the access terminal shall set this field to ‘111111’.
15 Keep If the pilot drop timer corresponding to the pilot in the above field
16 has expired, the access terminal shall set this field to ‘0’; otherwise,
17 the access terminal shall set this field to ‘1’.
18 Reserved The number of bits in this field is equal to the number needed to
19 make the message length an integer number of octets. This field shall
20 be set to all zeros.
21
22 8.8.6.2.27.8.6.2.2 TrafficChannelAssignment
23 The access network sends the TrafficChannelAssignment message to manage the access
24 terminal’s Active Set.
25
7-138
Field Length (bits)

MessageID 8
MessageSequence 8
ChannelIncluded 1
Channel 0 or 24
FrameOffset 4
DRCLength 2
DRCChannelGainBase 6
ACKChannelGain 6
NumPilots 4
NumPilots occurrences of the following record:
PilotPN 9
SofterHandoff 1
MACIndexLSBs 6
DRCCover 3
RABLength 2
RABOffset 3
RAChannelGainIncluded 0 or 1
NumPilots occurrences of the following field:
RAChannelGain 0 or 2
MACIndexMSBsIncluded 0 or 1
MACIndexMSB 0 or 1
DSCChannelGainBase 0 or 5
0 or N occurrences of the following field, where N
is the number of SofterHandoff fields set to ‘0’ in
this message
DSC 0 or 3
DeltaT2PsIncluded 0 or 1
DeltaT2P 0 or 6
7-139
Reserved Variable
3 MessageSequence field of the last TrafficChannelAssignment message
4 (modulo 2S, S=8) sent to this access terminal.
5 ChannelIncluded The access network shall set this field to ‘1’ if the Channel record is
6 included for these pilots. Otherwise, the access network shall set this
7 field to ‘0’.
8 Channel The access network shall include this field if the ChannelIncluded
9 field is set to ‘1’. The access network shall set this to the channel
11 network shall omit this field for this pilot offset. If Channel is
12 included, the access network shall set the SystemType field of the
13 Channel record to ‘0000’.
14 FrameOffset The access network shall set this field to the frame offset the access
15 terminal shall use when transmitting the Reverse Traffic Channel, in
16 units of slots.
17 DRCLength The access network shall set this field to the number of slots the
18 access terminal shall use to transmit a single DRC value, as shown
19 in Table 7.8.6.2-1.
20 Table 7.8.6.2-1. DRCLength Encoding
Field DRCLength
value (slots)
(binary)
‘00’ 1
‘01’ 2
‘10’ 4
‘11’ 8
21 DRCChannelGainBase
22 The access network shall set this field to the ratio of the power level
23 of the DRC Channel (when it is transmitted) to the power level of the
24 Reverse Traffic Pilot Channel expressed as 2's complement value in
25 units of 0.5 dB. The valid range for this field is from –9 dB to +6 dB,
26 inclusive. The access terminal shall support all the values in the
27 valid range for this field.
7-140
1 ACKChannelGain The access network shall set this field to the ratio of the power level
2 of the Ack Channel (when it is transmitted) to the power level of the
3 Reverse Traffic Pilot Channel expressed as 2's complement value in
4 units of 0.5 dB. The valid range for this field is from –3 dB to +6 dB,
5 inclusive. The access terminal shall support all the values in valid
6 range for this field.
7 NumPilots The access network shall set this field to the number of pilots
9 PilotPN The access network shall set this field to the PN Offset associated
10 with the sector that will transmit a Power Control Channel to the
11 access terminal, to whom the access terminal is allowed to point its
12 DRC, and whose Control Channel and Forward Traffic Channel the
13 access terminal may monitor.
14 SofterHandoff If the Forward Traffic Channel associated with this pilot will carry the
15 same closed-loop power-control bits as that of the previous pilot in
16 this message, the access network shall set this field to ‘1’; otherwise,
17 the access network shall set this field to ‘0’. The access network shall
18 set the first instance of this field to ‘0’. If the SofterHandoff field
19 associated with a PilotPN is equal to ‘1’, then the PilotPN is defined to
20 belong to the same cell as the previous PilotPN in this message.
21 MACIndexLSBs Least Significant Bits of the Medium Access Control Index. The
22 access network shall set this field to the six least significant bits of
23 the MACIndex assigned to the access terminal by this sector.
24 DRCCover The access network shall set this field to the index of the DRC cover
25 associated with the sector specified in this record.
26 RABLength If the traffic channel being assigned by this message is to use

27 Subtype 0 or Subtype 1 Reverse Traffic Channel MAC protocol, the
28 access network shall set the RABLength to specify the Reverse
29 Activity Bit length according to Table 9.7.6.2-2. Otherwise, the
31 Table 7.8.6.2-2. Encoding of the RABLength Field
Field value (binary) RABLength (slots)

‘00’ 8
‘01’ 16
‘10’ 32
‘11’ 64
32
7-141
1 RABOffset If the traffic channel being assigned by this message is to use

2 Subtype 0 or Subtype 1 Reverse Traffic Channel MAC protocol, the
3 access network shall set this field to indicate the offset associated
4 with the Reverse Activity Bit. Otherwise, the access network shall set
5 this field to ‘000’. The value (in slots) of RABOffset is the number the
6 field is set to multiplied by RABLength/8.
7 RAChannelGainIncluded
8 If this field is included, the access network shall set this field as
9 follows: If RAChannelGain field is included in this message, then the
12 RAChannelGain If RAChannelGainIncluded field is not included in this message or if

13 RAChannelGainIncluded field is equal to ‘0’, then the access network
15 as follows:
16 The ith occurrence of this field corresponds to the ith occurrence of
17 the PilotPN field in this message. The access network shall set the ith
18 occurrence of this field to the RA Channel Gain to be used by the
19 access terminal according to Table 7.8.6.2-3 of the ith PilotPN. The
20 access terminal uses this information to demodulate the RA Channel.
21 Table 7.8.6.2-3. Reverse Activity Channel Gain Encoding
Field RA Channel Gain

value
(dB)
(binary)
‘00’ −6
‘01’ −9
‘10’ −12
‘11’ −15
22 MACIndexMSBsIncluded
23 If the RAChannelGainIncluded field is not included in this message
24 or if RAChannelGainIncluded field is equal to ‘0’, then the access
25 network shall omit this field. Otherwise, the access network shall set
26 this field as follows: If MACIndexMSB fields are included in this
27 message, then the access network shall set this field to ‘1’.
29 MACIndexMSB Most significant bit of the Medium Access Control Index. If

30 MACIndexMSBsIncluded field is not included in this message or if
31 MACIndexMSBsIncluded field is equal to ‘0’, then the access network
33 as follows:
7-142
1 The ith occurrence of this field corresponds to the ith occurrence of

2 the PilotPN field in this message. The access network shall set the ith
3 occurrence of this field to the most significant bit of the 7-bit
4 MACIndex assigned to the access terminal by the ith PilotPN.
5 DSCChannelGainBase
6 If MACIndexMSBsIncluded field is not included in this message or if
9 to the power of the DSC channel relative to the pilot channel in units
10 of –0.5 dB, in the range from zero to –15.5 dB, inclusive.
11 DSC If MACIndexMSBsIncluded field is not included in this message or if

14 as follows: The access network shall set the ith occurrence of this
15 field to the DSC associated with the ith cell specified by the PilotPN
16 fields in this message.
17 DeltaT2PsIncluded
18 If the DSC field is not included in this message, then the access
19 network shall omit this field. If any of the fields after this field except
20 for Reserved are included the access network shall include this field.
21 Otherwise, the access network shall omit this field. If included, the
22 access network shall set this field as follows: If DeltaT2P fields are
23 included in this message, then the access network shall set this field
24 to ‘1’. Otherwise, the access network shall set this field to ‘0’.
25 DeltaT2P If DeltaT2PsIncluded field is not included in this message or if

26 DeltaT2sPIncluded field is equal to ‘0’, then the access network shall
27 omit this field. Otherwise, the ith occurrence of this field corresponds
28 to the ith occurrence of the PilotPN field in this message. The access
29 network shall set this field to the sector TxT2P offset value for the
30 corresponding pilot. This field is specified as a signed 6-bit value in
31 the range of -8.0 to 7.75 dB in units of 0.25 dB. The access terminal
32 shall support all valid values of this field.
36
7-143
Channels CC FTC SLP Reliable Best Effort67
1 8.8.6.2.37.8.6.2.3 TrafficChannelComplete
2 The access terminal sends the TrafficChannelComplete message to provide an
3 acknowledgment for the TrafficChannelAssignment message.
4
Field Length (bits)

MessageID 8
MessageSequence 8
7 of the TrafficChannelAssignment message whose receipt this message
8 is acknowledging.
9
Channels RTC SLP Reliable
10 8.8.6.2.47.8.6.2.4 ResetReport
11 The access network sends the ResetReport message to reset the RouteUpdate transmission
12 rules at the access terminal.
13
Field Length (bits)

MessageID 8

15
16 8.8.6.2.57.8.6.2.5 NeighborList
17 The NeighborList message is used to convey information corresponding to the neighboring
18 sectors to the access terminals when the access terminal is in the Connected State.
67 The TrafficChannelAssignment message sent in response to the Open command is sent

using best effort SLP. All subsequent TrafficChannelAssignment messages are sent using
reliable delivery SLP.
7-144
Field Length (bits)
MessageID 8
Count 5
Count occurrences of the following field:
PilotPN 9
Count occurrences of the following two fields:

ChannelIncluded 1
Channel 0 or 24
SearchWindowSizeIncluded 1
Count occurrences of the following field
SearchWindowSize 0 or 4
SearchWindowOffsetIncluded 1
SearchWindowOffset 0 or 3
FPDCHSupportedIncluded 0 or 1
m, 0 ≤ m ≤ Count. occurrences of the following field:
FPDCHSupported 0 or 1
Reserved Variable
3 Count The access network shall set this field to the number of records
4 specifying neighboring sectors information included in this message.
5 PilotPN The access network shall set this field to the PN Offset of a
6 neighboring sector for which the access network is providing search
7 window information in this message.
8 ChannelIncluded The access network shall set this field to ‘1’ if a Channel record is
9 included for this neighbor, and to ‘0’ otherwise. The access network
10 shall omit this field if the corresponding NeighborChannelIncluded
11 field is set to ‘0’. Otherwise, if included, the nth occurrence of this
12 field corresponds to the nth occurrence of PilotPN in the record that
7-145
1 contains the PilotPN field above.The access network may set this field
2 to ‘0’ if the channel associated with this pilot is the same as the
3 channel that is used to carry this message. If this field is set to ‘0’,
4 the access terminal shall assume that the channel associated with
5 this pilot is the same as the channel on which this message is
6 received. The nth occurrence of this field corresponds to the nth
7 occurrence of PilotPN in the record that contains the PilotPN field
8 above.
9 Channel Channel record specification for the neighbor channel. See 13.1 for
10 the Channel record format. The nth occurrence of this field
11 corresponds to the nth occurrence of PilotPN in the record that
12 contains the PilotPN field above.
13 SearchWindowSizeIncluded
14 The access network shall set this field to ‘1’ if SearchWindowSize field
15 for neighboring sectors is included in this message. Otherwise, the
17 SearchWindowSize The access network shall omit this field if SearchWindowSizeIncluded

18 is set to ‘0’. If SearchWindowSizeIncluded is set to ‘1’, the access
19 network shall set this field to the value shown in Table 7.8.6.2-4
20 corresponding to the search window size to be used by the access
21 terminal for the neighbor pilot. The nth occurrence of this field
7-146
1 Table 7.8.6.2-4. Search Window Sizes
Search Window
SearchWindowSize
Size
Value
(PN chips)
0 4
1 6
2 8
3 10
4 14
5 20
6 28
7 40
8 60
9 80
10 100
11 130
12 160
13 226
14 320
15 452
2 SearchWindowOffsetIncluded
3 The access network shall set this field to ‘1’ if SearchWindowOffset
4 field for neighboring sectors is included in this message. Otherwise,
5 the access network shall set this field to ‘0’.
6 SearchWindowOffset
7 The access network shall omit this field if
8 SearchWindowOffsetIncluded is set to ‘0’. If
9 SearchWindowOffsetIncluded is set to ‘1’, the access network shall
10 set this field to the value shown in Table 7.8.6.2-5 corresponding to
11 the search window offset to be used by the access terminal for the
12 neighbor pilot. The nth occurrence of this field corresponds to the nth
14 above.
7-147
1 Table 7.8.6.2-5. Search Window Offset
SearchWindowOffset Offset ( PN chips)
0 0
1 WindowSize68 /2
2 WindowSize
3 3 × WindowSize /2
4 - WindowSize /2
5 - WindowSize
6 -3 × WindowSize /2
7 Reserved
2 FPDCHSupportedIncluded
4 follows:
5 The access network shall set this field to ‘0’ if the FPDCHSupported
6 fields are omitted. Otherwise, the access network shall set this field
7 to ‘1’.
8 FPDCHSupported If FPDCHSupportedIncluded is not included or is included and is set

9 to ‘0’, the access network shall omit all occurrences of this field.
10 Otherwise, the access network shall include m occurrences of this
11 field, where m is the number of Channel records in this message that
12 have SystemType equal to 0x01, and the access network shall set the
13 occurrences of this field as follows:
14 The access network shall set the ith occurrence of this field as
15 follows:
16 If the system on the CDMA Channel corresponding to the ith Channel

17 record (see 13.1) that has SystemType equal to 0x01 supports the
18 Forward Packet Data Channel (see [3]), the access terminal shall set
19 the ith occurrence of this field to ‘1’. Otherwise, the access network
20 shall set the ith occurrence of this field to ‘0’.
22 make the message length an integer number of octets. The access
24 this field.
68 WindowSize is pilot’s search window size in PN chips.
7-148
2 8.8.6.2.67.8.6.2.6 AttributeOverride
3 The access network may send this message in order to override the configured values for
4 the attributes includes in this message.
5
Field Length (bits)
MessageID 8
MessageSequence 8
One or more instances of the following record:
AttributeRecord variable
8 MessageSequence field of the last AttributeOverride message (modulo
9 2S, S=8) sent to this access terminal.
10 The access network shall include one or more instances of the following record:
11 AttributeRecord The access network shall set this record to the attribute record that
12 the access terminal is to use to override the values of the configured
13 attribute specified by the AttributeID of this record. See 13.3 for the
14 format of the attributes. The access network shall not include more
15 than one AttributeRecord with the same AttributeID in this message.
16 The access network shall include exactly one instance of attribute
17 values per AttributeID. The access network shall set the ValueID
18 associated with the complex attributes to zero. The valid attribute
19 records that can be included in this message are
20 SetManagementSameChannelParameters and
21 SetManagementDifferentChannelParameters.
22
23 8.8.6.2.77.8.6.2.7 AttributeOverrideResponse
24 The access terminal sends the AttributeOverrideResponse message to provide an
25 acknowledgment for the AttributeOverride message.
26
7-149
Field Length (bits)
MessageID 8
MessageSequence 8
3 of the AttributeOverride message whose receipt this message is
4 acknowledging.
5
6 8.8.6.2.87.8.6.2.8 RouteUpdateRequest
7 The access network sends a RouteUpdateRequest message to request the access terminal
8 to send a RouteUpdate message.
9
Field Length (bits)
MessageID 8
ChannelIncluded 1
Channel 0 or 24
SectorCount 0 or 4
SectorCount occurrences of the following field:
SectorPilotPN 9
SectorSearchWindowSizeIncluded 0 or 1
SectorSearchWindowSize 0 or 4
SectorSearchWindowOffsetIncluded 0 or 1
SectorSearchWindowOffset 0 or 3
0 – 7 (as
Reserved
needed)
7-150
1 ChannelIncluded If SupportRouteUpdateEnhancements is less than 0x02 or if this

2 message is being sent on the Control Channel, the access network
3 shall set this field to ‘0’. Otherwise, the access network may set this
4 field to ‘1’ to indicate that the Channel field is included or to ‘0’ to
5 indicate that the Channel field is not included.
6 Channel If ChannelIncluded is set to ‘0’, the access network shall omit this
7 field. Otherwise, the access network shall set this field to a Channel
8 record specification. See 13.1 for the Channel record format. The
9 access network shall set the SystemType field of this record to 0x00 if
10 SupportRouteUpdateEnhancements is equal to 0x02. The access
11 network shall set SystemType field of this record to 0x00 or 0x01 if
12 SupportRouteUpdateEnhancements is equal to 0x03.
13 SectorCount If ChannelIncluded is set to ‘0’, the access network shall omit this
14 field. Otherwise, the access network shall set this field to the number
15 of records specifying neighboring sectors information included in this
16 message.
17 SectorPilotPN The access network shall set this field to the PN Offset of a
18 neighboring sector for which the access terminal is to report pilot
19 strength information.
20 SectorSearchWindowSizeIncluded
21 If ChannelIncluded is set to ‘0’, the access network shall omit this
22 field. Otherwise, the access network shall set this field to ‘1’ if
23 SectorSearchWindowSize field for neighboring sectors is included in
24 this message. Otherwise, the access network shall set this field to ‘0’.
25 SectorSearchWindowSize
27 SectorSearchWindowSizeIncluded is set to ‘0’. If
28 SectorSearchWindowSizeIncluded is set to ‘1’, the access network
29 shall set this field to the value shown in Table 7.8.6.2.8-1
32 corresponds to the nth occurrence of SectorPilotPN in the record that
33 contains the SectorPilotPN field above.
7-151
1 Table 7.8.6.2.8-1. Search Window Sizes
Search Window
SearchWindowSize
Size
Value
(PN chips)
0 4
1 6
2 8
3 10
4 14
5 20
6 28
7 40
8 60
9 80
10 100
11 130
12 160
13 226
14 320
15 452
2 SectorSearchWindowOffsetIncluded
5 SectorSearchWindowOffset field for neighboring sectors is included in
7 SectorSearchWindowOffset
9 SectorSearchWindowOffsetIncluded is set to ‘0’. If
10 SectorSearchWindowOffsetIncluded is set to ‘1’, the access network
12 corresponding to the search window offset to be used by the access
7-152
1 Table 7.8.6.2.8-2. Search Window Offset
0 0
1 WindowSize69 /2
2 WindowSize
4 - WindowSize /2
5 - WindowSize
7 Reserved
4 network shall set this field to 0. The access terminal shall ignore this
5 field.
6
Channels FTC CC SLP Best Effort
9 given attribute.
10
Field Length (bits)
MessageID 8
TransactionID 8

15
7-153
4
Field Length (bits)
MessageID 8
TransactionID 8
8
12
Field Length (bits)
MessageID 8
TransactionID 8
16
18 8.8.6.3.17.8.6.3.1 Commands Sent

7-154
1 • ReverseTrafficChannelMAC.Activate
2 • ReverseTrafficChannelMAC.Deactivate
3 • ForwardTrafficChannelMAC.Activate
4 • ForwardTrafficChannelMAC.Deactivate
5 • AccessChannelMAC.Activate
6 • AccessChannelMAC.Deactivate
7 8.8.6.3.27.8.6.3.2 Indications

14 Default Route Update Protocol. If the value of the SupportRouteUpdateEnhancements
15 attribute is not 0x00, then the access terminal and the access network shall support the
16 use of the Generic Attribute Update Protocol to update values of the following attributes
17 belonging to the Default Route Update Protocol:
18 • RouteUpdateRadiusMultiply
19 • RouteUpdateRadiusAdd
21 network shall not include the RouteUpdateRadiusMultiply and RouteUpdateRadiusAdd
22 attributes in an AttributeUpdateRequest message.

24 The configurable simple attributes for this protocol are listed in Table 7.8.7.1-1. The access
25 terminal shall not include these simple attributes in a ConfigurationRequest message or an
27 The access terminal and access network shall use as defaults the values in Table 7.8.7.1-1
28 that are typed in bold italics.
7-155
1 Table 7.8.7.1-1. Configurable Values
Attribute Attribute Value Meaning

ID s
0x00 The
SetManagementSameChannelPar
ameters and
SetManagementDifferentChannel
Parameters attributes in the
AttributeOverride message are
discarded.
0x01 The
0x03 SetManagementOverrideAllowed
SetManagementSameChannelPar
ameters and
SetManagementDifferentChannel
Parameters attributes in the
AttributeOverride message are
acted upon.
0x02- Reserved
0xff
0x00 Distance-based registration is
disabled.
0x0a Multiplier for the Route update
radius is 1.
0x01 Multiplier for the Route update
0xff RouteUpdateRadiusMultiply to radius in units of 0.1.
0x64
All Reserved
other
value
s
0x00 Addition to the Route update
00 radius is zero.
0x00 Addition to the Route update
01 to radius expressed as 2’s
0xfe RouteUpdateRadiusAdd 0x0fff complement value.
All Reserved
other
value
s
Protocol to update
RouteUpdateRadiusMultiply and
SupportRouteUpdateEnhanceme
0xfd RouteUpdateRadiusAdd and
nts
processing of
RouteUpdateRequest message is
not supported.
7-156

ID s
Protocol to update
RouteUpdateRadiusAdd and
processing of
RouteUpdateRequest message
without Channel Record is
supported.
Protocol to update
processing of
with Channel Record whose
SystemType is equal to 0x00 is
supported.
Protocol to update
processing of
with Channel Record whose
SystemType is equal to 0x00 and
0x01 is supported.
All Reserved
other
value
s

3 record definition). The following complex attributes are to be used only by the access
4 network in a ConfigurationRequest message:
5 • SearchParameters
6 • SetManagementSameChannelParameters
7 • SetManagementDifferentChannelParameters
8 The following complex attributes are to be used only by the access terminal in a
9 ConfigurationRequest message:
10 • SupportedCDMAChannels
11 8.8.7.2.17.8.7.2.1 SearchParameters Attribute

12
7-157
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
PilotIncrement 4 4
SearchWindowActive 4 8
SearchWindowNeighbor 4 10
SearchWindowRemaining 4 10
1 Length Length of the complex attribute in octets. The access network shall
3 Length field.
4 AttributeID The access network shall set this field to 0x00.
5 ValueID This field identifies this particular set of values for the attribute. The
6 access network shall increment this field for each complex attribute-
7 value record for a particular attribute.
8 PilotIncrement The access network shall set this field to the pilot PN sequence
9 increment, in units of 64 PN chips, that access terminals are to use
10 for searching the Remaining Set. The access network should set this
11 field to the largest increment such that the pilot PN sequence offsets
12 of all its neighbor access networks are integer multiples of that
13 increment. The access terminal shall support all the valid values for
14 this field.
15 SearchWindowActive
16 Search window size for the Active Set and Candidate Set. The access
19 terminal for the Active Set and Candidate Set. The access terminal
20 shall support all the valid values specified by this field.
21 SearchWindowNeighbor
22 Search window size for the Neighbor Set. The access network shall
24 the search window size to be used by the access terminal for the
25 Neighbor Set. The access terminal shall support all the valid values
26 specified by this field.
27 SearchWindowRemaining
28 Search window size for the Remaining Set. The access network shall
7-158

3 Remaining Set. The access terminal shall support all the valid values
5 8.8.7.2.27.8.7.2.2 SetManagementSameChannelParameters Attribute

6 The access terminal shall use these attributes if the pilot being compared is on the same
7 channel as the active set pilots’ channel.
8
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
PilotAdd 6 0x0e
PilotCompare 6 0x05
PilotDrop 6 0x12
PilotDropTimer 4 3
DynamicThresholds 1 0
SoftSlope 0 or 6 N/A
AddIntercept 0 or 6 N/A
DropIntercept 0 or 6 N/A
NeighborMaxAge 4 0
Reserved variable N/A
}
11 Length field.
16 PilotAdd This value is used by the access terminal to trigger a RouteUpdate in

17 the Connected State. The access network shall set this field to the
18 pilot detection threshold, expressed as an unsigned binary number
7-159
1 equal to ⎣- 2 × 10 × log10 Ec/I0 ⎦. The value used by the access

2 terminal is –0.5 dB times the value of this field. The access terminal
4 PilotDrop This value is used by the access terminal to start a pilot drop timer
5 for a pilot in the Active Set or the Candidate Set. The access network
6 shall set this field to the pilot drop threshold, expressed as an
7 unsigned binary number equal to ⎣- 2 × 10 × log10 Ec/I0 ⎦. The value
8 used by the access terminal is –0.5 dB times the value of this field.
9 The access terminal shall support all the valid values specified by
10 this field.
11 PilotCompare Active Set versus Candidate Set comparison threshold, expressed as

12 a 2’s complement number. The access terminal transmits a
13 RouteUpdate message when the strength of a pilot in the Candidate
14 Set exceeds that of a pilot in the Active Set by this margin. The
15 access network shall set this field to the threshold Candidate Set
16 pilot to Active Set pilot ratio, in units of 0.5 dB. The access terminal
18 PilotDropTimer Timer value after which an action is taken by the access terminal for
19 a pilot that is a member of the Active Set or Candidate Set, and
20 whose strength has not become greater than the value specified by
21 PilotDrop. If the pilot is a member of the Active Set, a RouteUpdate
22 message is sent in the Connected State. If the pilot is a member of
23 the Candidate Set, it will be moved to the Neighbor Set. The access
24 network shall set this field to the drop timer value shown in Table
25 7.8.7.2.2-1 corresponding to the pilot drop timer value to be used by
26 access terminals. The access terminal shall support all the valid
27 values specified by this field.
7-160
1 Table 7.8.7.2.2-1. Pilot Drop Timer Values
Timer Timer
PilotDropTimer Expiration PilotDropTimer 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
2 DynamicThresholds This field shall be set to ‘1’ if the following three fields are included in
3 this record. Otherwise, this field shall be set to ‘0’.
4 SoftSlope This field shall be included only if DynamicThresholds is set to ‘1’.

5 This field shall be set to an unsigned binary number, which is used
6 by the access terminal in the inequality criterion for adding a pilot to
7 the Active Set or dropping a pilot from the Active Set. The access
8 terminal shall support all the valid values specified by this field.
9 AddIntercept This field shall be included only if DynamicThresholds is set to ‘1’.

10 This field shall be set to a 2’s complement signed binary number in
11 units of dB. The access terminal shall support all the valid values
13 DropIntercept This field shall be included only if DynamicThresholds is set to ‘1’.

17 NeighborMaxAge The access network shall set this field to the maximum AGE value
18 beyond which the access terminal is to drop members from the
22 shall ignore this field. The length of this field shall be such that the
23 attribute value record is octet-aligned.
7-161
1 8.8.7.2.37.8.7.2.3 SetManagementDifferentChannelParameters Attribute

2 The access terminal shall use these attributes if the pilot being compared is on a channel
3 that is different from the active set pilots’ channel.
4
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
PilotAdd 6 0x0e
PilotCompare 6 0x05
PilotDrop 6 0x12
PilotDropTimer 4 3
NeighborMaxAge 4 0
}
7 Length field.

7-162
7 this field.




7-163
7 attribute value record is octet-aligned.
8 8.8.7.2.47.8.7.2.4 SupportedCDMAChannels Attribute

9 The access terminal uses this attribute to convey to the access network the CDMA
10 Channels supported by the access terminal.
11
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
BandClassCount 8 0
BandClassCount occurrences of the following record:
{
BandClass 5 N/A
BandSubClassCount 8 N/A
BandSubClassCount occurrences of the following field:
BandSubClass 8 N/A
}
Reserved 0–7 N/A
(as needed)
}
14 Length field.
17 access terminal shall set this field to an identifier assigned to this
18 complex value.
7-164
1 BandClassCount The access terminal shall set this field to the number of occurrences
2 of the BandClass field in this complex value.
3 BandClass The access terminal shall set this field to the band class supported
4 by the access terminal.
5 BandSubClassCount The access terminal shall set this field to the number of band sub-
6 classes supported by the access terminal in this band class.
7 BandSubClass The access terminal shall set this field to the band sub-class
9 Reserved The access terminal shall add reserved bits to make the length of
10 each attribute value record equal to an integer number of octets. The
11 access terminal shall set this field to zero. The access network shall

14

NRUPType Type field for this protocol Table 2.5.4-1
NRUPDefault Subtype field for this protocol 0x0000
NRUPActive Maximum size of the Active Set 6
NRUPCandidate Maximum size of the Candidate Set 6
NRUPNeighbor Minimum size of the Neighbor Set 20

17 This protocol defines the following parameter record in addition to the configuration
19 8.8.9.17.8.9.1 RouteUpdate Parameter

20 The following parameter shall be included in the Session State Information record only if
21 the Session State Information is being transferred while the connection is open.
7-165
1 Table 7.8.9.1-1. The Format of the Parameter Record for the RouteUpdate Parameter
Field Length (bits)

ParameterType 8
Length 8
TCAMessageSequence 8
RUPMessageSequence 8
ChannelIncluded 1
Channel 0 or 24
FrameOffset 4
DRCLength 2
DRCChannelGainBase 6
ACKChannelGain 6
NumPilots 4
NumPilots occurrences of the following fields
PilotPN 9
SectorID 128
SofterHandoff 1
MACIndexLSBs 6
DRCCover 3
RABLength 2
RABOffset 3
Reserved Variable
5 TCAMessageSequence
6 This field shall be set to the MessageSequence field of the last
7 TrafficChannelAssignment message that was sent by the source
8 access network.
9 RUPMessageSequence
11 RouteUpdate message that was received by the source access
12 network.
7-166
1 ChannelIncluded This field shall be set to the ChannelIncluded field in the last
3 access network.
4 Channel This field shall be included only if the ChannelIncluded field is set to
5 ‘1’. If included, this field shall be set to the last Channel field of the
6 last TrafficChannelAssignment message that was sent by the source
7 access network.
8 FrameOffset This field shall be set to the FrameOffset field in the last
10 access network.
11 DRCLength This field shall be set to the DRCLength field in the last
13 access network.
15 This field shall be set to the DRCChannelGainBase field in the last

17 access network.
18 ACKChannelGain This field shall be set to the ACKChannelGain field in the last
20 access network.
21 NumPilots This field shall be set to the NumPilots field in the last
23 access network.
24 PilotPN This field shall be set to the corresponding PilotPN field in the last
26 access network.
27 SectorID This field shall be set to the SectorID corresponding to the sector
28 associated with the PilotPN specified above.
29 SofterHandoff This field shall be set to the corresponding SofterHandoff field in the
31 access network.
32 MACIndexLSBs This field shall be set to the corresponding MACIndexLSBs field in

33 the last TrafficChannelAssignment message that was sent by the
34 source access network.
7-167
1 DRCCover This field shall be set to the corresponding DRCCover field in the last
3 access network.
4 RABLength This field shall be set to the corresponding RABLength field in the
6 access network.
7 RABOffset This field shall be set to the corresponding RABOffset field in the last
9 access network.
11 make the length of this parameter record length an integer number of
12 octets. This field shall be set to all zeros.
13 8.8.9.27.8.9.2 ExtendedRouteUpdate Parameter

15 the Session State Information is being transferred while the connection is open, and if
16 MACIndexMSB fields were included in the last TrafficChannelAssignment message that
17 was sent by the source access network.
7-168
1 Table 7.8.9.2-1. The Format of the Parameter Record for the ExtendedRouteUpdate
2 Parameter
Field Length (bits)

ParameterType 8
Length 8
NumPilots 4
MACIndexMSB 1
DSCChannelGainBase 5
NumCells 4
NumCells occurrences of the following field:
DSC 3
DeltaT2PsIncluded 0 or 1
DeltaT2P 0 or 6
6 NumPilots This field shall be set to the NumPilots field in the last
8 access network.
9 MACIndexMSB This field shall be set to the corresponding MACIndexMSB field in the
11 access network.
13 This field shall be set to the DSCChannelGainBase field in the last
15 access network.
16 NumCells This field shall be set to the number of DSC fields included in the last
18 access network.
7-169
1 DSC This field shall be set to the corresponding DSC field in the last
3 access network.
4 DeltaT2PsIncluded If any of the fields after this field except for Reserved are included the
5 access network shall include this field. Otherwise, the access
6 network shall omit this field. If included, the access network shall set
7 this field as follows: If DeltaT2P fields are included in this message,
10 DeltaT2P If DeltaT2PsIncluded field is not included or if DeltaT2sPIncluded

11 field is set to ‘0’, then the access network shall omit this field.
12 Otherwise,the ith occurrence of this field corresponds to the ith
13 occurrence of the PilotPN field in this message. The access network
14 shall set this field to the sector TxT2P offset value for the
15 corresponding pilot. This field is specified as a signed 6-bit value in
16 the range of -8.0 to 7.75 dB in units of 0.25 dB. The access terminal
17 shall support all valid values of this field.
21 8.8.9.37.8.9.3 AttributeOverrideMessageSequence Parameter

23 the Session State Information is being transferred while the Connection is open and
24 SetManagementOverrideAllowed is set to 0x01.

26 AttributeOverrideMessageSequence Parameter
Length
Field (bits)
ParameterType 8
Length 8
AttributeOverrideMessageSequence 8
30 AttributeOverrideMessageSequence
32 AttributeOverride message that was sent by the source access
7-170
1 network. If the access network has not sent the AttributeOverride

2 message during this connection, then this field shall be set to 255.
7-171
1 8.97.9 Multicarrier Route Update Protocol
2 8.9.17.9.1 Overview
3 The Multicarrier Route Update Protocol provides the procedures and messages used by the
4 access terminal and the access network to keep track of the access terminal’s approximate
5 location and to maintain the radio link as the access terminal moves between the coverage
6 areas of different sectors. . This protocol is not designed to operate with subtype 0, 1, and
7 2 of the Reverse Traffic Channel MAC Protocol.
10 • Idle State: This state corresponds to the Air-Link Management Protocol Idle State. In
11 this state, the access terminal autonomously maintains the Active Set. Route update
12 messages from the access terminal to the access network are based on the distance
13 between the access terminal’s current serving sector and the serving sector at the time
14 the access terminal last sent an update.
15 • Connected State: In this state the access network dictates the access terminal’s Active
16 Set. Route update messages from the access terminal to the access network are based
17 on changing radio link conditions.
18 Transitions between states are driven by commands received from Connection Layer
19 protocols and the transmission and reception of the TrafficChannelAssignment message.
20 The protocol states, messages and commands causing the transition between the states are
21 shown in Figure 7.9.1-1.
Tx / Rx
Initial State TrafficChannelAssignment
Rx Activate
Inactive Connected
Idle State
State State
Rx Deactivate Rx Close
22
Rx Deactivate
23 Figure 7.9.1-1. Multicarrier Route Update Protocol State Diagram
24 Throughout this protocol a pilot is defined to be specified by a <Pilot PN, CDMA Channel>
25 pair.
26 This protocol uses parameters that are provided, as public data by the Overhead Messages
27 Protocol, configured attributes, or protocol constants.
7-172
1 Table 7.9.1-1 lists all of the protocol parameters obtained from the public data of the
4 Overhead Messages Protocol
RU Parameter Comment
Latitude Latitude of sector in units of 0.25 second
Longitude Longitude of sector in units of 0.25 second
Distance (unless modified by the
RouteUpdateRadiusMultiply and/or
RouteUpdateRadiusOverh RouteUpdateRadiusAdd attributes) between the serving
ead sector and the sector in which location was last reported
which triggers a new report. If this field is set to zero, then
distance triggered reporting is disabled
NumNeighbors Number of neighbors specified in the message
NeighborPN PN Offset of each neighbor in units of 64 PN chips
NeighborChannelIncluded Set to ‘1’ if a Channel Record is included for the neighbor
Neighbor Channel Record specifying network type and
NeighborChannel
frequency
6 8.9.2.17.9.2.1 Commands
8 • Activate
9 • Deactivate
10 • Open
11 • Close
12 • SendRouteUpdate

15 • ConnectionLost (access network only)
16 • NetworkLost
17 • IdleHO
18 • ActiveSetUpdated
19 • AssignmentRejected
20 • ConnectionInitiated
7-173
2 8.9.2.37.9.2.3 Public Data

5 • All <Pilot PN, CDMA Channel> pairs in the Active Set
6 • The reverse link CDMA channels assigned to the access terminal.
7 • The FeedbackEnabled field associated with each sub-Active Set.
8 • If the FeedbackEnabled field associated with the sub-Active Set is set to ‘1’, the reverse
9 link CDMA channel that is used to send the MAC channel information (e.g., DRC, DSC,
10 ACK) associated with each sub-Active Set and the corresponding
11 FeedbackMultiplexingIndex for transmission of DRC, DSC, and ACK channels. If the
12 FeedbackEnabled field associated with the sub-Active Set is set to ‘0’, the above
13 information is not made public.
14 • The DSCForThisSubActiveSetEnabled associated with each of the assigned sub-Active
15 Sets
16 • The pilots in the Active Set that carry Control Channel.
17 • Information provided by the SofterHandoff field in the TrafficChannelAssignment
18 message for every pilot in the Active Set
19 • ForwardTrafficMACIndex and the associated interlaces for every pilot in the Active Set
20 • For each of the reverse CDMA channels assigned to the access terminal, the Active Set
21 member and the corresponding ReverseLinkMACIndex associated with the reverse link
22 CDMA channel.
23 • For each of the reverse CDMA channels assigned to the access terminal, the Active Set
24 member and the corresponding RABMACIndex associated with the reverse link CDMA
25 channel.
26 • Scheduler Group associated with each of the pilots in the Active Set.
27 • The sub-Active Set associated with each DRC Cover channel (see 7.9.6.1.2.5).
28 • The ReverseChannelDroppingRank associated with each of the assigned reverse link
29 CDMA channels.
30 • The MAC Index associated with each of the pilots in a sub-Active Set that is used to
31 carry the DRCLock channel for each of the reverse link CDMA channels70.
32 • SupportedCDMAChannels attribute
33 • Pilot strength of all pilots in the Active Set
70 In this protocol subtype, the MAC indexMAC Index and the forward CDMA channel that carry the
RPC and DRCLock are the same.
7-174
1 • FrameOffset specified in the TrafficChannelAssignment message

2 • Current RouteUpdate message
3 • The PilotReference sub-Active Set as specified in the TrafficChannelAssignment
4 message
5 • DeltaT2P for all pilots in the Active Set that carry RAB for a Reverse CDMA Channel


23 8.9.5.17.9.5.1 Procedures
25 the configuration messages. The access terminal should send a ConfigurationRequest
26 message containing the SupportedCDMAChannels attribute. If the access terminal sends a
27 ConfigurationRequest message containing the SupportedCDMAChannels attribute, then
28 the access terminal shall include in the attribute all Band Classes and Band Sub-classes

7-175
1 • The value of the following public data of the InUse instance of the protocol shall be set
2 to the corresponding attribute value of the InConfiguration protocol instance:
3 − SupportedCDMAChannels
4 • If the InUse instance of the Route Update Protocol has the same subtype as this
5 protocol instance, but the InUse instance of any other protocol in the Connection Layer
6 does not have the same subtype as the corresponding InConfiguration protocol
7 instance, then
17 • If the InUse instance of all protocols in the Connection Layer have the same subtype as
18 the corresponding InConfiguration protocol instance, then
22 − The InUse protocol instance at the access terminal shall perform the
26 • If the InUse instance of the Route Update Protocol does not have the same subtype as
27 this protocol instance, then the access terminal and the access network shall perform
28 the following:
34 instance for the Route Update Protocol at the access terminal and the access
35 network.
7-176
4
Field Length (bits)
MessageID 8
TransactionID 8
12
Field Length (bits)
MessageID 8
TransactionID 8

7-177
3 8.9.6.17.9.6.1 Procedures
5 8.9.6.1.1.17.9.6.1.1.1 Activate
10 8.9.6.1.1.27.9.6.1.1.2 Deactivate
12 If the protocol receives this command in any other state, the access terminal and the
13 access network shall:
16 • Issue an AccessChannelMAC.Deactivate command,
18 8.9.6.1.1.37.9.6.1.1.3 Open
19 If the protocol receives an Open command in the Idle State,
20 • The access terminal shall ignore it.
21 • The access network shall:
22 − Transmit a TrafficChannelAssignment message as follows:
23 + The access network should base the TrafficChannelAssignment message on the
24 last RouteUpdate message it received from the access terminal,
25 + If the SupportedCDMAChannels attribute contains one or more band classes,
26 then the access network shall assign a Traffic Channel on CDMA Channel(s)
27 supported by the access terminal as indicated by the value of the
28 SupportedCDMAChannels attribute.
29 + Channel(s) assigned to the access terminal shall be subject to the constraints
30 specified by the attributes of this protocol and the restrictions made public by
31 the physical layer protocol.
7-178
1 + The forward interlaces assigned to the access terminal shall be subject to the
2 supported DRX pattern(s) as specified by the SupportedDRXPatterns
3 attribute.
4 + The access network shall set the SubActiveSetCarriesControlChannel field of
5 the TrafficChannelAssignment for exactly one sub-Active Set in the access
6 terminal’s Active Set. The access network shall not set the
7 SubActiveSetCarriesControlChannel field associated with a sub-Active Set to
8 ‘1’ unless the sub-Active Set carries power control commands for at least one
9 reverse CDMA channel.71
10 + The access network shall set the FeedbackEnabled field for the sub-Active Sets
11 that carry power control commands for a reverse CDMA channel to ‘1’.
12 + DRC covers associated with members of the sub-Active Set shall be unique
13 within the sub-active set
14 + No two pilots in the sub-Active Set shall be in the same Pilot Group
15 − Return a ConnectionInitiated indication,
16 − Issue a ReverseTrafficChannelMAC.Activate command including the list of
17 Reverse CDMA Channels that are assigned in the TrafficChannelAssignment
18 message,
19 − Issue a ForwardTrafficChannelMAC.Activate command,
20 − Issue an AccessChannelMAC.Deactivate command,
21 − Transition to the Connected State.
23 8.9.6.1.1.47.9.6.1.1.4 Close
24 If the protocol receives a Close command in the Connected State the access terminal and
25 the access network shall:
71 This is to ensure that there is a ForwardTrafficValid bit in the QuickConfig message associated
with the access terminal.
7-179
1 8.9.6.1.27.9.6.1.2 Pilots and Pilot Sets

2 The access terminal estimates the strength of the Forward Channel transmitted by each
3 sector in its neighborhood. This estimate is based on measuring the strength of the
4 Forward Pilot Channel, henceforth referred to as the pilot.
5 When this protocol is in the Connected State, the access terminal uses pilot strengths to
6 decide when to generate RouteUpdate messages.
7 When this protocol is in the Idle State, the access terminal uses pilot strengths to decide
8 which sector’s Control Channel it monitors.
9 The following pilot sets are defined to support the Route Update process:
10 • Active Set: The set of pilots associated with the sectors currently serving the access
11 terminal. When a connection is open, a sector is considered to be serving an access
12 terminal when there is a Forward Traffic Channel assigned to the access terminal.
13 When a connection is not open, a sector is considered to be serving the access terminal
14 when the access terminal is monitoring that sector’s control channel.
15 • Candidate Set: The pilots that are not in the Active Set, but are received by the access
16 terminal with sufficient strength to indicate that the sectors transmitting them are good
17 candidates for inclusion in the Active Set.
18 • Neighbor Set: The set of pilots that are not in either one of the two previous sets, but
19 are likely candidates for inclusion in the Active Set.
20 • Remaining Set: The set of all possible pilots excluding the pilots that are in any of the
21 three previous sets.
22 At any given instant a pilot is a member of exactly one set.
23 The access terminal maintains all four sets. The access network maintains only the Active
24 Set.
25 The access terminal complies with the following rules when searching for pilots, estimating
26 the strength of a given pilot, and moving pilots between sets.
27 8.9.6.1.2.17.9.6.1.2.1 Neighbor Set Search Window Parameters Update

28 The access terminal shall maintain RouteUpdateNeighborList which is a list of structures of
29 type Neighbor (defined below). For each pilot in the Neighbor Set, the access terminal shall
30 maintain a structure in the RouteUpdateNeighborList.
31 A Neighbor structure consists of four fields: PilotPN, CDMA Channel, SearchWindowSize,
32 and SearchWindowOffset.
33 The RouteUpdateNeighborList is used by the access terminal to perform pilot search on a
34 pilot in the Neighbor Set.
35 When this set of procedures is invoked, the access terminal shall perform the following
36 steps in the order specified:
37 • For each pilot in the Neighbor Set, the access terminal shall first initialize the
38 corresponding Neighbor structure in RouteUpdateNeighborList as follows:
7-180
1 − Set the structure’s PilotPN field to the neighbor pilot’s PN.

2 − Set the structure’s Channel field to the neighbor pilot’s channel record.
3 − Set the structure’s SearchWindowSize field to the configurable attribute
4 SearchWindowNeighbor.
5 − Set the structure’s SearchWindowOffset to zero.
6 • For each pilot listed in the OverheadMessagesNeighborList, the access terminal shall
7 set the non-NULL fields of the corresponding Neighbor structure in the
8 RouteUpdateNeighborList to the fields of the Neighbor structure in the
9 OverheadMessagesNeighborList for this pilot.
10 • For each pilot listed in the NeighborListMessageNeighborList, the access terminal shall
11 set the non-NULL fields of the corresponding Neighbor structure in the
12 RouteUpdateNeighborList to the fields of the Neighbor structure in the
13 NeighborListMessageNeighborList for this pilot.
14 8.9.6.1.2.27.9.6.1.2.2 Pilot Search

15 The access terminal shall continually search for pilots in the Connected State and
16 whenever it is monitoring the Control Channel in the Idle State. The access terminal shall
17 search for pilots in all pilot sets. This search shall be governed by the following rules:
18 Search Priority: The access terminal should use the same search priority for pilots in
19 the Active Set and Candidate Set. In descending order of search rate, the access
20 terminal shall search, most often, the pilots in the Active Set and Candidate Set,
21 then shall search the pilots in the Neighbor Set, and lastly shall search the pilots in
22 the Remaining Set.
23 Search Window Size: The access terminal shall use the search window size specified by
24 the configurable attribute SearchWindowActive for pilots in the Active Set and
25 Candidate Set. For each pilot in the Neighbor Set, the access terminal shall use the
26 search window size specified by Table 7.9.6.2-4 and SearchWindowSize field of the
27 corresponding Neighbor structure in the RouteUpdateNeighborList. The access
28 terminal shall use search window size specified by configurable attribute
29 SearchWindowRemaining for pilots in the Remaining Set.
30 Search Window Center: The access terminal should center the search window around
31 the earliest usable multipath component for pilots in the Active Set. The access
32 terminal should center the search window for each pilot in the Neighbor Set around
33 the pilot’s PN sequence offset plus the search window offset specified by Table
34 7.9.6.2-5 and SearchWindowOffset field of the corresponding Neighbor structure in
35 the RouteUpdateNeighborList using timing defined by the access terminal’s time
36 reference (see 10.4.1.3.6). The access terminal should center the search window
37 around the pilot’s PN sequence offset using timing defined by the access terminal’s
38 time reference (see 10.4.1.3.6) for the Remaining Set.
7-181
1 8.9.6.1.2.37.9.6.1.2.3 Pilot Strength Measurement

2 The access terminal shall measure the strength of every pilot it searches. The strength
3 estimate formed by the access terminal shall be computed as the sum of the ratios of
4 received pilot energy per chip, Ec, to total received spectral density, I0 (signal and noise) for
5 at most k multipath components, where k is the maximum number of multipath
6 components that can be demodulated simultaneously by the access terminal.
7 8.9.6.1.2.47.9.6.1.2.4 Pilot Drop Timer Maintenance

8 For each pilot, the access terminal shall maintain a pilot drop timer.
10 • The access terminal shall start a pilot drop timer for each pilot in the Candidate Set or
11 the Active Set whenever the strength becomes less than the value specified by
12 PilotDrop. The access terminal shall consider the timer to be expired after the time
13 specified by PilotDropTimer.
14 • The access terminal shall reset and disable the timer whenever the strength of the pilot
15 becomes greater than the value specified by PilotDrop.
17 • The access terminal shall start a pilot drop timer for each pilot in the Candidate Set
18 whenever the strength of the pilot becomes less than the value specified by PilotDrop
19 The access terminal shall consider the timer value to be expired after the time specified
20 by PilotDropTimer. The access terminal shall reset and disable the timer if the strength
21 of the pilot becomes greater than the value specified by PilotDrop.
22 • The access terminal shall sort pilots in each Sub-Active Set in order of increasing
23 strengths, i.e., PS1 < PS 2 < PS 3 < ... < PS N , where NA is the number of the pilots in the
A
24 sub-Active Set. The access terminal shall start the timer whenever the strength PSi
25 satisfies the following inequality:
⎛ SoftSlope DropIntercept PilotDrop ⎞
26 10 × log10PSi < max⎜⎜ ×10 × log10 ∑ PS j + ,- ⎟
⎟
⎝ 8 j> i 2 2 ⎠
i = 1, 2, ..., NA − 1
27 The access terminal shall reset and disable the timer whenever the above inequality
28 is not satisfied for the corresponding pilot.
29 Sections 7.9.6.1.2.8 and 7.9.6.1.2.9 specify the actions the access terminal takes when the
30 pilot drop timer expires.
31 8.9.6.1.2.57.9.6.1.2.5 Sub-Active Sets

32 The sub-Active Set associated with a DRC Cover channel is defined to be the set of pilots in
33 the Active Set to which the access terminal can point using the DRC Cover channel. A
34 DRC Cover Channel is specified in the TrafficChannelAssignment message by the Reverse
35 CDMA Channel on which the DRC Cover is transmitted and the
7-182
1 FeedbackMultiplexingIndex associated with that DRC channel. Each pilot in the Active Set
2 belongs to exactly one sub-Active Set.
3 8.9.6.1.2.67.9.6.1.2.6 Pilot Groups

4 Two pilots are defined to belong to the same Pilot Group if both the PN offset and the
5 PilotGroupID associated with the two pilots are the same72. The PilotGroupID for a pilot is
6 determined as follows:
7 • The PilotGroupID associated with a pilot in the Active Set is specified in the
9 • If public data of the Overhead Messages protocol specifies the PilotGroupID for a pilot
10 that is not included in the most recently received TrafficChannelAssignment message,
11 then that value is the PilotGroupID for that pilot.
12 • If public data of the Overhead Messages protocol does not specify the PilotGroupID for a
13 pilot and there is no PilotGroupID specified for the pilot in the most recently received
14 TrafficChannelAssignment message, then the value of the PilotGroupID for that pilot is
15 assumed to be zero.
16 • The access terminal shall associate a PilotGroupID with each pilot in the Remaining Set
17 that is different from any other PilotGroupID associated with any other pilot.
18 8.9.6.1.2.77.9.6.1.2.7 Scheduler Groups

19 Each pilot in the Active Set belongs to a Scheduler Group73. Two pilots are defined to
20 belong to the same Scheduler Group if either of the following conditions is satisfied:
21 • The SchedulerTagIncluded field of the TrafficChannelAssignment message that
22 assigned the current Active Set is set to ‘1’ and the SchedulerTag associated with the
23 two pilots are the same.
24 • The SchedulerTagIncluded field of the TrafficChannelAssignment message that
25 assigned the current Active Set is set to ‘0’, and the two pilots are in the same sub-
26 Active Set, and the two pilots are in softer handoff with each other (as identified in the
27 TrafficChannelAssignment message).
28 If the TrafficChannelAssignment message does not specify the SchedulerTag for a pilot in
29 the Active Set, then the SchedulerTag associated with that pilot is assumed to be a number
30 that is different from all other SchedulerTag specified in the message.
72 If an additional CDMA channel is added to a sector and has the same coverage as an existing
CDMA channel it can be assigned the same PN offset and PilotGroupID and be part of the same Pilot
Group. If an additional CDMA channel is added to a sector and has different coverage than an
existing CDMA channel then it can be assigned a different PilotGroupID or a different PN offset or
both.
73 For example, pilots in the same Scheduler Group share the same QNSequence space as specified
by the Multi-Link Multi-Flow Packet Application defined in [20].
7-183
1 8.9.6.1.2.87.9.6.1.2.8 Active Set Management

2 The access terminal shall support a maximum Active Set size of NRUPActive pilots per sub-
3 Active Set.
4 Rules for maintaining the Active Set are specific to each protocol state (see 7.9.6.1.5 and
5 7.9.6.1.6).
6 8.9.6.1.2.97.9.6.1.2.9 Candidate Set Management

7 The access terminal shall support a maximum Candidate Set size of NRUPCandidate pilots. The
8 Candidate Set shall not include multiple pilots in the same Pilot Group. When adding a
9 pilot to the Candidate Set from a certain Pilot Group, the access terminal may choose to
10 add any pilot that belongs to the same Pilot Group. Also, the access terminal may replace
11 at any time a pilot in the Candidate Set with another pilot that belongs to the same Pilot
12 Group.
13 The access terminal shall add a pilot to the Candidate Set if one of the following conditions
14 is met:
15 • The pilot does not belong to the same Pilot Group as one of the pilots that is already in
16 the Active Set or Candidate Set and the strength of the pilot exceeds the value specified
17 by PilotAdd.
18 • Pilot is deleted from the Active Set, the Active Set does not include a pilot in the same
19 Pilot Group as the deleted pilot, its pilot drop timer has expired, DynamicThresholds is
20 equal to ‘1’, and the pilot strength is above the threshold specified by PilotDrop, and the
21 ThisSubActiveSetNotReportable field corresponding to the sub-Active Set to which the
22 pilot belonged was not set to ‘1’ in the TrafficChannelAssignment message that assigned
23 the previous Active Set (i.e., prior to deleting this pilot).
24 • Pilot is deleted from the Active Set, the Active Set does not include a pilot in the same
25 Pilot Group as the deleted pilot, and the pilot’s drop timer has not expired, and the
28 the previous Active Set (i.e., prior to deleting this pilot).
29 The access terminal shall delete a pilot from the Candidate Set if one of the following
30 conditions is met:
31 • A pilot in the same Pilot Group is added to the Active Set.
32 • Pilot’s drop timer has expired.
33 • Pilot is added to the Candidate Set; and, as a consequence, the size of the Candidate
34 Set exceeds NRUPCandidate. In this case, the access terminal shall delete the weakest pilot
35 in the set. Pilot A is considered weaker than pilot B:
36 − If pilot A has an active drop timer but pilot B does not,
37 − If both pilots have an active drop timer and pilot A’s drop timer is closer to
38 expiration than pilot B’s, or
7-184
1 − If neither of the pilots has an active drop timer and pilot A’s strength is less
2 than pilot B’s.
3 8.9.6.1.2.107.9.6.1.2.10 Neighbor Set Management

4 The access terminal shall support a minimum Neighbor Set size of NRUPNeighbor pilots. The
5 Neighbor Set shall not include multiple pilots in the same Pilot Group. When adding a pilot
6 to the Neighbor Set from a certain Pilot Group, the access terminal may choose to add any
7 pilot that belongs to the same Pilot Group. Also, the access terminal may replace at any
8 time a pilot in the Neighbor Set with another pilot that belongs to the same Pilot Group.
9 The access terminal shall maintain a counter, AGE, for each pilot in the Neighbor Set as
10 follows.
11
12 • If a pilot is added to the Active Set or Candidate Set, then all the pilots in the Neighbor
13 Set that belong to the same Pilot Group as the pilot added to the Active Set or
14 Candidate Set shall be deleted from the Neighbor Set.
15 • If a pilot in the Neighbor Set is replaced by another pilot belonging to the same Pilot
16 Group, then the same value for the AGE shall be associated with the newly added pilot.
17 • If a pilot is deleted from the Active Set, but a pilot that belongs to the same Pilot Group
18 is not added to the Candidate Set and the Active Set does not include a pilot that
19 belongs to the same Pilot Group as the deleted pilot and the
22 the previous Active Set (i.e., prior to deleting this pilot), then it shall be added to the
23 Neighbor Set with the AGE of 0.
24 • If a pilot is deleted from the Candidate Set, but a pilot that belongs to the same Pilot
25 Group is not added to the Active Set and the Active Set does not include a pilot that
26 belongs to the same Pilot Group as the deleted pilot, then it shall be added to the
27 Neighbor Set with the AGE of 0.
28 • If the size of the Neighbor Set is greater than the maximum Neighbor Set supported by
29 the access terminal, the access terminal shall delete enough pilots from the Neighbor
30 Set such that the size of the Neighbor Set is the maximum size supported by the access
31 terminal and pilots with higher AGE are deleted first.
32 • If the access terminal receives an OverheadMessages.Updated indication, then:
34 Set.
36 Messages Protocol that is a member of the Neighbor Set, the access terminal
7-185
2 Messages Protocol (in the order specified in the neighbor list) that is a member
3 of the Remaining Set, the access terminal shall perform the following:
5 the size of the Neighbor Set to increase beyond the maximum Neighbor Set
6 size supported by the access terminal, then the access terminal shall add this
7 neighbor list pilot to the Neighbor Set with its AGE set to NeighborMaxAge.
22 • If the access terminal receives a NeighborList message, then:
24 Set.
25 − For each pilot in the neighbor list given in the NeighborList message that is a
26 member of the Neighbor Set, the access terminal shall perform the following:
29 − For each pilot in the neighbor list given in the NeighborList message (in the
30 order specified in the message) that is a member of the Remaining Set, the
33 the size of the Neighbor Set to increase beyond the maximum Neighbor Set
34 size supported by the access terminal, then the access terminal shall add this
35 neighbor list pilot to the Neighbor Set with its AGE set to NeighborMaxAge.
7-186
10 + If the addition of this neighbor list pilot would cause the Neighbor Set size to
11 increase beyond the maximum Neighbor Set size supported by the access
12 terminal and the Neighbor Set does not contain a pilot with AGE greater than
13 NeighborMaxAge associated with the pilot’s channel, the access terminal shall
14 not add this neighbor list pilot to the Neighbor Set.
15 The access terminal shall perform the procedures specified in 7.9.6.1.2.1 if a pilot is added
16 to or deleted from the Neighbor Set.
17 8.9.6.1.2.117.9.6.1.2.11 Remaining Set Management

18 The access terminal shall initialize the Remaining Set to contain all the pilots whose PN
20 other set.
21 The access terminal shall add a pilot to the Remaining Set if it deletes the pilot from the
22 Neighbor Set and if a pilot belonging to the same Pilot Group was not added to the Active
23 Set or Candidate Set.
24 The access terminal shall delete the pilot from the Remaining Set if it adds the pilot or
25 another pilot belonging to the same Pilot Group to another set.
26 8.9.6.1.2.127.9.6.1.2.12 Pilot PN Phase Measurement

27 The access terminal shall measure the arrival time, PILOT_ARRIVAL, for each pilot reported
28 to the access network. The pilot arrival time shall be the time of occurrence, as measured
29 at the access terminal antenna connector, of the earliest arriving usable multipath
30 component of the pilot. The arrival time shall be measured relative to the access terminal’s
31 time reference in units of PN chips. The access terminal shall compute the reported pilot
32 PN phase, PILOT_PN_PHASE, as:
33 PILOT_PN_PHASE = (PILOT_ARRIVAL + (64 × PILOT_PN)) mod 215,
34 where PILOT_PN is the PN sequence offset index of the pilot.
35 8.9.6.1.37.9.6.1.3 Message Sequence Numbers

36 The access network shall validate all received RouteUpdate messages as specified in
37 7.9.6.1.3.1.
38 The access terminal shall validate all received TrafficChannelAssignment messages as
39 specified in 7.9.6.1.3.2.
7-187
1 The RouteUpdate message and the TrafficChannelAssignment message carry a

2 MessageSequence field that serves to flag duplicate or stale messages.
3 The MessageSequence field of the RouteUpdate message is independent of the
4 MessageSequence field of the TrafficChannelAssignment message.
5 8.9.6.1.3.17.9.6.1.3.1 RouteUpdate Message Validation

6 When the access terminal first sends a RouteUpdate message, it shall set the
7 MessageSequence field of the message to zero. Subsequently, the access terminal shall
8 increment this field each time it sends a RouteUpdate message.
9 The access network shall consider all RouteUpdate messages it receives in the Idle State as
10 valid.
11 The access network shall initialize the receive pointer, V(R) to the MessageSequence field of
12 the first RouteUpdate message it received in the Idle State, and the access network shall
13 subsequently set it to the MessageSequence field of each received RouteUpdate message.
14 When the access network receives a RouteUpdate message in the Connected State, it shall
15 validate the message using the procedure defined in 13.6. The access network shall discard
16 the message if it is invalid.
17 8.9.6.1.3.27.9.6.1.3.2 TrafficChannelAssignment Message Validation

18 The access network shall set the MessageSequence field of the TrafficChannelAssignment
19 message it sends in the Idle State to zero. Subsequently, each time the access network
20 sends a new TrafficChannelAssignment message in the Connected State, it shall increment
21 this field. If the access network is sending the same message multiple times, it shall not
22 change the value of this field between transmissions.74
24 of the TrafficChannelAssignment message that it receives in the Idle State.
25 When the access terminal receives a TrafficChannelAssignment message in the Connected
26 State, it shall validate the message using the procedure defined in 13.6. The access
27 terminal shall discard the message if it is invalid.
28 8.9.6.1.47.9.6.1.4 Inactive State

30 • The access terminal shall set the Active Set, the Candidate Set, and the Neighbor Set to
31 NULL.
32 • The access terminal shall initialize the Remaining Set to contain all the pilots whose PN
34 other set.
35 • The access terminal shall perform the following in the order specified:
7-188
1 − Remove all Neighbor structures from OverheadMessagesNeighborList.

2 − Remove all Neighbor structures from NeighborListMessageNeighborList.
3 − Perform the procedures specified in 7.9.6.1.2.1.
4 • The access terminal shall set (xL,yL), the longitude and latitude of the sector in whose
5 coverage area the access terminal last sent a RouteUpdate message, to (NULL, NULL).
6 8.9.6.1.57.9.6.1.5 Idle State

7 In this state, RouteUpdate messages from the access terminal are based on the distance
8 between the sector where the access terminal last sent a RouteUpdate message and the
9 sector currently in its active set.
10 The access network sends the TrafficChannelAssignment message to open a connection in
11 this state.
13 • Remove all Neighbor structures from NeighborListMessageNeighborList and perform the

16 The access network shall not initially maintain an Active Set for the access terminal in this
17 state.
18 If the access network receives an Open command, prior to sending a
19 TrafficChannelAssignment message, the access network shall initialize the Active Set to the
20 set of pilots in the TrafficChannelAssignment message that it sends in response to
21 command (see 7.9.6.1.1.3).
22 The access terminal shall initially keep an Active Set of size one when it is in the Idle State.
23 The Active Set pilot shall be the pilot associated with the Control Channel the access
24 terminal is currently monitoring. The access terminal shall return an IdleHO indication
25 when the Active Set changes in the Idle State.
26 The access terminal shall not change its Active Set pilot at a time that causes it to miss a
27 synchronous Control Channel capsule. Other rules governing when to replace this Active
28 Set pilot are beyond the scope of this specification.
29 If the access terminal receives a TrafficChannelAssignment message, it shall set its Active
30 Set to the list of pilots specified in the message if the TrafficChannelAssignment message
31 does not contain an AssignedChannel Record, or if the TrafficChannelAssignment message
32 contains a AssignedChannel Record and the access terminal supports the CDMA Channel
33 specified by the AssignedChannel Record.
34 8.9.6.1.5.27.9.6.1.5.2 Pilot Channel Supervision in the Idle State

35 The access terminal shall perform pilot channel supervision in the Idle State as follows:
7-189
1 • Access terminal shall monitor the pilot strength of the pilot in its active set, all the
2 pilots in the Candidate Set and all the pilots in the neighbor set that are on the same
3 frequency.
4 • If the strength of all the pilots that the access terminal is monitoring goes below the
5 value specified by PilotDrop, the access terminal shall start a pilot supervision timer.
6 The access terminal shall consider the timer to be expired after the time specified by
7 PilotDropTimer.
8 • If the strength of at least one of the pilots goes above the value specified by PilotDrop
9 while the pilot supervision timer is counting down, the access terminal shall reset and
11 • If the pilot supervision timer expires, the access terminal shall return a NetworkLost
12 indication.
13 8.9.6.1.5.37.9.6.1.5.3 Processing the TrafficChannelAssignment Message in the Idle State

14 If the access terminal receives a TrafficChannelAssignment message in this state, it shall,
15 perform the following if the TrafficChannelAssignment message does not contain an
16 AssignedChannel Record, or if the TrafficChannelAssignment message contains an
17 AssignedChannel Record and the access terminal supports the CDMA Channel specified by
18 the AssignedChannel Record:
19 • Update its Active Set as described in 7.9.6.1.2.8
20 • Set the following public data of the Forward Traffic Channel MAC Protocol to the
22 − DRCLength for each of the assigned sub-Active Sets
23 − ACKChannelGain for each of the assigned sub-Aactive Sets
25 − AuxDRCCover (if assigned) for every pilot in the Active Set
29 TrafficChannelAssignment message. Otherwise, set the DRCChannelGain public data of
30 the Forward Traffic Channel MAC protocol to the DRCChannelGainBase field of the
35 • Set the following public data of the Reverse Traffic Channel MAC Protocol to the
38 • Return a ConnectionInitiated Indication,
7-190
1 • If the AssignedChannel Record is included in the message, the access terminal shall
2 tune to the CDMA Channels specified by the CDMA AssignedChannel Records
3 associated with each pilot included in the message.
4 • Issue the following commands:
5 − ReverseTrafficChannelMAC.Activate with a parameter that indicates the reverse
6 CDMA channel(s) that are assigned by the TrafficChannelAssignment message.
7 − ForwardTrafficChannelMAC.Activate
8 − AccessChannelMAC.Deactivate
9 • Transition to the Connected State.

11 The access terminal shall send RouteUpdate messages to update its location with the
12 access network.
13 The access terminal shall not send a RouteUpdate message if the state timer of the
14 Connection Setup State in the Idle State Protocol is active.
15 The access terminal shall comply with the following rules regarding RouteUpdate
16 messages:
17 • The access terminal shall send a RouteUpdate message upon receiving a
18 SendRouteUpdate command.
19 • If the value of the SupportRouteUpdateEnhancements attribute is not 0x00, then the
20 access terminal shall send a RouteUpdate message whenever it receives a
21 RouteUpdateRequest message.
22 • The access terminal shall send a RouteUpdate message with every access channel
23 capsule transmitted by the access terminal.
24 • The access terminal shall include in the RouteUpdate message the pilot PN phase, pilot
25 strength, and drop timer status for exactly one pilot in each Pilot Group in the Active
26 Set and Candidate Set.
27 • The access terminal shall send a RouteUpdate message if all of the following conditions
28 are true:
29 − the RouteUpdateRadiusOverhead field of the SectorParameters message is not
30 set to zero, and
31 − the value of the RouteUpdateRadiusMultiply attribute is not 0x00, and
32 − the computed value r is greater than max ( 0, rm × ro + ra ), where ro is the
33 value provided in the RouteUpdateRadiusOverhead field of the
34 SectorParameters message transmitted by the sector in which the access
35 terminal last sent a RouteUpdate message, rm is the value of the
36 RouteUpdateRadiusMultiply attribute, and ra is the value of the
37 RouteUpdateRadiusAdd attribute.
7-191
1 If (xL,yL) are the longitude and latitude of the sector to which the access terminal last sent a
2 RouteUpdate, and (xC,yC) are the longitude and latitude of the sector currently providing
3 coverage to the access terminal, then r is given by75
⎢ ⎡ ⎤
2 ⎥
⎛ π y ⎞
⎢ ⎢(xC − xL )× cos⎜ ⎟ ⎥ + [ yC − y L ] ⎥
2
× L
⎢ ⎣ ⎝ 180 14400 ⎠⎦ ⎥
4 r=⎢ ⎥
⎢ 16 ⎥
⎢ ⎥
⎣ ⎦
⎢ ⎡ 2 ⎥
⎢ ⎢D longitude × cos⎛⎜ π × y L ⎞⎟⎤⎥ + [y C − y L ]2 ⎥
⎢ ⎣ ⎝ 180 14400 ⎠⎦ ⎥
r=⎢ ⎥
⎢ 16 ⎥
⎢ ⎥
⎣ ⎦
x − xL
5 D longitude = x C − x L if C < 180
14400
xC − xL
D longitude = 360 ×14400 − x C − x L if ≥ 180
14400
6 The access terminal shall compute r with an error of no more than ±5% of its true value
7 when |yL/14400| is less than 60 and with an error of no more than ±7% of its true value
8 when |yL/14400| is between 60 and 70.76
13 8.9.6.1.67.9.6.1.6 Connected State

14 In this state, RouteUpdate messages from the access terminal are based on changes in the
15 radio link between the access terminal and the access network, obtained through pilot
16 strength measurements at the access terminal.
17 The access network determines the contents of the Active Set through
18 TrafficChannelAssignment messages.

20 In the Connected State, the access terminal shall perform the following:
22 terminal shall:
75 The x’s denote longitude and the y’s denote latitude.
76xL and yL are given in units of 1/4 seconds. xL/14400 and yL/14400 are in units of degrees.
7-192
1 − Send a TrafficChannelComplete message with the MessageSequence field of

2 the message set to the MessageSequence field of the TrafficChannelAssignment
3 message,
4 − Return a ConnectionOpened indication.

6 In the Connected State, the access network shall perform the following:
8 network shall return a ConnectionOpened indication.
10 8.9.6.1.6.3.17.9.6.1.6.3.1 Access Network

11 Whenever the access network sends a TrafficChannelAssignment message to the access
12 terminal, it shall add to the Active Set any pilots listed in the message that are not
13 currently in the Active Set.
14 Upon sending a TrafficChannelAssignment message to the access terminal the access
15 network shall issue the following command:
16 • A ReverseTrafficChannelMAC.Activate command including the list of reverse CDMA
17 channels that this TrafficChannelAssignment message has added.
18 Upon receiving the TrafficChannelComplete message, the access network shall perform the
19 following:
20 • A ReverseTrafficChannelMAC.Deactivate command including the list of reverse CDMA
21 channels that the corresponding TrafficChannelAssignment message has removed.
23 following public data of the Forward Traffic Channel MAC Protocol to the corresponding
25 • DRCLength for each of the assigned sub-Active Sets
26 • ACKChannelGain for each of the assigned sub-Active Sets
28 • AuxDRCCover (if assigned) for every pilot in the Active Set
7-193

5 following public data of the Reverse Traffic Channel MAC Protocol to the corresponding
7 • RAChannelGain for every pilot in the Active Set
8 The access network shall delete a pilot from the Active Set if the pilot was not listed in a
9 TrafficChannelAssignment message and if the access network received the
10 TrafficChannelComplete message, acknowledging that TrafficChannelAssignment message.
11 The access network should send a TrafficChannelAssignment message to the access
12 terminal in response to changing radio link conditions, as reported in the access terminal’s
13 RouteUpdate messages.
14 The access network should only specify a pilot in the TrafficChannelAssignment message if
15 it has allocated the required resources in the associated sector.
16 If the SupportedCDMAChannels attribute contains one or more band classes, then the
17 access network shall assign a Traffic Channel on a CDMA Channel supported by the access
18 terminal as indicated by the value of the SupportedCDMAChannels attribute.
19 If the access network adds or deletes a pilot in the Active Set, it shall send an
20 ActiveSetUpdated indication.
21 If the access network adds a pilot that belongs to the same Pilot Group as a pilot specified
22 in a RouteUpdate message to the Active Set, the access network may use the PilotPNPhase
23 field provided in the message to obtain a round trip delay estimate from the access terminal
24 to the sector associated with this pilot. The access network may use this estimate to
25 accelerate the acquisition of the access terminal’s Reverse Traffic Channel in that sector.
26 The access network shall not set DRC Length associated with any sub-Active Set in the
27 TrafficChannelAssignment message to less than 4 slots if the Physical Layer Protocol
28 defines the DTXMode as public data, and it is set to ‘1’.
29 8.9.6.1.6.3.27.9.6.1.6.3.2 Access Terminal

30 If the access terminal receives a valid TrafficChannelAssignment message (see 7.9.6.1.3.2),
31 it shall replace the contents of its current Active Set with the pilots specified in the
32 message. The access terminal shall process the message as defined in 7.9.6.1.6.6.
33 Upon receiving a valid TrafficChannelAssignment message, the access terminal shall issue
34 the following commands:
35 • A ReverseTrafficChannelMAC.Activate command including the list of reverse CDMA
36 channels that this TrafficChannelAssignment message has added.
37 • A ReverseTrafficChannelMAC.Deactivate command including the list of reverse CDMA
38 channels that this TrafficChannelAssignment message has removed.
7-194
1 8.9.6.1.6.47.9.6.1.6.4 ResetReport Message

2 The access network may send a ResetReport message to reset the conditions under which
3 RouteUpdate messages are sent from the access terminal. Access terminal usage of the
4 ResetReport message is specified in the following section.

6 The access terminal sends a RouteUpdate message to the access network in this state to
7 request addition or deletion of pilots from its Active Set.
8 If the access terminal is sending the RouteUpdate message in response to a
10 include in a RouteUpdate message the pilot PN phase, pilot strength, and drop status for
11 pilots whose strength is above the value specified by PilotAdd and subject to the following
12 conditions:
13 • If the RouteUpdateRequest message contains one or more SectorPilotPN fields, the
14 access terminal shall include pilots in the CDMA channel indicated by the Channel
15 record and that are indicated by the SectorPilotPN fields. Otherwise, the access
16 terminal shall include pilots which are in the CDMA channel indicated by the Channel
17 record.
18 If the access terminal is not sending the RouteUpdate message in response to a
20 determine which pilots to include in the RouteUpdate message as follows:
21 If DynamicThresholds is equal to ‘0’, the access terminal shall include in the RouteUpdate
22 message the pilot PN phase, pilot strength, and drop timer status for exactly one pilot in
23 each Pilot Group in the Active Set and Candidate Set. If DynamicThresholds is equal to ‘1’,
24 then the access terminal shall include in the RouteUpdate message the pilot PN phase,
25 pilot strength, and drop timer status for exactly one pilot in each Pilot Group in the Active
26 Set, for each pilot in the Candidate Set whose strength is above the values specified by
27 PilotAdd, and for each pilot in the Candidate set whose strength, PS, satisfies the following
28 inequality for any sub-Active Set currently in the Active Set:
SoftSlope AddIntercept ,
29 10 × log10PS > ×10 × log10 ∑ PSi +
8 i∈A 2
30 where the summation is performed over all pilots belonging to the sub-Active Set.
31 The access terminal shall send a RouteUpdate message if any one of the following occurs:
32 • The value of the SupportRouteUpdateEnhancements attribute is not 0x00 and the
33 access terminal receives a RouteUpdateRequest message.
34 • The Multicarrier Route Update Protocol receives a SendRouteUpdate command.
36 Set pilot is greater than the value specified by PilotAdd.
38 Set pilot, PS, satisfies the following inequality for any sub-Active Set currently in the
39 Active Set:
7-195
⎛ SoftSlope AddInterce pt PilotAdd ⎞

1 10 × log10 PS > max ⎜ ×10 × log10 ∑ PSi + ,- ⎟
⎝ 8 i∈A 2 2 ⎠
2 where the summation is performed over all pilots belonging to the sub-Active Set.
3 • If DynamicThresholds is equal to ‘0’ and the strength of a Candidate Set pilot is greater
4 than the value specified by PilotCompare above an Active Set pilot, and a RouteUpdate
5 message carrying this information has not been sent since the last ResetReport
7 • If DynamicThresholds is equal to ‘0’ and the strength of a Candidate Set pilot is above
8 PilotAdd, and a RouteUpdate message carrying this information has not been sent since
9 the last ResetReport message was received.
11 − the strength of a Candidate Set pilot, PS, satisfies the following inequality for
12 any sub-Active Set currently in the Active Set:
SoftSlope AddIntercept
13 10 × log 10 PS > ×10 × log 10 ∑ PS i +
8 i∈A 2
14 where the summation is performed over all pilots belonging to the sub-Active
15 Set, and
19 − the strength of a Candidate Set pilot is greater than the value specified by
20 PilotCompare above an Active Set pilot, and
21 − the strength of a Candidate Set pilot, PS, satisfies the following inequality for
22 any sub-Active Set currently in the Active Set::
SoftSlope AddInterce pt
23 10 × log10PS > ×10 × log10 ∑ PSi +
8 i∈A 2
24 where the summation is performed over all pilots belonging to the sub-Active
25 Set, and
28 • The pilot drop timer of an Active Set pilot has expired, and a RouteUpdate message
29 carrying this information has not been sent since the last ResetReport message was
30 received.
7-196
1 8.9.6.1.6.67.9.6.1.6.6 Processing the TrafficChannelAssignment Message in the Connected

2 State
3 If a valid TrafficChannelAssignment (see 7.9.6.1.3.2) message does not contain an
4 AssignedChannel Record, or if a valid TrafficChannelAssignment message contains an
5 AssignedChannel Record and the access terminal supports the CDMA Channel specified by
6 the Channel Record, then the access terminal shall process the message as follows:
7 • The access terminal shall set the following public data of the Forward Traffic Channel
9 − DRCLength for each of the assigned sub-Active Sets
10 − ACKChannelGain for each of the assigned sub-Active Sets
12 − AuxDRCCover (if assigned) for every pilot in the Active Set
22 • The access terminal shall set the following public data of the Reverse Traffic Channel
25 • If the TrafficChannelAssignment message contains a value for the FrameOffset that is
26 different from the value of the FrameOffset received in the last
27 TrafficChannelAssignment message that was received in the Idle state, then the access
28 terminal shall return a RouteUpdate.AssignmentRejected indication and shall discard
29 the message.
30 • The access terminal shall update its Active Set as defined in 7.9.6.1.6.3.2.
31 • The access terminal shall issue the following command:
32 − ReverseTrafficChannelMAC.Activate with a parameter that indicates the reverse
33 CDMA channel(s) that are assigned by the TrafficChannelAssignment message.
34 • The access terminal shall tune to the CDMA channels specified in the
35 TrafficChannelAssignment messages associated with each pilot.
7-197
1 • For each reverse link CDMA channel, the access terminal shall start monitoring and
2 responding to the Power Control Channels sent from the forward link CDMA channel
3 associated with that reverse link CDMA channel as specified in the
4 TrafficChannelAssignment message and defined by the ReverseLinkMACIndex fields
5 provided in the message. The access terminal should use the SofterHandoff fields to
6 identify the Power Control Channels that are carrying identical information and can,
7 therefore, be soft-combined.
8 • The access terminal shall send the access network a TrafficChannelComplete message
9 specifying the MessageSequence value received in the TrafficChannelAssignment
10 message.
11 8.9.6.1.6.77.9.6.1.6.7 Processing the TrafficChannelComplete Message

12 The access network should set a transaction timer when it sends a
13 TrafficChannelAssignment message. If the access network sets a transaction timer, it shall
14 reset the timer when it receives a TrafficChannelComplete message containing a
15 MessageSequence field equal to the one sent in the TrafficChannelAssignment message.
16 If the timer expires, the access network should return a ConnectionLost indication.
17 8.9.6.1.6.87.9.6.1.6.8 Transmission and Processing of the NeighborList Message

18 The access network may send the NeighborList message to the access terminal when the
19 protocol is in the Connected State to override the search window size and/or search
20 window offset corresponding to a pilot in the Neighbor Set.
21 Upon receiving a NeighborList message, the access terminal shall perform the following in
23 • The access terminal shall remove all Neighbor structures from
24 NeighborListMessageNeighborList.
25 • For each pilot listed in the received NeighborList message, the access terminal shall add
26 a Neighbor structure to NeighborListMessageNeighborList and populate it as follows:
27 − Set the structure’s PilotPN field to the message’s corresponding PilotPN field.
28 − If the message’s ChannelIncluded field is set to ‘1’, set the structure’s Channel
29 field to the message’s corresponding Channel field. Otherwise, set the
30 structure’s Channel field to the current channel.
31 − If the message’s SearchWindowSizeIncluded field is set to ‘1’, then set the
32 structure’s SearchWindowSize field to the message’s corresponding
33 SearchWindowSize field. Otherwise, set the structure’s SearchWindowSize field
34 to NULL.
35 − If the SearchWindowOffsetIncluded field is set to ‘1’, then set the structure’s
36 SearchWindowOffset field to the message’s corresponding SearchWindowOffset
37 field. Otherwise, set the structure’s SearchWindowOffset field to NULL.
38 • Perform the procedures specified in 7.9.6.1.2.1.
7-198
1 8.9.6.1.6.97.9.6.1.6.9 Processing of OverheadMessages.Updated Indication

2 Upon receiving OverheadMessages.Updated indication, the access terminal shall perform
3 the OverheadMessagesNeighborList Initialization procedures as specified in 7.9.6.1.6.10
4 and then perform the procedures specified in 7.9.6.1.2.1.
5 8.9.6.1.6.107.9.6.1.6.10 OverheadMessagesNeighborList Initialization

6 When the OverheadMessagesNeighborList initialization procedures are invoked by the
7 access terminal, it shall perform the following:
8 • The access terminal shall remove all Neighbor structures from the
9 OverheadMessagesNeighborList list.
10 • For each pilot in the neighbor list given as public data of Overhead Messages Protocol,
11 the access terminal shall add a Neighbor structure to the
12 OverheadMessagesNeighborList list and populate it as follows:
13 − Set the structure’s PilotPN field to the corresponding NeighborPilotPN field
14 given as public data of the Overhead Messages Protocol.
15 − If the Overhead Messages Protocol’s NeighborChannelIncluded field is set to
16 ‘1’, set the structure’s Channel field to the Overhead Messages Protocol’s
17 corresponding NeighborChannel. Otherwise, set the structure’s Channel field
18 to the current channel.
19 − If the Overhead Messages Protocol’s SearchWindowSizeIncluded field is set to
20 ‘1’, then set the structure’s SearchWindowSize field to the Overhead Messages
21 Protocol’s corresponding SearchWindowSize field. Otherwise, set the
22 structure’s SearchWindowSize field to NULL.
23 − If the Overhead Messages Protocol’s SearchWindowOffsetIncluded field is set to
24 ‘1’, then set the structure’s SearchWindowOffset field to the Overhead
25 Messages Protocol’s corresponding SearchWindowOffset field. Otherwise, set
26 the structure’s SearchWindowOffset field to NULL.
28 8.9.6.2.17.9.6.2.1 RouteUpdate
29 The access terminal sends the RouteUpdate message to notify the access network of its
30 current location and provide it with an estimate of its surrounding radio link conditions.
31
7-199
Field Length (bits)

MessageID 8
MessageSequence 8
ReferencePilotPN 9
ReferencePilotStrength 6
ReferenceKeep 1
NumPilots 4
NumPilots occurrences of the following fields:
{
PilotPNPhase 15
ChannelIncluded 1
Channel 0 or 24
PilotStrength 6
Keep 1
}
ATTotalPilotTransmissionIncluded 0 or 1
ATTotalPilotTransmission 0 or 8
ReferencePilotChannelIncluded 0 or 1
ReferencePilotChannel 0 or 24
Reserved Variable
2 MessageSequence The access terminal shall set this field to the sequence number of
3 this message. The sequence number of this message is 1 more than
8
4 the sequence number of the last RouteUpdate message (modulo 2 )
5 sent by this access terminal. If this is the first RouteUpdate message
6 sent by the access terminal, it shall set this field to 0x00.
7 ReferencePilotPN The access terminal shall set this field to the access terminal’s time
8 reference (the reference pilot), relative to the zero offset pilot PN
9 sequence in units of 64 PN chips.
10 ReferencePilotStrength
11 The access terminal shall set this field to ⎣− 2 × 10 × log10PS ⎦, where
12 PS is the strength of the reference pilot, measured as specified in
13 7.9.6.1.2.3. If this value is less than 0, the access terminal shall set
7-200
1 this field to ‘000000’. If this value is greater than ‘111111’, the access
3 ReferenceKeep If the pilot drop timer corresponding to the reference pilot has
4 expired, the access terminal shall set this field to ‘0’; otherwise, the
6 NumPilots The access terminal shall set this field to the number of pilots that
7 follow this field in the message.
8 PilotPNPhase The PN offset in resolution of 1 chip of a pilot in the Active Set or

9 Candidate Set of the access terminal that is not the reference pilot.
10 ChannelIncluded The access terminal shall set this field to ‘1’ if the following Channel
11 record is included in this message. Otherwise, the access terminal
12 shall set this field to ‘0’ to indicate that the channel associated with
13 this pilot is the FDD-paired forward CDMA channel associated with
14 the reverse CDMA channel on which this message is being sent.
15 Channel The access terminal shall include this field if the ChannelIncluded
16 field is set to ‘1’. The access terminal shall set this to the channel
18 terminal shall omit this field for this pilot offset.
19 PilotStrength The access terminal shall set this field to ⎣− 2 × 10 × log10PS ⎦, where
20 PS is the strength of the pilot in the above field, measured as
21 specified in 7.9.6.1.2.3. If this value is less than 0, the access
22 terminal shall set this field to ‘000000’. If this value is greater than
23 ‘111111’, the access terminal shall set this field to ‘111111’.
24 Keep If the pilot drop timer corresponding to the pilot in the above field
25 has expired, the access terminal shall set this field to ‘0’; otherwise,
27 ATTotalPilotTransmissionIncluded
28 If this message is sent on the access channel, the access terminal
29 shall omit this field. Otherwise, the access terminal shall include
30 this field and set it to ‘1’.The access terminal shall set this field to ‘0’
31 if this message is sent on the access channel. Otherwise, the access
33 ATTotalPilotTransmission
34 The access terminal shall include this field only if the
35 ATTotalPilotTransmissionIncluded is included and is set to ‘1’. If
36 included, the access terminal shall set this field to the current total
37 average transmission power of pilot(s) when the transmitter is
7-201
1 enabled in units of 0.5 dBm. This field is expressed as a two’s

2 complement signed number.
3 ReferencePilotChannelIncluded
4 The access terminal shall not include this field when the message is
5 sent on the access channel. When this message is being sent on the
6 reverse traffic channel the access terminal shall include this field and
8 The access terminal shall set this field as follows: If the
9 ReferencePilotChannel is the FDD-paired forward CDMA channel
10 associated with the reverse CDMA channel on which this message is
11 being sent, the access terminal shall include and set this field to ‘0’;
12 otherwise the access terminal shall include and set this field to ‘1’.
13 ReferencePilotChannel
14 The access terminal shall include this field only if
15 ReferencePilotChannelIncluded is included and set to ‘1’. If included,
16 the access terminal shall set this to the channel record
17 corresponding to the reference pilot (see 13.1).
21
22 8.9.6.2.27.9.6.2.2 TrafficChannelAssignment
23 The access network sends the TrafficChannelAssignment message to manage the access
24 terminal’s Active Set.
25
7-202
Field Length (bits)

MessageID 8
MessageSequence 8
FrameOffset 4
NumSectors 5
NumSubActiveSets 4
AssignedChannelIncluded 1
SchedulerTagIncluded 1
FeedbackMultiplexingEnabled 1
NumSectors occurrences of the following SectorInformation record:
{0
RAChannelGain 2
PilotPN 9
DRCCover 3
SofterHandoff 1
}0
N occurrences of the following field, where N is the number of SofterHandoff fields set to ‘0’
in this message
DSC 3
NumSubActiveSets occurrences of the following SubActiveSetParameters record (starting
from NumFwdChannelsThisSubActiveSet and ending at RABMACIndex, inclusive):
{0
NumFwdChannelsThisSubActiveSet 0 or 4
NumFwdChannelsThisSubActiveSet occurrences of the following field:
{1
AssignedChannel 0 or 24
}1
FeedbackEnabled 1
FeedbackMultiplexingIndex 0 or 9
FeedbackReverseChannelIndex 0 or 4
SubActiveSetCarriesControlChannel 1
ThisSubActiveSetNotReportable 1
DSCForThisSubActiveSetEnabled 0 or 1
Next3FieldsSameAsBefore 0 or 1
7-203
DRCLength 0 or 2
DRCChannelGainBase 0 or 6
ACKChannelGain 0 or 6
NumReverseChannelsIncluded 1
NumReverseChannels 0 or 4
NumReverseChannels occurrences of the following record:
{1
ReverseChannelConfiguration 0 or 2
ReverseBandClass 0 or 5
ReverseChannelNumber 0 or 11
ReverseChannelDroppingRank 0 or 3
}1
NumSectors occurrences of the following record:
{1
PilotInThisSectorIncluded 1
ForwardChannelIndexThisPilot 0 or 4
PilotGroupID 0 or 3
NumUniqueForwardTrafficMACIndices 0 or 3
SchedulerTag 0 or 7
AuxDRCCoverIncluded 0 or 1
AuxDRCCover 0 or 3
ForwardTrafficMACIndexPerInterlaceEnabled 0 or 1
NumUniqueForwardTrafficMACIndices (if included) or zero occurrences of the following
record:
{2
ForwardTrafficMACIndex 0 or 10
AssignedInterlaces 0 or 4
}2
{2
ReverseLinkMACIndex 0 or 9
RABMACIndex 0 or 7
DeltaT2P 0 or 6
}2
7-204
}1
}0
Reserved Variable
1
4 MessageSequence field of the last TrafficChannelAssignment message
5 (modulo 2S, S=8) sent to this access terminal.
7 The access network shall set this field to the power of the DSC
8 channel relative to the pilot channel in units of –0.5 dB, in the range
9 from zero to –15.5 dB, inclusive.
10 FrameOffset The access network shall set this field to the frame offset the access
11 terminal is to use when transmitting the Reverse Traffic Channel, in
12 units of slots.
13 NumSectors The access network shall set this field to the number of
14 SectorInformationRecords included in this message.
15 NumSubActiveSets The access network shall set this field to the number of sub-
16 ActiveSetsub-Active Set assigned to the access terminal.
17 AssignedChannelIncluded
18 The access network shall set this field to ‘1’ if an AssignedChannel
19 field is included in this message.
20 SchedulerTagIncluded
21 The access network shall set this field to ‘1’ if the SchedulerTag field
22 is included in this message.
23 FeedbackMultiplexingEnabled
24 The access network shall set this field to ‘1’ if there is at least one
25 reverse link CDMA channel that carries DRC/DSC/ACK for more
26 than one sub-Active Sets. Otherwise, the access network shall set
27 this field to ‘0’.
28 RAChannelGain The access network shall set this field to the RA Channel Gain for
29 this pilot. The encoding of this field is as specified in Table 7.9.6.2-1.
7-205
1 Table 7.9.6.2-1. Reverse Activity Channel Encoding
Field RA Channel Gain

value
(dB)
(binary)
‘00’ −6
‘01’ −9
‘10’ −12
‘11’ −15
2 PilotPN The access network shall set this field to the PN Offset associated
3 with this sector.
4 DRCCover The access network shall set this field to the index of the DRC cover
6 SofterHandoff If the Forward Traffic Channel associated with this sector will carry
7 the same closed-loop power control bits as that of the previous sector
8 in this message, the access network shall set this field to ‘1’;
9 otherwise, the access network shall set this field to ‘0’. The access
10 network shall set the first instance of this field to ‘0’. If the
11 SofterHandoff field associated with a sector is equal to ‘1’, then the
12 sector is defined to belong to the same cell as the previous sector in
13 this record.
14 DSC The access network shall set this field as follows: The access network
15 shall set the ith occurrence of this field to the DSC associated with the
16 ith cell specified by the SofterHandoff field in this message.
17 NumSubActiveSets occurrences of the following SubActiveSetParameters record (starting
18 from NumFwdChannelsThisSubActiveSet and ending at RABMACIndex, inclusive) are
19 included in this message. The fields in the SubActiveSetParameters record are associated
20 with a single sub-Active Set. The first instance of the sub-Active Set specified below is
21 referred to as the PilotReference sub-Active Set78.
22 NumFwdChannelsThisSubActiveSet
24 AssignedChannelIncluded is set to ‘0’. If included, the access
25 network shall set this field to the number of forward link CDMA
26 channels associated with this sub-Active Set. The valid range for this
27 field is from 1 to 7, inclusive. All other values are reserved. If not
28 included, then the value of this field is assumed to be one.
78 The Reference Sub-Active Set is to be used by the Reverse Traffic Channel MAC protocol.
7-206
1 AssignedChannel The access network shall omit this field if the

2 AssignedChannelIncluded is set to ‘0’. If this field is omitted, then
3 the channel that carries this message is the channel that the access
4 network is assigning to the access terminal. If included, the access
5 network shall set this record to the channel record that specifies
6 each of the forward link CDMA channels in this sub-Active Set. The
7 access network shall set the SystemType field of the Channel record
8 to 0x00 or 0x02 (see 13.1). The multiplexing rules associated with
9 transmission of the DRC, DSC, and ACK channels corresponding to
10 this sub-Active Set is specified by the following field.
11 FeedbackEnabled The access network shall set this field to ‘0’ to indicate that the
12 access terminal is not to send DRC/DSC/ACK channels associated
13 with this sub-Active Set. Otherwise, the access network shall set this
15 FeedbackMultiplexingIndex
16 The access network shall include this field only if the the
17 FeedbackEnabled is set to ‘1’ and FeedbackMultiplexingEnabled field
18 is set to ‘1’. If included, the access network shall set this field to
19 specify how the MAC channels (DRC, DSC, and ACK) in support of
20 the forward link channel specified by the Channel record above are to
21 be multiplexed on the same reverse CDMA channel for this sub-
22 Active Set. The Physical Layer Protocol specifies multiplexing rules
23 based on the value of this field. If not included, the value of this field
24 is assumed to be zero.
25 FeedbackReverseChannelIndex
26 The access network shall include this field only if the
27 FeedbackEnabled field is set to ‘1’. If included, the access network
28 shall set this field to indicate the reverse link CDMA channel on
29 which the DSC (if applicable), DRC, and ACK channels are sent
30 associated with the sub-Active Set. A value of ‘n’ for this field refers
31 to the nth reverse link CDMA channel in the ascending order of
32 frequency that is assigned to the access terminal in this message.
33 SubActiveSetCarriesControlChannel
34 The access network shall set this field to ‘1’ if pilots in this Sub-
35 Active Set carry Control Channel. Otherwise the access network shall
36 set this field to ‘0’.The access network shall include this field only if
37 the FeedbackEnabled field is set to ‘1’. If included, the access
38 network shall set this field to ‘1’ to indicate that the access terminal
39 shall transmit a DSC channel for this sub-Active Set. The DSC
40 channel is to be transmitted on the same reverse link CDMA channel
41 that carries the DRC and ACK for this sub-Active Set.
7-207
1 ThisSubActiveSetNotReportable
2 The access network shall set this field to ‘1’ if the access terminal is
3 not to report pilots in this sub-Active Set.
4 DSCForThisSubActiveSetEnabled
7 shall set this field to ‘1’ to indicate that the access terminal shall
8 transmit a DSC channel for this Sub-Active Set. The DSC channel is
9 to be transmitted on the same reverse link CDMA channel that
10 carries the DRC and ACK for this Sub-Active Set.
11 Next3FieldsSameAsBefore
14 shall set this field to ‘1’ if the value of the next three fields for this
15 sub-Active Set is the same as the value of these three fields
16 associated with the previous sub-Active Set in this message.
17 Otherwise, the access network shall set this field to ‘0’. The access
18 network shall set the value of the first instance of this field in this
19 message to ‘0’.
20 DRCLength The access network shall include this field only if the
21 Next3FieldsSameAsBefore field is included and is set to ‘0’. If
22 included, the access network shall set this field to the number of
23 slots the access terminal shall use to transmit a single DRC value, as
24 shown in Table 7.9.6.2-2.
25 Table 7.9.6.2-2. DRCLength Encoding
Field DRCLength
value (slots)
(binary)
‘00’ 1
‘01’ 2
‘10’ 4
‘11’ 8
29 included, the access network shall set this field to the ratio of the
30 power level of the DRC Channel (when it is transmitted) to the power
31 level of the Reverse Traffic Pilot Channel expressed as 2's
32 complement value in units of 0.5 dB. The valid range for this field is
7-208
1 from –9 dB to +6 dB, inclusive. The access terminal shall support all

2 the values in the valid range for this field.
3 ACKChannelGain The access network shall include this field only if the
5 included, the access network shall set this field to the ratio of the
6 power level of the ACK Channel (when it is transmitted) to the power
7 level of the Reverse Traffic Pilot Channel expressed as 2's
8 complement value in units of 0.5 dB. The valid range for this field is
9 from –3 dB to +6 dB, inclusive. The access terminal shall support all
10 the values in valid range for this field.
11 NumReverseChannelsIncluded
12 The access network shall set this field to ‘1’ if the next field is
13 included in this message. Otherwise, the access network shall set
14 this field to ‘0’. If the configured value of the
15 ForwardFeedbackMultiplexingSupported attribute is 0x00, then the
16 access network shall set this field to ‘0’. If this field is set to '0' and
17 ReverseChanelConfigurationReverseChannelConfiguration for this
18 sub-active set is set to '00', then the value of the number of reverse
19 CDMA channels associated with this sub-active set is zero. If this
20 field is set to '0' and ReverseChanelConfiguration for this sub-active
21 set is set to '01' or '10', then number of reverse CDMA channels
22 associated with this sub-active set is one.
23 NumReverseChannels
24 If NumReverseChannelsIncluded is set to ‘0’, then the access network
25 shall omit this field. Otherwise, the access network shall include this
26 field and shall set this field to the number of reverse CDMA channels
27 associated with this sub-Active Set. If this field is omitted, the
28 number of occurrences of the following record is zero. If this field is
29 not included explicitly in the message then the value of this field
30 shall be assumed to be one.
31 ReverseChannelConfiguration
32 The access network shall set this field according to the table below to
33 specify the configuration of the CDMA reverse channel associated
34 with this sub-Active Set. If NumFwdChannelsThisSubActiveSet
35 associated with this sub-Active set is included and set to more than
36 one, the access network shall not set this field to ‘01’.
7-209
1 Table 7.9.6.1.6.10-3. ReverseChannelConfiguration Encoding
Value Meaning
‘00’ There is no reverse link CDMA channel associated with the
sub-Active Set.
‘01’ The paired CDMA reverse link channel associated with this
sub-Active Set is enabled. The power control bits, RAB, DRC
Lock, and ARQ channel associated with the paired reverse
link CDMA channel are sent on the pilots in this sub-Active
Set.
‘10’ The reverse link CDMA channel associated with this sub-
Active Set is specified using the ReverseBandclass and
ReverseChannelNumber fields. The power control bits, RAB,
DRC Lock, and ARQ channel associated with the reverse link
CDMA channel specified by the ReverseBandclass and
ReverseChannelNumber fields is carried by the pilots in this
sub-Active Set.
‘11’ Reserved
2 ReverseBandClass The access network shall include this field only if the
3 ReverseChannelConfiguration field is included and is set to ‘10’. The
4 access network shall set this field to the band class number for the
5 reverse CDMA channel associated with this sub-Active Set.
6 ReverseChannelNumber
8 ReverseChannelConfiguration field is included and is set to ‘10’. The
9 access network shall set this field to the channel number that
10 identifies the reverse CDMA channel associated with this sub-Active
11 Set.
12 ReverseChannelDroppingRank
14 ReverseChannelConfiguration field is included and is set to ‘00’. If
15 included this field shall be set to the rank that specifies the order in
16 which the access terminal is to drop the reverse CDMA channels if it
17 decides to do so (e.g., due to power-headroom limitation). A reverse
18 CDMA channel with a lower value of this field is to be dropped before
19 a reverse CDMA channel with a higher value for this field.
20 The nth occurrence of the following record corresponds to the nth occurrence of the
21 SectorInformation record above.
22 PilotInThisSectorIncluded
23 The access network shall set the nth occurrence of this field to ‘1’, if
24 the Active Set is to include a pilot in this sector (specified by the nth
7-210
1 occurrence of the SectorInformation record) associated with the sub-

2 Active SetspecifiedSet Specified by this SubActiveSetParameter
3 record. Otherwise, the access network shall set this field to ‘0’.
4 ForwardChannelIndexThisPilot
5 The access network shall only include this field if the
6 PilotInThisSectorIncluded field is set to ‘1’. If included, the access
7 network shall set this field to indicate the forward CDMA channel
8 associated with this pilot. A value of ‘n’ for this field refers to the nth
9 forward CDMA channel in the ascending order of frequency in this
10 sub-Active Set.
11 PilotGroupID The access network shall only include this field if the
12 SectorInThisFrequencyIncludedPilotInThisSectorIncluded field is set
13 to ‘1’. If included, the access network shall set this field to the Pilot
14 Group ID associated with this member of the active set.
15 NumUniqueForwardTrafficMACIndices
17 PilotInThisSectorIncluded field is set to ‘1’ and if the
19 shall set this field to the number of unique ForwardTrafficMACIndex
20 fields that are assigned to the access terminal. A value greater than
21 one indicates that the ForwardTrafficMACIndex assignment is made
22 per interlace.
23 SchedulerTag The access network shall only include this field if the
24 NumUniqueForwardTrafficMACIndices field is included and is set to
25 a value other than zero, and the SchedulerTagIncluded field is set to
26 ‘1’. If included, the access network shall set this field to a number
27 that indicate the Scheduler Group to which this pilot belongs.
28 AuxDRCCoverIncluded
31 a value other than zero. If included, the access network shall set this
32 field to ‘1’ if the following AuxDRCCover field is included.
33 AuxDRCCover The access network shall include this field only if the
34 AuxDRCCoverIncluded field is included and is set to ‘1’. If included,
35 the access network shall set this field to the auxiliary DRC Cover
37 ForwardTrafficMACIndexPerInterlaceEnabled
40 one. If included, the access network shall set this field to indicate
7-211
1 whether the ForwardTrafficMACIndex assignment is made per

2 interlace or not for this member of the Active Set. A ‘1’ indicates that
3 the ForwardTrafficMACIndex assignment is performed per interlace.
4 A ‘0’ indicates that the ForwardTrafficMACIndex assignment is valid
5 for all interlaces for this member of the Active Set.
6 ForwardTrafficMACIndex
8 ForwardTrafficMACIndexPerInterlaceEnabled is included and is set to
9 ‘1’ and if NumUniqueForwardTrafficMACIndices is set to a value
10 greater than one. If included, the access network shall set this field
11 to the Forward Traffic Channel MAC Index assigned to the access
12 terminal corresponding to this pilot on the interlace(s) specified by
13 AssignedInterlaces. If the
15 ‘0’, then the access network shall set this field to the Forward Traffic
16 Channel MAC Index assigned to the access terminal on all of the
17 forward link interlaces. This MAC Index identifies packets that are
18 destined for this access terminal.
20 If the ForwardTrafficMACIndexPerInterlaceEnabled is included and
21 set to one or if NumUniqueForwardTrafficMACIndices is included and
22 set to a value greater than one, then the access network shall set this
23 field to the MAC Index assigned to the access terminal corresponding
24 to this pilot on the interlace(s) specified by AssignedInterlaces.
25
26 If ForwardTrafficMACIndexPerInterlaceEnabled is included and set to

27 zero, then the access network shall set this field to the MAC Index
28 assigned to the access terminal corresponding to this pilot on all of
29 the forward link interlaces.
30
31 If the NumUniqueForwardTrafficMACIndices is not included or is

32 included and set to ‘0’, then there are no Traffic MAC indexMAC
33 Indices assigned to the access terminal for this pilot and the access
34 network shall omit this field.
35 This MAC Index identifies packets that are destined for this access
36 terminal.
37 AssignedInterlaces The access network shall include this field only if

39 ‘1’, or if NumUniqueForwardTrafficMACIndices is set to a value
40 greater than one. If included, the access network shall set this field
41 to indicate interlaces associated with the assigned
42 ForwardTrafficMACIndex field below. A ‘1’ in the k position of this
th
7-212
1 bitmap field indicates that the corresponding

2 ForwardTrafficMACIndex (specified in the next field) is valid on the
3 interlace k-1. A ‘0’ in the kth position of this bitmap field indicates
4 that the access terminal will not be served in the interlace k-1 with
5 the ForwardTrafficMACIndex specified in the following field. The 1st
6 position refers to the LSB of this field and the 4th position refers to
7 the MSB of this field. The access network shall set this field so that
8 at most one ForwardTrafficMACIndex is valid on each interlace.
9 ReverseLinkMACIndex If the PilotInThisSectorIncluded field is set to ‘0’ or if

10 ReverseChannelConfiguration is set to ‘00’, the access network shall
11 omit this field. Otherwise, the nth occurrence of this field shall
12 indicate the MAC Index that is used to send the power control
13 commands for nth reverse CDMA channel from this sector of this sub-
14 Active Set.
15 RABMACIndex If the PilotInThisSectorIncluded field is set to ‘0’ or if the preceding

18 indicate the MAC Index that is used to send the RAB commands for
19 nth reverse CDMA channel from this sector of this sub-Active Set.
20 DeltaT2P If the PilotInThisSectorIncluded field is set to ‘0’ or if the preceding

23 indicate the sector TxT2P offset value for the nth Reverse CDMA
24 Channel from this sector of this sub-Active Set. This field is specified
25 as a signed 6-bit value in the range of -8.0 to 7.75 dB in units of 0.25
26 dB. The access terminal shall support all valid values of this field.
30
Channels CC FTC SLP Reliable Best Effort79
31 8.9.6.2.37.9.6.2.3 TrafficChannelComplete
32 The access terminal sends the TrafficChannelComplete message to provide an
33 acknowledgment for the TrafficChannelAssignment message.
79 The TrafficChannelAssignment message snt in response to the Open command is sent

using best effort SLP. All subsequent TrafficChannelAssignment messages are sent using
reliable delivery SLP.
7-213
Field Length (bits)

MessageID 8
MessageSequence 8
4 of the TrafficChannelAssignment message whose receipt this message
5 is acknowledging.
6
7 8.9.6.2.47.9.6.2.4 ResetReport
8 The access network sends the ResetReport message to reset the RouteUpdate transmission
9 rules at the access terminal.
10
Field Length (bits)

MessageID 8

12
13 8.9.6.2.57.9.6.2.5 NeighborList
14 The NeighborList message is used to convey information corresponding to the neighboring
15 sectors to the access terminals when the access terminal is in the Connected State.
16
7-214
Field Length (bits)
MessageID 8
Count 5
Count occurrences of the following field:
PilotPN 9
Count occurrences of the following two fields:

ChannelIncluded 1
Channel 0 or 24
SearchWindowSizeIncluded 1
SearchWindowSize 0 or 4
SearchWindowOffsetIncluded 1
SearchWindowOffset 0 or 3
m, 0 ≤ m ≤ Count, occurrences of the following field:
Count - m occurrences of the following two fields:
PilotGroupIDIncluded 1
PilotGroupID 0 or 3
Reserved Variable
2 Count The access network shall set this field to the number of records
4 PilotPN The access network shall set this field to the PN Offset of a
5 neighboring sector for which the access network is providing search
6 window information in this message.
7 ChannelIncluded The access network shall set this field to ‘1’ if a Channel record is
8 included for this neighbor, and to ‘0’ otherwise. The access network
7-215
1 may set this field to ‘0’ if the channel associated with this pilot is the
2 same as the channel that is used to carry this message. If this field
3 is set to ‘0’, the access terminal shall assume that the channel
4 associated with this pilot is the same as the channel on which this
5 message is received. The nth occurrence of this field corresponds to
6 the nth occurrence of PilotPN in the record that contains the PilotPN
7 field above.
8 Channel Channel record specification for the neighbor pilot. See 13.1 for the
9 Channel record format. The nth occurrence of this field corresponds
10 to the nth occurrence of PilotPN in the record that contains the
11 PilotPN field above.
12 SearchWindowSizeIncluded
13 The access network shall set this field to ‘1’ if SearchWindowSize field
14 for neighboring sectors is included in this message. Otherwise, the
16 SearchWindowSize The access network shall omit this field if SearchWindowSizeIncluded

17 is set to ‘0’. If SearchWindowSizeIncluded is set to ‘1’, the access
7-216
Search Window
SearchWindowSize
Size
Value
(PN chips)
0 4
1 6
2 8
3 10
4 14
5 20
6 28
7 40
8 60
9 80
10 100
11 130
12 160
13 226
14 320
15 452
2 SearchWindowOffsetIncluded
3 The access network shall set this field to ‘1’ if SearchWindowOffset
4 field for neighboring sectors is included in this message. Otherwise,
6 SeachWindowOffsetSearchWindowOffset
8 SearchWindowOffsetIncluded is set to ‘0’. If
9 SearchWindowOffsetIncluded is set to ‘1’, the access network shall
11 the search window offset to be used by the access terminal for the
12 neighbor pilot. The nth occurrence of this field corresponds to the nth
14 above.
7-217
0 0
1 WindowSize80 /2
2 WindowSize
4 - WindowSize /2
5 - WindowSize
7 Reserved
4 follows:
7 to ‘1’.

9 to ‘0’, the access network shall omit all occurrences of this field.
11 field, where m is the number of Channel records in this message that
12 have SystemType equal to 0x01, and the access network shall set the
13 occurrences of this field as follows:
14 The access network shall set the ith occurrence of this field as
15 follows:
16 If the system on the CDMA Channel corresponding to the ith Channel

17 record that has SystemType equal to 0x01 supports the Forward
18 Packet Data Channel (see [3]), the access terminal shall set the ith
19 occurrence of this field to ‘1’. Otherwise, the access network shall set
20 the ith occurrence of this field to ‘0’.
21 PilotGroupIDIncluded The access network shall set this field to ‘1’ if PilotGroupID field for
22 neighboring sectors is included in this message. Otherwise, the
7-218
1 PilotGroupID The access network shall omit this field if PilotGroupIDIncluded is

2 set to ‘0’. If PilotGroupIDIncluded is set to ‘1’, the access network
3 shall set this field to the PilotGroupID associated with the neighbor
4 pilot. The field associated with the nth occurrence of the
5 PilotGroupIDIncluded field corresponds to the nth occurrence of
6 PilotPN in the record with corresponding SystemType equal to 0x00
7 or 0x02. The PilotPN together with the PilotGroupID identify a Pilot
8 Group (see 7.9.6.1.2.5).
12 this field.
13
14 8.9.6.2.67.9.6.2.6 RouteUpdateRequest
15 The access network sends a RouteUpdateRequest message to request the access terminal
16 to send a RouteUpdate message.
17
7-219
Field Length (bits)
MessageID 8
ChannelIncluded 1
Channel 0 or 24
SectorCount 0 or 4
SectorPilotPN 9
SectorSearchWindowSizeIncluded 0 or 1
SectorSearchWindowSize 0 or 4
SectorSearchWindowOffsetIncluded 0 or 1
SectorSearchWindowOffset 0 or 3
0 – 7 (as
Reserved
needed)
2 ChannelIncluded If SupportRouteUpdateEnhancements is less than 0x02 or if this

3 message is being sent on the Control Channel, the access network
4 shall set this field to ‘0’. Otherwise, the access network may set this
5 field to ‘1’ to indicate that the Channel field is included or to ‘0’ to
6 indicate that the Channel field is not included.
7 Channel If ChannelIncluded is set to ‘0’, the access network shall omit this
8 field. Otherwise, the access network shall set this field to a Channel
9 record specification. See 13.1 for the Channel record format. The
10 access network shall set the SystemType field of this record to 0x00 if
11 SupportRouteUpdateEnhancements is equal to 0x02. The access
12 network shall set the SystemType field of this record to 0x00 or 0x01
13 if SupportRouteUpdateEnhancements is equal to 0x03..
14 SectorCount If ChannelIncluded is set to ‘0’, the access network shall omit this
15 field. Otherwise, the access network shall set this field to the number
16 of records specifying neighboring sectors information included in this
17 message.
7-220
1 SectorPilotPN The access network shall set this field to the PN Offset of a
2 neighboring sector for which the access terminal is to report pilot
3 strength information.
4 SectorSearchWindowSizeIncluded
7 SectorSearchWindowSize field for neighboring sectors is included in
9 SectorSearchWindowSize
11 SectorSearchWindowSizeIncluded is set to ‘0’. If
12 SectorSearchWindowSizeIncluded is set to ‘1’, the access network
7-221
1 Table 7.9.6.2.6-1. Search Window Sizes
Search Window
SearchWindowSize
Size
Value
(PN chips)
0 4
1 6
2 8
3 10
4 14
5 20
6 28
7 40
8 60
9 80
10 100
11 130
12 160
13 226
14 320
15 452
2 SectorSearchWindowOffsetIncluded
5 SectorSearchWindowOffset field for neighboring sectors is included in
7 SectorSearchWindowOffset
9 SectorSearchWindowOffsetIncluded is set to ‘0’. If
10 SectorSearchWindowOffsetIncluded is set to ‘1’, the access network
7-222
1 Table 7.9.6.2.6-2. Search Window Offset
0 0
1 WindowSize81 /2
2 WindowSize
4 - WindowSize /2
5 - WindowSize
7 Reserved
4 network shall set this field to 0. The access terminal shall ignore this
5 field.
6
9 given attribute.
10
Field Length (bits)
MessageID 8
TransactionID 8

15
7-223
4
Field Length (bits)
MessageID 8
TransactionID 8
8
12
Field Length (bits)
MessageID 8
TransactionID 8
16
18 8.9.6.3.17.9.6.3.1 Commands Sent

7-224
1 • ReverseTrafficChannelMAC.Activate
2 • ReverseTrafficChannelMAC.Deactivate
3 • ForwardTrafficChannelMAC.Activate
4 • ForwardTrafficChannelMAC.Deactivate
5 • AccessChannelMAC.Activate
6 • AccessChannelMAC.Deactivate
7 8.9.6.3.27.9.6.3.2 Indications

14 Multicarrier Route Update Protocol. The access terminal and the access network shall
16 attributes belonging to the Multicarrier Route Update Protocol:
17 • RouteUpdateRadiusMultiply
18 • RouteUpdateRadiusAdd
19 • SetManagementParameters
21 network shall not include the RouteUpdateRadiusMultiply and RouteUpdateRadiusAdd
22 attributes in an AttributeUpdateRequest message.

24 The configurable simple attributes for this protocol are listed in Table 7.9.7.1-1.
25 The access terminal and access network shall use as defaults the values in Table 7.9.7.1-1
26 that are typed in bold italics.
7-225

ID
0x00 Distance-based registration is
disabled.
0x0A
Multiplier for the Route
update radius is 1.
0xff RouteUpdateRadiusMultiply
0x01 to 0x64 Multiplier for the Route
update radius in units of 0.1.
All other Reserved
values
0x0000
Addition to the Route update
radius is zero.
0x0001 to Addition to the Route update
0xfe RouteUpdateRadiusAdd 0x0fff
radius expressed as 2’s
complement value.
All other Reserved
values
7-226

ID
0x00 Use of Generic Attribute
Update Protocol to update
RouteUpdateRadiusMultiply
and RouteUpdateRadiusAdd
and processing of
RouteUpdateRequest
message is not supported.
and processing of
RouteUpdateRequest
message without Channel
Record is supported.
SupportRouteUpdateEnhanc RouteUpdateRadiusMultiply
0xfd
ements and RouteUpdateRadiusAdd
and processing of
RouteUpdateRequest
message with Channel
Record whose System Type is
equal to 0x00 is supported.
and processing of
RouteUpdateRequest
message with Channel
Record whose System Type is
equal to 0x00 and 0x01 is
supported.
All other Reserved
values
a maximum of one forward
link CDMA channels for pilots
in the Active Set
0x02 to 0x10 The value of the attribute
0xfc MaxNumberofFLSupported indicates the maximum
number of forward link
CDMA channels for pilots in
the Active Set
All other Reserved
values
7-227

ID
a maximum of one reverse
link CDMA channels for pilots
in the Active Set
0x02 to 0x10 The value of the attribute
0xfb MaxNumberofRLSupported indicates the maximum
number of assigned reverse
link CDMA channels that the
access terminal supports
All other Reserved
values
only a single forward link
CDMA channel.
0xNNNN The maximum separation
between the highest and
MaxForwardLinkBandwidthN lowest forward link CDMA
0xfa
oJammer channels within a Bandclass
that can be assigned to the
access terminal assuming
that there is no jammer
signal82 in between. The unit
of this attribute is 2.5 KHz.
only a single forward link
CDMA channel.
MaxForwardLinkBandwidthW lowest forward link CDMA
0xf9
ithJammer channels within a Bandclass
access terminal assuming
that there can be a jammer
signal in between. The unit
of this attribute is 2.5 KHz.
0xf8 MaxReverseLinkBandwidth only a single reverse link
CDMA channel.
82 The jammer signal refers to a non-HRPD signal.
7-228

ID
lowest reverse link CDMA
channels within a Bandclass
access terminal in units of
2.5 KHz.
a single sub-Active Set only.
0x02 to 0x10 The maximum number of

sub-Active Sets that the
0xf7 MaxNumberOfSub-ActiveSets access terminal can support.
All the other Reserved

values

support reception of more
than one
RPC/RAB/ARQ/DRCLock
channel from a single sub-
Active Set.
0x01 The access terminal does
support reception of more
ForwardFeedbackMultiplexin than one
0xf6
gSupported RPC/RAB/ARQ/DRCLock
channel from a single sub-
Active Set.
All other Reserved
values
7-229
2 record definition). The following complex attributes are to be used only by the access
3 network in a ConfigurationRequest message or an AttributeUpdateRequest message.
4 • SearchParameters
5 • SetManagementParameters
6 The following complex attributes are to be used only by the access terminal in a
7 ConfigurationRequest message:
8 • SupportedCDMAChannels
9 • SupportedDRXPatterns
10 8.9.7.2.17.9.7.2.1 SearchParameters Attribute

11
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
PilotIncrement 4 4
SearchWindowActive 4 8
SearchWindowNeighbor 4 10
SearchWindowRemaining 4 10
14 Length field.
19 PilotIncrement The access network shall set this field to the pilot PN sequence
20 increment, in units of 64 PN chips, that access terminals are to use
21 for searching the Remaining Set. The access network should set this
22 field to the largest increment such that the pilot PN sequence offsets
23 of all its neighbor access networks are integer multiples of that
24 increment. The access terminal shall support all the valid values for
25 this field.
7-230
1 SearchWindowActive
2 Search window size for the Active Set and Candidate Set. The access
5 terminal for the Active Set and Candidate Set. The access terminal
7 SearchWindowNeighbor
8 Search window size for the Neighbor Set. The access network shall
13 SearchWindowRemaining
14 Search window size for the Remaining Set. The access network shall
17 Remaining Set. The access terminal shall support all the valid values
19 8.9.7.37.9.7.3 SetManagementParameters Attribute

20
7-231
Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
PilotAdd 6 0x0e
PilotCompare 6 0x05
PilotDrop 6 0x12
PilotDropTimer 4 3
NeighborMaxAge 4 0
3 Length field.

20 this field.
7-232

18 Table 7.9.7.2.1-1. Pilot Drop Timer Values
Timer Timer
PilotDropTimer Expiration PilotDropTimer 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


7-233

13 entire record is octet-aligned.
14 8.9.7.3.17.9.7.3.1 SupportedCDMAChannels Attribute

15 The access terminal uses this attribute to convey to the access network the CDMA
16 Channels supported by the access terminal.
17
7-234
Field Length Default Value

(bits)
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
BandClassCount 8 0
BandClassCount occurrences of the following record:
{
BandClass 5 N/A
InterFlexDuplexTag 8 N/A
IntraFlexDuplexFlag 1 N/A
BandSubClassCount 8 N/A
BandSubClassCount occurrences of the following field:
BandSubClass 8 N/A
}
Reserved 0–7 N/A
(as
needed)
}
3 Length field.
7 complex value.
8 BandClassCount The access terminal shall set this field to the number of occurrences
9 of the BandClass field in this complex value.
10 BandClass The access terminal shall set this field to the band class supported
11 by the access terminal.
12 InterFlexDuplexTag The access terminal shall set this field to indicate the forward and
13 reverse CDMA channels across Band Classes that can be assigned to
14 it simultaneously as follows: If the value of the InterFlexDuplexTag
7-235
1 field associated with a set of Band Class records are the same, then
2 the access terminal supports the reception from a forward CDMA
3 channel(s) that belong to one of the Band Classes in that set, in
4 combination with transmission on a reverse CDMA channel(s) that
5 belong to a different Band Class in that set.
6 For example, if the value of the InterFlexDuplexTag associated with
7 Bandclass X and Band Class Y are the same, then the access
8 terminal supports assignment of a forward CDMA channel from Band
9 Class X and assignment of a reverse CDMA channel from Band Class
10 Y.
11 IntraFlexDuplexFlag The access terminal shall set this field to ‘1’ to indicate that the
12 access terminal supports reception from any forward CDMA channel
13 and transmission on any reverse CDMA channels within this Band
14 Class. The access terminal shall set this field to ‘0’ to indicate that
15 the access terminal supports reception and transmission only on
16 FDD-paired forward and reverse CDMA channels, respectively for
17 this Band Class (i.e., with the nominal frequency separation specified
18 for the Band Class).
19 BandSubClassCount The access terminal shall set this field to the number of band sub-
20 classes supported by the access terminal in this band class.
21 BandSubClass The access terminal shall set this field to the band sub-class
23 Reserved The access terminal shall add reserved bits to make the length of
24 each attribute value record equal to an integer number of octets. The
25 access terminal shall set this field to zero. The access network shall
27 8.9.7.3.27.9.7.3.2 SupportedDRXPatterns Attribute

28 The access terminal uses this attribute to convey to the access network the supported DRX
29 pattern(s).
30
7-236
Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
NumberofDRXPatterns 4 1
NumberofDRXPatterns occurrences of the following field:
{
SupportedDRXPattern 8 0x00
}
Reserved 0–7 N/A
(as needed)
}
3 Length field.
7 complex value.
8 NumberofDRXPatterns
10 of the SupportedDRXPattern field in this complex value.
11 SupportedDRXPattern
12 This field identifies the forward link interlaces for which the access
13 terminal supports assignment of ForwardTrafficMACIndex. The
14 encoding of this field is as shown in Table 7.9.7.3.2-1. The access
15 terminal shall list the SupportedDRXPattern in the order of
16 preference.
7-237
1 Table 7.9.7.3.2-1. Encoding of the SupportedDRXPattern Field
Field Value Meaning

0x00 The access terminal supports assignment of
Forward Traffic Channel MAC Index on all four
forward interlaces.
0x01 A DRX pattern is supported in which two
consecutive interlaces out of four forward link
interlaces have assigned
ForwardTrafficMACIndices and the next two
consecutive forward link interlaces do not have
assigned ForwardTrafficMACIndices.
0x02 A DRX pattern is supported in which three
interlaces have assigned
ForwardTrafficMACIndices and the next forward
link interlaces does not have an assigned
ForwardTrafficMACIndex.
0x03 A DRX pattern is supported in which three
interlaces do not have assigned
ForwardTrafficMACIndices and the next forward
link interlaces does have an assigned
0x04 A DRX pattern is supported in which alternating
interlaces are assigned a
All the other Reserved
values

3

NRUPType Type field for this protocol Table 2.5.4-1
Subtype field for this protocol
0x0001
NRUPMultiCarrier
NRUPActive Maximum number of the Active Set pilots per
6
sub-Active Set
NRUPCandidate Maximum number of Pilot Groups in the
6
Candidate Set
NRUPNeighbor Minimum size of Pilot Groups in the Neighbor
20
Set

7-238
3 8.9.9.17.9.9.1 RouteUpdate Parameter

7-239
1 Table 7.9.9.1-1. The Format of the Parameter Record for the RouteUpdate Parameter
Length
Field (bits)
ParameterType 8
Length 8
RUPMessageSequence 8
FrameOffset 4
NumSectors 5
NumSubActiveSets 4
AssignedChannelIncluded 1
SchedulerTagIncluded 1
FeedbackMultiplexingEnabled 1
NumSectors occurrences of the following SectorInformation
record:
{0
RAChannelGain 2
PilotPN 9
DRCCover 3
SofterHandoff 1
}0
N occurrences of the following field, where N is the number
of SofterHandoff fields set to ‘0’ in this message
DSC 3
NumSubActiveSets occurrences of the following
SubActiveSetParameters record (starting from
NumFwdChannelsThisSubActiveSet and ending at
RABMACIndex, inclusive):
{0
NumFwdChannelsThisSubActiveSet 0 or 4
NumFwdChannelsThisSubActiveSet occurrences of the
following field:
{1
AssignedChannel 0 or 24
}1
FeedbackEnabled 1
7-240
FeedbackMultiplexingIndex 0 or 9
FeedbackReverseChannelIndex 0 or 4
SubActiveSetCarriesControlChannel 1
ThisSubActiveSetNotReportable 1
DSCForThisSubActiveSetEnabled 0 or 1
Next3FieldsSameAsBefore 0 or 1
DRCLength 0 or 2
DRCChannelGainBase 0 or 6
ACKChannelGain 0 or 6
NumReverseChannelsIncluded 1
NumReverseChannels 0 or 4
{1
ReverseChannelConfiguration 0 or 2
ReverseChannelDroppingRank 0 or 3
}1
NumSectors occurrences of the following record:
{1
PilotInThisSectorIncluded 1
ForwardChannelIndexThisPilot 0 or 4
PilotGroupID 0 or 3
NumUniqueForwardTrafficMACIndices 0 or 3
SchedulerTag 0 or 7
AuxDRCCoverIncluded 0 or 1
AuxDRCCover 0 or 3
ForwardTrafficMACIndexPerInterlaceEnabled 0 or 1
NumUniqueForwardTrafficMACIndices (if included) or zero
occurrences of the following record:
{2
ForwardTrafficMACIndex 0 or 10
AssignedInterlaces 0 or 4
}2
7-241

{2
ReverseLinkMACIndex 0 or 9
RABMACIndex 0 or 7
DeltaT2P 0 or 6
}2
}1
}0
Reserved 0 – 7 (as
needed)
7 access network.
8 RUPMessageSequence
10 RouteUpdate message that was received by the source access
11 network.
12 The access network shall set the remaining fields in this Parameter Record to the values of
13 the corresponding fields in the last TrafficChannelAssignment message that was sent by
14 the source access network.
18
7-242
1 8.107.10 Default Packet Consolidation Protocol
2 8.10.17.10.1 Overview
3 The Default Packet Consolidation Protocol provides packet consolidation on the transmit
4 side and provides packet de-multiplexing on the receive side.
6 8.10.2.17.10.2.1 Commands

10 8.10.2.37.10.2.3 Public Data


14 The Protocol Data Unit for this protocol is a Connection Layer packet. Connection Layer
15 packets contain Session Layer packets destined to or from the same access terminal
16 address.
17 Two types of Connection Layer packets are defined:
18 • Format A: These packets are maximum length packets (including lower layer headers).
19 Format A packets contain one Session Layer packet and do not have Connection Layer
20 headers or padding.
21 • Format B: These packets are maximum length packets (including lower layer headers).
22 Format B packets contain one or more Session Layer packets and have a Connection
23 Layer header(s). The protocol places the Connection Layer header defined in 7.10.6.3.2
24 in front of each Session Layer packet and enough padding to create a maximum length
25 packet.
26 Format A provides an extra octet of payload per packet.
27 The packet format type is passed with the packet to the lower layers.
28 The Connection Layer encapsulation is shown in Figure 7.10.3-1 and Figure 7.10.3-2.
29 All transmitted packets are forwarded to the Security Layer.
30 All received packets are forwarded to the Session Layer after removing the Connection
31 Layer headers.
7-243
1 The maximum size Session Layer packet the protocol can encapsulate depends on the
2 Physical Layer channel on which this packet will be transmitted and on the specific
3 security protocols negotiated.
Connection Layer packet
Session
Layer
packet
4
5 Figure 7.10.3-1. Connection Layer Packet Structure (Format A)
Connection Layer packet
Connection Session Connection Session

Layer Layer Layer Layer Padding
header packet header packet
6
7 Figure 7.10.3-2. Connection Layer Packet Structure (Format B)


21 Upon creation of the InUse instance of this protocol, the access terminal and the access
22 network shall set the value of the attributes for this protocol instance to the default values
25 8.10.5.17.10.5.1 Procedures
7-244

8 then
15 instance, then
16 − The InConfiguration protocol instance at the access terminal and access
17 network shall become the InUse protocol instance for the Packet Consolidation
18 Protocol.
24
Field Length (bits)
MessageID 8
TransactionID 8
29
7-245
3
Field Length (bits)
MessageID 8
TransactionID 8

12
14 8.10.6.17.10.6.1 Procedures
15 This protocol receives the following information with every transmitted Session Layer
16 packet:
17 • Destination channel: Forward Traffic Channel, Control Channel, Reverse Traffic
18 Channel, Access Channel, or Broadcast Channel [14].
19 • Priority.
20 • Forced Single Encapsulation: Whether or not the Session Layer packet can be
21 encapsulated with other Session Layer packets in the same Connection Layer packet.
22 8.10.6.1.17.10.6.1.1 Destination Channels

23 Associated with a Connection Layer packet received by this protocol there shall be a
24 parameter indicating the destination channel on which the packet is to be transmitted.
7-246
1 Associated with a Connection Layer packet received by this protocol there may be a
2 parameter indicating a transmission deadline.
3 8.10.6.1.27.10.6.1.2 Priority Order

4 Packets are prioritized according to the following rules:
5 • If two packets have different priority numbers, the packet with the lower priority
6 number has priority.
7 • If two packets have the same priority number, the packet that was received first by the
8 protocol has priority.
9 Transmission of packets that have higher priority shall take precedence over transmission
10 of packets with lower priority within the constraints imposed by lower layer protocols. The
11 priority assigned to packets applies only to the order in which packets are chosen for
12 inclusion into a Connection Layer packet. The relative placement of Session Layer packets
13 within a Connection Layer packet shall follow the order in which they are to be processed
14 on the receive side.
15 8.10.6.1.37.10.6.1.3 Forced Single Encapsulation

16 If a Forward Traffic Channel Session Layer packet is marked as Forced Single
17 Encapsulation, the access network shall encapsulate it without any other Session Layer
18 packets in a Connection Layer packet. The Packet Consolidation Protocol shall also pass an
19 indication down to the physical layer with the Connection Layer packet, instructing the
20 physical layer to ensure that the Physical Layer packet containing this packet does not
21 contain any other Connection Layer packet. Forced Single Encapsulation applies only to
22 the Forward Traffic Channel MAC Layer packets.
23 Forced Single Encapsulation is used for test services that require a one to one mapping
24 between application packets and Physical Layer packets.
25 8.10.6.1.47.10.6.1.4 Access Terminal Procedures
26 8.10.6.1.4.17.10.6.1.4.1 Format A Packets

27 The access terminal shall create a Format A Connection Layer packet, only if the highest
28 priority pending Session Layer packet will fill the Security Layer payload.
29 The access terminal shall forward the Connection Layer packet for transmission to the
30 Security Layer.
31 8.10.6.1.4.27.10.6.1.4.2 Format B Packets

32 The access terminal shall create a Format B Connection Layer packet by adding the
33 Connection Layer header, defined in 7.10.6.3.2 in front of every Session Layer packet,
34 concatenating the result and adding enough padding to fill the Security Layer payload. The
35 resulting packet length shall not exceed the maximum payload that can be carried on the
36 Physical Layer Channel, given the transmission rate that will be used to transmit the
7-247
1 packet and the headers added by the lower layers. All concatenated Connection Layer
2 packets shall be transmitted on the same Physical Layer Channel.83
3 The protocol shall use the priority order to determine which Session Layer packets shall be
4 included in the Connection Layer packet. The protocol shall concatenate and encapsulate
5 Session Layer packets into a Connection Layer Packet.
6 The access terminal shall forward the Connection Layer packet for transmission to the
7 Security Layer.
8 8.10.6.1.57.10.6.1.5 Access Network Procedures
9 8.10.6.1.5.17.10.6.1.5.1 Control Channel

10 The Control Channel carries broadcast transmissions as well as directed transmissions to
11 multiple access terminals.
12 If the access network transmits a unicast packet to an access terminal over the Control
13 Channel, it should transmit this packet at least from all the sectors in the access terminal’s
14 Active Set. If the data is carried in a synchronous or sub-synchronous capsule, the
15 transmission should occur simultaneously at least once. The access network shall create
16 the Connection Layer packets as defined in 7.10.6.1.5.1.1.
17 The access network shall prioritize Connection Layer packets marked for transmission in a
18 Control Channel synchronous capsule as defined in 7.10.6.1.5.1.2.
20 Control Channel sub-synchronous capsule as defined in 7.10.6.1.5.1.3.
22 Control Channel asynchronous capsule as defined in 7.10.6.1.5.1.1 and 7.10.6.1.5.1.4
23 8.10.6.1.5.1.17.10.6.1.5.1.1 Control Channel Connection Layer Packets

24 The access network shall not encapsulate Session Layer packets destined to different
25 access terminals in the same Connection Layer packet.
26 The access network may encapsulate multiple Session Layer packets destined to a single
27 access terminal in the same Connection Layer packet.
28 The access network should assign a priority to the Connection Layer packet based on its
29 component Session Layer packets. If the Connection Layer packet contains a single Session
30 Layer packet, the priority of the Connection Layer packet should be the priority received
31 with the Session Layer packet.
32 If any Session Layer packet encapsulated in a Connection Layer packet is marked for
33 transmission in a synchronous capsule, the Connection Layer packet shall be marked for
34 transmission in a synchronous capsule. Connection Layer packets may be either Format A
35 or Format B. When the access network forms a Format A Connection Layer packet, it shall
36 set the Format A Connection Layer packet to the Session Layer packet. The resulting
83 i.e., Access Channel or Reverse Traffic Channel.
7-248
1 packet length shall not exceed the maximum payload that can be carried in a Control
2 Channel MAC Layer packet given the headers added by the lower layers. When the access
3 network forms a Format B Connection Layer packet, it shall create the Format B
4 Connection Layer packet by appending the Connection Layer header defined in 7.10.6.3.2
5 in front of every Session Layer packet it is encapsulating in this Connection Layer packet
6 and then concatenating the result. The resulting packet length shall not exceed the
7 maximum payload that can be carried in a Control Channel MAC Layer packet given the
8 headers added by the lower layers.
9 The access network shall forward the Connection Layer packet for transmission to the
10 Security Layer.
11 8.10.6.1.5.1.27.10.6.1.5.1.2 Synchronous Capsule Priority Rules

12 The access network should transmit, in priority order, all Connection Layer packets
13 marked for transmission in a Control Channel synchronous capsule. If the amount of
14 transmitted data (including lower layer headers) exceeds a single Control Channel MAC
15 Layer packet, the access network may extend the synchronous capsule, delay the
16 transmission of some Session Layer packets, or discard Session Layer packets. If the
17 access network discards packets, it should discard them in reverse priority order.
18 In addition to transmitting the above Connection Layer packets, the access network may
19 also transmit the following packets in a synchronous Control Channel capsule:
20 • Packets marked for transmission in an asynchronous Control Channel capsule, in
21 priority order
22 • Packets marked for transmission either on the Forward Traffic Channel or the Control
23 Channel, in priority order
24 If the access network transmits these additional packets, it should follow the above priority
25 ordering, and should transmit them at a lower priority than packets marked for
26 transmission in synchronous capsules only.
27 8.10.6.1.5.1.37.10.6.1.5.1.3 Sub-synchronous Capsule Priority Rules

28 Transmitting sub-synchronous capsules on the Control Channel is optional, because all
29 data marked for transmission in these capsules can also be transmitted in a synchronous
30 capsule.
31 If the access network chooses to transmit Connection Layer packets in a sub-synchronous
32 capsule of the Control Channel, it should do so in the following order:
33 • Packets marked for transmission in a sub-synchronous capsule of the Control Channel,
34 in priority order
35 • Packets marked for transmission in an asynchronous capsule of the Control Channel,
7-249
1 If the access network transmits packets marked for transmission an asynchronous Control
2 Channel capsule or the Forward Traffic Channel in a sub-synchronous capsule, then it
3 should follow the above priority ordering, and should transmit such packets at a lower
4 priority than packets marked for transmission in sub-synchronous capsules.
5 8.10.6.1.5.1.47.10.6.1.5.1.4 Asynchronous Capsule Priority Rules

6 Transmitting asynchronous capsules on the Control Channel is optional, because all data
7 marked for transmission in these capsules can also be transmitted in a synchronous
8 capsule.
9 If the access network chooses to transmit Connection Layer packets in an asynchronous
10 capsule of the Control Channel, it should do so in the following order:
11 • Packets marked for transmission in an asynchronous capsule of the Control Channel,
15 8.10.6.1.5.27.10.6.1.5.2 Forward Traffic Channel

16 The Forward Traffic Channel is time-multiplexed between the different access terminals.
17 The transmission priority given to each access terminal is beyond the scope of this
18 specification.84
19 8.10.6.1.5.2.17.10.6.1.5.2.1 Format A Packets

20 The access network shall create a Format A Connection Layer packet, only if the length of
21 the highest priority pending Session Layer packet will fill the security layer payload.
23 Security Layer.
24 8.10.6.1.5.2.27.10.6.1.5.2.2 Format B Packets

25 The access network shall create a Format B Connection Layer packet by adding the
26 Connection Layer header defined in 7.10.6.3.2 in front of every Session Layer packet,
27 concatenating the result and adding padding to fill the Security Layer payload. The
28 resulting packet length shall not exceed the maximum payload that can be carried on the
29 Forward Traffic Channel given the headers added by the lower layers.
30 The protocol shall encapsulate and concatenate Session Layer packets in priority order.
32 Security Layer.
84 Typical considerations for the access network are throughput maximization balanced with a
fairness criteria between users.
7-250

2 No messages are defined for the InUse instance of this protocol.
3 8.10.6.37.10.6.3 Header Format
4 8.10.6.3.17.10.6.3.1 Pad
5 When creating a Format B Connection Layer packet, the access network and the access
6 terminal shall add sufficient padding so that the packet fills the Security Layer payload and
7 set the padding bits to ‘0’. When receiving a Format B Connection Layer packet, the access
8 network and the access terminal shall ignore the padding bits.
9 8.10.6.3.27.10.6.3.2 Connection Layer Header

10 The access terminal and the access network add the following header in front of every
11 Session Layer packet encapsulated in a Format B Connection Layer packet.
12
Field Length (bits)

Length 8
13 Length Length of Session Layer packet in octets. The sender shall not set
14 this field to zero.
16 8.10.6.4.17.10.6.4.1 Commands Sent

18 8.10.6.4.27.10.6.4.2 Indications


23

NPCPType Type field for this protocol Table 2.5.4-1
NPCPDefault Subtype field for this protocol 0x0000

7-251
1 8.117.11 Overhead Messages Protocol
2 8.11.17.11.1 Overview
3 The QuickConfig message and the SectorParameters message are collectively termed the
4 overhead messages. These messages are broadcast by the access network over the Control
5 Channel. These messages are unique, in that they pertain to multiple protocols and are,
6 therefore, specified separately. The Overhead Messages Protocol provides procedures
7 related to transmission, reception and supervision of these messages.
8 This protocol can be in one of two states:
9 • Inactive State: In this state, the protocol waits for an Activate command. This state
10 corresponds only to the access terminal and occurs when the access terminal has not
11 acquired an access network or is not required to receive overhead messages.
12 • Active State: In this state the access network transmits and the access terminal
13 receives overhead messages.
Initial State Initial State

(AT) Activate (AN)
(AT Only)
Inactive State Active State
Deactivate
(AT only)
14
15 Figure 7.11.1-1. Overhead Messages Protocol State Diagram
17 8.11.2.17.11.2.1 Commands
19 • Activate
20 • Deactivate
21 • ANRedirect (access terminal only)
22 • CheckConfiguration (access terminal only)

25 • ANRedirected
26 • SupervisionFailed
7-252
1 • Updated
2 • ConfigurationChanged (access network only)
3 8.11.2.37.11.2.3 Public Data

6 • All data in the overhead messages
7 • OverheadParametersUpToDate



30 • The protocol at the access network shall enter the Active State.
7-253
2 8.11.5.17.11.5.1 Procedures

12 protocol instances of the Overhead Messages protocol to the Inactive State.
14 protocol instances of the Overhead Messages protocol to the Active State.
18 then
27 instance for the Overhead Messages Protocol at the access terminal and the
28 access network.
34
7-254
Field Length (bits)
MessageID 8
TransactionID 8
8
Field Length (bits)
MessageID 8
TransactionID 8

17
7-255
2 8.11.6.17.11.6.1 Procedures
3 8.11.6.1.17.11.6.1.1 Extensibility Requirements

4 Further revisions of the access network may add new overhead messages.
5 The access terminal shall discard overhead messages with a MessageID field it does not
6 recognize.
7 Further revisions of the access network may add new fields to existing overhead messages.
8 These fields shall be added to the end of the message, prior to the Reserved field if such a
9 field is defined.
10 The access terminal shall ignore fields it does not recognize.

13 8.11.6.1.2.17.11.6.1.2.1 Activate
14 If this protocol receives an Activate command in the Inactive State:
15 • The access terminal shall transition to the Active State.
16 • The access network shall ignore it.
17 If this protocol receives the command in the Active State, it shall be ignored.
18 8.11.6.1.2.27.11.6.1.2.2 Deactivate
19 If this protocol receives a Deactivate command in the Inactive State, it shall be ignored.
20 If this protocol receives the command in the Active State:
21 • Access terminal shall transition to the Inactive State.
22 • Access network shall ignore it.
23 8.11.6.1.37.11.6.1.3 Inactive State

24 This state corresponds only to the access terminal and occurs when the access terminal
25 has not acquired an access network or is not required to receive overhead messages. In this
26 state, the protocol waits for an Activate command.
7-256
1 8.11.6.1.47.11.6.1.4 Active State
2 8.11.6.1.57.11.6.1.5 Access Network Requirements

3 The access network shall include a QuickConfig message in every Control Channel
4 synchronous Sleep State capsule. The access network should include a SectorParameters
5 message in the synchronous capsule at least once every NOMPSectorParameters Control Channel
6 cycles. The access network shall set the SectorSignature field of the QuickConfig message
7 to the SectorSignature field of the next SectorParameters message. The access network
8 shall set the AccessSignature field of the QuickConfig message to the public data
9 AccessSignature (see Access Channel MAC Protocol). If the value of the SectorSignature
10 field of the QuickConfig message is different from that of the last QuickConfig message,
11 then the access network shall generate a ConfigurationChanged indication. The access
12 network shall not generate more than two ConfigurationChanged indications in any
13 OverheadCachePeriod interval.
14 If the access network supports emergency services for conversational rate set 1 or rate set
15 2 for interactive speech without bundling (see [10]) the Access Network shall set the third
16 LSB of the AccessHashingChannelMask for that CDMA channel to ‘1’85. Otherwise, the
17 Access Network shall set this bit to ‘0’.
18 8.11.6.1.67.11.6.1.6 Access Terminal Requirements

19 When in the Active State, the access terminal shall perform supervision on the QuickConfig
20 and the SectorParameters messages as specified in 7.11.6.1.6.1.1 and 7.11.6.1.6.1.2,
21 respectively.
22 If the access terminal does not have any stored value for the overhead parameters or if it
23 receives a RouteUpdate.IdleHO indication, or if it receives a
24 ConnectedState.ConnectionClosed indication, the access terminal shall set
25 OverheadParametersUpToDate to 0.
26 When the access terminal receives the QuickConfig message, it shall perform the following:
27 • If any of the following conditions are true:
28 − OverheadParametersUpToDate is equal to 0,
29 − the value of the SectorSignature field of the new QuickConfig message is
30 different from the last received value for SectorSignature corresponding to the
31 same sector86 from which the QuickConfig message is received, or
32 − the sector from which this QuickConfig message is received is different from
33 the sector from which the last QuickConfig message was received,
34 then the access terminal shall perform the following:
85 The access terminal can use this bit to determine whether to originate an emergency VoIP call on
this channel or tune to another system.

86 A sector is specified by its SectorID and the CDMA channel associated with it (see the definition of
Sector).
7-257
1 − The access terminal shall set OverheadParametersUpToDate to 0.

2 − The access terminal shall monitor every subsequent Control Channel
3 synchronous capsule until it receives the updated SectorParameters message.
4 When the access terminal receives the updated SectorParameters message, it
5 shall return an Updated indication and set OverheadParametersUpToDate to 1.
6 Upon receiving an updated overhead message, the access terminal should store the
7 signature associated with the message, the overhead message parameters, and the (PN
8 Offset, CDMA Channel) associated with the sector for at least OverheadCachePeriod
9 interval.
10 Upon receiving a CheckConfiguration command, the access terminal shall perform the
11 following:
12 • If any of the following conditions is true, then the access terminal shall set
13 OverheadParametersUpToDate to ‘0’, and monitor every subsequent Control Channel
14 synchronous capsule until it receives a SectorParameters message or a QuickConfig
15 message whose SectorSignature field is the same as the last received value for
16 SectorSignature from the same sector.
17 − OverheadParametersUpToDate is ‘0’, or
18 − the ConfigurationChange argument received with the command is different
19 than that received with the last CheckConfiguration command whose (PN
20 Offset, CDMA Channel) argument was the same as that of this command, or
21 − the access terminal’s overhead cache associated with the (PN Offset, CDMA
22 Channel) argument received with the command is older than
23 OverheadCachePeriod interval.
24 When the access terminal receives the above SectorParameters message or QuickConfig
25 message, it shall return an Updated indication and set OverheadParametersUpToDate to
26 ‘1’.If the Redirect field of the QuickConfig message is set to ‘1’, the access terminal shall
27 return an ANRedirected indication.87 Upon receiving an ANRedirect command, the access
28 terminal shall generate an ANRedirected indication.
29 The access terminal shall store a list of RouteUpdateTriggerCodes associated with subnets
30 visited by the access terminal for future comparisons and for future use. This list is called
31 the RouteUpdateTriggerCodeList. Each entry in the RouteUpdateTriggerCodeList shall
32 include the subnet and the RouteUpdateTriggerCode. Other protocols may cache
33 information keyed by (Subnet, RouteUpdateTriggerCode) pairs. If other protocols cache
34 information keyed by (Subnet, RouteUpdateTriggerCode) pairs, then these protocols shall
35 delete such information when the (Subnet, RouteUpdateTriggerCode) pair is deleted from
36 the RouteUpdateTriggerCodeList.
37 If RouteUpdateTriggerCodeListSize is set to 0x00, the access terminal shall delete all
38 entries in the RouteUpdateTriggerCodeList. Otherwise, the access terminal shall perform
39 the following:
87 Redirection is commonly used in networks under test.
7-258
1 • The access terminal shall delete any entries in the RouteUpdateTriggerCodeList other
2 than the current (Subnet, RouteUpdateTriggerCode) received in the most recent
3 SectorParameters message if the entries have an expiration timer that has been
4 running for at least 2^(RouteUpdateTriggerMaxAge + 3) × 1.28 seconds.
5 • If the expiration timer for the RouteUpdateTriggerCodeList entry corresponding to the
6 current (Subnet, RouteUpdateTriggerCode) received in the most recent
7 SectorParameters message has been running for at least 2^(RouteUpdateTriggerMaxAge
8 + 3) × 1.28 seconds, the access terminal shall reset, initialize to zero, and restart the
9 expiration timer for that entry.
10 • If the (Subnet, RouteUpdateTriggerCode) pair from the most recently received
11 SectorParameters message is not included in the RouteUpdateTriggerCodeList, then the
12 access terminal shall add the entry to the RouteUpdateTriggerCodeList and shall reset,
13 initialize to zero, and start the expiration timer for that entry88. The access terminal
14 shall generate a RouteUpdate.SendRouteUpdate command when it adds an entry to the
15 RouteUpdateTriggerCodeList. If there are more than the number of entries specified by
16 the RouteUpdateTriggerCodeListSize attribute in the RouteUpdateTriggerCodeList, then
17 the access terminal shall delete entries from the list until there are exactly
18 RouteUpdateTriggerCodeListSize entries in the list according to the following rules:
19 − The access terminal shall delete the oldest entries in the list first, and
20 − the access terminal shall not delete the entry in the list that corresponds to the
21 (Subnet, RouteUpdateTriggerCode) received in the most recent
23 8.11.6.1.6.17.11.6.1.6.1 Supervision Procedures
24 8.11.6.1.6.1.17.11.6.1.6.1.1 Supervision of QuickConfig Message

25 Upon entering the Active State, the access terminal shall start the following procedure to
26 supervise the QuickConfig message:
27 The access terminal shall set a QuickConfig supervision timer for TOMPQCSupervision.
28 If a QuickConfig message is received while the timer is active, the access terminal shall
29 reset and restart the timer.
30 If the timer expires, the access terminal shall return a SupervisionFailed indication and
32 8.11.6.1.6.1.27.11.6.1.6.1.2 Supervision of SectorParameters Message

33 Upon entering the Active State, the access terminal shall start the following procedure to
34 supervise the SectorParameters message:
35 The access terminal shall set a SectorParameters supervision timer for TOMPSPSupervision.
88 The AT could wait for confirmation that the RouteUpdate was delivered before updating
the RouteUpdateTriggerCode list.
7-259
1 If a SectorParameters message is received while the timer is active, the access terminal
2 shall reset and restart the timer.
3 If a QuickConfig message is received while the timer is active and the SectorSignature field
4 of the QuickConfig message matches the last received value for SectorSignature
5 corresponding to the same sector89 from which the QuickConfig message is received, the
6 access terminal shall reset and restart the timer.
7 If the timer expires, the access terminal shall return a SupervisionFailed indication and
10 8.11.6.2.17.11.6.2.1 QuickConfig
11 The QuickConfig message is used to indicate a change in the overhead messages’ contents
12 and to provide frequently changing information.
13
89 A sector is specified by its SectorID and the CDMA channel associated with it (see the definition of
Sector).
7-260
Field Length (bits)

MessageID 8
ColorCode 8
SectorID24 24
SectorSignature 16
AccessSignature 16
Redirect 1
RPCCount63To0 6
RPCCount63To0 occurrences of the following field
ForwardTrafficValid63To0 1
RPCCount127To64Included 0 or 1
RPCCount127To64 0 or 6
RPCCount127To64 occurrences of the following field:
ForwardTrafficValid127To64 0 or 1
RPCCount130To383Included 0 or 1
RPCCount130To383 0 or 8
RPCCount130To383 occurrences of the following field:
ForwardTrafficValid130To383 0 or 1
2 ColorCode The access network shall set this field to the color code
3 corresponding to this sector.
4 SectorID24 The access network shall set this field to the least significant 24 bits
5 of the SectorID value corresponding to this sector.
6 SectorSignature The access network shall set this field to the value of the
7 SectorSignature field of the next SectorParameters message it will
8 transmit.
9 AccessSignature The access network shall set this field to the value of the
10 AccessSignature parameter from the AccessParameters message that
11 is Public Data of the Access Channel MAC Protocol.
7-261
1 Redirect Access network redirect. The access network shall set this field to ‘1’
2 if it is redirecting all access terminals away from this access
3 network.90
4 RPCCount63To0 The access network shall set this field to the maximum number of
5 RPC channels supported by the sector corresponding to Forward
6 Traffic Channels associated with MAC indices 0 through 63,
7 inclusive.
8 ForwardTrafficValid63To0
9 The access network shall set occurrence n of this field to ‘1’ if the
10 Forward Traffic Channel associated with MACIndex 64-n is valid. The
11 access terminal uses this field to perform supervision of the Forward
12 Traffic Channel.
13 RPCCount127To64Included
14 If this field is included, the access network shall set this field to ‘1’ if
15 the RPCCount127To64 field is included in this message. Otherwise,
16 the access network shall set this field to ‘0’. The access network shall
17 include this field if any of the fields below it are included in this
18 message.
19 RPCCount127To64 If the RPCCount127To64Included field is omitted, or if

20 RPCCount127To64Included is ‘0’, then the access network shall omit
21 this field. Otherwise, the access network shall set this field to the
22 maximum number of RPC channels supported by the sector
23 corresponding to Forward Traffic Channels associated with MAC
24 indices 64 through 127, inclusive.
26 If the RPCCount127To64Included field is omitted, or if

27 RPCCount127To64Included is ‘0’, then the access network shall omit
28 this field. Otherwise, the access network shall set occurrence n of
29 this field to ‘1’ if the Forward Traffic Channel associated with
30 MACIndex 128-n is valid. The access terminal uses this field to
31 perform supervision of the Forward Traffic Channel.
32 RPCCount130To383Included
33 If this field is included, the access network shall set this field to ‘1’ if
34 the RPCCount130To383 field is included in this message. Otherwise,
90 Network redirect is commonly used during testing.
7-262
1 RPCCount130To383
3 RPCCount130To383Included is ‘0’, then the access network shall
4 omit this field. Otherwise, the access network shall set this field to
5 the maximum number of RPC channels supported by the sector
6 corresponding to Forward Traffic Channels associated with MAC
7 indices 128 through 383, inclusive.
10 RPCCount130To383Included is ‘0’, then the access network shall
11 omit this field. The access network shall set this field to ‘1’ if the
12 corresponding ReverseLinkMACIndex is valid. Otherwise, the access
14 The n th occurrence of this field corresponds to the
15 ReverseLinkMACIndex 130+(n-1)/2 if n is odd and to 257+n/2 if n is
16 even.
20 this field.
21
Channels CCsynSS SLP Best Effort
22 8.11.6.2.27.11.6.2.2 SectorParameters
23 The SectorParameters message is used to convey sector specific information to the access
24 terminals.
25
7-263
Field Length (bits)
MessageID 8
CountryCode 12
SectorID 128
SubnetMask 8
SectorSignature 16
Latitude 22
Longitude 23
RouteUpdateRadiusOverhead 11
LeapSeconds 8
LocalTimeOffset 11
ReverseLinkSilenceDuration 2
ReverseLinkSilencePeriod 2
ChannelCount 5
ChannelCount occurrences of the following field:
Channel 24
NeighborCount 5
NeighborCount occurrences of the following field:
NeighborPilotPN 9
NeighborCount occurrences of the following two fields:

NeighborChannelIncluded 1
NeighborChannel 0 or 24
NeighborSearchWindowSizeIncluded 1
NeighborCount occurrences of the following field
NeighborSearchWindowSize 0 or 4
NeighborSearchWindowOffsetIncluded 1
NeighborCount occurrences of the following field
NeighborSearchWindowOffset 0 or 3
ExtendedChannelIncluded 0 or 1
7-264
Field Length (bits)
ExtendedChannelCount 0 or 5
0 or ExtendedChannelCount occurrences of the
following field:
ExtendedChannel 24
AccessHashingChannelMaskIncluded 0 or 1
AccessHashingMaskLength 0 or 4
n, occurrences of the following record, where 0 ≤ n ≤
(ChannelCount + ExtendedChannelCount),
AccessHashingChannelMaskSameAsPr
1
evious
0 or
AccessHashi
AccessHashingChannelMask
ngMaskLengt
h+1
RouteUpdateTriggerCodeIncluded 0 or 1
RouteUpdateTriggerCode 0 or 12
RouteUpdateTriggerMaxAge 0 or 4
PriorSessionGAUP 0 or 1
m, 0 ≤ m ≤ NeighborCount occurrences of the
following field:
PilotGroupIDLoopIncluded 0 or 1
Zero or NeighborCount + 1 - m occurrences of the
following two fields:
PilotGroupIDIncluded 0 or 1
PilotGroupID 0 or 3
IsSectorMultiCarrierCapable 0 or 1
n, occurrences of the following two fields, where n is
the total number of Channel and ExtendedChannel
records in this message that have SystemType equal
to 0x02
7-265
Field Length (bits)
SecondaryColorCodeIncluded 0 or 1
SecondaryColorCodeCount 0 or 3
Zero or SecondaryColorCodeCount occurrences of the
following field:
SecondaryColorCode 8
PilotGroupIDLoopIncluded 0 or 1
Zero or NeighborCount + 1 - m occurrences of the
PilotGroupIDIncluded 0 or 1
PilotGroupID 0 or 3
IsSectorMultiCarrierCapable 0 or 1
n, occurrences of the following two fields, where n is
the total number of Channel and ExtendedChannel
records in this message that have SystemType equal
to 0x02
0 – 7 (as
Reserved
needed)
2 CountryCode The access network shall set this field to the three-digit BCD (binary
3 coded decimal) encoded representation of the Mobile Country Code
4 (as specified in [12]) associated with this sector.
5 SectorID Sector Address Identifier. The Access Network shall set the value of
6 the SectorID according to the rules specified in 13.9. The Access
7 Terminal shall not assume anything about the format of the SectorID
8 other than the (SectorID, CDMA Channel) pair uniquely identifies a
9 sector. The value of this field should be less than or equal to 104 if
10 SecondaryColorCodeIncluded field is included and is set to ‘1’.
7-266
1 SubnetMask Sector Subnet identifier. The access network shall set this field to the
2 number of consecutive 1's in the subnet mask of the subnet to which
3 this sector belongs.
4 SectorSignature SectorParameters message signature. The access network shall

5 change this field if the contents of the SectorParameters message
6 changes.
7 Latitude The latitude of the sector. The access network shall set this field to
8 this sector’s latitude in units of 0.25 second, expressed as a two’s
9 complement signed number with positive numbers signifying North
10 latitudes. The access network shall set this field to a value in the
11 range -1296000 to 1296000 inclusive (corresponding to a range of -
12 90° to +90°).
13 Longitude The longitude of the sector. The access network shall set this field to
14 this sector’s longitude in units of 0.25 second, expressed as a two’s
15 complement signed number with positive numbers signifying East
16 longitude. The access network shall set this field to a value in the
17 range -2592000 to 2592000 inclusive (corresponding to a range of -
18 180° to +180°).
19 RouteUpdateRadiusOverhead
20 If the access terminal is to perform distance based route updates, the
21 access network shall set this field to the non-zero “distance” beyond
22 which the access terminal is to send a new RouteUpdate message
23 (see Default Route Update Protocol). If access terminals are not to
24 perform distance based route updates, the access network shall set
25 this field to 0.91
26 LeapSeconds The number of leap seconds that have occurred since the start of
27 CDMA System Time.
28 LocalTimeOffset The access network shall set this field to the offset of the local time
29 from CDMA System Time. This value will be in units of minutes,
30 expressed as a two’s complement signed number.
31 ReverseLinkSilenceDuration
32 The access network shall set this field to specify the duration of the
33 Reverse Link Silence Interval in units of frames.
91 The access terminal determines whether to send a distance based RouteUpdate message or not
using the RouteUpdateRadiusOverhead value of the serving sector. If the serving sector allows
distance based Route Updates, the access terminal uses the RouteUpdateRadiusOverhead value sent
by the sector in which the access terminal last registered.
7-267
1 ReverseLinkSilencePeriod
2 The access network shall set this field to specify the period of the
3 Reverse Link Silence Interval. The Reverse Link Silence Interval is
4 defined as the time interval of duration ReverseLinkSilenceDuration
5 frames that starts at times T where T is the CDMA System Time in
6 units of frames and it satisfies the following equation:
7 T mod (2048×2ReverseLinkSilencePeriod - 1) = 0.
8 ChannelCount The access network shall set this field to the number of cdma2000
9 high rate packet data channels available to the access terminal on
10 this sector.
11 Channel Channel record specification for each channel. See 13.1 for the
12 Channel record format. The access network shall set the SystemType
13 field of this record to 0x00 or 0x02.
14 NeighborCount The access network shall set this field to the number of records
16 NeighborPilotPN The access network shall set this field to the PN Offset of a
17 neighboring sector that the access terminal should add to its
18 Neighbor Set.
19 NeighborChannelIncluded
20 The access network shall set this field to ‘1’ if a Channel record is
21 included for this neighbor, and to ‘0’ otherwise. The nth occurrence of
22 this field corresponds to the nth occurrence of NeighborPilotPN in the
23 record that contains the NeighborPilotPN field above.
24 NeighborChannel Channel record specification for the neighbor channel. See 13.1 for
25 the Channel record format. The access network shall omit this field if
26 the corresponding NeighborChannelIncluded field is set to ‘0’.
27 Otherwise, if included, the nth occurrence of this field corresponds to
28 the nth occurrence of NeighborPilotPN in the record that contains the
29 NeighborPilotPN field above.
30 NeighborSearchWindowSizeIncluded
31 The access network shall set this field to ‘1’ if
32 NeighborSearchWindowSize field for neighboring sectors is included
33 in this message. Otherwise, the access network shall set this field to
34 ‘0’.
35 NeighborSearchWindowSize
37 NeighborSearchWindowSizeIncluded is set to ‘0’. If
38 NeighborSearchWindowSizeIncluded is set to ‘1’, the access network
39 shall set this field to the value shown in Table 7.11.6.2-1
7-268

3 corresponds to the nth occurrence of NeighborPilotPN in the record
4 that contains the NeighborPilotPN field above.
Search Window
SearchWindowSize
Size
Value
(PN chips)
0 4
1 6
2 8
3 10
4 14
5 20
6 28
7 40
8 60
9 80
10 100
11 130
12 160
13 226
14 320
15 452
6 NeighborSearchWindowOffsetIncluded
7 The access network shall set this field to ‘1’ if
8 NeighborSearchWindowOffset field for neighboring sectors is included
9 in this message. Otherwise, the access network shall set this field to
10 ‘0’.
11 NeighborSearchWindowOffset
13 NeighborSearchWindowOffsetIncluded is set to ‘0’. If
14 NeighborSearchWindowOffsetIncluded is set to ‘1’, the access
7-269
1 corresponds to the nth occurrence of NeighborPilotPN in the record

2 that contains the NeighborPilotPN field above.
0 0
1 WindowSize92 /2
2 WindowSize
4 - WindowSize /2
5 - WindowSize
7 Reserved
4 ExtendedChannelIncluded
5 If any of the fields after this field except for Reserved are included,
6 the access network shall include this field. Otherwise, the access
8 this field as follows:
9 The access network shall set this field to ‘0’ if the ExtendedChannel
11 to ‘1’.
12 ExtendedChannelCount
13 If the ExtendedChannelIncluded field is omitted or is included and
14 set to ‘0’, the access network shall omit this field. Otherwise, the
15 access network shall include this field and shall set this field to the
16 number of cdma2000 high rate packet data extended channels
17 available to the access terminal on this sector. If this field is not
18 included, the access terminal shall assume that the value of this field
19 is ‘00000’.
20 ExtendedChannel Channel record specification for each extended channel. If

21 ExtendedChannelCount is not included, the access network shall
22 omit this field. See 13.1 for the Channel record format. The access
23 network shall set the SystemType field of this record to 0x00 or 0x02.
24 AccessHashingChannelMaskIncluded
7-270
4 AccessHashingChannelMask fields are omitted. Otherwise, the
6 AccessHashingMaskLength
7 If the AccessHashingChannelMaskIncluded field is omitted or is
8 included and set to ‘0’, the access network shall omit this field.
9 Otherwise, the access network shall set this field one less than the
10 number of bits in the AccessHashingChannelMask field(s).
11 If the AccessHashingChannelMaskIncluded field is omitted or is included and set to ‘0’, the

12 access network shall omit the following two-field record. Otherwise, the access network
13 shall include m occurrences of the following two field record, where m is the total number
14 of Channel and ExtendedChannel records in this message that have SystemType equal to
15 0x00 or 0x02.
16 AccessHashingChannelMaskSameAsPrevious
17 The access network shall set this field in the ith occurrence of this
18 record as follows:
19 If i is greater than 1 and the AccessHashingChannelMask for the ith
20 Channel or ExtendedChannel record with SystemType equal to 0x00
21 or 0x02 in this message is the same as the
22 AccessHashingChannelMask for the (i-1)th Channel or
23 ExtendedChannel record with SystemType equal to 0x00 or 0x02 in
24 this message, the access network may set this field to ‘1’. Otherwise,
26 AccessHashingChannelMask
27 The access network shall set this field in the ith occurrence of this
28 record as follows:
29 If the AccessHashingChannelMaskSameAsPrevious field in this
30 record is set to ‘1’, the access network shall omit this field.
31 Otherwise, the access network shall set this field to the
32 (AccessHashingMaskLength + 1) bit access hashing class of the ith
33 combined channel list entry in this message that has SystemType
34 equal to 0x00 or 0x02, where the combined channel list is defined to
35 be the ordered set of all Channel records in order (if any) with all
36 Extended Channel records appended in order (if any). If this field is
37 not included, the access terminal shall assume that the value of this
38 field is the same as the value for this field in the previous occurrence
39 of this record.
40 RouteUpdateTriggerCodeIncluded
41 The access network shall include this field if any of the fields other
42 than the Reserved field that follow this field are to be included in the
7-271
1 message. If this field is included, the access network shall set it as

2 follows: The access network shall set this field to ‘1’ if
3 RouteUpdateTriggerCode is included in this message. Otherwise, the
4 access network shall set this field to ‘0’. If this field is not included in
5 the message, that access terminal shall assume a value of ‘0’ for this
6 field.
7 RouteUpdateTriggerCode
8 If the RouteUpdateTriggerCodeIncluded field is not included in this
9 message, or if the RouteUpdateTriggerCodeIncluded field is included
10 and is set to ‘0’, then the access network shall omit this field.
11 Otherwise, the access network shall set this field to a 12-bit value93.
12 RouteUpdateTriggerMaxAge
13 If the RouteUpdateTriggerCodeIncluded field is not included in this
14 message or if the RouteUpdateTriggerCodeIncluded field is included
15 and set to ‘0’, the access network shall omit this field. Otherwise, the
16 access network shall set this field to indicate the duration of the
17 RouteUpdateTriggerCode timer.
18 PriorSessionGAUP The access network shall include this field if any of the fields other
20 message. If this field is included, then the access network shall set
22 If the access terminal is not allowed to include the PriorSession
23 attribute in an AttributeUpdateRequest message, then the access
27 The access network shall include this field if any of the fields other
29 message. If this field is not included in the message, the access
30 terminal shall assume a value of ‘0’ for this field. If this field is
31 included, the access network shall set this field as follows:
34 to ‘1’.

36 to ‘0’, then the access network shall omit all occurrences of this field.
93 The RouteUpdateTriggerCode represents parameters associated with other protocols or

applications. A RouteUpdate message is triggered when the RouteUpdateTriggerCode changes. The
access network can update parameters associated with other protocols or applications when it
determines that the parameters at the access terminal need to be updated.
7-272

2 field, where m is the number of NeighborChannel records in this
3 message that have SystemType equal to 0x01, and the access
4 network shall set the occurrences of this field as follows:
5 The access network shall set the ith occurrence of this field as follows:
6 If the system on the CDMA Channel corresponding to the ith
7 NeighborChannel record that has SystemType equal to 0x01
8 supports the Forward Packet Data Channel (see [3]), the access
9 network shall set the ith occurrence of this field to ‘1’. Otherwise, the
10 access network shall set the ith occurrence of this field to ‘0’.
11 PilotGroupIDLoopIncluded
13 fields that follow this field are to be included in the message. If
15 The access network shall set this field to ‘1’ if one or more
16 PilotGroupIDIncluded fields are included in this message. Otherwise,
18 PilotGroupIDIncluded
19 The access network shall omit this field if PilotGroupIDLoopIncluded
20 field is omitted or set to ‘0’. Otherwise, the access network shall
21 include this field and set it as follows: The access network shall set
22 the first occurrence of this field to ‘1’ if the PilotGroupID field
23 corresponding to the pilot transmitting this message is included in
24 this message. The access network shall set the n+1 th occurrence of
25 this field to ‘1’ if PilotGroupID field corresponding to the nth
26 occurrence of NeighborPilotPN field, with corresponding SystemType
27 equal to 0x00 or 0x02, is included in this message. Otherwise, the
29 If this field is not included in the message, the access terminal shall
30 assume a value of ‘0’ for this field.
31 PilotGroupID The access network shall omit this field if GroupIDIncluded field is
32 omitted or set to ‘0’. Otherwise, the access network shall include this
33 field and set it as follows:
34 The access network shall set this field to the PilotGroupID associated
35 with the neighbor pilot or the pilot transmitting this message. The
36 PilotPN of a neighbor pilot or the pilot transmitting this message,
37 together with the PilotGroupID identify a Pilot Group (see
38 8.9.6.1.2.5).
39 IsSectorMultiCarrierCapable
41 fields that follow this field are to be included in the message. If this
42 field is not included in the message, the access terminal shall
7-273
1 assume a value of ‘0’ for this field. If included, the access network
2 shall set this field to ‘1’ if the access network is capable of assigning
3 more than one channel to the access terminal while connected.
5 The access network shall include n occurrences of the following two field record, where n is
6 the total number of Channel and ExtendedChannel records in this message that have
7 SystemType equal to 0x02.
8 ReverseBandClass The access network shall include this field if any of the non-reserved
9 fields that follow this field are to be included in the message. The
10 access network shall set the ith occurrence of this field to the band
11 class number for the reverse CDMA channel associated with the ith
13 equal to 0x02. The combined channel list is defined to be the
14 ordered set of all Channel records in order (if any) with all Extended
15 Channel records appended in order (if any).
19 access network shall set the ith occurrence of this field to the channel
20 number that identifies the reverse CDMA channel associated with the
21 ith combined channel list entry in this message that has SystemType
25 SecondaryColorCodeIncluded
30 SecondaryColorCodeCount field is included. Otherwise, the access
32 SecondaryColorCodeCount
33 If SecondaryColorCodeIncluded is omitted or set to ‘0’, then the
34 access network shall omit this field. Otherwise, the access network
35 shall set this field as follows:
36 If SecondaryColorCodeIncluded is included and set to ‘1’, then the
37 access network shall set this field to indicate the number of
38 secondary color codes covering this sector. If the access terminal is
39 to consider all possible values of ColorCode to be included in this
40 message, then the access network shall set this field to ‘000’.
7-274
1 SecondaryColorCode
2 If SecondaryColorCodeCount is omitted or included and set to ‘000’,
3 then the access network shall omit this field. Otherwise, the access
4 network shall set this field as follows:
5 The access network shall set this field to a color code that is to be
6 considered to be a member of the set of the SecondaryColorCode
7 values.
8 PilotGroupIDLoopIncluded
12 The access network shall set this field to ‘1’ if one or more
13 PilotGroupIDIncluded fields are included in this message. Otherwise,
15 PilotGroupIDIncluded
16 The access network shall omit this field if PilotGroupIDLoopIncluded
17 field is omitted or set to ‘0’. Otherwise, the access network shall
18 include this field and set it as follows: The access network shall set
19 the first occurrence of this field to ‘1’ if the PilotGroupID field
20 corresponding to the pilot transmitting this message is included in
21 this message. The access network shall set the n+1 th occurrence of
22 this field to ‘1’ if PilotGroupID field corresponding to the nth
23 occurrence of NeighborPilotPN field, with corresponding SystemType
24 equal to 0x00 or 0x02, is included in this message. Otherwise, the
26 If this field is not included in the message, the access terminal shall
27 assume a value of ‘0’ for this field.
28 PilotGroupID The access network shall omit this field if PilotGroupIDIncluded field
29 is omitted or set to ‘0’. Otherwise, the access network shall include
30 this field and set it as follows:
31 The access network shall set this field to the PilotGroupID associated
32 with the neighbor pilot or the pilot transmitting this message. The
33 PilotPN of a neighbor pilot or the pilot transmitting this message,
34 together with the PilotGroupID identify a Pilot Group (see
35 7.9.6.1.2.5).
36 IsSectorMultiCarrierCapable
38 fields that follow this field are to be included in the message. If this
39 field is not included in the message, the access terminal shall
40 assume a value of ‘0’ for this field. If included, the access network
41 shall set this field to ‘1’ if the access network is capable of assigning
7-275
1 more than one channel to the access terminal while connected.

3 The access network shall include n occurrences of the following two field record, where n is
4 the total number of Channel and ExtendedChannel records in this message that have
5 SystemType equal to 0x02.
6 ReverseBandClass The access network shall include this field if any of the non-reserved
8 access network shall set the ith occurrence of this field to the band
9 class number for the reverse CDMA channel associated with the ith
17 access network shall set the ith occurrence of this field to the channel
18 number that identifies the reverse CDMA channel associated with the
19 ith combined channel list entry in this message that has SystemType
26 this field.
27
29 8.11.6.3.17.11.6.3.1 Commands Sent

30 This protocol sends the following command:
31 • RouteUpdate.SendRouteUpdate
32 8.11.6.3.27.11.6.3.2 Indications
34 • RouteUpdate.IdleHO
7-276

3 The simple configurable attributes are listed in Table 7.11.7-1. The access network and the
4 access terminal shall use the default values that are typed in bold italics.
5 Table 7.11.7-1 Configurable Simple Attributes

ID
0xff OverheadCachePeriod 0x00 Value of overhead cache period is zero.
0x01 to Value of overhead cache period in units
0xff of 5.12 seconds.
0x00 Sending of RouteUpdate messages based
on the RouteUpdateTriggerCodeList is
disabled.
RouteUpdateTriggerCod 0x01 – Size of the RouteUpdateTriggerCodeList
0xfe
eListSize 0x05
All other Reserved.
values

7

NOMPType Type field for this protocol Table 2.5.4-1
NOMPDefault Subtype field for this protocol 0x0000
12 Control
TOMPQCSupervision QuickConfig supervision timer
Channel cycles
12 Control
TOMPSPSupervision SectorParameters supervision timer
Channel cycles
The recommended maximum number of Control
NOMPSectorParameters Channel cycles between two consecutive 4
SectorParameters message transmissions

7-277
1 No text.
7-278
Security Layer 3GPP2 C.S0024-B v2.0
1 98 SECURITY LAYER

4 The Security Layer provides the following functions:
5 • Key Exchange: Provides the procedures followed by the access network and by the
6 access terminal to exchange security keys for authentication and encryption.
7 • Authentication: Provides the procedures followed by the access network and the access
8 terminal for authenticating traffic.
9 • Encryption: Provides the procedures followed by the access network and the access
10 terminal for encrypting traffic.
11 The Security Layer uses the Key Exchange Protocol, Authentication Protocol, Encryption
12 Protocol, and Security Protocol to provide these functions. Security Protocol provides public
13 variables needed by the authentication and encryption protocols (e.g., cryptosync, time-
14 stamp, etc.).
15 Figure 8.1.1-1 shows the protocols within the Security Layer.
Authentication Protocol Key Exchange Protocol
Encryption Protocol Security Protocol
16
17 Figure 8.1.1-1. Security Layer Protocols
18 9.28.2 Data Encapsulation for the InUse Protocol Instances

19 Figure 8.2-1 illustrates the relationship between a Connection Layer packet, a Security
20 Layer packet and a MAC Layer payload.
8-1
3GPP2 C.S0024-B v2.0 Security Layer
Connection
Layer
packet
Encryption Encryption Encryption Encryption

packet header payload trailer
Authentication Authentication Authentication Authentication

packet header payload trailer
Security Protocol
packet Security Security Security
or Protocol Protocol Protocol
Security Layer header payload trailer
Packet
MAC
Layer
payload
1
2 Figure 8.2-1. Security Layer Encapsulation
3 The Security Layer headers or trailers may not be present (or equivalently, have a size of
4 zero) if session configuration establishes the Default Security Layer or if the configured
5 Security Protocol does not require a header or trailer. The Encryption Protocol may add a
6 trailer to hide the actual length of the plain-text or padding to be used by the encryption
7 algorithm. The Encryption Protocol Header may contain variables such as initialization
8 vector (IV) to be used by the Encryption Protocol. The Authentication Protocol header or
9 trailer may contain the digital signature that is used to authenticate the portion of the
10 Authentication Protocol Packet that is authenticated. The Security Protocol header or
11 trailer may contain variables needed by the authentication and encryption protocols (e.g.,
12 cryptosync, time-stamp, etc.).
13 Figure 8.2-1 shows the portions of the security layer packet that may be encrypted and
14 authenticated. The authentication is performed on the Encryption Protocol Packet. This
15 avoids unnecessary decryption when authentication fails.
16 The Security Layer shall pass the ConnectionLayerFormat field given to it by the MAC Layer
17 to the Connection Layer with the Connection Layer packet.
8-2
1 9.38.3 Default Security Protocol
2 9.3.18.3.1 Overview
3 The Default Security Protocol does not provide any services, except for transferring packets
4 between the Authentication Protocol and the MAC layer.
6 9.3.2.18.3.2.1 Commands

10 9.3.2.38.3.2.3 Public Data


14 The protocol data unit for this protocol is a Security Layer packet. Each Security Layer
15 packet consists of an Authentication Protocol packet.


8-3
2 9.3.5.18.3.5.1 Procedures

12 then
21 instance for the Security Protocol.
27
Field Length (bits)
MessageID 8
TransactionID 8
8-4
7
Field Length (bits)
MessageID 8
TransactionID 8

16
18 9.3.6.18.3.6.1 Procedures
19 The protocol shall set the Security Layer packet to the Authentication Protocol packet and
20 shall forward it for transmission to the MAC Layer. This protocol does not define a Security
21 Protocol header or trailer.
22 This protocol shall set the Authentication Protocol packet to the Security Layer packet
23 received from the MAC Layer, and shall forward the packet to the Authentication Protocol.
8-5

3 9.3.6.38.3.6.3 Default Security Protocol Header

4 The Default Security Protocol does not add a header.
5 9.3.6.48.3.6.4 Default Security Protocol Trailer

6 The Default Security Protocol does not add a trailer.
8 9.3.6.5.18.3.6.5.1 Commands
10 9.3.6.5.28.3.6.5.2 Indications


NSPType Type field for this protocol Table 2.5.4-1
NSPDefault Subtype field for this protocol 0x0000

8-6
1 9.48.4 Generic Security Protocol
2 9.4.18.4.1 Overview
3 The Generic Security protocol performs the following tasks:
4 • On the transmission side, this protocol provides a cryptosync that may be used by the
5 negotiated Authentication Protocol and Encryption Protocol.
6 • On the receiving side, this protocol computes the cryptosync using the information
7 provided in the Generic Security Protocol header and makes the cryptosync publicly
8 available.
10 9.4.2.18.4.2.1 Commands

14 9.4.2.38.4.2.3 Public Data

17 • Cryptosync

19 The protocol data unit for this protocol is a Security Layer packet.

8-7
2 9.4.5.18.4.5.1 Procedures

12 then
21 instance for the Security Protocol.
27
Field Length (bits)
MessageID 8
TransactionID 8
8-8
7
Field Length (bits)
MessageID 8
TransactionID 8

16
18 9.4.6.18.4.6.1 Procedures
19 Each Security Layer packet consists of an Authentication Protocol packet and a Security
20 Protocol header.
21 The protocol shall construct a Security Layer packet out of the Authentication Protocol
22 packet as follows and shall pass the packets for transmission to the MAC Layer:
8-9
1 • When the protocol receives an Authentication Protocol packet from the Authentication
2 Protocol that is either authenticated or encrypted, it shall set CryptosyncShort in the
3 Generic Security Protocol header to the least significant 16 bits of the value of the
4 Cryptosync that is used by the Authentication Protocol or the Encryption Protocol to
5 authenticate or encrypt this packet. The Generic Security Protocol shall then add the
6 Generic Security Protocol header in front of the Authentication Protocol packet. The
7 packet structure is shown in Figure 8.2-1.
8 • When the protocol receives an Authentication Protocol packet from the Authentication
9 Protocol that is neither authenticated nor encrypted, the protocol shall not add a
10 security protocol header to the Authentication Protocol packet.
11 • This protocol shall not append a trailer to the Authentication Protocol packet.
12 This Generic Security Protocol shall construct the Authentication Protocol packet using the
13 Security Layer packet (received from the MAC Layer) as follows and shall forward the
14 packet to the Authentication Protocol:
15 • When the protocol receives a Security Layer packet from the MAC Layer that is either
16 authenticated or encrypted, it shall construct the Authentication Protocol packet by
17 removing the Security Layer header.
18 • When the protocol receives a Security Layer packet from the MAC Layer that is neither
19 authenticated nor encrypted, it shall set the Authentication Protocol packet to the
20 Security Layer packet.
21 When the Security Layer receives a Connection Layer packet that is to be either
22 authenticated or encrypted, the Generic Security Protocol shall choose a value for the
23 Cryptosync based on the current 64-bit representation of the CDMA System Time in units
24 of 80 ms, such that Cryptosync does not specify a time later than the time that the security
25 layer packet will be transmitted by the physical layer, and is not earlier than the current
26 CDMA System Time94. The protocol shall then set CryptosyncShort in the Generic Security
27 Protocol header to Cryptosync[15:0].
28 When the Generic Security Protocol receives a Security Layer packet from the MAC Layer
29 that is either authenticated or encrypted, it shall compute the 64-bit Cryptosync using
30 CryptosyncShort given in the Generic Security Protocol Header as follows:
31 Cryptosync = (SystemTime – (SystemTime[15:0] – CryptosyncShort) mod 216) mod
32 264,
33 where SystemTime is the current CDMA System Time in units of 80 ms,
34 SystemTime[15:0] is the 16 least significant bits of the SystemTime, and
35 CryptosyncShort is the 16-bit Generic Security protocol header.

94 For example, the protocol may choose the current CDMA System Time as Cryptosync.
8-10
1 9.4.6.38.4.6.3 Generic Security Protocol Header

2 The Generic Security Protocol Header is as follows:
3
Field Length(bits)
CryptosyncShort 0 or 16
4 CryptosyncShort The sender shall include this field, only if the Authentication Protocol
5 packet is either authenticated or encrypted. The sender shall set this
6 field to the 16 least significant bits of the Cryptosync.
7 9.4.6.48.4.6.4 Generic Security Protocol Trailer

8 The Generic Security Protocol does not add a trailer.
10 9.4.6.5.18.4.6.5.1 Commands
12 9.4.6.5.28.4.6.5.2 Indications


NSPType Type field for this protocol Table 2.5.4-1
NSPGeneric Subtype field for this protocol 0x0001

8-11
1 9.58.5 Default Key Exchange Protocol
2 9.5.18.5.1 Overview
3 The Default Key Exchange Protocol does not provide any services and is selected when the
4 Default Authentication Protocol and the Default Encryption Protocol are selected.
6 9.5.2.18.5.2.1 Commands

10 9.5.2.38.5.2.3 Public Data


14 This protocol does not carry payload on behalf of other layers or protocols.


8-12
2 9.5.5.18.5.5.1 Procedures

12 then
21 instance for the Key Exchange Protocol.
27
Field Length (bits)
MessageID 8
TransactionID 8
8-13
7
Field Length (bits)
MessageID 8
TransactionID 8

16
18 9.5.6.18.5.6.1 Procedures
19 There are no procedures associated with the InUse instance of this protocol.

8-14
2 9.5.6.3.18.5.6.3.1 Commands
4 9.5.6.3.28.5.6.3.2 Indications


9

NKEPType Type field for this protocol Table 2.5.4-1
NKEPDefault Subtype field for this protocol 0x0000

8-15
1 9.68.6 DH Key Exchange Protocol
2 9.6.18.6.1 Overview
3 The DH Key Exchange Protocol provides a method for session key exchange based on the
4 Diffie-Hellman (DH) key exchange algorithm.
6 9.6.2.18.6.2.1 Commands

9 This protocol does not return any indication.
10 9.6.2.38.6.2.3 Public Data

13 • FACAuthKey and its length
14 The authentication key for use on Forward Assigned Channels (e.g., the Forward Traffic
15 Channel).
16 • RACAuthKey and its length
17 The authentication key for use on Reverse Assigned Channels (e.g., the Reverse Traffic
18 Channel).
19 • FACEncKey and its length
20 The encryption key for use on Forward Assigned Channels (e.g., the Forward Traffic
21 Channel).
22 • RACEncKey and its length
23 The encryption key for use on Reverse Assigned Channels (e.g., the Reverse Traffic
24 Channel).
25 • FPCAuthKey and its length
26 The authentication key for use on Forward Public Channels (e.g., the Control Channel).
27 • RPCAuthKey and its length
28 The authentication key for use on Reverse Public Channels (e.g., the Access Channel).
29 • FPCEncKey and its length
30 The encryption key for use on Forward Public Channels (e.g. the Control Channel).
31 • RPCEncKey and its length
32 The encryption key for use on Reverse Public Channels (e.g. the Access Channel).
8-16
2 9.6.2.4.18.6.2.4.1 Commands
4 9.6.2.4.28.6.2.4.2 Indications


16 • The access terminal and the access network shall perform the following:
17 − Set SKey to zero and its length to the value of the KeyLength attribute,
18 − Set FACAuthKey to zero and its length to 160,
19 − Set RACAuthKey to zero and its length to 160,
20 − Set FACEncKey to zero and its length to 160,
21 − Set RACEncKey to zero and its length to 160,
22 − Set FPCAuthKey to zero and its length to 160,
23 − Set RPCAuthKey to zero and its length to 160,
24 − Set FPCEncKey to zero and its length to 160,
25 − Set RPCEncKey to zero and its length to 160.
27 InConfiguration protocol instance, then
28 − The access terminal and the access network shall set the fall-back values of
29 the attributes defined by the InConfiguration protocol instance to the values of
30 the corresponding attributes associated with the InUse protocol instance.
31 − The access terminal and the access network shall set the value of the public
32 data associated with the InConfiguration protocol instance to the
33 corresponding public data values for the InUse protocol.
8-17
4 9.6.5.18.6.5.1 Procedures
7 • If the access terminal and access network agree upon a different value for the
8 KeyLength attribute (per Generic Configuration Protocol), the access terminal and the
9 access network shall perform the following:
10 − Set SKey to zero and its length to the value of the KeyLength attribute,
11 − Set FACAuthKey to zero and its length to 160,
12 − Set RACAuthKey to zero and its length to 160,
13 − Set FACEncKey to zero and its length to 160,
14 − Set RACEncKey to zero and its length to 160,
15 − Set FPCAuthKey to zero and its length to 160,
16 − Set RPCAuthKey to zero and its length to 160,
17 − Set FPCEncKey to zero and its length to 160,
18 − Set RPCEncKey to zero and its length to 160.
19 The Key Exchange Protocol uses the KeyRequest and KeyResponse messages for
20 exchanging public session keys, and the ANKeyComplete and ATKeyComplete messages for
21 indicating that the secret session keys have been calculated.
22 The access terminal and the access network shall perform the following key exchange
23 procedure during session configuration.

25 Upon receiving the KeyRequest message, the access terminal shall perform the following:
26 • The access terminal shall choose a random number ATRand between 1 and p–2
27 (inclusive) and set the ATPubKey field of the KeyResponse message as follows:
28 ATPubKey = g ATRand mod p
29 where g and p are KeyLength dependent protocol constants for the DH Key
30 Exchange protocol, and KeyLength is specified during session configuration of the
31 DH Key Exchange Protocol.
32 • The access terminal shall send a KeyResponse message with the ATPubKey field set to
33 the value computed in the previous step, within TKEPATResponse second of receiving a
34 KeyRequest message.
35 • The access terminal shall compute SKey, the session key as follows:
8-18
1 SKey = ANPubKey ATRand mod p.

2 The random number ATRand should have the following properties:
3 • Number generated should have a uniform statistical distribution over its range,
4 • Numbers used in formulating different KeyResponse messages should be statistically
5 uncorrelated,
6 • Number used in formulating each KeyResponse message should not be derivable from
7 the previously used random numbers,
8 • Numbers used in formulating KeyResponse message sent by different access terminals
9 should be statistically uncorrelated.
10 After the access terminal sends a KeyResponse message, it shall set TKEPKeyCompAN to the
11 duration of time specified by Timeout, reported by the access network in the KeyRequest
12 message. The access terminal shall then start the AN Key Computation Timer with a time-
13 out value of TKEPKeyCompAN. The access terminal shall disable the AN Key Computation Timer
14 when it receives the ANKeyComplete message with a TransactionID that matches the
15 TransactionID field of the associated KeyRequest and KeyResponse messages.
16 When the AN Key Computation Timer expires, the access terminal shall declare failure.
17 After receiving an ANKeyComplete message with a TransactionID field that matches the
18 TransactionID field of the associated KeyRequest message, the access terminal shall
20 • Access terminal shall compute the 64-bit variable TimeStampLong as follows:
21 TimeStampLong = (SystemTime – (SystemTime[15:0] – TimeStampShort) mod 216)
22 mod 264,
23 where SystemTime is the current CDMA System Time in units of 80 ms,
24 SystemTime[15:0] is the 16 least significant bits of the SystemTime, and
25 TimeStampShort is the 16-bit field received in the ANKeyComplete message.
26 • Access terminal shall construct the message bits as shown in Table 8.6.5.1-1 using the
27 computed SKey, computed TimeStampLong, and TransactionID, and Nonce fields of the
28 ANKeyComplete message.
29 Table 8.6.5.1-1. Message Bits
Field Length(bits)
SKey KeyLength
TransactionID 8
Nonce 16
TimeStampLong 64
30 • Access terminal shall pad the message bits constructed in the previous step, as
31 specified in [6], and compute the 160-bit message digest as specified in [6].
8-19
1 • If the message digest computed in the previous step matches the KeySignature field of
2 ANKeyComplete message, the access terminal shall send an ATKeyComplete message
3 with the Result field set to ‘1’ within TKEPSigCompAT seconds of the later of the following
4 two events:
5 − Reception of the ANKeyComplete message.
6 − Finishing computing the SKey.
7 • Otherwise, the access terminal shall declare failure and send an ATKeyComplete
8 message with the Result field set to ‘0’.

10 The access network shall initiate the key exchange by sending a KeyRequest message. The
11 access network shall choose a random number ANRand between 1 and p–2 (inclusive) and
12 set the ANPubKey field of the KeyRequest message as follows:
13 ANPubKey = g ANRand mod p
14 where g, p, and KeyLength are specified during session configuration of the DH Key
15 Exchange Protocol.
16 The random number ANRand should have the following properties:
17 • The number generated should have a uniform statistical distribution over its range.
18 • The numbers used in formulating different KeyRequest messages should be statistically
19 uncorrelated.
20 • The number used in formulating each KeyRequest message should not be derivable
21 from the previously used random numbers.
22 • The numbers used in formulating KeyRequest message sent by different access
23 networks should be statistically uncorrelated.
24 If the access network does not receive a KeyResponse message with a TransactionID field
25 that matches the TransactionID field of the associated KeyRequest message, within
26 TKEPANResponse, the access network shall declare failure and stop performing the rest of the
27 key exchange procedure.
28 After receiving a KeyResponse message with a TransactionID field that matches the
29 TransactionID field of the associated KeyRequest message, the access network shall
31 • The access network shall set TKEPKeyCompAT to the duration of time specified by Timeout,
32 reported by the access terminal in the KeyResponse message. The access network shall
33 then start the AT Key Computation Timer with a time-out value of TKEPKeyCompAT.
34 • The access network shall compute SKey, the session key as follows:
35 SKey = ATPubKey ANRand mod p
8-20
1 • The access network shall construct the message bits, as shown in Table 8.6.5.1-2,
2 using the computed SKey, TimeStampLong, the TransactionID, and a 16-bit pseudo-
3 random value, Nonce. TimeStampLong is a 64-bit value that is set, based on the
4 current 64-bit representation of the CDMA System Time in units of 80 ms, such that
5 TimeStampLong does not specify a time later than the time that the message will be
6 transmitted by physical layer and is not earlier than the current CDMA System Time95.
7 Table 8.6.5.1-2. Message Bits
Field Length(bits)
SKey KeyLength
TransactionID 8
Nonce 16
TimeStampLong 64
8 • The access network shall pad the message bits constructed in the previous step, as
9 specified in [6], and compute the 160-bit message digest as specified in [6].
10 • The access network shall send an ANKeyComplete message with the KeySignature field
11 of the message set to the message digest computed in the previous step and the
12 TimeStampShort field of the message set to the 16 least significant bits of the CDMA
13 System Time used in the previous step. The access network shall then start the AT
14 Signature Computation Timer with a time-out value of TKEPSigCompAN.
15 The access network shall disable both the AT Key Computation Timer and the AT Key
16 Signature Computation Timer when it receives an ATKeyComplete message with a
17 TransactionID that matches the TransactionID field of the associated KeyRequest and
18 KeyResponse messages.
19 The access network shall declare failure and stop performing the rest of the key exchange
20 procedure if any of the following events occur:
21 • Both AT Key Computation and the AT Key Signature Computation Timers are expired,
22 or
23 • Access network receives an ATKeyComplete message with Result field set to ‘0’.
24 9.6.5.1.38.6.5.1.3 Authentication Key and Encryption Key Generation

25 The keys used for authentication and encryption are generated from the session key, SKey,
26 using the procedures specified in this section.
27 Table 8.6.5.1-3 defines eight sub-fields within the SKey. These sub-fields are of equal
28 length.
95 For example, the protocol may choose the current CDMA System Time as TimeStampLong.
8-21
1 Table 8.6.5.1-3. Subfields of SKey
K0 KeyLength / 8
K1 KeyLength / 8
K2 KeyLength / 8
K3 KeyLength / 8
K4 KeyLength / 8
K5 KeyLength / 8
K6 KeyLength / 8
K7 KeyLength / 8
2 The access network and the access terminal shall construct the message bits as shown in
3 Figure 8.6.5.1-1. In this figure, TimeStampLong and Nonce are the same as the one used
4 for generation of KeySignature (see 8.6.5.1.1, and 8.6.5.1.2).
5
MSB LSB
Message bits for K0 Nonce TimeStampLong
generation of
(KeyLength / 8) (16 bits) (64 bits)
FACAuthKey
generation of
RACAuthKey
generation of
FACEncKey
generation of
RACEncKey
generation of
FPCAuthKey
generation of
RPCAuthKey
generation of
FPCEncKey
generation of
RPCEncKey
6 Figure 8.6.5.1-1. Message Bits for Generation of Authentication and Encryption Keys
8-22
1 The access terminal and access network shall then pad the message bits constructed in the
2 previous step, as specified in [6], and compute the 160-bit message digests (for each of the
3 eight keys) as specified in [6]. The access network and the access terminal shall set the
4 FACAuthKey, RACAuthKey, FACEncKey, RACEncKey, FPCAuthKey, RPCAuthKey,
5 FPCEncKey, and RPCEncKey to the message digests for the corresponding key as shown in
6 Figure 8.6.5.1-1.

13 • The value of the following public data of the InUse protocol instance shall be set to the
14 value of the corresponding public data of the InConfiguration protocol instance:
15 − FACAuthKey and its length
16 − RACAuthKey and its length
17 − FACEncKey and its length
18 − RACEncKey and its length
19 − FPCAuthKey and its length
20 − RPCAuthKey and its length
21 − FPCEncKey and its length
22 − RPCEncKey and its length
24 then
27 associated with the InConfiguration instance of this protocol,
33 instance for the Key Exchange Protocol.
8-23
2 9.6.5.3.18.6.5.3.1 KeyRequest
3 The access network sends the KeyRequest message to initiate the session key exchange.
4
Field Length (bits)
MessageID 8
TransactionID 8
Timeout 8
ANPubKey KeyLength
(as negotiated)
7 KeyRequest message sent.
8 Timeout Shared secret calculation timeout. The access network shall set this
9 field to the maximum time in the number of seconds that the access
10 network requires for calculation of the session key (SKey).
11 ANPubKey Access network’s ephemeral public Diffie-Hellman key. The access

12 network shall set this field to the ephemeral public Diffie-Hellman
13 key of the access network as specified in 8.6.5.1.2.
14
15 9.6.5.3.28.6.5.3.2 KeyResponse
16 The access terminal sends the KeyResponse message in response to the KeyRequest
17 message.
18
Field Length (bits)
MessageID 8
TransactionID 8
Timeout 8
ATPubKey KeyLength (as negotiated)
8-24
1 TransactionID The access terminal shall set this field to the value of the
2 TransactionID field of the KeyRequest message to which the access
3 terminal is responding.
4 Timeout Shared secret calculation timeout. The access terminal shall set this
5 field to the maximum time in seconds that the access terminal
6 requires for calculation of the session key (SKey).
7 ATPubKey Access terminal’s ephemeral public Diffie-Hellman key. The access

8 terminal shall set this field to the ephemeral public Diffie-Hellman
9 key of the access terminal as specified in 8.6.5.1.1.
10
11 9.6.5.3.38.6.5.3.3 ANKeyComplete
12 The access network sends the ANKeyComplete message in response to the KeyResponse
13 message.
14
Field Length (bits)
MessageID 8
TransactionID 8
Nonce 16
TimeStampShort 16
KeySignature 160
16 TransactionID The access network shall set this field to the value of the
17 TransactionID field of the corresponding KeyRequest message.
18 Nonce The access network shall set this field to an arbitrarily chosen 16-bit
19 value Nonce that is used to compute the KeySignature.
20 TimeStampShort The access network shall set this field to the 16 least significant bits
21 of the TimeStampLong used in computing the KeySignature as
22 specified in 8.6.5.1.2.
23 KeySignature The access network shall set this field to the 20-octet signature of the
24 session key (SKey) as specified in 8.6.5.1.2.
25
8-25
1 9.6.5.3.48.6.5.3.4 ATKeyComplete
2 The access terminal sends the ATKeyComplete message in response to the ANKeyComplete
3 message.
4
Field Length (bits)
MessageID 8
TransactionID 8
Result 1
Reserved 7
6 TransactionID The access terminal shall set this field to the value of the
7 TransactionID field of the corresponding KeyRequest message.
8 Result The access terminal shall set this field to ‘1’ if the KeySignature field
9 of ANKeyComplete message matches the message digest computed
10 for the KeySignature as specified in 8.6.5.1.1; otherwise the access
14
17
Field Length (bits)
MessageID 8
TransactionID 8
8-26
7
Field Length (bits)
MessageID 8
TransactionID 8

16
18 9.6.6.18.6.6.1 Procedures
19 There are no procedures associated with the InUse instance of this protocol.

8-27
2 9.6.6.3.18.6.6.3.1 Commands
4 9.6.6.3.28.6.6.3.2 Indications

7 The configurable simple attribute for this protocol is listed in Table 8.6.7-1.
8 The access terminal shall use as defaults the values in Table 8.6.7-1 that are typed in bold
9 italics.

ID
0x00 Default is 96-octet (768-bit)
Diffie-Hellman key.
KeyLength = 768
0x01 128-octet (1024-bit) Diffie-
0x00 Session Key Length (KeyLength)
Hellman key.
KeyLength = 1024
0x02- Reserved
0xff

12

NKEPType Type field for this protocol Table 2.5.4-1
NKEPDH Subtype field for this protocol 0x0001
TKEPSigCompAN Time to receive ATKeyComplete after 3.5 seconds
sending ANKeyComplete
TKEPSigCompAT Time to send ATKeyComplete after 3 seconds
receiving ANKeyComplete
TKEPANResponse Time to receive KeyResponse after 3.5 seconds
sending KeyRequest
TKEPATResponse Time to send KeyResponse after 3 second
receiving KeyRequest
13
8-28
1 Table 8.6.6.3-1. Common Primitive Base and Common Prime Modulus for KeyLength
2 equal to 76896

g Common primitive base 0x02
p 0xFFFFFFFF 0xFFFFFFFF 0xC90FDAA2
0x2168C234 0xC4C6628B 0x80DC1CD1
0x29024E08 0x8A67CC74 0x020BBEA6
Common prime modulus 0x3B139B22 0x514A0879 0x8E3404DD
(MSB first) 0xEF9519B3 0xCD3A431B 0x302B0A6D
0xF25F1437 0x4FE1356D 0x6D51C245
0xE485B576 0x625E7EC6 0xF44C42E9
0xA63A3620 0xFFFFFFFF 0xFFFFFFFF
3 Table 8.6.6.3-2. Common Primitive Base and Common Prime Modulus for KeyLength
4 equal to 1024

g Common primitive base 0x02
p 0xFFFFFFFF 0xFFFFFFFF 0xC90FDAA2
0x2168C234 0xC4C6628B 0x80DC1CD1
0x29024E08 0x8A67CC74 0x020BBEA6
0x3B139B22 0x514A0879 0x8E3404DD
Common prime modulus 0xEF9519B3 0xCD3A431B 0x302B0A6D
0xF25F1437 0x4FE1356D 0x6D51C245
(MSB first) 0xE485B576 0x625E7EC6 0xF44C42E9
0xA637ED6B 0x0BFF5CB6 0xF406B7ED
0xEE386BFB 0x5A899FA5 0xAE9F2411
0x7C4B1FE6 0x49286651 0xECE65381
0xFFFFFFFF 0xFFFFFFFF
5 9.6.98.6.9 Message Flows

6 Figure 8.6.9-1 shows an example flow diagram in which the access network quickly
7 computes the Key and the signature and sends it to the access terminal. The access
8 terminal still needs time to finish the Key calculation. In this case the AT Signature
9 Computation Timer expires, but the AT Key Computation Timer does not expire.
96 The values for p and g are taken from [7].
8-29
AN AT
KeyRequest(TKEPKeyCompAN)
KeyResponse(TKEPKeyCompAT)
TKEPKeyCompAN
ANKeyComplete(KeySignature)
TKEPSigCompAN
TKEPKeyCompAT
y AT has finished
computing the Key
y AT starts
verifying the
signature
ATKeyComplete
2 Figure 8.6.9-1. Example Call Flow: Timer TKEPSigCompAN Expires But TKEPKeyCompAT Does
3 Not Expire
4 Figure 8.6.9-2 shows an example flow diagram in which the access network requires a
5 longer period of time to compute the Key. In this case the AT Key Computation Timer
6 expires, but the AT Signature Computation Timer does not expire.
8-30
AN AT
KeyRequest(TKEPKeyCompAN)
KeyResponse(TKEPKeyCompAT)
TKEPKeyCompAN
TKEPKeyCompAT
AT has finished
computing the
Key
ANKeyComplete(KeySignature)
AT starts
TKEPSigCompAN verifying the
signature
ATKeyComplete
2 Figure 8.6.9-2. Example Call Flow: Timer TKEPSigCompAN Does Not Expire But
3 TKEPKeyCompAT Expires

8 9.6.10.18.6.10.1 SKey Parameter
9 Table 8.6.10.1-1. The Format of the Parameter Record for the SKey Parameter
Field Length (bits)
ParameterType 8
Length 8
SKey 8 × (Length – 1)
8-31
1 SKey This field shall be set to the value of the SKey associated with the
2 access terminal’s session.
3 9.6.10.28.6.10.2 FACAuthKey Parameter
4 Table 8.6.10.2-1. The Format of the Parameter Record for the FACAuthKey
5 Parameter
Field Length (bits)
ParameterType 8
Length 8
FACAuthKey 8 × (Length – 1)
9 FACAuthKey This field shall be set to the value of the FACAuthKey associated with
11 9.6.10.38.6.10.3 RACAuthKey Parameter
12 Table 8.6.10.3-1. The Format of the Parameter Record for the RACAuthKey
13 Parameter
Field Length (bits)
ParameterType 8
Length 8
RACAuthKey 8 × (Length – 1)
17 RACAuthKey This field shall be set to the value of the RACAuthKey associated with
8-32
1 9.6.10.48.6.10.4 FACEncKey Parameter
2 Table 8.6.10.4-1. The Format of the Parameter Record for the FACEncKey Parameter
Field Length (bits)
ParameterType 8
Length 8
FACEncKey 8 × (Length – 1)
6 FACEncKey This field shall be set to the value of the FACEncKey associated with
8 9.6.10.58.6.10.5 RACEncKey Parameter
9 Table 8.6.10.5-1. The Format of the Parameter Record for the RACEncKey Parameter
Field Length (bits)
ParameterType 8
Length 8
RACEncKey 8 × (Length – 1)
13 RACEncKey This field shall be set to the value of the RACEncKey associated with
15 9.6.10.68.6.10.6 FPCAuthKey Parameter
16 Table 8.6.10.6-1. The Format of the Parameter Record for the FPCAuthKey
17 Parameter
Field Length (bits)
ParameterType 8
Length 8
FPCAuthKey 8 × (Length – 1)
8-33
3 FPCAuthKey This field shall be set to the value of the FPCAuthKey associated with
5 9.6.10.78.6.10.7 RPCAuthKey Parameter
6 Table 8.6.10.7-1. The Format of the Parameter Record for the RPCAuthKey
7 Parameter
Field Length (bits)
ParameterType 8
Length 8
RPCAuthKey 8 × (Length – 1)
11 RPCAuthKey This field shall be set to the value of the RPCAuthKey associated with
13 9.6.10.88.6.10.8 FPCEncKey Parameter
14 Table 8.6.10.8-1. The Format of the Parameter Record for the FPCEncKey Parameter
Field Length (bits)
ParameterType 8
Length 8
FPCEncKey 8 × (Length – 1)
18 FPCEncKey This field shall be set to the value of the FPCEncKey associated with
8-34
1 9.6.10.98.6.10.9 RPCEncKey Parameter
2 Table 8.6.10.9-1. The Format of the Parameter Record for the RPCEncKey Parameter
Field Length (bits)
ParameterType 8
Length 8
RPCEncKey 8 × (Length – 1)
6 RPCEncKey This field shall be set to the value of the RPCEncKey associated with
8-35
1 9.78.7 Default Authentication Protocol
2 9.7.18.7.1 Overview
3 The Default Authentication Protocol does not provide any services except for transferring
4 packets between the Encryption Protocol and the Security Protocol.
6 9.7.2.18.7.2.1 Commands

10 9.7.2.38.7.2.3 Public Data


14 The protocol data unit for this protocol is an Authentication Protocol packet.


8-36
2 9.7.5.18.7.5.1 Procedures

12 then
22 instance for the Authentication Protocol.
28
Field Length (bits)
MessageID 8
TransactionID 8
8-37
7
Field Length (bits)
MessageID 8
TransactionID 8

16
18 9.7.6.18.7.6.1 Procedures
19 When this protocol receives Encryption Protocol packets, it shall forward them to the
20 Security Protocol.
21 When the protocol receives a Security Protocol packet from the Security Protocol, it shall
22 set the Encryption Protocol packet to the Authentication Protocol packet and shall forward
23 the Encryption Protocol packet to the Encryption Protocol.
8-38
1 9.7.6.28.7.6.2 Default Authentication Protocol Header

2 The Default Authentication Protocol does not add a header.
3 9.7.6.38.7.6.3 Default Authentication Protocol Trailer

4 The Default Authentication Protocol does not add a trailer.

8 9.7.6.5.18.7.6.5.1 Commands
10 9.7.6.5.28.7.6.5.2 Indications


15

NAPType Type field for this protocol Table 2.5.4-1
NAPDefault Subtype field for this protocol 0x0000

8-39
1 9.88.8 SHA-1 Authentication Protocol
2 9.8.18.8.1 Overview
3 The SHA-1 Authentication Protocol provides a method for authentication of the Access
4 Channel MAC Layer packets by applying the SHA-1 hash function to message bits that are
5 composed of the ACAuthKey, security layer payload, CDMA System Time, and the sector
6 ID.
8 9.8.2.18.8.2.1 Commands

11 This protocol returns the following indication:
12 • Failed
13 9.8.2.38.8.2.3 Public Data


17 The protocol data unit for this protocol is an Authentication Protocol packet.

8-40
2 9.8.5.18.8.5.1 Procedures

12 then
21 instance for the Authentication Protocol.
27
Field Length (bits)
MessageID 8
TransactionID 8
8-41
7
Field Length (bits)
MessageID 8
TransactionID 8

16
18 9.8.6.18.8.6.1 Procedures
19 This protocol receives Encryption Protocol Packets and adds the authentication layer
20 header defined in 8.8.6.1.2 in front of each Access Channel Encryption Protocol Packet to
21 make an Access Channel Authentication Protocol Packet and forwards it to the Security
22 protocol.
8-42
1 When the protocol receives Access Channel Security protocol packets from the Security
2 protocol, it constructs the Encryption Protocol Packet by removing the Authentication
3 Protocol Header, and forwards the Encryption Protocol Packet to the Encryption Protocol.
4 The procedures in 8.8.6.1.2 and 8.8.6.1.1 shall apply to packets carried by the Access
5 Channel. For all other packets, the protocol shall perform the following:
6 • When this protocol receives Encryption Protocol packets, it shall forward them to the
7 Security Protocol.
8 • When the protocol receives a Security Protocol packet from the Security Protocol, it
9 shall set the Encryption Protocol packet to the Authentication Protocol packet and shall
10 forward the Encryption Protocol packet to the Encryption Protocol.

12 Upon reception of an Encryption Protocol packet destined for the Access Channel, the
13 access terminal shall compute ACPAC as follows:
14 • The access terminal shall construct the ACAuthKey as follows:
15 − If the Key Exchange Protocol does not define RPCAuthKey as public data, the
16 access terminal shall set ACAuthKey to zero of length specified by
17 ACAuthKeyLength.
18 − Otherwise, the access terminal shall perform the following:
19 + If the length of RPCAuthKey is equal to the length of ACAuthKey, then
20 ACAuthKey shall be RPCAuthKey.
21 + Otherwise, if the length of RPCAuthKey is greater than the length of
22 ACAuthKey, then ACAuthKey shall be the ACAuthKeyLength least significant
23 bits of RPCAuthKey.
24 + Otherwise, if the length of RPCAuthKey is less than the length of ACAuthKey,
25 then ACAuthKey shall be the concatenation of zeros at the end (LSB) of
26 RPCAuthKey, such that the length of the result is ACAuthKeyLength.
27 • The access terminal shall construct the Cryptosync as follows:
28 − If the Security Protocol does not define Cryptosync as its public data, then the
29 access terminal shall set the Cryptosync field used in Table 8.8.6.1-1 to zero.
30 Otherwise, this protocol shall use the value of the Cryptosync given as public
31 data by the Security Protocol.
32 − If the Security Protocol does not define CryptosyncLength as its public data,
33 then the access terminal shall set the CryptosyncLength field used in Table
34 8.8.6.1-1 to 64. Otherwise, this protocol shall use the value of the
35 CryptosyncLength given as public data by the Security Protocol.
36 • The access terminal shall construct the message bits for computing ACPAC as shown in
37 Table 8.8.6.1-1:
38
8-43
1 Table 8.8.6.1-1. Message Bits for ACPAC Computation
Field Length(bits)
ACAuthKey ACAuthKeyLength
Authentication Protocol variable
Payload
SectorID 128
Cryptosync CryptosyncLength
2 where SectorID is provided as public data by the Overhead Messages Protocol.

3 • The access terminal shall pad the message bits constructed in the previous step, as
4 specified in [6], and compute the 160-bit message digest as specified in [6] and set the
5 ACPAC field to the 64 least significant bits of the message digest.

7 Upon reception of an Authentication Protocol packet from the Access Channel, the access
8 network shall compute and verify the Access Channel MAC Layer packet authentication
9 code (ACPAC) given in the authentication protocol header as follows:
10 • The access network shall construct the ACAuthKey as follows:
11 − If the Key Exchange Protocol does not define RPCAuthKey as public data, the
12 access network shall set ACAuthKey to zero of length specified by
13 ACAuthKeyLength.
14 − Otherwise, the access network shall perform the following:
15 + If the length of RPCAuthKey is equal to the length of ACAuthKey, then
16 ACAuthKey shall be RPCAuthKey.
17 + Otherwise, if the length of RPCAuthKey is greater than the length of
18 ACAuthKey, then ACAuthKey shall be the ACAuthKeyLength least significant
19 bits of RPCAuthKey.
20 + Otherwise, if the length of RPCAuthKey is less than the length of ACAuthKey,
21 then ACAuthKey shall be set to RPCAuthKey with zeros concatenated to the
22 end (LSB) of it, such that the length of the result is ACAuthKeyLength.
23 • The access network shall construct the Cryptosync as follows:
24 − If the Security Protocol does not define Cryptosync as its public data, then the
25 access network shall set the Cryptosync field used in Table 8.8.6.1-2 to zero.
26 Otherwise, this protocol shall use the value of the Cryptosync given as public
27 data by the Security Protocol.
28 − If the Security Protocol does not define CryptosyncLength as its public data,
29 then the access network shall set the CryptosyncLength field used in Table
30 8.8.6.1-2 to 64. Otherwise, this protocol shall use the value of the
31 CryptosyncLength given as public data by the Security Protocol.
8-44
1 • The access network shall construct the message bits for computing ACPAC as shown in
2 Table 8.8.6.1-2:
3 Table 8.8.6.1-2. Message Bits for ACPAC Computation
Field Length(bits)
ACAuthKey ACAuthKeyLength
Authentication Protocol variable
Payload
SectorID 128
Cryptosync CryptosyncLength
4 where SectorID is provided as public data by the Overhead Messages protocol.

5 • The access network shall pad the message bits constructed in the previous step, as
6 specified in [6], and compute the 160-bit message digest as specified in [6] and set
7 ACPAC to the 64 least significant bits of the message digest.
8 If the ACPAC computed in the previous step matches the ACPAC field in the Protocol
9 Header, then the Protocol shall deliver the Authentication Layer Payload to the Encryption
10 Protocol. Otherwise, the Protocol shall issue a Failed indication and shall discard the
11 security layer packet.
12 9.8.6.28.8.6.2 SHA-1 Authentication Protocol Header Format

13 The SHA-1 Authentication Protocol Header is as follows:
14
Field Length(bits)
ACPAC 0 or 64
15 ACPAC Access Channel Packet Authentication Code. The access terminal

16 shall include this field for Encryption Protocol packets transmitted on
17 the Access Channel. Otherwise, the access terminal shall omit this
18 field. If included, the access terminal shall compute this field as
19 specified in 8.8.6.1.1. The access network shall omit this field.
20 9.8.6.38.8.6.3 SHA-1 Authentication Protocol Trailer

21 The SHA-1 Authentication Protocol does not add a trailer.
22 9.8.78.8.7 Interface to Other Protocols
23 9.8.7.18.8.7.1 Commands
25 9.8.7.28.8.7.2 Indications
8-45

2 The configurable simple attributes for this protocol are listed in Table 8.8.8-1.
3 The access terminal shall use as defaults the values in Table 8.8.8-1 that are typed in bold
4 italics.

ID
0x00A0 Default value for the
authentication key length in
bits.
0x00 ACAuthKeyLength
0x0000 – Access Channel authentication
key length in bits.
0xFFFF

7

NAPType Type field for this protocol Table 2.5.4-1
NAPSHA1 Subtype field for this protocol 0x0001

11 protocol.
8-46
1 9.98.9 Default Encryption Protocol

2 The Default Encryption Protocol does not alter the Security Layer packet payload (i.e., no
3 encryption/decryption) and does not add an Encryption Protocol Header or Trailer;
4 therefore, the Cipher-text for this protocol is equal to the Connection Layer packet. If
5 needed, end-to-end encryption can be provided at the application layer (which is outside
6 the scope of this specification).
8 9.9.1.18.9.1.1 Commands

12 9.9.1.38.9.1.3 Public Data


16 The protocol data unit for this protocol is an Encryption Protocol Packet.


8-47
2 9.9.4.18.9.4.1 Procedures

12 then
22 instance for the Encryption Protocol.
28
Field Length (bits)
MessageID 8
TransactionID 8
8-48
7
Field Length (bits)
MessageID 8
TransactionID 8

16
18 9.9.5.18.9.5.1 Procedures
19 The protocol shall set the Encryption Protocol Packet to the Connection Layer packet.

8-49
1 9.9.5.38.9.5.3 Default Encryption Protocol Header

2 The Default Encryption Protocol does not add a header.
3 9.9.5.48.9.5.4 Default Encryption Protocol Trailer

4 The Default Encryption Protocol does not add a trailer.
6 9.9.5.5.18.9.5.5.1 Commands
8 9.9.5.5.28.9.5.5.2 Indications


13

NEPType Type field for this protocol Table 2.5.4-1
NEPDefault Subtype field for this protocol 0x0000

17
8-50
MAC Layer 3GPP2 C.S0024-B v2.0
1 109 MAC LAYER

4 The MAC Layer contains the rules governing operation of the Control Channel, the Access
5 Channel, the Forward Traffic Channel, and the Reverse Traffic Channel.
6 This section presents the protocols for the MAC Layer. Each of these protocols can be
7 independently negotiated at the beginning of the session.
8 The MAC Layer contains the following protocols:
9 • Control Channel MAC Protocol: This protocol builds Control Channel MAC Layer
10 packets out of one or more Security Layer packets, contains the rules concerning
11 access network transmission and packet scheduling on the Control Channel, access
12 terminal acquisition of the Control Channel, and access terminal Control Channel MAC
13 Layer packet reception. This protocol also adds the access terminal address to
14 transmitted packets.
15 • Access Channel MAC Protocol: This protocol contains the rules governing access
16 terminal transmission timing and power characteristics for the Access Channel.
17 • Forward Traffic Channel MAC Protocol: This protocol contains the rules governing
18 operation of the Forward Traffic Channel. It dictates the rules the access terminal
19 follows when transmitting the Data Rate Control Channel, along with the rules the
20 access network uses to interpret this channel. The protocol supports both variable rate
21 and fixed rate operation of the Forward Traffic Channel.
22 • Reverse Traffic Channel MAC Protocol: This protocol contains the rules governing
23 operation of the Reverse Traffic Channel. It dictates the rules the access terminal
24 follows to assist the access network in acquiring the Reverse Traffic Channel. It also
25 indicates the rules the access terminal and the access network use to select the
26 transmission rate used over the Reverse Traffic Channel.
27 10.1.29.1.2 Data Encapsulation for the InUse Instances of the MAC Protocols
28 In the transmit direction, the MAC Layer receives Security Layer packets, adds layer-
29 related headers, trailers, concatenates them in the order to be processed on the receive
30 side, adds padding where applicable, and forwards the resulting packet for transmission to
31 the Physical Layer.
32 In the receive direction, the MAC Layer receives MAC packets from the Physical Layer and
33 forwards the contained Security Layer packets to the Security Layer in the order received
34 after removing the layer-related headers, trailers, and padding.
35 Figure 9.1.2-1, Figure 9.1.2-2, Figure 9.1.2-3, and Figure 9.1.2-4 illustrate the relationship
36 between Security Layer packets, MAC packets and Physical Layer packets for the Control
37 Channel, the Access Channel, and the Forward and Reverse Traffic Channels.
9-1
3GPP2 C.S0024-B v2.0 MAC Layer
Security Security
Layer Layer
packet packet
MAC MAC MAC MAC MAC

CC
Layer Layer Layer Layer Layer pad reserved
header
packet header payload header payload
MAC MAC
Layer Layer
packet packet
MAC MAC MAC

Layer Layer Layer
capsule packet packet
Physical Physical
Layer Layer
payload payload
1
2 Figure 9.1.2-1. Control Channel MAC Layer Packet Encapsulation
Security
Layer
packet
MAC MAC MAC

Layer Layer Layer FCS pad
capsule header payload
MAC MAC MAC

Layer Layer reserved ... Layer reserved
packets capsule fragment capsule fragment
Physical Physical
Layer ... Layer
payload payload
3
4 Figure 9.1.2-2. Access Channel MAC Layer Packet Encapsulation
9-2
Security Security
Layer Layer
packet packet
MAC MAC MAC

MAC Layer
Layer Layer Layer
trailer
Physical
Layer
payload
2
3 Figure 9.1.2-3. Forward Traffic Channel MAC Layer Packet Encapsulation
Security
Layer
packet
MAC MAC MAC

Layer Layer Layer
packet payload trailer
Physical
Layer
payload
5
6 Figure 9.1.2-4. Reverse Traffic Channel MAC Layer Packet Encapsulation
9-3
1 10.29.2 Default Control Channel MAC Protocol
2 10.2.19.2.1 Overview
3 The Default Control Channel MAC Protocol provides the procedures and messages required
4 for an access network to transmit and for an access terminal to receive the Control
5 Channel. This protocol operates with the Default (Subtype 0) Physical Layer Protocol, the
6 Subtype 1 Physical Layer Protocol, the Subtype 2 Physical Layer Protocol, or the Subtype 3
7 Physical Layer Protocol.
8 This specification assumes that the access network has one instance of this protocol for all
9 access terminals.
11 • Inactive State: in this state the protocol waits for an Activate command. This state
12 applies only to the access terminal and occurs when the access terminal has not
13 acquired an access network or is not monitoring the Control Channel.
14 • Active State: in this state the access network transmits and the access terminal
15 receives the Control Channel.
Initial State
Rx Activate
(AT Only)
Rx Deactivate
16
(AT only)
17 Figure 9.2.1-1. Default (Subtype 0) Control Channel MAC Protocol State Diagram
19 10.2.2.19.2.2.1 Commands
21 • Activate.
22 • Deactivate.

9-4
1 • Interrupted
2 10.2.2.39.2.2.3 Public Data

5 • Offset field of the Control Channel Header of the first Control Channel MAC Layer
6 packet of a synchronous capsule.

8 The transmission unit of this protocol is the Control Channel MAC Layer packet.


29 10.2.5.19.2.5.1 Procedures
9-5

8 then
17 − The access terminal shall set the initial state for the InConfiguration instance
18 of this protocol to the Active State.
19 − The access network shall set the initial state for the InConfiguration instance
22 instance for the Control Channel MAC Protocol.
28
Field Length (bits)
MessageID 8
TransactionID 8
9-6
7
Field Length (bits)
MessageID 8
TransactionID 8

16
18 10.2.6.19.2.6.1 Procedures
19 Each Control Channel MAC Layer packet consists of zero or more Security Layer packets
20 for zero or more access terminals.
21 The protocol constructs a packet out of the Security Layer packets, as follows:
22 • The protocol adds the MAC Layer header specified in 9.2.6.2.1 in front of every Security
23 Layer packet.
9-7
1 • The protocol concatenates the Control Channel Header specified in 9.2.6.2.2 followed
2 by the above formed packets.
3 • The protocol pads the resulting packet as defined in 9.2.6.2.3.
4 • The protocol adds the reserved bits as defined in 9.2.6.2.4.
5 The protocol then sends the packet for transmission to the Physical Layer. The packet
6 structure is shown in Figure 9.2.6-1.
7 Control Channel MAC Layer packets can be transmitted in a synchronous capsule that is
8 transmitted at a particular time, in a sub-synchronous capsule that is transmitted at a
9 particular time, or in an asynchronous capsule that can be transmitted at any time except
10 when a synchronous or sub-synchronous capsule is transmitted. A synchronous capsule
11 consists of one or more Control Channel MAC Layer packets.
12 A Control Channel Synchronous Sleep State capsule constitutes the Control Channel MAC
13 Layer packets of a Control Channel synchronous capsule starting from the beginning of a
14 synchronous capsule up to and including the first MAC Layer packet for which the
15 SleepStateCapsuleDone bit in the Control Channel header is set to ‘1’.
16 A sub-synchronous capsule consists of one Control Channel MAC Layer packet. An
17 asynchronous capsule consists of one Control Channel MAC Layer packet.
18 This protocol expects an address and a parameter indicating transmission in a
19 synchronous capsule, synchronous Sleep State capsule, sub-synchronous capsule, or an
20 asynchronous capsule with each transmitted Security Layer packet. For Security Layer
21 packets that are carried by an asynchronous capsule or by a sub-synchronous capsule,
22 this protocol can also receive an optional parameter indicating a transmission deadline.
MAC Layer packet
MAC Security MAC Security

CC
Layer Layer Layer Layer pad reserved
header
23
24 Figure 9.2.6-1. Control Channel MAC Packet Structure
25 Received packets are parsed into their constituent Security Layer packets. The packets that
26 are addressed to the access terminal (see 9.2.6.1.4.2.4) are then forwarded for further
27 processing to the Security Layer.

30 10.2.6.1.1.19.2.6.1.1.1 Activate
31 If this protocol receives an Activate command in the Inactive State, the access terminal
32 shall transition to the Active State
33 If this protocol receives this command in the Active State it shall be ignored.
9-8
1 10.2.6.1.1.29.2.6.1.1.2 Deactivate
3 If this protocol receives this command in the Active State, the access terminal shall
4 generate an Interrupted indication and transition to the Inactive State
5 10.2.6.1.29.2.6.1.2 Control Channel Cycle

6 The Control Channel cycle is defined as a 256 slot period, synchronous with CDMA System
7 Time; i.e., there is an integer multiple of 256 slots between the beginning of a cycle and the
8 beginning of CDMA System Time.
9 10.2.6.1.39.2.6.1.3 Inactive State

10 This state applies only to the access terminal.
11 When the protocol is in the Inactive State, the access terminal waits for an Activate
12 command.
13 10.2.6.1.49.2.6.1.4 Active State

14 In this state, the access network transmits, and the access terminal monitors the Control
15 Channel.

18 The access network shall always have one instance of this protocol operating per sector.
19 When the access network transmits the Control Channel, it shall do so using a rate of 38.4
20 kbps or 76.8 kbps.
21 The access network shall transmit synchronous capsules and it may transmit sub-
22 synchronous capsules and asynchronous capsules. When the access network transmits
23 synchronous capsules, it shall comply with 9.2.6.1.4.1.2. When the access network
24 transmits sub-synchronous capsules, it shall comply with 9.2.6.1.4.1.4. When the access
25 network transmits asynchronous capsules, it shall comply with 9.2.6.1.4.1.3.
26 The timing of synchronous, sub-synchronous, and asynchronous capsules is shown in
27 Figure 9.2.6.1.4.1-1.
9-9
2 Figure 9.2.6.1.4.1-1. Location of Control Channel Capsules
3 10.2.6.1.4.1.29.2.6.1.4.1.2 Transmission of Synchronous Capsules

4 The access network shall construct a synchronous capsule out of all the pending Security
5 Layer packets that are destined for transmission in a synchronous capsule. The
6 synchronous capsule may contain more than one Control Channel MAC Layer packet. The
7 access network shall transmit exactly one synchronous control channel capsule per sector
8 during each control channel cycle.
9 The access network shall set the SynchronousCapsule bit of the Control Channel Header to
10 ‘1’ for the Control Channel MAC Layer packet of a synchronous capsule.
11 The access network shall set the LastPacket bit of the Control Channel Header to ‘1’ only
12 for the last Control Channel MAC Layer packet of a synchronous capsule.
13 The access network shall set the FirstPacket bit of the Control Channel Header to ‘1’ only
14 for the first Control Channel MAC Layer packet of the Control Channel synchronous
15 capsule.
16 The access network shall set the SleepStateCapsuleDone bit of the Control Channel header
17 to ‘0’ if the MAC Layer packet belongs to the Control Channel synchronous Sleep State
18 capsule and the MAC Layer packet is not the last packet in the Control Channel
19 synchronous Sleep State capsule.
20 The access network shall set the Offset field of the Control Channel Header of the first
21 Control Channel MAC Layer packet of a synchronous capsule to the offset in slots of the
22 synchronous Control Channel capsule relative to the Control Channel Cycle. If the access
23 network has no pending Security Layer packets, it shall transmit a synchronous capsule
24 with one Control Channel MAC Layer packet containing only the Control Channel header.
25 The access network shall transmit the Control Channel MAC Layer packets of a
26 synchronous capsule as follows:
27 • The first MAC Layer packet shall start transmission at times T where T satisfies the
28 following equation:
29 T mod 256 = Offset.
9-10
1 • All other MAC Layer packets of the capsule shall start transmission at the earliest time
2 T following the end of transmission of the previous packet of the capsule that satisfies
3 the following equation:
4 T mod 4 = Offset,
5 where T is CDMA System Time in slots and Offset is the value specified in the Control
6 Channel header of the first Control Channel MAC Layer packet of the synchronous capsule.
7 10.2.6.1.4.1.39.2.6.1.4.1.3 Transmission of Asynchronous Capsules

8 The access network may transmit asynchronous capsules at any time during the Control
9 Channel cycle in which it does not transmit a synchronous capsule or a sub-synchronous
10 capsule. If the access network has queued Security Layer packets that are marked for
11 transmission in an asynchronous capsule, it should transmit the packets no later than
12 their associated transmission deadline, if one was provided. The access network may:
13 • Transmit these packets in a synchronous capsule.
14 • Transmit these packets in a sub-synchronous capsule.
15 • Transmit these packets in an asynchronous capsule.
17 ‘0’ for the Control Channel MAC Layer packet of an asynchronous capsule.
18 The access network shall set the FirstPacket and LastPacket bits of the Control Channel
19 Header to ‘1’ for the Control Channel MAC Layer packet of an asynchronous capsule.
20 The access network shall set the Offset field of the Control Channel Header to ‘00’ for the
21 Control Channel MAC Layer packet of an asynchronous capsule.
22 10.2.6.1.4.1.49.2.6.1.4.1.4 Transmission of Sub-synchronous Capsules

23 The access network shall construct a sub-synchronous capsule out of pending Security
24 Layer packets that are destined for transmission in a sub-synchronous capsule. The sub-
25 synchronous capsule shall contain one Control Channel MAC Layer packet. The access
26 network may transmit zero or more sub-synchronous control channel capsules per sector
28 If the access network has queued Security Layer packets that are marked for transmission
29 in a sub-synchronous capsule, it should transmit the packets no later than their
30 associated transmission deadline, if one was provided. The access network may:
31 • Transmit these packets in a synchronous capsule, or
34 ‘0’ for the Control Channel MAC Layer packet of a sub-synchronous capsule.
36 Header to ‘1’ for the Control Channel MAC Layer packet of a sub-synchronous capsule.
9-11
2 Control Channel MAC Layer packet of a sub-synchronous capsule.
3 The access network shall not transmit the Control Channel MAC Layer packet of a sub-
4 synchronous capsule except when the MAC Layer packet starts transmission at times T
5 where T satisfies both of the following equations:
6 T mod 4 = Offset
7 T mod 256 ≠ Offset
9 Channel header of the first Control Channel MAC Layer packet of a synchronous capsule.
11 10.2.6.1.4.2.19.2.6.1.4.2.1 Initial Acquisition

12 When the access terminal detects a Control Channel preamble and determines that the
13 packet being transmitted is the first Control Channel MAC Layer packet of a synchronous
14 capsule, it shall subtract Offset slots from the beginning of the half slot boundary at which
15 the preamble was detected, and shall set the result to the beginning of the 16-slot frame
16 and the beginning of the Control Channel Cycle. The Offset is the value specified in the
17 Control Channel header of the first Control Channel MAC Layer packet of the synchronous
18 capsule.
19 10.2.6.1.4.2.29.2.6.1.4.2.2 Normal Operation

20 If the access terminal changes the sector on which it is monitoring the Control Channel,
21 then the access terminal shall generate an Interrupted indication. If the access terminal
22 receives a Control Channel MAC Layer packet that has the LastPacket bit in the Control
23 Channel header set to ‘0’, the access terminal shall continue monitoring the Control
24 Channel for the Control Channel MAC Layer packets of the same capsule until at least one
25 of the following events occur:
26 • The protocol does not receive a Control Channel MAC Layer Packet at the designated
27 time,
28 • The protocol receives a Deactivate command97, or
29 • The protocol receives a Control Channel MAC Layer packet with the LastPacket bit set
30 to ‘1’.
31 10.2.6.1.4.2.39.2.6.1.4.2.3 Control Channel Supervision

32 Upon entering the active state, the access terminal shall set the Control Channel
33 supervision timer for TCCMPSupervision. If a Synchronous Control Channel capsule is received
34 while the timer is active, the timer is reset and restarted. If the timer expires the protocol
97 For example, this may occur if the access terminal is finished monitoring the Control Channel
Sleep State synchronous capsule and transitioning to the Sleep State.
9-12
1 returns a SupervisionFailed indication and disables the timer. A synchronous Control

2 Channel capsule is defined to have been received if all the MAC layer packets of that
3 synchronous Control Channel capsule were received successfully.
4 10.2.6.1.4.2.49.2.6.1.4.2.4 Address Matching

5 When the access terminal receives a Control Channel MAC packet, it shall perform the
6 following:
7 • Access terminal shall parse the packet into its constituent Security Layer packets.
8 • Access terminal shall forward the Security Layer packet along with the
9 SecurityLayerFormat and the ConnectionLayerFormat fields to the Security Layer if
10 either of the following two conditions are met:
11 − If the ATIType field and the ATI field of the ATI Record in the MAC Layer
12 header of a Security Layer packet is equal to the ATIType and ATI fields of any
13 member of the Address Management Protocol’s ReceiveATIList.
14 − If the ATIType of the ATI Record in the MAC Layer header of a Security Layer
15 packet is equal to ‘00’ (i.e., BATI) and the ReceiveATIList includes a record with
16 ATIType set to ‘00’.
17 • Otherwise, the access terminal shall discard the Security Layer packet.
18 10.2.6.29.2.6.2 Header and Trailer Formats
19 10.2.6.2.19.2.6.2.1 MAC Layer Header

20 The access network shall place the following header in front of every transmitted Security
21 Layer packet:
Field Length (bits)
Length 8
SecurityLayerFormat 1
ConnectionLayerFormat 1
Reserved 4
ATI Record 2 or 34
22 Length The access network shall set this field to the combined length, in
23 octets, of the Security Layer packet and this MAC Layer header
24 excluding the Length field.
25 SecurityLayerFormat
26 The access network shall set this field to ‘1’ if security layer packet is
27 either authenticated or encrypted; otherwise, the access network
29 ConnectionLayerFormat
30 The access network shall set this field to ‘1’ if the connection layer
9-13
1 packet is Format B; otherwise, the access network shall set this field
2 to ‘0’.
3 Reserved The access network shall set this field to all zeros. The access
4 terminal shall ignore this field.
5 ATI Record Access Terminal Identifier Record. The access network shall set this
6 field to the record specifying the access terminal’s address. This
7 record is defined in 13.2.
8 10.2.6.2.29.2.6.2.2 Control Channel Header

9 The access network shall place the following header in front of every Control Channel MAC
10 Layer packet:
Field Length (bits)
SynchronousCapsule 1
FirstPacket 1
LastPacket 1
Offset 2
SleepStateCapsuleDone 1
Reserved 2
11 SynchronousCapsule
12 For a Control Channel MAC Layer packet of a synchronous capsule,
13 the access network shall set this field to ‘1’; otherwise, the access
15 FirstPacket For the first Control Channel MAC Layer packet of a synchronous
16 capsule, asynchronous capsule, or sub-synchronous capsule, the
17 access network shall set this field to ‘1’; otherwise, the access
19 LastPacket For the last Control Channel MAC Layer packet of a synchronous
23 Offset For the first Control Channel MAC Layer packet of a synchronous
24 capsule, the access network shall set this field to the offset in slots of
25 the Synchronous Control Channel relative to the Control Channel
26 Cycle; otherwise, the access network shall set this field to zero.
27 SleepStateCapsuleDone
28 The access network shall set this field to ‘0’ if the MAC Layer packet
29 belongs to the Control Channel synchronous Sleep State capsule and
9-14
1 the MAC Layer packet is not the last packet in the Control Channel
2 synchronous Sleep State capsule. Otherwise, the access network
6 10.2.6.2.39.2.6.2.3 Pad
7 The access network shall add sufficient padding so that the Control Channel MAC Layer
8 packet including all payload and headers is 1000 bits long.
9 The access network shall set the padding bits to ‘0’. The access terminal shall ignore the
10 padding bits.
11 10.2.6.2.49.2.6.2.4 Reserved
12 The access network shall add 2 reserved bits.
13 The access network shall set the reserved bits to ‘0’. The access terminal shall ignore the
14 reserved bits.
16 10.2.6.3.19.2.6.3.1 Commands
18 10.2.6.3.29.2.6.3.2 Indications


23

NCCMPType Type field for this protocol Table 2.5.4-1
NCCMPDefault Subtype field for this protocol 0x0000
Control Channel supervision timer 12 Control Channel
TCCMPSupervision
value Cycles

9-15
1 10.39.3 Enhanced Control Channel MAC Protocol
2 10.3.19.3.1 Overview
3 The Enhanced Control Channel MAC Protocol provides the procedures and messages
4 required for an access network to transmit and for an access terminal to receive the
5 Control Channel. This protocol operates with the Subtype 2 Physical Layer Protocol or the
6 Subtype 3 Physical Layer Protocol.
8 access terminals.
10 • Inactive State: in this state the protocol waits for an Activate command. This state
12 acquired an access network or is not monitoring the Control Channel.
13 • Active State: in this state the access network transmits and the access terminal
14 receives the Control Channel.
Initial State
Rx Activate
(AT Only)
Rx Deactivate
15
(AT only)
16 Figure 9.3.1-1. Enhanced Control Channel MAC Protocol State Diagram
18 10.3.2.19.3.2.1 Commands
20 • Activate.
21 • Deactivate.
22 • ResetSupervisionTimer.

9-16
1 • Interrupted
2 10.3.2.39.3.2.3 Public Data

5 • Offset field of the Control Channel Header of the first Control Channel MAC Layer
6 packet of a synchronous capsule.
7 • CCShortPacketsMACIndex

9 The transmission unit of this protocol is the Control Channel MAC Layer packet.

22 10.3.59.3.5 Protocol Initialization for the InUse Protocol Instance
23 10.3.5.19.3.5.1 Procedures
24 This protocol in the Generic Configuration Protocol (see 13.7) to define the processing of the
25 configuration messages.

27 The access terminal and access network shall perform the procedures specified in this
28 section, in the Inactive State.
33 − CCShortPacketsMACIndex
9-17
2 then
11 − The access terminal shall set the value of the ConnectionOpen parameter to
12 NO.
13 − The access network shall enter the Active State.
15 10.3.6.19.3.6.1 Procedures

25 then
35 of this protocol to the Inactive State.
36 − The access network shall set the initial state for the InConfiguration instance
9-18

2 instance for the Control Channel MAC Protocol.
8
Field Length (bits)
MessageID 8
TransactionID 8
13
16
Field Length (bits)
MessageID 8
TransactionID 8
9-19

6
8 10.3.7.19.3.7.1 Procedures
9 Each Control Channel MAC Layer packet consists of one or more Security Layer packets for
10 one or more access terminals.
11 The protocol constructs a packet out of the Security Layer packets, as follows:
12 • The protocol adds the MAC Layer header specified in 9.3.7.2.1 in front of every Security
13 Layer packet.
14 • The protocol concatenates the Control Channel Header specified in 9.3.7.2.2 followed
15 by the above formed packets.
16 • The protocol pads the resulting packet as defined in 9.3.7.2.3.
17 • The protocol adds the reserved bits as defined in 9.3.7.2.4.
20 Control Channel MAC Layer packets can be transmitted in a synchronous capsule that is
21 transmitted at a particular time, in a quick synchronous capsule that is transmitted at a
22 particular time, in a sub-synchronous capsule that is transmitted at a particular time, or
23 in an asynchronous capsule that can be transmitted at any time except when a
24 synchronous capsule or sub-synchronous is transmitted. A synchronous capsule consists
25 of one or more Control Channel MAC Layer packets.
26 A Control Channel Synchronous Sleep State capsule constitutes the Control Channel MAC
27 Layer packets of a Control Channel synchronous capsule starting from the beginning of a
28 synchronous capsule up to and including the first MAC Layer packet for which the
29 SleepStateCapsuleDone bit in the Control Channel header is set to ‘1’.
30 A sub-synchronous capsule consists of one Control Channel MAC Layer packet. An
31 asynchronous capsule consists of one Control Channel MAC Layer packet. A quick
32 synchronous capsule consists of one Control Channel MAC Layer packet.
33 This protocol expects an address and a parameter indicating transmission in a
34 synchronous capsule, synchronous Sleep State capsule, sub-synchronous capsule, quick
35 synchronous capsule, or an asynchronous capsule with each transmitted Security Layer
36 packet. For Security Layer packets that are carried by an asynchronous capsule, quick
9-20
1 synchronous capsule, or by a sub-synchronous capsule this protocol can also receive an

2 optional parameter indicating a transmission deadline.
MAC Layer packet
MAC Security MAC Security

CC
Layer Layer Layer Layer pad reserved
header
3
4 Figure 9.3.7-1. Enhanced Control Channel MAC Packet Structure
5 Received packets are parsed into their constituent Security Layer packets. The packets that
6 are addressed to the access terminal (see 9.3.7.1.4.2.4) are then forwarded for further
7 processing to the Security Layer.

10 10.3.7.1.1.19.3.7.1.1.1 Activate
11 If this protocol receives an Activate command in the Inactive State, the access terminal
12 shall transition to the Active State
13 If this protocol receives this command in the Active State it shall be ignored.
14 10.3.7.1.1.29.3.7.1.1.2 Deactivate
16 If this protocol receives this command in the Active State, the access terminal shall
17 generate an Interrupted indication and transition to the Inactive State
18 10.3.7.1.29.3.7.1.2 Control Channel Cycle

19 The Control Channel cycle is defined as a 256 slot period, synchronous with CDMA System
20 Time; i.e., there is an integer multiple of 256 slots between the beginning of a cycle and the
21 beginning of CDMA System Time.
22 10.3.7.1.39.3.7.1.3 Inactive State

24 When the protocol is in the Inactive State, the access terminal waits for an Activate
25 command.
26 10.3.7.1.49.3.7.1.4 Active State

27 In this state, the access network transmits, and the access terminal monitors the Control
28 Channel. Upon entering the Active State, the access terminal shall set the value of the
29 ConnectionOpen parameter to NO.
9-21

3 When the access network transmits the Control Channel, it shall do so using the
4 Transmission Formats98 of [128, 4, 1024], [256, 4, 1024], [512, 4, 1024], [1024, 16, 1024],
5 or [1024, 8, 512] with nominal data rates of 19.2 kbps, 38.4 kbps, or 76.8 kbps. The access
6 network may transmit the Control Channel using Transmission Formats of [128, 4, 256]
7 and [256, 4, 256].
8 If the value of the CCShortPacketsMACIndex attribute is 0x00, then the access network
9 shall use the preamble MAC Index specified by Table 12.4.1.3.2.2-2 when transmitting
10 Control Channel packets with Transmission Formats [128, 4, 1024], [256, 4, 1024], or
11 [512, 4, 1024]. Otherwise, the access network may use either the preamble MAC Index
12 specified by the CCShortPacketsMACIndex attribute or the preamble MAC Index specified
13 by Table 12.4.1.3.2.2-2 when transmitting Control Channel packets with Transmission
14 Formats [128, 4, 1024], [256, 4, 1024], or [512, 4, 1024]. When the access network
15 transmits Control Channel packets with Transmission Formats (128, 4, 256) or (256, 4,
16 256) the access network shall use the preamble MAC Index specified by Table 13.4.1.3.2.2-
17 3.
18 The access network shall transmit synchronous capsules and it may transmit sub-
19 synchronous capsules, quick synchronous capsules, and asynchronous capsules. When
20 the access network transmits synchronous capsules, it shall comply with 9.3.7.1.4.1.2.
21 When the access network transmits sub-synchronous capsules, it shall comply with
22 9.3.7.1.4.1.4. When the access network transmits asynchronous capsules, it shall comply
23 with 9.3.7.1.4.1.3. When the access network transmits quick synchronous capsules, it
24 shall comply with 9.3.7.1.4.1.5.
25 The timing of synchronous, sub-synchronous, quick synchronous, and asynchronous
26 capsules is shown in Figure 9.3.7.1.4.1-1.
98 Transmission Format is defined as [ Payload Size(bits), Termination Target(slots), Preamble
Length(chips))
9-22
2 Figure 9.3.7.1.4.1-1. Location of Control Channel Capsules
3 10.3.7.1.4.1.29.3.7.1.4.1.2 Transmission of Synchronous Capsules

4 The access network shall construct a synchronous capsule out of all the pending Security
5 Layer packets that are destined for transmission in a synchronous capsule. The
6 synchronous capsule may contain more than one Control Channel MAC Layer packet. The
7 access network shall transmit exactly one synchronous control channel capsule per sector
9 The access network shall transmit the synchronous capsule using the Transmission
10 Formats of either [1024, 16, 1024] or [1024, 8, 512].
12 ‘1’ for all the Control Channel MAC Layer packets of a synchronous capsule.
13 The access network shall set the LastPacket bit of the Control Channel Header to ‘1’ only
14 for the last Control Channel MAC Layer packet of a synchronous capsule.
15 The access network shall set the FirstPacket bit of the Control Channel Header to ‘1’ only
16 for the first Control Channel MAC Layer packet of the Control Channel synchronous
17 capsule.
18 The access network shall set the SleepStateCapsuleDone bit of the Control Channel header
19 to ‘0’ if the MAC Layer packet belongs to the Control Channel synchronous Sleep State
20 capsule and the MAC Layer packet is not the last packet in the Control Channel
21 synchronous Sleep State capsule.
22 The access network shall set the Offset field of the Control Channel Header of the first
23 Control Channel MAC Layer packet of a synchronous capsule to the offset in slots of the
24 synchronous Control Channel capsule relative to the Control Channel Cycle. If the access
25 network has no pending Security Layer packets, it shall transmit a synchronous capsule
26 with one Control Channel MAC Layer packet containing only the Control Channel header.
27 The access network shall transmit the Control Channel MAC Layer packets of a
28 synchronous capsule as follows:
29 • The first MAC Layer packet shall start transmission at times T where T satisfies the
9-23
1 T mod 256 = Offset.

2 • All other MAC Layer packets of the capsule shall start transmission at the earliest time
3 T following the end of transmission of the previous packet of the capsule that satisfies
5 T mod 4 = Offset,
7 Channel header of the first Control Channel MAC Layer packet of the synchronous capsule.
8 10.3.7.1.4.1.39.3.7.1.4.1.3 Transmission of Asynchronous Capsules

9 The access network may transmit asynchronous capsules at any time during the Control
10 Channel cycle in which it does not transmit a synchronous capsule or a sub-synchronous
11 capsule. If the access network has queued Security Layer packets that are marked for
12 transmission in an asynchronous capsule, it should transmit the packets no later than
13 their associated transmission deadline, if one was provided. The access network may:
15 • Transmit these packets in a sub-synchronous capsule, or
16 • Transmit these packets in an asynchronous capsule.
18 ‘0’ for the Control Channel MAC Layer packet of an asynchronous capsule.
20 Header to ‘1’ for the Control Channel MAC Layer packet of an asynchronous capsule.
22 Control Channel MAC Layer packet of an asynchronous capsule.
23 10.3.7.1.4.1.49.3.7.1.4.1.4 Transmission of Sub-synchronous Capsules

24 The access network shall construct a sub-synchronous capsule out of pending Security
25 Layer packets that are destined for transmission in a sub-synchronous capsule. The sub-
26 synchronous capsule shall contain one Control Channel MAC Layer packet. The access
27 network may transmit zero or more sub-synchronous control channel capsules per sector
29 If the access network has queued Security Layer packets that are marked for transmission
30 in a sub-synchronous capsule, it should transmit the packets no later than their
31 associated transmission deadline, if one was provided. The access network may:
35 ‘0’ for the Control Channel MAC Layer packet of a sub-synchronous capsule.
37 Header to ‘1’ for the Control Channel MAC Layer packet of a sub-synchronous capsule.
9-24
2 Control Channel MAC Layer packet of a sub-synchronous capsule.
3 The access network shall not transmit the Control Channel MAC Layer packet of a sub-
5 where T satisfies both of the following equations:
6 T mod 4 = Offset
7 T mod 256 ≠ Offset
9 Channel header of the first Control Channel MAC Layer packet of a synchronous capsule.
10 10.3.7.1.4.1.59.3.7.1.4.1.5 Transmission of Quick Synchronous Capsules

11 The access network shall construct a quick synchronous capsule out of pending Security
12 Layer packets that are destined for transmission in a quick synchronous capsule. The
13 quick synchronous capsule shall contain one Control Channel MAC Layer packet. The
14 access network may transmit zero or more quick synchronous control channel capsules per
15 sector during each control channel cycle.
16 The access network shall transmit the quick synchronous capsule using the first slot of
17 Transmission Format [128, 4, 256] or [256, 4, 256].
19 ‘0’ for the Control Channel MAC Layer packet of a quick synchronous capsule.
21 Control Channel MAC Layer packet of a quick synchronous capsule.
22 The access network shall not transmit the Control Channel MAC Layer packet of a quick
24 where T satisfies the following equations:
25 (T + 1) mod 4 = Offset (if QuickPagingEnabled equals ‘1’ and SubSyncQuickPaging
26 equal ‘1’)
27 (T + 1) mod 256 = Offset (if QuickPagingEnabled equals ‘1’)
29 Channel header of the first Control Channel MAC Layer packet of a synchronous capsule
30 and SubSyncQuickPaging is public data of the Idle State Protocol.
32 10.3.7.1.4.2.19.3.7.1.4.2.1 Initial Acquisition

33 When the access terminal detects a Control Channel preamble and determines that the
34 packet being transmitted is the first Control Channel MAC Layer packet of a synchronous
35 capsule, it shall subtract Offset slots from the beginning of the half slot boundary at which
36 the preamble was detected, and shall set the result to the beginning of the 16-slot frame
37 and the beginning of the Control Channel Cycle. The Offset is the value specified in the
9-25
1 Control Channel header of the first Control Channel MAC Layer packet of the synchronous
2 capsule.
3 10.3.7.1.4.2.29.3.7.1.4.2.2 Normal Operation

4 If the access terminal changes the sector on which it is monitoring the Control Channel,
5 then the access terminal shall generate an Interrupted indication. The access terminal shall
6 maintain a parameter called ConnectionOpen. Upon receiving an
7 IdleState.ConnectionOpened indication, the access terminal shall set ConnectionOpen to
8 YES. Upon receiving a ConnectedState.ConnectionClosed indication, the access terminal
9 shall set ConnectionOpen to NO.
10 The access terminal need not look for preamble for the Control Channel packets with
11 Transmission Formats [128, 4, 1024], [256, 4, 1024], and [512, 4, 1024] when
12 ConnectionOpen is YES.
13 If the access terminal receives a Control Channel MAC Layer packet that has the
14 LastPacket bit in the Control Channel header set to ‘0’, the access terminal shall continue
15 monitoring the Control Channel for the Control Channel MAC Layer packets of the same
16 capsule until at least one of the following events occur:
17 • The protocol does not receive a Control Channel MAC Layer Packet at the designated
18 time,
19 • The protocol receives a Deactivate command99, or
20 • The protocol receives a Control Channel MAC Layer packet with the LastPacket bit set
21 to ‘1’.
22 10.3.7.1.4.2.39.3.7.1.4.2.3 Control Channel Supervision

23 Upon entering the active state, the access terminal shall set the Control Channel
24 supervision timer for TCCMPSupervision. If a Synchronous Control Channel capsule is received
25 while the timer is active, the access terminal shall reset the timer and restart the timer. If a
26 ResetSupervisionTimer command is received, then the access terminal shall reset and
27 restart the supervision timer. If the timer expires the protocol returns a SupervisionFailed
28 indication and disables the timer. A synchronous Control Channel capsule is defined to
29 have been received if all the MAC layer packets of that synchronous Control Channel
30 capsule were received successfully.
31 10.3.7.1.4.2.49.3.7.1.4.2.4 Address Matching

32 When the access terminal receives a Control Channel MAC packet, it shall perform the
33 following:
34 • The access terminal shall parse the packet into its constituent Security Layer packets.
99 For example, this may occur if the access terminal is finished monitoring the Control Channel
Sleep State synchronous capsule and transitioning to the Sleep State.
9-26
1 • The access terminal shall forward the Security Layer packet along with the
2 SecurityLayerFormat and the ConnectionLayerFormat fields to the Security Layer if
3 either of the following two conditions are met:
4 − If the ATIType field and the ATI field of the ATI Record in the MAC Layer
5 header of a Security Layer packet is equal to the ATIType and ATI fields of any
6 member of the Address Management Protocol’s ReceiveATIList.
7 − If the ATIType of the ATI Record in the MAC Layer header of a Security Layer
8 packet is equal to ‘00’ (i.e., BATI) and the ReceiveATIList includes a record with
9 ATIType set to ‘00’.
10 • Otherwise, the access terminal shall discard the Security Layer packet.
11 10.3.7.29.3.7.2 Header and Trailer Formats
12 10.3.7.2.19.3.7.2.1 MAC Layer Header

13 The access network shall place the following header in front of every transmitted Security
14 Layer packet:
Field Length (bits)
Length 8
Reserved 4
ATI Record 2 or 34
15 Length The access network shall set this field to the combined length, in
16 octets, of the Security Layer packet and this MAC Layer header
19 The access network shall set this field to ‘1’ if security layer packet is
20 either authenticated or encrypted; otherwise, the access network
25 to ‘0’.
26 Reserved The access network shall set this field to all zeros. The access
27 terminal shall ignore this field.
28 ATI Record Access Terminal Identifier Record. The access network shall set this
29 field to the record specifying the access terminal’s address. This
30 record is defined in 13.2.
9-27
1 10.3.7.2.29.3.7.2.2 Control Channel Header

2 The access network shall place the following header in front of every Control Channel MAC
3 Layer packet:
Field Length (bits)
SynchronousCapsule 1
FirstPacket 1
LastPacket 1
Offset 2
SleepStateCapsuleDone 1
Reserved 2
4 SynchronousCapsule
5 For a Control Channel MAC Layer packet of a synchronous capsule,
6 the access network shall set this field to ‘1’; otherwise, the access
8 FirstPacket For the first Control Channel MAC Layer packet of a synchronous
12 LastPacket For the last Control Channel MAC Layer packet of a synchronous
16 Offset For the first Control Channel MAC Layer packet of a synchronous
17 capsule, the access network shall set this field to the offset in slots of
18 the Synchronous Control Channel relative to the Control Channel
19 Cycle; otherwise, the access network shall set this field to zero.
20 SleepStateCapsuleDone
21 The access network shall set this field to ‘0’ if the MAC Layer packet
22 belongs to the Control Channel synchronous Sleep State capsule and
23 the MAC Layer packet is not the last packet in the Control Channel
24 synchronous Sleep State capsule. Otherwise, the access network
9-28
1 10.3.7.2.39.3.7.2.3 Pad
2 The access network shall add sufficient padding so that the size of the Control Channel
3 MAC Layer packet is equal to the size of the payload of the Physical Layer packet that will
4 be used to transmit the Control Channel MAC packet.
5 The access network shall set the padding bits to ‘0’. The access terminal shall ignore the
6 padding bits.
7 10.3.7.2.49.3.7.2.4 Reserved
8 The access network shall add 2 reserved bits.
9 The access network shall set the reserved bits to ‘0’. The access terminal shall ignore the
10 reserved bits.
12 10.3.7.3.19.3.7.3.1 Commands
14 10.3.7.3.29.3.7.3.2 Indications

21 terminal and the access network shall use as defaults the values in Table 9.3.8-1 that are
9-29

ID s
0x00 Preamble MAC Index for short

packet transmissions on the Control
Channel is not defined
0x01 Reserved
to
0x05
to packet transmissions on the Control
0x3f Channel
0x00 CCShortPacketsMACIndex Reserved
0x40
to
0x47
to packet transmissions on the Control
0x7f Channel
0x80 Reserved
to
0xff

3

NCCMPType Type field for this protocol Table 2.5.4-1
NS1ECCMP Subtype field for this protocol 0x0001
Control Channel supervision 12 Control Channel
TCCMPSupervision
timer value Cycles

9-30
1 10.49.4 Default Access Channel MAC Protocol
2 10.4.19.4.1 Overview
3 The Default Access Channel MAC Protocol provides the procedures and messages required
4 for an access terminal to transmit and an access network to receive the Access Channel.
5 This protocol operates with the Default (Subtype 0) Physical Layer Protocol, the Subtype 1
6 Physical Layer Protocol, the Subtype 2 Physical Layer Protocol, or the Subtype 3 Physical
7 Layer Protocol.
9 access terminals.
11 • Inactive State: In this state the protocol waits for an Activate command. This state
13 acquired an access network or the access terminal has a connection open.
14 • Active State: In this state the access terminal transmits and the access network
15 receives the Access Channel.
Initial State
Rx Activate
(AT only)
Rx Deactivate
16
(AT only)
17 Figure 9.4.1-1. Default Access Channel MAC Protocol State Diagram
19 10.4.2.19.4.2.1 Commands
21 • Activate
22 • Deactivate

25 • TransmissionSuccessful
9-31
1 • TransmissionAborted
2 • TransmissionFailed
3 • TxStarted
4 • TxEnded
6 • MACLayerCapsuleReceived
7 10.4.2.39.4.2.3 Public Data

10 • DataOffsetNom
11 • DataOffset9k6
12 • PowerStep
13 • OpenLoopAdjust
14 • ProbeInitialAdjust
15 • PreambleLength
16 • AccessSignature field of the next AccessParameters message to be sent by the access
17 network
18 • MIACMAC
19 • MQACMAC

21 The transmission unit of this protocol is the Access Channel MAC Layer packet. Each
22 Access Channel MAC Layer packet contains part or all of a Security Layer packet.

9-32

11 10.4.5.19.4.5.1 Procedures

22 − DataOffsetNom
23 − DataOffset9k6
25 then
28 associated with the InConfiguration instance of this protocol.
32 instance, then:
35 − The access network shall set the state for the InConfiguration instance of this
36 protocol to the Active State.
9-33

2 instance for the Access Channel MAC Protocol.
8
Field Length (bits)
MessageID 8
TransactionID 8
13
16
Field Length (bits)
MessageID 8
TransactionID 8
9-34

6
8 10.4.6.19.4.6.1 Procedures
9 The protocol constructs one or more packets out of the Security Layer packet as follows:
10 • The protocol adds the MAC Layer header specified in 9.4.6.2.1 in front of the Security
11 Layer packet,
12 • The protocol adds the FCS as defined in 9.4.6.2.2,
13 • The protocol pads the result as defined in 9.4.6.2.3,
14 • The protocol splits the result into one or more Access Channel MAC Layer capsule
15 fragments,
16 • The protocol adds the reserved bits, as defined in 9.4.6.2.4, to the capsule fragments to
17 construct the Access Channel MAC Layer packets.
18 This protocol passes the packets for transmission to the Physical Layer. An example of the
19 packet structure is shown in Figure 9.4.6.1-1.
20 Received packets are passed for further processing to the Security Layer after
21 concatenation, removing the padding, FCS checking, and removing the MAC layer headers.
22 The value of the SecurityLayerFormat and ConnectionLayerFormat fields shall be passed to
23 the Security Layer with the Security Layer packet.
MAC Layer capsule
MAC Security
Layer Layer FCS pad
header packet
MAC MAC
Layer reserved ... Layer reserved
capsule fragment capsule fragment
MAC Layer packet MAC Layer packet

24
25 Figure 9.4.6.1-1. Access Channel MAC Packet Structure
9-35

3 10.4.6.1.1.19.4.6.1.1.1 Activate
4 If this protocol receives an Activate command in the Inactive State,
7 If this protocol receives the command in the Active State it shall be ignored.
8 10.4.6.1.1.29.4.6.1.1.2 Deactivate
10 If this protocol receives the command in the Active State,
13 10.4.6.1.29.4.6.1.2 Access Channel Structure

14 Figure 9.4.6.1.2-1 and Figure 9.4.6.1.2-2 illustrate the access probe structure and the
15 access probe sequence.
16 The Access Channel Cycle specifies the time instants at which the access terminal may
17 start an access probe. An Access Channel probe may only begin at times T such that
18 T mod AccessCycleDuration = 0,
19 where T is CDMA System Time in slots.
20 The structure of an individual access probe is shown in Figure 9.4.6.1.2-1. In each access
21 probe, the pilot (I-channel) is first enabled and functions as a preamble. After
22 PreambleLength frames (PreambleLength × 16 slots), the probe data (Q-channel) is enabled
23 for up to CapsuleLengthMax × 16 slots.
9-36
Beginning of an Beginning of an
Access Channel Access Channel
Cycle Cycle
AccessCycleDuration AccessCycleDuration ...
Preamble Capsule
(PreambleLength × 16 slots) ( up to
CapsuleLength
Max ×16 slots)
Actual Access Probe Transmission
2 Figure 9.4.6.1.2-1. Access Probe Structure
3 Each probe in a sequence is transmitted at increased power until any of the following
4 conditions are met:
5 • The access terminal receives an ACAck message,
6 • Transmission is aborted because the protocol received a Deactivate command, or
7 • Maximum number of probes per sequence (ProbeNumStep) has been transmitted.
8 Prior to the transmission of the first probe, the access terminal performs a persistence test
9 which is used to control congestion on the Access Channel.
10 Additionally the access terminal performs a persistence test in between probe sequences.
τp τp τp
persistence
persistence
persistence
τs ...
probe 1 2 3 Np 1 2 3 Np 1 2 3 Np
Time
11
probe
sequence
1 2 ... Ns
12 Figure 9.4.6.1.2-2. Access Probe Sequences
13 10.4.6.1.39.4.6.1.3 Inactive State

15 In this state the access terminal waits for an Activate command.
9-37
1 10.4.6.1.49.4.6.1.4 Active State

2 In this state the access terminal is allowed to transmit on the Access Channel and the
3 access network is monitoring the Access Channel.
4 If the protocol receives a Deactivate command,
5 • Access terminal shall:
6 − Immediately cease transmitting on the Access Channel if it is in the process of
7 sending a probe.
8 − Return a TransmissionAborted indication if it was in the process of sending an
9 Access Channel MAC Layer capsule.
10 − Transition to the Inactive State.
11 • Access network shall ignore this command.
12 All other commands shall be ignored in this state.

14 This protocol enforces a stop-and-wait packet transmission policy over the Access Channel.
15 That is, the access terminal shall not send a new Access Channel MAC Layer capsule
16 before either:
17 • Receipt of an ACAck message for the previous capsule, or
18 • Transmission of the previous capsule failed after transmitting ProbeSequenceMax probe
19 sequences for it.
20 The access terminal shall return a TxStarted indication before transmitting the first probe
21 for an Access Channel MAC Layer capsule.100
22 The access terminal shall return a TxEnded indication either:
23 • Simultaneous with a TransmissionAborted or a TransmissionFailed indication, or
24 • TACMPTransaction seconds after a TransmissionSuccessful indication.
25 10.4.6.1.4.1.19.4.6.1.4.1.1 Reverse Link Silence Interval

26 The Reverse Link Silence Interval is defined as the time interval of duration
27 ReverseLinkSilenceDuration frames that starts at times T specified by the following
28 equation:
29 T mod (2048×2ReverseLinkSilencePeriod - 1) = 0.
30 where T is the CDMA System Time in units of frames.
31 The ReverseLinkSilenceDuration and ReverseLinkSilencePeriod parameters are given as
32 public data by the Overhead Messages Protocol.
100 Higher layer protocols use this indication as a notification that there may be an outstanding
transaction on the Access Channel; and, therefore, the access terminal should not go to sleep.
9-38
1 10.4.6.1.4.1.29.4.6.1.4.1.2 Probe Transmission

2 The access terminal shall conform to the following rules when sending a probe:
3 1. Current SectorParameters. The access terminal shall verify that the value of
4 SectorSignature field of the latest QuickConfig message is the same as
5 SectorSignature field of the latest SectorParameters message prior to sending the
6 first probe of the first probe sequence. Both SectorSignature values (one belonging
7 to the QuickConfig message and one belonging to the SectorParameters message)
8 are public data of the Overhead Messages Protocol.
9 2. Current AccessParameters. Prior to sending the first probe of the first probe
10 sequence, the access terminal shall verify that the last AccessParameters message it
11 received is current, according to the last AccessSignature value given as public data
12 by the Overhead Messages Protocol. If the AccessParameters message is not
13 current, the access terminal shall start the AccessParameters supervision timer for
14 TACMPAPSupervision. If the timer expires before it receives the current AccessParameters
15 message, the access terminal shall return a SupervisionFailed indication and
17 3. ATI Record. The access terminal shall set the ATI and ATIType fields of the ATI
18 Record in the MAC Layer header to TransmitATI.ATI and TransmitATI.ATIType,
19 respectively (TransmitATI is provided as public data by the Address Management
20 Protocol).
21 4. Probe Power Control. The access terminal shall send the ith probe in the probe
22 sequence at a power level given by X0+(i-1)×PowerStep, where X0 represents the
23 access terminal’s open-loop mean output power of the Pilot Channel and is given by
24 X0 = - Mean RX Power (dBm) + OpenLoopAdjust + ProbeInitialAdjust
25 and the Mean RX Power is estimated throughout the transmission of each probe.
26 5. Probe Structure. When sending a probe, the access terminal shall transmit
27 PreambleLength frames of pilot only, followed by up to CapsuleLengthMax frames of
28 probe data and pilot. The access terminal shall transmit a single Access Channel
29 Capsule per probe. The access terminal shall not change the probe data contents in
30 between probes.
31 6. Long Code Cover. The access terminal shall use the Access Channel long codes to
32 cover the entire probe. The Access Channel long code is specified in 10.3.1.3.8.2.
33 7. Inter-Probe Backoff. If the access terminal receives an ACAck message or it has
34 already transmitted ProbeNumStep (NP in Figure 9.4.6.1.2-2) probes in this probe
35 sequence, then it shall not send the next probe in this probe sequence. Otherwise,
36 after sending an access probe within an access probe sequence, the access terminal
37 shall perform the following procedures:
38 a. Set yTotal to 0,
39 b. Generate a pseudo random number y which is a uniformly distributed
40 integer random number between 0 and ProbeBackoff,
9-39
1 c. Add y to yTotal (i.e., yTotal = yTotal + y),

2 d. Compute P = TACMPATProbeTimeout + (yTotal × AccessCycleDuration)
3 e. If any portion of the access probe that would start at the first Access
4 Channel Cycle instance that occurs at least P slots after the end of the
5 previous access probe overlaps with the Reverse Link Silence Interval (see
6 9.4.6.1.4.1.1), then the access terminal shall re-start the procedures from
7 step ‘b’ above.
8 f. Consider the access probe that would start at the first Access Channel
9 Cycle instance that occurs at least P slots after the end of the previous
10 access probe. If any portion of the access probe plus the time interval that
11 is required to receive the corresponding ACAck message (as estimated by
12 the access terminal)101 overlaps with slots when the access terminal does
13 not receive the Forward Channel, then the access terminal shall transmit
14 the next access probe at the first Access Channel Cycle instance that
15 occurs at least P + T ×AccessCycleDuration) slots after the end of the
16 previous access probe where T is the minimum number of intervals of
17 length AccessCycleDuration that are needed to be added to P in order to
18 ensure that the access probe does not overlap with the slots when the
19 access terminal does not receive the Forward Channel. If the access probe
20 starting at new start time overlaps with a Reverse Link Silence Interval,
21 then add T to ytotal and then the access terminal shall re-start the
22 procedure from step ‘b’ above.
23 g. Otherwise, if neither condition ‘e’ nor condition ‘f’ are satisfied, the access
24 terminal shall transmit the next access probe at the first Access Channel
25 Cycle instance that occurs at least P slots after the end of the previous
26 access probe.
27 10.4.6.1.4.1.39.4.6.1.4.1.3 Access Channel Long Code Mask

28 The access terminal shall set the Access Channel long masks, MIACMAC and MQACMAC as
29 follows.
30 The 42-bit mask MIACMAC shall be as specified in Table 9.4.6.1.4.1.3-1.
31 Table 9.4.6.1.4.1.3-1. Access Channel Long Code Masks
BIT
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
MIACMAC 1 1 AccessCycleNumber Permuted (ColorCode | SectorID[23:0])

32
33 The 42-bit mask MQACMAC shall be derived from the mask MIACMAC as follows:
101 The turn-around time between the access network receiving an access probe and sending an
ACAck message is determined by the access network implementation, but the access terminal may
estimate such time interval.
9-40
1 MQACMAC[k] = MIACMAC[k-1], for k = 1,…, 41

2 MQACMAC[0] = MIACMAC[0] ⊕ MIACMAC[1] ⊕ MIACMAC[2] ⊕ MIACMAC[4] ⊕ MIACMAC[5] ⊕
3 MIACMAC[6] ⊕ MIACMAC[9] ⊕ MIACMAC[15] ⊕ MIACMAC[16] ⊕ MIACMAC[17] ⊕
5 MIACMAC[26] ⊕ MIACMAC[30] ⊕ MIACMAC[32] ⊕ MIACMAC[34] ⊕ MIACMAC[41]
6 where the ⊕ denotes the Exclusive OR operation, and MQACMAC[i] and MIACMAC[i] denote the
7 ith least significant bit of MQACMAC and MIACMAC, respectively.
8 In Table 9.4.6.1.4.1.3-1:
9 • SectorID is given as public data of Overhead Messages Protocol and corresponds to the
10 sector to which the access terminal is sending the access probe.
11 • ColorCode is given as public data of Overhead Messages Protocol and corresponds to
12 the sector to which the access terminal is sending the access probe.
13 • AccessCycleNumber is defined as follows:
14 AccessCycleNumber = SystemTime mod 256
15 Where:
16 • SystemTime is the CDMA System Time in slots corresponding to the slot in which the
17 first access probe preamble for this access probe is sent. Permuted(ColorCode |
18 SectorID[23:0]) is a permutation of the bits in ColorCode | SectorID[23:0] and is defined
19 as follows:
20 ColorCode | SectorID[23:0] = (S31, S30, S29, …, S0)
21 Permuted(ColorCode | SectorID[23:0]) =
22 (S0, S31, S22, S13, S4, S26, S17, S8, S30, S21, S12, S3, S25, S16, S7, S29, S20, S11, S2, S24,
23 S15, S6, S28, S19, S10, S1, S23, S14, S5, S27, S18, S9).
24 10.4.6.1.4.1.49.4.6.1.4.1.4 Probe Sequence Transmission

25 The access terminal shall conform to the following rules when sending a probe sequence:
26 1. Transmission of the First Probe.
27 − Prior to sending the first probe of the sequence, the access terminal shall
28 perform the following in the order specified:
29 + Silence Period Test: The access terminal shall wait until the beginning of the
30 first Access Channel Cycle such that transmission of the access probe that
31 would start at the beginning of the current Access Channel Cycle would not
32 overlap with the Reverse Link Silence Interval (see 9.4.6.1.4.1.1 for definition
33 of the Reverse Link Silence Interval).
9-41
1 + Persistence Test : For this test, the access terminal shall use the value p as
2 specified by APersistence[i] where i is the class of the access terminal and
3 APersistence[i] is the (i+1)st occurrence of the APersistence field in the
4 AccessParameters message.102 The value i=2 is reserved for test access
5 terminals. If the access terminal does not have a class defined, it shall use
6 i=0, corresponding to non-emergency access terminals. All other values of i are
7 reserved.
8 When p is not zero, the persistence test consists of comparing a uniformly
9 distributed random number x, 0 < x < 1, (using the procedure specified in 13.5)
10 with p. If x < p the test is said to succeed. If the persistence test succeeds or if
11 the number of consecutive unsuccessful persistence tests exceeds 4/p, the
12 access terminal may transmit in the first upcoming Access Channel Cycle such
13 that no portion of the access probe overlaps with the Reverse Link Silence
14 Interval and no portion of the access probe plus the time interval that is
15 required to receive the corresponding ACAck message (as estimated by the
16 access terminal)103 will overlap with slots when the access terminal does not
17 receive the Forward Channel. If any portion of the access probe overlaps with
18 the Reverse Link Silence Interval, then the access terminal shall not transmit
19 the access probe and shall re-start the procedures for Transmission of the First
20 Probe from the beginning. Otherwise, if p is not equal to zero, the access
21 terminal shall repeat the above-mentioned Silence Period Test and then the
22 Persistence Test starting from the next Access Channel Cycle. If p is equal to
23 zero, the access terminal shall return a TransmissionFailed indication and end
24 the access.
25 2. Probe Contents. The access terminal shall not change the data portion of the probe
26 contents between probe sequences.
27 3. Success Condition. If the access terminal receives an ACAck message it shall stop
28 the probe sequence, including any transmission in progress, and shall return a
29 TransmissionSuccessful indication.
102 The access terminal’s class is configured through means that are outside the scope of this
specification.
9-42
1 4. Failure Condition. If the access terminal has already sent ProbeSequenceMax probe
2 sequences for this access (NS in Figure 9.4.6.1.2-2), and if it does not receive an
3 ACAck message acknowledging its receipt within (TACMPATProbeTimeout + TACMPCycleLen)
4 slots after the end of the last access probe, or if the interval between two adjacent
5 probes in the access attempt is greater than TACMPATProbeTimeout + max(ProbeBackoff,
6 ProbeSequenceBackoff) × AccessCycleDuration + TACMPMaxDelayPrevProbe slots104, then
7 the access terminal shall return a TransmissionFailed indication and abort the
8 access.
9 5. Inter-Sequence Backoff. The access terminal shall generate a uniformly distributed
10 integer random number k between 0 and ProbeSequenceBackoff. The access
11 terminal shall wait for τS = (k × AccessCycleDuration) + TACMPATProbeTimeout slots from
12 the end of the last probe of the previous sequence before repeating this sequence.

14 The access network should send an AccessParameters message at least once every
15 NACMPAccessParameters slots.
16 The access network should send an ACAck message in response to every Access Channel
17 MAC Layer capsule it receives. The message should be sent within TACMPANProbeTimeout slots of
18 receipt of the packet. The access network shall return a MACLayerCapsuleReceived
19 indication upon sending an ACAck message.
20 The access network should monitor and control the load on the Access Channel. The
21 access network may control the load by adjusting the access persistence vector,
22 APersistence, sent as part of the AccessParameters message.
23 10.4.6.29.4.6.2 Header and Message Formats
24 10.4.6.2.19.4.6.2.1 MAC Layer Header

25 The access terminal shall place the following header in front of the Security Layer packet:
26
104 E.g., because the access terminal has tuned to the frequency associated with another air-
interface.
9-43
Field Length (bits)

Length 8
SessionConfigurationToken 16
Reserved 4
ATI Record 34
1 Length The access terminal shall set this field to the combined length, in
2 octets, of the Security Layer packet and this MAC Layer header.
5 The access terminal shall set this field to the value of the
6 SessionConfigurationToken which is public data of the Session
9 The access terminal shall set this field to ‘1’ if security layer packet is
10 either authenticated or encrypted; otherwise, the access terminal
13 The access terminal shall set this field to ‘1’ if the connection layer
14 packet is Format B; otherwise, the access terminal shall set this field
15 to ‘0’.
18 ATI Record Access Terminal Identifier Record. The access terminal shall set this
19 field to the record specifying the access terminal’s ID specified by
20 TransmitATI.ATI and TransmitATI.ATIType. This record is defined in
21 13.2.
22 10.4.6.2.29.4.6.2.2 FCS
23 The FCS shall be calculated using the standard CRC-CCITT generator polynomial:
24 g ( x ) = x 32 + x 26 + x 23 + x 22 + x16 + x12 + x11 + x10 + x 8 + x 7 + x 5 + x 4 + x 2 + x1 + 1

25 The FCS shall be equal to the value computed by the following procedure and the logic
26 shown below:
27 • All shift register elements shall be initialized to logical zeros.
28 • Switches shall be set in the up position.
9-44
1 • Register shall be clocked once for each bit of Access Channel MAC Layer Capsule,
2 excluding the FCS and padding bits. The Access Channel MAC Layer Capsule is read in
3 order from MSB to LSB, starting with the MSB of the MAC Layer header
4 • Switches shall be set in the down position so that the output is a modulo-2 addition
5 with a ‘0’ and the successive shift register inputs are ‘0’.
6 • Register shall be clocked an additional 32 times for the 32 FCS bits.
Input
‘0’
0 1 2 3 4 26
x x x x x x x31
Output
‘0’
Denotes one-bit storage element

Up for all the bits of the
Denotes modulo-2 addition Access Channel MAC Layer Capsule;
then, down for the 32-bit
Access Channel MAC Layer Capsule FCS.
7
8 Figure 9.4.6.2-1. Access Channel MAC Layer Capsule FCS
9 10.4.6.2.39.4.6.2.3 Padding Bits

10 The access terminal shall add sufficient padding so that the Access Channel MAC capsule,
11 including all payload, FCS, padding, and headers, is the smallest possible integer multiple
12 of 232 bits. The access terminal shall set the padding bits to ‘0’. The access network shall
13 ignore the padding bits.
14 10.4.6.2.49.4.6.2.4 Reserved Bits

15 The access terminal shall add 2 reserved bits to each Access Channel capsule fragment.
16 The access terminal shall set the reserved bits to ‘0’. The access network shall ignore the
17 reserved bits.
18 10.4.6.2.59.4.6.2.5 ACAck
19 The access network sends the ACAck message to acknowledge receipt of an Access
20 Channel MAC Layer capsule.
Field Length (bits)
MessageID 8

22
9-45
1 10.4.6.2.69.4.6.2.6 AccessParameters
2 The AccessParameters message is used to convey Access Channel information to the access
3 terminals.
4
Field Length (bits)

MessageID 8
AccessCycleDuration 8
AccessSignature 16
OpenLoopAdjust 8
ProbeInitialAdjust 5
ProbeNumStep 4
PowerStep 4
PreambleLength 3
CapsuleLengthMax 4
NACMPAPersist occurrences of the following field:
APersistence 6
Reserved variable
6 AccessCycleDuration
7 The access network shall set this field to the duration of an Access
8 Channel Cycle in units of slots.
9 AccessSignature AccessParameters message signature. The access network shall

10 change this field if the contents of the AccessParameters message
11 change.
12 OpenLoopAdjust The access network shall set this field to the negative of the nominal
13 power to be used by access terminals in the open loop power
14 estimate, expressed as an unsigned value in units of 1 dB. The value
15 used by the access terminal is -1 times the value of this field.
16 ProbeInitialAdjust The access network shall set this field to the correction factor to be
17 used by access terminals in the open loop power estimate for the
9-46
1 initial transmission on the Access Channel, expressed as a two’s

2 complement value in units of 1 dB.
3 ProbeNumStep The access network shall set this field to the maximum number of
4 access probes access terminals are to transmit in a single access
5 probe sequence. The access network shall set this field to a value in
6 the range [1 ... 15].
7 PowerStep Probe power increase step. The access network shall set this field to
8 the increase in power between probes, in resolution of 0.5 dB. The
9 access terminal shall support all the valid values specified by this
10 field.
11 PreambleLength The access network shall set this field to the length in frames of the
12 access probe preamble in the range [1 … 7]. The access terminal
14 CapsuleLengthMax Access Channel Max Capsule length. The access network shall set
15 this field to the maximum number of frames in an Access Channel
16 Capsule. The access network shall set this field to a value in the
17 range [2 … 15]. The access terminal shall support all the valid values
19 APersistence Access persistence vector. If a value in this vector is 0x3F, the access
20 terminal shall use zero as the corresponding persistence probability;
21 otherwise, if the value of this field, n, not equal to 0x3F, the access
-n/4
22 terminal shall use 2 as the corresponding persistence probability.
23 Reserved Number of bits in this field is equal to the number needed to make
24 the message length an integer number of octets. The access network
25 shall set this field to zero. The access terminal shall ignore this field.
26
Addressing Broadcast Priority 30
28 10.4.6.3.19.4.6.3.1 Commands
30 10.4.6.3.29.4.6.3.2 Indications
9-47

4 10.4.7.19.4.7.1 InitialConfiguration Attribute

5

Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
ProbeSequenceMax 4 3
ProbeBackoff 4 4
ProbeSequenceBackoff 4 8
Reserved 4 N/A
}
8 Length field.
9 AttributeID Parameter set identifier. The access network shall set this field to
10 0x00.
11 ValueID The access network shall set this field to an identifier assigned to this
12 complex attribute. The access network should change this field for
13 each set of values for this complex attribute.
14 ProbeSequenceMax Maximum number of probe sequences. The access network shall set
15 this field to the maximum number of probe sequences for a single
16 access attempt. The access network shall set this field to a value in
17 the range [1 … 15]. The access terminal shall support all the valid
19 ProbeBackoff Inter-probe backoff. The access network shall set this field to the
20 upper limit of the backoff range (in units of AccessCycleDuration)
21 that the access terminal is to use between probes. The access
23 ProbeSequenceBackoff
24 Inter-probe sequence backoff. The access network shall set this field
25 to the upper limit of the backoff range (in units of
9-48
1 AccessCycleDuration) that the access terminal is to use between

2 probe sequences. The access terminal shall support all the valid
6 10.4.7.29.4.7.2 PowerParameters Attribute

7

Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
DataOffsetNom 4 0
DataOffset9k6 4 0
10 Length field.
13 complex value.
14 DataOffsetNom The access network shall set this field to the nominal offset of the
15 access data channel power to pilot channel power, expressed as 2's
16 complement value in units of 0.5 dB. The access terminal shall
17 support all the valid values specified by this field.
18 DataOffset9k6 The access network shall set this field to the ratio of access channel
19 power at 9600 bps to the nominal access channel power at 9600 bps,
20 expressed as 2’s complement in units of 0.25 dB. The access
9-49

2

NACMPType Type field for this protocol Table 2.5.4-1
NACMPDefault Subtype field for this protocol 0x0000
Number of different persistence
NACMPAPersist 4
values
The recommended maximum
number of slots between
NACMPAccessParameters 3 * TACMPCycleLen
transmission of two consecutive
AccessParameters message.
TACMPAPSupervision AccessParameters supervision timer 12 * TACMPCycleLen
Time to receive an acknowledgment
TACMPATProbeTimeout at the access terminal for a probe 128 slots
before sending another probe
Maximum time to send an
TACMPANProbeTimeout acknowledgment for a probe at the 96 slots
access network
Time for access terminal to wait
after a successful transmission
TACMPTransaction 1 second
before returning a TxEnded
indication
Length of Control Channel Cycle
TACMPCycleLen used by the Access Channel MAC 256 slots
Protocol
A constant that determines the time
for the access terminal to wait until
after transmitting an access probe
TACMPMaxDelayPrevProbe 300 slots
in the access attempt before
returning a TransmissionFailed
indication

6 protocol.
9-50
1 10.59.5 Enhanced Access Channel MAC Protocol
2 10.5.19.5.1 Overview
3 The Enhanced Access Channel MAC Protocol provides the procedures and messages
4 required for an access terminal to transmit and an access network to receive the Access
5 Channel. This protocol operates with Subtype 1 Physical Layer Protocol, Subtype 2 Physical
6 Layer Protocol, or Subtype 3 Physical Layer Protocol.
8 access terminals.
10 • Inactive State: In this state the protocol waits for an Activate command. This state
12 acquired an access network or the access terminal has a connection open.
13 • Active State: In this state the access terminal transmits and the access network
14 receives the Access Channel.
Initial State
Rx Activate
(AT only)
Rx Deactivate
15
(AT only)
16 Figure 9.5.1-1. Enhanced Access Channel MAC Protocol State Diagram
18 10.5.2.19.5.2.1 Commands
20 • Activate
21 • Deactivate

24 • TransmissionSuccessful
25 • TransmissionAborted
9-51
1 • TransmissionFailed
2 • TxStarted
3 • TxEnded
5 • MACLayerCapsuleReceived
6 10.5.2.39.5.2.3 Public Data

9 • DataOffsetNom
13 • PowerStep
14 • OpenLoopAdjust
15 • ProbeInitialAdjust
16 • Length of the preamble
17 • AccessRateMax
18 • AccessSignature field of the next AccessParameters message to be sent by the access
19 network
20 • MIACMAC
21 • MQACMAC
22 • PNRandomizationDelay

24 The transmission unit of this protocol is the Access Channel MAC Layer packet. Each
25 Access Channel MAC Layer packet contains part or all of a Security Layer packet.

9-52
8 10.5.5.19.5.5.1 Procedures

24 then
31 instance, then:
34 − The access network shall set the state for the InConfiguration instance of this
35 protocol to the Active State.
9-53

2 instance for the Access Channel MAC Protocol.
8
Field Length (bits)
MessageID 8
TransactionID 8
13
16
Field Length (bits)
MessageID 8
TransactionID 8
9-54

6
8 10.5.6.19.5.6.1 Procedures
9 The protocol constructs one or more packets out of the Security Layer packet as follows:
10 • The protocol adds the MAC Layer header specified in 9.5.6.2.1 in front of the Security
11 Layer packet,
12 • The protocol adds the FCS as defined in 9.5.6.2.2,
13 • The protocol pads the result as defined in 9.5.6.2.3,
14 • The protocol splits the result into one or more Access Channel MAC Layer capsule
15 fragments,
16 • The protocol adds the reserved bits, as defined in 9.5.6.2.4, to the capsule fragments to
17 construct the Access Channel MAC Layer packets.
18 This protocol passes the packets for transmission to the Physical Layer. An example of the
19 packet structure is shown in Figure 9.5.6.1-1.
20 Received packets are passed for further processing to the Security Layer after
21 concatenation, removing the padding, FCS checking, and removing the MAC layer headers.
22 The value of the SecurityLayerFormat and ConnectionLayerFormat fields shall be passed to
23 the Security Layer with the Security Layer packet.
MAC Layer capsule
MAC Security
Layer Layer FCS pad
header packet
MAC MAC
Layer reserved ... Layer reserved
capsule fragment capsule fragment
MAC Layer packet MAC Layer packet

24
25 Figure 9.5.6.1-1. Enhanced Access Channel MAC Packet Structure
9-55

3 10.5.6.1.1.19.5.6.1.1.1 Activate
4 If this protocol receives an Activate command in the Inactive State,
7 If this protocol receives the command in the Active State it shall be ignored.
8 10.5.6.1.1.29.5.6.1.1.2 Deactivate
10 If this protocol receives the command in the Active State,
13 10.5.6.1.29.5.6.1.2 Access Channel Structure

14 Figure 9.5.6.1.2-1 and Figure 9.5.6.1.2-2 illustrate the access probe structure and the
15 access probe sequence.
16 The Access Channel Cycle specifies the time instants at which the access terminal may
17 start an access probe. An Access Channel probe may only begin at times T such that
18 (T - AccessOffset) mod AccessCycleDuration = 0,
19 where T is CDMA System Time in slots. If the AccessOffset field is not included in the
20 AccessParameters message, then the access terminal sets AccessOffset to zero.
21 The structure of an individual access probe is shown in Figure 9.5.6.1.2-1. In each access
22 probe, the pilot (I-channel) is first enabled and functions as a preamble. After
23 PreambleLengthSlots slots, the probe data (Q-channel) is enabled for up to
24 CapsuleLengthMax × 16 slots. If the PreambleLengthSlots field is not included in the
25 AccessParameters message, then the access terminal sets PreambleLengthSlots to
26 (PreambleLength × 16).
9-56
Beginning of an Beginning of an
Access Channel Access Channel
Cycle Cycle
AccessCycleDuration AccessCycleDuration ...
Preamble
(PreambleLengthSlots slots) Capsule
AccessOffset
Actual Access Probe Transmission
3 Figure 9.5.6.1.2-1. Access Probe Structure
4 Each probe in a sequence is transmitted at increased power until any of the following
5 conditions are met:
6 • The access terminal receives an ACAck message,
7 • Transmission is aborted because the protocol received a Deactivate command, or
8 • Maximum number of probes per sequence (ProbeNumStep) has been transmitted.
9 If the value of MaxPNRandomizationDelay is not equal to zero, the access terminal
10 computes a random delay, PNRandomizationDelay, prior to the transmission of each access
11 probe.
12 Prior to the transmission of the first probe, the access terminal performs a persistence test
13 which is used to control congestion on the Access Channel.
14 Additionally the access terminal performs a persistence test in between probe sequences.
PN randomization + p PN randomization + p PN randomization + p
probe 1 2 3 Np 1 2 3 Np 1 2 3 Np
Time
probe sequence 1 2 Ns
15
16 Figure 9.5.6.1.2-2. Access Probe Sequences
17
9-57
1 10.5.6.1.39.5.6.1.3 Inactive State

3 In this state the access terminal waits for an Activate command.
4 10.5.6.1.49.5.6.1.4 Active State

5 In this state the access terminal is allowed to transmit on the Access Channel and the
6 access network is monitoring the Access Channel.
7 If the protocol receives a Deactivate command,
8 • Access terminal shall:
9 − Immediately cease transmitting on the Access Channel if it is in the process of
10 sending a probe.
11 − Return a TransmissionAborted indication if it was in the process of sending an
12 Access Channel MAC Layer capsule.
13 − Transition to the Inactive State.
14 • Access network shall ignore this command.
15 All other commands shall be ignored in this state.

17 This protocol enforces a stop-and-wait packet transmission policy over the Access Channel.
18 That is, the access terminal shall not send a new Access Channel MAC Layer capsule
19 before either:
20 • Receipt of an ACAck message for the previous capsule, or
21 • Transmission of the previous capsule failed after transmitting ProbeSequenceMax probe
22 sequences for it.
23 The access terminal shall return a TxStarted indication before transmitting the first probe
24 for an Access Channel MAC Layer capsule.105
25 The access terminal shall return a TxEnded indication either:
26 • Simultaneously with a TransmissionAborted or a TransmissionFailed indication, or
27 • TACMPTransaction seconds after a TransmissionSuccessful indication.

30 ReverseLinkSilenceDuration frames that starts at times T and it satisfies the following
31 equation:
105 Higher layer protocols use this indication as a notification that there may be an outstanding
transaction on the Access Channel; and, therefore, the access terminal should not go to sleep.
9-58
1 T mod (2048×2ReverseLinkSilencePeriod - 1) = 0,
5 10.5.6.1.4.1.29.5.6.1.4.1.2 Probe Transmission

6 The access terminal shall conform to the following rules when sending a probe:
7 1. Current SectorParameters. The access terminal shall verify that the value of
8 SectorSignature field of the latest QuickConfig message is the same as
9 SectorSignature field of the latest SectorParameters message prior to sending the
10 first probe of the first probe sequence. Both SectorSignature values (one belonging
11 to the QuickConfig message and one belonging to the SectorParameters message)
12 are public data of the Overhead Messages Protocol.
13 2. Current AccessParameters. Prior to sending the first probe of the first probe
14 sequence, the access terminal shall verify that the last AccessParameters message it
15 received is current, according to the last AccessSignature value given as public data
16 by the Overhead Messages Protocol. If the AccessParameters message is not
17 current, the access terminal shall start the AccessParameters supervision timer for
18 TACMPAPSupervision. If the timer expires before it receives the current AccessParameters
19 message, the access terminal shall return a SupervisionFailed indication and
21 3. ATI Record. The access terminal shall set the ATI and ATIType fields of the ATI
22 Record in the MAC Layer header to TransmitATI.ATI and TransmitATI.ATIType,
23 respectively (TransmitATI is provided as public data by the Address Management
24 Protocol).
25 4. Probe Power Control. The access terminal shall send the ith probe in the probe
26 sequence at a power level given by X0+(i-1)×PowerStep, where X0 represents the
27 access terminal’s open-loop mean output power of the Pilot Channel and is given by
28 X0 = - Mean RX Power (dBm) + OpenLoopAdjust + ProbeInitialAdjust
29 where
30 ProbeInitialAdjust = ProbeInitialAdjustEACMAC +
31 min(PilotStrengthCorrectionMax, max(PilotStrengthNominal – PilotStrength,
32 PilotStrengthCorrectionMin)),
33 PilotStrength is the pilot strength of the sector to which the access terminal is
34 sending the access probe, and PilotStrengthNominal,
35 PilotStrengthCorrectionMin, PilotStrengthCorrectionMax, OpenLoopAdjust are
36 values of the corresponding fields of the AccessParameters message, and the
37 Mean RX Power is estimated throughout the transmission of each probe.
38 If the PilotStrengthNominal is not included in the AccessParameters message
39 then the access terminal shall set its value to 0 dB. If the
40 PilotStrengthCorrectionMin is not included in the AccessParameters message
9-59
1 then the access terminal shall set its value to 0 dB. If the
2 PilotStrengthCorrectionMax is not included in the AccessParameters message
3 then the access terminal shall set its value to 0 dB.
4 5. Maximum Payload Size. The access terminal shall determine the maximum payload
5 size that can be transmitted on the access channel as AccessPayloadMax =
6 CapsuleLengthMax × R96 bits, where R96 is the maximum Access Channel payload
7 contained in a 9.6 kbps physical layer packet as specified in Table 9.5.6.1.4.1.2-1.
8 Table 9.5.6.1.4.1.2-1. Access Channel Rates and Payload
Transmission Rate Minimum Payload Maximum Payload

(kbps) (bits) (bits)
9.6 1 232
19.2 233 488
38.4 489 1000
9 6. Transmitted Data Rate. The access terminal may update the transmitted data rate
10 for each frame in an access channel capsule. If the SectorAccessMaxRate field is
11 omitted from the AccessParameters message, then the access terminal shall select a
12 data rate of 9600 bps. Otherwise, the access terminal shall follow all of the following
13 rules when determining the access channel transmit data rate:
14 + The access terminal shall not select a data rate higher than AccessRateMax,
15 where AccessRateMax106 is computed as:
16 AccessRateMax = max (SectorAccessMaxRate, TerminalAccessRateMax).
17 + The access terminal shall not select a data rate for which the minimum payload
18 length, as specified in Table 9.5.6.1.4.1.2-1, is greater than the size of data it
19 has to send.
20 + The access terminal shall transmit at a data rate no higher than the highest
21 data rate that can be accommodated by the available transmit power.
22 7. Probe Structure. If the PreambleLengthSlots field is not included in the
23 AccessParameters message, then the access terminal shall set PreambleLengthSlots
24 to (PreambleLength × 16). When sending a probe, the access terminal shall transmit
25 PreambleLengthSlots slots of pilot only, followed by up to CapsuleLengthMax frames
26 of probe data and pilot. The access terminal shall transmit a single Access Channel
27 Capsule per probe. The access terminal shall not change the probe data contents in
28 between probes.
29 8. Long Code Cover. The access terminal shall use the Access Channel long codes to
30 cover the entire probe. The Access Channel long code is specified in 10.3.1.3.8.2.
106 SectorAccessMaxRate is the maximum data rate at which the access terminal is allowed to
transmit on the access channel unless TerminalAccessRateMax is higher.
9-60
1 9. PN randomization. If PNRandomizationDelaySupported attribute is set to 0x00, or

2 the MaxPNRandomizationDelay field is not included in the AccessParameters
3 message or is included and equal to zero, then the PNRandomizationDelay shall be
4 set to zero. Otherwise, the access terminal shall perform the following procedure to
5 compute the PNRandomizationDelay at the start of each access probe:
6 - The access terminal shall use the hash function (see 13.414.4) to compute the
7 PNRandomizationDelay to be used for the access probe. The access terminal
8 shall use the following hash function parameters as input to the hash function
9 and set the output of the hash function to PNRandomizationDelay:
10 • Key = The 32-bit ATI field in the ATI Record as specified in ‘3’ above
11 • Decorrelate: ProbeNumber
12 • N = MaxPNRandomizationDelay
13 10. Inter-Probe Backoff. If the access terminal receives an ACAck message or it has
14 already transmitted ProbeNumStep (NP in Figure 9.5.6.1.2-2) probes in this probe
15 sequence, then it shall not send the next probe in this probe sequence. Otherwise,
16 after sending an access probe within an access probe sequence, the access terminal
17 shall perform the following procedures:
18 h. Set yTotal to 0,
19 i. Generate a pseudo random number y which is a uniformly distributed
20 integer random number between 0 and ProbeBackoff,
21 j. Add y to yTotal (i.e., yTotal = yTotal + y),
22 k. Compute τP = TACMPATProbeTimeout + (yTotal × AccessCycleDuration) –
23 ProbeTimeOutAdjust
24 l. If any portion of the access probe that would start at the first Access
25 Channel Cycle instance that occurs at least τP slots plus
26 (PNRandomizationDelay × 8) chips after the end of the previous access
27 probe overlaps with the Reverse Link Silence Interval (see 9.5.6.1.4.1.1),
28 then the access terminal shall re-start the procedures from step ‘b’ above.
9-61
1 m. Consider the access probe that would start at the first Access Channel
2 Cycle instance that occurs at least τP slots plus (PNRandomizationDelay ×
3 8) chips after the end of the previous access probe. If any portion of the
4 access probe plus the time interval that is required to receive the
5 corresponding ACAck message (as estimated by the access terminal)107
6 overlaps with slots when the access terminal does not receive the Forward
7 Channel, then the access terminal shall transmit the next access probe at
8 the first Access Channel Cycle instance that occurs at least (τP + T ×
9 AccessCycleDuration) slots plus (PNRandomizationDelay × 8) chips after the
10 end of the previous access probe where T is the minimum number of
11 intervals of length AccessCycleDuration that are needed to be added to τP in
12 order to ensure that the access probe does not overlap with the slots when
13 the access terminal does not receive the Forward Channel. If the access
14 probe starting at new start time overlaps with a Reverse Link Silence
15 Interval, then add T to ytotal and then the access terminal shall re-start the
16 procedure from step ‘b’ above.
17 n. Otherwise, (if neither condition ‘e’ nor condition ‘f’ are satisfied) the access
18 terminal shall transmit the next access probe at the first Access Channel
19 Cycle instance that occurs at least τP slots plus (PNRandomizationDelay ×
20 8) chips after the end of the previous access probe.
21 If the AccessOffset field is not included in the AccessParameters message, then the
22 access terminal shall set AccessOffset to zero.
23 If the ProbeTimeOutAdjust field is not included in the AccessParameters message,

24 then the access terminal shall set ProbeTimeOutAdjust to zero.
25 10.5.6.1.4.1.39.5.6.1.4.1.3 Access Channel Long Code Mask

26 The access terminal shall set the Access Channel long masks, MIACMAC and MQACMAC as
27 follows.
28 The 42-bit mask MIACMAC shall be as specified in Table 9.5.6.1.4.1.3-1.
29 Table 9.5.6.1.4.1.3-1. Access Channel Long Code Masks
BIT
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
MIACMAC 1 1 AccessCycleNumber Permuted (ColorCode | SectorID[23:0])

30
31 The 42-bit mask MQACMAC shall be derived from the mask MIACMAC as follows:
32 MQACMAC[k] = MIACMAC[k-1], for k = 1,…, 41
9-62
1 MQACMAC[0] = MIACMAC[0] ⊕ MIACMAC[1] ⊕ MIACMAC[2] ⊕ MIACMAC[4] ⊕ MIACMAC[5] ⊕

4 MIACMAC[26] ⊕ MIACMAC[30] ⊕ MIACMAC[32] ⊕ MIACMAC[34] ⊕ MIACMAC[41]
5 where the ⊕ denotes the Exclusive OR operation, and MQACMAC[i] and MIACMAC[i] denote the
6 ith least significant bit of MQACMAC and MIACMAC, respectively.
7 In Table 9.5.6.1.4.1.3-1:
8 • SectorID is given as public data of Overhead Messages Protocol and corresponds to the
9 sector to which the access terminal is sending the access probe.
10 • ColorCode is given as public data of Overhead Messages Protocol and corresponds to
11 the sector to which the access terminal is sending the access probe.
12 • AccessCycleNumber is defined as follows :
13 AccessCycleNumber = (SystemTime − AccessOffset) mod 256
14 Where:
15 • SystemTime is the CDMA System Time in slots corresponding to the slot in which the
16 first access probe preamble for this access probe is sent. Permuted(ColorCode |
17 SectorID[23:0]) is a permutation of the bits in ColorCode | SectorID[23:0] and is defined
18 as follows:
19 ColorCode | SectorID[23:0] = (S31, S30, S29, …, S0)
20 Permuted(ColorCode | SectorID[23:0]) =
21 (S0, S31, S22, S13, S4, S26, S17, S8, S30, S21, S12, S3, S25, S16, S7, S29, S20, S11, S2, S24,
22 S15, S6, S28, S19, S10, S1, S23, S14, S5, S27, S18, S9).
23 10.5.6.1.4.1.49.5.6.1.4.1.4 Probe Sequence Transmission

24 The access terminal shall conform to the following rules when sending a probe sequence:
25 1. Transmission of the First Probe.
26 − Prior to sending the first probe of the sequence, the access terminal shall
27 perform the following in the order specified:
28 + Silence Period Test: The access terminal shall wait until the beginning of the
29 first Access Channel Cycle such that transmission of the access probe that
30 would start at the beginning of the current Access Channel Cycle would not
31 overlap with the Reverse Link Silence Interval (see 9.5.6.1.4.1.1 for definition
32 of the Reverse Link Silence Interval).
33 + Persistence Test :
34 1. If the value of PageResponseAPersistenceSupported equals 0x01 and the
35 access terminal is initiating a connection in response to a page and the page
9-63
1 message includes a PageResponseAPersistence value then the access

2 terminal should use that access persistence value for that connection108.
3 2. If the value of EmergencyAPersistenceIncluded field of the AccessParameters
4 message equals 0x01 and the access terminal is initiating a connection
5 related to Emergency calls the access terminal should use the
6 EmergencyAPersistence specified by the AccessParameters message.
7 3. If the value of ProfilebasedAPersistenceIncluded field of the AccessParameters
8 message equals 0x01 and the access terminal is initiating a connection
9 related to a FlowProfileID specified in the AccessParameters message then
10 the access terminal should use the FlowProfileID based access persistence
11 specified by the CommonAPersistence if the CommonAPersistenceIncluded
12 field of the AccessParameters message corresponding to that FlowProfileID
13 equals 0x01. If the value of ProfilebasedAPersistenceIncluded field of the
14 AccessParameters message equals 0x01 and the access terminal is initiating
15 a connection related to a FlowProfileID specified in the AccessParameters
16 message then the access terminal should use the FlowProfileID based access
17 persistence specified by the ProfileBasedAPersistence corresponding to its
18 class if the CommonAPersistenceIncluded field of the AccessParameters
19 message corresponding to that FlowProfileID equals 0x00.
20 + if condition 1 is not true and condition 2 is not true or condition 2 is true and
21 the AT chooses to not use the EmergencyAPersistence value and condition 3 is
22 not true or condition 3 is true and the AT chooses to not use the
23 ProfileBasedAPersistence value and iIf the value of the APersistenceOverride
24 attribute is not 0xff, then the access terminal shall use the value p as
25 specified by APersistenceOverride. Otherwise, the access terminal shall
26 determine the value p as follows:
27 + If the value of the AccessTerminalClassOverride attribute is not 0xff, the access
28 terminal shall use the value p as specified by APersistence[i], where i is
29 AccessTerminalClassOverride and APersistence[i] is the (i+1)st occurrence of
30 the APersistence field in the AccessParameters message. Otherwise, the
31 access terminal shall use the value p as specified by APersistence[i] where i is
32 the class of the access terminal and APersistence[i] is the (i+1)st occurrence of
33 the APersistence field in the AccessParameters message.109 The value i=2 is
34 reserved for test access terminals. If the access terminal does not have a class
35 defined, it shall use i=0, corresponding to non-emergency access terminals. All
36 other values of i are reserved.
108 If specified the access terminal uses the PageResponseAPersistence values for initiating a
connection in response to a page message instead of the APersistence values specified by the
AccessParameters message
109 The access terminal’s class is configured through means that are outside the scope of this
specification.
9-64
1 + When p is not zero, the persistence test consists of comparing a uniformly

2 distributed random number x, 0 < x < 1, (using the procedure specified in
3 13.5) with p. If x < p the test is said to succeed. If the persistence test
4 succeeds or if the number of consecutive unsuccessful persistence tests
5 exceeds 4/p, the access terminal may transmit in the first upcoming Access
6 Channel Cycle such that no portion of the access probe overlaps with the
7 Reverse Link Silence Interval and no portion of the access probe plus the time
8 interval that is required to receive the corresponding ACAck message (as
9 estimated by the access terminal)110 will overlap with slots when the access
10 terminal does not receive the Forward Channel. If any portion of the access
11 probe overlaps with the Reverse Link Silence Interval, then the access
12 terminal shall not transmit the access probe and shall re-start the procedures
13 for Transmission of the First Probe from the beginning. Otherwise, if p is not
14 equal to zero, the access terminal shall repeat the above-mentioned Silence
15 Period Test and then the Persistence Test starting from the next Access
16 Channel Cycle. If p is equal to zero, the access terminal shall return a
17 TransmissionFailed indication and end the access.
18 + PN randomization: If PNRandomizationDelaySupported attribute is set to 0x01,
19 and the MaxPNRandomizationDelay field is included in the AccessParameters
20 message and is not equal to zero, then the access terminal shall compute the
21 PN randomization delay as follows:
22 i. The access terminal shall use the hash function (see 13.4) to
23 compute the PNRandomizationDelay to be used for the access probe.
24 The access terminal shall use the following hash function parameters
25 as input to the hash function and set the output of the hash function
26 to PNRandomizationDelay:
27 • Key = The 32-bit ATI field in the ATI Record as specified in ‘3’ of
28 9.5.6.1.4.1.2.
29 • Decorrelate: ProbeNumber
30 • N = MaxPNRandomizationDelay
31 ii. Otherwise, the access terminal shall set the PNRandomizationDelay
32 to zero.
33 iii. The access terminal shall delay start of the access probe by
34 PNRandomizationDelay × 8 chips.
35 2. Probe Contents. The access terminal shall not change the data portion of the probe
36 contents between probe sequences.
9-65
1 3. Success Condition. If the access terminal receives an ACAck message it shall stop
2 the probe sequence, including any transmission in progress, and shall return a
3 TransmissionSuccessful indication.
4 4. Failure Condition. If the access terminal has already sent ProbeSequenceMax probe
5 sequences for this access (NS in Figure 9.5.6.1.2-2), and if it does not receive an
6 ACAck message acknowledging its receipt within (TACMPATProbeTimeout + TACMPCycleLen)
7 slots after the end of the last access probe, or if the interval between two adjacent
8 probes in the access attempt is greater than TACMPATProbeTimeout + max(ProbeBackoff,
9 ProbeSequenceBackoff) × AccessCycleDuration + TACMPMaxDelayPrevProbe ms111, then the
10 access terminal shall return a TransmissionFailed indication and abort the access.
11 5. Inter-Sequence Backoff. The access terminal shall generate a uniformly distributed
12 integer random number k between 0 and ProbeSequenceBackoff. The access
13 terminal shall wait for τS = (k × AccessCycleDuration) + TACMPATProbeTimeout slots from
14 the end of the last probe of the previous sequence before repeating this sequence.

16 The access network should send an AccessParameters message at least once every
17 NACMPAccessParameters slots.
18 The access network should send an ACAck message in response to every Access Channel
19 MAC Layer capsule it receives. The message should be sent within TACMPANProbeTimeout slots of
20 receipt of the packet. The access network shall return a MACLayerCapsuleReceived
21 indication upon sending an ACAck message.
22 The access network should monitor and control the load on the Access Channel. The
23 access network may control the load by adjusting the access persistence vector,
24 APersistence, the Emergency access persistence value, or the ProfileID based access
25 persistence values or vectors sent as part of the AccessParameters message.
26 10.5.6.29.5.6.2 Header and Message Formats
27 10.5.6.2.19.5.6.2.1 MAC Layer Header

28 The access terminal shall place the following header in front of the Security Layer packet:
29
111 E.g., because the access terminal has tuned to the frequency associated with another air-
interface.
9-66
Field Length (bits)

Length 8
SessionConfigurationToken 16
ProbeNumber 4
ATI Record 34
1 Length The access terminal shall set this field to the combined length, in
2 octets, of the Security Layer packet and this MAC Layer header.
5 The access terminal shall set this field to the value of the
6 SessionConfigurationToken which is public data of the Session
9 The access terminal shall set this field to ‘1’ if security layer packet is
10 either authenticated or encrypted; otherwise, the access terminal
15 to ‘0’.
16 ProbeNumber The access terminal shall set this field to one less than the probe
17 number during the current probe sequence. The access terminal
18 shall not set the value to ‘1111’.
19 Table 9.5.6.2.1-1. ProbeNumber Encoding
Value Meaning
‘0000-1110’ One less than the probe number in a probe sequence
‘1111’ Reserved
20 ATI Record Access Terminal Identifier Record. The access terminal shall set this
21 field to the record specifying the access terminal’s ID specified by
22 TransmitATI.ATI and TransmitATI.ATIType. This record is defined in
23 13.2.
24 10.5.6.2.29.5.6.2.2 FCS
25 The FCS shall be calculated using the standard CRC-CCITT generator polynomial:
9-67
1 g ( x ) = x 32 + x 26 + x 23 + x 22 + x16 + x12 + x11 + x10 + x 8 + x 7 + x 5 + x 4 + x 2 + x1 + 1

2 The FCS shall be equal to the value computed by the following procedure and the logic
3 shown below:
4 • All shift register elements shall be initialized to logical zeros.
5 • Switches shall be set in the up position.
6 • Register shall be clocked once for each bit of Access Channel MAC Layer Capsule,
7 excluding the FCS and padding bits. The Access Channel MAC Layer Capsule is read in
8 order from MSB to LSB, starting with the MSB of the MAC Layer header
9 • Switches shall be set in the down position so that the output is a modulo-2 addition
10 with a ‘0’ and the successive shift register inputs are ‘0’.
11 • Register shall be clocked an additional 32 times for the 32 FCS bits.
Input
‘0’
x0 x1 x2 x3 x4 x26 x31
Output
‘0’
Denotes one-bit storage element

Denotes modulo-2 addition Access Channel MAC Layer Capsule;
then, down for the 32-bit
Access Channel MAC Layer Capsule FCS.
12
13 Figure 9.5.6.2-1. Access Channel MAC Layer Capsule FCS
14 10.5.6.2.39.5.6.2.3 Padding Bits

15 The access terminal shall add sufficient padding so that the length of the Access Channel
16 MAC capsule, including all payload, FCS, padding, and headers, is equal to the sum of the
17 maximum payloads corresponding to the selected data rates (as shown in Table
18 9.5.6.1.4.1.2-1) of the Access Channel frames carrying the MAC capsule. The access
19 terminal shall set the padding bits to ‘0’. The access network shall ignore the padding bits.
20 10.5.6.2.49.5.6.2.4 Reserved Bits

21 The access terminal shall add 2 reserved bits to each Access Channel capsule fragment.
22 The access terminal shall set the reserved bits to ‘0’. The access network shall ignore the
23 reserved bits.
24 10.5.6.2.59.5.6.2.5 ACAck
25 The access network sends the ACAck message to acknowledge receipt of an Access
26 Channel MAC Layer capsule.
9-68
Field Length (bits)

MessageID 8

2
3 10.5.6.2.69.5.6.2.6 AccessParameters
4 The AccessParameters message is used to convey Access Channel information to the access
5 terminals.
6
9-69
Field Length (bits)

MessageID 8
AccessCycleDuration 8
AccessSignature 16
OpenLoopAdjust 8
ProbeInitialAdjustEACMAC 5
ProbeNumStep 4
PowerStep 4
PreambleLength 3
CapsuleLengthMax 4
APersistence 6
EnhancedAccessParametersIncluded 0 or 1
PreambleLengthSlots 0 or 1
AccessOffset 0 or 2
SectorAccessMaxRate 0 or 2
ProbeTimeOutAdjust 0 or 3
PilotStrengthNominal 0 or 3
PilotStrengthCorrectionMin 0 or 3
PilotStrengthCorrectionMax 0 or 3
MaxPNRandomizationDelayIncluded 0 or 1
MaxPNRandomizationDelay 0 or 4
EmergencyAPersistenceIncluded 0 or 1
EmergencyAPersistence 0 or 6
ProfileBasedAPersistenceIncluded 0 or 1
NumProfiles 0 or 4
NumProfiles occurrences of the following fields:
ProfileID 0 or 16
CommonPersistenceIncluded 0 or 1
CommonAPersistence 0 or 6
ProfileBasedAPersistence 0 or 6
9-70
Reserved variable
2 AccessCycleDuration
3 The access network shall set this field to the duration of an Access
4 Channel Cycle in units of slots.
5 AccessSignature AccessParameters message signature. The access network shall

6 change this field if the contents of the AccessParameters message
7 change.
8 OpenLoopAdjust The access network shall set this field to the negative of the nominal
9 power to be used by access terminals in the open loop power
10 estimate, expressed as an unsigned value in units of 1 dB. The value
11 used by the access terminal is -1 times the value of this field.
12 ProbeInitialAdjustEACMAC
13 The access network shall set this field to the correction factor to be
14 used by access terminals in the open loop power estimate for the
15 initial transmission on the Access Channel, expressed as a two’s
16 complement value in units of 1 dB.
17 ProbeNumStep The access network shall set this field to the maximum number of
18 access probes access terminals are to transmit in a single access
19 probe sequence. The access network shall set this field to a value in
20 the range [1 ... 15].
21 PowerStep Probe power increase step. The access network shall set this field to
22 the increase in power between probes, in resolution of 0.5 dB. The
23 access terminal shall support all the valid values specified by this
24 field.
25 PreambleLength The access network shall set this field to the length in frames of the
26 access probe preamble in the range [1 … 7]. The access terminal
27 shall support all the valid values specified by this field. If the
28 PreambleLengthSlots field is included in this message, then, the
29 access terminal shall ignore this field CapsuleLengthMax Access
30 Channel Max Capsule length. The access network shall set this field
31 to the maximum number of frames in an Access Channel Capsule.
32 The access network shall set this field to a value in the range [2 …
33 15]. The access terminal shall support all the valid values specified
34 by this field.
9-71
1 APersistence Access persistence vector. If a value in this vector is 0x3F, the access
2 terminal shall use zero as the corresponding persistence probability;
3 otherwise, if the value of this field, n, not equal to 0x3F, the access
-n/4
5 EnhancedAccessParametersIncluded
9 the field as follows: The access network shall set this field to ‘0’ if the
10 following seven fields are omitted. Otherwise, the access network
12 PreambleLengthSlots
13 If the EnhancedAccessParametersIncluded field is not included in
14 this message, or if EnhancedAccessParametersIncluded is included
15 and is equal to ‘0’, then the access network shall omit this field.
16 Otherwise, the access network shall set this field to the length in
17 units of slots of the access probe preamble according to Table
18 9.5.6.2.6-1.
19 Table 9.5.6.2.6-1. PreambleLengthSlots Encoding
Field value Meaning

(binary)
‘0’ 4 slots
‘1’ 16 slots
20 AccessOffset If the EnhancedAccessParametersIncluded field is not included in

23 Otherwise, the access network shall set this field to indicate the slot
24 relative to the start of the AccessCycleDuration when the access
25 terminal may start an access probe according to Table 9.5.6.2.6-2.
9-72
1 Table 9.5.6.2.6-2. AccessOffset Encoding
Field value Meaning

(binary)
‘00’ 0 slots
‘01’ 4 slots
‘10’ 8 slots
‘11’ 12 slots
2 SectorAccessMaxRate
6 Otherwise, the access network shall set this field to indicate the
7 maximum data rate at which the Access Channel capsule can be
8 transmitted according to Table 9.5.6.2.6-3.
9 Table 9.5.6.2.6-3. SectorAccessMaxRate Encoding
Field value Meaning

(binary)
‘00’ 9.6 kbps

‘01’ 19.2 kbps
‘10’ 38.4 kbps
‘11’ Reserved
10 ProbeTimeOutAdjust
14 Otherwise, the access network shall set this field in slots according to
15 Table 9.5.6.2.6-4.
9-73
1 Table 9.5.6.2.6-4. ProbeTimeOutAdjust Encoding
Field value Meaning

(binary)
‘000’ 0 slots
‘001’ 16 slots
‘010’ 32 slots
‘011’ 48 slots
‘100’ 64 slots
‘101’ 80 slots
‘110’ 96 slots
‘111’ 112 slots
2 PilotStrengthNominal
6 Otherwise, the access network shall set this field according to Table
7 9.5.6.2.6-5.
8 Table 9.5.6.2.6-5. PilotStrengthNominal Encoding
Field value Meaning

(binary)
‘000’ 0 dB
‘001’ – 1 dB
‘010’ – 2 dB
‘011’ – 3 dB
‘100’ – 4 dB
‘101’ 1 dB
‘110’ 2 dB
‘111’ 3 dB
9 PilotStrengthCorrectionMin
14 9.5.6.2.6-6.
9-74
1 Table 9.5.6.2.6-6. PilotStrengthCorrectionMin Encoding
Field value Meaning

(binary)
‘000’ 0 dB
‘001’ – 1 dB
‘010’ – 2 dB
‘011’ – 3 dB
‘100’ – 4 dB
‘101’ – 5 dB
‘110’ Reserved
‘111’ Reserved
2 PilotStrengthCorrectionMax
7 9.5.6.2.6-7.
8 Table 9.5.6.2.6-7. PilotStrengthCorrectionMax Encoding
Field value Meaning

(binary)
‘000’ 0 dB
‘001’ 1 dB
‘010’ 2 dB
‘011’ 3 dB
‘100’ 4 dB
‘101’ 5 dB
‘110’ Reserved
‘111’ Reserved
9 MaxPNRandomizationDelayIncluded
13 this field as follows: The access network shall set this field to ‘0’ if the
14 MaxPNRandomizationDelay is omitted. Otherwise, the access
9-75
1 MaxPNRandomizationDelay
2 If the MaxPNRandomizationDelayIncluded field is omitted or is
3 included and is equal to ‘0’, then the access network shall omit this
4 field. Otherwise, the access network shall set this field to the
5 maximum random delay at the start of each access probe in units of
6 8 chips.
7 EmergencyAPersistenceIncluded
8 If any of the fields after this field except for Reserved are included the
11 this field as follows: If an EmergencyAPersistence value is included
12 then the access network shall set this field to one. Otherwise, the
14 EmergencyAPersistence
15 If the EmergencyAPersistenceIncluded field is omitted or is included

16 and set to ‘0’ the access network shall omit this field. The access
17 terminal should use this value when initiating connections related to
18 Emergency calls. If this value is 0x3F, the access terminal shall use
19 zero as the corresponding persistence probability; otherwise, if the
20 value of this field, n, is not equal to 0x3F, the access terminal shall
-n/4
21 use 2 as the corresponding persistence probability.
22 ProfileBasedAPersistenceIncluded
23 If any of the fields after this field except for Reserved are included the
26 this field as follows: If Profile based APersistence is included then the
27 access network shall set this field to one. Otherwise, the access
28 network shall set this field to zero.
29 NumProfiles If the ProfileBasedAPersistenceIncluded field is omitted or is included

30 and set to ‘0’ the access network shall omit this field. Otherwise, the
31 access network shall set this field to the number of ProfileIDs for
32 which application based access persistence is provided.
33 ProfileID If the ProfileBasedAPersistenceIncluded field is omitted or is included

34 and set to ‘0’ the access network shall omit this field. Otherwise, the
35 access network specifies the ProfileID for which the APersistence
36 values are specified.
37 CommonPersistenceIncluded
9-76
1 If the corresponding ProfileID field is omitted or is included and set to

2 ‘0’ the access network shall omit this field. Otherwise the access
3 network shall set this field as follows: If the access network assigns
4 the same APersistence value for all access terminal classes for the
5 corresponding ProfileID (previous field) then the access terminal shall
6 set this field to one. Otherwise, the access network shall set this field
7 to zero.
8 CommonAPersistence
9 Common Access persistence value for corresponding ProfileID. If the

10 corresponding CommonPersistenceIncluded field is omitted or is
11 included and set to ‘0’ the access network shall omit this field.
12 Otherwise the access network shall set this field to the
13 CommonAPersistence value that should be used by access terminals
14 of all access classes if initiating connections related to the
15 corresponding ProfileID. If this value is 0x3F, the access terminal
16 shall use zero as the corresponding persistence probability;
17 otherwise, if the value of this field, n, is not equal to 0x3F, the access
-n/4
19 ProfileBasedAPersistence
20 Access persistence value for corresponding ProfileID for each access

21 class. If the ProfileBasedAPersistence field is omitted or is included
22 and set to ‘0’ or the corresponding ProfileID field is omitted or the
23 CommonAPersistence field for the corresponding ProfileID is included
24 and set to ‘1’, the access network shall omit this field. Otherwise, the
25 access network shall set this field to the ProfileID based Access
26 Persistence value that the access terminal should used based on its
27 access class. If this value is 0x3F, the access terminal shall use zero
28 as the corresponding persistence probability; otherwise, if the value
-
29 of this field, n, is not equal to 0x3F, the access terminal shall use 2
n/4
30 as the corresponding persistence probability.
31 Reserved Number of bits in this field is equal to the number needed to make
32 the message length an integer number of octets. The access network
33 shall set this field to zero. The access terminal shall ignore this field.
34
Addressing Broadcast Priority 30
36 The sender sends an AttributeUpdateRequest message to offer an attribute-value for a
37 given attribute.
9-77
Field Length (bits)
MessageID 8
TransactionID 8

6
10
Field Length (bits)
MessageID 8
TransactionID 8
14
18
9-78
Field Length (bits)
MessageID 8
TransactionID 8
4
6 10.5.6.3.19.5.6.3.1 Commands
8 10.5.6.3.29.5.6.3.2 Indications

13 Enhanced Access Channel MAC Protocol. The access terminal and the access network shall
15 attributes belonging to the Enhanced Access Channel MAC Protocol:
16 • TerminalAccessRateMax
17 • APersistenceOverride
18 • AccessTerminalClassOverride
19 The negotiable simple attributes for this protocol are listed in Table 9.5.7-1. The access
20 terminal and the access network shall use as default the values in Table 9.5.7-1 typed in
21 bold italics.
9-79

0xff The access terminal shall use
persistence probability value as
specified by the appropriate
APersistence field of the
0xff APersistenceOverride 0x3f The access terminal shall use zero as

the persistence probability.
0x00 to The access terminal shall use 2
-n/4
as
0x3e the persistence probability.
0x40 to Reserved
0xfe
0x00 Maximum data rate at which the
access terminal is allowed to transmit
an access probe is 9.6 kbps.
0xfe TerminalAccessRateMax an access probe is 19.2 kbps.
an access probe is 38.4 kbps.
All other Reserved
values
0x00 Nominal offset of the access data
channel power to the pilot channel
power is zero dB.
0x01- Nominal offset of the access data
0x07 channel power to the pilot channel
0xfd DataOffsetNom power,expressed as 2’s complement
and
in units of 0.5 dB.
0xf8-0xff
All other Reserved

values
0x00 Ratio of access channel power at
9600 bps to the nominal access
0xfc DataOffset9k6
channel power at 9600 bps is zero
dB.
9-80

0x01- Ratio of access channel power at
0x07 9600 bps to the nominal access
channel power at 9600 bps,
and
expressed as 2’s complement number
0xf8-0xff in units of 0.25 dB.
All other Reserved

values
dB.
0xfb DataOffset19k2 channel power at 19200 bps,
and
expressed as a 2’s complement
0xf8-0xff number in units of 0.25 dB.
All other Reserved

values
dB.
0xfa DataOffset38k4 channel power at 38400 bps,
and
expressed as a 2’s complement
0xf8-0xff number in units of 0.25 dB.
All other Reserved

values
0xff The access terminal uses persistence
probability value as specified by
APersistence[i] of the
AccessParameters message where i is
the class of the access terminal.
AccessTerminalClassOve 0x00 to The access terminal uses persistence
0xf9
rride 0x03 probability value as specified by
APersistence[AccessTerminalClassOve
rride] of the AccessParameters
message.
All other Reserved
values
9-81

0x00 PN randomization is not supported.
PNRandomization 0x01 PN randomization is supported.

0xf8
DelaySupported
All other Reserved
values
3 10.5.7.19.5.7.1 InitialConfiguration Attribute

4

Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
ProbeSequenceMax 4 3
ProbeBackoff 4 4
ProbeSequenceBackoff 4 8
Reserved 4 N/A
}
7 Length field.
8 AttributeID Parameter set identifier. The access network shall set this field to
9 0x00.
11 complex attribute. The access network should change this field for
12 each set of values for this complex attribute.
13 ProbeSequenceMax Maximum number of probe sequences. The access network shall set
14 this field to the maximum number of probe sequences for a single
15 access attempt. The access network shall set this field to a value in
16 the range [1 … 15]. The access terminal shall support all the valid
18 ProbeBackoff Inter-probe backoff. The access network shall set this field to the
19 upper limit of the backoff range (in units of AccessCycleDuration)
9-82
1 that the access terminal is to use between probes. The access

3 ProbeSequenceBackoff
4 Inter-probe sequence backoff. The access network shall set this field
5 to the upper limit of the backoff range (in units of
6 AccessCycleDuration) that the access terminal is to use between
7 probe sequences. The access terminal shall support all the valid

12
9-83

NACMPType Type field for this protocol Table 2.5.4-1
NS1ACMP Subtype field for this protocol 0x0001
Number of different persistence
NACMPAPersist 4
values
The recommended maximum
number of slots between
NACMPAccessParameters 3 * TACMPCycleLen
transmission of two consecutive
AccessParameters supervision
TACMPAPSupervision 12 * TACMPCycleLen
timer
Time to receive an acknowledgment
TACMPATProbeTimeout at the access terminal for a probe 128 slots
before sending another probe
Maximum time to send an
TACMPANProbeTimeout acknowledgment for a probe at the 96 slots
access network
Time for access terminal to wait
after a successful transmission
TACMPTransaction 1 second
before returning a TxEnded
indication
Length of Control Channel Cycle
TACMPCycleLen used by the Access Channel MAC 256 slots
Protocol
A constant that determines the
time for the access terminal to wait
until after transmitting an access
TACMP_MaxDelayPrevProbe 300 slots
probe in the access attempt before
returning a TransmissionFailed
indication

4 protocol.
9-84
1 10.69.6 Default Forward Traffic Channel MAC Protocol
2 10.6.19.6.1 Overview
3 The Default Forward Traffic Channel MAC Protocol provides the procedures and messages
4 required for an access network to transmit and an access terminal to receive the Forward
5 Traffic Channel. Specifically, this protocol addresses Forward Traffic Channel addressing
6 and Forward Traffic Channel rate control. This protocol operates with the Default (Subtype
7 0) Physical Layer Protocol or the Subtype 1 Physical Layer Protocol.
8 The access network maintains an instance of this protocol for every access terminal.
10 • Inactive State: In this state, the access terminal is not assigned a Forward Traffic
11 Channel. When the protocol is in this state, it waits for an Activate command.
12 • Variable Rate State: In this state, the access network transmits the Forward Traffic
13 Channel at a variable rate, as a function of the access terminal’s DRC value.
14 • Fixed Rate State: In this state, the access network transmits the Forward Traffic
15 Channel to the access terminal from one particular sector, at one particular rate.
16 The protocol states and allowed transitions between the states are shown in Figure 9.6.1-1.
17 The rules governing these transitions are provided in sections 9.6.6.1.3, 9.6.6.1.4, and
18 9.6.6.1.5 for transitions out of the Inactive State, Variable Rate State, and Fixed Rate State.
Initial State
Deactivate
Inactive Variable
State Rate State
Activate
AT Dependent
Deactivate
AT Dependent
Fixed Rate
State
19
20 Figure 9.6.1-1. Default Forward Traffic Channel MAC Protocol State Diagram
9-85
2 10.6.2.19.6.2.1 Commands
4 • Activate
5 • Deactivate

9 10.6.2.39.6.2.3 Public Data

12 • DRCGating
13 • DRCLength
14 • DRCChannelGain
15 • DRCLockPeriod
16 • DRCLockLength
19 • Transmission rate in the Fixed Rate State

21 The transmission unit of this protocol is a Forward Traffic Channel MAC Layer packet.
22 Each packet consists of one Security Layer packet.

9-86

9 State.
11 10.6.5.19.6.5.1 Procedures

22 − DRCGating
23 − DRCLockPeriod
24 − DRCLockLength
26 then
33 instance, then the access network and the access terminal shall perform the following
35 − The access terminal and the access network shall set the initial state for the
36 InConfiguration instance of this protocol to the Inactive State.
9-87

2 instance for the Forward Traffic Channel MAC Protocol.
8
Field Length (bits)
MessageID 8
TransactionID 8
13
16
Field Length (bits)
MessageID 8
TransactionID 8
9-88

6
8 10.6.6.19.6.6.1 Procedures
9 The protocol constructs a Forward Traffic Channel MAC Layer packet out of the Security
10 Layer packet by adding the MAC Layer trailer as defined in 9.6.6.2.1.
MAC Layer packet
Security MAC
Layer Layer
packet trailer
13
14 Figure 9.6.6-1. Forward Traffic Channel MAC Layer Packet Structure
15 If the MACLayerFormat field of the MAC Layer trailer is equal to ‘1’, received packets are
16 passed for further processing to the Security Layer after removing the layer-related trailer.
17 The access terminal shall discard the MAC packet if the MACLayerFormat field of the MAC
18 Layer trailer is equal to ‘0’. The ConnectionLayerFormat field within the MAC Layer trailer
19 shall be passed to the Security Layer with the Security Layer packet.
21 10.6.6.1.1.19.6.6.1.1.1 Activate
22 If this protocol receives an Activate command in the Inactive State, the access terminal and
23 the access network shall transition to the Variable Rate State.
24 If this protocol receives the command in any other state it shall be ignored.
25 10.6.6.1.1.29.6.6.1.1.2 Deactivate
26 If the protocol receives a Deactivate command in the Variable Rate State or the Fixed Rate
27 State,
28 • The access terminal shall cease monitoring the Forward Traffic Channel, shall cease
29 transmitting the DRC Channel, and shall transition to the Inactive State.
9-89
1 • The access network should cease transmitting the Forward Traffic Channel to this
2 access terminal, should cease receiving the DRC channel from this access terminal,
3 and should transition to the Inactive State.
4 If this command is received in the Inactive State it shall be ignored.
5 10.6.6.1.29.6.6.1.2 Forward Traffic Channel Addressing

6 Transmission on the Forward Traffic Channel is time division multiplexed. At any given
7 time, the channel is either being transmitted or not; and, if it is being transmitted, it is
8 addressed to a single user. When transmitting the Forward Traffic Channel, the access
9 network uses the MACIndex to identify the target access terminal.
10 Requirements for Forward Traffic Channel addressing are part of the Physical Layer.
11 10.6.6.1.39.6.6.1.3 Inactive State

12 When the protocol is in the Inactive State, the access terminal and the access network wait
13 for an Activate command.
14 10.6.6.1.49.6.6.1.4 Variable Rate State

15 In the Variable Rate State, the access network transmits at the rate dictated by the Data
16 Rate Control (DRC) Channel transmitted by the access terminal. The access terminal shall
17 use either a DRC cover index 0 or the DRC Cover index associated with a sector in its
18 Active Set. The DRC cover index 0 is called the “null cover”. A DRC cover that corresponds
19 to a sector in the access terminal’s Active Set is called a “sector cover”. The access terminal
20 is said to be pointing the DRC at a sector in its Active Set if the access terminal is using the
21 DRC cover corresponding to that sector.
22 The access terminal shall perform the supervision procedures described in 9.6.6.1.6.1 in
23 the Variable Rate State.
24 10.6.6.1.4.19.6.6.1.4.1 DRC and Packet Transmission Requirements

25 The access terminal uses the DRC cover to specify the transmitting sector (the access
26 terminal is said to point the DRC at that sector). The access terminal uses the DRC value to
27 specify the requested transmission rate.
28 10.6.6.1.4.1.19.6.6.1.4.1.1 Access Terminal Requirements

29 The access terminal shall obey the following rules when transmitting the DRC:
30 • access terminal shall use DRCLength slots to send a single DRC.
31 • The DRC value and/or cover may change in slots T such that:
32 (T + 1 – FrameOffset) mod DRCLength = 0,
33 where T is the CDMA System Time in slots.
34 • If the value of the DRCGating attribute is equal to 1, the access terminal shall transmit
35 the DRC over a one slot duration, starting in slot T that satisfies the following equation:
9-90

2 • DRC cover shall obey the following rules:
3 − If the access terminal’s current DRC cover is a sector cover, then the access
4 terminal’s next DRC cover shall not be a different sector cover. It may only be
5 the same sector cover or a null cover.
6 − If the access terminal’s most recent sector cover corresponds to sector A, then
7 the access terminal shall not use a sector cover corresponding to a sector B
8 until the access terminal has determined that packets received from sector B
9 will not overlap in time with packets received from sector A.
10 − The access terminal may inhibit transmission of data from the access network
11 by covering the DRC with the null cover. The access terminal shall set the DRC
12 to the value it would have used had it requested data from the best serving
13 sector.
14 − The access terminal shall use either the null cover or a sector cover (see
15 9.6.6.1.4) as DRC cover.
16 • Access terminal shall set the DRC to one of the valid values in Table 9.6.6.1.4.1-1,
17 corresponding to the rate it requests.
18 • Access terminal shall set the DRC to the maximum value that channel conditions
19 permit for the sector at which the access terminal is pointing its DRC. The access
20 terminal uses the null rate if the channel conditions do not permit even the lowest non-
21 null rate.
9-91
1 Table 9.6.6.1.4.1-1. DRC Value Specification
DRC Packet Length

Rate (kbps)
value (Slots)
0x0 null rate N/A
0x1 38.4 16
0x2 76.8 8
0x3 153.6 4
0x4 307.2 2
0x5 307.2 4
0x6 614.4 1
0x7 614.4 2
0x8 921.6 2
0x9 1228.8 1
0xa 1228.8 2
0xb 1843.2 1
0xc 2457.6 1
0xd Invalid N/A
0xe Invalid N/A
0xf Invalid N/A
2 • If the access terminal has finished sending its DRC to sector A during slot n specifying
3 a requested a non-null rate r, then the access terminal shall attempt to receive a packet
4 transmitted at rate r from sector A during slots n + 1 through n + DRCLength if it is not
5 already receiving a packet during these slots.
6 • If the access terminal has finished sending its DRC to sector A during slot n requesting
7 the null rate, and if the value of the NullRateDRC38.4Enable attribute is 0x0001, then
8 the access terminal shall attempt to receive a packet transmitted at rate 38.4 kbps from
9 sector A during slots n + 1 through n + DRCLength if it is not already receiving a packet
10 during these slots.
11 • If the access terminal detects a preamble from any sector, the access terminal shall
12 continue to receive the entire packet from that sector, using the requested rate.
13 • If the access terminal receives a DRCLock bit that is set to ‘0’ from a cell associated
14 with a sector in its active set and the access terminal is pointing its DRC to a sector
15 associated with that cell, the access terminal should stop pointing its DRC at that
16 sector.
17 10.6.6.1.4.1.29.6.6.1.4.1.2 Access Network Requirements

18 The access network shall obey the following rules when processing the DRC and sending a
19 packet to the access terminal:
9-92
1 • If the access network begins transmitting a packet to the access terminal at slot T, it
2 shall do so at the rate specified by the DRC whose reception was completed in slot
3 T – 1 – ((T – FrameOffset) mod DRCLength).
4 • If the DRC whose reception was completed in slot
5 T – 1 – ((T – FrameOffset) mod DRCLength) specified the null rate, and if the value of the
6 NullRateDRC38.4Enable attribute is 0x0001, then the access network may begin
7 transmitting a packet to the access terminal at slot T using the 38.4 kbps rate.
8 • Once the access network initiates a packet transmission to a particular access
9 terminal, it shall continue transmitting to that access terminal until it receives a
10 PhysicalLayer.ForwardTrafficCompleted indication.
11 The access network shall discard the FixedModeXoff message if the access network receives
12 the message in the Variable Rate State.
13 10.6.6.1.4.29.6.6.1.4.2 Transitions from the Variable Rate State

14 The access terminal may initiate procedures for transitioning to the Fixed Rate State at any
15 time. The access terminal shall perform the following steps in order to transition to the
16 Fixed Rate State:
17 • The access terminal shall start covering the DRC with the null cover.
18 • The access terminal shall wait until it has determined that it will not be served by any
19 sector and then, the access terminal shall send the FixedModeEnable message
20 specifying:
21 − A sector in the active set.
22 − A data rate.
23 − An “end time” for the operation in the Fixed Rate mode.
24 The access terminal shall transition to the Fixed Rate State after sending a
25 FixedModeEnable message. The access network shall transition to the Fixed Rate State
26 after reception of a FixedModeEnable message.
27 10.6.6.1.59.6.6.1.5 Fixed Rate State

28 In the Fixed Rate State, the access terminal receives Forward Traffic Channel MAC Layer
29 packets at a specific rate from a specific sector. When the access network transmits a
30 Forward Traffic Channel MAC Layer packet to the access terminal, it uses the specified
31 sector at the specified rate.
32 While in this state, the access terminal may send a FixedModeEnable message (e.g., to
33 extend the EndTime specified in the last FixedModeEnable message). If the access terminal
34 sends a FixedModeEnable message in this state, then the access terminal shall set the
35 fields included in the message according to the following rules:
36 • The <DRCCover, TCAMessageSequence> pair of fields included in the message shall be
37 set to the value of the <DRCCover, TCAMessageSequence> specified in the last
38 FixedModeEnable message sent,
9-93
1 • The DRCValue field included in the message shall be set to the value of the DRCValue
2 specified in the last FixedModeEnable message sent, and
3 • The EndTime field included in the message shall not specify a time earlier than the time
4 specified by the EndTime included in the last FixedModeEnable message sent.
6 the Fixed Rate State.
7 10.6.6.1.5.19.6.6.1.5.1 DRC Requirements

8 The access terminal shall cover the DRC with the null cover. The null cover is defined in
9 9.6.6.1.4.
10 The access terminal shall set the DRC value to the value it would have requested from this
11 serving sector, had it been in the Variable Rate State.
12 10.6.6.1.5.29.6.6.1.5.2 Packet Transmission

13 The access network shall only schedule Forward Traffic Channel MAC Layer packet
14 transmissions to the access terminal on the Forward Traffic Channel transmitted by the
15 sector specified in the last FixedModeEnable message received from the access terminal.
16 The access network shall set the transmission rate of any Forward Traffic Channel MAC
17 Layer packets sent to the access terminal to the rate specified in the last FixedModeEnable
18 message received from the access terminal. If the access network begins a Forward Traffic
19 Channel MAC Layer packet transmission, it shall continue transmitting the packet until it
20 receives a PhysicalLayer.ForwardTrafficCompleted indication. The access terminal shall
21 monitor the Forward Traffic Channel transmitted by the sector specified in the
22 FixedModeEnable message.
23 If the access terminal is not able to receive Forward Traffic Channel MAC Layer packets
24 from the sector specified in the last FixedModeEnable message at the rate specified in that
25 message, it should send at least one FixedModeXoff message to the access network112. The
26 access network shall not start transmission of any new Forward Traffic Channel MAC Layer
27 packets to the access terminal after reception of a FixedModeXoff message until the access
28 network transitions to the Variable Rate State.
29 10.6.6.1.5.39.6.6.1.5.3 Transitions from the Fixed Rate State

30 The access terminal shall transition to the Variable Rate State when either of the following
31 conditions is satisfied:
32 • If the current CDMA System Time is greater than or equal to the time specified by the
33 EndTime field in the last FixedModeEnable message sent.
112 Note that sending a FixedModeXoff message does not cause a transition out of the Fixed Rate
State. The process of determining the precise time to send the FixedModeXoff message when access
terminal is not able to receive Forward Traffic Channel MAC layer packets is left to the access
terminal implementation.
9-94
1 • If the sector specified in the last sent FixedModeEnable message is no longer a member
2 of the access terminal’s Active Set.
3 The access network shall transition to the Variable Rate State when either of the following
5 • If the current CDMA System Time is greater than or equal to the time specified by the
6 EndTime field in the last FixedModeEnable message received.
7 • If the access network determines that sector specified in the last received
8 FixedModeEnable message is no longer a member of the access terminal’s Active Set.
9 The time specified by EndTime (denoted by EndTimeLong) is computed as follows:
10 EndTimeLong = SystemTime + (EndTime – SystemTime[15:0]) mod 216,
11 Where, SystemTime is the current CDMA System Time in units of slots.
12 10.6.6.1.69.6.6.1.6 Supervision Procedures
13 10.6.6.1.6.19.6.6.1.6.1 DRC Supervision

14 The access terminal shall perform supervision on the DRC as follows:
15 • The access terminal shall set the DRC supervision timer for TFTCMDRCSupervision when it
16 transmits a null rate DRC.
17 • The access terminal shall disable the timer if the DRC supervision timer is active and
18 any of the following conditions is true:
19 − the access terminal requests a non-null rate
20 − the access terminal successfully receives a Forward Traffic Channel packet

21 addressed to the access terminal’s unicast address and the value of the
22 NullRateDRC38.4Enable attribute is equal to 0x0001.
23 • The access terminal may disable the timer if the DRC supervision timer is active and
24 the access terminal successfully receives a Control Channel packet.
25 • If the DRC supervision timer expires, the access terminal shall disable the Reverse
26 Traffic Channel transmitter and set the Reverse Traffic Channel Restart timer for time
27 TFTCMPRestartTx.
28 • If the access terminal generates consecutive non-null rate DRC values for more than
29 NFTCMPRestartTx slots or successfully receives a packet, the access terminal shall disable
30 the Reverse Traffic Channel Restart timer and shall enable the Reverse Traffic Channel
31 transmitter.
32 • If the Reverse Traffic Channel Restart timer expires, the access terminal shall return a
33 SupervisionFailed indication and transition to the Inactive State.
34 10.6.6.1.6.29.6.6.1.6.2 ForwardTrafficValid Monitoring

35 The access terminal shall monitor the bit associated with its MACIndex in the
36 ForwardTrafficValid63To0 field made available by the Overhead Messages Protocol. If the
9-95
1 Overhead Messages Protocol does not provide a ForwardTrafficValid63To0 field associated

2 with the access terminal, then the access terminal shall behave as if the field were set to
3 ‘0’. If this bit is set to 0, the access terminal shall return a SupervisionFailed indication and
5 10.6.6.29.6.6.2 Trailer and Message Formats
6 10.6.6.2.19.6.6.2.1 MAC Layer Trailer

7 The access network shall set the MAC Layer Trailer as follows:
8
Field Length (bits)

MACLayerFormat 1
12 to ‘0’.
13 MACLayerFormat The access network shall set this field to ‘1’ if the MAC layer packet
14 contains a valid payload; otherwise, the access network shall set this
16 10.6.6.2.29.6.6.2.2 FixedModeEnable
17 The access terminal sends the FixedModeEnable message to indicate a transition to the
18 Fixed Rate State.
19
Field Length (bits)

MessageID 8
DRCCover 3
DRCValue 4
EndTime 16
Reserved 1
22 The access terminal shall set this field to the MessageSequence field
23 of the TrafficChannelAssignment message that specifies the
24 association between the DRCCover field in this message and the
25 sector in the Active Set.
9-96
1 DRCCover The access terminal shall set this field to the DRC cover associated
2 with the sector in its Active Set from which it wants to receive
3 packets on the Forward Traffic Channel.
4 DRCValue The access terminal shall set this field to one of the valid DRC values
5 in Table 9.6.6.1.4.1-1 to indicate the rate at which it wants to receive
6 packets.
7 EndTime The access terminal shall set this field to the least significant 16 bits
8 of the CDMA System Time in units of slots until which (inclusive) it
9 requests to remain in the Fixed Rate State.
12
13 10.6.6.2.39.6.6.2.3 FixedModeXoff
14 The access terminal sends the FixedModeXoff message if it is not able to receive packets
16 message.
17
Field Length (bits)

MessageID 8
19
21 10.6.6.3.19.6.6.3.1 Commands Sent

23 10.6.6.3.29.6.6.3.2 Indications
24 This protocol registers to receive the following indication:
25 • PhysicalLayer.ForwardTrafficCompleted
9-97

2 The following attributes and default values are defined (see 13.3 for attribute record
3 definition).

5 The negotiable simple attribute for this protocol is listed in Table 9.6.7.1-1. The access
6 terminal shall use as defaults the values in Table 9.6.7.1-1 that are typed in bold italics.

0x0000 Continuous transmission
0x0001 Discontinuous transmission

0xff DRCGating
All other Reserved
values
0x0000 The access network will not
serve an access terminal
requesting the null rate.
0x0001 The access network may serve
0xfd NullRateDRC38.4Enable
an access terminal requesting
the null rate at 38.4 kbps.
All other Reserved
values
8
9 The access terminal shall support the default value of these attributes.
11 10.6.7.2.19.6.7.2.1 DRCLock Attribute

12 The following DRCLock complex attribute and default values are defined:
13
9-98

Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
DRCLockPeriod 1 ‘1’
DRCLockLength 2 ‘01’
Reserved 5 N/A
3 Length field.
6 complex value.
7 DRCLockPeriod The access network shall set this field according to Table 9.6.7.2.1-1
8 to specify the time interval in units of slots between transmission of
9 two consecutive DRCLock bit transmissions on the Forward MAC
10 Channel. The access terminal shall support all the values of this
11 attribute.
12 Table 9.6.7.2.1-1. DRCLockPeriod Encoding.
Field
DRCLockPeriod
value
(slots)
(binary)
‘0’ 8
‘1’ 16
13 DRCLockLength The access network shall set this according to Table 9.6.7.2.1-2 to
14 specify the number of times that a DRCLock bit is repeated. The
15 access terminal shall support all the values of this attribute.
9-99
1 Table 9.6.7.2.1-2. DRCLockLength Encoding
Field
value DRCLockLength
(binary)
‘00’ 4
‘01’ 8
‘10’ 16
‘11’ 32
2 Reserved This field shall be set to all zeros.
3 10.6.7.2.29.6.7.2.2 HandoffDelays Attribute

4 The following HandoffDelays complex attribute and default values are defined:
5

Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
SofterHandoffDelay 8 0x01
SoftHandoffDelay 8 0x10
8 Length field.
11 complex value.
12 SofterHandoffDelay The access network shall set this field to the minimum interruption
13 that the access terminal should expect when the access terminal
14 switches the DRC from a source sector to a target sector where the
15 target sector is such that its Forward Traffic Channel carries the
16 same closed-loop power-control bits as the source sector (see
17 SofterHandoff field of the Route Update Protocol
18 TrafficChannelAssignment message). The access network shall
19 specify this field in units of 8 slots. The value of this field excludes
20 the duration of time that the access terminal uses a null cover for the
21 DRC when it switches from the source sector to the target sector (see
22 9.6.6.1.4.1.1). The access terminal may use this number to adjust its
9-100
1 algorithm controlling DRC switching. The access terminal shall

2 support all the values of this attribute.
3 SoftHandoffDelay The access network shall set this field to the minimum interruption
4 that the access terminal should expect when the access terminal
5 switches the DRC from a source sector to a target sector where the
6 target sector is such that its Forward Traffic Channel does not always
7 carry the same closed-loop power-control bits as the source sector
8 (see SofterHandoff field of the Route Update Protocol
9 TrafficChannelAssignment message). The access network shall
10 specify this field in units of 8 slots. The value of this field excludes
11 the duration of time that the access terminal uses a null cover for the
12 DRC when it switches from the source sector to the target sector (see
13 9.6.6.1.4.1.1). The access terminal may use this number to adjust its
14 algorithm controlling DRC switching. The access terminal shall
15 support all the values of this attribute.

17

NFTCMPType Type field for this protocol Table 2.5.4-1
NFTCMPDefault Subtype field for this protocol 0x0000
Number of consecutive slots of non-null rate
DRCs to re-enable the Reverse Traffic
NFTCMPRestartTx 16
Channel transmitter once it is disabled due
to DRC supervision failure.
TFTCMDRCSupervision DRC supervision timer 240 ms
12 Control
TFTCMPRestartTx Reverse Channel Restart Timer Channel
cycles

21 protocol.
9-101
1 10.79.7 Enhanced Forward Traffic Channel MAC Protocol
2 10.7.19.7.1 Overview
3 The Enhanced Forward Traffic Channel MAC Protocol provides the procedures and
4 messages required for an access network to transmit and an access terminal to receive the
5 Forward Traffic Channel. Specifically, this protocol addresses Forward Traffic Channel
6 addressing and Forward Traffic Channel rate control. This protocol operates with the
13 Channel to the access terminal, in accordance with the DRC Channel received from the
14 access terminal.
15 • Fixed DRC State: In this state, the access network transmits the Forward Traffic
16 Channel to the access terminal, in accordance with the FixedModeEnable message
17 received from the access terminal.
20 9.7.6.1.9.2 for transitions out of the Inactive State, Variable Rate State, and Fixed DRC
21 State.
Initial State
Deactivate
Inactive Variable
State Rate State
Activate
AT Dependent
Deactivate
AT Dependent
Fixed DRC
State
22
23 Figure 9.7.1-1. Enhanced Forward Traffic Channel MAC Protocol State Diagram
9-102
2 10.7.2.19.7.2.1 Commands
4 • Activate
5 • Deactivate

9 10.7.2.39.7.2.3 Public Data

12 • DRCGating
14 • DRCLength
15 • DSCLength
17 • DRCChannelGainBase
18 • DSCChannelGain
19 • DSCChannelGainBase
21 • MultiUserPacketsEnabled
22 • DeltaACKChannelGainMUP
25 • State of the Enhanced Forward Traffic Channel MAC Protocol (Inactive State, Variable
26 Rate State, or Fixed DRC State)
27 • The DRC value and DRC cover specified by the latest FixedModeEnable message, if in
28 Fixed DRC State

31 Each Forward Traffic Channel MAC Layer packet consists of zero or more Security Layer
32 packets.
9-103

14 10.7.5.19.7.5.1 Procedures

25 − DRCGating
27 − DSCLength
28 − MultiUserPacketsEnabled
29 − DeltaACKChannelGainMUP
31 then
9-104
13
Field Length (bits)
MessageID 8
TransactionID 8

18
21
9-105
Field Length (bits)
MessageID 8
TransactionID 8

9
11 10.7.6.19.7.6.1 Procedures
12 At the access network, the Enhanced Forward Traffic Channel MAC Protocol encapsulates
13 zero or more Security Layer packets into a MAC Layer packet and passes the MAC Layer
14 packet for transmission to the Physical Layer Protocol, along with the Preamble MAC Index
15 and Transmission Format of the Forward Traffic Channel. The choice of Transmission
16 Format is governed by the DRC value and DRC cover information received from the access
17 terminal.
18 10.7.6.1.19.7.6.1.1 MAC Layer Packet

19 The MAC Layer packet is the basic unit of data provided by the Enhanced Forward Traffic
20 Channel MAC protocol to the Physical Layer Protocol. The MAC Layer packets shall be of
21 one of the following three two types:
22 • Single User Simplex
23 •Single User Multiplex
24 • Multi-User
25 The access network shall not transmit Single User Multiplex packets to the access terminal
26 if the SingleUserMultiplexPacketsEnabled attribute is set to 0x00. The access network shall
27 not transmit a Multi-User packet to the access terminal if the MultiUserPacketsEnabled
28 attribute is set to 0x00.
9-106
1 Single User Simplex packets are also and Single User Multiplex packets are collectively
2 referred to as Single User packets. The structure of a MAC Layer packet is shown in Figure
3 9.7.6.1.1-1. The MAC Layer packet consists of the following (in order):
4 • MAC Layer Header (which may be empty)
5 • MACHeaderDelimiter (if required)
6 • MAC Layer Payload
7 • PAD (if required)
8 • MAC Layer Trailer
9 The size of a MAC Layer packet takes on a discrete set of values, as shown in Figure
10 9.7.6.1.1-1.
MAC Layer Packet

98, 226, 482, 994, 2018, 3042, 4066, or 5090 bits
MAC MAC MAC MAC
MACHeaderD
Layer Layer Layer PAD Layer
elimiter
11
packet Header Payload Trailer
12 Figure 9.7.6.1.1-1. Enhanced Forward Traffic Channel MAC Layer Packet Structure
13 The MAC Layer payload consists of zero or more Security Layer packets addressed to zero
14 or more access terminals. The MAC Layer Header (if included), MACHeaderDelimiter (if
15 included), and MAC Layer Trailer are used to provide information needed to parse the
16 contents of the MAC Layer Payload and to specify the type of the MAC Layer packet (Single
17 User Simplex, Single User Multiplex, or Multi-User).
18 The MAC Layer payload may be followed by padding, which consists of a sequence of all
19 ‘0’s. The size of the padding sequence is chosen such that the overall size of the MAC Layer
20 packet is one of 98, 226, 482, 994, 2018, 3042, 4066, or 5090 bits.
21 10.7.6.1.1.19.7.6.1.1.1 Description of MAC Layer packet types

22 A Single User Simplex MAC Layer packet is used to carry one Security Layer packet in its
23 payload and is addressed to one access terminal. The MAC Layer Payload size equals the
24 size of the MAC Layer Packet minus the size of the MAC Layer Trailer. A Single User
25 Simplex packet consists of the following (in order):
26 • An empty MAC Layer Header
27 • A MAC Layer Payload consisting of one Security Layer packet
28 • No PAD
29 The Security Layer packet in a Single User Simplex packet contains a Format A or Format
30 B Connection Layer packet.
31 A Single User Multiplex MAC Layer packet is used to carry in its payload, one or more
32 Security Layer packets addressed to one access terminal. A Single User Multiplex packet
33 consists of the following (in order):
9-107
1 •Non-empty MAC Layer Header

2 •MACHeaderDelimiter (if required)
3 •MAC Layer Payload consisting of one or more Security Layer packets addressed to one
4 access terminal
5 •PAD (if required)
6 •MAC Layer Trailer
7 Each Security Layer packet in a Single User Multiplex packet contains a Format A
8 Connection Layer packet.
9 A Multi-User MAC Layer Packet is used to carry in its payload, zero or more Security Layer
10 packets addressed to zero or more access terminals. A Multi-User packet consists of the
11 following (in order):
12 • Non-empty MAC Layer Header
14 • MAC Layer Payload consisting of zero or more (max of eight) Security Layer packets
17 Each Security Layer packet in a Multi-User packet contains a Format A or Format B
19 10.7.6.1.1.29.7.6.1.1.2 Construction of MAC Layer packets

20 The structure of Single User Simplex MAC packets, Single User Multiplex packets and
21 Multi-User MAC packets are shown in Figure 9.7.6.1.1.2-1, Figure 10.7.6.1.1.2-2, and
22 Figure 9.7.6.1.1.2-2 respectively. The type of MAC Layer packet may be inferred from the
23 Preamble MAC Index and the MAC Layer Trailer. When the Preamble MAC Index is set to
24 the MAC Index assigned to the access terminal, the MAC Layer Trailer field indicates a
25 Single User Simplex packet if equal to ‘01’ or ‘11’, or a Single User Multiplex packet if equal
26 to ‘10’. For Single-User MAC packets, the values of ‘00’ and ‘10’ for the MAC Trailer is are
27 reserved. The access terminal shall not pass the payload of the Single-User Simplex MAC
28 packet to the higher layer if the MAC Layer Trailer is set to ‘00’ or ‘10’.
29 When the Preamble MAC Index is set to a Multi-User Preamble MAC Index as specified in
30 9.7.6.1.2, the access network shall set the MAC Trailer to ‘00’. For Multi-User MAC
31 packets, the values for the MAC Trailer other than ‘00’ are reserved. The access terminal
32 shall not pass the payload of the Multi-User MAC packet to the higher layer if the MAC
33 Layer Trailer associated with the Multi-User packet is set to any value other than ’00’.
9-108
96, 224, 480, 992, 2016, 3040, 4064, or 5088 bits 2 bits
( 12, 28, 60, 124, 252, 380, 508, or 636 octets )
MAC Layer Payload MAC

trailer
( Security Layer Packet ) 01 or 11
2 Figure 9.7.6.1.1.2-1 Format of Forward Traffic Channel Single User Simplex MAC
3 Layer Packet
96, 224, 480, 992, 2016, 3040, 4064, or 5088 bits 2 bits
( 12, 24, 60, 124, 252, 380, 508, or 636 octets )
MAC
MAC Layer Payload
MAC Layer Header MACHeaderDelimiter PAD Layer
( n Security Layer Packets )
( n Length Fields ) (optional) (optional) Trailer
( n = 1, 2, ... )
10
n octets
4
5 Figure 10.7.6.1.1.2-2 Format of Forward Traffic Channel Single User Multiplex MAC
6 Layer Packet
96, 224, 480, 992, 2016, 3040, 4064, or 5088 bits 2 bits
( 12, 28, 60, 124, 252, 380, 508, or 636 octets )

MAC Layer Header
nth nth MACHeader MAC Layer Payload MAC
1st 1st PAD
PacketInfo Length Delimiter ( n Security Layer Layer
PacketInfo Length (optio
Field Field Field Packets ) Trailer
Field Field nal)
0≤n ≤8 0 ≤ n ≤ 8 (optional) ( n = 0, 2, ..., 8 ) 00
2n octets
PacketInfo field Length : Length of the Security Layer packet (in octets)
1 octet
Format MACIndex
1 bit 7 bits
7
8 Figure 9.7.6.1.1.2-2 Format of Forward Traffic Channel Multiuser MAC Layer Packet
9 The access network shall construct a Single User Simplex MAC Layer packet as shown
10 below:
11
Field Length (bits)
Security Layer Packet 96, 224, 480, 992, 2016,

3040, 4064, or 5088
MAC Layer Trailer 2
12 Security Layer Packet
9-109
1 The access network shall set this field to a Security Layer packet
2 from the Security Protocol, containing a Format A or a Format B
4 MAC Layer Trailer If the Security Layer packet contains a Format B Connection Layer
5 Packet, the access network shall set this field to ‘11’. Otherwise, the
7 The access network shall construct a Single User Multiplex MAC Layer packet as shown
8 below.
Field Length (bits)
n occurrences following field:
Length 8
MACHeaderDelimiter 0 or 8
n (n ≥ 1) occurrences of the following field:
Security Layer Packet 8 × i, where i is the value of
the corresponding Length
field in the MAC Layer
Header
Pad As needed
MAC Layer Trailer 2
9 Length For 1 ≤ i ≤ n, the access network shall set the ith occurrence of this
10 field to the length, in octets, of the ith Security Layer packet in this
11 MAC Layer packet.
12 MACHeaderDelimiter
13 This field shall not be included if the sum of the lengths of the
14 Security Layer Packets, MAC header, and MAC trailer equals the size
15 of the corresponding MAC Layer packet. This field shall be included if
16 the MAC Layer Packet size exceeds the sum of the length of the
17 Security Layer Packets, MAC header, and MAC trailer by one or more
18 octets. If included this field shall be set to ‘0000000’.
20 Security Layer packet from the Security Protocol containing a Format

21 A Connection Layer packet.
22 PAD The access network shall set the size of this field to the size of the
23 MAC Layer Packet minus the size of MAC Layer Header (m octets),
9-110
1 payload and Trailer (two bits). The access network shall set the value
2 of this field to all ‘0’s. The receiver shall ignore this field.
3 MAC Layer Trailer The access network shall set this field to ‘10’.
4 The MAC Layer Payload consists of n Security Layer packets, where n is an integer greater
5 than or equal to one.
6 The access network shall construct a Multi-User MAC Layer packet as shown below.
7
Field Length (bits)

n occurrences (0 ≤ n ≤ 8) of the following two fields:
PktInfo 8
Length 8
MACHeaderDelimiter 0 or 8
n occurrences (0 ≤ n ≤ 8) of the following field:
Security Layer Packet 8 × i, where i is the
value of the
corresponding Length
field
Pad As needed
MAC trailer 2
8
9 PktInfo For 1 ≤ i ≤ n, the ith occurrence of this field as shown below.

10
Field Length (bits)

Format 1
MACIndex 7
11 Format If the ith Security Layer packet contains a Format B Connection

12 Layer packet, the access network shall set the ith occurrence of this
13 field to ‘1’. Otherwise, the access network shall set the ith occurrence
14 of this field to ‘0’.
15 MACIndex The ith occurrence of this field shall be set to MACIndex of the access
16 terminal to which the ith Security Layer packet is addressed. The
17 access network shall use the MACIndex assigned to the access
18 terminal by the sector transmitting this MAC Layer packet.
9-111
1 Length The ith occurrence of this field shall be set to the length, in octets, of
2 the ith Security Layer packet in this MAC Layer payload.
3 MACHeaderDelimiter
4 This field shall not be included if the sum of the lengths of the
5 Security Layer Packets, MAC header, and MAC trailer equals the size
6 of the corresponding MAC Layer packet. This field shall be included if
7 the MAC Layer Packet size exceeds the sum of the length of the
8 Security Layer Packets, MAC header, and MAC trailer by one or more
9 octets. If included this field shall be set to ‘00000000’.
11 Security Layer packet from the Security Protocol, containing a

12 Format A or Format B Connection Layer packet.
13 Pad The access network shall set the size of this field to the size of the
14 MAC Layer packet minus the size of MAC Layer header (2n octets),
15 MACHeaderDelimiter (if included), payload and trailer (2 bits). The
16 access network shall set the value of this field to all ‘0’s. The receiver
18 MAC trailer Forward Traffic Channel Medium Access Control trailer. The access
20 The MAC Layer payload consists of n Security Layer packets, where n is an integer from
21 zero to eight. The MAC Layer header consists of n PktInfo fields and n Length fields The
22 MACHeaderDelimiter is included if the MAC Layer Packet size exceeds the sum of the
23 length of the Security Layer Packets, MAC header, and MAC trailer by one or more octets. If
24 included this field shall be set to ‘0000000’. The Pad bits are included if the size of the MAC
25 Layer Packet exceeds the sum of the lengths of the Security Layer packets, MAC header,
26 MACHeaderDelimiter (if included), and MAC trailer.
27 10.7.6.1.29.7.6.1.2 Preamble MAC Index

28 The Forward Traffic Channel transmits at most one MAC Layer Packet at any given time.
29 The transmission of a MAC Layer packet on the Forward Traffic Channel is preceded by the
30 transmission of a Preamble MAC Index. The Preamble MAC Index preceding a Single User
31 MAC Layer packet specifies the address of the Single User MAC Layer packet. The
32 Preamble MAC Index preceding a Multi-User MAC Layer packet specifies the MAC Layer
33 Packet Size of the Multi-User MAC Layer packet.
34 When transmitting a Single User MAC Layer packet to an access terminal on the Forward
35 Traffic Channel, the access network shall set the Preamble MAC Index to the MACIndex
36 assigned to the access terminal by the transmitting sector. When transmitting a Multi-User
37 MAC Layer packet on the Forward Traffic Channel, the access network shall set the
38 Preamble MAC Index based on the size of the packet, in accordance with Table 9.7.6.1.2-1.
9-112
1 Table 9.7.6.1.2-1 Preamble MAC Index of Multi-User MAC packets
MAC Layer Preamble MAC Index

Packet Size
(bits)
98, 226, 482, or 994 66

2018 67
3042 68
4066 69
5090 70

3 A Single User Simplex (Simplex or Multiplex) MAC Layer packet is addressed to one access
4 terminal, while different Security Layer packets embedded in a Multi-User MAC Layer
5 packet may be addressed to different access terminals. When transmitting a Single User
6 Simplex (Simplex or Multiplex) packet, the MACIndex of the access terminal is indicated by
7 the Preamble MAC Index. When transmitting a Multi-User packet, the MACIndex of the
8 access terminal is specified in the PktInfo field of the MAC Layer Header, corresponding to
9 the Security Layer packet being addressed to the access terminal.
10 10.7.6.1.49.7.6.1.4 Transmission Format of the Forward Traffic Channel

11 After constructing a MAC Layer packet, the protocol sends the MAC Layer packet along
12 with a preamble MAC Index and a transmission format to the Physical Layer. The Physical
13 Layer protocol encapsulates the MAC Layer packet in a Physical Layer packet and embeds
14 the preamble MAC Index in a packet preamble. The packet preamble and the Physical
15 Layer packet are transmitted on the Forward Traffic Channel in accordance with the
16 transmission format specified by the Enhanced Forward Traffic Channel MAC protocol.
17 The transmission format of the Forward Traffic Channel is represented by an 3-tuple of
18 numbers, whose components are defined as follows:
19 • Physical Layer Packet Size: the total number of bits in the Physical Layer packet, which
20 encapsulates the MAC Layer packet.
21 • Nominal Transmit Duration: the maximum number of slots over which the Physical
22 Layer packet is transmitted on the Forward Link.
23 • Preamble Length: the number of chips of the packet preamble, which precedes the
24 transmission of the Physical Layer packet.
25 The Nominal Data Rate of a transmission format may be computed by dividing the Physical
26 Layer Packet Size by the Nominal Transmit Duration. For example, the transmission format
27 represented by the 3-tuple (512, 4, 256) has a Nominal Data Rate of 76.8 kbps. The actual
28 transmit duration of a packet may be smaller than its Nominal Transmit Duration;
29 consequently, the actual data rate of a packet may be higher than its Nominal Data Rate.
9-113
1 A transmission format is defined to be consistent with a MAC Layer packet if the size of the
2 MAC Layer packet is equal to the Physical Layer Packet Size of the transmission format,
3 less 30 bits (FCS + Tail). Table 9.7.6.1.4-1 provides the set of all transmission formats
4 defined by the Enhanced Forward Traffic Channel MAC protocol, as well as the list of all
5 transmission formats consistent with MAC Layer packets of each size.
7 Packet Size
MAC Layer List of consistent Transmission Formats

Packet Size
(Physical Layer Packet Size (bits), Nominal Transmit Duration (slots),
(bits)
Preamble Length (chips))
98 (128, 16, 1024), (128, 8, 512), (128, 4, 256), (128, 2, 128), (128, 1, 64)
226 (256, 16, 1024), (256, 8, 512), (256, 4, 256), (256, 2, 128), (256, 1, 64)
482 (512, 16, 1024), (512, 8, 512), (512, 4, 256), (512, 2, 128),
(512, 1, 64), (512, 2, 64), (512, 4, 128)
994 (1024, 16, 1024), (1024, 8, 512), (1024, 4, 256), (1024, 2, 128),
(1024, 1, 64), (1024, 2, 64), (1024, 4, 128)
2018 (2048, 4, 128), (2048, 2, 64), (2048, 1, 64)
3042 (3072, 2, 64), (3072, 1, 64)
4066 (4096, 2, 64), (4096, 1, 64)
5090 (5120, 2, 64), (5120, 1, 64)
8 When passing the MAC Layer packet and Transmission Format from the MAC Layer
9 Protocol to the Physical Layer Protocol, the access network shall specify a Transmission
10 Format that is consistent with the MAC Layer packet.
11 10.7.6.1.59.7.6.1.5 Data Rate Control and Data Source Control Channels

12 The access terminal transmits the DRC Channel and the DSC Channel in the Variable Rate
13 State, as well as in the Fixed DRC State.The DRC Channel transmission consists of a DRC
14 cover and a DRC value. The access terminal uses the DRC cover to specify the requested
15 sector for packet transmission. The access terminal uses the DRC value to specify the set
16 of requested transmission formats.
17 The access terminal shall use either the DRC cover index 0 or the 3-bit DRC Cover index
18 associated with a sector in its Active Set. The DRC cover index 0 is called the “null cover”. A
19 DRC cover that corresponds to a sector in Active Set of the access terminal is called a
20 “sector cover”.
21 The DSC Channel transmission is either a null-cover or a cell-cover. The DSC symbol index
22 0 is called the “null cover”. If the DSC is a cell-cover, it specifies the Forward Link Data
23 Source represented by the cell cover. A Forward Link Data Source (or equivalently, a Data
24 Source) of the access terminal is a group of sectors that maintain a common forward link
25 data queue for the access terminal. Sectors in the active set of an access terminal
26 belonging to the same cell constitute a Data Source of the access terminal. The access
9-114
1 terminal is defined to be pointing the DSC at a Forward Link Data Source, if the DSC
2 transmitted by the access terminal is the cell cover associated with that Data Source.
3 The access terminal shall set the DRC value to a 4-bit DRC index, ranging from 0x0 to 0xe.
4 The DRC index 0 is also known as the null-rate DRC. Each DRC index is associated with a
5 Rate Metric, a Span, a list of Single User transmission formats and a list of Multi-User
6 transmission formats, as shown in Table 9.7.6.1-2. Among the Single User transmission
7 formats associated with a DRC index, the transmission format with the largest Physical
8 Layer Packet Size is defined to be the canonical transmission format of the DRC index. In
9 Table 9.7.6.1-2, the canonical transmission format of each DRC index is typed in bold
10 italics. The Rate Metric and Span of a non-zero DRC index are equal to the Nominal Data
11 Rate (in kbps) and Nominal Transmit Duration (in slots) respectively, of the canonical
12 transmission format of the DRC index.
9-115
1 Table 9.7.6.1-2 Rate Metric, Span and Lists of Associated Transmission Formats
DRC Rate Span List of Associated List of Associated

Index Metric (slots) Single User Multi-User Transmission
(kbps) Transmission Formats Formats
0x0 0 16 (128, 16, 1024), (128, 4, 256), (256, 4, 256),

(256, 16, 1024), (512, 4, 256), (1024, 4, 256)
(512, 16, 1024),
(1024, 16, 1024)
0x1 38.4 16 (128, 16, 1024), (128, 4, 256), (256, 4, 256),
(256, 16, 1024), (512, 4, 256), (1024, 4, 256)
(512, 16, 1024),
(1024, 16, 1024)
0x2 76.8 8 (128, 8, 512), (128, 4, 256), (256, 4, 256),
(256, 8, 512), (512, 4, 256), (1024, 4, 256)
(512, 8, 512),
(1024, 8, 512)
0x3 153.6 4 (128, 4, 256), (128, 4, 256), (256, 4, 256),
(256, 4, 256), (512, 4, 256), (1024, 4, 256)
(512, 4, 256),
(1024, 4, 256)
0x4 307.2 2 (128, 2, 128), (128, 4, 256), (256, 4, 256),
(256, 2, 128), (512, 4, 256), (1024, 4, 256)
(512, 2, 128),
(1024, 2, 128)
0x5 307.2 4 (512, 4, 128), (128, 4, 256), (256, 4, 256),
(1024, 4, 128), (512, 4, 256), (1024, 4, 256),
(2048, 4, 128) (2048, 4, 128)
0x6 614.4 1 (128, 1, 64), (128, 4, 256), (256, 4, 256),
(256, 1, 64), (512, 4, 256), (1024, 4, 256)
(512, 1, 64),
(1024, 1, 64)
0x7 614.4 2 (512, 2, 64), (128, 4, 256), (256, 4, 256),
(1024, 2, 64), (512, 4, 256), (1024, 4, 256),
(2048, 2, 64) (2048, 4, 128)
0x8 921.6 2 (1024, 2, 64), (128, 4, 256), (256, 4, 256),
(3072, 2, 64) (512, 4, 256), (1024, 4, 256),
9-116
DRC Rate Span List of Associated List of Associated

Index Metric (slots) Single User Multi-User Transmission
(kbps) Transmission Formats Formats
(2048, 4, 128), (3072, 2, 64)

0x9 1228.8 1 (512, 1, 64), (128, 4, 256), (256, 4, 256),
(1024, 1, 64), (512, 4, 256), (1024, 4, 256),
(2048, 1, 64) (2048, 4, 128)
0xa 1228.8 2 (4096, 2, 64) (128, 4, 256), (256, 4, 256),
(512, 4, 256), (1024, 4, 256),
(2048, 4, 128), (3072, 2, 64),
(4096, 2, 64)
0xb 1843.2 1 (1024, 1, 64), (128, 4, 256), (256, 4, 256),
(3072, 1, 64) (512, 4, 256), (1024, 4, 256),
(2048, 4, 128), (3072, 2, 64)
0xc 2457.6 1 (4096, 1, 64) (128, 4, 256), (256, 4, 256),
(512, 4, 256), (1024, 4, 256),
(2048, 4, 128), (3072, 2, 64),
(4096, 2, 64)
0xd 1536 2 (5120, 2, 64) (128, 4, 256), (256, 4, 256),
(512, 4, 256), (1024, 4, 256),
(2048, 4, 128), (3072, 2, 64),
(4096, 2, 64), (5120, 2, 64)
0xe 3072 1 (5120, 1, 64) (128, 4, 256), (256, 4, 256),
(512, 4, 256), (1024, 4, 256),
(2048, 4, 128), (3072, 2, 64),
(4096, 2, 64), (5120, 2, 64)
1
2 The canonical packet size of a DRC index is defined to be the Physical Layer Packet Size of
3 the canonical transmission format of that DRC index. A Single User Transmission Format
4 associated with a DRC index shown in Table 9.7.6.1-2 is defined to be compatible with the
5 DRC index, if at least one of the following conditions is met:
6 • The given transmission format coincides with the canonical transmission format of the
7 DRC index, or
8 • The canonical packet size of the DRC index is strictly less than the value of the
9 ShortPacketsEnabledThresh attribute.
10 A Multi-User transmission format associated with a DRC index is defined to be compatible
11 with the DRC index, if the value of the MultiUserPacketsEnabled attribute is 0x01
9-117
1 The access terminal shall obey the following rules when transmitting the DRC Channel:
2 • Access terminal shall use DRCLength slots to send a single DRC. The DRC (value and
3 cover) is defined to take effect at the slot boundary following the end of its transmission,
4 and stay in effect for DRCLength slots.
5 • If the DRC cover changes in slot T the access terminal shall set DRCChannelGain equal
6 to DRCChannelGainBase + DRCChannelGainBoost from slot T through slot (T +
7 DRCBoostLength – 1). Otherwise, the access terminal shall set the DRCChannelGain
8 equal to DRCChannelGainBase.
9 • The DRC (value and cover) shall not change in slots other than T such that:
16 The access terminal shall obey the following rules when transmitting the DSC Channel:
17 • Access terminal shall use DSCLength slots to send a single DSC. The DSC is defined to
18 take effect one slot after the end of its transmission and to stay in effect for DSCLength
19 slots.
20 • The DSC shall not change in slots other that T such that:
21 [T + 1 + 15 × FrameOffset] mod DSCLength = 0,
22 where T is the CDMA System Time in slots113.
23 • If the DSC changes in slot T the access terminal shall set DSCChannelGain equal to
24 DSCChannelGainBase + DSCChannelGainBoost from slot T through slot (T +
25 DSCBoostLength – 1). Otherwise, the access terminal shall set the DSCChannelGain
26 equal to DSCChannelGainBase.
27 • If the access terminal receives a DRCLock bit that is set to ‘0’ from a cell associated
28 with a sector in its active set and the access terminal is pointing its DRC to a sector
29 associated with that cell, then the access terminal should not point the DSC to the
30 Data Source associated with that sector.
31 When transmitting the DRC Channel, the access terminal shall set the DRC cover
32 according to the following rules:
113 Note that [T + 1 + 15 × FrameOffset] = (T + 1 – FrameOffset) + (16 × FrameOffset), where the first
term on the right hand side ensures that DSC symbol boundaries coincide with DRC symbol
boundaries, and the second term enables frame offset staggering of DSC symbol boundaries over the
maximum allowed value of DSC length (i.e., 256 slots).
9-118
1 • If the access terminal’s current DRC cover is a sector cover, then the access terminal’s
2 next DRC cover shall not be a different sector cover. It may only be the same sector
3 cover or a null cover.
4 • If the DRC cover is a sector cover and the Data Source indicated by the DSC is included
5 in the terminals active set and the DRCLock bit associated with that Data Source is set
6 to ‘1’, then the sector indicated by the DRC cover shall belong to the Data Source
7 indicated by the DSC that is in effect during the next DRCLength slots following
8 transmission of the DRC.
9 • If the access terminal’s most recent sector cover belongs to sector A, then the access
10 terminal shall not use a sector cover corresponding to any other sector B, until the
11 access terminal has determined that packets that may be transmitted to the access
12 terminal from sector B will not overlap in time with packets transmitted from sector A.
13 A DRC transmitted by the access terminal is defined to be sustainable with respect to a
14 sector S in the active set of the access terminal, if one of the following conditions is met:
15 • The DRC value is zero, or
16 • The access terminal is capable of receiving any MAC layer packet from sector S,
17 provided the transmission format of the packet is compatible with the DRC value, and
18 the packet transmission begins when the DRC is in effect.
19 When transmitting the DRC Channel, the access terminal shall set the DRC value
21 • If the access terminal sets the DRC cover to a sector cover, it shall set the DRC value as
22 follows:
23 − The access terminal shall set the Tentative DRC value to a DRC index with the
24 maximum Rate Metric, such that the DRC is sustainable with respect to the
25 sector denoted by the DRC cover.
26 − The access terminal shall set the Transmitted DRC value to the Tentative DRC
27 value minus DRCOffsetN, where N is the one-digit hexadecimal value of the
28 DRC index, and DRCOffsetN is the corresponding parameter of the
29 DRCTranslationOffset attribute.
30 • If the access terminal sets the DRC cover to the null cover, it shall set the DRC value as
31 follows:
34 best sector in its active set.
35 − The access terminal shall set the Transmitted DRC value to the Tentative DRC
36 value minus DRCOffsetN, where N is the one-digit hexadecimal value of the
37 DRC index, and DRCOffsetN is the corresponding parameter of the
38 DRCTranslationOffset attribute.
39 The access terminal and the access network shall set the DRCOffsetN parameters of the
40 DRCTranslationOffset attribute such that both of the following conditions are satisfied:
9-119
1 • Rate Metric of the DRC index corresponding to the Transmitted DRC value shall be less
2 than or equal to that of the DRC index corresponding to the Tentative DRC value, and
3 • Span of the DRC index corresponding to the Transmitted DRC value shall be greater
4 than or equal to that of the DRC index corresponding to the Tentative DRC value.
5 An access terminal is defined to be a potential target of a Single User MAC Layer packet if
6 the packet is addressed to the access terminal, and is received using a transmission
7 format, transmitting sector, and the start time that could be used to receive a Single-User
8 packet to the access terminal. An access terminal is defined to be a potential target of a
9 Multi-User MAC Layer packet if the packet is received using a transmission format,
10 transmitting sector, and the start time that could be used to receive a Multi-User packet.
11 A slot t is defined to be a continuation of an earlier slot s, if the following conditions are
12 met:
13 • The access terminal is a potential target of a packet for which the reception began in
14 slot s.
15 • The slot t is in the same forward link interlace as the slot s; i.e., (t – s) mod 4 = 0.
16 • s < t < s + 4 × min(N1, N2, MinimumContinuationSpan), where N1 denotes the
17 Nominal Transmit Duration of the packet whose reception began in slot s and N2
18 denotes the Span of the DRC index corresponding to the DRC value that is in effect
19 during slot s (according to Table 9.7.6.1-2).
20 • Prior to slot t, the access network has not received a positive acknowledgment for the
21 packet for which the reception began in slot s.
22 If the access terminal is a potential target of a packet transmitted by a sector starting in
23 slot s, the access network shall not transmit a new packet from the same Forward Link
24 Data Source to the access terminal in any slot t that is a continuation of slot s.
26 10.7.6.1.6.19.7.6.1.6.1 Activate
30 10.7.6.1.6.29.7.6.1.6.2 Deactivate
31 If the protocol receives a Deactivate command in the Variable Rate State or the Fixed DRC
32 State,
34 transmitting the DRC and DSC Channels, and shall transition to the Inactive State.
36 access terminal, should cease receiving the DRC and DSC channels from this access
37 terminal, and should transition to the Inactive State.
9-120
2 10.7.6.1.79.7.6.1.7 Inactive State


6 In the Variable Rate State, the access network transmits the Forward Traffic Channel using
7 a sector and transmission format determined by the DRC Channel and the DSC Channel
8 transmitted by the access terminal.
11 10.7.6.1.8.19.7.6.1.8.1 Packet Transmission and DRC Requirements

13 The access terminal shall transmit a cell cover on the DSC Channel. The access terminal
14 shall set the cell cover to the value indicated by one of the DSC fields received in the last
16 The access terminal may inhibit transmission of data from the access network by setting
17 the DRC cover to the null cover.
18 In the Variable Rate State, a slot t is defined to be open at the access terminal, if slot t is
19 not the continuation of any previous slot, and the DRC in effect during slot t contains a
20 sector cover. The sector denoted by the sector cover is defined to be the serving sector of
21 the access terminal at slot t. In any open slot T, the access terminal shall attempt to receive
22 a MAC Layer packet from the serving sector, whose transmission begins in slot T and
23 whose packet type and transmission format are compatible with the DRC value in effect at
24 slot T.

28 • If the access network transmits a packet to the access terminal starting in slot T, it
29 shall do so from the sector associated with the DRC cover in effect at slot T.
30 • If the access network transmits a MAC Layer packet to the access terminal starting in
31 slot T, it shall use a packet type and transmission format compatible with the DRC
32 value in effect at slot T.
9-121

2 The access terminal may initiate procedures for transitioning to the Fixed DRC State at any
4 Fixed DRC State:
5 • The access terminal shall start covering the DRC with the null cover
6 • The access terminal shall set the DSC to the null cover .
7 • The access terminal shall wait until it has determined that it will not be served by
8 any sector and then, the access terminal shall send the FixedModeEnable message
9 specifying:
10 − A sector in the active set.
11 − A data rate.
12 − An “end time” for the operation in the Fixed DRC State.
13 The access terminal shall transition to the Fixed DRC State after sending a
14 FixedModeEnable message. The access network shall transition to the Fixed DRC State
15 after receiving of a FixedModeEnable message.
16 10.7.6.1.99.7.6.1.9 Fixed DRC State

21 • The <DRCCover, TCAMessageSequence> pair of fields included in the message shall
22 be set to the value of the <DRCCover, TCAMessageSequence> specified in the last
24 • The DRCValue field included in the message shall be set to the value of the
25 DRCValue specified in the last FixedModeEnable message sent, and
26 • The EndTime field included in the message shall not specify a time earlier than the
27 time specified by the EndTime included in the last FixedModeEnable message sent.
29 the Fixed DRC State.
31 from the sector specified in the last FixedModeEnable message at the rate compatible with
32 the DRCValue specified in that message, it should send at least one FixedModeXoff
33 message to the access network114. The access network should not start transmission of
114 Note that sending an FixedModeXoff message does not cause a transition out of the Fixed DRC
9-122
1 any new Forward Traffic Channel MAC Layer packets to the access terminal after reception
2 of a FixedModeXoff message until the access network transitions to the Variable Rate State.
3 10.7.6.1.9.19.7.6.1.9.1 Packet Transmission Requirements

5 The access terminal shall transmit the null cover on the DSC Channel.
6 In the Fixed DRC state, a slot t is said to be open if it is not the continuation of any
7 previous slot. The sector denoted by the DRCCover field of the most recent
8 FixedModeEnable message is defined to be the serving sector of the access terminal.
9 In any open slot T, the access terminal shall attempt to receive a MAC Layer packet from
10 the serving sector, whose transmission begins in slot T and whose packet type and
11 transmission format are compatible with the DRC index specified by the DRCValue field of
12 the most recent FixedModeEnable message.

17 shall do so from the sector denoted by the DRCCover field in the most recent
18 FixedModeEnable message from the access terminal.
19 • If the access network transmits a Single User Simplex (Simplex or Multiplex) packet
20 to the access terminal starting in slot T, it shall use a packet type and transmission
21 format that are compatible with the DRC index specified by the DRCValue field of
22 the most recent FixedModeEnable message from the access terminal.
23 10.7.6.1.9.29.7.6.1.9.2 Transitions from the Fixed DRC State

26 • If the current CDMA System Time is greater than or equal to the time specified by
27 the EndTime field in the last FixedModeEnable message sent.
28 • If the sector specified in the last sent FixedModeEnable message is no longer a
29 member of the access terminal’s Active Set.
33 the EndTime field in the last FixedModeEnable message received.
34 • If the access network determines that sector specified in the last received
35 FixedModeEnable message is no longer a member of the access terminal’s Active
36 Set.
9-123

2 where, SystemTime is the current CDMA System Time in units of slots.
4 10.7.6.1.10.19.7.6.1.10.1 DRC Supervision

5 The access terminal shall perform supervision on the DRC as follows:
6 • The access terminal shall set the DRC supervision timer for(DRCSupervisionTimer ×
7 10) + 240 ms when its Tentative DRC is a null rate DRC.
8 • The access terminal shall disable the timer if the DRC supervision timer is active
9 and any of the following conditions is true:
10 − the access terminal’s Tentative DRC indicates a non-null rate
11 − the access terminal successfully receives a Forward Traffic Channel packet or a

12 Control Channel packet
13 • If the DRC supervision timer expires, the access terminal shall disable the Reverse
14 Traffic Channel transmitter and set the Reverse Traffic Channel Restart timer for
15 time TFTCMPRestartTx.
16 • If the access terminal generates consecutive Tentative DRC values that correspond to
17 non-null rates for more than NFTCMPRestartTx slots or the access terminal successfully
18 receives a Forward Traffic Channel packet or a Control Channel packet, the access
19 terminal shall disable the Reverse Traffic Channel Restart timer and shall enable
20 the Reverse Traffic Channel transmitter.
21 • If the Reverse Traffic Channel Restart timer expires, the access terminal shall return
22 a SupervisionFailed indication and transition to the Inactive State.

24 The access terminal shall monitor the bit associated with its MACIndex in the
25 ForwardTrafficValid63To0 or ForwardTrafficValid127To64 field made available by the
26 Overhead Messages protocol. If the Overhead Messages Protocol does not provide a
27 ForwardTrafficValid63To0 or ForwardTrafficValid127To64 field associated with the access
28 terminal, then the access terminal shall behave as if the field were set to ‘0’. If this bit is
29 set to 0, the access terminal shall return a SupervisionFailed indication and transition to
30 the Inactive State.
34 Fixed DRC State.
35
9-124
Field Length (bits)

MessageID 8
DRCCover 3
DRCValue 4
EndTime 16
Reserved 1
7 DRCCover The access terminal shall set this field to the DRC cover associated
8 with the sector in its Active Set from which it wants to receive
9 packets on the Forward Traffic Channel.
10 DRCValue The access terminal shall set this field to one of the valid DRC values
11 (or DRC indices) in Table 9.7.6.1-2.
12 EndTime The access terminal shall set this field to the least significant 16 bits
13 of the CDMA System Time in units of slots until which (inclusive) it
14 requests to remain in the Fixed DRC State.
17
18 10.7.6.2.29.7.6.2.2 FixedModeXoff
21 message.
22
Field Length (bits)

MessageID 8

24
9-125
3 given attribute.
4
Field Length (bits)
MessageID 8
TransactionID 8

9
13
Field Length (bits)
MessageID 8
TransactionID 8
17
9-126
4
Field Length (bits)
MessageID 8
TransactionID 8
8
10 10.7.6.3.19.7.6.3.1 Commands Sent

12 10.7.6.3.29.7.6.3.2 Indications

17 Enhanced Forward Traffic Channel MAC Protocol. The access terminal and the access
18 network shall support the use of the Generic Attribute Update Protocol to update values of
19 the following attributes belonging to the Enhanced Forward Traffic Channel MAC Protocol:
20 • MultiUserPacketsEnabled
21 • ShortPacketsEnabledThresh
22 • DRCSupervisionTimer
23 • DRCTranslationOffset
24 • DRCChannelGainBoost
25 • DRCBoostLength
9-127
1 • DSCChannelGainBoost
2 • DSCBoostLength

4 The negotiable simple attributes for this protocol are listed in Table 9.7.7.1-1. The access


0xff DRCGating
All other Reserved
values
0x00 DRCLock bit is repeated 8
times.
times.
0xfe DRCLockLength
times.
times.
All other Reserved
values
0x00 Use of Multi-User MAC packets
is disabled
0x01 Use of Multi-User MAC packets
0xfd MultiUserPacketsEnabled
is enabled
All other Reserved
values
0x08 Length of a single DSC
transmission is 64 slots.
0x01 to Length of a single DSC
0xfc DSCLength 0x20 transmission in units of 8
slots.
All other Reserved
values
0x0c DeltaACKChannelGainMUP is
6 dB.
0x00 to DeltaACKChannelGainMUP in
0xfb DeltaACKChannelGainMUP
0x12 units of 0.5 dB.
All other Reserved
values
9-128

0x01 ShortPacketsEnabledThresh is
2048 bits.
1024 bits.
0xfa ShortPacketsEnabledThresh 0x02 ShortPacketsEnabledThresh is
3072 bits.
4096 bits.
All other Reserved
values
0x00 Use of Single User Multiplex
Packets is disabled
SingleUserMultiplexPackets 0x01 Use of Single User Multiplex
0xf9
Enabled Packets is enabled
All other Reserved
values
0x00 DRC Supervision Timer is 0
0xf8 DRCSupervisionTimer
0x01-0xff Value of DRC Supervision
Timer
0x04 Minimum continuation span is
4 sub-packets
0x01- Value of Minimum
0x03 and continuation span in sub-
0xf7 MinimumContinuationSpan
0x05- packets
0x10
All other Reserved
values
0x00 Increase in DSCChannelGain is
0dB relative to
DSCChannelGainBase starting
in slot where DSC is changed
0x01- Increase in DSCChannelGain
0xf6 DSCChannelGainBoost
0x06 in dB relative to
All other Reserved
values
0x10 Number of slots starting with
the slot in which the DSC is
0xf5 DSCBoostLength changed for which the DSC
Channel Gain is boosted is 128
slots
9-129

0x00- Number of slots in units of 8
0x0F and slots starting with the slot in
0x11- which the DSC is changed for
0x40 which the DSC Channel Gain
is boosted
All other Reserved
values
0x00 Increase in DRCChannelGain
is 0dB relative to
DRCChannelGainBase starting
in slot where DRC cover is
changed
0x01- Increase in DRCChannelGain
0xf4 DRCChannelGainBoost
in slot where DSC cover is
changed
All other Reserved
values
the slot in which the DRC cover
is changed for which the
DRCChannelGain is boosted is
8 slots
0xf3 DRCBoostLength
0x03 and slots starting with the slot in
0x05- which the DRC cover is
0x20 changed for which the
DRCChannelGain is boosted
All other Reserved
values
1
2 The access terminal shall support the default value of the DRCGating attribute.

5
9-130

Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
5 complex value.
6 SofterHandoffDelay The sender shall set this field to the minimum interruption that the
7 access terminal should expect when the access terminal switches the
8 DRC from one sector to another sector in the same Forward Link
9 Data Source. The sender shall specify this field in units of 8 slots.
10 The access terminal may use this number to adjust its algorithm
11 controlling DRC switching. The access terminal shall support all the
12 values of this field.
13 SoftHandoffDelay The sender shall set this field to the minimum interruption that the
14 access terminal should expect when the access terminal changes the
15 DSC from one Forward Link Data Source to another. The sender
16 shall specify this field in units of 8 slots. The access terminal may
17 use this number to adjust its algorithm controlling DSC switching.
18 The access terminal shall support all the values of this field.
19 10.7.7.2.29.7.7.2.2 DRCTranslationOffset Attribute

20
9-131

Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
DRCOffset1 1 0
DRCOffset2 2 0
DRCOffset3 2 0
DRCOffset4 3 0
DRCOffset5 3 0
DRCOffset6 3 0
DRCOffset7 3 0
DRCOffset8 4 0
DRCOffset9 4 0
DRCOffsetA 4 0
DRCOffsetB 4 0
DRCOffsetC 4 0
DRCOffsetD 4 0
DRCOffsetE 4 0
}
5 complex value.
6 DRCOffset1 The sender shall set this field to the offset to be used for computing
7 Transmitted DRC value when the Tentative DRC value is 0x1.
9-132
15 DRCOffsetA The sender shall set this field to the offset to be used for computing
16 Transmitted DRC value when the Tentative DRC value is 0xa.
17 DRCOffsetB The sender shall set this field to the offset to be used for computing
18 Transmitted DRC value when the Tentative DRC value is 0xb.
19 DRCOffsetC The sender shall set this field to the offset to be used for computing
20 Transmitted DRC value when the Tentative DRC value is 0xc.
21 DRCOffsetD The sender shall set this field to the offset to be used for computing
22 Transmitted DRC value when the Tentative DRC value is 0xd.
23 DRCOffsetE The sender shall set this field to the offset to be used for computing
24 Transmitted DRC value when the Tentative DRC value is 0xe.
27 set these bits to zeros. The receiver shall ignore this field.
9-133

2

NS1FTCMPEnhanced Subtype field for this protocol 0x0001
Number of consecutive slots of non-null
rate DRCs to re-enable the Reverse Traffic
NFTCMPRestartTx 16
12 Control
cycles

6 protocol.
9-134
1 10.89.8 Multicarrier Forward Traffic Channel MAC Protocol
2 10.8.19.8.1 Overview
3 The Multicarrier Forward Traffic Channel MAC Protocol provides the procedures and
4 messages required for an access network to transmit and an access terminal to receive the
5 Forward Traffic Channel. Specifically, this protocol addresses Forward Traffic Channel
6 addressing and Forward Traffic Channel rate control on each Forward CDMA Channel
7 assigned to the access terminal. This protocol operates with the Subtype 3 Physical Layer
8 Protocol.
14 Channel to the access terminal on one or more CDMA Channels, in accordance with the
15 DRC Channel received from the access terminal.
16 • Fixed DRC State: In this state, the access network transmits the Forward Traffic
17 Channel to the access terminal on one or more CDMA Channels, in accordance with the
18 FixedModeEnable message received from the access terminal.
21 9.8.6.1.9.2 for transitions out of the Inactive State, Variable Rate State, and Fixed DRC
22 State.
Initial State
Deactivate
Inactive Variable
State Rate State
Activate
AT Dependent
Deactivate
AT Dependent
Fixed DRC
State
23
24 Figure 9.8.1-1. Multicarrier Forward Traffic Channel MAC Protocol State Diagram
9-135
2 10.8.2.19.8.2.1 Commands
4 • Activate
5 • Deactivate

9 • ReverseTrafficChannelRestartTimerExpired along with arguments indicating the reverse
10 CDMA Channel associated with the expired Restart timer
11 10.8.2.39.8.2.3 Public Data

14 • DRCGating
16 • DSCLength
18 • DRCChannelGainBase
19 • DSCChannelGain
20 • DSCChannelGainBase
22 • DRCCover for every sub-Active set in the Active Set
23 • DSC for every sub-Active set in the Active Set
24 • State of the Multicarrier Forward Traffic Channel MAC Protocol (Inactive State, Variable
25 Rate State, or Fixed DRC State)
26 • The DRC value and DRC cover specified by the latest FixedModeEnable message, if in
27 Fixed DRC State
28 • AuxDRCCover for every pilot in the Active Set to which a DRCCover is assigned
29 • ExtendedSpansEnabled
30 • MUPPreambleBase
9-136

3 Each Forward Traffic Channel MAC Layer packet consists of zero or more Security Layer
4 packets.

18 10.8.5.19.8.5.1 Procedures
21 The access network shall not send a ConfigurationRequest message containing the
22 ATSupportedPacketFormats attribute.

31 − DRCGating
33 − DSCLength
34 − DeltaACKChannelGainMUP
9-137
2 then
20
Field Length (bits)
MessageID 8
TransactionID 8

25
9-138
Field Length (bits)
MessageID 8
TransactionID 8

10
12 10.8.6.19.8.6.1 Procedures
13 At the access network, the Multicarrier Forward Traffic Channel MAC Protocol
14 encapsulates zero or more Security Layer packets into a MAC Layer packet and passes the
15 MAC Layer packet for transmission to the Physical Layer Protocol, along with the Preamble
16 MAC Index, Transmission Format, and the forward CDMA channel assigned to the access
17 terminal (as indicated by public data of the Route Update Protocol) on which the packet is
18 to be transmitted. The choice of Transmission Format is governed by the DRC value and
19 DRC cover information corresponding to the CDMA channel on which the packet is to be
20 transmitted as received from the access terminal.
21 10.8.6.1.19.8.6.1.1 MAC Layer Packet

22 The MAC Layer packet is the basic unit of data provided by the Multicarrier Forward Traffic
23 Channel MAC protocol to the Physical Layer Protocol. The MAC Layer packets shall be of
24 one of the following two types:
25 • Single User
26 • Multi-User
27 The structure of a MAC Layer packet is shown in Figure 9.8.6.1.1-1.
28 The MAC Layer packet consists of the following (in order):
9-139
1 • MAC Layer Header (which may be empty)

3 • MAC Layer Payload
5 • MACTrailerDelimiter (if required)
7 The size of a MAC Layer packet takes on a discrete set of values, as shown in Figure
8 9.8.6.1.1-1.
10 Figure 9.8.6.1.1-1. Multicarrier Forward Traffic Channel MAC Layer Packet Structure
11 The MAC Layer payload consists of zero or more Security Layer packets addressed to zero
12 or more access terminals. The MAC Layer Header (if included), MACHeaderDelimiter (if
13 included), MACTrailerDelimiter (if included), and MAC Layer Trailer are used to provide
14 information needed to parse the contents of the MAC Layer Payload and to specify the type
15 of the MAC Layer packet (Single User or Multi-User).
16 The MAC Layer payload may be followed by padding, which consists of a sequence of all
17 ‘0’s. The size of the padding sequence is chosen such that the overall size of the MAC Layer
18 packet is one of 98, 226, 482, 994, 2018, 3042, 4066, 5090, 6114, 7138, or 8162 bits.
19 10.8.6.1.1.19.8.6.1.1.1 Description of MAC Layer packet types

20 A Single User MAC Layer packet is used to carry one Security Layer packet in its payload
21 and is addressed to one access terminal. The MAC Layer Payload size equals the size of the
22 MAC Layer Packet minus the size of the MAC Layer Trailer. A Single User packet consists of
23 the following (in order):
24 • An empty MAC Layer Header
25 • A MAC Layer Payload consisting of one Security Layer packet
26 • No PAD
27 The Security Layer packet in a Single User packet contains a Format A or Format B
29 A Multi-User MAC Layer Packet is used to carry in its payload, zero or more Security Layer
30 packets addressed to zero or more access terminals. A Multi-User packet consists of the
31 following (in order):
32 • MAC Layer Header (if required)
33 • DelimiterH (if required)
9-140
1 • MAC Layer Payload consisting of zero or more (max of sixteen) Security Layer packets
3 • DelimiterT (if required)
5 Each Security Layer packet addressed to an access terminal with ForwardTrafficMACIndex
6 ≤127 in a Multi-User packet contains a Format A or Format B Connection Layer packet.
7 Each Security Layer packet addressed to an access terminal with ForwardTrafficMACIndex
8 > 127 in a Multi-User packet contains a Format A Connection Layer packet.
9 10.8.6.1.1.29.8.6.1.1.2 Construction of MAC Layer packets

10 The structure of Single User MAC packets and Multi-User MAC packets are shown in
11 Figure 9.8.6.1.1.2-2 and Figure 9.8.6.1.1.2-2 respectively. The type of MAC Layer packet
12 may be inferred from the Preamble MAC Index and the MACPacketType field of the MAC
13 Layer Trailer. When the Preamble MAC Index is set to the ForwardTrafficMACIndex
14 assigned to the access terminal, the MACPacketType field indicates a Single User packet if
15 equal to ‘01’ or ‘11’,. For Single-User MAC packets, the values ‘10’ and ‘00’ for the
16 MACPacketType are reserved. The access terminal shall not pass the payload of the Single-
17 User MAC packet to the higher layer if the MACPacketType is set to ‘10’ or ‘00’. The access
18 terminal shall not ACK a Single User MAC packet if the MACPacketType is set to ‘10’ or
19 ‘00’. The access terminal shall not pass the payload of a Multi-User MAC packet to the
20 higher layer if the MACPacketType is set to a value other than ‘00’. The access terminal
21 shall not ACK a Multi-User MAC packet if the MACPacketType is set to a value other than
22 ‘00’.
23 When the Preamble MAC Index is set to a Multi-User Preamble MAC Index as specified in
24 9.8.6.1.2, the access network shall set the MACPacketType to ‘00’. For Multi-User MAC
25 packets, the values for the MACPacketType other than ‘00’ are reserved.
96, 224, 480, 992, 2016, 3040, 4064, 5088, 6112, 7136, or 8160 bits 2 bits
( 12, 28, 60, 124, 252, 380, 508, 636, 764, 892, or 1020 octets ) MAC Trailer
MAC Layer Payload MAC

PacketType
( Security Layer Packet ) ‘01’ or ‘11’
26
27 Figure 9.8.6.1.1.2-1 Format of Forward Traffic Channel Single User MAC Layer Packet
9-141
0≤n≤8
0≤n≤8
2 Figure 9.8.6.1.1.2-2 Format of Forward Traffic Channel Multi-User MAC Layer Packet
9-142
1 The access network shall construct a Single User MAC Layer packet as shown below:
2
Field Length (bits)
Security Layer Packet 96, 224, 480, 992, 2016,

3040, 4064, 5088, 6112,
7136, or 8160
MACPacketType 2

4 The access network shall set this field to a Security Layer packet
5 from the Security Protocol, containing a Format A or a Format B
7 MACPacketType If the Security Layer packet contains a Format B Connection Layer

8 Packet, then the access network shall set this field to ‘11’. Otherwise,
10 The access network shall construct a Multi-User MAC Layer packet as shown below. A
11 Multi-User packet carries 0 to 16 Security Layer packets. A Multi-User packet carries up to
12 8 Security Layer packets for access terminals with ForwardTrafficMACIndex ≤ 127, and up
13 to 8 Security Layer packets for access terminals with ForwardTrafficMACIndex > 127. The
14 first n (0 ≤ n ≤ 8) Security Layer packets are addressed to access terminals with
15 ForwardTrafficMACIndex ≤127. The last r (0 ≤ r ≤ 8) Security Layer packets are addressed
16 to access terminals with ForwardTrafficMACIndex >127.
17
9-143
Field Length (bits)

n occurrences (0 ≤ n ≤ 8) of the following two fields:
PacketInfoH 8
LengthH 8
DelimiterH 0 or 8
n occurrences (0 ≤ n ≤ 8) of the following field:
Security Layer Packet 8 × i, where i is the
value of the
corresponding LengthH
field
r occurrences (0 ≤ r ≤ 8) of the following field:
Security Layer Packet 8 × j, where j is the
value of the
corresponding LengthT
field
Pad As needed
DelimiterT 0 or 8
r occurrences (0 ≤ r ≤ 8) of the following two fields:
PacketInfoT 8
LengthT 8
MACPacketType 2
1
2 PacketInfoH For 0 ≤ i ≤ n, the ith occurrence of this field as shown below.

3
Field Length (bits)

Format 1
ForwardTra
fficMACInd 7
ex
4 Format If the ith Security Layer packet contains a Format B Connection

5 Layer packet, the access network shall set the ith occurrence of this
6 field to ‘1’. Otherwise, the access network shall set the ith occurrence
7 of this field to ‘0’.
9-144
1 The ith occurrence of this field shall be set to

2 ForwardTrafficMACIndex of the access terminal to which the ith
3 Security Layer packet is addressed. The access network shall use the
4 ForwardTrafficMACIndex assigned to the access terminal by the
5 sector transmitting this MAC Layer packet for the CDMA Channel
6 and interlace on which the MAC Layer packet is to be transmitted.
7 LengthH The ith occurrence of this field shall be set to the length, in octets, of
8 the ith Security Layer packet in this MAC Layer payload.
9 DelimiterH
10 This field shall not be included if the sum of the lengths of the first n
11 Security Layer Packets, PacketInfoH fields, LenghtH fields, and the
12 MACPacketType field equals the size of the corresponding MAC Layer
13 packet. Otherwise, this field shall be included and shall be set to
14 0x00.

16 The first n occurrences of this field shall contain a Security Layer
17 packet for access terminal with ForwardTrafficMACIndex ≤ 127 from
18 the Security Protocol, containing a Format A or Format B Connection
19 Layer packet. The next r occurrences of this field shall contain a
20 Security Layer packet for access terminal with
21 ForwardTrafficMACIndex > 127 from the Security Protocol,
22 containing a Format A Connection Layer packet.
23 Pad The access network shall set the length of this field to the size of the
24 MAC Layer packet minus the sum of the lengths of the rest of the
25 fields included in the MAC Layer packet. The access network shall
26 set the value of this field to all ‘0’s. The receiver shall ignore this field.
27 DelimiterT This field shall not be included if the sum of the lengths of the first
28 (n+r) Security Layer Packets, n PacketInfoH fields, n LengthH fields, r
29 PacketInfoT fields, r LengthT fields, and MACPacketType field equals
30 the length of the MAC Layer packet. Otherwise, this field shall be
31 included and shall be set to 0x00.
32 PacketInfoT For 0 ≤ j ≤ r, the jth occurrence of this field as shown below.

33
Field Length (bits)

ForwardTrafficMACIndex 8
35 The jth occurrence of this field shall be set to 128 less than the
36 ForwardTrafficMACIndex of the access terminal to which the (n+j)th
9-145
1 Security Layer packet is addressed. The access network shall use the
2 ForwardTrafficMACIndex assigned to the access terminal by the
3 sector transmitting this MAC Layer packet for the CDMA Channel
4 and interlace on which the MAC Layer packet is to be transmitted.
5 LengthT The jth occurrence of this field shall be set to the length, in octets, of
6 the (n+j)th Security Layer packet in this MAC Layer packet.
7 MACPacketType The access network shall set this field to ‘00’.
8 10.8.6.1.29.8.6.1.2 Preamble MAC Index

9 The Forward Traffic Channel transmits at most one MAC Layer Packet at any given time on
10 a given CDMA Channel. The transmission of a MAC Layer packet on the Forward Traffic
11 Channel is preceded by the transmission of a Preamble MAC Index. The Preamble MAC
12 Index preceding a Single User MAC Layer packet specifies the address of the Single User
13 MAC Layer packet. The Preamble MAC Index preceding a Multi-User MAC Layer packet
14 specifies the MAC Layer Packet Size of the Multi-User MAC Layer packet.
15 When transmitting a Single User MAC Layer packet to an access terminal on the Forward
16 Traffic Channel, the access network shall set the Preamble MAC Index to the
17 ForwardTrafficMACIndex assigned to the access terminal by the transmitting sector for the
18 CDMA Channel and the interlace on which the packet is to be transmitted. When
19 transmitting a Multi-User MAC Layer packet on the Forward Traffic Channel, the access
20 network shall set the Preamble MAC Index based on the size of the packet, in accordance
21 with Table 9.8.6.1.2-1.
22 Table 9.8.6.1.2-1 Preamble MAC Index of Multi-User MAC packets
MAC Layer Preamble MAC Index

Packet Size
(bits)
98, 226, 482, or 994 MUPPreambleBase

2018 MUPPreambleBase + 1

24 A Single User MAC Layer packet is addressed to one access terminal, while different
25 Security Layer packets embedded in a Multi-User MAC Layer packet may be addressed to
26 different access terminals. When transmitting a Single User packet, the
27 ForwardTrafficMACIndex of the access terminal is indicated by the Preamble MAC Index.
28 When transmitting a Multi-User packet, the ForwardTrafficMACIndex of the access
29 terminal is specified in the PacketInfoH or PacketInfoT field of the MAC Layer Header or
9-146
1 MAC Layer Trailer respectively, corresponding to the Security Layer packet being addressed
2 to the access terminal.
3 10.8.6.1.49.8.6.1.4 Transmission Format of the Forward Traffic Channel

4 After constructing a MAC Layer packet, the protocol sends the MAC Layer packet along
5 with a preamble MAC Index, transmission format and CDMA Channel to the Physical
6 Layer. The Physical Layer protocol encapsulates the MAC Layer packet in a Physical Layer
7 packet and embeds the preamble MAC Index in a packet preamble. The packet preamble
8 and the Physical Layer packet are transmitted on the Forward Traffic Channel in
9 accordance with the transmission format specified by the Multicarrier Forward Traffic
11 The transmission format of the Forward Traffic Channel is represented by an 3-tuple of
12 numbers Physical Layer Packet Size, Termination Target, and PreambleLength, and are
13 defined as follows:
14 • Physical Layer Packet Size: the total number of bits in the Physical Layer packet, which
15 encapsulates the MAC Layer packet.
16 • Termination Target: the nominal number of slots over which the Physical Layer packet
17 is transmitted on the Forward Link.
18 • Maximum Span: the maximum number of slots over which the Physical Layer packet is
19 transmitted on the Forward Link.
20 • Preamble Length: the number of chips of the packet preamble.
21 The Nominal Data Rate of a transmission format may be computed by dividing the Physical
22 Layer Packet Size by the Termination Target. For example, the transmission format
23 represented by the 3-tuple (512, 4, 256) has a Nominal Data Rate of 76.8 kbps. The actual
24 transmit duration of a packet may be smaller than its Termination Target; consequently,
25 the actual data rate of a packet may be higher than its Nominal Data Rate.
26 A transmission format is defined to be consistent with a MAC Layer packet if the size of the
27 MAC Layer packet is equal to the Physical Layer Packet Size of the transmission format,
28 less 30 bits (FCS + Tail). Table 9.8.6.1.4-1 provides the set of all transmission formats
29 defined by the Multicarrier Forward Traffic Channel MAC protocol, as well as the list of all
30 transmission formats consistent with MAC Layer packets of each size.
9-147
2 Packet Size
MAC Layer List of consistent Transmission Formats

Packet Size
(Physical Layer Packet Size (bits), Termination Target (slots), Preamble
(bits)
Length (chips))
98 (128, 16, 1024), (128, 8, 512), (128, 4, 256), (128, 2, 128), (128, 1, 64)
226 (256, 16, 1024), (256, 8, 512), (256, 4, 256), (256, 2, 128), (256, 1, 64)
482 (512, 16, 1024), (512, 8, 512), (512, 4, 256), (512, 2, 128),
(512, 1, 64), (512, 2, 64), (512, 4, 128)
994 (1024, 4, 64), (1024, 16, 1024), (1024, 8, 512), (1024, 4, 256), (1024, 2, 128),
(1024, 1, 64), (1024, 2, 64), (1024, 4, 128)
2018 (2048, 4, 64), (2048, 4, 128), (2048, 2, 64), (2048, 1, 64)
3042 (3072, 4, 64), (3072, 2, 64), (3072, 1, 64)
4066 (4096, 4, 64), (4096, 2, 64), (4096, 1, 64)
5090 (5120, 4, 64), (5120, 2, 64), (5120, 1, 64)
6114 (6144, 4, 64), (6144, 2, 64), (6144, 1, 64)
7138 (7168, 4, 64), (7168, 2, 64), (7168, 1, 64)
8162 (8192, 4, 64), (8192, 2, 64), (8192, 1, 64)
3 When passing the MAC Layer packet and Transmission Format from the MAC Layer
4 Protocol to the Physical Layer Protocol, the access network shall specify a Transmission
5 Format that is consistent with the MAC Layer packet.
6 10.8.6.1.59.8.6.1.5 Data Rate Control and Data Source Control Channels

7 This section defines the procedures for transmitting the DRC and DSC Channels associated
8 with each sub-Active Set in the access terminal’s Active Set.
9 The access terminal transmits a DRC Channel corresponding to each sub-Active Set as
10 indicated by public data of the Route Update Protocol in the Variable Rate State, as well as
11 in the Fixed DRC State. The access terminal transmits a DSC Channel corresponding to
12 each sub-Active Set as indicated by public data of the Route Update Protocol in the
13 Variable Rate State, as well as in the Fixed DRC State.
14 The DSC Channel transmission is either a null-cover or a cell-cover. The DSC symbol index
15 0 is called the “null cover”. If the DSC is a cell-cover, it specifies the Forward Link Data
16 Source represented by the cell cover. A Forward Link Data Source (or equivalently, a Data
17 Source) of the access terminal is a group of pilots in the sub-Active Set that maintain a
18 common forward link data queue for the access terminal. Pilots in the sub-Active Set of an
19 access terminal belonging to the same cell constitute a Data Source of the access terminal.
20 The access terminal is defined to be pointing the DSC at a Forward Link Data Source, if the
21 DSC transmitted by the access terminal is the cell cover associated with that Data Source.
9-148
1 Each DRC Channel transmission consists of a DRC cover and a DRC value. The access
2 terminal uses (DRC value, DRC cover) or (DRC value, auxiliary DRC cover) to specify the
3 set of requested transmission formats. The access terminal shall use the DRC cover or the
4 DSC and the auxiliary DRC cover to specify the requested pilot for packet transmission.
5 The access terminal shall use either the DRC cover index 0, the 3-bit DRC Cover index, or
6 the 3-bit auxiliary DRC Cover index associated with a sector in its sub-Active Set. The DRC
7 cover index 0 is called the “null cover”. A DRC cover or an auxiliary DRC cover that
8 corresponds to a pilot in the sub-Active Set of the access terminal is called a “pilot cover”.
9 Each pilot in the access terminal’s sub-Active Set is associated with one pilot cover (DRC
10 Cover) or two pilot covers (DRC Cover and Auxiliary DRC Cover). The access terminal may
11 have an auxiliary DRC cover associated with some of the pilots in its sub-Active Set.
12 The access terminal shall set the DRC value to a 5-bit DRC index, ranging from 0x0 to
13 0x1a. The DRC index 0 is also known as the null-rate DRC. Each DRC index is associated
14 with a Rate Metric, a Termination Target, a Maximum Span, a list of Single User
15 transmission formats and a list of Multi-User transmission formats, as shown in Table
16 9.8.6.1-2. Among the Single User transmission formats associated with a DRC index, the
17 transmission format with the largest Physical Layer Packet Size is defined to be the
18 canonical transmission format of the DRC index. In Table 9.8.6.1-2, the canonical
19 transmission format of each DRC index is typed in bold italics. The Rate Metric of a non-
20 zero DRC index is equal to the Nominal Data Rate (in kbps) of the canonical transmission
21 format of the DRC index. The Termination Target for each DRC Index specifies the nominal
22 duration over which the transmission formats associated with the DRC index are
23 transmitted. The Maximum Span for each DRC Index specifies the maximum duration over
24 which the Single User canonical transmission formats associated with the DRC index are
25 transmitted. The actual transmit duration of a single user packet with canonical
26 transmission format may be longer than its Termination Target, up to its Maximum Span;
27 consequently the actual data rate of a packet may be lower than its Nominal Data Rate.
9-149
1 Table 9.8.6.1-2 Rate Metric, Termination Target, Maximum Span, and Lists of
2 Associated Transmission Formats
DRC Rate Termination Maximum List of List of

Index Metric Target Span Associated Associated
(kbps) Single User Multi-User
(slots) (slots)
Transmission Transmission
Formats Formats
0x00 0 16 16 (128, 16, 1024), (128, 4, 256),
(256, 16, 1024), (256, 4, 256),
(512, 16, 1024), (512, 4, 256),

(1024, 4, 256)
(1024, 16, 1024)
0x01 38.4 16 16 (128, 16, 1024), (128, 4, 256),

(256, 16, 1024), (256, 4, 256),
(512, 16, 1024), (512, 4, 256),

(1024, 4, 256)
(1024, 16, 1024)
0x02 76.8 8 8 (128, 8, 512), (128, 4, 256),

(256, 8, 512), (256, 4, 256),
(512, 8, 512), (512, 4, 256),

(1024, 4, 256)
(1024, 8, 512)
0x03 153.6 4 8 (128, 4, 256), (128, 4, 256),

(256, 4, 256), (256, 4, 256),
(512, 4, 256), (512, 4, 256),

(1024, 4, 256)
(1024, 4, 256)
0x04 307.2 2 4 (128, 2, 128), (128, 4, 256),
(256, 2, 128), (256, 4, 256),
(512, 2, 128), (512, 4, 256),

(1024, 4, 256)
(1024, 2, 128)
0x05 307.2 4 8 (512, 4, 128), (128, 4, 256),
(1024, 4, 128), (256, 4, 256),
(2048, 4, 128) (512, 4, 256),

(1024, 4, 256),
(2048, 4, 128)
0x06 614.4 1 4 (128, 1, 64), (128, 4, 256),
(256, 1, 64), (256, 4, 256),
(512, 1, 64), (512, 4, 256),

(1024, 4, 256)
(1024, 1, 64)
9-150

(slots) (slots)
Formats Formats
0x07 614.4 2 4 (512, 2, 64), (128, 4, 256),
(1024, 2, 64), (256, 4, 256),
(2048, 2, 64) (512, 4, 256),

(1024, 4, 256),
(2048, 4, 128)
0x08 921.6 2 4 (1024, 2, 64), (128, 4, 256),
(3072, 2, 64) (256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64)
0x09 1228.8 1 4 (512, 1, 64), (128, 4, 256),
(1024, 1, 64), (256, 4, 256),
(2048, 1, 64) (512, 4, 256),

(1024, 4, 256),
(2048, 4, 128)
0x0a 1228.8 2 4 (4096, 2, 64) (128, 4, 256),
(256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
(4096, 2, 64)
0x0b 1843.2 1 4 (1024, 1, 64), (128, 4, 256),
(3072, 1, 64) (256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64)
0x0c 2457.6 1 4 (4096, 1, 64) (128, 4, 256),
(256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
9-151

(slots) (slots)
Formats Formats
(4096, 2, 64)
0x0d 1536 2 4 (5120, 2, 64) (128, 4, 256),
(256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
(4096, 2, 64),
(5120, 2, 64)
0x0e 3072 1 4 (5120, 1, 64) (128, 4, 256),
(256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
(4096, 2, 64),
(5120, 2, 64)
0x0f N/A N/A N/A N/A N/A
0x10 460.8 4 8 (1024, 4, 64), (128, 4, 256),
(2048, 4, 64), (256, 4, 256),
(3072, 4, 64) (512, 4, 256),

(1024, 4, 256),
(2048, 4, 128)
0x11 614.4 4 8 (1024, 4, 64), (128, 4, 256),
(2048, 4, 64), (256, 4, 256),
(4096, 4, 64) (512, 4, 256),

(1024, 4, 256),
(2048, 4, 128)
0x12 768.0 4 8 (1024, 4, 64) (128, 4, 256),
(2048, 4, 64) (256, 4, 256),
(5120, 4, 64) (512, 4, 256),

(1024, 4, 256),
(2048, 4, 128)
0x13 921.6 4 8 (2048, 4, 64), (128, 4, 256),
(6144, 4, 64) (256, 4, 256),
9-152

(slots) (slots)
Formats Formats
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128)
0x14 1075.2 4 8 (1024, 4, 64), (128, 4, 256),
(7168, 4, 64) (256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128)
0x15 1228.8 4 8 (8192, 4, 64) (128, 4, 256),
(256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128)
0x16 1843.2 2 4 (2048, 2, 64), (128, 4, 256),
(6144, 2, 64) (256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
(4096, 2, 64),
(5120, 2, 64)
0x17 2150.4 2 4 (1024, 2, 64), (128, 4, 256),
(7168, 2, 64) (256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
(4096, 2, 64),
(5120, 2, 64)
0x18 2457.6 2 4 (8192, 2, 64) (128, 4, 256),
(256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
(4096, 2, 64),
9-153

(slots) (slots)
Formats Formats
(5120, 2, 64)
0x19 3686.4 1 4 (2048, 1, 64), (128, 4, 256),
(6144, 1, 64) (256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
(4096, 2, 64),
(5120, 2, 64)
0x1a 4300.8 1 4 (1024, 1, 64), (128, 4, 256),
(7168, 1, 64) (256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
(4096, 2, 64),
(5120, 2, 64)
0x1b 4915.2 1 4 (8192, 1, 64) (128, 4, 256),
(256, 4, 256),
(512, 4, 256),
(1024, 4, 256),
(2048, 4, 128),
(3072, 2, 64),
(4096, 2, 64),
(5120, 2, 64)
1
2 The canonical packet size of a DRC index is defined to be the Physical Layer Packet Size of
3 the canonical transmission format of that DRC index.
4 The access terminal and the access network shall support all packet formats associated
5 with DRC indices 0x00 through 0x0e. The access terminal and the access network should
6 support all packet formats associated with DRC indices 0x10 through 0x1b. The access
7 terminal and the access network shall support all the packet formats associated with DRC
8 indices 0x10 through 0x1b for which the data rate is less than or equal to that indicated by
9 the MaxOptionalDataRate parameter of the ATSupportedPacketFormats attribute, and for
10 which the packet size is less than or equal to that indicated by the MaxOptionalPacketSize
11 parameter of the ATSupportedPacketFormats arttribute.
9-154
2 A Single User Transmission Format associated with a DRC index shown in Table 9.8.6.1-2
3 is defined to be compatible with the DRC index, if at least one of the following conditions is
4 met:
5 • The given transmission format coincides with the canonical transmission format of the
6 DRC index, or
7 • The canonical packet size of the DRC index is strictly less than the value of the
8 ShortPacketsEnabledThresh parameter of the ATSupportedPacketFormats attribute.
9 The access terminal shall obey the following rules when transmitting the DRC Channel:
10 • Access terminal shall use DRCLength slots to send a single DRC. The DRC (value and
11 cover) is defined to take effect at the slot boundary following the end of its transmission,
12 and stay in effect for DRCLength slots.
13 • If the DRC cover changes in slot T the access terminal shall set DRCChannelGain equal
14 to DRCChannelGainBase + DRCChannelGainBoost from slot T through slot (T +
15 DRCBoostLength – 1). Otherwise, the access terminal shall set the DRCChannelGain
16 equal to DRCChannelGainBase.
17 • The DRC (value and cover) shall not change in slots other than T such that:
24 The access terminal shall obey the following rules when transmitting the DSC Channel:
25 • Access terminal shall use DSCLength slots to send a single DSC. The DSC is defined to
26 take effect one slot after the end of its transmission and to stay in effect for DSCLength
27 slots.
28 • The DSC shall not change in slots other that T such that:
29 [T + 1 + 15 × FrameOffset] mod DSCLength = 0,
30 where T is the CDMA System Time in slots115.
115 Note that [T + 1 + 15 × FrameOffset] = (T + 1 – FrameOffset) + (16 × FrameOffset), where the first
term on the right hand side ensures that DSC symbol boundaries coincide with DRC symbol
boundaries, and the second term enables frame offset staggering of DSC symbol boundaries over the
maximum allowed value of DSC length (i.e., 256 slots).
9-155
1 • If the DSC changes in slot T the access terminal shall set DSCChannelGain equal to
2 DSCChannelGainBase + DSCChannelGainBoost from slot T through slot (T +
3 DSCBoostLength – 1). Otherwise, the access terminal shall set the DSCChannelGain
4 equal to DSCChannelGainBase.
5 • The access terminal receives DRCLock bits associated with every cell in each sub-Active
6 Set. The CDMA Channel and the MAC Index on which the DRCLock bits are received
7 are public data of the Route Update Protocol. If the access terminal receives a DRCLock
8 bit that is set to ‘0’ from a cell associated with a pilot in its active set and the access
9 terminal is pointing its DRC to a pilot associated with that cell, then the access
10 terminal should not point the DSC to the Data Source associated with that pilot.
11 When transmitting the DRC Channel, the access terminal shall set the DRC cover
13 • If the access terminal’s current DRC cover or auxiliary DRC cover is a pilot cover, then
14 the access terminal’s next DRC cover or auxiliary DRC cover shall not be a different
15 pilot cover. It may only be a cover for the same pilot or a null cover.
16 • If the DRC cover or auxiliary DRC cover is a pilot cover and the Data Source indicated
17 by the DSC is included in the terminals active set and the DRCLock bit associated with
18 that Data Source is set to ‘1’, then the pilot indicated by the DRC cover or auxiliary
19 DRC cover shall belong to the Data Source indicated by the DSC that is in effect during
20 the next DRCLength slots following transmission of the DRC.
21 • If the access terminal transmits a pilot cover when the DSC associated with that sub-
22 Active Set is not in effect, then the pilot cover shall be set to a DRC cover, and shall not
23 be set to an auxiliary DRC cover.
24 • If the access terminal’s most recent pilot cover belongs to pilot A, then the access
25 terminal shall not use a pilot cover corresponding to any other pilot B, until the access
26 terminal has determined that packets that may be transmitted to the access terminal
27 from pilot B will not overlap in time with packets transmitted from sector A.
28 A DRC transmitted by the access terminal is defined to be sustainable with respect to a
29 sector S in the active set of the access terminal, if one of the following conditions is met:
30 • The DRC value is zero, or
31 • The access terminal is capable of receiving any MAC layer packet from pilot S, provided
32 the transmission format of the packet is compatible with the DRC value, and the packet
33 transmission begins when the DRC is in effect.
34 When transmitting the DRC Channel, the access terminal shall set the DRC value
36 • If the access terminal sets the DRC cover or auxiliary DRC cover to a pilot cover, it shall
37 set the DRC value as follows:
40 pilot denoted by the DRC cover or auxiliary DRC cover.
9-156
1 − The access terminal shall set the Transmitted DRC value to four least
2 significant bits (LSBs) of the result of the DRC value specified by TxDRCMapN
3 that corresponds to the Tentative DRC value, where N is the hexadecimal value
4 of the DRC index, and TxDRCMapN is the corresponding parameter of the
5 TentativeDRCtoTxDRCMap attribute. If the most significant bit (MSB) of the
6 DRC value specified by TxDRCMapN of the Tentative DRC value is ‘1’, the
7 access terminal shall use the auxiliary DRC cover associated with the pilot.
8 Otherwise, the access terminal shall use the DRC cover associated with the
9 pilot.
10 • If the access terminal sets the DRC cover to the null cover, it shall set the DRC value as
11 follows:
14 best pilot in its sub-Active Set.
15 − The access terminal shall set the Transmitted DRC value to the DRC value
16 specified by TxDRCMapN that corresponds to the Tentative DRC value, where
17 N is the hexadecimal value of the DRC index, and TxDRCMapN is the
18 corresponding parameter of the TentativeDRCtoTxDRCMap attribute.
19 − The access terminal shall not use the optional transmission format when it
20 sets the DRC cover to the null cover.
21 The access terminal and the access network shall set the TxDRCMapN parameters of the
22 TentativeDRCtoTxDRCMap attribute such that both of the following conditions are
23 satisfied:
24 • Rate Metric of the DRC index corresponding to the Transmitted DRC value shall be less
25 than or equal to that of the DRC index corresponding to the Tentative DRC value, and
26 • Termination Target of the DRC index corresponding to the Transmitted DRC value shall
27 be greater than or equal to that of the DRC index corresponding to the Tentative DRC
28 value.
29 An access terminal is defined to be a potential target of a Single User MAC Layer packet if
30 the packet is addressed to the access terminal, and is received using a transmission
31 format, transmitting pilot, and the start time that could be used to receive a Single-User
32 packet to the access terminal. An access terminal is defined to be a potential target of a
33 Multi-User MAC Layer packet if the packet is received using a transmission format,
34 transmitting pilot, and the start time that could be used to receive a Multi-User packet.
35 A slot t is defined to be a continuation of an earlier slot s, if the following conditions are
36 met:
38 slot s.
9-157
1 • s < t < s + 4 × min(N1, N2, MinimumContinuationSpan), where N1 denotes the

2 Termination Target of the packet whose reception began in slot s and N2 denotes the
3 Termination Target of the DRC index corresponding to the DRC value that is in
4 effect during slot s (according to Table 9.8.6.1-2).
7 If the access terminal is a potential target of a packet transmitted by a pilot starting in slot
8 s, the access network shall not transmit another packet from the same Forward Link Data
9 Source to the access terminal in any slot t that is a continuation of slot s.
10 A slot t is defined to be an extension of an earlier slot s, if the following conditions are met:
12 slot s.
14 • s + 4 × N1 ≤ t < s + 4 × N3, where N1 denotes the Termination Target of the packet whose
15 reception began in slot s and N3 denotes the Maximum Span of the DRC index
16 corresponding to the DRC value that is in effect during slot s (according to Table
17 9.8.6.1-2Table 9.7.6.1-2).
21 10.8.6.1.6.19.8.6.1.6.1 Activate
25 10.8.6.1.6.29.8.6.1.6.2 Deactivate
26 If the protocol receives a Deactivate command in the Variable Rate State or the Fixed DRC
27 State,
29 transmitting the DRC and DSC Channels, and shall transition to the Inactive State.
31 access terminal, should cease receiving the DRC and DSC channels from this access
32 terminal, and should transition to the Inactive State.
34 10.8.6.1.79.8.6.1.7 Inactive State

9-158

2 In the Variable Rate State, the access network transmits one Forward Traffic Channel per
3 sub-Active Set using a sector and transmission format determined by the DRC Channel(s)
4 and the DSC Channel(s) transmitted by the access terminal.
7 10.8.6.1.8.19.8.6.1.8.1 Packet Transmission and DRC Requirements

9 The access terminal shall transmit a cell cover on the DSC Channel. The access terminal
10 shall set the cell cover to the value indicated by one of the DSC fields received in the last
12 The access terminal may inhibit transmission of data from pilots belonging to a sub-Active
13 Set by setting the corresponding DRC cover and the auxiliary DRC cover to the null cover.
14 In the Variable Rate State, a slot t is defined to be open at the access terminal, if slot t is
15 not the continuation of any previous slot, and the DRC in effect during slot t contains a
16 pilot cover. The pilot denoted by the pilot cover is defined to be the serving pilot of the
17 access terminal at slot t in the sub-Active Set that the pilot belongs to. In any open slot T,
18 the access terminal shall attempt to receive a MAC Layer packet from the serving pilot,
19 whose transmission begins in slot T and whose packet type and transmission format are
20 compatible with the DRC value in effect at slot T.

25 shall do so from the pilot associated with the DRC cover or the auxiliary DRC cover in
26 effect at slot T.
27 • If the access network transmits a MAC Layer packet to the access terminal starting in
28 slot T, it shall use a packet type and transmission format compatible with the DRC
29 value in effect at slot T.

33 The access terminal may initiate procedures for transitioning to the Fixed DRC State at any
35 Fixed DRC State:
36 • The access terminal shall start covering all DRC channels with the null cover
37 • The access terminal shall set all DSC channels to the null cover .
9-159
1 • The access terminal shall wait until it has determined that it will not be served by
2 any pilot and then, the access terminal shall send the FixedModeEnable message
3 specifying:
4 − A pilot in each sub-Active Set.
5 − A data rate associated with the pilot identified above.
6 − An “end time” for the operation in the Fixed DRC State.
7 The access terminal shall transition to the Fixed DRC State after sending a
8 FixedModeEnable message. The access network shall transition to the Fixed DRC State
9 after receiving of a FixedModeEnable message.
10 10.8.6.1.99.8.6.1.9 Fixed DRC State

15 • The <DRCCover, TCAMessageSequence> pair of fields included in the message shall
16 be set to the value of the <DRCCover, TCAMessageSequence> specified in the last
18 • The DRCValue field included in the message shall be set to the value of the
19 DRCValue specified in the last FixedModeEnable message sent, and
20 • The EndTime field included in the message shall not specify a time earlier than the
21 time specified by the EndTime included in the last FixedModeEnable message sent.
23 the Fixed DRC State.
25 from the pilot(s) specified in the last FixedModeEnable message at the rate compatible with
26 the DRCValue specified in that message, it should send at least one FixedModeXoff
27 message to the access network116. The access network should not start transmission of
28 any new Forward Traffic Channel MAC Layer packets to the access terminal after reception
29 of a FixedModeXoff message until the access network transitions to the Variable Rate State.
30 10.8.6.1.9.19.8.6.1.9.1 Packet Transmission Requirements

32 The access terminal shall transmit the null cover on the DSC Channel.
116 Note that sending an FixedModeXoff message does not cause a transition out of the Fixed DRC
9-160
1 In the Fixed DRC state, a slot t is said to be open if it is not the continuation of any
2 previous slot. The pilot denoted by the DRCCover field of the most recent FixedModeEnable
3 message is defined to be the serving pilot of the access terminal.
4 In any open slot T, the access terminal shall attempt to receive a MAC Layer packet from
5 the serving pilot(s), whose transmission begins in slot T and whose packet type and
6 transmission format are compatible with the DRC index specified by the DRCValue field(s)
7 of the most recent FixedModeEnable message.

12 shall do so from the pilot denoted by the DRCCover field in the most recent
14 • If the access network transmits a Single User packet to the access terminal starting
15 in slot T, it shall use a packet type and transmission format that are compatible
16 with the DRC index specified by the DRCValue field of the most recent
18 10.8.6.1.9.29.8.6.1.9.2 Transitions from the Fixed DRC State

22 the EndTime field in the last FixedModeEnable message sent.
23 • If the pilot specified in the last sent FixedModeEnable message is no longer a
24 member of the access terminal’s Active Set.
28 the EndTime field in the last FixedModeEnable message received.
29 • If the access network determines that pilot specified in the last received
30 FixedModeEnable message is no longer a member of the access terminal’s Active
31 Set.
34 where, SystemTime is the current CDMA System Time in units of slots.
9-161
2 10.8.6.1.10.19.8.6.1.10.1 DRC Supervision

3 The access terminal shall perform the DRC supervision independently for each of the
4 assigned reverse CDMA channels. The assigned reverse CDMA Channels are public data of
5 the Route Update Protocol. In the following procedures the Tentative DRC refers to the
6 Tentative DRC associated with a sub-Active set that carries the reverse power control bits
7 for that reverse link CDMA channel. The set of reverse CDMA channels that receive RPC
8 commands from a particular sub-Active set is referred to as reverse CDMA channel
9 associated with that sub-Active set.
10 The following figure shows an example in which the supervision for the reverse link CDMA
11 channel ‘y’ is performed based on the Tentative DRC_b because that is the Tentative DRC
12 associated with the sub-Active set that transmits power control bits associated with reverse
13 link CDMA channel ‘y’.
14
Supervision is performed on
DRC_b for RL frequency ‘y’ as this
is the DRC associated with the
Sub-Active set that carries the
RPC_x power control stream for the RL
FL frequency ‘a’ frequency ‘y’.
DRC_a
FL frequency ‘b’ DRC_b RL frequency ‘x’
RPC_y
RL frequency ‘y’
15
16 Figure 9.8.6-3. Example of the RPC and DRC Mapping Related to DRC supervision
17 The access terminal shall perform supervision on the DRC Supervision for each of the
18 assigned reverse CDMA channels associated with a sub-Active set (as defined above) as
19 follows:
20 • The access terminal shall maintain a DRC supervision timer for each assigned
21 reverse CDMA channel.
22 • The access terminal shall set the DRC supervision timer for (DRCSupervisionTimer ×
23 10) + 240 ms when the Tentative DRC of the associated sub-Active set is a null rate
24 DRC.
25 • The access terminal shall disable the timer if the DRC supervision timer is active
26 and any of the following conditions is true:
27 − the access terminal’s Tentative DRC of the associated sub-Active set indicates a
28 non-null rate
29 − the access terminal successfully receives a Forward Traffic Channel packet or a

30 Control Channel packet from a member of the associated sub-Active set
9-162
1 • If the DRC supervision timer expire, the access terminal shall disable transmission
2 of the corresponding Reverse Traffic Channel and set the Reverse Traffic Channel
3 Restart timer for time TFTCMPRestartTx for that reverse link CDMA Channel.
4 • If the Reverse Traffic Channel Restart timer is active and not expired, and either of
5 the following two conditions is satisfied, then the access terminal shall disable the
6 Reverse Traffic Channel Restart timer for that reverse link CDMA Channel and shall
7 enable transmission of the Reverse Traffic Channel on that reverse link CDMA
8 Channel.
9 − The access terminal generates consecutive Tentative DRC values that
10 correspond to non-null rates for more than NFTCMPRestartTx slots for the
11 associated sub-Active set, or
12 − the access terminal successfully receives a Forward Traffic Channel packet or
13 a Control Channel packet from a member of the e associated sub-Active set.
14 • If the Reverse Traffic Channel Restart timer expires for a reverse link CDMA channel,
15 the access terminal shall generate a ReverseTrafficChannelRestartTimerExpired
16 indication along with arguments indicating the reverse CDMA Channel associated
17 with the expired Restart timer.
18 • If the Reverse Traffic Channel Restart timers expire for all reverse link CDMA
19 Channels, then the access terminal shall return a SupervisionFailed indication and

22 The access terminal shall monitor the bit associated with its ReverseLinkMACIndex in the
23 ForwardTrafficValid63To0 or ForwardTrafficValid127To64 fields made available as public
24 data by the Overhead Messages protocol. If the Overhead Messages Protocol does not
25 provide a ForwardTrafficValid63To0 or ForwardTrafficValid127To64 field associated with
26 the access terminal, then the access terminal shall behave as if the field were set to ‘0’. If
27 this field is set to ‘0’, then the access terminal shall return a SupervisionFailed indication
28 and transition to the Inactive State.
32 Fixed DRC State.
33
9-163
Field Length (bits)

MessageID 8
NumSubActiveSets 5
NumSubActiveSets occurrences of the following
record:
DSC 3
DRCCover 3
DRCValue 4
EndTime 16
needed)
7 NumSubActiveSets
8 The access terminal shall set this field to the number of sub-Active
9 Sets assigned to the access terminal in the
10 TrafficChannelAssignment message with MessageSequence field
11 equal to the TCAMessageSequence field of this message.
12 DSC The ith occurrence of this field corresponds to the sub-Active Set
13 associated with the ith unique
14 (FeedbackMultiplexIndexFeedbackMultiplexingIndex,
15 FeedbackReverseChannelIndex) pair that the access terminal has
16 been assigned in the order of occurrence of unique
18 FeedbackReverseChannelIndex) pairs in the
19 TrafficChannelAssignment message whose MessageSequence field is
20 equal to the TCAMessageSequence field of this message. The access
21 terminal shall set the ith occurrence of this field to the DSC value
22 associated with the cell in the sub-Active Set from which it wants to
23 receive packets on the Forward Traffic Channel of the corresponding
24 CDMA Channel.
9-164
1 DRCCover The ith occurrence of this field corresponds to the sub-Active Set
2 associated with the ith unique
4 FeedbackReverseChannelIndex) pair that the access terminal has
5 been assigned in the order of occurrence of unique
7 FeedbackReverseChannelIndex) pairs in the
8 TrafficChannelAssignment message whose MessageSequence field is
9 equal to the TCAMessageSequence field of this message. The access
10 terminal shall set the ith occurrence of this field to the DRC cover
11 associated with the pilot in the sub-Active Set from which it wants to
12 receive packets on the Forward Traffic Channel of the corresponding
13 CDMA Channel.
14 DRCValue The ith occurrence of this field corresponds to pilot pointed to by the
15 ith DRCCover field. The access terminal shall set this field to one of
16 the valid DRC values (or DRC indices) in 9.8.6.2.1.EndTime The
17 access terminal shall set this field to the least significant 16 bits of
18 the CDMA System Time in units of slots until which (inclusive) it
19 requests to remain in the Fixed DRC State.
22 terminal shall set these bits to ‘0’. The access network shall ignore
23 this field.
24
25 10.8.6.2.29.8.6.2.2 FixedModeXoff
28 message.
29
Field Length (bits)

MessageID 8

31
9-165
3 given attribute.
4
Field Length (bits)
MessageID 8
TransactionID 8

9
12 AttributeUpdateRequest message to accept the offered attribute values. .
13
Field Length (bits)
MessageID 8
TransactionID 8
17
9-166
4
Field Length (bits)
MessageID 8
TransactionID 8
8
10 10.8.6.3.19.8.6.3.1 Commands Sent

12 10.8.6.3.29.8.6.3.2 Indications

17 Multicarrier Forward Traffic Channel MAC Protocol. The access terminal and the access
19 the following attributes belonging to the Multicarrier Forward Traffic Channel MAC
20 Protocol:
21 • DRCSupervisionTimer
22 • TentativeDRCtoTxDRCMap
23 • DRCChannelGainBoost
24 • DRCBoostLength
25 • DSCChannelGainBoost
26 • DSCBoostLength
9-167
1 If the value of the SupportGAUPMUPPreambles attribute is 0x01, then the access terminal
2 and the access network shall support the use of the Generic Attribute Update Protocol to
3 update values of the following attribute:
4 • MUPPreambleBase
5 If the value of the SupportGAUPDeltaACKChannelGainMUP attribute is 0x01, then the
6 access terminal and the access network shall support the use of the Generic Attribute
7 Update Protocol to update value of the following attribute belonging to the Multicarrier
8 Forward Traffic Channel MAC Protocol:
10 If the value of the SupportGAUPDeltaACKChannelGainMUP attribute is 0x00, the access
11 network shall not include the DeltaACKChannelGainMUP attribute in an
13 The access terminal shall not send an AttributeUpdateRequest message containing the
14 DeltaACKChannelGainMUP attribute.

16 The negotiable simple attributes for this protocol are listed in Table 9.8.7.1-1. The access
9-168

0xff DRCGating

times.
times.
0xfe DRCLockLength
times.
times.
All other Reserved
values
0x08 Length of a single DSC
transmission is 64 slots.
0x01 to Length of a single DSC
0xfcd DSCLength 0x20 transmission in units of 8
slots.
All other Reserved
values
0x0c DeltaACKChannelGainMUP is
6 dB.
0x00 to DeltaACKChannelGainMUP in
0xfbc DeltaACKChannelGainMUP 0x12 units of 0.5 dB.
0xff DeltaACKChannelGainMUP is
–∞ dB.
All other Reserved
values
0x00 DRC Supervision Timer is 0
0xf8b DRCSupervisionTimer
0x01- Value of DRC Supervision
0xff Timer
0x04 Minimum continuation span is
4 sub-packets
0x01- Value of Minimum
0x03 continuation span in sub-
0xf7a MinimumContinuationSpan and packets
0x05-
0x10
All other Reserved
values
9-169

0x00 Increase in DSCChannelGain is
0dB relative to
0xf69 DSCChannelGainBoost 0x01- Increase in DSCChannelGain

All other Reserved
values
the slot in which the DSC is
changed for which the DSC
Channel Gain is boosted is 128
slots
0xf58 DSCBoostLength
0x0F slots starting with the slot in
and which the DSC is changed for
0x11- which the DSC Channel Gain
0x40 is boosted
All other Reserved
values
0x00 Increase in DRCChannelGain
is 0dB relative to
in slot where DRC cover is
changed
0x01- Increase in DRCChannelGain
0xf47 DRCChannelGainBoost
in slot where DSC cover is
changed
All other Reserved
values
the slot in which the DRC cover
0xf36 DRCBoostLength is changed for which the
DRCChannelGain is boosted is
8 slots
0x03 slots starting with the slot in
and which the DRC cover is
0x05- changed for which the
0x20 DRCChannelGain is boosted
9-170

All other Reserved
values
Update Protocol to modify the
MUPPreambleBase attribute is
not supported
0xf25 SupportGAUPMUPPreambles
Update Protocol to modify the
MUPPreambleBase attribute is
supported
All other Reserved
values
0x42 Base MAC Index for Multi-User
packet preambles is decimal
66.
0x06 to Base MAC Index for Multi-User
MUPPreambleBase 0x3b packet preambles.
0xf14
and
0x48 to
0x7b
All other Reserved
values
0x00 DeltaACKChannelGainMUP
attribute can not be modified
using the Generic Attribute
Update Protocol.
SupportGAUPDeltaACKChan 0x01 DeltaACKChannelGainMUP
0xf0
nelGainMUP attribute can be modified using
the Generic Attribute Update
Protocol.
All other Reserved
values
0x00 The access terminal shall select

the same serving sector on all
the Sub-Active Sets. This
requires that the DRC cover (or
ServingSectorLockAcrossSub
0xef the auxiliary DRC cover) to be
ActiveSets
the same across the Sub-Active
Sets and the DSC value to be
the same across the Sub-Active
Sets.
9-171
0x01 The access terminal may select

a different serving sector on
each of the Sub-Active Sets.
The DRC cover (or auxiliary
DRC cover) may be different
across the Sub-Active Sets and
the DSC value may be different
across the Sub-Active Sets.
All other Reserved

values
1
2 The access terminal shall support the default value of the DRCGating attribute.

5

Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
10 complex value.
11 SofterHandoffDelay The sender shall set this field to the minimum interruption that the
12 access terminal should expect when the access terminal switches the
13 DRC from one sector to another sector in the same Forward Link
14 Data Source. The sender shall specify this field in units of 8 slots.
15 The access terminal may use this number to adjust its algorithm
16 controlling DRC switching. The access terminal shall support all the
9-172
1 SoftHandoffDelay The sender shall set this field to the minimum interruption that the
2 access terminal should expect when the access terminal changes the
3 DSC from one Forward Link Data Source to another. The sender
4 shall specify this field in units of 8 slots. The access terminal may
5 use this number to adjust its algorithm controlling DSC switching.
6 The access terminal shall support all the values of this field.
7 10.8.7.2.29.8.7.2.2 TentativeDRCtoTxDRCMap Attribute

8
9-173

Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
TxDRCMap01 5 0x01
TxDRCMap02 5 0x02
TxDRCMap03 5 0x03
TxDRCMap04 5 0x04
TxDRCMap05 5 0x05
TxDRCMap06 5 0x06
TxDRCMap07 5 0x07
TxDRCMap08 5 0x08
TxDRCMap09 5 0x09
TxDRCMap0A 5 0x0a
TxDRCMap0B 5 0x0b
TxDRCMap0C 5 0x0c
TxDRCMap0D 5 0x0d
TxDRCMap0E 5 0x0e
TxDRCMap10 5 0x05
TxDRCMap11 5 0x07
TxDRCMap12 5 0x07
TxDRCMap13 5 0x08
TxDRCMap14 5 0x08
TxDRCMap15 5 0x0a
TxDRCMap16 5 0x0b
TxDRCMap17 5 0x0b
TxDRCMap18 5 0x0c
TxDRCMap19 5 0x0e
TxDRCMap1A 5 0x0e
TxDRCMap1B 5 0x0e
}
Reserved 0 – 7 (as needed) N/A
9-174
5 complex value.
6 TxDRCMap01 The sender shall set this field to the DRC value that Tentative DRC
7 0x01 maps to. The sender shall not set this field to a DRC value that
8 corresponds to an optional canonical packet format with data rate
9 greater than that indicated by the MaxOptionalDataRate parameter
10 of the ATSupportedPacketFormats attribute. The sender shall not set
11 this field to a DRC value such that the corresponding canonical
12 packet format is optional and the payload size of the corresponding
13 canonical packet format is higher than that indicated by the
14 MaxOptionalPayloadSize parameter of the
15 ATSupportedPacketFormats attribute. The sender shall not set this
16 field to a DRC value whose Rate Metric is greater than that of DRC
17 index 0x01. The sender shall not set this field to a DRC value whose
18 Span is less than that of DRC index 0x01.
9-175
9-176
40 TxDRCMap0A The sender shall set this field to the DRC value that Tentative DRC
41 0x0a maps to. The sender shall not set this field to a DRC value that
9-177

8 index 0x0a. The sender shall not set this field to a DRC value whose
9 Span is less than that of DRC index 0x0a.
10 TxDRCMap0B The sender shall set this field to the DRC value that Tentative DRC
11 0x0b maps to. The sender shall not set this field to a DRC value that
21 index 0x0b. The sender shall not set this field to a DRC value whose
22 Span is less than that of DRC index 0x0b.
23 TxDRCMap0C The sender shall set this field to the DRC value that Tentative DRC
24 0x0c maps to. The sender shall not set this field to a DRC value that
34 index 0x0c. The sender shall not set this field to a DRC value whose
35 Span is less than that of DRC index 0x0c.
36 TxDRCMap0D The sender shall set this field to the DRC value that Tentative DRC
37 0x0d maps to. The sender shall not set this field to a DRC value that
9-178

4 index 0x0d. The sender shall not set this field to a DRC value whose
5 Span is less than that of DRC index 0x0d.
6 TxDRCMap0E The sender shall set this field to the DRC value that Tentative DRC
7 0x0e maps to. The sender shall not set this field to a DRC value that
17 index 0x0e. The sender shall not set this field to a DRC value whose
18 Span is less than that of DRC index 0x0e.
9-179
4 0x012 maps to. The sender shall not set this field to a DRC value
5 that corresponds to an optional canonical packet format with data
6 rate greater than that indicated by the MaxOptionalDataRate
7 parameter of the ATSupportedPacketFormats attribute. The sender
8 shall not set this field to a DRC value such that the corresponding
9 canonical packet format is optional and the payload size of the
10 corresponding canonical packet format is higher than that indicated
11 by the MaxOptionalPayloadSize parameter of the
9-180
9-181

23 TxDRCMap1A The sender shall set this field to the DRC value that Tentative DRC
24 0x01A maps to. The sender shall not set this field to a DRC value
34 index 0x1A. The sender shall not set this field to a DRC value whose
35 Span is less than that of DRC index 0x1A.
36 TxDRCMap1B The sender shall set this field to the DRC value that Tentative DRC
37 0x01B maps to. The sender shall not set this field to a DRC value
9-182

4 index 0x1B. The sender shall not set this field to a DRC value whose
5 Span is less than that of DRC index 0x1B.
6 Reserved The sender shall add reserved bits to make the length of the
7 attribute an integer number of octets. The sender shall set these bits
8 to ‘0’. The receiver shall ignore this field.
9 10.8.7.2.39.8.7.2.3 ATSupportedPacketFormats Attribute

10

Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
MaxOptionalDataRate 4 0x0
MaxOptionalPayloadSize 4 0x4
ShortPacketsEnabledThresh 4 0x1
}
Reserved 0 – 7 (as needed) N/A
15 complex value.
16 MaxOptionalDataRate
17 The sender shall set this field to the highest data rate it can support
18 if using the optional data rates as shown in Table 9.8.7.2.3-1.
9-183
1 Table 9.8.7.2.3-1. Values for MaxOptionalDataRate
Maximum Optional Data MaxOptionalDataRate

Rate Supported (kbps)
0.0 0x0
1228.8 0x1
3686.4 0x2
4300.8 0x3
4915.2 0x4
2 MaxOptionalPayloadSize
3 The sender shall set this field to the largest payload size it can support as
4 shown in Table 9.8.7.2.3-2.
5 Table 9.8.7.2.3-2. Values for MaxOptionalPayloadSize
Maximum Optional Physical MaxOptionalPayloadSize

Payload Supported (bits)
5120 0x4
6144 0x5
7168 0x6
8192 0x7
6 ShortPacketsEnabledThresh
7
8 The sender shall set this value according to Table 9.8.7.2.3-3. This field shall
9 be not be set to a value greater than MaxOptionalPayloadSize.
9-184
1 Table 9.8.7.2.3-3. Values for ShortPacketsEnabledThresh
ShortPacketsEnabledThresh Field
(bits)
1024 0x0
2048 0x1
3072 0x2
4096 0x3
5120 0x4
6144 0x5
7168 0x6
8192 0x7
2 Reserved The sender shall add reserved bits to make the length of the
5 10.8.7.2.49.8.7.2.4 ExtendedSpans Attribute

6

Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
ExtendedSpansEnabled 1 ‘0’
PERTargetSpan 0 or 1 N/A
Reserved 0 – 7 (as N/A

needed)
11 complex value.
9-185
1 ExtendedSpansEnabled
2 The sender shall set this field to ‘0’ to indicate that packet extensions
3 are disabled and to ‘1’ to indicate that packet extensions are enabled.
4 PERTargetSpan If ExtendedSpansEnabled is ‘0’, then the sender shall omit this field.
5 Otherwise, the sender shall set this field as follows:
6 The sender shall set this field to ‘0’ if the DRC Index generation is
7 performed to achieve a target PER after the termination target and to
8 ‘1’ if the DRC generation is performed to achieve a target PER after
9 the maximum span.
10 Reserved The sender shall add reserved bits to make the length of this

14

NS1MCFTCMPEnhanced Subtype field for this protocol 0x0002
Number of consecutive slots of non-null
rate DRCs to re-enable the Reverse Traffic
NFTCMPRestartTx 16
12 Control
cycles

18 protocol.
9-186
1 10.99.9 Default Reverse Traffic Channel MAC Protocol
2 10.9.19.9.1 Overview
3 The Default Reverse Traffic Channel MAC Protocol provides the procedures and messages
4 required for an access terminal to transmit, and for an access network to receive the
5 Reverse Traffic Channel. Specifically, this protocol addresses Reverse Traffic Channel
6 transmission rules and rate control. This protocol operates with the Default (Subtype 0)
7 Physical Layer Protocol or the Subtype 1 Physical Layer Protocol.
8 This specification assumes that the access network has one instance of this protocol for
9 every access terminal.
11 • Inactive State: In this state, the access terminal is not assigned a Reverse Traffic
13 • Setup State: In this state, the access terminal obeys the power control commands that
14 it receives from the access network. Data transmission on the Reverse Traffic Channel
15 is not allowed in this state.
16 • Open State: In this state, the access terminal may transmit data and negotiate different
17 transmission rates on the Reverse Traffic Channel.
18 The protocol states and the indications and events causing the transition between the
19 states are shown in Figure 9.9.1-1.
Initial State
Rx Activate
Inactive State Setup State
Rx Deactivate or
timer expires
Rx Deactivate Tx / Rx RTCAck
Open State
20
21 Figure 9.9.1-1. Default (Subtype 0) Reverse Traffic Channel MAC Protocol State
22 Diagram
9-187
2 10.9.2.19.9.2.1 Commands
4 • Activate
5 • Deactivate

8 • LinkAcquired
10 10.9.2.39.9.2.3 Public Data

21 • RPCStep
22 • MIRTCMAC
23 • MQRTCMAC

25 The transmission unit of this protocol is a Reverse Traffic Channel MAC Layer packet. Each
26 packet contains one Security Layer packet.

9-188
9 • The value of the public data for the InConfiguration protocol instance shall be set to the
10 value of the public data for the InUse protocol instance.

17 State.
19 10.9.5.19.9.5.1 Procedures

9-189
1 − RPCStep
3 then
15 instance for the Reverse Traffic Channel MAC Protocol.
21
Field Length (bits)
MessageID 8
TransactionID 8
26
9-190
3
Field Length (bits)
MessageID 8
TransactionID 8

12
14 10.9.6.19.9.6.1 Procedures
15 The protocol constructs a packet out of the Security Layer packets by adding the MAC
16 Layer trailer defined in 9.9.6.3.1. The protocol then sends the packet for transmission to
17 the Physical Layer. The packet structure is shown in Figure 9.9.6-1
MAC Layer packet
Security MAC
Layer Layer
packet trailer
18
19 Figure 9.9.6-1. Reverse Traffic Channel MAC Layer Packet Structure
9-191
3 The access network shall discard the MAC packet if the MACLayerFormat field of the MAC
4 Layer trailer is equal to ‘0’. The ConnectionLayerFormat field in the MAC Layer trailer shall
5 be passed to the Security Layer with the Security Layer packet.
6 The maximum size payload this protocol can support (i.e., the maximum size Security
7 Layer packet that can be carried) is a function of the transmission rate used on the Reverse
8 Traffic Channel. Table 9.9.6-1 provides the transmission rates and corresponding
9 minimum and maximum payload sizes available on the Reverse Traffic Channel.
10 Table 9.9.6-1. Reverse Traffic Channel Rates and Payload

0.0 0 0
9.6 1 232
19.2 233 488
38.4 489 1000
76.8 1001 2024
153.6 2025 4072
12 10.9.6.1.1.19.9.6.1.1.1 Activate
15 • Set ATILCM to TransmitATI.ATI
16 • Transition to the Setup State
18 10.9.6.1.1.29.9.6.1.1.2 Deactivate
19 If the protocol receives a Deactivate command in the Setup State or the Open State,
20 • Access terminal shall cease transmitting the Reverse Traffic Channel and shall
22 • Access network shall cease monitoring the Reverse Traffic Channel from this access
23 terminal and shall transition to the Inactive State.
9-192
1 10.9.6.1.29.9.6.1.2 Reverse Traffic Channel Long Code Mask

2 The access terminal shall set the long code masks for the reverse traffic channel (MIRTCMAC
3 and MQRTCMAC) as follows. The 42-bit mask MIRTCMAC shall be specified as shown in Table
4 9.9.6.1.2-1.
5 Table 9.9.6.1.2-1. Reverse Traffic Channel Long Code Masks
BIT
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
MIRTCMAC 1 1 1 1 1 1 1 1 1 1 Permuted (ATILCM)
6
8 Permuted (ATILCM) is defined as follows:

9 ATILCM = (A31, A30, A29, …, A0)
10 Permuted (ATILCM) =
11 (A0, A31, A22, A13, A4, A26, A17, A8, A30, A21, A12, A3, A25, A16, A7, A29, A20, A11, A2, A24,
12 A15, A6, A28, A19, A10, A1, A23, A14, A5, A27, A18, A9).
13 The 42-bit mask MQRTCMAC shall be derived from the mask MIRTCMAC as follows:
14 MQRTCMAC[k] = MIRTCMAC[k-1], for k = 1,…,41
15 MQRTCMAC[0] = MIRTCMAC[0] ⊕ MIRTCMAC[1] ⊕ MIRTCMAC[2] ⊕ MIRTCMAC[4] ⊕ MIRTCMAC[5] ⊕
16 MIRTCMAC[6] ⊕ MIRTCMAC[9] ⊕ MIRTCMAC[15] ⊕ MIRTCMAC[16] ⊕ MIRTCMAC[17] ⊕
18 MIRTCMAC[26] ⊕ MIRTCMAC[30] ⊕ MIRTCMAC[32] ⊕ MIRTCMAC[34] ⊕ MIRTCMAC[41]
19 where the ⊕ denotes the Exclusive OR operation, and MQRTCMAC[i] and MIRTCMAC[i] denote the
20 ith least significant bit of MQRTCMAC and MIRTCMAC, respectively.
21 10.9.6.1.39.9.6.1.3 Inactive State

22 When the protocol is in the Inactive State the access terminal and the access network wait
24 10.9.6.1.49.9.6.1.4 Setup State

26 The access terminal shall set a timer for TRTCMPATSetup seconds when it enters this state. If
27 the protocol is still in the Setup State when the timer expires, the access terminal shall
28 return a SupervisionFailed indication.
29 The access terminal shall start transmission on the Reverse Traffic Channel upon entering
30 this state, and shall obey the Reverse Power Control Channel. The access terminal shall set
31 the DRC value and cover as specified in the Forward Traffic Channel MAC Protocol.
9-193
1 The access terminal shall follow procedures specified in 9.9.6.2 in addition to the
2 requirement of the Physical Layer protocol for transmission on the Reverse Traffic Channel.
3 The access terminal shall not transmit any data on the Reverse Traffic Data Channel while
4 in this state.
5 If the access terminal receives an RTCAck message it shall return a LinkAcquired indication
6 and transition to the Open State.

8 The access network shall set a timer for TRTCMPANSetup seconds when it enters this state. If
9 the protocol is still in the Setup State when the timer expires, the access network shall
11 The access network shall attempt to acquire the Reverse Traffic Channel in this state. If the
12 access network acquires the Reverse Traffic Channel, it shall send an RTCAck message to
13 the access terminal, return a LinkAcquired indication, and shall transition to the Open
14 State.
15 10.9.6.1.59.9.6.1.5 Open State

18 10.9.6.1.5.19.9.6.1.5.1 Frame Offset Delay

19 The access terminal shall delay the Reverse Traffic Data Channel and Reverse Rate
20 Indicator Channel (RRI) transmissions by FrameOffset slots with respect to the system-
21 time-aligned frame boundary.
22 10.9.6.1.5.29.9.6.1.5.2 Rate Control

23 The description in this section uses the following variables: MaxRate, CurrentRate,
24 CombinedBusyBit, and CurrentRateLimit.
25 CurrentRateLimit shall be set initially to 9.6kbps. After a BroadcastReverseRateLimit
26 message or a UnicastReverseRateLimit message is received by the access terminal, the
27 access terminal shall update the CurrentRateLimit value as follows:
28 • If the RateLimit value in the message is less than or equal to the CurrentRateLimit
29 value, the access terminal shall set CurrentRateLimit to the RateLimit value in the
30 message immediately after the receipt of the message.
31 • If the RateLimit value in the message is greater than the CurrentRateLimit value, then
32 the access terminal shall set CurrentRateLimit to the RateLimit value in the message,
33 one frame (16 slots) after the message is received.
34 If the last received reverse activity bit is set to ‘1’ from any sector in the access terminal’s
35 active set, the access terminal shall set CombinedBusyBit to ‘1’. Otherwise, the access
36 terminal shall set CombinedBusyBit to ‘0’.
9-194
1 CurrentRate shall be set to the rate at which the access terminal was transmitting data
2 immediately before the new transmission time. If the access terminal was not transmitting
3 data immediately before the new transmission time, the access terminal shall set
4 CurrentRate to 0.
5 The access terminal sets the variable MaxRate based on its current transmission rate, the
6 value of the CombinedBusyBit, and a random number. The access terminal shall generate
7 a uniformly distributed random number x, 0 < x < 1, using the procedure specified in 13.5.
8 The access terminal shall evaluate the condition shown in Table 9.9.6.1.5-1 based on the
9 values of CurrentRate, CombinedBusyBit, and Condition. If the Condition is true, the
10 access terminal shall set MaxRate to the MaxRateTrue value for the corresponding row in
11 Table 9.9.6.1.5-1. Otherwise, the access terminal shall set MaxRate to the MaxRateFalse
12 value for the corresponding row in Table 9.9.6.1.5-1.
13 Table 9.9.6.1.5-1. Determination of MaxRate
CurrentRate Combined Condition MaxRateTrue MaxRateFalse

BusyBit
0 ‘0’ True 9.6kbps N/A
9.6kbps ‘0’ x < Transition009k6_019k2 19.2kbps 9.6kbps
153.6kbps ‘0’ False N/A 153.6kbps
0 ‘1’ False N/A 9.6kbps
14
15 The access terminal shall select a transmission rate that satisfies the following constraints:
16 • The access terminal shall transmit at a rate that is no greater than the value of
17 MaxRate.
19 CurrentRateLimit.
20 • The access terminal shall transmit at a data rate no higher than the highest data rate
21 that can be accommodated by the available transmit power.
22 • The access terminal shall not select a data rate for which the minimum payload length,
23 as specified in Table 9.9.6-1, is greater than the size of data it has to send.
9-195
1 10.9.6.1.5.39.9.6.1.5.3 Power Control

2 The access terminal shall control the reverse link transmit power in accordance with the
3 requirements of the Physical Layer Protocol.
4 10.9.6.29.9.6.2 Reverse Link Silence Interval

5 When invoked, the access terminal shall perform the procedures listed in this section.
6 The access terminal shall not transmit on the Reverse Traffic Data Channel if the
7 transmission of the Reverse Traffic Channel packet would overlap with the Reverse Link
8 Silence Interval117.
9 The access terminal shall not transmit on the Reverse Traffic Channel in time slots that
10 overlap with the Reverse Link Silence Interval.
12 ReverseLinkSilenceDuration frames that starts at times T specified by the following
13 equation:

20 The access terminal shall set the MAC Layer trailer as follows:
21
Field Length (bits)

MACLayerFormat 1
25 to ‘0’.
26 MACLayerFormat The access terminal shall set this field to ‘1’ if the MAC layer packet
27 contains a valid payload; otherwise, the access terminal shall set this
117 This implies that the access terminal must not even start transmission on the Reverse Traffic
Data Channel if the transmission of the Reverse Traffic Channel packet would overlap with the
Reverse Link Silence Interval.
9-196
1 10.9.6.3.29.9.6.3.2 RTCAck
2 The access network sends the RTCAck message to notify the access terminal that it has
3 acquired the Reverse Traffic Channel. The access network shall send this message using
4 the access terminal’s current ATI.
5
Field Length (bits)

MessageID 8

7
8 10.9.6.3.39.9.6.3.3 BroadcastReverseRateLimit
9 The BroadcastReverseRateLimit message is used by the access network to control the
10 transmission rate on the reverse link.
11
Field Length (bits)

MessageID 8
RPCCount 6
RPCCount occurrences of the following field
RateLimit 4
Reserved Variable
13 RPCCount The access network shall set this field to the number of RateLimit
14 fields in this message. RPCCount shall be greater than or equal to 64
15 minus the smallest MAC Index assigned to an access terminal that
16 has negotiated the Subtype 0 or Subtype 1 Reverse Traffic Channel
17 MAC Protocol.
18 RateLimit The access network shall set occurrence n of this field to the highest
19 data rate that the access terminal associated with MACIndex 64-n is
20 allowed to use on the Reverse Traffic Channel, as shown in Table
21 9.9.6.3-1.
9-197
1 Table 9.9.6.3-1. Encoding of the RateLimit Field
Field value Meaning

0x0 0 kbps
0x1 9.6 kbps
0x2 19.2 kbps
0x3 38.4 kbps
0x4 76.8 kbps
0x5 153.6 kbps
All other
Invalid
values
5 this field.
6
7 10.9.6.3.49.9.6.3.4 UnicastReverseRateLimit
8 The UnicastReverseRateLimit message is used by the access network to control the
9 transmission rate on the reverse link for a particular access terminal.
10
Field Length (bits)

MessageID 8
RateLimit 4
Reserved 4
12 RateLimit The access network shall set this field to the highest data rate that
13 the access terminal is allowed to use on the Reverse Traffic Channel,
9-198
Field value Meaning

0x0 0 kbps
0x1 9.6 kbps
0x2 19.2 kbps
0x3 38.4 kbps
0x4 76.8 kbps
0x5 153.6 kbps
All other
Invalid
values
5 this field.
6
8 10.9.6.4.19.9.6.4.1 Commands Sent

10 10.9.6.4.29.9.6.4.2 Indications

14 definition).

16
9-199

Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
DataOffsetNom 4 0
DataOffset9k6 4 0
DataOffset19k2 4 0
DataOffset38k4 4 0
DataOffset76k8 4 0
DataOffset153k6 4 0
RPCStep 2 1
Reserved 6 N/A
}
3 Length field.
6 complex value.
8 reverse link data channel power to pilot channel power, expressed as
9 2's complement value in units of 0.5 dB. The access terminal shall
11 DataOffset9k6 The access network shall set this field to the ratio of reverse link data
12 channel power at 9.6 kbps to the nominal reverse link data channel
13 power at 9.6 kbps, expressed as 2’s complement in units of 0.25 dB.
15 this field.
18 power at 19.2 kbps, expressed as 2’s complement in units of 0.25
19 dB. The access terminal shall support all the valid values specified by
20 this field.
9-200
5 this field.
10 this field.
12 channel power at 153.6 kbps to the nominal reverse link data
13 channel power at 153.6 kbps, expressed as 2’s complement in units
14 of 0.25 dB. The access terminal shall support all the valid values
16 RPCStep Reverse Power Control step. The access network shall set this field to
17 the power control step size the access terminal shall use when
18 controlling the power of the reverse link, as shown in Table 9.9.7.1-1.
20 this field.
21 Table 9.9.7.1-1. Encoding of the RPCStep Field
Field value Meaning

(binary)
‘00’ 0.5 dB
‘01’ 1.0 dB
All other
Invalid
values
24
25 10.9.7.29.9.7.2 RateParameters Attribute

26
9-201

Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
Transition009k6_019k2 8 0x30
Transition153k6_076k8 8 0xFF
5 complex value.
6 Transition009k6_019k2
7 The field is set to the probability the access terminal uses to increase
8 its transmission rate to 19.2kbps if it is currently transmitting at
9 9.6kbps. The probability is expressed in units of 1/255. The access
16
9-202
7 The field is set to the probability the access terminal uses to decrease
8 its transmission rate to 9.6kbps or lower if it is currently
9 transmitting at 19.2kbps. The probability is expressed in units of
10 1/255. The access terminal shall support all the valid values
9-203

NRTCMPType Type field for this protocol Table 2.5.4-1
NRTCMPDefault Subtype field for this protocol 0x0000
Maximum time for the access terminal to
TRTCMPATSetup transmit the Reverse Traffic Channel in 1.5 seconds
the Setup State
Maximum time for the access network to
TRTCMPANSetup acquire the Reverse Traffic Channel and 1 second
send a notification to the access terminal.

6 10.9.9.19.9.9.1 LongCodeMask Parameter

10 Parameter
Field Length (bits)
ParameterType 8
Length 8
MIRTCMAC 42
MQRTCMAC 42
Reserved 4
14 MIRTCMAC This field shall be set to the value of the reverse traffic channel in-
15 phase long code mask associated with the access terminal’s session.
16 MQRTCMAC This field shall be set to the value of the reverse traffic channel
17 quadrature-phase long code mask associated with the access
18 terminal’s session.
19 Reserved This field shall be set to zero.
9-204
1 10.109.10 Subtype 1 Reverse Traffic Channel MAC Protocol
2 10.10.19.10.1 Overview
3 The Subtype 1 Reverse Traffic Channel MAC Protocol provides the procedures and
4 messages required for an access terminal to transmit, and for an access network to receive
5 the Reverse Traffic Channel. Specifically, this protocol addresses Reverse Traffic Channel
6 transmission rules and rate control. This protocol operates with the Default (Subtype 0)
7 and Subtype 1 Physical Layer Protocols.
16 • Open State: In this state, the access terminal may transmit data and negotiate different
17 transmission rates on the Reverse Traffic Channel.
Initial State
Rx Activate
Rx Deactivate or
timer expires
Open State
20
21 Figure 9.10.1-1. Subtype 1 Reverse Traffic Channel MAC Protocol State Diagram
9-205
2 10.10.2.19.10.2.1 Commands
4 • Activate
5 • Deactivate

8 • LinkAcquired
10 10.10.2.39.10.2.3 Public Data

21 • RPCStep
22 • MIRTCMAC
23 • MQRTCMAC

26 packet contains one Security Layer packet.

9-206
12 10.10.5.19.10.5.1 Procedures

29 • RPCStep
31 then
9-207
10 10.10.5.39.10.5.3 Message Formats
13
Field Length (bits)
MessageID 8
TransactionID 8
18
21
9-208
Field Length (bits)
MessageID 8
TransactionID 8

9
11 10.10.6.19.10.6.1 Procedures
12 The protocol constructs a packet out of the Security Layer packets by adding the MAC
13 Layer trailer defined in 9.10.6.3.1. The protocol then sends the packet for transmission to
14 the Physical Layer. The packet structure is shown in Figure 9.10.6-1.
MAC Layer packet
Security MAC
Layer Layer
packet trailer
15
16 Figure 9.10.6-1. Reverse Traffic Channel MAC Layer Packet Structure
19 The access network shall discard the MAC packet if the MACLayerFormat field of the MAC
20 Layer trailer is equal to ‘0’. The ConnectionLayerFormat field in the MAC Layer trailer shall
21 be passed to the Security Layer with the Security Layer packet.
22 The maximum size payload this protocol can support (i.e., the maximum size Security
23 Layer packet that can be carried) is a function of the transmission rate used on the Reverse
9-209
1 Traffic Channel. Table 9.10.6-1 provides the transmission rates and corresponding
2 minimum and maximum payload sizes available on the Reverse Traffic Channel.
3 Table 9.10.6-1. Reverse Traffic Channel Rates and Payload

0.0 0 0
9.6 1 232
19.2 233 488
38.4 489 1000
76.8 1001 2024
153.6 2025 4072
5 10.10.6.1.1.19.10.6.1.1.1 Activate
11 10.10.6.1.1.29.10.6.1.1.2 Deactivate

21 9.10.6.1.2-1.
9-210
1 Table 9.10.6.1.2-1. Reverse Traffic Channel Long Code Masks
BIT
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
2

5 ATILCM = (A31, A30, A29, …, A0)
8 A15, A6, A28, A19, A10, A1, A23, A14, A5, A27, A18, A9).
10 MQRTCMAC[k] = MIRTCMAC[k-1], for k = 1,…,41
17 10.10.6.1.39.10.6.1.3 Inactive State

20 10.10.6.1.49.10.6.1.4 Setup State

27 the DRC value and DRC cover as specified in the Forward Traffic Channel MAC Protocol
28 that has been negotiated.
32 in this state.
9-211

10 State.
11 10.10.6.1.59.10.6.1.5 Open State

14 10.10.6.1.5.19.10.6.1.5.1 Frame Offset Delay

15 The access terminal shall delay the Reverse Traffic Data Channel and Reverse Rate
16 Indicator Channel (RRI) transmissions by FrameOffset slots with respect to the system-
17 time-aligned frame boundary.
18 10.10.6.1.5.29.10.6.1.5.2 Rate Control

19 The description in this section uses the following variables: MaxRate, CurrentRate,
20 CombinedBusyBit, and CurrentRateLimit.
21 CurrentRateLimit shall be set initially to 9.6kbps. After a BroadcastReverseRateLimit
22 message or a UnicastReverseRateLimit message is received by the access terminal, the
23 access terminal shall update the CurrentRateLimit value as follows:
24 • If the RateLimit value in the message is less than or equal to the CurrentRateLimit
25 value, the access terminal shall set CurrentRateLimit to the RateLimit value in the
26 message immediately after the receipt of the message.
27 • If the RateLimit value in the message is greater than the CurrentRateLimit value, then
28 the access terminal shall set CurrentRateLimit to the RateLimit value in the message,
29 one frame (16 slots) after the message is received.
30 If the last received reverse activity bit is set to ‘1’ from any sector in the access terminal’s
31 active set, the access terminal shall set CombinedBusyBit to ‘1’. Otherwise, the access
32 terminal shall set CombinedBusyBit to ‘0’.
33 CurrentRate shall be set to the rate at which the access terminal was transmitting data
34 immediately before the new transmission time. If the access terminal was not transmitting
35 data immediately before the new transmission time, the access terminal shall set
36 CurrentRate to 0.
37 The access terminal sets the variable MaxRate based on its current transmission rate, the
38 value of the CombinedBusyBit, and a random number. The access terminal shall generate
9-212
1 a uniformly distributed random number x, 0 < x < 1, using the procedure specified in 13.5.
2 The access terminal shall evaluate the condition shown in Table 9.10.6.1.5-1 based on the
3 values of CurrentRate, CombinedBusyBit, and Condition. If the Condition is true, the
4 access terminal shall set MaxRate to the MaxRateTrue value for the corresponding row in
5 Table 9.10.6.1.5-1. Otherwise, the access terminal shall set MaxRate to the MaxRateFalse
6 value for the corresponding row in Table 9.10.6.1.5-1.
7 Table 9.10.6.1.5-1. Determination of MaxRate
CurrentRate Combined Condition MaxRateTrue MaxRateFalse

BusyBit
0 ‘0’ True 9.6kbps N/A
0 ‘1’ False N/A 9.6kbps
8
9 The access terminal shall select a transmission rate that satisfies the following constraints:
11 MaxRate.
13 CurrentRateLimit.
14 • The access terminal shall transmit at a data rate no higher than the highest data rate
15 that can be accommodated by the available transmit power.
16 • The access terminal shall not select a data rate for which the minimum payload length,
17 as specified in Table 9.10.6-1, is greater than the size of data it has to send.
18 10.10.6.1.5.39.10.6.1.5.3 Power Control

21 10.10.6.29.10.6.2 Reverse Link Silence Interval

9-213
3 Silence Interval118.
7 ReverseLinkSilenceDuration frames that starts at times T, specified by the following
8 equation:

16
Field Length (bits)

MACLayerFormat 1
20 to ‘0’.
24 10.10.6.3.29.10.6.3.2 RTCAck
28
118 This implies that the access terminal must not even start transmission on the Reverse Traffic
Data Channel if the transmission of the Reverse Traffic Channel packet would overlap with the
Reverse Link Silence Interval.
9-214
Field Length (bits)

MessageID 8

2
3 10.10.6.3.39.10.6.3.3 BroadcastReverseRateLimit
4 The BroadcastReverseRateLimit message is used by the access network to control the
5 transmission rate on the reverse link.
6
Field Length (bits)

MessageID 8
RPCCount 6
RPCCount occurrences of the following field
RateLimit 4
Reserved Variable
8 RPCCount The access network shall set this field to the number of RateLimit
9 fields in this message. RPCCount shall be greater than or equal to 64
10 minus the smallest MAC Index assigned to an access terminal that
11 has negotiated the Subtype 0 or Subtype 1 Reverse Traffic Channel
12 MAC Protocol.
13 RateLimit The access network shall set occurrence n of this field to the highest
14 data rate that the access terminal associated with MACIndex 64-n is
15 allowed to use on the Reverse Traffic Channel, as shown in Table
16 9.9.6.3-1.
9-215
Field value Meaning

0x0 0 kbps
0x1 9.6 kbps
0x2 19.2 kbps
0x3 38.4 kbps
0x4 76.8 kbps
0x5 153.6 kbps
All other
Invalid
values
5 this field.
6
7 10.10.6.3.49.10.6.3.4 UnicastReverseRateLimit
8 The UnicastReverseRateLimit message is used by the access network to control the
9 transmission rate on the reverse link for a particular access terminal.
10
Field Length (bits)

MessageID 8
RateLimit 4
Reserved 4
12 RateLimit The access network shall set this field to the highest data rate that
13 the access terminal is allowed to use on the Reverse Traffic Channel,
9-216
Field value Meaning

0x0 0 kbps
0x1 9.6 kbps
0x2 19.2 kbps
0x3 38.4 kbps
0x4 76.8 kbps
0x5 153.6 kbps
All other
Invalid
values
5 this field.
6
9 given attribute.
10
Field Length (bits)
MessageID 8
TransactionID 8

15
9-217
4
Field Length (bits)
MessageID 8
TransactionID 8
8
12
Field Length (bits)
MessageID 8
TransactionID 8
16
18 10.10.6.4.19.10.6.4.1 Commands Sent

9-218
1 10.10.6.4.29.10.6.4.2 Indications

6 Subtype 1 Reverse Traffic Channel MAC Protocol. The access terminal and the access
8 the RateParameters attribute belonging to the Subtype 1 Reverse Traffic Channel MAC
9 Protocol.
11 definition).

13

Length 8 N/A
AttributeID 8 N/A
{
ValueID 8 N/A
DataOffsetNom 4 0
DataOffset9k6 4 0
DataOffset19k2 4 0
DataOffset38k4 4 0
DataOffset76k8 4 0
DataOffset153k6 4 0
RPCStep 2 1
Reserved 6 N/A
}
16 Length field.
19 complex value.
9-219
2 reverse link data channel power to pilot channel power, expressed as
3 2's complement value in units of 0.5 dB. The access terminal shall
7 power at 9.6 kbps, expressed as 2’s complement in units of 0.25 dB.
9 this field.
14 this field.
19 this field.
24 this field.
26 channel power at 153.6 kbps to the nominal reverse link data
27 channel power at 153.6 kbps, expressed as 2’s complement in units
28 of 0.25 dB. The access terminal shall support all the valid values
32 controlling the power of the reverse link, as shown in Table 9.10.7.1-
33 1. The access terminal shall support all the valid values specified by
34 this field.
9-220
1 Table 9.10.7.1-1. Encoding of the RPCStep Field
Field value Meaning

(binary)
‘00’ 0.5 dB
‘01’ 1.0 dB
All other
Invalid
values
4 10.10.7.29.10.7.2 RateParameters Attribute

5

Length 8 N/A
AttributeID 8 N/A
ValueID 8 N/A
Transition153k6_076k8 8 0xFF
10 complex value.
9-221
6
9-222

2

NS1RTCMP Subtype field for this protocol 0x0001
the Setup State


11 Parameter
Field Length (bits)
ParameterType 8
Length 8
MIRTCMAC 42
MQRTCMAC 42
Reserved 4
9-223
9-224

2 The use of Subtype 2 Reverse Traffic Channel MAC Protocol is discontinued and shall not
3 be used for any Reverse Traffic Channel MAC Protocol subtype.
4 10.11.1Overview
8 transmission rules and rate control. This protocol supports intra-access terminal Quality of
9 Service (QoS) for multiple concurrent MAC flows at the access terminal. Rate control is
10 accomplished via per MAC flow Traffic-to-Pilot power ratio (T2P) control. The Subtype 2
11 Reverse Traffic Channel MAC protocol provides per MAC flow QoS control. This is achieved
12 by distributed rate selection (at the access terminal) with centralized (scheduled) resource
13 allocation (by the access network). This protocol operates with the Default (Subtype 0)
14 Physical Layer Protocol or the Subtype 1 Physical Layer Protocol.
18 •Inactive State: In this state, the access terminal is not assigned a Reverse Traffic Channel.
19 When the protocol is in this state, it waits for an Activate command.
20 •Setup State: In this state, the access terminal obeys the power control commands that it
21 receives from the access network. Data transmission on the Reverse Traffic Channel is
22 not allowed in this state.
23 •Open State: In this state, the access terminal obeys the power control commands that it
24 receives from the access network. In this state, the access terminal may negotiate
25 different Subtype 2 Reverse Traffic Channel MAC Protocol parameters and attributes
26 per MAC flow and transmit data on the Reverse Traffic Channel.
9-225
Initial State
Rx Activate
Rx Deactivate or
timer expires
Open State
3 Each active MAC flow contributes to sector loading and its contribution is strongly
4 correlated with its average transmit T2P. An access terminal may transmit multiple active
5 MAC flows simultaneously. The Subtype 2 Reverse Traffic Channel MAC protocol uses the
6 average transmit T2P per active MAC flow as a measure of the air link resource used by
7 that MAC flow. The Subtype 2 Reverse Traffic Channel MAC protocol treats multiple active
8 flows associated with a single access terminal in a manner consistent with multiple active
9 MAC flows associated with multiple access terminals, subject to access terminal transmit
10 power constraints. This protocol controls the average T2P of an active MAC flow based on
11 the requirements of that MAC flow, requirements of other concurrent active MAC flows,
12 transmit power constraints, and sector loading. The Subtype 2 Reverse Traffic Channel
13 MAC protocol allows updating Reverse Traffic Channel MAC attributes (access terminal
14 specific and MAC flow specific) using the Generic Attribute Update Protocol.
15 10.11.2Primitives and Public Data
16 10.11.2.1Commands
18 •Activate
19 •Deactivate
20 10.11.2.2Return Indications
22 •LinkAcquired
23 •SupervisionFailed
9-226
1 10.11.2.3Public Data
3 •Subtype for this protocol
4 •RRI
5 •TxT2P
6 •RPCStep
7 •MIRTCMAC
8 •MQRTCMAC
9 •RAChannelGain for each pilot in the Active Set.
10 10.11.3Protocol Data Unit

12 Reverse Traffic Channel MAC Layer packet contains one Security Layer packet.
13 10.11.4Protocol Initialization
14 10.11.4.1Protocol Initialization for the InConfiguration Protocol Instance

17 •The fall-back values of the attributes for this protocol instance shall be set to the default
18 values specified for each attribute.
19 •If the InUse instance of this protocol has the same protocol subtype as this
23 •The value for each attribute for this protocol instance shall be set to the fall-back value for
24 that attribute.
25 •The value of the public data for the InConfiguration protocol instance shall be set to the
27 10.11.5Procedures and Messages for the InConfiguration Instance of the Protocol
31 The access network shall not initiate negotiation of the MaxMACFlows attribute.
9-227
1 10.11.5.2Commit Procedures
5 •All the public data that are defined by this protocol, but are not defined by the InUse
7 •The value of the following public data of the InUse protocol shall be set to the
9 −RPCStep
10 •If the InUse instance of this protocol has the same subtype as this protocol instance, then
11 −The access terminal and the access network shall set the attribute values
14 −The access terminal and the access network shall purge the InConfiguration
16 •If the InUse instance of this protocol does not have the same subtype as this protocol
19 −The access terminal shall set FRABn = 0, where n is the current sub-frame.
20 −For each MAC flow i, the access terminal shall set LastBucketLevelMaxi to NULL.
21 −The access terminal and the access network shall set the initial state for the
23 −The InConfiguration protocol instance shall become the InUse protocol instance
24 for the Reverse Traffic Channel MAC Protocol.
25 •All the public data not defined by this protocol shall be removed from the public data of
27 10.11.5.3Message Formats
28 10.11.5.3.1ConfigurationRequest
30
9-228
Field Length (bits)
MessageID 8
TransactionID 8
Zero or more instances of the following record:
6 10.11.5.3.2ConfigurationResponse
8
Field Length (bits)
MessageID 8
TransactionID 8
Zero or more instances of the following record:

17
9-229
1 10.11.6Procedures and Messages for the InUse Instance of the Protocol
3 The protocol constructs a Subtype 2 Reverse Traffic Channel MAC Layer packet out of a
4 Security Layer packet and passes the packet for transmission to the Physical Layer
5 Protocol.
6 The Subtype 2 Reverse Traffic Channel MAC Protocol supports multiple MAC flows. MAC
7 flow NN is defined to be active if the value of the BucketLevelMaxNN attribute associated
8 with MAC flow NN is not NULL, where NN is the two-digit hexadecimal flow number in the
9 range 0x00 to MaxNumMACFlows −1, inclusive. The number of active MAC Flows shall not
10 exceed the value of the MaxNumActiveMACFlows parameter of the MaxMACFlows attribute.
11 10.11.6.1.1MAC Layer Packet

12 The MAC Layer packet is the basic unit of data provided by the Subtype 2 Reverse Traffic
13 Channel MAC protocol to the Physical Layer Protocol. The structure of a MAC Layer packet
14 is shown in Figure 10.11.6.1.1-1. The MAC Layer packet consists of a Security Layer
15 packet followed by the MAC Layer trailer.
MAC Layer packet
Security MAC
Layer Layer
packet trailer
16
17 Figure 10.11.6.1.1-1.Reverse Traffic Channel MAC Layer Packet Structure
18 10.11.6.1.2Command Processing
19 10.11.6.1.2.1Activate
22 •Set ATILCM to TransmitATI.ATI
23 •Transition to the Setup State
25 10.11.6.1.2.2Deactivate
9-230
1 •Access terminal shall cease transmitting the Reverse Traffic Channel and shall transition
2 to the Inactive State.
3 •Access network shall cease monitoring the Reverse Traffic Channel from this access
6 10.11.6.1.3Reverse Traffic Channel Long Code Mask

9 10.11.6.1.3-1.
10 Table 10.11.6.1.3-1.Reverse Traffic Channel Long Code Masks
BIT
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
11

13 ATILCM = (A31, A30, A29, …, A0)
16 A15, A6, A28, A19, A10, A1, A23, A14, A5, A27, A18, A9).
18 MQRTCMAC[k] = MIRTCMAC[k−1], for k = 1,…,41
25 10.11.6.1.4Inactive State
28 10.11.6.1.5Setup State
29 10.11.6.1.5.1Access Terminal Requirements

9-231
3 the DRC value and DRC cover as specified by the Forward Traffic Channel MAC Protocol .
7 in this state.
10 10.11.6.1.5.2Access Network Requirements

17 State.
18 10.11.6.1.6Open State
19 10.11.6.1.6.1Access Terminal Requirements

20 Upon entering the Open State the access terminal shall perform the following.
21 −Set FRABn = 0, where n is the current sub-frame.
22 −For each MAC flow i, set LastBucketLevelMaxi to NULL.
23 Table 10.11.6.1.6.1-1 provides the transmission rates and corresponding minimum and
24 maximum payload sizes available on the Reverse Traffic Channel.
25 Table 10.11.6.1.6.1-1. Reverse Traffic Channel Rates and Payload

0.0 0 0
9.6 1 232
19.2 233 488
38.4 489 1000
76.8 1001 2024
153.6 2025 4072
26
9-232
1 Table 10.11.6.1.6.1-2. Traffic Channel to Pilot Channel power ratios
Physical
Layer
Data Channel Gain Relative to Pilot (dB)
Packet
Size
(bits)
0 − ∞ (Data Channel is not transmitted)

256 T2P256
512 T2P512
1024 T2P1024
2048 T2P2048
4096 T2P4096
2
3 The physical layer transmit duration is one frame.

4 T2PPS define the T2P’s used by the access terminal for transmitting a Reverse Traffic
5 Channel packet with packet size PS, where PS can take on the following values: 256, 512,
6 1024, 2048, and 4096 bits.
7 The access network uses the Reverse Activity (RA) bit (one RA bit per sector) to provide an
8 indication of loading on the each sector’s reverse link to the access terminal. The reliability
9 of the RA channel is improved by filtering the RA bit at the access terminal. A long term
10 filter is used to generate the FRAB (Filtered RA Bit) which indicates long term sector
11 loading.
12 The access terminal shall start transmission of the Reverse Traffic Data Channel and
13 Reverse Rate Indicator at the earliest time T following the end of transmission of the
14 previous packet that satisfies the following equation:
15 (T − FrameOffset) mod 16 = 0,
17 This section defines the procedures and rules that the access terminal shall use to
18 determine the T2P allocation for each active MAC flow. Variables with suffix m indicate
19 quantities that are updated every slot and variables with suffix n indicate quantities that
20 are updated every sub-frame. Unless otherwise stated, all filters used in this section are
21 first order IIR filters (see 14.13). PS indicates the physical layer packet size and takes on
22 values of 256, 512, 1024, 2048, or 4096 bits.
23 The description in this section uses the following variables:
24 •AllocationStagger: T2P allocation time stagger.
25 •BucketLeveli,n: Bucket Level (or accumulated T2P resource) at sub-frame n for MAC flow i.
26 •BucketFactori( ): Indicates by what factor (linear) the T2POutflowi,n can exceed

27 T2PInflowi,n for MAC flow i.
9-233
1 •BucketLevelMaxi: Max T2P resource that can be accumulated (bucket size) for MAC flow i.
2 •BucketLevelSati,n: Saturation Level for BucketLevel i,n.
3 •BurstDurationFactori: Maximum duration (in sub-frames) for which MAC flow i can
4 sustain a peak rate based on its T2P allocation.
5 •di,n: Number of octets allocated to MAC flow i for a Reverse Traffic Channel transmission
6 during sub-frame n.
7 •F: Set of all active MAC flows with non-empty queues.
8 •FRABn: Effective Filtered RAB value at sub-frame n.
9 •FRABn,s: Indicates the Filtered RAB value from sector s at sub-frame n.
10 •LastBucketLevelMaxi: The last recorded value of BucketLevelMaxi,n.
11 •PacketSizePSn: Physical Layer packet size, in octets, with packet size PS transmitted in
12 sub-frame n.
13 •PermittedPayloadPS_k: Maximum Physical Layer packet size that an access terminal is
14 permitted to transmit in sub-frame n if the Physical Layer packet size transmitted in
15 sub-frame n − (4 × k) was PS bits.
16 •PilotStrengthm,s: Filtered PilotStrength (filter time constant of PilotStrengthFilterTC) of a
17 sector s in the access terminal’s active set.
18 •PilotStrengthn,s: Filtered PilotStrength of sector s sampled at the start of sub-frame n.
19 •PilotStrength( ): Function that provides the scale factor for scaling T2PInflowi,n based on
20 the Pilot strength of the forward link serving sector. .
21 •PilotStrengthQRABThresholdDRCLock: Minimum PilotStrength value required for QRAB
22 (from any sector other than the Forward Link serving sector) to be included in the
23 QRABpsn computation when sector DRC is in lock.
24 •PilotStrengthQRABThresholdDRCUnlock: Minimum PilotStrength value required for QRAB

25 (from any sector other than the Forward Link serving sector) to be included in the
26 QRABpsn computation when sector DRC is not in lock.
27 •PotentialT2POutflowi: Potential Outflow from the bucket for MAC flow i.
28 •Qi,n: Queue length (in octets) of MAC flow i at sub-frame n.
29 •QRABi,n: Effective Quick RAB value for MAC flow i at sub-frame n.
30 •QRABn: Effective Quick RAB value at sub-frame n. QRABn,s: Indicates the Quick RAB
31 value from sector s at sub-frame n.
32 •QRABpsn: Indicates the effective Quick RAB value generated at sub-frame n based on
33 PilotStrengthn,s of the sectors s in its active set.
34 •QRABSelecti: Indicates which QRAB value, QRABpsn or QRABn that the access terminal
35 uses as an indication of sector loading for MAC flow i.
9-234
1 •rn: Real-valued uniformly distributed random number in the range [−1,1].
2 •SlotFRABm,s: Filtered value (with filter time constant FRABFilterTC) at slot m of the soft
3 RA bit SoftRABm,s provided by the Physical Layer Protocol.
4 •SlotQRABm,s: Hard-limited value of SoftQRABm,s, taking on a value of −1 or +1.
5 •SoftQRABm,s: Filtered value (with filter time constant QRABFilterTC) at slot m of the soft
6 RA bit SoftRABm,s provided by the physical layer.
7 •SoftRABm,s: Soft RA bit provided by the Physical Layer Protocol at slot m for sector s.
8 •SumPayloadn: Sum of the octets di,n of all active MAC flows i included in a packet
9 transmitted in sub-frame n.
10 •T2PInflowmini: Minimum value of the permitted T2PInflow for MAC flow i.
11 •T2PInflowmaxi: Maximum value of the permitted T2PInflow for MAC flow i.
12 •T2PConversionFactor: Conversion Factor from T2P to Physical Layer packet size.

13 •T2PFilterTCi: Filter time constant for MAC flow i used to compute the average T2P.
14 •T2PNoTxFilterTC: Filter time constant used to compute the average T2P when the access
15 terminal is in Open state but not transmitting on the Reverse Traffic Channel due to
16 not receiving the corresponding Forward Channel.
17 •TT2PHoldi,n: Indicates number of sub-frames following sub-frame n for which the T2P
18 allocation received via the Grant message shall be maintained by the access terminal
19 for MAC flow i.
20 •T2PInflowi,n: Denotes the average T2P resource added to the bucket for MAC flow i at sub-
21 frame n.
22 •T2POutflowi,n: Denotes the average T2P resource utilized (and subtracted) from the bucket
23 for MAC flow i at sub-frame n.
24 •TxT2Pmax( ): Maximum TxT2P that an access terminal is permitted to transmit as a
25 function of PilotStrengthn,s, where s is the forward link serving sector.
26 •TxT2Pmin: TxT2P that an access terminal is permitted to transmit at any time.

27 •TxT2Pn: Transmitted T2P during sub-frame n.
28 •ΔT2PInflowi,n: Increase or decrease in T2PInflowi,n at sub-frame n for MAC flow i.
29 •T2PUpi( ): Two-dimensional piecewise linear function for computing increase in T2PInflow

30 for MAC flow i based on current T2PInflow and current FRAB.
31 •T2PDni( ): Two-dimensional piecewise linear function for computing decrease in T2PInflow
32 for MAC flow i based on current T2PInflow and current FRAB.
33 The access terminal shall determine T2PUpi(T2PInflowi,n, FRABn) and T2PDni(T2PInflowi,n,
34 FRABn) by bilinear interpolation on the T2P-FRAB grid using the method described in
35 14.12. The access terminal shall determine PilotStrength(PilotStrengthn,s) by linear
36 interpolation on the PilotStrength axis using the method described in 14.11.
9-235
1 The access terminal shall determine BucketFactori,n by bilinear interpolation on the T2P-
2 FRAB grid using the method described in 14.12. The access terminal shall determine
3 TxT2Pmaxn(PilotStrengthn,s) by linear interpolation on the PilotStrength axis using the
4 method described in 14.11.
5 The T2PUp(), T2PDn(), PilotStrength(), BucketFactor(), and TxT2Pmax() functions are
6 piecewise linear in the dB domain.
7 If the access terminal is receiving the corresponding Forward Channel and no slot of sub-
8 frame n overlaps with a Reverse Link Silence Interval, then the access terminal shall
9 perform the following operations at the start of every slot m of sub-frame n for each sector s
10 in its active set:
11 1.Initialization due to active set update: Upon inclusion of a new sector s into the
12 access terminal’s active set, the access terminal shall perform the following steps:
13 −Set PilotStrengthm,s to the corresponding PilotStrength which is public data of the
14 Route Update Protocol
15 −Set SoftQRABm,s = 0
16 −Set SlotFRABm,s = FRABn−1
17 2.Update PilotStrengthm,s: The access terminal shall update the PilotStrength (in the
18 linear domain) using an IIR filter with filter time constant PilotStrengthFilterTC,
19 where PilotStrength is public data of the Route Update Protocol.
20 3.Update SlotQRABm,s: The access terminal shall generate SlotQRABm,s by filtering
21 (IIR filter with filter time constant QRABFilterTC) the soft RA bit from sector s in
22 slot m to generate SoftQRABm,s, and then hard-limiting SoftQRABm,s to generate
23 SlotQRABm,s. The hard-limiter maps positive input values to +1 and negative or
24 zero input values to −1.
25 4.Update SlotFRABm,s: The access terminal shall generate SlotFRABm,s by filtering
26 (IIR filter with filter time constant FRABFilterTC) the soft RA bit (SoftRABm,s) from
27 sector s in slot m.
28 If the access terminal is receiving the Forward Channel and any slot of sub-frame n
29 overlaps with a Reverse Link Silence Interval, the access terminal shall perform the
30 following operations at the start of every slot m of sub-frame n for each sector s in its active
31 set:
32 1.Update PilotStrengthm,s: The access terminal shall update the PilotStrength (in the
35 2.Update SlotQRABm,s: Set SoftQRABm,s = 0 and SlotQRABm,s = −1.
36 3.Update SlotFRABm,s: Set SlotFRABm,s = max(0, SlotFRABm-1,s).
37 If the access terminal is not receiving the Forward Channel, the access terminal shall
9-236
1 1.Update PilotStrengthm,s: This value is not changed as part of this operation.
2 2.Update SlotQRABm,s: Set SoftQRABm,s = 0 and SlotQRABm,s = −1.
3 3.Update SlotFRABm,s: This value is not changed as part of this operation.
4 The access terminal shall perform the following operations at the start of each sub-frame n
5 to determine allocation for that sub-frame:
6 1.Update PilotStrengthn,s
7 −The access terminal shall sample PilotStrengthm,s for a sector s in the access
8 terminal’s active set at sub-frame n to generate PilotStrengthn,s.
9 2.Update QRABn
10 −The access terminal shall sample SlotQRABm,s from each sector s in the access
11 terminal’s active set at sub-frame n to generate QRABn,s.
12 −The access terminal shall determine QRABn from QRABn,s at sub-frame n using
13 the following rules :
14 +The access terminal shall set QRABn = +1 (Loaded) if QRABn,s == +1 (Loaded)
15 for any sector s in the access terminal’s active set.
16 +The access terminal shall set QRABn = −1 (UnLoaded) if QRABn,s == −1
17 (UnLoaded) for every sector s in the access terminal’s active set.
18 3.Update QRABpsn
19 −The access terminal shall determine QRABpsn from QRABn,s at sub-frame n

20 using the following rules :
21 +The access terminal shall set QRABpsn = +1 (Loaded) if QRABn,s == +1 for a
22 sector s in the access terminal’s active set, which satisfies one or more of the
23 following conditions:
24 −Sector s is the forward link serving sector for the access terminal
25 −The DRCLock bit from a cell associated with sector s is ‘0’ (Out of Lock) and
26 PilotStrengthn,s of sector s is greater than
27 PilotStrengthQRABThresholdDRCUnlock.
28 −The DRCLock bit from a cell associated with sector s is ‘1’ (In Lock) and
30 PilotStrengthQRABThresholdDRCLock.
31 +The access terminal shall set QRABpsn = −1 (UnLoaded) if none of the
32 conditions above are satisfied.
33 4.Update FRABn
34 −The access terminal shall sample SlotFRABm,s at sub-frame n to generate

35 FRABn,s. The access terminal shall set FRABn to the largest value of FRABn,s
36 received from all sectors s in the access terminal’s active set.
9-237
1 5.Initialization for each active MAC flow i

2 −For each active MAC flow i the access terminal shall perform the following step:
3 +If LastBucketLevelMaxi is NULL and BucketLevelMaxi is not NULL then the
5 −Set BucketLeveli,n119 = 0.
6 −Set T2PInflowi,n−1 = 10^(T2PInflowmini/10).
7 −Set TT2PHoldi,n−1 = 0.
8 −Set T2POutflow i,n−1 = 0.
9 −Set BucketLevelSati,n = 10^(BucketLevelMaxi/10).
10 +Set LastBucketLevelMaxi = BucketLevelMaxi.
11 6.Update buckets with inflows for each active MAC flow i.

12 −Determine ΔT2PInflowi,n
13 +The access terminal shall set QRABi,n = +1 (Loaded) if either of the following
15 −QRABSelecti == +1 for MAC flow i and QRABpsn == +1 at sub-frame n
16 −QRABSelecti == 0 for MAC flow i and QRABn == +1 at sub-frame n
17 +If none of the conditions above are satisfied, the access terminal shall set
18 QRABi,n = −1 (Unloaded)
19 +If TT2PHoldi,n−1 == 0 and QRABi,n == +1 the access terminal shall compute

20 ΔT2PInflowi,n using the following equation:
21 ΔT2PInflowi,n= −1 × 10^(T2PDni(10 × log10(T2PInflowi,n−1) +
22 PilotStrength(PilotStrengthn,s), FRABn)/10)
23 where s is the forward link serving sector for the access terminal.
24 +If TT2PHoldi,n−1 == 0 and QRABi,n == −1 and BucketLeveli,n <
25 BucketLevelSati,n, then the access terminal shall compute ΔT2PInflowi,n
26 using the following equation:
27 ΔT2PInflowi,n= + 1 × 10^(T2PUpi(10 × log10( T2PInflowi,n−1) +
29 where s is the forward link serving sector for the access terminal.
30 +If TT2PHoldi,n−1 == 0 and QRABi,n == −1 and BucketLeveli,n ≥
31 BucketLevelSati,n, then the access terminal shall set ΔT2PInflowi,n using the
119 BucketLevel
i,n is allowed to take on a negative value.
9-238
1 ΔT2PInflowi,n = 0
2 +The access terminal shall set ΔT2PInflowi,n to 0 if the access terminal is not
3 receiving the corresponding Forward Channel or any slot of sub-frame n
4 overlaps with a Reverse Link Silence Interval.
5 −Update T2P Inflows
6 +If TT2PHoldi,n−1 == 0, then the access terminal shall update T2PInflowi,n, using
7 the following equations if receiving the corresponding Forward Channel during
8 sub-frame n.
9 T2PInflowi,n = (1 − (1/T2PFilterTCi)) × T2PInflowi,n−1 + (1/T2PFilterTCi) ×
10 T2POutflowi,n−1 + ΔT2PInflowi,n
11 T2PInflowi,n = max(T2PInflowi,n , 10^(T2PInflowmini / 10))
12 T2PInflowi,n = min(T2PInflowi,n , 10^(T2PInflowmaxi / 10))
13 +If TT2PHoldi,n−1 == 0, then the access terminal shall update T2PInflowi,n if not
14 receiving the corresponding Forward Channel during sub-frame n using the
15 following equations:
16 T2PInflowi,n = (1 − (1/T2PNoTxFilterTC)) × T2PInflowi,n−1
17 T2PInflowi,n = max(T2PInflowi,n, 10^(T2PInflowmini / 10))
18 T2PInflowi,n = min(T2PInflowi,n, 10^(T2PInflowmaxi / 10))
19 +If TT2PHoldi,n−1 > 0, then the access terminal shall maintain the inflow
20 T2PInflowi,n as the inflow in the previous sub-frame T2PInflowi,n−1.
21 +If TT2PHoldi,n−1 > 0, the access terminal shall decrement the value of TT2PHold
22 by 1 sub-frame using the following equation:
23 TT2PHoldi,n = TT2PHoldi,n−1 − 1
24 7.Determine Reverse Traffic Channel packet transmission for sub-frame n

25 −If the access terminal started transmission of a reverse traffic channel packet in
26 sub-frame n-1, n-2, or n-3, it shall continue transmission of that packet in
27 sub-frame n.
28 −The access terminal shall not start transmission of a Reverse Traffic Channel
29 packet in sub-frame n if the first slot T within sub-frame n does not satisfy the
33 −If the access terminal starts transmission a Reverse Traffic Channel packet in
34 sub-frame n, it shall determine the packet size, and contents of the packet in
35 accordance with 10.11.6.1.6.1.1.
36 8.Determine TxT2Pn
9-239
1 −If the access terminal transmits a Reverse Traffic Channel packet in sub-frame n
2 with Physical Layer packet size PS, the access terminal shall set TxT2P during
3 sub-frame n using the following equation:
4 TxT2Pn = 10^(T2PPS / 10)
5 9.Update T2P outflows for each active MAC flow i

6 −If the access terminal transmits a Reverse Traffic Channel packet in sub-frame n,
7 the bucket outflows shall be specified by the following equation:
8 T2POutflowi,n = (di,n / SumPayloadn) × TxT2Pn
9 where di,n is the number of octets from active MAC flow i contained in the payload
10 and SumPayloadn is the sum of di,n over all active MAC flows i.
11 −If the access terminal does not transmit a Reverse Traffic Channel packet in sub-
12 frame n, the bucket outflows shall be specified by the following equation:
13 T2POutflowi,n = 0
14 10.Update Bucket Level for each active MAC flow i

15 −The access terminal shall determine BucketLevelSati,n+1 for active MAC flow i using
17 BucketLevelSati,n+1 = min(BurstDurationFactori × BucketFactori(10 ×
18 log10(T2PInflowi,n), FRABn) × T2PInflowi,n, 10^(BucketLevelMaxi / 10)).
19 −If the access terminal is not receiving the corresponding Forward Channel during
20 sub-frame n or any slot of sub-frame n overlaps with the Reverse Link Silence
21 Interval, then the access terminal shall set BucketLeveli,n+1 = 0.
22 −If the access terminal is receiving the corresponding Forward Channel during
23 sub-frame n and no slot of sub-frame n overlaps with the Reverse Link Silence
24 Interval, then the access terminal shall set the bucket level for the next sub-
25 frame as specified by the following equation120:
26 BucketLeveli,n+1 = min(BucketLeveli,n + T2PInflowi,n – T2POutflowi,n ,
27 BucketLevelSati,n+1)
28 11.When the access terminal transmits a security layer packet, the access terminal
29 shall transmit the Security Layer packet only on the active MAC flow associated by
30 the AssociatedFlowsNN attribute with the application layer packet(s) contained in
31 the Security Layer packet . The access terminal shall not transmit Security Layer
32 packets containing signaling using any flow other than MAC flow 0x00.
33 10.11.6.1.6.1.1Packet size and Transmission Mode selection requirements

34
120 BucketLevel
i,n is allowed to take on a negative value
9-240
1 10.11.6.1.6.1.1.1Procedures
2 1.The access terminal shall set PotentialT2POutflowi for each active MAC flow i by
4 PotentialT2POutflowi = max (0, min((1 + AllocationStagger × rn) × (BucketLeveli,n / 4
5 + T2PInflowi,n) , BucketFactori(10 × log10(T2PInflowi,n), FRABn) × T2PInflowi,n))
6 2.The access terminal shall determine T2PConversionFactor by maximizing the

7 T2PConversionFactor over all permitted Physical Layer packet sizes, using the
9 T2PConversionFactor = maxPS(PacketSizePS / 10^( T2PPS /10))
10 3.The access terminal shall construct the set F to be the set of all active MAC flows
11 with non-empty queues at sub-frame n.
12
13 10.11.6.1.6.1.1.2Requirements
14 1.If the access terminal starts transmission of a Reverse Traffic Channel packet in
15 sub-frame n with packet size PS with di,n octets from each active MAC flow i, then
16 the access terminal shall ensure that the following conditions are satisfied:
17 −Condition 1:
18 PS ≤ min(PermittedPayloadPS1_1, PermittedPayloadPS2_2, PermittedPayloadPS3_3)
19 where PSk is the Physical Layer packet size transmitted in sub-frame n - 4 × k
20 −Condition 2:
21 10^(T2PPS/10) ≤ max(10^(TxT2Pmin / 10), ∑i∈FPotentialT2POutflowi)
22 −Condition 3:
23 10^(T2PPS / 10) ≤ 10^(TxT2Pmax(PilotStrengthn,s) / 10)
24 −Condition 4: No packet with lower T2PPS is able to carry a packet of size PS as

25 specified by the following equation:
26 ∑ i∈F min(di,n , T2PConversionFactor × PotentialT2POutflowi)
27 −Condition 5: Packet size PS can be accommodated by the available transmit

28 power.
29 10.11.6.1.6.1.2Request message
30 The access terminal may include a request in the Request message for up to
31 MaxNumMACFlows MAC flows. The access terminal can include requests for multiple MAC
32 flows in a single Request packet. The access terminal shall transmit the Request message
33 in the first Reverse Traffic Channel packet that it transmits after one of the following
9-241
1 1.ReqRatio is not equal to 0 and the access terminal has transmitted (1 / ReqRatio – 1)
2 × RequestPktSize bits of data on the traffic channel since the last Request packet
3 transmission, where RequestPktSize denotes the number of bits in the Request
4 message.
5 2.MaxReqInterval is not equal to zero and MaxReqInterval frames have elapsed since
6 the last transmission of a Request message.
7 10.11.6.1.6.1.3Grant message
8 If the access terminal receives a Grant message the access terminal shall update the
9 following parameters for each MAC flow i for which the Grant message was received.
10 •T2PInflowi,n with 10x/10, where x is the value of T2PInflow in units of dB
11 •BucketLeveli,n with 10x/10, where x is the value of BucketLevel in units of dB
12 •TT2PHoldi,n with 4 × x, where x is the value of TT2PHold in units of frames
13 10.11.6.1.6.1.4Power Control
15 requirements of the Physical Layer.
16 10.11.6.1.6.1.5Reverse Link Silence Interval

20 Silence Interval.
24 ReverseLinkSilenceDuration frames that starts at times T and it satisfies the following
25 equation:
26 T mod (2048 × (2ReverseLinkSilencePeriod) – 1) = 0
28 The ReverseLinkSilenceDuration and ReverseLinkSilencePeriod parameters are public data
29 of the Overhead Messages Protocol.
30 10.11.6.1.6.2Access Network Requirements

31 The access network uses the RA bit to reflect the reverse link sector loading. The access
32 network should transmit the Reverse Activity Channel with a gain equal to or greater than
33 that specified by RAChannelGain.
34 The access network should ensure that T2PPS is such that the Reverse Traffic Channel
35 packet is received by the access network with the target packet erasure rate.
9-242
1 10.11.6.1.6.2.1Grant message
2 The access network may transmit Grant messages at any time. The Grant messages are
3 either transmitted autonomously or are transmitted in response to Request messages
4 received from the access terminal. The Grant message is transmitted by the access network
5 to an access terminal for which the access network is the forward link serving sector. The
6 timing and content of the Grant message is determined by the access network. The Grant
7 message contains “grants” for one or more MAC flows. A per MAC flow resource allocation
8 contains the following:
9 −T2PInflow
10 −BucketLevel
11 −TT2PHold
12 10.11.6.2Trailer and Message Formats
13 10.11.6.2.1MAC Layer Trailer

15
Field Length (bits)
MACLayerFormat 1
17 If the Security Layer packet contains a Format B Connection Layer

18 packet, then the access terminal shall set this field to ‘1’. Otherwise,
23 10.11.6.2.2RTCAck
27
Field Length (bits)

MessageID 8

29
9-243
1 10.11.6.2.3Request
2 The access terminal sends the Request message to notify the access network of the
3 maximum TxT2P that it can use for Reverse Traffic Channel transmissions and the queue
4 length for zero or more of its MAC flows.
5
Field Length (bits)

MessageID 8
MaxSupportableTxT2P 8
NumMACFlows 5
NumMACFlows occurrences of the following
record:
MACFlowID 4
QueueLength 4
Reserved 3
7 MaxSupportableTxT2P
8 The access terminal shall set this field to its maximum supportable
9 Transmit Traffic-to-Pilot power ratio. The access terminal shall
10 specify this field as an 8-bit value with units of 0.25 dB.
11 NumMACFlows The access terminal shall set this field to the number of MAC flows
12 for which the access terminal transmits a request.
13 MACFlowID The access terminal shall set this field to the identifier that is
14 assigned to the MAC flow. The access terminal shall support MAC
15 flow identifiers in the range 0…15, inclusive.
16 QueueLength The access terminal shall set this field to the length of the queue
17 associated with the MACFlowID indicated by this field. The access
18 terminal shall specify this field as a 4-bit number as specified in
19 Table 10.11.6.2.3-1.
9-244
1 Table 10.11.6.2.3-1.Encoding of QueueLength Field
QueueLength, QueueLength (octets)

q
QL
0 0 ≤ QL < 32
1 32 ≤ QL < 64
2 64 ≤ QL < 96
3 96 ≤ QL < 128
4 128 ≤ QL < 192
5 192 ≤ QL < 256
6 256 ≤ QL < 384
7 384 ≤ QL < 512
8 512 ≤ QL < 768
9 768 ≤ QL < 1024
10 1024 ≤ QL < 1536
11 1536 ≤ QL < 2048
12 2048 ≤ QL < 4096
13 4096 ≤ QL < 8192
14 8192 ≤ QL < 16384
15 QL ≥ 16384
2
3 Reserved The access terminal shall set this field to ‘000’. The access network
5
6 10.11.6.2.4Grant
7 The access network transmits the Grant message to notify the access terminal of the
8 following parameters for one or more of the active MAC flows at the access terminal:
9 •T2PInflow
10 •BucketLevel
11 •TT2PHold
12
9-245
Field Length (bits)
MessageID 8
NumMACflows 4
(NumMACflows+1) occurrences of the following record:
MACFlowID 4
T2PInflow 8
BucketLevel 8
TT2PHold 6
Reserved 0-7 (as

needed)
2 NumMACflows The access network shall set this field to one less than the number of
3 MAC Flows for which the Grant is transmitted. The access network
4 shall specify this field as a 4-bit value in the range 0…15, inclusive.
5 The access terminal shall support all valid values for this field.
6 MACFlowID The access network shall set this field to the MAC Flow identifier for
7 which the Grant is transmitted. The access network shall specify this
8 field as a 4-bit value in the range 0…15, inclusive. The access
9 terminal shall support all valid values for this field.
10 T2PInflow The access network shall set this field to the T2PInflow for the MAC
11 flow identified by the corresponding MACFlowID. The access network
12 may set this field to 255 to indicate a value of -∞. Otherwise, the
13 access network shall specify this field as an 8-bit value in the range
14 of 0 to 63.5 dB in units of 0.25 dB. The access network shall support
15 all valid values of this field. The access terminal shall support all
16 valid values for this field.
17 BucketLevel The access network shall set this field to BucketLevel for the MAC
21 of 0 to 63.5 dB in units of 0.25 dB. The access terminal shall support
22 all valid values of this field.
23 TT2PHold The access network shall set this field to the interval of time, for
24 which the access terminal shall maintain the T2PInflow for the MAC
25 flow identified by the corresponding MACFlowID after receiving the
9-246
1 Grant message. The access network shall specify this field as a 6-bit
2 in units of frames. The access terminal shall support all valid values
3 of this field.
5 entire message an integer number of octets. The access network
6 shall set these bits to ‘0’. The access terminal shall ignore this field.
7
8 10.11.6.2.5AttributeUpdateRequest
10 given attribute.
11
Field Length (bits)
MessageID 8
TransactionID 8

16
17 10.11.6.2.6AttributeUpdateAccept
20
Field Length (bits)
MessageID 8
TransactionID 8
9-247
3
4 10.11.6.2.7AttributeUpdateReject
7
Field Length (bits)
MessageID 8
TransactionID 8
11
12 10.11.6.3Interface to Other Protocols
13 10.11.6.3.1Commands Sent
15 10.11.6.3.2Indications
17 10.11.7Configuration Attributes
18 The access terminal and the access network shall support the use of the Generic Attribute
19 Update Protocol to configure values of the following attributes:
20 •AssociatedFlowsNN
21 •BucketFactorNN
22 •BucketLevelMaxNN
23 •BurstDurationFactorNN
24 •PermittedPayload
25 •PilotStrengthQRABThresholdDRCLock
9-248
1 •PilotStrengthQRABThresholdDRCUnlock
2 •QRABSelectNN
3 •RequestParameters
4 •T2PFilterTCNN
5 •T2PTransitionFunctionNN
6 •T2PInflowRangeNN
7 where NN is the two-digit hexadecimal flow number in the range 0x00 to
8 MaxNumMACFlows – 1, inclusive. The updated values of the attributes shall be consistent
9 with the value of the MaxNumActiveMACFlows parameter of the MaxMACFlows attribute.
10 The access network and the access terminal shall not use the Generic Attribute Update
11 Protocol to configure any other attributes of the Subtype 2 Reverse Traffic Channel MAC
12 Protocol.
14 definition).
15 10.11.7.1Simple Attributes
9-249
1 Table 10.11.7.1-1.Configurable Simple Attributes

ID
0xffff FRABFilterTC 0x02 IIR filter time constant the access
terminal uses for computing the Filtered
RA bit is 384 slots.
0x00 IIR filter time constant the access
All other Reserved
values
0xfffe PilotStrengthFilterTC 0x01 IIR filter time constant the access
terminal uses for computing the filtered
serving sector Pilot Strength,
PilotStrengthn,s for sector s is 64 slots.


All other Reserved

values
0xfffd QRABFilterTC 0x00 IIR filter time constant the access
terminal uses for computing the Quick
RA bit is 4 slots.
terminal uses for computing the Quick
RA bit is 8 slots.
All other Reserved
values
0xfffc T2PNoTxFilterTC 0x01 IIR filter time constant the access
terminal uses for computing T2PInflown
is 24 sub-frames when access terminal is
in Open state but not transmitting on the
Reverse Link.
9-250

ID
0x00 IIR filter time constant that the access
Reverse Link.
Reverse Link.
Reverse Link.
is 128 sub-frames when access terminal
is in Open state but not transmitting on
the Reverse Link.
All other Reserved
values
0xfffb PilotStrengthQRABThre 0x18 PilotStrengthQRABThresholdDRCLock is
sholdDRCLock −6 dB
0x00 to PilotStrengthQRABThresholdDRCLock is
0x3f in units of –0.25 dB in the range 0 dB to
–15.75 dB, inclusive
All other Reserved
values
0xfffa PilotStrengthQRABThre 0x0c PilotStrengthQRABThresholdDRCUnlock
sholdDRCUnlock is −3 dB
0x00 to PilotStrengthQRABThresholdDRCUnlock
0x3f is in units of –0.25 dB in the range 0 dB
to –15.75 dB, inclusive
All other Reserved
values
0xfe00 BucketLevelMax00 0x50 BucketLevelMax for flow 0x00 is 20 dB
0x01 to BucketLevelMax for flow 0x00 in units of
0xff 0.25 dB
0x00 Reserved
0xfe01 BucketLevelMax01 0x6c BucketLevelMax for flow 0x01 is 27 dB
9-251

ID
0x01 to BucketLevelMax for flow 0x01 in units of
0xff 0.25 dB
0x00 BucketLevelMax for flow 0x01 is NULL
0xfeNN BucketLevelMaxNN 0x00 BucketLevelMax for flow NN is NULL.
NN is the NN is the two-digit 0x01 to BucketLevelMax for flow NN in units of
two-digit hexadecimal MAC flow 0xff 0.25 dB
hexadeci number in the range
mal MAC 0x02 through
flow MaxNumMACFlows −1,
number inclusive, where
in the hexadecimal digits A
range through F are specified
0x02 in upper case letters.
through
MaxNum
MACFlow
s −1,
inclusive.
0xfdNN QRABSelectNN 0x00 Use QRAB
NN is the NN is the two-digit 0x01 Use QRABps
two-digit hexadecimal MAC flow
All other Reserved
values
mal MAC 0x00 through
through
MaxNum
MACFlow
s −1,
inclusive.
0xfcNN BurstDurationFactorNN 0x00 BurstDurationFactor for flow NN is 4
NN is the NN is the two-digit 0x01 BurstDurationFactor for flow NN is 8
0x02 BurstDurationFactor for flow NN is 16
mal MAC 0x00 through 0x03 BurstDurationFactor for flow NN is 32
9-252

ID
flow MaxNumMACFlows −1, All other Reserved
number inclusive, where values
through
MaxNum
MACFlow
s −1,
inclusive.
0xfbNN T2PFilterTCNN 0x01 IIR filter time constant the access
terminal uses for computing T2PInflowi,n
NN is the NN is the two-digit
two-digit hexadecimal MAC flow for flow 0xNN is 24 sub-frames.
hexadeci number in the range 0x00 IIR filter time constant the access
mal MAC 0x00 through terminal uses for computing T2PInflowi,n
flow NMFRTCMACFlowMax − 1,
for flow 0xNN is 16 sub-frames.
in the hexadecimal digits A 0x02 IIR filter time constant the access
range through F are specified terminal use for computing T2PInflowi,n
0x00 in upper case letters. for flow 0xNN is 32 sub-frames.
through
NMFRTCMAC 0x03 IIR filter time constant the access
FlowMax −
1, for flow 0xNN is 64 sub-frames.
inclusive.
for flow 0xNN is 128 sub-frames.
All other Reserved
values
1
2 10.11.7.2Complex Attributes
3 The following configurable complex attributes are defined:
4 10.11.7.2.1AssociatedFlowsNN Attribute
5 NN is the two-digit hexadecimal number that identifies the MAC Flows in the range 0x01
6 through MaxNumMACFlows −1, inclusive.
7
9-253
Field Length(bits) Default for NN between 0x02 and Default

(MaxNumMACFlows −1), for NN =
inclusive 0x01
Length 8 N/A N/A

One or more occurrences of the following attribute value record:
{
ValueID 8 N/A N/A
FlowCount 8 0 1
FlowCount occurrences of the following two fields:
{
Stream 9 N/A 511
SubStream 8 N/A 0
}
Reserved 0 – 7 (as N/A N/A
needed)
}
4 hexadecimal number that identifies the MAC Flow in the range 0x01
7 complex value.
8 FlowCount The sender shall set this field to the number of higher layer flows
9 associated with this MAC Flow.
10 Stream If this flow is generated by an application bound to a stream, then

11 the sender shall set this field to the stream number. If this flow is
12 generated by an application bound to a virtual stream, then the
13 sender shall set this field to three more than the virtual stream
14 number. If this MAC flow is to be associated with all higher layer flow
15 not associated with a MAC flow, then the sender shall set this field to
16 ‘111111111’.
17 SubStream If the application bound generating this flow defines sub-streams,

18 then the sender shall set this field to the number of the sub-stream
9-254
1 associated with this MAC flow121. Otherwise, the sender shall set this
2 field to ‘00000000’. If Stream is ‘111111111’, then the sender shall
5 attribute value record an integer number of octets. The receiver shall
7 10.11.7.2.2BucketFactorNN Attribute
121 For example, in case of the Multi-flow Packet Application, this field is set to the RLP flow number
corresponding to the RLP flow associated with this MAC flow.
9-255
Length Default for Default for

Field (bits) NN > 0x00 NN = 0x00
Length 8 N/A N/A

{
ValueID 8 N/A N/A
NumT2PAxisValues 4 0x04 0x01
NumFRABAxisValues 3 0x01 0x00
NumT2PAxisValues + 1 occurrences of the following field:
T2PAxis 8 See Table See Table
10.11.7.2.2-1 10.11.7.2.2-4
NumFRABAxisValues + 1 occurrences of the following field:
FRABAxis 4 See Table See Table
10.11.7.2.2-2 10.11.7.2.2-5
(NumT2PAxisValues + 1) × (NumFRABAxisValues + 1) occurrences of the following
field:
BucketFactorT2PAxisFRABAxis 8 See Table See Table
10.11.7.2.2-3 10.11.7.2.2-6
Reserved 0-7 (as N/A N/A

needed)
}
5 hexadecimal MAC flow number in the range 0x00 through
6 MaxNumMACFlows −1, inclusive.
8 complex value.
9 NumT2PAxisValues The sender shall set this field to the number of occurrences of
10 T2PAxis field in this record minus 1. The sender shall specify this
11 field as an 4-bit value. The receiver shall support all valid values
13 NumFRABAxisValues
9-256
1 The sender shall set this field to the number of occurrences of

2 FRABAxis field in this record minus 1. The sender shall specify this
5 T2PAxis The sender shall set this field to values that define the T2P axis. The
6 sender shall specify this field as an 8-bit value in units of 0.25 dB.
7 The values specified shall be monotonically increasing. The receiver
8 shall support all valid values specified by this field.
9 FRABAxis The sender shall set this field to values that define the FRAB axis.
10 The sender shall specify this field as a 4-bit 2’s complement value in
11 the range -1…7/8, inclusive. The values specified shall be
12 monotonically increasing. The receiver shall support all valid values
14 BucketFactorT2PAxisFRABAxis
15 The sender shall set this field to the values of the function
16 BucketFactor() at the T2PInflow value of T2PAxis and FRAB value of
17 FRABAxis. The sender shall set the data in the following order:
18 BucketFactor( ) is specified for all the FRABaxis values, then cycled
19 through for each T2PAxis value. The sender shall specify this field as
20 an 8-bit value in the range 1...32 7/8, inclusive, in units of 1/8. The
21 receiver shall support all valid values specified by this field.
24 set these bits to zero. The receiver shall ignore this field.
25
26 Table 10.11.7.2.2-1. T2PAxis Default Values
Field Default for NN

> 0x00
T2PAxis00 0x00
T2PAxis01 0x34
T2PAxis02 0x35
T2PAxis03 0x44
T2PAxis04 0x50
27
9-257
1 Table 10.11.7.2.2-2. FRABAxis Default Values

> 0x00
FRABAxis0 0x8
FRABAxis1 0xb
2
3 Table 10.11.7.2.2-3. BucketFactor Default Values
Field Default for

NN > 0x00
BucketFactorT2PAxis00FRABAxis0 0x28
4
Field Default for

NN = 0x00
T2PAxis00 0x10
T2PAxis01 0x2b
6
Field Default for

NN = 0x00
FRABAxis0 0x0
8
9-258
Field Default for

NN = 0x00
2
3 10.11.7.2.3CommonPowerParameters Attribute
4

Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
AllocationStagger 4 ‘0101’
TxT2Pmin 8 0x0F
RPCStep 2 ‘01’
Reserved 0-7(as N/A
needed)
}
7 Length field.
10 complex value.
11 AllocationStagger T2P allocation stagger factor. The access network shall set this field
12 to the desired T2P allocation dither factor across MAC flows at an
13 access terminal and across access terminals. This field is a 4-bit
14 value in steps of 1/16 in the range of 0…15/16, inclusive. The access
15 terminal shall support all valid values specified by this field.
16 TxT2Pmin The sender shall set this field to the minimum TxT2P that the
17 receiver is always allowed to transmit, expressed as an 8-bit number
18 in units of 0.25 dB. The receiver shall support all valid values
9-259
3 controlling the power of the reverse link, as shown in Table
4 10.11.7.2.3-1. The access terminal shall support all the valid values
6 Table 10.11.7.2.3-1.Encoding of the RPCStep Field
Field value Meaning

(binary)
‘00’ 0.5 dB
‘01’ 1.0 dB
‘10’ Reserved
‘11’ Reserved
9 set these bits to ’0’. The receiver shall ignore this field.
9-260
1 10.11.7.2.4PermittedPayload Attribute
2
Field Length(bits) Default

Length 8 N/A
AttributeID 16 N/A
One or more occurrences of the following attribute value
record:
ValueID 8 N/A
PermittedPayload0_1 4 0x1
7 complex value.
8 PermittedPayload0_1
9 The sender shall set this field to the maximum packet size that the
10 receiver can transmit in the sub-frame n if the Data Channel was not
9-261
1 transmitted in sub-frame n−4. The sender shall specify this field as a

2 4-bit value as specified in Table 10.11.7.2.4-1. The receiver shall
3 support all valid values specified by this field.
13 transmitted in sub-frame n−12. The sender shall specify this field as
14 a 4-bit value as specified in Table 10.11.7.2.4-1. The receiver shall
18 receiver can transmit in the sub-frame n if the Reverse Traffic
19 Channel payload transmitted in sub-frame n−4 was 256 bits. The
20 sender shall specify this field as a 4-bit value as specified in Table
21 10.11.7.2.4-1. The receiver shall support all valid values specified by
22 this field.
29 this field.
36 this field.
9-262
7 this field.
14 this field.
21 this field.
28 this field.
35 this field.
9-263
6 this field.
13 this field.
20 this field.
27 this field.
34 this field.
9-264

4 this field.
11 this field.
12 Table 10.11.7.2.4-1. Packet Size Encoding
Packet size Value

(bits)
0 0x0
256 0x1
512 0x2
1024 0x3
2048 0x4
4096 0x5
13
9-265
1 10.11.7.2.5PilotStrength Attribute
2
Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
NumPilotStrengthAxisValues 4 0x2
NumPilotStrengthAxisValues occurrences of the following two fields:
{
PilotStrengthAxis 6 See Table
10.11.7.2.5-1
PilotStrengthPilotStrengthAxis 4 0x0
}
needed)
}
5 Length field.
8 complex value.
9 NumPilotStrengthAxisValues

11 PilotStrengthAxis field in this record. The sender shall not set this
12 field to zero.
13 PilotStrengthAxis
14 The sender shall set this field to the values that define the
15 PilotStrength axis. The sender shall specify this field as a 6-bit value
16 in units of –0.25 dB in the range 0 dB to –15.75 dB, inclusive. The
17 values specified shall be monotonically increasing. The receiver shall
19 PilotStrengthPilotStrengthAxis
9-266
1 The sender shall set this field to the scale factor used to scale the
2 T2PInflow if the filtered serving sector PilotStrength equals the
3 corresponding PilotStrengthAxis. The sender shall specify this field as
4 a 2’s complement 4-bit value in units of 1 dB. The receiver shall
8 set these bits to ‘0’. The receiver shall ignore this field.
9 Table 10.11.7.2.5-1. PilotStrengthAxis Default Values
Field Default
PilotStrengthAxis0 0x3C
PilotStrengthAxis1 0x00
10
11 10.11.7.2.6PowerParameters Attribute
12

Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2P256 8 0x0f
T2P512 8 0x1b
T2P1024 8 0x27
T2P2048 8 0x35
T2P4096 8 0x4a
15 Length field.
18 complex value.
19 T2P256 The sender shall set this field to the Data Channel power relative to
20 the Pilot Channel power when transmitting a 256-bit payload. The
21 sender shall specify this field as an 8-bit number in units of 0.25 dB.
9-267
1 The receiver shall support all valid values specified by this field in the
2 range 0xf7 to 0x24, inclusive122.
7 range 0x03 to 0x30, inclusive.
12 range 0x0f to 0x3c, inclusive.
17 range 0x1d to 0x4a, inclusive.
22 range 0x32 to 0x5f, inclusive.
23 10.11.7.2.7RequestParameters Attribute
24
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
ReqRatio 4 0x0
MaxReqInterval 4 0x0
27 Length field.
122 The range for T2PXXXX values is consistent with the range for DataOffsetNom and
DataOffsetXXXX for subtype 0 and subtype 1 Reverse Traffic Channel MAC Protocol. The range
relative to the default is [-6dB, +5.25dB]
9-268
3 complex value.
4 ReqRatio The sender shall set this field to the maximum permitted ratio of the
5 request bits to traffic bits. The sender shall specify this field as a 4-
6 bit value in units of 0.005 for a range of 0…0.075, inclusive. The
8 MaxReqInterval The sender shall set this field to the maximum time duration that the
9 access terminal shall wait to transmit Request packet once it has
10 transmitted a Request packet. The sender shall specify this field as a
11 4-bit number in units of frames and has a range of 1…15 frames,
12 inclusive. A value of 0 will disable Request packet transmission due
13 to any fixed interval. The sender shall support all valid values
15 10.11.7.2.8T2PInflowRangeNN Attribute
18
Field Length(bits) Default for NN Default for

> 0x00 NN = 0x00
Length 8 N/A N/A
ValueID 8 N/A N/A
T2PInflowmin 8 0x07 0x10
T2PInflowmax 8 0x78 0x2b
21 Length field.
26 complex value.
27 T2PInflowmin The sender shall set this field to the minimum T2P inflow that the
28 receiver is to use as input to the Subtype 2 Reverse Traffic Channel
29 MAC algorithm. The sender shall specify this field as an 8-bit value in
9-269
1 units of 0.25 dB. The receiver shall support all valid values specified
2 by this field.
3 T2PInflowmax The sender shall set this field to the maximum T2P inflow that the
4 receiver is to use as input to the Subtype 2 Reverse Traffic Channel
5 MAC algorithm. The sender shall specify this field as an 8-bit value in
6 units of 0.25 dB. The receiver shall support all valid values specified
7 by this field.
8 10.11.7.2.9T2PTransitionFunctionNN Attribute
11
Field Length(bits) Default for NN > Default for NN

0x00 = 0x00
Length 8 N/A N/A

{
ValueID 8 N/A N/A
10.11.7.2.9-1 10.11.7.2.9-4
10.11.7.2.9-2 10.11.7.2.9-6
(NumT2PAxisValues + 1) × (NumFRABAxisValues + 1) of the following two fields:
T2PUpT2PAxisFRABAxis 8 See Table See Table
10.11.7.2.9-3 10.11.7.2.9-7
T2PDnT2PAxisFRABAxis 8 See Table See Table
10.11.7.2.9-4 10.11.7.2.9-8

needed)
}
9-270
5 complex value.
6 NumT2PAxisValues The sender shall set this field to the number of values specified on
7 the T2P axis minus 1. The sender shall specify this field as an 4-bit
8 value. The receiver shall support all valid values specified by this
9 field.
10 NumFRABAxisValues The sender shall set this field to the number of values specified on
11 the FRAB axis minus 1. The sender shall specify this field as a 3-bit
13 field.
23 T2PUpT2PAxisFRABAxis
24 The sender shall set this field to the value of the function T2PUp of
25 the associated MAC flow at [T2PAxis, FRABAxis]. The sender shall set
26 the data in the following order: T2PUp( ) is specified for all the
27 FRABaxis values, then cycled through for each T2PAxis value. The
28 receiver shall use the value of this field to compute ΔT2PInflow. The
29 sender shall specify this field as an 8-bit 2’s complement in units of
30 0.25 dB. The receiver shall support all valid values specified by this
31 field.
32 T2PDnT2PAxisFRABAxis
33 The sender shall set this field to the value of the function T2PDn of
35 the data in the following order: T2PDn( ) is specified for all the
36 FRABaxis values, then cycled through for each T2PAxis value. The
37 receiver shall use the value of this field to compute ΔT2PInflow. The
38 sender shall specify this field as an 8-bit 2’s complement in units of
9-271
1 0.25 dB. The receiver shall support all valid values specified by this
2 field.
9-272

> 0x00
T2PAxis00 0x0e
T2PAxis01 0xfb
T2PAxis02 0xef
T2PAxis03 0xef

> 0x00
FRABAxis0 0x8
FRABAxis1 0xb
FRABAxis2 0xe
FRABAxis3 0x7
3 Table 10.11.7.2.9-3. T2PUpT2PAxisFRABAxis Default Values

> 0x00
T2PUpT2PAxis00FRABAxis0 0x0e
T2PUpT2PAxis00FRABAxis1 0xfb
T2PUpT2PAxis00FRABAxis2 0xef
T2PUpT2PAxis00FRABAxis3 0xef
T2PUpT2PAxis01FRABAxis1 0xe8
T2PUpT2PAxis01FRABAxis2 0xdc
T2PUpT2PAxis03FRABAxis0 0x17
4
9-273
1 Table 10.11.7.2.9-4. T2PDnT2PAxisFRABAxis Default Values

> 0x00
T2PDnT2PAxis00FRABAxis0 0xe3
T2PDnT2PAxis00FRABAxis1 0xdc
T2PDnT2PAxis00FRABAxis2 0xd0
T2PDnT2PAxis01FRABAxis1 0xdc
T2PDnT2PAxis02FRABAxis0 0x0e
T2PDnT2PAxis02FRABAxis1 0x07
T2PDnT2PAxis02FRABAxis2 0xfb
T2PDnT2PAxis03FRABAxis2 0x0b
T2PDnT2PAxis03FRABAxis3 0x0b
2

= 0x00
T2PAxis00 0x10
T2PAxis01 0x2b
4

= 0x00
FRABAxis0 0x0
6
9-274

= 0x00
T2PUpT2PAxis00FRABAxis0 0xf4
T2PUpT2PAxis01FRABAxis0 0xbc
2

= 0x00
4 10.11.7.2.10TxT2Pmax Attribute
5
Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
{
PilotStrengthAxis 6 See Table 10.11.7.2.10-1
TxT2PmaxPilotStrengthAxis 7 See Table 10.11.7.2.10-2
}
needed)
}
8 Length field.
11 complex value.
9-275

4 field to zero.
5 PilotStrengthAxis The sender shall set this field to the values that define the
7 in units of –0.25dB in the range 0 dB to –15.75 dB, inclusive. The
10 TxT2PmaxPilotStrengthAxis
11 The sender shall set this field to the maximum TxT2P that the access
12 terminal is allowed to transmit based on the filtered serving sector
13 PilotStrength specified by the corresponding PilotStrengthAxis. The
14 sender shall specify this field as a 7-bit value expressed in units of
15 0.5 dB. The access terminal shall support all valid values specified by
16 this field.
Field Default
21 Table 10.11.7.2.10-2. TxT2PmaxPilotStrengthAxis Default Values
Field Default
TxT2PmaxPilotStrengthAxis0 0x18
TxT2PmaxPilotStrengthAxis1 0x36
22
23 10.11.7.2.11MaxMACFlows Attribute
24
9-276
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
MaxNumMACFlows 8 0x04
MaxNumActiveMACFlows 8 0x04
5 complex value.
6 MaxNumMACFlows The sender shall set this field to indicate the maximum total number
7 of activated and deactivated MAC flows supported. The value shall be
8 in the range of 0x04 to 0x10, inclusive
9 MaxNumActiveMACFlows
11 active MAC flows supported. The value shall be in the range of 0x04
12 to MaxNumMACFlows, inclusive.

14
15 Subtype field for this protocol 0x0002 is reserved and cannot be used for any other Reverse
16 Traffic Channel MAC subtype.
17

the Setup State
18 10.11.9Session State Information

9-277
3 10.11.9.1LongCodeMask Parameter

7 Parameter
Field Length (bits)
ParameterType 8
Length 8
MIRTCMAC 42
MQRTCMAC 42
Reserved 4
9-278
2 10.12.19.12.1 Overview
6 transmission rules and rate control. This protocol supports intra-access terminal Quality of
7 Service (QoS) for multiple concurrent active MAC flows at the access terminal. Rate control
8 is accomplished via per active MAC flow Traffic-to-Pilot power ratio (T2P) control. The
9 Subtype 3 Reverse Traffic Channel MAC protocol provides per active MAC flow QoS control.
10 This is achieved by distributed rate selection (at the access terminal) and centralized
11 (scheduled) resource allocation (by the access network). This protocol operates with the
21 • Open State: In this state, the access terminal obeys the power control commands that it
22 receives from the access network. In this state, the access terminal may negotiate
23 different Subtype 3 Reverse Traffic Channel MAC Protocol parameters and attributes
24 per MAC flow and transmit data on the Reverse Traffic Channel.
9-279
Initial State
Rx Activate
Rx Deactivate or
timer expires
Open State
3 Each active MAC flow contributes to sector loading and its contribution is strongly
4 correlated with its average transmit T2P. An access terminal may transmit multiple active
5 MAC flows simultaneously. The Subtype 3 Reverse Traffic Channel MAC protocol uses the
6 average transmit T2P per active MAC flow as a measure of the air link resource used by
7 that MAC flow. The Subtype 3 Reverse Traffic Channel MAC protocol treats multiple active
8 MAC flows associated with a single access terminal in a manner consistent with multiple
9 active MAC flows associated with multiple access terminals, subject to access terminal
10 transmit power constraints. This protocol controls the average T2P of an active MAC flow
11 based on the requirements of that MAC flow, requirements of other concurrent active MAC
12 flows, transmit power constraints, and sector loading. The Subtype 3 Reverse Traffic
13 Channel MAC protocol allows updating Reverse Traffic Channel MAC attributes (access
14 terminal specific and MAC flow specific) using the Generic Attribute Update Protocol.
16 10.12.2.19.12.2.1 Commands
18 • Activate
19 • Deactivate

22 • LinkAcquired
9-280
1 10.12.2.39.12.2.3 Public Data

4 • ARQMode
5 • AuxiliaryPilotChannelGain
6 • AuxiliaryPilotChannelMinPayload
7 • Rate1M8Supported
8 • RRI (Payload Index and sub-packet Index)
9 • RRIChannelGain
10 • TxT2P
11 • RPCStep
12 • MIRTCMAC
13 • MQRTCMAC
14 • RAChannelGain for each pilot in the Active Set


9-281
2 10.12.5.19.12.5.1 Procedures

14 − ARQMode
15 − AuxiliaryPilotChannelGain
16 − AuxiliaryPilotChannelMinPayload
17 − Rate1M8Supported
18 − RPCStep
20 then
9-282
4
Field Length (bits)
MessageID 8
TransactionID 8
12
Field Length (bits)
MessageID 8
TransactionID 8

9-283
3 10.12.6.19.12.6.1 Procedures
4 The protocol constructs a Subtype 3 Reverse Traffic Channel MAC Layer packet out of a
6 Protocol.
7 The Subtype 3 Reverse Traffic Channel MAC Protocol supports multiple MAC Flows. MAC
9 with MAC flow NN is greater than zero, where NN is the two-digit hexadecimal flow number
10 in the range 0x00 to MaxNumMACFlows −1, inclusive. The number of active MAC Flows
11 shall not exceed the value of the MaxNumActiveMACFlows parameter of the MaxMACFlows
12 attribute.
13 10.12.6.1.19.12.6.1.1 MAC Layer Packet

14 The MAC Layer packet is the basic unit of data provided by the Subtype 3 Reverse Traffic
16 is shown in Figure 9.12.6.1.1-1. The MAC Layer packet consists of a Security Layer packet
17 followed by the MAC Layer trailer. The MAC Layer packet is transmitted in one of two
18 modes, Low Latency mode or High Capacity mode.
MAC Layer packet
Security MAC
Layer Layer
packet trailer
19
22 10.12.6.1.2.19.12.6.1.2.1 Activate
9-284
1 10.12.6.1.2.29.12.6.1.2.2 Deactivate

11 9.12.6.1.3-1.
BIT
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
13

15 ATILCM = (A31, A30, A29, …, A0)
18 A15, A6, A28, A19, A10, A1, A23, A14, A5, A27, A18, A9).
27 10.12.6.1.49.12.6.1.4 Inactive State

9-285
1 10.12.6.1.59.12.6.1.5 Setup State

8 the DRC value, DRC cover, and DSC value as specified by the Enhanced Forward Traffic
9 Channel MAC Protocol (see 9.7).
10 The access terminal shall follow procedures specified in 9.12.6.1.6.1.5 in addition to the
13 in this state.

23 State.
24 10.12.6.1.69.12.6.1.6 Open State

26 Upon entering the Open State the access terminal shall perform the following.
27 − Set FRABn = 0, where n is the current sub-frame.
28 − For each MAC flow i, set LastBucketLevelMaxi to NULL.
30 maximum payload sizes available on the Reverse Traffic Channel for different values of
31 Reverse Link transmit duration.
32
9-286
1 Table 9.12.6.1.6.1-1.Reverse Traffic Channel Rates and Payload
Payload Payload Effective Data Rate (kbps)

Size (bits) Size (bits)
Minimum Maximum Transmit Transmit Transmit Transmit
Duration Duration Duration Duration
1 sub- 2 sub- 3 sub- 4 sub-
frame frames frames frames
1 96 19.2 9.6 6.4 4.8
97 224 38.4 19.2 12.8 9.6
225 480 76.8 38.4 25.6 19.2
481 736 115.2 57.6 38.4 28.8
737 992 153.6 76.8 51.2 38.4
993 1504 230.4 115.2 76.8 57.6
1505 2016 307.2 153.6 102.4 76.8
2017 3040 460.8 230.4 153.6 115.2
3041 4064 614.4 307.2 204.8 153.6
4065 6112 921.6 460.8 307.2 230.4
6113 8160 1228.8 614.4 409.6 307.2
8161 12256 1843.2 921.6 614.4 460.8
2
9-287
Physical Data Channel Gain Relative Data Channel Gain Relative to

Layer Transmission to Pilot (dB) Pilot (dB)
Packet Mode
Size Pre-Transition Post-Transition
(bits)
− ∞ (Data Channel is not − ∞ (Data Channel is not

0 N/A
transmitted) transmitted)
128 High Capacity T2PHiCapPreTransition128 T2PHiCapPostTransition128
128 Low Latency T2PLoLatPreTransition128 T2PLoLatPostTransition128
2
3 The Subtype 3 Reverse Traffic Channel MAC Protocol supports two Transmission modes,
4 High Capacity mode and Low Latency mode. Each Transmission mode is specified per
9-288
1 active MAC flow and is characterized by a physical layer transmit duration. The physical
2 layer transmit duration is one, two, three or four sub-packets. A termination target is
3 specified for each packet size for both the Low Latency and the High Capacity transmission
4 modes. The termination target is defined as one less than the number of sub-packets that
5 an access terminal is required to transmit for the packet to be received by the access
6 network with the target packet erasure rate123. The termination target is defined by
7 LoLatTerminationTargetPS for a packet with packet size PS transmitted in Low Latency
8 mode. The termination target is defined by HiCapTerminationTargetPS for a packet with
9 packet size PS transmitted in High Capacity mode. The transmit duration defines the
10 effective date rate for a given packet size as shown in Table 9.12.6.1.6.1-1. For example, a
11 256-bit payload results in an effective data rate of 38.4kbps, 19.2kbps, 12.8kbps, and
12 9.6kbps for a transmit duration of one, two, three, or four sub-packets respectively.
13 T2PHiCapPreTransitionPS defines the T2P's used by the access terminal for transmitting
14 the first HiCapT2PTransitionPS+1 sub-packets of a Reverse Traffic Channel packet with
15 packet size PS in High Capacity Mode, where PS can take on the following values: 128, 256,
16 512, 768, 1024, 1536, 2048, 3072, 4096, 6144, and 8192, and 12288 bits.
17 T2PHiCapPostTransitionPS defines the T2P's used by the access terminal for transmitting
18 the subsequent sub-packets of a Reverse Traffic Channel packet with packet size PS in
19 High Capacity Mode.
20 T2PLoLatPreTransitionPS defines the T2P's used by the access terminal for transmitting the
21 first LoLatT2PTransitionPS+1 sub-packets of a Reverse Traffic Channel packet with packet
22 size PS in Low Latency Mode, where PS can take on the following values: 128, 256, 512,
23 768, 1024, 1536, 2048, 3072, 4096, 6144, and 8192, and 12288 bits.
24 T2PLoLatPostTransitionPS defines the T2P's used by the access terminal for transmitting
25 the subsequent sub-packets of a Reverse Traffic Channel packet with packet size PS in Low
26 Latency Mode.
27 The access network uses the RA bit (one RA bit per sector) to provide an indication of
28 loading on the each sector’s reverse link to the access terminal. The reliability of the RA
29 channel is improved by filtering the RA bit at the access terminal. A short-term filter
30 followed by a threshold detector is used at the access terminal to generate the QRAB
31 (Quick RA Bit) which indicates instantaneous sector loading. A long-term filter is used to
32 generate the FRAB (Filtered RA Bit) which indicates longer term sector loading.
34 Reverse Rate Indicator at the earliest time T, following the end of transmission of the
35 previous packet, that satisfies the following equation
39 determine the T2P allocation for each active MAC flow. Variables with suffix m indicate
40 quantities that are updated every slot and variables with suffix n indicate quantities that
123 The target packet erasure rate typically used by the physical layer is 1%
9-289
1 are updated every sub-frame. Unless otherwise stated, all filters used in this section are
2 first order IIR filters (see 13.13). PS indicates the physical layer packet size and takes on
3 values of 128, 256, 512, 768, 1024, 1536, 2048, 3072, 4,096, 6144, 8192, or 12288 bits
4 and subscript N indicates the sub-packet identifier of a physical layer packet and takes on
5 values zero, one, two, or three.
6 The description in this section uses the following variables and functions:
7 • AllocationStagger: T2P allocation time stagger.
8 • AuxiliaryPilotChannelGain: Auxiliary Pilot Channel Gain.
9 • BucketLeveli,n: Bucket Level (or accumulated T2P resource) at sub-frame n for MAC
10 flow i.
11 • BucketFactori( ): Indicates by what factor (linear) the T2POutflowi,n can exceed
12 T2PInflowi,n for MAC flow i.
13 • BucketLevelMaxi: Max T2P resource that can be accumulated (bucket size) for MAC
14 flow i.
15 • BucketLevelSati,n: Saturation Level for BucketLevel i,n.
16 • BurstDurationFactori: Max duration (in sub-frames) for which MAC flow i can sustain a
17 peak rate based on its T2P allocation.
18 • di,n: Number of octets allocated to MAC flow i for a Reverse Traffic Channel
19 transmission during sub-frame n.
20 • DeltaT2P: The TxT2P adjust value. If this value is made public by the Route Update
21 Protocol, then DeltaT2P is set to the public data value corresponding to the serving
22 sector pilot. If the Route Update protocol does not define the DeltaT2P as public data,
23 then the DeltaT2P value is set to zero.
24 • FRABn: Effective Filtered RAB value at sub-frame n from all sectors in the access
25 terminal’s active set.
26 • FRABn,s: Indicates the Filtered RAB value from sector s at sub-frame n.
27 • F: Set of all active MAC flows with non-empty queues.

28 • FLL: Set of all active MAC flows with non-empty queues associated with the Low
29 Latency mode.
30 • FRABlow: FRAB threshold. FRABn values below FRABlow indicate a sector with a
31 lightly loaded reverse link.
32 • HiCapT2PTransitionPS: Number of sub-packets (excluding the first) from the start of
33 the packet for which the pre-transition T2P values are used for High Capacity mode
34 Reverse Traffic Channel transmissions with packet size PS.
35 • LastBucketLevelMaxi: The last recorded value of BucketLevelMaxi,n.
9-290
1 • LoLatT2PTransitionPS: Number of sub-packets (excluding the first) from the start of the
2 packet for which the pre-transition T2P values are used for Low Latency mode Reverse
3 Traffic Channel transmissions with packet size PS.
4 • MergeThreshold: Merge Threshold (in octets) for Reverse Traffic Channel packets.
5 • MergeThresholdi: Merge Threshold (in octets) for MAC flow i if transmitted in High
6 Capacity Mode.
7 • PacketSizePS: Physical Layer packet size, in octets, of packet size PS transmitted in
8 sub-frame n.
9 • PktTxT2Pn,N : Transmitted T2P during sub-packet N of a Reverse Traffic Channel
10 packet, whose first sub-packet is transmitted in sub-frame n and 0 ≤ N ≤ 3.
11 • PayloadThresh: Minimum packet size of a Reverse Traffic Channel packet transmitted
12 in LoLat mode that does not contain any MAC flows with LoLat transmission mode
13 when MaxNumSubpacketsI=3 in transmit interlace I.
14 • PermittedPayloadPS_k: Maximum Physical Layer packet size that an access terminal is
15 permitted to transmit in sub-frame n if the Physical Layer packet size transmitted in
16 sub-frame n − k was PS bits.
17 • PilotStrengthm,s: Filtered PilotStrength (filter time constant of PilotStrengthFilterTC) of
18 a sector s in the access terminal’s active set.
19 • PilotStrengthn,s: Filtered PilotStrength sampled at the start of sub-frame n for sector s
20 in the access terminal’s active set.
21 • PilotStrength( ): Function that provides the scale factor for scaling T2PInflowi,n based
22 on the PilotStrength of the forward link serving sector.
23 • PilotStrengthQRABThresholdDRCLock: Minimum PilotStrength value required for
24 QRAB (from any sector other than the Forward Link serving sector) to be included in
25 the QRABpsn computation when sector DRC is in lock.
26 • PilotStrengthQRABThresholdDRCUnlock: Minimum PilotStrength value required for

27 QRAB (from any sector other than the Forward Link serving sector) to be included in
28 the QRABpsn computation when sector DRC is not in lock.
29 • PotentialT2POutflowi,LL: Potential Outflow from the bucket for MAC flow i due to a Low
30 Latency mode transmission.
31 • PotentialT2POutflowi,HC: Potential Outflow from the bucket for MAC flow i due to a
32 High Capacity mode transmission.
33 • Qi,n: Queue length (in octets) of MAC flow i at sub-frame n.
34 • QOutflowi,HC: Queue outflow (in octets) for MAC flow i with TMi == HiCap.
35 • QRABi,n: Effective Quick RAB value for MAC flow i at sub-frame n.
36 • QRABn: Effective QRAB at sub-frame n.
37 • QRABn,s: Indicates the Quick RAB value from sector s at sub-frame n.
9-291
1 • QRABpsn: Indicates the effective Quick RAB value generated at sub-frame n based on
2 PilotStrengthn,s of the sectors s in its active set.
3 • QRABSelecti: Indicates which QRAB value, QRABpsn or QRABn that the access
4 terminal uses as an indication of short-term sector loading for MAC flow i.
5 • RRIChannelGainn: RRI Channel Gain in sub-frame n.
6 • RRIChannelGainPreTransitionM: RRI Channel Gain prior to the T2P transition if the

7 Reverse Traffic Channel transmission uses a T2P transition value of M+1 sub-frames.
8 • RRIChannelGainPostTransitionM: RRI Channel Gain following the T2P transition if the
10 • rn: Real-valued uniformly distributed random number in the range [−1,+1].
11 • SlotFRABm,s: Filtered value (with filter time constant FRABFilterTC) at slot m of the soft
12 RA bit SoftRABm,s provided by the Physical Layer Protocol.
13 • SlotQRABm,s: Hard-limited value of SoftQRABm,s
14 • SoftQRABm,s: Filtered value (with filter time constant QRABFilterTC) at slot m of the
15 soft RA bit SoftRABm,s provided by the Physical Layer Protocol.
16 • SoftRABm,s: Soft RA bit provided by the Physical Layer Protocol at slot m for sector s.
17 • SumPayloadn: Sum of the octets di,n of all active MAC flows i included in a packet
18 transmitted in sub-frame n.
19 • SumQOutflow: Sum of the queue outflows (in octets) for all MAC flows with non-empty
20 queues and TMi == HiCap.
21 • T2PInflowmini: Minimum value of the permitted T2PInflow for MAC flow i.
22 • T2PInflowmaxi: Maximum value of the permitted T2PInflow for MAC flow i.
23 • T2PConversionFactorLL: Conversion Factor from T2P to MACPacketSize for Reverse

24 Traffic Channel transmissions that are transmitted using the Low Latency Mode.
25 • T2PConversionFactorHC: Conversion Factor from T2P to MACPacketSize for Reverse
26 Traffic Channel transmissions that are transmitted using the High Capacity Mode.
27 • T2PFilterTCi: Filter time constant used to compute the average T2P for MAC Flow i.
28 • T2PNoTxFilterTC: Filter time constant used to compute the average T2P when the
29 access terminal is in Open state but not transmitting on the Reverse Traffic Channel
30 due to not receiving the corresponding Forward Channel.
31 • TMi: Transmission Mode for MAC flow i. Transmission Mode for a Reverse Traffic
32 Channel packet is either LoLat (Low Latency Mode) or HiCap (High Capacity Mode).
33 • TT2PHoldi,n: Indicates number of sub-frames following sub-frame n for which the T2P
35 for MAC flow i.
9-292
1 • T2PInflowi,n: Denotes the average T2P resource added to the bucket for MAC flow i at
2 sub-frame n.
3 • T2POutflowi,n: Denotes the average T2P resource utilized (and subtracted) from the
4 bucket for MAC flow i at sub-frame n.
5 • TxT2Pmacn: MAC layer transmit T2P during sub-frame n
6 • TxT2Pmax(PilotStrengthn,s): Maximum TxT2P for that an access terminal is permitted

7 to transmit as a function of PilotStrengthn,s where s is the forward link serving sector.
8 • TxT2Pmin: TxT2P that an access terminal is permitted to transmit at any time.

9 • TxT2Pn: Transmitted T2P during sub-frame n.
10 • TxT2PLoLatPSN =
11 − T2PLoLatPreTransitionPS if N ≤ LoLatT2PTransitionPS
12 − T2PLoLatPostTransitionPS if N > LoLatT2PTransitionPS
13 • TxT2PHiCapPSN =
14 − T2PHiCapPreTransitionPS if N ≤ HiCapT2PTransitionPS
15 − T2PHiCapPostTransitionPS if N > HiCapT2PTransitionPS
16 • TxT2PHiCapNominalPS: Nominal TxT2P for a packet with packet size PS transmitted in
17 High Capacity mode.
18 • TxT2PLoLatNominalPS: Nominal TxT2P for a packet with packet size PS transmitted in
19 Low Latency mode.
20 • ΔT2PInflowi,n: Increase or decrease in T2PInflowi,n at sub-frame n for MAC flow i.
21 • T2PUpi( ): Two-dimensional piecewise linear function for computing increase in

22 T2PInflowi,n based on current T2PInflow and current FRAB for active MAC flow i.
23 • T2PDni( ): Two-dimensional piecewise linear function for computing the decrease in

24 T2PInflow based on current T2PInflow and current FRAB for MAC flow i.
25 The access terminal shall determine T2PUpi(T2PInflowi,n, FRABn) and T2PDni(T2PInflowi,n,
26 FRABn) by bilinear interpolation on the T2P-FRAB grid using the equations described in
27 13.12.
28 The access terminal shall determine PilotStrength(PilotStrengthn,s) by linear interpolation
29 on the PilotStrength axis using the method described in 13.11.
30 The access terminal shall determine BucketFactori,n by bilinear interpolation on the T2P-
31 FRAB grid using the equations described in 13.12.
32 The access terminal shall determine TxT2Pmaxn(PilotStrengthn,s) by linear interpolation on
33 the PilotStrength axis using the method described in 13.11.
9-293
1 If the access terminal is receiving the corresponding Forward Channel in sub-frame n, and
2 no slot of sub-frame n overlaps with a Reverse Link Silence Interval, then the access
3 terminal shall perform the following operations at the start of every slot m of sub-frame n
4 for each sector s in its active set:
5 1. Initialization due to active set update: Upon inclusion of a new sector s into the
6 access terminal’s active set, the access terminal shall perform the following steps:
7 − Set PilotStrengthm,s to the corresponding PilotStrength, which is public data of
8 the Route Update Protocol.
9 − Set SoftQRABm,s = 0.
10 − Set SlotFRABm,s = FRABn−1.
11 2. Update PilotStrengthm,s: The access terminal shall update the PilotStrength (in the
14 3. Update SlotQRABm,s: The access terminal shall generate SlotQRABm,s by filtering
15 (IIR filter with filter time constant QRABFilterTC) the soft RA bit from sector s in
16 slot m to generate SoftQRABm,s, and then hard-limiting SoftQRABm,s to generate
17 SlotQRABm,s. The hard-limiter maps positive input values to +1 and negative or
18 zero input values to −1.
19 4. Update SlotFRABm,s: The access terminal shall generate SlotFRABm,s by filtering
20 (IIR filter with filter time constant FRABFilterTC) the soft RA bit (SoftRABm,s).
21 If the access terminal is receiving the Forward Channel and any slot of sub-frame n
22 overlaps with a Reverse Link Silence Interval, the access terminal shall perform the
23 following operations at the start of every slot of sub-frame n for each sector s in its active
24 set:
25 1. Update PilotStrengthm,s: The access terminal shall update the PilotStrength (in the
28 2. Update SlotQRABm,s: Set SoftQRABm,s = 0, and and SlotQRABm,s = −1.
29 3. Update SlotFRABm,s: Set SlotFRABm,s = max(0, SlotFRABm-1,s).
30 If the access terminal is not receiving the Forward Channel, the access terminal shall
33 1. Update PilotStrengthm,s: This value does not change as part of this operation.
34 2. Update SlotQRABm,s: Set SoftQRABm,s = 0 and SlotQRABm,s = −1.
35 3. Update SlotFRABm,s: This value does not change as part of this operation.
37 to determine allocation for that sub-frame:
38 1. Update PilotStrengthn,s
9-294
1 − The access terminal shall sample PilotStrengthm,s for each sector s in the
2 access terminal’s active set at sub-frame n to generate PilotStrengthn,s.
3 2. Update QRABn
4 − The access terminal shall sample SlotQRABm,s from each sector s in the
5 access terminal’s active set at sub-frame n to generate QRABn,s.
6 − The access terminal shall determine QRABn from QRABn,s at sub-frame n

8 + The access terminal shall set QRABn = +1 (Loaded) if QRABn,s == +1 (Loaded)
9 for any sector s in the access terminal’s active set.
10 + The access terminal shall set QRABn = −1 (UnLoaded) if QRABn,s == −1
11 (UnLoaded) for every sector s in the access terminal’s active set.
12 3. Update QRABpsn
13 − The access terminal shall determine QRABpsn from QRABn,s at sub-frame n

15 + The access terminal shall set QRABpsn = +1 (Loaded) if QRABn,s == +1 for a
16 sector s in the access terminal’s active set, which satisfies one or more of the
18 − Sector s is the forward link serving sector for the access terminal
19 − The DRCLock bit from a cell associated with sector s is ‘0’ (Out-of-lock) and
22 − The DRCLock bit from a cell associated with sector s is ‘1’ (In-lock) and
25 + The access terminal shall set QRABpsn = −1 (UnLoaded) if none of the
27 4. Update FRABn
28 − The access terminal shall sample SlotFRABm,s at sub-frame n to generate

29 FRABn,s. The access terminal shall set FRABn to the maximum real-numbered
30 value of FRABn,s received over all sectors s in the access terminal’s active set.
31 FRABn is thus within the range [− 1(Unloaded), + 1(Loaded)].
32 5. Initialization for each active MAC flow i

33 − For each active MAC flow i the access terminal shall perform the following
34 steps:
35 + If LastBucketLevelMaxi is NULL and BucketLevelMaxi is not NULL then the
37 − Set BucketLeveli,n = 0.
9-295
1 − Set T2PInflowi,n−1 = 10^(T2PInflowmini/10).
2 − Set TT2PHoldi,n−1 = 0.
3 − Set T2POutflow i,n−1 = 0.
4 − Set BucketLevelSati,n = 10^(BucketLevelMaxi/10).
5 + Set LastBucketLevelMaxi = BucketLevelMaxi.
6 6. Update buckets with inflows for each active MAC flow i.

7 − Determine ΔT2PInflowi,n
8 + The access terminal shall set QRABi,n = +1 (Loaded) if either of the following
10 − QRABSelecti == +1 for MAC flow i and QRABpsn == +1 at sub-frame n
11 − QRABSelecti == 0 for MAC flow i and QRABn == +1 at sub-frame n
12 + If none of the conditions immediately above are satisfied, the access terminal
13 shall set QRABi,n = −1 (Unloaded)
14 + If TT2PHoldi,n−1 == 0 and QRABi,n == +1 the access terminal shall compute

15 ΔT2PInflowi,n using the following equation:
16 ΔT2PInflowi,n= −1 × 10^(T2PDni(10 × log10(T2PInflowi,n−1) +
18 where sector s is the forward link serving sector for the access terminal.
19 + If TT2PHoldi,n−1 == 0 and QRABi,n == −1 and BucketLeveli,n <
20 BucketLevelSati,n, then the access terminal shall compute ΔT2PInflowi,n
22 ΔT2PInflowi,n= +1 × 10^(T2PUpi(10 × log10(T2PInflowi,n−1) +
25 + If TT2PHoldi,n−1 == 0 and QRABi,n == −1 and BucketLeveli,n ≥ BucketLevelSat
26 i,n, then the access terminal shall set ΔT2PInflowi,n using the following
27 equation:
28 ΔT2PInflowi,n = 0
29 + The access terminal shall set ΔT2PInflowi,n = 0 if the access terminal is not
30 receiving the corresponding Forward Channel or sub-frame n overlaps with a
31 Reverse Link Silence Interval.
32 − Update T2P Inflows
33 + If TT2PHoldi,n−1 == 0, then the access terminal shall update T2PInflowi,n,
34 using the following equations if receiving the corresponding Forward Channel
35 during sub-frame n.
9-296
1 T2PInflowi,n = (1 − (1/T2PFilterTCi)) × T2PInflowi,n−1 + (1/T2PFilterTCi) ×

2 T2POutflowi,n−1 + ΔT2PInflowi,n
3 T2PInflowi,n = max( T2PInflowi,n , 10^(T2PInflowmini / 10))
4 T2PInflowi,n = min( T2PInflowi,n , 10^(T2PInflowmaxi / 10))
5 + If TT2PHoldi,n−1 == 0, then the access terminal shall update T2PInflowi,n if not

6 receiving the corresponding Forward Channel during sub-frame n using the
7 following equations:
8 T2PInflowi,n = (1 − (1/T2PNoTxFilterTC)) × T2PInflowi,n−1
9 T2PInflowi,n = max(T2PInflowi,n, 10^(T2PInflowmini / 10))
10 T2PInflowi,n = min(T2PInflowi,n, 10^(T2PInflowmaxi / 10))
11 + If TT2PHoldi,n−1 > 0, then the access terminal shall maintain the inflow
12 T2PInflowi,n as the inflow in the previous sub-frame T2PInflowi,n−1.
13 + If TT2PHoldi,n−1 > 0, the access terminal shall decrement the value of

14 TT2PHold by 1 sub-frame using the following equation:
15 TT2PHoldi,n = TT2PHoldi,n−1 −1
16 7. Determine sub-packet transmission for sub-frame n

17 − If the access terminal transmitted the first, second or third sub-packet of a
18 packet in sub-frame n−3, and the access terminal did not receive a positive
19 acknowledgment from the access network for the sub-packet transmitted in
20 sub-frame n−3, and the sub-packet index of the next (second, third, or fourth)
21 sub-packet is not greater than MaxNumSubPacketsI, where I is the interlace
22 offset of sub-frame n, then the access terminal shall transmit the next (second,
23 third or fourth) sub-packet of the packet in sub-frame n. Otherwise, the access
24 terminal shall not transmit the next sub-packet of the packet in sub-frame n.
25 The reverse-link interlace offset I for a sub-packet starting in slot T is specified
26 as I = (T - FrameOffset)/4 mod 3, where T is the CDMA System Time in slots
27 and 0 ≤ I ≤ 2
28 − If the access terminal transmits a new packet in sub-frame n, it shall
29 determine the packet size, transmission mode and contents of the new packet
30 in accordance with 9.12.6.1.6.1.1.
31 − If the access terminal transmits a new packet in sub-frame n with packet size PS
32 in High Capacity mode, the access terminal shall set the variables PktTxT2Pn,0,
33 PktTxT2Pn,1, PktTxT2Pn,2, and PktTxT2Pn,3 in accordance with the following
34 equations:
35 PktTxT2Pn,N = T2PHiCapPreTransitionPS if N ≤ HiCapT2PTransitionPS
36 PktTxT2Pn,N = T2PHiCapPostTransitionPS if N > HiCapT2PTransitionPS
9-297
1 − If the access terminal transmits a new packet in sub-frame n with packet size PS
2 in Low Latency mode, the access terminal shall set the variables PktTxT2Pn,0,
3 PktTxT2Pn,1, PktTxT2Pn,2, and PktTxT2Pn,3 in accordance with the following
4 equations:
5 PktTxT2Pn,N = T2PLoLatPreTransitionPS if N ≤ LoLatT2PTransitionPS
6 PktTxT2Pn,N = T2PLoLatPostTransitionPS if N > LoLatT2PTransitionPS
7 8. Determine TxT2Pmacn and TxT2Pn TxT2Pn
8 − If the access terminal transmits sub-packet N of a Reverse Traffic Channel

9 packet in sub-frame n, the access terminal shall set TxT2Pmacn and TxT2Pn
10 during sub-frame n using the following equations124:
11 TxT2Pmacn = 10^(PktTxT2Pn − 3 × N, N / 10)
12 TxT2Pn = 10^((PktTxT2Pn − 3 × N, N+ DeltaT2P) / 10)
13 9. Update T2P outflows for each active MAC flow i

14 − If the access terminal transmits a sub-packet of a Reverse Traffic Channel
15 packet in sub-frame n and physical layer packet size PS is greater than or
16 equal to AuxiliaryPilotChannelMinPayload, the bucket outflows shall be
18 T2POutflowi,n = ((di,n / SumPayloadn) × TxT2Pn) × (1 +
19 10^(AuxiliaryPilotChannelGain / 10))
20 where di,n is the number of octets from an active MAC flow i contained in the
21 payload and SumPayloadn is the sum of di,n over all active MAC flows i.

23 packet in sub-frame n and physical layer packet size PS is less than
24 AuxiliaryPilotChannelMinPayload, the bucket outflows shall be specified by the
26 T2POutflowi,n = (di,n / SumPayloadn) × TxT2Pn
27 where di,n is the number of octets from an active MAC flow i contained in the
28 payload and SumPayloadn is the sum of di,n over all active MAC flows i.
29 − If the access terminal does not transmit a sub-packet of a Reverse Traffic

30 Channel packet in sub-frame n, the bucket outflows shall be specified by the
32 T2POutflowi,n = 0
33 10. Update Bucket Level for each active MAC flow i
124 n − 3 × N refers to the first sub-frame of the packet that is currently being transmitted in sub-
frame n.
9-298
1 − The access terminal shall determine BucketLevelSati,n+1 for each active MAC flow
2 i using the following equation:
3 BucketLevelSati,n+1 = min(BurstDurationFactori × BucketFactori(10 ×
4 log10(T2PInflowi,n), FRABn) × T2PInflowi,n, 10^( BucketLevelMaxi / 10))
5 − If the access terminal is not receiving the corresponding Forward Channel

6 during sub-frame n or any slot of sub-frame n overlaps with the Reverse Link
7 Silence Interval, then the access terminal shall set BucketLeveli,n+1 = 0.
8 − If the access terminal is receiving the corresponding Forward Channel during

12 BucketLeveli,n+1 = min(BucketLeveli,n + T2PInflowi,n – T2POutflowi,n ,
13 BucketLevelSat i,n+1)
14 11. RRIChannelGain computation

15 − The access terminal shall set the RRI Channel Gain126 for sub-packet N ( 0 ≤ N
16 ≤ 3) of a Reverse Traffic Channel packet transmitted in sub-frame n, using the
18 RRIChannelGainn = RRIChannelGainPreTransitionM, if N ≤ M
19 RRIChannelGainn = RRIChannelGainPostTransitionM, if N > M
20 If transmitting the packet in Low Latency Mode, M is equal to the T2PTransition

21 value LoLatT2PTransitionPS. Otherwise, M is equal to the T2PTransition value
22 HiCapT2PTransitionPS.
125 Note that BucketLevel

i,n+1 is allowed to take on a negative value.
126 The mapping between the T2P transition value and the RRI Channel Gain is shown in
the table below.
T2PTransitionValue and RRIChannelGain mapping
T2PTransitionValue sub-packet N
M 0 1 2 3
0 PreTransition0 PostTransition0 PostTransition0 PostTransition0
1 PreTransition1 PreTransition1 PostTransition1 PostTransition1
2 PreTransition2 PreTransition2 PreTransition2 PostTransition2
3 PreTransition3 PreTransition3 PreTransition3 PreTransition3
9-299
1 − The access terminal shall set the RRI Channel Gain in sub-frame n using the
2 following equation if the access terminal does not transmit any sub-packet in
3 sub-frame n
4 RRIChannelGainn = RRIChannelGainPreTransition3
5 12. When the access terminal transmits a security layer packet, the access terminal
10 10.12.6.1.6.1.19.12.6.1.6.1.1 Packet size and Transmission Mode Selection Requirements

11
12 10.12.6.1.6.1.1.19.12.6.1.6.1.1.1 Procedures
13 1. If PS < AuxiliaryPilotChannelMinPayload the access terminal shall determine

14 TxT2PHiCapNominalPS using the following equation:
15 TxT2PHiCapNominalPS=maxN(10 × log10(10^(TxT2PHiCapPSN/10)))
16 where the max is taken over the sub-packet indices 0 ≤ N ≤

17 HiCapTerminationTargetPS for each packet size PS.
18 2. If PS ≥ AuxiliaryPilotChannelMinPayload the access terminal shall determine
20 TxT2PHiCapNominalPS = maxN(10 × log10(10^(TxT2PHiCapPSN/10) × (1 +

21 10^(AuxiliaryPilotChannelGain/10))))
25 TxT2PLoLatNominalPS using the following equation:
26 TxT2PLoLatNominalPS, = maxN(10 × log10(10^(TxT2PLoLatPSN/10)))

28 LoLatTerminationTargetPS for each packet size PS.
31 TxT2PLoLatNominalPS = maxN(10 × log10(10^(TxT2PLoLatPSN/10) × (1 +

35 5. The access terminal shall set PotentialT2POutflowi,HC for each active MAC flow i
9-300
1 PotentialT2POutflowi,HC = max (0, min((1 + AllocationStagger × rn) × (BucketLeveli,n

2 / 4 + T2PInflowi,n) , BucketFactori(10 × log10(T2PInflowi,n), FRABn) × T2PInflowi,n))
3 6. The access terminal shall set PotentialT2POutflowi,LL for each active MAC flow i
5 PotentialT2POutflowi,LL = max (0, min((1 + AllocationStagger × rn) × (BucketLeveli,n
6 / 2 + T2PInflowi,n) , BucketFactori(10 × log10(T2PInflowi,n), FRABn) × T2PInflowi,n))
7 7. The access terminal shall determine T2PConversionFactorHC by maximizing the

8 T2PConversionFactor associated with the High Capacity mode over all permitted
9 Physical Layer packet sizes, using the following equation:
10 T2PConversionFactorHC = maxPS(PacketSizePS / 10^(TxT2PHiCapNominalPS /10))
11 where PacketSizePS is in octets.

12 8. The access terminal shall determine T2PConversionFactorLL by maximizing the
13 T2PConversionFactor associated with the Low Latency mode over all permitted
14 packet sizes, using the following equation:
15 T2PConversionFactorLL = maxPS(PacketSizePS / 10^(TxT2PLoLatNominalPS /10))
16 where PacketSizePS is in octets.

17 9. The access terminal shall determine QOutflowi,HC for each active MAC flow i by
19 QOutflowi,HC = min(Qi,n, PotentialT2POutflowi,HC × T2PConversionFactorHC)
20 10. The access terminal shall construct the set F to be the set of all active MAC flows
22 11. The access terminal shall determine SumQOutflow by summing QOutflowi,HC over
23 all active MAC flows i from the set F with TMi == HiCap.
24 12. The access terminal shall construct the set FLL using the following rules:
25 − If the transmission mode TMi of any active MAC flow i with non-empty queue
26 (i.e., Qi,n > 0) at sub-frame n is LoLat or MaxNumSubPacketsI < 3 for the
27 interlace of sub-frame n, then set TMmin = LoLat. Otherwise set TMmin =
28 HiCap.
29 − The set FLL shall be equal to the set F if TMmin == HiCap, and the packet size
30 for transmission at sub-frame n is greater than or equal to PayloadThresh.
31 − The set FLL shall be the empty set if TMmin == HiCap, and the packet size for
32 transmission at sub-frame n is less than PayloadThresh.
33 − The set FLL shall be equal to the set F if TMmin == LoLat, and one or more of
34 the following conditions are satisfied:
35 + FRABn < FRABlow
36 + SumQOutflow ≥ MergeThreshold
9-301
1 − If TMmin == LoLat, FRABn ≥ FRABlow, and SumQOutflow < MergeThreshold,

2 then the set FLL shall consist of all active MAC flows i from the set F that
3 satisfy one or more of the following conditions:
4 + TMi == LoLat
5 + QOutflowi,HC ≥ MergeThresholdi
7 10.12.6.1.6.1.1.29.12.6.1.6.1.1.2 Requirements
8 1. If the access terminal starts transmission of a new packet in sub-frame n with

9 packet size PS in High Capacity mode with di,n octets from each active MAC flow i,
10 the access terminal shall ensure that all of the following conditions are satisfied:
11 − Condition 1:
13 where PSk is the Physical Layer packet size transmitted in sub-frame n - k
14 − Condition 2:
15 10^(TxT2PHiCapNominalPS/10) ≤ max(10^(TxT2Pmin / 10),
16 ∑i∈F(PotentialT2POutflowi,HC))
17 − Condition 3:
18 If PS < AuxiliaryPilotChannelMinPayload, max(10^(T2PHiCapPreTransitionPS / 10),
19 10^(T2PHiCapPostTransitionPS / 10)) ≤ 10^(T2Pmax(PilotStrengthn,s) / 10)
20 If PS ≥ AuxiliaryPilotChannelMinPayload, (1 + 10^(AuxiliaryPilotChannelGain/10)) ×
21 max(10^(T2PHiCapPreTransitionPS / 10), 10^(T2PHiCapPostTransitionPS / 10)) ≤
22 10^(TxT2Pmax(PilotStrengthn,s) / 10)
24 − Condition 4: No packet with lower TxT2PHiCapNominalPS is able to carry a
25 payload of size as specified by the following equation:
26 ∑ i∈F min(di,n , T2PConversionFactorHC × PotentialT2POutflowi,HC)
27 − Condition 5:
28 HiCapTerminationTargetPS ≤ MaxNumSubPacketsI
29 where I is the reverse-link interlace offset of sub-frame n.
30 − Condition 6: Packet size PS can be accommodated by the available transmit
31 power.
32 2. If the access terminal starts transmission of a new packet in sub-frame n with
33 packet size PS in Low Latency mode with di,n octets from each active MAC flow i,
34 then the access terminal shall ensure that all of the following conditions are
35 satisfied:
9-302
1 − Condition 1:
3 where PSk is the Physical Layer packet size transmitted in sub-frame n - k
4 − Condition 2:
5 10^(TxT2PLoLatNominalPS/10) ≤ max( 10^( TxT2Pmin / 10 ), ∑i∈FLL (
6 PotentialT2POutflowi,LL ) )
7 − Condition 3:
8 If PS < AuxiliaryPilotChannelMinPayload, max(10^(T2PLoLatPreTransitionPS / 10),
9 10^(T2PLoLatPostTransitionPS / 10) ) ≤ 10^(TxT2Pmax(PilotStrengthn,s) / 10)
10 If PS ≥ AuxiliaryPilotChannelMinPayload, (1 + 10^(AuxiliaryPilotChannelGain/10)) ×
11 max(10^(T2PLoLatPreTransitionPS / 10), 10^(T2PLoLatPostTransitionPS / 10)) ≤
12 10^(TxT2Pmax(PilotStrengthn,s) / 10)
14 − Condition 4: No packet with lower TxT2PLoLatNominalPS is able to carry a
16 ∑ i∈FLL min( di,n , T2PConversionFactorLL × PotentialT2POutflowi,LL )
17 − Condition 5:
18 LoLatTerminationTargetPS ≤ MaxNumSubPacketsI
19 where I is the reverse-link interlace offset of sub-frame n.
20 − Condition 6: Packet size PS can be accommodated by the available transmit
21 power.
22 10.12.6.1.6.1.29.12.6.1.6.1.2 Request message

28 1. ReqRatio is not equal to 0 and the access terminal has transmitted (1 / ReqRatio –
29 1) × RequestPktSize bits of data on the traffic channel since the last Request packet
31 message.
32 2. MaxReqInterval is not equal to zero and MaxReqInterval frames have elapsed since
33 the last transmission of a Request packet.
34 10.12.6.1.6.1.39.12.6.1.6.1.3 Grant message

35 If the access terminal received a Grant message the access terminal shall update the
36 following parameters for each MAC flow i for which the Grant message was received.
9-303
1 • T2PInflowi,n with 10x/10, where x is the value of T2PInflow in units of dB.
2 • BucketLeveli,n with 10x/10, where x is the value of BucketLevel in units of dB.
3 • TT2PHoldi,n with 4 × x, where x is the value of TT2PHold in units of frames.
4 10.12.6.1.6.1.49.12.6.1.6.1.4 Power Control


11 The access terminal should not start transmission of a packet if a sub-frame within its
12 termination target overlaps with a Reverse Link Silence Interval. The Reverse Link Silence
13 Interval is defined as the time interval of duration ReverseLinkSilenceDuration frames that
14 starts at times T and it satisfies the following equation:

20 The access network uses the RA bit to reflect the reverse link sector loading. The access
21 network should transmit the Reverse Activity Channel with a gain equal to or greater than
22 that specified by RAChannelGain. In the following requirements, PS takes on the following
23 values: 128, 256, 512, 768, 1024, 1536, 2048, 3072, 4096, 6144, 8192, and 12288. Each
24 value of PS represents a physical layer packet size, expressed in bits.
25 The access network shall set the value of T2PHiCapPreTransitionPS127 to be less than or
26 equal to the value of T2PLoLatPreTransitionPS128.
27 The access network shall set the value of LoLatTerminationTargetPS to be less than or
28 equal to the value of HiCapTerminationTargetPS.
127 The access network typically sets the values of T2PHiCapPreTransitionPS and
T2PHiCapPostTransitionPS such that T2PHiCapPreTransitionPS is greater than
T2PHiCapPostTransitionPS.
128 The access network typically sets the values of T2PLoLatPreTransitionPS and
T2PLoLatPostTransitionPS such that T2PLoLatPreTransitionPS is greater than
T2PLoLatPostTransitionPS.
9-304
1 The access network should set the values of LoLatTerminationTargetPS such that the
2 packet transmitted by the access terminal with packet size PS in the Low Latency mode is
3 received by the access network within LoLatTerminationTargetPS sub-frames with a failure
4 rate not exceeding the target packet erasure rate.
5 The access network should set the values of HiCapTerminationTargetPS such that the
6 packet transmitted by the access terminal with packet size PS in the High Capacity mode is
7 received by the access network within HiCapTerminationTargetPS sub-frames with a failure
9 10.12.6.1.6.2.19.12.6.1.6.2.1 Grant Message

10 The access network may transmit Grant messages at any time. The Grant messages may
11 be transmitted autonomously or in response to Request messages received from access
12 terminals. The Grant message is transmitted by the access network to the access terminal
13 for which the access network is the forward link serving sector. The timing and content of
14 the Grant message is determined by the access network. The Grant message contains
15 “grants” for one or more MAC flows belonging to one access terminal. A per MAC flow
16 resource allocation contains the following:
17 − T2PInflow
18 − BucketLevel
19 − TT2PHold

23
Field Length (bits)
TransmissionMode 1

28 TransmissionMode If the MAC Layer packet is transmitted in the Low Latency Mode,
29 then the access terminal shall set this field to ‘1’. Otherwise, the
9-305
1 10.12.6.2.29.12.6.2.2 RTCAck
5
Field Length (bits)

MessageID 8

7
8 10.12.6.2.39.12.6.2.3 Request
12
Field Length (bits)

MessageID 8
MaxSupportableTxT2P 8
NumMACFlows 5
NumMACFlows occurrences of the following two
fields:
MACFlowID 4
QueueLength 4
Reserved 3
14 MaxSupportableTxT2P
15 The access terminal shall set this field to its maximum supportable
16 Transmit Traffic-to-Pilot power ratio. The access terminal shall
17 specify this field as an 8-bit value with units of 0.25 dB.
19 for which a request is transmitted.
9-306
6 terminal shall specify this field as a 4-bit number as specified in
7 Table 9.12.6.2.3-1.
QueueLength, QueueLength (octets)

q
QL
0 0 ≤ QL < 32
1 32 ≤ QL < 64
2 64 ≤ QL < 96
3 96 ≤ QL < 128
4 128 ≤ QL < 192
5 192 ≤ QL < 256
6 256 ≤ QL < 384
7 384 ≤ QL < 512
8 512 ≤ QL < 768
9 768 ≤ QL < 1024
10 1024 ≤ QL < 1536
11 1536 ≤ QL < 2048
12 2048 ≤ QL < 4096
13 4096 ≤ QL < 8192
14 8192 ≤ QL < 16384
15 QL ≥ 16384
11
12 10.12.6.2.49.12.6.2.4 Grant
14 following parameters for one or more of the active MAC flows at the access terminal:
9-307
1 • T2PInflow
2 • BucketLevel
3 • TT2PHold
4
Field Length (bits)

MessageID 8
NumMACFlows 4
(NumMACflows occurrences + 1) of the following fields:
MACFlowID 4
T2PInflow 8
BucketLevel 8
TT2PHold 6
Reserved 0-7 (as

needed)
6 NumMACFlows The access network shall set this field to one less than the number of
7 MAC Flows for which the Grant is transmitted. The access network
8 shall specify this field as a 4-bit value in the range 0…15, inclusive.
9 The access terminal shall support all valid values for this field.
10 MACFlowID The access network shall set this field to the MAC Flow for which the
11 Grant is transmitted. The access network shall specify this field as a
12 4-bit value in the range 0…15, inclusive. The access terminal shall
13 support all valid values for this field.
14 T2PInflow The access network shall set this field to the average T2P for the MAC
18 of 0 to 63.5 dB in units of 0.25 dB. The access network shall support
19 all valid values of this field. The access terminal shall support all
20 valid values for this field.
9-308
1 of 0 to 63.5 dB in units of 0.25 dB. The access terminal shall support

2 all valid values of this field.
3 TT2PHold The access network shall set this field to the interval of time for
5 flow identified by the corresponding MACFlowID after receiving the
6 Grant message. The access network shall specify this field as a 6-bit
7 value in units of frames. The access terminal shall support all valid
11 shall set these bits to ‘0’.The access terminal shall ignore this field.
12
15 given attribute.
16
Field Length (bits)
MessageID 8
TransactionID 8

21
25
9-309
Field Length (bits)
MessageID 8
TransactionID 8
4
8
Field Length (bits)
MessageID 8
TransactionID 8
12
14 10.12.6.3.19.12.6.3.1 Commands Sent

16 10.12.6.3.29.12.6.3.2 Indications

21 • ARQMode
9-310
1 • AuxiliaryPilotChannelParameters
2 • AssociatedFlowsNN
3 • BucketFactorNN
4 • BucketLevelMaxNN
5 • BurstDurationFactorNN
6 • MergeThreshold
7 • MergeThresholdNN
8 • PayloadThresh
9 • PermittedPayload
10 • PilotStrengthQRABThresholdDRCLock
11 • PilotStrengthQRABThresholdDRCUnlock
12 • PowerParameters128
24 • QRABSelectNN
25 • RequestParameters
26 • TransmissionModeNN
27 • T2PFilterTCNN
28 • T2PTransitionFunctionNN
29 • T2PInflowRangeNN
31 MaxNumMACFlows – 1, inclusive. The updated values of the attributes shall be consistent
32 with the value of the MaxNumActiveMACFlows parameter of the MaxMACFlows attribute.
9-311
2 Update Protocol to configure values of the MaxNumSubPackets attribute if the value of the
3 SupportGAUPMaxNumSubPackets attribute is 0x01. Otherwise, the access network and
4 the access terminal shall not include the MaxNumSubPackets attribute in an
7 Protocol to configure any other attributes of the Subtype 3 Reverse Traffic Channel MAC
8 Protocol.
10 definition).

9-312

ID
0xffff ARQMode 0x00 Reverse Link ARQ Mode = 0
0x01 Reverse Link ARQ Mode = 1
All other Reserved
values
0xfffe FRABFilterTC 0x02 IIR filter time constant used by the
access terminal for computing the
Filtered RA bit is 384 slots.
0x00 IIR filter time constant used by the
0x03 IIR filter time constant used for
computing the Filtered RA bit is
512 slots.
All other Reserved
values
0xfffd FRABlow 0x03 Reverse Link Loading Threshold =
−0.8
0x00 Reverse Link Loading Threshold =
−0.2
−0.4
−0.6
−1.0
All other Reserved
values
0xfffc MergeThreshold 0x02 Merge Threshold is 512 octets
0x00 Merge Threshold is 128 octets
0x05 Merge Threshold is infinite octets
All other Reserved
values
9-313

ID
0xfffb PayloadThresh 0x01 Minimum packet size of a Reverse
Traffic Channel packet that the
access terminal is permitted to
transmit in LoLat mode if the
packet does not contain any MAC
flows with LoLat transmission
mode is 1024 octets.
0x00 Minimum packet size of a Reverse
mode is 768 octets.
mode is infinite octets.
All other Reserved
values
0xfffa PilotStrengthFilterTC 0x01 IIR filter time constant used by the
filtered serving sector Pilot
Strength, PilotStrengthn,s is 64
slots.
slots.
slots.
9-314

ID
All other Reserved
values
0xfff9 QRABFilterTC 0x00 IIR filter time constant used by the
Quick RA bit is 4 slots.
All other Reserved
values
0xfff8 T2PNoTxFilterTC 0x01 IIR filter time constant used by the
access terminal when it is in Open
State but not transmitting on the
Reverse Link for computing
T2PInflown is 24 sub-frames.




All other Reserved

values
0xfff7 PilotStrengthQRABThreshol 0x18 PilotStrengthQRABThresholdDRCL
dDRCLock ock is −6 dB
0x00 to PilotStrengthQRABThresholdDRCL
0x3f ock is in units of –0.25 dB in the
range 0 dB to –15.75 dB, inclusive
9-315

ID
All other Reserved
values
0xfff6 PilotStrengthQRABThreshol 0x0c PilotStrengthQRABThresholdDRCU
dDRCUnlock nlock is −3 dB
0x00 to PilotStrengthQRABThresholdDRCU
0x3f nlock is in units of –0.25 dB in the
All other Reserved
values
0xfff5 Rate1M8Supported 0x00 The access terminal does not
support 1.8 Mbps transmission on
the Reverse Traffic Channel
0x01 The access terminal supports 1.8
Mbps transmission on the Reverse
Traffic Channel
All other Reserved
values
0xfff4 SupportGAUPMaxNumSub 0x00 Modification of the
Packets MaxNumSubPackets attribute
using the Generic Attribute Update
Protocol is not supported.
0x01 Modification of the
MaxNumSubPackets attribute
Protocol is supported.
All other Reserved
values
0xff3 BucketLevelMax00 0x50 BucketLevelMax for flow 0x00 is
20 dB
0xfe00
0x01 to BucketLevelMax for flow 0x00 in
0xff units of 0.25 dB
0x00 Reserved
0xfff2 BucketLevelMax01 0x6c BucketLevelMax for flow 0x01 is
27 dB
0xfe01
0x00 BucketLevelMax for flow 0x01 is
NULL
0xfeNN BucketLevelMaxNN 0x00 BucketLevelMax for flow NN is
NULL
9-316

ID
NN is the NN is the two-digit 0x01 to BucketLevelMax for flow NN in
two-digit hexadecimal MAC flow 0xff units of 0.25 dB
hexadecim number in the range 0x02
al MAC through
number in inclusive, where
the range hexadecimal digits A
0x02 through F are specified in
through upper case letters.
MaxNum
MACFlows
−1,
inclusive.
0xfd00 MergeThreshold00 0x00 Merge Threshold for flow 0x00 if it
is transmitted in High Capacity
Mode is 0 octets
0x01 Merge Threshold for flow 0x00 if it

Mode is 32 octets

Mode is 128 octets

Mode is 1024 octets

Mode is infinite octets
All other Reserved

values
0xfdNN MergeThresholdNN 0x02 Merge Threshold for flow NN if it is
transmitted in High Capacity Mode
is 128 octets.
hexadecim number in the range 0x01 0x00 Merge Threshold for flow NN if it is
al MAC through transmitted in High Capacity Mode
flow MaxNumMACFlows −1, is 0 octets.
0x01 Merge Threshold for flow NN if it is
0x01 transmitted in High Capacity Mode
through F are specified in
through is 32 octets.
upper case letters.
MaxNum 0x03 Merge Threshold for flow NN if it is
MACFlows transmitted in High Capacity Mode
−1, is 1024 octets.
9-317

ID
inclusive. 0x04 Merge Threshold for flow NN if it is
is 4096 octets.
is 8192 octets.
is infinite octets.
All other Reserved
values
0xfcNN TransmissionModeNN 0x00 The Transmission mode for flow NN
is High Capacity
two-digit hexadecimal MAC flow 0x01 The Transmission mode for flow NN
hexadecim number in the range 0x00 is Low Latency
al MAC through
All other Reserved
values
MaxNum
MACFlows
−1,
inclusive,
where
hexadecim
al digits A
through F
are
specified
in upper
case
letters.
0xfbNN QRABSelectNN 0x00 Use QRAB
9-318

ID
hexadecim number in the range 0x00 All other Reserved
al MAC through values
MaxNum
MACFlows
−1,
inclusive,
where
hexadecim
al digits A
through F
are
specified
in upper
case
letters.
0xfaNN BurstDurationFactorNN 0x00 BurstDurationFactor for flow NN is
4
two-digit hexadecimal MAC flow 0x01 BurstDurationFactor for flow NN is
hexadecim number in the range 0x00 8
al MAC through
0x02 BurstDurationFactor for flow NN is
number in 16
inclusive, where
the range hexadecimal digits A 0x03 BurstDurationFactor for flow NN is
0x00 through F are specified in 32
MaxNum All other Reserved
MACFlows values
−1,
inclusive,
where
hexadecim
al digits A
through F
are
specified
in upper
case
letters.
0xf9NN T2PFilterTCNN 0x01 IIR filter time constant used by the
access terminal for computing
T2PInflown for flow 0xNN is 24
sub-frames.
9-319

ID
hexadecim number in the range 0x00 0x00 IIR filter time constant used by the
al MAC through access terminal for computing
flow NMFRTCMACFlowMaxMaxNumMA T2PInflown for flow 0xNN is 16
number in CFlows − 1, inclusive,
sub-frames.
the range where hexadecimal digits A
0x00 through F are specified in 0x02 IIR filter time constant used by the
through upper case letters. access terminal for computing
NMFRTCMACFl T2PInflown for flow 0xNN is 32
owMaxMaxN
sub-frames.
umMACFl
ows − 1, 0x03 IIR filter time constant used by the
inclusive. access terminal for computing
sub-frames.
sub-frames.
All other Reserved
values
1

4 10.12.7.2.19.12.7.2.1 AssociatedFlowsNN Attribute

7
Field Length(bits) Default Default for

NN = 0x01
for NN between
0x02 and
(MaxNumMACFlow
s −1), inclusive
Length 8 N/A N/A
9-320

{
ValueID 8 N/A N/A
FlowCount 8 0 1
{
Stream 9 N/A 511
SubStream 8 N/A 0

needed)
7 complex value.

13 sender shall set this field to 3 more than the virtual stream number.
14 If this MAC flow is to be associated with all higher layer flow not
15 associated with a MAC flow, then the sender shall set this field to
16 ‘111111111’.

9-321

6 10.12.7.2.29.12.7.2.2 AuxiliaryPilotChannelParameters Attribute

7

Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
AuxiliaryPilotChannelGain 4 0x0c
AuxiliaryPilotChannelMinPayload 4 0x7
12 complex value.
13 AuxiliaryPilotChannelGain
14 The sender shall set this field to the Auxiliary Pilot Channel Gain
15 relative to the Traffic Channel Gain that the access terminal uses to
16 compute the Auxiliary Pilot Channel transmit power level. The sender
17 shall specify this field as a 4-bit value in units of –1 dB in the range 0
18 dB to -15 dB, inclusive. The receiver shall support all valid values
20 AuxiliaryPilotChannelMinPayload
21 The sender shall set this field to the minimum Reverse Traffic
22 Channel payload for which the access terminal is required to
23 transmit the Auxiliary Pilot Channel. The sender shall specify this
24 field as a 4-bit number as shown in Table 9.12.7.2.2-1. The receiver
9-322
1 Table 9.12.7.2.2-1.Encoding of AuxiliaryPilotChannelMinPayload Field
Field value Meaning
‘0000’ 128
‘0001’ 256
‘0010’ 512
‘0011’ 768
‘0100’ 1024
‘0101’ 1536
‘0110’ 2048
‘0111’ 3072
‘1000’ 4096
‘1001’ 6144
‘1010’ 8192
‘1011’ 12288
2
3 10.12.7.2.39.12.7.2.3 BucketFactorNN Attribute

9-323
Default for Default for

Field Length (bits) NN > 0x00 NN = 0x00
Length 8 N/A N/A

{
ValueID 8 N/A N/A
9.12.7.2.3-1 9.12.7.2.3-4
9.12.7.2.3-2 9.12.7.2.3-5
field:
9.12.7.2.3-3 9.12.7.2.3-6

needed)
}
4 Length field.
9 complex value.
9-324
1 NumFRABAxisValues

4 field as a 3-bit value. The receiver shall support all valid values
17 BucketFactor( ) at the T2PInflow value of T2PAxis and the FRAB
18 value of FRABAxis. The sender shall set the data in the following
19 order: BucketFactor( ) is specified for all the FRABaxisFRABAxis
20 values, then cycled through for each T2PAxis value. The sender shall
21 specify this field as an 8-bit value in the range 1...32 7/8, inclusive
22 in units of 1/8. The receiver shall support all valid values specified
23 by this field.
9-325
Field Default for

NN > 0x00
T2PAxis00 0x00
T2PAxis01 0x48
Field Default for

NN > 0x00
FRABAxis0 0x8
FRABAxis1 0xb
FRABAxis2 0x7
3
Field Default
for NN >
0x00
5
Field Default for

NN = 0x00
T2PAxis00 0x10
T2PAxis01 0x2b
Field Default for

NN = 0x00
FRABAxis0 0x0
8
9-326
Field Default for

NN = 0x00
2
3 10.12.7.2.49.12.7.2.4 CommonPowerParameters Attribute

4

Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
TxT2Pmin 8 0x0F
RPCStep 2 ‘01’
Reserved 0-7(as N/A
needed)
}
5
10 complex value.
11 AllocationStagger T2P allocation stagger factor. The sender shall set this field to the
12 desired T2P allocation dither factor across MAC flows at an access
13 terminal and across access terminals. This field is a 4-bit value in
14 steps of 1/16 in the range of 0…15/16, inclusive. The access
9-327
1 RPCStep Reverse Power Control step. The sender shall set this field to the
2 power control step size the access terminal is to use when controlling
3 the power of the reverse link, as shown in Table 9.12.7.2.4-1. The
4 access terminal shall support the 0.5 dB and 1.0 dB step sizes and
5 should support the 1.5 dB and 2.0 dB step sizes.
Field value Meaning

(binary)
‘00’ 0.5 dB
‘01’ 1.0 dB
‘10’ 1.5 dB
‘11’ 2.0 dB
10 10.12.7.2.59.12.7.2.5 MaxNumSubPackets Attribute

11

Length 8 N/A
AttributeID 16 N/A
record:
{
ValueID 8 N/A
MaxNumSubPackets0 2 0x3
Reserved 2 N/A
}
16 complex value.
9-328
1 MaxNumSubPackets0
2 The sender shall set this field to one less than the maximum number
3 of subpackets for interlace 0. The sender shall specify this field as a
4 2-bit value in the range 0x0 to 0x3, inclusive.
5 MaxNumSubPackets1
9 MaxNumSubPackets2
14 field.
9-329
1 10.12.7.2.69.12.7.2.6 PermittedPayload Attribute

2
Length 8 N/A
AttributeID 16 N/A
record:
{
ValueID 8 N/A
9-330

PermittedPayload4096_1 4 0xb
PermittedPayload8192_1 4 0xc
Reserved 4 N/A
6 complex value.
9-331
13 this field.
20 this field.
27 this field.
34 this field.
9-332
6 this field.
13 this field.
20 this field.
27 this field.
34 this field.
9-333

4 this field.
11 this field.
18 this field.
25 this field.
32 this field.
9-334

2 this field.
9 this field.
16 this field.
23 this field.
30 this field.
37 this field.
9-335
7 this field.
14 this field.
21 this field.
28 this field.
35 this field.
9-336
6 this field.
13 this field.
20 this field.
27 this field.
34 this field.
9-337

4 this field.
11 this field.
18 this field.
25 this field.
32 this field.
9-338

2 this field.
4 field.
5
6 Table 9.12.7.2.6-1. Packet size encoding
Packet size Value

(bits)
0 0x0
128 0x1
256 0x2
512 0x3
768 0x4
1024 0x5
1536 0x6
2048 0x7
3072 0x8
4096 0x9
6144 0xa
8192 0xb
12288 0xc
7
9-339
1 10.12.7.2.79.12.7.2.7 PilotStrength Attribute

2
Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
{

9.12.7.2.7-1
PilotStrengthPilotStrengthAxis 4 See Table
9.12.7.2.7-2
}
Reserved 4(0-7) N/A
Variable
}
3
6 Length field.
9 complex value.

13 field to zero.
9-340
2 The sender shall set this field to the scale factor used to scale
4 corresponding PilotStrengthAxis field. The sender shall specify this
5 field as a 2’s complement 4-bit value in units of 1 dB. The receiver
9 ignore this field.The sender shall set this field to ‘0000’. The receiver
11
Field Default
13
14 Table 9.12.7.2.7-2. PilotStrengthPilotStrengthAxis Default Values
Field Default
PilotStrengthPilotStrengthAxis 0x0
0
PilotStrengthPilotStrengthAxis 0x0
1
15
16
9-341
1 10.12.7.2.89.12.7.2.8 PowerParameters128 Attribute

2
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
LoLatT2PTransition128 2 0x1
LoLatTerminationTarget128 2 0x1
HiCapT2PTransition128 2 0x3
HiCapTerminationTarget128 2 0x3
T2PLoLatPreTransition128 8 0x1C
T2PLoLatPostTransition128 8 0x03
T2PHiCapPreTransition128 8 0x03
T2PHiCapPostTransition128 8 0x03
7 complex value.
8 LoLatT2PTransition128
9 The sender shall set this field to one less than the number of sub-
10 frames for which the receiver shall use the pre-transition T2P values
11 and the number of sub-frames after which the receiver shall use the
12 post-transition T2P values when transmitting a Reverse Traffic
13 Channel packet with packet size of 128 bits using the Low Latency
14 Mode. The sender shall specify this field as a 2-bit value in units of
15 sub-frames. The receiver shall support all valid values specified by
16 this field.
17 LoLatTerminationTarget128
18 The sender shall set this field to one less than the expected number
19 of sub-frames needed to achieve the target Physical Layer erasure
20 rate for a Reverse Traffic Channel packet with packet size of 128 bits
21 transmitted using the Low Latency Mode. The sender shall specify
9-342
1 this field as a 2-bit value in units of sub-frames. The receiver shall

3 HiCapT2PTransition128
8 Channel packet with packet size of 128 bits using the High Capacity
9 mode. The sender shall specify this field as a 2-bit value in units of
11 this field.
12 HiCapTerminationTarget128
16 transmitted using the High Capacity Mode. The sender shall specify
19 T2PLoLatPreTransition128
20 The sender shall set this field to the Data Channel power relative to
21 the Pilot Channel power when transmitting a 128-bit payload using
22 the Low Latency mode prior to the T2P transition. The sender shall
23 specify this field as an 8-bit number in units of 0.25 dB. The sender
24 shall set this field to a value in the range 0x00 through 0x80,
25 inclusive.
26 T2PLoLatPostTransition128
29 the Low Latency mode following the T2P transition. The sender shall
32 inclusive.
33 T2PHiCapPreTransition128
36 the High Capacity mode prior to the T2P transition. The sender shall
9-343
2 inclusive.
3 T2PHiCapPostTransition128
6 the High Capacity mode following the T2P transition. The sender
7 shall specify this field as an 8-bit number in units of 0.25 dB. The
8 sender shall set this field to a value in the range 0x00 through 0x80,
9 inclusive.

11
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPreTransition256 8 0x28
T2PLoLatPostTransition256 8 0x0F
T2PHiCapPreTransition256 8 0x0F
T2PHiCapPostTransition256 8 0x0F
14 Length field.
17 complex value.
9-344
4 this field.
20 this field.
34 inclusive.
41 inclusive.
9-345
7 inclusive.
14 inclusive.

16
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPostTransition512 8 0x1C
T2PHiCapPreTransition512 8 0x1C
T2PHiCapPostTransition512 8 0x1C
19 Length field.
22 complex value.
9-346
9 this field.
25 this field.
39 inclusive.
9-347
4 inclusive.
11 inclusive.
18 inclusive.

20
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPreTransition768 8 0x3B
23 Length field.
9-348
2 complex value.
11 this field.
27 this field.
41 inclusive.
9-349
7 inclusive.
14 inclusive.
21 inclusive.
9-350

2
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
5 Length field.
8 complex value.
17 this field.
21 rate for a Reverse Traffic Channel packet with packet size of 1024
22 bits transmitted using the Low Latency Mode. The sender shall
23 specify this field as a 2-bit value in units of sub-frames. The receiver
9-351
9 this field.
14 bits transmitted using the High Capacity Mode. The sender shall
23 inclusive.
30 inclusive.
37 inclusive.
9-352
2 inclusive.

4
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPostTransition1536 8 0x2E
T2PHiCapPreTransition1536 8 0x2E
T2PHiCapPostTransition1536 8 0x2E
7 Length field.
8 AttributeID The sender shall set this field to 0x000a.
10 complex value.
19 this field.
9-353
12 this field.
26 inclusive.
33 inclusive.
40 inclusive.
9-354
7 inclusive.

9
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPreTransition2048 8 0x4D
12 Length field.
13 AttributeID The sender shall set this field to 0x000b.
15 complex value.
9-355

2 this field.
6 rate for a Reverse Traffic Channel packet with packet size of 2,048
18 this field.
28 the Pilot Channel power when transmitting a 2,048-bit payload using
32 inclusive.
39 inclusive.
9-356

5 inclusive.
12 inclusive.

14
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
17 Length field.
18 AttributeID The sender shall set this field to 0x000c.
20 complex value.
9-357
6 this field.
22 this field.
36 inclusive.
9-358
2 inclusive.
9 inclusive.
16 inclusive.

18
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
21 Length field.
22 AttributeID The sender shall set this field to 0x000d.
9-359
2 complex value.
11 this field.
27 this field.
41 inclusive.
9-360
7 inclusive.
14 inclusive.
21 inclusive.
9-361

2
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
5 Length field.
6 AttributeID The sender shall set this field to 0x000e.
8 complex value.
17 this field.
9-362
9 this field.
23 inclusive.
30 inclusive.
37 inclusive.
9-363
2 inclusive.

4
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPostTransition8192 8 0x4A
T2PHiCapPreTransition8192 8 0x4A
T2PHiCapPostTransition8192 8 0x4A
7 Length field.
8 AttributeID The sender shall set this field to 0x000f.
10 complex value.
19 this field.
9-364
12 this field.
22 the Pilot Channel power when transmitting an 8192-bit payload
23 using the Low Latency mode prior to the T2P transition. The sender
26 inclusive.
30 using the Low Latency mode following the T2P transition. The sender
33 inclusive.
37 using the High Capacity mode prior to the T2P transition. The sender
40 inclusive.
9-365
4 using the High Capacity mode following the T2P transition. The
6 The sender shall set this field to a value in the range 0x00 through
7 0x80, inclusive.

9
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
12 Length field.
15 complex value.
24 this field.
9-366
13 Channel packet with packet size of 12288 bits using the High
14 Capacity mode. The sender shall specify this field as a 2-bit value in
15 units of sub-frames. The receiver shall support all valid values
26 the Pilot Channel power when transmitting a 12288-bit payload
30 inclusive.
37 inclusive.
9-367
2 inclusive.
5 the Pilot Channel power when transmitting a 12,288-bit payload
9 0x80, inclusive.
10 10.12.7.2.209.12.7.2.20 RequestParameters Attribute

11
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
ReqRatio 4 0x0
14 Length field.
17 complex value.
9-368
1 10.12.7.2.219.12.7.2.21 RRIChannelPowerParameters Attribute

2

Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
RRIChannelGainPreTransition0 4 0x0
RRIChannelGainPostTransition0 4 0xA
RRIChannelGainPreTransition2 4 0xA
Reserved 4 N/A
5 Length field.
8 complex value.
9 RRIChannelGainPreTransition0
10 The sender shall set this field to the RRI Channel Gain for sub-
11 packets transmitted prior to the T2P transition for a T2P transition
12 value of 1 sub-frame. The sender shall specify this field as a 2’s
13 complement 4-bit number in units of 1dB. The receiver shall support
14 all valid values specified by this field.
15 RRIChannelGainPostTransition0
17 packets transmitted following the T2P transition for a T2P transition
9-369
4 value of 2 sub-frames. The sender shall specify this field as a 2’s
30 all valid values specified by this field. The access terminal also uses
31 this value to set the gain of the RRI channel when no packet is being
32 transmitted on the Reverse Traffic Channel.
33 Reserved The access network shall set this field to ‘0000’. The access terminal
35 10.12.7.2.229.12.7.2.22 T2PInflowRangeNN Attribute

9-370
Field Length(bits) Default for Default for

NN > 0x00 NN = 0x00
Length 8 N/A N/A
ValueID 8 N/A N/A
4 Length field.
9 complex value.
11 receiver is to use to determine the T2P allocation for MAC flow NN.
12 The sender shall specify this field as an 8-bit value in units of 0.25
13 dB. The receiver shall support all valid values specified by this field.
15 receiver is to use to determine the T2P allocation for MAC flow NN.
16 The sender shall specify this field as an 8-bit value in units of 0.25
17 dB. The receiver shall support all valid values specified by this field.
18 10.12.7.2.239.12.7.2.23 T2PTransitionFunctionNN Attribute

9-371
Field Length(bits) Default for NN > Default for NN =

0x00 0x00
Length 8 N/A N/A

{
ValueID 8 N/A N/A
9.12.7.2.23-1 9.12.7.2.23-5
FRABAxis 4 SeeTable See Table
9.12.7.2.23-2 9.12.7.2.23-6
9.12.7.2.23-3 9.12.7.2.23-7
9.12.7.2.23-4 9.12.7.2.23-8

needed)
}
8 complex value.
12 field.
9-372
4 field.
17 the data in the following order: T2PUp( ) is specified for all the
18 FRABaxisFRABAxis values, then cycled through for each T2PAxis
19 value. The receiver shall use the value of this field to compute
20 ΔT2PInflow. The sender shall specify this field as an 8-bit 2’s
21 complement in units of 0.25 dB. The receiver shall support all valid
26 the data in the following order: T2PDn( ) is specified for all the
27 FRABaxisFRABAxis values, then cycled through for each T2PAxis
9-373
Field Default for

NN > 0x00
T2PAxis00 0x00
T2PAxis01 0x22
T2PAxis02 0x47
T2PAxis03 0x5a
Field Default for

NN > 0x00
FRABAxis0 0x8
FRABAxis1 0xb
FRABAxis2 0xe
FRABAxis3 0x7
3
9-374
1 Table 9.12.7.2.23-3. T2PUpT2PAxisTTFRABAxisF Default Values

> 0x00
T2PUpT2PAxis00FRABAxis0 0x1d
T2PUpT2PAxis00FRABAxis1 0x0a
T2PUpT2PAxis00FRABAxis2 0xfe
9-375
1 Table 9.12.7.2.23-4. T2PDnT2PAxisTTFRABAxisF Default Values
Field Default for

NN > 0x00
T2PDnT2PAxis03FRABAxis0 0x2d
T2PDnT2PAxis03FRABAxis2 0x1a
2
Field Default for

NN = 0x00
T2PAxis00 0x10
T2PAxis01 0x2b
4
Field Default for

NN = 0x00
FRABAxis0 0x0
6
9-376
Field Default for

NN = 0x00
2
Field Default for

NN = 0x00
4
5 10.12.7.2.249.12.7.2.24 TxT2Pmax Attribute

6
Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
{
}
needed)
}
9 Length field.
12 complex value.
9-377

4 field to zero.
12 terminal is allowed to transmit if the filtered serving sector
13 PilotStrength equals corresponding
14 PilotStrengthaxisPilotStrengthAxis value. The sender shall specify
15 this field as a 7-bit value expressed in units of 0.5 dB. The access
Field Default
Field Default
TxT2PmaxPilotStrengthAxis 0x18
0
1
22 10.12.7.2.259.12.7.2.25 MaxMACFlows Attribute

23
9-378
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
5 complex value.

14

the Setup State

9-379


5 Parameter
Field Length (bits)
ParameterType 8
Length 8
MIRTCMAC 42
MQRTCMAC 42
Reserved 4
9-380
1 No text.
9-381
1 10.139.13 Multicarrier Reverse Traffic Channel MAC Protocol
2 10.13.19.13.1 Overview
3 The Multicarrier Reverse Traffic Channel MAC Protocol provides the procedures and
4 messages required for an access terminal to transmit using single or multiple Reverse
5 CDMA Channels, and for an access network to receive the respective Reverse CDMA
6 Channels. Specifically, this protocol addresses Reverse Traffic Channel transmission rules
7 and rate control. This protocol supports intra-access terminal Quality of Service (QoS) for
8 multiple concurrent active MAC flows over single or multiple assigned Reverse CDMA
9 Channels at the access terminal. Rate control in each assigned Reverse CDMA Channel is
10 accomplished via per active MAC flow Traffic-to-Pilot power ratio (T2P) control. The
11 Multicarrier Reverse Traffic Channel MAC protocol provides per active MAC flow QoS
12 control in each and across all assigned Reverse CDMA Channels. This is achieved by
13 distributed rate selection (at the access terminal) and centralized (scheduled) resource
14 allocation (by the access network) in each assigned Reverse CDMA Channel. The
15 Multicarrier Reverse Traffic Channel MAC achieves per active MAC flow data policing using
16 a Data Token Bucket mechanism which spans all assigned Reverse CDMA Channels at the
17 access terminal for each active MAC flow. The Data Token bucket parameters are
18 controlled by the access network. Additionally, the Multicarrier Reverse Traffic Channel
19 MAC provides QoS for each active MAC flow and controls each active MAC flow’s
20 contribution to the network loading in each assigned Reverse CDMA Channel using a T2P
21 Token Bucket mechanism and a one-bit (the Reverse Activity Bit, or RAB) feedback from
22 the access network. This protocol operates with the Subtype 3 Physical Layer Protocol.
25 This protocol operates in one of three states for each of the supported Reverse CDMA
26 Channels (the supported Reverse CDMA Channels are public data of the Route Update
27 Protocol.):
29 Channel on that Reverse CDMA Channel. When the protocol is in this state, it waits for
30 an Activate command.
32 it receives from the access network for the Reverse CDMA Channel assigned130 by the
33 access network. Data transmission on the Reverse Traffic Channel corresponding to the
34 Reverse CDMA Channel is not allowed in this state.
35 • Open State: In this state, the access terminal obeys the power control commands that it
36 receives from the access network for the Reverse CDMA Channel assigned by the access
37 network. In this state, the access terminal may transmit data on the Reverse Traffic
38 Channel corresponding to this assigned Reverse CDMA Channel.
130 The assigned Reverse CDMA Channels are public data of the Route Update Protocol.
9-382
Initial State
Rx Activate
Rx Deactivate or
timer expires
Open State
4 Figure 9.13.1-1. Multicarrier Reverse Traffic Channel MAC Protocol State Diagram
5 (for each supported Reverse CDMA Channel)
6 Each active MAC flow contributes to sector loading in each of the assigned Reverse CDMA
7 Channels and its contribution is strongly correlated with its average transmit T2P in that
8 channel. An access terminal may transmit multiple active MAC flows simultaneously on
9 one or more of the assigned Reverse CDMA Channels. The Multicarrier Reverse Traffic
10 Channel MAC protocol uses the average transmit T2P per active MAC flow in each of the
11 assigned Reverse CDMA Channels as a measure of the air link resource used by that MAC
12 flow in the corresponding Reverse CDMA Channel. The Multicarrier Reverse Traffic
13 Channel MAC protocol treats multiple active MAC flows associated with a single access
14 terminal in a manner consistent with multiple active MAC flows associated with multiple
15 access terminals, subject to access terminal transmit power constraints. This protocol
16 controls the average T2P of an active MAC flow in each assigned Reverse CDMA Channel
17 and the average data rate of an active MAC flow across all assigned Reverse CDMA
18 Channels based on the requirements of that MAC flow, requirements of other concurrent
19 active MAC flows, transmit power constraints, and sector loading on each assigned Reverse
20 Traffic Channel. The Multicarrier Reverse Traffic Channel MAC protocol allows updating
21 Reverse Traffic Channel MAC attributes (access terminal specific, MAC flow specific, and
22 assigned Reverse CDMA Channel specific) using the Generic Attribute Update Protocol.
24 10.13.2.19.13.2.1 Commands
26 • Activate (along with arguments indicating the assigned Reverse CDMA Channels)
27 • Deactivate
9-383

3 • LinkAcquired
5 • ReverseCDMAChannelDropped
6 10.13.2.39.13.2.3 Public Data

9 • ARQMode for each assigned Reverse CDMA Channel
10 • AuxiliaryPilotChannelGain
11 • AuxiliaryPilotChannelMinPayload
12 • RRI (Payload Index and sub-packet Index for each assigned Reverse CDMA Channel)
13 • RRIChannelGain for each assigned Reverse CDMA Channel
14 • TxT2P for each assigned Reverse CDMA Channel
15 • RPCStep
16 • MIRTCMAC
17 • MQRTCMAC
18 • RAChannelGain for each pilot in the Active Set


9-384
4 10.13.5.19.13.5.1 Procedures
8 The access network shall not initiate negotiation of the MaxPacketSize attribute.

17 − ARQMode
18 − AuxiliaryPilotChannelGain
19 − AuxiliaryPilotChannelMinPayload
20 − RPCStep
22 then
9-385
4
Field Length (bits)
MessageID 8
TransactionID 8
12
Field Length (bits)
MessageID 8
TransactionID 8

9-386
3 10.13.6.19.13.6.1 Procedures
4 The protocol constructs a Multicarrier Reverse Traffic Channel MAC Layer packet out of a
6 Protocol.
7 The Multicarrier Reverse Traffic Channel MAC Protocol supports multiple MAC Flows. MAC
9 with MAC flow NN is greater than zero, where NN is the two-digit hexadecimal flow number
10 in the range 0x00 to MaxNumMACFlows −1, inclusive. The number of active MAC Flows
11 shall not exceed the value of the MaxNumActiveMACFlows parameter of the MaxMACFlows
12 attribute.
13 The Multicarrier Reverse Traffic Channel MAC Protocol supports multiple Reverse CDMA
14 Channels.
15 10.13.6.1.19.13.6.1.1 MAC Layer Packet

16 The MAC Layer packet is the basic unit of data provided by the Multicarrier Reverse Traffic
18 is shown in Figure 9.13.6.1.1-1.The MAC Layer packet consists of a Security Layer packet
19 followed by the MAC Layer trailer. The MAC Layer packet is transmitted in one of two
20 modes, Low Latency mode or High Capacity mode.
MAC Layer packet
Security MAC
Layer Layer
packet trailer
21
24 10.13.6.1.2.19.13.6.1.2.1 Activate
9-387
1 • Transition the protocol to the Setup State for the Reverse CDMA Channel(s) provided as
2 arguments along with the Activate command. If no arguments are provided, then the
3 protocol shall transition to the Setup state for the Reverse CDMA Channel assigned by
4 the access network as indicated by public data of the Route Update Protocol.
6 10.13.6.1.2.29.13.6.1.2.2 Deactivate
7 If the protocol receives a Deactivate command and is in the Setup State or the Open State
8 for any Reverse CDMA Channel,
10 transition the protocol to the Inactive State for all Reverse CDMA Channels.
12 terminal and shall transition the protocol to the Inactive State for all Reverse CDMA
13 Channels.

18 9.13.6.1.3-1.
BIT
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
20

22 ATILCM = (A31, A30, A29, …, A0)
25 A15, A6, A28, A19, A10, A1, A23, A14, A5, A27, A18, A9).
9-388
1 10.13.6.1.49.13.6.1.4 Inactive State

4 10.13.6.1.59.13.6.1.5 Setup State

6 The access terminal shall set a ReverseAcquisition timer for the Reverse CDMA Channel for
7 TRTCMPATSetup seconds when it enters this state.
8 If the ReverseAcquisition timer for this Reverse CDMA Channel expires, then the access
9 terminal shall perform the following:
10 • If the protocol is in the Inactive State for all other Reverse CDMA Channels except the
11 Reverse CDMA Channels whose ReverseAcquisition timers expire at the same time as this
12 Reverse CDMAChannel, then the access terminal shall return a SupervisionFailed
13 indication.
14 • If the protocol is in the Setup or Open State for any other Reverse CDMA Channels
15 except the Reverse CDMA Channels whose ReverseAcquisition timers expire at the same
16 time as this Reverse CDMA Channel, then the access terminal shall send a
17 ReverseCDMAChannelDropped message with appropriate ReasonCode, and revert to the
18 Inactive state for this Reverse CDMA Channel.
20 this state, and shall obey the Reverse Power Control Channel.
21 The access terminal shall follow procedures specified in 9.13.6.1.6.1.6 in addition to the
23 The access terminal shall not transmit any data on the Reverse Traffic Data Channel
24 associated with the Reverse CDMA Channel while in this state.
25 Upon receiving an RTCAck message, the access terminal shall send a RTCAckAck message.
26 If the access terminal receives an RTCAck message indicating that the Reverse CDMA
27 Channel has been acquired, and the protocol is not in the Open state for any Reverse
28 CDMA Channel, then the access terminal shall generate a LinkAcquired indication. If the
29 access terminal receives an RTCAck message indicating that the Reverse CDMA Channel
30 has been acquired, then the protocol shall transition to the Open State for the acquired
31 Reverse CDMA Channel.

33 The access network shall set a ReverseAcquisition timer for the Reverse CDMA Channel for
34 TRTCMPANSetup seconds when it enters this state. If the protocol is in the Inactive State for all
35 other Reverse CDMA Channels when the timer expires, then the access network shall
38 access network acquired the Reverse Traffic Channel on the Reverse CDMA Channel, and if
39 the protocol is not in the Open state for any of the other Reverse CDMA Channels, then the
9-389
1 access network shall generate a LinkAcquired indication. If the access network acquires the
2 Reverse Traffic Channel on the Reverse CDMA Channel, then it shall send an RTCAck
3 message to the access terminal , and the protocol shall transition to the Open State for the
4 acquired Reverse CDMA Channel.
5 10.13.6.1.69.13.6.1.6 Open State

7 Upon receiving a RTCAck message, the access terminal shall send a RTCAckAck message.
8 Upon entering the Open State for Reverse CDMA Channel r, the access terminal shall
9 perform the following.
10 − Set FRABr,n = 0, where n is the current sub-frame.
11 − For each MAC flow i, set LastBucketLevelMaxi,r to NULL.
12 Upon entering the Open State for Reverse CDMA Channel r, or upon acceptance of an
13 update of the corresponding configuration attribute using Generic Attribute Update
14 Protocol, the access terminal shall set the following parameters to the corresponding
15 attribute values in Reverse CDMA Channel r.
16 • T2PTransitionFunction
17 • T2PInflowRange
18 • PilotStrength
19 • TxT2PMax
21 maximum payload sizes available on the Reverse Traffic Channel in each Reverse CDMA
22 Channel for different values of Reverse Link transmit duration.
23
9-390
1 Table 9.13.6.1.6.1-1.Reverse Traffic Channel Rates and Payload
Payload Payload Effective Data Rate (kbps)

Size (bits) Size (bits)
Minimum Maximum Transmit Transmit Transmit Transmit
Duration Duration Duration Duration
1 sub- 2 sub- 3 sub- 4 sub-
frame frames frames frames
1 96 19.2 9.6 6.4 4.8
97 224 38.4 19.2 12.8 9.6
225 480 76.8 38.4 25.6 19.2
481 736 115.2 57.6 38.4 28.8
737 992 153.6 76.8 51.2 38.4
993 1504 230.4 115.2 76.8 57.6
1505 2016 307.2 153.6 102.4 76.8
2017 3040 460.8 230.4 153.6 115.2
3041 4064 614.4 307.2 204.8 153.6
4065 6112 921.6 460.8 307.2 230.4
6113 8160 1228.8 614.4 409.6 307.2
8161 12256 1843.2 921.6 614.4 460.8
2
9-391
Physical Data Channel Gain Relative Data Channel Gain Relative to

Layer Transmission to Pilot (dB) Pilot (dB)
Packet Mode
Size Pre-Transition Post-Transition
(bits)
− ∞ (Data Channel is not − ∞ (Data Channel is not

0 N/A
transmitted) transmitted)
2
3 The Multicarrier Reverse Traffic Channel MAC Protocol supports two Transmission modes,
4 High Capacity mode and Low Latency mode. Each Transmission mode is specified per
9-392
1 active MAC flow and is characterized by a physical layer transmit duration. The physical
2 layer transmit duration is one, two, three or four sub-packets. A termination target is
3 specified for each packet size for both the Low Latency and the High Capacity transmission
4 modes. The termination target is defined as one less than the number of sub-packets that
5 an access terminal is required to transmit for the packet to be received by the access
6 network with the target packet erasure rate131. The termination target is defined by
7 LoLatTerminationTargetPS for a packet with packet size PS transmitted in Low Latency
8 mode. The termination target is defined by HiCapTerminationTargetPS for a packet with
9 packet size PS transmitted in High Capacity mode. The access terminal may transmit using
10 different Transmission modes in each assigned Reverse CDMA Channel. The transmit
11 duration defines the effective data rate for a given packet size as shown in Table
12 9.13.6.1.6.1-1. For example, a 256-bit payload results in an effective data rate of 38.4kbps,
13 19.2kbps, 12.8kbps, and 9.6kbps for a transmit duration of one, two, three, or four sub-
14 packets respectively.
15 T2PHiCapPreTransitionPS defines the T2P's used by the access terminal for transmitting
16 the first HiCapT2PTransitionPS+1 sub-packets of a Reverse Traffic Channel packet with
17 packet size PS in High Capacity Mode, where PS can take on the following values: 128, 256,
18 512, 768, 1024, 1536, 2048, 3072, 4096, 6144, and 8192, and 12288 bits.
19 T2PHiCapPostTransitionPS defines the T2P's used by the access terminal for transmitting
20 the subsequent sub-packets of a Reverse Traffic Channel packet with packet size PS in
21 High Capacity Mode.
22 T2PLoLatPreTransitionPS defines the T2P's used by the access terminal for transmitting the
23 first LoLatT2PTransitionPS+1 sub-packets of a Reverse Traffic Channel packet with packet
24 size PS in Low Latency Mode, where PS can take on the following values: 128, 256, 512,
25 768, 1024, 1536, 2048, 3072, 4096, 6144, and 8192, and 12288 bits.
26 T2PLoLatPostTransitionPS defines the T2P's used by the access terminal for transmitting
27 the subsequent sub-packets of a Reverse Traffic Channel packet with packet size PS in Low
28 Latency Mode.
29 The access network uses the RA bit (one RA bit per Reverse CDMA Channel per sector) to
30 provide an indication of loading on each Reverse CDMA Channel in each sector’s reverse
31 link to the access terminal. The reliability of the RA channel is improved by filtering the RA
32 bit at the access terminal. A short-term filter followed by a threshold detector is used at the
33 access terminal to generate the QRAB (Quick RA Bit) which indicates instantaneous sector
34 loading. A long-term filter is used to generate the FRAB (Filtered RA Bit) which indicates
35 longer term sector loading in the corresponding Reverse CDMA Channel.
37 Reverse Rate Indicator in each assigned Reverse CDMA Channel at the earliest time T,
38 following the end of transmission of the previous packet, that satisfies the following
39 equation
131 The target packet erasure rate typically used by the physical layer is 1%
9-393

3 determine the T2P allocation for each active MAC flow in each assigned Reverse CDMA
4 Channel. Variables with suffix m indicate quantities that are updated every slot and
5 variables with suffix n indicate quantities that are updated every sub-frame. Unless
6 otherwise stated, all filters used in this section are first order IIR filters (see 13.13). PS
7 indicates the physical layer packet size and takes on values of 128, 256, 512, 768, 1024,
8 1536, 2048, 3072, 4,096, 6144, 8192, or 12288 bits and subscript N indicates the sub-
9 packet identifier of a physical layer packet and takes on values zero, one, two, or three.
10 The description in this section uses the following variables and functions:
11 • AllocationStagger: T2P allocation time stagger.
12 • AuxiliaryPilotChannelGain: Auxiliary Pilot Channel Gain.
13 • BucketLeveli,r,n: Bucket Level (or accumulated T2P resource) at sub-frame n for MAC
14 flow i in Reverse CDMA Channel r, where r is in set RCn.
15 • BucketFactori( ): Indicates by what factor (linear) the T2POutflowi,r,n can exceed

16 T2PInflowi,r,n for MAC flow i.
17 • BucketLevelMaxi: Max T2P resource that can be accumulated (bucket size) for MAC
18 flow i in each Reverse CDMA Channel.
19 • BucketLevelSati,r,n: Saturation Level for BucketLevel i,r,n in Reverse CDMA Channel r,
20 where r is in set RCn.
21 • BurstDurationFactori: Max duration (in sub-frames) for which MAC flow i can sustain a
22 peak rate based on its T2P allocation.
23 • DataBucketLeveli,n: Data Bucket Level (or accumulated data tokens) at sub-frame n
24 for MAC flow i.
25 • DataBucketLevelMaxi: Max data token resource that can be accumulated (bucket size)
26 for MAC flow i.
27 • DataTokenInflowi: The data token resource added to the data bucket for MAC flow i at
28 sub-frame n
29 • di,r,n: Number of octets allocated to MAC flow i for a Reverse Traffic Channel
30 transmission during sub-frame n in Reverse CDMA Channel r, where r is in set RCn.
31 • DeltaT2Pr: The TxT2P adjust value in Reverse CDMA Channel r. If this value is made
32 public by the Route Update Protocol for each of the pilots in the Active Set that carries
33 RAB for reverse CDMA Channel r, then DeltaT2Pr is set to the public data value
34 corresponding to the serving sector pilot. If the Route Update protocol does not define
35 the DeltaT2P as public data or if the sub-active set that carries RAB for the Reverse
36 CDMA Channel r does not include a pilot associated with the serving sector, then the
37 DeltaT2Pr value is set to zero.
9-394
1 • fr,s: The Forward CDMA Channel from pilotPN s which carries RAB for the Reverse
2 CDMA Channel r. Reverse CDMA Channel r is in the access terminal’s set RCn, and
3 fr,s is in the access terminal’s active set Sn. This association is conveyed using public
4 data of the Route Update Protocol.
5 • FCr,n: The sub-Active Set carrying RAB for Reverse CDMA Channel r, which is public
6 data of the Route Update Protocol. Note that set FCr,n is a subset of set Sn.
7 • FRABr,n: Effective Filtered RAB value at sub-frame n from all fr,s in set FCr,n for
8 Reverse CDMA Channel r in set RCn.
9 • FRABfr,s,n: Indicates the Filtered RAB value from fr,s for Reverse CDMA Channel r in set
10 RCn and fr,s in set FCr,n at sub-frame n.
11 • F: Set of all active MAC flows with non-empty queues.

12 • Fr,LL: Set of all active MAC flows with non-empty queues associated with the Low
13 Latency mode in Reverse CDMA Channel r, where r is in RCn.
14 • FRABlow: FRAB threshold. FRABr,n values below FRABlow indicate a sector with a
15 lightly loaded Reverse CDMA Channel r.
16 • HiCapT2PTransitionPS: Number of sub-packets (excluding the first) from the start of
17 the packet for which the pre-transition T2P values are used for High Capacity mode
18 Reverse Traffic Channel transmissions with packet size PS.
19 • LastBucketLevelMaxi,r: The last recorded value of BucketLevelMaxi,n.
20 • LoLatT2PTransitionPS: Number of sub-packets (excluding the first) from the start of the
21 packet for which the pre-transition T2P values are used for Low Latency mode Reverse
22 Traffic Channel transmissions with packet size PS.
23 • MergeThreshold: Merge Threshold (in octets) for Reverse Traffic Channel packets.
24 • MergeThresholdi: Merge Threshold (in octets) for MAC flow i if transmitted in High
25 Capacity Mode.
26 • PacketSizePSr: Physical Layer packet size, in octets, of packet size PS transmitted in
27 sub-frame n in Reverse CDMA Channel r, where r is in set RCn.
28 • PktTxT2Pr,n,N: Transmitted T2P during sub-packet N of a Reverse Traffic Channel

29 packet in Reverse CDMA Channel r, where r is in set RCn, whose first sub-packet is
30 transmitted in sub-frame n and 0 ≤ N ≤ 3.
31 • PayloadThresh: Minimum packet size of a Reverse Traffic Channel packet transmitted
32 in Low Latency mode that does not contain any MAC flows with Low Latency
33 transmission mode when MaxNumSubpacketsI=3 in transmit interlace I.
34 • PermittedPayloadPSr_k: Maximum Physical Layer packet size that an access terminal is
35 permitted to transmit in Reverse CDMA Channel r, where r is in set RCn, in sub-frame
36 n if the Physical Layer packet size transmitted in sub-frame n − k was PSr bits.
9-395
1 • PilotStrengthf,m: Filtered PilotStrength (filter time constant of PilotStrengthFilterTC) at

2 slot m of pilot f.
3 • PilotStrengthn: The value of PilotStrengthf,n for the serving sector pilot f in set SRn
4 when SRn contains a serving sector pilot. Otherwise, the maximum value of
5 PilotStrengthf,n over all pilots f in set SRn at sub-frame n.
6 • PilotStrengthf,n: Filtered PilotStrength sampled at the start of sub-frame n of pilot f.
7 • PilotStrengthr( ): Function that provides the scale factor for scaling T2PInflowi,r,n based
8 on the value of PilotStrengthn.
9 • PilotStrengthQRABThresholdDRCLockr: Minimum PilotStrength value required for

10 QRAB of each fr,s in FCr,n (from any pilot other than the strongest fr,s in FCr,n) to be
11 included in the QRABpsr,n computation when Reverse CDMA Channel r in set RCn is in
12 lock.
13 • PilotStrengthQRABThresholdDRCUnlockr: Minimum PilotStrength value required for
14 QRAB of each fr,s in FCr,n (from any pilot other than the strongest fr,s in FCr,n) to be
15 included in the QRABpsr,n computation when Reverse CDMA Channel r in set RCn is
16 not in lock.
17 • PotentialDataBucketOutflowi,n: Potential Outflow from the data token bucket for MAC
18 flow i.
19 • PotentialT2POutflowi,r,LL: Potential Outflow from the bucket for MAC flow i in Reverse
20 CDMA Channel r, where r is in set RCn, due to a Low Latency mode transmission.
21 • PotentialT2POutflowi,r,HC: Potential Outflow from the bucket for MAC flow i in Reverse
22 CDMA Channel r, where r is in set RCn, due to a High Capacity mode transmission.
23 • Qi,n: Queue length (in octets) of MAC flow i at sub-frame n.
24 • QOutflowi,r,HC: Queue outflow (in octets) for MAC flow i in Reverse CDMA Channel r,
25 where r is in set RCn, with TMi == HiCap.
26 • QRABi,r,n: Effective Quick RAB value for MAC flow i in Reverse CDMA Channel r,
27 where r is in set RCn, at sub-frame n.
28 • QRABr,n: Effective QRAB in Reverse CDMA Channel r, where r is in set RCn, at sub-
29 frame n.
30 • QRABfr,s,n: Indicates the Quick RAB value from fr,s in set FCr,n for Reverse CDMA
31 Channel r in set RCn at sub-frame n.
32 • QRABpsr,n: Indicates the effective Quick RAB value generated at sub-frame n for
33 Reverse CDMA Channel r, where r is in set RCn, based on each PilotStrength fr,s,n of the
34 fr,s in set FCr,n.
35 • QRABSelecti: Indicates which QRAB value, QRABpsr,n or QRABr,n, that the access
36 terminal uses as an indication of short-term sector loading for MAC flow i for each
37 Reverse CDMA Channel r in set RCn.
9-396
1 • RCn: The set of reverse link CDMA channels assigned by the access network to the
2 access terminal and enabled by the RTCAck message prior to sub-frame n.
3 • RRIChannelGainr,n: RRI Channel Gain in sub-frame n for Reverse CDMA Channel r in
4 set RCn.
5 • RRIChannelGainPreTransitionM: RRI Channel Gain prior to the T2P transition if the

7 • RRIChannelGainPostTransitionM: RRI Channel Gain following the T2P transition if the
9 • Reverse Logical Channel: Reference logical index associated with each assigned
10 Reverse CDMA Channel, communicated by the access network to the access terminal in
11 the RTCAck messages.
12 • rr,n: Real-valued uniformly distributed random number in the range [−1,+1] for Reverse
13 CDMA Channel r in set RCn.
14 • Sn = {(f1,a), (f2,a), (f1,b), …}: The active set of the access terminal at subframe n, where
15 each member of the active set is denoted by a Reverse Forward CDMA Channel and
16 PilotPN pair.
17 • SRn = {(f1,a), (f2,b), …}: The PilotReference sub-Active Set of the access terminal at
18 subframe n, where each member of the set is denoted by a carrier and pilotPN pair.
19 • SlotFRABfr,s,m: Filtered value (with filter time constant FRABFilterTC) at slot m of the
20 soft RA bit SoftRABfr,s,m from fr,s for assigned Reverse CDMA Channel r, where fr,s is in
21 set FCr,n. The soft RA bit value is provided by the Physical Layer Protocol.
22 • SlotQRABfr,s,m: Hard-limited value of SoftQRABfr,s,m
23 • SoftQRABfr,s,m: Filtered value (with filter time constant QRABFilterTC) at slot m of the
24 soft RA bit SoftRABfr,s,m from fr,s for assigned Reverse CDMA Channel r, where fr,s is in
25 set FCr,n. The soft RA bit value is provided by the Physical Layer Protocol.
26 • SoftRABfr,s,m: Soft RA bit provided by the Physical Layer Protocol at slot m from fr,s for
27 Reverse CDMA Channel r, where fr,s is in set FCr,n.
28 • SumPayloadr,n: Sum of the octets di,r,n of all active MAC flows i included in a packet
29 transmitted in sub-frame n in Reverse CDMA Channel r, where r is in set RCn.
30 • SumTransmittedDatai,n: Sum of the octets di,r,n over all Reverse CDMA Channels r
31 that are in the access terminal’s set RCn for active MAC flow i in sub-frame n.
32 • SumQOutflowr: Sum of the queue outflows (in octets) for all MAC flows with non-empty
33 queues and TMi == HiCap in Reverse CDMA Channel r, where r is in set RCn.
34 • T2PInflowmini,r: Minimum value of the permitted T2PInflow for MAC flow i in Reverse
35 CDMA Channel r, where r is in set RCn.
36 • T2PInflowmaxi,r: Maximum value of the permitted T2PInflow for MAC flow i in Reverse
37 CDMA Channel r, where r is in set RCn.
9-397
1 • T2PConversionFactorLL: Conversion Factor from T2P to MACPacketSize for Reverse

2 Traffic Channel transmissions that are transmitted using the Low Latency Mode.
3 • T2PConversionFactorHC: Conversion Factor from T2P to MACPacketSize for Reverse
4 Traffic Channel transmissions that are transmitted using the High Capacity Mode.
5 • T2PFilterTCi: Filter time constant used to compute the average T2P for MAC Flow i.
6 • T2PNoTxFilterTC: Filter time constant used to compute the average T2P when the
7 access terminal is in Open state but not transmitting on the Reverse Traffic Channel
8 due to not receiving the corresponding Reverse Activity Bit.
9 • TMi: Transmission Mode for MAC flow i. Transmission Mode for a Reverse Traffic
10 Channel packet is either LoLat (Low Latency Mode) or HiCap (High Capacity Mode).
11 • TT2PHoldi,r,n: Indicates number of sub-frames following sub-frame n for which the T2P
13 for MAC flow i in Reverse CDMA Channel r, where r is in set RCn.
14 • T2PInflowi,r,n: Denotes the average T2P resource added to the bucket for MAC flow i in
15 Reverse CDMA Channel r, where r is in set RCn, at sub-frame n.
16 • T2POutflowi,r,n: Denotes the average T2P resource utilized (and subtracted) from the
17 bucket for MAC flow i in Reverse CDMA Channel r, where r is in set RCn, at sub-frame
18 n.
19 • TxT2Pmacr,n: MAC layer transmit T2P during sub-frame n in Reverse CDMA Channel r,
20 where r is in set RCn
21 • TxT2Pmaxr(PilotStrengthn): Maximum TxT2P that an access terminal is permitted to

22 transmit in Reverse CDMA Channel r, where r is in set RCn, as a function of
23 PilotStrengthn.
24 • TxT2Pmin: TxT2P that an access terminal is permitted to transmit at any time in any
25 Reverse CDMA Channel r, where r is in set RCn.
26 • TxT2Pr,n: Transmitted T2P during sub-frame n in Reverse CDMA Channel r, where r is

27 in set RCn.
28 • TxT2PLoLatPSN =
29 − T2PLoLatPreTransitionPS if N ≤ LoLatT2PTransitionPS
30 − T2PLoLatPostTransitionPS if N > LoLatT2PTransitionPS
31 • TxT2PHiCapPSN =
32 − T2PHiCapPreTransitionPS if N ≤ HiCapT2PTransitionPS
33 − T2PHiCapPostTransitionPS if N > HiCapT2PTransitionPS
34 • TxT2PHiCapNominalPS: Nominal TxT2P for a packet with packet size PS transmitted in
35 High Capacity mode.
9-398
1 • TxT2PLoLatNominalPS: Nominal TxT2P for a packet with packet size PS transmitted in

2 Low Latency mode.
3 • ΔT2PInflowi,r,n: Increase or decrease in T2PInflowi,r,n at sub-frame n for MAC flow i in
5 • T2PUpi,r( ): Two-dimensional piecewise linear function for computing the increase in

6 T2PInflowi,r,n based on current T2PInflow and current FRAB for active MAC flow i in
8 • T2PDni,r( ): Two-dimensional piecewise linear function for computing the decrease in

9 T2PInflowi,r,n based on current T2PInflow and current FRAB for active MAC flow i in
11 The access terminal shall determine T2PUpi,r(T2PInflowi,r,n, FRABr,n) and

12 T2PDni,r(T2PInflowi,r,n, FRABr,n) by bilinear interpolation on the T2P-FRAB grid using the
13 equations described in 13.12.
14 The access terminal shall determine PilotStrengthr(PilotStrengthn) by linear interpolation
15 on the PilotStrength axis using the method described in 13.11.
16 The access terminal shall determine BucketFactori(T2PInflowi,r,n, FRABr,n) by bilinear
17 interpolation on the T2P-FRAB grid using the equations described in 13.12.
18 The access terminal shall determine TxT2Pmaxr(PilotStrengthn) by linear interpolation on
19 the PilotStrength axis using the method described in 13.11.
22 The access terminal shall perform the following operations at the start of every slot m of
23 sub-frame n for each pilot f that is in set SRn but not in FCr,n for any Reverse CDMA
24 Channel r:
25 1. Upon inclusion of a new member pilot f into the access terminal’s set SRn at sub-
26 frame n, the access terminal shall perform the following step:
27 − Set PilotStrengthf,m to the PilotStrength for pilot f, which is public data of the
28 Route Update Protocol.
29 2. Update PilotStrengthf,m: The access terminal shall update the PilotStrength (in the
31 where PilotStrength of pilot f is public data of the Route Update Protocol.
32 If no slot of sub-frame n overlaps with a Reverse Link Silence Interval, then the access
33 terminal shall perform the following operations at the start of every slot m of sub-frame n
34 for each Reverse CDMA Channel r with a monitored RAB that is in the access terminal’s set
35 RCn, and for each fr,s that is in the access terminal’s set FCr,n:
36 1. Initialization due to active set update: Upon inclusion of a new member fr,s into
37 the access terminal’s set FCr,n at sub-frame n, the access terminal shall perform
38 the following steps:
9-399
1 − Set PilotStrengthfr,s,m to the PilotStrength for fr,s, which is public data of the Route
2 Update Protocol.
3 − Set SoftQRABfr,s,m = 0.
4 − Set SlotFRABfr,s,m = FRABr,n−1.
5 2. Update PilotStrengthfr,s,m: The access terminal shall update the PilotStrength (in
6 the linear domain) using an IIR filter with filter time constant
7 PilotStrengthFilterTC, where PilotStrength of fr,s is public data of the Route Update
8 Protocol.
9 3. Update SlotQRABfr,s,m: The access terminal shall generate SlotQRABfr,s,m by
10 filtering (IIR filter with filter time constant QRABFilterTC) the soft RA bit from fr,s
11 for Reverse CDMA Channel r in slot m to generate SoftQRABfr,s,m, and then hard-
12 limiting SoftQRABfr,s,m to generate SlotQRABfr,s,m. The hard-limiter maps positive
13 input values to +1 and negative or zero input values to −1.
14 4. Update SlotFRABfr,s,m: The access terminal shall generate SlotFRABfr,s,m by
15 filtering (IIR filter with filter time constant FRABFilterTC) the soft RA bit for
16 Reverse CDMA Channel r from fr,s in slot m (SoftRABfr,s,m).
17 If any slot of sub-frame n overlaps with a Reverse Link Silence Interval, the access terminal
18 shall perform the following operations at the start of every slot of sub-frame n for each
19 Reverse CDMA Channel r with a monitored RAB that is in the access terminal’s set RCn,
20 and for each fr,s that is in the access terminal’s set FCr,n:
21 1. Update PilotStrengthfr,s,m: The access terminal shall update the PilotStrength (in
22 the linear domain) using an IIR filter with filter time constant
23 PilotStrengthFilterTC, where PilotStrength of fr,s is public data of the Route Update
24 Protocol.
25 2. Update SlotQRABfr,s,m: Set SoftQRABfr,s,m = 0, and and SlotQRABfr,s,m, = −1.
26 3. Update SlotFRABfr,s,m: Set SlotFRABfr,s,m = max(0, SlotFRABfr,s,m-1).
27 The access terminal shall perform the following operations at the start of every slot m of
28 sub-frame n for each Reverse CDMA Channel r without a monitored RAB that is in the
29 access terminal’s set RCn, and for each fr,s that is in the access terminal’s set FCr,n:
30 1. Update PilotStrengthfr,s,m: This value does not change as part of this operation.
31 2. Update SlotQRABfr,s,m: Set SoftQRABfr,s,m = 0 and SlotQRABfr,s,m = −1.
32 3. Update SlotFRABfr,s,m: This value does not change as part of this operation.
33 The access terminal shall perform the following operations at the start of each sub-frame n:
34 1. Determine the maximum allowed outflow from the data token bucket for each
35 active MAC flow i
36 − The access terminal shall determine the maximum allowed outflow from the
37 data token bucket for each active MAC flow i using the following equation:
9-400
1 PotentialDataBucketOutflowi,n =max(DataTokenInflowi + DataBucketLeveli,n, 0)
2 2. Update Data Token Bucket Level for each active MAC flow i
3 − The access terminal shall set the Data Token Bucket Level for the next sub-frame
4 as specified by the following equation132:
5 DataBucketLeveli,n+1 = min(DataTokenInflowi + DataBucketLeveli,n –
6 SumTransmittedDatai,n, DataBucketLevelMaxi )
7 where SumTransmittedDatai,n is the sum of di,r,n over all Reverse CDMA Channels
8 r that are in the access terminal’s set RCn for active MAC flow i in sub-frame n, and
9 di,r,n is the number of octets from an active MAC flow i contained in the payload in
10 Reverse CDMA Channel r.
11 3. Update PilotStrengthf,n for each pilot f that is in set SRn but not in FCr,n for any
12 Reverse CDMA Channel r:
13 − The access terminal shall sample PilotStrengthf,m for each f in set SRn but not
14 in FCr,n for any Reverse CDMA Channel r at sub-frame n to generate
15 PilotStrengthf,n.
17 in each Reverse CDMA Channel r in set RCn to determine allocation for that sub-frame:
18 1. Update PilotStrengthfr,s,n for each fr,s in set FCr,n
19 − The access terminal shall sample PilotStrengthfr,s,m for each fr,s in set FCr,n at
20 sub-frame n to generate PilotStrengthfr,s,n.
21 2. Update QRABr,n
22 − The access terminal shall sample SlotQRABfr,s,m from each fr,s in set FCr,n at
23 sub-frame n to generate QRABfr,s,n.
24 − The access terminal shall determine QRABr,n from QRABfr,s,n at sub-frame n

26 + The access terminal shall set QRABnr,n = +1 (Loaded) if QRABfr,s,n == +1
27 (Loaded) for any fr,s in the access terminal’s set FCr,n at sub-frame n.
28 + The access terminal shall set QRABnr,n = −1 (UnLoaded) if QRABfr,s,n == −1

29 (UnLoaded) for every fr,s in the access terminal’s set FCr,n at sub-frame n.
30 3. Update QRABpsr,n
31 − The access terminal shall determine QRABpsr,n from QRABfr,s,n at sub-frame n

132 Note that DataBucketLevel

i,n+1 is allowed to take on a negative value
9-401
1 + The access terminal shall set QRABpsr,n = +1 (Loaded) if QRABfr,s,n == +1 for a

2 fr,s in the access terminal’s set FCr,n, which satisfies one or more of the
4 − PilotStrengthfr,s,n is the maximum value of PilotStrengthf’r,s,n over all f’r,s in
5 the set FCr,n at sub-frame n
6 − The DRCLock bit for Reverse CDMA Channel r from the cell associated with
7 pilotPN s is ‘0’ (Out-of-lock) and PilotStrengthfr,s,n is greater than
9 − The DRCLock bit for Reverse CDMA Channel r from the cell associated with
10 pilotPN s is ‘1’ (In-lock) and PilotStrengthfr,s,n is greater than
12 + The access terminal shall set QRABpsr,n = −1 (UnLoaded) if none of the
14 4. Update FRABr,n
15 − The access terminal shall sample SlotFRABfr,s,m at sub-frame n to generate

16 FRABfr,s,n. The access terminal shall set FRABr,n to the maximum real-
17 numbered value of FRABfr,s,n received over all fr,s in the access terminal’s set
18 FCr,n at sub-frame n. FRABr,n is thus within the range [− 1(Unloaded), +
19 1(Loaded)].
20 5. Initialization for each active MAC flow i
21 − For each active MAC flow i the access terminal shall perform the following
22 steps:
23 + If LastBucketLevelMaxi,r is NULL for all assigned Reverse CDMA Channels r
24 and BucketLevelMaxi is not NULL then the access terminal shall perform the
25 following:
26 − Set DataBucketLeveli = DataBucketLevelMaxi
27 − For each assigned Reverse CDMA Channel r, the access terminal shall
29 − Set BucketLeveli,r,n = 0.
30 − Set T2PInflowi,r,n−1 = 10^(T2PInflowmini/10).
31 − Set TT2PHoldi,r,n−1 = 0.
32 − Set T2POutflow i,r,n−1 = 0.
33 − Set BucketLevelSati,r,n = 10^(BucketLevelMaxi/10).
34 + For each assigned Reverse CDMA Channel r, the access terminal shall perform
35 the following:
36 − Set LastBucketLevelMaxi,r = BucketLevelMaxi.
9-402
1 6. Initialization for each active MAC flow i upon assignment of a new Reverse CDMA
2 Channel r and receipt of the RTCAck message for r at sub-frame n at the access
3 terminal
4 − For each active MAC flow i upon assignment of a new Reverse CDMA Channel
5 r at sub-frame n the access terminal shall perform the following steps:
6 + If LastBucketLevelMaxi is NULL and BucketLevelMaxi is not NULL then the
8 − Set BucketLeveli,r,n = 0.
9 − Set T2PInflowi,r,n−1 = 10^(T2PInflowmini,r/10).
10 − Set TT2PHoldi,r,n−1 = 0.
11 − Set T2POutflowi,r,n−1 = 0.
12 − Set BucketLevelSati,r,n = 10^(BucketLevelMaxi/10).
13 − Set LastBucketLevelMaxi,r = BucketLevelMaxi.
14 7. Update buckets with inflows for each active MAC flow i.

15 − Determine ΔT2PInflowi,r,n
16 + The access terminal shall set QRABi,r,n = +1 (Loaded) if either of the following
18 − QRABSelecti == +1 for MAC flow i and QRABpsr,n == +1 at sub-frame n
19 − QRABSelecti == 0 for MAC flow i and QRABr,n == +1 at sub-frame n
20 + If none of the conditions immediately above are satisfied, the access terminal
21 shall set QRABi,r,n = −1 (Unloaded)
22 + If SRn contains a serving sector pilot, the access terminal shall set
23 PilotStrengthn to the value of PilotStrengthf,n for the serving sector pilot f in
24 set SRn.
25 + If SRn does not contain a serving sector pilot, the access terminal shall set
26 PilotStrengthr,n to be the maximum value of PilotStrengthf,n over all pilots f
27 in set SRn at sub-frame n
28 + If TT2PHoldi,r,n−1 == 0 and QRABi,r,n == +1 the access terminal shall compute

29 ΔT2PInflowi,r,n using the following equation:
30 ΔT2PInflowi,r,n= −1 × 10^(T2PDni,r(10 × log10(T2PInflowi,r,n−1) +
31 PilotStrengthr(PilotStrengthn), FRABr,n)/10)
32 + If TT2PHoldi,r,n−1 == 0 and QRABi,r,n == −1 and BucketLeveli,r,n <
33 BucketLevelSati,r,n, then the access terminal shall compute ΔT2PInflowi,r,n
9-403
1 ΔT2PInflowi,r,n= +1 × 10^(T2PUpi,r(10 × log10(T2PInflowi,r,n−1) +

2 PilotStrengthr(PilotStrengthn), FRABr,n)/10)
3 + If TT2PHoldi,r,n−1 == 0 and QRABi,r,n == −1 and BucketLeveli,r,n ≥

4 BucketLevelSat i,r,n, then the access terminal shall set ΔT2PInflowi,r,n using
6 ΔT2PInflowi,r,n = 0
7 + The access terminal shall set ΔT2PInflowi,r,n = 0 if the access terminal is not
8 receiving the RAB for Reverse CDMA Channel r or sub-frame n overlaps with a
9 Reverse Link Silence Interval.
10 − Update T2P Inflows
11 + If TT2PHoldi,r,n−1 == 0, then the access terminal shall update T2PInflowi,r,n,
12 using the following equations if receiving the RAB for Reverse CDMA Channel
13 r during sub-frame n.
14 T2PInflowi,r,n = (1 − (1/T2PFilterTCi)) × T2PInflowi,r,n−1 + (1/T2PFilterTCi) ×

15 T2POutflowi,r,n−1 + ΔT2PInflowi,r,n
16 T2PInflowi,r,n = max( T2PInflowi,r,n , 10^(T2PInflowmini,r / 10))
17 T2PInflowi,r,n = min( T2PInflowi,r,n , 10^(T2PInflowmaxi,r / 10))
18 + If TT2PHoldi,r,n−1 == 0, then the access terminal shall update T2PInflowi,r,n if

19 not receiving the RAB for Reverse CDMA Channel r during sub-frame n using
20 the following equations:
21 T2PInflowi,r,n = (1 − (1/T2PNoTxFilterTC)) × T2PInflowi,r,n−1
22 T2PInflowi,r,n = max(T2PInflowi,r,n, 10^(T2PInflowmini,r / 10))
23 T2PInflowi,r,n = min(T2PInflowi,r,n, 10^(T2PInflowmaxi,r / 10))
24 + If TT2PHoldi,r,n−1 > 0, then the access terminal shall maintain the inflow
25 T2PInflowi,r,n as the inflow in the previous sub-frame T2PInflowi,r,n−1.
26 + If TT2PHoldi,r,n−1 > 0, the access terminal shall decrement the value of

27 TT2PHold by 1 sub-frame using the following equation:
28 TT2PHoldi,r,n = TT2PHoldi,r,n−1 −1
29 8. Determine sub-packet transmission for sub-frame n
9-404
1 − If the access terminal transmitted the first, second or third sub-packet of a

2 packet in sub-frame n−3 in Reverse CDMA Channel r, and the access terminal
3 did not receive a positive acknowledgment from the access network for the
4 sub-packet transmitted in sub-frame n−3 in Reverse CDMA Channel r, and the
5 sub-packet index of the next (second, third, or fourth) sub-packet is not
6 greater than MaxNumSubPacketsIr, where I is the interlace offset of sub-frame
7 n in Reverse CDMA Channel r, then the access terminal shall transmit the
8 next (second, third or fourth) sub-packet of the packet in sub-frame n in
9 Reverse CDMA Channel r. Otherwise, the access terminal shall not transmit
10 the next sub-packet of the packet in sub-frame n in Reverse CDMA Channel r.
11 The reverse-link interlace offset I in Reverse CDMA Channel r for a sub-packet
12 starting in slot T is specified as I = (T - FrameOffset)/4 mod 3, where T is the
13 CDMA System Time in slots and 0 ≤ I ≤ 2
14 − If the access terminal transmits a new packet in sub-frame n in Reverse CDMA
15 Channel r, it shall determine the packet size, transmission mode and contents
16 of the new packet in accordance with 9.13.6.1.6.1.1
18 Channel r with packet size PSr in High Capacity mode, the access terminal
19 shall set the variables PktTxT2Pr,n,0, PktTxT2Pr,n,1, PktTxT2Pr,n,2, and
20 PktTxT2Pr,n,3 in accordance with the following equations:
21 PktTxT2Pr,n,N = T2PHiCapPreTransitionPSr if N ≤ HiCapT2PTransitionPSr
22 PktTxT2Pr,n,N = T2PHiCapPostTransitionPSr if N > HiCapT2PTransitionPSr

24 Channel r with packet size PSr in Low Latency mode, the access terminal shall
25 set the variables PktTxT2Pr,n,0, PktTxT2Pr,n,1, PktTxT2Pr,n,2, and
26 PktTxT2Pr,n,3 in accordance with the following equations:
27 PktTxT2Pr,n,N = T2PLoLatPreTransitionPSr if N ≤ LoLatT2PTransitionPSr
28 PktTxT2Pr,n,N = T2PLoLatPostTransitionPSr if N > LoLatT2PTransitionPSr
29 9. Determine TxT2Pmacr,n and TxT2Pr,n
30 − If the access terminal transmits sub-packet N of a Reverse Traffic Channel

31 packet in sub-frame n in Reverse CDMA Channel r, the access terminal shall
32 set TxT2Pmacr,n and TxT2Pmacr,n using the following equation133:
33 TxT2Pmacr,n = 10^(PktTxT2Pr,n − 3 × N, N / 10)
34 TxT2Pr,n = 10^((PktTxT2Pr,n − 3 × N, N+ DeltaT2Pr) / 10)
35 10. Update T2P outflows for each active MAC flow i
133 n − 3 × N refers to the first sub-frame of the packet that is currently being transmitted in sub-
frame n.
9-405

2 packet in sub-frame n in Reverse CDMA Channel r and physical layer packet
3 size PSr is greater than or equal to AuxiliaryPilotChannelMinPayload, the
4 bucket outflows in Reverse CDMA Channel r shall be specified by the following
5 equation:
6 T2POutflowi,r,n = ((di,r,n / SumPayloadr,n) × TxT2Pr,n) × (1 +
7 10^(AuxiliaryPilotChannelGain / 10))
8 where di,r,n is the number of octets from an active MAC flow i contained in the
9 payload in Reverse CDMA Channel r and SumPayloadr,n is the sum of di,r,n over all
10 active MAC flows i.
12 packet in sub-frame n in Reverse CDMA Channel r and physical layer packet
13 size PSr is less than AuxiliaryPilotChannelMinPayload, the bucket outflows in
14 Reverse CDMA Channel r shall be specified by the following equation:
15 T2POutflowi,r,n = (di,r,n / SumPayloadr,n) × TxT2Pr,n
16 where di,r,n is the number of octets from an active MAC flow i contained in the
17 payload in Reverse CDMA Channel r and SumPayloadr,n is the sum of di,r,n over
18 all active MAC flows i.
19 − If the access terminal does not transmit a sub-packet of a Reverse Traffic
20 Channel packet in sub-frame n in Reverse CDMA Channel r, the bucket
21 outflows in Reverse CDMA Channel r shall be specified by the following
22 equation:
23 T2POutflowi,r,n = 0
24 11. Update Bucket Level for each active MAC flow i

25 − The access terminal shall determine BucketLevelSati,r,n+1 for each active
26 MAC flow i using the following equation:
27 BucketLevelSati,r,n+1 = min(BurstDurationFactori × BucketFactori(10 ×
28 log10(T2PInflowi,r,n), FRABr,n) × T2PInflowi,r,n, 10^( BucketLevelMaxi / 10))
29 − If the access terminal is not receiving the RAB for Reverse CDMA Channel r
30 during sub-frame n or any slot of sub-frame n overlaps with the Reverse Link
31 Silence Interval, then the access terminal shall set BucketLeveli,r,n+1 = 0.
32 − If the access terminal is receiving the RAB for Reverse CDMA Channel r during
134 Note that BucketLevel

i,n+1 is allowed to take on a negative value.
9-406
1 BucketLeveli,r,n+1 = min(BucketLeveli,r,n + T2PInflowi,r,n – T2POutflowi,r,n ,

2 BucketLevelSat i,r,n+1)
3 12. RRIChannelGain computation

4 − The access terminal shall set the RRI Channel Gain135 for sub-packet N ( 0 ≤ N
5 ≤ 3) of a Reverse Traffic Channel packet transmitted in sub-frame n in Reverse
6 CDMA Channel r using the following equation:
7 RRIChannelGainr,n = RRIChannelGainPreTransitionM, if N ≤ M
8 RRIChannelGainr,n = RRIChannelGainPostTransitionM, if N > M
9 If transmitting the packet in Low Latency Mode in Reverse CDMA Channel r, M

10 is equal to the T2PTransition value LoLatT2PTransitionPSr. Otherwise, M is
11 equal to the T2PTransition value HiCapT2PTransitionPSr.
12 − The access terminal shall set the RRI Channel Gain in sub-frame n in Reverse
13 CDMA Channel r using the following equation if the access terminal does not
14 transmit any sub-packet in sub-frame n in Reverse CDMA Channel r:
15 RRIChannelGainr,n = RRIChannelGainPreTransition3
16 13. When the access terminal transmits a security layer packet, the access terminal
21 10.13.6.1.6.1.19.13.6.1.6.1.1 Packet size and Transmission Mode Selection Requirements

22
135 The mapping between the T2P transition value and the RRI Channel Gain is shown in the table
below.
T2PTransitionValue and RRIChannelGain mapping
T2PTransitionValue sub-packet N
M 0 1 2 3
0 PreTransition0 PostTransition0 PostTransition0 PostTransition0
1 PreTransition1 PreTransition1 PostTransition1 PostTransition1
2 PreTransition2 PreTransition2 PreTransition2 PostTransition2
3 PreTransition3 PreTransition3 PreTransition3 PreTransition3
9-407
1 10.13.6.1.6.1.1.19.13.6.1.6.1.1.1 Procedures for Reverse CDMA Channel r

4 TxT2PHiCapNominalPS=maxN(10 × log10(10^(TxT2PHiCapPSN/10)))

9 TxT2PHiCapNominalPS = maxN(10 × log10(10^(TxT2PHiCapPSN/10) × (1 +

15 TxT2PLoLatNominalPS, = maxN(10 × log10(10^(TxT2PLoLatPSN/10)))

20 TxT2PLoLatNominalPS = maxN(10 × log10(10^(TxT2PLoLatPSN/10) × (1 +

24 5. The access terminal shall set PotentialT2POutflowi,r,HC for each active MAC flow i
25 in Reverse CDMA Channel r using the following equation:
26 PotentialT2POutflowi,r,HC = max (0, min((1 + AllocationStagger × rr,n) ×
27 (BucketLeveli,r,n / 4 + T2PInflowi,r,n) , BucketFactori(10 × log10(T2PInflowi,r,n),
28 FRABr,n) × T2PInflowi,r,n))
29 6. The access terminal shall set PotentialT2POutflowi,r,LL for each active MAC flow i
30 in Reverse CDMA Channel r using the following equation:
31 PotentialT2POutflowi,r,LL = max (0, min((1 + AllocationStagger × rr,n) ×
32 (BucketLeveli,r,n / 2 + T2PInflowi,r,n) , BucketFactori(10 × log10(T2PInflowi,r,n),
33 FRABr,n) × T2PInflowi,r,n))
34 7. The access terminal shall set PotentialT2POutflowi,r,HC = 0 and

35 PotentialT2POutflowi,r,LL = 0 for each active MAC flow i in Reverse CDMA Channel
9-408
1 r if PotentialDataBucketOutflowi,n is equal to 0 for active MAC flow i at sub-frame

2 n.
3 8. The access terminal shall determine T2PConversionFactorHC by maximizing the
4 T2PConversionFactor associated with the High Capacity mode over all permitted
5 Physical Layer packet sizes, using the following equation:
6 T2PConversionFactorHC = maxPS(PacketSizePSr / 10^(TxT2PHiCapNominalPS /10))
7 where PacketSizePSr is in octets.

8 9. The access terminal shall determine T2PConversionFactorLL by maximizing the
9 T2PConversionFactor associated with the Low Latency mode over all permitted
10 packet sizes, using the following equation:
11 T2PConversionFactorLL = maxPS(PacketSizePSr / 10^(TxT2PLoLatNominalPS /10))
12 where PacketSizePSr is in octets.

13 10. The access terminal shall determine QOutflowi,r,HC for each active MAC flow i in
14 Reverse CDMA Channel r by using the following equation:
15 QOutflowi,r,HC = min(Qi,n, PotentialT2POutflowi,r,HC × T2PConversionFactorHC)
16 11. The access terminal shall construct the set F to be the set of all active MAC flows
18 12. The access terminal shall determine SumQOutflowr in Reverse CDMA Channel r
19 by summing QOutflowi,r,HC over all active MAC flows i in Reverse CDMA Channel
20 r from the set F with TMi == HiCap.
21 13. The access terminal shall construct the set Fr,LL for Reverse CDMA Channel r
22 using the following rules:
23 − If the transmission mode TMi of any active MAC flow i with non-empty queue
24 (i.e., Qi,n > 0) at sub-frame n is LoLat or MaxNumSubPacketsIr < 3 for the
25 interlace of sub-frame n in Reverse CDMA Channel r, then set TMr,min =
26 LoLat. Otherwise set TMr,min = HiCap.
27 − The set Fr,LL shall be equal to the set F if TMr,min == HiCap, and the packet
28 size for transmission at sub-frame n in Reverse CDMA Channel r is greater
29 than or equal to PayloadThresh.
30 − The set Fr,LL shall be the empty set if TMr,min == HiCap, and the packet size
31 for transmission at sub-frame n in Reverse CDMA Channel r is less than
32 PayloadThresh.
33 − The set Fr,LL shall be equal to the set F if TMr,min == LoLat, and one or more
34 of the following conditions are satisfied in Reverse CDMA Channel r:
35 + FRABr,n < FRABlow
36 + SumQOutflowr ≥ MergeThreshold
9-409
1 − If TMr,min == LoLat, FRABr,n ≥ FRABlow, and SumQOutflowr <

2 MergeThreshold, then the set Fr,LL shall consist of all active MAC flows i from
3 the set F that satisfy one or more of the following conditions in Reverse CDMA
4 Channel r:
5 + TMi == LoLat
6 + QOutflowi,r,HC ≥ MergeThresholdi
8 10.13.6.1.6.1.1.29.13.6.1.6.1.1.2 Requirements for Reverse CDMA Channel r
9 1. If the access terminal starts transmission of a new packet in sub-frame n in

10 Reverse CDMA Channel r with packet size PSr in High Capacity mode with di,r,n
11 octets from each active MAC flow i, the access terminal shall ensure that all of the
12 following conditions are satisfied in Reverse CDMA Channel r:
13 − Condition 1:
14 PSr ≤ min(PermittedPayloadPS1r_1, PermittedPayloadPS2r_2,
15 PermittedPayloadPS3r_3)
16 where PSkr is the Physical Layer packet size transmitted in sub-frame n - k in

17 Reverse CDMA Channel r.
18 − Condition 2:
19 10^(TxT2PHiCapNominalPSr/10) ≤ max(10^(TxT2Pmin / 10),
20 ∑i∈F(PotentialT2POutflowi,r,HC))
21 − Condition 3:
22 If PSr < AuxiliaryPilotChannelMinPayload, then
23 max(10^(T2PHiCapPreTransitionPSr / 10), 10^(T2PHiCapPostTransitionPSr / 10)) ≤

24 10^(TxT2Pmaxr(PilotStrengthn) / 10).
25 If PSr ≥ AuxiliaryPilotChannelMinPayload, then
26 (1 + 10^(AuxiliaryPilotChannelGain/10)) × max(10^(T2PHiCapPreTransitionPSr /
27 10), 10^(T2PHiCapPostTransitionPSr / 10)) ≤ 10^(TxT2Pmaxr(PilotStrengthn) / 10).
28
29 − Condition 4: No packet with lower TxT2PHiCapNominalPSr is able to carry a

31 ∑ i∈F min(di,r,n , T2PConversionFactorHC × PotentialT2POutflowi,r,HC)
32 − Condition 5:
33 HiCapTerminationTargetPSr ≤ MaxNumSubPacketsIr
34 where Ir is the reverse-link interlace offset of sub-frame n in Reverse CDMA

35 Channel r.
9-410
1 − Condition 6: Packet size PSr can be accommodated by the available transmit

2 power and such that transmit power differential across adjacent reverse link
3 CDMA channels as specified by MaxRLTxPwrDiff is satisfied, where
4 MaxRLTxPwrDiff is public data of the subtype 3 Physical Layer Protocol.
5 − Condition 7: Packet size PSr is not larger than what is allowed by the
6 MaxPacketSize attribute.
7 2. If the access terminal starts transmission of a new packet in sub-frame n in Reverse
8 CDMA Channel r with packet size PSr in Low Latency mode with di,r,n octets from
9 each active MAC flow i, then the access terminal shall ensure that all of the following
10 conditions are satisfied in Reverse CDMA Channel r:
11 − Condition 1:
12 PSr ≤ min(PermittedPayloadPS1r_1, PermittedPayloadPS2r_2,
13 PermittedPayloadPS3r_3)
14 where PSkr is the Physical Layer packet size transmitted in sub-frame n - k

15 inReverse CDMA Channel r.
16 − Condition 2:
17 10^(TxT2PLoLatNominalPSr/10) ≤ max( 10^( TxT2Pmin / 10 ), ∑i∈Fr,LL (
18 PotentialT2POutflowi,r,LL ) )
19 − Condition 3:
20 If PSr < AuxiliaryPilotChannelMinPayload, then
21 max(10^(T2PLoLatPreTransitionPSr / 10), 10^(T2PLoLatPostTransitionPSr / 10) ) ≤

22 10^(TxT2Pmaxr(PilotStrengthn) / 10).
23 If PSr ≥ AuxiliaryPilotChannelMinPayload, then
24 (1 + 10^(AuxiliaryPilotChannelGain/10)) × max(10^(T2PLoLatPreTransitionPSr /
25 10), 10^(T2PLoLatPostTransitionPSr / 10)) ≤ 10^(TxT2Pmaxr(PilotStrengthn) / 10).
26
27 − Condition 4: No packet with lower TxT2PLoLatNominalPSr is able to carry a

29 ∑ i∈Fr,LL min( di,r,n , T2PConversionFactorLL × PotentialT2POutflowi,r,LL )
30 − Condition 5:
31 LoLatTerminationTargetPSr ≤ MaxNumSubPacketsIr
32 where Ir is the reverse-link interlace offset of sub-frame n in Reverse CDMA

33 Channel r.
9-411
1 − Condition 6: Packet size PSr can be accommodated by the available transmit

2 power and such that transmit power differential across adjacent reverse link
3 CDMA channels as specified by MaxRLTxPwrDiff is satisfied, where
4 MaxRLTxPwrDiff is public data of the subtype 3 Physical Layer Protocol.
5 − Condition 7: Packet size PSr is not larger than what is allowed by the
6 MaxPacketSize attribute.
7 10.13.6.1.6.1.29.13.6.1.6.1.2 Messages
8 10.13.6.1.6.1.2.19.13.6.1.6.1.2.1 Request message

14 1. ReqRatio is not equal to 0 and the access terminal has transmitted (1 / ReqRatio –
15 1) × RequestPktSize bits of data on the traffic channel since the last Request packet
17 message.
18 2. MaxReqInterval is not equal to zero and MaxReqInterval frames have elapsed since
19 the last transmission of a Request packet.
20 10.13.6.1.6.1.39.13.6.1.6.1.3 Grant message

21 If the access terminal receives a Grant message the access terminal shall update the
22 following parameters for each MAC flow i in each Reverse CDMA Channel r for which the
23 Grant message is received.
24 • T2PInflowi,r,n with 10x/10, where x is the value of T2PInflow in units of dB.
25 • BucketLeveli,r,n with 10x/10, where x is the value of BucketLevel in units of dB.
26 • TT2PHoldi,r,n with 4 × x, where x is the value of TT2PHold in units of frames.
27 10.13.6.1.6.1.3.19.13.6.1.6.1.3.1 CarrierRequest message

28 The access terminal sends the CarrierRequest message to request allocation or de-
29 allocation of Reverse CDMA Channels from the access network. The access terminal shall
30 generate a RouteUpdate.SendRouteUpdate command upon sending a CarrierRequest
31 message.
32 10.13.6.1.6.1.3.29.13.6.1.6.1.3.2 Reverse CDMA Channel Dropping

33 The access terminal shall stop transmission (drop) on a Reverse CDMA Channel with the
34 lowest ReverseChannelDroppingRank if the access terminal is assigned multiple Reverse
35 CDMA Channels and it determines that it does not have sufficient power to sustain all the
36 assigned Reverse CDMA Channels. The ReverseChannelDroppingRank associated with a
37 Reverse CDMA Channel is public data of the Route Update Protocol.
9-412
1 Upon receiving a ForwardTrafficChannelMAC.ReverseTrafficChannelRestartTimerExpired

2 indication, the access terminal shall stop transmission (drop) on the Reverse CDMA
3 Channel(s) included as arguments along with the indication.
4 Upon dropping a Reverse CDMA Channel, the access terminal shall send a
5 ReverseCDMAChannelDropped message with the appropriate ReasonCode, and generate a
6 ReverseLinkDropped indication with arguments indicating which Reverse CDMA Channels
7 were dropped. Once an access terminal transmits a ReverseCDMAChannelDropped
8 message, transmission on the Reverse CDMA Channels whose drop is indicated in the
9 message is not permitted until the access network re-assigns the Reverse CDMA Channels
10 to the access terminal (e.g. with a TrafficChannelAssignment message).
11 10.13.6.1.6.1.49.13.6.1.6.1.4 Reverse Logical Channels

12 There are NRTCMPMACCarrierMax Reverse Logical Channels, and each acquired Reverse CDMA
13 Channel is associated with a unique Reverse Logical Channel. MAC flow and access
14 terminal attributes which vary across Reverse CDMA Channels are specified for each
15 Reverse Logical Channel for use in the associated Reverse CDMA Channel. MAC flow and
16 access terminal attribute defaults shall be applied across all Reverse Logical Channels.
17 10.13.6.1.6.1.59.13.6.1.6.1.5 Power Control

18 The access terminal shall control the reverse link transmit power in each assigned Reverse
19 CDMA Channel in accordance with the requirements of the Physical Layer Protocol.

24 The access terminal should not start transmission of a packet if a sub-frame within its
25 termination target overlaps with a Reverse Link Silence Interval. The Reverse Link Silence
26 Interval is defined as the time interval of duration ReverseLinkSilenceDuration frames that
27 starts at times T and it satisfies the following equation:

33 The access network uses the RA bit to reflect the reverse link sector loading in each
34 Reverse CDMA Channel. The access network should transmit the Reverse Activity Channel
35 with a gain equal to or greater than that specified by RAChannelGain. In the following
36 requirements, PS takes on the following values: 128, 256, 512, 768, 1024, 1536, 2048,
37 3072, 4096, 6144, 8192, and 12288. Each value of PS represents a physical layer packet
38 size, expressed in bits.
9-413
1 The access network shall set the value of T2PHiCapPreTransitionPS136 to be less than or
2 equal to the value of T2PLoLatPreTransitionPS137.
3 The access network shall set the value of LoLatTerminationTargetPS to be less than or
4 equal to the value of HiCapTerminationTargetPS.
5 The access network should set the values of LoLatTerminationTargetPS such that the
6 packet transmitted by the access terminal with packet size PS in the Low Latency mode is
7 received by the access network within LoLatTerminationTargetPS sub-frames with a failure
9 The access network should set the values of HiCapTerminationTargetPS such that the
10 packet transmitted by the access terminal with packet size PS in the High Capacity mode is
11 received by the access network within HiCapTerminationTargetPS sub-frames with a failure
13 If the access network does not receive an RTCAckAck message or a Reverse Traffic Channel
14 packet on the corresponding Reverse CDMA Channel within an implementation specific
15 time interval of entering the Open state, then the access network should re-transmit the
16 RTCAck message an implementation specific number of times.
17 10.13.6.1.6.2.19.13.6.1.6.2.1 ReverseCDMAChannelDropped message

18 Upon receiving the ReverseCDMAChannelDropped message, the access network shall send
19 a ReverseCDMAChannelDroppedAck message and generate a ReverseLinkDropped
20 indication with argument indicating which Reverse CDMA Channels were dropped.
21 10.13.6.1.6.2.29.13.6.1.6.2.2 Grant Message

22 The access network may transmit Grant messages at any time. The Grant messages may
23 be transmitted autonomously or in response to Request messages received from access
24 terminals. The Grant message is transmitted by the access network to the access terminal
25 on the Forward Traffic Channel. The timing and content of the Grant message is
26 determined by the access network. The Grant message contains “grants” for one or more
27 MAC flows belonging to one access terminal, and for one or more Reverse CDMA Channels.
28 A per MAC flow and per Reverse CDMA Channel resource allocation contains the following:
29 − T2PInflow
30 − BucketLevel
31 − TT2PHold
136 The access network typically sets the values of T2PHiCapPreTransitionPS and
T2PHiCapPostTransitionPS such that T2PHiCapPreTransitionPS is greater than
T2PHiCapPostTransitionPS.
137 The access network typically sets the values of T2PLoLatPreTransitionPS and
T2PLoLatPostTransitionPS such that T2PLoLatPreTransitionPS is greater than
T2PLoLatPostTransitionPS.
9-414

4
Field Length (bits)
TransmissionMode 1

9 TransmissionMode If the MAC Layer packet is transmitted in the Low Latency Mode,
10 then the access terminal shall set this field to ‘1’. Otherwise, the
12 10.13.6.2.29.13.6.2.2 RTCAck
14 acquired one or more of the assigned Reverse CDMA Channels, and that the access
15 terminal can start traffic transmissions on the indicated Reverse CDMA Channels.
16
Field Length (bits)

MessageID 8
RTCAckID 8
NumReverseChannels 4
(NumReverseChannels + 1) occurrences of the
ReverseChannel 24
ReverseLogicalChannel 4
needed)
18 RTCAckID The access network shall set this field to one more (modulo 256) than
19 the RTCAckID field of the previous RTCAck message. If this is the
20 first RTCAck message being sent by the access network, then the
9-415
3 Reverse CDMA Channels for which the message is transmitted.
4 ReverseChannel The access network shall set this field to the identifier channel record
5 that specifies the assigned reverse link channel is assigned to the
6 Reverse CDMA Channel assigned to the access terminal that has
7 been acquired by the access network.
8 ReverseLogicalChannel
9 The access network shall set this field to the logical channel
10 associated with the Reverse CDMA Channel record specified in the
11 previous field, in the range from 0 to NRTCMPMACCarrierMax-1.
12 Reserved The access network shall add Reserved bits to make the length of the
14 network shall set these bits to ‘0’. The access terminal shall ignore
15 this field.
Best Effort
Channels FTC SLP
Reliable
16 10.13.6.2.3RTCAckAck
17 The access terminal sends the RTCAckAck message to acknowledge reception of the
18 RTCAck message.
19
Field Length (bits)

MessageID 8
RTCAckID 8
21 RTCAckID The access terminal shall this field to the RTCAckID field of the
22 corresponding RTCACk message.
23
24 10.13.6.2.49.13.6.2.3 CarrierRequest
25 The access terminal sends the CarrierRequest message to request allocation or de-
26 allocation of additional Reverse CDMA Channels from the access network
27
9-416
Field Length (bits)

MessageID 8
Reserved 4
3 The access terminal shall set this field to one less than the total
4 number of Reverse CDMA Channels it is requesting be allocated to it.
7
9 10.13.6.2.59.13.6.2.4 ReverseCDMAChannelDropped
10 The access terminal sends the ReverseCDMAChannelDropped message to notify the access
11 network that it has dropped one or more Reverse CDMA Channels.
12
Field Length (bits)

MessageID 8
TransactionID 8
(NumReverseChannels + 1) occurrences of the
ReverseChannel 24
ReasonCode 4
Reserved 0 or 4
15 ReverseCDMAChannelDropped message sent.
9-417
2 The access terminal shall set this field to one less than the number of
4 ReverseChannel The access terminal shall set this field to the identifier that is
5 assigned to the Reverse CDMA Channel assigned to the access
6 terminal that has been dropped by the access terminal.
7 ReasonCode The access terminal shall set this field to the reason it has dropped
8 the Reverse CDMA Channel. Table 9.13.6.2.4-1 specifies the
9 ReasonCode definitions.
10 Table 9.13.6.2.4-1. Reason Codes

11
ReasonCode Meaning
0x0 Headroom Limitation
0x1 FTCMAC DRC Supervision
0x2 ReverseAcquisition timer expired
0x3-0xf Reserved
12
13 Reserved The access terminal shall include reserved bits to make the
14 length of the entire message equal to an integer number of octets.
15 The access terminal shall set this field to zero. The access
16 network shall ignore this field.
17 10.13.6.2.69.13.6.2.5 ReverseCDMAChannelDroppedAck
18 The access network sends the ReverseCDMAChannelDroppedAck message to acknowledge
19 the receipt of a ReverseCDMAChannelDropped message.
20
Field Length (bits)

MessageID 8
TransactionID 8
23 corresponding ReverseCDMAChannelDropped message.
9-418
1 10.13.6.2.79.13.6.2.6 Request
5
Field Length (bits)

MessageID 8
ATTotalPilotTransmission 8
NumMACFlows 5
NumMACFlows occurrences of the following two
fields:
MACFlowID 4
QueueLength 8
Reserved 3
7 ATTotalPilotTransmission
8 The access terminal shall set this field to the current total average
9 transmission power of pilot(s) when the transmitter is enabled in
10 units of 0.5 dBm. This field is expressed as a two’s complement
11 signed number.
12
14 for which a request is transmitted.
20 terminal shall specify this field as an 8-bit number as specified in
21 Table 9.13.6.2.6-1.
9-419
QueueLength QueueLength (octets)

Field
QL
0x00 zero
0xFF 2^(254/12 + 7) < QL + 96
x, else ⎣2^((x-1)/12 + 7)⎦ < QL + 96 ≤ ⎣2^(x/12 + 7)⎦
4
5 10.13.6.2.89.13.6.2.7 Grant
7 following parameters for one or more of the active MAC flows and for one or more of the
8 assigned Reverse CDMA Channels at the access terminal:
9 • T2PInflow
10 • BucketLevel
11 • TT2PHold
12
9-420
Field Length (bits)

MessageID 8
(NumReverseChannels occurrences + 1) of the following
fields:
ReverseLogicalChannel 4
NumMACFlows 4
(NumMACflows occurrences + 1) of the following fields:
MACFlowID 4
T2PInflow 8
BucketLevel 8
TT2PHold 6
Reserved 0-7 (as

needed)
5 ReverseLogicalChannel
6 The access network shall set this field to the logical channel
7 associated with the Reverse CDMA Channel for which flow grants are
8 specified, in the range from 0 to NRTCMPMACCarrierMax-1.
9 NumMACFlows The access network shall set this field to one less than the number of
10 MAC Flows for the Reverse CDMA Channel identified by
11 ReverseLogicalChannel for which the Grant is transmitted. The
12 access network shall specify this field as a 4-bit value in the range
13 0…15, inclusive. The access terminal shall support all valid values
14 for this field.
15 MACFlowID The access network shall set this field to the MAC Flow for which the
16 Grant is transmitted. The access network shall specify this field as a
17 4-bit value in the range 0…15, inclusive. The access terminal shall
19 T2PInflow The access network shall set this field to the average T2P for the MAC
20 flow identified by the corresponding MACFlowID for the Reverse
9-421
1 CDMA Channel identified by ReverseLogicalChannel. The access

2 network may set this field to 255 to indicate a value of -∞. Otherwise,
3 the access network shall specify this field as an 8-bit value in the
4 range of 0 to 63.5 dB in units of 0.25 dB. The access network shall
5 support all valid values of this field. The access terminal shall
9 CDMA Channel identified by ReverseLogicalChannel. The access
10 network may set this field to 255 to indicate a value of -∞. Otherwise,
11 the access network shall specify this field as an 8-bit value in the
12 range of 0 to 63.5 dB in units of 0.25 dB. The access terminal shall
13 support all valid values of this field.
14 TT2PHold The access network shall set this field to the interval of time for
17 CDMA Channel identified by ReverseLogicalChannel after receiving
18 the Grant message. The access network shall specify this field as a 6-
19 bit value in units of frames. The access terminal shall support all
20 valid values of this field.
23 shall set these bits to ‘0’.The access terminal shall ignore this field.
24
27 given attribute.
28
Field Length (bits)
MessageID 8
TransactionID 8
9-422

2
6
Field Length (bits)
MessageID 8
TransactionID 8
10
14
Field Length (bits)
MessageID 8
TransactionID 8
18
9-423
2 10.13.6.3.19.13.6.3.1 Commands Sent

4 • RouteUpdate.SendRouteUpdate
5 10.13.6.3.29.13.6.3.2 Indications
7 • ForwardTrafficChannelMAC.ReverseTrafficChannelRestartTimerExpired, with arguments
8 indicating the Reverse CDMA Channels for which the restart timer has expired.

12 • ARQModeCC
13 • AuxiliaryPilotChannelParameters
14 • AssociatedATConfigurationsCC
15 • AssociatedFlowConfigurationsNC
16 • AssociatedFlowsNN
17 • BucketFactorNN
18 • BucketLevelMaxNN
19 • BurstDurationFactorNN
20 • DataTokenInflowNNDataTokenBucketNN
21 •DataBucketLevelMaxNN
22 • MergeThreshold
23 • MergeThresholdNN
24 • PayloadThresh
25 • PermittedPayload
26 • PilotStrengthQRABThresholdDRCLockCC
27 • PilotStrengthQRABThresholdDRCUnlockCC
28 • PilotStrengthConfigXX
9-424
11 • QRABSelectNN
12 • RequestParameters
13 • TransmissionModeNN
14 • T2PFilterTCNN
15 • T2PTransitionFunctionConfigXX
16 • T2PInflowRangeConfigXX
17 • TxT2PmaxConfigXX
19 MaxNumMACFlows – 1, inclusive, CC is the two-digit hexadecimal reverse logical channel
20 number in the range 0x0 to NRTCMPMACCarriersMax-1, and XX is the two-digit hexadecimal
21 configuration number in the range 0x0 to NRTCMPMACConfigsMax-1. The updated values of the
22 attributes shall be consistent with the value of the MaxNumActiveMACFlows parameter of
23 the MaxMACFlows attribute.
25 Update Protocol to configure values of the MaxNumSubPacketsCC attribute if the value of
26 the SupportGAUPMaxNumSubPackets attribute is 0x01. Otherwise, the access network
27 and the access terminal shall not include the MaxNumSubPacketsCC attribute in an
30 Protocol to configure any other attributes of the Multicarrier Reverse Traffic Channel MAC
31 Protocol.
33 definition).

9-425

ID
0xfffe FRABFilterTC 0x02 IIR filter time constant used by the
0x03 IIR filter time constant used for
computing the Filtered RA bit is
512 slots.
All other Reserved
values
0xfffd FRABlow 0x03 Reverse Link Loading Threshold =
−0.8
−0.2
−0.4
−0.6
−1.0
All other Reserved
values
0xfffc MergeThreshold 0x02 Merge Threshold is 512 octets
0x05 Merge Threshold is infinite octets
All other Reserved
values
9-426

ID
0xfffb PayloadThresh 0x01 Minimum packet size of a Reverse
mode is 768 octets.
mode is infinite octets.
All other Reserved
values
0xfffa PilotStrengthFilterTC 0x01 IIR filter time constant used by the
slots.
slots.
slots.
9-427

ID
All other Reserved
values
0xfff9 QRABFilterTC 0x00 IIR filter time constant used by the
All other Reserved
values
0xfff7 T2PNoTxFilterTC 0x01 IIR filter time constant used by the




All other Reserved

values
0xfff26 SupportGAUPMaxNumSub 0x00 Modification of the
Packets MaxNumSubPacketsCC attribute
Protocol is not supported.
9-428

ID
0x01 Modification of the
MaxNumSubPacketsCC attribute
Protocol is supported.
All other Reserved
values
0xfff15 MaxPacketSize 0x00 The largest packet size that the
access terminal can transmit in
any sub-frame in any CDMA
Channel is 1024 bit.
0x01 The largest packet size that the
All other Reserved
values
0xfe00 BucketLevelMax00 0x50 BucketLevelMax for flow 0x00 is
20 dB
0x00 Reserved
0xfe01 BucketLevelMax01 0x6c BucketLevelMax for flow 0x01 is
27 dB
0x00 BucketLevelMax for flow 0x01 is
NULL
0xfeNN BucketLevelMaxNN 0x00 BucketLevelMax for flow NN is
NULL
9-429

ID
NN is the NN is the two-digit 0x01 to BucketLevelMax for flow NN in
two-digit hexadecimal MAC flow 0xff units of 0.25 dB
hexadecim number in the range 0x02
al MAC through
MaxNum
MACFlows
−1,
inclusive.
0xfd00 MergeThreshold00 0x00 Merge Threshold for flow 0x00 if it
Mode is 0 octets

Mode is 32 octets

Mode is 128 octets

Mode is 1024 octets

Mode is infinite octets
All other Reserved

values
0xfdNN MergeThresholdNN 0x02 Merge Threshold for flow NN if it is
is 128 octets.
hexadecim number in the range 0x01 0x00 Merge Threshold for flow NN if it is
al MAC through transmitted in High Capacity Mode
flow MaxNumMACFlows −1, is 0 octets.
0x01 transmitted in High Capacity Mode
through F are specified in
through is 32 octets.
upper case letters.
MaxNum 0x03 Merge Threshold for flow NN if it is
MACFlows transmitted in High Capacity Mode
−1, is 1024 octets.
9-430

ID
inclusive. 0x04 Merge Threshold for flow NN if it is
is 4096 octets.
is 8192 octets.
is infinite octets.
All other Reserved
values
0xfcNN TransmissionModeNN 0x00 The Transmission mode for flow NN
is High Capacity
two-digit hexadecimal MAC flow 0x01 The Transmission mode for flow NN
hexadecim number in the range 0x00 is Low Latency
al MAC through
All other Reserved
values
MaxNum
MACFlows
−1,
inclusive,
where
hexadecim
al digits A
through F
are
specified
in upper
case
letters.
0xfbNN QRABSelectNN 0x00 Use QRAB
9-431

ID
hexadecim number in the range 0x00 All other Reserved
al MAC through values
MaxNum
MACFlows
−1,
inclusive,
where
hexadecim
al digits A
through F
are
specified
in upper
case
letters.
0xfaNN BurstDurationFactorNN 0x00 BurstDurationFactor for flow NN is
4
two-digit hexadecimal MAC flow 0x01 BurstDurationFactor for flow NN is
hexadecim number in the range 0x00 8
al MAC through
0x02 BurstDurationFactor for flow NN is
number in 16
inclusive, where
the range hexadecimal digits A 0x03 BurstDurationFactor for flow NN is
0x00 through F are specified in 32
MaxNum All other Reserved
MACFlows values
−1,
inclusive,
where
hexadecim
al digits A
through F
are
specified
in upper
case
letters.
0xf9NN T2PFilterTCNN 0x01 IIR filter time constant used by the
sub-frames.
9-432

ID
hexadecim number in the range 0x00 0x00 IIR filter time constant used by the
al MAC through access terminal for computing
flow NMFRTCMACFlowMaxMaxNumMA T2PInflown for flow 0xNN is 16
number in CFlows − 1, inclusive,
sub-frames.
the range where hexadecimal digits A
0x00 through F are specified in 0x02 IIR filter time constant used by the
through upper case letters. access terminal for computing
NMFRTCMACFl T2PInflown for flow 0xNN is 32
owMaxMaxN
sub-frames.
umMACFl
ows − 1, 0x03 IIR filter time constant used by the
inclusive. access terminal for computing
sub-frames.
sub-frames.
All other Reserved
values
0xf8CC ARQModeCC 0x00 Reverse Link ARQ Mode = 0
Where CC 0x01 Reverse Link ARQ Mode = 1
denotes a
All other Reserved
reverse
values
logical
channel
in the
range
0x00
through
NRTCMPMACC
arriersMax −1
0xf7CC PilotStrengthQRABThreshol 0x018 PilotStrengthQRABThresholdDRCL

dDRCLockCC ock is −6 dB
0x00 to PilotStrengthQRABThresholdDRCL
Where CC
0x3f ock is in units of –0.25 dB in the
denotes a
reverse
logical
channel
in the
range All other Reserved
0x00 values
through
NRTCMPMACC
arriersMax −1
9-433

ID
0xf6CC PilotStrengthQRABThreshol 0x0c PilotStrengthQRABThresholdDRCU
dDRCUnlockCC nlock is −3 dB
Where CC 0x00 to PilotStrengthQRABThresholdDRCU

denotes a 0x3f nlock is in units of –0.25 dB in the
reverse range 0 dB to –15.75 dB, inclusive
logical All other Reserved
channel values
in the
range
0x00
through
NRTCMPMACC
arriersMax −1

4 10.13.7.2.19.13.7.2.1 AssociatedFlowsNN Attribute

7
Field Length(bits) Default Default for

NN = 0x01
for NN between
0x02 and
(MaxNumMACFlow
s −1), inclusive
Length 8 N/A N/A

{
ValueID 8 N/A N/A
FlowCount 8 0 1
{
Stream 9 N/A 511
SubStream 8 N/A 0
9-434
needed)
7 complex value.

13 sender shall set this field to 3 more than the virtual stream number.
14 If this MAC flow is to be associated with all higher layer flow not
15 associated with a MAC flow, then the sender shall set this field to
16 ‘111111111’.

25 10.13.7.2.29.13.7.2.2 AssociatedFlowConfigurationsNC Attribute

26 N is the single-digit hexadecimal number that identifies the MAC Flows in the range 0x0
27 through MaxNumMACFlows −1, inclusive. C is the single-digit hexadecimal number that
28 identifies the Reverse Logical Channel in the range 0x0 through NRTCMPMACCarrierMax −1,
29 inclusive.
9-435
Field Length(bits) Default Default

N=0x0 N≥>0x1
Length 8 N/A N/A
One or more occurences of the following record:
ValueID 8 N/A N/A
T2PTransitionFunction 4 0x0 0x1
T2PInflowRange 4 0x0 0x1
1
4 AttributeID The sender shall set this field to 0x17NC, where N is the single-digit
5 hexadecimal number that identifies the MAC Flows in the range 0x0
6 through MaxNumMACFlows −1, inclusive. C is the single-digit
7 hexadecimal number that identifies the Reverse Logical Channel in
8 the range 0x0 through NRTCMPMACCarrierMax −1, inclusive.
10 complex value.
11 T2PTransitionFunction
12 Associate the parameter T2PTransitionFunction with the
13 configuration attribute T2PTransitionFunctionConfigXX.
14 T2PInflowRange Associate the parameter T2PInflowRange with the configuration

15 attribute T2PInflowRangeConfigXX.
16 10.13.7.2.39.13.7.2.3 AssociatedATConfigurationsCC Attribute

17 CC is the two-digit hexadecimal number that identifies the Reverse Logical Channel in the
18 range 0x00 through NRTCMPMACCarrierMax −1, inclusive.
19

Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
PilotStrength 4 0x0
TxT2PMax 4 0x0
20
9-436
3 AttributeID The sender shall set this field to 0x18CC, where CC is the two-digit
4 hexadecimal number that identifies the Reverse Logical Channel in
5 the range 0x00 through NRTCMPMACCarrierMax −1, inclusive.
7 complex value.
8 PilotStrength Associate the parameter PilotStrength with the configuration

9 attribute PilotStrengthConfigXX.
10 TxT2PMax Associate the parameter TxT2PMax with the configuration attribute

11 TxT2PMaxConfigXX.
12 10.13.7.2.49.13.7.2.4 AuxiliaryPilotChannelParameters Attribute

13

Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
AuxiliaryPilotChannelGain 4 0x0c
AuxiliaryPilotChannelMinPayload 4 0x7
18 complex value.
19 AuxiliaryPilotChannelGain
20 The sender shall set this field to the Auxiliary Pilot Channel Gain
21 relative to the Traffic Channel Gain that the access terminal uses to
22 compute the Auxiliary Pilot Channel transmit power level. The sender
23 shall specify this field as a 4-bit value in units of –1 dB in the range 0
24 dB to -15 dB, inclusive. The receiver shall support all valid values
26 AuxiliaryPilotChannelMinPayload
27 The sender shall set this field to the minimum Reverse Traffic
28 Channel payload for which the access terminal is required to
9-437
1 transmit the Auxiliary Pilot Channel. The sender shall specify this
2 field as a 4-bit number as shown in Table 9.13.7.2.4-1. The receiver
4 Table 9.13.7.2.4-1.Encoding of AuxiliaryPilotChannelMinPayload Field
Field value Meaning
‘0000’ 128
‘0001’ 256
‘0010’ 512
‘0011’ 768
‘0100’ 1024
‘0101’ 1536
‘0110’ 2048
‘0111’ 3072
‘1000’ 4096
‘1001’ 6144
‘1010’ 8192
‘1011’ 12288
5
6 10.13.7.2.59.13.7.2.5 BucketFactorNN Attribute

9-438

Length 8 N/A N/A

{
ValueID 8 N/A N/A
9.13.7.2.5-1 9.13.7.2.5-4
9.13.7.2.5-2 9.13.7.2.5-5
field:
9.13.7.2.5-3 9.13.7.2.5-6

needed)
}
4 Length field.
9 complex value.
9-439
1 NumFRABAxisValues

4 field as a 3-bit value. The receiver shall support all valid values
17 BucketFactor( ) at the T2PInflow value of T2PAxis and the FRAB
18 value of FRABAxis. The sender shall set the data in the following
19 order: BucketFactor( ) is specified for all the FRABaxisFRABAxis
20 values, then cycled through for each T2PAxis value. The sender shall
21 specify this field as an 8-bit value in the range 1...32 7/8, inclusive
22 in units of 1/8. The receiver shall support all valid values specified
23 by this field.
9-440
Field Default for

NN > 0x00
T2PAxis00 0x00
T2PAxis01 0x48
Field Default for

NN > 0x00
FRABAxis0 0x8
FRABAxis1 0xb
FRABAxis2 0x7
3
Field Default
for NN >
0x00
5
Field Default for

NN = 0x00
T2PAxis00 0x10
T2PAxis01 0x2b
Field Default for

NN = 0x00
FRABAxis0 0x0
8
9-441
Field Default for

NN = 0x00
2
3 10.13.7.2.69.13.7.2.6 CommonPowerParameters Attribute

4

Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
TxT2Pmin 8 0x0F
RPCStep 2 ‘01’
Reserved 0-7(as N/A
needed)
}
5
10 complex value.
11 AllocationStagger T2P allocation stagger factor. The sender shall set this field to the
12 desired T2P allocation dither factor across MAC flows at an access
13 terminal and across access terminals. This field is a 4-bit value in
14 steps of 1/16 in the range of 0…15/16, inclusive. The access
9-442
1 RPCStep Reverse Power Control step. The sender shall set this field to the
2 power control step size the access terminal is to use when controlling
3 the power of the reverse link, as shown in Table 9.13.7.2.6-1. The
4 access terminal shall support the 0.5 dB and 1.0 dB step sizes and
5 should support the 1.5 dB and 2.0 dB step sizes.
Field value Meaning

(binary)
‘00’ 0.5 dB
‘01’ 1.0 dB
‘10’ 1.5 dB
‘11’ 2.0 dB
10 10.13.7.2.79.13.7.2.7 DataTokenBucketNN Attribute

13

Length 8 N/A N/A

{
ValueID 8 N/A N/A
DataTokenInflow 8 0xFF 0xFF
DataBucketLevelMax 8 0xFF 0xFF
}
20 complex value.
9-443
1 DataTokenInflow The sender shall set this field to the data token inflow rate for the
2 data token bucket, expressed as an 8-bit number as in Table
4 this field.
5 Table 9.13.7.2.7-1.Encoding of the DataTokenInflow Field
Field value Meaning

(octets/sub-frame)
0x00 Zero
0xFF ∞
0x00 < x ≤ 0x7F ⎣2^(x/12 + 4) - 15⎦
0x80 < x ≤ 0xFE Reserved
6 DataBucketLevelMax The sender shall set this field to the maximum data token bucket
7 size, expressed as an 8-bit number as in Table 9.13.7.2.7-2. The
9 Table 9.13.7.2.7-2.Encoding of the DataBucketLevelMax Field
Field value Meaning

(octets)
0x00 Zero
0xFF ∞
0x00 < x ≤ 0xFE ⎣2^(x/12 + 4) - 15⎦
10 10.13.7.2.89.13.7.2.8 MaxNumSubPacketsCC Attribute

11 CC denotes a reverse logical channel in the range 0x00 through NRTCMPMACCarriersMax −1,
12 inclusive.
9-444

Length 8 N/A
AttributeID 16 N/A
record:
{
ValueID 8 N/A
Reserved 2 N/A
}
4 AttributeID The sender shall set this field to 0x1aCC.
6 complex value.
7 MaxNumSubPackets0
11 MaxNumSubPackets1
15 MaxNumSubPackets2
20 field.
21
9-445
1 10.13.7.2.99.13.7.2.9 PermittedPayload Attribute

2
Length 8 N/A
AttributeID 16 N/A
record:
{
ValueID 8 N/A
9-446

Reserved 4 N/A
6 complex value.
9-447
13 this field.
20 this field.
27 this field.
34 this field.
9-448
6 this field.
13 this field.
20 this field.
27 this field.
34 this field.
9-449

4 this field.
11 this field.
18 this field.
25 this field.
32 this field.
9-450

2 this field.
9 this field.
16 this field.
23 this field.
30 this field.
37 this field.
9-451
7 this field.
14 this field.
21 this field.
28 this field.
35 this field.
9-452
6 this field.
13 this field.
20 this field.
27 this field.
34 this field.
9-453

4 this field.
11 this field.
18 this field.
25 this field.
32 this field.
9-454

2 this field.
4 field.
5
6 Table 9.13.7.2.9-1. Packet size encoding
Packet size Value

(bits)
0 0x0
128 0x1
256 0x2
512 0x3
768 0x4
1024 0x5
1536 0x6
2048 0x7
3072 0x8
4096 0x9
6144 0xa
8192 0xb
12288 0xc
7
8 10.13.7.2.109.13.7.2.10 PilotStrengthConfigXX Attribute

9 XX is the two-digit hexadecimal number that identifies the attribute configuration index in
10 the range 0x00 through NRTCMPMACConfigsMax −1, inclusive.
9-455
Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
{

9.13.7.2.10-1
PilotStrengthPilotStrengthAxis 4 See Table
9.13.7.2.10-2
}
Reserved 4(0-7) N/A
Variable
}
2
5 Length field.
6 AttributeID The sender shall set this field to 0x1bXX, where XX is the two-digit
7 hexadecimal number that identifies the attribute configuration index
8 in the range 0x00 through NRTCMPMACConfigsMax −1, inclusive.
10 complex value.

14 field to zero.
9-456

4 The sender shall set this field to the scale factor used to scale
6 corresponding PilotStrengthAxis field. The sender shall specify this
7 field as a 2’s complement 4-bit value in units of 1 dB. The receiver
11 ignore this field.The sender shall set this field to ‘0000’. The receiver
13
Field Default
15
16 Table 9.13.7.2.10-2. PilotStrengthPilotStrengthAxis Default Values
Field Default
PilotStrengthPilotStrengthAxis0 0x0
PilotStrengthPilotStrengthAxis1 0x0
17
18
9-457

2
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPreTransition128 8 0x1C
7 complex value.
14 Mode. The sender shall specify this field as a 2-bit value in units of
16 this field.
9-458

11 this field.
25 inclusive.
32 inclusive.
9-459
2 inclusive.
9 inclusive.

11
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPostTransition256 8 0x0F
T2PHiCapPreTransition256 8 0x0F
T2PHiCapPostTransition256 8 0x0F
14 Length field.
17 complex value.
9-460
4 this field.
20 this field.
34 inclusive.
41 inclusive.
9-461
7 inclusive.
14 inclusive.

16
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPostTransition512 8 0x1C
T2PHiCapPreTransition512 8 0x1C
T2PHiCapPostTransition512 8 0x1C
19 Length field.
22 complex value.
9-462
9 this field.
25 this field.
39 inclusive.
9-463
4 inclusive.
11 inclusive.
18 inclusive.

20
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPreTransition768 8 0x3B
23 Length field.
9-464
2 complex value.
11 this field.
27 this field.
41 inclusive.
9-465
7 inclusive.
14 inclusive.
21 inclusive.
9-466

2
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
5 Length field.
8 complex value.
17 this field.
9-467
9 this field.
23 inclusive.
30 inclusive.
37 inclusive.
9-468
2 inclusive.

4
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
7 Length field.
8 AttributeID The sender shall set this field to 0x000a.
10 complex value.
19 this field.
9-469
12 this field.
26 inclusive.
33 inclusive.
40 inclusive.
9-470
7 inclusive.

9
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
12 Length field.
13 AttributeID The sender shall set this field to 0x000b.
15 complex value.
9-471

2 this field.
18 this field.
28 the Pilot Channel power when transmitting a 2,048-bit payload using
32 inclusive.
39 inclusive.
9-472

5 inclusive.
12 inclusive.

14
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
17 Length field.
18 AttributeID The sender shall set this field to 0x000c.
20 complex value.
9-473
6 this field.
22 this field.
36 inclusive.
9-474
2 inclusive.
9 inclusive.
16 inclusive.

18
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
21 Length field.
22 AttributeID The sender shall set this field to 0x000d.
9-475
2 complex value.
11 this field.
27 this field.
41 inclusive.
9-476
7 inclusive.
14 inclusive.
21 inclusive.
9-477

2
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
5 Length field.
6 AttributeID The sender shall set this field to 0x000e.
8 complex value.
17 this field.
9-478
9 this field.
23 inclusive.
30 inclusive.
37 inclusive.
9-479
2 inclusive.

4
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
T2PLoLatPostTransition8192 8 0x4A
T2PHiCapPreTransition8192 8 0x4A
T2PHiCapPostTransition8192 8 0x4A
7 Length field.
8 AttributeID The sender shall set this field to 0x000f.
10 complex value.
19 this field.
9-480
12 this field.
26 inclusive.
33 inclusive.
40 inclusive.
9-481
7 0x80, inclusive.

9
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
12 Length field.
15 complex value.
24 this field.
9-482
13 Channel packet with packet size of 12288 bits using the High
14 Capacity mode. The sender shall specify this field as a 2-bit value in
15 units of sub-frames. The receiver shall support all valid values
30 inclusive.
37 inclusive.
9-483
2 inclusive.
5 the Pilot Channel power when transmitting a 12,288-bit payload
9 0x80, inclusive.
10 10.13.7.2.239.13.7.2.23 RequestParameters Attribute

11
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
ReqRatio 4 0x0
14 Length field.
17 complex value.
9-484
1 10.13.7.2.249.13.7.2.24 RRIChannelPowerParameters Attribute

2

Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
Reserved 4 N/A
5 Length field.
8 complex value.
9-485
30 all valid values specified by this field. The access terminal also uses
31 this value to set the gain of the RRI channel when no packet is being
32 transmitted on the Reverse Traffic Channel.
33 Reserved The access network shall set this field to ‘0000’. The access terminal
35 10.13.7.2.259.13.7.2.25 T2PInflowRangeConfigXX Attribute

37 the range 0x00 through NRTCMPMACConfigsMax −1, inclusive..
9-486
Field Length(bits) Default for Default for

NNXX > NN XX = 0x00
0x00
Length 8 N/A N/A
ValueID 8 N/A N/A
4 Length field.
5 AttributeID The sender shall set this field to 0x15XX, where XX is the two-digit
9 complex value.
11 receiver is to use to determine the T2P allocation for MAC
12 configuration XX. The sender shall specify this field as an 8-bit value
16 receiver is to use to determine the T2P allocation for MAC
17 configuration XX. The sender shall specify this field as an 8-bit value
20 10.13.7.2.269.13.7.2.26 T2PTransitionFunctionConfigXX Attribute

9-487
Field Length(bits) Default for XX > Default for XX =

0x00 0x00
Length 8 N/A N/A

{
ValueID 8 N/A N/A
9.13.7.2.26-1 9.13.7.2.26-5
9.13.7.2.26-2 9.13.7.2.26-6
9.13.7.2.26-3 9.13.7.2.26-7
9.13.7.2.26-4 9.13.7.2.26-8

needed)
}
4 AttributeID The sender shall set this field to 0x16XX, where XX is the two-digit
8 complex value.
12 field.
9-488
4 field.
16 the associated MAC configuration at [T2PAxis, FRABAxis]. The sender
17 shall set the data in the following order: T2PUp( ) is specified for all
18 the FRABaxisFRABAxis values, then cycled through for each T2PAxis
25 the associated MAC configuration at [T2PAxis, FRABAxis]. The sender
26 shall set the data in the following order: T2PDn( ) is specified for all
27 the FRABaxisFRABAxis values, then cycled through for each T2PAxis
9-489
Field Default for

XX > 0x00
T2PAxis00 0x00
T2PAxis01 0x22
T2PAxis02 0x47
T2PAxis03 0x5a
Field Default for

XX > 0x00
FRABAxis0 0x8
FRABAxis1 0xb
FRABAxis2 0xe
FRABAxis3 0x7
3
9-490
1 Table 9.13.7.2.26-3. T2PUpT2PAxisTTFRABAxisF Default Values
Field Default for XX

> 0x00
T2PUpT2PAxis00FRABAxis0 0x1d
T2PUpT2PAxis00FRABAxis1 0x0a
9-491
1 Table 9.13.7.2.26-4. T2PDnT2PAxisTTFRABAxisF Default Values
Field Default for

XX > 0x00
T2PDnT2PAxis03FRABAxis0 0x2d
2
Field Default for

XX = 0x00
T2PAxis00 0x10
T2PAxis01 0x2b
4
Field Default for

XX = 0x00
FRABAxis0 0x0
6
9-492
Field Default for

XX = 0x00
2
Field Default for

XX = 0x00
4
5 10.13.7.2.279.13.7.2.27 TxT2PmaxConfigXX Attribute

8
Length 8 N/A
AttributeID 16 N/A
{
ValueID 8 N/A
{
}
needed)
}
11 Length field.
9-493
1 AttributeID The access network shall set this field to 0x1cXX, where XX is the
2 two-digit hexadecimal number that identifies the attribute
3 configuration index in the range 0x00 through NRTCMPMACConfigsMax −1,
4 inclusive.
6 complex value.

10 field to zero.
18 terminal is allowed to transmit if the filtered serving sector
19 PilotStrength equals corresponding PilotStrengthAxis value. The
20 sender may set this field to 0 to indicate a value of -∞ dB. Otherwise,
21 the sender shall specify this field as a 7-bit value expressed in units
22 of 0.5 dB. The access terminal shall support all valid values specified
23 by this field.
9-494
Field Default
Field Default
0
1
3 10.13.7.2.289.13.7.2.28 MaxMACFlows Attribute

4
Length 8 N/A
AttributeID 16 N/A
ValueID 8 N/A
9 complex value.
9-495

2

Maximum total number of Reverse CDMA
NRTCMPMACCarrierMax 16
Channels
Maximum total number of attribute
NRTCMPMACConfigsMax 16
configurations
the Setup State



11 Parameter
Field Length (bits)
ParameterType 8
Length 8
MIRTCMAC 42
MQRTCMAC 42
Reserved 4
9-496

5
9-497
1 No text
9-498
Default (Subtype 0) and Subtype 1 Physical Layer Protocol 3GPP2 C.S0024-B v2.0
1 1110 DEFAULT (SUBTYPE 0) AND SUBTYPE 1 PHYSICAL LAYER PROTOCOL
2 11.110.1 Default (Subtype 0) and Subtype 1 Physical Layer Protocol Instance
3 11.1.110.1.1 Overview
4 This chapter contains the specification for the Default (Subtype 0) Physical Layer Protocol
5 and the Subtype 1 Physical Layer Protocol.
7 11.1.2.110.1.2.1 Commands

11 • ForwardTrafficCompleted
12 11.1.2.310.1.2.3 Public Data

15 • SoftRAB for every sector in the access terminal’s active set if the access terminal has
16 negotiated Subtype 2 Reverse Traffic Channel MAC protocol.

18 The transmission unit of this protocol is the Physical Layer packet. Each Physical Layer
19 packet contains one or more MAC Layer packets.

10-1
3GPP2 C.S0024-B v2.0 Default (Subtype 0) and Subtype 1 Physical Layer Protocol
3 11.1.4.210.1.4.2 Protocol Initialization for the InUse Protocol Instance of the Subtype 1
4 Physical Layer Protocol
10 11.1.5.110.1.5.1 Procedures

20 then
32 instance for this Protocol.
35
10-2
4
Field Length (bits)
MessageID 8
TransactionID 8
12
Field Length (bits)
MessageID 8
TransactionID 8

10-3
4 11.1.6.110.1.6.1 Procedures
5 Procedures for the InUse Instance of the protocol are described in 0, 10.3, and 10.4.

7 These protocols do not define any message formats.
9 11.1.6.3.110.1.6.3.1 Commands
10 These protocols do not issue any commands.
11 11.1.6.3.210.1.6.3.2 Indications
12 These protocols do not register to receive any indications

14 No configuration attributes are defined for these protocols.
16 11.1.8.110.1.8.1 Protocol Numeric Constants for the Default (Subtype 0) Physical Layer
17 Protocol
18
NPHYPType Type field for this protocol Table 2.5.4-1
NPHYPDefault Subtype field for this protocol 0x0000
19 11.1.8.210.1.8.2 Protocol Numeric Constants for the Subtype 1 Physical Layer Protocol
20
NS1PHYP Subtype field for this protocol 0x0001

21
10-4

3 Information record (see13.8).
10-5
1 11.210.2 Physical Layer Packets
2 11.2.110.2.1 Overview
3 The transmission unit of the physical layer is a physical layer packet. A physical layer
4 packet can be of length 256, 512, 1024, 2048, 3072, or 4096 bits. The format of the
5 physical layer packet depends upon the channel on which it is transmitted. A physical
6 layer packet carries one or more MAC layer packets.
7 11.2.210.2.2 Physical Layer Packet Formats
8 11.2.2.110.2.2.1 Control Channel Physical Layer Packet Format

9 The length of a Control Channel physical layer packet shall be 1,024 bits. Each Control
10 Channel physical layer packet shall carry one Control Channel MAC layer packet. Control
11 Channel physical layer packets shall use the following format:
12
Field Length (bits)
MAC Layer Packet 1,002

FCS 16
TAIL 6
13
14 MAC Layer Packet - MAC layer packet from the Control Channel MAC protocol.
15 FCS - Frame check sequence (see 10.2.4).
16 TAIL - Encoder tail bits. This field shall be set to all ‘0’s.
17 Figure 10.2.2.1-1 illustrates the format of the Control Channel physical layer packets.
Physical Layer Packet

(1,024 Bits)
MAC Layer Packet FCS TAIL

1,002 16 6
Bits Bits Bits
18
19 Figure 10.2.2.1-1. Physical Layer Packet Format for the Control Channel
20 11.2.2.210.2.2.2 Access Channel Physical Layer Packet Format

21 The length of an Access Channel physical layer packet of the Default (Subtype 0) Physical
22 Layer Protocol shall be 256 bits. The length of an Access Channel physical layer packet of
23 the Subtype 1 Physical Layer Protocol shall be 256, 512, or 1024 bits. Each Access
24 Channel physical layer packet shall carry one Access Channel MAC layer packet. Access
25 Channel physical layer packets of the Default (Subtype 0) Physical Layer Protocol shall use
26 the following format:
27
10-6
Field Length (bits)
MAC Layer Packet 234

FCS 16
TAIL 6
1
2 MAC Layer Packet - MAC layer packet from the Access Channel MAC protocol.
5 Access Channel physical layer packets of the Subtype 1 Physical Layer Protocol shall use
6 the following format:
7
Field Length (bits)
MAC Layer Packet 234, 490, or 1002

FCS 16
TAIL 6
8
9 MAC Layer Packet - MAC layer packet from the Access Channel MAC protocol.
12 Figure 10.2.2.2-1 illustrates the format of the Access Channel physical layer packets of the
13 Default (Subtype 0) Physical Layer Protocol and Figure 10.2.2.2-2 illustrates the format of
14 the Access Channel physical layer packets of the Subtype 1 Physical Layer Protocol.

(256 Bits)
FCS TAIL
MAC Layer Packet
16 6
234 Bits
Bits Bits
15
16 Figure 10.2.2.2-1. Default (Subtype 0) Physical Layer Protocol Packet Format for the
17 Access Channel

(256, 512, or 1024 Bits)

234, 490, or 1002 16 6
Bits Bits Bits
18
19 Figure 10.2.2.2-2. Subtype 1 Physical Layer Protocol Packet Format for the Access
20 Channel
10-7
1 11.2.2.310.2.2.3 Forward Traffic Channel Physical Layer Packet Format

2 The length of a Forward Traffic Channel physical layer packet shall be 1024, 2048, 3072,
3 or 4096 bits. A Forward Traffic Channel physical layer packet shall carry 1, 2, 3, or 4
4 Forward Traffic Channel MAC layer packets depending on the rate of transmission.
5 Forward Traffic Channel physical layer packets shall use the following format:
6
Field Length (bits)
0, 1, 2, or 3 occurrences of the following two fields:

PAD 22
One occurrence of the following three fields:
FCS 16
TAIL 6
7
8 MAC Layer Packet - MAC layer packet from the Forward Traffic Channel MAC
9 Protocol.
10 PAD - This field shall be set to all ‘0’s. The receiver shall ignore this
11 field.
14 Figure 10.2.2.3-1 illustrates the format of the Forward Traffic Channel physical layer
15 packets.
10-8

(1,024 Bits)
MAC Layer
FCS TAIL
Packet
16 6
1,002
Bits Bits
Bits

(2,048 Bits)
MAC Layer MAC Layer

PAD FCS TAIL
Packet Packet
22 16 6
1,002 1,002
Bits Bits Bits
Bits Bits

(3,072 Bits)
MAC Layer MAC Layer MAC Layer

PAD PAD FCS TAIL
Packet Packet Packet
22 22 16 6
1,002 1,002 1,002
Bits Bits Bits Bits
Bits Bits Bits

(4,096 Bits)
MAC Layer MAC Layer MAC Layer MAC Layer

PAD PAD PAD FCS TAIL
Packet Packet Packet Packet
22 22 22 16 6
1,002 1,002 1,002 1,002
Bits Bits Bits Bits Bits
Bits Bits Bits Bits
1
2 Figure 10.2.2.3-1. Physical Layer Packet Format for the Forward Traffic Channel
3 11.2.2.410.2.2.4 Reverse Traffic Channel Physical Layer Packet Format

4 The length of a Reverse Traffic Channel physical layer packet shall be 256, 512, 1024,
5 2048, or 4096 bits. Each Reverse Traffic Channel physical layer packet shall carry one
6 Reverse Traffic Channel MAC layer packet. Reverse Traffic Channel physical layer packets
7 shall use the following format:
8
Field Length (bits)
234, 490, 1002, 2026,

MAC Layer Packet
or 4074
FCS 16
TAIL 6
9
10 MAC Layer Packet - MAC layer packet from the Reverse Traffic Channel MAC
11 Protocol.
14 Figure 10.2.2.4-1 illustrates the format of the Reverse Traffic Channel physical layer
15 packets.
10-9

(256, 512, 1024, 2048, or 4096 Bits)

234, 490, 1002, 2026, or 4074 16 6
Bits Bits Bits
1
2 Figure 10.2.2.4-1. Physical Layer Packet Format for the Reverse Traffic Channel
3 11.2.310.2.3 Bit Transmission Order

4 Each field of the physical layer packets shall be transmitted in sequence such that the
5 most significant bit (MSB) is transmitted first and the least significant bit (LSB) is
6 transmitted last. The MSB is the left-most bit in the figures of the document.
7 11.2.410.2.4 Computation of the FCS Bits

8 The FCS computation described here shall be used for computing the FCS field in the
9 Control Channel physical layer packets, the Forward Traffic Channel physical layer
10 packets, the Access Channel physical layer packets, and the Reverse Traffic Channel
11 physical layer packets.
12 The FCS shall be a CRC calculated using the standard CRC-CCITT generator polynomial:
13 g(x) = x16 + x12 + x5 + 1.
14 The FCS shall be equal to the value computed according to the following procedure as
15 shown in Figure 10.2.4-1:
16 • All shift-register elements shall be initialized to ‘0’s.
17 • The switches shall be set in the up position.
18 • The register shall be clocked once for each bit of the physical layer packet except for the
19 FCS and TAIL fields. The physical layer packet shall be read from MSB to LSB.
20 • The switches shall be set in the down position so that the output is a modulo-2
21 addition with a ‘0’ and the successive shift-register inputs are ‘0’s.
22 • The register shall be clocked an additional 16 times for the 16 FCS bits.
23 • The output bits constitute all fields of the physical layer packets except the TAIL field.
10-10
Input
‘0’
x0 x1 x5 x12 x15
Output
‘0’

physical layer packet except for the
FCS and TAIL fields;
then, down for the 16-bit FCS field.
1
2 Figure 10.2.4-1. FCS Computation for the Physical Layer Packet
10-11
1 11.310.3 Access Terminal Requirements

2 This section defines requirements specific to access terminal equipment and operation.
3 11.3.110.3.1 Transmitter
4 11.3.1.110.3.1.1 Frequency Parameters

5 The access terminal shall meet the requirements in the current version of [15].
6 11.3.1.1.110.3.1.1.1 Frequency Tolerance

8 11.3.1.210.3.1.2 Power Output Characteristics

9 All power levels are referenced to the access terminal antenna connector unless otherwise
10 specified.
11 11.3.1.2.110.3.1.2.1 Output Power Requirements of Reverse Channels
12 11.3.1.2.1.110.3.1.2.1.1 Access Channel Output Power

13 When transmitting over the Access Channel, the access terminal transmits Access Probes
14 until the access attempt succeeds or ends.
15 11.3.1.2.1.210.3.1.2.1.2 Reverse Traffic Channel Output Power

16 When the access terminal is transmitting the Reverse Traffic Channel, the access terminal
17 shall control the mean output power using a combination of closed-loop and open-loop
18 power control (see 10.3.1.2.4 and 10.3.1.4). Throughout 10.3.1.2, the channel formed by
19 multiplexing the RRI Channel onto the Pilot Channel is referred to as the Pilot Channel.
21 transmits the Pilot Channel, the DRC Channel, the ACK Channel when acknowledging
22 received physical layer packets, and the Data Channel when transmitting physical layer
23 packets. These channels shall be transmitted at power levels according to open-loop and
24 closed-loop power control. The transmitted power level of the Data Channel shall be
25 adjusted depending on the selected data rate (see 10.3.1.2.4) and reverse link power
26 control. The traffic data shall be transmitted in the form of physical layer packets (duration
27 26.66… ms), which may occur either contiguously or sporadically. When the data rate is
28 changed, the access terminal output power, relative to the desired value in steady state,
29 shall be within ±0.5 dB or 20% of the change in dB, whichever is greater. The access
30 terminal output power shall settle to within ±0.5 dB of the steady-state value within 200 μs
31 of the physical layer packet boundary.
32 11.3.1.2.210.3.1.2.2 Maximum Output Power

10-12
1 11.3.1.2.310.3.1.2.3 Output Power Limits
2 11.3.1.2.3.110.3.1.2.3.1 Minimum Controlled Output Power

4 11.3.1.2.3.210.3.1.2.3.2 Standby Output Power

5 The access terminal shall disable its transmitter except when it is instructed by a MAC
6 protocol to transmit. When the transmitter is disabled, the output noise power spectral
7 density of the access terminal shall be less than –61 dBm/1 MHz for all frequencies within
8 the transmit bands that the access terminal supports.
9 11.3.1.2.410.3.1.2.4 Controlled Output Power

10 The access terminal shall provide two independent means for output power adjustment: an
11 open-loop estimation performed by the access terminal and a closed-loop correction
12 involving both the access terminal and the access network. Accuracy requirements on the
13 controlled range of mean output power (see 10.3.1.2.5) need not apply for the following
14 three cases:
15 • Mean output power levels exceeding the minimum ERP/EIRP at the maximum output
16 power for the corresponding access terminal class;
17 • Mean output power levels less than the minimum controlled output power (see
18 10.3.1.2.3.1); or
19 • Mean input power levels exceeding –25 dBm within the 1.23-MHz bandwidth.
20 11.3.1.2.4.110.3.1.2.4.1 Estimated Open-Loop Output Power

21 Open-loop operation shall be based on the power of the received Forward Pilot Channel (see
22 10.4.1.3.2.1).
23 The nominal access probe structure and its transmit power requirements are defined as
24 part of the Access Channel MAC Protocol. The power of the Access Data Channel relative to
25 that of the Pilot Channel shall be as specified in Table 10.3.1.2.4.1-1 in which
26 DataOffsetNom and DataOffset9k6 are public data of the Access Channel MAC Protocol
27 when using the Default (Subtype 0) Physical Layer Protocol. The power of the Access Data
28 Channel relative to that of the Pilot Channel shall be as specified in Table 10.3.1.2.4.1-1 in
29 which DataOffsetNom, DataOffset9k6, DataOffset19k2, and DataOffset38k4 are public
30 data of the Access Channel MAC Protocol when using the Subtype 1 Physical Layer
31 Protocol. The output power of the Pilot Channel during the preamble portion of an access
32 probe shall be increased relative to the nominal Pilot Channel power during the data
33 portion of the probe by an amount such that the total output power of the preamble and
34 data portions of the access probe, if transmitted at 9.6kbps, are the same.
35 Once instructed by the Reverse Traffic Channel MAC Protocol, the access terminal initiates
36 Reverse Traffic Channel transmission. The initial mean output power of the Pilot Channel
37 of the Reverse Traffic Channel shall be equal to the mean output power of the Pilot Channel
38 at the end of the last Access Channel probe minus the difference in the forward link mean
10-13
1 received signal power from the end of the last Access Channel probe to the start of the
2 Reverse Traffic Channel transmission.
3 The subsequent mean output power of the Pilot Channel of the total reverse link
4 transmission shall be the mean output power of the Pilot Channel at the end of the last
5 Access Channel probe minus the difference in the forward link mean received signal power
6 from the end of the last Access Channel probe to the current Reverse Traffic Channel
7 transmission, plus closed loop corrections as specified in 10.3.1.2.4.2.
8 The accuracy of the incremental adjustment to the mean output power, as dictated by the
9 Access Channel MAC Protocol and the Reverse Traffic Channel MAC Protocol, shall be
10 ±0.5 dB or 20% of the change in dB, whichever is greater.
11 During the transmission of the Reverse Traffic Channel, the determination of the output
12 power needed to support the Data Channel, the DRC Channel, and the ACK Channel is an
13 additional open-loop process performed by the access terminal.
14 The power of the Data Channel relative to that of the Pilot Channel shall be as specified in
15 Table 10.3.1.2.4.1-1 in which DataOffsetNom, DataOffset9k6, DataOffset19k2,
16 DataOffset38k4, DataOffset76k8, and DataOffset153k6 are public data of the Reverse
17 Traffic Channel MAC Protocol.
18 Table 10.3.1.2.4.1-1. Relative Power Levels vs. Data Rate
Data Rate Data Channel Gain Relative to Pilot

(kbps) (dB)
0 –∞ (Data Channel Is Not Transmitted)

9.6 DataOffsetNom + DataOffset9k6 + 3.75
19
20 During the transmission of the DRC Channel, the power of the DRC Channel relative to
21 that of the Pilot Channel shall be as specified by DRCChannelGain, where
22 DRCChannelGain is public data of the Forward Traffic Channel MAC Protocol.
23 During the transmission of the ACK Channel, the power of the ACK Channel relative to that
24 of the Pilot Channel shall be as specified by ACKChannelGain, where ACKChannelGain is
25 public data of the Forward Traffic Channel MAC Protocol.
26 The access terminal shall maintain the power of the Data Channel, DRC Channel, and ACK
27 Channel, relative to that of the Pilot Channel, to within ±0.25 dB of the specified values.
28 If the access terminal is unable to transmit at the requested output power level when the
29 maximum Reverse Traffic Channel data rate is 9600 bps, the access terminal shall reduce
30 the power of the DRC Channel and the ACK Channel accordingly. The maximum power
31 reduction for the DRC Channel corresponds to gating off the DRC Channel. The maximum
10-14
1 power reduction for the ACK Channel corresponds to gating off the ACK Channel. If the
2 ACK Channel is active, the ACK Channel power reduction shall occur only after the DRC
3 Channel has been gated off. The access terminal shall perform the power reduction within
4 one slot of determining that the access terminal is unable to transmit at the requested
5 output power level.
6 11.3.1.2.4.210.3.1.2.4.2 Closed-Loop Output Power

7 For closed-loop correction (with respect to the open-loop estimate), the access terminal
8 shall adjust the mean output power level of the Pilot Channel in response to each power-
9 control bit received on the Reverse Power Control (RPC) Channel. The nominal change in
10 mean output power level of the Pilot Channel per single power-control bit shall be set
11 according to the RPCStep, which is public data of the Reverse Traffic Channel MAC
12 Protocol.
13 For the 1.0 dB step size, the change in mean output power level per power-control bit shall
14 be within ±0.5 dB of the nominal value (1 dB), and the change in mean output power level
15 per 10 power-control bits of the same sign shall be within ±2.0 dB of 10 times the nominal
16 change (10 dB). For the 0.5 dB step size, the change in mean output power level per power-
17 control bit shall be within ±0.3 dB of the nominal value (0.5 dB), and the change in mean
18 output power level per 20 power-control bits of the same sign shall be within ±2.5 dB of 20
19 times the nominal change (10 dB). A ‘0’ power-control bit requires the access terminal to
20 increase transmit power, and a ‘1’ power-control bit requires the access terminal to
21 decrease transmit power. The access terminal shall provide a closed-loop adjustment range
22 greater than ±24 dB around its open-loop estimate.
23 See 10.3.1.4 for combining power-control bits received from different multipath
24 components or from different sectors during handoff.
25 11.3.1.2.510.3.1.2.5 Power Transition Characteristics
26 11.3.1.2.5.110.3.1.2.5.1 Open-Loop Estimation

27 Following a step change in mean input power, ΔPin, the mean output power of the access
28 terminal shall transition to its final value in a direction opposite in sign to ΔPin, with
29 magnitude contained between the mask limits defined by139:
30 • Upper Limit:
31 For 0 < t < 24 ms: max [1.2 × |ΔPin| × (t/24), |ΔPin| × (t/24) + 2.0 dB] + 1.5 dB
32 For t ≥ 24 ms: max [1.2 × |ΔPin|, |ΔPin| + 0.5 dB] + 1.5 dB
33 • Lower Limit:
34 For t > 0: max [0.8 × |ΔPin| × [1 – e(1.66…–t)/36] – 2.0 dB, 0] – 1 dB
35 where “t” is expressed in units of milliseconds and ΔPin is expressed in units of dB.
139 The mask limits allow for the effect of alternating closed-loop power-control bits.
10-15
1 These limits shall apply to a step change ΔPin of ±20 dB or less. The absolute value of the
2 change in mean output power due to open-loop power control shall be a monotonically
3 increasing function of time. If the change in mean output power consists of discrete
4 increments, no single increment shall exceed 1.2 dB.
5 11.3.1.2.5.210.3.1.2.5.2 Closed-Loop Correction

6 Following the reception of a closed-loop power-control bit, the mean output power of the
7 access terminal shall be within 0.3 dB and 0.15 dB of the final value in less than 500 μs for
8 step sizes of 1.0 dB and 0.5 dB, respectively.
9 11.3.1.310.3.1.3 Modulation Characteristics
10 11.3.1.3.110.3.1.3.1 Reverse Channel Structure

11 The Reverse Channel consists of the Access Channel and the Reverse Traffic Channel. The
12 Access Channel shall consist of a Pilot Channel and a Data Channel. The Reverse Traffic
13 Channel shall consist of a Pilot Channel, a Reverse Rate Indicator (RRI) Channel, a Data
14 Rate Control (DRC) Channel, an Acknowledgment (ACK) Channel, and a Data Channel. The
15 RRI Channel is used to indicate the data rate of the Data Channel being transmitted on the
16 Reverse Traffic Channel. The DRC Channel is used by the access terminal to indicate to the
17 access network the requested Forward Traffic Channel data rate and the selected serving
18 sector on the Forward Channel. The ACK Channel is used by the access terminal to inform
19 the access network whether or not the physical layer packet transmitted on the Forward
20 Traffic Channel has been received successfully.
21 The structure of the reverse link channels for the Access Channel shall be as shown in
22 Figure 10.3.1.3.1-1 for the Default (Subtype 0) Physical Layer Protocol and Figure
23 10.3.1.3.1-2 for the Subtype 1 Physical Layer Protocol, and the structure of the reverse link
24 channels for the Reverse Traffic Channel shall be as shown in Figure 10.3.1.3.1-3 and
25 Figure 10.3.1.3.1-4. For the Reverse Traffic Channel, the encoded RRI Channel symbols
26 shall be time-division multiplexed with the Pilot Channel. This time-division-multiplexed
27 channel is still referred to as the Pilot Channel. For the Access Channel, the RRI symbols
28 shall not be transmitted and the Pilot Channel shall not be time-division multiplexed. The
29 Pilot Channel, the DRC Channel, the ACK Channel, and the Data Channel shall be
30 orthogonally spread by Walsh functions of length 4, 8, or 16 (see 10.3.1.3.7). Each Reverse
31 Traffic Channel shall be identified by a distinct user long code. The Access Channel for
32 each sector shall be identified by a distinct Access Channel long code.
33 The Reverse Traffic Channel frame shall be 26.66… ms in duration. The zero offset frame
34 boundary shall be aligned to the rollover of the short PN codes (see 10.3.1.3.8.1). Each
35 Reverse Traffic Channel frame shall consist of 16 slots, with each slot 1.66… ms in
36 duration. Each slot contains 2048 PN chips.
37 When the access terminal is transmitting a Reverse Traffic Channel, it shall continuously
38 transmit the Pilot Channel and the RRI Channel. These channels shall be time-division
39
16 . When the DRC Channel is
multiplexed, and shall be transmitted on Walsh channel W0
40 active (see 10.3.1.3.3.5), it shall be transmitted for full slot durations on Walsh channel
10-16
1
16 . The access terminal shall transmit an ACK Channel bit in response to every Forward
W8
2 Traffic Channel slot that is associated with a detected preamble directed to the access
3 terminal. Otherwise, the ACK Channel shall be gated off. When the ACK Channel bit is
4 transmitted, it shall be transmitted on the first half slot on Walsh channel W48 .
5 For the Reverse Traffic Channel, the encoded RRI symbols shall be time-division
6 multiplexed with the Pilot Channel, and the encoded RRI symbols shall be allocated the
7 first 256 chips of every slot as shown in Figure 10.3.1.3.1-5.
8 Figure 10.3.1.3.1-6 and Figure 10.3.1.3.1-7 give examples of the ACK Channel operation
9 for a 153.6 kbps Forward Traffic Channel. The 153.6 kbps Forward Traffic Channel
10 physical layer packets use four slots, and these slots are transmitted with a three-slot
11 interval between them, as shown in the figures. The slots from other physical layer packets
12 are interlaced in the three intervening slots.
13 Figure 10.3.1.3.1-6 shows the case of a normal physical layer packet termination. In this
14 case, the access terminal transmits NAK responses on the ACK Channel after the first three
15 slots of the physical layer packet are received indicating that it was unable to correctly
16 receive the Forward Traffic Channel physical layer packet after only one, two, or three of
17 the nominal four slots. An ACK or NAK is also transmitted after the last slot is received, as
18 shown.
19 Figure 10.3.1.3.1-7 shows the case where the Forward Traffic Channel physical layer
20 packet transmission is terminated early. In this example, the access terminal transmits an
21 ACK response on the ACK Channel after the third slot is received indicating that it has
22 correctly received the physical layer packet. When the access network receives such an
23 ACK response, it does not transmit the remaining slots of the physical layer packet.
24 Instead, it may begin the transmission of any subsequent physical layer packets.
25 When the access terminal has received all slots of a physical layer packet or has
26 transmitted a positive ACK response, the physical layer shall return a
27 ForwardTrafficCompleted indication.
10-17
W016 = ( + + + + + + + + + + + + + + + + )
Signal Point
Pilot Channel Mapping
(All 0's) 0 +1
1 –1
128 Binary
Symbols
per Slot W24 = (+ + − − )
Signal Point
Data Channel Encoder Interleaved
Channel Mapping
Physical Layer (Code Rate = Packet
Interleaver 0 +1
Packets 1/4) Repetition
1 –1
256 Bits 1,024 38.4 ksps 307.2 ksps

9.6 kbps Symbols
cos(2 fCt)
I I Baseband
Filter
Quadrature
Spreading
(Complex Multiply) s(t)
I = I PNI – Q PNQ
Data Q = I PNQ + Q PNI
Channel Q Q Baseband
Relative Filter
Gain
1.2288 Mcps PNI PNQ

sin(2 fCt)
Walsh Cover
(+ – )
Note: The Walsh covers and PN

Decimator
by Factor sequences are represented with 1
values with the mapping +1 for
of 2
binary ‘0’ and –1 for binary ‘1’.
PI PQ
I-Channel Q-Channel
Short Short
PN Sequence PN Sequence
UI UQ
I-Channel Q-Channel
Access Long-Code Access Long-Code
1
2 Figure 10.3.1.3.1-1. Default (Subtype 0) Physical Layer Protocol Reverse Channel

3 Structure for the Access Channel
10-18
W016 = ( + + + + + + + + + + + + + + + + )
Signal Point
(All 0's) 0 +1
1 –1
128 Binary
Symbols
per Slot W24 = (+ + − − )
Signal Point
Channel Mapping
Interleaver 0 +1
1 –1
256 Bits, 9.6 kbps 1,024 Symbols 38.4 ksps 307.2 ksps
512 Bits, 19.2 kbps 2,048 Symbols 76.8 ksps
cos(2 fCt)
I I Baseband
Filter
Quadrature
Spreading
I = I PNI – Q PNQ
Relative Filter
Gain
1.2288 Mcps PNI PNQ

sin(2 fCt)
Walsh Cover
(+ – )

Decimator
of 2
PI PQ
I-Channel Q-Channel
Short Short
UI UQ
I-Channel Q-Channel
1
2 Figure 10.3.1.3.1-2. Subtype 1 Physical Layer Protocol Reverse Channel Structure for
3 the Access Channel
10-19
W016 = ( + + + + + + + + + + + + + + + + )
W816 = ( + + + + + + + + − − − − − − − − )
Walsh Cover
Wi8 , i = 0,..., 7
W48 = (+ + + + − − − − )
W24 = (+ + − − )
3 (Part 1 of 2)
10-20
cos(2 fCt)
A
I I Baseband
Filter
ACK
Channel
C
Relative
Quadrature
Gain
Spreading
I = I PNI – Q PNQ
DRC
Q = I PNQ + Q PNI
Channel
B
Relative
Gain
Q Q Baseband
Filter
Data
Channel
D
Relative PNI PNQ
Gain sin(2 fCt)
Walsh Cover
(+ – )
Decimator Note: The Walsh covers and PN

of 2
PI PQ
I-Channel Q-Channel
Short Short
UI UQ
I-Channel Q-Channel
User Long-Code User Long-Code
1
3 (Part 2 of 2)
1 Slot
2,048 Chips
RRI Pilot
256 Chips
1,792 Chips
4
5 Figure 10.3.1.3.1-5. Pilot Channel and RRI Channel TDM Allocations for the Reverse
6 Traffic Channel
10-21
Transmit Transmit Transmit Transmit

Forward Traffic Slot 1 Slot 2 Slot 3 Slot 4
Channel Physical
Layer Packet
Transmissions
with 153.6 kbps
Slots n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n + 9 n + 10 n + 11 n + 12 n + 13 n + 14 n + 15
DRC Channel
Transmission
Requesting
153.6 kbps
DRC
Request for
153.6 kbps One-Half Slot Offset
ACK Channel
Half-Slot
Transmissions
NAK NAK NAK ACK
One Slot
or
1 NAK
2 Figure 10.3.1.3.1-6. Multislot Physical Layer Packet with Normal Termination
First Slot for the Next

Transmission

Slot 1 Slot 2 Slot 3 Slot 1
Forward Traffic
Channel Physical
Layer Packet
Transmissions
with 153.6 kbps
Slots n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n+9 n + 10 n + 11 n + 12
DRC Channel
Transmission
Requesting
153.6 kbps
DRC
Request for
ACK Channel
Half-Slot
Transmissions
NAK NAK ACK

One Slot
3
4 Figure 10.3.1.3.1-7. Multislot Physical Layer Packet with Early Termination
5 11.3.1.3.1.110.3.1.3.1.1 Modulation Parameters

6 The modulation parameters for the Access Channel and the Reverse Traffic Channel shall
7 be as specified in Table 10.3.1.3.1.1-1.
10-22
1 Table 10.3.1.3.1.1-1. Modulation Parameters for the Access Channel and the Reverse
2 Traffic Channel
Data Rate (kbps)

Parameter 9.6 19.2 38.4 76.8 153.6
Reverse Rate Index 1 2 3 4 5

Bits per Physical
256 512 1,024 2,048 4,096
Layer Packet
Physical Layer
Packet Duration 26.66… 26.66… 26.66… 26.66… 26.66…
(ms)
Code Rate 1/4 1/4 1/4 1/4 1/2
Code Symbols per
Physical Layer 1,024 2,048 4,096 8,192 8,192
Packet
Code Symbol Rate
38.4 76.8 153.6 307.2 307.2
(ksps)
Interleaved Packet
8 4 2 1 1
Repeats
Modulation Symbol
307.2 307.2 307.2 307.2 307.2
Rate (ksps)
Modulation Type BPSK BPSK BPSK BPSK BPSK
PN Chips per
Physical Layer 128 64 32 16 8
Packet Bit
3
4 11.3.1.3.1.210.3.1.3.1.2 Data Rates

5 The access terminal shall transmit information on the Access Channel at a fixed data rate
6 of 9.6 kbps if using the Default (Subtype 0) Physical Layer Protocol.
7 The access terminal shall transmit information on the Access Channel at a variable data
8 rate of 9.6, 19.2, or 38.4 kbps, according to the Access Channel MAC Protocol if using the
10 The access terminal shall transmit information on the Reverse Traffic Channel at a variable
11 data rate of 9.6, 19.2, 38.4, 76.8, or 153.6 kbps, according to the Reverse Traffic Channel
12 MAC Protocol.
13 11.3.1.3.210.3.1.3.2 Access Channel

14 The Access Channel is used by the access terminal to initiate communication with the
15 access network or to respond to an access terminal directed message. The Access Channel
10-23
1 consists of a Pilot Channel and a Data Channel as shown in Figure 10.3.1.3.2-1 and Figure
2 10.3.1.3.2-2.
3 An access probe shall consist of a preamble followed by one or more Access Channel
4 physical layer packets. During the preamble transmission, only the Pilot Channel shall be
5 transmitted. During the Access Channel physical layer packet transmission, both the Pilot
6 Channel and the Data Channel shall be transmitted. The output power of the Pilot Channel
7 during the preamble portion of an access probe is higher than it is during the data portion
8 of the probe. The output power of the preamble is independent of the data rate and is set
9 equal to that of the data portion transmitted at 9.6 kbps as shown in Figure 10.3.1.3.2-1
10 and Figure 10.3.1.3.2-2.
11 The preamble length is specified by the parameter PreambleLength in frames or the
12 parameter PreambleLengthSlots in slots both of which are public data from the Access
13 Channel MAC Protocol. The Access Channel physical layer packets of the Default (Subtype
14 0) Physical Layer Protocol are transmitted at a fixed data rate of 9.6 kbps. The Access
15 Channel physical layer packets of the Subtype 1 Physical Layer Protocol are transmitted at
16 data rates of 9.6, 19.2, or 38.4 kbps.
10-24
Transmit
Power
Data Channel
(Q Phase)
Pilot Channel
(I Phase)
Pilot Channel
(I Phase)
Time
Capsule Frames
Preamble Frames (Access Channel
1
Physical Layer Packets)
2 Figure 10.3.1.3.2-1. Example of an Access Probe Transmitted at 9.6 kbps (Subtype 0

3 Physical Layer Protocol)
5 Figure 10.3.1.3.2-2. Example of an Access Probe Transmitted at 9.6 kbps (Subtype 1

6 Physical Layer Protocol)
10-25
Transmit
Power
Power Level
of 9.6 kbps
data
Data Channel
(Q Phase)
Pilot Channel
(I Phase)
Pilot Channel
(I Phase)
Time
Preamble Capsule Frames
1
slots Access Channel Physical Layer Packets

3 or 38.4 kbps
4 10.3.1.3.3 Reverse Traffic Channel
5 11.3.1.3.2.110.3.1.3.3.1 Pilot Channel

6 The access terminal shall transmit unmodulated symbols with a binary value of ‘0’ on the
7 Pilot Channel. The Pilot Channel shall be transmitted continuously during Access Channel
8 transmission. It is transmitted on the I channel using the 16-chip Walsh function number
9 0 ( W016 = + + + + + + + + + + + + + + + +) cover.
10 11.3.1.3.2.210.3.1.3.3.2 Data Channel

11 One or more Access Channel physical layer packets shall be transmitted on the Data
12 Channel during every access probe. The Access Channel physical layer packets of the
13 Default (Subtype 0) Physical Layer Protocol are transmitted at a fixed data rate of 9.6 kbps
14 on the Q-branch using the 4-chip Walsh function number 2 ( W24 = + + – –). The Access
15 Channel physical layer packets of the Subtype 1 Physical Layer Protocol are transmitted at
16 a fixed data rate of 9.6, 19.2, or 38.4 kbps on the Q-branch using the 4-chip Walsh
17 function number 2 ( W24 = + + – –). The Access Channel physical layer packets of the
18 Default (Subtype 0) Physical Layer Protocol shall be preceded by a preamble of
19 PreambleLength frames where only the Pilot Channel is transmitted. The Access Channel
20 physical layer packets of the Subtype 1 Physical Layer Protocol shall be preceded by a
21 preamble of PreambleLength frames or PreambleLengthSlots slots where only the Pilot
22 Channel is transmitted. The PreambleLength parameter and the PreambleLengthSlots
23 parameter are public data from the Access Channel MAC Protocol.Reverse Traffic Channel
24 The Reverse Traffic Channel is used by the access terminal to transmit user-specific traffic
25 or signaling information to the access network. The Reverse Traffic Channel consists of a
26 Pilot Channel, an RRI Channel, a DRC Channel, an ACK Channel, and a Data Channel.
27 The access terminal shall support transmission of information on the Data Channel of the
28 Reverse Traffic Channel at data rates of 9.6, 19.2, 38.4, 76.8, and 153.6 kbps. The data
10-26
1 rate used on the Data Channel is specified by the Reverse Traffic Channel MAC Protocol.
2 The gain of the Data Channel relative to that of the Pilot Channel for the Reverse Traffic
3 Channel depends on the data rate as shown in Table 10.3.1.2.4.1-1.
4 11.3.1.3.2.310.3.1.3.3.3 Pilot Channel

6 Pilot Channel. The transmission of the Pilot Channel and the RRI Channel shall be time
7 multiplexed on the same Walsh channel as shown in Figure 10.3.1.3.1-3. The Pilot
8 Channel and the RRI Channel shall be transmitted at the same power. It is transmitted on
9 the I channel using the 16-chip Walsh function number 0 ( W016 =
10 + + + + + + + + + + + + + + + +) cover.
11 11.3.1.3.2.410.3.1.3.3.4 Reverse Rate Indicator Channel

12 The RRI Channel is used by the access terminal to indicate the data rate at which the Data
13 Channel is transmitted. The data rate is represented by a three-bit RRI symbol at the rate
14 of one three-bit symbol per 16-slot physical layer packet. Each RRI symbol shall be
15 encoded into a seven-bit codeword by a simplex encoder as specified in Table 10.3.1.3.3.4-
16 1. Then, each codeword shall be repeated 37 times and the last three symbols shall be
17 disregarded (i.e., punctured), as shown in Figure 10.3.1.3.1-3. The resulting 256 binary
18 symbols per physical layer packet shall be time-division multiplexed with the Pilot Channel
19 symbols and span the same time interval as the corresponding physical layer packet. The
20 time-division-multiplexed Pilot and RRI Channel sequence is spread with the 16-chip
21 Walsh function W016 producing 256 RRI chips per slot. The RRI chips shall be time-division
22 multiplexed into the first 256 chips of every slot as shown in Figure 10.3.1.3.1-5. When no
23 physical layer packet is transmitted on the Reverse Traffic Channel, the access terminal
24 shall transmit the zero data rate RRI codeword on the RRI Channel, as specified in Table
25 10.3.1.3.3.4-1. The Pilot Channel and the RRI Channel is transmitted on the I-branch.
26 Table 10.3.1.3.3.4-1. RRI Symbol and Simplex Encoder Assignments
Data Rate (kbps) RRI Symbol RRI Codeword
0 000 0000000
9.6 001 1010101
19.2 010 0110011
38.4 011 1100110
76.8 100 0001111
153.6 101 1011010
Reserved 110 0111100
Reserved 111 1101001
27
10-27
1 11.3.1.3.2.510.3.1.3.3.5 Data Rate Control Channel

2 The DRC Channel is used by the access terminal to indicate to the access network the
3 selected serving sector and the requested data rate on the Forward Traffic Channel. The
4 requested Forward Traffic Channel data rate is mapped into a four-bit DRC value as
5 specified by the Forward Traffic Channel MAC Protocol. An eight-ary Walsh function
6 corresponding to the selected serving sector is used to spread the DRC Channel
7 transmission. The cover mapping is defined by the public data DRCCover from the Forward
9 The DRC values shall be transmitted at a data rate of 600/DRCLength DRC values per
10 second, where DRCLength is public data from the Forward Traffic Channel MAC Protocol.
11 When DRCLength is greater than one, the DRC value and DRCCover inputs in Figure
12 10.3.1.3.1-3 are repeated for DRCLength consecutive slots as specified in the Forward
14 The DRC values shall be block encoded to yield eight-bit bi-orthogonal codewords, as
15 specified in Table 10.3.1.3.3.5-1. Each DRC codeword shall be transmitted twice per slot.
16 Each bit of a repeated codeword shall be spread by an eight-ary Walsh function Wi8 as
17 defined in Table 10.3.1.3.3.5-2, where i equals DRCCover. Each Walsh chip of the eight-ary
18 Walsh function is further spread by the Walsh function W816 . Each DRC value shall be
19 transmitted over DRCLength slots when the DRC Channel is continuously transmitted.
20 The access terminal may support gated DRC transmissions. For an access terminal that
21 supports gated DRC transmissions, it shall gate its DRC transmissions if the value of the
22 DRCGating attribute equals 1, where DRCGating is public data from the Forward Traffic
23 Channel MAC Protocol. When the DRC transmissions are gated, each DRC symbol shall be
24 transmitted over only one of every DRCLength slots as specified in the Forward Traffic
25 Channel MAC Protocol. Slots where the DRC Channel is not gated off are called active slots.
26 The DRC Channel is transmitted on the Q-branch as shown in Figure 10.3.1.3.1-3 and
27 Figure 10.3.1.3.1-4.
28 The timing of the Forward Traffic Channel transmission corresponding to a DRC symbol
29 shall be as specified by the Forward Traffic Channel MAC Protocol. The transmission of
30 DRC symbols shall start at the mid-slot point. The timing for the Default Forward Traffic
31 Channel MAC Protocol for nongated and gated transmission are shown in Figure
32 10.3.1.3.3.5-1 and Figure 10.3.1.3.3.5-2, respectively.
10-28
1 Table 10.3.1.3.3.5-1. DRC Bi-Orthogonal Encoding
DRC Value Codeword
0x0 00000000
0x1 11111111
0x2 01010101
0x3 10101010
0x4 00110011
0x5 11001100
0x6 01100110
0x7 10011001
0x8 00001111
0x9 11110000
0xA 01011010
0xB 10100101
0xC 00111100
0xD 11000011
0xE 01101001
0xF 10010110
2
3 Table 10.3.1.3.3.5-2. 8-ary Walsh Functions
W08 0000 0000
W18 0101 0101
W28 0011 0011
W38 0110 0110
W48 0000 1111
W58 0101 1010
W68 0011 1100
W78 0110 1001

4
10-29
One Slot
Forward Traffic Channel Slots
Where the Information in the
DRC Channel Transmission is
Used for New Physical Layer
Packet Transmissions
DRC Channel
Transmission
a) DRCLength = 1

DRC Channel
Transmission
b) DRCLength = 2

DRC Channel
Transmission
c) DRCLength = 4

DRC Channel
Transmission
d) DRCLength = 8
1
2 Figure 10.3.1.3.3.5-1. DRC Timing for Nongated Transmission
10-30
One Slot
DRC Channel
Transmission
a) DRCLength = 2

DRC Channel
Transmission
b) DRCLength = 4

DRC Channel
Transmission
c) DRCLength = 8
1
2 Figure 10.3.1.3.3.5-2. DRC Timing for Gated Transmission
3 11.3.1.3.2.610.3.1.3.3.6 ACK Channel

4 The ACK Channel is used by the access terminal to inform the access network whether a
5 physical layer packet transmitted on the Forward Traffic Channel has been received
6 successfully or not. The access terminal shall transmit an ACK Channel bit in response to
7 every Forward Traffic Channel slot that is associated with a detected preamble directed to
8 the access terminal. The access terminal shall transmit at most one redundant positive
9 ACK in response to a Forward Traffic Channel slot that is detected as a continuation of the
10 physical layer packet that has been successfully received. Otherwise, the ACK Channel
11 shall be gated off.
12 The ACK Channel shall be BPSK modulated. A ‘0’ bit (ACK) shall be transmitted on the ACK
13 Channel if a Forward Traffic Channel physical layer packet has been successfully received;
14 otherwise, a ‘1’ bit (NAK) shall be transmitted. A Forward Traffic Channel physical layer
15 packet is considered successfully received if the FCS checks. For a Forward Traffic Channel
16 physical layer packet transmitted in slot n on the Forward Channel, the corresponding ACK
17 Channel bit shall be transmitted in slot n + 3 on the Reverse Channel (see Figure
18 10.3.1.3.1-6 and Figure 10.3.1.3.1-7). The ACK Channel transmission shall be transmitted
19 in the first half of the slot and shall last for 1024 PN chips as shown in Figure 10.3.1.3.1-6
20 and Figure 10.3.1.3.1-7. The ACK Channel uses the Walsh channel identified by the Walsh
21 function W48 and shall be transmitted on the I-branch.
22 11.3.1.3.2.710.3.1.3.3.7 Data Channel

23 The Data Channel shall be transmitted at the data rates given in Table 10.3.1.3.4.1-1. Data
24 transmissions shall only begin at slot FrameOffset within a frame. The FrameOffset
10-31
1 parameter is public data of the Reverse Traffic Channel MAC Protocol. All data transmitted
2 on the Reverse Traffic Channel is encoded, block interleaved, sequence repeated, and
3 orthogonally spread by Walsh function W24 .
4 11.3.1.3.310.3.1.3.4 Encoding
5 11.3.1.3.3.110.3.1.3.4.1 Reverse Link Encoder Structure and Parameters

6 The Reverse Traffic Channel and Access Channel physical layer packets shall be encoded
7 with the encoder parameters as specified in Table 10.3.1.3.4.1-1. First, the encoder shall
8 discard the six bits of the TAIL field in the physical layer packet inputs (i.e., it shall discard
9 the last six bits in the input physical layer packets). Then, it shall encode the remaining
10 bits with a turbo encoder, as specified in 10.3.1.3.4.2. The turbo encoder shall add an
11 internally generated tail.
12 The encoder parameters shall be as specified in Table 10.3.1.3.4.1-1.
13 Table 10.3.1.3.4.1-1. Parameters for the Reverse Link Encoder
Data Rate
9.6 19.2 38.4 76.8 153.6
(kbps)
Reverse Rate Index 1 2 3 4 5

Bits per
Physical Layer 256 512 1,024 2,048 4,096
Packet
Number of Turbo
Encoder Input 250 506 1,018 2,042 4,090
Symbols
Turbo Encoder
1/4 1/4 1/4 1/4 1/2
Code Rate
Encoder Output
Block Length 1,024 2,048 4,096 8,192 8,192
(Code Symbols)
14
15 11.3.1.3.3.210.3.1.3.4.2 Turbo Encoding

16 The turbo encoder encodes the input data and adds an output tail sequence. If the total
17 number of input bits is Nturbo, the turbo encoder generates Nturbo/R encoded data output
18 symbols followed by 6/R tail output symbols, where R is the code rate of 1/2 or 1/4. The
19 turbo encoder employs two systematic, recursive, convolutional encoders connected in
20 parallel, with an interleaver, the turbo interleaver, preceding the second recursive
21 convolutional encoder.
22 The two recursive convolutional codes are called the constituent codes of the turbo code.
23 The outputs of the constituent encoders are punctured and repeated to achieve the (Nturbo
24 + 6)/R output symbols.
10-32
1 11.3.1.3.3.2.110.3.1.3.4.2.1 Turbo Encoders

2 A common constituent code shall be used for the turbo codes of rate 1/2 and 1/4. The
3 transfer function for the constituent code shall be
⎡ n0 (D) n1(D) ⎤
4 G(D) = ⎢1 ⎥
⎣ d(D) d(D) ⎥⎦
5 where d(D) = 1 + D2 + D3, n0(D) = 1 + D + D3, and n1(D) = 1 + D + D2 + D3.
6 The turbo encoder shall generate an output symbol sequence that is identical to the one
7 generated by the encoder shown in Figure 10.3.1.3.4.2.2-1. Initially, the states of the
8 constituent encoder registers in this figure are set to zero. Then, the constituent encoders
9 are clocked with the switches in the positions noted.
10 The encoded data output symbols are generated by clocking the constituent encoders
11 Nturbo times with the switches in the up positions and puncturing the outputs as specified
12 in Table 10.3.1.3.4.2.2-1. Within a puncturing pattern, a ‘0’ means that the symbol shall be
13 deleted and a ‘1’ means that the symbol shall be passed onwards. The constituent encoder
14 outputs for each bit period shall be output in the sequence X, Y0, Y1, X′, Y′0, Y′1 with the X
15 output first. Symbol repetition is not used in generating the encoded data output symbols.
16 11.3.1.3.3.2.210.3.1.3.4.2.2 Turbo Code Termination

17 The turbo encoder shall generate 6/R tail output symbols following the encoded data
18 output symbols. This tail output symbol sequence shall be identical to the one generated
19 by the encoder shown in Figure 10.3.1.3.4.2.2-1. The tail output symbols are generated
20 after the constituent encoders have been clocked Nturbo times with the switches in the up
21 position. The first 3/R tail output symbols are generated by clocking Constituent Encoder 1
22 three times with its switch in the down position while Constituent Encoder 2 is not clocked
23 and puncturing and repeating the resulting constituent encoder output symbols. The last
24 3/R tail output symbols are generated by clocking Constituent Encoder 2 three times with
25 its switch in the down position while Constituent Encoder 1 is not clocked and puncturing
26 and repeating the resulting constituent encoder output symbols. The constituent encoder
28 output first.
29 The constituent encoder output symbol puncturing and symbol repetition shall be as
30 specified in Table 10.3.1.3.4.2.2-2. Within a puncturing pattern, a ‘0’ means that the
31 symbol shall be deleted and a ‘1’ means that the symbol shall be passed onwards. For rate-
32 1/2 turbo codes, the tail output symbols for each of the first three tail bit periods shall be
33 XY0, and the tail output symbols for each of the last three tail bit periods shall be X′Y′0.
34 For rate-1/4 turbo codes, the tail output symbols for each of the first three tail bit periods
35 shall be XXY0Y1, and the tail output symbols for each of the last three tail bit periods shall
36 be X′X′Y′0Y′1.
10-33
Constituent Encoder 1
X
Y0
n0
Y1
n1
Nturbo
Information
Bits
(Input)
Control
Symbol ( Nturbo + 6) /R
Puncturing Code
Clocked once for each of the Nturbo data bit periods with the switch
and Symbols
up; then, clocked once for each of the three Constituent Encoder 1 Repetition (Output)
tail bit periods with the switch down; then, not clocked for the three
Constituent Encoder 2 tail bit periods.
Turbo
Interleaver
X'
Y'0
n0
Y'1
n1
Control
up; then, not clocked for the three Constituent Encoder 1
tail bit periods; then, clocked once for each of the three
Constituent Encoder 2 tail bit periods with the switch down.
1
2 Figure 10.3.1.3.4.2.2-1. Turbo Encoder
10-34
1 Table 10.3.1.3.4.2.2-1. Puncturing Patterns for the Data Bit Periods
Code Rate
Output 1/2 1/4
X 11 11
Y0 10 11
Y1 00 10
X′ 00 00
Y′0 01 01
Y′1 00 11
Note: For each rate, the puncturing table shall be read first from
top to bottom and then from left to right.
2
3 Table 10.3.1.3.4.2.2-2. Puncturing Patterns for the Tail Bit Periods
Code Rate
Output 1/2 1/4
X 111 000 111 000

Y0 111 000 111 000
Y1 000 000 111 000
X′ 000 111 000 111
Y′0 000 111 000 111
Y′1 000 000 000 111
Note: For rate-1/2 turbo codes, the puncturing table shall be
read first from top to bottom and then from left to right. For rate-
1/4 turbo codes, the puncturing table shall be read first from top
to bottom repeating X and X′, and then from left to right.
4
5 11.3.1.3.3.2.310.3.1.3.4.2.3 Turbo Interleavers

6 The turbo interleaver, which is part of the turbo encoder, shall block interleave the turbo
7 encoder input data that is fed to Constituent Encoder 2.
8 The turbo interleaver shall be functionally equivalent to an approach where the entire
9 sequence of turbo interleaver input bits are written sequentially into an array at a sequence
10 of addresses, and then the entire sequence is read out from a sequence of addresses that
11 are defined by the procedure described below.
10-35
1 Let the sequence of input addresses be from 0 to Nturbo – 1. Then, the sequence of
2 interleaver output addresses shall be equivalent to those generated by the procedure
3 illustrated in Figure 10.3.1.3.4.2.3-1 and described below.140
4 1. Determine the turbo interleaver parameter, n, where n is the smallest integer such
5 that Nturbo ≤ 2n+5. Table 10.3.1.3.4.2.3-1 gives this parameter for the different
6 physical layer packet sizes.
7 2. Initialize an (n + 5)-bit counter to 0.
8 3. Extract the n most significant bits (MSBs) from the counter and add one to form a
9 new value. Then, discard all except the n least significant bits (LSBs) of this value.
10 4. Obtain the n-bit output of the table lookup defined in Table 10.3.1.3.4.2.3-2 with a
11 read address equal to the five LSBs of the counter. Note that this table depends on
12 the value of n.
13 5. Multiply the values obtained in Steps 3 and 4, and discard all except the n LSBs.
14 6. Bit-reverse the five LSBs of the counter.
15 7. Form a tentative output address that has its MSBs equal to the value obtained in
16 Step 6 and its LSBs equal to the value obtained in Step 5.
17 8. Accept the tentative output address as an output address if it is less than Nturbo;
18 otherwise, discard it.
19 9. Increment the counter and repeat Steps 3 through 8 until all Nturbo interleaver
20 output addresses are obtained.
Add 1
n MSBs and n Bits MSBs
(in + 4…i5) Select the Next
n LSBs Multiply Discard (5 + n)-Bit
and n Bits LSBs If Interleaver
Select the (tn – 1…t0) Input ≥ Output
n LSBs Nturbo Address
(n + 5)-Bit Table n Bits (i0…i4tn – 1…t0)
Counter Lookup
5 LSBs Bit 5 Bits

(i4…i0) Reverse (i0…i4)
21
22 Figure 10.3.1.3.4.2.3-1. Turbo Interleaver Output Address Calculation Procedure
140 This procedure is equivalent to one where the counter values are written into a 25-row by
2n-column array by rows, the rows are shuffled according to a bit-reversal rule, the elements within
each row are permuted according to a row-specific linear congruential sequence, and tentative output
addresses are read out by column. The linear congruential sequence rule is x(i + 1) = (x(i) + c) mod 2n,
where x(0) = c and c is a row-specific value from a table lookup.
10-36
1 Table 10.3.1.3.4.2.3-1. Turbo Interleaver Parameter
Turbo Turbo
Physical Layer Interleaver Interleaver
Packet Size Block Size Parameter
Nturbo n
256 250 3
512 506 4
1,024 1,018 5
2,048 2,042 6
4,096 4,090 7
2
10-37
1 Table 10.3.1.3.4.2.3-2. Turbo Interleaver Lookup Table Definition
Table n=3 n=4 n=5 n=6 n=7

Index Entries Entries Entries Entries Entries
0 1 5 27 3 15
1 1 15 3 27 127
2 3 5 1 15 89
3 5 15 15 13 1
4 1 1 13 29 31
5 5 9 17 5 15
6 1 9 23 1 61
7 5 15 13 31 47
8 3 13 9 3 127
9 5 15 3 9 17
10 3 7 15 15 119
11 5 11 3 31 15
12 3 15 13 17 57
13 5 3 1 5 123
14 5 15 13 39 95
15 1 5 29 1 5
16 3 13 21 19 85
17 5 15 19 27 17
18 3 9 1 15 55
19 5 3 3 13 57
20 3 1 29 45 15
21 5 3 17 5 41
22 5 15 25 33 93
23 5 1 29 15 87
24 1 13 9 13 63
25 5 1 13 9 15
26 1 9 23 15 13
27 5 15 13 31 15
28 3 11 13 17 81
29 5 3 1 5 57
30 5 15 13 15 31
31 3 5 13 33 69
2
10-38
1 11.3.1.3.410.3.1.3.5 Channel Interleaving

2 The sequence of binary symbols at the output of the encoder shall be interleaved with a bit-
3 reversal channel interleaver.
4 The bit-reversal channel interleaver shall be functionally equivalent to an approach where
5 the entire sequence of symbols to be interleaved is written into a linear sequential array
6 with addresses from 0 to 2L – 1 and they are read out from a sequence of addresses based
7 on the procedure described below.
8 • The sequence of array addresses from which the interleaved symbols are read out is
9 generated by a bit-reversal address generator.
10 • The ith interleaved symbol is read out from the array element at address Ai that
11 satisfies:
12 Ai = Bit_Reversal(i, L)
13 where i = 0 to 2L – 1 and Bit_Reversal(y, L) indicates the bit-reversed L-bit value of y

14 such that if i is expressed in the binary form of i = bL–1bL–2…b1b0, where bk = 0 or
15 1, b0 is the LSB and bL-1 is the MSB, Ai = b0b1…bL–2bL–1.
16 • The bit-reversal interleaving process is completed when all of the symbols in the entire
17 linear array are read out.
18 Figure 10.3.1.3.5-1 illustrates the procedure for generating the channel interleaver output
19 address.
Counter
(Output i from 0 to 2L – 1 in Binary Form)
bL–1 bL–2 b1 b0
Bit_Reversal
b0 b1 bL–2 bL–1
Channel Interleaver Read Address A i

(Binary Representation)
20
21 Figure 10.3.1.3.5-1. Channel Interleaver Address Generation
22 11.3.1.3.510.3.1.3.6 Sequence Repetition

23 If the data rate is lower than 76.8 kbps, the sequence of interleaved code symbols shall be
24 repeated before being modulated. The number of repeats varies for each data rate and shall
10-39
1 be as specified in Table 10.3.1.3.1.1-1. The repetition shall be functionally equivalent to

2 sequentially reading out all the symbols from the interleaver memory as many times as
3 necessary to achieve the fixed 307.2-ksps modulation symbol rate.
4 11.3.1.3.610.3.1.3.7 Orthogonal Covers

5 The Pilot Channel, consisting of the time-division-multiplexed Pilot and RRI Channels, the
6 DRC Channel, the ACK Channel, and the Data Channel shall be spread with Walsh
7 functions, also called Walsh covers, at a fixed chip rate of 1.2288 Mcps. Walsh function
8 time alignment shall be such that the first Walsh chip begins at a slot boundary referenced
9 to the access terminal transmission time.
10 The Walsh cover assignments are shown in Figure 10.3.1.3.1-1, and Figure 10.3.1.3.1-2,
11 and Figure 10.3.1.3.1-3. The Pilot Channel shall be covered by the 16-chip Walsh function
12 number 0 ( W016 = + + + + + + + + + + + + + + + +). The DRC Channel shall be covered by the
13 16-chip Walsh function number 8 ( W816 = + + + + + + + + – – – – – – – –). The ACK Channel
14 shall be covered by the 8-chip Walsh function number 4 ( W48 = + + + + – – – –). The Data
15 Channel shall be covered by the 4-chip Walsh function number 2 ( W24 = + + – –).
16 11.3.1.3.710.3.1.3.8 Quadrature Spreading

17 Following the orthogonal spreading, the ACK, DRC, and Data Channel chip sequences shall
18 be scaled by a factor that gives the gain of each of these channels relative to that of the
19 Pilot Channel. The relative gain values for the ACK and DRC Channels are specified by the
20 parameters ACKChannelGain and DRCChannelGain which are public data of the Forward
21 Traffic Channel MAC Protocol. For the Reverse Traffic Channel, the relative gain of the Data
22 Channel is specified by parameters that are public data of the Reverse Traffic Channel MAC
23 Protocol as described in 10.3.1.2.4.1. For the Access Channel, the relative gain of the Data
24 Channel is specified by parameters that are public data of the Access Channel MAC
25 Protocol as described in 10.3.1.2.4.1.
26 After the scaling, the Pilot and scaled ACK, DRC, and Data Channel sequences are
27 combined to form resultant I-Channel and Q-Channel sequences, and these sequences are
28 quadrature spread as shown in Figure 10.3.1.3.1-1, Figure 10.3.1.3.1-2, and Figure
29 10.3.1.3.1-4. The quadrature spreading shall occur at the chip rate of 1.2288 Mcps, and it
30 shall be used for the Reverse Traffic Channel and the Access Channel. The Pilot and scaled
31 ACK Channel sequences shall be added to form the resultant I-Channel sequence, and the
32 scaled DRC and Data Channel sequences shall be added to form the resultant Q-Channel
33 sequence. The quadrature spreading operation shall be equivalent to a complex multiply
34 operation of the resultant I-Channel and resultant Q-Channel sequences by the PNI and
35 PNQ PN sequences, as shown in Figure 10.3.1.3.1-1,Figure 10.3.1.3.1-2, and Figure
36 10.3.1.3.1-4.
37 The I and Q PN sequences, PNI and PNQ, shall be obtained from the long-code PN
38 sequences, UI and UQ, and the access terminal common short PN sequences, PI and PQ.
39 The binary long-code PN sequence and short PN sequence values of ‘0’ and ‘1’ shall be
40 mapped into values of +1 and –1, respectively.
10-40
1 The bipolar PNI sequence values shall be equivalent to those obtained by multiplying the
2 bipolar PI values by the bipolar UI values.
3 The bipolar PNQ sequence values shall be equivalent to those obtained with the following
4 procedure:
5 1. Multiply the bipolar PQ values by the bipolar UQ values.
6 2. Decimate the sequence of values obtained in Step 1 by a factor of two. That is, the
7 decimator provides an output that is constant for two consecutive chips by deleting
8 every other input value and repeating the previous input value in place of the
9 deleted value. The retained values shall align with the first chip of a slot.
10 3. Multiply pairs of decimator output symbols by the Walsh cover sequence (+ –). That
11 is, pass the first value of every pair unchanged and multiply the second value of
12 every pair by –1.
13 4. Multiply the sequence obtained in Step 3 by the bipolar PNI sequence.
14 11.3.1.3.7.110.3.1.3.8.1 Access Terminal Common Short-Code PN Sequences

15 The access terminal common short-code PN sequences shall be the zero-offset I and Q PN
16 sequences with a period of 215 chips, and they shall be based on the following
17 characteristic polynomials, respectively:
18 PI(x) = x15 + x13 + x9 + x8 + x7 + x5 + 1
19 (for the in-phase (I) sequence)

20 and
21 PQ(x) = x15 + x12 + x11 + x10 + x6 + x5 + x4 + x3 + 1
22 (for the quadrature-phase (Q) sequence).

23 The maximum length linear feedback shift-register sequences {I(n)} and {Q(n)} based on the
24 above are of length 215 – 1 and can be generated by the following linear recursions:
25 I(n) = I(n – 15) ⊕ I(n – 10) ⊕ I(n – 8) ⊕ I(n – 7) ⊕ I(n – 6) ⊕ I(n – 2)
26 (based on PI(x) as the characteristic polynomial)
27 and
28 Q(n) = Q(n – 15) ⊕ Q(n – 12) ⊕ Q(n – 11) ⊕ Q(n – 10) ⊕ Q(n – 9) ⊕
29 Q(n – 5) ⊕ Q(n – 4) ⊕ Q(n – 3)
30 (based on PQ(x) as the characteristic polynomial),
31 where I(n) and Q(n) are binary valued (‘0’ and ‘1’) and the additions are modulo-2. In order
32 to obtain the I and Q common short-code PN sequences (of period 215), a ‘0’ is inserted in
33 the {I(n)} and {Q(n)} sequences after 14 consecutive ‘0’ outputs (this occurs only once in
34 each period). Therefore, the short-code PN sequences have one run of 15 consecutive ‘0’
35 outputs instead of 14. The initial state of the access terminal common short-code PN
36 sequences, both I and Q, shall be that state in which the output of the short-code PN
37 sequence generator is the ‘1’ following the 15 consecutive ‘0’ outputs.
10-41
1 The chip rate for the access terminal common short-code PN sequence shall be 1.2288
2 Mcps. The short-code PN sequence period is 32768/1228800 = 26.666… ms, and exactly
3 75 PN sequences repetitions occur every 2 seconds.
4 The access terminal shall align the I and Q short-code PN sequences such that the first
5 chip on every even-second mark as referenced to the transmit time reference (see 10.3.1.7)
6 is the ‘1’ after the 15 consecutive ‘0’s (see Figure 1.14-1).
7 11.3.1.3.7.210.3.1.3.8.2 Long Codes

8 The in-phase and quadrature-phase long codes, UI and UQ, shall be generated from a
9 sequence, called the long-code generating sequence, by using two different masks. The
10 long-code generating sequence shall satisfy the linear recursion specified by the following
11 characteristic polynomial:
12 p(x) = x42 + x35 + x33 + x31 + x27 + x26 + x25 + x22 + x21 + x19 +
13 x18 + x17 + x16 + x10 + x7 + x6 + x5 + x3 + x2 + x + 1.
14 The long codes, UI and UQ, shall be generated by a modulo-2 inner product of the 42-bit
15 state vector of the sequence generator and two 42-bit masks, MI and MQ, respectively, as
16 shown in Figure 10.3.1.3.8.2-1. The masks MI and MQ vary depending on the channel on
17 which the access terminal is transmitting.
18 For transmission on the Access Channel, MI and MQ shall be set to MIACMAC and
19 MQACMAC (given as public data of the Access Channel MAC Protocol), respectively, and the
20 long-code sequences are referred to as the access long codes.
21 For transmission on the Reverse Traffic Channel, MI and MQ shall be set to MIRTCMAC and
22 MQRTCMAC (given as public data of the Reverse Traffic Channel MAC Protocol),
23 respectively, and the long-code sequences are referred to as the user long codes.
24 The long code generator shall be reloaded with the hexa-decimal value 0x24B91BFD3A8 at
25 the beginning of every period of the short codes. Thus, the long codes are periodic with a
26 period of 215 PN chips.
10-42
MI41
x 42
42
MI40
x 41
41
x 40
40
x 39
Modulo-2
UI
Addition
39
x8
8 MI1
MI0
x7
x6
6
MQ41
x5
MQ40
x4
Modulo-2
x3 UQ
Addition
x2
MQ1
2
MQ0
x
2 Figure 10.3.1.3.8.2-1. Long Code Generators
10-43
1 11.3.1.3.7.310.3.1.3.8.3 Baseband Filtering

2 Following the quadrature spreading operation, the I’ and Q’ impulses are applied to the
3 inputs of the I and Q baseband filters as shown in Figure 10.3.1.3.1-1, Figure 10.3.1.3.1-2,
4 and Figure 10.3.1.3.1-4. The baseband filters shall have a frequency response S(f) that
5 satisfies the limits given in Figure 10.3.1.3.8.3-1. Specifically, the normalized frequency
6 response of the filter shall be contained within ±δ1 in the passband 0 ≤ f ≤ fp and shall be
7 less than or equal to –δ2 in the stopband f ≥ fs. The numerical values for the parameters
8 are δ1 = 1.5 dB, δ2 = 40 dB, fp = 590 kHz, and fs = 740 kHz.
20 log10 S(f )
δ1
δ1
δ2
f
0 fp fs
9
10 Figure 10.3.1.3.8.3-1. Baseband Filter Frequency Response Limits
11 The impulse response of the baseband filter, s(t), should satisfy the following equation:
∞
12 Mean Squared Error = ∑
k =0
[αs(kTs – τ) – h(k)]2 ≤ 0.03,
13 where the constants α and τ are used to minimize the mean squared error. The constant Ts
14 is equal to 203.451… ns, which equals one quarter of a PN chip. The values of the
15 coefficients h(k), for k < 48, are given in Table 10.3.1.3.8.3-1; h(k) = 0 for k ≥ 48. Note that
16 h(k) equals h(47 – k).
10-44
1 Table 10.3.1.3.8.3-1. Baseband Filter Coefficients
k h(k)
0, 47 –0.025288315
1, 46 –0.034167931
2, 45 –0.035752323
3, 44 –0.016733702
4, 43 0.021602514
5, 42 0.064938487
6, 41 0.091002137
7, 40 0.081894974
8, 39 0.037071157
9, 38 –0.021998074
10, 37 –0.060716277
11, 36 –0.051178658
12, 35 0.007874526
13, 34 0.084368728
14, 33 0.126869306
15, 32 0.094528345
16, 31 –0.012839661
17, 30 –0.143477028
18, 29 –0.211829088
19, 28 –0.140513128
20, 27 0.094601918
21, 26 0.441387140
22, 25 0.785875640
23, 24 1.0
2
3 11.3.1.410.3.1.4 Closed-Loop Power-Control Operation

4 Once the connection is established, the access network continuously transmits ‘0’ (up) or
5 ‘1’ (down) RPC bits to the access terminal, based on measurements of the reverse link
6 signal quality. If the received quality is above the target threshold, a ‘1’ bit is transmitted. If
7 the received quality is below the target threshold, a ‘0’ bit is transmitted.
8 If the access terminal did not transmit on the Reverse Traffic Channel in slot n, then it
9 shall ignore the received RPC bit in slot n + 1. Otherwise, the access terminal shall adjust
10 its output power by a discrete amount in the direction indicated by the RPC bit after the
10-45
1 RPC bit is received as specified in 10.3.1.2.4.2 and 10.3.1.2.5.2. The RPC bit is considered
2 received after the 64-chip MAC burst following the second pilot burst of a slot which
3 contains an RPC bit as shown in Figure 10.4.1.3.1-2.
4 The SofterHandoff public data of the Route Update Protocol indicates whether or not two
5 different sectors are transmitting the same RPC bit. In each slot containing power-control
6 bits, the access terminal should provide diversity combining of the identical RPC Channels
7 and shall obtain at most one power-control bit from each set of identical RPC Channels.
8 The access terminal shall increase its output power if all the resulting RPC bits are ‘0’
9 (“up”). If any resulting RPC bit is ‘1’ (“down”), the access terminal shall decrease its output
10 power as specified in 10.3.1.2.4.2.
11 11.3.1.510.3.1.5 Reception of the DRCLock Channel

12 Once the connection is established, the access network continuously transmits ‘0’ or ‘1’
13 DRCLock bits to the access terminal on the DRCLock Channel. The access terminal shall
14 process the DRCLock bits received on the DRCLock Channel as specified by the Forward
15 Traffic Channel MAC protocol.
17 different sectors are transmitting the same DRCLock bit. In each slot containing a
18 DRCLock bit, the access terminal should provide diversity combining of the identical
19 DRCLock Channels and shall obtain at most one DRCLock bit from each set of identical
20 DRCLock Channels.
21 11.3.1.610.3.1.6 Reception of the Reverse Activity Channel

22 Once the connection is established, the access terminal shall process the RA bit for each
23 sector in its active set along with the RAChannelGain public data of the Reverse Traffic
24 Channel MAC protocol, to generate the log-likelihood ratio LLRrab if the access terminal
25 has negotiated subtype 2 Reverse Traffic Channel MAC protocol.
26 If the access terminal has negotiated subtype 2 Reverse Traffic Channel MAC protocol, the
27 access terminal shall map the log-likelihood ratio (LLR) of the RA bit demodulation, LLRrab
28 for each sector in the access terminal’s active set from a range of [-∞, +∞] to a range of [-1,
29 +1] to generate SoftRAB for each sector in the access terminal’s active set using the
30 following function:
31 SoftRAB = 0.4 × LLRrab, -2.5 ≤ LLRrab ≤ 2.5
32 SoftRAB = +1, LLRrab > 2.5
33 SoftRAB = -1, LLRrab < -2.5
34 where -1 ≤ SoftRAB ≤ 1 and SoftRAB is a real valued input for the Reverse Traffic Channel
35 MAC Protocol.
36 11.3.1.710.3.1.7 Synchronization and Timing

37 The nominal relationship between the access terminal and access network transmit and
38 receive time references shall be as shown in Figure 1.14-1. The access terminal shall
39 establish a time reference that is used to derive timing for the transmitted chips, symbols,
10-46
1 slots, frames, and system timing. The access terminal initial time reference shall be
2 established from the acquired Pilot Channel and from the Sync message transmitted on the
3 Control Channel. Under steady-state conditions, the access terminal time reference shall
4 be within ±1 μs of the time of occurrence, as measured at the access terminal antenna
5 connector, of the earliest arriving multipath component being used for demodulation. If
6 another multipath component belonging to the same Pilot Channel or to a different Pilot
7 Channel becomes the earliest arriving multipath component to be used, the access
8 terminal time reference shall track to the new component. If the difference between the
9 access terminal time reference and the time of occurrence of the earliest arriving multipath
10 component being used for demodulation, as measured at the access terminal antenna
11 connector, is less than ±1 μs, the access terminal may directly track its time reference to
12 the earliest arriving multipath component being used for demodulation.
13 If an access terminal time reference correction is needed, it shall be corrected no faster
14 than 203 ns (1/4 chip) in any 200-ms period and no slower than 305 ns (3/8 PN chip) per
15 second.
16 The access terminal time reference shall be used as the transmit time reference of the
17 Reverse Traffic Channel and the Access Channel.
10-47
1 11.410.4 Access Network Requirements

2 This section defines requirements specific to access network equipment and operation.
4 The transmitter shall reside in each sector of the access network. These requirements apply
5 to the transmitter in each sector.

7 The access network shall meet the requirements in the current version of [15].

9 The average frequency difference between the actual sector transmit carrier frequency and
10 the specified sector transmit frequency assignment shall be less than ±5 × 10-8 of the
11 frequency assignment (±0.05 ppm).

15 11.4.1.3.110.4.1.3.1 Forward Channel Structure

16 The Forward Channel shall have the overall structure shown in Figure 10.4.1.3.1-1. The
17 Forward Channel shall consist of the following time-multiplexed channels: the Pilot
18 Channel, the Forward Medium Access Control (MAC) Channel, and the Forward Traffic
19 Channel or the Control Channel. The Traffic Channel carries user physical layer packets.
20 The Control Channel carries control messages, and it may also carry user traffic. Each
21 channel is further decomposed into code-division-multiplexed quadrature Walsh channels.
22 The forward link shall consist of slots of length 2048 chips (1.66… ms). Groups of 16 slots
23 shall be aligned to the PN rolls of the zero-offset PN sequences and shall align to CDMA
24 System Time on even-second ticks.
25 Within each slot, the Pilot, MAC, and Traffic or Control Channels shall be time-division
26 multiplexed as shown in Figure 10.4.1.3.1-2 and shall be transmitted at the same power
27 level.
28 The Pilot Channel shall consist of all-‘0’ symbols transmitted on the I-branch with Walsh
29 cover 0. Each slot shall be divided into two half slots, each of which contains a pilot burst.
30 Each pilot burst shall have a duration of 96 chips and be centered at the midpoint of the
31 half slot.141
141 The pilot is used by the access terminal for initial acquisition, phase recovery, timing recovery,
and maximal-ratio combining. An additional function of the pilot is to provide the access terminal
10-48
1 The MAC Channel shall consist of three subchannels: the Reverse Power Control (RPC)
2 Channel, the DRCLock Channel, and the Reverse Activity (RA) Channel. The RA Channel
3 transmits a reverse link activity bit (RAB) stream.
4 Each MAC Channel symbol shall be BPSK modulated on one of 64 64-ary Walsh codewords
5 (covers). The MAC symbol Walsh covers shall be transmitted four times per slot in bursts of
6 64 chips each. A burst shall be transmitted immediately preceding each of the pilot bursts
7 in a slot, and a burst shall be transmitted immediately following each of the pilot bursts in
8 a slot. The Walsh channel gains may vary the relative power.
9 The Forward Traffic Channel is a packet-based, variable-rate channel. The user physical
10 layer packets for an access terminal shall be transmitted at a data rate that varies from
11 38.4 kbps to 2.4576 Mbps.142
12 The Forward Traffic Channel and Control Channel data shall be encoded in blocks called
13 physical layer packets. The output of the encoder shall be scrambled and then fed into a
14 channel interleaver. The output of the channel interleaver shall be fed into a QPSK/8-
15 PSK/16-QAM modulator. The modulated symbol sequences shall be repeated and
16 punctured, as necessary. Then, the resulting sequences of modulation symbols shall be
17 demultiplexed to form 16 pairs (in-phase and quadrature) of parallel streams. Each parallel
18 stream with a rate of 76.8ksps is covered with a distinct walsh function of length 16. The
19 Walsh-coded symbols of all the streams shall be summed together to form a single in-phase
20 stream and a single quadrature stream at a chip rate of 1.2288 Mcps. The resulting chips
21 are time-division multiplexed with the preamble, Pilot Channel, and MAC Channel chips to
22 form the resultant sequence of chips for the quadrature spreading operation.
23 Forward Traffic Channel and Control Channel physical layer packets can be transmitted in
24 1 to 16 slots (see Table 10.4.1.3.1.1-1 and Table 10.4.1.3.1.1-2). When more than one slot
25 is allocated, the transmit slots shall use 4-slot interlacing. That is, the transmit slots of a
26 physical layer packet shall be separated by three intervening slots, and slots of other
27 physical layer packets shall be transmitted in the slots between those transmit slots. If a
28 positive acknowledgment is received on the reverse link ACK Channel before all of the
29 allocated slots have been transmitted, the remaining untransmitted slots shall not be
30 transmitted and the next allocated slot may be used for the first slot of the next physical
31 layer packet transmission.
32 Figure 10.4.1.3.1-3 and Figure 10.4.1.3.1-4 illustrate the multislot interlacing approach for
33 a 153.6 kbps Forward Traffic Channel with DRCLength of one slot. The 153.6 kbps
34 Forward Traffic Channel physical layer packets use four slots, and these slots are
35 transmitted with a three-slot interval between them, as shown in the figures. The slots from
36 other physical layer packets are interlaced in the three intervening slots. Figure 10.4.1.3.1-
37 3 shows the case of a normal physical layer packet termination. In this case, the access
38 terminal transmits NAK responses on the ACK Channel after the first three slots of the
with a means of predicting the receive C/I for the purpose of access-terminal-directed forward data
rate control (DRC) of the Data Channel transmission.
142 The DRC symbol from the access terminal is based primarily on its estimate of the forward C/I for
the duration of the next possible forward link packet transmission.
10-49
1 physical layer packet are received indicating that it was unable to correctly receive the
2 Forward Traffic Channel physical layer packet after only one, two, or three of the nominal
3 four slots. An ACK or NAK is also transmitted after the last slot is received, as shown.
10 When the access network has transmitted all the slots of a physical layer packet or has
11 received a positive ACK response, the physical layer shall return a ForwardTrafficCompleted
12 indication.
13 The Control Channel shall be transmitted at a data rate of 76.8 kbps or 38.4 kbps. The
14 modulation characteristics for the Control Channel shall be the same as those of the
15 Forward Traffic Channel transmitted at the corresponding rate.
16 The Forward Traffic Channel and Control Channel data symbols shall fill the slot as shown
17 in Figure 10.4.1.3.1-2. A slot during which no traffic or control data is transmitted is
18 referred to as an idle slot. During an idle slot, the sector shall transmit the Pilot Channel
19 and the MAC Channel, as described earlier.
10-50
Forward Traffic I
QPSK/ C
Channel or Encoder
Channel 8-PSK/
Control Channel R = 1/3
Interleaver 16-QAM Q
Physical Layer or 1/5
Modulator D
Packets
Scrambler 16 Channels
I I I I I I
C Sequence Walsh
Symbol 16-ary Walsh
Repetition/ Channel
DEMUX Walsh Chip Level
Q Symbol Q Q Q Gain = Q Q
1 to 16 Covers Summer
D Puncturing 1/4
32-Symbol Bi-
Orthogonal Cover
with MACIndex i
Signal Point
Preamble Mapping Sequence I
(All 0's) 0 +1 Repetition
1 –1
Q
0
64-ary Walsh Cover for
I Channel for
MACIndex i 64 to 1,024
Even MACIndex
Signal Point Q Channel for PN Chips I Walsh
MAC Channel RPC Bits for per Physical Channels
Mapping RPC Channel Odd MACIndex
MACIndex i Layer Packet
0 +1 Gain: G(i)
600 (1-1/DRCLockPeriod) bps for Preamble A
1 –1
MAC Channel DRCLock TDM TDM
Bit Signal Point
symbols for MACIndex i DRCLock B
Repetition Mapping
(600/DRCLockLength) Channel Gain: I I
(Factor = 0 +1 G'(i)
(1/DRCLockPeriod) bits Walsh Sequence Q Walsh
DRCLockLength) 1 –1
per second Chip Level Repetition Channels
Walsh Cover W264 Summer Q (Factor = 4) Q
MAC Channel Signal Point I

RA 256 PN
RA Bits Mapping
Channel Chips
1 Bit per Slot 0 +1
Gain per Slot
(600 bps) 1 –1
for MAC
Walsh Cover 0
Signal Point
Pilot Channel Mapping I
(All 0’s) 0 +1
1 –1
Q
0
cos(2 fCt)
192 PN
Chips
per Slot
I I Baseband for Pilot
A
Filter
Quadrature
Spreading Forward
(Complex Multiply) Modulated
I = I PNI – Q PNQ Waveform
Q = I PNQ + Q PNI
Q Q Baseband
B
Filter

sin(2 fCt) sequences are represented with 1
PNI PNQ values with the mapping +1 for
I-Channel Q-Channel binary ‘0’ and –1 for binary ‘1’.
1.2288 Mcps 1.2288 Mcps
1
2 Figure 10.4.1.3.1-1. Forward Channel Structure
10-51
1/2 Slot 1/2 Slot

1,024 Chips 1,024 Chips
Data MAC Pilot MAC Data Data MAC Pilot MAC Data
400 64 96 64 400 400 64 96 64 400
Chips Chips Chips Chips Chips Chips Chips Chips Chips Chips
Active Slot
MAC Pilot MAC MAC Pilot MAC

64 96 64 64 96 64
Chips Chips Chips Chips Chips Chips
Idle Slot
1
2 Figure 10.4.1.3.1-2. Forward Link Slot Structure

Channel Physical
Layer Packet
Transmissions
with 153.6 kbps
DRC Channel
Transmission
Requesting
153.6 kbps
DRC
Request for
ACK Channel
Half-Slot
Transmissions
NAK NAK NAK ACK
One Slot
or
3 NAK
4 Figure 10.4.1.3.1-3. Multislot Physical Layer Packet with Normal Termination
10-52

Transmission

Forward Traffic
Channel Physical
Layer Packet
Transmissions
with 153.6 kbps
DRC Channel
Transmission
Requesting
153.6 kbps
DRC
Request for
ACK Channel
Half-Slot
Transmissions
NAK NAK ACK

One Slot
1
2 Figure 10.4.1.3.1-4. Multislot Physical Layer Packet with Early Termination

4 The modulation parameters for the Forward Traffic Channel and the Control Channel shall
5 be as shown in Table 10.4.1.3.1.1-1 and Table 10.4.1.3.1.1-2. The Control Channel shall
6 only use the 76.8 kbps and 38.4 kbps data rates.
10-53
1 Table 10.4.1.3.1.1-1. Modulation Parameters for the Forward Traffic Channel and the
2 Control Channel (Part 1 of 2)
Number of Values per Physical Layer Packet
Data TDM Chips

Rate (Preamble,
Code Modulation
(kbps) Slots Bits Pilot,
Rate Type
MAC,
Data)
1,024
3,072
38.4 16 1,024 1/5 QPSK
4,096
24,576
512
1,536
76.8 8 1,024 1/5 QPSK
2,048
12,288
256
768
153.6 4 1,024 1/5 QPSK
1,024
6,144
128
384
307.2 2 1,024 1/5 QPSK
512
3,072
64
192
614.4 1 1,024 1/3 QPSK
256
1,536
3
10-54
2 Control Channel (Part 2 of 2)
Number of Values per Physical Layer Packet
Data TDM Chips

Rate (Preamble,
Code Modulation
(kbps) Slots Bits Pilot,
Rate Type
MAC,
Data)
128
768
307.2 4 2,048 1/3 QPSK
1,024
6,272
64
384
614.4 2 2,048 1/3 QPSK
512
3,136
64
192
1,228.8 1 2,048 1/3 QPSK
256
1,536
64
384
921.6 2 3,072 1/3 8-PSK
512
3,136
64
192
1,843.2 1 3,072 1/3 8-PSK
256
1,536
64
384
1,228.8 2 4,096 1/3 16-QAM
512
3,136
64
192
2,457.6 1 4,096 1/3 16-QAM
256
1,536
3
4 The modulation parameters for the MAC Channel shall be as shown in Table 10.4.1.3.1.1-
5 3.
10-55
1 Table 10.4.1.3.1.1-3. Modulation Parameters for the MAC Channel
Parameter RPC Channel DRCLock Channel RA Channel

600 × 600/(DRCLockLength × 600
Rate (bps) DRCLockPeriod)
(1−1/DRCLockPeriod)
Bit Repetition
1 DRCLockLength 1
Factor
Modulation BPSK BPSK BPSK
(Channel) (I or Q) (I or Q) (I)
Modulation 2,400 ×
Symbol Rate (1−1/DRCLockPeriod) 2,400/DRCLockPeriod 2,400
(sps)
Walsh Cover
64 64 64
Length
Walsh Sequence
Repetition 4 4 4
Factor
PN Chips/Slot 256 256 256
PN Chips/Bit 256 256 × DRCLockLength 256
2
3 11.4.1.3.1.210.4.1.3.1.2 Data Rates

4 The Forward Traffic Channel shall support variable-data-rate transmission from 38.4 kbps
5 to 2.4576 Mbps, as shown in Table 10.4.1.3.1.1-1 and Table 10.4.1.3.1.1-2.
6 The data rate of the Control Channel shall be 76.8 kbps or 38.4 kbps.
7 11.4.1.3.210.4.1.3.2 Forward Link Channels
8 11.4.1.3.2.110.4.1.3.2.1 Pilot Channel

9 A Pilot Channel shall be transmitted by the sector on each active Forward Channel as
10 described in 10.4.1.3.1. The Pilot Channel is an unmodulated signal that is used for
11 synchronization and other functions by an access terminal operating within the coverage
12 area of the sector. The Pilot Channel shall be transmitted at the full sector power.
13 11.4.1.3.2.1.110.4.1.3.2.1.1 Modulation
14 The Pilot Channel shall consist of all-‘0’ symbols transmitted on the I component only.
15 11.4.1.3.2.1.210.4.1.3.2.1.2 Orthogonal Spreading

16 The Pilot Channel shall be assigned Walsh cover 0.
17 11.4.1.3.2.1.310.4.1.3.2.1.3 Quadrature Spreading

18 See 10.4.1.3.4.
10-56
1 11.4.1.3.2.210.4.1.3.2.2 Forward MAC Channel

2 The Forward MAC Channel shall be composed of Walsh channels that are orthogonally
3 covered and BPSK modulated on a particular phase of the carrier (either in-phase or
4 quadrature phase). Each Walsh channel shall be identified by a MACIndex value that is
5 between 0 and 63 and defines a unique 64-ary Walsh cover and a unique modulation
6 phase. The Walsh functions assigned to the MACIndex values shall be as follows:
64
Wi/2 for i = 0, 2,…, 62
7
W(i64
−1)/2+ 32 for i = 1, 3,…, 63
8 where i is the MACIndex value. MAC Channels with even-numbered MACIndex values shall
9 be assigned to the in-phase (I) modulation phase, while those with odd-numbered
10 MACIndex values shall be assigned to the quadrature (Q) modulation phase. The MAC
11 symbol Walsh covers shall be transmitted four times per slot in bursts of length 64 chips
12 each. These bursts shall be transmitted immediately preceding and following the pilot
13 bursts of each slot.
14 The MAC Channel use versus MACIndex shall be as specified in Table 10.4.1.3.2.1.3-1.
15 Symbols of each MAC Channel shall be transmitted on one of the Walsh channels. The
16 MAC channel gains may vary the relative power as a function of time. The orthogonal
17 Walsh channels shall be scaled to maintain a constant total transmit power. The Walsh
18 Channel gains can vary as a function of time.
19 Table 10.4.1.3.2.1.3-1. MAC Channel and Preamble Use Versus MACIndex
MACIndex MAC Channel Use Preamble Use
0 and 1 Not Used Not Used

Not Used 76.8 kbps Control
2
Channel
Not Used 38.4 kbps Control
3
Channel
4 RA Channel Not Used
Available for RPC Available for Forward
Channel and DRCLock Traffic Channel if
5
Channel Broadcast is not
Transmissions negotiated
Available for RPC
Available for Forward
Channel and DRCLock
6–63 Traffic Channel
Channel
Transmissions
Transmissions
20
10-57
1 11.4.1.3.2.2.110.4.1.3.2.2.1 Reverse Power Control Channel

2 The Reverse Power Control (RPC) Channel for each access terminal with an open
3 connection shall be assigned to one of the available MAC Channels. It is used for the
4 transmission of the RPC bit stream destined to that access terminal. The RPC Channel and
5 the DRCLock Channel shall be time-division multiplexed and transmitted on the same
6 MAC Channel. The RPC Channel shall be transmitted in DRCLockPeriod – 1 slots out of
7 every DRCLockPeriod slots, where DRCLockPeriod is given as public data by the Forward
9 The RPC data rate shall be 600 × (1 − 1/DRCLockPeriod) bps. The access network shall
10 transmit an RPC bit in every slot T with
11 (T − FrameOffset) mod DRCLockPeriod ≠ 0.
12 Each RPC bit shall be transmitted four times in a slot in bursts of 64 chips each. One burst
13 shall be transmitted immediately preceding and following each pilot burst in a slot as
14 shown in Figure 10.4.1.3.1-2.
15 11.4.1.3.2.2.210.4.1.3.2.2.2 DRCLock Channel

16 The DRCLock Channel for each access terminal with an open connection shall be assigned
17 to one of the available MAC Channels. It is used for the transmission of the DRCLock bit
18 stream destined to that access terminal. The RPC Channel and the DRCLock Channel are
19 time-division multiplexed and transmitted on the same MAC Channel. The DRCLock
20 Channel shall be transmitted in one out of every DRCLockPeriod slots.
21 Each DRCLock bit shall be repeated and transmitted in DRCLockLength slots,143 where
22 DRCLockLength is given as public data by the Forward Traffic Channel MAC Protocol. The
23 DRCLock data rate shall be 600/(DRCLockLength × DRCLockPeriod) bps. The access
24 network shall transmit a DRCLock bit in every slot T with
25 (T − FrameOffset) mod DRCLockPeriod = 0.
26 Each DRCLock bit shall be transmitted four times in a slot in bursts of 64 chips each. One
27 burst shall be transmitted immediately preceding and following each pilot burst in a slot as
29 The value of the DRCLock bit may change only in slot T with
30 (T − FrameOffset) mod (DRCLockLength × DRCLockPeriod) = 0.
31 An example for the transmission of DRCLock bits with DRCLockLength equal to 8 and
32 DRCLockPeriod equal to 8 is shown in Figure 10.4.1.3.2.2.2-1.
33
143 Repeated DRCLock bits are transmitted in slots that are DRCLockPeriod slots apart.
10-58
DRCLock bit repeated DRCLock bit repeated

DRCLockLength times DRCLockLength times
slot
DRCLockPeriod DRCLock symbol is sent Time

once every DRCLockPeriod
slots
Legend Note:
DRCLock bit In this figure:
DRCLockLength = 8
RPC bit DRCLockPeriod = 8
1
2 Figure 10.4.1.3.2.2.2-1. DRCLock Puncturing Example
3 11.4.1.3.2.2.310.4.1.3.2.2.3 Reverse Activity Channel

4 The Reverse Activity (RA) Channel shall transmit the Reverse Activity Bit (RAB) stream over
5 the MAC Channel with MACIndex 4.
6 The RA Channel data rate shall be 600 bps. The RA bit in each slot shall be further
7 repeated to form four symbols per slot for transmission.
9 11.4.1.3.2.3.110.4.1.3.2.3.1 Forward Traffic Channel Preamble

10 A preamble sequence shall be transmitted with each Forward Traffic Channel and Control
11 Channel physical layer packet in order to assist the access terminal with synchronization
12 of each variable-rate transmission.
13 The preamble shall consist of all-‘0’ symbols transmitted on the in-phase component only.
14 The preamble shall be time multiplexed into the Forward Traffic Channel stream as
15 described in 10.4.1.3.3. The preamble sequence shall be covered by a 32-chip bi-
16 orthogonal sequence and the sequence shall be repeated several times depending on the
17 transmit mode. The bi-orthogonal sequence shall be specified in terms of the 32-ary Walsh
18 functions and their bit-by-bit complements by
32
Wi/2 for i = 0, 2,…, 62
19
W(i32
−1)/2 for i = 1, 3,…, 63
20 where i = 0, 1,…, 63 is the MACIndex value and Wi32 is the bit-by-bit complement of the
21 32-chip Walsh function of order i.
22 The channel type versus MACIndex mapping for the preamble shall be as specified in Table
23 10.4.1.3.2.1.3-1.
24 The 32-chip preamble repetition factor shall be as specified in Table 10.4.1.3.2.3.1-1.
10-59
1 Table 10.4.1.3.2.3.1-1. Preamble Repetition
Values per Physical Layer Packet

Data 32-Chip
Rate Preamble Preamble
(kbps) Slots
Sequence Chips
Repetitions
38.4 16 32 1,024
76.8 8 16 512
153.6 4 8 256
307.2 2 4 128
614.4 1 2 64
307.2 4 4 128
614.4 2 2 64
1,228.8 1 2 64
921.6 2 2 64
1,843.2 1 2 64
1,228.8 2 2 64
2,457.6 1 2 64
2
3 11.4.1.3.2.3.210.4.1.3.2.3.2 Encoding
4 The Traffic Channel physical layer packets shall be encoded with code rates of R = 1/3 or
5 1/5. The encoder shall discard the 6-bit TAIL field of the physical layer packet inputs and
6 encode the remaining bits with a parallel turbo encoder, as specified in 10.4.1.3.2.3.2.1.
7 The turbo encoder will add an internally generated tail of 6/R output code symbols, so that
8 the total number of output symbols is 1/R times the number of bits in the input physical
9 layer packet.
10 Figure 10.4.1.3.2.3.2-1 illustrates the forward link encoding approach. The forward link
11 encoder parameters shall be as specified in Table 10.4.1.3.2.3.2-1.
10-60
Forward Traffic Channel Discard Turbo Encoder

or 6-Bit with an Code
Control Channel Encoder Internally Symbols
Physical Layer Packets Tail Field Generated Tail
Data Total Bits Bits Symbols

Rate Slots Code per per per
(kbps) Used Rate Packet Packet Packet
38.4 16 1/5 1,024 1,018 5,120
76.8 8 1/5 1,024 1,018 5,120
153.6 4 1/5 1,024 1,018 5,120
307.2 2 1/5 1,024 1,018 5,120
614.4 1 1/3 1,024 1,018 3,072
307.2 4 1/3 2,048 2,042 6,144
614.4 2 1/3 2,048 2,042 6,144
1,228.8 1 1/3 2,048 2,042 6,144
921.6 2 1/3 3,072 3,066 9,216
1,843.2 1 1/3 3,072 3,066 9,216
1,228.8 2 1/3 4,096 4,090 12,288
1
2,457.6 1 1/3 4,096 4,090 12,288
2 Figure 10.4.1.3.2.3.2-1. Forward Link Encoder
3 Table 10.4.1.3.2.3.2-1. Parameters of the Forward Link Encoder
Values per Physical Layer Packet

Data Turbo Turbo
Rate Encoder Code Encoder
(kbps) Slots Bits
Input Rate Output
Bits Symbols
38.4 16 1,024 1,018 1/5 5,120

76.8 8 1,024 1,018 1/5 5,120
153.6 4 1,024 1,018 1/5 5,120
307.2 2 1,024 1,018 1/5 5,120
614.4 1 1,024 1,018 1/3 3,072
307.2 4 2,048 2,042 1/3 6,144
614.4 2 2,048 2,042 1/3 6,144
1,228.8 1 2,048 2,042 1/3 6,144
921.6 2 3,072 3,066 1/3 9,216
1,843.2 1 3,072 3,066 1/3 9,216
1,228.8 2 4,096 4,090 1/3 12,288
2,457.6 1 4,096 4,090 1/3 12,288
4
5 11.4.1.3.2.3.2.110.4.1.3.2.3.2.1 Turbo Encoder

6 The turbo encoder employs two systematic, recursive, convolutional encoders connected in
8 convolutional encoder. The two recursive convolutional codes are called the constituent
10-61
1 codes of the turbo code. The outputs of the constituent encoders are punctured and
2 repeated to achieve the desired number of turbo encoder output symbols.
3 The transfer function for the constituent code shall be
⎡ n0 (D) n1(D) ⎤
4 G(D) = ⎢1 ⎥
⎣ d(D) d(D) ⎥⎦
7 generated by the encoder shown in Figure 10.4.1.3.2.3.2.1-1. Initially, the states of the
10 Let Nturbo be the number of bits into the turbo encoder after the 6-bit physical layer packet
11 TAIL field is discarded. Then, the encoded data output symbols are generated by clocking
12 the constituent encoders Nturbo times with the switches in the up positions and
13 puncturing the outputs as specified in Table 10.4.1.3.2.3.2.1-1. Within a puncturing
14 pattern, a ‘0’ means that the symbol shall be deleted and a ‘1’ means that the symbol shall
15 be passed onwards. The constituent encoder outputs for each bit period shall be output in
16 the sequence X, Y0, Y1, X′, Y′0, Y′1 with the X output first. Symbol repetition is not used in
17 generating the encoded data output symbols.
20 by the encoder shown in Figure 10.4.1.3.2.3.2.1-1. The tail output symbols are generated
29 output first.
30 The constituent encoder output symbol puncturing for the tail symbols shall be as
31 specified in Table 10.4.1.3.2.3.2.1-2. Within a puncturing pattern, a ‘0’ means that the
33 1/5 turbo codes, the tail output code symbols for each of the first three tail bit periods
34 shall be punctured and repeated to achieve the sequence XXY0Y1Y1, and the tail output
35 code symbols for each of the last three tail bit periods shall be punctured and repeated to
36 achieve the sequence X′X′Y′0Y′1Y′1. For rate-1/3 turbo codes, the tail output symbols for
37 each of the first three tail bit periods shall be XXY0, and the tail output symbols for each of
38 the last three tail bit periods shall be X′X′Y′0.
10-62
X
Y0
n0
Y1
n1
Nturbo
Information
Bits
(Input)
Control
Puncturing Code
and Symbols
Turbo
Interleaver
X'
Y'0
n0
Y'1
n1
Control
1
2 Figure 10.4.1.3.2.3.2.1-1. Turbo Encoder
10-63
1 Table 10.4.1.3.2.3.2.1-1. Puncturing Patterns for the Data Bit Periods
Code Rate
Output 1/3 1/5
X 1 1
Y0 1 1
Y1 0 1
X′ 0 0
Y′ 0 1 1
Y′ 1 0 1
Note: For each rate, the puncturing table shall be read

from top to bottom.
2
3 Table 10.4.1.3.2.3.2.1-2. Puncturing Patterns for the Tail Bit Periods
Code Rate
Output 1/3 1/5
X 111 000 111 000

Y0 111 000 111 000
Y1 000 000 111 000
X′ 000 111 000 111
Y′ 0 000 111 000 111
Y′ 1 000 000 000 111
read first from top to bottom repeating X and X′, and then from
left to right. For rate-1/5 turbo codes, the puncturing table shall
be read first from top to bottom repeating X, X′, Y1, and Y′1 and
then from left to right.
4
5 11.4.1.3.2.3.2.210.4.1.3.2.3.2.2 Turbo Interleaver

10-64
3 illustrated in Figure 10.4.1.3.2.3.2.2-1 and described below.144
5 that Nturbo ≤ 2n+5. Table 10.4.1.3.2.3.2.2-1 gives this parameter for the different
10 4. Obtain the n-bit output of the table lookup defined in Table 10.4.1.3.2.3.2.2-2 with
11 a read address equal to the five LSBs of the counter. Note that this table depends
12 on the value of n.
Add 1
Counter Lookup
5 LSBs Bit 5 Bits

21
22 Figure 10.4.1.3.2.3.2.2-1. Turbo Interleaver Output Address Calculation Procedure
10-65
1 Table 10.4.1.3.2.3.2.2-1. Turbo Interleaver Parameter
Turbo Turbo
Nturbo n
1,024 1,018 5
2,048 2,042 6
3,072 3,066 7
4,096 4,090 7
2
10-66
1 Table 10.4.1.3.2.3.2.2-2. Turbo Interleaver Lookup Table Definition
Table n=5 n=6 n=7

Index Entries Entries Entries
0 27 3 15
1 3 27 127
2 1 15 89
3 15 13 1
4 13 29 31
5 17 5 15
6 23 1 61
7 13 31 47
8 9 3 127
9 3 9 17
10 15 15 119
11 3 31 15
12 13 17 57
13 1 5 123
14 13 39 95
15 29 1 5
16 21 19 85
17 19 27 17
18 1 15 55
19 3 13 57
20 29 45 15
21 17 5 41
22 25 33 93
23 29 15 87
24 9 13 63
25 13 9 15
26 23 15 13
27 13 31 15
28 13 17 81
29 1 5 57
30 13 15 31
31 13 33 69
2
10-67
1 11.4.1.3.2.3.310.4.1.3.2.3.3 Scrambling
2 The output of the encoder shall be scrambled to randomize the data prior to modulation.
3 The scrambling sequence shall be equivalent to one generated with a 17-tap linear
4 feedback shift register with a generator sequence of h(D) = D17 + D14 + 1, as shown in
5 Figure 10.4.1.3.2.3.3-1. At the start of the physical layer packet, the shift register shall be
6 initialized to the state [1111111r5r4r3r2r1r0d3d2d1d0]. The r5r4r3r2r1r0 bits shall be equal
7 to the 6-bit preamble MACIndex value (see Table 10.4.1.3.2.1.3-1). The d3d2d1d0 bits shall
8 be determined by the data rate, as specified in Table 10.4.1.3.2.3.3-1. The initial state shall
9 generate the first scrambling bit. The shift register shall be clocked once for every encoder
10 output code symbol to generate a bit of the scrambling sequence. Every encoder output
11 code symbol shall be XOR’d with the corresponding bit of the scrambling sequence to yield
12 a scrambled encoded bit.
13 Table 10.4.1.3.2.3.3-1. Parameters Controlling the Scrambler Initial State
Data Rate Slots per Physical d3 d2 d1 d0

(kbps) Layer Packet
38.4 16 0 0 0 1
76.8 8 0 0 1 0
153.6 4 0 0 1 1
307.2 2 0 1 0 0
307.2 4 0 1 0 1
614.4 1 0 1 1 0
614.4 2 0 1 1 1
921.6 2 1 0 0 0
1,228.8 1 1 0 0 1
1,228.8 2 1 0 1 0
1,843.2 1 1 0 1 1
2,457.6 1 1 1 0 0
14
10-68
Scrambler Initial State
1 1 1 1 1 1 1 r5 r4 r3 r2 r1 r0 d3 d2 d1 d0
Scrambling
Sequence
1
2 Figure 10.4.1.3.2.3.3-1. Symbol Scrambler
3 11.4.1.3.2.3.410.4.1.3.2.3.4 Channel Interleaving

4 The channel interleaving shall consist of a symbol reordering followed by symbol
5 permuting.
6 11.4.1.3.2.3.4.110.4.1.3.2.3.4.1 Symbol Reordering

7 The scrambled turbo encoder data and tail output symbols generated with the rate-1/5
8 encoder shall be reordered according to the following procedure:
9 1. All of the scrambled data and tail turbo encoder output symbols shall be
10 demultiplexed into five sequences denoted U, V0, V1, V′0, and V′1. The scrambled
11 encoder output symbols shall be sequentially distributed from the U sequence to
12 the V′1 sequence with the first scrambled encoder output symbol going to the U
13 sequence, the second to the V0 sequence, the third to the V1 sequence, the fourth
14 to the V′0 sequence, the fifth to the V′1 sequence, the sixth to the U sequence, etc.
15 2. The U, V0, V1, V′0, and V′1 sequences shall be ordered according to UV0V′0V1V′1.
16 That is, the U sequence of symbols shall be first and the V′1 sequence of symbols
17 shall be last.
21 demultiplexed into three sequences denoted U, V0, and V′0. The scrambled encoder
22 output symbols shall be sequentially distributed from the U sequence to the V′0
23 sequence with the first scrambled encoder output symbol going to the U sequence,
24 the second to the V0 sequence, the third to the V′0 sequence, the fourth to the U
25 sequence, etc.
10-69
1 2. The U, V0, and V′0 sequences shall be ordered according to UV0V′0. That is, the U
2 sequence of symbols shall be first and the V′0 sequence of symbols shall be last.
3 Table 10.4.1.3.2.3.4.1-1 gives the order of the symbols out of the turbo encoder and their
4 mapping to demultiplexer output sequences. The encoder output symbol notation is used,
5 but the encoder output symbols are scrambled before the reordering demultiplexer.
6 Table 10.4.1.3.2.3.4.1-1. Scrambled Turbo Encoder Output and Symbol Reordering

7 Demultiplexer Symbol Sequences
Symbol Sequence
Type of Sequence
R = 1/5 R = 1/3
Turbo Encoder X Y 0 Y1 Y′ 0 Y′ 1 X Y0 Y′ 0
Data Output Sequence
Turbo Encoder
Constituent Encoder 1 X X Y 0 Y1 Y1 X X Y0
Tail Output Sequence
Turbo Encoder
Constituent Encoder 2 X′ X′ Y′0 Y′1 Y′1 X′ X′ Y′0
Tail Output Sequence
Demultiplexer U V0 V ′ 0 V 1 V ′ 1 U V0 V′0
Output Sequence
8
9 11.4.1.3.2.3.4.210.4.1.3.2.3.4.2 Symbol Permuting

10 The reordered symbols shall be permuted in three separate bit-reversal interleaver blocks
11 with rate-1/5 coding and in two separate blocks with rate-1/3 coding. The permuter input
12 blocks shall consist of the U sequence of symbols, the V0 sequence of symbols followed by
13 the V′0 sequence of symbols (denoted as V0/V′0), and, with rate-1/5 coding, the V1
14 sequence of symbols followed by the V′1 sequence of symbols (denoted as V1/V′1).
15 The sequence of interleaver output symbols for the blocks shall be equivalent to those
16 generated by the procedure described below with the parameters specified in Table
17 10.4.1.3.2.3.4.2-1:
18 1. Write the entire sequence of symbols in the input block into a rectangular array of
19 K rows and M columns. Write the symbols in by rows starting from the top row,
20 writing the rows from left to right.
21 2. Label the columns of the array by the index j, where j = 0,…, M – 1 and column 0
22 is the left-most column. Then, end-around shift the symbols of each column
23 downward by j mod K for the U block and by ⎣j/4⎦ mod K for the V0/V′0 and
24 V1/V′1 blocks.
25 3. Reorder the columns such that column j is moved to column BRO(j), where BRO(j)
26 indicates the bit-reversed value of j. For example, for M = 512, BRO(6) = 192.
10-70
1 4. Read the entire array of symbols out by columns starting from the left-most
2 column, reading the columns from top to bottom.
3 With rate-1/5 coding, the interleaver output sequence shall be the interleaved U sequence
4 of symbols followed by the interleaved V0/V′0 sequence of symbols followed by the
5 interleaved V1/V′1 sequence of symbols. With rate-1/3 coding, the interleaver output
6 sequence shall be the interleaved U sequence of symbols followed by the interleaved V0/V′0
7 sequence of symbols.
8 Table 10.4.1.3.2.3.4.2-1. Channel Interleaver Parameters
U Block V0/V′0 and V1/V′1 Block

Physical Layer Interleaver Parameters Interleaver Parameters
Packet Size
K M K M
1,024 2 512 2 1,024

2,048 2 1,024 2 2,048
3,072 3 1,024 3 2,048
4,096 4 1,024 4 2,048
9
10 11.4.1.3.2.3.510.4.1.3.2.3.5 Modulation
11 The output of the channel interleaver shall be applied to a modulator that outputs an in-
12 phase stream and a quadrature stream of modulated values. The modulator generates
13 QPSK, 8-PSK, or 16-QAM modulation symbols, depending on the data rate.
14 11.4.1.3.2.3.5.110.4.1.3.2.3.5.1 QPSK Modulation

15 For physical layer packet sizes of 1,024 or 2,048 bits, groups of two successive channel
16 interleaver output symbols shall be grouped to form QPSK modulation symbols. Each
17 group of two adjacent block interleaver output symbols, x(2k) and x(2k + 1), k = 0,…, M – 1,
18 shall be mapped into a complex modulation symbol (mI(k), mQ(k)) as specified in Table
19 10.4.1.3.2.3.5.1-1. Figure 10.4.1.3.2.3.5.1-1 shows the signal constellation of the QPSK
20 modulator, where s0 = x(2k) and s1 = x(2k + 1).
10-71
1 Table 10.4.1.3.2.3.5.1-1. QPSK Modulation Table
Interleaved Symbols Modulation Symbols

s1 s0
mI(k) mQ(k)
x(2k + 1) x(2k)
0 0 D D
0 1 –D D
1 0 D –D
1 1 –D –D
Note: D = 1 2.
2
Q Channel
s1s 0
01 00
1 2
−1 2 1 2
I Channel
−1 2
11 10
4 Figure 10.4.1.3.2.3.5.1-1. Signal Constellation for QPSK Modulation
5 11.4.1.3.2.3.5.210.4.1.3.2.3.5.2 8-PSK Modulation

6 For physical layer packet sizes of 3,072 bits, groups of three successive channel interleaver
7 output symbols shall be grouped to form 8-PSK modulation symbols. Each group of three
8 adjacent block interleaver output symbols, x(3k), x(3k + 1), and x(3k + 2), k = 0,…, M – 1 ,
10 10.4.1.3.2.3.5.2-1. Figure 10.4.1.3.2.3.5.2-1 shows the signal constellation of the 8-PSK
11 modulator, where s0 = x(3k), s1 = x(3k + 1), and s2 = x(3k + 2).
10-72
1 Table 10.4.1.3.2.3.5.2-1. 8-PSK Modulation Table

s2 s1 s0
mI(k) mQ(k)
x(3k + 2) x(3k + 1) x(3k)
0 0 0 C S
0 0 1 S C
0 1 1 –S C
0 1 0 –C S
1 1 0 –C –S
1 1 1 –S –C
1 0 1 S –C
1 0 0 C –S
Note: C = cos(π/8) ≈ 0.9239 and S = sin(π/8) ≈ 0.3827 .
2
Q Channel
C = cos(π/8)
011 001 S = sin(π/8)
C
s 2s1s 0
010 S 000
–C –S S C
I Channel
–S
110 100
–C
111 101
4 Figure 10.4.1.3.2.3.5.2-1. Signal Constellation for 8-PSK Modulation
5 11.4.1.3.2.3.5.310.4.1.3.2.3.5.3 16-QAM Modulation

6 For physical layer packet sizes of 4,096 bits, groups of four successive channel interleaver
7 output symbols shall be grouped to form 16-QAM modulation symbols. Each group of four
8 adjacent block interleaver output symbols, x(4k), x(4k + 1), x(4k + 2), and x(4k + 3), k =
9 0,…, M – 1 shall be mapped into a complex modulation symbol (mI(k), mQ(k)) as specified
10 in Table 10.4.1.3.2.3.5.3-1. Figure 10.4.1.3.2.3.5.3-1 shows the signal constellation of the
11 16-QAM modulator, where s0 = x(4k), s1 = x(4k + 1), s2 = x(4k + 2), and s3 = x(4k + 3).
10-73
1 Table 10.4.1.3.2.3.5.3-1. 16-QAM Modulation Table

s3 s2 s1 s0
mQ(k) mI(k)
x(4k + 3) x(4k + 2) x(4k + 1) x(4k)
0 0 0 0 3A 3A
0 0 0 1 3A A
0 0 1 1 3A –A
0 0 1 0 3A –3A
0 1 0 0 A 3A
0 1 0 1 A A
0 1 1 1 A –A
0 1 1 0 A –3A
1 1 0 0 –A 3A
1 1 0 1 –A A
1 1 1 1 –A –A
1 1 1 0 –A –3A
1 0 0 0 –3A 3A
1 0 0 1 –3A A
1 0 1 1 –3A –A
1 0 1 0 –3A –3A
Note: A = 1 10 ≈ 0.3162 .
2
10-74
Q Channel
s 3s 2s1s0
0010 0011 0001 0000
3A
A = 1 10
0110 0111 0101 0100

A
–3A –A A 3A
I Channel
1110 1111 1101 1100

–A
1010 1011 1001 1000

–3A
2 Figure 10.4.1.3.2.3.5.3-1. Signal Constellation for 16-QAM Modulation
3 11.4.1.3.2.3.610.4.1.3.2.3.6 Sequence Repetition and Symbol Puncturing

4 Table 10.4.1.3.2.3.6-1 gives the number of modulation symbols that the modulator
5 provides per physical layer packet and the number of modulation symbols needed for the
6 data portion of the allocated slots. If the number of required modulation symbols is more
7 than the number provided, the complete sequence of input modulation symbols shall be
8 repeated as many full-sequence times as possible followed by a partial transmission if
9 necessary. If a partial transmission is needed, the first portion of the input modulation
10 symbol sequence shall be used. If the number of required modulation symbols is less than
11 the number provided, only the first portion of the input modulation symbol sequence shall
12 be used.
13 The sequence repetition and symbol puncturing parameters shall be as specified in Table
14 10.4.1.3.2.3.6-1. The entries in the column labeled “Number of Modulation Symbols
15 Needed” are equal to the number of data TDM chips given in Table 10.4.1.3.1.1-1 and
16 Table 10.4.1.3.1.1-2.
10-75
1 Table 10.4.1.3.2.3.6-1. Sequence Repetition and Symbol Puncturing Parameters
Values per Physical Layer Packet Coding
Number of
Data Number
Number of Number of Modulation Effective
Rate Number Number Modulation Modulation of Full Symbols in
Repeti-
(kbps) of Slots of Bits Sequence Code tion
Symbols Symbols Last Partial
Trans- Rate Factor
Provided Needed Trans-
missions
mission
38.4 16 1,024 2,560 24,576 9 1,536 1/5 9.6

76.8 8 1,024 2,560 12,288 4 2,048 1/5 4.8
153.6 4 1,024 2,560 6,144 2 1,024 1/5 2.4
307.2 2 1,024 2,560 3,072 1 512 1/5 1.2
614.4 1 1,024 1,536 1,536 1 0 1/3 1
307.2 4 2,048 3,072 6,272 2 128 1/3 2.04
614.4 2 2,048 3,072 3,136 1 64 1/3 1.02
1,228.
1 2,048 3,072 1,536 0 1,536 2/3 1
8
921.6 2 3,072 3,072 3,136 1 64 1/3 1.02
1,843.
1 3,072 3,072 1,536 0 1,536 2/3 1
2
1,228.
2 4,096 3,072 3,136 1 64 1/3 1.02
8
2,457.
1 4,096 3,072 1,536 0 1,536 2/3 1
6
2
3 11.4.1.3.2.3.710.4.1.3.2.3.7 Symbol Demultiplexing

4 The in-phase stream at the output of the sequence repetition operation shall be
5 demultiplexed into 16 parallel streams labeled I0, I1, I2,…, I15. If mI(0), mI(1), mI(2),
6 mI(3),… denote the sequence of sequence-repeated modulation output values in the in-
7 phase stream, then for each k = 0, 1, 2,…, 15, the kth demultiplexed stream Ik shall consist
8 of the values mI(k), mI(16 + k), mI(32 + k), mI(48 + k),….
9 Similarly, the quadrature stream at the output of the sequence repetition operation shall be
10 demultiplexed into 16 parallel streams labeled Q0, Q1, Q2,…, Q15. If mQ(0), mQ(1), mQ(2),
11 mQ(3),…denote the sequence of sequence-repeated modulation output values in the
12 quadrature stream, then for each k = 0, 1, 2,…,15, the kth demultiplexed stream Qk shall
13 consist of the values mQ(k), mQ(16 + k), mQ(32 + k), mQ(48 + k),….
14 Each demultiplexed stream at the output of the symbol demultiplexer shall consist of
15 modulation values at the rate of 76.8 ksps.
10-76
1 11.4.1.3.2.3.810.4.1.3.2.3.8 Walsh Channel Assignment

2 The individual streams generated by the symbol demultiplexer shall be assigned to one of
3 16 distinct Walsh channels. For each k = 0, 1, 2,…, 15, the demultiplexed streams with
4 labels Ik and Qk shall be assigned to the in-phase and quadrature phases, respectively, of
5 the kth Walsh channel Wk16 . The modulation values associated with the in-phase and
6 quadrature phase components of the same Walsh channel are referred to as Walsh
7 symbols.
8 11.4.1.3.2.3.910.4.1.3.2.3.9 Walsh Channel Scaling

9 The modulated symbols on each branch of each Walsh channel shall be scaled to maintain
10 a constant total transmit power independent of data rate. For this purpose, each
1 1
11 orthogonal channel shall be scaled by a gain of = . The gain settings are normalized
16 4
12 to a unity reference equivalent to unmodulated BPSK transmitted at full power.
13 11.4.1.3.2.3.1010.4.1.3.2.3.10 Walsh Chip Level Summing

14 The scaled Walsh chips associated with the 16 Walsh channels shall be summed on a chip-
15 by-chip basis.
16 11.4.1.3.2.410.4.1.3.2.4 Control Channel

17 The Control Channel transmits broadcast messages and access-terminal-directed
18 messages. The Control Channel messages shall be transmitted at a data rate of 76.8 kbps
19 or 38.4 kbps. The modulation characteristics shall be the same as those of the Forward
20 Traffic Channel at the corresponding data rate. The Control Channel transmissions shall be
21 distinguished from Forward Traffic Channel transmissions by having a preamble that is
22 covered by a bi-orthogonal cover sequence with MACIndex 2 or 3, as specified in
23 10.4.1.3.2.3.1. A MACIndex value of 2 shall be used for the 76.8 kbps data rate, and a
24 MACIndex value of 3 shall be used for the 38.4 kbps data rate.
25 11.4.1.3.310.4.1.3.3 Time-Division Multiplexing

26 The Forward Traffic Channel or Control Channel data modulation chips shall be time-
27 division multiplexed with the preamble, Pilot Channel, and MAC Channel chips according
28 to the timing diagrams in Figure 10.4.1.3.3-1, Figure 10.3.1.3.3.5-2, Figure 10.4.1.3.3-3,
29 and Figure 10.4.1.3.3-4. The multiplexing parameters shall be as specified in Table
30 10.4.1.3.3-1
31 The Walsh chip rate shall be fixed at 1.2288 Mcps.
10-77
2,560 or 3,072
Modulation Symbols
Data Modulation Symbols

(Repeated Sequence If Needed)
Preamble Data Pilot Data Pilot Pilot Data Pilot Data

N 400 – N & MAC 800 & MAC & MAC 800 & MAC 400
Chips Chips 224 Chips 224 224 Chips 224 Chips
Chips Chips Chips Chips
2 or 4 Slots
4,096 or 8,192 Chips
1
2 Figure 10.4.1.3.3-1. Preamble, Pilot, MAC, and Data Multiplexing for the Multiple-Slot
3 Cases with Data Rates of 153.6, 307.2, 614.4, 921.6, and 1228.8 kbps
2,560
Modulation Symbols

(Repeated Sequence)
Preamble Pilot Preamble Data Pilot Data Pilot Pilot Data Pilot Data
400 & MAC 112 Chips 688 Chips & MAC 800 & MAC & MAC 800 & MAC 400
Chips 224 for 76.8 kbps for 76.8 kbps 224 Chips 224 224 Chips 224 Chips
Chips 624 Chips 176 Chips Chips Chips Chips Chips
for 38.4 kbps for 38.4 kbps
8 or 16 Slots
16,384 or 32,768 Chips
4
5 Figure 10.4.1.3.3-2. Preamble, Pilot, MAC, and Data Multiplexing with Data Rates of
6 38.4 and 76.8 kbps
10-78
3,072 Data Modulation Symbols
Preamble Data Pilot Data Pilot Data

64 336 & MAC 800 & MAC 400
Chips Chips 224 Chips 224 Chips
Chips Chips
1 Slot
2,048 Chips
1
2 Figure 10.4.1.3.3-3. Preamble, Pilot, MAC, and Data Multiplexing for the 1-Slot Cases
3 with Data Rates of 1.2288, 1.8432, and 2.4576 Mbps

64 336 & MAC 800 & MAC 400
Chips Chips
1 Slot
2,048 Chips
4
5 Figure 10.4.1.3.3-4. Preamble, Pilot, MAC, and Data Multiplexing for the 1-Slot Case
6 with a Data Rate of 614.4 kbps
10-79
1 Table 10.4.1.3.3-1. Preamble, Pilot, MAC, and Data Multiplexing Parameters
Data Number of Values per Physical Layer Packet

Rate Preamble Pilot MAC Data
(kbps) Slots Bits
38.4 16 1,024 1,024 3,072 4,096 24,576

76.8 8 1,024 512 1,536 2,048 12,288
153.6 4 1,024 256 768 1,024 6,144
307.2 2 1,024 128 384 512 3,072
614.4 1 1,024 64 192 256 1,536
307.2 4 2,048 128 768 1,024 6,272
614.4 2 2,048 64 384 512 3,136
1,228.8 1 2,048 64 192 256 1,536
921.6 2 3,072 64 384 512 3,136
1,843.2 1 3,072 64 192 256 1,536
1,228.8 2 4,096 64 384 512 3,136
2,457.6 1 4,096 64 192 256 1,536
2

4 Following orthogonal spreading, the combined modulation sequence shall be quadrature
5 spread as shown in Figure 10.4.1.3.1-1. The spreading sequence shall be a quadrature
6 sequence of length 215 (i.e., 32768 PN chips in length). This sequence is called the pilot PN
7 sequence and shall be based on the following characteristic polynomials:
8 PI(x) = x15 + x10 + x8 + x7 + x6 + x2 + 1

10 and
11 PQ(x) = x15 + x12 + x11 + x10 + x9 + x5 + x4 + x3 + 1

14 above polynomials are of length 215 – 1 and can be generated by the following linear
15 recursions:
16 I(n) = I(n – 15) ⊕ I(n – 13) ⊕ I(n – 9) ⊕ I(n – 8) ⊕ I(n – 7) ⊕ I(n – 5)
18 and
19 Q(n) = Q(n – 15) ⊕ Q(n – 12) ⊕ Q(n – 11) ⊕ Q(n – 10) ⊕ Q(n – 6) ⊕ Q(n – 5) ⊕
20 Q(n – 4) ⊕ Q(n – 3)
10-80
3 to obtain the I and Q pilot PN sequences (of period 215), a ‘0’ is inserted in the {I(n)} and
4 {Q(n)} sequences after 14 consecutive ‘0’ outputs (this occurs only once in each period).
5 Therefore, the pilot PN sequences have one run of 15 consecutive ‘0’ outputs instead of 14.
6 The chip rate for the pilot PN sequence shall be 1.2288Mcps. The pilot PN sequence period
7 is 32768/1228800 = 26.666… ms, and exactly 75 pilot PN sequence repetitions occur every
8 2 seconds.
9 Pilot Channels shall be identified by an offset index in the range from 0 through 511
10 inclusive. This offset index shall specify the offset value (in units of 64 chips) by which the
11 pilot PN sequence lags the zero-offset pilot PN sequence. The zero-offset pilot PN sequence
12 shall be such that the start of the sequence shall be output at the beginning of every even
13 second in time, referenced to access network transmission time. The start of the zero-offset
14 pilot PN sequence for either the I or Q sequences shall be defined as the state of the
15 sequence for which the next 15 outputs inclusive are ‘0’. Equivalently, the zero-offset
16 sequence is defined such that the last chip prior to the even-second mark as referenced to
17 the transmit time reference is a ‘1’ prior to the 15 consecutive ‘0’s.
18 11.4.1.3.510.4.1.3.5 Filtering

20 Following the quadrature spreading operation, the I′ and Q′ impulses are applied to the
21 inputs of the I and Q baseband filters as shown in Figure 10.4.1.3.1-1. The baseband
22 filters shall have a frequency response S(f) that satisfies the limits given in Figure
23 10.4.1.3.5.1-1. Specifically, the normalized frequency response of the filter shall be
24 contained within ±δ1 in the passband 0 ≤ f ≤ fp and shall be less than or equal to –δ2 in the
25 stopband f ≥ fs. The numerical values for the parameters are δ1 = 1.5 dB, δ2 = 40 dB, fp =
26 590 kHz, and fs = 740 kHz.
10-81
20 log10 S(f )
δ1
δ1
δ2
f
0 fp fs
1
∞
k =0
[αs(kTs – τ) – h(k)]2 ≤ 0.03,
10-82
k h(k)
0, 47 –0.025288315
1, 46 –0.034167931
2, 45 –0.035752323
3, 44 –0.016733702
4, 43 0.021602514
5, 42 0.064938487
6, 41 0.091002137
7, 40 0.081894974
8, 39 0.037071157
9, 38 –0.021998074
10, 37 –0.060716277
11, 36 –0.051178658
12, 35 0.007874526
13, 34 0.084368728
14, 33 0.126869306
15, 32 0.094528345
16, 31 –0.012839661
17, 30 –0.143477028
18, 29 –0.211829088
19, 28 –0.140513128
20, 27 0.094601918
21, 26 0.441387140
22, 25 0.785875640
23, 24 1.0
2
3 11.4.1.3.5.210.4.1.3.5.2 Phase Characteristics

4 The access network shall provide phase equalization for the transmit signal path.145 The
5 equalizing filter shall be designed to provide the equivalent baseband transfer function
ω2 + jαωω0 − ω0 2 ,
6 H(ω) = K
ω2 − jαωω0 − ω0 2
145This equalization simplifies the design of the access terminal receive filters.
10-83
1 where K is an arbitrary gain, j equals − 1 , α equals 1.36, ω0 equals 2π × 3.15 × 105, and ω
2 is the radian frequency. The equalizing filter implementation shall be equivalent to applying
3 baseband filters with this transfer function, individually, to the baseband I and Q
4 waveforms.
5 A phase error test filter is defined to be the overall access network transmitter filter
6 (including the equalizing filter) cascaded with a filter having a transfer function that is the
7 inverse of the equalizing filter specified above. The response of the test filter should have a
8 mean squared phase error from the best fit linear phase response that is no greater than
9 0.01 squared radians when integrated over the frequency range 1 kHz ≤ |f – fc| ≤ 630 kHz.
10 For purposes of this requirement, “overall” shall mean from the I and Q baseband filter
11 inputs (see 10.4.1.3.5.1) to the RF output of the transmitter.
12 11.4.1.3.610.4.1.3.6 Synchronization and Timing
13 11.4.1.3.6.110.4.1.3.6.1 Timing Reference Source

14 Each sector shall use a time base reference from which all time-critical transmission
15 components, including pilot PN sequences, slots, and Walsh functions, shall be derived.
16 The time-base reference shall be time-aligned to CDMA System Time, as described in 1.14.
17 Reliable external means should be provided at each sector to synchronize each sector’s
18 time base reference to CDMA System Time. Each sector should use a frequency reference of
19 sufficient accuracy to maintain time alignment to CDMA System Time. In the event that the
20 external source of CDMA System Time is lost,146 the sector shall maintain transmit timing
21 within ±10 μs of CDMA System Time for a period of not less than 8 hours.
22 11.4.1.3.6.210.4.1.3.6.2 Sector Transmission Time

23 All sectors should radiate the pilot PN sequence within ±3 µs of CDMA System Time and
24 shall radiate the pilot PN sequence within ±10 µs of CDMA System Time.
25 Time measurements are made at the sector antenna connector. If a sector has multiple
26 radiating antenna connectors for the same CDMA channel, time measurements are made
27 at the antenna connector having the earliest radiated signal.
28 The rate of change for timing corrections shall not exceed 102 ns (1/8 PN chip) per 200 ms.
29
146 These guidelines on time keeping requirements reflect the fact that the amount of time error
between sectors that can be tolerated in an access network is not a hard limit. Each access terminal
can search an ever-increasing time window as directed by the sectors. However, increasing this
window gradually degrades performance since wider windows require a longer time for the access
terminals to search out and locate the various arrivals from all sectors that may be in view.
10-84
Subtype 2 Physical Layer 3GPP2 C.S0024-B v2.0
1 1211 SUBTYPE 2 PHYSICAL LAYER
2 12.111.1 Subtype 2 Physical Layer Protocol Instance
3 12.1.111.1.1 Overview
4 This chapter contains the specification for the Subtype 2 Physical Layer Protocol. The
5 Subtype 2 Physical Layer supports the Enhanced (Subtype 1) Access Channel MAC
6 Protocol, the Enhanced (Subtype 1) Control Channel MAC Protocol, the Enhanced (Subtype
7 1) Forward Traffic Channel MAC Protocol, and the Subtype 3 Reverse Traffic Channel MAC
8 Protocol.
10 12.1.2.111.1.2.1 Commands

14 • ReverseTrafficPacketsMissed
15 • ForwardTrafficCompleted
16 12.1.2.311.1.2.3 Public Data

19 • SoftRAB for each sector in the access terminal’s active set if the access terminal has
20 negotiated Subtype 3 Reverse Traffic Channel MAC protocol.

22 The transmission unit of this protocol is a Subtype 2 Physical Layer packet. Each Subtype
23 2 Physical Layer packet contains a MAC Layer packet.

11-1
3GPP2 C.S0024-B v2.0 Subtype 2 Physical Layer
10 12.1.5.111.1.5.1 Procedures

20 then
35
11-2
4
Field Length (bits)
MessageID 8
TransactionID 8
11
Field Length (bits)
MessageID 8
TransactionID 8

20
21
11-3
2 12.1.6.111.1.6.1 Procedures
3 Procedures for the InUse Instance of the protocol are described in 11.2, 11.3, and 11.4.

5 These protocols do not define any message formats.
7 12.1.6.3.111.1.6.3.1 Commands
9 12.1.6.3.211.1.6.3.2 Indications
10 These protocols do not register to receive any indications

12 No configuration attributes are defined for these protocols.

14
NS2PHYP Subtype field for this protocol 0x0002

15

11-4
2 12.2.111.2.1 Overview
4 packet can be of length 128, 256, 512, 768, 1024, 1536, 2048, 3072, 4096, 5120, 6144,
5 8192, or 12288 bits. The format of the physical layer packet depends upon the channel on
6 which it is transmitted. A physical layer packet carries one MAC layer packet.

9 The length of a Control Channel physical layer packet shall be 128, 256, 512, or 1024 bits.
10 Each Control Channel physical layer packet shall carry one Control Channel MAC layer
11 packet. The 1024-bit Control Channel physical layer packets shall use the following format:
12
Field Length (bits)

FCS 16
TAIL 6
13
14 MAC Layer Packet - MAC layer packet from the Control Channel MAC Protocol.
17
18 All other Control Channel physical layer packets shall use the following format:
19
Field Length (bits)

FCS 24
TAIL 6
23 Figure 11.2.2.1-1 illustrates the valid formats for the Control Channel physical layer
24 packets.
11-5
3 Figure 11.2.2.1-1. Physical Layer Packet Formats for the Control Channel

5 The length of an Access Channel physical layer packet shall be 256, 512, or 1024 bits.
6 Each Access Channel physical layer packet shall carry one Access Channel MAC layer
7 packet. Access Channel physical layer packets shall use the following format:
8
Field Length (bits)

FCS 16
TAIL 6
9
10 MAC Layer Packet - MAC layer packet from the Access Channel MAC Protocol.
13 Figure 11.2.2.2-1 illustrates the format of the Access Channel physical layer packets.
14
15 Figure 11.2.2.2-1. Physical Layer Packet Format for the Access Channel

17 The length of a Forward Traffic Channel physical layer packet shall be 128, 256, 512, 1024,
18 2048, 3072, 4096, or 5120 bits. A Forward Traffic Channel physical layer packet shall
11-6
1 carry one Forward Traffic Channel MAC layer packet addressed to one or more access
2 terminals. Forward Traffic Channel physical layer packets shall use the following format:
3
Field Length (bits)
MAC Layer Packet 98, 226, 482, 994,

2018, 3042, 4066, or
5090
FCS 24
TAIL 6
5 Protocol.
9 packets.
10

13 The length of a Reverse Traffic Channel physical layer packet shall be 128, 256, 512, 768,
14 1024, 1536, 2048, 3072, 4096, 6144, 8192, or 12288 bits. Each Reverse Traffic Channel
15 physical layer packet shall carry one Reverse Traffic Channel MAC layer packet. Reverse
16 Traffic Channel physical layer packets shall use the following format:
17
Field Length (bits)
98, 226, 482, 738, 994,

1506, 2018, 3042,
MAC Layer Packet
4066, 6114,8162, or
12258
FCS 24
TAIL 6
18
20 Protocol.
11-7

4 packets.


16 The 16-bit FCS shall be a CRC calculated using the standard CRC-CCITT generator
17 polynomial:
18 g(x) = x16 + x12 + x5 + 1.
20 polynomial:
21 g(x) = x24 + x23 + x6 + x5 + x + 1.
22 The 16-bit FCS shall be equal to the value computed according to the following procedure
23 as shown in Figure 12.2.4-1:
31 • The output bits constitute all fields except the TAIL field of the physical layer.
11-8
Input
‘0’
x0 x1 x5 x12 x15
Output
‘0’

1
2 Figure 11.2.4-1. 16-bit FCS Computation for the Physical Layer Packet
12 • The output bits constitute all fields except the TAIL field of the physical layer packets.
13
Input
‘0’
0 1 5 6 23
x x x x x x24
Output
‘0’

14
11-9




10 specified.

14 until the access attempt succeeds or ends. When the access terminal is transmitting the
15 Access Channel, the access terminal shall control the mean output power as specified in
16 the Access Channel MAC Protocol (see Table 14.1-1).

19 shall control the mean output power using a combination of closed-loop power control,
20 open-loop power control, and the rules specified by the Reverse Traffic Channel MAC
21 Protocol (see 12.3.1.2.4, 12.3.2.1, and Table 14.1-1).
22 When the TxT2P (public data of the Reverse Traffic Channel MAC Protocol) is changed, the
23 access terminal output power, relative to the desired value in steady state, shall be within
24 ±0.5 dB or 20% of the change in dB, whichever is greater. The access terminal output
25 power shall settle to within ±0.5 dB or 20% of the change in dB, whichever is greater, of the
26 steady-state value within 200 μs of the physical layer sub-frame147 boundary.

147
The start of a sub-frame is specified by (T-FrameOffset) mod 4 = 0, where T is the
CDMA System Time in slots.
11-10



10 The access terminal shall provide two independent means for output power adjustment: an
11 open-loop estimation performed by the access terminal and a closed-loop correction
12 involving both the access terminal and the access network. Accuracy requirements on the
13 controlled range of mean output power (see 11.3.1.2.5) need not apply for the following
14 three cases:
18 11.3.1.2.3.1); or
19 • Mean input power levels exceeding –25 dBm within the 1.23-MHz bandwidth.

21 Open-loop operation shall be based on the power of the received Forward Pilot Channel (see
22 11.4.1.3.2.1).
23 The nominal access probe structure and its transmit power requirements are defined as
24 part of the Access Channel MAC Protocol. The power of the Access Data Channel relative to
25 that of the Pilot Channel shall be as specified in Table 12.3.1.2.4.1-1 in which
26 DataOffsetNom, DataOffset9k6, DataOffset19k2, and DataOffset38k4 are public data of the
27 Access Channel MAC Protocol. The output power of the Pilot Channel during the preamble
28 portion of an access probe shall be increased relative to the nominal Pilot Channel power
29 during the data portion of the probe by an amount such that the total output power of the
30 preamble and data portion of the access probe, if transmitted at 9.6 kbps, are the same.
32 Reverse Traffic Channel transmission. The initial mean output power of the Pilot Channel
33 of the Reverse Traffic Channel shall be equal to the mean output power of the Pilot Channel
34 at the end of the last Access Channel probe minus the difference in the forward link mean
35 received signal power from the end of the last Access Channel probe to the start of the
36 Reverse Traffic Channel transmission.
37 The subsequent mean output power of the Pilot Channel of the total reverse link
38 transmission shall be the mean output power of the Pilot Channel at the end of the last
11-11
1 Access Channel probe minus the difference in the forward link mean received signal power
2 from the end of the last Access Channel probe to the current Reverse Traffic Channel
3 transmission, plus closed loop corrections as specified in 11.3.1.2.4.2.
4 The accuracy of the incremental adjustment to the mean output power, as dictated by the
5 Access Channel MAC Protocol and the Reverse Traffic Channel MAC Protocol, shall be
6 ±0.5 dB or 20% of the change in dB, whichever is greater.
7 When the access terminal is transmitting the Access Channel, the power of the Data
8 Channel relative to that of the Pilot Channel during the data portion of the Access Channel
9 transmission shall be as specified in Table 11.3.1.2.4.1-1 in which DataOffsetNom,
10 DataOffset9k6, DataOffset19k2, and DataOffset38k4 are public data of the Access
11 Channel MAC Protocol. When the access terminal is transmitting the Access Channel, the
12 power of the Pilot Channel during the preamble portion of the Access Channel transmission
13 shall be equal to the total power transmitted during the data portion of the Access Channel
14 transmission when the Data Channel is transmitted at 9.6 kbps.
16 Transmissions

(kbps) (dB)

17
18 During the transmission of the RRI Channel, the power of the RRI Channel relative to that
19 of the Pilot Channel shall be as specified by RRIChannelGain, where RRIChannelGain is
20 public data of the Reverse Traffic Channel MAC Protocol.
21 During the transmission of the DSC Channel, the power of the DSC Channel relative to
22 that of the Pilot Channel shall be as specified by DSCChannelGain, where
23 DSCChannelGain is public data of the Forward Traffic Channel MAC Protocol.
24 During the transmission of the DRC Channel, the power of the DRC Channel relative to
25 that of the Pilot Channel shall be as specified by DRCChannelGain, where
26 DRCChannelGain is public data of the Forward Traffic Channel MAC Protocol.
28 of the Pilot Channel shall be as specified by ACKChannelGain, where ACKChannelGain is
29 public data of the Forward Traffic Channel MAC Protocol if the access terminal is
30 transmitting an ACK in response to a Single User packet.
32 of the Pilot Channel shall be as specified by ACKChannelGain +
33 DeltaACKChannelGainMUP if the access terminal is transmitting an ACK in response to a
11-12
1 Multi-User packet, where ACKChannelGain and DeltaACKChannelGainMUP are public

2 data of the Forward Traffic Channel MAC Protocol.
3 During the transmission of the Data Channel, the power of the Data Channel relative to
4 that of the Pilot Channel shall be as specified by TxT2P, where TxT2P is public data of the
5 Reverse Traffic Channel MAC Protocol.
6 The Auxiliary Pilot Channel shall be transmitted during the nth half slot if the Reverse
7 Traffic Channel transmit payload is greater than or equal to
8 AuxiliaryPilotChannelMinPayload during half slots n−1 or n+1, where
9 AuxiliaryPilotChannelMinPayload is public data of the Reverse Traffic Channel MAC
10 Protocol.
11 If the Auxiliary Pilot Channel is transmitted during the nth half slot, its power shall be
12 specified relative to the maximum of the Data Channel Gains during half-slots n−1 and
13 n+1 by AuxiliaryPilotChannelGain, where AuxiliaryPilotChannelGain is public data of the
15 The access terminal shall maintain the power of the RRI Channel, DSC Channel, DRC
16 Channel, ACK Channel, and Data Channel relative to that of the Pilot Channel, to within
17 ±0.25 dB of the specified values.
18 The access terminal shall maintain the power of the Auxiliary Pilot Channel during the nth
19 half slot relative to that of the maximum of the Data Channel Gains during half slots n−1
20 and n+1 to within ±0.25 dB of the specified values.
21 If TxT2P is less than or equal to TxT2Pmin (both public data of the Reverse Traffic Channel
22 MAC Protocol) and the access terminal is unable to transmit the Reverse Traffic Channel at
23 the required output power level, the access terminal shall reduce the power of the DRC
24 Channel and the ACK Channel accordingly. The maximum power reduction for the DRC
25 Channel corresponds to gating off the DRC Channel. The maximum power reduction for the
26 ACK Channel corresponds to gating off the ACK Channel. If the ACK Channel is active, the
27 ACK Channel power reduction shall occur only after the DRC Channel has been gated off.
28 The access terminal shall perform the power reduction within one slot of determining that
29 the access terminal is unable to transmit at the requested output power level.

32 shall adjust the mean output power level of the Pilot Channel in response to each power-
33 control bit received on the Reverse Power Control (RPC) Channel. The nominal change in
34 mean output power level of the Pilot Channel per single power-control bit shall be set
35 according to the RPCStep, which is public data of the Reverse Traffic Channel MAC
36 Protocol.
37 For the 1.0 dB step size, the change in mean output power level per power-control bit shall
38 be within ±0.5 dB of the nominal value (1 dB), and the change in mean output power level
40 change (10 dB). For the 0.5 dB step size, the change in mean output power level per power-
41 control bit shall be within ±0.3 dB of the nominal value (0.5 dB), and the change in mean
42 output power level per 20 power-control bits of the same sign shall be within ±2.5 dB of 20
11-13
1 times the nominal change (10 dB). For the 1.5 dB step size, the change in mean output
2 power level for an active reverse CDMA channel per power-control bit shall be within
3 ±0.5 dB of the nominal value (1.5 dB), and the change in mean output power level for an
4 active reverse CDMA channel per 10 power-control bits of the same sign shall be within
5 ±3.0 dB of 10 times the nominal change (15 dB). For the 2.0 dB step size, the change in
6 mean output power level for an active reverse CDMA channel per power-control bit shall be
7 within ±0.5 dB of the nominal value (2.0 dB), and the change in mean output power level
8 for an active reverse CDMA channel per 10 power-control bits of the same sign shall be
9 within ±4.0 dB of 10 times the nominal change (20 dB). A ‘0’ power-control bit requires the
10 access terminal to increase transmit power, and a ‘1’ power-control bit requires the access
11 terminal to decrease transmit power. The access terminal shall provide a closed-loop
12 adjustment range greater than ±24 dB around its open-loop estimate.
14 components or from different sectors during handoff.
15 12.3.1.2.511.3.1.2.5 Power Transition Characteristics

17 Following a step change in mean input power, ΔPin, the mean output Pilot Channel power
18 of the access terminal shall transition to its final value in a direction opposite in sign to
19 ΔPin, with magnitude contained between the mask limits defined by148:
20 • Upper Limit:
23 • Lower Limit:

31 Following the reception of a closed-loop power-control bit, the mean output power of the
32 access terminal shall be within 0.3 dB and 0.15 dB of the final value in less than 500 μs for
33 step sizes of 1.0 dB and 0.5 dB, respectively and within 0.3 dB of the final value in less
34 than 500 μs for step sizes of 1.5 dB and 2 dB.
11-14

5 Channel shall consist of a Pilot Channel, a Reverse Rate Indicator (RRI) Channel, a Data
6 Source Control (DSC) Channel, a Data Rate Control (DRC) Channel, an Acknowledgment
7 (ACK) Channel, and a Data Channel. The Reverse Traffic Channel may also include an
8 Auxiliary Pilot Channel.
9 The RRI Channel is used to indicate the payload size and the sub-packet identifier of the
10 physical layer packet transmitted on the Reverse Traffic Channel. The DSC Channel is used
11 by the access terminal to indicate to the access network the selected serving cell on the
12 Forward Channel. The DRC Channel is used by the access terminal to indicate to the
13 access network the requested Forward Traffic Channel data rate and the selected serving
14 sector on the Forward Channel. The serving sector is the sector that the access terminal
15 selects for receiving the Forward Traffic Channel. The serving cell is the cell that contains
16 the serving sector. The ACK Channel is used by the access terminal to inform the access
17 network whether or not the physical layer packet transmitted on the Forward Traffic
18 Channel has been received successfully. The Auxiliary Pilot Channel is used by the access
19 terminal to aid reverse link channel estimation by the access network.
20 The structure of the reverse link channels for the Access Channel shall be as shown in
21 Figure 11.3.1.3.1-1, and the structure of the reverse link channels for the Reverse Traffic
22 Channel shall be as shown in Figure 11.3.1.3.1-2 through Figure 11.3.1.3.1-6. For the
23 Access Channel, the RRI symbols shall not be transmitted. The Pilot Channel, the RRI
24 Channel, the DSC Channel, the DRC Channel, the ACK Channel, the Data Channel, and
25 the Auxiliary Pilot Channel shall be orthogonally spread by Walsh functions of length 2, 4,
26 8, 16, or 32 (see 11.3.1.3.8). The Data Channel shall be BPSK, QPSK, or 8-PSK modulated
27 and each modulated stream shall be covered by either a 4-ary Walsh function or a 2-ary
28 Walsh function. The Data Channel shall be B4 modulated (BPSK modulation with 4-ary
29 Walsh cover), Q4 modulated (QPSK modulation with 4-ary Walsh cover), Q2 modulated
30 (QPSK modulation with 2-ary Walsh cover), Q4Q2 modulated (sum of the Q4 and Q2
31 modulated symbols), or E4E2 modulated (sum of E4 (8-PSK modulated with 4-ary Walsh
32 cover), and E2 (8-PSK modulated with 2-ary Walsh cover) modulated symbols). Each
33 Reverse Traffic Channel shall be identified by a distinct user long code. The Access Channel
34 for each sector shall be identified by a distinct Access Channel long code.
35 The Access Channel frame and Reverse Traffic Channel frame shall be 26.66… ms in
36 duration. The zero offset frame boundary shall be aligned to the rollover of the short PN
37 codes (see 11.3.1.3.12.1). Each Reverse Traffic Channel frame149 shall consist of 16 slots or
38 four sub-frames and each sub-frame shall consist of 4-slots, with each slot 1.66… ms in
39 duration. Each slot contains 2048 PN chips. A sub-packet is the smallest unit of a Reverse
149 The start of a frame is specified by ( T − FrameOffset ) mod 16 = 0, where T is the CDMA System
Time in slots.
11-15
1 Traffic Channel transmission that can be acknowledged at the physical layer by the access
2 network. A sub-packet is transmitted over four contiguous slots. A sub-frame is a group of
3 four contiguous slots during which the access terminal may transmit a sub-packet. The
4 structure of the Reverse Traffic Channel sub-frame is shown in Figure 11.3.1.3.1-9. Each
5 physical layer packet can be transmitted in up to a maximum of four sub-packets. When
6 more than one sub-packet is transmitted, the transmitted sub-packets shall use a three
7 sub-frame interlacing. That is, the transmitted sub-packets of a physical layer packet shall
8 be separated by two intervening sub-frames, and sub-packets of other physical layer
9 packets may be transmitted in the sub-frames between those transmitted sub-packets.
10 When the access terminal is transmitting a Reverse Traffic Channel, it shall continuously
11 transmit the Pilot Channel and the RRI Channel. The Pilot Channel shall be transmitted on
16
12 Walsh channel W016 . The RRI Channel shall be transmitted on Walsh channel W4 . The
13 DSC Channel and the ACK Channel shall be time-division multiplexed on Walsh channel
14 W1232 . The DSC Channel shall be transmitted on the second half slot on Walsh channel
15 W1232 and shall be repeated for DSCLength slots, where DSCLength is public data of the
16 Forward Traffic Channel MAC Protocol. When the DRC Channel is active (see 11.3.1.3.3.4),
17 it shall be transmitted for a full slot duration on Walsh channel W816 and repeated for
18 DRCLength slots, where DRCLength is public data of the Forward Traffic Channel MAC
19 Protocol. The access terminal shall transmit an ACK Channel bit in response to every
20 Forward Traffic Channel slot that is associated with a detected preamble directed to the
21 access terminal. Otherwise, the ACK Channel shall be gated off. When the ACK Channel bit
22 is transmitted, it shall be time-division multiplexed with the DSC Channel and transmitted
32
23 on the first half slot on Walsh channel W12 . The access terminal shall transmit the Data
24 Channel as specified by the Reverse Traffic Channel MAC Protocol. When transmitting the
25 Data Channel the access terminal shall transmit the Data Channel on Walsh channel
26 W24 or W12 , or both. The access terminal shall transmit the Auxiliary Pilot Channel as
27 specified by the Reverse Traffic Channel MAC Protocol. When transmitting the Auxiliary
28 Pilot Channel, the access terminal shall transmit the Auxiliary Pilot Channel on Walsh
32
29 channel W28 . The Walsh channel assignments for the Physical Layer Reverse Traffic
30 Channels are shown in Table 11.3.1.3.1-1.
11-16
2 Channel
Channel Walsh Channel
Pilot W016
Reverse Rate Indicator (RRI) W416

Data Source Control (DSC) W1232
Data Rate Control (DRC) W816
ACK W1232
Data W24 and/or W12
Auxiliary Pilot W2832
13 shown.
23 The access terminal shall not forward the physical layer packet to a higher layer if the
24 physical layer packet was not successfully received.
11-17
W016 = ( + + + + + + + + + + + + + + + + )
Signal Point
(All 0's) 0 +1
1 –1
128 Binary
Symbols
per Slot W24 = (+ + − − )
Signal Point
Channel Mapping
Interleaver 0 +1
1 –1
256 Bits, 9.6 kbps 1,024 Symbols 38.4 ksps 307.2 ksps
cos(2 fCt)
I I Baseband
Filter
Quadrature
Spreading
I = I PNI – Q PNQ
Relative Filter
Gain
1.2288 Mcps PNI PNQ

sin(2 fCt)
Walsh Cover
(+ – )

Decimator
of 2 values with the mapping +1 for
PI PQ
I-Channel Q-Channel
Short Short
UI UQ
I-Channel Q-Channel
1
2 Figure 11.3.1.3.1-1. Reverse Channel Structure for the Access Channel
11-18
W016 = (+ + + + + + + + + + + + + + + +)
W2832 = (+ + + + − − − − − − − − + + + + − − − − + + + + + + + + − − − −)
W416 = (+ + + + − − − − + + + + − − − −)
W1232 = ( + + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + + )
W1232 = (+ + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + +)
W816 = ( + + + + + + + + − − − − − − − −)
Wi8 i = 0,1,...7
3 the Reverse Traffic Channel (Part 1 of 5)
11-19
W24 = (+ + − −)
W24 = (+ + − −)
W24 = (+ + − −)
W12 = (+ −)
W12 = (+ −)
11-20
W24 = (+ + − −) 1
3
1 Symbol 4 Chips
D4I
First 2 Code
Symbols QPSK
Modulator
D4Q
1 Symbol 4 Chips
1
W24 = (+ + − −) 3
6 Code
Demux
Symbols
W12 = (+ −) 2
3
2 Symbols 4 Chips
D2I
QPSK
Last 4 Code Modulator
Symbols
D2Q
2 Symbols 4 Chips
2
W12 = (+ −) 3
D4I
Data I
G
D2I
D4Q
Data Q
H
D2Q
Q4Q2 modulation
1
11-21
W24 = (+ + − −) 1
3
1 Symbol 4 Chips
E4I
First 3 Code
Symbols 8-PSK
Modulator
E4Q
1 Symbol 4 Chips
1
W24 = (+ + − −) 3
9 Code
Demux
Symbols
W12 = (+ −) 2
3
2 Symbols 4 Chips
E2I
8-PSK
Last 6 Code Mapping
Symbols
E2Q
2 Symbols 4 Chips
2
W12 = (+ −) 3
E4I
Data I
G
E2I
E4Q
Data Q
H
E2Q
E4E2 modulation
2
11-22
11-23

Channel Physical
Layer Packet
Transmissions
with 153.6 kbps
DRC Channel
Transmission
Requesting
153.6 kbps
DRC
Request for
ACK Channel
Half-Slot
Transmissions
NAK NAK NAK ACK
One Slot
or
1 NAK
3 Normal Termination

Transmission

Forward Traffic
Channel Physical
Layer Packet
Transmissions
with 153.6 kbps
DRC Channel
Transmission
Requesting
153.6 kbps
DRC
Request for
ACK Channel
Half-Slot
Transmissions
NAK NAK ACK

One Slot
4
6 Early Termination
11-24
2 Figure 11.3.1.3.1-9. Reverse Traffic Channel Sub-frame Structure

4 The modulation parameters for the Access Channel and the Reverse Traffic Channel shall
5 be as specified in Table 11.3.1.3.1.1-1 and Table 11.3.1.3.1.1-2, respectively.
6 Table 11.3.1.3.1.1-1. Modulation Parameters for the Access Channel
Data Rate (kbps)

Parameter 9.6 19.2 38.4
Reverse Rate Index 1 2 3

Bits per Physical
256 512 1,024
Layer Packet
Physical Layer
Packet Duration 26.66… 26.66… 26.66…
(ms)
Code Rate 1/4 1/4 1/4
Code Symbols per
Physical Layer 1,024 2,048 4,096
Packet
Code Symbol Rate
38.4 76.8 153.6
(ksps)
Interleaved Packet
8 4 2
Repeats
Modulation Symbol
307.2 307.2 307.2
Rate (ksps)
Modulation Type BPSK BPSK BPSK
PN Chips per
Physical Layer 128 64 32
Packet Bit
7
11-25
1 Table 11.3.1.3.1.1-2. Modulation Parameters for the Reverse Traffic Channel
Payloa Modulation Effective Data Rate (kbps) Effective Code Rate

d Size [Repetition]
(bits)
After After After After After After After After
4 8 12 16 4 8 12 16
Slots Slots Slots Slots Slots Slots Slots Slots
128 B4 19.2 9.6 6.4 4.8 1/5 1/5 1/5 1/5

[3.2] [6.4] [9.6] [12.8]
256 B4 38.4 19.2 12.8 9.6 1/5 1/5 1/5 1/5
[1.6] [3.2] [4.8] [6.4]
512 B4 76.8 38.4 25.6 19.2 1/4 1/5 1/5 1/5
[1] [1.6] [2.4] [3.2]
768 B4 115.2 57.6 38.4 28.8 3/8 1/5 1/5 1/5
[1] [1.07] [1.6] [2.13]
1024 B4 153.6 76.8 51.2 38.4 1/2 1/4 1/5 1/5
[1] [1] [1.2] [1.6]
1536 Q4 230.4 115.2 76.8 57.6 3/8 1/5 1/5 1/5
[1] [1.07] [1.6] [2.13]
2048 Q4 307.2 153.6 102.4 76.8 1/2 1/4 1/5 1/5
[1] [1] [1.2] [1.6]
3072 Q2 460.8 230.4 153.6 115.2 3/8 1/5 1/5 1/5
[1] [1.07] [1.6] [2.13]
4096 Q2 614.4 307.2 204.8 153.6 1/2 1/4 1/5 1/5
[1] [1] [1.2] [1.6]
6144 Q4Q2 921.6 460.8 307.2 230.4 1/2 1/4 1/5 1/5
[1] [1] [1.2] [1.6]
8192 Q4Q2 1228.8 614.4 409.6 307.2 2/3 1/3 2/9 1/5
[1] [1] [1] [1.2]
12288 E4E2 1843.2 921.6 614.4 460.8 2/3 1/3 1/3 1/3
[1] [1] [1.5] [2]
2
3 12.3.1.3.1.211.3.1.3.1.2 Data Rates

4 The access terminal shall transmit information on the Access Channel at a data rate of 9.6
5 kbps, 19.2 kbps, or 38.4 kbps.
6 The access terminal shall transmit information on the Reverse Traffic Channel at a variable
7 data rate ranging from 4.8 kbps to 1228.8 kbps as shown in Table 12.3.1.3.1.1-2,
8 according to the Reverse Traffic Channel MAC Protocol. The access terminal may transmit
9 information on the Reverse Traffic Channel at 1843.2 kbps using the 12288-bit payload as
10 shown in Table 11.3.1.3.1.1-2 according to Rate1M8Supported, which is public data of the
11-26
1 12.3.1.3.211.3.1.3.2 Access Channel

4 consists of a Pilot Channel and a Data Channel as shown in Figure 11.3.1.3.2-1.
11 equal to that of the data portion transmitted at 9.6 kbps as shown in Figure 11.3.1.3.2-1.
12 The preamble length is specified by the parameter PreambleLength or the parameter
13 PreambleLengthSlots which are public data from the Access Channel MAC Protocol. The
14 Access Channel physical layer packets are transmitted at data rates of 9.6, 19.2, or 38.4
15 kbps.
16

18 kbps
11-27

3 or 38.4 kbps
4 12.3.1.3.2.111.3.1.3.2.1 Pilot Channel

7 transmission. It istransmittedis transmitted on the I channel using the 16-chip Walsh
8 function number 0 ( W016 = + + + + + + + + + + + + + + + +) cover.
9 12.3.1.3.2.211.3.1.3.2.2 Data Channel

11 Channel during every access probe. The Access Channel physical layer packets are
12 transmitted at data rates of 9.6 kbps, 19.2 kbps, or 38.4 kbps on the Q-branch using the
13 4-chip Walsh function number 2 ( W24 = + + – –). The Access Channel physical layer packets
14 shall be preceded by a preamble of PreambleLength frames or PreambleLengthSlots slots
15 where only the Pilot Channel is transmitted. The PreambleLength parameter and the
16 PreambleLengthSlots parameter are public data from the Access Channel MAC Protocol.
17 12.3.1.3.311.3.1.3.3 Reverse Traffic Channel

19 or signaling information to the access network. The Reverse Traffic Channel consists of a
20 Pilot Channel, an RRI Channel, a DSC Channel, a DRC Channel, an ACK Channel, and a
21 Data Channel. The Reverse Traffic Channel may also include an Auxiliary Pilot Channel.
22 The access terminal supports transmission of information on the Data Channel of the
23 Reverse Traffic Channel at a variable data rate ranging from of 4.8 kbps to 1228.8 kbps as
24 shown in Table 11.3.1.3.1.1-2. The access terminal may transmit information on the
25 Reverse Traffic Channel at 1843.2 kbps using the 12288-bit payload as shown in Table
26 11.3.1.3.1.1-2, according to Rate1M8Supported, which is public data of the Reverse Traffic
27 Channel MAC Protocol. The data rate used on the Data Channel is specified by the Reverse
28 Traffic Channel MAC Protocol. The gain of the Data Channel relative to that of the Pilot
11-28
1 Channel for the Reverse Traffic Channel depends on the T2P (traffic-to-pilot power ratio)
2 profile for the transmitted payload size and the transmission mode of the packet. The T2P
3 profile for each payload size and transmission mode are determined by the Reverse Traffic
4 Channel MAC Protocol (see 9.12).The Reverse Traffic Channel MAC Protocol supports two
5 transmission modes, the High Capacity mode and the Low Latency mode. Each
6 transmission mode is characterized by a physical layer transmit duration of one, two, three
7 or four sub-packets. The T2P profile is defined for each payload size for each transmission
8 mode and is characterized by the T2P transition. The T2P transition is the number of sub-
9 packets of a Reverse Traffic Channel packet transmitted from the beginning of the
10 transmission prior to a change in the T2P.
11 12.3.1.3.3.111.3.1.3.3.1 Pilot Channel

13 Pilot Channel. It is transmitted on the I channel using the 16-chip Walsh function number
14 0 ( W016 = + + + + + + + + + + + + + + + +) cover.

16 The RRI Channel is used by the access terminal to indicate the payload size and sub-
17 packet identifier of the physical layer packet transmitted on the Data Channel.
18 The transmitted payload size shall be a 4-bit symbol as shown in Table 11.3.1.3.3.2-1. The
19 sub-packet identifier shall be a 2-bit symbol as shown in Table 11.3.1.3.3.2-2. The 6-bit
20 RRI symbol shall be formed using the 4-bit symbol representing the payload size and the 2-
21 bit symbol representing the sub-packet identifier. A 32-dimensional bi-orthogonal signal
22 constellation shall be used to encode the 6-bit RRI symbols. The bi-orthogonal signal
23 constellation shall be assigned based on the payload size and the sub-packet identifier. The
24 Walsh function used to represent the RRI shall be based on the payload index i and sub-
25 packet index j as shown in the following equations:
32
W 2×i + ⎣ j / 2 ⎦ if j = odd
W232×i + ⎣ j / 2 ⎦ if j = even
26
27 The bi-orthogonal codeword shall be repeated four times. The resulting symbols are
16
28 covered with the 16-chip Walsh Channel W . The RRI Channel is transmitted on the in-
4
29 phase (I) channel. The access terminal shall set the payload index to 0x0 and sub-packet
30 index to 0 to indicate a null-rate RRI.
11-29
1 Table 11.3.1.3.3.2-1. Payload Size to Payload Index Mapping
Payload Size Payload Index

(bits)
0 0x0
128 0x1
256 0x2
512 0x3
768 0x4
1024 0x5
1536 0x6
2048 0x7
3072 0x8
4096 0x9
6144 0xa
8192 0xb
12288 0xc
Reserved 0xd
Reserved 0xe
Reserved 0xf
2
3 Table 11.3.1.3.3.2-2. Sub-packet Identifier to Sub-packet Index Mapping
Sub-packet Sub-packet
Identifier Index
0 0x0
1 0x1
2 0x2
3 0x3
4
5 12.3.1.3.3.311.3.1.3.3.3 Data Source Control Channel

6 The access terminal uses the DSC Channel to indicate to the access network the selected
7 serving cell on the forward link. The serving cell is indicated by the DSC value (3-bit value
8 as specified in Table 11.3.1.3.3.3-1) for that cell. The DSC value takes effect one slot after
9 the end of its transmission and stays in effect for DSCLength slots, where DSCLength is
10 public data of the Forward Traffic Channel MAC Protocol.
11-30
1 The DSC values shall be transmitted at a data rate of 600/DSCLength DSC values per
2 second. The DSC values shall be block encoded to yield 32-bit codewords, as specified in
3 Table 11.3.1.3.3.3-1. The DSC value is repeated for DSCLength consecutive slots. Each bit
32
4 of the codeword is spread by a 32-ary Walsh function W12 . The DSC Channel is
5 transmitted on the in-phase (I) Channel as shown in Figure 11.3.1.3.1-6.
6 The timing of the Forward Traffic Channel transmission corresponding to a DSC symbol
7 shall be as specified by the Forward Traffic Channel MAC Protocol. Figure 11.3.1.3.3-1
8 shows transmission of DSC symbols based on the Forward Traffic Channel MAC Protocol.
9 Figure 11.3.1.3.3-1 shows an example of the DSC Channel timeline for a DRCLength of two
10 slots and DSCLength of eight slots.
11 Table 11.3.1.3.3.3-1. DSC Encoding
DSC Value Codeword
0x0 00000000000000000000000000000000
0x1 01011010101101010110101011010101
0x2 00110110011011001101100110110011
0x3 01101100110110011011001101100110
0x4 11110001111000111100011110001111
0x5 10101011010101101010110101011010
0x6 11000111100011110001111000111100
0x7 10011101001110100111010011101001
12
11-31
DRCLength =
2 slots
1 slot ½ slot
DSC m1 DSC m DSC m+1
DSCLength = 8 slots DSCLength = 8 slots
Period of Validity of DSC m1 Period of Validity of DSC m
1 slot
½ slot
A D A D A D A D A DA D A D A D
C S C S C S C S C S C S C S C S
K C K C K C K C K C K C K C K C
D D D D
R R R R
C C C C
Change of DRC Cover

1
2 Figure 11.3.1.3.3-1. DSC Channel Timeline

5 selected serving sector and the requested data rate on the Forward Traffic Channel. The
6 requested Forward Traffic Channel data rate is mapped into a four-bit DRC value as
7 specified by the Forward Traffic Channel MAC Protocol. An 8-ary Walsh function
8 corresponding to the selected serving sector is used to spread the DRC Channel
9 transmission. The cover mapping is defined by the public data DRCCover from the Forward
16 The DRC values shall be block encoded to yield 8-bit bi-orthogonal codewords, as specified
17 in Table 11.3.1.3.3.4-1. Each DRC codeword shall be transmitted twice per slot. Each bit of
18 a repeated codeword shall be spread by an 8-ary Walsh function Wi8 as defined in Table
11-32
1 11.3.1.3.3.4-1, where i equals DRCCover. Each Walsh chip of the 8-ary Walsh function is
2 further spread by the Walsh function W816 . Each DRC value shall be transmitted over
3 DRCLength slots when the DRC Channel is continuously transmitted.
10 The DRC Channel shall be transmitted on the Q-branch as shown in Figure 11.3.1.3.1-6.
13 DRC symbols shall start at the mid-slot point. The timing for the Forward Traffic Channel
14 MAC Protocol for nongated and gated transmissions are shown in Figure 11.3.1.3.3.4-1
15 and Figure 11.3.1.3.3.4-2, respectively.
DRC Value Codeword
0x0 00000000
0x1 11111111
0x2 01010101
0x3 10101010
0x4 00110011
0x5 11001100
0x6 01100110
0x7 10011001
0x8 00001111
0x9 11110000
0xA 01011010
0xB 10100101
0xC 00111100
0xD 11000011
0xE 01101001
0xF 10010110
17
11-33
W08 0000 0000
W18 0101 0101
W28 0011 0011
W38 0110 0110
W48 0000 1111
W58 0101 1010
W68 0011 1100
W78 0110 1001

2
One Slot
DRC Channel
Transmission
a) DRCLength = 1

DRC Channel
Transmission
b) DRCLength = 2

DRC Channel
Transmission
c) DRCLength = 4

DRC Channel
Transmission
d) DRCLength = 8
3
11-34
One Slot
DRC Channel
Transmission
a) DRCLength = 2

DRC Channel
Transmission
b) DRCLength = 4

DRC Channel
Transmission
c) DRCLength = 8
1
3 12.3.1.3.3.511.3.1.3.3.5 ACK Channel

5 physical layer packet addressed to the access terminal and transmitted on the Forward
6 Traffic Channel has been received successfully or not. The access terminal shall transmit
7 an ACK Channel bit in response to every Forward Traffic Channel slot that is associated
8 with a detected preamble directed to the access terminal. The access terminal shall
9 transmit at most one redundant positive ACK in response to a Forward Traffic Channel slot
10 that is detected as a continuation of the physical layer packet that has been successfully
11 received. Otherwise, the ACK Channel shall be gated off.
12 When acknowledging a Single User packet, the ACK Channel shall use BPSK (bipolar
13 keying) modulation, with a 1 representing positive acknowledgement and –1 representing
14 negative acknowledgment. When acknowledging a Multi-User packet, the ACK Channel
15 shall use OOK (ON-OFF keying) modulation, with a 1 (ON) representing positive
16 acknowledgement and a 0 (OFF) representing negative acknowledgment. The access
17 terminal shall transmit a positive acknowledgment on the ACK channel if it successfully
18 receives a packet addressed to it on the Forward Traffic Channel. Otherwise, the access
19 terminal shall transmit a negative acknowledgment on the ACK channel. A Forward Traffic
20 Channel physical layer packet is considered successfully received if it has a valid FCS. The
21 address of a Single User packet is indicated by the packet preamble, whereas the address
22 of a Multi-User packet is indicated by the MAC Layer header. For a Forward Traffic
23 Channel physical layer packet transmitted in slot n on the Forward Channel, the
24 corresponding ACK Channel bit shall be transmitted in slot n + 3 on the Reverse Channel
25 (see Figure 11.3.1.3.1-7 and Figure 11.3.1.3.1-8). The ACK Channel transmission shall be
11-35
1 transmitted in the first half of the slot and shall last for 1024 PN chips as shown in Figure
2 11.3.1.3.1-7 and Figure 11.3.1.3.1-8. The ACK Channel uses the Walsh channel identified
32
3 by the Walsh function W12 and is transmitted on the I-branch.
4 A Forward Traffic Channel physical layer packet is considered successfully received if the
5 FCS checks. For a Forward Traffic Channel physical layer packet transmitted in slot n on
6 the Forward Channel, the corresponding ACK Channel bit shall be transmitted in slot n + 3
7 on the Reverse Channel (see Figure 11.3.1.3.1-7 and Figure 11.3.1.3.1-8). The ACK
8 Channel transmission shall be transmitted in the first half of the slot and shall last for
9 1024 PN chips as shown in Figure 11.3.1.3.1-7 and Figure 11.3.1.3.1-8. The ACK Channel
32
10 shall use the Walsh channel identified by the Walsh function W12 and shall be transmitted
11 on the I channel.
12 12.3.1.3.3.611.3.1.3.3.6 Data Channel

13 The Data Channel is transmitted at the data rates given in Table 11.3.1.3.1.1-2. An access
14 terminal shall not start a new packet transmission in any slot T specified by the following
15 equation:
16 (T-FrameOffset) mod 4 ≠ 0,
17 where T is the CDMA System Time in slots. The FrameOffset parameter is public data of
18 the Reverse Traffic Channel MAC Protocol. All data transmitted on the Reverse Traffic
19 Channel is encoded, block interleaved, sequence repeated, BPSK, QPSK, or 8-PSK
2
20 modulated and orthogonally spread by Walsh function W24 or Walsh function W1 or both.
21 The Data Channel shall be modulated as shown in Table 11.3.1.3.3.6-1.
22 Table 11.3.1.3.3.6-1. Data Channel Modulation Formats
Modulation
(Modulation, Walsh Function)
Format
B4 (BPSK, W24 )
Q4 (QPSK, W24 )
2
Q2 (QPSK, W1 )
2
Q4Q2 (QPSK, W24 ) + (QPSK, W1 )
2
E4E2 (8-PSK, W24 ) + (8-PSK, W1 )
23 12.3.1.3.3.711.3.1.3.3.7 Auxiliary Pilot Channel

24 The access terminal shall transmit on the Auxiliary Pilot Channel unmodulated symbols
25 with a binary value of ‘0’. The Auxiliary Pilot Channel shall be transmitted during the nth
26 half slot if the transmitted payload during half slots n−1 or n+1 is greater than or equal to
27 AuxiliaryPilotChannelMinPayload, which is public data of the Reverse Traffic Channel MAC
28 Protocol. If the Auxiliary Pilot Channel is transmitted during the nth half slot , its power
29 shall be specified relative to the maximum of the Data Channel Gains during half-slots n−1
11-36
1 and n+1 by AuxiliaryPilotChannelGain, where AuxiliaryPilotChannelGain is public data of

2 the Reverse Traffic Channel MAC Protocol. The Auxiliary Pilot Channel power level shall be
3 updated at the start of every half slot.
4 If the Auxiliary Pilot Channel is transmitted, it uses the Walsh channel identified by the
32
5 Walsh function W28 and is transmitted on the I-branch as shown in Figure 11.3.1.3.1-6.
6 12.3.1.3.411.3.1.3.4 Encoding

8 The Access Channel physical layer packets shall be encoded with code rate of 1/4. First,
9 the encoder shall discard the six bits of the TAIL field in the physical layer packet inputs
10 (i.e., it shall discard the last six bits in the input physical layer packets). Then, it shall
11 encode the remaining bits with a turbo encoder, as specified in 11.3.1.3.4.2. The turbo
12 encoder will add an internally generated tail.
13 The encoder parameters shall be as specified in Table 11.3.1.3.4-1.
14 Table 11.3.1.3.4-1. Parameters for the Reverse Link Encoder for the Access Channel
Data Rate
9.6 19.2 38.4
(kbps)

Code Rate 1/4 1/4 1/4
Bits per
256 512 1,024
Number of Turbo Encoder Input
250 506 1,018
Symbols
Turbo Encoder Code Rate 1/4 1/4 1/4
Encoder Output Block Length
1,024 2,048 4,096
(Code Symbols)
15
16 The Reverse Traffic Channel physical layer packets shall be encoded with code rates of 1/5
17 or 1/3. First, the encoder shall discard the six bits of the TAIL field in the physical layer
18 packet inputs (i.e., it shall discard the last six bits in the input physical layer packets).
19 Then, it shall encode the remaining bits with a turbo encoder, as specified in 11.3.1.3.4.2.
20 The turbo encoder will add an internally generated tail.
21 The encoder parameters shall be as specified in Table 11.3.1.3.4-2 and Table 11.3.1.3.4-3.
11-37
2 Channel – Part 1 of 2
Data Rate
(kbps) 4.8 9.6 19.2 28.8 38.4 57.6
[After 16 Slots]
Code Rate 1/5 1/5 1/5 1/5 1/5 1/5

Bits per
Physical Layer 128 256 512 768 1,024 1,536
Packet
Number of Turbo
Encoder Input 122 250 506 762 1,018 1,530
Symbols
Turbo Encoder
1/5 1/5 1/5 1/5 1/5 1/5
Code Rate
Encoder Output
Block Length 640 1,280 2,560 3,840 5,120 7,680
(Code Symbols)
3
Data Rate
(kbps) 76.8 115.2 153.6 230.4 307.2 460.8
[ After 16 Slots]
Code Rate 1/5 1/5 1/5 1/5 1/5 1/3

Bits per
Physical Layer 2,048 3,072 4,096 6,144 8,192 12,288
Packet
Number of Turbo
Encoder Input 2,042 3,066 4,090 6,138 8,186 12,282
Symbols
Turbo Encoder
1/5 1/5 1/5 1/5 1/5 1/3
Code Rate
Encoder Output
10,24 15,36 30,74
Block Length 20,480 40,960 36,864
0 0 0
(Code Symbols)
6 12.3.1.3.4.211.3.1.3.4.2 Turbo Encoding

11-38
1 symbols followed by 6/R tail output symbols, where R is the code rate of 1/3, 1/4, or 1/5.
8 12.3.1.3.4.2.111.3.1.3.4.2.1 Turbo Encoders

14 A common constituent code shall be used for the rate 1/3, 1/4, and 1/5 Turbo codes. The
⎡ n0 (D) n1(D) ⎤
G(D) = ⎢1 ⎥
⎣ d(D) d(D) ⎥⎦
16

11-39
2 output first.
7 XXY0Y1, and the tail output symbols for each of the last three tail bit periods shall be
8 X′X′Y′0Y′1. For rate-1/5 turbo codes, the tail output code symbols for each of the first three
9 tail bit periods shall be punctured and repeated to achieve the sequence XXY0Y1Y1, and
10 the tail output code symbols for each of the last three tail bit periods shall be punctured
11 and repeated to achieve the sequence X′X′Y′0Y′1Y′1. For rate-1/3 turbo codes, the tail
12 output symbols for each of the first three tail bit periods shall be XXY0, and the tail output
13 symbols for each of the last three tail bit periods shall be X′X′Y′0.
11-40
X
Y0
n0
Y1
n1
Nturbo
Information
Bits
(Input)
Control
Puncturing Code
and Symbols
Turbo
Interleaver
X'
Y'0
n0
Y'1
n1
Control
1
11-41
Code Rate
Output 1/3 1/4 1/5
X 1 11 1
Y0 1 11 1
Y1 0 10 1
X′ 0 00 0
Y′ 0 1 01 1
Y′ 1 0 11 1
2
Code Rate
Output 1/3 1/4 1/5
X 111 000 111 000 111 000

Y0 111 000 111 000 111 000
Y1 000 000 111 000 111 000
X′ 000 111 000 111 000 111
Y′ 0 000 111 000 111 000 111
Y′ 1 000 000 000 111 000 111
be read first from top to bottom repeating X and X′, and then
from left to right. For rate-1/5 turbo codes, the puncturing table
shall be read first from top to bottom repeating X, X′, Y1, and Y′1
and then from left to right.
4

11-42
14 the value of n.
Add 1
Counter Lookup
5 LSBs Bit 5 Bits

23
11-43
Turbo Turbo
Nturbo n
128 122 2
256 250 3
512 506 4
768 762 5
1,024 1,018 5
1,536 1,530 6
2,048 2,042 6
3,072 3,066 7
4,096 4,090 7
6,144 6,138 8
8,192 8,186 8
12,288 12,282 9
2
11-44
Table n=2 n=3 n=4 n=5 n=6 n=7 n=8 n=9

Index Entries Entries Entries Entries Entries Entries Entries Entries
0 3 1 5 27 3 15 3 13
1 3 1 15 3 27 127 1 335
2 3 3 5 1 15 89 5 87
3 1 5 15 15 13 1 83 15
4 3 1 1 13 29 31 19 15
5 1 5 9 17 5 15 179 1
6 3 1 9 23 1 61 19 333
7 1 5 15 13 31 47 99 11
8 1 3 13 9 3 127 23 13
9 1 5 15 3 9 17 1 1
10 3 3 7 15 15 119 3 121
11 1 5 11 3 31 15 13 155
12 1 3 15 13 17 57 13 1
13 1 5 3 1 5 123 3 175
14 1 5 15 13 39 95 17 421
15 3 1 5 29 1 5 1 5
16 3 3 13 21 19 85 63 509
17 1 5 15 19 27 17 131 215
18 3 3 9 1 15 55 17 47
19 3 5 3 3 13 57 131 425
20 3 3 1 29 45 15 211 295
21 1 5 3 17 5 41 173 229
22 3 5 15 25 33 93 231 427
23 1 5 1 29 15 87 171 83
24 3 1 13 9 13 63 23 409
25 1 5 1 13 9 15 147 387
26 3 1 9 23 15 13 243 193
27 1 5 15 13 31 15 213 57
28 3 3 11 13 17 81 189 501
29 1 5 3 1 5 57 51 313
30 1 5 15 13 15 31 15 489
31 3 3 5 13 33 69 67 391
2
11-45
1 12.3.1.3.511.3.1.3.5 Scrambling for Reverse Traffic Channel Physical Layer Packets

5 Figure 11.3.1.3.5-1. At the start of the physical layer packet, the shift register shall be
6 initialized to the state [11111111111i1i0d3d2d1d0]. The d3d2d1d0 bits shall be determined
7 by the payload size, as specified in Table 11.3.1.3.5-1. The i1i0 bits shall be determined by
8 the reverse link interlace offset151, as specified in Table 11.3.1.3.5-2. The initial state shall
13 Table 11.3.1.3.5-1. Parameters Controlling the Scrambler Initial State – Part 1 of 2
Payload Size (bits) d3 d2 d1 d0
128 0 0 0 0
256 0 0 0 1
512 0 0 1 0
768 0 0 1 1
1024 0 1 0 0
1536 0 1 0 1
2048 0 1 1 0
3072 0 1 1 1
4096 1 0 0 0
6144 1 0 0 1
8192 1 0 1 0
12288 1 0 1 1
14
Reverse Link Interlace Offset i1 i0
0 0 0
1 0 1
2 1 0
16
151 The reverse-link interlace offset i for a sub-packet starting in slot T is specified as i = (T -
FrameOffset)/4 mod 3, where T is the CDMA System Time in slots and 0 ≤ i ≤ 2.
11-46
1 1 1 1 1 1 1 1 1 1 1 i1 i0 d3 d2 d1 d0
Scrambling
Sequence
1
2 Figure 11.3.1.3.5-1. Symbol Scrambler
3 12.3.1.3.611.3.1.3.6 Channel Interleaving for Access Channel Physical Layer Packets

13 satisfies:

21 address.
11-47
Counter
bL–1 bL–2 b1 b0
Bit_Reversal
b0 b1 bL–2 bL–1

1
3 12.3.1.3.711.3.1.3.7 Channel Interleaving for Reverse Traffic Channel Physical Layer

4 Packets
5 The sequence of binary symbols at the output of the encoder shall be interleaved with a
6 channel interleaver. Channel interleaving shall consist of a Symbol Reordering stage
7 followed by a Matrix Interleaving stage.
8 The packet length, N (including data and tail bits) is expressed as N = R × K × 2m, where, R,
9 K and m are positive integers. The channel interleaver is described in terms of the
10 parameters R, K, m, and an end-around-shift parameter D.
11 12.3.1.3.7.111.3.1.3.7.1 Symbol Reordering

12 Turbo encoder data and tail output symbols generated with the rate-1/5 encoder shall be
13 reordered according to the following steps:
14 1. All of the data and tail turbo encoder output symbols shall be demultiplexed into
15 five sequences denoted U, V0, V1, V′0, and V′1. The scrambled encoder output
16 symbols shall be sequentially distributed from the U sequence to the V′1 sequence
17 with the first scrambled encoder output symbol going to the U sequence, the second
18 to the V0 sequence, the third to the V1 sequence, the fourth to the V′0 sequence,
19 the fifth to the V′1 sequence, the sixth to the U sequence, etc.
22 shall be last.
11-48
2 demultiplexed into three sequences denoted U, V0 and V′0. The scrambled encoder
6 sequence, etc.
7 2. The U, V0 and V′0 sequences shall be ordered according to UV0 V′0. That is, the U
9 12.3.1.3.7.211.3.1.3.7.2 Matrix Interleaving

10 The Matrix Interleaving operation is carried out in the following steps:
11 1. The N symbols of the U-sequence symbols are written into a 3-dimensional cuboidal
12 array with R rows, C ≡ 2m columns, and K levels. Symbols are written into the 3-
13 dimensional array with level-index incrementing first, followed by column-index,
14 followed by row-index. In other words, the ith incoming symbol ((r × C + c) × K + k),
15 where 0 ≤ i < N goes into the rth row, cth column, and kth level where, 0 ≤ r < R, 0 ≤
16 c < C, and 0 ≤ k < K.
17 2. The linear array of R symbols, at the cth column and kth level, is end-around-
18 shifted by (c × K + k) mod R. In other words, matrix[r] [c] [k] is transformed to
19 matrix[(r + c × K + k) mod R] [c] [k].
20 3. The linear array of C ≡ 2m symbols, at each given level and row, is bit-reverse
21 interleaved (based on column-index). Symbols from the cuboidal array are read out
22 with row-index incrementing first, followed by column-index, followed by level-
23 index. In other words, the ith output symbol ((k × C + c) × R + r), where 0 ≤ i < N
24 comes from the rth row, cth column, and kth level, where 0 ≤ r < R , 0 ≤ c < C, and 0
25 ≤ k < K.
26 4. The N symbols of the V0 sequence, followed by the N symbols of the V0’ sequence
27 are written into a 3-dimensional cuboidal array with R rows, C ≡ 2m+1 columns and
28 K levels. Symbols are written into the 3-dimensional array with level-index
29 incrementing first, followed by column-index, followed by row-index. In other words,
30 the ith incoming symbol ((r × C + c) × K + k), where 0 ≤ i < 2 × N goes into the rth
31 row, cth column, and kth level, where 0 ≤ r < R , 0 ≤ c < C, and 0 ≤ k < K.
33 shifted by the amount ⎣(K × c + k) / D⎦ mod R. In other words, matrix[r][c][k] is
34 transformed to matrix[r + ⎣( K × c + k) / D⎦ mod R][c] [k].
35 6. The linear array of C ≡ 2m+1 symbols, at each given level and row, is bit-reverse
36 interleaved (based on the column-index).
37 7. Symbols from the cuboidal array are read out with row-index incrementing first,
38 followed by column-index, followed by level-index. In other words, the ith output
39 symbol ((k × C + c) × R + r), where 0 ≤ i < 2 × N comes from the rth row, cth column,
40 and kth level , where, 0 ≤ r < R , 0 ≤ c < C, and 0 ≤ k < K.
11-49
1 8. The sequence of V1 and V1’ symbols are processed similar to the V0 and V0’
2 symbols, as described in 4 through 7.
3 Table 12.3.1.3.7.2-1 below shows the interleaver parameters for various packets used on
4 the Reverse Traffic Channel.
5 Table 11.3.1.3.7.2-1. Channel Interleaver Parameters
Payload size (bits) N K R m D
128 128 1 1 7 1
256 256 1 1 8 1
512 512 1 1 9 1
768 768 3 1 8 1
1024 1024 1 1 10 1
1536 1536 3 2 8 1
2048 2048 1 2 10 1
3072 3072 3 2 9 1
4096 4096 1 2 11 1
6144 6144 3 2 10 1
8192 8192 1 2 12 1
12288 12288 1 3 12 1
6

8 The Pilot Channel, the RRI Channel, the DSC Channel, the DRC Channel, the ACK
9 Channel, the Data Channel, and the Auxiliary Pilot Channel shall be spread with Walsh
13 The Walsh cover assignments are shown in Figure 11.3.1.3.1-2, Figure 11.3.1.3.1-3, and
14 Figure 11.3.1.3.1-4. The Pilot Channel shall be covered by the 16-chip Walsh function
15 number 0 ( W016 = + + + + + + + + + + + + + + + +). The RRI Channel shall be covered by a
16
16 16-chip Walsh function number 4 ( W4 = + + + + – – – – + + + + – – – –). The DSC channel
17 shall be time-division multiplexed with the ACK Channel and covered by the 32-chip Walsh
32
18 function number 12 ( W12 = + + + + – – – – – – – – + + + + + + + + – – – – – – – – + + + +). The
19 DRC Channel shall be covered by the 16-chip Walsh function number 8 ( W816 =
20 + + + + + + + + – – – – – – – –). The ACK Channel shall be time-division multiplexed with the
32
21 DSC Channel and covered by the 32-chip Walsh function number 12 ( W12 = + + + + – – – –
22 – – – – + + + + + + + + – – – – – – – – + + + +). The Data Channel shall be covered by one or
23 both of the 4-chip Walsh function number 2 ( W24 = + + – –) and the 2-chip Walsh function
11-50
2
1 number 1 ( W1 = + − ). The Auxiliary Pilot Channel shall be covered by a 32-chip Walsh
32
2 function number 28 ( W28 = + + + + − − − − − − − − + + + + − − − − + + + + + + + + − − − −).
3 The RRI, DSC, DRC, ACK, and Data Channel chip sequences shall be scaled by a factor
4 that gives the gain of each of these channels relative to that of the Pilot Channel. The
5 Auxiliary Pilot Channel chip sequences shall be scaled by a factor that gives its gain
6 relative to that of the Data Channel. The relative gain values for the RRI, DSC, DRC, and
7 Data Channel are specified by the parameters RRIChannelGain, DSCChannelGain,
8 DRCChannelGain, and TxT2P. The relative gain value for the ACK Channel transmitted in
9 response to a Single User packet is specified by the parameter ACKChannelGain. The
10 relative gain value for the ACK Channel transmitted in response to a Multi-User packet is
11 specified by ACKChannelGain + DeltaACKChannelGainMUP. The relative gain value for the
12 Auxiliary Pilot Channel is specified by the parameter AuxiliaryPilotChannelGain. The
13 DSCChannelGain, DRCChannelGain, ACKChannelGain, and DeltaACKChannelGainMUP
14 are public data of the Forward Traffic Channel MAC Protocol. The RRIChannelGain is
15 public data of the Reverse Traffic Channel MAC Protocol. For the Reverse Traffic Channel,
16 the relative gain is specified by TxT2P, where TxT2P is public data of the Reverse Traffic
17 Channel MAC Protocol. For the Auxiliary Pilot Channel, the relative gain is specified by
18 AuxiliaryPilotChannelGain where AuxiliaryPilotChannelGain is public data of the Reverse
19 Traffic Channel MAC Protocol. For the Access Channel, the relative gain of the Data
21 Protocol.
22 12.3.1.3.911.3.1.3.9 Modulation
24 phase stream and a quadrature stream of modulated values. The channel interleaver
25 output is modulated and Walsh covered. The modulator generates BPSK, QPSK, or 8-PSK
2
26 modulation symbols that are Walsh covered by a 2-ary Walsh cover W1 , a 4-ary Walsh
4
27 cover W2 or both. The modulation and Walsh covering depends on the payload size. The
28 modulation formats are B4, Q4, Q2, Q4Q2, and E4E2.
29 12.3.1.3.9.111.3.1.3.9.1 B4 Modulation
30 For physical layer packet sizes with payload sizes less than or equal to 1024 bits, each
31 channel interleaver output symbol shall form a B4 modulation symbol (BPSK modulated
4
32 and Walsh covered by a 4-ary Walsh cover, W2 as specified in Table 11.3.1.3.9.1-1.)
11-51
1 Table 11.3.1.3.9.1-1. B4 Modulation Table
Interleaved Modulation
Symbols Symbols
0 +D +D –D –D
1 –D –D +D +D
Note: D = 1 .
2 12.3.1.3.9.211.3.1.3.9.2 Q4 Modulation
4 interleaver output symbols shall be grouped to form Q4 modulation symbols (QPSK
5 modulated and 4-ary Walsh covered). Each group of two adjacent block interleaver output
6 symbols, x(2k) and x(2k + 1), k = 0,…, M – 1 shall be mapped into a complex modulation
7 symbol (mI(k), mQ(k)) as specified in Table 11.3.1.3.9.2-1.
8 Table 11.3.1.3.9.2-1. Q4 Modulation Table

x(2k + 1) x(2k) mI(k) mQ(k)
0 0 +D +D –D –D +D +D –D –D
0 1 –D –D +D +D +D +D –D –D
1 0 +D +D –D –D –D –D +D +D
1 1 –D –D +D +D –D –D +D +D
Note: D = 1 2.
9 12.3.1.3.9.311.3.1.3.9.3 Q2 Modulation
10 For physical layer packet sizes of 3,072 or 4,096 bits, groups of four successive channel
12 modulated and 2-ary Walsh covered). Each group of four adjacent block interleaver output
13 symbols, x(4k), x(4k + 1), x(4k + 2), x(4k + 3), k = 0,…, M – 1 shall be mapped into a
14 complex modulation symbol (mI(k), mQ(k)) as specified in Table 11.3.1.3.9.3-1.
11-52

x(4k+3) x(4k+2) x(4k+1) x(4k) mI(k) mQ(k)
0 0 0 0 +D –D +D –D +D –D +D –D
0 0 0 1 –D +D +D –D +D –D +D –D
0 0 1 0 +D –D +D –D –D +D +D –D
0 0 1 1 –D +D +D –D –D +D +D –D
0 1 0 0 +D –D –D +D +D –D +D –D
0 1 0 1 –D +D –D +D +D –D +D –D
0 1 1 0 +D –D –D +D −D +D +D –D
0 1 1 1 –D +D –D +D −D +D +D –D
1 0 0 0 +D –D +D –D +D –D –D +D
1 0 0 1 –D +D +D –D +D –D –D +D
1 0 1 0 +D –D +D –D –D +D –D +D
1 0 1 1 −D +D +D –D –D +D –D +D
1 1 0 0 +D –D –D +D +D –D –D +D
1 1 0 1 –D +D –D +D +D –D –D +D
1 1 1 0 +D –D –D +D –D +D –D +D
1 1 1 1 –D +D –D +D –D +D –D +D
Note: D = 1 2.
2 12.3.1.3.9.411.3.1.3.9.4 Q4Q2 Modulation

3 For physical layer packet sizes of 6,144 or 8,192 bits, groups of six successive channel
4 interleaver output symbols shall be grouped to form Q4Q2 modulation symbols which are
5 the sum of Q4 modulation symbols scaled by 1 / 3 and the Q2 modulation symbols scaled
6 by 2 / 3 (see Figure 11.3.1.3.1-4). Of each group of six adjacent block interleaver output
7 symbols, x(6k), x(6k + 1), x(6k + 2), x(6k + 3), x(6k + 4) and x(6k + 5) for k = 0,…, M – 1, the
8 output symbols, x(6k) and x(6k + 1) are grouped to form Q4 modulation symbols, as shown
9 in Table 12.3.1.3.9.2-1and the output symbols x(6k + 2), x(6k + 3), x(6k + 4) and x(6k + 5)
10 are grouped to form Q2 modulation symbols as shown in Table 12.3.1.3.9.3-1. The symbols
11 formed due to Q4 and Q2 modulation are then scaled and summed according to Figure
12 11.3.1.3.1-4 to form Q4Q2 modulated symbols.
13 12.3.1.3.9.511.3.1.3.9.5 E4E2 Modulation

14 For physical layer packet size of 12,288 bits, groups of nine successive channel interleaver
15 output symbols shall be grouped to form E4E2 modulation symbols which are the sum of
16 E4 modulation symbols scaled by 1 / 3 and the E2 modulation symbols scaled by
11-53
1 2 / 3 (see Figure 11.3.1.3.1-5). Of each group of nine adjacent block interleaver output
2 symbols, x(9k), x(9k+1), x(9k+2), x(9k+3), x(9k+4), x(9k+5), x(9k+6), x(9k+7), x(9k+8), for k
3 = 0,…, M – 1, the output symbols, x(9k), x(9k+1) and x(9k+2) are grouped to form E4
4 modulation symbols, as shown in Table 11.3.1.3.9.5-1 and the output symbols x(9k+3),
5 x(9k+4), x(9k+5), x(9k+6), x(9k+7), and x(9k+8) are grouped to form E2 modulation symbols
6 as shown in Table 11.3.1.3.9.5-2. The symbols formed due to E4 and E2 modulation are
7 then scaled and summed according to Figure 11.3.1.3.1-5 form E4E2 modulated symbols.
8 Table 11.3.1.3.9.5-1. E4 Modulation Table

x(9k + 2) x(9k + 1) x(9k) mI(k) mQ(k)
0 0 0 +C +C –C –C +S +S –S –S
0 0 1 +S +S –S –S +C +C –C –C
0 1 1 –S –S +S +S +C +C –C –C
0 1 0 –C –C +C +C +S +S –S –S
1 1 0 –C –C +C +C –S –S +S +S
1 1 1 –S –S +S +S –C –C +C +C
1 0 1 +S +S –S –S –C –C +C +C
1 0 0 +C +C –C –C –S –S +S +S
11-54

x(9k+8) x(9k+7) x(9k+6) x(9k+5) x(9k+4) x(9k+3) mI(k) mQ(k)
0 0 0 0 0 0 +C –C +C –C +S –S +S –S
0 0 0 0 0 1 +S –S +C –C +C –C +S –S
0 0 0 0 1 0 –C +C +C –C +S –S +S –S
0 0 0 0 1 1 –S +S +C -C +C –C +S –S
0 0 0 1 0 0 +C –C +C –C –S +S +S –S
0 0 0 1 0 1 +S –S +C –C –C +C +S –S
0 0 0 1 1 0 –C +C +C –C –S +S +S –S
0 0 0 1 1 1 –S +S +C –C –C +C +S –S
0 0 1 0 0 0 +C –C +S –S +S –S +C –C
0 0 1 0 0 1 +S –S +S –S +C –C +C –C
0 0 1 0 1 0 –C +C +S –S +S –S +C –C
0 0 1 0 1 1 –S +S +S –S +C –C +C –C
0 0 1 1 0 0 +C –C +S –S –S +S +C –C
0 0 1 1 0 1 +S –S +S –S –C +C +C –C
0 0 1 1 1 0 –C +C +S –S –S +S +C –C
0 0 1 1 1 1 –S +S +S –S –C +C +C –C
0 1 0 0 0 0 +C –C –C +C +S –S +S –S
0 1 0 0 0 1 +S –S –C +C +C –C +S –S
0 1 0 0 1 0 –C +C –C +C +S –S +S –S
0 1 0 0 1 1 –S +S –C +C +C –C +S –S
0 1 0 1 0 0 +C –C –C +C –S +S +S –S
0 1 0 1 0 1 +S –S –C +C –C +C +S –S
0 1 0 1 1 0 –C +C –C +C –S +S +S –S
0 1 0 1 1 1 –S +S –C +C –C +C +S –S
0 1 1 0 0 0 +C –C –S +S +S –S +C –C
0 1 1 0 0 1 +S –S –S +S +C –C +C –C
0 1 1 0 1 0 –C +C –S +S +S –S +C –C
0 1 1 0 1 1 –S +S –S +S +C –C +C –C
0 1 1 1 0 0 +C –C –S +S –S +S +C –C
0 1 1 1 0 1 +S –S –S +S –C +C +C –C
0 1 1 1 1 0 –C +C –S +S –S +S +C –C
11-55

0 1 1 1 1 1 –S +S –S +S –C +C +C –C
1 0 0 0 0 0 +C –C +C –C +S –S –S +S
1 0 0 0 0 1 +S –S +C –C +C –C –S +S
1 0 0 0 1 0 –C +C +C –C +S –S –S +S
1 0 0 0 1 1 –S +S +C –C +C –C –S +S
1 0 0 1 0 0 +C –C +C –C –S +S –S +S
1 0 0 1 0 1 +S –S +C –C –C +C –S +S
1 0 0 1 1 0 –C +C +C –C –S +S –S +S
1 0 0 1 1 1 –S +S +C –C –C +C –S +S
1 0 1 0 0 0 +C –C +S –S +S –S –C +C
1 0 1 0 0 1 +S –S +S –S +C –C –C +C
1 0 1 0 1 0 –C +C +S –S +S –S –C +C
1 0 1 0 1 1 –S +S +S –S +C –C –C +C
1 0 1 1 0 0 +C –C +S –S –S +S –C +C
1 0 1 1 0 1 +S –S +S –S –C +C –C +C
1 0 1 1 1 0 –C +C +S –S –S +S –C +C
1 0 1 1 1 1 –S +S +S –S –C +C –C +C
1 1 0 0 0 0 +C –C –C +C +S –S –S +S
1 1 0 0 0 1 +S –S –C +C +C –C –S +S
1 1 0 0 1 0 –C +C –C +C +S –S –S +S
1 1 0 0 1 1 –S +S –C +C +C –C –S +S
1 1 0 1 0 0 +C –C –C +C –S +S –S +S
1 1 0 1 0 1 +S –S –C +C –C +C –S +S
1 1 0 1 1 0 –C +C –C +C –S +S –S +S
1 1 0 1 1 1 –S +S –C +C –C +C –S +S
1 1 1 0 0 0 +C –C –S +S +S –S –C +C
1 1 1 0 0 1 +S –S –S +S +C –C –C +C
1 1 1 0 1 0 –C +C –S +S +S –S –C +C
1 1 1 0 1 1 –S +S –S +S +C –C –C +C
1 1 1 1 0 0 +C –C –S +S –S +S –C +C
1 1 1 1 0 1 +S –S –S +S –C +C –C +C
1 1 1 1 1 0 –C +C –S +S –S +S –C +C
11-56

1 1 1 1 1 1 –S +S –S +S –C +C –C +C
1 12.3.1.3.1011.3.1.3.10 Sequence Repetition for Access Channel Physical Layer Packets

2 The sequence of interleaved code symbols shall be repeated before being modulated. The
3 number of repeats shall be as specified in Table 11.3.1.3.1.1-1. The repetition shall be
4 functionally equivalent to sequentially reading out all the symbols from the interleaver
5 memory as many times as necessary to achieve the fixed 307.2-ksps modulation symbol
6 rate.
7 12.3.1.3.1111.3.1.3.11 Sequence Repetition and Symbol Selection for Reverse Traffic

8 Channel Physical Layer Packets
10 number of repeats varies for each pair of (payload size, number of sub-frames) and shall be
11 as specified in Table 11.3.1.3.1.1-2. The repetition shall be functionally equivalent to
13 necessary to achieve the target modulation symbol rate, which varies for each payload size.
14 Assume the total number of coded symbols is N, and the number of code symbols in each
15 sub-frame is M, the jth code symbol in ith sub-frame is the kth code symbol output of the
16 channel interleaver, where k = (j + i × M) mod N, i = 0, 1, 2, 3, j = 0, 1, …, M-1. Note the 0th
17 code symbol is the first code symbol output of the channel interleaver.

19 Following the orthogonal spreading and scaling, the Pilot, RRI, DSC, DRC, ACK, Data, and
20 Auxiliary Pilot Channel sequences are combined to form resultant I-Channel and Q-
21 Channel sequences, and these sequences are quadrature spread as shown in Figure
22 11.3.1.3.1-1 and Figure 11.3.1.3.1-6. The quadrature spreading shall occur at the chip
23 rate of 1.2288 Mcps, and it shall be used for the Reverse Traffic Channel and the Access
24 Channel. The Pilot, DSC or ACK(if transmitted), RRI, Data(if transmitted), and Auxiliary
25 Pilot Channel (if transmitted) sequences shall be added to form the resultant I-Channel
26 sequence, and the DRC and Data Channel sequences shall be added to form the resultant
27 Q-Channel sequence. The quadrature spreading operation shall be equivalent to a complex
28 multiply operation of the resultant I-Channel and resultant Q-Channel sequences by the
29 PNI and PNQ PN sequences, as shown in Figure 11.3.1.3.1-1 and Figure 11.3.1.3.1-6.
11-57
2 procedure:

16 PI(x) = x15 + x13 + x9 + x8 + x7 + x5 + 1

18 and
19 PQ(x) = x15 + x12 + x11 + x10 + x6 + x5 + x4 + x3 + 1

23 I(n) = I(n – 15) ⊕ I(n – 10) ⊕ I(n – 8) ⊕ I(n – 7) ⊕ I(n – 6) ⊕ I(n – 2)
25 and
26 Q(n) = Q(n – 15) ⊕ Q(n – 12) ⊕ Q(n – 11) ⊕ Q(n – 10) ⊕ Q(n – 9) ⊕
27 Q(n – 5) ⊕ Q(n – 4) ⊕ Q(n – 3)
33 outputs instead 14. The initial state of the access terminal common short-code PN
11-58
5 chip on every even-second mark as referenced to the transmit time reference (see 12.3.3) is
6 the ‘1’ after the 15 consecutive ‘0’s (see Figure 1.14-1).
7 12.3.1.3.12.211.3.1.3.12.2 Long Codes

12 p(x) = x42 + x35 + x33 + x31 + x27 + x26 + x25 + x22 + x21 + x19 +
13 x18 + x17 + x16 + x10 + x7 + x6 + x5 + x3 + x2 + x + 1.
11-59
MI41
x 42
42
MI40
x 41
41
x 40
40
x 39
Modulo-2
UI
Addition
39
x8
8 MI1
MI0
x7
x6
6
MQ41
x5
MQ40
x4
Modulo-2
x3 UQ
Addition
x2
MQ1
2
MQ0
x
2 Figure 11.3.1.3.12.2-1. Long-Code Generators
11-60

3 inputs of the I and Q baseband filters as shown in Figure 11.3.1.3.1-1 and Figure
4 11.3.1.3.1-6. The baseband filters shall have a frequency response S(f) that satisfies the
5 limits given in Figure 11.3.1.3.12.3-1. Specifically, the normalized frequency response of
6 the filter shall be contained within ±δ1 in the passband 0 ≤ f ≤ fp and shall be less than or
7 equal to –δ2 in the stopband f ≥ fs. The numerical values for the parameters are δ1 = 1.5
8 dB, δ2 = 40 dB, fp = 590 kHz, and fs = 740 kHz.
20 log10 S(f )
δ1
δ1
δ2
f
0 fp fs
9
∞
k =0
[αs(kTs – τ) – h(k)]2 ≤ 0.03,
11-61
k h(k)
0, 47 –0.025288315
1, 46 –0.034167931
2, 45 –0.035752323
3, 44 –0.016733702
4, 43 0.021602514
5, 42 0.064938487
6, 41 0.091002137
7, 40 0.081894974
8, 39 0.037071157
9, 38 –0.021998074
10, 37 –0.060716277
11, 36 –0.051178658
12, 35 0.007874526
13, 34 0.084368728
14, 33 0.126869306
15, 32 0.094528345
16, 31 –0.012839661
17, 30 –0.143477028
18, 29 –0.211829088
19, 28 –0.140513128
20, 27 0.094601918
21, 26 0.441387140
22, 25 0.785875640
23, 24 1.0
2
3 12.3.211.3.2 Receiver

5 Once the connection is established, the access network transmits ‘0’ (up) or ‘1’ (down) RPC
6 bits to the access terminal, based on measurements of the reverse link signal quality. If the
7 received quality is above the target threshold, a ‘1’ bit is transmitted. If the received quality
8 is below the target threshold, a ‘0’ bit is transmitted.
11-62
1 The access terminal shall receive RPC commands in slots T as specified by the following
2 equation:
5 The access terminal shall ignore the RPC command during all other slots.
6 If the access terminal did not transmit on the Reverse Traffic Channel in slot n, then it
7 shall ignore the received RPC bit in slot n + 1. Otherwise, the access terminal shall adjust
8 its output power by a discrete amount in the direction indicated by the RPC bit after the
9 RPC bit is received as specified in 11.3.1.2.4 and 11.3.1.2.5.2. The RPC bit is considered
10 received after the 64-chip MAC burst following the second pilot burst of a slot which
11 contains an RPC bit as shown in Figure 11.4.1.3.1-2.
13 different sectors are transmitting the same RPC bit. In each slot containing power-control
14 bits, the access terminal should provide diversity combining of the identical RPC Channels
15 and shall obtain at most one power-control bit from each set of identical RPC Channels.
16 The access terminal shall increase its output power if all the resulting RPC bits are ‘0’
17 (“up”). If any resulting RPC bit is ‘1’ (“down”), the access terminal shall decrease its output
18 power as specified in 11.3.1.2.4.2.

20 Once the connection is established, the access network continuously transmits ‘0’ or ‘1’
21 DRCLock bits to the access terminal on the DRCLock Channel. The access terminal shall
22 process the DRCLock bits received on the DRCLock Channel as specified by the Forward
25 different sectors are transmitting the same DRCLock bit. In each slot containing a
26 DRCLock bit, the access terminal should provide diversity combining of the identical
27 DRCLock Channels and shall obtain at most one DRCLock bit from each set of identical
28 DRCLock Channels.

30 The access network transmits the Reverse Activity Channel every slot. Once the connection
31 is established, the access terminal shall process the RA bit for each sector in its active set
32 along with the RAChannelGain public data of the Reverse Traffic Channel MAC protocol, to
33 generate the log-likelihood ratio LLRrab. The access terminal shall map the log-likelihood
34 ratio (LLR) of the RA bit demodulation, LLRrab from a range of [−∞, +∞] to a range of [−1, +1]
35 to generate SoftRAB for each sector in its active set using the following function:
36 SoftRAB = 0.4 × LLRrab, −2.5 ≤ LLRrab ≤ 2.5
38 SoftRAB = −1, LLRrab < −2.5
11-63
1 where -1 ≤ SoftRAB ≤ 1 and SoftRAB is a real-valued input for the Reverse Traffic Channel
2 MAC Protocol.
3 12.3.2.411.3.2.4 Reception of ARQ Channel

4 Each sector of an access network transmits a positive acknowledgment (ACK) or a negative
5 acknowledgment (NAK) in response to a physical layer packet using the ARQ Channel. The
6 H-ARQ (Hybrid-ARQ), L-ARQ (Last-ARQ), and P-ARQ (Packet-ARQ) bits are transmitted on
7 the ARQ Channel.
8 An H-ARQ bit is transmitted on the ARQ Channel by a sector in the access terminal’s active
9 set following the reception of all subpackets up to sub-packet (MaxNumSubPacketsI–1) of
10 a physical layer packet transmitted on interlace offset I, where MaxNumSubPacketsI is
11 public data of the Reverse Traffic Channel MAC Protocol. The H-ARQ bit transmitted by a
12 sector in slots m, m+1, and m+2 indicates to the access terminal whether or not the
13 physical layer packet transmitted in slots m−8, m−7, m−6, and m−5 was successfully
14 received by the cell containing that sector. The sector transmits the H-ARQ bit based on
15 ARQMode if the sector is part of the serving cell, where ARQMode is public data of the
16 Reverse Traffic Channel MAC Protocol. The ARQMode is a 1-bit value that indicates the
17 modulation (Bi-Polar (+1 implies ACK and −1 implies NAK) Keying or ACK-oriented ON-OFF
18 (+1 implies ACK and 0 implies NAK) Keying) of the H-ARQ bit. ARQMode 0 implies that the
19 H-ARQ bit transmitted by a sector that is part of the serving cell uses Bi-Polar Keying and
20 ARQMode 1 implies that the H-ARQ bit transmitted by a sector that is part of the serving
21 cell uses ACK-oriented ON-OFF Keying. A sector transmits the H-ARQ bit using ACK-
22 oriented ON-OFF Keying if the sector is not part of the serving cell.
23 The SofterHandoff public data of the RouteUpdateProtocolRoute Update Protocol indicates
24 whether or not two different sectors are transmitting the same ARQ bit. In each slot
25 containing an ARQ bit, the access terminal should provide diversity combining of the
26 identical ARQ channels and shall obtain at most one ARQ bit from each set of the identical
27 ARQ channels.
28 The H-ARQ transmission rules are summarized in Table 11.3.2.4-1.
29 Table 11.3.2.4-1. H-ARQ Transmission Rules
Sector of
Serving ARQMode Modulation
Cell
Bi-Polar Keying
YES 0
(+1 ⇒ ACK, −1 ⇒ NAK)
ACK-oriented On-Off Keying
YES 1
(+1 ⇒ ACK, 0 ⇒ NAK)
NO N/A
(+1 ⇒ ACK, 0 ⇒ NAK)
30
11-64
1 The L-ARQ bit transmitted by a sector in the access terminal’s active set following the
2 reception of the (MaxNumSubPacketsI+1)th sub-packet of a physical layer packet
3 transmission on interlace offset I in slots m, m+1, and m+2 indicates to the access terminal
4 whether or not the physical layer packet transmitted in slots m−8, m−7, m−6, and m−5 was
5 successfully received by the cell containing that sector, where MaxNumSubPacketsI is
6 public data of the Reverse Traffic Channel MAC Protocol. The sector transmits the L-ARQ
7 bit using NAK-oriented ON-OFF Keying (0 implies ACK, −1 implies NAK) in slots m, m+1,
8 and m+2 following the reception of the (MaxNumSubPacketsI+1)th sub-packet of a physical
9 layer packet transmitted in slots m−8, m−7, m−6, and m−5 on interlace offset I.
10 The P-ARQ bit transmitted by a sector in the access terminal’s active set in slots m, m+1,
11 and m+2 indicates to the access terminal whether or not the physical layer packet that was
12 transmitted starting in slot m−(MaxNumSubPacketsI +1)×12 was successfully received by
13 the cell containing that sector if transmitted in interlace offset I. The access network
14 transmits the P-ARQ bit using NAK-oriented ON-OFF Keying in slots m, m+1, and m+2 in
15 response to a physical layer packet that was transmitted starting in slot m−48.
16 Figure 11.3.2.4-1 shows the ARQ mechanism for a Reverse Traffic Channel physical layer
17 packet transmitted over all four sub-packets, with MaxNumSubPacketsI for that interlace
18 offset equal to three. In this case, the access network transmits NAK responses on the ARQ
19 Channel using the H-ARQ bit after the first three sub-packets of the physical layer packet
20 are transmitted by the access terminal indicating that it was unable to successfully receive
21 the Reverse Traffic Channel packet after the first, second, and third sub-packets. After the
22 fourth sub-packet the sector transmits an ACK using the L-ARQ bit and the P-ARQ bit
23 indicating that the sector successfully received the Reverse Traffic Channel physical layer
24 packet.
25 The access terminal shall stop transmission of a packet on the Reverse Traffic Channel if it
26 receives a positive acknowledgement for that packet from any sector in its active set.
27 The access terminal shall stop transmission of a packet on the Reverse Traffic Channel if
28 the transmitted packet’s sub-packet index is greater than MaxNumSubPacketsI when
29 transmitting on interlace-offset I.
30 If the access terminal has not received a positive acknowledgment152
31 (MaxNumSubPacketsI+1)× 12 + 2 slots after the start of a physical layer packet
32 transmission on the Reverse Traffic Channel for transmissions on interlace offset I, then
33 this protocol shall return a ReverseTrafficPacketsMissed indication along with parameters
34 that uniquely identify the lost MAC, Security, Connection, Session, Stream, and
35 Application Layer packets.
37 packet transmitted over two sub-packets on interlace-offset I with MaxNumSubPacketsI
38 equal to three. In this example, the access network transmits an ACK response on the ARQ
152 Unless the access terminal has received a NAK on the L-ARQ or P-ARQ channels, the access
terminal does not indicate it has received a positive acknowledgement from a non-serving cell if the
DRCLock bit from that cell for the reverse CDMA channel is out of lock.
11-65
1 Channel using the H-ARQ bit after the second sub-packet is transmitted by the access
2 terminal indicating that it has successfully received the physical layer packet. Following
3 reception of a positive acknowledgment on the ARQ Channel, the access terminal shall not
4 transmit the remaining sub-packets of the physical layer packet. The access terminal may
5 begin transmission of a new physical layer packet on that interlace. The access network
6 transmits an ACK on the ARQ Channel using the P-ARQ bit in sub-frame n+12.
7 Figure 11.3.2.4-3 shows failure to terminate a Reverse Traffic Channel physical layer
8 packet transmitted over all four sub-packets on interlace-offset I with MaxNumSubPacketsI
9 equal to three. In this case, the access network transmits NAK responses on the ARQ
11 are transmitted by the access terminal indicating that it was unable to correctly receive the
12 Reverse Traffic Channel packet after the first, second and third sub-packets. After the
13 fourth sub-packet the access network transmits a NAK on the ARQ Channel using both the
14 L-ARQ bit and the P-ARQ bit indicating that it was unable to successfully receive the
15 packet.
P-ARQ bit on
ARQ Channel
ACK
1 Sub-frame
L-ARQ bit on
ARQ Channel
1 Sub-frame ACK
3 Slots
H-ARQ bit on
ARQ Channel
NAK NAK NAK

First Sub-packet
for the Next
Physical Layer
Packet
Transmission
Transmit Transmit Transmit Transmit Transmit

Reverse Traffic Sub-packet Sub-packet Sub-packet Sub-packet Sub-packet
Channel Physical 1 2 3 4 1
Layer Packet
Transmissions
Sub-frames n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n + 9 n + 10 n + 11 n + 12

16
18 Transmit Duration
11-66

3 Termination
11-67
2 Figure 11.3.2.4-3. Reverse Traffic Channel Packet Transmission Failure
3 12.3.311.3.3 Synchronization and Timing

21 second.
11-68
2 Reverse Traffic Channel and the Access Channel.
11-69



9 The average frequency difference between the actual sector transmit carrier frequency and
10 the specified sector transmit frequency assignment shall be less than ±5 × 10-8 of the
11 frequency assignment (±0.05 ppm).


16 The Forward Channel shall have the overall structure shown in Figure 11.4.1.3.1-1. The
17 Forward Channel shall consist of the following time-multiplexed channels: the Pilot
18 Channel, the Forward Medium Access Control (MAC) Channel, and the Forward Traffic
19 Channel or the Control Channel. The Traffic Channel carries user physical layer packets.
20 The Control Channel carries control messages, and it may also carry user traffic. Each
21 channel is further decomposed into code-division-multiplexed quadrature Walsh channels.
22 The forward link shall consist of slots of length 2048 chips (1.66… ms). Groups of 16 slots
23 shall be aligned to the PN rolls of the zero-offset PN sequences and shall align to CDMA
24 System Time on even-second ticks.
25 Within each slot, the Pilot, MAC, and Traffic or Control Channels shall be time-division
26 multiplexed as shown in Figure 11.4.1.3.1-2 and shall be transmitted at the same power
27 level.
28 The Pilot Channel shall consist of all-‘0’ symbols transmitted on the I-branch with Walsh
29 cover 0. Each slot shall be divided into two half slots, each of which contains a pilot burst.
30 Each pilot burst shall have a duration of 96 chips and be centered at the midpoint of the
31 half slot.153
11-70
1 The MAC Channel shall consist of four subchannels: the Reverse Power Control (RPC)
2 Channel, the DRCLock Channel, the Reverse Activity (RA) Channel and the ARQ Channel.
3 The RPC Channel transmits power control commands used by the access terminal for
4 closed loop power control. The DRCLock Channel transmits a reverse link quality
5 indication used by the access terminal for forward link serving sector selection. The RA
6 Channel transmits a reverse link activity bit (RAB) stream. The ARQ Channel transmits an
7 access terminal specific indication of whether or not Reverse Traffic Channel packets from
8 that access terminal were received successfully by the access network. Each MAC Channel
9 symbol shall be BPSK or OOK modulated on the in-phase or quadrature-phase of one of
10 128 128-ary Walsh codewords (covers). The MAC symbol Walsh covers shall be transmitted
11 two times per slot in four bursts of 64 chips each. A burst shall be transmitted immediately
12 preceding each of the pilot bursts in a slot, and a burst shall be transmitted immediately
13 following each of the pilot bursts in a slot. The Walsh channel gains may vary the relative
14 power.
16 layer packets for an access terminal shall be transmitted at a data rate that varies from 4.8
17 kbps to 3.072 Mbps.154 Forward Traffic Channel and Control Channel physical layer
18 packets are defined using a Transmission Format. The Transmission Format consists of the
19 following:
20 • Physical Layer Packet Size of the physical layer packet (in bits)
21 • Nominal Transmit Duration of the physical layer packet (in slots)
22 • Preamble Length associated with the physical layer packet (in chips)
23 The Transmission Format is public data of the Forward Traffic Channel MAC Protocol. For
24 example, (1024, 1, 64) indicates a 1024-bit physical layer packet with a nominal transmit
25 duration of 1 slot with a 64-chip preamble.
29 PSK/16-QAM modulator. The modulated symbol sequences shall be repeated and
32 stream with a rate of 76.8ksps is covered with a distinct Walsh function of length 16. The
36 form the resultant sequence of chips for the quadrature spreading operation. Forward
37 Traffic Channel and Control Channel physical layer packets can be transmitted in 1 to 16
11-71
1 slots (see Table 11.4.1.3.1.1-1). When more than one slot is allocated, the transmit slots
2 shall use 4-slot interlacing. That is, the transmit slots of a physical layer packet shall be
3 separated by three intervening slots, and slots of other physical layer packets shall be
4 transmitted in the slots between those transmit slots.
5 Figure 11.3.1.3.1-7 and Figure 11.3.1.3.1-8 illustrate the multislot interlacing approach for
6 a 153.6 kbps Forward Traffic Channel packet with Transmission Format (1024, 4, 256)
7 with DRCLength of one slot. The 153.6 kbps Forward Traffic Channel physical layer packet
8 with Transmission Format (1024, 4, 256) uses four slots, and these slots are transmitted
9 with a three-slot interval between them, as shown in the figures. The slots from other
10 physical layer packets are interlaced in the three intervening slots. Figure 11.3.1.3.1-7
11 shows the case of a normal physical layer packet termination. In this case, the access
23 received a positive ACK response, the physical layer shall return a ForwardTrafficCompleted
24 indication.
25 The Control Channel shall be transmitted using the Transmission Formats of (128, 4,
26 1024), (256, 4, 1024), (512, 4, 1024), (1024, 16, 1024), and (1024, 8, 512). The modulation
27 characteristics for the Control Channel shall be the same as those of the Forward Traffic
28 Channel transmitted using the corresponding Transmission Format.
11-72
Forward Traffic I
QPSK/ C
Channel or Encoder
Channel 8-PSK/
Control Channel R = 1/3
Modulator D
Packets
I I I I I I
C Sequence Walsh
Symbol 16-ary Walsh
Repetition/ Channel
D Puncturing 1/4
64-Symbol Bi-
Orthogonal Cover
with MACIndex i
Signal Point
Preamble Mapping Sequence I
(All 0's) 0 +1 Repetition
1 –1
Q
0
64 to 1,024
128-ary Walsh Cover RPC bits: PN Chips
for MACIndex i I Channel for Even MACIndex, per Physical
Signal Point Q Channel for Odd MACIndex Layer Packet
MAC Channel RPC bits for Mapping RPC Channel H-ARQ or L-ARQ bits: for Preamble
MACIndex i, 150 bps 0 +1 Gain: G-rpc(i) I Channel for Even MACIndex,
(T-FrameOffset) mod 4 = 3 1 –1 Q Channel for Odd MACIndex
TDM
MAC Channel H-ARQ bits or 1:3
L-ARQ bits for MACIndex i ARQ Signal I Walsh
ARQ Channel
(T-FrameOffset) mod 4 ≠ 3 Point Channels
Gain: G-arq(i)
Mapping
A
128-ary Walsh Cover for DRC Lock bits:
TDM
MACIndex i Q Channel for Even MACIndex,
I Channel for Odd MACIndex B
MAC Channel P-ARQ bits for Signal Point P-ARQ bits:
MACIndex i Mapping ARQ Channel Q Channel for Even MACIndex, Q Walsh
(T-FrameOffset) mod 4 ≠ 3 0 0 Gain: G-arq(i) I Channel for Odd MACIndex Channels
1 -1
TDM
MAC Channel DRCLock 3:1
symbols for MACIndex i Bit Repetition Signal Point DRCLock
(600/DRCLockLength) (Factor = Mapping Channel
DRCLockLength/ 0 +1 Gain: I I
bits per second
(T-FrameOffset) mod 4 = 3 4) 1 –1 G-drclock(i) Walsh Sequence
Chip Level Repetition
Walsh Cover W2128 Summer Q (Factor = 2) Q

RA 256 PN
RA Bits Mapping
Channel Chips
1 Bit per Slot 0 +1
Gain per Slot
(600 bps) 1 –1
for MAC
Walsh Cover 0
Signal Point
(All 0’s) 0 +1
1 –1
Q
0
cos(2 fCt)
192 PN
Chips
per Slot
I I Baseband for Pilot
A
Filter
Quadrature
Spreading Forward
(Complex Multiply) Modulated
I = I PNI – Q PNQ Waveform
Q = I PNQ + Q PNI
Q Q Baseband
B
Filter

PNI PNQ values with the mapping +1 for
I-Channel Q-Channel binary ‘0’ and –1 for binary ‘1’.
1.2288 Mcps 1.2288 Mcps
1
11-73
1/2 Slot 1/2 Slot

400 64 96 64 400 400 64 96 64 400
Active Slot

64 96 64 64 96 64
Idle Slot
1

4 The modulation parameters for the Forward Traffic Channel and the Control Channel shall
5 be as shown in Table 11.4.1.3.1.1-1. The Control Channel shall only use the Transmission
6 Formats of (1024, 8, 512), (1024, 16, 1024), (128, 4, 1024), (256, 4, 1024), or (512, 4,
7 1024).
11-74
2 Control Channel
Transmission Format
(Physical Layer Packet Size(bits), Nominal Code Modulation Nominal Data Rate
Transmit Duration (slots), Preamble Rate Type (kbps)
Length (chips))
(128, 16, 1024) 1/5 QPSK 4.8

(128, 8, 512) 1/5 QPSK 9.6
(128, 4, 1024) 1/5 QPSK 19.2
(128, 4, 256) 1/5 QPSK 19.2
(128, 2, 128) 1/5 QPSK 38.4
(128, 1, 64) 1/5 QPSK 76.8
(256, 16, 1024) 1/5 QPSK 9.6
(256, 8, 512) 1/5 QPSK 19.2
(256, 4, 1024) 1/5 QPSK 38.4
(256, 4, 256) 1/5 QPSK 38.4
(256, 2, 128) 1/5 QPSK 76.8
(256, 1, 64) 1/5 QPSK 153.6
(512, 16, 1024) 1/5 QPSK 19.2
(512, 8, 512) 1/5 QPSK 38.4
(512, 4, 1024) 1/5 QPSK 76.8
(512, 4, 256) 1/5 QPSK 76.8
(512, 4, 128) 1/5 QPSK 76.8
(512, 2, 128) 1/5 QPSK 153.6
(512, 2, 64) 1/5 QPSK 153.6
(512, 1, 64) 1/5 QPSK 307.2
(1024, 16, 1024) 1/5 QPSK 38.4
(1024, 8, 512) 1/5 QPSK 76.8
(1024, 4, 256) 1/5 QPSK 153.6
(1024, 4, 128) 1/5 QPSK 153.6
(1024, 2, 128) 1/5 QPSK 307.2
(1024, 2, 64) 1/5 QPSK 307.2
(1024, 1, 64) 1/3 QPSK 614.4
(2048, 4, 128) 1/3 QPSK 307.2
(2048, 2, 64) 1/3 QPSK 614.4
11-75
Transmission Format
Length (chips))
(2048, 1, 64) 1/3 QPSK 1,228.8

(3072, 2, 64) 1/3 8-PSK 921.6
(3072, 1, 64) 1/3 8-PSK 1,843.2
(4096, 2, 64) 1/3 16-QAM 1,228.8
(4096, 1, 64) 1/3 16-QAM 2,457.6
(5120, 2, 64) 1/3 16-QAM 1,536.0
(5120, 1, 64) 1/3 16-QAM 3,072.0
2 2.

Rate(bps) 150 150/(DRCLockLength) 600
Bit Repetition
1 DRCLockLength 1
Factor
Modulation BPSK(I or Q)
BPSK(I or Q) BPSK(I)
(Channel)
Modulation 300
Symbol Rate 300 1,200
(sps)
Walsh Cover
128 128 128
Length
Walsh Sequence
Repetition 2 2 2
Factor
PN Chips/Slot 256 256 256
PN Chips/Bit 256 256 × DRCLockLength 256
4 12.4.1.3.1.211.4.1.3.1.2 Data Rates

5 The Forward Traffic Channel shall support variable-data-rate transmission from 4.8 kbps
6 to 3.072 Mbps corresponding to the Transmission Formats of (128, 16, 1024) and (5120, 1,
7 64) respectively, as shown in Table 11.4.1.3.1.1-1
8 The data rate of the Control Channel shall be 76.8 kbps (Transmission Format of (512, 4,
9 1024) or (1024, 8, 512)), 38.4 kbps (Transmission Format of (256, 4, 1024) or (1024, 16,
10 1024)), or 19.2 kbps (Transmission Format of (128, 4, 1024)).
11-76
2 12.4.1.3.2.111.4.1.3.2.1 Pilot Channel

3 A Pilot Channel shall be transmitted by the sector on each active Forward Channel as
6 area of the sector. The Pilot Channel shall be transmitted at the full sector power.
7 12.4.1.3.2.1.111.4.1.3.2.1.1 Modulation
8 The Pilot Channel shall consist of all-‘0’ symbols transmitted on the I component only.

10 The Pilot Channel shall be assigned Walsh cover 0.

12 See 12.3.1.3.12.

14 The Forward MAC Channel shall be composed of Walsh channels that are orthogonally
15 covered and BPSK modulated or OOK (ON-OFF Keying) modulated on each phase of the
16 carrier (either in-phase or quadrature phase). Each Walsh channel shall be identified by a
17 MACIndex value that is between 0 and 127 and defines a unique 128-ary Walsh cover and
18 a unique modulation phase. The Walsh functions assigned to the MACIndex values shall be
19 as shown in Table 11.4.1.3.2.2-1.
20 Table 11.4.1.3.2.2-1. Forward Link MAC Channel Assignment
MAC Index, 128-ary (T – FrameOffset) mod 4 = 3 (T – FrameOffset) mod 4 ≠ 3

Walsh
i I-branch Q-branch I-branch Q-branch
Function
6, 8, …, 62 Wi128
/2
RPC DRCLock ARQ ARQ
(H-ARQ bit or (P-ARQ bit)
L-ARQ bit)
5 (if broadcast W(128

i −1) / 2 + 32
DRCLock RPC ARQ ARQ
is not
(P-ARQ bit) (H-ARQ bit or
negotiated), 7,
L-ARQ bit)
9, …, 63
72,74,…,126 Wi128
/ 2 + 32
RPC DRCLock ARQ ARQ
(H-ARQ bit or (P-ARQ bit)
L-ARQ bit)
73,75,….,127 W(128
i −1) / 2 + 64
DRCLock RPC ARQ ARQ
(P-ARQ bit) (H-ARQ bit or
11-77
MAC Index, 128-ary (T – FrameOffset) mod 4 = 3 (T – FrameOffset) mod 4 ≠ 3

Walsh
Function
L-ARQ bit)
4 W2128 RA RA
1
2 RPC Channels with even-numbered MACIndex values shall be assigned to the in-phase (I)
3 modulation phase, while those with odd-numbered MACIndex values shall be assigned to
4 the quadrature (Q) modulation phase. RPC Channels shall be transmitted in slots T
6 (T-FrameOffset) mod 4 = 3,
8 The DRCLock Channel with even-numbered MACIndex values shall be assigned to the
9 quadrature (Q) modulation phase, while those with odd-numbered MACIndex values shall
10 be assigned to the in-phase (I) modulation phase. The DRCLock Channel shall be
11 transmitted in slots T specified by the following equation:
12 (T – FrameOffset) mod 4 = 3,
14 The ARQ Channel shall not be transmitted in slots other than T specified by the following
15 equation:
18 The H-ARQ bit, L-ARQ bit and P-ARQ bits shall be transmitted on the ARQ Channel using
19 rules specified in 0.
20 When the H-ARQ bit is transmitted on the ARQ Channel with even-numbered MACIndex
21 values the H-ARQ bit shall be assigned to the in-phase (I) modulation phase. When the H-
22 ARQ bit is transmitted on the ARQ Channel with odd-numbered MACIndex values the H-
23 ARQ bit shall be assigned to the quadrature (Q) modulation phase.
24 When the L-ARQ bit is transmitted on the ARQ Channel with even-numbered MACIndex
25 values the L-ARQ bit shall be assigned to the in-phase (I) modulation phase. When the L-
26 ARQ bit is transmitted on the ARQ Channel with odd-numbered MACIndex values the L-
27 ARQ bit shall be assigned to the quadrature (Q) modulation phase.
28 When the P-ARQ bit is transmitted on the ARQ Channel with even-numbered MACIndex
29 values the P-ARQ bit shall be assigned to the quadrature (Q) modulation phase. When the
30 P-ARQ bit is transmitted on the ARQ Channel with odd-numbered MACIndex values the P-
31 ARQ bit shall be assigned to the in-phase (I) modulation phase.
32 The MAC symbol Walsh covers shall be transmitted two times per slot in four bursts of
33 length 64 chips each. These bursts shall be transmitted immediately preceding and
34 following the pilot bursts of each slot.
11-78
1 The MAC Channel use versus MACIndex shall be as specified in Table 11.4.1.3.2.2-2.
4 Walsh channels shall be scaled to maintain a constant total transmit power. The Walsh
5 Channel gains can vary as a function of time.
11-79
1 Table 11.4.1.3.2.2-2. MAC Channel and Preamble Use Versus MACIndex
MACIndex MAC Channel Use Preamble Use Preamble Length
0 and 1 Not Used Not Used N/A

Not Used 76.8 kbps Control Channel
2 512
(1024, 8, 512)
3 1024
(1024, 16, 1024)
4 RA Channel Not Used N/A
Available for RPC
Channel, DRCLock Forward Traffic Channel if
5 Channel and ARQ Broadcast is not Variable
Channel negotiated
Transmissions
64 and 65 Not Used Not Used N/A
Not Used Multi-User packet
(128, 4, 256)
66 (256, 4, 256) 256
(512, 4, 256)
(1024, 4, 256)
67 128
(2048, 4, 128)
68 64
(3072, 2, 64)
69 64
(4096, 2, 64)
70 64
(5120, 2, 64)
(128, 4, 1024)
38.4 kbps Control Channel
71 1024
(256, 4, 1024)
(512, 4, 1024)
11-80
Available for RPC

Available for Forward
6–63 and Channel, DRCLock
Traffic Channel
Channel and ARQ Variable
72-127 Transmissions of Single
Channel
User packets
Transmissions
1

3 The Reverse Power Control (RPC) Channel for each access terminal with an open
4 connection shall be assigned to one of the available MAC Channels. It is used for the
5 transmission of the RPC bit stream destined to that access terminal. The RPC Channel and
6 the DRCLock Channel shall be transmitted on the in-phase and quadrature-phase of the
7 same MAC Channel according to the assignment defined in Table 11.4.1.3.2.2-1.The RPC
8 Channel shall be time-division multiplexed with the ARQ Channel and transmitted in 1 slot
9 out of every 4 slots.
10 The RPC data rate shall be 150 bps. The access network shall transmit an RPC bit in every
11 slot T specified using the following equation:

14 Each RPC bit shall be transmitted two times in a slot in four bursts of 64 chips each. One
17 12.4.1.3.2.2.211.4.1.3.2.2.2 DRCLock Channel

18 The DRCLock Channel for each access terminal with an open connection shall be assigned
19 to one of the available MAC Channels. It is used for the transmission of the DRCLock bit
20 stream destined to that access terminal. The RPC Channel and the DRCLock Channel shall
21 be transmitted on the in-phase and quadrature phase of the same MAC Channel according
22 to the assignment defined in Table 11.4.1.3.2.2-1. The DRCLock Channel shall be time-
23 division multiplexed with the ARQ Channel and transmitted in one out of every 4 slots.
24 Each DRCLock bit shall be repeated and transmitted in DRCLockLength slots, where
26 DRCLock data rate shall be 150/(DRCLockLength) bps. The access network shall transmit
27 a DRCLock bit in every slot T with

30 Each DRCLock bit shall be transmitted two times in a slot in bursts of 64 chips each. One
32 shown in Figure 11.4.1.3.1-2. .
33 The value of the DRCLock bit may change only in slot T specified by the following equation:
34 (T − FrameOffset) mod (4 × DRCLockLength) = 3,
11-81

4 the MAC Channel with MACIndex 4. The RA bit shall be transmitted in every slot and the
5 RA Channel data rate shall be 600 bps. The RA bit in each slot shall be further repeated to
6 form two symbols per slot for transmission.
7 12.4.1.3.2.2.411.4.1.3.2.2.4 ARQ Channel

8 Each sector of an access network shall transmit a positive acknowledgment (ACK) or a
9 negative acknowledgment (NAK) in response to a physical layer packet using the ARQ
10 Channel. The H-ARQ, L-ARQ and P-ARQ bits are transmitted on the ARQ Channel.
12 set following the reception of all subpackets up to subpacket MaxNumSubPacketsI-1 of a
13 physical layer packet transmitted on interlace offset I, where MaxNumSubPacketsI is public
14 data of the Reverse Traffic Channel MAC Protocol. The H-ARQ bit transmitted by a sector in
15 slots m, m+1, and m+2 indicates to the access terminal whether or not the physical layer
16 packet transmitted in slots m−8, m−7, m−6, and m−5 was successfully received by the cell
17 containing that sector. A sector transmits H-ARQ bits based on ARQMode if the sector is
18 part of the serving, where ARQMode is public data of the Reverse Traffic Channel MAC
19 Protocol. The ARQMode is a 1-bit value that indicates the modulation of the H-ARQ bit (Bi-
20 Polar(+1 implies ACK and −1 implies NAK) Keying or ACK-oriented ON-OFF(+1 implies ACK
21 and 0 implies NAK) Keying). ARQMode 0 implies that the H-ARQ bit transmitted by a sector
22 that is part of the serving cell uses Bi-Polar Keying and ARQMode 1 implies that the H-ARQ
23 bit is transmitted by a sector that is part of the serving cell uses ACK-oriented ON-OFF
24 Keying. A sector transmits the H-ARQ bit to an access terminal using Bi-Polar Keying or
25 ACK-oriented ON-OFF Keying if the sector is part of the serving cell. A sector transmits the
26 H-ARQ bit using ACK-oriented ON-OFF Keying if it is not part of the serving cell.
27 A sector shall transmit H-ARQ bits based on ARQMode if the sector is part of the serving
28 cell. The sector shall transmit the H-ARQ bit using Bi-Polar Keying or ACK-oriented ON-
29 OFF Keying (+1 implies ACK and 0 implies NAK) in slots m, m+1, and m+2 following
30 reception of all sub-packets up to subpacket MaxNumSubPacketsI-1 of a physical layer
31 packet transmitted on interlace offset I in slots m−8, m−7, m−6, and m−5 if the sector is
32 part of the serving cell. The sector shall transmit the H-ARQ bit using ACK-oriented ON-
33 OFF Keying in slots m, m+1, and m+2 following reception of all sub-packets up to
34 subpacket MaxNumSubPacketsI-1 of a physical layer packet transmitted on interlace offset
35 I in slots m−8, m−7, m−6, and m−5 if the sector is not part of the serving cell.
36 An L-ARQ bit is transmitted on the ARQ Channel by a sector in the access terminal’s active
37 set following the reception of the (MaxNumSubPacketsI+1)th sub-packet of a physical layer
38 packet transmitted on interlace offset I. The L-ARQ bit is transmitted in slots m, m+1, and
39 m+2 to indicate to the access terminal whether or not the physical layer packet transmitted
40 in slots m−8, m−7, m−6, and m−5 was successfully received by the cell containing that
41 sector.
11-82
1 The sector shall transmit the L-ARQ bit on the ARQ Channel using NAK-oriented ON-OFF
2 Keying (0 implies ACK, −1 implies NAK) in slots m, m+1, and m+2 following reception of the
3 (MaxNumSubPacketsI+1)th sub-packet of a physical layer packet transmitted on interlace
4 offset I in slots m−8, m−7, m−6, and m−5.
5 A P-ARQ bit transmitted on the ARQ Channel by a sector in the access terminal’s active set
6 in slots m, m+1, and m+2 indicates to the access terminal whether or not the physical layer
7 packet that was transmitted starting in slot m−(MaxNumSubPacketsI+1)×12 on interlace
8 offset I was successfully received by the cell containing that sector. The access network
9 shall transmit the P-ARQ bit using NAK-oriented ON-OFF Keying in slots m, m+1, and m+2
10 in response to a physical layer packet that was transmitted starting in slot
11 m−(MaxNumSubPacketsI+1)×12 on interlace offset I.
12 When the access network has received all slots of a physical layer packet or has
13 transmitted an ACK response, this protocol shall return a ReverseTrafficCompleted
14 indication.
15 The access network shall not forward the physical layer packet to a higher layer if the
18 packet transmitted over all four sub-packets, where MaxNumSubPacketsI equals to three
19 for that interlace. In this case, the access network transmits NAK responses on the ARQ
20 Channel using the H-ARQ bits after the first three sub-packets of the physical layer packet
25 packet.
27 packet transmitted over two sub-packets, where MaxNumSubPacketsI equals to three for
28 that interlace. In this example, the access network transmits an ACK response on the ARQ
31 reception of a positive acknowledgment on the ARQ Channel, the access terminal does not
32 transmit the remaining slots of the physical layer packet. The access terminal may begin
33 transmission of a new physical layer packet on that interlace. The access network
41 fourth sub-packet the access network transmits an NAK on the ARQ Channel using both
42 the L-ARQ bit and the P-ARQ bit indicating that it was unable to successfully receive the
43 packet.
11-83

6 The preamble shall consist of all-‘0’ symbols transmitted on the in-phase component only.
7 The preamble shall be time multiplexed into the Forward Traffic Channel stream as
8 described in 11.4.1.3.3. The preamble sequence shall be covered by a 64-chip bi-
9 orthogonal sequence and the sequence shall be repeated several times depending on the
10 transmit mode. The bi-orthogonal sequence shall be specified in terms of the 64-ary Walsh
12 Wi/264 for i = 0, 2, …., 126
13 W(i64-1)/2 for i = 1, 3, …., 127

64
14 where i = 0, 1,…, 127 is the MACIndex value and Wi is the bit-by-bit complement of the
15 64-chip Walsh function of order i.
16 The channel type versus MACIndex mapping for the preamble shall be as specified in Table
17 11.4.1.3.2.2-2.
18 The 64-chip preamble repetition factor shall be as specified in Table 11.4.1.3.2.3.1-1.
11-84
Transmission Format 64 chip

(Physical Layer Packet Size(bits), Nominal Preamble
Transmit Duration (slots), Preamble Length Sequence
(chips)) Repetition
(128, 16, 1024) 16

(128, 4, 1024) 16
(128, 8, 512) 8
(128, 4, 256) 4
(128, 2, 128) 2
(128, 1, 64) 1
(256, 16, 1024) 16
(256, 4, 1024) 16
(256, 8, 512) 8
(256, 4, 256) 4
(256, 2, 128) 2
(256, 1, 64) 1
(512, 16, 1024) 16
(512, 4, 1024) 16
(512, 8, 512) 8
(512, 4, 256) 4
(512, 4, 128) 2
(512, 2, 128) 2
(512, 2, 64) 1
(512, 1, 64) 1
(1024, 16, 1024) 16
(1024, 8, 512) 8
(1024, 4, 256) 4
(1024, 4, 128) 2
(1024, 2, 128) 2
(1024, 2, 64) 1
(1024, 1, 64) 1
(2048, 4, 128) 2
(2048, 2, 64) 1
11-85

(Physical Layer Packet Size(bits), Nominal Preamble
Transmit Duration (slots), Preamble Length Sequence
(chips)) Repetition
(2048, 1, 64) 1
(3072, 2, 64) 1
(3072, 1, 64) 1
(4096, 2, 64) 1
(4096, 1, 64) 1
(5120, 2, 64) 1
(5120, 1, 64) 1
1
2 12.4.1.3.2.3.211.4.1.3.2.3.2 Encoding
3 The Forward Traffic Channel physical layer packets and the Control Channel physical layer
4 packets shall be encoded with code rates of R = 1/3 or 1/5. The encoder shall discard the
5 6-bit TAIL field of the physical layer packet inputs and encode the remaining bits with a
6 parallel turbo encoder, as specified in 12.4.1.3.2.3.2.1. The turbo encoder will add an
7 internally generated tail of 6/R output code symbols, so that the total number of output
8 symbols is 1/R times the number of bits in the input physical layer packet.
11
11-86
Transmission Format Turbo Turbo

(Physical Layer Packet Size(bits), Nominal Encoder Code Encoder
Transmit Duration (slots), Preamble Input Rate Output
Length (chips)) Bits Symbols
(128, 16, 1024) 122 1/5 640

(128, 4, 1024) 122 1/5 640
(128, 8, 512) 122 1/5 640
(128, 4, 256) 122 1/5 640
(128, 2, 128) 122 1/5 640
(128, 1, 64) 122 1/5 640
(256, 16, 1024) 250 1/5 1,280
(256, 4, 1024) 250 1/5 1,280
(256, 8, 512) 250 1/5 1,280
(256, 4, 256) 250 1/5 1,280
(256, 2, 128) 250 1/5 1,280
(256, 1, 64) 250 1/5 1,280
(512, 16, 1024) 506 1/5 2,560
(512, 4, 1024) 506 1/5 2,560
(512, 8, 512) 506 1/5 2,560
(512, 4, 256) 506 1/5 2,560
(512, 4, 128) 506 1/5 2,560
(512, 2, 128) 506 1/5 2,560
(512, 2, 64) 506 1/5 2,560
(512, 1, 64) 506 1/5 2,560
(1024, 16, 1024) 1,018 1/5 5,120
(1024, 8, 512) 1,018 1/5 5,120
(1024, 4, 256) 1,018 1/5 5,120
(1024, 4, 128) 1,018 1/5 5,120
(1024, 2, 128) 1,018 1/5 5,120
(1024, 2, 64) 1,018 1/5 5,120
(1024, 1, 64) 1,018 1/3 3,072
(2048, 4, 128) 2,042 1/3 6,144
(2048, 2, 64) 2,042 1/3 6,144
11-87

(2048, 1, 64) 2,042 1/3 6,144

(3072, 2, 64) 3,066 1/3 9,216
(3072, 1, 64) 3,066 1/3 9,216
(4096, 2, 64) 4,090 1/3 12,288
(4096, 1, 64) 4,090 1/3 12,288
(5120, 2, 64) 5,114 1/3 15,360
(5120, 1, 64) 5,114 1/3 15,360
1
2 12.4.1.3.2.3.2.111.4.1.3.2.3.2.1 Turbo Encoder

⎡ n0 (D) n1(D) ⎤
G(D) = ⎢1 ⎥
⎣ d(D) d(D) ⎥⎦
9
11-88
8 output first.
11-89
X
Y0
n0
Y1
n1
Nturbo
Information
Bits
(Input)
Control
Puncturing Code
and Symbols
Turbo
Interleaver
X'
Y'0
n0
Y'1
n1
Control
1
11-90
Code Rate
Output 1/3 1/5
X 1 1
Y0 1 1
Y1 0 1
X′ 0 0
Y′ 0 1 1
Y′ 1 0 1

from top to bottom.
2
Code Rate
Output 1/3 1/5
X 111 000 111 000

Y0 111 000 111 000
Y1 000 000 111 000
X′ 000 111 000 111
Y′ 0 000 111 000 111
Y′ 1 000 000 000 111
4

11-91
Add 1
Counter Lookup
5 LSBs Bit 5 Bits

21
11-92
Turbo Turbo
Nturbo n
128 122 2
256 250 3
512 506 4
1,024 1,018 5
2,048 2,042 6
3,072 3,066 7
4,096 4,090 7
5,120 5,114 8
2
11-93
Table n=2 n=3 n=4 n=5 n=6 n=7 n=8

Index Entries Entries Entries Entries Entries Entries Entries
0 3 1 5 27 3 15 3
1 3 1 15 3 27 127 1
2 3 3 5 1 15 89 5
3 1 5 15 15 13 1 83
4 3 1 1 13 29 31 19
5 1 5 9 17 5 15 179
6 3 1 9 23 1 61 19
7 1 5 15 13 31 47 99
8 1 3 13 9 3 127 23
9 1 5 15 3 9 17 1
10 3 3 7 15 15 119 3
11 1 5 11 3 31 15 13
12 1 3 15 13 17 57 13
13 1 5 3 1 5 123 3
14 1 5 15 13 39 95 17
15 3 1 5 29 1 5 1
16 3 3 13 21 19 85 63
17 1 5 15 19 27 17 131
18 3 3 9 1 15 55 17
19 3 5 3 3 13 57 131
20 3 3 1 29 45 15 211
21 1 5 3 17 5 41 173
22 3 5 15 25 33 93 231
23 1 5 1 29 15 87 171
24 3 1 13 9 13 63 23
25 1 5 1 13 9 15 147
26 3 1 9 23 15 13 243
27 1 5 15 13 31 15 213
28 3 3 11 13 17 81 189
29 1 5 3 1 5 57 51
30 1 5 15 13 15 31 15
31 3 3 5 13 33 69 67
2
11-94
1 12.4.1.3.2.3.311.4.1.3.2.3.3 Scrambling
6 initialized to the state [ 1 1 1 b 2 b1 b 0 r6 r5 r4 r3 r2 r1 r0 d 3 d 2 d1 d 0 ]. The r6r5r4r3r2r1r0 bits shall be
7 equal to the 7-bit preamble MACIndex value (see Table 11.4.1.3.2.2-2). The d3d2d1d0 bits
8 shall be determined by the nominal data rate, as specified in Table 11.4.1.3.2.3.3-1. The
9 b2b1b0 bits shall be determined by the payload size, as specified in Table 11.4.1.3.2.3.3-1.
10 The initial state shall generate the first scrambling bit. The shift register shall be clocked
11 once for every encoder output code symbol to generate a bit of the scrambling sequence.
12 Every encoder output code symbol shall be XOR’d with the corresponding bit of the
13 scrambling sequence to yield a scrambled encoded bit.
11-95
Transmission
Format
(Physical Layer Nominal
Packet Size (bits), b2 b1 b0 d3 d2 d1 d0 Data
Nominal Transmit Rate
Duration (slots), (kbps)
Preamble Length
(chips))
(128, 16, 1024) 0 0 0 0 0 0 1 4.8

(128, 8, 512) 0 0 0 0 0 1 0 9.6
(128, 4, 256) 0 0 0 0 0 1 1 19.2
(128, 4, 1024) 0 0 0 0 0 1 1 19.2
(128, 2, 128) 0 0 0 0 1 0 0 38.4
(128, 1, 64) 0 0 0 0 1 1 0 76.8
(256, 16, 1024) 0 0 1 0 0 0 1 9.6
(256, 8, 512) 0 0 1 0 0 1 0 19.2
(256, 4, 256) 0 0 1 0 0 1 1 38.4
(256, 4, 1024) 0 0 1 0 0 1 1 38.4
(256, 2, 128) 0 0 1 0 1 0 0 76.8
(256, 1, 64) 0 0 1 0 1 1 0 153.6
(512, 16, 1024) 0 1 0 0 0 0 1 19.2
(512, 8, 512) 0 1 0 0 0 1 0 38.4
(512, 4, 256) 0 1 0 0 0 1 1 76.8
(512, 4, 1024) 0 1 0 0 0 1 1 76.8
(512, 4, 128) 0 1 0 0 1 0 1 76.8
(512, 2, 128) 0 1 0 0 1 0 0 153.6
(512, 2, 64) 0 1 0 0 1 1 1 153.6
(512, 1, 64) 0 1 0 0 1 1 0 307.2
(1024, 16, 1024) 1 1 1 0 0 0 1 38.4
(1024, 8, 512) 1 1 1 0 0 1 0 76.8
(1024, 4, 256) 1 1 1 0 0 1 1 153.6
(1024, 4, 128) 0 1 1 0 1 0 1 153.6
(1024, 2, 128) 1 1 1 0 1 0 0 307.2
(1024, 2, 64) 0 1 1 0 1 1 1 307.2
11-96
Transmission
Format
Packet Size (bits), b2 b1 b0 d3 d2 d1 d0 Data
Preamble Length
(chips))
(1024, 1, 64) 1 1 1 0 1 1 0 614.4

(2048, 4, 128) 1 1 1 0 1 0 1 307.2
(2048, 2, 64) 1 1 1 0 1 1 1 614.4
(2048, 1, 64) 1 1 1 1 0 0 1 1228.8
(3072, 2, 64) 1 1 1 1 0 0 0 921.6
(3072, 1, 64) 1 1 1 1 0 1 1 1843.2
(4096, 2, 64) 1 1 1 1 0 1 0 1228.8
(4096, 1, 64) 1 1 1 1 1 0 0 2457.6
(5120, 2, 64) 1 1 1 1 1 0 1 1536.0
(5120, 1, 64) 1 1 1 1 1 1 0 3072.0
1
1 1 1 b2 b1 b0 r6 r5 r4 r3 r2 r1 r0 d3 d2 d1 d0
Scrambling
Sequence
2

6 Channel Interleaver. Channel interleaving shall consist of a Symbol Reordering stage
11-97
1 followed by a Matrix Interleaving stage which is followed by a Short Sequence Repetition

2 Stage.
3 The packet length, N (including data and tail bits) is expressed as N = R × K × 2m, where R,
5 parameters R, K, m, a short-packet wrap-around parameter W, and an end-around-shift
6 parameter D.

18 shall be last.
26 sequence, etc.
27 4. The U, V0 and V′0sequences shall be ordered according to UV0 V′0. That is, the U
29 12.4.1.3.2.3.4.211.4.1.3.2.3.4.2 Matrix Interleaving

36 c < C, and 0 ≤ k < K.
38 shifted by (c × K + k) mod R. In other words, matrix[ r ] [ c ] [ k ] is transformed to
11-98
2 interleaved (based on column-index).
3 4. If K > 3, then the symbols at level given by ⎣K/2⎦ are swapped with symbols at level
4 1 (k=1).
7 symbol ((k × C + c) × R + r), where 0 ≤ i < N comes from the rth row, cth column, and
8 kth level where, 0 ≤ r < R , 0 ≤ c < C, and 0 ≤ k < K.
10 are written into with R rows, C ≡ 2m+1 columns and K levels. Symbols are written
11 into the 3-dimensional array with level-index incrementing first, followed by
12 column-index, followed by row-index. In other words, the ith incoming symbol ((r ×
13 C + c) × K + k), where 0 ≤ i < 2 × N goes into the rth row, cth column, and kth level,
14 where 0 ≤ r < R , 0 ≤ c < C, and 0 ≤ k < K.
17 transformed to matrix[r + ⎣(K × c + k) / D⎦ mod R][c] [k].
20 9. If K > 3, then the symbols at level ⎣K/2⎦ are swapped with symbols at level 1 (k=1).
23 symbol ((k × C + c) × R + r), where 0 ≤ i < 2 × N comes from the rth row, cth column
27 12.4.1.3.2.3.4.311.4.1.3.2.3.4.3 Short Sequence Repetition

28 If the total number of symbols (3 × N or 5 × N) output by the Matrix Interleaving stage as
29 described above is less than the wrap-around parameter W, then the output sequence is
30 repeated partially or fully so that the length of the sequence is equal to W binary symbols.
31 Otherwise, the symbol sequence output by the matrix interleaver described above is
32 regarded as the output of the channel interleaver. Table 11.4.1.3.2.3.4.3-1 below shows the
33 interleaver parameters for various packets used on the Forward Traffic Channel.
11-99
Transmission Format N K R m D W
(Physical Layer Packet
Size(bits), Nominal
Transmit Duration
(slots), Preamble Length
(chips))
(128, 16, 1024) 128 1 2 6 4 0

(128, 8, 512) 128 1 2 6 4 0
(128, 4, 1024) 128 1 2 6 4 0
(128, 4, 256) 128 1 2 6 4 0
(128, 2, 128) 128 1 2 6 4 0
(128, 1, 64) 128 1 2 6 4 0
(256, 16, 1024) 256 1 2 7 4 0
(256, 8, 512) 256 1 2 7 4 0
(256, 4, 1024) 256 1 2 7 4 0
(256, 4, 256) 256 1 2 7 4 0
(256, 2, 128) 256 1 2 7 4 0
(256, 1, 64) 256 1 2 7 4 0
(512, 16, 1024) 512 1 2 8 4 0
(512, 8, 512) 512 1 2 8 4 0
(512, 4, 1024) 512 1 2 8 4 0
(512, 4, 256) 512 1 2 8 4 0
(512, 4, 128) 512 1 2 8 4 6,144
(512, 2, 128) 512 1 2 8 4 0
(512, 2, 64) 512 1 2 8 4 6,144
(512, 1, 64) 512 1 2 8 4 0
(1024, 16, 1024) 1024 1 2 9 4 0
(1024, 8, 512) 1024 1 2 9 4 0
(1024, 4, 256) 1024 1 2 9 4 0
(1024, 4, 128) 1024 1 2 9 4 6,144
(1024, 2, 128) 1024 1 2 9 4 0
(1024, 2, 64) 1024 1 2 9 4 6,144
(1024, 1, 64) 1024 1 2 9 4 0
(2048, 4, 128) 2048 1 2 10 4 0
(2048, 2, 64) 2048 1 2 10 4 0
11-100
Transmission Format N K R m D W
Size(bits), Nominal
Transmit Duration
(chips))
(2048, 1, 64) 2048 1 2 10 4 0

(3072, 2, 64) 3072 1 3 10 4 0
(3072, 1, 64) 3072 1 3 10 4 0
(4096, 2, 64) 4096 1 4 10 4 0
(4096, 1, 64) 4096 1 4 10 4 0
(5120, 2, 64) 5120 5 4 8 10 0
(5120, 1, 64) 5120 5 4 8 10 0
1
2 12.4.1.3.2.3.511.4.1.3.2.3.5 Modulation
5 QPSK, 8-PSK, or 16-QAM modulation symbols, depending on the data rate.
6 12.4.1.3.2.3.5.111.4.1.3.2.3.5.1 QPSK Modulation

7 For physical layer packet sizes of 128, 256, 512, 1,024, or 2,048 bits, groups of two
8 successive channel interleaver output symbols shall be grouped to form QPSK modulation
9 symbols. Each group of two adjacent block interleaver output symbols, x(2k) and x(2k + 1),
10 k = 0,…, M – 1 shall be mapped into a complex modulation symbol (mI(k), mQ(k)) as
11 specified in Table 11.4.1.3.2.3.5.1-1. Figure 11.4.1.3.2.3.5.1-1 shows the signal
12 constellation of the QPSK modulator, where s0 = x(2k) and s1 = x(2k + 1).

s1 s0
mI(k) mQ(k)
x(2k + 1) x(2k)
0 0 D D
0 1 –D D
1 0 D –D
1 1 –D –D
Note: D = 1 2.
14
11-101
Q Channel
s1s 0
01 00
1 2
−1 2 1 2
I Channel
−1 2
11 10
3 12.4.1.3.2.3.5.211.4.1.3.2.3.5.2 8-PSK Modulation

4 For physical layer packet sizes of 3,072 bits, groups of three successive channel interleaver
5 output symbols shall be grouped to form 8-PSK modulation symbols. Each group of three
6 adjacent block interleaver output symbols, x(3k), x(3k + 1), and x(3k + 2), k = 0,…, M – 1
8 11.4.1.3.2.3.5.2-1. Figure 11.4.1.3.2.3.5.2-1 shows the signal constellation of the 8-PSK
9 modulator, where s0 = x(3k), s1 = x(3k + 1), and s2 = x(3k + 2).
11-102

s2 s1 s0
mI(k) mQ(k)
x(3k + 2) x(3k + 1) x(3k)
0 0 0 C S
0 0 1 S C
0 1 1 –S C
0 1 0 –C S
1 1 0 –C –S
1 1 1 –S –C
1 0 1 S –C
1 0 0 C –S
Q Channel
C = cos(π/8)
011 001 S = sin(π/8)
C
s 2s1s 0
010 S 000
–C –S S C
I Channel
–S
110 100
–C
111 101
4 12.4.1.3.2.3.5.311.4.1.3.2.3.5.3 16-QAM Modulation

5 For physical layer packet sizes of 4,096 and 5,120 bits, groups of four successive channel
6 interleaver output symbols shall be grouped to form 16-QAM modulation symbols. Each
7 group of four adjacent block interleaver output symbols, x(4k), x(4k + 1), x(4k + 2), and
8 x(4k + 3), i = 0,…, M – 1 shall be mapped into a complex modulation symbol (mI(k), mQ(k))
9 as specified in Table 11.4.1.3.2.3.5.3-1. Figure 11.4.1.3.2.3.5.3-1 shows the signal
10 constellation of the 16-QAM modulator, where s0 = x(4k), s1 = x(4k + 1), s2 = x(4k + 2), and
11 s3 = x(4k + 3).
11-103

s3 s2 s1 s0
mQ(k) mI(k)
x(4k + 3) x(4k + 2) x(4k + 1) x(4k)
0 0 0 0 3A 3A
0 0 0 1 3A A
0 0 1 1 3A –A
0 0 1 0 3A –3A
0 1 0 0 A 3A
0 1 0 1 A A
0 1 1 1 A –A
0 1 1 0 A –3A
1 1 0 0 –A 3A
1 1 0 1 –A A
1 1 1 1 –A –A
1 1 1 0 –A –3A
1 0 0 0 –3A 3A
1 0 0 1 –3A A
1 0 1 1 –3A –A
1 0 1 0 –3A –3A
Note: A = 1 10 ≈ 0.3162 .
2
11-104
Q Channel
s 3s 2s1s0
0010 0011 0001 0000
3A
A = 1 10
0110 0111 0101 0100

A
–3A –A A 3A
I Channel
1110 1111 1101 1100

–A
1010 1011 1001 1000

–3A

12 be used.
14 11.4.1.3.2.3.6-1.
11-105
Transmission Values per Physical Layer Packet Coding

Format
(Physical Layer
Number of
Packet Number
Number of Number of Modulation
Size(bits), of Full Effective Repeti-
Modulation Modulation Symbols in
Nominal Sequence Code tion
Transmit Trans- Rate Factor
Duration (slots), missions
mission
Preamble Length
(chips))
(128, 16, 1024) 320 24,576 76 256 1/5 76.8

(128, 8, 512) 320 12,288 38 128 1/5 38.4
(128, 4, 1024) 320 5,376 16 256 1/5 16.8
(128, 4, 256) 320 6,144 19 64 1/5 19.2
(128, 2, 128) 320 3,072 9 192 1/5 9.6
(128, 1, 64) 320 1,536 4 256 1/5 4.8
(256, 16, 1024) 640 24,576 38 256 1/5 38.4
(256, 8, 512) 640 12,288 19 128 1/5 19.2
(256, 4, 1024) 640 5,376 8 256 1/5 8.4
(256, 4, 256) 640 6,144 9 384 1/5 9.6
(256, 2, 128) 640 3,072 4 512 1/5 4.8
(256, 1, 64) 640 1,536 2 256 1/5 2.4
(512, 16, 1024) 1,280 24,576 19 256 1/5 19.2
(512, 8, 512) 1,280 12,288 9 768 1/5 9.6
(512, 4, 1024) 1,280 5,376 4 256 1/5 4.2
(512, 4, 256) 1,280 6,144 4 1,024 1/5 4.8
(512, 4, 128) 3,072 6,272 2 128 1/5 2.04
(512, 2, 128) 1,280 3,072 2 512 1/5 2.4
(512, 2, 64) 3,072 3,136 1 64 1/5 1.02
(512, 1, 64) 1,280 1,536 1 256 1/5 1.2
(1024, 16, 1024) 2,560 24,576 9 1,536 1/5 9.6
(1024, 8, 512) 2,560 12,288 4 2,048 1/5 4.8
(1024, 4, 256) 2,560 6,144 2 1,024 1/5 2.4
(1024, 4, 128) 3,072 6,272 2 128 1/5 2.04
(1024, 2, 128) 2,560 3,072 1 512 1/5 1.2
11-106

Format
(Physical Layer
Number of
Packet Number
mission
Preamble Length
(chips))
(1024, 2, 64) 3,072 3,136 1 64 1/5 1.02

(1024, 1, 64) 1,536 1,536 1 0 1/3 1
(2048, 4, 128) 3,072 6,272 2 128 1/3 2.04
(2048, 2, 64) 3,072 3,136 1 64 1/3 1.02
(2048, 1, 64) 3,072 1,536 0 1,536 2/3 1
(3072, 2, 64) 3,072 3,136 1 64 1/3 1.02
(3072, 1, 64) 3,072 1,536 0 1,536 2/3 1
(4096, 2, 64) 3,072 3,136 1 64 1/3 1.02
(4096, 1, 64) 3,072 1,536 0 1,536 2/3 1
(5120, 2, 64) 3,840 3,136 0 3,136 20/49 1
(5120, 1, 64) 3,840 1,536 0 1,536 5/6 1
1

5 mI(3),… denotes the sequence of sequence-repeated modulation output values in the in-
10 mQ(3),…denotes the sequence of sequence-repeated modulation output values in the
11-107

7 symbols.

1 1
16 4

15 by-chip basis.
16 12.4.1.3.2.411.4.1.3.2.4 Control Channel

18 messages. Control Channel packets belonging to the synchronous capsule shall be
19 transmitted using a Transmission Format of (1024, 8, 512) corresponding to a data rate of
20 76.8 kbps or using a Transmission Format of (1024, 16, 1024) corresponding to a data rate
21 of 38.4 kbps. Control Channel packets belonging to an asynchronous or a sub-
22 synchronous capsule shall be transmitted using Transmission Formats of (1024, 8, 512),
23 (1024, 16, 1024), (128, 4, 1024), (256, 4, 1024), or (512, 4, 1024). The modulation
24 characteristics shall be the same as those of the Forward Traffic Channel at the
25 corresponding Transmission Format. The Control Channel transmissions shall be
26 distinguished from Forward Traffic Channel transmissions by having a preamble that is
27 covered by a bi-orthogonal cover sequence with MACIndex 2, 3, 71, or that specified by the
28 CCShortPacketsMACIndex attribute as specified in 11.4.1.3.2.3.1. A MACIndex value of 2
29 shall be used for the Transmission Format of (1024, 8, 512) or 76.8 kbps data rate, a
30 MACIndex value of 3 shall be used for the Transmission Format of (1024, 16, 1024) or 38.4
31 kbps data rate, and a MACIndex value of 71 or a MACIndex value specified by
32 CCShortPacketsMACIndex attribute value shall be used for the Transmission Formats of
33 (128, 4, 1024), (256, 4, 1024), or (512, 4, 1024).

35 The Forward Traffic Channel or Control Channel data modulation chips shall be time-
36 division multiplexed with the preamble, Pilot Channel, and MAC Channel chips according
37 to the timing diagrams in Figure 11.4.1.3.3-1, Figure 11.4.1.3.3-2, Figure 11.4.1.3.3-3,
38 Figure 11.4.1.3.3-4 and Figure 11.4.1.3.3-5. The multiplexing parameters shall be as
39 specified in Table 11.4.1.3.3-1 through Table 11.4.1.3.3-5.
11-108

2 Forward Traffic Channel physical layer packets with Transmission Formats as shown in
3 Table 11.4.1.3.3-1 shall be time division multiplexed with the preamble, Pilot Channel and
4 MAC Channel chips according to the timing diagrams in Figure 11.4.1.3.3-1.

6 Figure 11.4.1.3.3-1
Transmission Format
(Physical Layer Packet Size (bits), Nominal Transmit
Duration (slots), Preamble Length (chips))
(128, 4, 256)
(128, 2, 128)
(256, 4, 256)
(256, 2, 128)
(512, 4, 256)
(512, 4, 128)
(512, 2, 128)
(512, 2, 64)
(1024, 4, 256)
(1024, 4, 128)
(1024, 2, 128)
(1024, 2, 64)
(2048, 4, 128)
(2048, 2, 64)
(3072, 2, 64)
(4096, 2, 64)
(5120, 2, 64)
7
11-109
320, 640, 1,280, 2,560,

3,072, or 3,840
Modulation Symbols


N 400 – N & MAC 800 & MAC & MAC 800 & MAC 400
2 or 4 Slots
4,096 or 8,192 Chips
1
3 Cases with Transmission Formats in Table 11.4.1.3.3-1

8 Figure 11.4.1.3.3-2
Transmission Format
(Physical Layer Packet Size(bits), Nominal Transmit
(128, 16, 1024)

(128, 8, 512)
(256, 16, 1024)
(256, 8, 512)
(512, 16, 1024)
(512, 8, 512)
(1024, 16, 1024)
(1024, 8, 512)
9
11-110
320, 640, 1,280 or 2,560

Modulation Symbols

(Repeated Sequence)
Chips 224 or or 224 Chips 224 224 Chips 224 Chips
8 or 16 Slots
16,384 or 32,768 Chips
1
2 Figure 11.4.1.3.3-2. Preamble, Pilot, MAC, and Data Multiplexing with Transmission
3 Formats in Table 12.4.1.3.3-2

8 Figure 11.4.1.3.3-3
Transmission Format
(128, 1, 64)
(256, 1, 64)
(512, 1, 64)
(2048, 1, 64)
(3072, 1, 64)
(4096, 1, 64)
(5120, 1, 64)
9
11-111
320, 640, 1,280, 3,072 or 3,840 Data Modulation Symbols

64 336 & MAC 800 & MAC 400
Chips Chips
1 Slot
2,048 Chips
1
2 Figure 11.4.1.3.3-3. Preamble, Pilot, MAC, and Data Multiplexing for the 1-Slot Cases with
3 Transmission Formats in Table 11.4.1.3.3-3

8 Figure 11.4.1.3.3-4
Transmission Format
(1024, 1, 64)

64 336 & MAC 800 & MAC 400
Chips Chips
1 Slot
2,048 Chips
9
11 with Transmission Formats in Table 11.4.1.3.3-4.
11-112
1 Forward Traffic Channel physical layer packets with Packet Transmission Formats as
2 shown in Table 11.4.1.3.3-5 Table 14.3.1.3.3-5 shall be time division multiplexed with the
3 preamble, Pilot Channel and MAC Channel chips according to the timing diagrams in
4 Figure 11.4.1.3.3-5Figure 14.3.1.3.3-5.

6 Figure 11.4.1.3.3-5Figure 12.4.1.3.3-5
Transmission Format
(128, 4, 1,024)
(256, 4, 1,024)
(512, 4, 1,024)
7
320, 640, or 1280

Modulation Symbols

(Repeated Sequence)
Chips 224 224 Chips 224 224 Chips 224 Chips
Chips Chips Chips Chips Chips
4 Slots (8,192 Chips)

8
11 Table 12.4.1.3.3-6 shows the number of Pilot chips, MAC chips, and Data chips
12 corresponding to each of the possible transmission formats
11-113
Transmission Format
(Physical Layer Packet Size(bits), Pilot MAC Data
Nominal Transmit Duration (slots), chips chips chips
(128, 16, 1,024) 3,072 4,096 24,576
(128, 8, 512) 1,536 2,048 12,288
(128, 4, 1024) 768 1,024 5,376
(128, 4, 256) 768 1,024 6,144
(128, 2, 128) 384 512 3,072
(128, 1, 64) 192 256 1,536
(256, 16, 1024) 3,072 4,096 24,576
(256, 8, 512) 1,536 2,048 12,288
(256, 4, 1024) 768 1,024 5,376
(256, 4, 256) 768 1,024 6,144
(256, 2, 128) 384 512 3,072
(256, 1, 64) 192 256 1,536
(512, 16, 1024) 3,072 4,096 24,576
(512, 8, 512) 1,536 2,048 12,288
(512, 4, 1024) 768 1,024 5,376
(512, 4, 256) 768 1,024 6,144
(512, 4, 128) 768 1,024 6,272
(512, 2, 128) 384 512 3,072
(512, 2, 64) 384 512 3,136
(512, 1, 64) 192 256 1,536
(1024, 16, 1024) 3,072 4,096 24,576
(1024, 8, 512) 1,536 2,048 12,288
(1024, 4, 256) 768 1,024 6,144
(1024, 4, 128) 768 1,024 6,272
(1024, 2, 128) 384 512 3,072
(1024, 2, 64) 384 512 3,136
(1024, 1, 64) 192 256 1,536
(2048, 4, 128) 768 1,024 6,272
(2048, 2, 64) 384 512 3,136
(2048, 1, 64) 192 256 1,536
11-114
Transmission Format
(3072, 2, 64) 384 512 3,136
(3072, 1, 64) 192 256 1,536
(4096, 2, 64) 384 512 3,136
(4096, 1, 64) 192 256 1,536
(5120, 2, 64) 384 512 3,136
(5120, 1, 64) 192 256 1,536
1

3 Following orthogonal spreading, the combined modulation sequence shall be quadrature
4 spread as shown in Figure 11.4.1.3.1-1. The spreading sequence shall be a quadrature
5 sequence of length 215 (i.e., 32768 PN chips in length). This sequence is called the pilot PN
6 sequence and shall be based on the following characteristic polynomials:
7 PI(x) = x15 + x10 + x8 + x7 + x6 + x2 + 1

9 and
10 PQ(x) = x15 + x12 + x11 + x10 + x9 + x5 + x4 + x3 + 1

14 recursions:
15 I(n) = I(n – 15) ⊕ I(n – 13) ⊕ I(n – 9) ⊕ I(n – 8) ⊕ I(n – 7) ⊕ I(n – 5)
17 and
18 Q(n) = Q(n – 15) ⊕ Q(n – 12) ⊕ Q(n – 11) ⊕ Q(n – 10) ⊕ Q(n – 6) ⊕ Q(n – 5) ⊕
19 Q(n – 4) ⊕ Q(n – 3)
11-115
3 2 seconds.
4 Pilot Channels shall be identified by an offset index in the range from 0 through 511
5 inclusive. This offset index shall specify the offset value (in units of 64 chips) by which the
6 pilot PN sequence lags the zero-offset pilot PN sequence. The zero-offset pilot PN sequence
7 shall be such that the start of the sequence shall be output at the beginning of every even
8 second in time, referenced to access network transmission time. The start of the zero-offset
9 pilot PN sequence for either the I or Q sequences shall be defined as the state of the
10 sequence for which the next 15 outputs inclusive are ‘0’. Equivalently, the zero-offset
11 sequence is defined such that the last chip prior to the even-second mark as referenced to
12 the transmit time reference is a ‘1’ prior to the 15 consecutive ‘0’s.
13 12.4.1.3.511.4.1.3.5 Filtering

18 12.3.1.3.6-1. Specifically, the normalized frequency response of the filter shall be contained
19 within ±δ1 in the passband 0 ≤ f ≤ fp and shall be less than or equal to –δ2 in the stopband
20 f ≥ fs. The numerical values for the parameters are δ1 = 1.5 dB, δ2 = 40 dB, fp = 590 kHz,
21 and fs = 740 kHz.
11-116
20 log10 S(f )
δ1
δ1
δ2
f
0 fp fs
1
∞
k =0
[αs(kTs – τ) – h(k)]2 ≤ 0.03,
7 coefficients h(k), for k < 48, are given in Figure 11.4.1.3.5.1-1; h(k) = 0 for k ≥ 48. Note that
11-117
k h(k)
0, 47 –0.025288315
1, 46 –0.034167931
2, 45 –0.035752323
3, 44 –0.016733702
4, 43 0.021602514
5, 42 0.064938487
6, 41 0.091002137
7, 40 0.081894974
8, 39 0.037071157
9, 38 –0.021998074
10, 37 –0.060716277
11, 36 –0.051178658
12, 35 0.007874526
13, 34 0.084368728
14, 33 0.126869306
15, 32 0.094528345
16, 31 –0.012839661
17, 30 –0.143477028
18, 29 –0.211829088
19, 28 –0.140513128
20, 27 0.094601918
21, 26 0.441387140
22, 25 0.785875640
23, 24 1.0
2

ω2 + jαωω0 − ω0 2
H(ω) = K
ω2 − jαωω0 − ω0 2 ,
6
11-118
4 waveforms.
11 inputs (see Table 11.4.1.3.5.1-1) to the RF output of the transmitter.

15 components, including pilot PN sequences, slots, and Walsh functions, shall be derived.
16 The time-base reference shall be time-aligned to CDMA System Time, as described in 1.14.
17 Reliable external means should be provided at each sector to synchronize each sector’s
18 time base reference to CDMA System Time. Each sector should use a frequency reference of
19 sufficient accuracy to maintain time alignment to CDMA System Time. In the event that the
20 external source of CDMA System Time is lost,157 the sector shall maintain transmit timing
21 within ±10 μs of CDMA System Time for a period of not less than 8 hours.

24 shall radiate the pilot PN sequence within ±10 µs of CDMA System Time.
29
11-119
1 1No text
11-120
SUBTYPE 3 Physical Layer 3GPP2 C.S0024-B v2.0
1 1312 SUBTYPE 3 PHYSICAL LAYER
2 13.112.1 Subtype 3 Physical Layer Protocol Instance
3 13.1.112.1.1 Overview
4 This chapter contains the specification for the Subtype 3 Physical Layer Protocol. The
5 Subtype 3 Physical Layer operates with the Enhanced Access Channel MAC Protocol, the
6 Enhanced Control Channel MAC Protocol, the Multicarrier Forward Traffic Channel MAC
7 Protocol, and the Multicarrier Reverse Traffic Channel MAC Protocol.
9 13.1.2.112.1.2.1 Commands

13 • ReverseTrafficPacketsMissed for every active reverse CDMA channel assigned to the
14 access terminal.
15 • ForwardTrafficCompleted for every active forward CDMA channel assigned to the access
16 terminal.
17 13.1.2.312.1.2.3 Public Data

20 • SoftRAB for each sector in the access terminal’s active set if the access terminal has
21 negotiated Multicarrier Reverse Traffic Channel MAC Protocol.
22 • MaxRLTxPwrDiff if the access terminal has negotiated Multicarrier Reverse Traffic
23 Channel MAC Protocol
24 • Long Code Mask for DRC, ACK, and DSC transmissions for forward CDMA channels on
25 a reverse CDMA channel if using BasicFeedbackMultiplexing mode or
26 EnhancedFeedbackMultiplexing mode
27 • MultiCarrierCapability
28 • MACIndexBits
29 • DTXMode

31 The transmission unit of this protocol is a Subtype 3 Physical Layer packet. Each Subtype
32 3 Physical Layer packet contains a MAC Layer packet.
12-1
3GPP2 C.S0024-B v2.0 SUBTYPE 3 Physical Layer

15 The access terminal shall not initiate negotiation of the following attributes:
16 • MaxRLTxPwrDiff
17 • AdditionalCarriersInitTxPwr
19 13.1.5.112.1.5.1 Procedures

29 then
12-2
13
Field Length (bits)
MessageID 8
TransactionID 8
20
Field Length (bits)
MessageID 8
TransactionID 8
12-3

6
8 13.1.6.112.1.6.1 Procedures
9 Procedures for the InUse Instance of the protocol are described in 12.2, 12.3, and 12.4.
13 given attribute.
14
Field Length (bits)
MessageID 8
TransactionID 8

19
23
12-4
Field Length (bits)
MessageID 8
TransactionID 8
4
8
Field Length (bits)
MessageID 8
TransactionID 8
12
14 13.1.6.3.112.1.6.3.1 Commands
16 13.1.6.3.212.1.6.3.2 Indications
17 These protocols do not register to receive any indications.

12-5
2 Update Protocol to update values of the following attributes belonging to the Subtype 3
3 Physical Layer Protocol:
4 • MaxRLTxPwrDiff
5 • DTXMode
6 • DTXRRIMode
7 • AdditionalCarriersInitTxPower
8 The access terminal shall not send an AttributeUpdateRequest message proposing to

9 update the value of the MaxRLTxPwrDiff attribute.

11 The negotiable simple attributes for this protocol are listed in Table 12.1.7.1-1Table
12 10.7.7.1-1. The access terminal shall use as defaults the values in Table 12.1.7.1-1Table
13 10.7.7.1-1 that are typed in bold italics.
12-6

0x00 Access Terminal supports
NoFeedbackMultiplexing mode
BasicFeedbackMultiplexing
mode
0xff MultiCarrierCapability
EnhancedFeedbackMultiplexin
g mode
All other Reserved
values
0x06 No Limit on the Max Transmit
Power differential between
adjacent carriers
0x00 The Max Transmit Power
differential between adjacent
carriers is 15 dB
carriers is 18 dB
0xfe MaxRLTxPwrDiff carriers is 21 dB
carriers is 24 dB
carriers is 27 dB
carriers is 30 dB
All other Reserved
values
0x00 Maximum Terminal Transmit
Power is 20 mW
0xfd MaxTransmitPower
0x01 to Maximum Terminal Transmit
0xff Power in 25 mW increments158
158 The maximum access terminal transmit power takes the following values: 20 mW, 25 mW, 50
mW, 75 mW, 100 mW…and so on up to the maximum value of 6.4W.
12-7

0x00 DTXMode is disabled
0xfc DTXMode 0x01 DTXMode is enabled
All other Reserved

values
0x00 DTXRRIMode if DTXMode is
enabled is 0
0x01 DTXRRIMode if DTXMode is
0xfb DTXRRIMode
enabled is 1
All other Reserved
values
0x00 Access Terminal supports a 7-
bit Preamble MAC Index and a
7-bit Reverse Link MAC Index
0x01 Access Terminal supports an 8-
0xfa MACIndexBits
bit Preamble MAC Index and a
9-bit Reverse Link MAC Index
All other Reserved
values
2 13.1.7.2.112.1.7.2.1 AdditionalCarriersInitTxPower Attribute

3
12-8

Length 8 N/A
AttributeID 8 N/A
One or more instances of the following:
ValueID 8 N/A
AdditionalCarriersAssigned 1 0
ReferenceCDMAChannel 24 0x00000
NumAdditionalRLCDMAChannels 4 0x0
Assigned
NumAdditionalRLCDMAChannelsAssigned occurrences of the
following fields:
ReverseCDMAChannel 24 0x00000
NumSectors 3 0x0
NumSectors instances of the following two fields:
PilotPNOffset 9 0x000
TxInitAdjustRelativeToReferenceC 5 0x00
DMAChannel
Reserved 0-7 (as N/A

needed)
3 Length field.
6 complex value.
7 AdditionalCarriersAssigned
8 The access network shall set this field to ‘1’ if additional reverse
9 CDMA channels (not including any of the active reverse CDMA
10 channels) are assigned to the access terminal. Otherwise, the access
11 network shall set this field to zero. If this field is set to zero, the
12 access terminal shall ignore the rest of the fields in this attribute.
13 ReferenceCDMAChannel
14 The access network shall set this field to the active reverse CDMA
15 channel that the access terminal shall use to determine the initial
16 transmit power for the additional reverse CDMA channels.
12-9
1 NumAdditionalRLCDMAChannelsAssigned
2 The access network shall set this field to the number of additional
3 reverse CDMA channels assigned to the access terminal.
4 ReverseCDMAChannel
5 The access network shall set this field to the channel record of the
6 reverse CDMA channel assigned to the access terminal.
7 NumSectors The access network shall set this field to the number of sectors for
8 which the TxInitAdjust field is transmitted to the access terminal.
9 PilotPNOffset The access network shall set this field to the pilot PN sequence offset
10 for this sector in units of 64 chips.
11 TxInitAdjustRelativeToReferenceCDMAChannel
12 The access network shall set this field to the TxInitAdjust for the
13 assigned reverse CDMA channel relative to that of the reference
14 CDMA channel expressed as a 2’s complement number in steps of
15 1dB. The access terminal shall support all valid values of this field.
18 set the reserved bits to zero. The access terminal shall ignore this
19 field.
20 13.1.7.2.212.1.7.2.2 ReversePilotTransmitSlots Attribute

21
Field Length Default

(bits)
Length 8 N/A
AttributeID 168 N/A
ValueID 8 N/A
ReversePilotTransmitSlotsEnabled 1 0x0
ReversePilotTransmitSlotsDuration 0 or 3 0x0
ReversePilotTransmitSlotsPeriod 0 or 4 0x0
Reserved 0-7 (as N/A

needed)
24 Length field.
12-10
3 complex value.
4 ReversePilotTransmitSlotsEnabled
5 The access network shall set this field to enable or disable Revere
6 Link Pilot transmissions for slots specified by
7 ReversePilotTransmitSlotsDuration and
8 ReversePilotTransmitSlotsPeriod.
9 ReversePilotTransmitSlotsDuration
10 If the ReversePilotTransmitSlotsEnabled field is set to ‘1’ the access
11 network shall set the duration of the Reverse Link Pilot
12 Transmissions Interval in units of sub-frames to a value shown in
13 Table 12.1.7.2.2-1. Otherwise, the access network shall omit this
14 field.
15 ReversePilotTransmitSlotsPeriod
16 If the ReversePilotTransmitSlotsEnabled field is set to ‘1’ the access
17 network shall set the period of the Reverse Link Pilot Transmit Slots
18 Interval to a value shown in Table 12.1.7.2.2-2. Otherwise, the
19 access network shall omit this field. The Reverse Link Pilot Transmit
20 Slots Interval is defined as the time interval of duration
21 ReversePilotTransmitSlotsDuration frames that starts at times T
22 where T is the CDMA System Time in units of frames such that:
23 T mod ReversePilotTransmitSlotsPeriod = 0.
26 set the reserved bits to zero. The access terminal shall ignore this
27 field.
28 Table 12.1.7.2.2-1.Encoding of ReversePilotTransmitSlotsDuration Field
Field value Meaning
‘000’ 4
‘001’ 8
‘010’ 12
‘011’ 16
29
12-11
1 Table 12.1.7.2.2-2.Encoding of ReversePilotTransmitSlotsPeriod Field
Field value Meaning
‘0000’ 16
‘0001’ 20
‘0010’ 24
‘0011’ 28
‘0100’ 32

3
NPHYP Subtype field for this protocol 0x0003

4

8
12-12
2 13.2.112.2.1 Overview
4 packet can be of length 128, 256, 512, 768, 1024, 1536, 2048, 3072, 4096, 5120, 6144,
5 7168, 8192, or 12288 bits. The format of the physical layer packet depends upon the
6 channel on which it is transmitted. A physical layer packet carries one MAC layer packet.

9 The length of a Control Channel physical layer packet shall be 128, 256, 512, or 1024 bits.
10 Each Control Channel physical layer packet shall carry one Control Channel MAC layer
11 packet. The 1024-bit Control Channel physical layer packets shall use the following format:
12
Field Length (bits)

FCS 16
TAIL 6
13
17
18 All other Control Channel physical layer packets shall use the following format:
19
Field Length (bits)

FCS 24
TAIL 6
23 Figure 12.2.2.1-1 illustrates the valid formats for the Control Channel physical layer
24 packets.
12-13
3 Figure 12.2.2.1-1. Physical Layer Packet Formats for the Control Channel

5 The length of an Access Channel physical layer packet shall be 256, 512, or 1024 bits.
6 Each Access Channel physical layer packet shall carry one Access Channel MAC layer
7 packet. Access Channel physical layer packets shall use the following format:
8
Field Length (bits)

FCS 16
TAIL 6
9
10 MAC Layer Packet - MAC layer packet from the Access Channel MAC Protocol.
13 Figure 12.2.2.2-1 illustrates the format of the Access Channel physical layer packets.
14
15 Figure 12.2.2.2-1. Physical Layer Packet Format for the Access Channel

17 The length of a Forward Traffic Channel physical layer packet shall be 128, 256, 512, 1024,
18 2048, 3072, 4096, 5120, 6144, 7168, or 8192 bits. A Forward Traffic Channel physical
19 layer packet shall carry one Forward Traffic Channel MAC layer packet addressed to one or
12-14
1 more access terminals. Forward Traffic Channel physical layer packets shall use the
2 following format:
3
Field Length (bits)
MAC Layer Packet 98, 226, 482, 994,

2018, 3042, 4066,
5090, 6114, 7138, or
8162
FCS 24
TAIL 6
5 Protocol.
9 packets.
10

13 The length of a Reverse Traffic Channel physical layer packet shall be 128, 256, 512, 768,
14 1024, 1536, 2048, 3072, 4096, 6144, 8192, or 12288 bits. Each Reverse Traffic Channel
15 physical layer packet shall carry one Reverse Traffic Channel MAC layer packet. Reverse
16 Traffic Channel physical layer packets shall use the following format:
17
Field Length (bits)
98, 226, 482, 738, 994,

1506, 2018, 3042,
MAC Layer Packet
4066, 6114,8162, or
12258
FCS 24
TAIL 6
18
12-15
2 Protocol.
6 packets.


19 polynomial:
20 g(x) = x16 + x12 + x5 + 1.
22 polynomial:
23 g(x) = x24 + x23 + x6 + x5 + x + 1.
12-16
2 • The output bits constitute all fields except the TAIL field of the physical layer.
Input
‘0’
x0 x1 x5 x12 x15
Output
‘0’

3
14 • The output bits constitute all fields except the TAIL field of the physical layer packets.
15
Input
‘0’
x0 x1 x5 x6 x23 x24
Output
‘0’

16
12-17




10 specified.

14 until the access attempt succeeds or ends. When the access terminal is transmitting the
15 Access Channel, the access terminal shall control the mean output power as specified in
16 the Access Channel MAC Protocol (see Table 14.1-1).

19 shall control the mean output power for each active reverse CDMA channel, using a
20 combination of closed-loop power control, open-loop power control, and the rules specified
21 by the Reverse Traffic Channel MAC Protocol (see 12.3.1.2.4, 12.3.2.1, and Table 14.1-1),
22 where the reverse CDMA channels assigned to the access terminal are public data of the
23 Route Update Protocol.
24 When the TxT2P (public data of the Reverse Traffic Channel MAC Protocol) is changed, the
25 access terminal output power, relative to the desired value in steady state, shall be within
26 ±0.5 dB or 20% of the change in dB, whichever is greater. The access terminal output
27 power shall settle to within ±0.5 dB or 20% of the change in dB, whichever is greater, of the
28 steady-state value within 200 μs of the physical layer sub-frame159 boundary.

159
The start of a sub-frame is specified by (T-FrameOffset) mod 4 = 0, where T is the
CDMA System Time in slots.
12-18



10 The access terminal shall provide two independent means for output power adjustment for
11 each active reverse CDMA channel: an open-loop estimation performed by the access
12 terminal and a closed-loop correction involving both the access terminal and the access
13 network. Accuracy requirements on the controlled range of mean output power (see 0) need
14 not apply for the following three cases:
18 12.3.1.2.3.1); or
19 • Mean input power levels exceeding –25 dBm within the 1.23-MHz bandwidth for each
20 assigned forward CDMA channel.
21 For a given access terminal, the transmit power differential between adjacent carriers shall
22 not exceed MaxRLTxPwrDiff. For any pair of adjacent reverse CDMA channels, the access
23 terminal shall maintain this differential by imposing on the carrier with higher transmit
24 power a maximum output power limitation that is MaxRLTxPwrDiff above the total transmit
25 power of the other carrier in the pair. Following the reception of an updated value of
26 MaxRLTxPwrDiff, the updated MaxRLTxPwrDiff shall take effect in each interlace in the
27 next sub-frame of that interlace unless a packet is currently being transmitted in that
28 interlace. For interlaces where a packet is currently being transmitted, the MaxRLTxPwrDiff
29 shall take effect at the end of that packet transmission, i.e. either maximum number of
30 sub-frames have been transmitted or the packet has been decoded early.

32 Open-loop operation for each assigned reverse CDMA channel shall be based on the sum of
33 the powers of the received Forward Pilot Channels (see 12.4.1.3.2.1) associated with that
34 assigned reverse CDMA channel.The nominal access probe structure and its transmit
35 power requirements are defined as part of the Access Channel MAC Protocol. The power of
36 the Access Data Channel relative to that of the Pilot Channel shall be as specified in Table
37 12.3.1.2.4.1-1 in which DataOffsetNom, DataOffset9k6, DataOffset19k2, and
38 DataOffset38k4 are public data of the Access Channel MAC Protocol. The output power of
39 the Pilot Channel during the preamble portion of an access probe shall be increased
12-19
1 relative to the nominal Pilot Channel power during the data portion of the probe by an
2 amount such that the total output power of the preamble and data portion of the access
3 probe, if transmitted at 9.6 kbps, are the same.
5 Reverse Traffic Channel transmission. If the access terminal has transmitted an access
6 probe on that carrier, the initial mean output power of the Pilot Channel of the Reverse
7 Traffic Channel shall be equal to the mean output power of the Pilot Channel at the end of
8 the last Access Channel probe minus the difference in the forward link mean received
9 signal power from the end of the last Access Channel probe to the start of the Reverse
10 Traffic Channel transmission. If the access terminal has not transmitted an access probe
11 on that carrier, the initial mean output power of the Pilot Channel of that Reverse Traffic
12 Channel shall be set to TxPilotInitPwr given by
13 TxPilotInitPwr = TxPilotPwrRefCarrier (dBm) – OpenLoopPwrRefCarrier (dBm) +
14 OpenLoopPwr (dBm) + TxInitAdjustServingSector (dB)
15 where
16 – TxPilotPwrRefCarrier is the transmit power of the reverse link Pilot Channel on
17 the ReferenceCDMAChannel
18 – OpenLoopPwrRefCarrier is the open loop mean output power of the reverse link
19 Pilot Channel of the ReferenceCDMAChannel
20 – OpenLoopPwr is the open loop mean output power of the reverse link Pilot
21 Channel on the reverse CDMA channel assigned to the access terminal
22 - TxInitAdjustServingSector is the TxInitAdjustRelativeToReferenceCDMAChannel
23 that corresponds to the forward link serving sector if it is included in the
24 AdditionalCarriersInitTxPower attribute. If it is not included in the attribute, the
25 access terminal shall set its value to 0 dB.
26 The subsequent mean output power of the Pilot Channel of the reverse CDMA channel for
27 which the access terminal has transmitted an access probe shall be the mean output
28 power of the Pilot Channel at the end of the last Access Channel probe minus the difference
29 in the forward link mean received signal power from the end of the last Access Channel
30 probe to the current Reverse Traffic Channel transmission, plus closed loop corrections as
31 specified in 12.3.1.2.4.2. The subsequent mean output power of the Pilot Channel of the
32 reverse CDMA channel for which the access terminal has not transmitted an access probe
33 shall be the initial mean output power of the Pilot Channel plus closed loop corrections as
34 specified in 12.3.1.2.4.2.The accuracy of the incremental adjustment to the mean output
35 power for an active reverse CDMA channel, as dictated by the Access Channel MAC
36 Protocol and the Reverse Traffic Channel MAC Protocol, shall be ±0.5 dB or 20% of the
37 change in dB, whichever is greater.
38 When the access terminal is transmitting the Access Channel, the power of the Data
39 Channel relative to that of the Pilot Channel during the data portion of the Access Channel
40 transmission shall be as specified in Table 12.3.1.2.4.1-1 in which DataOffsetNom,
41 DataOffset9k6, DataOffset19k2, and DataOffset38k4 are public data of the Access Channel
42 MAC Protocol. When the access terminal is transmitting the Access Channel, the power of
43 the Pilot Channel during the preamble portion of the Access Channel transmission shall be
12-20
1 equal to the total power transmitted during the data portion of the Access Channel
2 transmission when the Data Channel is transmitted at 9.6 kbps.
4 Transmissions

(kbps) (dB)

5
6 During the transmission of the RRI Channel on each active reverse CDMA channel, the
7 power of the RRI Channel relative to that of the Pilot Channel shall be as specified by
8 RRIChannelGain, where RRIChannelGain is public data of the Reverse Traffic Channel
9 MAC Protocol.
10 If the DSC Channel is transmitted for a forward CDMA channel, the power of the DSC
11 Channel relative to that of the Pilot Channel of the associated reverse CDMA channel
12 during the transmission of the DSC Channel shall be specified by DSCChannelGain, where
13 DSCChannelGain is public data of the Forward Traffic Channel MAC Protocol. Each
14 assigned forward CDMA channel and the reverse CDMA channel that is used to transmit
15 the DSC Channel associated with each forward CDMA channel are public data of the Route
16 Update Protocol.
17 During the transmission of the DRC Channel for each forward CDMA channel, the power of
18 the DRC Channel relative to that of the Pilot Channel of the associated reverse CDMA
19 channel, shall be as specified by DRCChannelGain, where DRCChannelGain is public data
20 of the Forward Traffic Channel MAC Protocol.
21 During the transmission of the ACK Channel for each forward CDMA channel, the power of
22 the ACK Channel relative to that of the Pilot Channel of the associated reverse CDMA
23 channel, shall be as specified by ACKChannelGain if the access terminal is transmitting an
24 ACK in response to a Single User packet, where ACKChannelGain is public data of the
25 Forward Traffic Channel MAC Protocol.
26 During the transmission of the ACK Channel for each forward CDMA channel, the power of
27 the ACK Channel relative to that of the Pilot Channel of the associated reverse CDMA
28 channel, shall be as specified by ACKChannelGain + DeltaACKChannelGainMUP if the
29 access terminal is transmitting an ACK in response to a Multi-User packet, where
30 ACKChannelGain and DeltaACKChannelGainMUP are public data of the Forward Traffic
31 Channel MAC Protocol.
32 During the transmission of the Data Channel on each active reverse CDMA channel, the
33 power of the Data Channel relative to that of the Pilot Channel shall be as specified by
34 TxT2P, where TxT2P is public data of the Reverse Traffic Channel MAC Protocol.
12-21
1 The Auxiliary Pilot Channel shall be transmitted on each active reverse CDMA channel
2 during the nth half slot if the Reverse Traffic Channel transmit payload is greater than or
3 equal to AuxiliaryPilotChannelMinPayload during half slots n−1 or n+1, where
4 AuxiliaryPilotChannelMinPayload is public data of the Reverse Traffic Channel MAC
5 Protocol.
6 If the Auxiliary Pilot Channel is transmitted on each active reverse CDMA channel during
7 the nth half slot, its power shall be specified relative to the maximum of the Data Channel
8 Gains during half-slots n−1 and n+1 by AuxiliaryPilotChannelGain, where
9 AuxiliaryPilotChannelGain is public data of the Reverse Traffic Channel MAC Protocol.
10 The access terminal shall maintain the power of the RRI Channel, and Data Channel for
11 each active reverse CDMA channel relative to that of the Pilot Channel, to within ±0.25 dB
12 of the specified values.
13 The access terminal shall maintain the power of the DSC Channel, DRC Channel and ACK
14 Channel, for each forward CDMA channel relative to that of the Pilot Channel of the
15 associated reverse CDMA channel, to within ±0.25 dB of the specified values.
16 The access terminal shall maintain the power of the Auxiliary Pilot Channel for each active
17 reverse CDMA channel during the nth half slot relative to that of the maximum of the Data
18 Channel Gains during half slots n−1 and n+1 to within ±0.25 dB of the specified values.
19 If the number of active reverse CDMA channels160 for an access terminal is equal to one
20 and if TxT2P is less than or equal to TxT2Pmin (both public data of the Reverse Traffic
21 Channel MAC Protocol) and the access terminal is unable to transmit the Reverse Traffic
22 Channel at the required output power level, the access terminal shall reduce the power of
23 the DSC Channel, the DRC Channel and the ACK Channel accordingly. The maximum
24 power reduction for the DSC Channel shall correspond to transmitting the DSC Channel
25 with gain equal to DSCChannelGainBase, where DSCChannelGainBase is public data of
26 the Forward Traffic Channel MAC Protocol. The maximum power reduction for the DRC
27 Channel shall correspond to gating off the DRC Channel. If the DRC Channel is active, the
28 DRC Channel power reduction shall occur only after the DSC Channel transmit power is
29 reduced to a level corresponding to DSCChannelGainBase. The maximum power reduction
30 for the ACK Channel shall correspond to gating off the ACK Channel. If the ACK Channel is
31 active, the ACK Channel power reduction shall occur only after the DRC Channel has been
32 gated off.
33 If the number of active reverse CDMA channels for an access terminal exceeds one and if
34 the TxT2P on all active reverse CDMA channels is less than or equal to TxT2Pmin and the
35 access terminal is unable to transmit the Reverse Traffic Channel at the required output
36 power level, the access terminal shall reduce the power of the active reverse CDMA
37 channels that carry only data, active reverse CDMA channels carrying overhead and data,
38 and the active reverse CDMA channels accordingly.
160 An active reverse CDMA channel is a reverse CDMA channel transmitting Pilot Channel on the
reverse link.
12-22
1 The maximum power reduction for the active reverse CDMA channels carrying only data is
2 gating off the Data Channels, RRI Channels, and Pilot Channels. Power reduction of the
3 Pilot Channels shall occur only after the Data and RRI Channels have been gated off. The
4 power reduction shall be performed sequentially for each active reverse CDMA channel
5 carrying only data in order of increasing ReverseChannelDroppingRank starting with the
6 active reverse CDMA channel with lowest ReverseChannelDroppingRank, where
7 ReverseChannelDroppingRank is public data of the Route Update Protocol.
8 The maximum power reduction for the active reverse CDMA channels carrying overhead
9 and data is gating off the Data and RRI Channels, DSC Channels, DRC Channels, ACK
10 Channels, and the Pilot Channels accordingly. The maximum power reduction of the Data
11 and RRI Channels corresponds to gating off the Data and RRI Channels. The maximum
12 power reduction of the DSC Channels shall correspond to transmitting the corresponding
13 DSC Channels with gain equal to DSCChannelGainBase, where DSCChannelGainBase is
14 public data of the Forward Traffic Channel MAC Protocol. If the DRC Channels are active,
15 power reduction of the DRC Channels shall occur only after the Data and RRI Channels
16 have been gated off and the DSC Channels are transmitted at a power level corresponding
17 to DSCChannelGain of DSCChannelGainBase. If the ACK Channels are active, power
18 reduction of the ACK Channels shall occur only after all the DRC Channels have been
19 gated off. Further power reduction of DSC Channels corresponds to gating off the DSC
20 Channels. If the DSC Channels are transmitted at DSCChannelGainBase, then power
21 reduction of the DSC Channels shall occur only after the ACK Channels have been gated
22 off. Power reduction of the Pilot Channels shall occur only after the DSC Channels have
23 been gated off. The power reduction shall be performed sequentially for each active reverse
24 CDMA channel carrying overhead and data in order of increasing
25 ReverseChannelDroppingRank starting with the active reverse CDMA channel with lowest
26 ReverseChannelDroppingRank.
27 For the active reverse CDMA channel with the highest value of
28 ReverseChannelDroppingRank, the maximum power reduction for the DSC Channels shall
29 correspond to transmitting the DSC Channels with gain equal to DSCChannelGainBase,
30 where DSCChannelGainBase is public data of the Forward Traffic Channel MAC Protocol.
31 The maximum power reduction for the DRC Channels corresponds to gating off the DRC
32 Channels. The maximum power reduction for the ACK Channels corresponds to gating off
33 the ACK Channels. If the DRC Channels are active, DRC Channel power reduction shall
34 occur only after the transmit power of the DSC Channels is reduced to a level
35 corresponding to DSCChannelGainBase. If the ACK Channels are active, ACK Channel
36 Power reduction shall occur only after the DRC Channels have been gated off.
37 The access terminal shall perform the power reduction within one slot of determining that
38 the access terminal is unable to transmit at the requested output power level.

41 shall adjust the mean output power level of the Pilot Channel corresponding to each active
42 reverse CDMA channel in response to each power-control bit received on the Reverse Power
43 Control (RPC) Channel of the associated forward CDMA channelforward CDMA channel of
12-23
1 the associated sub-active set. The nominal change in mean output power level of the Pilot
2 Channel per single power-control bit shall be set according to the RPCStep, which is public
3 data of the Reverse Traffic Channel MAC Protocol.
4 For the 1.0 dB step size, the change in mean output power level for an active reverse CDMA
5 channel per power-control bit shall be within ±0.5 dB of the nominal value (1 dB), and the
6 change in mean output power level for an active reverse CDMA channel per 10 power-
7 control bits of the same sign shall be within ±2.0 dB of 10 times the nominal change (10
8 dB). For the 0.5 dB step size, the change in mean output power level for an active reverse
9 CDMA channel per power-control bit shall be within ±0.3 dB of the nominal value (0.5 dB),
10 and the change in mean output power level for an active reverse CDMA channel per 20
11 power-control bits of the same sign shall be within ±2.5 dB of 20 times the nominal change
12 (10 dB). For the 1.5 dB step size, the change in mean output power level for an active
13 reverse CDMA channel per power-control bit shall be within ±0.5 dB of the nominal value
14 (1.5 dB), and the change in mean output power level for an active reverse CDMA channel
16 change (15 dB). For the 2.0 dB step size, the change in mean output power level for an
17 active reverse CDMA channel per power-control bit shall be within ±0.5 dB of the nominal
18 value (2.0 dB), and the change in mean output power level for an active reverse CDMA
19 channel per 10 power-control bits of the same sign shall be within ±4.0 dB of 10 times the
20 nominal change (20 dB). A ‘0’ power-control bit for an active reverse CDMA channel
21 requires the access terminal to increase transmit power for that reverse CDMA channel if
22 the transmit power differential between adjacent carriers does not exceed MaxRLTxPwrDiff,
23 and a ‘1’ power-control bit for an active reverse CDMA channel requires the access terminal
24 to decrease transmit power for that reverse CDMA channel. If the transmit power
25 differential between adjacent carriers exceeds MaxRLTxPwrDiff, then the access terminal
26 shall decrease the transmit power on one or more carriers such that the transmit power
27 differential between adjacent carriers does not exceed MaxRLTxPwrDiff. The access
28 terminal shall provide a closed-loop adjustment range for an active reverse CDMA channel
29 greater than ±24 dB around its open-loop estimate.
30 A ‘0’ power-control bit for an active reverse CDMA channel requires the access terminal to
31 increase transmit power for that reverse CDMA channel if the transmit power differential
32 between adjacent carriers does not exceed MaxRLTxPwrDiff. If the transmit power
33 differential between adjacent carriers exceeds MaxRLTxPwrDiff, the access terminal shall
34 decrease the transmit power for that reverse CDMA channel even if ‘0’ power-control bit is
35 received. A ‘1’ power-control bit for an active reverse CDMA channel requires the access
36 terminal to decrease transmit power for that reverse CDMA channel.
38 components or from different sectors for an active reverse CDMA channel during handoff.
12-24
1 13.3.1.2.4.312.3.1.2.4.3 Power Transition Characteristics

3 Following a step change in sum of the mean input powers, ΔPin, of all forward CDMA
4 channels associated with an assigned reverse CDMA channel the mean output Pilot
5 Channel power of the access terminal for that assigned reverse CDMA channel shall
6 transition to its final value in a direction opposite in sign to ΔPin, with magnitude contained
7 between the mask limits defined by161:
8 • Upper Limit:
11 • Lower Limit:

19 Following the reception of a closed-loop power-control bit for an active reverse CDMA
20 channel, the mean output power for the corresponding reverse CDMA channel of the access
21 terminal shall be within 0.3 dB and 0.15 dB of the final value in less than 500 μs for step
22 sizes of 1.0 dB and 0.5 dB, respectively, and within 0.3 dB of the final value in less than
23 500 μs for step sizes of 1.5 dB and 2 dB.

26 Anaccess network and access terminal that support this protocol shall support the
27 NoFeedbackMultiplexing mode162 and should support the BasicFeedbackMultiplexing
28 mode and the EnhancedFeedbackMultiplexing mode163.
162 In NoFeedbackMultiplexing mode each reverse CDMA channel carries the feedback channels for
the forward CDMA channels corresponding to at most one sub-Active Set.The minimum number of
forward and reverse CDMA channels in this mode is one.
163 In BasicFeedbackMultiplexing mode at least one of the reverse CDMA channel carries feedback
for forward CDMA channels corresponding to more than one sub-Active Set using unique long codes
for the feedback channels associated with forward CDMA channels corresponding to each sub-Active
12-25
3 Channel shall consist of one or more Pilot Channels, one or more Reverse Rate Indicator
4 (RRI) Channels, one or more Data Source Control (DSC) Channels, one or more Data Rate
5 Control (DRC) Channels, one or more Acknowledgment (ACK) Channels, and one or more
6 Data Channels. The Reverse Traffic Channel may also include one or more Auxiliary Pilot
7 Channels.
8 The Reverse Traffic Channel in NoFeedbackMultiplexing mode consists of reverse link
9 transmissions on one or more reverse CDMA channels using the same user long code,
10 where the assigned reverse CDMA channels are public data of the Route Update Protocol.
11 For NoFeedbackMultiplexing mode the user long code is public data of Reverse Traffic
12 Channel MAC Protocol. The Reverse Channel in BasicFeedbackMultiplexing mode consists
13 of one or more reverse CDMA channels. In BasicFeedbackMultiplexing mode the DRC,
14 ACK, and DSC channels corresponding to different forward CDMA channels are
15 multiplexed on to an associated reverse CDMA channel and transmitted using unique long
16 codes. In EnhancedFeedbackMultiplexing mode, each of the DRC, ACK, and DSC Channels
17 corresponding to different forward CDMA channels are multiplexed on to an associated
18 reverse CDMA channel and transmitted using unique long codes. In
19 EnhancedFeedbackMultiplexing mode, one unique long code is used for the DRC, ACK, and
20 DSC channel transmissions for up to four forward CDMA channels.
21 FeedbackMultiplexingIndex is public data of the Route Update Protocol and is composed of
22 the information as shown in Table 12.3.1.3.1-1.
23 Table 12.3.1.3.1-1. FeedbackMultiplexingIndex composition
FeedbackMultiplexingIndex bits Information
4 MSB’s LongCodeMaskMSBs
Bit positions 3, 4, and 5 DRCCoverOffset
2 LSB’s FeedbackMultiplexingMethod
24
25 For the BasicFeedbackMultiplexing mode and the EnhancedFeedbackMultiplexing mode, if

26 the LongCodeMaskMSBs corresponding to a forward CDMA channel equals ‘1111’ the long
27 code for the corresponding DRC, ACK, and DSC is public data of the Reverse Traffic
28 Channel MAC Protocol. For the BasicFeedbackMultiplexing mode and the
29 EnhancedFeedbackMultiplexing mode, if the LongCodeMaskMSBs corresponding to a
30 forward CDMA channel is not equal to ‘1111’ the long code for the corresponding DRC,
31 ACK, and DSC are generated by the Physical Layer Protocol.
32 The RRI Channel is used to indicate the payload size and the sub-packet identifier of the
33 physical layer packet transmitted on the Reverse Traffic Channel. The DSC Channel is used
Set. In EnhancedFeedbackMultiplexing mode at least one of the reverse CDMA channels carries
feedback for forward CDMA channels corresponding to up to four sub-Active Sets using one long
code.
12-26
1 by the access terminal to indicate to the access network the selected serving cell for one or
2 more forward CDMA channels on the Forward Channel. The DRC Channel is used by the
3 access terminal to indicate to the access network the requested Forward Traffic Channel
4 data rate and the selected serving sector corresponding to a forward CDMA channel on the
5 Forward Channel. The serving sector corresponding to a forward CDMA channel is the
6 sector that the access terminal selects for receiving the Forward Traffic Channel for that
7 forward CDMA channel. The serving cell corresponding to a forward CDMA channel is the
8 cell that contains the serving sector for that forward CDMA channel. The ACK Channel is
9 used by the access terminal to inform the access network whether or not the physical layer
10 packet transmitted on a forward CDMA channel of the Forward Traffic Channel has been
11 received successfully. The Auxiliary Pilot Channel is used by the access terminal to aid
12 reverse link channel estimation by the access network on a reverse CDMA channel. The
13 structure of the reverse link channels for the Access Channel shall be as shown in Figure
14 12.3.1.3.1-1, and the structure of the reverse link channels for the Reverse Traffic Channel
15 shall be as shown in Figure 12.3.1.3.1-2 through Figure 12.3.1.3.1-6. The structure of the
16 reverse link channels for the NoFeedbackMultiplexing mode is shown in Figure 12.3.1.3.1-
17 2,Figure 12.3.1.3.1-6, Figure 12.3.1.3.1-7. The structure of the reverse link channels for
18 the BasicFeedbackMultiplexing mode is shown in Figure 12.3.1.3.1-8. The structure of the
19 reverse link for the EnhancedFeedbackMultiplexing mode is shown in Figure 12.3.1.3.1-9
20 through Figure 12.3.1.3.1-15.
21 For the Access Channel, the RRI symbols shall not be transmitted. The Pilot Channel, the
22 RRI Channel, the DSC Channel, the DRC Channel, the ACK Channel, the Data Channel,
23 and the Auxiliary Pilot Channel shall be orthogonally spread by Walsh functions of length
24 2, 4, 8, 16, or 32 (see 12.3.1.3.8). For the BasicFeedbackMultiplexing mode, the DSC
25 Channel, the DRC Channel, and the ACK Channel for forward CDMA channels may be
26 multiplexed on an associated reverse CDMA channel using a unique long code. For the
27 EnhancedFeedbackMultiplexing mode the DSC Channel, the DRC Channel, and the ACK
28 Channel for up to four forward CDMA channels may be multiplexed on an associated
29 reverse CDMA channel using the same unique long code.
30 The Data Channel for each reverse CDMA channel shall be BPSK, QPSK, or 8-PSK
31 modulated and each modulated stream shall be covered by either a 4-ary Walsh function or
32 a 2-ary Walsh function. The Data Channel shall be B4 modulated (BPSK modulation with
33 4-ary Walsh cover), Q4 modulated (QPSK modulation with 4-ary Walsh cover), Q2
34 modulated (QPSK modulation with 2-ary Walsh cover), Q4Q2 modulated (sum of the Q4
35 and Q2 modulated symbols), or E4E2 modulated (sum of E4 (8-PSK modulated with 4-ary
36 Walsh cover), and E2 (8-PSK modulated with 2-ary Walsh cover) modulated symbols). Each
37 Reverse Traffic Channel shall be identified by a user long code specified by the
38 LongCodeMaskMSBs of the reverse CDMA channel associated with the forward CDMA
39 channel. The Access Channel for each sector shall be identified by a distinct Access
40 Channel long code.
41 The Access Channel frame and Reverse Traffic Channel frame shall be 26.66… ms in
42 duration. The zero offset frame boundary shall be aligned to the rollover of the short PN
12-27
1 codes (see 12.3.1.3.12.1). Each Reverse Traffic Channel frame164 shall consist of 16 slots or
2 four sub-frames and each sub-frame shall consist of 4-slots, with each slot 1.66… ms in
3 duration. Each slot contains 2048 PN chips. A sub-packet is the smallest unit of a Reverse
4 Traffic Channel transmission that can be acknowledged at the physical layer by the access
5 network. A sub-packet is transmitted over four contiguous slots. A sub-frame is a group of
6 four contiguous slots during which the access terminal may transmit a sub-packet. The
7 structure of the Reverse Traffic Channel sub-frame is shown in Figure 12.3.1.3.1-19. Each
8 physical layer packet can be transmitted in up to a maximum of four sub-packets. When
9 more than one sub-packet is transmitted on an active reverse CDMA channel, the
10 transmitted sub-packets shall use a three sub-frame interlacing. That is, the transmitted
11 sub-packets of a physical layer packet shall be separated by two intervening sub-frames,
12 and sub-packets of other physical layer packets may be transmitted in the sub-frames
13 between those transmitted sub-packets.
14 When the access terminal is transmitting a Reverse Traffic Channel on a reverse CDMA
15 channel, it shall continuously transmit the Pilot Channel and the RRI Channel on that
16 reverse CDMA channel if DTXMode is equal to ‘0’. The Pilot Channel for a reverse CDMA
17 channel shall be transmitted on Walsh channel W016 on that carrier. The RRI Channel for a
16
18 reverse CDMA channel shall be transmitted on Walsh channel W4 on that carrier. The DSC
32
19 Channel and the ACK Channel shall be time-division multiplexed on Walsh channel W12 .
20 For the NoFeedbackMultiplexing mode each DSC Channel corresponding to a forward
21 CDMA channel shall be transmitted on an associated reverse CDMA channel during the
32
22 second half slot on Walsh channel W12 on that reverse CDMA channel and shall be
23 repeated for DSCLength slots, where DSCLength is public data of the Forward Traffic
24 Channel MAC Protocol. For the BasicFeedbackMultiplexing mode each DSC Channel
25 corresponding to a forward CDMA channel shall be transmitted on an associated reverse
32
26 CDMA channel during the second half slot on Walsh channel W12 on that reverse CDMA
27 channel and shall be repeated for DSCLength slots, where DSCLength is public data of the
28 Forward Traffic Channel MAC Protocol.
29 For the EnhancedFeedbackMultiplexing mode if two DSC Channels corresponding to two
30 forward CDMA channels associated with one reverse CDMA channel are transmitted they
31 shall be transmitted on that reverse CDMA channel during the second half of the slot on
32
32 the I-branch or Q-branch on Walsh channel W12 and shall be repeated for DSCLength
33 slots, where DSCLength is public data of the Forward Traffic Channel MAC Protocol.
34 For the EnhancedFeedbackMultiplexing mode if three DSC Channels corresponding to
35 three forward CDMA channels associated with one reverse CDMA channel are transmitted,
36 then two of the DSC Channels shall be time-division multiplexed and transmitted on that
37 reverse CDMA channel during the second half of the slot on the I-branch on Walsh channel
38 W1232 and shall be repeated for DSCLength/2 slots. The other DSC Channel shall be
164 The start of a frame is specified by ( T − FrameOffset ) mod 16 = 0, where T is the CDMA System
Time in slots.
12-28
1 transmitted on that reverse CDMA channel during the second half of the slot on the Q-
32
2 branch on Walsh channel W12 and shall be repeated for DSCLength slots.
3 For the eEnhancedFeedbackMultiplexing mode if four DSC Channels corresponding to four

4 forward CDMA channels associated with one reverse CDMA channel are transmitted, then
5 two of the DSC Channels shall be time-division multiplexed and transmitted on that
6 reverse CDMA channel during the second half of the slot on the I-branch on Walsh channel
7 W1232 and shall be repeated for DSCLength/2 slots. The other two DSC Channels shall be
8 time-division multiplexed and transmitted on that reverse CDMA channel during the
32
9 second half of the slot on the Q-branch on Walsh channel W12 and shall be repeated for
10 DSCLength/2 slots.
11 For the NoFeedbackMultiplexing mode and the BasicFeedbackMultiplexing mode when
12 each DRC Channel is active (see 12.3.1.3.3.4), it shall be transmitted for a full slot duration
13 on Walsh channel W816 and repeated for DRCLength slots, where DRCLength is public data
14 of the Forward Traffic Channel MAC Protocol. For the EnhancedFeedbackMultiplexing
15 mode when the DRC Channel is active (see 12.3.1.3.3.4), it shall be transmitted for a full
16 slot duration on the Q-branch and may be transmitted for a full slot duration on the I-
2 2
17 branch using codeword Walsh function W0 or W1 on Walsh channel W816 and repeated for
18 DRCLength slots, where DRCLength is public data of the Forward Traffic Channel MAC
19 Protocol.
20 For the NoFeedbackMultiplexing mode and the BasicFeedbackMultiplexing mode the
21 access terminal shall transmit each ACK Channel bit in response to every Forward Traffic
22 Channel slot that is associated with a detected preamble directed to the access terminal on
23 the corresponding forward CDMA channel. Otherwise, the ACK Channel shall be gated off.
24 When the ACK Channel bit is transmitted, it shall be time-division multiplexed with the
32
25 DSC Channel and transmitted on the first half slot on Walsh channel W12 . For the
26 EnhancedFeedbackMultiplexing mode the access terminal shall transmit each ACK
27 Channel bit in response to every Forward Traffic Channel slot that is associated with a
28 detected preamble directed to the access terminal on the corresponding forward CDMA
29 channel. Otherwise, the ACK Channel shall be gated off. When the ACK Channel bit is
30 transmitted, it shall be time-division multiplexed with the DSC Channel and transmitted
31 on the I-branch and may be time-division multiplexed with the DSC Channel and
4 4 4 4
32 transmitted on the Q-branch using Walsh function W0 , W1 , W2 or W3 during the first
32
33 half slot on Walsh channel W12 . For the EnhancedFeedbackMultiplexing mode if the
34 access terminal transmits a single DSC Channel, the ACK Channel transmissions
35 corresponding to some forward CDMA channels may be time-division multiplexed with the
36 ACK Channel transmissions corresponding to other forward CDMA channels as shown in
37 Figure 12.3.1.3.1-18.
38 The access terminal shall transmit each Data Channel as specified by the Reverse Traffic
39 Channel MAC Protocol. When transmitting the Data Channel the access terminal shall
4 2
40 transmit the Data Channel on Walsh channel W2 or W1 , or both. The access terminal shall
41 transmit the Auxiliary Pilot Channel as specified by the Reverse Traffic Channel MAC
12-29
1 Protocol. When transmitting the Auxiliary Pilot Channel, the access terminal shall transmit
32
2 the Auxiliary Pilot Channel on Walsh channel W28 . The Walsh channel assignments for the
3 Physical Layer Reverse Traffic Channels are shown in Table 12.3.1.3.1-2.
5 Channel
Channel Walsh Channel
Pilot W016
Reverse Rate Indicator (RRI) W416

Data Source Control (DSC) W1232
Data Rate Control (DRC)
(Symmetric Multicarrier Mode and W816
BasicFeedbackMultiplexing Mode)
Data Rate Control (DRC) W02 and/or W12

(EnhancedFeedbackMultiplexing mode) followed by W816
ACK
(No FeedbackMultiplexing mode and W1232
BasicFeedbackMultiplexing mode)
ACK W04 , W14 , W24 or W34

32
(EnhancedFeedbackMultiplexing mode) followed by W12
Data W24 and/or W12

Auxiliary Pilot W2832
16 shown.
12-30
3 Figure 12.3.1.3.1-18 shows the EnhancedFeedbackMultiplexing mode of operation where
4 the ACK channel associated with the first forward CDMA channel is transmitted during the
5 second half of the slot and the ACK channel associated with the fifth forward CDMA
6 channel is transmitted during the first half of the slot as the DSC Channel is not
7 transmitted using the second long code. In this example, the Forward Traffic Channel
8 physical layer packet transmission is terminated normally, i.e., at nominal span, for the
9 first forward CDMA channel and is early terminated for the fifth forward CDMA channel.
10 Figure 12.3.1.3.1-20 shows an example of the packet extension operation for a (5120, 1,
11 64) packet transmission format. This transmission format has a termination target of one
12 slot and can be extended up to four slots. In this example the access terminal transmits a
13 NAK response on the ACK Channel after the first, second, and third slot of the physical
14 layer packet is received indicating that it was unable to correctly receive the Forward Traffic
15 Channel physical layer packet after the first, second, and third slot. The access network
16 transmits the second slot, third slot, and fourth slot as extension slots if
17 ExtendedSpansEnabled equals ‘1’. The access network transmits the second slot resulting
18 in a packet transmission format of (5120, 2, 64). The access network transmits the third
19 slot using the same data chips as the first slot and transmits the fourth slot using the
20 same data chips as the second slot. The access terminal soft-combines the data chips from
21 slot 3 with those received during slot 1 and the data chips from slot 4 with those received
22 from slot 2. An ACK or NAK is transmitted after the fourth slot is received, as shown.
23 Figure 12.3.1.3.1-21 shows an example of the packet extension operation for a (5120, 2,
24 64) packet transmission format. This transmission format has a termination target of two
25 slots and can be extended up to four slots. In this example the access terminal transmits a
26 NAK response on the ACK Channel after the first, second, and third slot of the physical
27 layer packet is received indicating that it was unable to correctly receive the Forward Traffic
28 Channel physical layer packet after the first, second, and third slot. The access network
29 transmits the third slot and the fourth slot as extension slots if ExtendedSpansEnabled
30 equals ‘1’. The access network transmits the third slot using the extension preamble and
31 the same data chips as the first slot and transmits the fourth slot using the same data
32 chips as the second slot. The access terminal soft-combines the data chips from slot 3 with
33 those received during slot 1 and the data chips from slot 4 with those received from slot 2.
34 An ACK or NAK is transmitted after the fourth slot is received, as shown.
38 The access terminal shall not forward the physical layer packet to a higher layer if the
12-31
W016 = ( + + + + + + + + + + + + + + + + )
W 24 = (+ + − − )
2 Figure 12.3.1.3.1-1. Reverse Channel Structure for the Access Channel
12-32
W016 = (+ + + + + + + + + + + + + + + +)
Signal Point
(All 0's) A
0 +1
1 -1
1.2288 Mcps
W2832 = (+ + + + − − − − − − − − + + + + − − − − + + + + + + + + − − − −)
Signal Point
Auxiliary Pilot Mapping
B
Channel (All 0's) 0 +1
1 -1
1.2288 Mcps
W416 = (+ + + + − − − − + + + + − − − −)
RRI Channel Signal Point
Bi- Codeword
(One 6-bit Symbol Mapping
Orthogonal Repetition C
per 4-slot Physical 0 +1
Encoder (Factor = 4)
Layer Subpacket) 1 -1
1.2288 Mcps
32 Binary
Symbols
per Slot
W1232 = (+ + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + +)
Symbol
ACK Channel ACK Signal
Repetition D
(1 Bit per Slot) Mapping
(Factor = 32)
1.2288 Mcps
32 Binary
Symbols
per Half Slot
W1232 = (+ + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + +)
Signal Point
DSC Channel
Mapping
(One 3-Bit Symbol Encoder E
0 +1
per Active Slot)
1 -1
1.2288 Mcps
32 Binary
Symbols
per Half Slot W816 = (+ + + + + + + + − − − − − − − −)
DRC Channel Signal Point

(One 4-Bit Symbol Bi- Codeword
Mapping
per Active Orthogonal Repetition F
0 +1
Slot) Encoder (Factor = 2)
1 -1
8 Binary 16 Binary
Symbols Symbols
DRC Cover Symbols per Active Slot per Active Slot Walsh
(One 3-Bit Symbol Cover
per Active
Wi8 i = 0,1,...7
Slot)
Data
G
Data Channel Interleaved (I)
Channel
(Physical Layer Encoder Packet Modulator
Interleaver
Packets) Repetition Data
H
(Q)
1.2288 Mcps
Scrambler
2 Figure 12.3.1.3.1-2. Subtype 3 Physical Layer Protocol NoFeedbackMultiplexing mode

3 Reverse Channel Structure for the Reverse Traffic Channel for single carrier
4 operation (Part 1 of 5)
12-33
W24 = (+ + − −)
W24 = (+ + − −)
W24 = (+ + − −)
W12 = (+ −)
W12 = (+ −)
12-34
W24 = (+ + − −) 1
3
1
W24 = (+ + − −) 3
W12 = (+ −) 2
3
2
W12 = (+ −) 3
12-35
W24 = (+ + − −) 1
3
1 Symbol 4 Chips
E4I
First 3 Code
Symbols 8-PSK
Modulator
E4Q
1 Symbol 4 Chips
1
W24 = (+ + − −) 3
9 Code
Demux
Symbols
W12 = (+ −) 2
3
2 Symbols 4 Chips
E2I
8-PSK
Last 6 Code Mapping
Symbols
E2Q
2 Symbols 4 Chips
2
W12 = (+ −) 3
E4I
Data I
G
E2I
E4Q
Data Q
H
E2Q
E4E2 modulation
2
12-36

3 Reverse Channel Structure for the Reverse Traffic Channel for single carrier
4 operation (Part 5 of 5)
12-37
cos(2 fC,1t)
I I’ Baseband
Reverse Carrier # 1 Filter
Pilot, Auxiliary Pilot, Quadrature s1(t)
RRI, DRC, ACK, DSC, Spreading
Data Channels Baseband
Q Q’
Filter
UQ sin(2 fC,1t)
UI Q-Channel
I-Channel User Long-Code
User Long-Code PN Sequence
PN Sequence
cos(2 fC,2t)
I I’ Baseband
Reverse Carrier # 2 Filter
Pilot, Auxiliary Pilot, Quadrature s2(t)
Q Q’
Filter
UQ sin(2 fC,2t)
UI Q-Channel
PN Sequence
cos(2 fC,Nt)
I I’ Baseband
Reverse Carrier # N Filter
Pilot, Auxiliary Pilot, Quadrature sN(t)
Q Q’
Filter
UQ sin(2 fC,Nt)
UI Q-Channel
PN Sequence
1

3 Reverse Channel Structure for the Reverse Traffic Channel for Multicarrier operation
12-38
Reverse Channels
(Pilot, Data, RRI,
Auxiliary Pilot) I I1
+ Quadrature Spreading
Q
Reverse Overhead
Channels cos(2 fCt)
(DRC, ACK, DSC)
for Forward Link UI1 UQ1
carrier # 1
Q1 I’ Baseband
I2
Filter
Reverse Overhead
Channels – I
Forward Link Quadrature Spreading s(t)
Q
carriers # 2
(DRC, ACK, DSC)
Q2 Baseband
Q’
UI2 UQ2 IN Filter
sin(2 fCt)
Reverse Overhead
I
Channels – Fwd Quadrature Spreading
Link N Q QN
(DRC, ACK, DSC)
UIN UQN
1
2 Figure 12.3.1.3.1-8. BasicFeedbackMultiplexing Mode Transmission (N forward CDMA

3 channels with 1 Reverse CDMA channel)
W816 = (+ + + + + + + + − − − − − − − −)
W02
Wi8 i = 0,1,...7
W816 = (+ + + + + + + + − − − − − − − −)
W02
W j8 j = 0,1,...7
5
6 Figure 12.3.1.3.1-9. EnhancedFeedbackMultiplexing Mode DRC Channel

7 Transmission (2 Forward CDMA channels with 1 Reverse CDMA channel)
12-39
Wi8 i = 0,1,...7
W12
W816 = (+ + + + + + + + − − − − − − − −)
W02
Wi8 i = 0,1,...7
W j8 j = 0,1,...7
W12
W816 = (+ + + + + + + + − − − − − − − −)
W02
W j8 j = 0,1,...7
2
3 Figure 12.3.1.3.1-10. EnhancedFeedbackMultiplexing Multicarrier Mode DRC

4 Channel Transmission (4 Forward CDMA channels with 1 Reverse CDMA channel)
W1232 = (+ + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + +)
ACK Channel ACK Symbol ACK

(1 Bit per Slot) Walsh Cover
Signal Repetition Channel I
Carrier 1 Mapping (Factor = 8) W04 Gain
32 Binary Symbols per Half Slot
W1232 = (+ + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + +)

Signal Repetition Channel Q
32 Binary
Symbols
7 per Half Slot

10
12-40
W1232 = (+ + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + +)
Signal Repetition Channel

Signal Repetition Channel I
32 Binary
Symbols
per Half Slot
W1232 = (+ + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + +)
Signal Repetition Channel

Signal Repetition Channel Q
32 Binary
Symbols
1 per Half Slot

W1232 = ( + + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + + )
Signal Point
DSC Channel 1
Mapping
(One 3-Bit Symbol Encoder I
0 +1
per Active Slot)
1 -1
1.2288 Mcps
32 Binary
Symbols
per Half Slot
W1232 = ( + + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + + )
Signal Point
DSC Channel 2
Mapping
(One 3-Bit Symbol Encoder Q
0 +1
per Active Slot)
1 -1
1.2288 Mcps
32 Binary
Symbols
5 per Half Slot

7 Transmission (2 independent DSC Channel Transmissions with 1 Reverse CDMA
8 channel)
12-41
W1232 = ( + + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + + )
W1232 = ( + + + + − − − − − − − − + + + + + + + + − − − − − − − − + + + + )

3 Transmission (4 independent DSC Channel Transmissions with 1 Reverse CDMA
4 channel)
Reverse Channels
(Pilot, Data, RRI, Data,
Auxiliary Pilot) I I1
+ Quadrature Spreading
Q
Reverse Overhead
Channels cos(2 fCt)
(DRC, ACK, DSC)
DRC, ACK for FL UI1 UQ1
carriers 1-4
Q1 Baseband
I2 I’
Reverse Overhead Filter
Channels –
I
Fwd Link carriers 5-8 Quadrature Spreading s(t)
(DRC, ACK, DSC) Q
with offset ACK (if DSC
not transmitted)
Q2 Baseband
Q’
UI2 UQ2 I4 Filter
sin(2 fCt)
Reverse Overhead
Channels – Fwd Link
I
13-16 Quadrature Spreading
(DRC, ACK, DSC) Q Q4
with offset ACK (if DSC
not transmitted)
UI4 UQ4
6
7 Figure 12.3.1.3.1-15. EnancedFeedbackMultiplexing Mode Transmission (16 forward

8 CDMA channels with 1 Reverse CDMA channel)
10
11
12
13
12-42

Channel Physical
Layer Packet
Transmissions
with 153.6 kbps
DRC Channel
Transmission
Requesting
153.6 kbps
DRC
Request for
ACK Channel
Half-Slot
Transmissions
NAK NAK NAK ACK
One Slot
or
2 NAK
4 Normal Termination

Transmission

Forward Traffic
Channel Physical
Layer Packet
Transmissions
with 153.6 kbps
DRC Channel
Transmission
Requesting
153.6 kbps
DRC
Request for
ACK Channel
Half-Slot
Transmissions
NAK NAK ACK

One Slot
5
7 Early Termination
12-43
3 early Termination on one carrier and normal termination on another carrier for
4 EnhancedFeedbackMultiplexing mode with single DSC transmission and offset ACK
5 transmission
8 Figure 12.3.1.3.1-19. NoFeedbackMultiplexing mode Reverse Traffic Channel Sub-

9 frame Structure with single carrier
12-44
Transmit Slot 3
(extension)
Transmit Slot 2 Extension Transmit Slot 4
Transmit Slot 1 (extension) Preamble Tx (extension)
Tx Format Tx Format Same as Same as
Forward Traffic (5120, 1, 64) (5120, 2, 64) Transmit Slot 1 Transmit Slot 2
Channel Physical
Layer Packet
Transmission
Format
(5120, 1, 64) Slots n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n + 9 n + 10 n + 11 n + 12 n + 13 n + 14 n + 15
DRC Channel
Transmission
Requesting
3.1 Mbps
DRC
Request for
3.1 Mbps One-Half Slot Offset
ACK Channel
Half-Slot
Transmissions
NAK NAK NAK ACK
One Slot
or
1 NAK
3 Packet Extension with DRC request corresponding to a 1-slot termination target
Transmit Slot 3
(extension)
Extension Transmit Slot 4
Transmit Slot 1 Transmit Slot 2 Preamble Tx (extension)
Tx Format (5120, Tx Format Same as Transmit Same as Transmit
Forward Traffic 1, 64) (5120, 2, 64) Slot 1 Slot 2
Channel Physical
Layer Packet
Transmission
Format
(5120, 2, 64) Slots n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n+9 n + 10 n + 11 n + 12 n + 13 n + 14 n + 15
DRC Channel
Transmission
Requesting
1.5 Mbps
DRC
Request for
1.5 Mbps One-Half Slot Offset
ACK Channel
Half-Slot
Transmissions
NAK NAK NAK ACK
One Slot
or
4 NAK
6 Packet Extension with DRC request corresponding to a 2-slot termination target

8 The modulation parameters for the Access Channel and the Reverse Traffic Channel for
9 each reverse CDMA channel shall be as specified in Table 12.3.1.3.1.1-1 and Table
10 12.3.1.3.1.1-2, respectively.
12-45
1 Table 12.3.1.3.1.1-1. Modulation Parameters for the Access Channel
Data Rate (kbps)

Parameter 9.6 19.2 38.4

Bits per Physical
256 512 1,024
Layer Packet
Physical Layer
Packet Duration 26.66… 26.66… 26.66…
(ms)
Code Rate 1/4 1/4 1/4
Code Symbols per
Physical Layer 1,024 2,048 4,096
Packet
Code Symbol Rate
38.4 76.8 153.6
(ksps)
Interleaved Packet
8 4 2
Repeats
Modulation Symbol
307.2 307.2 307.2
Rate (ksps)
Modulation Type BPSK BPSK BPSK
PN Chips per
Physical Layer 128 64 32
Packet Bit
2
3 The modulation parameters of the Reverse Traffic Channel shall be as specified in Table
4 12.3.1.3.1.1-2.
12-46
1 Table 12.3.1.3.1.1-2. Modulation Parameters for the Reverse Traffic Channel
Payloa Modulation Effective Data Rate (kbps) Effective Code Rate

d Size [Repetition]
(bits)
After After After After After After After After
4 8 12 16 4 8 12 16
Slots Slots Slots Slots Slots Slots Slots Slots
128 B4 19.2 9.6 6.4 4.8 1/5 1/5 1/5 1/5

[3.2] [6.4] [9.6] [12.8]
256 B4 38.4 19.2 12.8 9.6 1/5 1/5 1/5 1/5
[1.6] [3.2] [4.8] [6.4]
512 B4 76.8 38.4 25.6 19.2 1/4 1/5 1/5 1/5
[1] [1.6] [2.4] [3.2]
768 B4 115.2 57.6 38.4 28.8 3/8 1/5 1/5 1/5
[1] [1.07] [1.6] [2.13]
1024 B4 153.6 76.8 51.2 38.4 1/2 1/4 1/5 1/5
[1] [1] [1.2] [1.6]
1536 Q4 230.4 115.2 76.8 57.6 3/8 1/5 1/5 1/5
[1] [1.07] [1.6] [2.13]
2048 Q4 307.2 153.6 102.4 76.8 1/2 1/4 1/5 1/5
[1] [1] [1.2] [1.6]
3072 Q2 460.8 230.4 153.6 115.2 3/8 1/5 1/5 1/5
[1] [1.07] [1.6] [2.13]
4096 Q2 614.4 307.2 204.8 153.6 1/2 1/4 1/5 1/5
[1] [1] [1.2] [1.6]
6144 Q4Q2 921.6 460.8 307.2 230.4 1/2 1/4 1/5 1/5
[1] [1] [1.2] [1.6]
8192 Q4Q2 1228.8 614.4 409.6 307.2 2/3 1/3 2/9 1/5
[1] [1] [1] [1.2]
12288 E4E2 1843.2 921.6 614.4 460.8 2/3 1/3 1/3 1/3
[1] [1] [1.5] [2]
2
3 13.3.1.3.1.212.3.1.3.1.2 Data Rates

4 The access terminal shall transmit information on the Access Channel at a data rate of 9.6
5 kbps, 19.2 kbps, or 38.4 kbps.
6 The access terminal shall transmit information on the Reverse Traffic Channel for each
7 active reverse CDMA channel at a variable data rate ranging from 4.8 kbps to 1843.2 kbps
8 as shown in Table 12.3.1.3.1.1-2 with the maximum physical layer packet size for each
9 active reverse CDMA channel specified by MaxPacketSize, which is public data of the
10 Reverse Traffic Channel MAC Protocol. The peak data rate for each active reverse CDMA
12-47
1 channel is the data rate achieved by transmitting the MaxPacketSize with a termination
2 target of 1 sub-frame.
3 13.3.1.3.212.3.1.3.2 Access Channel

6 consists of a Pilot Channel and a Data Channel as shown in Figure 12.3.1.3.2-1.
13 equal to that of the data portion transmitted at 9.6 kbps as shown in Figure 12.3.1.3.2-1.
14 The preamble length is specified by the parameter PreambleLength or the parameter
15 PreambleLengthSlots which are public data from the Access Channel MAC Protocol. The
16 Access Channel physical layer packets are transmitted at data rates of 9.6, 19.2, or 38.4
17 kbps.
18

20 kbps
12-48

3 or 38.4 kbps
4 13.3.1.3.2.112.3.1.3.2.1 Pilot Channel

7 transmission. It is transmitted on the I channel using the 16-chip Walsh function number
8 0 ( W016 = + + + + + + + + + + + + + + + +) cover.
9 13.3.1.3.2.212.3.1.3.2.2 Data Channel

11 Channel during every access probe. The Access Channel physical layer packets are
12 transmitted at data rates of 9.6 kbps, 19.2 kbps, or 38.4 kbps on the Q-branch using the
13 4-chip Walsh function number 2 ( W24 = + + – –). The Access Channel physical layer packets
14 shall be preceded by a preamble of PreambleLength frames or PreambleLengthSlots slots
15 where only the Pilot Channel is transmitted. The PreambleLength parameter and the
16 PreambleLengthSlots parameter are public data from the Access Channel MAC Protocol.
17 13.3.1.3.312.3.1.3.3 Reverse Traffic Channel

19 or signaling information to the access network. When transmitting a single reverse CDMA
20 channel in NoFeedbackMultiplexing mode, the Reverse Traffic Channel consists of a Pilot
21 Channel, an RRI Channel, a DSC Channel, a DRC Channel, an ACK Channel, and a Data
22 Channel. When transmitting a single reverse CDMA channel in NoFeedbackMultiplexing
23 mode, the Reverse Traffic Channel may also include an Auxiliary Pilot Channel. When
24 transmitting a single reverse CDMA channel in BasicFeedbackMultiplexing mode or
12-49
1 EnhancedFeedbackMultiplexing mode165 the Reverse Traffic Channel may include

2 additional DRC Channels, ACK Channels, and DSC Channels.
3 The access terminal supports transmission of information on the Data Channel of the
4 Reverse Traffic Channel for each active reverse CDMA channel at a variable data rate
5 ranging from of 4.8 kbps to 1843.2 kbps as shown in Table 12.3.1.3.1.1-2 with the
6 maximum physical layer packet size for each active reverse CDMA channel as specified by
7 MaxPacketSize, which is public data of the Reverse Traffic Channel MAC Protocol. The peak
8 data rate for each active reverse CDMA channel is the data rate achieved by transmitting
9 the MaxPacketSize with a termination target of 1 sub-frame. The data rate used on the
10 Data Channel for each active reverse CDMA channel is specified by the Reverse Traffic
11 Channel MAC Protocol. The gain of the Data Channel relative to that of the Pilot Channel
12 for the Reverse Traffic Channel for each active reverse CDMA channel depends on the T2P
13 (traffic-to-pilot power ratio) profile for the transmitted payload size and the transmission
14 mode of the packet. The T2P profile for each payload size and transmission mode for each
15 active reverse CDMA channel are determined by the Reverse Traffic Channel MAC Protocol
16 (see Table 9.12.6.1.6.1-2). The Reverse Traffic Channel MAC Protocol supports two
17 transmission modes for each active reverse CDMA channel, the High Capacity mode and
18 the Low Latency mode. Each transmission mode is characterized by a physical layer
19 transmit duration of one, two, three or four sub-packets. The T2P profile is defined for each
20 payload size for each transmission mode and is characterized by the T2P transition. The
21 T2P transition is the number of sub-packets of a Reverse Traffic Channel packet
22 transmitted from the beginning of the transmission prior to a change in the T2P.
23 13.3.1.3.3.112.3.1.3.3.1 Pilot Channel

25 Pilot Channel. It is transmitted on the I channel using the 16-chip Walsh function number
26 0 ( W016 = + + + + + + + + + + + + + + + +) cover.

28 The RRI Channel is used by the access terminal to indicate the payload size and sub-
29 packet identifier of the physical layer packet transmitted on the Data Channel for each
30 active reverse CDMA channel.
31 The transmitted payload size for each active reverse CDMA channel shall be a 4-bit symbol
32 as shown in Table 12.3.1.3.3.2-1. The sub-packet identifier shall be a 2-bit symbol as
33 shown in Table 12.3.1.3.3.2-2. The 6-bit RRI symbol shall be formed using the 4-bit symbol
34 representing the payload size and the 2-bit symbol representing the sub-packet identifier. A
35 32-dimensional bi-orthogonal signal constellation shall be used to encode the 6-bit RRI
36 symbols. The bi-orthogonal signal constellation shall be assigned based on the payload size
37 and the sub-packet identifier. The Walsh function used to represent the RRI shall be based
38 on the payload index i and sub-packet index j as shown in the following equations:
165 Feedback multiplexing is required when the number of assigned sub-Active Sets is greater than
the number of reverse CDMA channels.
12-50
32
W 2×i + ⎣ j / 2 ⎦ if j = odd
W232×i + ⎣ j / 2 ⎦ if j = even
1
2 The bi-orthogonal codeword shall be repeated four times. The resulting symbols are
16
3 covered with the 16-chip Walsh Channel W . The RRI Channel is transmitted on the in-
4
4 phase (I) channel. The access terminal shall set the payload index to 0x0 and sub-packet
5 index to 0 to indicate a null-rate RRI.
6 Table 12.3.1.3.3.2-1. Payload Size to Payload Index Mapping
Payload Size Payload Index

(bits)
0 0x0
128 0x1
256 0x2
512 0x3
768 0x4
1024 0x5
1536 0x6
2048 0x7
3072 0x8
4096 0x9
6144 0xa
8192 0xb
12288 0xc
Reserved 0xd
Reserved 0xe
Reserved 0xf
7
8 Table 12.3.1.3.3.2-2. Sub-packet Identifier to Sub-packet Index Mapping
Sub-packet Sub-packet
Identifier Index
0 0x0
1 0x1
2 0x2
3 0x3
9
12-51
1 13.3.1.3.3.312.3.1.3.3.3 Data Source Control Channel

2 The access terminal uses a DSC Channel to indicate to the access network the selected
3 serving cell on the forward link for one or more forward CDMA channels. The serving cell
4 for one or more forward CDMA channels is indicated by the DSC value (3-bit value as
5 specified in Table 12.3.1.3.3.3-3) for that cell. The DSC value takes effect one slot after the
6 end of its transmission and stays in effect for DSCLength slots, where DSCLength is public
7 data of the Forward Traffic Channel MAC Protocol.
8 The DSC Channel data rate shall be as specified in Table 12.3.1.3.3.3-1, where N is the
9 number of sub-Active Sets and M is the number of DSC values for N sub-Active Sets
10 Table 12.3.1.3.3.3-1. DSC Channel Data Rate
Number of Forward Number of

CDMA channels DSC Values DSC Channel
Mode associated with a data rate (per
Single Reverse sec)
CDMA channel
1 1 per reverse
600/DSCLength
NoFeedbackMultiplexing CDMA channel
N (N ≤ 16) M≤N
600/DSCLength
BasicFeedbackMultiplexing
N (N ≤ 16) M≤N 600/DSCLength
max of 4 per long or
code 600/(DSCLengt
EnhancedFeedbackMultiplexing
h/2)
11 The DSC values shall be block encoded to yield 32-bit codewords, as specified in Table
12 12.3.1.3.3.3-3. The DSC value is repeated for DSCLength consecutive slots. Each bit of the
32
13 codeword is spread by a 32-ary Walsh function W12 . The DSC Channel is transmitted on
14 the in-phase (I) Channel as shown in Figure 12.3.1.3.1-6.
15 For NoFeedbackMultiplexing mode, each DSC Channel shall be transmitted during the
32
16 second half of each slot on the I-branch using Walsh function W12 as shown in Figure
17 12.3.1.3.1-2.
18 For BasicFeedbackMultiplexing mode, the DSC Channels associated with multiple forward
19 CDMA channels may be transmitted on a single reverse CDMA channel as shown in Figure
20 12.3.1.3.1-8. Each DSC Channel corresponding to a forward CDMA channel is transmitted
21 on the associated reverse CDMA channel during the second half of each slot on the I-
22 branch and spread using a long code mask that is specified by the LongCodeMaskMSBs.
23 All DSC Channel transmissions for forward CDMA channels associated with a reverse
24 CDMA channel are code division multiplexed and transmitted during the second half of
12-52
1 the slot on that reverse CDMA channel. The assigned forward CDMA channels and the
2 reverse CDMA channels are public data of the Route Update Protocol.
3 For EnhancedFeedbackMultiplexing mode, the DSC Channels associated with forward
4 CDMA channels may be transmitted on a single reverse CDMA channel as shown in Figure
5 12.3.1.3.1-13, and Figure 12.3.1.3.1-14.
6 If the value of the FeedbackMultiplexingMethod associated with the forward CDMA channel
7 is equal to ‘00’ and the DSC Channel is transmitted, then the DSC Channel shall be
8 transmitted using a long code mask specified by LongCodeMaskMSBs during the second
9 half of each slot on the I-branch.
11 is equal to ‘01’ and the DSC Channel is transmitted, then the DSC Channel shall be
12 transmitted using a long code mask specified by LongCodeMaskMSBs during the second
13 half of each slot on the Q-branch.
15 is equal to ‘10’ and the DSC Channel is transmitted, then the DSC Channel shall be time
16 division multiplexed with the DSC Channel associated with the forward CDMA channel
17 with the value of FeedbackMultiplexingMethod equal to ‘00’. These two DSC Channels shall
18 be transmitted using a long code mask specified by LongCodeMaskMSBs during the second
19 half of each slot T such that T mod 2 = 0 on the I-branch, where T is the CDMA System
20 Time in slots.
22 is equal to ‘11’', and the DSC Channel is transmitted, then the DSC Channel shall be time
23 division multiplexed with the DSC Channel associated with the forward CDMA channel
24 with the value of FeedbackMultiplexingMethod equal to ‘01’. These two DSC Channels shall
25 be transmitted using a long code mask specified by LongCodeMaskMSBs during the second
26 half of each slot T such that T mod 2 = 1 on the Q-branch. DSC Channel transmission for
27 different values of FeedbackMultiplexingMethod are summarized in Table 12.3.1.3.3.3-2.
28 Table 12.3.1.3.3.3-2. DSC Channel transmission and FeedbackMultiplexingMethod
FeedbackMultiplexingMethod DSC Channel transmission

‘00’ Second half of each slot on the I-branch
‘01 Second half of each slot on the Q-branch
Time multiplexed with DSC Channel with
FeedbackMultiplexingMethod = ‘00’ during 2nd half
‘10’
of each slot such that T mode 2 = 0 on the I-
branch
Time multiplexed with DSC Channel with
FeedbackMultiplexingMethod = ‘01’ during 2nd half
‘11’
of each slot such that T mode 2 = 1 on the Q-
branch
29 The timing of the Forward Traffic Channel transmission corresponding to a DSC symbol
30 shall be as specified by the Forward Traffic Channel MAC Protocol. Figure 12.3.1.3.3-1
12-53
1 shows transmission of DSC symbols based on the Forward Traffic Channel MAC Protocol.
2 Figure 12.3.1.3.3-1 shows an example of the DSC Channel timeline for a DRCLength of two
3 slots and DSCLength of eight slots.
4 Table 12.3.1.3.3.3-3. DSC Encoding
DSC Value Codeword
0x0 00000000000000000000000000000000
0x1 01011010101101010110101011010101
0x2 00110110011011001101100110110011
0x3 01101100110110011011001101100110
0x4 11110001111000111100011110001111
0x5 10101011010101101010110101011010
0x6 11000111100011110001111000111100
0x7 10011101001110100111010011101001
5
12-54
DRCLength =
2 slots
1 slot ½ slot
DSC m1 DSC m DSC m+1
DSCLength = 8 slots DSCLength = 8 slots
Period of Validity of DSC m1 Period of Validity of DSC m
1 slot
½ slot
A D A D A D A D A DA D A D A D
C S C S C S C S C S C S C S C S
K C K C K C K C K C K C K C K C
D D D D
R R R R
C C C C
Change of DRC Cover

1
2 Figure 12.3.1.3.3-1. DSC Channel Timeline (NoFeedbackMultiplexing Mode and

3 BasicFeedbackMultiplexing Mode)
4 Figure 12.3.1.3.3-1 shows the transmission of DSC symbols based on the Forward Traffic
5 Channel MAC Protocol for the NoFeedbackMultiplexing mode and
6 BasicFeedbackMultiplexing mode. Figure 12.3.1.3.3-2 shows the transmission of DSC
7 symbols based on the Forward Traffic Channel MAC Protocol for
8 EnhancedFeedbackMultiplexing Mode. Figure 12.3.1.3.3-2 shows an example of the DSC
9 Channel timeline for a DRCLength of two slots and DSCLength of eight slots with
10 EnhancedFeedbackMultiplexing mode, four forward CDMA channels with four independent
11 DSC per carrier where DSC Channels with value of FeedbackMultiplexingMethod to ‘00’
12 and ‘10’ are transmitted time division multiplexed on the I-branch and the DSC Channels
13 with value of FeedbackMultiplexingMethod equal to ‘01’ and ‘11’ are transmitted time
14 division multiplexed on the Q-branch. The example shows the time division multiplex
15 transmission of DSC Channels with value of FeedbackMultiplexingMethod equal to ‘00’ and
16 ‘10’.
17
12-55
2 Figure 12.3.1.3.3-2. DSC Channel Timeline (EnhancedFeedbackMultiplexing mode

3 with time division multiplexing of two DSC Channel transmissions)

6 selected serving sector and the requested data rate on the Forward Traffic Channel for the
7 forward CDMA channel. The requested Forward Traffic Channel data rate is mapped into a
8 four-bit DRC value and 3-bit sector cover as specified by the Forward Traffic Channel MAC
9 Protocol. An 8-ary Walsh function corresponding to the DRCCover or the AuxDRCCover of
10 the selected serving sector and DRC value range (MSB of DRC value equal to zero or equal
11 to one) for the forward CDMA channel is used to spread the DRC Channel transmission.
12 The cover mapping for each forward CDMA channel of each sector is defined by the public
13 data DRCCover and AuxDRCCover from the Forward Traffic Channel MAC Protocol. An
14 access terminal shall transmit DRC values greater than 0xf only if it is assigned an
15 auxiliary DRC cover, AuxDRCCover, associated with the corresponding forward CDMA
16 channel.
12-56
3 For NoFeedbackMultiplexing mode, the DRC values for each forward CDMA channel shall
4 be block encoded to yield 8-bit bi-orthogonal codewords, as specified in Table 12.3.1.3.3.4-
5 2. Each DRC codeword shall be transmitted twice per slot. Each bit of a repeated codeword
6 shall be spread by an 8-ary Walsh function Wi8 as defined in Table 12.3.1.3.3.4-3, where i
7 equals DRCCover or AuxDRCCover. Each Walsh chip of the 8-ary Walsh function is further
8 spread by the Walsh function W816 . Each DRC value shall be transmitted over DRCLength
9 slots when the DRC Channel is continuously transmitted.
16 For NoFeedbackMultiplexing mode, each DRC Channel shall be transmitted on the Q-
17 branch as shown in Figure 12.3.1.3.1-6.
20 DRC symbols shall start at the mid-slot point. For BasicFeedbackMultiplexing mode, the
21 DRC Channels associated with multiple forward CDMA channels may be transmitted on a
22 reverse CDMA channel as shown in Figure 12.3.1.3.1-8. Each DRC Channel is transmitted
23 on the Q-branch and spread using a long code mask that is specified by the
24 LongCodeMaskMSBs,. All DRC Channel transmissions for forward CDMA channels
25 associated with a reverse CDMA channel corresponding to the
26 FeedbackReverseChannelIndex are code division multiplexed and transmitted on that
27 reverse CDMA channel.
28 For EnhancedFeedbackMultiplexing mode, the DRC Channels associated with multiple
29 forward CDMA channels may be transmitted on a reverse CDMA channel corresponding to
30 the FeedbackReverseChannelIndex as shown in Figure 12.3.1.3.1-9 and Figure 12.3.1.3.1-
31 10.
32 If the value of the FeedbackMultiplexingMethod corresponding to the forward CDMA
33 channel is equal to ‘00’, then the DRC Channel shall be transmitted on the associated
34 reverse CDMA channel, FeedbackReverseChannelIndex, using a long code mask specified
2
35 by the LongCodeMaskMSBs using codeword Walsh cover W0 on the Q-branch.

37 channel is equal to ‘01’, then the DRC Channel shall be transmitted on the associated
38 reverse CDMA channel, FeedbackReverseChannelIndex, using a long code mask specified
2
39 by the LongCodeMaskMSBs using codeword Walsh cover W0 on the I-branch.

41 channel is equal to ‘10’, then the DRC Channel shall be code division multiplexed using
12-57
2
1 codeword Walsh cover W1 and transmitted on the associated reverse CDMA channel,
2 FeedbackReverseChannelIndex, using a long code mask specified by the
3 LongCodeMaskMSBs on the Q-branch.
4 If the value of the FeedbackMultiplexingMethod corresponding forward CDMA channel is
5 equal to ‘11’, then the DRC Channel shall be code division multiplexed using codeword
6 Walsh cover W12 and transmitted on the associated reverse CDMA channel,
7 FeedbackReverseChannelIndex, using a long code mask specified by the
8 LongCodeMaskMSBs on the I-branch. DSC Channel transmission for different values of
9 FeedbackMultiplexingMethod are summarized in Table 12.3.1.3.3.4-1.
10 Table 12.3.1.3.3.4-1. DRC Channel transmission and FeedbackMultiplexingMethod
FeedbackMultiplexingMethod DRC Channel transmission

2
‘00’ Codeword Walsh cover W0 on the Q-branch
2
‘01 Codeword Walsh cover W0 on the I-branch
2
‘10’ Codeword Walsh cover W1 on the Q-branch
2
‘11’ Codeword Walsh cover W1 on the I-branch
11
12 For EnhancedFeedbackMultiplexing mode, the DRC values shall be block encoded to yield
13 8-bit bi-orthogonal codewords, as specified in Table 12.3.1.3.3.4-2. Each DRC codeword
14 shall be spread by a 2-ary Walsh function as defined in Table 12.3.1.3.3.4-4. The codeword
15 Walsh covered DRC shall be spread by an 8-ary Walsh function Wi8 as defined in Table
16 12.3.1.3.3.4-3, where i equals DRCCover or AuxDRCCover. The 8-ary Walsh function shall
17 be determined by adding the value of the DRCCover to the value of DRCCover offset
18 specified by DRCCoverOffset. Each Walsh chip of the 8-ary Walsh function is further
19 spread by the Walsh function W816 . Each DRC value shall be transmitted over DRCLength
20 slots when the DRC Channel is continuously transmitted.
23 DRC symbols shall start at the mid-slot point. The timing for the Forward Traffic Channel
24 MAC Protocol for non-gated and gated transmissions are shown in Figure 12.3.1.3.3.4-1
25 and Figure 12.3.1.3.3.4-2, respectively.
12-58
DRC Value Codeword
0x0 00000000
0x1 11111111
0x2 01010101
0x3 10101010
0x4 00110011
0x5 11001100
0x6 01100110
0x7 10011001
0x8 00001111
0x9 11110000
0xA 01011010
0xB 10100101
0xC 00111100
0xD 11000011
0xE 01101001
0xF 10010110
2
W08 0000 0000
W18 0101 0101
W28 0011 0011
W38 0110 0110
W48 0000 1111
W58 0101 1010
W68 0011 1100
W78 0110 1001

4
12-59
W02 00
W12 01
2
One Slot
DRC Channel
Transmission
a) DRCLength = 1

DRC Channel
Transmission
b) DRCLength = 2

DRC Channel
Transmission
c) DRCLength = 4

DRC Channel
Transmission
d) DRCLength = 8
3
12-60
One Slot
DRC Channel
Transmission
a) DRCLength = 2

DRC Channel
Transmission
b) DRCLength = 4

DRC Channel
Transmission
c) DRCLength = 8
1
3 13.3.1.3.3.512.3.1.3.3.5 ACK Channel

5 physical layer packet addressed to the access terminal and transmitted on a particular
6 forward CDMA channel of the Forward Traffic Channel has been received successfully or
7 not. The access terminal shall transmit an ACK Channel bit in response to every Forward
8 Traffic Channel slot that is associated with a detected single-user preamble on a forward
9 CDMA channel in an assigned interlace, directed to the access terminal.
10 If DTXMode is equal to ‘1’, the access terminal shall transmit an ACK Channel bit in
11 response to every Forward Traffic Channel slot that is associated with a detected multi-
12 user preamble on a forward CDMA channel in an assigned interlace, directed to the access
13 terminal in the slot specified by (T-FrameOffset) mod 4 = 0, and the first half slot of slot
14 specified by (T-FrameOffset) mod 4 = 1.
15 The access terminal shall transmit at most one redundant positive ACK in response to a
16 Forward Traffic Channel slot on a forward CDMA channel in an assigned interlace, that is
17 detected as a continuation of the physical layer packet that has been successfully received.
18 Otherwise, the ACK Channel shall be gated off.
19 When acknowledging a Single User packet, the ACK Channel shall use BPSK (bipolar
20 keying) modulation, with a 1 representing positive acknowledgement and –1 representing
21 negative acknowledgment. When acknowledging a Multi-User packet, the ACK Channel
22 shall use OOK (ON-OFF keying) modulation, with a 1 (ON) representing positive
23 acknowledgement and a 0 (OFF) representing negative acknowledgment. The access
24 terminal shall transmit a positive acknowledgment on the ACK channel if it successfully
25 receives a packet addressed to it on the Forward Traffic Channel. Otherwise, the access
12-61
1 terminal shall transmit a negative acknowledgment on the ACK channel. A Forward Traffic
2 Channel physical layer packet is considered successfully received if it has a valid FCS. The
3 address of a Single User packet is indicated by the packet preamble, whereas the address
4 of a Multi-User packet is indicated by the MAC Layer header.
5 For NoFeedbackMultiplexing mode and BasicFeedbackMultiplexing mode, for a Forward
6 Traffic Channel physical layer packet transmitted in slot n on the Forward Channel, the
7 corresponding ACK Channel bit shall be transmitted in slot n + 3 on the Reverse Channel
8 (see Figure 12.3.1.3.1-16 and Figure 12.3.1.3.1-17). The ACK Channel transmission shall
9 be transmitted in the first half of the slot and shall last for 1024 PN chips as shown in
10 Figure 12.3.1.3.1-16 and Figure 12.3.1.3.1-17.
11 For NoFeedbackMultiplexing mode and BasicFeedbackMultiplexing mode, the ACK
32
12 Channel uses the Walsh channel identified by the Walsh function W12 and is transmitted
13 on the I-branch.
14 For BasicFeedbackMultiplexing mode, the ACK Channels associated with forward CDMA
15 channels may be transmitted on a reverse CDMA channel as shown in Figure 12.3.1.3.1-8.
16 Each ACK Channel is transmitted on the I-branch and spread using a long code mask that
17 is specified by the LongCodeMaskMSBs. All ACK Channel transmissions for forward CDMA
18 channels associated with a reverse CDMA channel are code division multiplexed and
19 transmitted using that reverse CDMA channel.
20 For EnhancedFeedbackMultiplexing mode, the ACK Channels for the forward CDMA
21 channels may be transmitted on an associated reverse CDMA channel as shown in Figure
22 12.3.1.3.1-11 and Figure 12.3.1.3.1-12.
24 channel is equal to ‘00’, then the ACK Channel shall be transmitted on the associated
4
25 reverse CDMA channel using Walsh cover W0 using a long code mask specified by the
26 LongCodeMaskMSBs on the I-branch.
28 channel is equal to ‘01’, then the ACK Channel shall be transmitted on the associated
4
29 reverse CDMA channel using Walsh cover W2 using a long code mask specified by the
30 LongCodeMaskMSBs on the Q-branch.
32 channel is equal to ‘10’, then the ACK Channel shall be code division multiplexed using
4
33 Walsh over W1 and transmitted on the associated reverse CDMA channel, using a long
34 code mask specified by the LongCodeMaskMSBs on the I-branch.
36 channel is equal to ‘11’, then the ACK Channel shall be code division multiplexed using
4
37 Walsh over W3 and transmitted on the associated reverse CDMA channel, using a long
38 code mask specified by the LongCodeMaskMSBs on the Q-branch.
40 channel is an even number, for a Forward Traffic Channel physical layer packet
12-62
1 transmitted in slot n on the Forward Channel, the corresponding ACK Channel bit shall be
2 transmitted in slot n + 3 on the Reverse Channel (see Figure 12.3.1.3.1-16 and Figure
3 12.3.1.3.1-17). This ACK Channel transmission shall be transmitted in the first half of the
4 slot and shall last for 1024 PN chips as shown in Figure 12.3.1.3.1-16 and Figure
5 12.3.1.3.1-17.
7 channel is an odd number and the DSC Channel is transmitted using the corresponding
8 FeedbackMultiplexingIndex, for a Forward Traffic Channel physical layer packet
9 transmitted in slot n on the Forward Channel, the corresponding ACK Channel bit shall be
10 transmitted in slot n + 3 on the Reverse Channel (see Figure 12.3.1.3.1-16 and Figure
11 12.3.1.3.1-17). This ACK Channel transmission shall be transmitted in the first half of the
12 slot and shall last for 1024 PN chips as shown in Figure 12.3.1.3.1-16 and Figure
13 12.3.1.3.1-17.
15 channel is an odd number and the DSC Channel is not transmitted using the
16 corresponding FeedbackMultiplexingIndex, for a Forward Traffic Channel physical layer
17 packet transmitted in slot n on the Forward Channel, the corresponding ACK Channel bit
18 shall be transmitted in slot n + 2 on the Reverse Channel (see Figure 12.3.1.3.1-18). This
19 ACK Channel transmission shall be transmitted in the second half of the slot and shall last
20 for 1024 PN chips as shown in Figure 12.3.1.3.1-18.
21 ACK Channel transmission for different values of FeedbackMultiplexingMethod are
22 summarized in Table 12.3.1.3.3.5-1 and
23 .
24 Table 12.3.1.3.3.5-1. ACK Channel transmission and FeedbackMultiplexingMethod if

25 DSC Channel is transmitted using that FeedbackMultiplexingMethod
FeedbackMultiplexingMethod ACK Channel transmission

4
Walsh cover W0 on the I-branch in slot ‘n+3’
‘00’
corresponding to packet received in slot ‘n’
4
Walsh cover W2 on the Q-branch in slot ‘n+3’
‘01
4
‘10’
4
‘11’
26
27
28
29
12-63
3 Table 12.3.1.3.3.5-2. ACK Channel transmission and FeedbackMultiplexingMethod if

4 DSC Channel is not transmitted using that FeedbackMultiplexingMethod
FeedbackMultiplexingMethod ACK Channel transmission

4
‘00’
4
‘01
4
‘10’
4
‘11’
5 For EnhancedFeedbackMultiplexing mode, the ACK values shall be repeated eight times
6 and shall be spread by one of the 4-ary Walsh function as defined in Table 12.3.1.3.3.5-3.
32
7 This 32-bit value shall be spread by a 32-ary Walsh function W12 to yield 1024 chips
8 which are transmitted on the I-branch or Q-branch during the first half of the slot or the
9 second half of the slot.
W04 0000
W14 0101
W24 0011
W34 0110
11 13.3.1.3.3.612.3.1.3.3.6 Data Channel

12 Each Data Channel is transmitted at the data rates given in Table 12.3.1.3.1.1-2. An
13 access terminal shall not start a new packet transmission in any slot T on a reverse CDMA
14 channel, specified by the following equation:
16 where T is the CDMA System Time in slots. The FrameOffset parameter is public data of
17 the Reverse Traffic Channel MAC Protocol. All data transmitted on the Reverse Traffic
18 Channel is encoded, block interleaved, sequence repeated, BPSK, QPSK, or 8-PSK
2
19 modulated and orthogonally spread by Walsh function W24 or Walsh function W1 or both.
20 Each Data Channel shall be modulated as shown in Table 12.3.1.3.3.6-1.
12-64
1 Table 12.3.1.3.3.6-1. Data Channel Modulation Formats
Modulation
(Modulation, Walsh Function)
Format
B4 (BPSK, W24 )
Q4 (QPSK, W24 )
2
Q2 (QPSK, W1 )
2
Q4Q2 (QPSK, W24 ) + (QPSK, W1 )
2
E4E2 (8-PSK, W24 ) + (8-PSK, W1 )
2 13.3.1.3.3.712.3.1.3.3.7 Auxiliary Pilot Channel

3 The access terminal shall transmit on the Auxiliary Pilot Channel for each active reverse
4 CDMA channel, using unmodulated symbols with a binary value of ‘0’. The Auxiliary Pilot
5 Channel shall be transmitted during the nth half slot if the transmitted payload during
6 half slots n−1 or n+1 is greater than or equal to AuxiliaryPilotChannelMinPayload, which is
7 public data of the Reverse Traffic Channel MAC Protocol. If the Auxiliary Pilot Channel is
8 transmitted during the nth half slot, its power shall be specified relative to the maximum of
9 the Data Channel Gains during half-slot n−1 and half-slot n+1 by
10 AuxiliaryPilotChannelGain, where AuxiliaryPilotChannelGain is public data of the Reverse
11 Traffic Channel MAC Protocol. The Auxiliary Pilot Channel power level shall be updated at
12 the start of every half slot.
13 If the Auxiliary Pilot Channel is transmitted, it uses the Walsh channel identified by the
32
14 Walsh function W28 and is transmitted on the I-branch as shown in Figure 12.3.1.3.1-6.
15 13.3.1.3.412.3.1.3.4 Encoding

17 The Access Channel physical layer packets shall be encoded with code rate of 1/4. First,
18 the encoder shall discard the six bits of the TAIL field in the physical layer packet inputs
19 (i.e., it shall discard the last six bits in the input physical layer packets). Then, it shall
20 encode the remaining bits with a turbo encoder, as specified in 12.3.1.3.4.2. The turbo
21 encoder will add an internally generated tail.
22 The encoder parameters shall be as specified in Table 12.3.1.3.4-1.
12-65
1 Table 12.3.1.3.4-1. Parameters for the Reverse Link Encoder for the Access Channel
Data Rate
9.6 19.2 38.4
(kbps)

Code Rate 1/4 1/4 1/4
Bits per
256 512 1,024
Number of Turbo Encoder Input
250 506 1,018
Symbols
Turbo Encoder Code Rate 1/4 1/4 1/4
Encoder Output Block Length
1,024 2,048 4,096
(Code Symbols)
2
3 The Reverse Traffic Channel physical layer packets shall be encoded with code rates of 1/5
4 or 1/3. First, the encoder shall discard the six bits of the TAIL field in the physical layer
5 packet inputs (i.e., it shall discard the last six bits in the input physical layer packets).
6 Then, it shall encode the remaining bits with a turbo encoder, as specified in 12.3.1.3.4.2.
7 The turbo encoder will add an internally generated tail.
8 The encoder parameters shall be as specified in Table 12.3.1.3.4-2 and Table 12.3.1.3.4-3.
Data Rate
(kbps) 4.8 9.6 19.2 28.8 38.4 57.6
[After 16 Slots]
Code Rate 1/5 1/5 1/5 1/5 1/5 1/5

Bits per
Physical Layer 128 256 512 768 1,024 1,536
Packet
Number of Turbo
Encoder Input 122 250 506 762 1,018 1,530
Symbols
Turbo Encoder
1/5 1/5 1/5 1/5 1/5 1/5
Code Rate
Encoder Output
Block Length 640 1,280 2,560 3,840 5,120 7,680
(Code Symbols)
11
12-66
Data Rate
(kbps) 76.8 115.2 153.6 230.4 307.2 460.8
[ After 16 Slots]
Code Rate 1/5 1/5 1/5 1/5 1/5 1/3

Bits per
Physical Layer 2,048 3,072 4,096 6,144 8,192 12,288
Packet
Number of Turbo
Encoder Input 2,042 3,066 4,090 6,138 8,186 12,282
Symbols
Turbo Encoder
1/5 1/5 1/5 1/5 1/5 1/3
Code Rate
Encoder Output
10,24 15,36 30,74
Block Length 20,480 40,960 36,864
0 0 0
(Code Symbols)
3 13.3.1.3.4.212.3.1.3.4.2 Turbo Encoding

6 symbols followed by 6/R tail output symbols, where R is the code rate of 1/3, 1/4, or 1/5.
13 13.3.1.3.4.2.112.3.1.3.4.2.1 Turbo Encoders

19 A common constituent code shall be used for the rate 1/3, 1/4, and 1/5 Turbo codes. The
⎡ n0 (D) n1(D) ⎤
G(D) = ⎢1 ⎥
⎣ d(D) d(D) ⎥⎦
21
12-67

23 output first.
28 XXY0Y1, and the tail output symbols for each of the last three tail bit periods shall be
29 X′X′Y′0Y′1. For rate-1/5 turbo codes, the tail output code symbols for each of the first three
30 tail bit periods shall be punctured and repeated to achieve the sequence XXY0Y1Y1, and
31 the tail output code symbols for each of the last three tail bit periods shall be punctured
32 and repeated to achieve the sequence X′X′Y′0Y′1Y′1. For rate-1/3 turbo codes, the tail
33 output symbols for each of the first three tail bit periods shall be XXY0, and the tail output
34 symbols for each of the last three tail bit periods shall be X′X′Y′0.
12-68
X
Y0
n0
Y1
n1
Nturbo
Information
Bits
(Input)
Control
Puncturing Code
and Symbols
Turbo
Interleaver
X'
Y'0
n0
Y'1
n1
Control
1
12-69
Code Rate
Output 1/3 1/4 1/5
X 1 11 1
Y0 1 11 1
Y1 0 10 1
X′ 0 00 0
Y′ 0 1 01 1
Y′ 1 0 11 1
2
Code Rate
Output 1/3 1/4 1/5
X 111 000 111 000 111 000

Y0 111 000 111 000 111 000
Y1 000 000 111 000 111 000
X′ 000 111 000 111 000 111
Y′ 0 000 111 000 111 000 111
Y′ 1 000 000 000 111 000 111
be read first from top to bottom repeating X and X′, and then
from left to right. For rate-1/5 turbo codes, the puncturing table
shall be read first from top to bottom repeating X, X′, Y1, and Y′1
and then from left to right.
4

12-70
14 the value of n.
Add 1
Counter Lookup
5 LSBs Bit 5 Bits

23
12-71
Turbo Turbo
Nturbo n
128 122 2
256 250 3
512 506 4
768 762 5
1,024 1,018 5
1,536 1,530 6
2,048 2,042 6
3,072 3,066 7
4,096 4,090 7
6,144 6,138 8
8,192 8,186 8
12,288 12,282 9
2
12-72
Table n=2 n=3 n=4 n=5 n=6 n=7 n=8 n=9

Index Entries Entries Entries Entries Entries Entries Entries Entries
0 3 1 5 27 3 15 3 13
1 3 1 15 3 27 127 1 335
2 3 3 5 1 15 89 5 87
3 1 5 15 15 13 1 83 15
4 3 1 1 13 29 31 19 15
5 1 5 9 17 5 15 179 1
6 3 1 9 23 1 61 19 333
7 1 5 15 13 31 47 99 11
8 1 3 13 9 3 127 23 13
9 1 5 15 3 9 17 1 1
10 3 3 7 15 15 119 3 121
11 1 5 11 3 31 15 13 155
12 1 3 15 13 17 57 13 1
13 1 5 3 1 5 123 3 175
14 1 5 15 13 39 95 17 421
15 3 1 5 29 1 5 1 5
16 3 3 13 21 19 85 63 509
17 1 5 15 19 27 17 131 215
18 3 3 9 1 15 55 17 47
19 3 5 3 3 13 57 131 425
20 3 3 1 29 45 15 211 295
21 1 5 3 17 5 41 173 229
22 3 5 15 25 33 93 231 427
23 1 5 1 29 15 87 171 83
24 3 1 13 9 13 63 23 409
25 1 5 1 13 9 15 147 387
26 3 1 9 23 15 13 243 193
27 1 5 15 13 31 15 213 57
28 3 3 11 13 17 81 189 501
29 1 5 3 1 5 57 51 313
30 1 5 15 13 15 31 15 489
31 3 3 5 13 33 69 67 391
2
12-73
1 13.3.1.3.512.3.1.3.5 Scrambling for Reverse Traffic Channel Physical Layer Packets

5 Figure 12.3.1.3.5-1. At the start of the physical layer packet, the shift register shall be
6 initialized to the state [11111111111i1i0d3d2d1d0]. The d3d2d1d0 bits shall be determined
7 by the payload size, as specified in Table 12.3.1.3.5-1. The i1i0 bits shall be determined by
8 the reverse link interlace offset167, as specified in Table 12.3.1.3.5-2. The initial state shall
Payload Size (bits) d3 d2 d1 d0
128 0 0 0 0
256 0 0 0 1
512 0 0 1 0
768 0 0 1 1
1024 0 1 0 0
1536 0 1 0 1
2048 0 1 1 0
3072 0 1 1 1
4096 1 0 0 0
6144 1 0 0 1
8192 1 0 1 0
12288 1 0 1 1
14
Reverse Link Interlace Offset i1 i0
0 0 0
1 0 1
2 1 0
16
167 The reverse-link interlace offset i for a sub-packet starting in slot T is specified as i = (T -
FrameOffset)/4 mod 3, where T is the CDMA System Time in slots and 0 ≤ i ≤ 2.
12-74
1 1 1 1 1 1 1 1 1 1 1 i1 i0 d3 d2 d1 d0
Scrambling
Sequence
1
2 Figure 12.3.1.3.5-1. Symbol Scrambler
3 13.3.1.3.612.3.1.3.6 Channel Interleaving for Access Channel Physical Layer Packets

13 satisfies:

21 address.
12-75
Counter
bL–1 bL–2 b1 b0
Bit_Reversal
b0 b1 bL–2 bL–1

1
3 13.3.1.3.712.3.1.3.7 Channel Interleaving for Reverse Traffic Channel Physical Layer

4 Packets
6 channel interleaver. Channel interleaving shall consist of a Symbol Reordering stage
7 followed by a Matrix Interleaving stage.
8 The packet length, N (including data and tail bits) is expressed as N = R × K × 2m, where, R,
10 parameters R, K, m, and an end-around-shift parameter D.
11 13.3.1.3.7.112.3.1.3.7.1 Symbol Reordering

12 Turbo encoder data and tail output symbols generated with the rate-1/5 encoder shall be
13 reordered according to the following steps:
14 1. All of the data and tail turbo encoder output symbols shall be demultiplexed into
15 five sequences denoted U, V0, V1, V′0, and V′1. The scrambled encoder output
16 symbols shall be sequentially distributed from the U sequence to the V′1 sequence
17 with the first scrambled encoder output symbol going to the U sequence, the second
18 to the V0 sequence, the third to the V1 sequence, the fourth to the V′0 sequence,
19 the fifth to the V′1 sequence, the sixth to the U sequence, etc.
22 shall be last.
12-76
6 sequence, etc.
7 2. The U, V0 and V′0 sequences shall be ordered according to UV0 V′0. That is, the U
9 13.3.1.3.7.212.3.1.3.7.2 Matrix Interleaving

16 c < C, and 0 ≤ k < K.
18 shifted by (c × K + k) mod R. In other words, matrix[r] [c] [k] is transformed to
21 interleaved (based on column-index). Symbols from the cuboidal array are read out
22 with row-index incrementing first, followed by column-index, followed by level-
23 index. In other words, the ith output symbol ((k × C + c) × R + r), where 0 ≤ i < N
24 comes from the rth row, cth column, and kth level, where 0 ≤ r < R , 0 ≤ c < C, and 0
25 ≤ k < K.
27 are written into a 3-dimensional cuboidal array with R rows, C ≡ 2m+1 columns and
28 K levels. Symbols are written into the 3-dimensional array with level-index
29 incrementing first, followed by column-index, followed by row-index. In other words,
30 the ith incoming symbol ((r × C + c) × K + k), where 0 ≤ i < 2 × N goes into the rth
31 row, cth column, and kth level, where 0 ≤ r < R , 0 ≤ c < C, and 0 ≤ k < K.
34 transformed to matrix[r + ⎣( K × c + k) / D⎦ mod R][c] [k].
36 interleaved (based on the column-index).
39 symbol ((k × C + c) × R + r), where 0 ≤ i < 2 × N comes from the rth row, cth column,
12-77
3 Table 12.3.1.3.7.2-1 below shows the interleaver parameters for various packets used on
4 the Reverse Traffic Channel.
5 Table 12.3.1.3.7.2-1. Channel Interleaver Parameters
Payload size (bits) N K R m D
128 128 1 1 7 1
256 256 1 1 8 1
512 512 1 1 9 1
768 768 3 1 8 1
1024 1024 1 1 10 1
1536 1536 3 2 8 1
2048 2048 1 2 10 1
3072 3072 3 2 9 1
4096 4096 1 2 11 1
6144 6144 3 2 10 1
8192 8192 1 2 12 1
12288 12288 1 3 12 1
6

8 The Pilot Channel, the RRI Channel, the DSC Channel, the DRC Channel, the ACK
9 Channel, the Data Channel, and the Auxiliary Pilot Channel shall be spread with Walsh
13 The Walsh cover assignments are shown in Figure 12.3.1.3.1-2, Figure 12.3.1.3.1-3, and
14 Figure 12.3.1.3.1-4. The Pilot Channel shall be covered by the 16-chip Walsh function
15 number 0 ( W016 = + + + + + + + + + + + + + + + +). The RRI Channel shall be covered by a
16
16 16-chip Walsh function number 4 ( W4 = + + + + – – – – + + + + – – – –). The DSC channel
17 shall be time-division multiplexed with the ACK Channel and covered by the 32-chip Walsh
32
18 function number 12 ( W12 = + + + + – – – – – – – – + + + + + + + + – – – – – – – – + + + +). The
19 DRC Channel shall be covered by the 16-chip Walsh function number 8 ( W816 =
20 + + + + + + + + – – – – – – – –). The ACK Channel shall be time-division multiplexed with the
32
21 DSC Channel and covered by the 32-chip Walsh function number 12 ( W12 = + + + + – – – –
22 – – – – + + + + + + + + – – – – – – – – + + + +). The Data Channel shall be covered by one or
23 both of the 4-chip Walsh function number 2 ( W24 = + + – –) and the 2-chip Walsh function
12-78
2
1 number 1 ( W1 = + − ). The Auxiliary Pilot Channel shall be covered by a 32-chip Walsh
32
2 function number 28 ( W28 = + + + + − − − − − − − − + + + + − − − − + + + + + + + + − − − −).
3 The RRI, DSC, DRC, ACK, and Data Channel chip sequences shall be scaled by a factor
4 that gives the gain of each of these channels relative to that of the Pilot Channel. The
5 Auxiliary Pilot Channel chip sequences shall be scaled by a factor that gives its gain
6 relative to that of the Data Channel. The relative gain values for the RRI, DSC, DRC, and
7 Data Channel are specified by the parameters RRIChannelGain, DSCChannelGain,
8 DRCChannelGain, and TxT2P. The relative gain value for the ACK Channel transmitted in
9 response to a Single User packet is specified by the parameter ACKChannelGain. The
10 relative gain value for the ACK Channel transmitted in response to a Multi-User packet is
11 specified by ACKChannelGain + DeltaACKChannelGainMUP. The relative gain value for the
12 Auxiliary Pilot Channel is specified by the parameter AuxiliaryPilotChannelGain. The
13 DSCChannelGain, DRCChannelGain, ACKChannelGain, and DeltaACKChannelGainMUP
14 are public data of the Forward Traffic Channel MAC Protocol. The RRIChannelGain is
15 public data of the Reverse Traffic Channel MAC Protocol. For the Reverse Traffic Channel,
16 the relative gain is specified by TxT2P, where TxT2P is public data of the Reverse Traffic
17 Channel MAC Protocol. For the Auxiliary Pilot Channel, the relative gain is specified by
18 AuxiliaryPilotChannelGain where AuxiliaryPilotChannelGain is public data of the Reverse
19 Traffic Channel MAC Protocol. For the Access Channel, the relative gain of the Data
21 Protocol.
22 13.3.1.3.912.3.1.3.9 Modulation
24 phase stream and a quadrature stream of modulated values. The channel interleaver
25 output is modulated and Walsh covered. The modulator generates BPSK, QPSK, or 8-PSK
2
26 modulation symbols that are Walsh covered by a 2-ary Walsh cover W1 , a 4-ary Walsh
4
27 cover W2 or both. The modulation and Walsh covering depends on the payload size. The
28 modulation formats are B4, Q4, Q2, Q4Q2, and E4E2.
29 13.3.1.3.9.112.3.1.3.9.1 B4 Modulation
30 For physical layer packet sizes with payload sizes less than or equal to 1024 bits, each
31 channel interleaver output symbol shall form a B4 modulation symbol (BPSK modulated
4
32 and Walsh covered by a 4-ary Walsh cover, W2 as specified in Table 12.3.1.3.9.1-1.)
12-79
1 Table 12.3.1.3.9.1-1. B4 Modulation Table
Interleaved Modulation
Symbols Symbols
0 +D +D –D –D
1 –D –D +D +D
Note: D = 1 .
2 13.3.1.3.9.212.3.1.3.9.2 Q4 Modulation
5 modulated and 4-ary Walsh covered). Each group of two adjacent block interleaver output
6 symbols, x(2k) and x(2k + 1), k = 0,…, M – 1 shall be mapped into a complex modulation
7 symbol (mI(k), mQ(k)) as specified in Table 12.3.1.3.9.2-1.

x(2k + 1) x(2k) mI(k) mQ(k)
0 0 +D +D –D –D +D +D –D –D
0 1 –D –D +D +D +D +D –D –D
1 0 +D +D –D –D –D –D +D +D
1 1 –D –D +D +D –D –D +D +D
Note: D = 1 2.
9 13.3.1.3.9.312.3.1.3.9.3 Q2 Modulation
10 For physical layer packet sizes of 3,072 or 4,096 bits, groups of four successive channel
12 modulated and 2-ary Walsh covered). Each group of four adjacent block interleaver output
13 symbols, x(4k), x(4k + 1), x(4k + 2), x(4k + 3), k = 0,…, M – 1 shall be mapped into a
14 complex modulation symbol (mI(k), mQ(k)) as specified in Table 12.3.1.3.9.3-1.
12-80

x(4k+3) x(4k+2) x(4k+1) x(4k) mI(k) mQ(k)
0 0 0 0 +D –D +D –D +D –D +D –D
0 0 0 1 –D +D +D –D +D –D +D –D
0 0 1 0 +D –D +D –D –D +D +D –D
0 0 1 1 –D +D +D –D –D +D +D –D
0 1 0 0 +D –D –D +D +D –D +D –D
0 1 0 1 –D +D –D +D +D –D +D –D
0 1 1 0 +D –D –D +D −D +D +D –D
0 1 1 1 –D +D –D +D −D +D +D –D
1 0 0 0 +D –D +D –D +D –D –D +D
1 0 0 1 –D +D +D –D +D –D –D +D
1 0 1 0 +D –D +D –D –D +D –D +D
1 0 1 1 −D +D +D –D –D +D –D +D
1 1 0 0 +D –D –D +D +D –D –D +D
1 1 0 1 –D +D –D +D +D –D –D +D
1 1 1 0 +D –D –D +D –D +D –D +D
1 1 1 1 –D +D –D +D –D +D –D +D
Note: D = 1 2.
2 13.3.1.3.9.412.3.1.3.9.4 Q4Q2 Modulation

3 For physical layer packet sizes of 6,144 or 8,192 bits, groups of six successive channel
4 interleaver output symbols shall be grouped to form Q4Q2 modulation symbols which are
5 the sum of Q4 modulation symbols scaled by 1 / 3 and the Q2 modulation symbols scaled
6 by 2 / 3 (see Figure 12.3.1.3.1-4). Of each group of six adjacent block interleaver output
7 symbols, x(6k), x(6k + 1), x(6k + 2), x(6k + 3), x(6k + 4) and x(6k + 5) for k = 0,…, M – 1, the
8 output symbols, x(6k) and x(6k + 1) are grouped to form Q4 modulation symbols, as shown
9 in Table 12.3.1.3.9.2-1and the output symbols x(6k + 2), x(6k + 3), x(6k + 4) and x(6k + 5)
10 are grouped to form Q2 modulation symbols as shown in Table 12.3.1.3.9.3-1. The symbols
11 formed due to Q4 and Q2 modulation are then scaled and summed according to Figure
12 12.3.1.3.1-4 to form Q4Q2 modulated symbols.
13 13.3.1.3.9.512.3.1.3.9.5 E4E2 Modulation

14 For physical layer packet size of 12,288 bits, groups of nine successive channel interleaver
15 output symbols shall be grouped to form E4E2 modulation symbols which are the sum of
16 E4 modulation symbols scaled by 1 / 3 and the E2 modulation symbols scaled by
12-81
1 2 / 3 (see Figure 12.3.1.3.1-5). Of each group of nine adjacent block interleaver output
2 symbols, x(9k), x(9k+1), x(9k+2), x(9k+3), x(9k+4), x(9k+5), x(9k+6), x(9k+7), x(9k+8), for k
3 = 0,…, M – 1, the output symbols, x(9k), x(9k+1) and x(9k+2) are grouped to form E4
4 modulation symbols, as shown in Table 12.3.1.3.9.5-1and the output symbols x(9k+3),
5 x(9k+4), x(9k+5), x(9k+6), x(9k+7), and x(9k+8) are grouped to form E2 modulation symbols
6 as shown in Table 12.3.1.3.9.5-2. The symbols formed due to E4 and E2 modulation are
7 then scaled and summed according to Figure 12.3.1.3.1-5 form E4E2 modulated symbols.

x(9k + 2) x(9k + 1) x(9k) mI(k) mQ(k)
0 0 0 +C +C –C –C +S +S –S –S
0 0 1 +S +S –S –S +C +C –C –C
0 1 1 –S –S +S +S +C +C –C –C
0 1 0 –C –C +C +C +S +S –S –S
1 1 0 –C –C +C +C –S –S +S +S
1 1 1 –S –S +S +S –C –C +C +C
1 0 1 +S +S –S –S –C –C +C +C
1 0 0 +C +C –C –C –S –S +S +S
12-82

0 0 0 0 0 0 +C –C +C –C +S –S +S –S
0 0 0 0 0 1 +S –S +C –C +C –C +S –S
0 0 0 0 1 0 –C +C +C –C +S –S +S –S
0 0 0 0 1 1 –S +S +C -C +C –C +S –S
0 0 0 1 0 0 +C –C +C –C –S +S +S –S
0 0 0 1 0 1 +S –S +C –C –C +C +S –S
0 0 0 1 1 0 –C +C +C –C –S +S +S –S
0 0 0 1 1 1 –S +S +C –C –C +C +S –S
0 0 1 0 0 0 +C –C +S –S +S –S +C –C
0 0 1 0 0 1 +S –S +S –S +C –C +C –C
0 0 1 0 1 0 –C +C +S –S +S –S +C –C
0 0 1 0 1 1 –S +S +S –S +C –C +C –C
0 0 1 1 0 0 +C –C +S –S –S +S +C –C
0 0 1 1 0 1 +S –S +S –S –C +C +C –C
0 0 1 1 1 0 –C +C +S –S –S +S +C –C
0 0 1 1 1 1 –S +S +S –S –C +C +C –C
0 1 0 0 0 0 +C –C –C +C +S –S +S –S
0 1 0 0 0 1 +S –S –C +C +C –C +S –S
0 1 0 0 1 0 –C +C –C +C +S –S +S –S
0 1 0 0 1 1 –S +S –C +C +C –C +S –S
0 1 0 1 0 0 +C –C –C +C –S +S +S –S
0 1 0 1 0 1 +S –S –C +C –C +C +S –S
0 1 0 1 1 0 –C +C –C +C –S +S +S –S
0 1 0 1 1 1 –S +S –C +C –C +C +S –S
0 1 1 0 0 0 +C –C –S +S +S –S +C –C
0 1 1 0 0 1 +S –S –S +S +C –C +C –C
0 1 1 0 1 0 –C +C –S +S +S –S +C –C
0 1 1 0 1 1 –S +S –S +S +C –C +C –C
0 1 1 1 0 0 +C –C –S +S –S +S +C –C
0 1 1 1 0 1 +S –S –S +S –C +C +C –C
0 1 1 1 1 0 –C +C –S +S –S +S +C –C
12-83

0 1 1 1 1 1 –S +S –S +S –C +C +C –C
1 0 0 0 0 0 +C –C +C –C +S –S –S +S
1 0 0 0 0 1 +S –S +C –C +C –C –S +S
1 0 0 0 1 0 –C +C +C –C +S –S –S +S
1 0 0 0 1 1 –S +S +C –C +C –C –S +S
1 0 0 1 0 0 +C –C +C –C –S +S –S +S
1 0 0 1 0 1 +S –S +C –C –C +C –S +S
1 0 0 1 1 0 –C +C +C –C –S +S –S +S
1 0 0 1 1 1 –S +S +C –C –C +C –S +S
1 0 1 0 0 0 +C –C +S –S +S –S –C +C
1 0 1 0 0 1 +S –S +S –S +C –C –C +C
1 0 1 0 1 0 –C +C +S –S +S –S –C +C
1 0 1 0 1 1 –S +S +S –S +C –C –C +C
1 0 1 1 0 0 +C –C +S –S –S +S –C +C
1 0 1 1 0 1 +S –S +S –S –C +C –C +C
1 0 1 1 1 0 –C +C +S –S –S +S –C +C
1 0 1 1 1 1 –S +S +S –S –C +C –C +C
1 1 0 0 0 0 +C –C –C +C +S –S –S +S
1 1 0 0 0 1 +S –S –C +C +C –C –S +S
1 1 0 0 1 0 –C +C –C +C +S –S –S +S
1 1 0 0 1 1 –S +S –C +C +C –C –S +S
1 1 0 1 0 0 +C –C –C +C –S +S –S +S
1 1 0 1 0 1 +S –S –C +C –C +C –S +S
1 1 0 1 1 0 –C +C –C +C –S +S –S +S
1 1 0 1 1 1 –S +S –C +C –C +C –S +S
1 1 1 0 0 0 +C –C –S +S +S –S –C +C
1 1 1 0 0 1 +S –S –S +S +C –C –C +C
1 1 1 0 1 0 –C +C –S +S +S –S –C +C
1 1 1 0 1 1 –S +S –S +S +C –C –C +C
1 1 1 1 0 0 +C –C –S +S –S +S –C +C
1 1 1 1 0 1 +S –S –S +S –C +C –C +C
1 1 1 1 1 0 –C +C –S +S –S +S –C +C
12-84

1 1 1 1 1 1 –S +S –S +S –C +C –C +C
1 13.3.1.3.1012.3.1.3.10 Sequence Repetition for Access Channel Physical Layer Packets

3 number of repeats shall be as specified in Table 12.3.1.3.1.1-1. The repetition shall be
4 functionally equivalent to sequentially reading out all the symbols from the interleaver
5 memory as many times as necessary to achieve the fixed 307.2-ksps modulation symbol
6 rate.
7 13.3.1.3.1112.3.1.3.11 Sequence Repetition and Symbol Selection for Reverse Traffic

8 Channel Physical Layer Packets
10 number of repeats varies for each pair of (payload size, number of sub-frames) and shall be
11 as specified in Table 12.3.1.3.1.1-2. The repetition shall be functionally equivalent to
13 necessary to achieve the target modulation symbol rate, which varies for each payload size.
14 Assume the total number of coded symbols is N, and the number of code symbols in each
15 sub-frame is M, the jth code symbol in ith sub-frame is the kth code symbol output of the
16 channel interleaver, where k = (j + i × M) mod N, i = 0, 1, 2, 3, j = 0, 1, …, M-1. Note the 0th
17 code symbol is the first code symbol output of the channel interleaver.

19 Following the orthogonal spreading and scaling, the Pilot, RRI, DSC, DRC, ACK, Data, and
20 Auxiliary Pilot Channel sequences are combined to form resultant I-Channel and Q-
21 Channel sequences, and these sequences are quadrature spread as shown in Figure
22 12.3.1.3.1-1 and Figure 12.3.1.3.1-6. The quadrature spreading shall occur at the chip
23 rate of 1.2288 Mcps, and it shall be used for the Reverse Traffic Channel and the Access
24 Channel. The Pilot, DSC or ACK(if transmitted), RRI, Data(if transmitted), and Auxiliary
25 Pilot Channel (if transmitted) sequences shall be added to form the resultant I-Channel
26 sequence, and the DRC and Data Channel sequences shall be added to form the resultant
27 Q-Channel sequence. The quadrature spreading operation shall be equivalent to a complex
28 multiply operation of the resultant I-Channel and resultant Q-Channel sequences by the
29 PNI and PNQ PN sequences, as shown in Figure 12.3.1.3.1-1 and Figure 12.3.1.3.1-6.
12-85
2 procedure:

16 PI(x) = x15 + x13 + x9 + x8 + x7 + x5 + 1

18 and
19 PQ(x) = x15 + x12 + x11 + x10 + x6 + x5 + x4 + x3 + 1

23 I(n) = I(n – 15) ⊕ I(n – 10) ⊕ I(n – 8) ⊕ I(n – 7) ⊕ I(n – 6) ⊕ I(n – 2)
25 and
26 Q(n) = Q(n – 15) ⊕ Q(n – 12) ⊕ Q(n – 11) ⊕ Q(n – 10) ⊕ Q(n – 9) ⊕
27 Q(n – 5) ⊕ Q(n – 4) ⊕ Q(n – 3)
33 outputs instead 14. The initial state of the access terminal common short-code PN
12-86
5 chip on every even-second mark as referenced to the transmit time reference (see 12.3.3) is
6 the ‘1’ after the 15 consecutive ‘0’s (see Figure 1.14-1).
7 13.3.1.3.12.212.3.1.3.12.2 Long Codes

12 p(x) = x42 + x35 + x33 + x31 + x27 + x26 + x25 + x22 + x21 + x19 +
13 x18 + x17 + x16 + x10 + x7 + x6 + x5 + x3 + x2 + x + 1.
12-87
MI41
x 42
42
MI40
x 41
41
x 40
40
x 39
Modulo-2
UI
Addition
39
x8
8
MI1
MI0
x7
x6
6
MQ41
x5
MQ40
x4
Modulo-2
x3 Addition
UQ
x2
2
MQ1
MQ0
x
2 Figure 12.3.1.3.12.2-1. Long-Code Generators
3 For BasicFeedbackMultiplexing mode and EnhancedFeedbackMultiplexing mode the long

4 code masks shall be generated as follows. The 42-bit mask long code mask for
5 transmissions on the I-branch, MI’ARTCMAC, shall be specified as shown in Table
6 12.3.1.3.12.2-1.
12-88
1 Table 12.3.1.3.12.2-1. Additional Long Code Masks for Reverse Traffic Channel in
2 BasicFeedbackMultiplexing mode and EnhancedFeedbackMultiplexing mode
BIT
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15
14
13
12
11
10
09
08
07
06
05
04
03
02
01
00
MI’ARTCMAC X X X X 1 1 1 1 1 1 Permuted (ATILCM )
3
4 In BasicFeedbackMultiplexing mode and EnhancedFeedbackMultiplexing mode the access

5 terminal shall generate a unique pair of long code mask for each unique value of the
6 LongCodeMaskMSBs.
8 ATILCM = (A31, A30, A29, …, A0)
11 A15, A6, A28, A19, A10, A1, A23, A14, A5, A27, A18, A9).
12 The 42-bit mask long code mask for transmissions on the Q-branch, MQ’RTCMAC, shall be
13 derived from the long code mask for transmissions on the I-branch, MI’RTCMAC, as follows:
14 MQ’ARTCMAC[k] = MI’ARTCMAC[k−1], for k = 1,…,41
15 MQ’ARTCMAC[0] = MI’ARTCMAC[0] ⊕ MI’ARTCMAC[1] ⊕ MI’ARTCMAC[2] ⊕ MI’ARTCMAC[4] ⊕
16 MI’ARTCMAC[5] ⊕ MI’ARTCMAC[6] ⊕ MI’ARTCMAC[9] ⊕ MI’ARTCMAC[15] ⊕ MI’ARTCMAC[16] ⊕
19 MI’ARTCMAC[41]
20 where the ⊕ denotes the Exclusive OR operation, and MQ’ARTCMAC[i] and MI’ARTCMAC[i] denote
21 the ith least significant bit of MQ’ARTCMAC and MI’ARTCMAC, respectively.

24 inputs of the I and Q baseband filters as shown in Figure 12.3.1.3.1-1and Figure
25 12.3.1.3.1-6 for each reverse CDMA channel. The baseband filters shall have a frequency
26 response S(f) that satisfies the limits given in Figure 12.3.1.3.12.3-1 for each reverse CDMA
27 channel. Specifically, the normalized frequency response of the filter shall be contained
28 within ±δ1 in the passband 0 ≤ f ≤ fp and shall be less than or equal to –δ2 in the stopband
29 f ≥ fs. The numerical values for the parameters are δ1 = 1.5 dB, δ2 = 40 dB, fp = 590 kHz,
30 and fs = 740 kHz.
12-89
20 log10 S(f )
δ1
δ1
δ2
f
0 fp fs
1
∞
k =0
[αs(kTs – τ) – h(k)]2 ≤ 0.03,
12-90
k h(k)
0, 47 –0.025288315
1, 46 –0.034167931
2, 45 –0.035752323
3, 44 –0.016733702
4, 43 0.021602514
5, 42 0.064938487
6, 41 0.091002137
7, 40 0.081894974
8, 39 0.037071157
9, 38 –0.021998074
10, 37 –0.060716277
11, 36 –0.051178658
12, 35 0.007874526
13, 34 0.084368728
14, 33 0.126869306
15, 32 0.094528345
16, 31 –0.012839661
17, 30 –0.143477028
18, 29 –0.211829088
19, 28 –0.140513128
20, 27 0.094601918
21, 26 0.441387140
22, 25 0.785875640
23, 24 1.0
2
3 13.3.1.412.3.1.4 Discontinuous Transmission

4 If DTXMode is equal to ‘1’ the access terminal shall not transmit the DRC Channel, the
5 ACK Channel, and the DSC Channel, in the second half slot of slot specified by (T –
6 FrameOffset) mod 4 = 1, the slot specified by (T-FrameOffset) mod 4 = 2, and the first half
7 slot of slot specified by (T-FrameOffset) mod 4 = 3 on any active reverse CDMA channel.
8 If DTXMode is equal to ‘1’ the access terminal shall not transmit the ACK Channel bit in
9 response to a Forward Traffic Channel slot that is associated with a multi-user packet on a
10 forward CDMA channel in an assigned interlace in the slot specified by (T-FrameOffset)
12-91
1 mod 4 = 2, and the first half slot of slot specified by (T-FrameOffset) mod 4 = 3 on any
2 active reverse CDMA channel.
3 If DTXMode is equal to ‘1’, the access terminal shall transmit a pilot channel for a ½ slot
4 prior to the transmission of an ACK Channel bit in slots specified by (T-FrameOffset) mod 4
5 = 2, and (T-FrameOffset) mod 4 = 3 in response to a Forward Traffic Channel slot
6 associated with a detected single user packet preamble on a forward CDMA channel in an
7 assigned interlace, directed to the access terminal.
8 If DTXMode is equal to ‘1’ and the DTXRRIMode is equal to ‘0’, the access terminal shall
9 not transmit the RRI Channel in the second half slot of slot specified by (T – FrameOffset)
10 mod 4 = 1, the slot specified by (T-FrameOffset) mod 4 = 2, and the first half slot of slot
11 specified by (T-FrameOffset) mod 4 = 3 on any active reverse CDMA channel.
12 If DTXMode is equal to ‘1’, and the DTXRRIMode is equal to ‘1’, and the access terminal is
13 not transmitting a reverse traffic channel sub-packet in a sub-frame on an active reverse
14 CDMA channel, then the access terminal shall not transmit the RRI Channel in that sub-
15 frame.
16 If DTXMode is equal to ‘1’ and the access terminal is not transmitting a reverse traffic
17 channel sub-packet in a sub-frame on an active reverse CDMA channel, then the access
18 terminal shall not transmit the Pilot Channel on that reverse CDMA channel, in the second
19 half slot of slot specified by (T – FrameOffset) mod 4 = 1, slot specified by (T-FrameOffset)
20 mod 4 = 2, and first half slot of slot specified by (T-FrameOffset) mod 4 = 3
21 If DTXMode is equal to ‘1’ and the ReversePilotTransmitSlotsEnabled is equal to ‘1’, the
22 access terminal shall transmit the Pilot Channel on each active reverse CDMA channel
23 starting in slot specified by T mod ReversePilotTransmitSlotsPeriod = 0 for
24 ReversePilotTransmitSlotsDuration slots.
25 Figure 12.3.1.4-1 shows sub-frames with data transmission and sub-frames without data
26 transmission for the access terminal transmission with DTXMode equal to ‘1’ and
27 DTXRRIMode equal to ‘0’ and Figure 12.3.1.4-2 shows sub-frames with data transmission
28 and sub-frames without data transmission for the access terminal transmission with
29 DTXMode equal to ‘1’ and DTXRRIMode equal to ‘1’.
30

32 DTXRRIMode equal to ’0’
12-92

3 DTXRRIMode equal to ’1’
6 13.3.212.3.2 Receiver

8 Once the connection is established for an active reverse CDMA channel, the access network
9 transmits ‘0’ (up) or ‘1’ (down) RPC bits to the access terminal on the associated forward
10 CDMA channelforward CDMA channel of the associated sub-active set. If the received
11 quality of the reverse link of the active reverse CDMA channel is above the target threshold,
12 a ‘1’ bit is transmitted on the RPC channel of the forward CDMA channel associated with
13 that active reverse CDMA channel. If the received quality of the reverse link of the active
14 reverse CDMA channel is below the target threshold, a ‘0’ bit is transmitted on the RPC
15 channel of the forward CDMA channel associated with that active reverse CDMA channel.
16 The access terminal shall receive RPC commands for each active reverse CDMA channel, on
17 the associated forward CDMA channelforward CDMA channel of the associated sub-active
18 set, in slots T as specified by the following equation:
21 The access terminal shall ignore the RPC command during all other slots.
22 If the access terminal did not transmit on the Reverse Traffic Channel of an active reverse
23 CDMA channel in slot n, then it shall ignore the received RPC bit in subframe n + 1 for that
24 active reverse CDMA channel. Otherwise, the access terminal shall adjust its output power
25 by a discrete amount in the direction indicated by the RPC bit after the RPC bit is received
26 as specified in 12.3.1.2.4.2 and 12.3.1.2.4.5. The RPC bit is considered received after the
27 64-chip MAC burst following the second pilot burst of a slot which contains an RPC bit as
30 different sectors are transmitting the same RPC bit for each active reverse CDMA channel.
31 In each slot containing power-control bits, the access terminal should provide diversity
32 combining of the identical RPC Channels and shall obtain at most one power-control bit
33 from each set of identical RPC Channels for each active reverse CDMA channel. The access
12-93
1 terminal shall increase its output power if all the resulting RPC bits are ‘0’ (“up”) for each
2 active reverse CDMA channel. If any resulting RPC bit is ‘1’ (“down”) for an active reverse
3 CDMA channel, the access terminal shall decrease its output power as specified in
4 12.3.1.2.4.2 for that active reverse CDMA channel.

6 Once the connection is established on an active reverse CDMA, the access network
7 continuously transmits ‘0’ or ‘1’ DRCLock bits to the access terminal on the DRCLock
8 Channel on the forward CDMA channel associated with that active reverse CDMA channel.
9 The access terminal shall process the DRCLock bits received on the DRCLock Channel on
10 the forward CDMA channel associated with that active reverse CDMA channel as specified
11 by the Forward Traffic Channel MAC Protocol.
13 different sectors are transmitting the same DRCLock bit for an active reverse CDMA
14 channel on the associated forward CDMA. In each slot containing a DRCLock bit, the
15 access terminal should provide diversity combining of the identical DRCLock Channels for
16 each active reverse CDMA channel and shall obtain at most one DRCLock bit from each set
17 of identical DRCLock Channels for that active reverse CDMA channel.

19 The access network transmits the Reverse Activity Channel every slot for every reverse
20 CDMA channel. Once the reverse link connection is established for an active reverse CDMA
21 channel, the access terminal shall process the RA bit for each active reverse CDMA channel
22 from each sector in its active set along with the RAChannelGain public data of the Reverse
23 Traffic Channel MAC protocol, to generate the log-likelihood ratio LLRrab for that active
24 reverse CDMA channel. The access terminal shall map the log-likelihood ratio (LLR) of the
25 RA bit demodulation, LLRrab from a range of [−∞, +∞] to a range of [−1, +1] to generate
26 SoftRAB for an active reverse CDMA channel from each sector in its active set using the
27 following function:
28 SoftRAB = 0.4 × LLRrab, −2.5 ≤ LLRrab ≤ 2.5
30 SoftRAB = −1, LLRrab < −2.5
31 where -1 ≤ SoftRAB ≤ 1 and SoftRAB is a real-valued input for the Reverse Traffic Channel
32 MAC Protocol.
33 13.3.2.412.3.2.4 Reception of ARQ Channel

34 Each sector of an access network transmits a positive acknowledgment (ACK) or a negative
35 acknowledgment (NAK) on the forward CDMA channel in response to a physical layer
36 packet received on an associated reverse CDMA channel using the ARQ Channel. The H-
37 ARQ (Hybrid-ARQ), L-ARQ (Last-ARQ), and P-ARQ (Packet-ARQ) bits are transmitted on the
38 ARQ Channel of the forward CDMA channel associated with the reverse CDMA channel.
12-94
1 An H-ARQ bit for an active reverse CDMA channel is transmitted on the ARQ Channel of
3 set by a sector in the access terminal’s active set following the reception of the first, second,
4 or third sub-packet, up to sub-packet (MaxNumSubPacketsI–1) of a physical layer packet
5 transmitted on interlace offset I on that active reverse CDMA channel, where
6 MaxNumSubPacketsI is public data of the Reverse Traffic Channel MAC Protocol. The H-
7 ARQ bit for an active reverse CDMA channel transmitted by a sector on the forward CDMA
8 channel in slots m, m+1, and m+2 indicates to the access terminal whether or not the
9 physical layer packet transmitted in slots m−8, m−7, m−6, and m−5 on that active reverse
10 CDMA channel was successfully received by the cell containing that sector. The sector
11 transmits the H-ARQ bit for an active reverse CDMA channel based on ARQMode for that
12 active reverse CDMA channel if the sector is part of the serving cell, where ARQMode is
13 public data of the Reverse Traffic Channel MAC Protocol. The ARQMode is a 1-bit value
14 that indicates the modulation (Bi-Polar (+1 implies ACK and −1 implies NAK) Keying or
15 ACK-oriented ON-OFF (+1 implies ACK and 0 implies NAK) Keying) of the H-ARQ bit for an
16 active reverse CDMA channel, if it is transmitted after the first, second, or third sub-
17 packets of a physical layer packet by a sector that is part of the serving cell. ARQMode 0
18 implies that the H-ARQ bit transmitted for an active reverse CDMA channel by a sector that
19 is part of the serving cell uses Bi-Polar Keying and ARQMode 1 implies that the H-ARQ bit
20 transmitted for an active reverse CDMA channel by a sector that is part of the serving cell
21 uses ACK-oriented ON-OFF Keying. A sector transmits the H-ARQ bit using ACK-oriented
22 ON-OFF Keying if the sector is not part of the serving cell.
23 The SofterHandoff public data of the RouteUpdateProtocolRoute Update Protocol indicates
24 whether or not two different sectors are transmitting the same ARQ bit for an active reverse
25 CDMA channel on the associated forward CDMA channelforward CDMA channel of the
26 associated sub-active set. In each slot containing an ARQ bit, the access terminal should
27 provide diversity combining of the identical ARQ channels for each active reverse CDMA
28 channel and shall obtain at most one ARQ bit from each set of the identical ARQ channels
29 for that active reverse CDMA channel.
30 The H-ARQ transmission rules are summarized in Table 12.3.2.4-1.
31 Table 12.3.2.4-1. H-ARQ Transmission Rules
Sector of
Serving ARQMode Modulation
Cell
Bi-Polar Keying
YES 0
(+1 ⇒ ACK, −1 ⇒ NAK)
YES 1
(+1 ⇒ ACK, 0 ⇒ NAK)
NO N/A
(+1 ⇒ ACK, 0 ⇒ NAK)
32
12-95
1 The L-ARQ bit for an active reverse CDMA channel is transmitted on the associated forward
2 CDMA channelforward CDMA channel of the associated sub-active set by a sector in the
3 access terminal’s active set following the reception of the (MaxNumSubPacketsI+1)th sub-
4 packet of a physical layer packet transmission on interlace offset I in slots m, m+1, and
5 m+2 on the active reverse CDMA channel indicates to the access terminal whether or not
6 the physical layer packet transmitted in slots m−8, m−7, m−6, and m−5 on that active
7 reverse CDMA channel was successfully received by the cell containing that sector, where
8 MaxNumSubPacketsI is public data of the Reverse Traffic Channel MAC Protocol. The
9 sector transmits the L-ARQ bit using NAK-oriented ON-OFF Keying (0 implies ACK, −1
10 implies NAK) in slots m, m+1, and m+2 of the forward CDMA channel associated with the
11 reverse CDMA channel following the reception of the (MaxNumSubPacketsI+1)th sub-packet
12 of a physical layer packet transmitted in slots m−8, m−7, m−6, and m−5, on that active
13 reverse CDMA channel, on interlace offset I.
14 The P-ARQ bit for an active reverse CDMA channel is transmitted on associated the forward
15 CDMA channel by a sector in the access terminal’s active set in slots m, m+1, and m+2 on
16 the active reverse CDMA channel indicates to the access terminal whether or not the
17 physical layer packet that was transmitted starting in slot m−(MaxNumSubPacketsI +1)×12
18 on that active reverse CDMA channel was successfully received by the cell containing that
19 sector if transmitted in interlace offset I,. The access network transmits the P-ARQ bit using
20 NAK-oriented ON-OFF Keying in slots m, m+1, and m+2 in response to a physical layer
21 packet that was transmitted starting in slot m−48.
23 packet transmitted over all four sub-packets on an active reverse CDMA channel, with
24 MaxNumSubPacketsI for that interlace offset on that reverse CDMA channel equal to three.
25 In this case, the access network transmits ACK or NAK responses on the forward CDMA
26 channel associated with that reverse CDMA channel. The access network transmits NAK
27 responses on the ARQ Channel using the H-ARQ bit after the first three sub-packets of the
28 physical layer packet are transmitted by the access terminal indicating that it was unable
29 to successfully receive the Reverse Traffic Channel packet after the first, second, and third
30 sub-packets. After the fourth sub-packet the sector transmits an ACK using the L-ARQ bit
31 and the P-ARQ bit indicating that the sector successfully received the Reverse Traffic
32 Channel physical layer packet.
33 The access terminal shall stop transmission of a packet on the Reverse Traffic Channel of
34 an active reverse CDMA channel , if it receives a positive acknowledgement for that packet
35 on the associated forward CDMA channelforward CDMA channel of the associated sub-
36 active set from any sector in its active set.
37 The access terminal shall stop transmission of a packet on the Reverse Traffic Channel of
38 an active reverse CDMA channel if the transmitted packet’s sub-packet index on that
39 reverse CDMA channel is greater than MaxNumSubPacketsI when transmitting on
40 interlace-offset I.
12-96
1 If the access terminal has not received a positive acknowledgment168

2 (MaxNumSubPacketsI+1)× 12 + 2 slots after the start of a physical layer packet
3 transmission on the Reverse Traffic Channel on an active reverse CDMA channel, for
4 transmissions on interlace offset I of that reverse CDMA channel, then this protocol shall
5 return a ReverseTrafficPacketsMissed indication corresponding to that reverse CDMA
6 channel, indication along with parameters that uniquely identify the lost MAC, Security,
7 Connection, Session, Stream, and Application Layer packets.
9 packet transmitted over two sub-packets on an active reverse CDMA channel, on interlace-
10 offset I with MaxNumSubPacketsI equal to three. In this example, the access network
11 transmits ACK or NAK responses on the forward CDMA channel associated with that
12 reverse CDMA channel. The access network transmits an ACK response on the ARQ
15 reception of a positive acknowledgment on the ARQ Channel, the access terminal shall not
16 transmit the remaining sub-packets of the physical layer packet on that reverse CDMA
17 channel. The access terminal may begin transmission of a new physical layer packet on
18 that interlace of that reverse CDMA channel. The access network transmits an ACK on the
19 ARQ Channel on the forward CDMA channel associated with that reverse CDMA channel,
20 using the P-ARQ bit in sub-frame n+12.
22 packet transmitted over all four sub-packets on an active reverse CDMA channel, on
23 interlace-offset I with MaxNumSubPacketsI equal to three. In this case, the access network
24 transmits ACK or NAK responses on the forward CDMA channel associated with that
25 reverse CDMA channel. The access network transmits NAK responses on the ARQ Channel
26 using the H-ARQ bit after the first three sub-packets of the physical layer packet are
27 transmitted by the access terminal indicating that it was unable to correctly receive the
29 fourth sub-packet the access network transmits a NAK on the ARQ Channel using both the
30 L-ARQ bit and the P-ARQ bit indicating that it was unable to successfully receive the
31 packet.
168 Unless the access terminal has received a NAK on the L-ARQ or P-ARQ channels, the access
terminal does not indicate it has received a positive acknowledgement from a non-serving cell if the
DRCLock bit from that cell for the reverse CDMA channel is out of lock.
12-97
P-ARQ bit on
ARQ Channel
ACK
1 Sub-frame
L-ARQ bit on
ARQ Channel
1 Sub-frame ACK
3 Slots
H-ARQ bit on
ARQ Channel
NAK NAK NAK

First Sub-packet
for the Next
Physical Layer
Packet
Transmission
Transmit Transmit Transmit Transmit Transmit

Reverse Traffic Sub-packet Sub-packet Sub-packet Sub-packet Sub-packet
Channel Physical 1 2 3 4 1
Layer Packet
Transmissions
Sub-frames n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n + 9 n + 10 n + 11 n + 12

1
3 Transmit Duration
12-98

3 Termination
12-99
2 Figure 12.3.2.4-3. Reverse Traffic Channel Packet Transmission Failure
3 13.3.312.3.3 Synchronization and Timing

21 second.
12-100
2 Reverse Traffic Channel. If PNRandomizationDelay is non-zero, the access terminal shall
3 transmit the Access Channel using the access terminal time reference plus
4 PNRandomizationDelay for each probe, where PNRandomizationDelay is public data of the
5 Access Channel MAC Protocol.
12-101



9 The average frequency difference between the actual sector transmit carrier frequency for
10 each forward CDMA channel and the specified sector transmit frequency assignment for
11 that forward CDMA channel shall be less than ±5 × 10-8 of the frequency assignment
12 (±0.05 ppm).


17 The Forward Channel shall have the overall structure shown in Figure 12.4.1.3.1-1 for a
18 forward CDMA channel. The Forward Channel for each forward CDMA channel shall
19 consist of the following time-multiplexed channels: the Pilot Channel, the Forward Medium
20 Access Control (MAC) Channel, and the Forward Traffic Channel or the Control Channel.
21 The Traffic Channel corresponding to a forward CDMA channel carries user physical layer
22 packets. The Control Channel carries control messages, and it may also carry user traffic.
23 Each channel is further decomposed into code-division-multiplexed quadrature Walsh
24 channels.
25 The forward link corresponding to a forward CDMA channel shall consist of slots of length
26 2048 chips (1.66… ms). Groups of 16 slots shall be aligned to the PN rolls of the zero-offset
27 PN sequences and shall align to CDMA System Time on even-second ticks.
28 For every forward CDMA channel, within each slot, the Pilot, MAC, and Traffic or Control
29 Channels shall be time-division multiplexed as shown in Figure 12.4.1.3.1-2 and shall be
30 transmitted at the same power level.
31 The Pilot Channel for a forward CDMA channel, shall consist of all-‘0’ symbols transmitted
32 on the I-branch with Walsh cover 0. Each slot shall be divided into two half slots, each of
12-102
1 which contains a pilot burst. Each pilot burst shall have a duration of 96 chips and be
2 centered at the midpoint of the half slot.169
3 The MAC Channel for a forward CDMA channel, shall consist of four subchannels: the
4 Reverse Power Control (RPC) Channel, the DRCLock Channel, the Reverse Activity (RA)
5 Channel and the ARQ Channel. The RPC Channel for a reverse CDMA channel is
6 transmitted on the associated forward CDMA channelforward CDMA channel of the
7 associated sub-active set transmits power control commands used by the access terminal
8 for closed loop power control on that reverse CDMA channel. The DRCLock Channel
9 transmits a reverse link quality indication for a reverse CDMA channel is transmitted on
11 set and is used by the access terminal for forward link serving sector selection for each
12 forward CDMA channel. The RA Channel transmits a reverse link activity bit (RAB) stream
13 for a reverse CDMA channel is transmitted on the associated forward CDMA
14 channelforward CDMA channel of the associated sub-active set. The ARQ Channel
15 transmits an access terminal specific indication of whether or not Reverse Traffic Channel
16 packets from that access terminal were received successfully by the access network for a
17 reverse CDMA channel on the associated forward CDMA channelforward CDMA channel of
18 the associated sub-active set. Each MAC Channel symbol shall be BPSK or OOK modulated
19 on the in-phase or quadrature-phase of one of 128 128-ary Walsh codewords (covers). For
20 MAC indices less than 128, The MAC symbol Walsh covers shall be transmitted two times
21 per slot in four bursts of 64 chips each. If the MAC indexMAC Index is greater than or
22 equal to 128 but less than 256, the corresponding MAC symbol Walsh cover shall be
23 transmitted during the first half of each slot in two bursts of 64 chips each. If the MAC
24 indexMAC Index is greater than or equal to 256 but less than 384, the corresponding MAC
25 symbol Walsh cover shall be transmitted during the second half of each slot in two bursts
26 of 64 chips each. A burst shall be transmitted immediately preceding each of the pilot
27 bursts in a slot, and a burst shall be transmitted immediately following each of the pilot
28 bursts in a slot. The Walsh channel gains may vary the relative power.
30 layer packets for an access terminal shall be transmitted as shown in Table 12.4.1.3.1.1-1
31 at a data rate that varies from 4.8 kbps to 3.072 Mbps170, and the optional user physical
32 layer packets as shown in Table 12.4.1.3.1.1-1, if transmitted, shall be transmitted at a
33 data rate that varies from 153.6 kbps to 4.915 Mbps. Forward Traffic Channel and Control
34 Channel physical layer packets are defined using a Transmission Format. The
35 Transmission Format consists of the following:
36 • Physical Layer Packet Size of the physical layer packet (in bits)
12-103
1 • Nominal Transmit Duration of the physical layer packet (in slots)

2 • Preamble Length associated with the physical layer packet (in chips)
3 The Transmission Format is public data of the Forward Traffic Channel MAC Protocol. For
4 example, (1024, 1, 64) indicates a 1024-bit physical layer packet with a nominal transmit
5 duration of 1 slot with a 128-chip preamble.
9 PSK/16-QAM/64-QAM modulator. The modulated symbol sequences shall be repeated and
12 stream with a rate of 76.8ksps is covered with a distinct Walsh function of length 16. The
16 form the resultant sequence of chips for the quadrature spreading operation. Forward
17 Traffic Channel and Control Channel physical layer packets can be transmitted in 1 to 16
18 slots (see Table 12.4.1.3.1.1-1). When more than one slot is allocated for a forward CDMA
19 channel, the transmit slots shall use 4-slot interlacing. That is, the transmit slots of a
20 physical layer packet corresponding to a forward CDMA channel shall be separated by
21 three intervening slots, and slots of other physical layer packets shall be transmitted in the
22 slots between those transmit slots.
23 Figure 12.3.1.3.1-16 and Figure 12.3.1.3.1-17 illustrate the multislot interlacing approach
24 for a 153.6 kbps Forward Traffic Channel packet with Transmission Format (1024, 4, 256)
25 with DRCLength of one slot. The 153.6 kbps Forward Traffic Channel physical layer packet
26 with Transmission Format (1024, 4, 256) uses four slots, and these slots are transmitted
27 with a three-slot interval between them, as shown in the figures. The slots from other
28 physical layer packets are interlaced in the three intervening slots. Figure 12.3.1.3.1-16
29 shows the case of a normal physical layer packet termination. In this case, the access
41 received a positive ACK response for a forward CDMA channel, the physical layer shall
42 return a ForwardTrafficCompleted indication.
12-104
1 The Control Channel, if transmitted on a forward CDMA channel, shall be transmitted

2 using the Transmission Formats of (128, 4, 1024), (128, 4, 256), (256, 4, 1024), (256, 4,
3 256), (512, 4, 1024), (1024, 16, 1024), and (1024, 8, 512). The modulation characteristics
4 for the Control Channel shall be the same as those of the Forward Traffic Channel
5 transmitted using the corresponding Transmission Format.
10
12-105
Forward Traffic I
QPSK/ C
Channel or Encoder 8-PSK/
Channel
Control Channel R = 1/3 16-QAM/
Modulator D
Packets
I I I I I I
C Sequence Walsh
Symbol 16-ary Walsh
Repetition/ Channel
D Puncturing 1/4
128-Symbol Bi-
Orthogonal Cover
with MACIndex i I
Signal Point I Channel For
Preamble Sequence
Mapping i<128 and Q
(All 0's) Puncture/
0 +1 Channel for Q
1 –1 Repetition
i > 128
64 to 1,024
128-ary Walsh Cover for RPC bits: PN Chips
MACIndex i I Channel for Even MACIndex, per Physical
Q Channel for Odd MACIndex Layer Packet
Signal Point
MAC Channel RPC bits for H-ARQ or L-ARQ bits: for Preamble
Mapping RPC Channel
MACIndex i, 150 bps 0 +1 Gain: G-rpc(i) I Channel for Even MACIndex,
(T-FrameOffset) mod 4 = 3 1 –1 Q Channel for Odd MACIndex
TDM
MAC Channel H-ARQ bits or L- 1:3
ARQ bits for MACIndex i ARQ Signal ARQ Channel I Walsh
(T-FrameOffset) mod 4 ≠ 3 Point Mapping Gain: G-arq(i) Channels
A
128-ary Walsh Cover for DRC Lock bits:
TDM
MACIndex i Q Channel for Even MACIndex,
I Channel for Odd MACIndex B
MAC Channel P-ARQ bits for Signal Point P-ARQ bits:
MACIndex i Mapping ARQ Channel Q Channel for Even MACIndex, Q Walsh
(T-FrameOffset) mod 4 ≠ 3 0 0 Gain: G-arq(i) I Channel for Odd MACIndex Channels
1 -1
TDM
MAC Channel DRCLock 3:1
symbols for MACIndex i Signal Point
Bit Repetition DRCLock
(150/DRCLockLength) bits Mapping
(Factor = Channel Gain: I I
per second 0 +1
DRCLockLength/4) G-drclock(i)
(T-FrameOffset) mod 4 = 3 1 –1 Walsh Sequence
Walsh Cover W128 Chip Level Repetition
j
Summer Q (Factor = 2) Q
for RABMACIndex j
RA
RA Bits for RABMACIndex j Mapping 256 PN Chips
Channel
1 Bit per Slot 0 +1 per Slot
Gain
(600 bps) 1 –1 for MAC
Walsh Cover 0
Signal Point
(All 0’s) 0 +1
1 –1
Q
0
cos(2 fCt)
192 PN Chips
per Slot
for Pilot
I I Baseband
A
Filter
Quadrature Spreading
Forward
(Complex Multiply)
Modulated
I = I PNI – Q PNQ
Waveform
Q = I PNQ + Q PNI
Q Q Baseband
B
Filter

PNI PNQ values with the mapping +1 for binary
I-Channel PN Q-Channel ‘0’ and –1 for binary ‘1’.
Sequence PN Sequence
1.2288 Mcps 1.2288 Mcps
1
12-106
1/2 Slot 1/2 Slot

400 64 96 64 400 400 64 96 64 400
Active Slot

64 96 64 64 96 64
Idle Slot
1

4 The access network and access terminal shall support the physical layer packet formats for
5 the Forward Traffic Channel and the Control Channel as shown in Table 12.4.1.3.1.1-1.
6 The access network and access terminal should support the physical layer packet formats
7 for the Forward Traffic Channel as shown in Table 12.4.1.3.1.1-2.
8 If ExtendedSpansEnabled equals ‘1’ the access network shall support transmission of
9 physical layer packet formats with packet extensions and the access terminal shall support
10 reception of physical layer packet formats with packet extensions.
11 If ExtendedSpansEnabled equals ‘1’, the termination target of the requested DRC is one
12 slot, the access terminal is unable to successfully receive the physical layer packet after the
13 first slot, and the access network transmits an extension slot, then the access network
14 shall transmit the second slot as that of a packet transmission format with the same
15 physical layer packet size, a termination target for two slots, and the same preamble
16 length.
18 slot or two slots, the access terminal is unable to successfully receive the physical layer
19 packet after the first two slots, and the access network transmits an extension slot, then
20 the access network shall transmit the third slot using the extension preamble and the
21 same data chips as transmitted during the first slot.
23 slot or two slots, the access terminal is unable to successfully receive the physical layer
24 packet after the first three slots, and the access network transmits an extension slot, then
25 the access network shall transmit in the fourth slot the same data chips as transmitted
26 during the second slot.
27 If ExtendedSpansEnabled equals ‘1’, the termination target of the requested DRC is four
28 slots, the access terminal is unable to successfully receive the physical layer packet after
29 the first four slots, and the access network transmits an extension slot, then the access
30 network shall transmit the fifth slot using the extension preamble and the same data chips
31 as transmitted during the first slot.
12-107
3 the first five slots, and the access network transmits an extension slot, then the access
4 network shall transmit in the sixth slot the same data chips transmitted during the second
5 slot.
8 the first six slots, and the access network transmits an extension slot, then the access
9 network shall transmit in the seventh slot the same data chips transmitted during the third
10 slot.
13 the first seven slots, and the access network transmits an extension slot, then the access
14 network shall transmit in the eighth slot the same data chips transmitted during the fourth
15 slot.
16 If the access network transmits an extension slot for a packet the access network shall
17 transmit it using the same scrambler seed as used for the first slot of the corresponding
18 packet.
19
12-108
2 Control Channel
Transmission Format
Length (chips))
(128, 16, 1024) 1/5 QPSK 4.8

(128, 8, 512) 1/5 QPSK 9.6
(128, 4, 1024) 1/5 QPSK 19.2
(128, 4, 256) 1/5 QPSK 19.2
(128, 2, 128) 1/5 QPSK 38.4
(128, 1, 64) 1/5 QPSK 76.8
(256, 16, 1024) 1/5 QPSK 9.6
(256, 8, 512) 1/5 QPSK 19.2
(256, 4, 1024) 1/5 QPSK 38.4
(256, 4, 256) 1/5 QPSK 38.4
(256, 2, 128) 1/5 QPSK 76.8
(256, 1, 64) 1/5 QPSK 153.6
(512, 16, 1024) 1/5 QPSK 19.2
(512, 8, 512) 1/5 QPSK 38.4
(512, 4, 1024) 1/5 QPSK 76.8
(512, 4, 256) 1/5 QPSK 76.8
(512, 4, 128) 1/5 QPSK 76.8
(512, 2, 128) 1/5 QPSK 153.6
(512, 2, 64) 1/5 QPSK 153.6
(512, 1, 64) 1/5 QPSK 307.2
(1024, 16, 1024) 1/5 QPSK 38.4
(1024, 8, 512) 1/5 QPSK 76.8
(1024, 4, 256) 1/5 QPSK 153.6
(1024, 4, 128) 1/5 QPSK 153.6
(1024, 2, 128) 1/5 QPSK 307.2
(1024, 2, 64) 1/5 QPSK 307.2
(1024, 1, 64) 1/3 QPSK 614.4
(2048, 4, 128) 1/3 QPSK 307.2
(2048, 2, 64) 1/3 QPSK 614.4
12-109
Transmission Format
Length (chips))
(2048, 1, 64) 1/3 QPSK 1,228.8

(3072, 2, 64) 1/3 8-PSK 921.6
(3072, 1, 64) 1/3 8-PSK 1,843.2
(4096, 2, 64) 1/3 16-QAM 1,228.8
(4096, 1, 64) 1/3 16-QAM 2,457.6
(5120, 2, 64) 1/3 16-QAM 1,536.0
(5120, 1, 64) 1/3 16-QAM 3,072.0
1 Table 12.4.1.3.1.1-2. Modulation Parameters for the Optional Packet Formats on the
2 Forward Traffic Channel
Transmission Format
Length (chips))
(1024, 4, 64) 1/5 QPSK 153.6

(2048, 4, 64) 1/3 QPSK 307.2
(3072, 4, 64) 1/3 QPSK 460.8
(4096, 4, 64) 1/3 QPSK 614.4
(5120, 4, 64) 1/3 8-PSK 768.0
(6144, 4, 64) 1/3 16-QAM 921.6
(6144, 2, 64) 1/3 64-QAM 1,843.2
(6144, 1, 64) 1/3 64-QAM 3,686.4
(7168, 4, 64) 1/3 16-QAM 1,075.2
(7168, 2, 64) 1/3 64-QAM 2,150.4
(7168, 1, 64) 1/3 64-QAM 4300.8
(8192, 4, 64) 1/3 16-QAM 1,228.8
(8192, 2, 64) 1/3 64-QAM 2,457.6
(8192, 1, 64) 1/3 64-QAM 4,915.2
5 3.
12-110

Rate(bps) 150 150/(DRCLockLength) 600
Bit Repetition
1 DRCLockLength 1
Factor
Modulation BPSK(I or Q)
BPSK(I or Q) BPSK(I)
(Channel)
300 (for MAC indices
Modulation 300 (for MAC indices less
less than 128) and 150
Symbol Rate than 128) and 150 (for MAC 1,200
(sps) (for MAC indices greater
indices greater than 128)
than 128)
Walsh Cover
128 128 128
Length
2 (for MAC indices less
Walsh Sequence 2 (for MAC indices less
than 128) and 1 (for
Repetition than 128) and 1 (for MAC 2
Factor MAC indices greater
indices greater than 128)
than 128)
256 (for MAC indices 256 (for MAC indices below
below 128) and 128 (for 128) and 128 (for MAC
PN Chips/Slot 256
MAC indices greater indices greater than 128)
than 128)
256 (for MAC indices 256 × DRCLockLength (for
less than 128) and 128 MAC indices less than 128)
PN Chips/Bit 256
(for MAC indices greater and 128 (for MAC indices
128) above 128)
2 13.4.1.3.1.212.4.1.3.1.2 Data Rates

3 The Forward Traffic Channel corresponding to a forward CDMA channel shall support
4 variable-data-rate transmission, as shown in Table 12.4.1.3.1.1-1 and should support
5 variable-data-rate transmission as shown in Table 12.4.1.3.1.1-2.
6 The data rate of the Control Channel shall be 76.8 kbps (Transmission Format of (512, 4,
7 1024) or (1024, 8, 512)), 38.4 kbps (Transmission Format of (256, 4, 1024), (256, 4, 256),
8 or (1024, 16, 1024)), or 19.2 kbps (Transmission Format of (128, 4, 1024) or (128, 4, 256)).
10 13.4.1.3.2.112.4.1.3.2.1 Pilot Channel

11 A Pilot Channel shall be transmitted by the sector on each forward CDMA channel as
14 area of the sector.
12-111
1 13.4.1.3.2.1.112.4.1.3.2.1.1 Modulation
2 The Pilot Channel corresponding to a forward CDMA channel shall consist of all-‘0’ symbols
3 transmitted on the I component only.

5 The Pilot Channel corresponding to a forward CDMA channel shall be assigned Walsh cover
6 0.

8 See 12.3.1.3.12.

10 The Forward MAC Channel corresponding to a forward CDMA channel shall be composed
11 of Walsh channels that are orthogonally covered and BPSK modulated or OOK (ON-OFF
12 Keying) modulated on each phase of the carrier (either in-phase or quadrature phase. Each
13 Walsh channel for each forward CDMA channel shall be identified by a
14 ReverseLinkMACIndex value that is between 0 and 383 and defines a unique 128-ary
15 Walsh cover and a unique modulation phase. The Walsh functions assigned to the
16 ReverseLinkMACIndex values shall be as shown in Table 12.4.1.3.2.2-1.
17 Table 12.4.1.3.2.2-1. Forward Link MAC Channel Assignment
ReverseLink Transmit 128-ary (T – FrameOffset) (T – FrameOffset) mod 4

MACIndex, Time Walsh mod 4 = 3 ≠3
Function
4, 6, 8, …, Both 1st Wi128

/2
RPC or DRCLock ARQ ARQ
62 and 2nd RA (if RA is
(H-ARQ (P-ARQ bit) (if
half of not
bit or L- RA is not
the slot transmitt
ARQ bit) transmitted
ed on
on MAC
MAC
Index i)
Index i)
5 (if Both 1st W(128

i −1) / 2 + 32
DRCLock RPC (if ARQ ARQ
broadcast is and 2nd or RA RA is not
(P-ARQ (H-ARQ bit or
not half of transmitt
bit) L-ARQ bit) (if
negotiated), the slot ed on
RA is not
7, 9, …, 63 MAC
transmitted
Index i)
on MAC
Index i)
72,74,…,126 Both 1st Wi128

/ 2 + 32
RPC or DRCLock ARQ ARQ
and 2nd RA (if RA is
(H-ARQ (P-ARQ bit) (if
half of not
bit or L- RA is not
the slot transmitt
12-112

Function
ed on ARQ bit) transmitted

MAC on MAC
Index i) Index i)
73,75,….,127 Both 1st W(128

i −1) / 2 + 64
DRCLock RPC (if ARQ ARQ
and 2nd or RA RA is not
half of transmitt
bit) L-ARQ bit) (if
the slot ed on
RA is not
MAC
transmitted
Index i)
on MAC
Index i)
130, 132, …, 1st half of Wi128

/2
RPC DRCLock ARQ ARQ
190 the slot
(H-ARQ (P-ARQ bit)
only W(128
i −128 ) / 2
bit or L-
ARQ bit)
131, 133, … , 1st half of W(128

i −1) / 2 + 32
DRCLock RPC ARQ ARQ
191 the slot
only W(128
i −128 −1) / 2 + 32
bit) L-ARQ bit)
194, 196, …, 1st half of Wi128

/ 2 + 32
RPC DRCLock ARQ ARQ
254 the slot
(H-ARQ (P-ARQ bit)
only W(128
i −128 ) / 2 + 32
bit or L-
ARQ bit)
195, 197, … , 1st half of W(128

i −1) / 2 + 64
DRCLock RPC ARQ ARQ
255 the slot
only W(128
i −128 −1) / 2 + 64
bit) L-ARQ bit)
258, 260, …, 2nd half of Wi128

/2
RPC DRCLock ARQ ARQ
318 the slot
(H-ARQ (P-ARQ bit)
only W(128
i − 256 ) / 2
bit or L-
ARQ bit)
259, 261, … , 2nd half of W(128

i −1) / 2 + 32
DRCLock RPC ARQ ARQ
319 the slot
only W(128
i − 256 −1) / 2 + 32
bit) L-ARQ bit)
322, 324, …, 2nd half of Wi128

/ 2 + 32
RPC DRCLock ARQ ARQ
382 the slot
(H-ARQ (P-ARQ bit)
only W(128
i − 256 ) / 2 + 32
bit or L-
ARQ bit)
12-113

Function
323, 325, … , 2nd half of W(128

i −1) / 2 + 64
DRCLock RPC ARQ ARQ
383 the slot
only W(128
i − 256 −1) / 2 + 64
bit) L-ARQ bit)
1
2 RPC Channels with even-numbered ReverseLinkMACIndex values shall be assigned to the

3 in-phase (I) modulation phase, while those with odd-numbered ReverseLinkMACIndex
4 values shall be assigned to the quadrature (Q) modulation phase. RPC Channels for each
5 active reverse CDMA channel, shall be transmitted on the associated forward CDMA
6 channelforward CDMA channel of the associated sub-active set in slots T specified by the
8 (T-FrameOffset) mod 4 = 3,
9 where T is the CDMA System Time in slots and FrameOffset is the frame offset assigned to
11 The DRCLock Channel with even-numbered ReverseLinkMACIndex values shall be
12 assigned to the quadrature (Q) modulation phase, while those with odd-numbered
13 ReverseLinkMACIndex values shall be assigned to the in-phase (I) modulation phase. The
14 DRCLock Channel for each active reverse CDMA channel, shall be transmitted on the
15 associated forward CDMA channelforward CDMA channel of the associated sub-active set
16 in slots T specified by the following equation:
17 (T – FrameOffset) mod 4 = 3,
19 The ARQ Channel for each active reverse CDMA channel, shall not be transmitted on the
21 in slots other than T specified by the following equation:
24 The H-ARQ bit, L-ARQ bit and P-ARQ bits shall be transmitted on the ARQ Channel using
25 rules specified in 12.3.2.4.
26 When the H-ARQ bit is transmitted on the ARQ Channel with even-numbered
27 ReverseLinkMACIndex values the H-ARQ bit shall be assigned to the in-phase (I)
28 modulation phase. When the H-ARQ bit is transmitted on the ARQ Channel with odd-
29 numbered ReverseLinkMACIndex values the H-ARQ bit shall be assigned to the quadrature
30 (Q) modulation phase.
31 When the L-ARQ bit is transmitted on the ARQ Channel with even-numbered
32 ReverseLinkMACIndex values the L-ARQ bit shall be assigned to the in-phase (I)
33 modulation phase. When the L-ARQ bit is transmitted on the ARQ Channel with odd-
12-114
1 numbered ReverseLinkMACIndex values the L-ARQ bit shall be assigned to the quadrature
2 (Q) modulation phase.
3 When the P-ARQ bit is transmitted on the ARQ Channel with even-numbered
4 ReverseLinkMACIndex values the P-ARQ bit shall be assigned to the quadrature (Q)
5 modulation phase. When the P-ARQ bit is transmitted on the ARQ Channel with odd-
6 numbered ReverseLinkMACIndex values the P-ARQ bit shall be assigned to the in-phase (I)
7 modulation phase.
8 For MAC indices less than 128, the MAC symbol Walsh covers shall be transmitted two
9 times per slot in four bursts of length 64 chips each. For MAC indices greater than or equal
10 to 128 but less than 256, the MAC symbol Walsh covers shall be transmitted once per slot
11 during the first half-slot in two bursts of length 64 chips each. For MAC indices greater
12 than or equal to 256 but less than 384, the MAC symbol Walsh covers shall be transmitted
13 once per slot during the second half-slot in two bursts of length 4 chips each. These bursts
14 shall be transmitted immediately preceding and following the pilot bursts of each slot. The
15 MAC Channel use versus ReverseLinkMACIndex shall be as specified in Table 12.4.1.3.2.2-
16 2. The Preamble use versus ReverseLinkMACIndex shall be as specified in Table
17 12.4.1.3.2.2-3.
20 Walsh channels shall be scaled to maintain a constant total transmit power for each
21 forward CDMA channel. The Walsh Channel gains can vary as a function of time.
12-115
1 Table 12.4.1.3.2.2-2. MAC Channel Versus MACIndex
MACIndex MAC Channel Use
0 and 1 Not Used

2 Not Used
3 Not Used
4-63, Available for RPC Channel, DRCLock Channel,
66-127 ARQ Channel, and RA Channel (if specified by
the Route Update Protocol)
64-,65, Not Used

128-129,
192-193,
256-257,
320-321,
384-512
130-191 Available for RPC Channel, DRCLock Channel
194-255, and , ARQ Channel
258-319,
322-383
2
12-116
1 Table 12.4.1.3.2.2-3. Preamble Use Versus MACIndex
MACIndex Preamble Use Preamble Length
0 and 1 Not Used N/A

2 512
(1024, 8, 512)
3 1024
(1024, 16, 1024)
Available for Forward Traffic Channel
Transmissions of Single User packets
4 (if not assigned to RABMACIndex) Variable
Available for Extension Preamble if
assigned to RABMACIndex
Broadcast, Forward Traffic Channel
5 or RABMACIndex (if Broadcast is not Variable
negotiated)
64 and 65 Not Used N/A
Multi-User packet (if
MUPPreambleBase equals 66)
(128, 4, 256)
66 256
(256, 4, 256)
(512, 4, 256)
(1024, 4, 256)
67 MUPPreambleBase equals 66) 128
(2048, 4, 128)
(3072, 2, 64)
(4096, 2, 64)
(5120, 2, 64)
12-117
MACIndex Preamble Use Preamble Length

(128, 4, 1024), (128, 4, 256)
38.4 kbps Control Channel 256,
71
(256, 4, 1024), (256, 4, 256) 1024
(512, 4, 1024)
Available for Forward Traffic Channel
6–63, Transmissions of Single User packets
72-127, (if not assigned to RABMACIndex) or Variable
Multi-User packets (if
MUPPreambleBase not equal to 66)
130-191, Available for Forward Traffic Channel
Variable
194-255 Transmissions of Single User packets
128-129,
192-193, Not Used N/A
256-512,
1

3 The Reverse Power Control (RPC) Channel for each access terminal’s active reverse CDMA
4 channel with an open connection shall be assigned to one of the available MAC Channels
5 on the associated forward CDMA channelforward CDMA channel of the associated sub-
6 active set. It is used for the transmission of the RPC bit stream associated with that reverse
7 CDMA channel destined to that access terminal. On the forward CDMA channel, the RPC
8 Channel and the DRCLock Channel shall be transmitted on the in-phase and quadrature-
9 phase of the same MAC Channel according to the assignment defined in Table
10 12.4.1.3.2.2-1. The RPC Channel for each active reverse CDMA channel shall be time-
11 division multiplexed with the ARQ Channel for that reverse CDMA channel and transmitted
12 in 1 slot out of every 4 slots.
13 The RPC data rate shall be 150 bps. For each active reverse CDMA channel, the access
14 network shall transmit an RPC bit in every slot T on the forward link specified using the

18 For MAC indices less than 128, each RPC bit shall be transmitted two times in a slot in
19 four bursts of 64 chips each. For MAC indices greater than or equal to 128 but less than
20 256, each RPC bit shall be transmitted once per slot during the first half of the slot in two
21 bursts of 64 chips each. For MAC indices greater than or equal to 256 but less than 384,
22 each RPC bit shall be transmitted once per slot during the second half of the slot in two
12-118
1 bursts of 64 chips each. One burst shall be transmitted immediately preceding and
2 following each pilot burst in a slot as shown in Figure 12.4.1.3.1-2.
3 13.4.1.3.2.2.212.4.1.3.2.2.2 DRCLock Channel

4 The DRCLock Channel for each access terminal’s reverse CDMA channel with an open
5 connection shall be assigned to one of the available MAC Channels on the associated
6 forward CDMA channelforward CDMA channel of the associated sub-active set It is used
7 for the transmission of the DRCLock bit stream destined to that access terminal. On a
8 forward CDMA channel, the RPC Channel and the DRCLock Channel for the corresponding
9 reverse CDMA channel, shall be transmitted on the in-phase and quadrature phase of the
10 same MAC Channel according to the assignment defined in Table 12.4.1.3.2.2-1. On a
11 forwardCDMA channel, the DRCLock Channel shall be time-division multiplexed with the
12 ARQ Channel and transmitted in one out of every 4 slots.
13 Each DRCLock bit shall be repeated and transmitted in DRCLockLength slots, where
15 DRCLock data rate shall be 150/(DRCLockLength) bps. For each active reverse CDMA
16 channel of a given access terminal, the access network shall transmit a DRCLock bit on the
18 in every slot T with

21 For MAC indices less than 128, each DRCLock bit shall be transmitted two times in a slot
22 in bursts of 64 chips each. For MAC indices greater than or equal to 128 but less than 256,
23 each DRCLock bit shall be transmitted once per slot during the first half of the slot in two
24 bursts of 64 chips each. For MAC indices greater than or equal to 256 but less than 384,
25 each DRCLock bit shall be transmitted once per slot during the second half of the slot in
26 two bursts of 64 chips each. One burst shall be transmitted immediately preceding and
27 following each pilot burst in a slot as shown in Figure 12.4.1.3.1-2. The value of the
28 DRCLock bit may change only in slot T specified by the following equation:
29 (T − FrameOffset) mod (4 × DRCLockLength) = 3,

33 the MAC Channel with the ReverseLinkMACIndices specified by the RABMACIndex
34 corresponding to each of the pilots in the Active Set and are public data of the Route
35 Update Protocol. Each RA bit shall be transmitted in every slot for every reverse CDMA
36 channel and the RA Channel data rate shall be 600 bps. The RA bit in each slot shall be
37 further repeated to form two symbols per slot for transmission.
12-119
1 12.4.1.3.2.2.4 ARQ Channel.

2 Each sector of an access network shall transmit a positive acknowledgment (ACK) or a
3 negative acknowledgment (NAK) in response to a physical layer packet using the ARQ
4 Channel for each active reverse CDMA channel. The H-ARQ, L-ARQ and P-ARQ bits are
5 transmitted on the ARQ Channel for each active reverse CDMA channel.
7 set following the reception of all subpackets up to subpacket MaxNumSubPacketsI-1 of a
8 physical layer packet transmitted on interlace offset I, where MaxNumSubPacketsI is public
9 data of the Reverse Traffic Channel MAC Protocol. The H-ARQ bit transmitted by a sector in
10 slots m, m+1, and m+2 indicates to the access terminal whether or not the physical layer
11 packet transmitted in slots m−8, m−7, m−6, and m−5 was successfully received by the cell
12 containing that sector. A sector transmits H-ARQ bits based on ARQMode if the sector is
13 part of the serving, where ARQMode is public data of the Reverse Traffic Channel MAC
14 Protocol. The ARQMode is a 1-bit value that indicates the modulation of the H-ARQ bit (Bi-
15 Polar(+1 implies ACK and −1 implies NAK) Keying or ACK-oriented ON-OFF(+1 implies ACK
16 and 0 implies NAK) Keying). ARQMode 0 implies that the H-ARQ bit transmitted by a sector
17 that is part of the serving cell uses Bi-Polar Keying and ARQMode 1 implies that the H-ARQ
18 bit is transmitted by a sector that is part of the serving cell uses ACK-oriented ON-OFF
19 Keying. A sector transmits the H-ARQ bit to an access terminal using Bi-Polar Keying or
20 ACK-oriented ON-OFF Keying if the sector is part of the serving cell. A sector transmits the
21 H-ARQ bit using ACK-oriented ON-OFF Keying if it is not part of the serving cell.
22 A sector shall transmit H-ARQ bits based on ARQMode if the sector is part of the serving
23 cell. The sector shall transmit the H-ARQ bit using Bi-Polar Keying or ACK-oriented ON-
24 OFF Keying (+1 implies ACK and 0 implies NAK) in slots m, m+1, and m+2 following
25 reception of all sub-packets up to subpacket MaxNumSubPacketsI-1 of a physical layer
26 packet transmitted on interlace offset I in slots m−8, m−7, m−6, and m−5 if the sector is
27 part of the serving cell. The sector shall transmit the H-ARQ bit using ACK-oriented ON-
28 OFF Keying in slots m, m+1, and m+2 following reception of all sub-packets up to
29 subpacket MaxNumSubPacketsI-1 of a physical layer packet transmitted on interlace offset
30 I in slots m−8, m−7, m−6, and m−5 if the sector is not part of the serving cell.
31 An L-ARQ bit is transmitted on the ARQ Channel by a sector in the access terminal’s active
32 set following the reception of the (MaxNumSubPacketsI+1)th sub-packet of a physical layer
33 packet transmitted on interlace offset I. The L-ARQ bit is transmitted in slots m, m+1, and
34 m+2 to indicate to the access terminal whether or not the physical layer packet transmitted
35 in slots m−8, m−7, m−6, and m−5 was successfully received by the cell containing that
36 sector.
37 The sector shall transmit the L-ARQ bit on the ARQ Channel using NAK-oriented ON-OFF
38 Keying (0 implies ACK, −1 implies NAK) in slots m, m+1, and m+2 following reception of the
39 (MaxNumSubPacketsI+1)th sub-packet of a physical layer packet transmitted on interlace
40 offset I in slots m−8, m−7, m−6, and m−5.
41 A P-ARQ bit transmitted on the ARQ Channel by a sector in the access terminal’s active set
42 in slots m, m+1, and m+2 indicates to the access terminal whether or not the physical layer
43 packet that was transmitted starting in slot m−(MaxNumSubPacketsI+1)×12 on interlace
12-120
1 offset I was successfully received by the cell containing that sector. The access network
2 shall transmit the P-ARQ bit using NAK-oriented ON-OFF Keying in slots m, m+1, and m+2
3 in response to a physical layer packet that was transmitted starting in slot
4 m−(MaxNumSubPacketsI+1)×12 on interlace offset I.
5 When the access network has received all slots of a physical layer packet or has
6 transmitted an ACK response, this protocol shall return a ReverseTrafficCompleted
7 indication.
8 The access network shall not forward the physical layer packet to a higher layer if the
13 Channel using the H-ARQ bits after the first three sub-packets of the physical layer packet
18 packet.
20 packet transmitted over two sub-packets, where MaxNumSubPacketsI equals to three for
21 that interlace. In this example, the access network transmits an ACK response on the ARQ
24 reception of a positive acknowledgment on the ARQ Channel, the access terminal does not
25 transmit the remaining slots of the physical layer packet. The access terminal may begin
26 transmission of a new physical layer packet on that interlace. The access network
34 fourth sub-packet the access network transmits an NAK on the ARQ Channel using both
35 the L-ARQ bit and the P-ARQ bit indicating that it was unable to successfully receive the
36 packet.

12-121
1 The preamble shall consist of all-‘0’ symbols. The preamble shall be transmitted on the in-
2 phase component for ForwardTrafficMACIndex less than 128 and shall be transmitted on
3 the quadrature-phase component for ForwardTrafficMACIndex greater than 128. The
4 preamble shall be time multiplexed into the Forward Traffic Channel stream as described
5 in 12.4.1.3.3. The preamble sequence shall be covered by a 128-chip bi-orthogonal
6 sequence and the sequence shall be repeated several times depending on the transmit
7 mode. The bi-orthogonal sequence shall be specified in terms of the 128-ary Walsh
9
128
10 Wi/2 for i = 0, 2, …., 254
11 W(i128
−1)/2 for i = 1, 3, …., 255
128
12 where i = 0, 1,…, 255 is the ForwardTrafficMACIndex value and Wi is the bit-by-bit
13 complement of the 128-chip Walsh function of order i. The channel type versus
14 ForwardTrafficMACIndex mapping for the preamble shall be as specified in Table
15 12.4.1.3.2.2-2. The 128-chip preamble repetition factor shall be as specified in Table
16 12.4.1.3.2.3.1-1. The access network shall transmit only the first 64-chips of the 128-ary
17 Walsh function for repetition factor of 0.5.
18 An extension preamble shall be transmitted with each Forward Traffic Channel physical
19 layer packet if ExtendedSpansEnabled is equal to ‘1’ in slots as shown in Table
20 12.4.1.3.2.3.1-2.
21 The extension preamble shall consist of all ‘0’ symbols transmitted on the in-phase
22 component only. The extension preamble shall be time multiplexed into the Forward Traffic
23 Channel stream. The extension preamble shall be covered by the 128-chip walsh sequence
24 W2128 and this sequence shall be repeated several times and the repetition factor shall be as
25 specified in Table 12.4.1.3.2.3.1-1.
26
12-122

(Physical Layer Packet Size(bits), Preamble
Termination Target(slots), Preamble Length Sequence
(chips)) Repetition
(128, 16, 1024) 8

(128, 4, 1024) 8
(128, 8, 512) 4
(128, 4, 256) 2
(128, 2, 128) 1
(128, 1, 64) 0.5
(256, 16, 1024) 8
(256, 4, 1024) 8
(256, 8, 512) 4
(256, 4, 256) 2
(256, 2, 128) 1
(256, 1, 64) 0.5
(512, 16, 1024) 8
(512, 4, 1024) 8
(512, 8, 512) 4
(512, 4, 256) 2
(512, 4, 128) 1
(512, 2, 128) 1
(512, 2, 64) 1
(512, 1, 64) 1
(1024, 16, 1024) 8
(1024, 8, 512) 4
(1024, 4, 256) 2
(1024, 4, 128) 1
(1024, 4, 64) 0.5
(1024, 2, 128) 1
(1024, 2, 64) 0.5
(1024, 1, 64) 0.5
(2048, 4, 128) 1
12-123

(Physical Layer Packet Size(bits), Preamble
Termination Target(slots), Preamble Length Sequence
(chips)) Repetition
(2048, 4, 64) 0.5

(2048, 2, 64) 0.5
(2048, 1, 64) 0.5
(3072, 2, 64) 0.5
(3072, 1, 64) 0.5
(4096, 2, 64) 0.5
(4096, 1, 64) 0.5
(5120, 2, 64) 0.5
(5120, 1, 64) 0.5
(6144, 4, 64) 0.5
(7168, 4, 64) 0.5
(8192, 4, 64) 0.5
1
12-124
1 Table 12.4.1.3.2.3.1-2. Extended Span and Extension Preamble Transmit Slot and
2 Repetition
Canonical Single Termination Maximum 128-chip Extension

User Transmission Target Span (slots) Extension Preamble
Format Preamble Transmit slot
(slots)
Repetition
(1024, 16, 1024) 16 16 NA NA

(1024, 16, 1024) 16 16 NA NA
(1024, 8, 512) 8 8 NA NA
(1024, 4, 256) 4 8 2 5
(1024, 2, 128) 2 4 1 3
(2048, 4, 128) 4 8 1 5
(1024, 1, 64) 1 4 0.5 3
(2048, 2, 64) 2 4 0.5 3
(3072, 2, 64) 2 4 0.5 3
(2048, 1, 64) 1 4 0.5 3
(4096, 2, 64) 2 4 0.5 3
(3072, 1, 64) 1 4 0.5 3
(4096, 1, 64) 1 4 0.5 3
(5120, 2, 64) 2 4 0.5 3
(5120, 1, 64) 1 4 0.5 3
(3072, 4, 64) 4 8 0.5 35
(4096, 4, 64) 4 8 0.5 5
(5120, 4, 64) 4 8 0.5 5
(6144, 4, 64) 4 8 0.5 5
(7168, 4, 64) 4 8 0.5 5
(8192, 4, 64) 4 8 0.5 5
(6144, 2, 64) 2 4 0.5 3
(7168, 2, 64) 2 4 0.5 3
(8192, 2, 64) 2 4 0.5 3
(6144, 1, 64) 1 4 0.5 3
(7168, 1, 64) 1 4 0.5 3
(8192, 1, 64) 1 4 0.5 3
3
12-125
1 13.4.1.3.2.3.212.4.1.3.2.3.2 Encoding
2 The Forward Traffic Channel physical layer packets and the Control Channel physical layer
3 packets shall be encoded with code rates of R = 1/3 or 1/5. The encoder shall discard the
4 6-bit TAIL field of the physical layer packet inputs and encode the remaining bits with a
5 parallel turbo encoder, as specified in 12.4.1.3.2.3.2.1. The turbo encoder will add an
6 internally generated tail of 6/R output code symbols, so that the total number of output
7 symbols is 1/R times the number of bits in the input physical layer packet.
10
12-126

(128, 16, 1024) 122 1/5 640

(128, 4, 1024) 122 1/5 640
(128, 8, 512) 122 1/5 640
(128, 4, 256) 122 1/5 640
(128, 2, 128) 122 1/5 640
(128, 1, 64) 122 1/5 640
(256, 16, 1024) 250 1/5 1,280
(256, 4, 1024) 250 1/5 1,280
(256, 8, 512) 250 1/5 1,280
(256, 4, 256) 250 1/5 1,280
(256, 2, 128) 250 1/5 1,280
(256, 1, 64) 250 1/5 1,280
(512, 16, 1024) 506 1/5 2,560
(512, 4, 1024) 506 1/5 2,560
(512, 8, 512) 506 1/5 2,560
(512, 4, 256) 506 1/5 2,560
(512, 4, 128) 506 1/5 2,560
(512, 2, 128) 506 1/5 2,560
(512, 2, 64) 506 1/5 2,560
(512, 1, 64) 506 1/5 2,560
(1024, 16, 1024) 1,018 1/5 5,120
(1024, 8, 512) 1,018 1/5 5,120
(1024, 4, 256) 1,018 1/5 5,120
(1024, 4, 128) 1,018 1/5 5,120
(1024, 4, 64) 1,018 1/5 5,120
(1024, 2, 128) 1,018 1/5 5,120
(1024, 2, 64) 1,018 1/5 5,120
(1024, 1, 64) 1,018 1/3 3,072
(2048, 4, 128) 2,042 1/3 6,144
12-127

(2048, 4, 64) 2,042 1/3 6,144

(2048, 2, 64) 2,042 1/3 6,144
(2048, 1, 64) 2,042 1/3 6,144
(3072, 4, 64) 3,066 1/3 9,216
(3072, 2, 64) 3,066 1/3 9,216
(3072, 1, 64) 3,066 1/3 9,216
(4096, 4, 64) 4,090 1/3 12,288
(4096, 2, 64) 4,090 1/3 12,288
(4096, 1, 64) 4,090 1/3 12,288
(5120, 4, 64) 5,114 1/3 15,360
(5120, 2, 64) 5,114 1/3 15,360
(5120, 1, 64) 5,114 1/3 15,360
(6144, 4, 64) 6,138 1/3 18,432
(6144, 2, 64) 6,138 1/3 18,432
(6144, 1, 64) 6,138 1/3 18,432
(7168, 4, 64) 7,162 1/3 21,504
(7168, 2, 64) 7,162 1/3 21,504
(7168, 1, 64) 7,162 1/3 21,504
(8192, 4, 64) 8,186 1/3 24,576
(8192, 2, 64) 8,186 1/3 24,576
(8192, 1, 64) 8,186 1/3 24,576
1
2 13.4.1.3.2.3.2.112.4.1.3.2.3.2.1 Turbo Encoder

⎡ n0 (D) n1(D) ⎤
G(D) = ⎢1 ⎥
⎣ d(D) d(D) ⎦⎥
9
12-128
25 output first.
12-129
X
Y0
n0
Y1
n1
Nturbo
Information
Bits
(Input)
Control
Puncturing Code
and Symbols
Turbo
Interleaver
X'
Y'0
n0
Y'1
n1
Control
1
12-130
Code Rate
Output 1/3 1/5
X 1 1
Y0 1 1
Y1 0 1
X′ 0 0
Y′ 0 1 1
Y′ 1 0 1

from top to bottom.
2
Code Rate
Output 1/3 1/5
X 111 000 111 000

Y0 111 000 111 000
Y1 000 000 111 000
X′ 000 111 000 111
Y′ 0 000 111 000 111
Y′ 1 000 000 000 111
4

12-131
Add 1
Counter Lookup
5 LSBs Bit 5 Bits

21
12-132
Turbo Turbo
Nturbo n
128 122 2
256 250 3
512 506 4
1,024 1,018 5
2,048 2,042 6
3,072 3,066 7
4,096 4,090 7
5,120 5,114 8
6,144 6,138 8
7,168 7,162 8
8,192 8,186 8
2
12-133
Table n=2 n=3 n=4 n=5 n=6 n=7 n=8

Index Entries Entries Entries Entries Entries Entries Entries
0 3 1 5 27 3 15 3
1 3 1 15 3 27 127 1
2 3 3 5 1 15 89 5
3 1 5 15 15 13 1 83
4 3 1 1 13 29 31 19
5 1 5 9 17 5 15 179
6 3 1 9 23 1 61 19
7 1 5 15 13 31 47 99
8 1 3 13 9 3 127 23
9 1 5 15 3 9 17 1
10 3 3 7 15 15 119 3
11 1 5 11 3 31 15 13
12 1 3 15 13 17 57 13
13 1 5 3 1 5 123 3
14 1 5 15 13 39 95 17
15 3 1 5 29 1 5 1
16 3 3 13 21 19 85 63
17 1 5 15 19 27 17 131
18 3 3 9 1 15 55 17
19 3 5 3 3 13 57 131
20 3 3 1 29 45 15 211
21 1 5 3 17 5 41 173
22 3 5 15 25 33 93 231
23 1 5 1 29 15 87 171
24 3 1 13 9 13 63 23
25 1 5 1 13 9 15 147
26 3 1 9 23 15 13 243
27 1 5 15 13 31 15 213
28 3 3 11 13 17 81 189
29 1 5 3 1 5 57 51
30 1 5 15 13 15 31 15
31 3 3 5 13 33 69 67
2
12-134
1 13.4.1.3.2.3.312.4.1.3.2.3.3 Scrambling
6 initialized to the state [ 1 r7 d 4 b 2 b1 b 0 r6 r5 r4 r3 r2 r1 r0 d 3 d 2 d1 d 0 ]. The r7r6r6r5r4r3r2r1r0
7 bits shall be equal to the 8-bit ForwardTrafficMACIndex value (see Table 12.4.1.3.2.2-2)
8 with r7 = 0 if MACIndexBits = 0x00 and shall be equal to the 8-bit ForwardTrafficMACIndex
9 value if MACIndexBits = 0x01. The d4d3d2d1d0 bits and the b2b1b0 bits shall as specified
10 in Table 12.4.1.3.2.3.3-1. The initial state shall generate the first scrambling bit. The shift
11 register shall be clocked once for every encoder output code symbol to generate a bit of the
12 scrambling sequence. Every encoder output code symbol shall be XOR’d with the
13 corresponding bit of the scrambling sequence to yield a scrambled encoded bit.’ The
14 scrambler initial state that is used to generate the data bits for an extension slot of a
15 packet shall be the same as that used to generate the data bits for the first slot of the
16 corresponding packet.
12-135
Transmission
Format
Packet Size (bits), b2 b1 b0 d4 d3 d2 d1 d0 Data
Preamble Length
(chips))
(128, 16, 1024) 0 0 0 0 0 0 0 1 4.8

(128, 8, 512) 0 0 0 0 0 0 1 0 9.6
(128, 4, 256) 0 0 0 0 0 0 1 1 19.2
(128, 4, 1024) 0 0 0 0 0 0 1 1 19.2
(128, 2, 128) 0 0 0 0 0 1 0 0 38.4
(128, 1, 64) 0 0 0 0 0 1 1 0 76.8
(256, 16, 1024) 0 0 1 0 0 0 0 1 9.6
(256, 8, 512) 0 0 1 0 0 0 1 0 19.2
(256, 4, 256) 0 0 1 0 0 0 1 1 38.4
(256, 4, 1024) 0 0 1 0 0 0 1 1 38.4
(256, 2, 128) 0 0 1 0 0 1 0 0 76.8
(256, 1, 64) 0 0 1 0 0 1 1 0 153.6
(512, 16, 1024) 0 1 0 0 0 0 0 1 19.2
(512, 8, 512) 0 1 0 0 0 0 1 0 38.4
(512, 4, 256) 0 1 0 0 0 0 1 1 76.8
(512, 4, 1024) 0 1 0 0 0 0 1 1 76.8
(512, 4, 128) 0 1 0 0 0 1 0 1 76.8
(512, 2, 128) 0 1 0 0 0 1 0 0 153.6
(512, 2, 64) 0 1 0 0 0 1 1 1 153.6
(512, 1, 64) 0 1 0 0 0 1 1 0 307.2
(1024, 16, 1024) 1 1 1 0 0 0 0 1 38.4
(1024, 8, 512) 1 1 1 0 0 0 1 0 76.8
(1024, 4, 256) 1 1 1 0 0 0 1 1 153.6
(1024, 4, 128) 0 1 1 0 0 1 0 1 153.6
(1024, 4, 64) 0 0 0 1 1 1 1 1 153.6
(1024, 2, 128) 1 1 1 0 0 1 0 0 307.2
12-136
Transmission
Format
Packet Size (bits), b2 b1 b0 d4 d3 d2 d1 d0 Data
Preamble Length
(chips))
(1024, 2, 64) 0 1 1 0 0 1 1 1 307.2

(1024, 1, 64) 1 1 1 0 0 1 1 0 614.4
(2048, 4, 128) 1 1 1 0 0 1 0 1 307.2
(2048, 4, 64) 0 0 1 1 1 1 1 1 307.2
(2048, 2, 64) 1 1 1 0 0 1 1 1 614.4
(2048, 1, 64) 1 1 1 0 1 0 0 1 1228.8
(3,072, 4, 64) 1 1 1 1 0 0 0 0 460.8
(3072, 2, 64) 1 1 1 0 1 0 0 0 921.6
(3072, 1, 64) 1 1 1 0 1 0 1 1 1843.2
(4096, 4, 64) 1 1 1 1 0 0 0 1 614.4
(4096, 2, 64) 1 1 1 0 1 0 1 0 1228.8
(4096, 1, 64) 1 1 1 0 1 1 0 0 2457.6
(5120, 4, 64) 1 1 1 1 0 0 1 0 768.0
(5120, 2, 64) 1 1 1 0 1 1 0 1 1536.0
(5120, 1, 64) 1 1 1 0 1 1 1 0 3072.0
(6144, 4, 64) 1 1 1 1 0 0 1 1 921.6
(6144, 2, 64) 1 1 1 1 0 1 1 0 1,843.2
(6144, 1, 64) 1 1 1 1 1 0 0 1 3,686.4
(7168, 4, 64) 1 1 1 1 0 1 0 0 1,075.2
(7168, 2, 64) 1 1 1 1 0 1 1 1 2,150.4
(7168, 1, 64) 1 1 1 1 1 0 1 0 4,300.8
(8192, 4, 64) 1 1 1 1 0 1 0 1 1,228.8
(8192, 2, 64) 1 1 1 1 1 0 0 0 2,457.6
(8192, 1, 64) 1 1 1 1 1 0 1 1 4,915.2
1
12-137
1 r7 d4 b2 b1 b0 r6 r5 r4 r3 r2 r1 r0 d3 d2 d1 d0
Scrambling
Sequence
2

6 Channel Interleaver. Channel interleaving shall consist of a Symbol Reordering stage
7 followed by a Matrix Interleaving stage which is followed by a Short Sequence Repetition
8 Stage.
9 The packet length, N (including data and tail bits) is expressed as N = R × K × 2m - L where
10 R, K, L and m are non-negative integers. The channel interleaver is described in terms of
11 the parameters R, K, L, m, a short-packet wrap-around parameter W, and an end-around-
12 shift parameter D.

24 shall be last.
12-138
8 sequence, etc.
9 2. The U, V0 and V′0sequences shall be ordered according to UV0 V′0. That is, the U
11 13.4.1.3.2.3.4.212.4.1.3.2.3.4.2 Matrix Interleaving

12 The Matrix Interleaving stage receives either 3 x N or 5 x N input symbols and generates
13 either 3 x N or 5 x N output symbols. If the L parameter is non-zero, the output of the
14 Matrix Interleaving stage consists of all of the outputs of the cuboidal array corresponding
15 to the U-sequence followed by the outputs of the cuboidal array corresponding to the V-
16 sequence truncated to the required length. The Matrix Interleaving operation is carried out
17 in the following steps:
18 1. The N symbols of the U-sequence symbols followed by L zeros are written into a 3-
19 dimensional cuboidal array with R rows, C ≡ 2m columns, and K levels. Symbols are
20 written into the 3-dimensional array with level-index incrementing first, followed by
22 C + c) × K + k), where 0 ≤ i < N+L goes into the rth row, cth column, and kth level
23 where, 0 ≤ r < R, 0 ≤ c < C, and 0 ≤ k < K.
25 shifted by (c × K + k) mod R. In other words, matrix[ r ] [ c ] [ k ] is transformed to
29 4. If K = 5, then the symbols at level given by ⎣K/2⎦ are swapped with symbols at level
30 1 (k=1). Otherwise, the symbols at level given by k are moved to level given by (79 ×
31 k) mod K. In other words, symbols at [r][c][k] is transformed to [r][c][(79 × k) mod K]
32 for all r, c, and k.
33 5. The N+L output Ssymbols from the cuboidal array are read out with row-index
34 incrementing first, followed by column-index, followed by level-index. In other
35 words, the ith output symbol ((k × C + c) × R + r), where 0 ≤ i < N+L comes from the
36 rth row, cth column, and kth level where, 0 ≤ r < R , 0 ≤ c < C, and 0 ≤ k < K.
37 6. The N symbols of the V0 sequence followed by L zeros, followed by the N symbols of
38 the V0’ sequence, followed by L zeros are written into a 3-dimensional cuboidal
39 array with R rows followed by L zeros, C ≡ 2m+1 columns and K levels. Symbols are
40 written into the 3-dimensional array with level-index incrementing first, followed by
12-139
2 C + c) × K + k), where 0 ≤ i < 2 × (N+L) goes into the rth row, cth column, and kth
3 level, where 0 ≤ r < R , 0 ≤ c < C, and 0 ≤ k < K.
6 transformed to matrix[r + ⎣(K × c + k) / D⎦ mod R][c] [k].
9 9. If K = 5, then the symbols at level ⎣K/2⎦ are swapped with symbols at level 1 (k=1).
10 ). Otherwise, the symbols at level given by k are moved to level given by (79 × k)
11 mod K. In other words, symbol at position [r][c][k] is moved to [r][c][(79 × k) mod K]
12 for all r, c, and k.
13 10. The 2 x N –L output Symbols symbols from the cuboidal array are read out with
14 row-index incrementing first, followed by column-index, followed by level-index. In
15 other words, the ith output symbol ((k × C + c) × R + r), where 0 ≤ i < 2 × N-L comes
16 from the rth row, cth column and kth level , where, 0 ≤ r < R , 0 ≤ c < C, and 0 ≤ k <
17 K.
20 13.4.1.3.2.3.4.312.4.1.3.2.3.4.3 Short Sequence Repetition

21 If the total number of symbols (3 × N or 5 × N) output by the Matrix Interleaving stage as
22 described above is less than the wrap-around parameter W, then the output sequence is
23 repeated partially or fully so that the length of the sequence is equal to W binary symbols.
24 Otherwise, the symbol sequence output by the matrix interleaver described above is
25 regarded as the output of the channel interleaver. Table 12.4.1.3.2.3.4.3-1 below shows the
26 interleaver parameters for various packets used on the Forward Traffic Channel.
12-140
Transmission Format N K R m L D W
Size(bits), Nominal
Transmit Duration
(chips))
(128, 16, 1024) 128 1 2 6 0 4 0

(128, 8, 512) 128 1 2 6 0 4 0
(128, 4, 1024) 128 1 2 6 0 4 0
(128, 4, 256) 128 1 2 6 0 4 0
(128, 2, 128) 128 1 2 6 0 4 0
(128, 1, 64) 128 1 2 6 0 4 0
(256, 16, 1024) 256 1 2 7 0 4 0
(256, 8, 512) 256 1 2 7 0 4 0
(256, 4, 1024) 256 1 2 7 0 4 0
(256, 4, 256) 256 1 2 7 0 4 0
(256, 2, 128) 256 1 2 7 0 4 0
(256, 1, 64) 256 1 2 7 0 4 0
(512, 16, 1024) 512 1 2 8 0 4 0
(512, 8, 512) 512 1 2 8 0 4 0
(512, 4, 1024) 512 1 2 8 0 4 0
(512, 4, 256) 512 1 2 8 0 4 0
(512, 4, 128) 512 1 2 8 0 4 6,144
(512, 2, 128) 512 1 2 8 0 4 0
(512, 2, 64) 512 1 2 8 0 4 6,144
(512, 1, 64) 512 1 2 8 0 4 0
(1024, 16, 1024) 1024 1 2 9 0 4 0
(1024, 8, 512) 1024 1 2 9 0 4 0
(1024, 4, 256) 1024 1 2 9 0 4 0
(1024, 4, 128) 1024 1 2 9 0 4 6,144
(1024, 4, 64) 1024 1 2 9 0 4 0
(1024, 2, 128) 1024 1 2 9 0 4 0
(1024, 2, 64) 1024 1 2 9 0 4 6,144
(1024, 1, 64) 1024 1 2 9 0 4 0
(2048, 4, 128) 2048 1 2 10 0 4 0
12-141
Transmission Format N K R m L D W
Size(bits), Nominal
Transmit Duration
(chips))
(2048, 4, 64) 2048 1 2 10 0 4 0

(2048, 2, 64) 2048 1 2 10 0 4 0
(2048, 1, 64) 2048 1 2 10 0 4 0
(3072, 4, 64) 3072 3 2 9 0 4 0
(3072, 2, 64) 3072 1 3 10 0 4 0
(3072, 1, 64) 3072 1 3 10 0 4 0
(4096, 4, 64) 4096 1 2 11 0 4 0
(4096, 2, 64) 4096 1 4 10 0 4 0
(4096, 1, 64) 4096 1 4 10 0 4 0
(5120, 4, 64) 5120 1707 3 0 1 4 0
(5120, 2, 64) 5120 5 4 8 0 10 0
(5120, 1, 64) 5120 5 4 8 0 10 0
(6144, 4, 64) 6144 3 4 9 0 4 0
(6144, 2, 64) 6144 1 6 10 0 4 0
(6144, 1, 64) 6144 1 6 10 0 4 0
(7168, 4, 64) 7168 7 4 8 0 4 0
(7168, 2, 64) 7168 1195 6 0 2 14 0
(7168, 1, 64) 7168 1195 6 0 2 14 0
(8192, 4, 64) 8192 1 4 11 0 4 0
(8192, 2, 64) 8192 683 6 1 4 16 0
(8192, 1, 64) 8192 683 6 1 4 16 0
1
2 13.4.1.3.2.3.512.4.1.3.2.3.5 Modulation
5 QPSK, 8-PSK, 16-QAM, or 64-QAM modulation symbols, depending on the data rate.
6 13.4.1.3.2.3.5.112.4.1.3.2.3.5.1 QPSK Modulation

7 For physical layer packets using QPSK modulation, groups of two successive channel
8 interleaver output symbols shall be grouped to form QPSK modulation symbols. Each
9 group of two adjacent block interleaver output symbols, x(2k) and x(2k + 1), k = 0,…, M – 1
12-142
1 12.4.1.3.2.3.5.1-1. Figure 12.4.1.3.2.3.5.1-1 shows the signal constellation of the QPSK

2 modulator, where s0 = x(2k) and s1 = x(2k + 1).

s1 s0
mI(k) mQ(k)
x(2k + 1) x(2k)
0 0 D D
0 1 –D D
1 0 D –D
1 1 –D –D
Note: D = 1 2.
4
Q Channel
s1s 0
01 00
1 2
−1 2 1 2
I Channel
−1 2
11 10
7 13.4.1.3.2.3.5.212.4.1.3.2.3.5.2 8-PSK Modulation

8 For physical layer packets using 8-PSK modulation, groups of three successive channel
9 interleaver output symbols shall be grouped to form 8-PSK modulation symbols. Each
10 group of three adjacent block interleaver output symbols, x(3k), x(3k + 1), and x(3k + 2), k
11 = 0,…, M – 1 shall be mapped into a complex modulation symbol (mI(k), mQ(k)) as specified
12 in Table 12.4.1.3.2.3.5.2-1. Figure 12.4.1.3.2.3.5.2-1 shows the signal constellation of the
13 8-PSK modulator, where s0 = x(3k), s1 = x(3k + 1), and s2 = x(3k + 2).
12-143

s2 s1 s0
mI(k) mQ(k)
x(3k + 2) x(3k + 1) x(3k)
0 0 0 C S
0 0 1 S C
0 1 1 –S C
0 1 0 –C S
1 1 0 –C –S
1 1 1 –S –C
1 0 1 S –C
1 0 0 C –S
Q Channel
C = cos(π/8)
011 001 S = sin(π/8)
C
s 2s1s 0
010 S 000
–C –S S C
I Channel
–S
110 100
–C
111 101
4 13.4.1.3.2.3.5.312.4.1.3.2.3.5.3 16-QAM Modulation

5 For physical layer packets using 16-QAM modulation, groups of four successive channel
7 group of four adjacent block interleaver output symbols, x(4k), x(4k + 1), x(4k + 2), and
8 x(4k + 3), i = 0,…, M – 1 shall be mapped into a complex modulation symbol (mI(k), mQ(k))
9 as specified in Table 12.4.1.3.2.3.5.3-1. Figure 12.4.1.3.2.3.5.3-1 shows the signal
10 constellation of the 16-QAM modulator, where s0 = x(4k), s1 = x(4k + 1), s2 = x(4k + 2), and
11 s3 = x(4k + 3).
12-144

s3 s2 s1 s0
mQ(k) mI(k)
x(4k + 3) x(4k + 2) x(4k + 1) x(4k)
0 0 0 0 3A 3A
0 0 0 1 3A A
0 0 1 1 3A –A
0 0 1 0 3A –3A
0 1 0 0 A 3A
0 1 0 1 A A
0 1 1 1 A –A
0 1 1 0 A –3A
1 1 0 0 –A 3A
1 1 0 1 –A A
1 1 1 1 –A –A
1 1 1 0 –A –3A
1 0 0 0 –3A 3A
1 0 0 1 –3A A
1 0 1 1 –3A –A
1 0 1 0 –3A –3A
Note: A = 1 10 ≈ 0.3162 .
2
12-145
Q Channel
s 3s 2s1s0
0010 0011 0001 0000
3A
A = 1 10
0110 0111 0101 0100

A
–3A –A A 3A
I Channel
1110 1111 1101 1100

–A
1010 1011 1001 1000

–3A
3 13.4.1.3.2.3.5.412.4.1.3.2.3.5.4 64-QAM Modulation

4 For physical layer packets using 64-QAM modulation, groups of six successive channel
6 group of six adjacent block interleaver output symbols, x(6k), x(6k + 1), x(6k + 2), x(6k+3),
7 x(6k+4), and x(6k + 5), k = 0,…, M – 1 shall be mapped into a complex modulation symbol
8 (mI(k), mQ(k)) as specified in Table 12.4.1.3.2.3.5.3-1. Figure 12.4.1.3.2.3.5.3-1 shows the
9 signal constellation of the 64-QAM modulator, where s0 = x(6k), s1 = x(6k + 1), s2 = x(6k +
10 2), s3 = x(6k + 3), s4 = x(6k + 4), and s5 = x(6k + 5).
12-146
Modulation
Interleaved Symbols
Symbols
s5 s4 s3 s2 s1 s0
mQ(k) mI(k)
x(6k + 5) x(6k + 4) x(6k + 3) x(6k + 2) x(6k + 1) x(6k)
0 0 0 0 0 0 7A 7A
0 0 0 0 0 1 7A 5A
0 0 0 0 1 1 7A 3A
0 0 0 0 1 0 7A A
0 0 0 1 1 0 7A -A
0 0 0 1 1 1 7A -3A
0 0 0 1 0 1 7A –5A
0 0 0 1 0 0 7A –7A
0 0 1 0 0 0 5A 7A
0 0 1 0 0 1 5A 5A
0 0 1 0 1 1 5A 3A
0 0 1 0 1 0 5A A
0 0 1 1 1 0 5A -A
0 0 1 1 1 1 5A -3A
0 0 1 1 0 1 5A –5A
0 0 1 1 0 0 5A –7A
0 1 1 0 0 0 3A 7A
0 1 1 0 0 1 3A 5A
0 1 1 0 1 1 3A 3A
0 1 1 0 1 0 3A A
0 1 1 1 1 0 3A -A
0 1 1 1 1 1 3A -3A
0 1 1 1 0 1 3A –5A
0 1 1 1 0 0 3A –7A
0 1 0 0 0 0 A 7A
0 1 0 0 0 1 A 5A
0 1 0 0 1 1 A 3A
0 1 0 0 1 0 A A
0 1 0 1 1 0 A -A
12-147
Modulation
Interleaved Symbols
Symbols
s5 s4 s3 s2 s1 s0
mQ(k) mI(k)
x(6k + 5) x(6k + 4) x(6k + 3) x(6k + 2) x(6k + 1) x(6k)
0 1 0 1 1 1 A -3A
0 1 0 1 0 1 A –5A
0 1 0 1 0 0 A –7A
1 1 0 0 0 0 -A 7A
1 1 0 0 0 1 -A 5A
1 1 0 0 1 1 -A 3A
1 1 0 0 1 0 -A A
1 1 0 1 1 0 -A -A
1 1 0 1 1 1 -A -3A
1 1 0 1 0 1 -A –5A
1 1 0 1 0 0 -A –7A
1 1 1 0 0 0 –3A 7A
1 1 1 0 0 1 –3A 5A
1 1 1 0 1 1 –3A 3A
1 1 1 0 1 0 –3A A
1 1 1 1 1 0 –3A -A
1 1 1 1 1 1 –3A -3A
1 1 1 1 0 1 –3A –5A
1 1 1 1 0 0 –3A –7A
1 0 1 0 0 0 -5A 7A
1 0 1 0 0 1 -5A 5A
1 0 1 0 1 1 -5A 3A
1 0 1 0 1 0 -5A A
1 0 1 1 1 0 -5A -A
1 0 1 1 1 1 -5A -3A
1 0 1 1 0 1 -5A –5A
1 0 1 1 0 0 -5A –7A
1 0 0 0 0 0 –7A 7A
1 0 0 0 0 1 –7A 5A
1 0 0 0 1 1 –7A 3A
12-148
Modulation
Interleaved Symbols
Symbols
s5 s4 s3 s2 s1 s0
mQ(k) mI(k)
x(6k + 5) x(6k + 4) x(6k + 3) x(6k + 2) x(6k + 1) x(6k)
1 0 0 0 1 0 –7A A
1 0 0 1 1 0 –7A -A
1 0 0 1 1 1 –7A -3A
1 0 0 1 0 1 –7A –5A
1 0 0 1 0 0 –7A –7A
Note: A = 1 / 42 ≈ 0.1543 .
1
Q Channel S 5 S 4 S 3 S 2 S1 S 0
000100 000101 000111 000110 000010 000011 000001 000000
7A
001100 001101 001111 001110 001010 001011 001001 001000

5A
A = 1 / 42
011100 011101 011111 011110 011010 011011 011001 011000

3A
010100 010101 010111 010110 010010 010011 010001 010000

A
–7A –5A –3A –A A 3A 5A 7A

I Channel
110100 110101 110111 110110 110010 110011 110001 110000
–A
111100 111101 111111 111110 111010 111011 111001 111000

–3A
101100 101101 101111 101110 101010 101011 101001 101000

–5A
100100 100101 100111 100110 100010 100011 100001 100000

2
–7A

12-149
6 be used.
8 12.4.1.3.2.3.6-1.
12-150

Format
(Physical Layer
Number of
Packet Number
mission
Preamble Length
(chips))
(128, 16, 1024) 320 24,576 76 256 1/5 76.8

(128, 8, 512) 320 12,288 38 128 1/5 38.4
(128, 4, 1024) 320 5,376 16 256 1/5 16.8
(128, 4, 256) 320 6,144 19 64 1/5 19.2
(128, 2, 128) 320 3,072 9 192 1/5 9.6
(128, 1, 64) 320 1,536 4 256 1/5 4.8
(256, 16, 1024) 640 24,576 38 256 1/5 38.4
(256, 8, 512) 640 12,288 19 128 1/5 19.2
(256, 4, 1024) 640 5,376 8 256 1/5 8.4
(256, 4, 256) 640 6,144 9 384 1/5 9.6
(256, 2, 128) 640 3,072 4 512 1/5 4.8
(256, 1, 64) 640 1,536 2 256 1/5 2.4
(512, 16, 1024) 1,280 24,576 19 256 1/5 19.2
(512, 8, 512) 1,280 12,288 9 768 1/5 9.6
(512, 4, 1024) 1,280 5,376 4 256 1/5 4.2
(512, 4, 256) 1,280 6,144 4 1,024 1/5 4.8
(512, 4, 128) 3,072 6,272 2 128 1/5 2.04
(512, 2, 128) 1,280 3,072 2 512 1/5 2.4
(512, 2, 64) 3,072 3,136 1 64 1/5 1.02
(512, 1, 64) 1,280 1,536 1 256 1/5 1.2
(1024, 16, 1024) 2,560 24,576 9 1,536 1/5 9.6
(1024, 8, 512) 2,560 12,288 4 2,048 1/5 4.8
(1024, 4, 256) 2,560 6,144 2 1,024 1/5 2.4
(1024, 4, 128) 3,072 6,272 2 128 1/5 2.04
12-151

Format
(Physical Layer
Number of
Packet Number
mission
Preamble Length
(chips))
(1024, 4, 64) 2,560 6,336 2 1,216 1/5

2.48
(1024, 2, 128) 2,560 3,072 1 512 1/5 1.2
(1024, 2, 64) 3,072 3,136 1 64 1/5 1.02
(1024, 1, 64) 1,536 1,536 1 0 1/3 1
(2048, 4, 128) 3,072 6,272 2 128 1/3 2.04
(2048, 4, 64) 3,072 6,336 2 192 1/3 2.06
(2048, 2, 64) 3,072 3,136 1 64 1/3 1.02
(2048, 1, 64) 3,072 1,536 0 1,536 2/3 1
(3072, 4, 64) 4,608 6,336 1 1,728 1/3 1.38
(3072, 2, 64) 3,072 3,136 1 64 1/3 1.02
(3072, 1, 64) 3,072 1,536 0 1,536 2/3 1
(4096, 4, 64) 6,144 6,336 1 192 1/3 1.03
(4096, 2, 64) 3,072 3,136 1 64 1/3 1.02
(4096, 1, 64) 3,072 1,536 0 1,536 2/3 1
(5120, 4, 64) 5,120 6,336 1 1216 1/3 1.24
(5120, 2, 64) 3,840 3,136 0 3,136 20/49 1
(5120, 1, 64) 3,840 1,536 0 1,536 5/6 1
(6144, 4, 64) 4,608 6,336 1 1,728 1/3 1.38
(6144, 2, 64) 3,072 3,136 1 64 1/3 1.02
(6144, 1, 64) 3,072 1,536 0 1,536 2/3 1
(7168, 4, 64) 5,376 6,336 1 960 1/3 1.18
(7168, 2, 64) 3,584 3,136 0 3,136 8/21 1
(7168, 1, 64) 3,584 1,536 0 1,536 7/9 1
(8192, 4, 64) 6,144 6,336 1 192 1/3 1.03
(8192, 2, 64) 4,096 3,136 0 3,136 64/147 1
12-152

Format
(Physical Layer
Number of
Packet Number
mission
Preamble Length
(chips))
(8192, 1, 64) 4,096 1,536 0 1,536 8/9 1

1

5 mI(3),… denotes the sequence of sequence-repeated modulation output values in the in-
10 mQ(3),…denotes the sequence of sequence-repeated modulation output values in the

21 symbols.

1 1
16 4
12-153

3 by-chip basis.
4 13.4.1.3.2.412.4.1.3.2.4 Control Channel

6 messages. Control Channel packets belonging to the synchronous capsule shall be
7 transmitted using a Transmission Format of (1024, 8, 512) corresponding to a data rate of
8 76.8 kbps or using a Transmission Format of (1024, 16, 1024) corresponding to a data rate
9 of 38.4 kbps. Control Channel packets belonging to an asynchronous or a sub-
10 synchronous capsule shall be transmitted using Transmission Formats of (1024, 8, 512),
11 (1024, 16, 1024), (128, 4, 1024), (256, 4, 1024), or (512, 4, 1024). Control Channel packets
12 belonging to a quick synchronous capsule shall be transmitted using Transmission
13 Formats of (128, 4, 256) or (256, 4, 256). The modulation characteristics shall be the same
14 as those of the Forward Traffic Channel at the corresponding Transmission Format. The
15 Control Channel transmissions shall be distinguished from Forward Traffic Channel
16 transmissions by having a preamble that is covered by a bi-orthogonal cover sequence with
17 ForwardTrafficMACIndex 2, 3, 71, or that specified by the CCShortPacketsMACIndex
18 attribute as specified in 12.4.1.3.2.3.1. A ForwardTrafficMACIndex value of 2 shall be used
19 for the Transmission Format of (1024, 8, 512) or 76.8 kbps data rate, a
20 ForwardTrafficMACIndex value of 3 shall be used for the Transmission Format of (1024, 16,
21 1024) or 38.4 kbps data rate, and a ForwardTrafficMACIndex value of 71 or a
22 ForwardTrafficMACIndex value specified by CCShortPacketsMACIndex attribute value shall
23 be used for the Transmission Formats of (128, 4, 1024), (256, 4, 1024), or (512, 4, 1024). A
24 ForwardTrafficMACIndex value of 71 shall be used for the Transmission Formats of (128, 4,
25 256) and (256, 4, 256).

27 The Forward Traffic Channel or Control Channel data modulation chips for each forward
28 CDMA channel shall be time-division multiplexed with the preamble, Pilot Channel, and
29 MAC Channel chips according to the timing diagrams in Figure 12.4.1.3.3-1, Figure
30 12.4.1.3.3-2, Figure 12.4.1.3.3-3, Figure 12.4.1.3.3-4 and Figure 12.4.1.3.3-5. The
31 multiplexing parameters shall be as specified in Table 12.4.1.3.3-1 through Table
32 12.4.1.3.3-6.
12-154

2 Figure 12.4.1.3.3-1
Transmission Format
(Physical Layer Packet Size (bits), Nominal Transmit
(128, 4, 256)
(128, 2, 128)
(256, 4, 256)
(256, 2, 128)
(512, 4, 256)
(512, 4, 128)
(512, 2, 128)
(512, 2, 64)
(1024, 4, 256)
(1024, 4, 128)
(1024, 4, 64)
(1024, 2, 128)
(1024, 2, 64)
(2048, 4, 128)
(2048, 4, 64)
(2048, 2, 64)
(3072, 4, 64)
(3072, 2, 64)
(4096, 4, 64)
(4096, 2, 64)
(5120, 4, 64)
(5120, 2, 64)
(6144, 4, 64)
(6144, 2, 64)
(7168, 4, 64)
(7168, 2, 64)
(8192, 4, 64)
(8192, 2, 64)
3
12-155
320, 640, 1,280, 2,560,

3,072, 3,648, 3,840, 4,224,
4,608, 5,376, 6,144
Modulation Symbols

N 400 – N & MAC 800 & MAC & MAC 800 & MAC 400
2 or 4 Slots
4,096 or 8,192 Chips
2

9 Figure 12.4.1.3.3-2
Transmission Format
(128, 16, 1024)

(128, 8, 512)
(256, 16, 1024)
(256, 8, 512)
(512, 16, 1024)
(512, 8, 512)
(1024, 16, 1024)
(1024, 8, 512)
10
12-156
320, 640, 1,280 or

2,560
Modulation Symbols

(Repeated Sequence)
Chips 224 or or 224 Chips 224 224 Chips 224 Chips
8 or 16 Slots
16,384 or 32,768 Chips
1
2 Figure 12.4.1.3.3-2. Preamble, Pilot, MAC, and Data Multiplexing with Transmission
3 Formats in Table 12.4.1.3.3-2

8 Figure 12.4.1.3.3-3
Transmission Format
(128, 1, 64)
(256, 1, 64)
(512, 1, 64)
(2048, 1, 64)
(3072, 1, 64)
(4096, 1, 64)
(5120, 1, 64)
(6144, 1, 64)
(7168, 1, 64)
(8192, 1, 64)
9
12-157
320, 640, 1,280, 3,072, 3,648, 3,840, or 4,224 Data Modulation Symbols

64 336 & MAC 800 & MAC 400
Chips Chips
1 Slot
2,048 Chips
2
3 Figure 12.4.1.3.3-3. Preamble, Pilot, MAC, and Data Multiplexing for the 1-Slot Cases with
4 Transmission Formats in Table 12.4.1.3.3-3
12-158

2 Figure 12.4.1.3.3-4
Transmission Format
(1024, 1, 64)

64 336 & MAC 800 & MAC 400
Chips Chips
1 Slot
2,048 Chips
3
5 with Transmission Formats in Table 12.4.1.3.3-4.
6 Forward Traffic Channel physical layer packets with Packet Transmission Formats as
7 shown in Table 12.4.1.3.3-5 Table 14.3.1.3.3-5 shall be time division multiplexed with the
8 preamble, Pilot Channel and MAC Channel chips according to the timing diagrams in
9 Figure 12.4.1.3.3-5Figure 14.3.1.3.3-5.

11 Figure 12.4.1.3.3-5
Transmission Format
(128, 4, 1,024)
(256, 4, 1,024)
(512, 4, 1,024)
12
12-159
320, 640, or 1280

Modulation Symbols

(Repeated Sequence)
Chips 224 224 Chips 224 224 Chips 224 Chips
Chips Chips Chips Chips Chips
4 Slots (8,192 Chips)

1
4 Table 12.4.1.3.3-6 shows the number of Pilot chips, MAC chips, and Data chips
5 corresponding to each of the possible transmission formats
12-160
Transmission Format
(128, 16, 1,024) 3,072 4,096 24,576
(128, 8, 512) 1,536 2,048 12,288
(128, 4, 1024) 768 1,024 5,376
(128, 4, 256) 768 1,024 6,144
(128, 2, 128) 384 512 3,072
(128, 1, 64) 192 256 1,536
(256, 16, 1024) 3,072 4,096 24,576
(256, 8, 512) 1,536 2,048 12,288
(256, 4, 1024) 768 1,024 5,376
(256, 4, 256) 768 1,024 6,144
(256, 2, 128) 384 512 3,072
(256, 1, 64) 192 256 1,536
(512, 16, 1024) 3,072 4,096 24,576
(512, 8, 512) 1,536 2,048 12,288
(512, 4, 1024) 768 1,024 5,376
(512, 4, 256) 768 1,024 6,144
(512, 4, 128) 768 1,024 6,272
(512, 2, 128) 384 512 3,072
(512, 2, 64) 384 512 3,136
(512, 1, 64) 192 256 1,536
(1024, 16, 1024) 3,072 4,096 24,576
(1024, 8, 512) 1,536 2,048 12,288
(1024, 4, 256) 768 1,024 6,144
(1024, 4, 128) 768 1,024 6,272
(1024, 4, 64) 768 1,024 6,336
(1024, 2, 128) 384 512 3,072
(1024, 2, 64) 384 512 3,136
(1024, 1, 64) 192 256 1,536
(2048, 4, 128) 768 1,024 6,272
(2048, 4, 64) 768 1,024 6,336
12-161
Transmission Format
(2048, 2, 64) 384 512 3,136
(2048, 1, 64) 192 256 1,536
(3072, 4, 64) 768 1,024 6,336
(3072, 2, 64) 384 512 3,136
(3072, 1, 64) 192 256 1,536
(4096, 4, 64) 768 1,024 6,336
(4096, 2, 64) 384 512 3,136
(4096, 1, 64) 192 256 1,536
(5120, 4, 64) 768 1,024 6,336
(5120, 2, 64) 384 512 3,136
(5120, 1, 64) 192 256 1,536
(6144, 4, 64) 768 1,024 6,336
(6144, 2, 64) 384 512 3,136
(6144, 1, 64) 192 256 1,536
(7168, 4, 64) 768 1,024 6,336
(7168, 2, 64) 384 512 3,136
(7168, 1, 64) 192 256 1,536
(8192, 4, 64) 768 1,024 6,336
(8192, 2, 64) 384 512 3,136
(8192, 1, 64) 192 256 1,536
1

3 Following orthogonal spreading, the combined modulation sequence for each forward
4 CDMA channel shall be quadrature spread as shown in Figure 12.4.1.3.1-1. The spreading
5 sequence shall be a quadrature sequence of length 215 (i.e., 32768 PN chips in length).
6 This sequence is called the pilot PN sequence and shall be based on the following
7 characteristic polynomials:
8 PI(x) = x15 + x10 + x8 + x7 + x6 + x2 + 1

10 and
11 PQ(x) = x15 + x12 + x11 + x10 + x9 + x5 + x4 + x3 + 1
12-162

4 recursions:
5 I(n) = I(n – 15) ⊕ I(n – 13) ⊕ I(n – 9) ⊕ I(n – 8) ⊕ I(n – 7) ⊕ I(n – 5)
7 and
8 Q(n) = Q(n – 15) ⊕ Q(n – 12) ⊕ Q(n – 11) ⊕ Q(n – 10) ⊕ Q(n – 6) ⊕ Q(n – 5) ⊕
9 Q(n – 4) ⊕ Q(n – 3)
17 2 seconds.
18 Pilot Channels for each forward CDMA channel shall be identified by an offset index in the
19 range from 0 through 511 inclusive. This offset index shall specify the offset value (in units
20 of 64 chips) by which the pilot PN sequence lags the zero-offset pilot PN sequence. The
21 zero-offset pilot PN sequence shall be such that the start of the sequence shall be output at
22 the beginning of every even second in time, referenced to access network transmission
23 time. The start of the zero-offset pilot PN sequence for either the I or Q sequences shall be
24 defined as the state of the sequence for which the next 15 outputs inclusive are ‘0’.
25 Equivalently, the zero-offset sequence is defined such that the last chip prior to the even-
26 second mark as referenced to the transmit time reference is a ‘1’ prior to the 15 consecutive
27 ‘0’s.
28 13.4.1.3.512.4.1.3.5 Filtering

33 12.3.1.3.6-1 for each forward CDMA channel. Specifically, the normalized frequency
34 response of the filter for each forward CDMA channel shall be contained within ±δ1 in the
35 passband 0 ≤ f ≤ fp and shall be less than or equal to –δ2 in the stopband f ≥ fs. The
36 numerical values for the parameters are δ1 = 1.5 dB, δ2 = 40 dB, fp = 590 kHz, and fs = 740
37 kHz.
12-163
20 log10 S(f )
δ1
δ1
δ2
f
0 fp fs
1
3 The impulse response of the baseband filter, s(t), for each forward CDMA channel should
4 satisfy the following equation:
∞
k =0
[αs(kTs – τ) – h(k)]2 ≤ 0.03,
8 coefficients h(k), for k < 48, are given in Figure 12.4.1.3.5.1-1; h(k) = 0 for k ≥ 48. Note that
12-164
k h(k)
0, 47 –0.025288315
1, 46 –0.034167931
2, 45 –0.035752323
3, 44 –0.016733702
4, 43 0.021602514
5, 42 0.064938487
6, 41 0.091002137
7, 40 0.081894974
8, 39 0.037071157
9, 38 –0.021998074
10, 37 –0.060716277
11, 36 –0.051178658
12, 35 0.007874526
13, 34 0.084368728
14, 33 0.126869306
15, 32 0.094528345
16, 31 –0.012839661
17, 30 –0.143477028
18, 29 –0.211829088
19, 28 –0.140513128
20, 27 0.094601918
21, 26 0.441387140
22, 25 0.785875640
23, 24 1.0
2

ω2 + jαωω0 − ω0 2
H(ω) = K
ω2 − jαωω0 − ω0 2 ,
6
12-165
4 waveforms for each forward CDMA channel.
11 inputs (see Table 12.4.1.3.5.1-1) to the RF output of the transmitter.

15 components, including pilot PN sequences, slots, and Walsh functions for each forward
16 CDMA channel, shall be derived. The time-base reference shall be time-aligned to CDMA
17 System Time, as described in 1.14. Reliable external means should be provided at each
18 sector to synchronize each sector’s time base reference to CDMA System Time. Each sector
19 should use a frequency reference of sufficient accuracy to maintain time alignment to
20 CDMA System Time. In the event that the external source of CDMA System Time is lost,173
21 the sector shall maintain transmit timing within ±10 μs of CDMA System Time for a period
22 of not less than 8 hours.

25 shall radiate the pilot PN sequence within ±10 µs of CDMA System Time for each forward
26 CDMA channel.
12-166
1 1No text
12-167
Common Algorithms and Data Structures 3GPP2 C.S0024-B v2.0
1 1413 COMMON ALGORITHMS AND DATA STRUCTURES
2 14.113.1 Channel Record

3 The Channel record defines an access network channel frequency and the type of system
4 on that frequency. This record contains the following fields:
5
Field Length (bits)
SystemType 8
BandClass 5
ChannelNumber 11
6 SystemType The access network shall set this field to one of the following values:
7 Table 13.1-1. SystemType Encoding
Field value Meaning

System compliant to this
specification.
ChannelNumber field
0x00 specifies forward CDMA
channel and Reverse CDMA
channel that are FDD-
paired.
0x01 System compliant to [2]174
System compliant to this
specification.
0x02 ChannelNumber field
specifies only the forward
CDMA channel.
0x03-0xff Reserved
8 BandClass If the SystemType field is set to 0x00 or 0x01, the access network
9 shall set this field to the band class number corresponding to the
10 frequency assignment of the channel specified by this record for both
11 the forward CDMA channel and the reverse CDMA channel. If the
12 SystemType is set to 0x02, then access network shall set this field to
13 the band class number corresponding to the frequency assignment of
14 the channel specified by this record for the forward CDMA channel
15 only.
174 SystemType of 0x01 applies to [2] and all of its predecessors.
13-1
3GPP2 C.S0024-B v2.0 Common Algorithms and Data Structures
1 ChannelNumber If the SystemType is set to 0x00 or 0x01, the access network shall set
2 this field to the channel number corresponding to the frequency
3 assignment of the channel specified by this record for both the
4 forward CDMA channel and the reverse CDMA channel. If the
5 SystemType is set to 0x02, this access network shall set this field to
6 the channel number corresponding to the frequency assignment of
7 the channel specified by this record for the forward CDMA channel
8 only.
13-2
1 14.213.2 Access Terminal Identifier Record

2 The Access Terminal Identifier record provides a unicast, multicast, or broadcast access
3 terminal address. This record contains the following fields:
4
Field Length (bits)
ATIType 2
ATI 0 or 32
5 ATIType Access Terminal Identifier Type. This field shall be set to the type of
6 the ATI, as shown in Table 13.2-1:
7 Table 13.2-1. ATIType Field Encoding
ATIType ATIType ATI

Description Length
(bits)
Broadcast ATI
'00' 0
(BATI)
‘01’ Multicast ATI (MATI) 32
‘10’ Unicast ATI 32
'11' Random ATI (RATI) 32
8 ATI Access Terminal Identifier. The field is included only if ATIType is not
9 equal to ‘00’. This field shall be set as shown in Table 13.2-1.
10 14.313.3 Attribute Record

11 The attribute record defines a set of suggested values for a given attribute. The attribute
12 record format is defined, such that if the recipient does not recognize the attribute, it can
13 discard it and parse attribute records that follow this record.
14 An attribute can be one of the following three types:
15 • Simple attribute, if it contains a single value,
16 • Attribute list, if it contains multiple single values which are to be interpreted as
17 different suggested values for the same attribute identifier (e.g., a list of possible
18 protocol Subtypes for the same protocol Type), or
19 • Complex attribute, if it contains multiple values that together form a complex value for
20 a particular attribute identifier (e.g., a set of parameters for the Route Update Protocol).
21 Simple attributes are a special case of an attribute list containing a single value.
22 The type of the attribute is determined by the attribute identifier.
23 The sender of a ConfigurationResponse message (see 13.7) selects an attribute-value from
24 a ConfigurationRequest message by sending the attribute value if it is a simple attribute or
13-3
1 a selected value out of an attribute list. Selection of complex-attributes is done by sending

2 the value identifier which identifies the complex value.
3 The format of a simple attribute and attribute list is given by
4
Field Length (bits)
Length 8
AttributeID Protocol Specific
AttributeValue Attribute dependent
Reserved variable
5 Length Length in octets of the attribute record, excluding the Length field.
6 AttributeID Attribute identifiers are unique in the context of the protocol being
7 configured.
8 AttributeValue A suggested value for the attribute. Attribute value lengths are, in
9 general, an integer number of octets. Attribute values have an
10 explicit or implicit length indication (e.g., fixed length or null
11 terminated strings) so that the recipient can successfully parse the
12 record when more than one value is provided.
13 Reserved The length of this field is the smallest value that will make the
14 attribute record octet aligned. The sender shall set this field to zero.
15 The receiver shall ignore this field.
16 The format of a complex attribute is given by
17
Field Length (bits)
Length 8
AttributeID Protocol Specific
One or more instances of the following fields
ValueID Protocol Specific
An appropriate number of instances of the following
record for each instance of the ValueID field
AttributeValue Attribute dependent
Reserved variable
18 Length Length in octets of the attribute record, excluding the Length field.
13-4
1 AttributeID Attribute identifiers are unique in the context of the protocol being
2 configured.
3 ValueID It identifies the set of attribute values following this field. The sender
4 shall increment this field for each new set of values for this complex
5 attribute.
6 AttributeValue A suggested value for the attribute. Attribute value lengths are in
7 general an integer number of octets. Attribute values have an explicit
8 or implicit length indication (e.g., fixed length or null terminated
9 strings) so that the recipient can successfully parse the record when
10 more than one value is provided.
11 Reserved The length of this field is the smallest value that will make the
12 attribute record octet aligned. The sender shall set this field to zero.
13 The receiver shall ignore this field.
14 14.413.4 Hash Function

15 The hash function takes three arguments, Key (typically the access terminal’s ATI), N (the
16 number of resources), and Decorrelate (an argument used to de-correlate values obtained
17 for different applications for the same access terminal).
18 Define:
19 • Word L to be bits 0-15 of Key
20 • Word H to be bits 16-31 of Key
21 where bit 0 is the least significant bit of Key.
22 The hash value is computed as follows175:
23 R = ⎣N × ((40503 × (L ⊕ H ⊕ Decorrelate)) mod 216) / 216⎦.
24 14.513.5 Pseudorandom Number Generator
25 14.5.113.5.1 General Procedures

26 When an access terminal is required to use the pseudo random number generator
27 described in this section, then the access terminal shall implement the linear congruential
28 generator defined by
29 zn = a × zn-1 mod m
30 where a = 75 = 16807 and m = 231 - 1 = 2147483647. zn is the output of the generator.176
175 This formula is adapted from Knuth, D. N., Sorting and Searching, vol. 3 of The Art of Computer
Programming, 3 vols., (Reading, MA: Addison-Wesley, 1973), pp. 508-513. The symbol ⊕ represents
bitwise exclusive-or function (or modulo 2 addition) and the symbol ⎣ ⎦ represents the “largest integer
smaller than” function.
13-5
1 The access terminal shall initialize the random number generator as defined in 13.5.2.
2 The access terminal shall compute a new zn for each subsequent use.
3 The access terminal shall use the value un = zn / m for those applications that require a
4 binary fraction un, 0 < un < 1.
5 The access terminal shall use the value kn = ⎣N × zn / m⎦ for those applications that require
6 a small integer kn, 0 ≤ kn ≤ N-1.
7 14.5.213.5.2 Initialization
8 The access terminal shall initialize the random number generator by setting z0 to
9 z0 = (HardwareID ⊕ χ) mod m
10 where HardwareID is the least 32 bits of the hardware identifier associated with the access
11 terminal, and χ is a time-varying physical measure available to the access terminal. If the
12 initial value so produced is found to be zero, the access terminal shall repeat the procedure
13 with a different value of χ.
14 14.613.6 Sequence Number Validation

15 When the order in which protocol messages are delivered is important, air interface
16 protocols use a sequence number to verify this order.
17 The sequence number has s bits. The sequence space is 2S. All operations and comparisons
18 performed on sequence numbers shall be carried out in unsigned modulo 2S arithmetic.
19 For any message sequence number N, the sequence numbers in the range [N+1, N+2S-1 -1]
20 shall be considered greater than N, and the sequence numbers in the range [N-2S-1, N-1]
21 shall be considered smaller than N.
22 The receiver of the message maintains a receive pointer V(R) whose initialization is defined
23 as part of the protocol. When a message arrives, the receiver compares the sequence
24 number of the message with V(R). If the sequence number is greater than V(R), the message
25 is considered a valid message and V(R) is set to this sequence number; otherwise, the
26 message is considered an invalid message.
27 14.713.7 Generic Configuration Protocol
28 14.7.113.7.1 Introduction
29 The Generic Configuration Protocol provides a means to negotiate protocol parameters. The
30 procedure consists of the initiator sending an attribute and one or more allowed values.
31 The responder then selects one of the offered values. Each attribute must have a well
176 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.
13-6
1 known fall-back value; if the responder does not select any of the offered values, the fall-
2 back value is selected.
3 14.7.213.7.2 Procedures
4 14.7.2.113.7.2.1 Configuration Negotiation

5 The protocol uses a ConfigurationRequest message and a ConfigurationResponse message
6 to negotiate a mutually acceptable configuration. The initiator uses the
7 ConfigurationRequest message to provide the responder with a list of acceptable attribute
8 values for each attribute. The responder uses the ConfigurationResponse message to
9 provide the initiator with the accepted attribute value for each attribute, choosing the
10 accepted attribute value from the initiator’s acceptable attribute value list.
11 The initiator shall order the acceptable attribute values for each attribute in descending
12 order of preference. The initiator shall send these ordered attribute-value lists to the
13 responder using one or more ConfigurationRequest messages. If the ordered attribute value
14 lists fit within one ConfigurationRequest message, then the initiator should use one
15 ConfigurationRequest message. If the ordered attribute value lists do not fit within one
16 ConfigurationRequest message, then the initiator may use more than one
17 ConfigurationRequest message. Each ConfigurationRequest message shall contain one or
18 more complete ordered attribute value lists; an ordered attribute value list for an attribute
19 shall not be split within a ConfigurationRequest message and shall not be split across
20 multiple ConfigurationRequest messages.
21 After sending a ConfigurationRequest message, the sender shall set the value of all
22 parameters that were listed in the message to NULL.
23 After receiving a ConfigurationRequest message, the responder shall respond within
24 TTurnaround, where TTurnaround = 2 seconds, unless specified otherwise. For each attribute
25 included in the ConfigurationRequest message, the responder shall choose an acceptable
26 attribute value from the associated acceptable attribute value list. If the responder does not
27 recognize an attribute or does not find an acceptable attribute value in the associated
28 attribute list, then the responder shall skip the attribute. The responder shall send the
29 accepted attribute value for each attribute within one ConfigurationResponse message. The
30 value included for each attribute shall be one of the values listed in the
31 ConfigurationRequest message. After receiving a ConfigurationResponse message, the
32 initiator shall pair the received message with the associated ConfigurationRequest
33 message. If the ConfigurationResponse message does not contain an attribute found in the
34 associated ConfigurationRequest message, then the initiator shall assume that the missing
35 attribute is using the fall-back value.
36 If the initiator requires no further negotiation of protocols or configuration of negotiated
37 protocols and if the value of the any of the parameters for which the initiator has sent a
38 ConfigurationRequest message is NULL, then the sender shall declare a failure.
39 The initiator and the responder shall use the attribute values in the ConfigurationResponse
40 messages as the configured attribute values, provided that the attribute values were also
41 present in the associated ConfigurationRequest message.
13-7
1 14.7.313.7.3 Message Formats

2 The receiver shall discard all unrecognized messages. The receiver shall discard all
3 unrecognized fields following the fields defined herein. The receiver may log the message for
4 diagnostic reasons.
5 The specification of the Physical Layer channels on which the following messages are to be
6 carried; and, whether the messages are to be sent reliably or as best-effort, is provided in
7 the context of the protocols in which these messages are used.
8 14.7.3.113.7.3.1 ConfigurationRequest
9 The sender sends the ConfigurationRequest message to offer a set of attribute-values for a
10 given attribute.
11
Field Length (bits)

TransactionID 8
12 MessageID The value of this field is specified in the context of the protocol using
13 this message. The value 0x50 is recommended.
17 14.7.3.213.7.3.2 ConfigurationResponse
18 The sender sends a ConfigurationResponse message to select an attribute-value from a list
19 of offered values.
20
Field Length (bits)

TransactionID 8
13-8

6 14.813.8 Session State Information Record

7 The Session State Information is to be used in [8][9] for transferring the session parameters
8 corresponding to the InUse protocol instances from a source access network to a target
9 access network. Session parameters are the attributes and the internal parameters that
10 define the state of each protocol. The format of this record is shown in Table 13.8-1. If an
11 attribute is not contained in the Session State Information record, the target access
12 network shall assume that the missing attributes have the default values (specified for each
13 attribute in each protocol). The sender shall include all the Parameter Records associated
14 with the ProtocolType and ProtocolSubtype in the same Session State Information Record.
15 Table 13.8-1. The Format of the Session State Information Record
Field Length (bits)
FormatID 8
Reserved 1
ProtocolType 7 or 15
ProtocolSubtype 16
One or more instances of the following Parameter
Record:
ParameterType 8
ParameterType-specific Variable
record
16 FormatID This field identifies the format of the rest of the fields in this record
17 and shall be set to zero.
19 ProtocolType This field has the following format:

20

Type1 7
Type2 0 or 8
22 Type value for the protocol (as defined in [10]) associated with the
23 encapsulated .
13-9
2 encapsulated parameter is 7 bits, then this sub-field shall be
3 omitted. Otherwise, this field shall be set to the 8 least significant
4 bits of the Type value for the protocol associated with the
5 encapsulated parameter.177
6 ProtocolSubtype This field shall be set to the protocol subtype value (see Table 14.1-1)
7 for the protocol associated with the encapsulated session
8 parameters.
9 ParameterType This field shall be set according to Table 13.8-2.
10 Table 13.8-2. Encoding of the DataType ParameterType Field
Field Value Meaning
0x00 The ParameterType-specific

record consists of a Complex or a
Simple Attribute as defined in
13.3. The ValueID field of the
complex attribute shall be set to
zero.
All other values ParameterType-specific record
are protocol dependent
11 ParameterType-specific record
12 If the ParameterType field is set to 0x00, then this record shall be set
13 to the simple or complex attribute (see 13.3) associated with the
14 protocol identified by the (ProtocolType, ProtocolSubtype) pair.
15 Otherwise, the structure of this record shall be as specified by the
16 protocol which is identified by the (ProtocolType, ProtocolSubtype)
17 pair.
13-10
1 14.913.9 SectorID Provisioning

2 The SectorID is an IPv6 address from one of the following four address pools: Global
3 Unicast, Site-Local Unicast, Link-Local Unicast and Reserved
4 This section describes the rules for assigning SectorID values to sectors in order to ensure
5 that the value of the SectorID is unique across operator networks, when the SectorID is a
6 Global Unicast address, Site-Local Unicast address, a Link-Local Unicast address or a
7 Reserved address. If the SectorID is Global Unicast address, then the value of the SectorID
8 is globally unique.
9 14.9.113.9.1 Overview of Relevant Formats
10 14.9.1.113.9.1.1 Global Unicast IPv6 Address Format

11 Global Unicast addresses have the following format:
12
13 | n bits | m bits | 128-n-m bits |
14 +-----------------------+-----------+--------------+
15 | global routing prefix | subnet ID | interface ID |
16 +-----------------------+-----------+--------------+
17 Figure 13.9.1.1-1. Global Unicast IPv6 Address Format
18 For all Global Unicast addresses, except those that start with binary 000, the Interface ID
19 is required to be 64 bits long and to be constructed in Modified EUI-64 format.
20 14.9.1.213.9.1.2 Site-Local Unicast IPv6 Address Format

21 Addresses that start with binary 1111111011 are Site-Local Unicast addresses. However,
22 only Site-Local Unicast addresses of the following format have been defined.
23
24 | 10 bits | 38 bits | 16 bits | 64 bits |
25 +------------+----------+-----------+-------------+
26 | 1111111011 | 00 ... 0 | subnet ID |interface ID |
27 +------------+----------+-----------+-------------+
28 Figure 13.9.1.2-1. Site-Local Unicast IPv6 Address Format
29 The Interface ID is required to be 64 bits long and to be constructed in Modified EUI-64

30 format.
31 14.9.1.313.9.1.3 Link-Local Unicast IPv6 Address Format

32 Addresses that start with binary 1111111010 are Link-Local Unicast addresses. However,
33 only Link-Local addresses of the following format have been defined.
34
13-11
1 | 10 bits | 54 bits | 64 bits |

2 +------------+----------+--------------|
3 | 1111111010 | 00 ... 0 | interface ID |
4 +------------+----------+--------------+
5 Figure 13.9.1.3-1. Link-Local Unicast IPv6 Address Format
6 The Interface ID is required to be 64 bits long and to be constructed in Modified EUI-64

7 format.
8 14.9.1.413.9.1.4 Reserved IPv6 Address Format

9 Reserved addresses have the following format
10
11 | 8 bits | 120 bits |
12 +----------+----------+
13 | 00 ... 0 | SS ... S |
14 +----------+----------+
15 Figure 13.9.1.4-1. Format of the Reserved IPv6 Addresses
16 However, the Unspecified address, the Loopback address, and the Embedded IPv4
17 addresses have been chosen from the Reserved Address pool. Therefore, the following
18 values shall be excluded from the Reserved IPv6 address category for SectorID values.
19
20 | 127 bits | 1 bit |
21 +----------+-------+
22 | 00 ... 0 | 0 |
23 +----------+-------+
24 | 127 bits | 1 bit |

25 +----------+-------+
26 | 00 ... 0 | 1 |
27 +----------+-------+
28 | 80 bits | 16 bits | 32 bits |

29 +----------+----------+--------------+
30 | 00 ... 0 | 00 ... 0 | IPv4 Address |
31 +----------+----------+--------------+
32 | 80 bits | 16 bits | 32 bits |

33 +----------+----------+--------------+
34 | 00 ... 0 | 11 ... 1 | IPv4 Address |
35 +----------+----------+--------------+
36 Figure 13.9.1.4-2. IPv6 Values That Are to be Avoided
37 14.9.1.513.9.1.5 Modified EUI-64 Format

38 The Modified EUI-64 Format may take on one of two formats: the universally unique format
39 and the locally unique (non-universally unique) format.
40 If the Modified EUI-64 value is universally unique, then it has the following format:
13-12
1
2 | 6 bits | 1 bit | 1 bit | 16 bits | 40 bits |
3 +--------+-------+-------+----------+----------+
4 | CCCCCC | 1 | G | CC ... C | MM ... M |
5 +--------+-------+-------+----------+----------+
6 Figure 13.9.1.5-1. Universally Unique Modified EUI-64
7 The “C” bits are a company identifier assigned to the manufacturer. The “M” bits are the
8 bits chosen by the manufacturer to ensure that the values assigned by the manufacturer
9 are unique. The “G” bit is the group/individual bit.
10 If the Modified EUI-64 value is locally unique, then it has the format:
11
12 | 6 bits | 1 bit | 57 bits |
13 +--------+-------+----------+
14 | LLLLLL | 0 | LL ... L |
15 +--------+-------+----------+
16 Figure 13.9.1.5-2. Locally Unique Modified EUI-64
17 where the L bits are local node identifier that is chosen such that it is unique on the link.
18 14.9.213.9.2 SectorID Construction

19 The access network shall construct the SectorID to be either a Globally Unique SectorID or
20 a Locally Unique SectorID as described below.
21 If a Globally Unique SectorID is used, the SectorID is universally unique by construction.
22 If a Locally Unique SectorID is used, it is the responsibility of the network to ensure the
23 uniqueness of the SectorID throughout the networks that the access terminal can visit.
24 14.9.2.113.9.2.1 Construction of Globally Unique SectorID

25 There are multiple methods by which a network can be uniquely identified. Networks
26 connected to IPv6 networks are uniquely identified using an IPv6 subnet prefix. Networks
27 connected to the ANSI-41 core are uniquely identified using a System Identifier (SID).
28 Networks connected to the GSM/UMTS core are uniquely identified using a Mobile Country
29 Code (MCC) and a Mobile Network Code (MNC). Networks connected to IPv4 networks are
30 uniquely identified using an IPv4 subnet prefix.
31 It is likely that different operators will have different preferences when it comes to which
32 type of unique identifier to use. Therefore, the following proposal allows the operator to use
33 an IPv6 unique identifier, an ANSI-41 unique identifier, a GSM/UMTS unique identifier, or
34 an IPv4 unique identifier, while ensuring that the SectorID is unique across operator
35 networks.
36 14.9.2.1.113.9.2.1.1 SectorID Based On an IPv6 Unique Identifier

37 When the SectorID is based on an IPv6 unique identifier, the SectorID shall be any Global
38 Unicast IPv6 Address that has been assigned to the operator and that does not start with
13-13
1 binary 00000000. The Global Unicast IPv6 addresses that start with binary 00000000 are
2 excluded because the conflict with the Reserved addresses.
3 An Operator that has not been assigned any IPv6 addresses but has been assigned at least
4 one globally unique IPv4 address may construct a Global Unicast IPv6 address using the
5 6to4 method described in [13].
6 14.9.2.1.213.9.2.1.2 SectorID Not Based On an IPv6 Unique Identifier

7 When the SectorID is not based on an IPv6 unique identifier, the SectorID shall be a Site-
8 Local Unicast IPv6 Address, a Link-Local Unicast IPv6 Address or a Reserved IPv6 Address.
9 When the SectorID is a Site-Local Unicast IPv6 Address or a Link-Local Unicast IPv6
10 Address, the interface ID shall be a locally unique Modified EUI-64 value.
11 As is shown below for Site-Local Unicast, Link-Local Unicast and Reserved, there are
12 certain bits of the addresses that must take on fixed values in order to meet the IPv6
13 address requirements. The remaining bits (denoted by “S”) are used to create unique
14 SectorID values. Therefore, the number of bits available for creating the unique SectorID is
15 79, 63 and 120 bits for Site-Local Unicast, Link-Local Unicast and Reserved, respectively.
16
17 | 10 bits | 38 bits | 16 bits | 6 bits | 1 bit | 57 bits |
18 +------------+----------+----------+--------+-------+----------+
19 | 1111111011 | 00 ... 0 | SS ... S | SSSSSS | 0 | SS ... S |
20 +------------+----------+----------+--------+-------+----------+
21 Figure 13.9.2.1.2-1. “S” bits in the Site-Local Unicast IPv6 Address Format
22
23 | 10 bits | 54 bits | 6 bits | 1 bit | 57 bits |

24 +------------+----------+--------+-------+----------+
25 | 1111111010 | 00 ... 0 | SSSSSS | 0 | SS ... S |
26 +------------+----------+--------+-------+----------+
27 Figure 13.9.2.1.2-2. “S” bits in the Link-Local Unicast IPv6 Address Format
28
29 | 8 bits | 120 bits |

30 +----------+----------+
31 | 00 ... 0 | SS ... S |
32 +----------+----------+
33 Figure 13.9.2.1.2-3. “S” bits in the Reserved IPv6 Address Format
34 The “S” bits are further broken down into the following sub-fields
35
36 | #P bits | #T bits | #N bits | #X bits |
37 +-----------+----------+----------+----------+
38 | 00 ... 01 | TT ... T | NN ... N | XX ... X |
39 +-----------+----------+----------+----------+
13-14
1 Figure 13.9.2.1.2-4. sub-fields of the “S” bits
2 where the “T” bits identify the type of unique identifier (IPv4, GSM/UMTS or ANSI-41), the
3 “N” bits are the operator’s unique identifier, the “X” bits are operator selected bits (i.e., bits
4 selected by the operator).
5 The “P” bits, which are a run of zero or more 0’s followed by one 1, allow for flexible
6 positioning of the unique identifier within the IPv6 address. The number of “P” bits shall
7 be less than or equal to 64. This is to ensure that the addresses in the Reserved IPv6
8 address format category for SectorID do not collide with the Locally Unique SectorIDs
9 (because the number of leading zeros in the SectorID in the Reserved IPv6 address format
10 category is less than 72).
11 The “T” bits shall be chosen such that the values are prefix free.
12 The following sections specify how the “T” bits, the “N” bits, and the “X” bits are assigned
13 for each of the unique identifier types defined in this document (that is, ANSI-41,
14 GSM/UMTS, and IPv4).
15 14.9.2.1.2.113.9.2.1.2.1 ANSI-41 Method

16 Ignoring bits in the SectorID that shall take on fixed values in order to meet IPv6
17 requirements, the SectorID format is as follows:
18
19 | #P bits | 2 bit | 15 bits | #X bits |
20 +-----------+----------+----------+----------+
21 | 00 ... 01 | 00 | SID | XX ... X |
22 +-----------+----------+----------+----------+
23 | PP ... P | TT ... T | NN ... N | XX ... X |
25 the ANSI-41 Method
26 The “T” bits shall be set to the binary value ‘00’. The “N” bits shall be set to “SID”, which is
27 the ANSI-41 System Identifier that has been assigned to the operator. The “X” bits shall be
28 set by the operator and shall be chosen to ensure that the SectorID values and
29 corresponding UATI values are unique within the operator’s network. Therefore, there are
30 up to 61, 45, and 102 operator settable bits for Site-Local Unicast, Link-Local Unicast and
31 Reserved addresses, respectively.
32 14.9.2.1.2.213.9.2.1.2.2 GSM/UMTS Method

33 Ignoring bits in the SectorID that must take on fixed values in order to meet IPv6
35
36 | #P bits | 2 bits | 12 bits | 12 bits | #X bits |
37 +-----------+----------+---------+---------+----------+
38 | 00 ... 01 | 01 | MCC | MNC | XX ... X |
39 +-----------+----------+---------+---------+----------+
40 | PP ... P | TT ... T | NN ... N | XX ... X |
13-15
2 the GSM/UMTS Method
3 The “T” bits shall be set to the binary value ‘01’. The “N” bits shall be set to “MCC” and
4 “MNC”, which are the binary coded decimal versions of a Mobile Country Code and Mobile
5 Network Code pair that have been assigned to the operator. The “X” bits shall be set by the
6 operator and shall be chosen to ensure that the SectorID values and corresponding UATI
7 values are unique within the operator’s network. Therefore, there are up to 52, 36, and 93
8 operator settable bits for Site-Local Unicast, Link-Local Unicast and Reserved addresses,
9 respectively.
10 14.9.2.1.2.313.9.2.1.2.3 IPv4 Unique Identifier

11 Ignoring bits in the SectorID that must take on fixed values in order to meet IPv6
13
14 | PP ... P | 2 bits | #N bits | #X bits |
15 +-----------+----------+--------------------+----------+
16 | 00 ... 01 | 10 | IPv4 Subnet Prefix | XX ... X |
17 +-----------+----------+--------------------+----------+
18 | PP ... P | TT ... T | NN ... N | XX ... X |
20 the IPv4 Method
21 The “T” bits shall be set to the binary value ‘10’. The “N” bits are set to “IPv4 Subnet Prefix”,
22 which is a prefix of a globally unique IPv4 subnet assigned to the operator. The “X” bits
23 shall be set by the operator and shall be chosen to ensure that the SectorID values and
24 corresponding UATI values are unique within the operator’s network. Therefore, there are
25 52, 36, and 93 operator settable bits for Site-Local Unicast, Link-Local Unicast and
26 Reserved addresses, respectively, assuming that “IPv4 Subnet Prefix” is a 24-bit prefix
27 identifying an IPv4 class C subnet.
28 14.9.2.213.9.2.2 Construction of Locally Unique SectorID

29 The format of the Locally Unique SectorID is as follows:
30
31 | 72 bits | #X bits |
32 +-----------+-----------+
33 | 00 ... 0 | XX ... X |
34 Figure 13.9.2.2-1. Format of the Locally Unique SectorID
35 The “X” bits shall be set by the network to ensure the uniqueness of the SectorID
36 throughout the networks that the access terminal can visit.
13-16
1 14.1013.10 Generic Attribute Update Protocol
2 14.10.113.10.1 Introduction
3 The Generic Attribute Update Protocol provides a means to update protocol attributes. The
4 protocol uses an AttributeUpdateRequest message, an AttributeUpdateAccept message,
5 and an AttributeUpdateReject message to negotiate a mutually acceptable configuration.
6 The initiator uses the AttributeUpdateRequest message to provide the responder with a
7 proposed value for each attribute. The responder uses the AttributeUpdateAccept message
8 to accept the proposed values. If the responder is an access network, and if any of the
9 attribute values in the received AttributeUpdateRequest message is not acceptable to it,
10 then the access network sends the AttributeUpdateReject message, and the access
11 terminal and access network continue to use the previously negotiated values for the
12 attributes.
13 The access terminal is not allowed to send an AttributeUpdateReject message.
14 14.10.213.10.2 Procedures
15 14.10.2.113.10.2.1 Initiator Requirements

16 The access terminal and the access network shall not send an AttributeUpdateRequest
17 message if the ConfigurationLock public data of the Session Configuration Protocol is set to
18 Locked.
19 Unless indicated otherwise, the access terminal shall not send an AttributeUpdateRequest
20 message on the Access Channel. Unless indicated otherwise, the access network shall not
21 send an AttributeUpdateRequest message on the Control Channel.
22 The initiator shall include one attribute value for each attribute included in the
24 After sending an AttributeUpdateRequest message, the initiator should continue to use
25 previously negotiated values for attributes listed in the message until it receives either an
26 AttributeUpdateAccept message or an AttributeUpdateReject message. However, the
27 initiator should be prepared for the responder to begin using attribute values proposed by
28 the initiator in the AttributeUpdateRequest message.
29 If the initiator receives an AttributeUpdateAccept message, then it shall pair the received
30 message with the associated AttributeUpdateRequest message using the TransactionID
31 field of the messages. The initiator shall use the attribute values in the
32 AttributeUpdateRequest message as the configured attribute values. If the access terminal
33 receives an AttributeUpdateReject message, then it shall use the previously configured
34 values of the attributes included in the corresponding AttributeUpdateRequest message.
35 If the initiator does not receive the corresponding AttributeUpdateAccept or
36 AttributeUpdateReject message in response to the AttributeUpdateRequest message, it
37 should re-transmit the AttributeUpdateRequest message.
38 While the initiator is waiting for a response to an AttributeUpdateRequest message, it shall
39 not transmit another AttributeUpdateRequest message with a different TransactionID field
13-17
1 that requests reconfiguration of an attribute included in the original

3 14.10.2.213.10.2.2 Responder Requirements

4 After receiving an AttributeUpdateRequest message, the responder shall respond within
5 TTurnaround, where TTurnaround = 2 seconds, unless specified otherwise by the protocol which
6 uses the Generic Attribute Update Protocol.
7 If the responder is an access terminal, then
8 • The responder shall send an AttributeUpdateAccept message.
9 • Upon sending an AttributeUpdateAccept message, the responder shall begin using the
10 accepted attribute values.
11 If the responder is an access network, then
12 • If the responder finds the proposed value for each attribute in the
13 AttributeUpdateRequest message to be acceptable, then the responder shall send an
14 AttributeUpdateAccept message. Upon sending an AttributeUpdateAccept message, the
15 responder shall begin using the accepted attribute values.
16 • If the responder does not recognize an attribute or does not find a proposed attribute
17 value to be acceptable, then it shall send an AttributeUpdateReject message.
18 • If the responder sends an AttributeUpdateReject message, then it shall continue to use
19 the previously configured values of the attributes found in the corresponding
21 14.10.313.10.3 Message Formats

22 The specification of the Physical Layer channels on which the following messages are to be
23 carried; and, whether the messages are to be sent reliably or as best-effort, is provided in
24 the context of the protocols in which these messages are used.
25 14.10.3.113.10.3.1 AttributeUpdateRequest
27 given attribute.
28
Field Length (bits)

TransactionID 8
13-18
4 14.10.3.213.10.3.2 AttributeUpdateAccept
7
Field Length (bits)

TransactionID 8
12 14.10.3.313.10.3.3 AttributeUpdateReject
15
Field Length (bits)

TransactionID 8

21

TTurnaround Maximum time to respond to an 2 sec
AttributeUpdateRequest message.
13-19
1 14.1113.11 Linear Interpolation

2 The access terminal shall use the following procedure for linear interpolation:
3 3. Let f(x) be the one-dimensional function which is explicitly defined on some finite
4 set of x-axis points Σx.
5 4. Let y’ = f(x’) be the interpolated value of the function at the input x’.
6 5. If f(x) is explicitly defined at only one point on the x-axis, then set y’ equal to the
7 value of the function at that point.
8 6. If f(x) is explicitly defined at two or more points on the x-axis, continue as follows:
9 − If x’ is outside the range of Σx, then set x’ equal to the nearest value of Σx.
10 − Let x1, x2 be the points in Σx that are closest to x’, which satisfy the relation x1
11 ≤ x’ ≤ x2. Define y1, y2 as follows:
x y = f(x)
x1 y1
x2 y2
12 Then the value of y' is given by the equation:

13 y' = y1 + (y2 – y1) × (x’ – x1)/(x2 – x1)
14 The access terminal shall compute y' with an error of no more than ±2% of its true value.
13-20
1 14.1213.12 Bi-linear Interpolation

2 The access terminal shall use the following procedure for bi-linear interpolation:
3 1. Let f(x,y) be the two-dimensional function which is explicitly defined on some finite
4 set of x-axis and y-axis points, denoted Σx and Σy respectively.
5 2. Let z’ = f(x’,y’) be the interpolated value of the function at inputs x’ and y’.
6 3. If f(x,y) is explicitly defined at only one point on both the x-axis and y-axis, then
7 set z’ equal to the value of the function at that point.
8 4. If f(x,y) is explicitly defined at only one point on either the x-axis or the y-axis, then
9 use the procedure of 13.11 on the other axis, and set z’ to the result.
10 5. If f(x,y) is explicitly defined at two or more points for both the x-axis and the y-axis,
11 continue as follows:
12 − If x’ is outside the range of Σx, then set x’ equal to the nearest value of Σx.
13 − If y’ is outside the range of Σy, then set y’ equal to the nearest value of Σy.
14 − Let x1, x2 be the points in Σx that are closest to x’, which satisfy the relation x1
15 ≤ x’ ≤ x2. Let y1, y2 be the points in Σy that are closest to y’, which satisfy the
16 relation y1 ≤ y’ ≤ y2. Define z1, z2, z3, and z4 as follows:
(x,y) z = f(x,y)
(x1,y1) z1
(x2,y1) z2
(x1,y2) z3
(x2,y2) z4
17 Then the value of z' is given by the equation:

18 z’ = a × ( b × z4 + (1– b) × z2 ) + (1– a) × ( b × z3 + (1-b) × z1 )
19 where
20 a = (x’ – x1)/(x2 – x1)
21 b = (y’ – y1)/(y2 – y1)
22 The access terminal shall compute z' with an error of no more than ±2% of its true value.
13-21
1 14.1313.13 IIR filter implementation

2 The access terminal shall perform IIR filter implementation using the following equation:
3 y(n) = (1 – 1/τ) × y(n – 1) + (1/τ) × x(n)
4 where n denotes the time index in slots or sub-frames, τ denotes the filter time constant, y
5 denotes the IIR filter output and x denotes the IIR filter input. The filter shall be updated
6 every slot or every sub-frame. The filter update rate is a function of the quantity filtered.
7 The access terminal shall compute y(n) with an error of no more than ±2% of its true value.
13-22
Assigned Names And Numbers 3GPP2 C.S0024-B v2.0
1 1514 ASSIGNED NAMES AND NUMBERS
2 15.114.1 Protocols
3 Table 14.1-1 shows the Protocol Type and Protocol Subtypes assigned to the protocols
4 defined in this specification. An updated list of Protocol Types and Protocol Subtypes is
5 specified in [10].
14-1
3GPP2 C.S0024-B v2.0 Assigned Names And Numbers
1 Table 14.1-1. Protocol Type and Subtypes
Protocol Type Protocol Subtype Page

Name ID Length Name ID
(bits)
Physical Layer 0x00 7 Default Physical Layer 0x0000 10-1
Physical Layer 0x00 7 Subtype 1 Physical Layer 0x0001 10-1
Control Channel MAC 0x01 7 Default Control Channel 0x0000 9-4
MAC
Control Channel MAC 0x01 7 Enhanced Control Channel 0x0001 9-16
MAC
Access Channel MAC 0x02 7 Default Access Channel 0x0000 9-16
MAC
Access Channel MAC 0x02 7 Enhanced Access Channel 0x0001 9-51
MAC
Forward Traffic 0x03 7 Default Forward Traffic 0x0000 9-85
Forward Traffic 0x03 7 Enhanced Forward Traffic 0x0001 9-102
Forward Traffic 0x03 7 Multicarrier Forward Traffic 0x0001 9-135
Reverse Traffic 0x04 7 Default Reverse Traffic 0x0000 9-187
Reverse Traffic 0x04 7 Subtype 1 Reverse Traffic 0x0001 9-205
Reverse Traffic 0x05 7 Multicarrier Reverse Traffic 0x0004 9-382
Key Exchange 0x05 7 Default Key Exchange 0x0000 8-12
Key Exchange 0x05 7 DH Key Exchange 0x0001 8-16
Authentication 0x06 7 Default Authentication 0x0000 8-36
Authentication 0x06 7 SHA-1 Authentication 0x0001 8-40
14-2

(bits)
Encryption 0x07 7 Default Encryption 0x0000 8-47
Security 0x08 7 Default Security 0x0000 8-3
Security 0x08 7 Generic Security 0x0001 8-7
Packet Consolidation 0x09 7 Default Packet 0x0000 7-243
Consolidation
Air-Link Management 0x0a 7 Default Air-Link 0x0000 7-5
Management
Initialization State 0x0b 7 Default Initialization State 0x0000 7-21
Idle State 0x0c 7 Default Idle State 0x0000 7-29
Idle State 0x0c 7 Enhanced Idle State 0x0001 7-45
Idle State 0x0c 7 Quick Idle State 0x0002 7-71
Connected State 0x0d 7 Default Connected State 0x0000 7-71
Route Update 0x0e 7 Default Route Update 0x0000 7-111
Route Update 0x0e 7 Multicarrier Route Update 0x00000x00 7-172
01
Overhead Messages 0x0f 7 Overhead Messages 0x0000 7-252
Session Management 0x10 7 Default Session 0x0000 6-3
Management
Address Management 0x11 7 Default Address 0x0000 6-17
Management
Session Configuration 0x12 7 Default Session 0x0000 6-40
Configuration
Multimode Capability 0x1b 7 Generic Multimode 0x0001 6-76
Discovery Capability Discovery
Stream 0x13 7 Default Stream 0x0000 5-3
Virtual Stream 0x19 7 Generic Virtual Stream 0x0001 5-9
Stream 0 Application 0x14 7 Default Signaling 0x0000 2-1
Application
Stream 1 Application 0x15 7 Default Packet Application 0x0001 3-1
bound to the radio network.
bound to the service
14-3
3GPP2 C.S0024-B v2.0 Assigned Names And Numbers

(bits)
network
Stream 1 Application 0x15 7 Multi-Flow Packet 0x0004 4-1
Application bound to the
radio network.
service network.
Stream 1 Application 0x15 7 3G1X Circuit Services 0x0006 5-1
Notification Application
bound to the radio network
network
radio network.
service network.
bound to the radio network
network
radio network.
service network.
Virtual Stream VS 0x1a 15 3G1X Circuit Services 0x0006 5-1
14-4

(bits)
Application, where VS VS, Notification Application
is the two-digit where
hexadecimal virtual VS is
stream number in the the
range 0x01 to 0xff. two-
digit
hexad
ecima
l
virtua
l
strea
m
numb
er in
the
range
0x01
to
0xff
14-5

C.S0024-B v2.0 070624

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

C.S0024-B v2.0 070624

Caricato da

Copyright:

Formati disponibili

3GPP2 C.

Date: March 2007

cdma2000 High Rate Packet Data Air Interface

1 2 Default Signaling Application ...................................................................................... 2-1

1 2.6 Signaling Link Protocol ........................................................................................2-12

1 2.6.6.2 ResetAck ................................................................................................. 2-20

1 3.4.4.1.1.2.1 Reset Procedure for the Initiating Side ......................................3-6

1 3.5.4.3.2 Indications......................................................................................... 3-15

1 4.1 Introduction ..........................................................................................................4-1

1 4.4.4.1.1.2.5 RLP Reset Message Flows....................................................... 4-10

1 4.4.4.4.17 AttributeUpdateAccept .....................................................................4-31

1 4.6.4.2.1 LocationRequest ................................................................................ 4-38

1 5.3.2.3 Public Data ................................................................................................5-9

1 6.2.4 Protocol Initialization....................................................................................... 6-5

1 6.2.7 Configuration Attributes ................................................................................6-15

1 6.3.7.1.5.1 Access Terminal Requirements .................................................... 6-23

1 6.4.4.2 Protocol Initialization for the InUse Protocol Instance...............................6-42

1 6.4.6.2.11 DeletePersonalityAck ....................................................................... 6-62

1 7.2.6.1 Procedures .............................................................................................. 7-10

1 7.3.2.1 Commands ..............................................................................................7-21

1 7.4.2 Primitives and Public Data ............................................................................ 7-31

1 7.4.6.1.6.1 Access Terminal Requirements.....................................................7-39

1 7.5.6.1.1.1 Activate........................................................................................ 7-50

1 7.5.7.2.2 SlottedMode Attribute ........................................................................7-67

1 7.6.6.1.6.1 Access Terminal Requirements .................................................... 7-80

1 7.7.2.3 Public Data ............................................................................................7-103

1 7.7.9 Session State Information ........................................................................... 7-110

1 7.8.6.1.2.8 Remaining Set Management .......................................................7-123

1 7.8.6.2.5 NeighborList .................................................................................... 7-144

1 7.9.6.1.5.3 Processing the TrafficChannelAssignment Message in the Idle

1 7.9.7.2 Complex Attributes ................................................................................7-229

1 7.10.6.1.5 Access Network Procedures ........................................................... 7-248

1 7.11.5.3 Message Formats .................................................................................7-254

1 8.3.2.1 Commands ................................................................................................ 8-3

1 8.4.4.1 Protocol Initialization for the InConfiguration Protocol Instance .................8-7

1 8.5.5.3.1 ConfigurationRequest ........................................................................ 8-13

1 8.6.5.3.3 ANKeyComplete .................................................................................8-25

1 8.8.5.3.2 ConfigurationResponse ......................................................................8-42

1 8.9.5.4 Default Encryption Protocol Trailer.......................................................... 8-50

1 9.2.6.1.2 Control Channel Cycle .........................................................................9-9

1 9.3.4.1 Protocol Initialization for the InConfiguration Protocol Instance............... 9-17

1 9.3.7.2.3 Pad ....................................................................................................9-29

1 9.4.6.1.4.1 Access Terminal Requirements .................................................... 9-38

1 9.5.5.2 Commit Procedures .................................................................................9-53

1 9.5.7.1 InitialConfiguration Attribute................................................................... 9-82

1 9.6.6.1.5.1 DRC Requirements.......................................................................9-94

1 9.7.5.3 Message Formats................................................................................... 9-105

1 9.8.6.1.1.2 Construction of MAC Layer packets ........................................... 9-141

1 9.8.7.1 Simple Attributes ...................................................................................9-168

1 9.9.6.1.4.1 Access Terminal Requirements .................................................. 9-193

1 9.10.5.2 Commit Procedures..............................................................................9-207

1 9.10.7.2 RateParameters Attribute .................................................................... 9-221

1 9.12.6.1.6 Open State .....................................................................................9-286

1 9.12.7.2.8 PowerParameters128 Attribute ...................................................... 9-342

1 9.13.5.2 Commit Procedures..............................................................................9-385

1 9.13.6.2.1 MAC Layer Trailer .......................................................................... 9-415

1 9.13.7.2.17 PowerParameters2048 Attribute...................................................9-471

1 10.3.1.2.3.2 Standby Output Power .............................................................10-13

1 10.3.1.3.8.3 Baseband Filtering ................................................................... 10-44

1 10.4.1.3.2.3.5 Modulation .........................................................................10-71

1 11.1.5.3.1 ConfigurationRequest ...................................................................... 11-3

1 11.3.1.2.4 Controlled Output Power................................................................11-11